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
@donnalux we think the answer to this one is no, the role that is added for the cloud account connectivity is going to be the role that provisions the cluster until further notice
What is your feature idea?
When provisioning a cluster or creating an AWS cloud account the user may need to do this using either IAM role or user
Why is it needed?
Allows user to be able to create clusters with the permissions they require.
Is this missing feature preventing you from using kubefirst?
Code of Conduct
The text was updated successfully, but these errors were encountered: