<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Eks on Ajay Dhungel</title>
    <link>/tags/eks/</link>
    <description>Recent content in Eks on Ajay Dhungel</description>
    <generator>Hugo 0.125.0</generator>
    <language>en</language>
    <copyright>DevOps Engineer | Cloud Infrastructure | AWS</copyright>
    <lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/eks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>One Command to a Running Cluster: Terraform, ArgoCD, and the GitOps Handoff</title>
      <link>/posts/terraform-argocd-gitops/</link>
      <pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate>
      <guid>/posts/terraform-argocd-gitops/</guid>
      <description>Introduction When I started using Terraform and Kubernetes together, one question kept coming up: where does Terraform stop and something else begin?&#xA;The easy answer is to let Terraform manage everything. It can install Helm charts, create Kubernetes resources, manage namespaces. But Terraform tracks state as a snapshot. It knows what it deployed, but has no idea what is actually running. If a deployment crashes, if pods are stuck pending, if someone deletes something manually, Terraform does not know and does not care.</description>
    </item>
  </channel>
</rss>
