NGINX Ingress Controller Generates Incorrect Configuration for Kind Ingress Objects with Custom Ports

[medicharlachiranjeevi]

Description: NGINX Ingress Controller Generates Incorrect Configuration for Kind Ingress Objects with Custom Ports

Summary:
The NGINX Ingress Controller incorrectly generates NGINX configurations when creating new Ingress objects of kind Ingress. Despite being configured to use custom ports (9090 for HTTP and 9443 for HTTPS) and running as a non-root user (UID: 101), the controller still attempts to create configurations for default ports 80 and 443, causing permission-related failures.

Steps to Reproduce:

1. Configure the NGINX Ingress Controller with the following:
   • User ID (UID): 101 (non-root)
   • Group ID (GID): 101
   • Custom ports:
     • HTTP: 9090
     • HTTPS: 9443
2. Deploy the NGINX Ingress Controller with the above settings.
3. Create a new Ingress object of kind Ingress in the cluster.
4. Monitor the generated NGINX configuration and logs.

Expected Behavior:
The NGINX Ingress Controller should generate configurations only for the custom ports (9090 and 9443) and properly handle new Ingress objects without referring to root-restricted ports.

Actual Behavior:
When a new Ingress object is created, the controller generates configurations targeting the default ports 80 and 443, leading to permission failures as the non-root user (UID: 101) cannot bind to these ports.

Impact:

• NGINX fails to reload with valid configurations due to permission issues.
• Non-root deployments are non-functional, breaking compliance and best practices.
• Service downtime or unexpected behavior for applications relying on Ingress.

Environment Details:

• Deployment configuration:
  • User: Non-root (UID: 101, GID: 101)
  • HTTP port: 9090
  • HTTPS port: 9443

Logs/Error Messages:

• Errors like Permission denied when attempting to bind to ports 80 and 443.
• Configuration files generated with incorrect port mappings for the new Ingress object.