GitOps A/B testing with Istio and Helm
2 likes1,880 views
This document discusses using GitOps and Helm to perform A/B testing with Istio on Kubernetes clusters. It introduces Weave Flux, an open source GitOps operator for Kubernetes that implements a control loop to continuously apply the desired application state from a Git repository. The Weave Flux Helm operator extends this to automate Helm chart releases defined as custom resources. An example is provided of setting up GitOps with Weave Flux and the Helm operator to perform A/B testing on an application by managing different versions through a Helm chart. Links are included to GitOps examples for Helm and Istio configurations.
GitOps A/B testing with Istio and Helm
- 1. A/B Testing with Istio and Helm The GitOps Way Stefan Prodan - stefan@weave.works London August 2018 1
- 2. ● Building cloud-native OSS since 2014 (Weave Net, Moby, Kubernetes, Prometheus) ● Founding member of CNCF ● Alexis Richardson (Weaveworks CEO) is chair of the CNCF Technical Oversight Committee ● Weave Cloud runs on Kubernetes since 2015 2 About Weaveworks
- 3. Introducing GitOps GitOps builds on DevOps with Git as a single source of truth for the desired state of the system ● The entire system state is under version control and described in a single Git repository ● Operational changes on production clusters are made by pull request ● Rollback and audit logs are provided via Git ● When disaster strikes, the whole infrastructure can be quickly restored from Git
- 4. CI Image RegistryCode Repo Typical CICD pipeline ClusterDev RW RW RWRW RO RW RO
- 5. CICode Repo Kubernetes API GitOps CICD pipeline Dev RO RO CD OperatorRO RW RW RW RW Image Registry Config Repo
- 6. Weave Flux - The GitOps Kubernetes Operator Weave Flux implements a control loop that continuously applies the desired state to your cluster, offering protection against harmful actions like deployments deletion or network policies altering. Weave Flux Helm Operator provides an extension to Weave Flux that automates Helm Chart releases for it. A Chart release is described through a Kubernetes custom resource named FluxHelmRelease.
- 7. Weave Flux OSS 7 Setup helm repo add weaveworks https://weaveworks.github.io/flux helm install --name flux weaveworks/flux --namespace flux --set helmOperator.create=true --set helmOperator.git.chartsPath=charts --set git.url=ssh://git@github.com/stefanprodan/gitops-istio --set git.branch=ab-testing
- 9. Flux Helm Release custom resource 9 apiVersion: helm.integrations.flux.weave.works/v1alpha2 kind: FluxHelmRelease metadata: name: frontend namespace: demo annotations: flux.weave.works/automated: "true" flux.weave.works/tag.chart-image: semver:~1.0 spec: chartGitPath: podinfo releaseName: frontend values: image: quay.io/stefanprodan/podinfo:1.0.0
- 11. GitOps Demo A/B Testing with Istio 11
- 12. A/B Testing Initial State 12
- 13. A/B Testing Desired State 13
- 14. GitOps Examples 14 ● Helm ○ https://github.com/stefanprodan/gitops-helm ● Istio ○ https://github.com/stefanprodan/gitops-istio