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

document and minimize IAM rule policy for CSI #19

Merged
merged 5 commits into from
Mar 7, 2024

Conversation

sauterp
Copy link
Member

@sauterp sauterp commented Mar 7, 2024

Description

We document the minimal IAM rule policy needed for the CSI to operate.

Checklist

(For exoscale contributors)

  • Changelog updated (under Unreleased block)
  • Integration tests OK

Testing

The documented policy is also setup for the CSI during integration tests.

Copy link

This pull request has been linked to Shortcut Story #88955: CSI: document required permissions for API key.

@sauterp sauterp marked this pull request as ready for review March 7, 2024 08:43
README.md Outdated
@@ -6,7 +6,25 @@ Exoscale Block Storage Container Storage Interface Driver.

* Make sure you have the [CCM](https://github.com/exoscale/exoscale-cloud-controller-manager) deployed and running in your cluster.

* Create secret with [exoscale-secret.sh](./deployment/exoscale-secret.sh).
* An API key and we recommend assigning it an IAM role with minimal permissions as in the following policy:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this role be part of the predefined user roles catalog?

@brutasse @anthonygalea

README.md Outdated Show resolved Hide resolved
Co-authored-by: Arnaud Geiser <[email protected]>
@sauterp sauterp merged commit f40ebce into main Mar 7, 2024
1 check passed
@sauterp sauterp deleted the philippsauter/sc-88955/minimize-IAM-role branch March 7, 2024 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants