The Wire · Showcase
KARPENTER FIXED, GATEWAY API CONFORMANCE MOVES TO NEW HOME
By RepoJournal · Filed · About Kubernetes
Karpenter deployment is corrected with infrastructure upgrades while Gateway API conformance images establish new CI pipeline.
Karpenter was deployed incorrectly and is now fixed [1], alongside a broader infrastructure refresh that upgraded to the latest Intel VMs with local SSDs (3 generations forward), eliminated unnecessary bootstrap steps, and applied proper kubelet OOM kill reporting [1]. The Gateway API conformance images migrated to a new repository home at k-sigs/gateway-api-conformance-images, triggering coordinated updates across infrastructure: new Artifact Registry setup [2], prow job bootstrapping [4], and test-infra configuration changes [3] [4]. S390x conformance testing received updates to remove deprecated Boskos configuration from master jobs while adding config-forker and config-rotator support for stable branch expansion [3]. Meanwhile, the SMB CSI driver was promoted to v1.20.3 in the Kubernetes registry [5], and GitHub Actions dependencies received routine security bumps across codeql-action components [6].
Action items
- → Review karpenter corrections if running in-cluster conformance tests kubernetes/k8s.io [plan]
- → Update prow job references if maintaining Gateway API conformance pipeline kubernetes/test-infra [plan]
- → Verify s390x conformance job stability after Boskos removal kubernetes/test-infra [monitor]
References
- [1] fix karpenter and use newer bottlerocket features ↗ kubernetes/k8s.io
- [2] Enable image registry for Gateway API conformance images ↗ kubernetes/k8s.io
- [3] Update conformance job for master for s390x ↗ kubernetes/test-infra
- [4] Bootstrap jobs and configs for gwapi conformance images ↗ kubernetes/test-infra
- [5] Merge pull request #9675 from andyzhangx/patch-34 kubernetes/k8s.io
- [6] Bump the actions group with 4 updates ↗ kubernetes/release
FAQ
- What changed in Kubernetes on July 3, 2026?
- Karpenter deployment is corrected with infrastructure upgrades while Gateway API conformance images establish new CI pipeline.
- What should Kubernetes teams do about it?
- Review karpenter corrections if running in-cluster conformance tests • Update prow job references if maintaining Gateway API conformance pipeline • Verify s390x conformance job stability after Boskos removal
- Which Kubernetes repositories shipped on July 3, 2026?
- kubernetes/k8s.io, kubernetes/test-infra, kubernetes/release