This message was deleted.
# rke2a
adamant-kite-43734
05/16/2024, 10:46 AMThis message was deleted.
p
powerful-librarian-10572
05/16/2024, 10:52 AMhttps://helm.sh/docs/helm/helm_registry_login/
is an available argumentCopy code--key-file string identify registry client using this SSL key file
đź‘Ť 1
c
creamy-pencil-82913
05/16/2024, 4:56 PMno, not supported at the moment. I guess we could make it so that if the HelmChart’s Spec.AuthSecret pointed to a TLS secret, we would use that for tls client auth.
creamy-pencil-82913
05/16/2024, 5:37 PMb
better-animal-75203
05/17/2024, 6:27 AMSo current workaround for now would be using "set.spec" ,right?
c
creamy-pencil-82913
05/17/2024, 6:53 AMNo, set is passed through to the --set flag. There is no way to add arbitrary flags to the helm command.
b
better-animal-75203
05/17/2024, 8:58 AMOur private helm repo only support tls client auth, so I am not sure how can I make it work then. Any workaround if you know?
better-animal-75203
05/17/2024, 9:01 AMMay be if I pull it using normal helm command(passing certs) . then base64 encode the downloaded helm tar and add it into the helm "spec.chartContent"
c
creamy-pencil-82913
05/17/2024, 4:48 PMThat would work
creamy-pencil-82913
05/17/2024, 4:49 PMYou're the first person I've seen using TLS client auth for a helm repo!
3 Views