What would you like to be added:
KUDO should store init parameters somwhere in the cluster. Either a config map, or labels/attributes on the controller, etc.
Why is this needed:
Currently, when a user installs KUDO he can use a couple of parameters, notably:
--kudo-image
--kudo-image-pull-policy
--service-account
--unsafe-self-signed-webhook-ca
These flags should be used with exact the same values on all further invocations that affect the KUDO installation. Upgrades to KUDO, uninstall, verification if the installation is correct, etc.
This is
a) very inconvenient
b) error prone
c) problematic if multiple users work with the KUDO installation.
What would you like to be added: KUDO should store init parameters somwhere in the cluster. Either a config map, or labels/attributes on the controller, etc.
Why is this needed: Currently, when a user installs KUDO he can use a couple of parameters, notably:
--kudo-image--kudo-image-pull-policy--service-account--unsafe-self-signed-webhook-caThese flags should be used with exact the same values on all further invocations that affect the KUDO installation. Upgrades to KUDO, uninstall, verification if the installation is correct, etc.
This is a) very inconvenient b) error prone c) problematic if multiple users work with the KUDO installation.