Day 36/40 - Kubernetes Logging and Monitoring | Certified Kubernetes Administrator(CKA) 2024

About this video

### Summary of the Video Content: 1. **Introduction and Context**: - The video is part of the "CKA 2024" series, specifically video number 36. - Focuses on logging and monitoring in Kubernetes as a foundation for upcoming troubleshooting scenarios. 2. **Kubernetes Monitoring Basics**: - Kubernetes does not come with built-in monitoring capabilities. - **Metrics Server** is an add-on installed to expose metrics like CPU and memory utilization. - Metrics Server aggregates data collected by **CAdvisor** (which runs on each node) and sends it to the API server via the Metrics API. 3. **Installation and Troubleshooting of Metrics Server**: - Installed using YAML files or Helm charts. - Common issues include certificate validation errors, which can be resolved by disabling TLS verification via flags in the deployment configuration. - Demonstrates troubleshooting steps using `kubectl describe`, `kubectl logs`, and editing deployments to fix errors. 4. **Logging in Kubernetes**: - Logs are emitted to `stdout` or `stderr` and stored locally on nodes. - For advanced log aggregation and analysis, logs need to be transported to third-party systems like Splunk, ELK, or other observability tools. 5. **CRICTL for Container Runtime Troubleshooting**: - Starting from Kubernetes v1.24, Docker is no longer the default container runtime; **containerd** is used instead. - **CRICTL** is the command-line tool for interacting with container runtimes like containerd. - Commands like `crictl ps`, `crictl images`, and `crictl logs` are used for troubleshooting at the container level. - Useful when `kubectl` commands fail due to API server unavailability or other cluster-level issues. 6. **Debugging Scenarios**: - Demonstrates debugging a non-responsive API server by identifying missing or misconfigured static pod manifests. - Shows how to manually pull images and check container logs using `crictl`. - Highlights the importance of `crictl` for low-level debugging in Kubernetes clusters. 7. **Upcoming Content**: - The next video will focus on **application failure troubleshooting** using a sample three-tier application with multiple services and deployments. - Will cover practical aspects of debugging application failures using the concepts and tools introduced in this video. 8. **Call to Action**: - Encourages viewers to like, comment, and share the video to support the channel. - Mentions a target of 150 likes and 100 comments within 24 hours. ### Key Takeaways: - **Metrics Server** is essential for exposing resource utilization metrics in Kubernetes. - **CRICTL** is a critical tool for troubleshooting container runtime issues, especially in clusters without Docker. - Logs in Kubernetes are stored locally by default and require third-party tools for advanced analytics. - Understanding low-level debugging techniques is crucial for resolving cluster-wide issues, especially when higher-level tools like `kubectl` are unavailable.

Course: Certified Kubernetes Administrator Full Course For beginners | CKA 2025

This playlist contains the complete CKA series for beginners, based on the latest 2025 curriculum. It includes 40+ videos with hands-on demos, assignments, and exam-based scenarios. We will cover everything from the basics to the Advanced, including fundamental concepts such as Docker, containers, Docker storage and networking, DNS, etc.