1. Proposed title of this feature request

Preallocated and predictable NodePort for Ingress

2. What is the nature and description of the request?

Right now, the NodePort for ingress is set dynamically within the acceptable range when the HostedCluster is created. This is not predictable across a fleet of HostedClusters.

Add a field to the HostedCluster CR to allow an explicit NodePort to be set on any given HostedCluster.

3. Why does the customer need this? (List the business requirements here)

To allow for a well-defined and predictable NodePort on each HostedCluster.

With a known NodePort, we can reliably create, during provisioning, a LoadBalancer service for Ingress that maps to a controller managed endpointslice for use cases that do not use the default pod network and only use the secondary network along with a custom base domain.

4. List any affected packages or components.