Epic Goal

• node_exporter should not only be aware how may CPUs a node has but when running in a containerized context should also take limits into account.
• This can already be influenced by setting GOMAXPROCS, but this is cumbersome and requires additional scripting.

Why is this important?

• By default (no GOMAXPROCS set) node exporter will assume it can use all of a nodes CPU. With container limits set this can lead to node_exporter running with overcommited cpu parallelozation and consequently consuming a lot of additional CPU cyles.

Scenarios

1. A user sets a CPU limit for the node_expiorter daemon set, node_exporter tries to only use a core count according to the limit.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://issues.redhat.com//browse/OCPBUGS-13153

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>