Orchestration API removal

Kubernetes 1.36 gitRepo volume disabled permanently gitRepo volume feature gate official

Pod admission/startup fails for a manifest that still mounts a gitRepo volume.

search-observedKubernetesContainer orchestrationOrchestration API removalk8s_136

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.36 permanently disables gitRepo volume
Likely root cause: Pod admission/startup fails for a manifest that still mounts a gitRepo volume.
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

Pod admission/startup fails for a manifest that still mounts a gitRepo volume.

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.36 gitRepo volume disabled permanently gitRepo volume feature gate official
Kubernetes gitRepo volume disabled feature gate GitRepoVolumeDriver 1.36
Kubernetes gitRepo volume docs
https://kubernetes.io/docs/concepts/storage/volumes/
'gitRepo' in https://kubernetes.io/docs/concepts/storage/volumes/

Source Trail