-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modify kube-flannel.yaml to use rbac.authorization.k8s.io/v1 #1342
Modify kube-flannel.yaml to use rbac.authorization.k8s.io/v1 #1342
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Can you please also change docs to reflect that change (just to have a reference that new roles wouldn't be compatible with <1.17 ?
Thanks @rajatchopra & @AleksandrNull ! I split
|
This commit modifies Documentation/kube-flannel.yaml to use ClusterRole & ClusterRoleBinding of 'rbac.authorization.k8s.io/v1'. Before this commit, 'rbac.authorization.k8s.io/v1beta1' is used at kube-flannel.yaml. However, from Kubernetes v1.17, this v1beta1 version is deprecated and 'rbac.authorization.k8s.io/v1' becomes GA. At the time of writing this commit, latest Kubernets version is v1.19. So, according to Kubernetes support policy, only v1.19, v1.18 & v1.17 are supported and it's safe to use 'rbac.authorization.k8s.io/v1' now. This commit also modifies docs to mention this change.
51543b3
to
8a1bcf6
Compare
Kindly ping: Thank you. |
@@ -31,6 +33,10 @@ This file does not bundle RBAC permissions. If you need those, run | |||
If you didn't apply the `kube-flannel-rbac.yml` manifest and you need to, you'll see errors in your flanneld logs about failing to connect. | |||
* `Failed to create SubnetManager: error retrieving pod spec...` | |||
|
|||
### For Kubernetes v1.16 | |||
|
|||
`kube-flannel.yaml` uses `ClusterRole` & `ClusterRoleBinding` of `rbac.authorization.k8s.io/v1`. When you use Kubernetes v1.16, you should replace `rbac.authorization.k8s.io/v1` to `rbac.authorization.k8s.io/v1beta1` because `rbac.authorization.k8s.io/v1` had become GA from Kubernetes v1.17. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rbac.authorization.k8s.io/v1 is added to k8s since 1.8.0, source We don't need to add that.
Description
[Type of fix] : Bug
This commit modifies
Document/kube-flannel.yaml
to useClusterRole
&ClusterRoleBinding
ofrbac.authorization.k8s.io/v1
.Before this commit,
rbac.authorization.k8s.io/v1beta1
is used atkube-flannel.yaml
. However, from Kubernetes v1.17, this v1beta1 version is deprecated andrbac.authorization.k8s.io/v1
becomes GA.At the time of writing this commit, latest Kubernets version is v1.19. So, according to Kubernetes support policy, only v1.19, v1.18 & v1.17 are supported and it's safe to use
rbac.authorization.k8s.io/v1
now.Todos
Release Note