Breaking Change: Kubernetes 1.34 Tightens Image Name Resolution Rules — What It Means for You
Blog post from Replicated
Kubernetes 1.34 introduces a significant change for distributions using the CRI-O runtime, such as RedHat OpenShift and Oracle Cloud Infrastructure Kubernetes Engine, by enforcing stricter image name resolution rules. This update requires all container image references to include a fully qualified registry path, eliminating the previous convenience of using short image names resolved by default registries like Docker Hub. The change aims to enhance supply chain security but may disrupt existing manifests, Helm charts, and deployment pipelines that rely on short image names, potentially causing failed image pulls or pods stuck in ImagePullBackOff. Organizations are advised to audit and update their Kubernetes manifests to include full registry paths, with companies like Replicated proactively notifying their customers and adjusting their own deployments to ensure minimal disruption. This development highlights the importance of staying informed about Kubernetes updates and testing against new versions to maintain application reliability and compatibility.