Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to etcd 3.5.3 for Kubernetes 1.22+ #9604

Merged
merged 2 commits into from Apr 14, 2022

Conversation

embik
Copy link
Member

@embik embik commented Apr 14, 2022

What does this PR do / Why do we need it:

What it says on the title: Updating the etcd 3.5 patch release we include with Kubernetes 1.22+ clusters to 3.5.3, a new release out since yesterday (etcd-io/etcd#13894 & https://github.com/etcd-io/etcd/releases/tag/v3.5.3). It is supposed to fix the data consistency issues that were the trigger for not recommending etcd 3.5.[0-2] for production.

This should be backported to all active release branches, but I'd like to have it up on dev / master for a bit to make sure it's stable. Cherry-picks will be up soon though.

Does this PR close any issues?:
Fixes #

Special notes for your reviewer:

Documentation:

Does this PR introduce a user-facing change?:

For Kubernetes 1.22 and higher, etcd is updated to v3.5.3 to fix data consistency issues as reported by upstream developers

Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. labels Apr 14, 2022
@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik

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

The pull request process is described here

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

@kubermatic-bot kubermatic-bot added sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 14, 2022
@embik embik requested a review from xmudrii April 14, 2022 06:21
@kubermatic-bot kubermatic-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Apr 14, 2022
@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Apr 14, 2022
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: b8ffa5ff6810e89b5fc4a25f901dfb2b929cf86f

@embik
Copy link
Member Author

embik commented Apr 14, 2022

/retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants