Skip to content
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 users to specify the name of the provider-aws service account #607

Closed
patjones opened this issue Mar 26, 2021 · 1 comment
Closed
Labels
enhancement New feature or request

Comments

@patjones
Copy link

patjones commented Mar 26, 2021

What problem are you facing?

Hi there! I am trying to automate the install of crossplane with argocd on openshift across different environments. One issue I have is that openshift requires me to attach the anyuid cluster role to the service accounts that will be spinning up pods. It's pretty straightforward to provide a clusterrolebinding for the crossplane and rbac-manager service account but the uuid appended provider-aws service account is more problematic. I'm aware it's possible to specify a completely different service account to use with a controller config, but noticed that the clusterrole that provider-aws uses is also uuid appended and I'd have to manage my own. My concern is that it seems like bad idea to try and manage the clusterrole for the aws provider as I imagine it will be changing often with the addition of new aws services, etc.

How could Crossplane help solve your problem?

I believe letting users specify the name of the service account that gets spun up for a provider would be extremely helpful in this openshift specific situation but would love to hear any other ideas. Thank you for taking the time to read this!

@MisterMX
Copy link
Collaborator

Closing as this is not an issue specific to this provider but rather something that belongs to github.com/crossplane/crossplane.

Choosing the SA name can be done in the ControllerConfig (which is a generic Crossplane resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants