AKS Coaching
Budget: ₹400 – ₹750 INR
I’m preparing for an interview that will probe deeply into Azure Kubernetes Service rolling upgrades, and I’d like a seasoned AKS engineer to walk me through the topic—especially how to handle rollback scenarios when things go sideways.
During our session I want to focus on real-world production incidents I’ve faced: pods refusing to start, brief but alarming service disruptions, and the occasional network blip that breaks communication between nodes. I need you to dissect each situation, show why it happens during an upgrade, and demonstrate how an effective rollback strategy brings the cluster back to a healthy state.
Please structure the discussion around practical, example-driven explanations rather than theory dumps. If you can share kubectl commands, upgrade wave configurations, or sample Helm charts that illustrate a smooth rollback, that will make the content stick. A short diagram or two is welcome, but live or recorded walkthroughs of the commands and manifests will be most valuable.
Deliverables
• 60-90 min hands-on coaching call (recording allowed)
• Companion notes or code snippets used during the walkthrough
• Quick-reference checklist I can review right before the interview
If you’ve led AKS upgrades in production and have war stories (and fixes) to prove it, I’m eager to learn from you.
During our session I want to focus on real-world production incidents I’ve faced: pods refusing to start, brief but alarming service disruptions, and the occasional network blip that breaks communication between nodes. I need you to dissect each situation, show why it happens during an upgrade, and demonstrate how an effective rollback strategy brings the cluster back to a healthy state.
Please structure the discussion around practical, example-driven explanations rather than theory dumps. If you can share kubectl commands, upgrade wave configurations, or sample Helm charts that illustrate a smooth rollback, that will make the content stick. A short diagram or two is welcome, but live or recorded walkthroughs of the commands and manifests will be most valuable.
Deliverables
• 60-90 min hands-on coaching call (recording allowed)
• Companion notes or code snippets used during the walkthrough
• Quick-reference checklist I can review right before the interview
If you’ve led AKS upgrades in production and have war stories (and fixes) to prove it, I’m eager to learn from you.