cluster.ninja

beta API version · group rbac.authorization.k8s.io

rbac.authorization.k8s.io/v1beta1

Removed in 1.22

No Kubernetes release since 1.22 serves apiVersion: rbac.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 rbac.authorization.k8s.io/v1beta1

KindIntroducedDeprecatedStops being servedUse instead
ClusterRole 1.6 1.17 1.22 rbac.authorization.k8s.io/v1
ClusterRoleBinding 1.6 1.17 1.22 rbac.authorization.k8s.io/v1
Role 1.6 1.17 1.22 rbac.authorization.k8s.io/v1
RoleBinding 1.6 1.17 1.22 rbac.authorization.k8s.io/v1

Served in which releases

Kind162025303537
ClusterRole
ClusterRoleBinding
Role
RoleBinding

served served, deprecated exists but off by default not served · 1.16 to 1.37

Migrating off rbac.authorization.k8s.io/v1beta1

RBAC resources removed in 1.22

Move to rbac.authorization.k8s.io/v1, served since 1.8. Existing objects stay readable through the new version.

- apiVersion: rbac.authorization.k8s.io/v1beta1
+ apiVersion: rbac.authorization.k8s.io/v1
  kind: ClusterRole

From the Kubernetes Deprecated API Migration Guide, © The Kubernetes Authors, CC BY 4.0.

To convert files mechanically: kubectl convert -f old.yaml --output-version rbac.authorization.k8s.io/v1 (the kubectl-convert plugin, installed separately). Review defaults it fills in.

Other versions of rbac.authorization.k8s.io

rbac.authorization.k8s.io/v1 Stable

Check your manifests for rbac.authorization.k8s.io/v1beta1 and other removed versions →