-
Notifications
You must be signed in to change notification settings - Fork 42.1k
Move cloud-specific roles out of RBAC bootstrap #66635
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
Move cloud-specific roles out of RBAC bootstrap #66635
Conversation
|
Deleting the roles is the easy part. The hard part is coordinating with the whole provisioning ecosystem to avoid unexpected breakage. How do we know when this is safe to merge? |
|
@tallclair I'm not familiar with where what component this gets run in, is it part of the APIServer? |
|
@micahhausler yeah, it's part of the RBAC plugin, so whichever apiserver that's loaded in. Typically it's the kube-aggregator server, with extension servers using delegation, but I think it's also possible to run RBAC in each extension apiserver. |
|
Does this line need to be removed too? https://github.com/kubernetes/kubernetes/pull/66635/files#diff-eee450e334a11e0b683ce965f584c3c4R531 |
|
/retest |
|
/test pull-kubernetes-bazel-test |
|
@wgliang I think the expected output needs to be updated. |
Signed-off-by: Doug Davis <[email protected]>
|
@wgliang will you have time to finish this one? |
|
Yeah, I'll will update it. |
|
@wgliang thanks. If it helps, I created this: master...duglin:pr66635 if case you didn't have time. There's another "aws" line I think might need to be removed too. |
f329c87 to
c5875e7
Compare
|
@duglin |
|
/lgtm |
|
with the thaw... any chance of moving this one along now? |
|
This LGTM, but I'd like to get approval from someone from @kubernetes/sig-aws-misc |
|
ping @justinsb @kubernetes/sig-aws-misc |
|
/cc @lavalamp - FYI |
|
How did this get in there in the first place? We really shouldn't have any cloud provider specific code like this that's not hidden behind an interface in a cloud provider package. |
|
@lavalamp it got in here via #56709 and at that time there used to be a generic |
|
BTW - is there any reason we can't deprecate this RBAC policy first and remove it in next release? That at least will give time for installation tools to catch up and will be consistent with how other cloudprovider policies are being removed. cc @justinsb |
|
agree with announcing removal prior to removing |
|
@wgliang can you make sure a deprecation notice makes it into the 1.13 release notes, and is announced to the relevant sigs (looks like aws, in this case), along with the required action for deployers? do we want to copy this role out to a yaml manifest that deployers can use as they transition to granting this permission externally? |
|
@liggitt No problem. I will follow up with 1.13 release note and communicate with the relevant personnel. |
|
added to 1.13 release notes as deprecated /hold |
|
/hold cancel master is open for 1.15 dev now, can you rebase this? |
c5875e7 to
128fd88
Compare
|
@liggitt Done. |
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb, liggitt, wgliang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
We consider it part of the storage configuration for AWS now. Upstream change: kubernetes/kubernetes#66635
We consider it part of the storage configuration for AWS now. Upstream change: kubernetes/kubernetes#66635
* Update kubeadm init and join configs with new versions and options. * This includes switching to cgroupfs cgroup driver in kubelet due to kubernetes/kubernetes#76531. * Add AWS RBAC to keights-system Ansible role since kubernetes/kubernetes#66635 removes those permissions by default. * Update CI assets and README build status badges.
What this PR does / why we need it:
The system:aws-cloud-provider ClusterRole(Binding)s should be removed from the bootstrap policy, and instead configured by the provisioning tools.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #66628
Special notes for your reviewer:
@tallclair
/sig aws
/sig cloud-provider
/sig auth
Release note: