Getting secret name tiller-client-certs about kubergrunt HOT 5 CLOSED

This should be doable, as long as all three commands (grant, configure, revoke) are updated to support this semantic. Right now configure and revoke use that name in some capacity to uniquely identify that secret.

On another note, does flux support looking up the secret by labels? We attach the label gruntwork.io/tiller-entity-id and gruntwork.io/tiller-namespace that you can use to look up the Secrets using more friendly strings.

from kubergrunt.

Let's keep this open since I think it is a valid enhancement to make. With that said, this whole functionality will be deprecated soon once helm 3 reaches GA :)

from kubergrunt.

I took a look at the code and figured it was md5 hashed number of service account name so I'm currently had success getting the name using the following

  flux_namespace_sa = "${var.tiller_namespace}.${local.flux_service_account}"
  tls_client_secret_name = "tiller-client-${md5(local.flux_namespace_sa)}-certs"

Note that both flux/tiller is being deployed in the same namespace to be able to mount secrets.

from kubergrunt.

Hi @yorinasub17 sorry for not getting back earlier, currently flux helm chart only able to get certs by secret name, I'm using the workaround which works well for me

tls_client_secret_name = "tiller-client-${md5(local.flux_namespace_sa)}-certs"

if you prefer the issue to be closed, that's fine by me.

Thanks for your help

from kubergrunt.

Helm features are removed, so this is no longer relevant.

from kubergrunt.