<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ingress Controller on Support Tools</title><link>https://support.tools/tags/ingress-controller/</link><description>Recent content in Ingress Controller on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://support.tools/tags/ingress-controller/index.xml" rel="self" type="application/rss+xml"/><item><title>Ingress-NGINX Retirement on RKE2: Migrating to Traefik Without Downtime</title><link>https://support.tools/ingress-nginx-retirement-rke2-migrating-traefik-without-downtime/</link><pubDate>Wed, 04 Feb 2026 00:00:00 -0500</pubDate><guid>https://support.tools/ingress-nginx-retirement-rke2-migrating-traefik-without-downtime/</guid><description>&lt;p&gt;The Kubernetes community announced in November 2025 that Ingress-NGINX is being retired. Best-effort maintenance ended in March 2026, and there are no more releases, bug fixes or security patches from upstream. RKE2 shipped ingress-nginx as its default ingress controller until v1.36, so most existing RKE2 clusters still run it.&lt;/p&gt;&#10;&lt;p&gt;This post walks through the practical side of migrating RKE2 clusters from ingress-nginx to Traefik. The emphasis is on running both controllers side-by-side so you can migrate gradually without taking production offline.&lt;/p&gt;</description></item></channel></rss>