We would like to share an upcoming change to our platform’s connectivity. To ensure we continue providing the most secure and modern infrastructure, we are transitioning our Kubernetes-driven ingress services from NGINX to HAProxy.

What is changing?

We are moving from our current NGINX-based setup to HAProxy as our new standard. This transition is part of our commitment to staying aligned with the latest industry standards and ensuring that our systems remain robust, scalable, and fully supported.

Why now?

The project behind the NGINX Ingress Controller is reaching its planned retirement (see Learn More) at the end of March 2026. By moving to HAProxy soon, we are upgrading to a solution known for its reliability and high performance.

What this means for our you as our customer?

• Intershop teams are managing the transition behind the scenes.
  
  
• Potential action required for
  
  
  • DNS configuration in case of using DNS A-records: If you as a customer are using DNS A-records for one or more domains - pointing to fixed public IP address(s) of Intershop Commerce Platform instead of using DNS CNAME-records, you will be required to change that IP address(es) and we need to align a date for switch-over. In such case, please file a service request as soon as possible via Intershop service portal.
    Please note that Intershop recommends to always use DNS CNAME-records where possible, see Intershop Confluence customer system page.
  • certain internal IT-related configurations such as VPN/NAT/routing for accessing test environments in Intershop Platform - e.g. access to the new public IP address(es) should be making use of your company VPN if the current VPN config does so for the current IP address(es)
    
    
• For an overview of current/old and future public IP address mappings, please refer to the attached table in the to be created tickets by the service managers (upcoming).
  
  
• It is important that you as a customer cross-check if those IP address(es) is/are used anywhere else in your IT landscape.

Timeline

The transition is going to start soon and is scheduled to be completed by end of March 2026. Our teams will communicate directly if any further specific minor adjustments are needed for a particular service. We will not automatically start migration if DNS A-records are involved without further alignment. Intershop will contact and align with all affected customer via a dedicated ticket in the service portal to managed this change directly.

Expected Impact

Brief service interruptions may occur during the short maintenance window (way less than 10 min expected). Intershop will ensure interruptions are kept to an absolute minimum.

Learn More

You can read more about the official industry-wide transition and why this move is the best path forward:

• Official Ingress NGINX Retirement: http://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/
• Microsoft Azure Kubernetes Services (AKS) Ingress Update: http://blog.aks.azure.com/2025/11/13/ingress-nginx-update