-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
kubeadm: add KEP 4214 for separate super-user kubeconfig #4218
kubeadm: add KEP 4214 for separate super-user kubeconfig #4218
Conversation
/cc |
ee53fd3
to
757a788
Compare
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 overall.
/lgtm
keps/sig-cluster-lifecycle/kubeadm/4214-separate-super-user-kubeconfig/kep.yaml
Show resolved
Hide resolved
keps/sig-cluster-lifecycle/kubeadm/4214-separate-super-user-kubeconfig/README.md
Show resolved
Hide resolved
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.
overall LGTM
keps/sig-cluster-lifecycle/kubeadm/4214-separate-super-user-kubeconfig/README.md
Show resolved
Hide resolved
keps/sig-cluster-lifecycle/kubeadm/4214-separate-super-user-kubeconfig/README.md
Show resolved
Hide resolved
/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.
SGTM
keps/sig-cluster-lifecycle/kubeadm/4214-separate-super-user-kubeconfig/README.md
Outdated
Show resolved
Hide resolved
keps/sig-cluster-lifecycle/kubeadm/4214-separate-super-user-kubeconfig/README.md
Outdated
Show resolved
Hide resolved
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neolit123, pacoxu, SataQiu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Can we annotate, or label, the kubeadm-managed ClusterRole and ClusterRoleBinding with something that clearly marks them as deployed by kubeadm? |
the clusterrole is "cluster-admin". that is a stock one and preferred over adding a new clusterrole. |
Sure. But I'm asking for a label or annotation. Otherwise, we have to start teaching heuristics to other tools. An annotation is almost 100% unambiguous. (Heuristics like: look for a |
it's an already established pattern for kubeadm and other k8s components, so tools should already know about it. |
What I wish I could document: The fact it's RBAC isn't relevant to me. It's that each different tool has its own heuristic and that's more things to code. Anyway, I get the sense this would want its own KEP. |
757a788
to
d0aceb2
Compare
keps/sig-cluster-lifecycle/kubeadm/4214-separate-super-user-kubeconfig/README.md
Outdated
Show resolved
Hide resolved
d0aceb2
to
dec4a58
Compare
/lgtm |
/hold cancel |
Create two separate files instead -
admin.conf
containing a regular Kubernetes cluster-admin credential and asuper-admin.conf
containing a cluster-admin credential bound to the
system:masters
group.kubeadm: generate a client certificate with "system:masters" in a separate file #4214
Feature Reqest: Don't bind the admin.conf user to system:masters kubeadm#2414
ONE