crossZoneLoadBalancing is false for huliu-aws1017a-wswz9-int and huliu-aws1017a-wswz9-ext loadbalancers, but should be true.

https://drive.google.com/file/d/18oBCtXjD7sH4o3b9RO4Njd6V2eXtH1oI/view?usp=sharing
https://drive.google.com/file/d/1aL1rikuasjmicpCGLa94Jf-orK_I4JeK/view?usp=sharing

scheme is internet-facing for huliu-aws1017a-wswz9-int loadbalancer, but should be internal

https://drive.google.com/file/d/14lNEVZ9dzjBl7quiVQM6KYSF-pYsowLE/view?usp=sharing
https://drive.google.com/file/d/1cPTxZfpk8jNGDVJjH-fDQSTiVEmM0ffS/view?usp=sharing

    4.21.0-0.nightly-2025-10-15-162146

    always

    1.Install an AWS techpreview cluster, check loadbalancers in controlplanemachineset and AWSCluser

In controlplanemachineset, it's
            loadBalancers:
            - name: huliu-aws1017a-wswz9-int
              type: network
            - name: huliu-aws1017a-wswz9-ext
              type: network

In AWSCluster, it's

liuhuali@Lius-MacBook-Pro huali-test % oc get awscluster
NAME                   CLUSTER                READY   VPC   BASTION IP
huliu-aws1017a-wswz9   huliu-aws1017a-wswz9   true          
liuhuali@Lius-MacBook-Pro huali-test % oc get awscluster huliu-aws1017a-wswz9 -oyaml
apiVersion: infrastructure.cluster.x-k8s.io/v1beta2
kind: AWSCluster
metadata:
  annotations:
    cluster.x-k8s.io/managed-by: cluster-capi-operator-infracluster-controller
  creationTimestamp: "2025-10-17T00:53:08Z"
  generation: 1
  labels:
    cluster.x-k8s.io/cluster-name: huliu-aws1017a-wswz9
  name: huliu-aws1017a-wswz9
  namespace: openshift-cluster-api
  ownerReferences:
  - apiVersion: cluster.x-k8s.io/v1beta1
    blockOwnerDeletion: true
    controller: true
    kind: Cluster
    name: huliu-aws1017a-wswz9
    uid: dbdb2a21-0820-43c1-a622-ca7427035d1d
  resourceVersion: "24276"
  uid: be68ffae-2fef-4190-a273-b5875fdb0f13
spec:
  bastion:
    enabled: false
  controlPlaneEndpoint:
    host: api-int.huliu-aws1017a.qe.devcluster.openshift.com
    port: 6443
  controlPlaneLoadBalancer:
    crossZoneLoadBalancing: false
    loadBalancerType: nlb
    name: huliu-aws1017a-wswz9-int
    scheme: internet-facing
  identityRef:
    kind: AWSClusterControllerIdentity
    name: default
  network:
    vpc:
      availabilityZoneSelection: Ordered
      availabilityZoneUsageLimit: 3
      subnetSchema: PreferPrivate
  region: us-east-2
  secondaryControlPlaneLoadBalancer:
    crossZoneLoadBalancing: false
    loadBalancerType: nlb
    name: huliu-aws1017a-wswz9-ext
    scheme: internet-facing
status:
  ready: true


    

  For huliu-aws1017a-wswz9-int loadbalaner, crossZoneLoadBalancing is false, but on AWS console, Cross-zone load balancing is On; scheme is internet-facing, but on AWS console, Scheme is Internal

For huliu-aws1017a-wswz9-ext loadbalaner, crossZoneLoadBalancing is false, but on AWS console, Cross-zone load balancing is On

    loadbalancers inforamtion of AWSCluster should be the same with AWS

    new feature testing for https://issues.redhat.com//browse/OCPCLOUD-2709