DevOpsDreams

Progressive Delivery on Kubernetes: Canary, Blue-Green, and the Control Plane You Actually Need Canary and blue-green deployments solve different operational problems. This guide shows how to run both on Kubernetes with safer promotion, rollback, and traffic control. TL;DR Progressive delivery on Kubernetes is more than applying a new Deployment manifest and hoping the rollout settles cleanly. Native Deployments handle rolling updates well, but production canary and blue-green strategies need explicit promotion steps, analysis gates, and traffic control. In practice, that usually means adding a rollout controller such as Argo Rollouts or Flagger, wiring it to metrics, and designing rollback paths before release day. If you do that work up front, you reduce blast radius, shorten incident response, and make release behavior much more predictable. Argo Rollouts icon. The updated article covers canary and blue-green strategies, analysis gates, and promotion control. Rolling Updates Are...

Progressive Delivery with Canary and Blue-Green on Kubernetes As you rollout a new version of your Android app, you want to make sure that users don't experience any issues. But with the Android 17 Beta introducing a Secure-By-Default Architecture, you'll need to adapt your deployment strategy to ensure a seamless transition. TL;DR Implement canary releases to test new versions of your app before rolling out to all users. Use blue-green deployments to switch between two versions of your app with minimal downtime. Set up rolling updates to gradually migrate users to the new version. Monitor progress and roll back if necessary. Be aware of common pitfalls such as incomplete rollbacks, stuck deployments, and poor monitoring. Introducing Progressive Delivery on Kubernetes Progressive delivery is a strategy for deploying new versions of your application in a controlled manner, minimizing the risk of failures and downtime. Two popular techniques for...