Deprecated note/link on page "Set up a High Availability etcd Cluster with kubeadm"

[DC4JG]

The note at the top of the page states that in regards to certificate rotation "The long-term plan is to empower the tool etcdadm to manage these aspects.".

The linked etcdadm repository was archived on Jul 16, 2024 and is part of Kubernetes Retired.

Is there some other tool available for the stated feature set (then please update the note) or is this note deprecated and support/development was dropped? A quick search yielded this issue linking etcd-manager as possible successor but I'm not qualified to provide further insight.

I'm just a newbie reading the docs and noticing a "dead" link in the documentation 😇

[neolit123]

The note at the top of the page states that in regards to certificate rotation "The long-term plan is to empower the tool etcdadm to manage these aspects.".

etcdadm used etcd-manager but we don't have a direct CLI replacement to apply in the docs. so +1 to remove the note for the time being,

/sig cluster-lifecycle /help /kind deprecation /triage accepted

steps:

• edit the page https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/
• remove the note:

Note:
While kubeadm is being used as the management tool for external etcd nodes in this guide, please note that kubeadm does not plan to support certificate rotation or upgrades for such nodes. The long-term plan is to empower the tool [etcdadm](https://github.com/kubernetes-sigs/etcdadm) to manage these aspects.

• send a PR for this repository's main branch

[k8s-ci-robot]

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

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

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

In response to [this](https://github.com/kubernetes/website/issues/47818): >> The note at the top of [the page](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/) states that in regards to certificate rotation "The long-term plan is to empower the tool [etcdadm](https://github.com/kubernetes-sigs/etcdadm) to manage these aspects.". > >etcdadm used etcd-manager but we don't have a direct CLI replacement to apply in the docs. so +1 to remove the note for the time being, > >/sig cluster-lifecycle >/help >/kind deprecation >/triage accepted > >steps: >- edit the page https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/ >- remove the note: > >``` >Note: >While kubeadm is being used as the management tool for external etcd nodes in this guide, please note that kubeadm does not plan to support certificate rotation or upgrades for such nodes. The long-term plan is to empower the tool [etcdadm](https://github.com/kubernetes-sigs/etcdadm) to manage these aspects. >``` > >- send a PR for this repository's `main` branch > > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[neolit123]

/remove-kind deprecation /kind cleanup

[steve-hardman]

I can help with this.

/assign