Day 48 - Migrate Ingress To Gateway API | Kubernetes hands-on demo

About this video

### Comprehensive Final Summary: Migration of Ingress to Gateway API This document synthesizes the key points from Video 48 of the CK 2025 series, which focuses on migrating an application from Kubernetes Ingress to the Gateway API. The migration process is a critical task for Kubernetes administrators, both from a practical and exam-oriented perspective. Below is a comprehensive summary of the video's content: --- #### **1. Introduction and Prerequisites** - **Context**: This is the 48th video in the CK 2025 series, building on prior knowledge of Kubernetes fundamentals, Ingress (covered in Day 33), and Gateway API (covered in Day 47). - **Migration Importance**: Organizations are transitioning from Ingress to Gateway API due to its advanced features, such as enhanced flexibility, scalability, and better support for modern use cases like HTTP/HTTPS routing, gRPC, and multi-protocol traffic management. - **Prerequisites**: Viewers are expected to have foundational knowledge of Kubernetes, Ingress, and Gateway API concepts to fully grasp the migration process. --- #### **2. Purpose and Importance** - **Relevance**: Migrating from Ingress to Gateway API is not only a practical necessity for modern Kubernetes deployments but also a critical skill for certification exams. - **Educational Value**: While automated tools like `Ingress to Gateway` simplify migration, the video emphasizes manual mapping to provide a deeper understanding of the underlying mechanics. --- #### **3. Migration Process Overview** The migration process involves two approaches: 1. **Automated Tool**: - Tools like `Ingress to Gateway` streamline the migration but lack educational depth. - Suitable for quick migrations but less ideal for learning purposes. 2. **Manual Mapping**: - Preferred method for gaining in-depth knowledge. - Steps include: - Creating listeners and entry points in the Gateway resource. - Adding service details in the Gateway YAML configuration. - Configuring TLS termination and routing rules (HTTP, HTTPS, gRPC). - Applying changes and deleting the old Ingress resource post-migration. --- #### **4. Demo Setup** - **Application Deployment**: - Deployed an application with the hostname `gatewayve.web.gates.local`, locally resolved via `/etc/hosts`. - Created a namespace (`webapp`), deployment (`web-service`), and service exposed on port 80. - Used a ConfigMap to serve a simple HTML page via NGINX. - **TLS Configuration**: - Generated self-signed certificates using OpenSSL. - Created a Kubernetes TLS secret for secure communication. - **Ingress Setup**: - Installed the NGINX Ingress Controller using Helm. - Created an Ingress resource with annotations for rewrite target and SSL redirect. - Verified functionality by accessing the application via `curl`. --- #### **5. Gateway API Setup** - **Initial Configuration**: - Installed Gateway API Custom Resource Definitions (CRDs) and the NGINX Gateway Controller. - Encountered an issue with the STTPS route due to an invalid listener reference. - **Error Resolution**: - Created a `ReferenceGrant` object named "allow-gateway-to-web-app-secret" in the same namespace as the referenced secret. - This grant allowed the NGINX gateway to access the necessary secrets, resolving the error. - **Testing**: - Used `curl` commands to test specific node IPs for both STTP and STTPS routes. - Fixed hostname resolution issues by updating `/etc/hosts` with appropriate mappings. - Successful responses confirmed that requests were routed through the Gateway API instead of the Ingress. --- #### **6. Completion of Migration** - **Final Steps**: - Deleted the original Ingress resource after verifying successful routing via the Gateway API. - Conducted additional tests to confirm that the Gateway API continued to handle requests seamlessly. - **Outcome**: - Demonstrated a complete migration from Ingress to Gateway API. - Highlighted the importance of this migration for both practical applications and exam preparation. --- #### **7. Conclusion and Next Steps** - **Key Takeaways**: - Migration from Ingress to Gateway API is a crucial advancement in Kubernetes networking. - Manual mapping provides valuable insights into the Gateway API's architecture and functionality. - **Encouragement for Practice**: - Viewers are encouraged to practice hands-on by completing related tasks available in the GitHub repository. - Practical experience reinforces theoretical knowledge and prepares users for real-world scenarios and certification exams. --- ### **Final Thoughts** This video effectively bridges the gap between legacy Ingress configurations and the modern Gateway API. By emphasizing manual migration steps, it equips viewers with the skills needed to manage advanced Kubernetes networking requirements. The hands-on demo ensures that learners can confidently apply these concepts in

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.