beta API version · group authorization.k8s.io
authorization.k8s.io/v1beta1
Removed in 1.22
No Kubernetes release since 1.22 serves apiVersion: authorization.k8s.io/v1beta1. 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 authorization.k8s.io/v1beta1
| Kind | Introduced | Deprecated | Stops being served | Use instead |
|---|---|---|---|---|
| LocalSubjectAccessReview | 1.2 | 1.19 | 1.22 | authorization.k8s.io/v1 |
| SelfSubjectAccessReview | 1.2 | 1.19 | 1.22 | authorization.k8s.io/v1 |
| SelfSubjectRulesReview | 1.8 | 1.19 | 1.22 | authorization.k8s.io/v1 |
| SubjectAccessReview | 1.2 | 1.19 | 1.22 | authorization.k8s.io/v1 |
Served in which releases
served served, deprecated exists but off by default not served · 1.16 to 1.37
Migrating off authorization.k8s.io/v1beta1
SubjectAccessReview resources removed in 1.22
Move to authorization.k8s.io/v1, served since 1.6. Existing objects stay readable through the new version.
What changes:
spec.groupwas renamed tospec.groupsin v1 (fixes #32709)
- apiVersion: authorization.k8s.io/v1beta1
+ apiVersion: authorization.k8s.io/v1
kind: LocalSubjectAccessReviewFrom the Kubernetes Deprecated API Migration Guide, © The Kubernetes Authors, CC BY 4.0.
To convert files mechanically: kubectl convert -f old.yaml --output-version authorization.k8s.io/v1 (the kubectl-convert plugin, installed separately). Review defaults it fills in.
Other versions of authorization.k8s.io
authorization.k8s.io/v1 Stable
Check your manifests for authorization.k8s.io/v1beta1 and other removed versions →