Upgrade Policy for Istio


HI Team,

I have several questions for the upgrade scenario for Istio, Seems I can not find clear answer in our docs yet:

What version span do we support when upgrade? do we support upgrade from 1.0.0 to 1.1 directly?

When upgrade, how about the existed crd resources I defined? Do they suppose to work without any change with the new crd in latest istio version?

How about Envoy version span do we support? Can I only upgrade control plane?

Thanks a lot if some one can share some lights there!

Iris Ding



Good questions. The environments workgroup meets Wednesday and I will add this topic to the agenda. We have no formal policy.

What I have been enforcing and telling individuals that ask is:
1.0.6->1.1.0 is supported with helm upgrade/helm rollback and kubectl apply
Existing custom resources are maintained
Data plane is upgradeable

But lets come out with an official statement at the environments workgroup meeting.