calico-node and kube-sriov-device-plugin platform pods are requesting CPU resources
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Mohammad Issa |
Bug Description
Brief Description
-----------------
While running tests in the lab I noticed that the calico-node and kube-sriov-
Severity
-----------------
Minor: System/Feature is usable with minor issue
Steps to Reproduce
-----------------
Boot up the current load, run "kubectl describe node <nodename>" for either an AIO node or both controller and worker nodes, then look at the "CPU Requests" column in the table for "Non-terminated Pods".
Expected Behavior
-----------------
There should be no CPU requests for pods in the platform namespaces.
Actual Behavior
-----------------
calico-node pod requested 250m (25% of a CPU) and kube-sriov-
Reproducibility
-----------------
100% Reproducible
System Configuration
-----------------
All
Load info
-----------------
BUILD_ID=
Last Pass
-----------------
Not sure, it would have passed when we first modified all the platform pods to have no CPU requests. Not sure what release that was.
Timestamp/Logs
-----------------
N/A
Alarms
-----------------
N/A
Test Activity
-----------------
Developer testing.
Workaround
-----------------
Can still use the system, just can't allocate as many application CPUs as expected.
Changed in starlingx: | |
assignee: | nobody → Mohammad Issa (m-issa) |
description: | updated |
Changed in starlingx: | |
status: | Fix Released → Opinion |
status: | Opinion → Fix Released |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.7.0 stx.networking |
Fix proposed to branch: master /review. opendev. org/c/starlingx /ansible- playbooks/ +/844329
Review: https:/