-
Feature Request
-
Resolution: Done
-
Undefined
-
None
-
None
-
False
-
False
-
Undefined
-
-
-
-
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)
First, the customer does not want OSD managed operator workloads to be scheduled on their paid worker nodes.
Second, if a customer overloads workers it is possible catalog pods will not be scheduled and therefore SRE operators cannot install or upgrade.
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
- is incorporated by
-
OPRUN-2335 Support customizing node selectors / taints / tolerations to default catalog pods
- Closed
- is related to
-
OCPSTRAT-811 [PRD scope] OLM 1.0 - Extension Catalogs (F1)
- New
-
OCPSTRAT-429 [Phase 2 MVP/Tech Preview] OLM 1.0 - Extension Catalogs (F1)
- Closed
- links to