{"id":47966,"date":"2026-06-24T16:53:52","date_gmt":"2026-06-24T14:53:52","guid":{"rendered":"https:\/\/www.cloudmagazin.com\/?p=47966"},"modified":"2026-06-24T18:03:34","modified_gmt":"2026-06-24T16:03:34","slug":"ingress-nginx-is-discontinued-the-path-to-gateway-api","status":"publish","type":"post","link":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/","title":{"rendered":"Ingress-NGINX is discontinued: The path to Gateway API"},"content":{"rendered":"<div>\n<p style=\"color:#6190a9;font-size:0.9em;margin:0 0 16px;padding:0;\">7 min read<\/p>\n<p style=\"line-height:1.8;\"><strong>On 24 March 2026 the Kubernetes project archived the ingress-nginx repository. Since then no bug fixes or security patches have been issued for the controller that terminates web traffic in most clusters. Anyone still running it is operating their most critical network component without maintenance.<\/strong><\/p>\n<h2>Key Takeaways<\/h2>\n<ul>\n<li><strong>End-of-life is final:<\/strong> Since 24 March 2026 ingress-nginx has been archived-no new features, no bug fixes, no CVE patches. The underlying Kubernetes Ingress API remains, but the popular community controller does not.<\/li>\n<li><strong>The Gateway API is the designated successor:<\/strong> Version 1.5.1 is stable, multiple conformant controllers are available, and the ingress2gateway 1.0 tool automatically converts more than 30 annotations.<\/li>\n<li><strong>The effort lies in edge cases:<\/strong> The standard path is mechanical, yet Auth snippets, session affinity and canary rules must be rebuilt by hand.<\/li>\n<\/ul>\n<p style=\"font-size:0.88em;color:#666;margin:20px 0 32px 0;border-top:1px solid #e5e5e5;border-bottom:1px solid #e5e5e5;padding:10px 0;\"><span style=\"color:#004a59;font-weight:700;text-transform:uppercase;font-size:0.72em;letter-spacing:0.14em;margin-right:14px;\">Related:<\/span><a href=\"https:\/\/www.cloudmagazin.com\/en\/2026\/04\/21\/kubernetes-1-36-arrives-user-namespaces-stable-ipvs-gone\/\" style=\"color:#333;text-decoration:underline;\">Kubernetes rewrites the rules: IPVS and Ingress-NGINX out<\/a>&nbsp;&nbsp;<span style=\"color:#ccc;\">\/<\/span>&nbsp;&nbsp;<a href=\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/10\/kubernetes-as-the-default-os-for-ai-cluster-as-a-compliance-issue\/\" style=\"color:#333;text-decoration:underline;\">Kubernetes as default AI OS: clusters as a compliance question<\/a><\/p>\n<h2 style=\"margin-top:64px;margin-bottom:20px;padding-top:16px;\">Why the clock has run out<\/h2>\n<p style=\"line-height:1.8;\">The announcement arrived in November 2025 from the Kubernetes SIG Network and the Security Response Committee; a follow-up statement in January 2026 underlined the gravity. By March 2026 the best-effort maintenance ended and the GitHub repository was archived on 24 March. There is no long grace period to sit it out-the support is over.<\/p>\n<p style=\"line-height:1.8;\">The real issue is not missing functionality but security exposure. New vulnerabilities continue to surface; the NGINX Rift heap-overflow disclosed in May 2026 affected archived builds as well. No patches will ever arrive. Running end-of-life software directly in the Layer-7 data path triggers automatic findings in audits under SOC 2, PCI-DSS or ISO 27001. Anyone needing compliance evidence now has an open red flag.<\/p>\n<p style=\"line-height:1.8;\">One clarification is vital because it is often muddled: the Kubernetes Ingress API itself is not disappearing. It remains generally available but frozen. Active development has fully migrated to the Gateway API. The concrete controller ingress-nginx is affected, not the concept of Ingress per se.<\/p>\n<p style=\"line-height:1.8;\"><strong>What is the Gateway API?<\/strong> The Gateway API is a Kubernetes standard for Layer-7 routing that replaces the older Ingress API. It cleanly separates roles between infrastructure and application teams, describes routes in far more expressive terms and is designed from the ground up for multi-tenancy inside the same cluster. Since 2026 it has been the official path for new network code.<\/p>\n<div class=\"evm-stat-highlight\" style=\"text-align:center;background:#004a59;border-radius:12px;padding:40px 24px;margin:32px 0;\">\n<div style=\"font-size:3.4em;font-weight:800;color:#0bb7fd;letter-spacing:-0.03em;line-height:1;\">0<\/div>\n<div style=\"font-size:1em;color:rgba(255,255,255,0.9);margin-top:12px;max-width:520px;margin-left:auto;margin-right:auto;line-height:1.5;\">Security patches for ingress-nginx have been issued since the end-of-life date on 24 March 2026. Every new L7-path vulnerability remains permanently unpatched.<\/div>\n<div style=\"font-size:0.78em;color:rgba(255,255,255,0.7);margin-top:12px;\">Source: Kubernetes SIG Network, Security Response Committee<\/div>\n<\/div>\n<h2 style=\"margin-top:64px;margin-bottom:20px;padding-top:16px;\">Three Paths, One Main Route<\/h2>\n<p style=\"line-height:1.8;\">Every team still running on ingress-nginx faces three choices. The differences lie less in the technology itself than in the timeline and how much technical debt you\u2019re willing to carry forward.<\/p>\n<p style=\"line-height:1.8;\">The first path is migrating to the Gateway API. This is the direction the ecosystem is heading, and for most clusters it\u2019s the cleanest cut. The second path is switching to a different Ingress Controller-Traefik, HAProxy, Envoy Gateway, or the commercial F5-NGINX variant. This keeps the familiar Ingress API alive but merely postpones the strategic decision. The third path is commercial security support for the archived version, offered by third-party vendors. That buys time for an orderly migration but doesn\u2019t solve the underlying problem.<\/p>\n<p style=\"line-height:1.8;\">For new platforms and anyone already planning modernization, the choice falls on the Gateway API. The comparison below explains why-and where the honest trade-offs lie.<\/p>\n<div class=\"evm-pros-cons\" style=\"display:grid;grid-template-columns:repeat(auto-fit,minmax(280px,1fr));gap:16px;margin:28px 0;\">\n<div style=\"background:#fafafa;border-top:3px solid #2d7a3e;padding:18px 20px;border-radius:4px;\">\n<p style=\"margin:0 0 10px 0;font-size:0.78em;font-weight:700;text-transform:uppercase;letter-spacing:0.12em;color:#2d7a3e;\">Why Gateway API wins<\/p>\n<ul style=\"margin:0;padding-left:18px;color:#333;line-height:1.55;font-size:0.95em;\">\n<li style=\"margin-bottom:6px;\">Official development track-all new features land here<\/li>\n<li style=\"margin-bottom:6px;\">Clean separation of concerns between infrastructure and application<\/li>\n<li style=\"margin-bottom:6px;\">More expressive routes without annotation sprawl<\/li>\n<li>Portable across conformant controllers<\/li>\n<\/ul><\/div>\n<div style=\"background:#fafafa;border-top:3px solid #c0392b;padding:18px 20px;border-radius:4px;\">\n<p style=\"margin:0 0 10px 0;font-size:0.78em;font-weight:700;text-transform:uppercase;letter-spacing:0.12em;color:#c0392b;\">Where it still stumbles<\/p>\n<ul style=\"margin:0;padding-left:18px;color:#333;line-height:1.55;font-size:0.95em;\">\n<li style=\"margin-bottom:6px;\">Custom annotations don\u2019t map 1:1<\/li>\n<li style=\"margin-bottom:6px;\">The team must learn a second resource model<\/li>\n<li style=\"margin-bottom:6px;\">Observability and dashboards need new wiring<\/li>\n<li>The controller maturity varies by feature<\/li>\n<\/ul><\/div>\n<\/div>\n<h2 style=\"margin-top:64px;margin-bottom:20px;padding-top:16px;\">The Migration in Five Steps<\/h2>\n<p style=\"line-height:1.8;\">The good news first: for the standard case, the move is now mechanical. Since 20 March 2026, ingress2gateway has reached version 1.0-a stable tool from the SIG Network that translates existing Ingress definitions, including more than 30 common annotations, into Gateway and HTTPRoute objects. Follow the sequence below and you\u2019ll keep downtime at zero.<\/p>\n<div class=\"evm-timeline\" style=\"margin:28px 0;border:1px solid #e5e5e5;border-radius:6px;overflow:hidden;\">\n<div style=\"background:#004a59;color:#fff;padding:12px 18px;font-size:0.78em;font-weight:700;text-transform:uppercase;letter-spacing:0.14em;\">Zero-downtime migration path<\/div>\n<div style=\"padding:8px 0;\">\n<div style=\"display:flex;gap:18px;padding:12px 20px;border-bottom:1px solid #f0f0f0;\">\n<div style=\"min-width:90px;font-weight:700;color:#0bb7fd;\">Step 1<\/div>\n<div style=\"color:#333;line-height:1.6;\"><strong>Inventory your estate.<\/strong> List every Ingress object and its annotations. The number of routes doesn\u2019t drive the effort; the list of edge cases does.<\/div>\n<\/p><\/div>\n<div style=\"display:flex;gap:18px;padding:12px 20px;border-bottom:1px solid #f0f0f0;\">\n<div style=\"min-width:90px;font-weight:700;color:#0bb7fd;\">Step 2<\/div>\n<div style=\"color:#333;line-height:1.6;\"><strong>Install the CRDs.<\/strong> Roll out the Gateway-API resources from the standard channel, version 1.5.1. Traffic remains untouched; you\u2019re only laying down the new vocabulary.<\/div>\n<\/p><\/div>\n<div style=\"display:flex;gap:18px;padding:12px 20px;border-bottom:1px solid #f0f0f0;\">\n<div style=\"min-width:90px;font-weight:700;color:#0bb7fd;\">Step 3<\/div>\n<div style=\"color:#333;line-height:1.6;\"><strong>Pick and deploy a controller.<\/strong> Run a conformant controller such as Envoy Gateway in parallel with your existing ingress-nginx. Two data paths side-by-side, still no cut-over.<\/div>\n<\/p><\/div>\n<div style=\"display:flex;gap:18px;padding:12px 20px;border-bottom:1px solid #f0f0f0;\">\n<div style=\"min-width:90px;font-weight:700;color:#0bb7fd;\">Step 4<\/div>\n<div style=\"color:#333;line-height:1.6;\"><strong>Convert with ingress2gateway.<\/strong> Feed the tool your Ingress YAML; it emits Gateway and HTTPRoute objects. Inspect the output-don\u2019t apply blindly, especially when you\u2019ve added custom annotations.<\/div>\n<\/p><\/div>\n<div style=\"display:flex;gap:18px;padding:12px 20px;\">\n<div style=\"min-width:90px;font-weight:700;color:#0bb7fd;\">Step 5<\/div>\n<div style=\"color:#333;line-height:1.6;\"><strong>Shift traffic incrementally.<\/strong> Move route by route or via weighted DNS to the new path, watch metrics, then decommission the old controller. Migration is complete only when nothing still points to ingress-nginx.<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/div>\n<h2 style=\"margin-top:64px;margin-bottom:20px;padding-top:16px;\">Where the details get sticky<\/h2>\n<p style=\"line-height:1.8;\">The five steps sound smooth, and they are-for a platform that has kept its Ingress rules clean and generic. Friction appears where teams have spent years collecting annotations that are specific to ingress-nginx. No tool translates those fully.<\/p>\n<p style=\"line-height:1.8;\">The most common tripwires are easy to spot in advance. Auth snippets and external authentication must be rebuilt around the Gateway API\u2019s filter model. Sticky sessions and session affinity are modeled differently than the old cookie annotations. Canary deployments that once ran via annotation now live in weighted HTTPRoute rules. Anything tied to custom snippets or embedded NGINX config simply has no direct counterpart in the new world-this is intentional, not a shortcoming of the Gateway API.<\/p>\n<p style=\"line-height:1.8;\">Yet there\u2019s upside that only becomes visible once you\u2019re live. The Gateway API\u2019s clear separation of roles lets the platform team own the gateway while application teams create their own routes without touching shared infrastructure. If you\u2019re already migrating, you can use the exercise to finally carve out those responsibilities cleanly. What feels like a forced compliance task can turn into platform hygiene you\u2019d never have prioritised otherwise.<\/p>\n<h2 style=\"padding-top:64px;margin-bottom:20px;\">Frequently Asked Questions<\/h2>\n<details>\n<summary><strong>Do I need to migrate immediately, or will ingress-nginx just keep running?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">Technically, the last version continues to run and won\u2019t vanish from the cluster. However, it will no longer receive security updates. Any new vulnerabilities will remain unpatched, and in compliance audits, end-of-life software in the data path counts as a finding. The right time to migrate is therefore more like yesterday than later.<\/p>\n<\/details>\n<details>\n<summary><strong>Does the Kubernetes Ingress API itself remain available?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">Yes. The Ingress API remains generally available, though it is now frozen and will not gain new features. Only the community controller ingress-nginx has been deprecated. If you want to stay with the Ingress API, you can switch to another controller such as Traefik or HAProxy.<\/p>\n<\/details>\n<details>\n<summary><strong>What exactly does the ingress2gateway tool do?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">It reads existing Ingress definitions and generates corresponding Gateway and HTTPRoute objects. Version 1.0 supports more than 30 common ingress-nginx annotations. For standard cases the conversion is mechanical, but you should still review the generated output before applying it.<\/p>\n<\/details>\n<details>\n<summary><strong>Which controllers are alternatives to the Gateway API?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">If you don\u2019t want to switch to the new model, you can replace ingress-nginx with Traefik, HAProxy, Envoy Gateway, or the commercial F5 NGINX variant. These keep the familiar Ingress API, but the fundamental decision is merely postponed rather than resolved.<\/p>\n<\/details>\n<details>\n<summary><strong>How can I keep downtime at zero when switching?<\/strong><\/summary>\n<p style=\"margin:8px 0 4px 24px;color:#555;line-height:1.6;\">Run the new controller in parallel alongside ingress-nginx, shift traffic route-by-route or via weighted DNS, and monitor the process. Only decommission ingress-nginx once no traffic remains on the old path.<\/p>\n<\/details>\n<div style=\"margin:40px 0 24px 0;\">\n<p style=\"margin:0 0 12px 0;font-size:0.78em;font-weight:700;text-transform:uppercase;letter-spacing:0.18em;color:#666;\">More from the MBF Media Network<\/p>\n<div style=\"padding:14px 18px;border-left:3px solid #202528;background:#fafafa;margin-bottom:6px;\">\n<div style=\"font-size:0.7em;font-weight:700;color:#202528;text-transform:uppercase;letter-spacing:0.12em;margin-bottom:4px;\">mybusinessfuture<\/div>\n<p> <a href=\"https:\/\/mybusinessfuture.com\/der-ki-engpass-im-mittelstand-sitzt-in-den-altsystemen\/\" style=\"font-weight:600;line-height:1.4;color:#1a1a1a;text-decoration:none;\">AI in SMEs: The Bottleneck Lies in Legacy Systems<\/a> <\/div>\n<div style=\"padding:14px 18px;border-left:3px solid #d65663;background:#fafafa;margin-bottom:6px;\">\n<div style=\"font-size:0.7em;font-weight:700;color:#d65663;text-transform:uppercase;letter-spacing:0.12em;margin-bottom:4px;\">digital-chiefs<\/div>\n<p> <a href=\"https:\/\/www.digital-chiefs.de\/geopolitik-datacenter-roadmap-lieferketten-capex-cio\/\" style=\"font-weight:600;line-height:1.4;color:#1a1a1a;text-decoration:none;\">Geopolitics Meets the Datacentre Roadmap: What CIOs Must Secure Now<\/a> <\/div>\n<div style=\"padding:14px 18px;border-left:3px solid #69d8ed;background:#fafafa;\">\n<div style=\"font-size:0.7em;font-weight:700;color:#69d8ed;text-transform:uppercase;letter-spacing:0.12em;margin-bottom:4px;\">securitytoday<\/div>\n<p> <a href=\"https:\/\/www.securitytoday.de\/2026\/06\/08\/api-security-der-blinde-fleck-hinter-jeder-integration\/\" style=\"font-weight:600;line-height:1.4;color:#1a1a1a;text-decoration:none;\">API Security: The Blind Spot Behind Every Integration<\/a> <\/div>\n<\/p><\/div>\n<p style=\"text-align:right;color:#868e96;font-size:0.85em;margin-top:48px;\"><em>Source of title image: Unsplash \/ Growtika<\/em><\/p>\n<p style=\"text-align:right;color:#868e96;font-size:0.85em;margin-top:48px;\"><em>Image source: Unsplash \/ Growtika<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"Kubernetes archived ingress-nginx in March 2026: no more security patches. Here&#8217;s how to smoothly migrate to the Gateway API without downtime.","protected":false},"author":31,"featured_media":47963,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_yoast_wpseo_focuskw":"Gateway API Migration","_yoast_wpseo_title":"Ingress-NGINX is discontinued: The path to Gateway API","_yoast_wpseo_metadesc":"**\"Kubernetes drops ingress-nginx in March 2026 - no security updates! Migrate smoothly to Gateway API with zero downtime. Act now!\"** (149 chars)","_yoast_wpseo_meta-robots-noindex":"","_yoast_wpseo_meta-robots-nofollow":"","_yoast_wpseo_meta-robots-adv":"","_yoast_wpseo_canonical":"","_yoast_wpseo_opengraph-title":"","_yoast_wpseo_opengraph-description":"","_yoast_wpseo_opengraph-image":"","_yoast_wpseo_opengraph-image-id":0,"_yoast_wpseo_twitter-title":"","_yoast_wpseo_twitter-description":"","_yoast_wpseo_twitter-image":"","_yoast_wpseo_twitter-image-id":0,"ngg_post_thumbnail":0,"pre_headline":"","bildquelle":"","teasertext":"","language":"de","_evm_translation_lang":"","featured_post":0,"featured_post_sortierung":0,"_wp_old_slug":[],"footnotes":""},"categories":[11],"tags":[],"industry":[],"class_list":["post-47966","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ratgeber"],"evm_reading_time_minutes":8,"wpml_language":"en","wpml_translation_of":47962,"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.1.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Ingress-NGINX is discontinued: The path to Gateway API<\/title>\n<meta name=\"description\" content=\"**&quot;Kubernetes drops ingress-nginx in March 2026 - no security updates! Migrate smoothly to Gateway API with zero downtime. Act now!&quot;** (149 chars)\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Ingress-NGINX is discontinued: The path to Gateway API\" \/>\n<meta property=\"og:description\" content=\"**&quot;Kubernetes drops ingress-nginx in March 2026 - no security updates! Migrate smoothly to Gateway API with zero downtime. Act now!&quot;** (149 chars)\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/\" \/>\n<meta property=\"og:site_name\" content=\"cloudmagazin\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/cloudmagazincom\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-24T14:53:52+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-24T16:03:34+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/06\/ingress-nginx-eol-gateway-api-migration-cover-hero.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"576\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Alec Chizhik\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@cloudmagazin\" \/>\n<meta name=\"twitter:site\" content=\"@cloudmagazin\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Alec Chizhik\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"NewsArticle\",\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/\"},\"author\":{\"name\":\"Alec Chizhik\",\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/person\/ce38baaa19a580268aedce096597eb3c\"},\"headline\":\"Ingress-NGINX is discontinued: The path to Gateway API\",\"datePublished\":\"2026-06-24T14:53:52+00:00\",\"dateModified\":\"2026-06-24T16:03:34+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/\"},\"wordCount\":1314,\"publisher\":{\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/06\/ingress-nginx-eol-gateway-api-migration-cover-hero.jpg\",\"articleSection\":[\"Guides\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/\",\"url\":\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/\",\"name\":\"Ingress-NGINX is discontinued: The path to Gateway API\",\"isPartOf\":{\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/06\/ingress-nginx-eol-gateway-api-migration-cover-hero.jpg\",\"datePublished\":\"2026-06-24T14:53:52+00:00\",\"dateModified\":\"2026-06-24T16:03:34+00:00\",\"description\":\"**\\\"Kubernetes drops ingress-nginx in March 2026 - no security updates! Migrate smoothly to Gateway API with zero downtime. Act now!\\\"** (149 chars)\",\"breadcrumb\":{\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#primaryimage\",\"url\":\"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/06\/ingress-nginx-eol-gateway-api-migration-cover-hero.jpg\",\"contentUrl\":\"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/06\/ingress-nginx-eol-gateway-api-migration-cover-hero.jpg\",\"width\":1024,\"height\":576,\"caption\":\"Cloud-Computing-Konzept: Weg zur Gateway API nach Ingress-NGINX-Abk\u00fcndigung. (Foto: Growtika \/ Unsplash)\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.cloudmagazin.com\/en\/home\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Ingress-NGINX is discontinued: The path to Gateway API\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/#website\",\"url\":\"https:\/\/www.cloudmagazin.com\/en\/\",\"name\":\"cloudmagazin\",\"description\":\"Inspiration f\u00fcr Businessentscheider\",\"publisher\":{\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.cloudmagazin.com\/en\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/#organization\",\"name\":\"cloudmagazin\",\"url\":\"https:\/\/www.cloudmagazin.com\/en\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2020\/04\/cloudmagazin-logo-klein_menu.jpg\",\"contentUrl\":\"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2020\/04\/cloudmagazin-logo-klein_menu.jpg\",\"width\":150,\"height\":150,\"caption\":\"cloudmagazin\"},\"image\":{\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/cloudmagazincom\/\",\"https:\/\/x.com\/cloudmagazin\",\"https:\/\/www.linkedin.com\/showcase\/cloudmagazin\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/person\/ce38baaa19a580268aedce096597eb3c\",\"name\":\"Alec Chizhik\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/03\/alec-chizhik.jpg\",\"contentUrl\":\"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/03\/alec-chizhik.jpg\",\"caption\":\"Alec Chizhik\"},\"description\":\"Alec is the Chief Digital Officer at Evernine and writes about cloud architectures, IT security, and digital operations practices.\",\"sameAs\":[\"https:\/\/www.linkedin.com\/in\/alecchizhik\/\"],\"url\":\"https:\/\/www.cloudmagazin.com\/en\/author\/alec\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Ingress-NGINX is discontinued: The path to Gateway API","description":"**\"Kubernetes drops ingress-nginx in March 2026 - no security updates! Migrate smoothly to Gateway API with zero downtime. Act now!\"** (149 chars)","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/","og_locale":"en_US","og_type":"article","og_title":"Ingress-NGINX is discontinued: The path to Gateway API","og_description":"**\"Kubernetes drops ingress-nginx in March 2026 - no security updates! Migrate smoothly to Gateway API with zero downtime. Act now!\"** (149 chars)","og_url":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/","og_site_name":"cloudmagazin","article_publisher":"https:\/\/www.facebook.com\/cloudmagazincom\/","article_published_time":"2026-06-24T14:53:52+00:00","article_modified_time":"2026-06-24T16:03:34+00:00","og_image":[{"width":1024,"height":576,"url":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/06\/ingress-nginx-eol-gateway-api-migration-cover-hero.jpg","type":"image\/jpeg"}],"author":"Alec Chizhik","twitter_card":"summary_large_image","twitter_creator":"@cloudmagazin","twitter_site":"@cloudmagazin","twitter_misc":{"Written by":"Alec Chizhik","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"NewsArticle","@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#article","isPartOf":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/"},"author":{"name":"Alec Chizhik","@id":"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/person\/ce38baaa19a580268aedce096597eb3c"},"headline":"Ingress-NGINX is discontinued: The path to Gateway API","datePublished":"2026-06-24T14:53:52+00:00","dateModified":"2026-06-24T16:03:34+00:00","mainEntityOfPage":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/"},"wordCount":1314,"publisher":{"@id":"https:\/\/www.cloudmagazin.com\/en\/#organization"},"image":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/06\/ingress-nginx-eol-gateway-api-migration-cover-hero.jpg","articleSection":["Guides"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/","url":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/","name":"Ingress-NGINX is discontinued: The path to Gateway API","isPartOf":{"@id":"https:\/\/www.cloudmagazin.com\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#primaryimage"},"image":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/06\/ingress-nginx-eol-gateway-api-migration-cover-hero.jpg","datePublished":"2026-06-24T14:53:52+00:00","dateModified":"2026-06-24T16:03:34+00:00","description":"**\"Kubernetes drops ingress-nginx in March 2026 - no security updates! Migrate smoothly to Gateway API with zero downtime. Act now!\"** (149 chars)","breadcrumb":{"@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#primaryimage","url":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/06\/ingress-nginx-eol-gateway-api-migration-cover-hero.jpg","contentUrl":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/06\/ingress-nginx-eol-gateway-api-migration-cover-hero.jpg","width":1024,"height":576,"caption":"Cloud-Computing-Konzept: Weg zur Gateway API nach Ingress-NGINX-Abk\u00fcndigung. (Foto: Growtika \/ Unsplash)"},{"@type":"BreadcrumbList","@id":"https:\/\/www.cloudmagazin.com\/en\/2026\/06\/24\/ingress-nginx-is-discontinued-the-path-to-gateway-api\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cloudmagazin.com\/en\/home\/"},{"@type":"ListItem","position":2,"name":"Ingress-NGINX is discontinued: The path to Gateway API"}]},{"@type":"WebSite","@id":"https:\/\/www.cloudmagazin.com\/en\/#website","url":"https:\/\/www.cloudmagazin.com\/en\/","name":"cloudmagazin","description":"Inspiration f\u00fcr Businessentscheider","publisher":{"@id":"https:\/\/www.cloudmagazin.com\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.cloudmagazin.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.cloudmagazin.com\/en\/#organization","name":"cloudmagazin","url":"https:\/\/www.cloudmagazin.com\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/logo\/image\/","url":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2020\/04\/cloudmagazin-logo-klein_menu.jpg","contentUrl":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2020\/04\/cloudmagazin-logo-klein_menu.jpg","width":150,"height":150,"caption":"cloudmagazin"},"image":{"@id":"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/cloudmagazincom\/","https:\/\/x.com\/cloudmagazin","https:\/\/www.linkedin.com\/showcase\/cloudmagazin\/"]},{"@type":"Person","@id":"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/person\/ce38baaa19a580268aedce096597eb3c","name":"Alec Chizhik","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cloudmagazin.com\/en\/#\/schema\/person\/image\/","url":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/03\/alec-chizhik.jpg","contentUrl":"https:\/\/www.cloudmagazin.com\/wp-content\/uploads\/2026\/03\/alec-chizhik.jpg","caption":"Alec Chizhik"},"description":"Alec is the Chief Digital Officer at Evernine and writes about cloud architectures, IT security, and digital operations practices.","sameAs":["https:\/\/www.linkedin.com\/in\/alecchizhik\/"],"url":"https:\/\/www.cloudmagazin.com\/en\/author\/alec\/"}]}},"_links":{"self":[{"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/posts\/47966","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/users\/31"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/comments?post=47966"}],"version-history":[{"count":1,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/posts\/47966\/revisions"}],"predecessor-version":[{"id":47967,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/posts\/47966\/revisions\/47967"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/media\/47963"}],"wp:attachment":[{"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/media?parent=47966"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/categories?post=47966"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/tags?post=47966"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.cloudmagazin.com\/en\/wp-json\/wp\/v2\/industry?post=47966"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}