-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
fix: Expand Permissions for external-secrets IRSA Policy towards AWS Secrets Manager #416
fix: Expand Permissions for external-secrets IRSA Policy towards AWS Secrets Manager #416
Conversation
9685300
to
3acd563
Compare
Some kubectl describe Output:
Some Logs:
|
I also managed to update the documentation at external-secrets/external-secrets#2653 |
### [5.29.2](v5.29.1...v5.29.2) (2023-08-30) ### Bug Fixes * Expand Permissions for external-secrets IRSA Policy towards AWS Secrets Manager ([#416](#416)) ([fa74a18](fa74a18))
This PR is included in version 5.29.2 🎉 |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Initial set of permissions (#414) was not sufficient. Checked the source code of the secrets manager implementation of external-secrets and added remaining permissions.
Motivation and Context
There were errors on certain use cases, such as a secret changes and needs to be pushed again.
Breaking Changes
No
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request