<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AKS on Saurabh Chaubey</title>
    <link>https://saurabh-chaubey.com/tags/aks/</link>
    <description>Recent content in AKS on Saurabh Chaubey</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 20 Sep 2025 10:00:00 +0000</lastBuildDate><atom:link href="https://saurabh-chaubey.com/tags/aks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrating 70&#43; Microservices to Azure Kubernetes Service — A Platform Engineer&#39;s Playbook</title>
      <link>https://saurabh-chaubey.com/post/cloud/migrating-microservices-to-azure-kubernetes-service/</link>
      <pubDate>Sat, 20 Sep 2025 10:00:00 +0000</pubDate>
      
      <guid>https://saurabh-chaubey.com/post/cloud/migrating-microservices-to-azure-kubernetes-service/</guid>
      <description>Migrating a handful of microservices to Kubernetes is one thing. Migrating over seventy — with their interconnected dependencies, legacy configurations, and the weight of years of organic growth — is an entirely different challenge. This is the story of how our platform engineering team planned and executed a large-scale migration from on-premises infrastructure to Azure Kubernetes Service (AKS) at a major enterprise insurance company, and the lessons we learned along the way.</description>
    </item>
    
  </channel>
</rss>
