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.

Sign up for GitHub

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

Jump to bottom

K8S_SECRETS is not required #438

Open
JfcAtCyberArk opened this issue Feb 10, 2022 · 2 comments
Open

K8S_SECRETS is not required #438

JfcAtCyberArk opened this issue Feb 10, 2022 · 2 comments
Labels
internal-contributor kind/enhancement

Comments

@JfcAtCyberArk
Copy link

Is your feature request related to a problem? Please describe.

Currently the secrets-provider-for-k8s is expecting a K8S_SECRETS parameter (init or application mode).
As described in issue #140 and solution design #137 this limits scalability, especially for application mode.

Describe the solution you would like

K8S_SECRETS is optional.
Default list is based on secrets the service account has access to.
@rpothier
Copy link
Contributor

Hi @JfcAtCyberArk ,
Thanks for opening this issue, we are reviewing it and will get back to you.

@alexkalish
Copy link
Contributor

Hey @JfcAtCyberArk. Could you please file an official enterprise enhancement request? That would be the best way to get your suggestion in front of key product stakeholders. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
internal-contributor kind/enhancement
Milestone
No milestone
Development

No branches or pull requests
4 participants
@alexkalish @rpothier @JfcAtCyberArk @ConjOps