WARNING: Jenkins X version 2.x is unmaintained. Do not use it.
Please refer to the v3 documentation for the latest supported version.
DNS
To be able to access services hosted within your cluster we default to an nip.io domain. This makes it super easy to setup and manage DNS.
However, for users who want services in the cluster to be available on a personal domain, we use external-dns which is just as easy.
external-dns
NOTE: Currently only supported on GKE
ExternalDNS can be used to help expose Kubernetes Services and Ingresses by synchronizing with DNS providers.
If you are using jx boot to install and configure your setup then modify your jx-requirements.yml
file to enable ingress.externalDNS: true
as described in the boot ingress documentation
Otherwise to setup your cluster using ExternalDNS use:
This will then prompt you for your domain.
A CloudDNS managed zone is then created within your clusters GCP Project, the record-sets which expose your services will be created by ExternalDNS within this managed zone.
delegation
Once the installation is complete, a list of name servers will be outputted to the terminal, please update your registrar using these name servers in order to delegate your domain onto Google CloudDNS.
Google domains
If you’re using Google Domains as your domain registrar please see here for details on delegating to custom name servers.
URL template
All services should be available on the same domain, of which is derived as follows:
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.