All Topics
All Topics
Technology
Technology
AI
AI
Business
Business
Entertainment
Entertainment
News
News
Programming
Programming
Science
Science
Design
Design
Environment
Environment
Finance
Finance
Crypto
Crypto
Politics
Politics
Sports
Sports
Education
Education
Gaming
Gaming
Art
Art
Music
Music
Health
Health
Security
Security
Books
Books
Food
Food
Travel
Travel
Personal
Personal
Bluesky
Twitter

Implementing Ringed Canary Deployments on AKS with Azure Developer CLI, Bicep, Helm, and ArgoRollouts

By

Luke Murray

3d ago· 9 min readen

Summary

This article details how to implement ringed (canary) deployments for Azure Kubernetes Service (AKS) using Azure Developer CLI (AZD), Bicep, Helm, and ArgoRollouts. The author shares their experience building a Fan Intelligence proof-of-technology for the FIFA World Cup 2026, emphasizing the need for safe, multi-region deployment strategies with health gates and instant rollback capabilities. The post provides a technical walkthrough of setting up progressive delivery pipelines that minimize blast radius and ensure high availability for mission-critical applications serving millions of users.

Source

bskyImplementing Ringed Canary Deployments on AKS with Azure Developer CLI, Bicep, Helm, and ArgoRolloutsluke.geek.nz

Key quotes

· 3 pulled
When you have millions of fans receiving real-time notifications during a live match, the last thing you want is a bad deploy taking down a region.
The default approach for a lot of Kubernetes projects is kubectl apply and hoping for the best. That works for a dev cluster. It does not work when your RTO is measured in minutes and your blast radius spans multiple continents.
This post covers the ringed deployment pipeline
Snippet from the RSS feed
Ringed, multi-region canary deployments with Azure Developer CLI, Bicep, Helm & ArgoRollouts—automated AKS rollouts with health gates and instant rollback.

You might also wanna read

Comments

Sign in to join the conversation.

No comments yet. Be the first.