Bug 1956960 - Ability To Specify NodeSelector for Operator Registry Pods
Summary: Ability To Specify NodeSelector for Operator Registry Pods
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Kevin Rizza
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 18:29 UTC by Dustin Row
Modified: 2021-05-04 22:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-04 22:01:06 UTC
Target Upstream Version:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.