Istio 1.7.6

[cbron]

https://istio.io/latest/news/releases/1.7.x/announcing-1.7.6/

[cbron]

May close in favor of #30410

[cbron]

Ideally we can do 1.7.5 and 1.8 in 2.5.5. We'll see if thats feasible. Typically we don't release 2 charts at the same time, but once we move to 1.8 it's hard to go back to release 1.7.x, so doing it now is better. And we have to release 1.8.

[anupama2501]

Verified the following cases on
Rancher Version:
Rancher | v2.5-8d5b3b8d933d04b04e0f0ae3a23d48d0a962c53f-head
User Interface | v2.5-dev
Helm | v2.16.8-rancher1
Machine | v0.15.0-rancher49

1. Create a cluster as a standard user
2. Install v2 monitoring and istio [jaeger and ingress enabled]
3. Create a namespace[enable istio-injection] for the demo app
4. Deploy demo bookservice app
5. From the Istio Overview page, Access Kiali and view the traffic graph
6. Deploy the weight based routing yaml to update the weights for traffic routing to a specific version of the reviews service
7. Check the app and graph and see traffic only directed to based on the weights of the reviews service in yaml

Installed istio 1.7.301 and upgraded it to 1.7.600. Performed the above 7 steps and verified everything is working as expected.
Uninstalled 1.7.301 and re-installed 1.7.600:
Seeing an issue: rancher/dashboard#2222
Performed the steps 1 through 7 and verified everything is working as expected

[brendarearden]

Will be skipping this Istio version in favor of 1.8.1.

[armsnyder]

Can we please re-open this @brendarearden @cbron? The Istio 1.8 upgrade notes state that you cannot upgrade from <1.7.5 to 1.8.x without seeing connectivity issues that require manual intervention to fix. See the note here: https://istio.io/latest/news/releases/1.8.x/announcing-1.8/upgrade-notes/#connectivity-issues-among-your-proxies-when-updating-from-1-7-x-where-x-5

Going forward can we consider this chart to be production-ready, or will there be more breaking changes like this one such that we'd be better off using the upstream Istio installation methods? 😭

[brendarearden]

@armsnyder Thank you for bringing this to our attention! We are looking into it right now and hope to have a solution for you soon! we will also be making slight changes to how to maintain our istio chart to ensure we are staying production-ready and up to date with upstream istio for future releases.