$ the-wire · showcase
VPA chart 0.12.0 syncs CRDs on upgrade; kOps gains Amazon Linux 2027 coverage
By RepoJournal · Filed · About Kubernetes
The VPA Helm chart now manages CRDs as templates so upgrades keep them in sync, while kOps test infra adds full Amazon Linux 2027 support and minikube fixes a Hugo security break.
The vertical-pod-autoscaler chart shipped 0.12.0 [1] with a breaking structural change: CRDs moved from the crds/ folder (Helm never updates on helm upgrade) to templates/crds/, so they now sync automatically with the chart version instead of requiring manual kubectl apply [2]. The move is gated behind a new crds.enabled value (default true) [2]. Upgrading to 0.12.0 changes how CRDs are deployed; users who disabled CRD management must set crds.enabled=false.
[kops] test-infra graduates Amazon Linux 2027 from optional presubmits to a full distro in the grid and periodic jobs [3][4]. The change adds 116 jobs across al2027 and al2027arm64 and gates them to kops 1.37 and latest, since kops 1.35 and 1.36 do not recognize the amzn-2027 distro and would hit nodeup's unsupported distro error [4]. The previously redundant pull-kops-e2e-k8s-aws-al2027 presubmit was dropped to avoid testgrid duplicate-name validation failures [5]. Also, the etcd-operator jobs no longer test the customized-controller branch [6].
minikube's site build hit a breaking change from Hugo: "Hugo v0.162.0 introduced a security.allowContent policy that blocks text/html content files by default" [7]. With 138 .html content files, any Hugo bump past v0.162.0 broke Netlify deploys with an access denied error. The fix adds [security] allowContent = ['.*'] to site/config.toml, and Hugo was bumped from v0.160.1 to v0.165.0 [8][9]. Separately, minikube fixed a test timeout by raising TestNoKubernetes from 5m to 15m; on KVM the preceding subtests took ~293.4s, leaving little time and causing the VM to be killed mid-boot with misleading 'connect: no route to host' errors [10]. Dependency bumps address two high-priority grype findings: golang.org/x/crypto to v0.56.0 and go-getter to v1.8.6, while grpc and docker remain untouched because no fixed upstream release exists [11].
Action items
- → Review VPA chart 0.12.0 upgrade notes; confirm crds.enabled behavior matches your setup kubernetes/autoscaler [plan]
- → If you run kops jobs below 1.37, expect al2027 jobs to be gated accordingly kubernetes/test-infra [monitor]
- → minikube site maintainers: deploy Hugo 0.165.0 with the new allowContent config kubernetes/minikube [immediate]
References
- [1] vertical-pod-autoscaler-chart-0.12.0 ↗ kubernetes/autoscaler
- [2] vpa chart: move CRDs to templates/ so they sync on upgrade ↗ kubernetes/autoscaler
- [3] [kops] Add Amazon Linux 2027 to the grid and distro jobs ↗ kubernetes/test-infra
- [4] [kops] Add Amazon Linux 2027 to the grid and distro jobs ↗ kubernetes/test-infra
- [5] [kops] Drop the redundant al2027 cilium presubmit ↗ kubernetes/test-infra
- [6] Merge pull request #37825 from ArkaSaha30/remove-customized-controller-workflows-etcd-o ↗ kubernetes/test-infra
- [7] site: allow text/html content for Hugo >= 0.162.0 ↗ kubernetes/minikube
- [8] Merge pull request #23652 from rishiraj38/fix-hugo-security-allowcontent ↗ kubernetes/minikube
- [9] site: update hugo from v0.160.1 to v0.165.0 ↗ kubernetes/minikube
- [10] test: Fix TestNoKubernetes timeout and unskip StartNoArgs on KVM ↗ kubernetes/minikube
- [11] deps: Bump golang.org/x/crypto to v0.56.0 and go-getter to v1.8.6 ↗ kubernetes/minikube