Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-56173

CNO does not have a way to understand if frrk8s is running on a node

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.19
    • Networking / FRR-K8s
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • Rejected
    • CNF Network Sprint 274, CNF Network Sprint 276, CNF Network Sprint 279, CNF Network Sprint 280
    • 4
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      Now that CNO deploys frr-k8s we do not support node selector. That means once metallb instance is deployed
      then operator asks the CNO to deploy frr-k8s, and CNO deploy frr-k8s without any selector.
      There might be use case e.g. a cluster with one node with performance profile that should not run any pod that is not needed and occupy resources.

              fpaoline@redhat.com Federico Paolinelli
              gkopels@redhat.com Gregory Kopels
              None
              None
              Arti Sood Arti Sood
              None
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: