Kubernetes 1.22: API Removals

On this page

Kubernetes 1.22 removed multiple v1beta1 APIs that had been deprecated since 1.16. If your cluster upgraded without deploying updated manifests, things likely broke.

Key Removals

Old APINew API
extensions/v1beta1 Ingressnetworking.k8s.io/v1 Ingress
rbac.authorization.k8s.io/v1beta1rbac.authorization.k8s.io/v1
admissionregistration.k8s.io/v1beta1admissionregistration.k8s.io/v1

How to Detect

Bash1 line
kubectl convert -f old-ingress.yaml --output-version networking.k8s.io/v1

Key Takeaways

  • Use **kubent** (kube no trouble) to scan for deprecated APIs before upgrading.
  • Always test upgrades in a dev cluster first.

Discover more from C4: Container, Code, Cloud & Context

Subscribe to get the latest posts sent to your email.

Written by

Nithin Mohan TK

Hello Namaste! 👋🏻 I'm an accomplished Enterprise Solution Architect & Engineering Leader with 20+ years of progressive experience architecting, building, and scaling transformative enterprise solutions. ⚜️ Solution Architect / AI & Cloud 📌 Galway, Ireland

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.