Description
What happened?
PodResourcesAPI provide a List()
endpoint which reports about all the resources that consumed by pods and containers on the node.
The problem is that pods which are in terminal phase (i.e. are in Failed
or Succeeded
status) are reported as well. about The internal managers reassign resources assigned to pods in terminal phase, so PodResources should ignore them, because they can still be in used.
What did you expect to happen?
PodResources should ignore and not reports about resources which are in used by pods which are in terminal phase.
How can we reproduce it (as minimally and precisely as possible)?
Provided a new test-case that demonstrates the exact problem and can be used as a reproducer: #119402
Anything else we need to know?
The docs that describes PodResourceAPI are not refer explicitly to whether List()
should ignore terminal pod's resources or not, meaning it might not be a bug at all.
OTOH, internal managers reassign resources assigned to pods in terminal phase so it make sense to not account them.
Kubernetes version
Kubernetes v1.26.2
Cloud provider
OS version
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
Install tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
Metadata
Metadata
Assignees
Labels
Type
Projects
Status