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

Support unsealing into multiple namespaces #929

Open
KlavsKlavsen opened this issue Aug 25, 2022 · 1 comment
Open

Support unsealing into multiple namespaces #929

KlavsKlavsen opened this issue Aug 25, 2022 · 1 comment
Labels
backlog Issues/PRs that will be included in the project roadmap enhancement

Comments

@KlavsKlavsen
Copy link
Contributor

KlavsKlavsen commented Aug 25, 2022

Which component:
Controller

Is your feature request related to a problem? Please describe.
We have several containers that needs fetching from a password protected registry - and currently we have to have the SAME secret defined for each namespace we need them in.

We also have other secrets, which we have to duplicate in multiple namespaces

Describe the solution you'd like
If we could put multiple namespace targets on 1 secret - that would make life so much easier :)

@github-actions github-actions bot added the triage Issues/PRs that need to be reviewed label Aug 25, 2022
@alemorcuq alemorcuq added enhancement backlog Issues/PRs that will be included in the project roadmap and removed triage Issues/PRs that need to be reviewed labels Aug 25, 2022
@alemorcuq alemorcuq added this to Inbox in Sealed Secrets via automation Aug 25, 2022
@rowi1de
Copy link

rowi1de commented Nov 18, 2022

You can try this as a workaround https://github.com/emberstack/kubernetes-reflector but it would be a really helpful feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Issues/PRs that will be included in the project roadmap enhancement
Projects
Sealed Secrets
  
Inbox
Development

No branches or pull requests

3 participants