<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Api-Gateway on Anish Bista</title><link>https://anishbista.org/tags/api-gateway/</link><description>Recent content in Api-Gateway on Anish Bista</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 04 Mar 2026 07:44:59 +0000</lastBuildDate><atom:link href="https://anishbista.org/tags/api-gateway/index.xml" rel="self" type="application/rss+xml"/><item><title>How We Migrated from Ingress Nginx to Traefik Ingress Controller</title><link>https://anishbista.org/blog/how-we-migrated-from-ingress-nginx-to-traefik-ingress-controller/</link><pubDate>Wed, 04 Mar 2026 07:44:59 +0000</pubDate><guid>https://anishbista.org/blog/how-we-migrated-from-ingress-nginx-to-traefik-ingress-controller/</guid><description>&lt;blockquote>
&lt;p>Note: This is a hand-written blog. In this blog, I am going to walk you through how we migrated from the ingress-nginx controller to the Traefik ingress controller. Let’s get started, I will try to keep it concise and short.&lt;/p>&lt;/blockquote>
&lt;p>Those who don’t know: &lt;a href="https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/">ingress-nginx is going to retirement&lt;/a> , so I am sure the majority of organizations are affected. Before that, I would like to take a moment to thank all the maintainers and contributors who have made public traffic management great over the last 10 years. Everything eventually reaches its end of life, but with every ending comes new innovation and adoption.&lt;/p></description></item><item><title>Choosing the Best Kubernetes API Gateway: comparing Kong, Envoy, and kgateway</title><link>https://anishbista.org/blog/kubernetes-api-gateway-comparison/</link><pubDate>Thu, 24 Jul 2025 00:00:00 +0000</pubDate><guid>https://anishbista.org/blog/kubernetes-api-gateway-comparison/</guid><description>&lt;h2 id="api-gateways-in-kubernetes-a-quick-glimpse">API Gateways in Kubernetes: A Quick Glimpse&lt;a class="heading-anchor" href="#api-gateways-in-kubernetes-a-quick-glimpse" aria-label="Link to this section">#&lt;/a>&lt;/h2>
&lt;p>Think of your Kubernetes cluster as a busy city. Microservices are like the traffic moving through it. To avoid chaos and ensure everything runs smoothly, you need something to control and guide the flow. That&amp;rsquo;s where an API Gateway comes in. It acts like the city&amp;rsquo;s main traffic controller, managing where each request goes, ensuring security, balancing the load, and keeping the system organized.&lt;/p></description></item></channel></rss>