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
getting some information #2855
Comments
@erikbgithub Thank you for using Helm. Hopefully we can get your issues taken care of. To see parsed results of templating you may add the Helm uses gRPC not REST so you will not be able to see requests to Tiller as you might be used to in conventional REST applications.
Hope that helps. Please let us know if you have any more questions. |
Hi jascott1, thanks for responding. I'm not sure the namespace question is complete. Because I do both in a separate session after Example. Let's assume you start the day with a new bash session in which no helm environment is set. Tiller is already deployed. Now you do just a |
nope, I can understand @jascott1's instructions quite clearly (but then again, I'm a helm dev).
I can understand the confusion, though. TILLER_NAMESPACE is documented here:
Does that help clear things up? If not, I highly suggest taking a look through the Using Helm section of the docs to get a clearer picture. |
Ah now I understand. Thanks! |
Hi,
I really love the basic idea of helm templating. So I decided to use it for a project. But some things are still really hard to get.
For instance, after you parse my templates, where do you put the parsed results? It's so important if you have a parser for anything that you can view the results to see what the parser did maybe different than one expected.
Where can I see what http requests helm is sending (url+body)? I'm not having a default kubernetes installation here and need to make sure that others can also reach the tiller service. Also maybe seeing some http responses may help debug things.
What is the difference between the argument
--namespace
and the environment variable$TILLER_NAMESPACE
? For some reason I can only use helm when I do the second version. And I had nothing tell me about the problem. It was dumb try and error. Would be really nice if there would be a smarter way to debug.And why does a
helm delete --purge <name>
not remove everything? For instance in my environment there is always a serviceaccount that still exists after.Thanks!
The text was updated successfully, but these errors were encountered: