You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configure kubernetes authentication between the Jenkins cluster and Hashicorp Vault
Add required CASC env vars as described in documentation:
CASC_VAULT_URL="https://" (url of the vault server)
CASC_VAULT_KUBERNETES_ROLE="jenkins-role" (name of role in Vault)
CASC_VAULT_MOUNT="csi_lke_jenkins" (name of said cluster auth mount in vault)
CASC_VAULT_PATHS="csi_lke_jenkins/sso-secrets" (path of an example secret)
Update jcasc file to take values from vault path, as described in documentation, example (tried using 3 different approaches to extract secrets under path csi_lke_jenkins/sso-secrets):
Jenkins config refreshes, none of the configured values are there...
Expected Results
I expected either the values from vault will be inputted in the configuration file,
or at least to get some kind of error log specifying why this isn't working, whether anything failed
Actual Results
Values are simply not added to the jcasc config file, not seeing any logs from the plugin
Anything else?
Important to note this is definitely not an issue with the kubernetes authentication configuration, as we use the same service account and role for the general vault integration, and it is working as intended.
I am also not sure if the issue is with kubernetes auth support or generally with the jcasc integration, as the kubernetes auth is the only method I am currently able to test.
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Running on k8s, Linux based
Reproduction steps
Expected Results
I expected either the values from vault will be inputted in the configuration file,
or at least to get some kind of error log specifying why this isn't working, whether anything failed
Actual Results
Values are simply not added to the jcasc config file, not seeing any logs from the plugin
Anything else?
Important to note this is definitely not an issue with the kubernetes authentication configuration, as we use the same service account and role for the general vault integration, and it is working as intended.
I am also not sure if the issue is with kubernetes auth support or generally with the jcasc integration, as the kubernetes auth is the only method I am currently able to test.
The text was updated successfully, but these errors were encountered: