1. Proposed title of this feature request:
Validate and Add Test Coverage for LoadBalancer Services with allocateLoadBalancerNodePorts=false on Azure and GCP

2. What is the nature and description of the request?
This request is to formally validate, support, and add regression test coverage for Kubernetes LoadBalancer Services configured with:

allocateLoadBalancerNodePorts=false

externalTrafficPolicy=Local

Cloud provider–specific requirements met (Azure Floating IP enabled, equivalent behavior on GCP)

Although this configuration aligns with upstream Kubernetes and cloud-provider documentation and is observed to work in practice, there is currently no explicit OpenShift test coverage validating this behavior. The request is to ensure this configuration is officially supported and protected against regressions in future OpenShift, Cloud Controller Manager (CCM), and cloud-provider updates.

3. Why does the customer need this? (List the business requirements here)
To prevent NodePort exhaustion on large, high-traffic clusters caused by default NodePort allocation.

To support source IP preservation, which is mandatory for:

NetworkPolicy-based ingress filtering

Security and compliance requirements

To maintain operational consistency, as:

externalTrafficPolicy=Local is already required

Azure Floating IP is already enabled for other use cases (e.g., HA ports)

To gain long-term stability and support guarantees for a configuration that is already required by multiple application teams.

4. List any affected packages or components.
Azure cloud provider integration
GCP cloud provider integration