-
Notifications
You must be signed in to change notification settings - Fork 35
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
Minimum permissions #96
Comments
Hey @antoinecastex we definitely agree the "least privilege" is concept we should implement, we'll start working on this shortly, I'll keep this udpated with our progress. |
Hey @antoinecastex thanks for the patience, it took us longer than expected 😅 First a Warning: This is what we did:
That's that, we would like to document that in our main README, however it could be super helpful if you could test that in your test environment first and let us know if you encounter any issues before we do. Please let me know if my above instructions are clear enough as well 😄 Awaiting your reply |
It's done and that's work very well thanks @eranchetz |
Hey @antoinecastex I don't know if you are using Zorya for CloudSQL, but it seems we were missing one permission: I have also added it above and I will document it later on. |
@eranchetz i'm not using for CloudSQL from now but thanks for the information |
Hello Team DoIt !
Hope you are doing well ?
Here we are deploying Zorya globally to manage the VMs and also the Cloud SQL instances & GKE Cluster, that's nice !
We just have a question regarding permission for theses 3 products
What's the minimum permissions (can be created under custom role) for that ? Because for example Compute Instance Admin v1 seems to be big just for start and stop vms ?
Thanks a lot
The text was updated successfully, but these errors were encountered: