The Fine Art of Canary Deployments
Canary Deployments are the last ingredient of any Continuous Delivery or Continuous Deployment rollout. A canary deployment is a deployment strategy that releases an application or service incrementally to a subset of users. All infrastructure in a target environment is updated in small phases (e.g., 2%, 25%, 75%, 100%). This control makes a canary release the lowest risk-prone compared to all other deployment strategies, like the blue-green strategy. If you need to back out of a production deployment quickly without much disruption, then canary deployments may be an excellent practice to set up.
We will treat this talk like a recipe so that you can set up a canary in your work environment.
- Continuous Integration, Continuous Delivery,
- Continuous Deployment Overview
- You can perform this anywhere: Cloud instances or Kubernetes
- What is Canary? What are some of the strategies you can use?
- What CD Frameworks perform Canary Deployments?
- How do you perform metrics? Are things going too slow or too fast?
- How do you back out if this rollout is not performing as well as it should?
- Can you perform canary deployments without a CD framework? Perhaps something native to Kubernetes?
- Performing using Spinnaker, Argo, Istio
- Conclusion
About Daniel Hinojosa
Daniel is a programmer, consultant, instructor, speaker, and recent author. With over 20 years of experience, he does work for private, educational, and government institutions. He is also currently a speaker for No Fluff Just Stuff tour. Daniel loves JVM languages like Java, Groovy, and Scala; but also dabbles with non JVM languages like Haskell, Ruby, Python, LISP, C, C++. He is an avid Pomodoro Technique Practitioner and makes every attempt to learn a new programming language every year. For downtime, he enjoys reading, swimming, Legos, football, and barbecuing.
More About Daniel »