Uploaded image for project: 'Nuxeo ECM Build/Test Environment'
  1. Nuxeo ECM Build/Test Environment
  2. NXBT-3092

Use real domain names in jx-prod and jx-preprod (GCP)

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Jenkins X
    • Tags:
    • Sprint:
      DevTools-12, DevTools-13

      Description

      Description

      Update DNS records and names for the various exposed services inside jenkins X.

      Technical Aspect

      Connect to the wanted jx cluster : (ie: gcloud container clusters get-credentials jx-prod --zone us-east1-b --project jx-preprod).
      Execute the following to get the LoadBalancer IP address:

      kubectl get svc jxing-nginx-ingress-controller -n default -o'jsonpath={ .status.loadBalancer.ingress[0].ip }' 

      Note that in our jx-prod cluster, we have set the Ingress in the default namespace vs the jx default one :kube-system namespace.

      Go to gcloud dashboard, create a DNS zone for the domain wished (ie: platform.dev.nuxeo.com). Copy the associated nameservers.
      Inside this zone, create the A records (ie: jenkins.platform.dev.nuxeo.com) pointing to the LoadBalancer IP address.

      Go to aws route53, create a NS DNS record for the domain wished (ie : platform.dev.nuxeo.com), paste the copied nameservers. 

      Connect to the jx cluster, do kubectl get ingress --namespace=<the namespace> -o yaml
      Edit the host part and set it to the domain name.
       

      Examples of A records:

      jenkins.platform.dev.nuxeo.com
      nexus.platform.dev.nuxeo.com
      docker-registry.platform.dev.nuxeo.com
      chartmuseum.platform.dev.nuxeo.com

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.