Configure nodeSelectors via Pelorus CRD

[shaprerna]

OpenShift version

Not related to OpenShift

Problem description

Patched pelorus sub config to add nodeSelector and Tolerations but when looking at pelorus operator pod that doesn't cascade to the pod

Steps to reproduce

Adding below pelorus subscription yaml with nodeSelector and tolerations from values.yaml

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  annotations:
    argocd.argoproj.io/sync-options: ServerSideApply=true
  name: devworkspace-operator-fast-redhat-operators-openshift-marketplace
spec:
  config:
    {{- with .Values.nodeSelector }}
    nodeSelector:
      {{- toYaml . | nindent 6 }}
    {{- end }}
    {{- with .Values.tolerations }}
    tolerations:
      {{- toYaml . | nindent 6 }}
    {{- end }}
    resources:
      limits:
        memory: 4Gi
      requests:
        cpu: 500m
        memory: 4Gi

values.yaml

nodeSelector:
  node-role.kubernetes.io/infra: ''
tolerations:
  - effect: NoSchedule
    key: node-role.kubernetes.io/infra
    operator: Exists

Current behavior

Pelorus operator pod doesn't apply above nodeSelector or Tolerations or these resource config it still has the default values.

Expected behavior

Pelorus should provide a configuration mechanism to control the nodeSelector and Tolerations of all workloads it manages including dependent operators workloads

Code of Conduct

• I agree to follow Pelorus's Code of Conduct