From the course: Debugging Kubernetes
Unlock the full course today
Join today to access over 24,900 courses taught by industry experts.
Debugging Pods running outdated Alpine Linux - Kubernetes Tutorial
From the course: Debugging Kubernetes
Debugging Pods running outdated Alpine Linux
- [Instructor] We're now going to look at DNS problems that come about from running old versions of the Alpine Linux. While you will most likely not encounter this on newer Kubernetes clusters, this still pops up from time to time. Before we log in, let's learn more about how DNS works within Kubernetes. DNS within Kubernetes is not actually built into the cluster. It's an add-on that runs as a pod within the kube system namespace. There are two DNS add-ons that you'll likely work with, Core DNS and kube DNS. You'll usually see kube DNS installed on clusters that are very old. Usually running version 1.18 of Kubernetes or older. Most Kubernetes clusters these days will be using core DNS. Every pod in service within Kubernetes receives a DNS record issued by the clusters DNS add-on. However, you'll quickly notice that the records created for these resources are quite long, so let's break down how their hierarchy works. The last two parts of a record will always be the cluster's root…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
-
-
(Locked)
Conquering DNS misconfigurations within Pods11m 19s
-
(Locked)
Debugging Pods running outdated Alpine Linux5m 29s
-
(Locked)
Conquering CoreDNS and other DNS issues5m 51s
-
(Locked)
Troubleshooting Pod networking7m 50s
-
(Locked)
Troubleshooting NetworkPolicies5m 19s
-
(Locked)
Debugging unreachable Kubernetes Services6m 56s
-
(Locked)
Solving failing Ingress resources10m 24s
-
(Locked)
Troubleshooting Ingress resources with unavailable services2m 37s
-
(Locked)
Debugging aggressive ingress path types4m 32s
-
(Locked)
Challenge: The flaky web app59s
-
(Locked)
Solution: The flaky web app5m 42s
-
(Locked)
-
-