Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-2575

Ability to configure node-selector and tolerations for netobserv-plugin-static

XMLWordPrintable

    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None

      Currently it is possible to configure node-selector and tolerations for netobserv-plugin running on netobserv namespace through FlowCollector:

      apiVersion: flows.netobserv.io/v1beta2
kind: FlowCollector
metadata:
  annotations:
    argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true
  name: cluster
spec:
  consolePlugin:
    advanced:
      scheduling:
        nodeSelector:
          node-role.kubernetes.io/infra: ''
        tolerations:
          - key: node-role.kubernetes.io/infra
            operator: Exists

      This does not apply to netobserv-plugin-static plugin running in openshift-netobserv-operator namespace.
      netobserv-controller-manager pod placement is configured through OLM Subscription:

      apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: netobserv-operator
  namespace: openshift-netobserv-operator
spec:
  channel: stable
  config:
    nodeSelector:
      node-role.kubernetes.io/infra: ''
    tolerations:
      - key: node-role.kubernetes.io/infra
        operator: Exists
  name: netobserv-operator
  source: redhat-operators
  sourceNamespace: openshift-marketplace

      Since netobserv-plugin-static deployment is owned by netobserv-controller-manager deployment, it should inherit the nodeSelector/tolerations configured for netobserv-controller-manager.

       

              Unassigned Unassigned
              laurent.tourreau Laurent TOURREAU
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: