Community Ingress-NGINX Retirement and Self-Managed Runtime Fabric (RTF)

For Runtime Fabric on Self-Managed Kubernetes, the Ingress Controller is a customer-managed component. MuleSoft does not mandate, distribute, or maintain the Ingress controller for self-managed RTF clusters.

• Compatibility: Runtime Fabric supports any Ingress controller that adheres to standard Kubernetes Ingress specifications.

• Responsibility: The selection, installation, configuration, and lifecycle management of the Ingress Controller (including migrating away from deprecated solutions) are the sole responsibility of the customer.

Recommendation

Customers currently utilizing the community ingress-nginx controller should plan to migrate to a supported alternative before the March 2026 EOL date to ensure continued security updates and stability.

1. Choosing a Replacement You are free to swap the deprecated NGINX controller for any compliant alternative that meets your organization's architectural and security standards. MuleSoft Support cannot provide specific vendor recommendations.

2. Configuration Requirements Ensure your chosen controller is configured to process the Ingress resources generated by the Runtime Fabric Agent. Refer to the official documentation for requirements:

• Configuring Ingress with HTTP Route-Template Custom Resource in Runtime Fabric

• Configuring Ingress Resource Template in Runtime Fabric

• Limitations - Ingress Controller

3. Implementation Support Since the Ingress Controller is external infrastructure, MuleSoft Support cannot perform the migration or configuration of the new controller.

• For assistance with architectural design or migration execution, please engage your internal Kubernetes administration team or contact your MuleSoft Account Team or Customer Success Manager (CSM) to coordinate an engagement with  MuleSoft Professional Services.