Questions regarding the keystore

[johanneskastl]

I found the apacheds container image in the "Mastering Kubernetes" book, and started playing around with it. As I already played with 389ds and OpenLDAP in Kubernetes, I was curious.

I hacked together a helm chart that does deploy it successfully, and I can talk to the container. But only via LDAP (port 389).

For TLS I guess I need to prepare a proper TLS certificate and put it into the keystore file in /etc/apacheds/apacheds.jks. From what I found so far this is a mostly manual process. Not sure if this could be automated in the container setup, aka having certificate files from e.g. cert-manager mounted inside the container and automatically put into the keystore.

If this was possible, I daresay it would be a nice addition to the container image...

[mlbiam]

happy to accept docs, but this isn't meant for any kind of production use (apacheds recommends against it) so I don't really invest too much time here. It's really just meant as an easier to deploy "AD" then customizing OpenLDAP.