Document uprating a non High Available kubeadm cluster to HA

[lianghao208]

As what was discussed in Slack Channel, I think an instruction docs for kubeadm to transfer a non High Available cluster to a High Available cluster is necessary.

[neolit123]

a new page under tasks can be added for that.
but i would defer to community members / users to contribute that instead of the kubeadm maintainers.

currently the scenario of not using an LB is mostly claimed as unsupported with some notes here:
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#considerations-about-apiserver-advertise-address-and-controlplaneendpoint

/sig cluster-lifecycle
/help

PRs welcome.

[k8s-ci-robot]

@neolit123:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

a new page under tasks can be added for that.
but i would defer to community members / users to contribute that instead of the kubeadm maintainers.

currently the scenario of not using an LB is mostly claimed as unsupported with some notes here:
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/#considerations-about-apiserver-advertise-address-and-controlplaneendpoint

/sig cluster-lifecycle
/help

PRs welcome.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sftim]

/retitle Document uprating a non High Available kubeadm cluster to HA
/language en

[sftim]

/triage accepted
/priority backlog

[lianghao208]

Any updates on this issue?

[sftim]

This issue is ready for a contributor to work on it. SIG Docs has not made work on this a priority for the current quarterly plan.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[sftim]

/lifecycle frozen

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[sftim]

/triage accepted
Still worth doing

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[divya-mohan0209]

This is still worth doing IMO.
/triage accepted