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

agent doesn't deploy on master nodes

XMLWordPrintable

    • False
    • None
    • False
    • Added toleration on the agent DaemonSet to schedule on every node when taints are set.
    • NetObserv - Sprint 264, NetObserv - Sprint 265
    • Critical

      Description of problem:

      CLI agent daemonset doesn't deploy on master nodes

      Steps to Reproduce:

      1. Run CLI 
2.
3.

      Actual results:

      $ oc get pods -n netobserv-cli
NAME                  READY   STATUS    RESTARTS   AGE
collector             1/1     Running   0          13s
netobserv-cli-2vbmh   1/1     Running   0          23s
netobserv-cli-f4dtd   1/1     Running   0          23s
netobserv-cli-xqldh   1/1     Running   0          23s

      Expected results:

      CLI agent daemonset pods should run on all nodes

              jpinsonn@redhat.com Julien Pinsonneau
              rhn-support-memodi Mehul Modi
              Mehul Modi Mehul Modi
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: