The ExternalDNS Operator encounters problems during the deployment of operands on HCP clusters (ROSA and vanilla HyperShift).
- The operand deployment's node placement is restricted to control plane nodes (https://github.com/openshift/external-dns-operator/blob/48345f6ac0a7ed3d76b6d7532f8b88d9222990d2/pkg/operator/controller/externaldns/deployment.go#L203-L214) while the HCP cluster only have nodes with the worker profile.
- The operand deployment does not have the bound service account token mounted inside the container. This prevents the use of STS-enabled credential secrets. A similar bug was previously fixed in ALBO: https://github.com/openshift/aws-load-balancer-operator/pull/51.

All GA versions (1.x)

Always

 1. Create HyperShift HCP or ROSA HCP cluster
 2. Install ExternlDNS Operator from the OperatorHub
 3. Create a given sample of ExternalDNS custom resource:
apiVersion: externaldns.olm.openshift.io/v1beta1
kind: ExternalDNS
metadata:
  name: sample-aws
spec:
  provider:
    type: AWS
    aws:
      credentials:
        name: aws-sts-creds
  source:
    type: OpenShiftRoute
    openshiftRouteOptions:
      routerName: default
  zones:
  - Z04015592QJX3EK1YYYY    

 ExternalDNS deployment stuck in Pending state.

 ExternalDNS deployment is Running and ready.