CODEWITHSUNDEEP
kubernetesinfluxdb
Greg McNamara
Greg McNamara

Reputation: 35

InfluxDb on Kubernetes with TLS ingress

I'm setting up influxdb2 on a kubernetes cluster using helm. I have enabled ingress and it works ok on port 80, but when I enable TLS and set the "secretName" to an existing TLS secret on kubernetes it times out on port 443. Is my assumption that "secretName" in the helm chart refers to a kubernetes cluster secret? Or is it a secret within influxdb itself? I can't find any useful documentation about this.

Upvotes: 0

Views: 761

Answers (1)

Kiran Indukuri
Kiran Indukuri

Reputation: 412

It is a reference to a new Kubernetes secret that is going to be created corresponding to the tls cert. It does not have to reference an existing secret. If you run kubectl get secrets after a successful apply , you would see a secret something like <cert-name>-afr5d

Upvotes: 0

Related Questions