WARNING: Jenkins X version 2.x is unmaintained. Do not use it.
Please refer to the v3 documentation for the latest supported version.
TLS
Configuring TLS with Jenkins X
As documented in the Ingress section of the Boot documentation, you can configure a global default certificate for all Jenkins X ingresses.
This requires using DNS01 for a wildcard certificate, or manually adding and updating your certificate.
In case this is not practical, and you want to generate one certificate per ingress using http01, you can specify the secretName
to be used for each ingress in the values.yaml
as described below:
ingress:
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
hook:
ingress:
tls:
secretName: tls-hook
nexus:
ingress:
tls:
secretName: tls-nexus
...
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified June 24, 2020: fix: de-duplicating nested install structure (ba9f980e30)