Day 37/40 - Application Failure Troubleshooting From CKA

About this video

### Comprehensive Final Summary The document provides an in-depth exploration of troubleshooting Kubernetes application issues, framed within the context of CK/CKA certification exam preparation. It combines theoretical insights with practical demonstrations using a voting app deployed in a Kubernetes environment. #### **Introduction and Context** The content is part of the CK 2024 series (Video #37) by instructor "BI," focusing on diagnosing and resolving common application issues in Kubernetes. The goal is not only to educate but also to engage the audience by encouraging them to interact with the video (100 likes and 100 comments within 24 hours). #### **Objective** The primary aim is to demonstrate effective troubleshooting techniques for Kubernetes applications, emphasizing key concepts such as service configuration, port mapping, and label/selector alignment. These skills are directly applicable to CK/CKA certification exams. #### **Demo Application Overview** The demo application is a voting app adapted from Docker examples for Kubernetes practice. It consists of: - **Frontend**: A Python-based voting app (port 31000) and a Node.js-based results app (port 31001). - **Backend**: Redis for caching, NetWorker as a message broker, and PostgreSQL for persistent storage. - Communication between components is facilitated through Kubernetes ClusterIP services. #### **Application Architecture** The architecture highlights the separation of concerns: - **Frontend Services**: Voting app and Results app expose user interfaces. - **Backend Services**: Redis, NetWorker, and PostgreSQL handle data processing and storage. - All components communicate via Kubernetes services, which rely on correct labels/selectors and port configurations. #### **Troubleshooting Scenario** The app was initially inaccessible due to two critical issues: 1. **Voting App Issue**: A mismatch in the service selector (`app=vote` vs. `app=votes`). This was resolved by correcting the selector in the YAML configuration. 2. **Results App Issue**: A target port mismatch (service configured for port 8080, while the container exposed port 80). This was fixed by aligning the target port in the service configuration. Additionally, network policy restrictions were identified as a temporary obstacle, where frontend traffic was blocked due to incorrect labels. Adjusting the network policy to match the correct labels resolved this issue. #### **Key Learnings** The troubleshooting process underscored several critical lessons: - **Label/Selector Alignment**: Ensuring that service selectors match pod labels is essential for proper communication. - **Port Configuration**: Service target ports must align with container-exposed ports to avoid connectivity issues. - **Debugging Tools**: Commands like `kubectl get`, `kubectl describe`, and `kubectl edit` are invaluable for inspecting and modifying Kubernetes resources. - **Secrets Management**: Storing sensitive information (e.g., database credentials) as environment variables is discouraged; instead, secrets management tools should be used. #### **Tools and Resources** The instructor provided a GitHub repository for hands-on practice and emphasized the use of `kubectl` commands for resource inspection and modification. #### **Outcome** Through systematic debugging, both the voting and results apps were successfully made accessible. The step-by-step resolution process demonstrated how to identify and fix common Kubernetes issues, reinforcing practical skills for real-world scenarios. #### **Exam Relevance** The content aligns closely with CK/CKA certification objectives, particularly in areas like service configuration, port mapping, and troubleshooting application connectivity. These tasks are frequently tested in the exams, making the material highly relevant for candidates. #### **Additional Insights** Beyond the immediate issues, deeper challenges were explored, such as: - **Database Connectivity**: Problems with updating or displaying voting results were traced to potential connection string errors or backend worker misconfigurations. - **Application Complexity**: Issues related to the Linux image or application-specific execution details were acknowledged but not fully resolved, highlighting the complexity of real-world environments. - **Network Policies**: Temporary restrictions due to incorrect labels were addressed, showcasing the importance of precise network policy definitions. #### **Conclusion** The session concluded by summarizing the troubleshooting journey and emphasizing its educational value. While most issues were resolved, the instructor noted that some complexities (e.g., application-level bugs) might persist in real-world deployments. The process served as a practical example of Kubernetes troubleshooting, preparing learners for both certification exams and production environments. #### **Next Steps** The instructor hinted at covering control plane failures in the next video, indicating a progression to more advanced topics in Kubernetes operations. --- This comprehensive summary encapsulates the key points, technical insights, and educational goals of the document, providing a clear roadmap for understanding and resolving Kubernetes application issues. **Final Answer**: {The document provides a detailed walkthrough of troubleshooting Kubernetes application issues, emphasizing label/selector alignment, port configuration, and the use of `kubectl` commands, while also highlighting the relevance of these skills for CK/CKA certification exams.}

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.