You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: