A writeup from a live AKS workshop using Pulumi with C#, covering six practical Kubernetes recommendations: choosing a familiar language for IaC, enabling Cilium on AKS for eBPF networking, using stack-aware AI assistants for debugging, leveraging Pulumi's Terraform module support for gradual migration, splitting slow infrastructure from fast workloads into separate Pulumi stacks, and adopting GitOps with Argo CD or Flux. The post also covers a real-world Docker Hub rate limiting incident that disrupted the live demo and how it was resolved by building images directly in Azure Container Registry.
Table of contents
1. Pick the language your team already usesAside: everyone’s path ran through Docker Swarm2. Use Cilium on AKS if you can3. Debugging Kubernetes is easier when your tools have the full context4. You don’t have to abandon Terraform to start5. Split slow infrastructure from fast workloads6. GitOps is the wayTry it yourself14.2K Impressions1 Comment