Versions Compared

Old Version 1

changes.mady.by.user Jenni Wallin

Saved on

compared with

New Version 2

changes.mady.by.user Wei Siong Siow

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Create a file called external-dns-values.yaml and populate it with the following helm values:

    Code Block
    gcpgoogle:
  zoneTypezoneVisibility: public
  project: pt-dev-stratus-bliz
domainFilters:
  - <gke_domain_dns_name from terraform output>
policy: sync
provider: google
txtOwnerId: <gke_domain_zone_name from terraform output>
serviceAccount:
  annotations:
    iam.gke.io/gcp-service-account: <external_dns_service_account from terraform output>

  2. Install the ExternalDNS helm chart:

    Code Block
    helm install external-dns bitnami/external-dns -n uepe \
--version <helm chart version> -f external-dns-values.yaml

    Where <helm chart version> is a compatible version listed in the Compatibility Matrix (4.3).

Ingress NGINX Controller

Info

This is an optional add-on. Refer to the Introduction - GCP (4.13) chapter for additional information.

...

  1. Install the ingress-nginx-controller helm chart:

    Code Block
    helm install ingress-nginx ingress-nginx/ingress-nginx --version <helm chart version> -f ingress-nginx-values.yaml -n uepe

    Where <helm chart version> is a compatible version listed in the Compatibility Matrix (4.3).

Info

If you are running multiple installations on the cluster, in case the Nginx IngressClass resource is already installed, then you should set the following helm value to avoid hitting a resource already exists error:

controller.ingressClassResource.enabled=false

...

This section is now complete. Now proceed to the Usage Engine Private Edition Preparations - GCP (4.3) section.