<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Stack on Arian Svirsky | DevOps Engineering</title><link>/skills/</link><description>Recent content in Stack on Arian Svirsky | DevOps Engineering</description><generator>Hugo</generator><language>en</language><atom:link href="/skills/index.xml" rel="self" type="application/rss+xml"/><item><title>Tools &amp; Technologies</title><link>/skills/overview/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/skills/overview/</guid><description>&lt;p>Not a checklist — these are things I actually use in production and have opinions about.&lt;/p>
&lt;h2 id="kubernetes">Kubernetes&lt;/h2>
&lt;p>EKS, GKE — I&amp;rsquo;ve run clusters on both. Helm for packages, Kustomize for overlays, ArgoCD for GitOps. Opinions: Autopilot is great until you need node-level access. Managed node groups are the sweet spot for most teams.&lt;/p>
&lt;h2 id="infrastructure-as-code">Infrastructure as Code&lt;/h2>
&lt;p>Terraform for cloud resources (modules, remote state, workspaces). Pulumi when the team prefers real programming languages over HCL. I&amp;rsquo;ve used both in production and can argue for either depending on the context.&lt;/p></description></item></channel></rss>