Orchestration API removal
Kubernetes 1.29 flowcontrol.apiserver.k8s.io v1beta2 assuredConcurrencyShares nominalConcurrencyShares removed
Manifest migration fails because assuredConcurrencyShares no longer exists.
Agent Quick Fix
Repair against the current Kubernetes contract, then keep the change narrow and source-backed.
Product: Kubernetes
Current-contract area: Kubernetes 1.29 removes flowcontrol v1beta2 and renames field
Likely root cause: Manifest migration fails because assuredConcurrencyShares no longer exists.
Repair direction: Verifier checks migrated apiVersion/fields and preservation of behavior. Check resource behavior after apply, not only schema acceptance.Symptom
Manifest migration fails because assuredConcurrencyShares no longer exists.
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.
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.29 flowcontrol.apiserver.k8s.io v1beta2 assuredConcurrencyShares nominalConcurrencyShares removed
site:kubernetes.io flowcontrol v1beta2 assuredConcurrencyShares nominalConcurrencyShares Kubernetes 1.29
assuredConcurrencyShares nominalConcurrencyShares
https://kubernetes.io/docs/reference/using-api/deprecation-guide/
'flowcontrol.apiserver.k8s.io/v1beta2' in https://kubernetes.io/docs/reference/using-api/deprecation-guide/