public_git
/
kubernetes-operator
mirror of https://github.com/jenkinsci/kubernetes-operator.git
1
0
Fork 0
Code Issues Releases Wiki Activity

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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
website/content/en/docs/Getting Started/v0.7.x/ldap.md
View File

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