Allow Kubernetes token (Service account) deployments about helm HOT 2 CLOSED

Thanks @italolelis! You are definitely right using a service account is the way to go for deploying with Helm. However ultimately we do need a Kubeconfig to coordinate talking to the Kubernetes cluster. I think the question here is how that Kubeconfig file is built up, is that correct?

The way that I've actually built up a Kubeconfig file before is using a script like this: https://gist.github.com/ericchiang/d2a838ddad3f44436ae001a342e1001e. This will embed your service account token and configuration into a Kubeconfig file. If you run that on your machine it should spit out a Kubeconfig file which you can then add into your GitHub repository secrets.

I noticed that you also have the setting skip_tls_verify: true above -- this method will copy in the necessary certificates so you won't have to specify this option!

from helm.

Hey @colinjfw,

Thanks for your reply. Yeah, that makes sense. I'll try that out and see how everything blends into the workflow. Should be straight forward. Thank you for providing the script, it was really helpful.

I think we can close this issue then

from helm.