Yes, it's fine to run +/- 1 minor release between your control plane and your nodes. And in the special case of 3.7 and 3.9 we've tested that 3.7 nodes against 3.9 control plane, it's not safe to generally assume that we'd ever support a two version delta elsewhere though.
On Thu, May 10, 2018 at 5:20 AM, Shake Chen <[email protected]> wrote: > HI > > I have test update. only would cause the docker restart. > > you can update from 3.6 to 3.7, 3.7 to 3.9. > > On Thu, May 10, 2018 at 4:08 PM, Brian Holsen <[email protected]> > wrote: > >> >> >> I’m planning to upgrade a Openshift Origin 3.6 cluster to 3.9, which has >> 3 masters, 3 etcd, 2 infra nodes and 8 nodes for common use. >> >> It’s not possible to just run the upgrade yaml, cause it will take A LOT >> of time. I’d like to know if it’s possible that I can do the upgrade like >> this: >> >> 1. Update control plane to 3.7 at night, after the upgrade, let it >> run as is >> 2. Update nodes to 3.7 through 2 or more nights, to reduce cluster >> down time >> 3. Repeat step1&2 to upgrade to 3.9 >> >> >> >> I didn’t find any mention on the official docs that clears if master and >> node of different version (eg. Masters of v3.7 and nodes of v3.6) could >> co-exist, and also for nodes of different versions(eg. Nodes of v3.6 and >> Nodes of v3.7) >> >> Thanks. >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >> > > > -- > Shake Chen > > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
