Shulou(Shulou.com)06/01 Report--

This article introduces you how to automatically configure DNS in ExternalDNS, the content is very detailed, interested friends can refer to, hope to be helpful to you.

ExternalDNS subproject

The ExternalDNS subproject (the incubator process has been deprecated) is sponsored by sig-network and initiated by Tim Hockin to automate the configuration of cloud DNS providers. This is important because it further supports infrastructure automation, allowing users to configure DNS directly while the application is deployed.

The traditional enterprise deployment model usually consists of multiple isolated business units to handle different parts of the deployment process. But Kubernetes with ExternalDNS is different from the traditional enterprise deployment model in that it automates this part of the process. Sometimes it's possible that a piece of software is ready, but it has to wait for another business unit to configure DNS manually. With ExternalDNS, this potential problem is solved.

With ExternalDNS, organizational teams can automate and collaborate for shared responsibility, which avoids manual configuration errors and enables all parties to bring their products to market more effectively.

ExternalDNS configuration and deployment on AKS

I have many years of experience in the .NET field as a software developer. The Microsoft developer community has always had a special place in my heart, and over the past few years I have participated in many Azure users in the Philadelphia area meetup to share how to use Kubernetes on Azure through ACS (Azure Container Service) and AKS (Azure Kubernetes Service). Coincidentally, the users who asked me about ExternalDNS also chose Azure as their IaaS product.

The following is the step-by-step instructions and helper code I prepared to start ExternalDNS on the AKS cluster. This tutorial applies even if you are using a managed Kubernetes on another public cloud.

precondition

Log in to Azure AD and set up a subscription if necessary.

Decide on a few points for attention first

1. Note that the external template files in this document use many optional settings.

2. It is also in the debug-level log, so you can also do your own troubleshooting.

Set up ExternalDNS on Azure AKS or Azure IaaS

1. Create an Azure DNS record

2. Assign DNS according to the needs of your registrant

3. Create a service principal to act on behalf of Kubernetes

4. Create your cloud provider configuration

5. Use the cloud provider configuration to create a Kubernetes key.

6. If you are using Azure IaaS Backed Clusters configured by Rancher, remove ingress controller from the cluster.

Note: if you are a cluster configured with AKS in Rancher, ingress controller will not be provided.

7. Install nginx ingress controller and configure it for ExternalDNS. Create ingress-nginx deployment and services.

8. Because RBAC is enabled by default on Rancher-based Kubernetes clusters, you can create a yaml file named externaldns.yaml from the following script, or use the externaldns-template.yaml file in this repo.

Verification

1. Create a nginx service in ingress in the same way as deploying ExternalDNS

2. Create nginx-ingress controller

3. Wait a few minutes

4. Check to see if any record has been created

5. Check the log

On how to automatically configure DNS in ExternalDNS to share here, I hope the above content can be of some help to you, you can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.