GitOps, A Slightly Realistic Situation on Kubernetes with Flux
You’re tired of talks that deploy hello-worlds to demonstrate the relevance of the younameit tool. That’s good news: what we’re interested in is trying out a slightly realistic DevSecOps situation. So we’re going to build a step-by-step enterprise scenario where devs and ops collaborate on a daily basis around a GitOps workflow based on Kubernetes and Flux. The dev teams deploy / update / rollback Pokémon WebApps using Kustomize and/or Helm charts. On the Ops side, we take care of the platform’s security issues by implementing Kyverno: segregation of team rights, WebApps network flows and control of activities on the cluster. And we monitor everything via Prometheus and Grafana. Finally, we will see how to articulate upgrade and configuration while respecting the blue/green pattern and canary deployment, thanks to Istio. At the end of this hands-on, you may have discovered some technologies. But above all you will have seen how to implement them in a dev-to-prod process that resembles a real case.
