docker-openldap/example/kubernetes/using-secrets
Bertrand Gouny 80b9afb242 Merge branch 'timgates42-bugfix_typos' into release-1.5.0 2021-02-19 12:58:52 +01:00
..
environment Adding readme and ignores 2019-05-11 14:04:41 -05:00
.gitignore Adding ldap deployment to example mechanism so it is gitignored as well 2021-02-03 14:10:40 -06:00
Makefile Adding port 636 2021-02-03 14:30:56 -06:00
README.md Merge branch 'timgates42-bugfix_typos' into release-1.5.0 2021-02-19 12:58:52 +01:00
gce-statefullset.yaml docs: v1.5.0 2021-02-14 13:55:13 +01:00
ldap-deployment.yaml.example docs: v1.5.0 2021-02-14 13:55:13 +01:00
ldap-secret.tpl Templating out the secret yaml 2019-05-11 14:03:46 -05:00
ldap-service.yaml redefining port 2021-02-03 22:08:08 -06:00

README.md

Helm-chart

After setting the variables you can get strange variables like:

https://github.com/osixia/docker-openldap/issues/342

I have found that using this helm chart does not have those issues:

https://github.com/jp-gouin/helm-openldap.git

Generating ldap-secret.yaml

make example

Then edit the yaml files in the environment directory to have the desired parameters, and then make the secret file:

make ldap-secret.yaml

And deploy the secret you just made:

kubectl apply -f ldap-secret.yaml

Apply the deployment yaml for ldap in k8s:

kubectl apply -f ldap-deployment.yaml

Finally apply the service yaml for ldap in k8s:

kubectl apply -f ldap-service.yaml