Upgrade to etcd client 3.3.17#83801
Conversation
odinuge
left a comment
There was a problem hiding this comment.
Thanks!
You should probably remove the changelog from the previous PR to avoid duplicates in the changelog, otherwise lgtm. 😄
/lgtm
Done, thanks! |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jpbetz, liggitt 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 |
|
/retest |
1 similar comment
|
/retest |
|
it looks like this didn't bump bbolt to 1.3.3, even though etcd did between 3.3.15 and 3.3.17. should it have? |
Yes. This got missed. I've opened #83970 to bump bbolt. |
Upgrade to etcd client 3.3.17
Manual cherry pick of #83801: Upgrade to etcd 3.3.17 client + bbolt v1.3.3
Upgrade to etcd 3.3.16 that was merged yesterday rolledback because etcd 3.3.16 was a bad release. etcd 3.3.17 is the same as 3.3.16, but with a clean release (#83761).
What type of PR is this?
/kind bug
What this PR does / why we need it:
Fixes for two major issues with the etcd 3.3 client to 1.16:
Which issue(s) this PR fixes:
Fixes #83550 via etcd-io/etcd#11211 (backported to etcd 3.3 via etcd-io/etcd#11216)
Fixes #83028 via etcd-io/etcd#11184 (backported to etcd 3.3 via etcd-io/etcd#11215)
Special notes for your reviewer:
Separate PR to upgrade to etcd 3.3.17 server will follow. We typically upgrade clients first.
Does this PR introduce a user-facing change?:
/sig api-machinery
/area etcd
/priority critical-urgent