is it okay to upgrade apiversions for clusterrole and clusterrolebinding due to kubernetes version upgrade.
The rbac.authorization.k8s.io/v1beta1 API version of ClusterRole, ClusterRoleBinding, Role, and RoleBinding is no longer served as of v1.22.
Migrate manifests and API clients to use the rbac.authorization.k8s.io/v1 API version, available since v1.8.
All existing persisted objects are accessible via the new APIs
No notable changes
I think there is no harm for anyone if we change the apiversions since
"Migrate manifests and API clients to use the scheduling.k8s.io/v1 API version, available since v1.14."
Hello @hiddeco
is it okay to upgrade apiversions for clusterrole and clusterrolebinding due to kubernetes version upgrade.
The rbac.authorization.k8s.io/v1beta1 API version of ClusterRole, ClusterRoleBinding, Role, and RoleBinding is no longer served as of v1.22.
Migrate manifests and API clients to use the rbac.authorization.k8s.io/v1 API version, available since v1.8. All existing persisted objects are accessible via the new APIs No notable changes
https://kubernetes.io/docs/reference/using-api/deprecation-guide/
I think there is no harm for anyone if we change the apiversions since "Migrate manifests and API clients to use the scheduling.k8s.io/v1 API version, available since v1.14."
what do you think?