Upgrade Policy for Istio

#1

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

#2

Iris,

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.

Cheers
-steve

#3

Is there an upgrade path from 1.0.2 to 1.0.6? The official docs seem clear about how to upgrade from 1.0.6 to 1.1.x.

The uncertain part is how policies have changed between 1.0.2 and 1.1.0, an example is this: https://twitter.com/linsun_unc/status/1098429168025550848?s=12

#4

Would recommend you to upgrade from 1.0.2 to 1.0.6 first before moving to 1.1. There is not much behavior changes between 1.0.2 to 1.0.6.

Lin

#5

Thanks Steve. Looking forward to our official statement about this!

Best Regards,

Iris Ding

#6

Thanks Lin, we were planning to test it out in our development kubernetes cluster.