-
Notifications
You must be signed in to change notification settings - Fork 243
Open
Description
Describe the bug
On the services TPL files withe CA cert secretName is defined with
secretName: "{{ .Release.Name }}-{{ .Values.tls.ca_suffix }}"
(see), in my deployment the Release.Name is not used for the CA Secret, but the services expectd the name everytime, so in this case, the container does not find the ca secret.
To Reproduce
- create a ca secret e.g. "foobar" (without release name prefix)
- deploy the helm chart and set the values with
nameOverride: pulsar fullnameOverride: pulsar broker: replicaCount: 1 zookeeper: replicaCount: 1 bookkeeper: replicaCount: 1 proxy: replicaCount: 1 tls: enabled: true ca_suffix: foobar broker: enabled: true zookeeper: enabled: true bookkeeper: enabled: true proxy: enabled: true - on the e.g.
pulsar-zookeeper-0pod you can see the error messageMountVolume.SetUp failed for volume "ca" : secret "release-name-foobar" not found
Expected behavior
three possibility solutions:
- behaviour as it is
- I can define free name of the ca without any release prefix
This bevaiour exists as well on all Pulsar components, Zookeeper, Bookie etc, so it should be consist on all services.
Thanks a lot
Metadata
Metadata
Assignees
Labels
No labels