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

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

Creating dns records on an public dns zone for Azure by using Red Hat External dns Operator

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

Procedure
  1. Check the user. The user must have access to the kube-system namespace. If you don’t have the credentials, as you can fetch the credentials from the kube-system namespace to use the cloud provider client:

    $ oc whoami
    Example output
    system:admin
  2. Fetch the values from azure-credentials secret present in kube-system namespace.

    $ 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)
  3. Login to azure with base64 decoded values:

    $ az login --service-principal -u "${CLIENT_ID}" -p "${CLIENT_SECRET}" --tenant "${TENANT_ID}"
  4. Get the routes to check the domain:

    $ 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
  5. Get the list of dns zones to find the one which corresponds to the previously found route’s domain:

    $ az network dns zone list --resource-group "${RESOURCE_GROUP}"
  6. Create Externaldns resource for route source:

    apiVersion: externaldns.olm.openshift.io/v1alpha1
    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)
    EOF
    1 Specifies the name of External dns CR.
    2 Define the zone ID.
    3 Defines the Azure dns provider.
    4 You can define options for the source of dns records.
    5 If the source is OpenShiftRoute then 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 OpenShift route resource as the source for the dns records which gets created in the previously specified dns provider.
  7. Check the records created for OCP routes using 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 zones which populates the provider type to azure-private-dns in the Externaldns container args.