helm-operator when creating certificate via secret , diff certificate seen in different pods even after using same certificate from secret

[malli31]

Bug Report

helm-operator when creating certificate via secret , diff certificate seen in different pods even after using same certificate from secret

What did you do?

Created certificate in

{{- $cn := "localhost" }}

{{- $CA := genCA $cn 3650 }}
{{- $Cert := genSignedCert $cn nil nil 3650 $CA }}

{{- $PemCert := $Cert.Cert | b64enc | quote }}
{{- $PemKey := $Cert.Key | b64enc | quote }}
{{- $PemCA := $CA.Cert | b64enc | quote }}

apiVersion: v1
kind: Secret
metadata:
namespace: {{ .Release.Namespace }}
name: Secret-certs
data:
ca-cert.pem: {{ $PemCA }}

Started using this after mounting in my pods

volumes:
- name: container-certs
secret:
secretName: Secret-certs

What did you expect to see?

I want to have same certificate in both pods since same secret is being used

What did you see instead? Under which circumstances?

Environment

Operator type:

Kubernetes cluster type:

$ operator-sdk version

$ go version (if language is Go)

$ kubectl version

Possible Solution

Additional context

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale