Activating the External DNS integrated service creates DNS entries for the public services running in the cluster. Note that:

  • You have to create and expose the public services (for example, enable Ingress).
  • Existing services are ignored. Pipeline creates DNS entries only for the public services that are exposed after you have activated the External DNS integrated service.
  • The time it takes for the DNS entry of a service to become accessible depends on your cloud DNS provider.

You can make the DNS entries publicly available from the entire Internet, or you can restrict access to specific subdomains.

Prerequisites 🔗︎

  • Access to one of the supported domain name (DNS) providers, with a secret already configured in Banzai Cloud Pipeline.
  • Depending on the DNS provider you use, you might have to create provider-specific resources first, for example, a Resource Group in AzureDNS, or a Project in Google Cloud DNS.
  • To make the integrated services (for example, Cluster logging and Cluster monitoring) accessible, enable Ingress for the service.

Configure the External DNS integrated service 🔗︎

  1. Navigate to Cluster Management, then the cluster you want to configure. A sidebar opens.

  2. In the sidebar, click External DNS.

  3. Configure access to DNS entries. You can make the DNS entries publicly available from the entire Internet, or you can restrict access to specific subdomains by using the Domain filters field.

    • To make the entries available without restrictions, leave the Domain filters field empty.
    • To restrict access to a domain and its subdomains, enter example.com Domain filters field.
    • To restrict access to a domain without its subdomains, enter `.example.com into the Domain filters field. Note the leading dot (.) character, that’s required to prevent access from the subdomains.

    Use commas to list multiple subdomains, for example, .a.example.com, .b.example.com. Wildcards are not supported.

  4. Permit deleting DNS entries. By default, the External DNS integrated service only adds the DNS entries of the public services to the DNS registry of your DNS provider. To enable deleting the entries of services that do not exist anymore, select Policy > Synchronize.

  5. Select the type of Kubernetes resources for which the External DNS integrated service should create DNS entries from the Sources field.

    • Service: Externally available services.
    • Ingress: Public ingress endpoints.
    • Istio Gateway:
    • Custom Resource Definition:

  6. Select your cloud DNS provider and set the provider-specific options. Note that you must create some of these options at your cloud DNS provider before you can use them here. For example, a Resource Group in AzureDNS, or a Project in Google Cloud DNS.

  7. Enter a domain name for the cluster into the Cluster > Cluster domain field. (Skip this step if you are using Banzai Cloud DNS.) Note that if you have set the Domain filters field, then the Cluster domain must contain the filtered domain (in case of multiple filtered domains, one of the filtered domains). For example, if you have set my.example.com, then the Cluster domain can be my-cluster-domain.my.example.com.

  8. Click ACTIVATE or SAVE ALL CHANGES to apply your changes. The time it takes for the DNS entry of a service to become accessible depends on your cloud DNS provider.