[Backport release-1.9] fix: pin the runtime images (eMudhra CA fix) and accept the removed APIPriorityAndFairness gate

Merged
JE
4d ago
+215-9

Description

Backport of #184 to release-1.9, for v1.9.2 (KubeVela 1.10 / 1.11): the eMudhra CA fix (both runtime images pinned to
alpine:3.24@sha256:3f4d6b32…, 3.24.4 with ca-certificates-bundle 20261020-r0; builder images pinned by digest)
and the shim for the APIPriorityAndFairness feature gate KubeVela's charts still pass. See #184 for the details.

Change

#184's commits, cherry-picked with -x:

CommitOn master (#184)
fix: pin the cluster-gateway runtime image to alpine 3.241a94604
fix: build the addon-manager on alpine 3.24c90d5a0
fix: accept the removed APIPriorityAndFairness feature gated4881d6
fix: keep a malformed APIPriorityAndFairness gate for the parser to rejectbc296bd

Conflicts resolved by hand, only where release-1.9 differs from master: the builder images are this branch's Go 1.23 (golang:1.23-alpine@sha256:383395b7…, golang:1.23@sha256:60deed95…), and cmd/apiserver/main.go is the apiserver-runtime main (only its import block and the first line of main change). pkg/featuregates/removed.go and its test are the same as on master.

I have:

  • Signed off the commits (DCO).

How has this been tested

On this branch's code: go build ./cmd/apiserver/main.go, go vet, the unit test; the gateway image built locally (Alpine 3.24.4, the fixed bundle) started with KubeVela's chart args (the shim's warning, then normal start); the addon-manager for amd64 and arm64; Brotli clean, eMudhra safe on all three. Under KubeVela 1.10.9's and 1.11.1's charts as released on k3d with a joined second cluster: join, probe, deploying to the second cluster, updating, reading through the proxy (vela logs) and deleting all work.

Special notes for your reviewer

Please merge together with #184 and the other backport. After the merge, the release-1.9 push publishes
oamdev/cluster-gateway:release-1.9-<sha>; I'll scan it and run it under KubeVela's charts before asking for v1.9.2.


Summary by cubic

Backports the eMudhra CA fix and the APIPriorityAndFairness feature-gate shim from #184 to release-1.9, for v1.9.2 (KubeVela 1.10 / 1.11).

  • Pins the cluster-gateway and addon-manager runtime images to alpine:3.24@sha256:3f4d6b32… (3.24.4, ca-certificates-bundle 20261020-r0) and builder images by digest.
  • Adds pkg/featuregates/removed.go, which rewrites the removed APIPriorityAndFairness gate KubeVela's charts still pass into --enable-priority-and-fairness, so the apiserver starts normally. Malformed gates (missing, empty, or non-boolean values) are left for the feature-gate parser to reject.
  • Resolves cherry-pick conflicts by hand where release-1.9 differs from master: the Go 1.23 builder images and the apiserver-runtime main in cmd/apiserver/main.go.