A Kubernetes upgrade moves a cluster or its components to a newer release. Because API versions are deprecated before removal, upgrades require advance inventory and remediation rather than a single version change. section 9.3
A practical upgrade workflow:
- Detect the Kubernetes upgrade event and query the API for changed apiVersions. section 9.3
- Scan running deployments for outdated API versions while backward compatibility remains available. section 9.3
- Use required team metadata to assign each migration to its owning team and create Jira issues with recommended strategies. section 9.3
Admission registration migration
When admission registration advances from v1alpha1 to v1beta1, workloads using v1alpha1 remain usable for two release cycles but must migrate before removal. section 9.3
apiVersion: admissionregistration.k8s.io/v1alpha1 Kind: MutatingWebHook apiVersion: apps/v1 Kind: Deployment
Compare an outdated admission webhook API with a current Deployment manifest while reviewing upgrade impact. section 9.3
