Overview
In this self-paced exercise, you will learn how to configure, deploy and test External DNS within an Amazon EKS cluster and Amazon's Route 53 using add-ons, blueprints and workloads.
When deployed to a Kubernetes cluster External DNS can syncrhonize service and ingress resources with DNS providers allowing you to control DNS records dynamically. This allows external clients to access the services running inside the cluster by resolving the service's or ingress's hostname to the external IP address of the Kubernetes cluster.
What Will You Do by Part¶
| Part | What will you do? |
|---|---|
| 1 | Configure and Provision an Amazon EKS Cluster |
| 2 | Cluster Blueprint with External DNS |
| 3 | Deploy a test Workload to the EKS cluster to utilize External DNS |
| 4 | Deprovision the EKS cluster |
Assumptions¶
- You have access to an Amazon AWS account with privileges to create an IAM Role with the default Full IAM Policy to allow provisioning of resources on your behalf as part of the EKS cluster lifecycle. Steps to create the IAM Role can be found here.
- You have created a Cloud Credential using the ARN of the AWS IAM Role created above in the project "defaultproject"
- You have installed and configured the RCTL CLI so that you can perform the tasks with automation and declarative cluster specification files
- You have created a public or private Route 53 hosted zone