Overview/Description
Kubernetes uses Ingress to expose HTTP and HTTPS routes from outside the cluster to services within the cluster. It also facilitates DNS management by replacing Kube-DNS with CoreDNS, which is a flexible and extensible DNS server that can serve as the Kubernetes cluster DNS. In this course you’ll recognize the role of Ingress in enabling routing, the prerequisites required to create and configure Ingress, the prominent Ingress controllers and when to implement them. You’ll recall the prominent PathTypes and the use of HostName wildcards, the features of CoreDNS and Kube-DNS along with the features of prominent network and CNI plugins. Moving on, you’ll create a simple Ingress resource, update the configuration file to update the Ingress resource backend, configure the Ingress resource to run a web application behind external HTTPS load balancer and install CoreDNS as the default DNS service while installing a fresh Kubernetes cluster. Finally, you’ll upgrade the DNS service of existing Kubernetes clusters to CoreDNS, replace Kube-DNS and enforce network policies in Google Kubernetes Engine. This course is part of a series that aligns with the objectives for the Certified Kubernetes Administrator exam and can be used to prepare for this exam.
Kubernetes Administrator: Ingress and Cluster DNS & CNI Management
discover the key concepts covered in this course
recognize the role of Ingress in enabling routing outside the cluster to services within the cluster and list the prerequisites required to create and configure Ingress
list prominent Ingress controllers and cluster scenarios that are suitable for implementing the right Ingress controller
create a simple ingress resource and update the configuration file to update the ingress resource backend and data to an object storage backend
list the prominent path types and describe the use of Hostname wildcards for creating multiple paths within an Ingress
configure the Ingress resource to run a web application behind an external HTTPS load balancer
describe the features of CoreDNS and the plugins that can be configured in the Corefile configuration
differentiate between CoreDNS and kube-dns and recognize the best cluster DNS service for Kubernetes cluster implementation
install CoreDNS using kubeadm as the default DNS service while installing a fresh Kubernetes cluster
upgrade a DNS service of an existing Kubernetes cluster to CoreDNS and replace kube-dns using the kubeadm upgrade command
list and describe the features of prominent network plugins that can be used in Kubernetes to configure and clean up pod networking
list CNI for Kubernetes features that can be used to build the Kubernetes networking model
configure and enforce network policies in Google Kubernetes Engine