Repository navigation
Commit a0cd77d
committed
chore(kubernetes): refresh managed Kubernetes patch versions
Bumps every supported Kubernetes minor in the apps/kubernetes version map to its
latest upstream patch, picking up the published Go-stdlib / x/net fixes in the
control-plane component images:
- v1.35: v1.35.1 -> v1.35.6
- v1.34: v1.34.4 -> v1.34.9
- v1.33: v1.33.8 -> v1.33.13
- v1.32: v1.32.12 -> v1.32.13
v1.31 and v1.30 already track their latest patch (.14). The major/minor enum is
unchanged, so the generated values schema, CRD and README are untouched
(make generate is a no-op).
The version range is intentionally held at v1.30-v1.35 and does NOT advance to
v1.36: KubeVirt 1.8.2 rejects the kubelet checksum on Kubernetes 1.36 (int32 CRD
validation), leaving tenant VMIs stuck Scheduled. The kamaji bump to 26.6.4-edge
raises KubeadmVersion to v1.36.0, so hack/update-versions.sh would otherwise add
v1.36 here -- that expansion is deferred until the KubeVirt regression is fixed.
The script also caps the top minor at the exact KubeadmVersion (v1.35.0); v1.35
is set to the latest patch (v1.35.6) by hand instead, matching the existing
practice of running a patch above the kubeadm tool version.
The OS-package advisories in the scan live in the ubuntu-container-disk worker
images; those clear when the release pipeline rebuilds them on the floating
ubuntu noble/current base (no source change needed -- the base is not pinned).
Assisted-By: Claude <[email protected]>
Signed-off-by: Aleksei Sviridkin <[email protected]>1 parent 82b8c46 commit a0cd77d
1 file changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | | - | |
2 | | - | |
3 | | - | |
4 | | - | |
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
5 | 5 | | |
6 | 6 | | |
0 commit comments