Back to all scenarios
Scenario #129
Cluster Management
K8s v1.17, Azure AKS
Failed Cluster Upgrade Due to Incompatible API Versions
The cluster upgrade failed because certain deprecated API versions were still in use, causing compatibility issues with the new K8s version.
Find this helpful?
What Happened
The upgrade to K8s v1.18 was blocked due to deprecated API versions still being used in certain resources, such as extensions/v1beta1 for Ingress and ReplicaSets.
Diagnosis Steps
- 1Checked the upgrade logs and identified that the upgrade failed due to the use of deprecated API versions.
- 2Inspected Kubernetes manifests for resources still using deprecated APIs and discovered several resources in the cluster using old API versions.
Root Cause
The use of deprecated API versions prevented the upgrade to a newer Kubernetes version.
Fix/Workaround
• Updated Kubernetes manifests to use the latest stable API versions.
• Re-applied the updated resources and retried the cluster upgrade.Lessons Learned
Always update API versions to ensure compatibility with new Kubernetes versions before performing upgrades.
How to Avoid
- 1Regularly audit API versions in use across the cluster.
- 2Use tools like kubectl deprecations or kubectl check to identify deprecated resources before upgrades.