Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.20.z
Component/s: insights-runtime-extractor
Labels:
None

Activity Type:
None
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

 Pods fro insights-runtime-extractor daemonset are not deployed if the nodes are tainted

Version-Release number of selected component (if applicable):

    4.20.8

How reproducible:

    Permanently

Steps to Reproduce:

    1. Create a node with this taint spec: key : node-role.kubernetes.io/infra effect: NoSchedule
    2. Observe the insights-runtime-extractor is not deployed in this node
     3.

Actual results:

    insights-runtime-extractor is not deployed if the node has a taint

Expected results:

    insights-runtime-extractor should be deployed every nodes

Additional info:

Root cause:    an empty toleration seem to me missing in the Daemonset

tolerations:
- operator: Exists

Assignee:: Isaac Jimeno

Reporter:: Laurent TOURREAU

Need Info From:: None

Contributors:: None

QA Contact:: Jeff Mesnil

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2026/01/21 12:30 PM

Updated:: 2026/01/21 12:30 PM

Details

Description

Attachments

Easy Agile Planning Poker

Activity

People

Dates