You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: I'm intend to contribute a guide that helping "Upgrading a existing single master cluster created with kubeadm to a HA master smoothly", but I'm not sure where should I put it to. Also the post name I should use in URL.
Proposed Solution: My best guess is content/en/docs/setup/independent/into-high-availability.md and https://kubernetes.io/docs/setup/independent/into-high-availability/, is that cool?
For those who put a single master kubernetes cluster created with kubeadm into used, they might not likely to recreate their cluster. this post will help them to make their single master HA without recreate it. They will only need to:
delete old KubeConfigmanifest/etcdpki/etcd-serverpki/etcd-peerpki/apiserver
recreate them using kubeadm alpha phase command with HA configure
@lentil1016
thanks for the proposed idea.
my initial feedback here would be that this is probably not necessary given we have the other guide, but i would leave it to others to comment further and make the decision!
@neolit123
♥ Thanks for feedback.
Actually, the procedures of "upgrading old cluster" is only a little different from "creating a new one". So I'm also thinking insert it into this post Creating Highly Available Clusters with kubeadm rather than create a new page. But I'm not sure if that will make this post not easy to be searched by the user, for it will make this post meets two needs.
This is a Feature propose
Problem: I'm intend to contribute a guide that helping "Upgrading a existing single master cluster created with kubeadm to a HA master smoothly", but I'm not sure where should I put it to. Also the post name I should use in URL.
Proposed Solution: My best guess is
content/en/docs/setup/independent/into-high-availability.md
andhttps://kubernetes.io/docs/setup/independent/into-high-availability/
, is that cool?Page to Update:
https://kubernetes.io/docs/setup/independent/into-high-availability/
For those who put a single master kubernetes cluster created with kubeadm into used, they might not likely to recreate their cluster. this post will help them to make their single master HA without recreate it. They will only need to:
KubeConfig
manifest/etcd
pki/etcd-server
pki/etcd-peer
pki/apiserver
kubeadm alpha phase
command with HA configureapiserver
/controller
/scheduler
/etcd
containersthen this single master will be able to joined by other master, and upgrade to a HA master
The text was updated successfully, but these errors were encountered: