<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Karpenter on Nahuel Hernandez</title>
    <link>https://nahuelhernandez.com/tags/karpenter/</link>
    <description>Recent content in Karpenter on Nahuel Hernandez</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 19 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nahuelhernandez.com/tags/karpenter/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Running MCP Servers on EKS: Architecture for Production Agentic Workloads</title>
      <link>https://nahuelhernandez.com/blog/mcp_servers_on_eks_production/</link>
      <pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://nahuelhernandez.com/blog/mcp_servers_on_eks_production/</guid>
      <description>For most of 2025, MCP servers lived on developer laptops. You connected your editor or your local Claude client to a stdio process, the process held a session, you were the only user. Production was not a concern because there was no production.
That changed quickly. By the back half of 2025, internal teams started exposing MCP servers as shared infrastructure. Wrap an internal API, an EKS cluster, a Postgres database, or a SaaS account in MCP, deploy it, point an agent or a fleet of agents at it.</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>
