-
Notifications
You must be signed in to change notification settings - Fork 39.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
Allow custom service account names to be used for cloud controllers #103178
Allow custom service account names to be used for cloud controllers #103178
Conversation
/sig cloud-provider |
/cc @cheftako |
0c643eb
to
b7a8502
Compare
/triage accepted |
b7a8502
to
a3d566b
Compare
a3d566b
to
8643261
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.
"route": startRouteControllerWrapper, | ||
var DefaultInitFuncConstructors = map[string]ControllerInitializerConstructor{ | ||
"cloud-node": { | ||
ClientName: "node-controller", |
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.
this probably deserves a comment that it's node-controller for historical reasons
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.
+1
Constructor: StartCloudNodeControllerWrapper, | ||
}, | ||
"cloud-node-lifecycle": { | ||
ClientName: "node-controller", |
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.
same here this probably deserves a comment that it's node-controller for historical reasons
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.
Also that if you want to over-ride this is an example of where you should make the override.
/lgtm |
/test pull-kubernetes-integration |
/hold |
Addressing comments. |
Also added examples to |
/approve |
/lgtm |
/ok-to-test |
@nckturner needs rebase. PTAL |
* This allows a controller to use cloud provider managed RBAC when --use-service-account-credentials is set. * Create ControllerInitFuncConstructor to pass to init funcs to avoid future function signature growth. * Add comments for context around legacy naming of node controllers. * Add example for setting client names from cloud controller manager.
a5f84b3
to
a5b47f7
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cheftako, nckturner, wongma7 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 |
/remove-hold |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Allow custom client/service account names to be used for cloud controllers. This allows a cloud controller to use cloud provider managed RBAC when --use-service-account-credentials is set, rather than the in-tree default RBAC that is bootstrapped by the API server (like the node-controller).
Which issue(s) this PR fixes:
Fixes kubernetes/cloud-provider#48
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: