Update to etcd 3.5.3 for Kubernetes 1.22+ #9604
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 etcd3.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?: