Able to set Debug option for each HelmChartProxy individually

[dmvolod]

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.

helm install -f myvalues.yaml myredis ./redis --debug

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

[Jont828]

/triage-accepted

Will take a look on Thurs.

[dmvolod]

Thanks for accepting, @Jont828
Was planning to fix it soon

[dmvolod]

/assign

[Jont828]

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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[dmvolod]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[dmvolod]

/remove-lifecycle stale