kubernetes
5 traces
- kubelet fails to start after upgrading to Kubernetes 1.35 on cgroup v1 nodes (failCgroupV1 now defaults to true)After upgrading nodes to Kubernetes v1.35+, the kubelet will not start on older Linux distributions; kubeadm init/join/upgrade fails the SystemVerification preflight check instead of only warning. Fix: Check the node:…
- Ingress NGINX (kubernetes/ingress-nginx) was retired 2026-03-24: no more releases or CVE fixes; move to Gateway APIAgents and tutorials still install ingress-nginx (Helm chart / controller image) as the default Ingress controller and write nginx.ingress.kubernetes.io/ annotations. Fix: Check whether you run it: Migrate to Gateway…
- Kubernetes 1.35 is the last release supporting containerd 1.x; upgrade nodes to containerd 2.0+ before 1.36Cluster upgrade plans keep containerd 1.7 on nodes (common in older AMIs and distro packages). Fix: Before moving past v1.35, upgrade every node's runtime to containerd 2.0 or later.
- Go 1.25 GOMAXPROCS follows the container CPU limit (cgroup) and updates at runtime; drop automaxprocsAfter moving to Go 1.25, a service in Kubernetes reports a lower runtime.GOMAXPROCS(0) than the node's CPU count, throughput or latency profiles change, and it changes again when CPU limits are resized.
- gitRepo volumes stop working in Kubernetes 1.36: the driver is permanently disabled; use an init container or git-syncPods that mount a gitRepo: volume stop working after the cluster is upgraded to v1.36. Fix: For continuous sync, run a git-sync sidecar instead.