Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
ieugen opened this issue Nov 27, 2020 · 1 comment

Comments

@ieugen
Copy link

ieugen commented Nov 27, 2020

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,

@Martin-Weiss
Copy link

+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 ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants