Skip to content

Add general info on upgrade policy to main upgrade doc#1115

Open
neeraj542 wants to merge 1 commit intoetcd-io:mainfrom
neeraj542:add-upgrade-policy-doc
Open

Add general info on upgrade policy to main upgrade doc#1115
neeraj542 wants to merge 1 commit intoetcd-io:mainfrom
neeraj542:add-upgrade-policy-doc

Conversation

@neeraj542
Copy link

@neeraj542 neeraj542 commented Feb 3, 2026

Add version-agnostic upgrade policies/advice for the Etcd subproject:

  • Only upgrades across one minor version are supported (e.g. 3.4 to 3.5)
  • Users should update to the most recent patch version before upgrading minor versions
  • Upgrades from EOL versions may work but are no longer supported

Fixes DONE

Fixes #1114

@k8s-ci-robot
Copy link

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

@ivanvc
Copy link
Member

ivanvc commented Feb 3, 2026

/ok-to-test

@ivanvc
Copy link
Member

ivanvc commented Feb 3, 2026

@neeraj542, thanks for you pull request :) Could you please address the linter warnings? Thanks

@jberkus
Copy link
Contributor

jberkus commented Feb 4, 2026

@ronaldngounou @wendy-ha18 can one of you do a quick readability review on this?

Add version-agnostic upgrade policies/advice for the Etcd subproject:
- Only upgrades across one minor version are supported (e.g. 3.4 to 3.5)
- Users should update to the most recent patch version before upgrading minor versions
- Upgrades from EOL versions may work but are no longer supported

Fixes etcd-io#1114

Signed-off-by: neeraj542 <mneeraj2133@gmail.com>
@neeraj542 neeraj542 force-pushed the add-upgrade-policy-doc branch from 7423f19 to da354f8 Compare February 4, 2026 05:16
@neeraj542
Copy link
Author

thanks for guiding on my contribution, I've fixed the linter issues. Please review this PR.

cc: @ivanvc , @jberkus

@ronaldngounou
Copy link
Member

Thank you @neeraj542 for your contribution.
/lgtm

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: neeraj542, ronaldngounou
Once this PR has been reviewed and has the lgtm label, please assign spzala for approval. For more information see the Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@neeraj542
Copy link
Author

my pleasure @ronaldngounou, still its showing me as Merging Blocked, could anyone pls look into this..

@ronaldngounou
Copy link
Member

@jberkus for approval

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add general info on upgrade policy to main upgrade doc

5 participants