This version now use the Bitnami Openldap container image.

More detail on the container image can be found here

There are some major changes between the Osixia version and the Bitnami version , ergo the major gap of the chart version.

• Upgrade may not work fine between 3.x and 4.x
• Ldap and Ldaps port are non privileged ports (1389 and 1636) internally but are exposed through global.ldapPort and global.sslLdapPort (389 and 636)
• Replication is now purely setup by configuration. Extra schemas are loaded using LDAP_EXTRA_SCHEMAS: "cosine,inetorgperson,nis,syncprov,serverid,csyncprov,rep,bsyncprov,brep,acls. You can add your own schemas via the customSchemaFiles option.

A default tree (Root organisation, users and group) is created during startup, this can be skipped using LDAP_SKIP_DEFAULT_TREE , however you need to use customLdifFiles or customLdifCm to create a root organisation.

• This will be improved in a future update.

• Kubernetes 1.8+
• PV support on the underlying infrastructure

This chart will do the following:

• Instantiate 3 instances of OpenLDAP server with multi-master replication
• A phpldapadmin to administrate the OpenLDAP server
• ltb-passwd for self service password

To install the chart with the release name my-release:

$ helm repo add helm-openldap https://jp-gouin.github.io/helm-openldap/
$ helm install my-release helm-openldap/openldap-stack-ha

We use the container images provided by https://github.com/bitnami/containers/tree/main/bitnami/openldap. The container image is highly configurable and well documented. Please consult to documentation of the image for more information.

The following table lists the configurable parameters of the openldap chart and their default values.

Global parameters to configure the deployment of the application.

Parameters related to the configuration of the application.

Parameters related to PHPLdapAdmin

For more advance configuration see README.md
For all possible chart parameters see chart's README.md

Parameters related to Self-service password.

For more advance configuration see README.md
For all possible parameters see chart's README.md

Parameters related to Kubernetes.

Specify each parameter using the --set key=value[,key=value] argument to helm install.

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

$ helm install --name my-release -f values.yaml stable/openldap

Tip: You can use the default values.yaml

To enable PhpLdapAdmin set phpldapadmin.enabled to true

Ingress can be configure if you want to expose the service. Setup the env part of the configuration to access the OpenLdap server

Note : The ldap host should match the following namespace.Appfullname

Example :

phpldapadmin:
  enabled: true
  ingress:
    enabled: true
    annotations: {}
    # Assuming that ingress-nginx is used
    ingressClassName: nginx
    path: /
    ## Ingress Host
    hosts:
    - phpldapadmin.local
  env:
    PHPLDAPADMIN_LDAP_CLIENT_TLS_REQCERT: "never"

To enable Self-service-password set ltb-passwd.enabled to true

Ingress can be configure if you want to expose the service.

Setup the ldap part with the information of the OpenLdap server.

Set bindDN accordingly to your ldap domain

Note : The ldap server host should match the following ldap:https://namespace.Appfullname

Example :

ltb-passwd:
  enabled : true
  ingress:
    enabled: true
    annotations: {}
    # Assuming that ingress-nginx is used
    ingressClassName: nginx
    host: "ssl-ldap2.local"

Deleting the Deployment will not delete associated Persistent Volumes if persistence is enabled.

Do the following after deleting the chart release to clean up orphaned Persistent Volumes.

$ kubectl delete pvc -l release=${RELEASE-NAME}

global.existingSecret can be used to override the default secret.yaml provided

You can increase the level of log using env.LDAP_LOGLEVEL

Valid log levels can be found here

Warning when using custom ldif in the customLdifFiles or customLdifCm section you have to create the high level object organization

dn: dc=test,dc=example
dc: test
o: Example Inc.
objectclass: top
objectclass: dcObject
objectclass: organization

note the admin user is created by the application and should not be added as a custom ldif

All internal configuration like cn=config , cn=module{0},cn=config cannot be configured yet.

This major update switch the base image from Osixia to Bitnami Openldap

• Upgrade may not work fine between 3.x and 4.x
• Ldap and Ldaps port are non privileged ports (1389 and 1636)
• Replication is now purely setup by configuration
• Extra schema cannot be added/modified

A default tree (Root organisation, users and group) is created during startup, this can be skipped using LDAP_SKIP_DEFAULT_TREE , however you need to use customLdifFiles or customLdifCm to create a root organisation.

• This will be improved in a future update.

This major update of the chart enable new feature for the deployment such as :

• supporting initcontainer
• supporting sidecar
• use global parameters to ease the configuration of the app
• out of the box integration with phpldapadmin and self-service password in a secure way