Modified ldap.md for issue #937 (#951)

This commit is contained in:
Aniket Shitole 2024-02-04 15:54:47 +05:30 committed by GitHub
parent 2ba5334c10
commit 332eabe8d7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 24 additions and 25 deletions

View File

@ -77,31 +77,30 @@ data:
userIdStrategy: "caseInsensitive" userIdStrategy: "caseInsensitive"
``` ```
> Note the use of `${LDAP_MANAGER_PASSWORD}` above. You can reference >Note the use of `${LDAP_MANAGER_PASSWORD}` above. You can reference
> Kubernetes secrets in your JCasC ConfigMaps by adding the following to your >Kubernetes secrets in your JCasC ConfigMaps by adding the following to your
> Jenkins object:
> Jenkins object:
> ```yaml
> kind: Jenkins ```yaml
> spec: kind: Jenkins
> configurationAsCode: spec:
> configurations: configurationAsCode:
> - name: jenkins-casc configurations:
> secret: - name: jenkins-casc
> # This here secret:
> name: jenkins-casc-secrets # This here
> ``` name: jenkins-casc-secrets
> ```
> ```yaml ```yaml
> apiVersion: v1 apiVersion: v1
> kind: Secret kind: Secret
> metadata: metadata:
> name: jenkins-cred-conf-secrets name: jenkins-cred-conf-secrets
> stringData: stringData:
> LDAP_MANAGER_PASSWORD: <password-for-manager-created-in-ldap> LDAP_MANAGER_PASSWORD: <password-for-manager-created-in-ldap>
> ``` ```
> Schema reference: [v1alpha2.ConfigurationAsCode](./schema/#github.com/jenkinsci/kubernetes-operator/pkg/apis/jenkins/v1alpha2.ConfigurationAsCode)
> Schema reference: [v1alpha2.ConfigurationAsCode](./schema/#github.com/jenkinsci/kubernetes-operator/pkg/apis/jenkins/v1alpha2.ConfigurationAsCode)
Finally you must configure the Jenkins operator to use the manager's Finally you must configure the Jenkins operator to use the manager's
credentials from the AD. credentials from the AD.