Skip to content

Configuring domain names

You can customize the domain of an individual Knative Service, or set a global default domain for all Services created on a cluster. The fully qualified domain name for a route by default is {route}.{namespace}.svc.cluster.local.

Configuring a domain for a single Knative Service

If you want to customize the domain of an individual Service, see the documentation about DomainMapping.

Configuring the default domain for all Knative Services on a cluster

You can change the default domain for all Knative Services on a cluster by modifying the config-domain ConfigMap.


  1. Open the config-domain ConfigMap in your default text editor:

    kubectl edit configmap config-domain -n knative-serving
  2. Edit the file to replace svc.cluster.local with the domain you want to use, then remove the _example key and save your changes. In this example, is configured as the domain for all routes:

    apiVersion: v1
    data: ""
    kind: ConfigMap

If you have an existing deployment, Knative reconciles the change made to the ConfigMap, and automatically updates the host name for all of the deployed Services and Routes.

Verification steps

  1. Deploy an app to your cluster.
  2. Retrieve the URL for the Route:

    kubectl get route <route-name> --output jsonpath="{.status.url}"

    Where <route-name> is the name of the Route.

  3. Observe the customized domain that you have configured.

Publish your Domain

To make your domain publicly accessible, you must update your DNS provider to point to the IP address for your service ingress.

  1. Create a wildcard record for the namespace and custom domain to the ingress IP Address, which would enable hostnames for multiple services in the same namespace to work without creating additional DNS entries.

    *                   59     IN     A
  2. Create an A record to point from the fully qualified domain name to the IP address of your Knative gateway. This step needs to be done for each Knative Service or Route created.       59     IN     A
  3. After the domain update has propagated, you can access your app by using the fully qualified domain name of the deployed route.

We use analytics and cookies to understand site traffic. Information about your use of our site is shared with Google for that purpose. Learn more.

× OK