duynguyen/k8s-cluster
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: update jenkins values to use existing-secret for admin credentials

Browse Source
This commit is contained in:
duynguyen
2026-04-12 23:26:38 +07:00
parent eb00e23e48
commit 741e3fb63b
1 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
manifest/jenkins/values.yaml
View File

@@ -89,19 +89,11 @@ controller:
# @default -- <random password>
password:
# -- The key in the existing admin secret containing the username
userKey: jenkins-admin-user
# -- The key in the existing admin secret containing the password
passwordKey: jenkins-admin-password
# The default configuration uses this secret to configure an admin user
# If you don't need that user or use a different security realm, then you can disable it
# -- Must stay true so the controller mounts the admin Secret; when existingSecret is set, the chart does not create that Secret (supply it yourself or via externalSecret).
createSecret: false
# -- If set, chart does not create the admin Secret; you must create it (e.g. kubectl) or use externalSecret (requires ESO CRDs on the cluster).
existingSecret: ""
# -- Emits external-secrets.io/v1beta1 ExternalSecret (needs External Secrets Operator installed). Helm cannot talk to Vault without it or another sync mechanism.
externalSecret:
enabled: true
@@ -116,6 +108,15 @@ controller:
property: password
# Must match secretKey below; exposed to the template as .password
secretKey: password
# -- If set, chart does not create the admin Secret; you must create it (e.g. kubectl) or use externalSecret (requires ESO CRDs on the cluster).
existingSecret: "jenkins-admin"
# -- The key in the existing admin secret containing the username
userKey: jenkins-admin-user
# -- The key in the existing admin secret containing the password
passwordKey: jenkins-admin-password
# -- Email address for the administrator of the Jenkins instance
jenkinsAdminEmail: