Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

new post proposal "Upgrading a existing single master cluster created with kubeadm to a HA master smoothly" #10384

Closed
Lentil1016 opened this Issue Sep 26, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@Lentil1016
Copy link
Contributor

Lentil1016 commented Sep 26, 2018

This is a Feature propose

  • Feature Request
  • Bug Report

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?

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:

  • delete old KubeConfig manifest/etcd pki/etcd-server pki/etcd-peer pki/apiserver
  • recreate them using kubeadm alpha phase command with HA configure
  • restart apiserver/controller/scheduler/etcd containers
  • change old ETCD master's PeerUrl from https://127.0.0.1:2380 to https://{CP0_IP}:2380

then this single master will be able to joined by other master, and upgrade to a HA master

@Lentil1016

This comment has been minimized.

Copy link
Contributor Author

Lentil1016 commented Sep 26, 2018

/assign @Lentil1016

@neolit123

This comment has been minimized.

Copy link
Member

neolit123 commented Sep 26, 2018

@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!

/cc @kubernetes/sig-cluster-lifecycle
/assign @chuckha @liztio

@Lentil1016

This comment has been minimized.

Copy link
Contributor Author

Lentil1016 commented Sep 26, 2018

@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.

Expecting for further feedback.

@Lentil1016

This comment has been minimized.

Copy link
Contributor Author

Lentil1016 commented Oct 23, 2018

I'll close this unnecessary proposal, Thanks for the feedback.

@Lentil1016 Lentil1016 closed this Oct 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.