CustomDomain NotReady in AWS PrivateLink ROSA cluster

Issue

• Creating a CustomDomain in AWS PrivateLink ROSA cluster never finish.

• The CustomDomain CR is in NotReady status in AWS PrivateLink ROSA cluster, with reason Creating:

  status:
  conditions:
  - message: Creating Apps Custom Domain (apps.tc01686-dev.afs1-nprd.aws-za.sbgrp.cloud)
    reason: Creating
    status: "True"
    type: Creating
  

• The ingress ClusterOperator is degraded with the following message:

    message: 'Some ingresscontrollers are degraded: ingresscontroller "console-domain" is degraded: DegradedConditions: One or more other status conditions indicate a degraded state: LoadBalancerReady=False (LoadBalancerPending: The LoadBalancer service is pending)'
    reason: IngressControllersDegraded
    status: "True"
    type: Degraded
  

• The ingresscontroller generated by the CustomDomain CR show the following messages:

  message: 'One or more status conditions indicate unavailable: LoadBalancerReady=False (LoadBalancerPending: The LoadBalancer service is pending)'
  

  message: 'One or more other status conditions indicate a degraded state: LoadBalancerReady=False (LoadBalancerPending: The LoadBalancer service is pending)'
  

• The ingress-operator shows the following errors:

  ERROR   operator.ingress_controller     controller/controller.go:244    got retryable error; requeueing {"after": "1m0s", "error": "IngressController is degraded: LoadBalancerRead
  y=False (SyncLoadBalancerFailed: The service-controller component is reporting SyncLoadBalancerFailed events like: Error syncing load balancer: failed to ensure load balancer: could not find any suitable subnets for creating the ELB\nThe kube-controller-manager logs may contain more details.)"}
  

  ERROR   operator.ingress_controller     controller/controller.go:244    got retryable error; requeueing {"after": "1m0s", "error": "IngressController is degraded: LoadBalancerReady=False (LoadBalancerPending: The LoadBalancer service is pending)"}