Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-5592

External DNS operator doesn't work on HCP clusters

XMLWordPrintable

    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request
      Make External DNS operator compatible with HCP clusters

      2. What is the nature and description of the request?
      Installing the External DNS operator in HCP clusters is not successful since some pods are hard-coded placed in master nodes only and HCP doesn't have them.

      https://github.com/openshift/external-dns-operator/blob/48345f6ac0a7ed3d76b6d7532f8b88d9222990d2/pkg/operator/controller/externaldns/deployment.go#L203-L206
      	nodeSelectorLbl := map[string]string{
		osLabel:             linuxOS,
		masterNodeRoleLabel: "",
	}

      Manually editing the deployment doesn't work since it is owned by the operator and eventually the manual changes are overwritten

      3. Why does the customer need this? (List the business requirements here)
      We need to be able to get those pods running on worker so that the operator can get successfully installed on HCP clusters.

              mcurry@redhat.com Marc Curry
              rhn-support-gilins Givaldo Lins
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: