
Goodbye Ingress, Hello Gateway API: Migrating the Right Way
Hi, dear community of readers, continuing with this blog posts to learn called Learning Kubernetes, this time is the time to learn about how to use the Gateway API. Now all the teams are looking to migrate, so my goal with this post is to help you with a quick start guide to understand and use the Gateway API with the implementation created by NGINX. I know that a lot of people used the NGINX Ingress Controller in their clusters, so makes sense to continue in that way but using the Gateway API. So let's summarize my goals: Start using Gateway API and deprecate your Ingress Controller Setup a functional Gateway API with NGINX for your services So let's start with this content, I know you want to now how to use the Gateway API. What you will learn In this blog post you will learn how to: Install the Gateway API & NGINX Gateway Fabric Create and use Gateways and HTTP Routes Configure Cert-Manager for TLS for your Gateways Requirements A Kubernetes Cluster Access to the cluster using kubec
Continue reading on Dev.to
Opens in a new tab



![[MM’s] Boot Notes — The Day Zero Blueprint — Test Smarter on Day One](/_next/image?url=https%3A%2F%2Fcdn-images-1.medium.com%2Fmax%2F1368%2F1*AvVpFzkFJBm-xns4niPLAA.png&w=1200&q=75)