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
User Story
Right now, debug option can be enabling for whole controller and components centrally as running flag. And it's not possible to setup it for each HelmChartProxy, but in some cases, whole controller reconfiguration are not allowing.
As a user, I would like to enable debug option for each HelmChartProxy individually like a helm cli command, i.e.
Detailed Description
For this case, I suggesting to create an optional Debug (bool) field inside the HelmOptions API struct, propagate it into the HelmInit method and set log level to 2 (default) if this option is enabled.
/kind feature
The text was updated successfully, but these errors were encountered:
I took a closer look at your issue, and I think passing the --debug flag in to helm install or helm upgrade for an individual HelmChartProxy instance makes sense. Only thing is that I'm not sure if we can set the log level on the CRD level, since that gets set by the controller args for the whole container when the caaph-controller-manager pod gets created, not on each reconciliation loop.
User Story
Right now, debug option can be enabling for whole controller and components centrally as running flag. And it's not possible to setup it for each HelmChartProxy, but in some cases, whole controller reconfiguration are not allowing.
As a user, I would like to enable debug option for each HelmChartProxy individually like a helm cli command, i.e.
Detailed Description
For this case, I suggesting to create an optional Debug (bool) field inside the
HelmOptions
API struct, propagate it into the HelmInit method and set log level to2
(default) if this option is enabled./kind feature
The text was updated successfully, but these errors were encountered: