The presentation discusses the challenges of upgrading Istio and proposes a GitOps approach to automate service mesh upgrades.
- Upgrading Istio is difficult and time-consuming
- 88% of Istio installations still have known CVEs despite efforts to make upgrades easier
- The GitOps approach using Flux and Flagger can automate Istio upgrades and improve observability
- The Helm controller in Flux provides a better experience than the Istio operator
- Istio upgrades should be treated like any other piece of infrastructure and automated using GitOps
The speaker emphasizes the importance of automating Istio upgrades and not treating it as a unique and special piece of infrastructure. They caution against using the Istio operator and recommend using the Helm controller in Flux instead. The GitOps approach using Flux and Flagger can improve observability and automate upgrades, making it easier for users to keep Istio up to date.