Allowing users to modify webhook configuration values directly is not ideal. Currently, generating webhooks relies on Kubebuilder markers, which creates challenges in Helm chart generation.
The goal is to enable webhook chart generation with minimal exposure in values.yaml, ideally limiting it to webhook.enable: true, as done for other options. Exposing all data does not make sense when we do not want people to make changes to it.
Additionally, the current approach requires using --force to regenerate webhooks, which overwrites any value customisations.yaml, leading to a potential loss of configurations.
camilamacedo86
commented
5 days ago
What do you want to happen?
Allowing users to modify webhook configuration values directly is not ideal. Currently, generating webhooks relies on Kubebuilder markers, which creates challenges in Helm chart generation.
The goal is to enable webhook chart generation with minimal exposure in values.yaml, ideally limiting it to webhook.enable: true, as done for other options. Exposing all data does not make sense when we do not want people to make changes to it.
Additionally, the current approach requires using --force to regenerate webhooks, which overwrites any value customisations.yaml, leading to a potential loss of configurations.
Extra Labels
No response