{"slug": "kubernetes-gateway-api", "name": "Kubernetes Gateway API", "category": "networking", "category_name": "Networking and VPN", "description": "", "recommenders": 4, "commenters": 4, "warners": 0, "score": 3.288, "rising": -1.31, "first": "2025-11-13", "latest": "2026-04-23", "why": "the Gateway API supercedes Ingress and provides much more functionality without much more complexity", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 4, "neutral": 0, "compare": 0, "warn": 0}, "spark": [3, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "the Gateway API supercedes Ingress and provides much more functionality without much more complexity", "kind": "", "icon": true, "domain": "k8s.io", "github_repo": null, "official_url": "https://gateway-api.sigs.k8s.io", "pricing": "", "aliases": ["Kubernetes Gateway API", "Gateway API"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 766121697, "item_id": 47882606, "url": "https://news.ycombinator.com/item?id=47882606", "by": "KronisLV", "date": "2026-04-23", "version": null, "stance": "recommend", "quote": "nowadays you're supposed to use Gateway instead", "excerpt": "> IS that a thing still? Yeah, using it in production. If you don't need the equivalent of CRDs or other complex stuff like network meshes, it's stable and pretty okay! My ingress is just a regular web server image, for example. > It comes for \"free\" with k8s with ingress controllers. Ingress Controllers will keep working but the API is frozen, I think nowadays you're supposed to use Gateway instead: https://gateway-", "context": "", "use_case": "", "switched_from": "", "story": "I Am Building a Cloud"}, {"id": 734808961, "item_id": 45925560, "url": "https://news.ycombinator.com/item?id=45925560", "by": "szszrk", "date": "2025-11-14", "version": null, "stance": "recommend", "quote": "it's clear that Gateway API is something to get interested in.", "excerpt": "It's a much less of a deal than it seems. Yeah, it is a popular project that has been around for a while, but this is just another day at work. Things evolve, there are migration paths no matter if you want to stay with ingresses or move on... Kubernetes is promoting Gateway API for a while now. It's in GA for 2 years already (while Ingress was in GA quite late, 2020/K8s 1.19?). Sun-setting ingress-nginx was not exac", "context": "", "use_case": "", "switched_from": "", "story": "Kubernetes Ingress Nginx is retiring"}, {"id": 734799249, "item_id": 45924953, "url": "https://news.ycombinator.com/item?id=45924953", "by": "PhilippGille", "date": "2025-11-14", "version": null, "stance": "recommend", "quote": "Literally the second link in the article is \"migrating to API Gateway\"", "excerpt": "Literally the second link in the article is \"migrating to API Gateway\" and points to https://gateway-api.sigs.k8s.io/guides/ Which has this section about migration: https://gateway-api.sigs.k8s.io/guides/migrating-from-ingress/ And this list of Gateway controllers: https://gateway-api.sigs.k8s.io/implementations/", "context": "", "use_case": "", "switched_from": "", "story": "Kubernetes Ingress Nginx is retiring"}, {"id": 734791200, "item_id": 45924450, "url": "https://news.ycombinator.com/item?id=45924450", "by": "nunez", "date": "2025-11-13", "version": null, "stance": "recommend", "quote": "the Gateway API supercedes Ingress and provides much more functionality without much more complexity", "excerpt": "/r/kubernetes had this announcement up about five mins after it dropped at Kubecon. It's a huge deal. So many tutorials and products used ingress-nginx for basic ingress, so them throwing in the towel (but not really) is big news. That said, (a) the Gateway API supercedes Ingress and provides much more functionality without much more complexity, and (b) NGINX and HAproxy have Gateway controllers. To generally answer ", "context": "", "use_case": "", "switched_from": "", "story": "Kubernetes Ingress Nginx is retiring"}]}], "caveats": [], "who": [], "tags": [], "use_cases": [], "compared": [], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=45921431", "title": "Kubernetes Ingress Nginx is retiring", "mentions": 3}, {"url": "https://news.ycombinator.com/item?id=47872324", "title": "I Am Building a Cloud", "mentions": 1}], "sentiment_by_month": {"2025-11": {"recommend": 3}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 766121697, "item_id": 47882606, "url": "https://news.ycombinator.com/item?id=47882606", "by": "KronisLV", "date": "2026-04-23", "version": null, "stance": "recommend", "quote": "nowadays you're supposed to use Gateway instead", "excerpt": "> IS that a thing still? Yeah, using it in production. If you don't need the equivalent of CRDs or other complex stuff like network meshes, it's stable and pretty okay! My ingress is just a regular web server image, for example. > It comes for \"free\" with k8s with ingress controllers. Ingress Controllers will keep working but the API is frozen, I think nowadays you're supposed to use Gateway instead: https://gateway-", "context": "", "use_case": "", "switched_from": "", "story": "I Am Building a Cloud"}, {"id": 734808961, "item_id": 45925560, "url": "https://news.ycombinator.com/item?id=45925560", "by": "szszrk", "date": "2025-11-14", "version": null, "stance": "recommend", "quote": "it's clear that Gateway API is something to get interested in.", "excerpt": "It's a much less of a deal than it seems. Yeah, it is a popular project that has been around for a while, but this is just another day at work. Things evolve, there are migration paths no matter if you want to stay with ingresses or move on... Kubernetes is promoting Gateway API for a while now. It's in GA for 2 years already (while Ingress was in GA quite late, 2020/K8s 1.19?). Sun-setting ingress-nginx was not exac", "context": "", "use_case": "", "switched_from": "", "story": "Kubernetes Ingress Nginx is retiring"}, {"id": 734799249, "item_id": 45924953, "url": "https://news.ycombinator.com/item?id=45924953", "by": "PhilippGille", "date": "2025-11-14", "version": null, "stance": "recommend", "quote": "Literally the second link in the article is \"migrating to API Gateway\"", "excerpt": "Literally the second link in the article is \"migrating to API Gateway\" and points to https://gateway-api.sigs.k8s.io/guides/ Which has this section about migration: https://gateway-api.sigs.k8s.io/guides/migrating-from-ingress/ And this list of Gateway controllers: https://gateway-api.sigs.k8s.io/implementations/", "context": "", "use_case": "", "switched_from": "", "story": "Kubernetes Ingress Nginx is retiring"}, {"id": 734791200, "item_id": 45924450, "url": "https://news.ycombinator.com/item?id=45924450", "by": "nunez", "date": "2025-11-13", "version": null, "stance": "recommend", "quote": "the Gateway API supercedes Ingress and provides much more functionality without much more complexity", "excerpt": "/r/kubernetes had this announcement up about five mins after it dropped at Kubecon. It's a huge deal. So many tutorials and products used ingress-nginx for basic ingress, so them throwing in the towel (but not really) is big news. That said, (a) the Gateway API supercedes Ingress and provides much more functionality without much more complexity, and (b) NGINX and HAproxy have Gateway controllers. To generally answer ", "context": "", "use_case": "", "switched_from": "", "story": "Kubernetes Ingress Nginx is retiring"}]}