This is a cache of https://docs.okd.io/4.12/networking/external_dns_operator/nw-creating-dns-records-on-azure.html. It is a snapshot of the page at 2024-11-17T18:29:59.354+0000.
Creating <strong>dns</strong> records on a public zone for Azure - External <strong>dns</strong> Operator | Networking | OKD 4.12
  1. Documentation
×

Creating dns records on Azure

You can create dns records on Azure by using the External dns Operator.

Using the External dns Operator on a {entra-first}-enabled cluster or a cluster that runs in Microsoft Azure Government (MAG) regions is not supported.

Creating dns records on an Azure public dns zone

You can create dns records on a public dns zone for Azure by using the External dns Operator.

Prerequisites

  • You must have administrator privileges.

  • The admin user must have access to the kube-system namespace.

Procedure

  1. Fetch the credentials from the kube-system namespace to use the cloud provider client by running the following command:

    $ CLIENT_ID=$(oc get secrets azure-credentials  -n kube-system  --template={{.data.azure_client_id}} | base64 -d)
$ CLIENT_SECRET=$(oc get secrets azure-credentials  -n kube-system  --template={{.data.azure_client_secret}} | base64 -d)
$ RESOURCE_GROUP=$(oc get secrets azure-credentials  -n kube-system  --template={{.data.azure_resourcegroup}} | base64 -d)
$ SUBSCRIPTION_ID=$(oc get secrets azure-credentials  -n kube-system  --template={{.data.azure_subscription_id}} | base64 -d)
$ TENANT_ID=$(oc get secrets azure-credentials  -n kube-system  --template={{.data.azure_tenant_id}} | base64 -d)

  2. Log in to Azure by running the following command:

    $ az login --service-principal -u "${CLIENT_ID}" -p "${CLIENT_SECRET}" --tenant "${TENANT_ID}"

  3. Get a list of routes by running the following command:

    $ oc get routes --all-namespaces | grep console
    Example output
    openshift-console          console             console-openshift-console.apps.test.azure.example.com                       console             https   reencrypt/Redirect     None
openshift-console          downloads           downloads-openshift-console.apps.test.azure.example.com                     downloads           http    edge/Redirect          None

  4. Get a list of dns zones by running the following command:

    $ az network dns zone list --resource-group "${RESOURCE_GROUP}"

  5. Create a YAML file, for example, external-dns-sample-azure.yaml, that defines the Externaldns object:

    Example external-dns-sample-azure.yaml file
    apiVersion: externaldns.olm.openshift.io/v1beta1
kind: Externaldns
metadata:
  name: sample-azure (1)
spec:
  zones:
  - "/subscriptions/1234567890/resourceGroups/test-azure-xxxxx-rg/providers/Microsoft.Network/dnszones/test.azure.example.com" (2)
  provider:
    type: Azure (3)
  source:
    openshiftRouteOptions: (4)
      routerName: default (5)
    type: OpenShiftRoute (6)
    1 Specifies the External dns name.
    2 Defines the zone ID.
    3 Defines the provider type.
    4 You can define options for the source of dns records.
    5 If the source type is OpenShiftRoute, you can pass the OpenShift Ingress Controller name. External dns selects the canonical hostname of that router as the target while creating CNAME record.
    6 Defines the route resource as the source for the Azure dns records.

  6. Check the dns records created for OKD routes by running the following command:

    $ az network dns record-set list -g "${RESOURCE_GROUP}"  -z test.azure.example.com | grep console

    To create records on private hosted zones on private Azure dns, you need to specify the private zone under the zones field which populates the provider type to azure-private-dns in the Externaldns container arguments.