-
Notifications
You must be signed in to change notification settings - Fork 40.4k
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 the Debian images to pick up CVE fixes in the base images #102302
Update the Debian images to pick up CVE fixes in the base images #102302
Conversation
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
/area security /priority important-soon |
# artifacts. It should start at zero for each LATEST_ETCD_VERSION and increment | ||
# for each revision of this image at that etcd version. | ||
REVISION?=0 | ||
REVISION?=1 |
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.
We did this the last time we bumped images (reference: https://github.com/kubernetes/kubernetes/pull/100976/files#diff-de315dbb88d6d341b1682ef2fb0798723139fb4202ac607a334fc301e9359ec7R37), so I thought we should do it this time too.
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.
doesn't hurt usually to do this. however we still haven't updated to the 3.5 beta image yet (
kubernetes/build/dependencies.yaml
Lines 79 to 93 in fd82c69
# etcd | |
- name: "etcd" | |
version: 3.4.13 | |
refPaths: | |
- path: cluster/gce/manifests/etcd.manifest | |
match: etcd_docker_tag|etcd_version | |
- path: cluster/gce/upgrade-aliases.sh | |
match: ETCD_IMAGE|ETCD_VERSION | |
- path: cmd/kubeadm/app/constants/constants.go | |
- path: hack/lib/etcd.sh | |
match: ETCD_VERSION= | |
- path: staging/src/k8s.io/sample-apiserver/artifacts/example/deployment.yaml | |
match: quay.io/coreos/etcd | |
- path: test/e2e/framework/nodes_util.go | |
match: const etcdImage |
0
. But will defer to the @kubernetes/sig-release-leads
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 like the etcd 3.5.0-beta.3-1
image has been already built, so I believe it doesn't make sense to revert the REVISION to 0
any longer. Ref: kubernetes/k8s.io#2101
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, justaugustus, xmudrii 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 |
…302-upstream-release-1.21 Automated cherry pick of #102302: Update debian-iptables to buster-v1.6.1
…302-upstream-release-1.20 Automated cherry pick of #102302: Update debian-iptables to buster-v1.6.1
…302-upstream-release-1.19 Automated cherry pick of #102302: Update debian-iptables to buster-v1.6.1
What type of PR is this?
/kind feature
What this PR does / why we need it:
Update the Debian images to pick up CVE fixes in the base images:
debian-base
image to v1.7.0debian-iptables
image to v1.6.1Which issue(s) this PR fixes:
Related to #102215
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/assign @justaugustus @dims
/sig release
/area release-eng