You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I'm doing right now is propagating this TLS certificate to other namespaces via the https://github.com/emberstack/kubernetes-reflector, which requires annotating the secret, which isn't possible via the helm chart.
What did you expect to happen?
Ability to set the self-generated secrets annotation via values.yml
How can we reproduce it (as minimally and precisely as possible)?. Please include values file.
What happened?
Installed helm chart for a production workload generates the TLS certificates with default labels and annotations:
kubectl describe secret redpanda-default-cert -n redpanda
What I'm doing right now is propagating this TLS certificate to other namespaces via the https://github.com/emberstack/kubernetes-reflector, which requires annotating the secret, which isn't possible via the helm chart.
What did you expect to happen?
Ability to set the self-generated secrets annotation via
values.yml
How can we reproduce it (as minimally and precisely as possible)?. Please include values file.
Values:
Anything else we need to know?
No response
Which are the affected charts?
Redpanda
Chart Version(s)
Cloud provider
kubernetes v1.29.9
JIRA Link: K8S-469
The text was updated successfully, but these errors were encountered: