apache / apache/pulsar-helm-chart
CA Cert Suffix without release name
- Dominant language
- Shell
- Stars
- 240
- Forks
- 260
- Avg merge
- 4h 12m
- Merged PRs (30d)
- 1
Description
**Describe the bug**
On the services TPL files withe CA cert secretName is defined with
```
secretName: "{{ .Release.Name }}-{{ .Values.tls.ca_suffix }}"
```
([see](https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/_bookkeeper.tpl#L78)), 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**
1. create a ca secret e.g. "foobar" (without release name prefix)
2. 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
```
3. on the e.g. `pulsar-zookeeper-0` pod you can see the error message
```
MountVolume.SetUp failed for volume "ca" : secret "release-name-foobar" not found
```
**Expected behavior**
three possibility solutions:
1. behaviour as it is
2. 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
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.