Skip to content

docs: recommend 3.5.32 before upgrading to 3.6 - #1203

Open
locker95 wants to merge 1 commit into
etcd-io:mainfrom
locker95:docs/upgrade-3.6-july-patch
Open

docs: recommend 3.5.32 before upgrading to 3.6#1203
locker95 wants to merge 1 commit into
etcd-io:mainfrom
locker95:docs/upgrade-3.6-july-patch

Conversation

@locker95

@locker95 locker95 commented Aug 3, 2026

Copy link
Copy Markdown

The 3.5→3.6 upgrade guide still said patch to 3.5.26. The July release (3.5.32 / 3.6.13) is what brings write-only-skip-check and the WAL-aware etcdutl check v2store, which the same page already walks through.

Bumped the checklist to 3.5.32 and linked the July blog.

Fixes #1194

Point the 3.5→3.6 upgrade checklist at the July patch release so
operators get write-only-skip-check and the improved etcdutl v2store
check before rolling members.

Fixes etcd-io#1194

Signed-off-by: Dean Chen <862469039@qq.com>
@kubernetes-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: locker95
Once this PR has been reviewed and has the lgtm label, please assign ivanvc 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

@kubernetes-prow

Copy link
Copy Markdown

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

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.

Update upgrade docs based on July patch release

1 participant