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

Ability To Specify NodeSelector for Operator Registry Pods

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Backlog (View Workflow)
    • Priority: Unprioritized
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: OLM
    • Labels:
      None
    • SFDC Cases Links:
    • SFDC Cases Counter:

      Description

      1. Proposed title of this feature request
      "OLM Registry Pod NodeSelector Customization"
      2. What is the nature and description of the request?
      The pods of all OSD managed operators need to be scheduled on specific node types ("infra" nodes). Although we have the ability to specific the nodeSelector for our operator pods, we do not have the ability to specify the nodeSelector for the operator registry pods.
      3. Why does the customer need this? (List the business requirements here)
      The customer does not want OSD managed operator workloads to be scheduled on their paid worker nodes.
      4. List any affected packages or components.
      OLM (Operator Lifecycle Manager)

      Additional Info:
      BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1956960
      Relevant Code: https://github.com/operator-framework/operator-lifecycle-manager/blob/v0.17.0/pkg/controller/registry/reconciler/reconciler.go#L94-L154

        Attachments

          Activity

            People

            Assignee:
            daniel_messer Daniel Messer
            Reporter:
            drow.openshift Dustin Row
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: