Hi Kubernetes Users and Dev
I have a HA cluster with 1.3.6 running. I have three masters, each running
apiserver, kube-scheduler and controller-manager and etcd running. I want
to upgrade to 1.5.2 without bringing the cluster down.
I was thinking a couple of ways:-
Method 1:
1. Bring one master down and upgrade, while maintaining the quorom for
etcd
2. The new master comes up as 1.5.2 while the remaining continue to run
as 1.3.6
3. In this scenario
1. If kubelets running as 1.3.6 try to talk to new master 1.5.2, will
that work ?
2. Is that supported scenario ?
3. What about kube-proxy ?
4. Will the api-server running as 1.5.2 be able to talk to kubelets
Method 3:
The other way would be to partition the cluster , and move some minions and
a single master to new 1.5.2. That is not preferable imo.
Are there other ways people can think of making this work ?
-Mayank
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
