Bug 1956960

Summary: Ability To Specify NodeSelector for Operator Registry Pods
Product: OpenShift Container Platform Reporter: Dustin Row <drow>
Component: OLMAssignee: Kevin Rizza <krizza>
OLM sub component: OLM QA Contact: Jian Zhang <jiazha>
Status: CLOSED NOTABUG Docs Contact:
Severity: unspecified    
Priority: unspecified CC: ankithom
Version: 4.6.zKeywords: ServiceDeliveryImpact
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-04 22:01:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dustin Row 2021-05-04 18:29:18 UTC
Description of problem:
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.



Version-Release number of selected component (if applicable): N/A


How reproducible: 100%


Steps to Reproduce:
1. Deploy an operator via OLM in a particular namespace
2. oc get pods -n <desired-namespace> -o wide | grep registry

Actual results:
Pods land on worker nodes.

Expected results:
We can specify a nodeSelector in the CatalogSource of the operator and the registry pods land in the preferred node pool.

Additional info:
Please see relevant code as to where this registry pod is created:
https://github.com/operator-framework/operator-lifecycle-manager/blob/v0.17.0/pkg/controller/registry/reconciler/reconciler.go#L94-L154