jingyuanliang
commented
4 months ago No, but these -gke.X builds are just for vulnerability bumps.
For example, the v0.6.20-gke.14..v0.6.20-gke.17 diff is:
diff --git a/Makefile b/Makefile
index dfa8812..22101fd 100644
--- a/Makefile
+++ b/Makefile
@@ -30,7 +30,7 @@
# The "FROM" part of the Dockerfile. This should be a manifest-list which
# supports all of the platforms listed in ALL_PLATFORMS.
-BASE_IMAGE ?= gcr.io/gke-release/distroless-iptables:v0.2.5-gke.16@sha256:44872042ce9439b8caae61c5e2a58666353eaccadf5267472605fddef847bbd2
+BASE_IMAGE ?= gcr.io/gke-release/distroless-iptables:v0.2.5-gke.19@sha256:c09253f7d1a548e5b608a146cf6e156ab1a0e4b73f769fb15584d06133953653
# Where to push the docker images.
REGISTRY ?= gcr.io/gke-release-staging
@@ -61,7 +61,7 @@
TAG := $(VERSION)__$(OS)_$(ARCH)
GO_VERSION := 1.20
-BUILD_IMAGE := us-docker.pkg.dev/google.com/api-project-999119582588/go-boringcrypto-internal/golang:1.21.9@sha256:65520c73b91975f8caa56e7ba70b2c090e7f965274720dd56d9c06e0ebde487d
+BUILD_IMAGE := us-docker.pkg.dev/google.com/api-project-999119582588/go-boringcrypto-internal/golang:1.21.10@sha256:22bf183308a509052787257ae698bb5100cb444430fb5d169f17c965a17dc5ab
BIN_EXTENSION :=
ifeq ($(OS), windows)
diff --git a/scripts/Makefile b/scripts/Makefile
index 28a1dfc..5d7180b 100644
--- a/scripts/Makefile
+++ b/scripts/Makefile
@@ -30,7 +30,7 @@
# The "FROM" part of the Dockerfile. This should be a manifest-list which
# supports all of the platforms listed in ALL_PLATFORMS.
-BASE_IMAGE ?= gcr.io/gke-release/distroless-iptables:v0.2.5-gke.16@sha256:44872042ce9439b8caae61c5e2a58666353eaccadf5267472605fddef847bbd2
+BASE_IMAGE ?= gcr.io/gke-release/distroless-iptables:v0.2.5-gke.19@sha256:c09253f7d1a548e5b608a146cf6e156ab1a0e4b73f769fb15584d06133953653
# Where to push the docker images.
REGISTRY ?= gcr.io/gke-release-staging
@@ -71,7 +71,7 @@
TAG := $(VERSION)__$(OS)_$(ARCH)
GO_VERSION := 1.20
-BUILD_IMAGE := us-docker.pkg.dev/google.com/api-project-999119582588/go-boringcrypto-internal/golang:1.21.9@sha256:65520c73b91975f8caa56e7ba70b2c090e7f965274720dd56d9c06e0ebde487d
+BUILD_IMAGE := us-docker.pkg.dev/google.com/api-project-999119582588/go-boringcrypto-internal/golang:1.21.10@sha256:22bf183308a509052787257ae698bb5100cb444430fb5d169f17c965a17dc5ab
BIN_EXTENSION :=
ifeq ($(OS), windows)
ndlanier
I am trying to track down an issue one of my gke clusters experienced where my current investigation has lead me to inspect netd. I have resolved the issue (as far as I know) by upgrading the minor version. Comparing the image version of netd from a cluster on the previous gke version to what I upgraded the problematic cluster to I see the old is on 0.6.20-gke.14 and the new is on 0.6.20-gke.17
I'm not finding any documentation for what changes have been made between those two releases. Is there any documentation for these types of releases?
Thank you.