Insights operator - 0/X nodes are available: X node(s) didn't match node selector

Solution Verified - Updated -

Issue

  • Insights Operator pod cannot be scheduled on clusters with a default node selector, for example:
$ oc describe pod insights-operator-xxxxxx -n openshift-insights
[...]
  Events:
    Type     Reason            Age                    From               Message
    ----     ------            ----                   ----               -------
    Warning  FailedScheduling  118m (x25 over 118m)   default-scheduler  0/10 nodes are available: 10 node(s) didn't match node selector.
    Warning  FailedScheduling  118s (x121 over 117m)  default-scheduler  0/10 nodes are available: 10 node(s) didn't match node selector.

Environment

  • OpenShift Container Platform
    • 4.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content