<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ArgoCD on Nahuel Hernandez</title>
    <link>https://nahuelhernandez.com/tags/argocd/</link>
    <description>Recent content in ArgoCD on Nahuel Hernandez</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 22 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nahuelhernandez.com/tags/argocd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Translating an AWS EKS Stack to Azure AKS: The Architectural Decisions Behind a Real Migration</title>
      <link>https://nahuelhernandez.com/blog/translating_eks_to_aks_migration/</link>
      <pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://nahuelhernandez.com/blog/translating_eks_to_aks_migration/</guid>
      <description>There is a comforting table on Microsoft Learn that maps AWS services to Azure services. RDS to Flexible Server. Cognito to Entra ID B2C. SQS to Service Bus. ECR to ACR. S3+CloudFront to Blob+Front Door. The table is correct. It is also misleading, because it implies the migration is a translation problem.
It is not. The translation is the easy part. The hard part is the sequence of architectural decisions you have to make once you accept that some services do not translate cleanly, that some Azure equivalents are better, that some are worse, and that doing a literal one-to-one mapping is the most expensive way to ship.</description>
    </item>
    
    <item>
      <title>GitOps Meets Auto-Scaling: How ArgoCD and Karpenter Should Be Designed Together on EKS</title>
      <link>https://nahuelhernandez.com/blog/argocd_karpenter_design_eks/</link>
      <pubDate>Fri, 14 Nov 2025 00:00:00 +0000</pubDate>
      
      <guid>https://nahuelhernandez.com/blog/argocd_karpenter_design_eks/</guid>
      <description>Most EKS clusters I have audited in the last two years have ArgoCD installed and Karpenter installed. Almost none of them have those two things designed to work together. ArgoCD is set up by the platform team, Karpenter is set up later by the cost-optimization initiative, and the two run side by side without anyone owning the gap between them.
That gap is where you get the weird Sunday-night incidents. A new app rolls out, ArgoCD marks it as Healthy, Karpenter is busy consolidating the cluster, and 15% of your replicas end up Pending for 90 seconds.</description>
    </item>
    
  </channel>
</rss>
