It seems that the helm chart for the Single doesn't properly respect creating a custom certificate.
Issue: name of the kubernetes secret holding the certificate (and credentials for that matter, same issue there) MUST be as according to the _helpers.tpl definition (clusterName prefix), else the StatefulSet will not use it.
Workaround: just name the certificate secret {clusterName}-certificate and the credentials {clusterName}-credentials.
It seems that the helm chart for the Single doesn't properly respect creating a custom certificate.
Issue: name of the kubernetes secret holding the certificate (and credentials for that matter, same issue there) MUST be as according to the
_helpers.tpl
definition (clusterName prefix), else the StatefulSet will not use it.Workaround: just name the certificate secret
{clusterName}-certificate
and the credentials{clusterName}-credentials
.Definition of certificate secret name: https://github.com/timescale/timescaledb-kubernetes/blob/8b946109c6273515d5414e4ddd1f60aa79f7c242/charts/timescaledb-single/values.yaml#L49-L52
Volume definition in statefulset: https://github.com/timescale/timescaledb-kubernetes/blob/8b946109c6273515d5414e4ddd1f60aa79f7c242/charts/timescaledb-single/templates/statefulset-timescaledb.yaml#L513-L515
Definition of the
secrets_certificate
name: https://github.com/timescale/timescaledb-kubernetes/blob/8b946109c6273515d5414e4ddd1f60aa79f7c242/charts/timescaledb-single/templates/_helpers.tpl#L109-L111