-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Build etcd image of v3.5.16 #127283
Build etcd image of v3.5.16 #127283
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
Signed-off-by: bzsuni <bingzhe.sun@daocloud.io>
c6ca64b
to
7008652
Compare
/lgtm |
LGTM label has been added. Git tree hash: 238686b80211adbb1f5e9bc88a86f0cdfe8e57d9
|
@@ -28,7 +28,7 @@ import ( | |||
) | |||
|
|||
var ( | |||
supportedEtcdVersions = []string{"3.4.18", "3.5.15"} | |||
supportedEtcdVersions = []string{"3.4.18", "3.5.16"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be updated to v3.4.34?
https://github.com/kubernetes/kubernetes/pull/127283/files#diff-de315dbb88d6d341b1682ef2fb0798723139fb4202ac607a334fc301e9359ec7R18 should be update if we want to bump the 3.4.x here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be updated to v3.4.34?
Yes, I think so.
- It seems that nobody care about etcd 3.4.x obviously it isn't updated for a long time?
- It's accepted to address it in a separate PR since this one is solely intended to bump the 3.5.x?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that nobody care about etcd 3.4.x obviously it isn't updated for a long time?
A quick check, we didn't build 3.4.18 even. The latest 3.4.x in kubernetes/k8s.io
is 3.4.13-3
.
https://github.com/kubernetes/k8s.io/blob/ca7a917e59f19fbdab73b07440bf7d843e61126d/registry.k8s.io/images/k8s-staging-etcd/images.yaml#L6
"sha256:528ff5e3c80ca0d58d1ab15dc329dc300f9c3fefaffa4c822ca2c389ce254644": ["3.4.13-3"]
It's accepted to address it in a separate PR since this one is solely intended to bump the 3.5.x?
Agree.
/lgtm |
/SIG etcd |
/remove-sig api-machinery This should be SIG etcd now. |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahrtr, bzsuni, dims 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 |
Any takers for v3.5.17 ? |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
etcd is now released in v3.5.16
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: