Improvement for k8s.io/docs/tasks/administer-cluster/configure-upgrade-etcd/ about website HOT 9 CLOSED

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from website.

I think the existing content is correct.

Reference:

https://etcd.io/docs/v3.6/op-guide/recovery/#restoring-a-cluster
https://github.com/etcd-io/etcd/blob/main/etcdutl/README.md

from website.

/language en

from website.

Yep, the existing one is correct. This can be closed.

Maybe the etcd team needs to do some more advertising on the newer cli. Though maybe we should list both the old and new for awhile until it's more well known so folks aren't spending so much time filing issues and PR for the same thing every few days. :D

from website.

I see that the page https://kubernetes.io/docs/tasks/administer-cluster/configure-upgrade-etcd/#restoring-an-etcd-cluster
already has below note

"The usage of etcdctl for restoring has been deprecated since etcd v3.5.x and may be removed from a future etcd release."

Maybe some cleanup to make it more visible can be useful. Let me see if I can submit PR for this.

from website.

/sig etcd

/priority awaiting-more-evidence

from website.

Existing documentation id correct and it can be closed.

from website.

Improvements have been made to the page since this issue was raised, including the addition of a tab layout for the example commands using etcdctl and etcdutl, as well as clarifications on the usage of etcdutl vs etcdctl.

Closing this issue now.
/close

from website.

@dipesh-rawat: Closing this issue.

from website.