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 API | New API |
|---|---|
| extensions/v1beta1 Ingress | networking.k8s.io/v1 Ingress |
| rbac.authorization.k8s.io/v1beta1 | rbac.authorization.k8s.io/v1 |
| admissionregistration.k8s.io/v1beta1 | admissionregistration.k8s.io/v1 |
How to Detect
kubectl convert -f old-ingress.yaml --output-version networking.k8s.io/v1Key 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.