-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
fix: select secretstores in same ns as pushsecret #5109
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: select secretstores in same ns as pushsecret #5109
Conversation
Signed-off-by: Grace Do <[email protected]>
e07e526 to
61e6ddf
Compare
|
/ok-to-test sha=61e6ddf949c8f61b8f0ff5912fe2731a13380912 |
|
|
|
/ok-to-test sha=5423347c7a480512433ca085af51f0e6a9f1cba2 |
moolen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for fixing this issue 🙇, really appreciated!
There's another issue with r.List() in pushsecret_controller which should be scoped to a namespace, thanks for raising this.
) Signed-off-by: Grace Do <[email protected]> Co-authored-by: Gergely Brautigam <[email protected]> Co-authored-by: Moritz Johner <[email protected]>



Problem Statement
PushSecretsdefining label selectors to selectSecretStoresare trying to selectSecretStoresfrom all namespaces, instead of the same namespace as thePushSecret. This causes errors reconciling thePushSecretas it attempts to get theseSecretStoresin the same namespace but they don't exist.Related Issue
Proposed Changes
When listing
SecretStoresby label selector, thenamespaceoption should be passed in to only getSecretStoresin the same namespace as thePushSecret.Checklist
git commit --signoffmake testmake reviewable