CKAD v1.35 · Application Observability and Maintenance (15%) → "Understand API deprecations" Target time: 15 minutes
Three manifests written for an old cluster live in:
scenarios/ckad/07-api-deprecations/manifests/
They use API versions that have been removed from Kubernetes. Applying them as-is fails.
Work out which API version each resource should use today, and what
other fields changed alongside the version bump. kubectl explain and
kubectl api-resources will tell you.
Migrate all three so they apply cleanly to namespace migrate:
legacy-ing (also needs a Service legacy-svc)legacy-cronlegacy-pdbDo NOT edit the originals — write the migrated versions to scenarios/ckad/07-api-deprecations/fixed/ and apply from there.
Record, in /tmp/removed-apis.txt, one line per resource in the form ->
Hint: the Ingress changed more than its apiVersion.