use etcd 3.5.6-0 after etcd image is promoted#114093
use etcd 3.5.6-0 after etcd image is promoted#114093k8s-ci-robot merged 1 commit intokubernetes:masterfrom
Conversation
|
Please note that we're already in Test Freeze for the Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Wed Nov 23 21:33:10 UTC 2022. |
|
/priority critical-urgent cc @kubernetes/release-managers - please add please see https://groups.google.com/a/kubernetes.io/g/dev/c/sEVopPxKPDo/m/9ME3CzicBwAJ for context. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, pacoxu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/milestone v1.26 |
|
I think this should also be cherry-picked to 1.25-1.23. @pacoxu Do you want to take care of that? |
Cherry-Pick PRs are opened now. |
…93-upstream-release-1.25 Automated cherry pick of #114093: use etcd 3.5.6-0 after promotion
…93-upstream-release-1.22 Automated cherry pick of #114093: use etcd 3.5.6-0 after promotion
…93-upstream-release-1.24 Automated cherry pick of #114093: use etcd 3.5.6-0 after promotion
…93-upstream-release-1.23 Automated cherry pick of #114093: use etcd 3.5.6-0 after promotion
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
migrateutility #114084Which issue(s) this PR fixes:
Fixes None
Special notes for your reviewer:
Two possible data inconsistency issues in etcd v3.4.[20-21] and v3.5
Two issues below:
1 - etcd v3.5.[0-5] data inconsistency issue for a case when etcd crashes during processing defragmentation operation
2 - etcd v3.4.[20-21] and v3.5.5 data inconsistency issue for a case when auth is enabled and a new member added to the cluster
Does this PR introduce a user-facing change?