beta API version · group flowcontrol.apiserver.k8s.io
flowcontrol.apiserver.k8s.io/v1beta3
Removed in 1.32
No Kubernetes release since 1.32 serves apiVersion: flowcontrol.apiserver.k8s.io/v1beta3. Objects that were stored through it are still in etcd and readable through the replacement version; only manifests and clients that name this version break.
Kinds in flowcontrol.apiserver.k8s.io/v1beta3
| Kind | Introduced | Deprecated | Stops being served | Use instead |
|---|---|---|---|---|
| FlowSchema | 1.26 | 1.29 | 1.32 | flowcontrol.apiserver.k8s.io/v1 |
| PriorityLevelConfiguration | 1.26 | 1.29 | 1.32 | flowcontrol.apiserver.k8s.io/v1 |
Served in which releases
served served, deprecated exists but off by default not served · 1.16 to 1.37
Migrating off flowcontrol.apiserver.k8s.io/v1beta3
Flow control resources removed in 1.32
Move to flowcontrol.apiserver.k8s.io/v1, served since 1.29. Existing objects stay readable through the new version.
What changes:
- The PriorityLevelConfiguration
spec.limited.nominalConcurrencySharesfield only defaults to 30 when unspecified, and an explicit value of 0 is not changed to 30.
- apiVersion: flowcontrol.apiserver.k8s.io/v1beta3
+ apiVersion: flowcontrol.apiserver.k8s.io/v1
kind: FlowSchemaFrom the Kubernetes Deprecated API Migration Guide, © The Kubernetes Authors, CC BY 4.0.
To convert files mechanically: kubectl convert -f old.yaml --output-version flowcontrol.apiserver.k8s.io/v1 (the kubectl-convert plugin, installed separately). Review defaults it fills in.
Other versions of flowcontrol.apiserver.k8s.io
flowcontrol.apiserver.k8s.io/v1 Stableflowcontrol.apiserver.k8s.io/v1beta1 Removed in 1.26flowcontrol.apiserver.k8s.io/v1beta2 Removed in 1.29
Check your manifests for flowcontrol.apiserver.k8s.io/v1beta3 and other removed versions →