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

Cannot set all CLI arguments to secrets-init #48

Open
tpiscitell opened this issue Jan 25, 2024 · 1 comment
Open

Cannot set all CLI arguments to secrets-init #48

tpiscitell opened this issue Jan 25, 2024 · 1 comment

Comments

@tpiscitell
Copy link

I noticed the arguments passed to secrets-init are hard coded to just --project. However, secrets-init has other arguments that it accepts. It would be nice if we could specify exactly what arguments are set by the webhook controller.

@tpiscitell
Copy link
Author

FWIW, I think the most straight forward solution is to create a CLI flag in kube-secrets-init for every one in secrets-init. That would make it easy to specify arguments for secrets-init when deploying kube-secrets-init. However, it does come at the cost of requiring a change in kube-secrets-init every time secrets-init changes.

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

No branches or pull requests

1 participant