Kubernetes: Ingress NGINX retirement and your migration roadmap

  • Date: Thursday, February 26, 2026, 2:00 p.m. (CET)

  • Language: English

The retirement of the Ingress NGINX controller marks a significant change in the Kubernetes ecosystem and directly affects production clusters worldwide. After March 2026, the controller will reach its end of life, meaning it will no longer receive security updates, bug fixes, or maintenance.

As the Ingress NGINX EOL date approaches, organizations that continue to rely on the controller face increasing security, operational, and compliance risks. This webinar explains the background of the end-of-life decision and provides a structured roadmap to approach migration as a planned evolution rather than an emergency response.

Register now for free!

img_OrangeWhite Cute Simple Doodle iOS Icon_20

What will you learn in this webinar?

  • Ingress NGINX end-of-life announcement
    Timeline, technical background, and what the retirement means for your Kubernetes clusters.

  • Risks of running unmaintained ingress software
    Security vulnerabilities, operational instability, and compliance exposure after March 2026.
  • Ingress NGINX migration paths
    Overview of available options and their key differences.
  • Assessing current Ingress NGINX usage
    How to identify and evaluate ingress configurations across clusters and environments.
  • Strategic decision-making
    Immediate controller replacement versus longer-term API and architecture modernization.
  • Phased migration planning
    Building a migration timeline aligned with organizational capacity and delivery constraints.
  • Testing and validation strategies
    Ensuring zero-downtime transitions and minimizing risk during migration.
  • The future of Kubernetes networking
    Understanding the Gateway API as the long-term standard and why this shift is happening.
img_OrangeWhite Cute Simple Doodle iOS Icon_14

Why should you attend this webinar?

This webinar provides clarity on what needs to happen, when it needs to happen, and how to approach the Ingress NGINX migration without unnecessary pressure.

After attending, you will be able to:

  • Understand why the Ingress NGINX end of life affects your organization
  • Assess the urgency and scope of migration work for your specific environments
  • Evaluate migration approaches based on team skills, timelines, and infrastructure complexity
  • Create a realistic migration roadmap with clear milestones and decision points
  • Communicate risks and plans effectively to stakeholders and leadership
  • Avoid common mistakes that lead to rushed, high-risk migrations close to the deadline
  • Plan proactively instead of reacting as the Ingress NGINX EOL date approaches
  • Position your Kubernetes networking infrastructure for long-term security and maintainability

Your webinar host: Amir Zahirovic

Amir is a DevOps engineer with a strong background in Kubernetes, GitOps, and CI/CD. He combines deep AWS expertise with a passion for automation, reliability, and cloud-native best practices. In addition to building scalable delivery pipelines and operating infrastructure at scale, Amir focuses on enabling teams through clear guidance, hands-on training, and practical knowledge sharing. His goal is to help others gain confidence in modern DevOps workflows and build sustainable, self-sufficient practices.

Register now

Simply register for this and other webinars using the form. You can find more information about the other webinars here.

FAQ – Ingress NGINX End of Life

The Ingress NGINX controller is reaching end of life in March 2026. After that, it will no longer be maintained or receive security updates.

The Ingress NGINX controller is reaching end of life in March 2026.

After end of life, running Ingress NGINX increases security, operational, and compliance risks because vulnerabilities and bugs will no longer be fixed.

No. Kubernetes is not removing the Ingress API. The end of life applies only to the Ingress NGINX controller, not to Kubernetes Ingress itself.

Yes. To remain on a supported and secure setup, organizations should plan and complete a migration before the end-of-life date.

Organizations can replace the ingress-nginx controller with another ingress controller or migrate to Gateway API to modernize Kubernetes networking.

The Gateway API is considered the long-term direction for Kubernetes networking. It is more flexible than Ingress, but adoption depends on platform maturity and use cases.

Yes. With parallel deployments, testing, and staged traffic cutovers, zero-downtime migrations are possible.

Planning should start well before March 2026 to reduce risk, avoid rushed changes, and keep more migration options available.

These blog posts might interest you

PreviousNext