-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Product / Portfolio Work
-
None
-
0% To Do, 100% In Progress, 0% Done
-
False
-
-
False
-
None
-
5
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
IngressController configuration
2. What is the nature and description of the request?
As a platform engineer I would like the opportunity to configure how the ingresscontroller publishes the default ingress route, by setting the `endpointPublishingStrategy` and it's underlying functions (like type, ports etc).
3. Why does the customer need this? (List the business requirements here)
Customers will be running external loadbalancers, and the current default setting is to randomize the nodePort that the service is exposing the ingress on, which is impossible to predict, and hard to automate.
By giving the users the option to configure this at install-time, the loadbalancer could already be configured before the cluster is up.