I finally had some time to rework my helm chart for 389ds. It seems to be in a
working state, so if anyone is interested I would be glad to have some testers.
Please be aware that this is the first version, use at your own risk and proceed
with caution. Here be dragons...
That said, it works for me, I get a working pod that I can interact with using
ldapsearch/ldapadd/... and dsidm. (dsctl does not work for $REASONS, see my
This chart might be opinionated, as I tailored it to my needs (e.g. using a
Let's encrypt TLS certificate, ...).
By default, it creates a service of type Loadbalancer with ports 389 and 636
(TCP). It uses the TLS certificate from a Kubernetes secret and the CA
certificate from a configMap that is created automatically. The README has the
full details and explanations.
It is currently based on the 2.2 image from dockerhub due to the missing tags,
see my other earlier mail. :-)
Please feel free to point out any errors or improvements. I cannot promise to
integrate each and every request, but I'll do my best.
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg
GF: Ralph Dehner
Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537