Making changes to your LDAP configuration

You can modify your LDAP configuration by updating either the LDAP settings ConfigMap or the ldap section of the Db2uInstance CR.

There are two types of LDAP configuration changes you can make, each with different requirements and impacts:

Changes to the LDAP settings ConfigMap require a pod restart.
Changes to the Db2uInstance CR ldap section require downtime.

Making changes to the LDAP settings ConfigMap

Changes made to the LDAP settings ConfigMap require a restart of all the pods. Once the edits to the ConfigMap are made, restarting the pods will result in the changes taking effect.

To edit the LDAP settings ConfigMap:

Run the following command:

oc edit configmap <ldap-configmap-name> -n <namespace>

Save your changes.

Restart the Db2u pods to apply the changes:
```
oc delete pods -l app=<db2uinstance-name> -n <namespace>
```
The pods will automatically restart and pick up the new LDAP configuration.

Making changes to the Db2uInstance CR

Changes to the ldap section of the Db2uInstance CR is a downtime operation. This includes changes to fields such as enabled, transparentLdap, searcherPassword, or fromVolumeSource.

To make changes to the Db2uInstance CR:

Add the downtime annotation to the Db2uInstance:

metadata:
  annotations:
    db2u.databases.ibm.com/maintenance-downtime: "true"

Edit the fields in the ldap section of the Db2uInstance CR. Any of the fields can be changed.
Apply the updated Db2uInstance CR:
```
oc apply -f db2uinstance.yaml
```
The Db2 pods will restart to apply the changes.
Wait for the pods to return to a Ready state:
```
oc get pods -n <namespace> -w
```

Remove the downtime annotation from the Db2uInstance CR to exit maintenance mode:

oc annotate db2uinstance <instance-name> db2u.databases.ibm.com/maintenance-downtime-