You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.The text was updated successfully, but these errors were encountered: