upgrade-etcd.md: add a paragraph about the supported upgrade path

[neolit123]

Add a paragraph explaining how the supported upgrade path of etcd works. Include all versions in support 3.4 - 3.7.

happy to adjust the wording or the target .md files if needed.

xref etcd-io/etcd-operator#168 (comment)

/assign @ahrtr

[k8s-ci-robot]

Hi @neolit123. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[neolit123]

oops, the bot already suggested @ahrtr
/unassign @nate-double-u

[ahrtr]

Thanks for raising the PR.

Instead of updating each upgrade guide, I think it should be better to just update it in one place https://github.com/etcd-io/website/blob/main/content/en/docs/v3.7/upgrades/_index.md

Also I don't see much value to have https://github.com/etcd-io/website/blob/main/content/en/docs/v3.7/upgrades/upgrading-etcd.md, probably we can just remove it.

cc @jberkus

[neolit123]

/retitle add a paragraph about the supported upgrade path

[k8s-ci-robot]

@neolit123: Re-titling can only be requested by trusted users, like repository collaborators.

Details

In response to this:

/retitle add a paragraph about the supported upgrade path

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-sigs/prow repository.

[neolit123]

Thanks for raising the PR.

Instead of updating each upgrade guide, I think it should be better to just update it in one place https://github.com/etcd-io/website/blob/main/content/en/docs/v3.7/upgrades/_index.md

Also I don't see much value to have https://github.com/etcd-io/website/blob/main/content/en/docs/v3.7/upgrades/upgrading-etcd.md, probably we can just remove it.

cc @jberkus

updated.

[ahrtr]

Please also update the following files,

• https://github.com/etcd-io/website/blob/main/content/en/docs/v3.6/upgrades/_index.md
• https://github.com/etcd-io/website/blob/main/content/en/docs/v3.5/upgrades/_index.md
• https://github.com/etcd-io/website/blob/main/content/en/docs/v3.4/upgrades/_index.md

[ahrtr]

Suggested change

	## Supported upgrade path
	## Supported upgrade path
	etcd only supports upgrades in the following two cases:
	- Upgrading between patch releases within the same minor version.
	- Upgrading from the current version to the next minor version (or to the next major version, if the current minor version is the last minor of the current major).

[neolit123]

updated.

[ahrtr]

/ok-to-test

[ahrtr]

LGTM & thx

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahrtr, neolit123

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [ahrtr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ivanvc]

This PR overlaps #1115 (#1114). I'll defer to @jberkus to decide on which one he prefers.

[neolit123]

This PR overlaps #1115 (#1114). I'll defer to @jberkus to decide on which one he prefers.

i didn't know @jberkus added #1114 let's cloae this pr here if needed.

/hold

[ahrtr]

This PR overlaps #1115 (#1114). I'll defer to @jberkus to decide on which one he prefers.

Oh, I didn't see that PR either.