k3s-io/helm-controller

How to specify `--debug` to helm charts so installing with bad configuration is easier

ieugen opened this issue · 1 comments

Hello,

How can I enable --debug to helm controller so that I can debug failing charts.

For example I install apps like this:

helm upgrade --install dashboard-auth-proxy k8s-at-home/oauth2-proxy \
        --version=4.0.1 \
        --namespace system-apps \
        -f oauth2-values.yaml \
        --debug

This is one error I got with debug that I did not get with helm-controller:

client.go:108: [debug] creating 5 resource(s)
Error: Ingress.extensions "dashboard-auth-proxy-oauth2-proxy" is invalid: spec.rules[0].host: Invalid value: "map[host: xxxxxx paths:[/]]": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
helm.go:94: [debug] Ingress.extensions "dashboard-auth-proxy-oauth2-proxy" is invalid: spec.rules[0].host: Invalid value: "map[host:xxxxxx paths:[/]]": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

Helm controller swallowed the error and gave me nothing.
If there is a yaml issue I get the full output and the error printed.

I don't know if other params - like dry-run make sense.

Thanks,

+1 - just had problems with SSL (missing trust to signing CA) and with DNS name resolution - but the current logs do not give "feedback" to realize what is going wrong ;-)