Read on Twitter
Next I'm watching @stefanprodan talk about Progressive Delivery Techniques with Flagger. #KubeCon
They made Flagger to make more safe deployments, with things like automated rollbacks. #KubeCon
Flagger is on GitHub here: https://github.com/weaveworks/flagger #KubeCon
Running your pipeline again to roll back may mean you get a new artifact. #KubeCon
We can use the CD part of the pipeline instead, leaving off the CD part. With GitOps you can version your infra and app deployments. #KubeCon
CD challenges. [The question about whether multiple versions can run at the same time is a big one.]
![CD challenges. [The question about whether multiple versions can run at the same time is a big one.]](https://pbs.twimg.com/media/EnN91F6UUAATX73.jpg "CD challenges. [The question about whether multiple versions can run at the same time is a big one.]")
Progressive Delivery with Flagger #KubeCon
Oh there’s a TGIK on it. Thanks @timmycarr :) https://twitter.com/timmycarr/status/1329544311608897539
Good discussion on how Flagger works with Canaries, A/B testing, and Blue/Green deployments. [Deployment safety is one of the biggest things that impacts the quality of life for oncall folks. If you can make deployments routine and safe, you can sleep a lot better.] #KubeCon
Demo time :) Using Flux, Linkerd and Contour. #KubeCon
[I can't hear Progressive Delivery without thinking of @monkchips.] #KubeCon
