# ingress-nginx Published articles for ingress-nginx. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Cilium 1.20: Gateway API ExternalAuth, TCPRoute/UDPRoute, ENI IPAM for IPv6, and more DevFeed: [Cilium 1.20: Gateway API ExternalAuth, TCPRoute/UDPRoute, ENI IPAM for IPv6, and more]() Original publisher: [Read original article]() Author: Nico Vibert and Donia Chaiehloudj, Cilium Published: 2026-09-14T10:45:49Z Content type: article Language: en Sources: [Cloud Native Computing Foundation]() Topics: [Cilium](), [Open Source](), [API](), [networking](), [Kubernetes](), [Amazon Web Services](), [eBPF](), [VPC](), [nginx]() Tags: [2026](), [api](), [authentication](), [authorization](), [aws](), [blog](), [cilium](), [cloud](), [cni](), [ebpf](), [google](), [ingress-nginx](), [ipv4](), [ipv6](), [kubernetes](), [microsoft](), [network](), [networking](), [nginx](), [open-source](), [release]() ### AI overview Cilium 1.20 expands Gateway API support with ExternalAuth, CORS filters, ListenerSets, TCPRoute, and UDPRoute. The release also introduces extensible datapath plugins, advances networking standardization with Kubernetes, and adds beta IPv6 support for AWS ENI IPAM. ### Source excerpt Cilium 1.20, the second major open source Cilium release of 2026 after Cilium 1.19, is finally here. Three themes stand out in this release: Thank you to every contributor, reviewer and maintainer who made Cilium 1.20... ## Technology Short Take 193 DevFeed: [Technology Short Take 193]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2026-04-03T14:00:00Z Content type: article Language: en Sources: [Scott's Weblog]() Topics: [datacenter](), [networking](), [Security](), [GitHub Actions](), [GitOps](), [ingress-nginx](), [Docker](), [litellm](), [Large Language Model]() Tags: [aws](), [blog-post](), [cilium](), [cli](), [cloud](), [cni](), [containers](), [cri-o](), [devops](), [docker](), [github-actions](), [gitops](), [go](), [iac](), [ingress-nginx](), [k8s](), [kubernetes](), [linux](), [litellm](), [networking](), [oci](), [security](), [technology]() ### AI overview Technology Short Take 193 is a curated roundup of data center technology links covering networking, IPv4 address space, consumer-router regulation, servers and hardware, security incidents involving Trivy and software supply chains, Ingress-NGINX migration, GitOps, local LLMs, and infrastructure management. ### Source excerpt Welcome to Technology Short Take #193! I know it has only been a couple weeks since the last Tech Short Take, but I am guessing that readers won't really mind another one. Here is my latest collection of articles and posts about data center-related technologies. Enjoy! Networking Brian Linkletter shares his 2026 list of network simulators and emulators. (Hat tip to Ivan P. for the link.) Emmanuel Vitus brings to light a battle over IPv4 address space and the control of the regional internet registries. Doug Dawson discusses the recent FCC ban on consumer-grade routers and the potential impacts to industry and ISPs. Servers/Hardware RIP Mac Pro. I had a "classic Mac Pro" (2012 era) for a long time, and I loved that system. (I even ran Linux on it for a while.) It is a shame to see it go. I mentioned on social media (Mastodon/Bluesky) that I recently purchased all the hardware for a new PC build. It'll be part PC/part home server, as I look to expand the type and scope of services that I self-host. Don't be surprised if a few articles emerge out of this. Security Trivy's GitHub Actions were compromised by attackers, leading to the exposure of CI/CD secrets. This post on the Socket blog has more details, and Rose Security has a write-up that provides more details on how a typosquatted domain and a fake version tag were involved. At least one other software supply chain exploit has been tracked back to the Trivy compromise: the Python litellm module on PyPI steals credentials. The Docker side of the Trivy compromise is shared in detail in this Docker blog post. Cloud Computing/Cloud Management Looking for some help in migrating away from Ingress-NGINX? This announcement of Ingress2Gateway 1.0 might be just what you are seeking. The FluxCD team published a post discussing Morgan Stanley's "Stairway to GitOps" presentation, which describes the firm's five-year journey from push-based pipelines to a self-service GitOps platform. Although I am not an AI fanboy, I do recogni ## Fork Yeah: We're keeping ingress-nginx alive DevFeed: [Fork Yeah: We're keeping ingress-nginx alive]() Original publisher: [Read original article]() Published: 2025-12-22T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [nginx](), [Kubernetes](), [Security](), [migration](), [Open Source](), [Maintainers](), [chainguard](), [container images](), [GitHub]() Tags: [chainguard](), [chainguard-emeritoss](), [chainguard-open-source](), [container-images](), [github](), [ingress](), [ingress-nginx](), [ingress-nginx-retirement](), [kubeapps](), [kubernetes](), [maintainers](), [migration](), [nginx](), [open-source](), [security]() ### AI overview Chainguard is maintaining a fork of ingress-nginx through its EmeritOSS program after the upstream project announced retirement and planned archiving in March 2026. It offers CVE-free container images, remediation SLAs, and FIPS versions while users evaluate migration options such as the Gateway API or other ingress controllers. ### Source excerpt Chainguard is keeping ingress-nginx alive through EmeritOSS, providing security-focused maintenance so teams can migrate safely without risk. ## Introducing Chainguard EmeritOSS: Sustainable stewardship for mature open source DevFeed: [Introducing Chainguard EmeritOSS: Sustainable stewardship for mature open source]() Original publisher: [Read original article]() Published: 2025-12-16T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [Open Source](), [chainguard](), [maintenance](), [ingress-nginx](), [kaniko](), [kubeapps]() Tags: [chainguard](), [chainguard-containers-open-source](), [chainguard-emeritoss](), [chainguard-open-source](), [emeritoss](), [ingress-nginx](), [kaniko](), [kubeapps](), [maintenance](), [open-source](), [open-source-maintenance]() ### AI overview Chainguard announces EmeritOSS, a program for preserving and securely maintaining mature, unmaintained open source projects. The program starts with Kaniko, Kubeapps, and ingress-nginx. ### Source excerpt EmeritOSS is a stability-focused program that preserves and secures mature, unmaintained open source projects, starting with Kaniko, Kubeapps, and ingress-nginx. ## Ingress NGINX Retirement: What You Need to Know DevFeed: [Ingress NGINX Retirement: What You Need to Know]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2025-11-12T17:00:00Z Content type: release Language: en Sources: [Kubernetes Contributors Blog]() Topics: [ingress-nginx](), [ingress nginx retirement](), [Kubernetes](), [Security](), [Vulnerabilities](), [Network]() Tags: [alternatives](), [gateway](), [ingress-nginx](), [ingress-nginx-retirement](), [kubernetes](), [releases](), [security](), [security-vulnerabilities]() ### AI overview Kubernetes SIG Network and the Security Response Committee announce the upcoming retirement of Ingress NGINX. Best-effort maintenance will continue until March 2026; afterward, the project will receive no further releases, bug fixes, or security updates. Existing deployments and installation artifacts will remain available, and users are encouraged to migrate to alternatives such as Gateway API. ### Source excerpt To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX . Best-effort maintenance will continue until March 2026. Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered. Existing deployments of Ingress NGINX will continue to function and installation artifacts will remain available. We recommend migrating to one of the many alternatives. Consider migrating to Gateway API , the modern replacement for Ingress. If you must continue using Ingress, many alternative Ingress controllers are listed in the Kubernetes documentation . Continue reading for further information about the history and current state of Ingress NGINX, as well as next steps. About Ingress NGINX Ingress is the original user-friendly way to direct network traffic to workloads running on Kubernetes. (Gateway API is a newer way to achieve many of the same goals.) In order for an Ingress to work in your cluster, there must be an Ingress controller running. There are many Ingress controller choices available, which serve the needs of different users and use cases. Some are cloud-provider specific, while others have more general applicability. Ingress NGINX was an Ingress controller, developed early in the history of the Kubernetes project as an example implementation of the API. It became very popular due to its tremendous flexibility, breadth of features, and independence from any particular cloud or infrastructure provider. Since those days, many other Ingress controllers have been created within the Kubernetes project by community groups, and by cloud native vendors. Ingress NGINX has continued to be one of the most popular, deployed as part of many hosted Kubernetes platforms and within innumerable independent users' clusters. History and Challenges The breadth and flexibility of Ingress NGINX has caused maint ## Ingress-nginx-controller: Nightmare on CVE Street DevFeed: [Ingress-nginx-controller: Nightmare on CVE Street]() Original publisher: [Read original article]() Published: 2025-04-02T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [nginx](), [Vulnerabilities](), [Security](), [Kubernetes](), [chainguard containers](), [chainguard os](), [chainguard]() Tags: [availability](), [chainguard](), [chainguard-containers](), [chainguard-os](), [container-images](), [containers](), [cve](), [cves](), [ingress](), [ingress-nginx](), [kubernetes](), [nginx](), [remote-code-execution](), [security](), [vulnerabilities](), [wiz]() ### AI overview The article describes several critical remote code execution vulnerabilities affecting the Ingress-nginx-controller, including risks to Kubernetes cluster secrets, service availability, privileges, and security controls. It also explains how Chainguard reviewed its infrastructure, identified affected Chainguard Containers, and prepared patches using Chainguard OS's continuous update model. ### Source excerpt Chainguard was able to quickly respond to and handle the recent ingress-nginx-controller CVEs that were discovered by Wiz. See the actions we have taken. ## Ingress-nginx CVE-2025-1974: What It Is and How to Fix It DevFeed: [Ingress-nginx CVE-2025-1974: What It Is and How to Fix It]() Original publisher: [Read original article]() Author: Abhimanyu Saharan Published: 2025-03-25T00:00:00Z Content type: article Language: en Sources: [Abhimanyu Saharan]() Topics: [nginx]() Tags: [2025](), [cve](), [how-to](), [ingress-nginx](), [kubernetes](), [rce](), [security]() ### AI overview The article explains CVE-2025-1974, known as IngressNightmare, a critical remote code execution vulnerability in ingress-nginx that affects more than 40% of clusters. It covers how to detect and patch the flaw. ### Source excerpt CVE-2025-1974 (IngressNightmare) is a critical RCE flaw in ingress-nginx affecting 40%+ of clusters. Learn how to detect and patch it. ## Iterating Towards a More Scalable Ingress DevFeed: [Iterating Towards a More Scalable Ingress]() Original publisher: [Read original article]() Author: Francisco Mejia Published: 2018-08-31T18:00:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Kubernetes](), [nginx](), [Cloud](), [Production Engineering]() Tags: [ingress-nginx](), [kubernetes](), [load-balancer](), [nginx](), [open-source](), [optimization](), [performance](), [production-engineering](), [shopify]() ### AI overview Shopify describes scaling its Kubernetes infrastructure and migrating cluster ingress from Google Cloud Load Balancer Controller to ingress-nginx. The article focuses on optimizing ingress-nginx dynamic configuration to reduce NGINX reloads and improve performance during frequent deployments. ### Source excerpt Shopify, the leading cloud-based, multi-channel commerce platform, is growing at an incredibly fast pace. Since the beginning of 2016, the number of merchants on the platform increased from 375,000 to 600,000+. As the platform scales, we face new and exciting challenges such as implementing Shopify's Pod architecture and future proofing our cloud storage usage. Shopify's infrastructure relies heavily on Kubernetes to serve millions of requests every minute.