Using External Keystore for Gerrit Helm Deployment Secrets (LDAP & PKCS12)

52 views
Skip to first unread message

Umebyoshi88

unread,
Jul 4, 2025, 9:47:58 AMJul 4
to Repo and Gerrit Discussion

Hi all,

I'm currently deploying Gerrit using the k8s-gerrit Helm charts and looking for a clean way to handle secrets like:

  • The pkcs12 keystore file and its password

  • The LDAP bind username and password

Right now, these values would end up in plain text in gerrit.config when rendered with Helm, which is obviously not ideal. I'd like to pull them dynamically at runtime from an external keystore or K8s Secret (mounted or otherwise), rather than hardcoding them into the chart values.

Has anyone found a pattern or approach for referencing secrets like these in a secure way during Helm rendering or at runtime? Ideally without maintaining a fork of the chart.

Appreciate any tips or pointers!
Best,

Basim

Thomas Dräbing

unread,
Jul 4, 2025, 10:03:49 AMJul 4
to Umebyoshi88, Repo and Gerrit Discussion
Hi Basim,

first of all please note that these helm charts were deprecated in favor of the Gerrit Operator which is part of the same project.

Regarding secrets find my comments inline below:

On Fri, 4 Jul 2025 at 15:47, Umebyoshi88 <basal...@gmail.com> wrote:

Hi all,

I'm currently deploying Gerrit using the k8s-gerrit Helm charts and looking for a clean way to handle secrets like:

  • The pkcs12 keystore file and its password

  • The LDAP bind username and password

Right now, these values would end up in plain text in gerrit.config when rendered with Helm, which is obviously not ideal. I'd like to pull them dynamically at runtime from an external keystore or K8s Secret (mounted or otherwise), rather than hardcoding them into the chart values.

There is no safe way to handle secrets in values.yml files of helm charts. The way the operator implements it, but which wasn't added to the chart before its deprecation, is that only a reference to a secret is provided in the configuration. Then the user applies the secret itself and the operator just configures the pods to mount it (usually in $SITE/etc).

HTH,
Thomas

Has anyone found a pattern or approach for referencing secrets like these in a secure way during Helm rendering or at runtime? Ideally without maintaining a fork of the chart.

Appreciate any tips or pointers!
Best,

Basim

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/repo-discuss/5c13ca5c-3b1e-4ad8-96be-a23619f3c73cn%40googlegroups.com.

Umebyoshi88

unread,
Aug 7, 2025, 1:27:55 PMAug 7
to Repo and Gerrit Discussion
Thank you Thomas, we found a way thanks to your input!
Reply all
Reply to author
Forward
0 new messages