Orchestration API removal

Kubernetes 1.25 CronJob batch/v1beta1 removed batch/v1 deprecation guide

A deployment tool reports no matches for CronJob.

search-observedKubernetesContainer orchestrationOrchestration API removalk8s_deprecation

Agent Quick Fix

Manifests are static and may still validate against cached schemas; the target cluster's served API set is external and version-specific.

Product: Kubernetes
Current-contract area: Kubernetes 1.25 removes CronJob batch/v1beta1
Likely root cause: A deployment tool reports no matches for CronJob.
Repair direction: Verifier checks migrated apiVersion/fields and preservation of behavior. Check resource behavior after apply, not only schema acceptance.

Validation Status

Codex searched organically in the validation run. No no-web counterfactual is attached to this page yet.

Symptom

A deployment tool reports no matches for CronJob.

Why This Happens

Manifests are static and may still validate against cached schemas; the target cluster's served API set is external and version-specific.

Verification

Verifier checks migrated apiVersion/fields and preservation of behavior. Check resource behavior after apply, not only schema acceptance.

Common Wrong Fixes

Changing local code without checking the current external contract.
Retrying the same install, build, or API call with no version/source change.
Applying a broad unsafe bypass when a narrow compatibility fix is available.

Codex Search Keywords

These are the search terms observed in a neutral Codex validation run for this failure shape.

Kubernetes 1.25 CronJob batch/v1beta1 removed batch/v1 deprecation guide
site:kubernetes.io deprecated API migration guide v1.25 CronJob batch/v1beta1
https://kubernetes.io/docs/reference/using-api/deprecation-guide/
'CronJob' in https://kubernetes.io/docs/reference/using-api/deprecation-guide/