A city permits API still ships Deployment manifests using an API version that staging accepts on an older cluster, but production rejects the apply. What should the team do first?
Select an answer to reveal the explanation.
Short Explanation
Staging and production can be like two different building codes for the same blueprint. Manifests have to match what the target cluster still accepts, not just what worked last quarter on staging. Update the YAML to supported API versions before you hit production apply.
Full Explanation
Kubernetes rejects resources that use removed or unsupported API versions on that cluster. Version skew between staging and production is common when environments upgrade at different times. Application maintainers must convert or rewrite manifests so the apiVersion fields match the destination cluster’s supported APIs, then re-apply. Forcing past validation or freezing every cluster at the oldest version hides debt instead of fixing the manifests.