This training course is designed to help you master the skills of deploying cloud-native applications into Kubernetes.
Observe first hand the end-to-end process of deploying a sample cloud-native application into a Kubernetes cluster. By taking this course you'll not only get to see firsthand the skills required to perform a robust enterprise-grade deployment into Kubernetes, but you'll also be able to apply them yourself as all code and deployment assets are available for you to perform your own deployment:
This training course provides you with in-depth coverage and demonstrations of the following Kubernetes resources:
- Ingress/Ingress Controller
- Persistent Volume
- Persistent Volume Claim
- Headless Service
What you'll learn:
- Learn and understand the basic principles of deploying cloud-native applications into a Kubernetes cluster
- Understand how to set up and configure a locally provisioned Kubernetes cluster using Minikube
- Understand how to work with and configure many of the key Kubernetes cluster resources such as Pods, Deployments, Services, etc.
- And finally, you’ll learn how to manage deployments and Kubernetes cluster resources through their full lifecycle.
This training course provides you with many hands-on demonstrations where you will observe first hand how to
- Create and provision a Minikube Kubernetes cluster
- Install the Cilium CNI plugin
- Build and deploy Docker containers
- Create and configure Kubernetes resources using kubectl
- A basic understanding of containers and containerization
- A basic understanding of software development and the software development life cycle
- A basic understanding of networks and networking
- Anyone interested in learning Kubernetes
- Software Developers interested in Kubernetes containerization, orchestration, and scheduling
- DevOps Practitioners
- [Instructor] Okay, welcome back. In this lecture, I'll quickly demonstrate how DNS works internally within the Cluster. And, as an example, how we can test DNS resolution for the registered services deployed as part of our sample application.
For starters, let's view the system pods within the cluster which are used for DNS. Within the terminal, I'll run the following command: kubectl get pods --namespace= kube-system -l, for label, k8s- app=kube-dns. Now, this results in the following two CoreDNS pods which are used for DNS and have been deployed in the kube-system namespace. Next, I'll launch the following pod for DNS testing purposes which is based on the tutum/dnsutils image. This will give us the ability to run the dig utility which allows us to resolve various DNS names currently registered within our cluster.
Okay, we'll now attempt to resolve the mongo.cloudacademy.svc.cluster.local service name using the dig utility like so. Here, we can see that this results in the answer section containing the following three A records, one for each of the mongo pods where the IP address is the address assigned to the pod. This is designed like so, since the mongo service was deployed as a headless service where the ClusterIP property was set to None. Next, we'll attempt to resolve the api.cloudacademy.svc.cluster.local service record. And here we can see that it resolves differently. In this case, the answer section contains a single A record containing the VIP address, 10.101.151.37 which the cluster registered and assigned to the API service when it was deployed.
And finally, we'll query and resolve the frontend.cloudacademy.svc.cluster.local service record. And again, we can see that the answer section contains a single A record containing the VIP address, 10.107.216.59, which the cluster registered and assigned to the frontend service when it was deployed. Let's now exit this testing pod and run a quick check on the services that are currently deployed within the cloudacademy namespace. I'll run the command: kubectl get svc, for service. And as expected the frontend and api services have the ClusterIP addresses that we've just seen when we performed DNS resolution on the cluster-registered service names. And finally, notice how the ClusterIP is set to None for the mongo service. It is this property that makes it a headless service and changes the behavior of DNS for the equivalent service record as seen earlier.
Okay that concludes this brief DNS review and testing demonstration. The key takeaway from this lecture is knowing how to query and resolve DNS names within the cluster.
Jeremy is a Content Lead Architect and DevOps SME here at Cloud Academy where he specializes in developing DevOps technical training documentation.
He has a strong background in software engineering, and has been coding with various languages, frameworks, and systems for the past 25+ years. In recent times, Jeremy has been focused on DevOps, Cloud (AWS, Azure, GCP), Security, Kubernetes, and Machine Learning.
Jeremy holds professional certifications for AWS, Azure, GCP, Terraform, Kubernetes (CKA, CKAD, CKS).