Awkward pod status message for admission errors due to node-pressure condition #112605
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Projects
What happened?
When a Pod admission fails due to node-pressure condition then the Pod's
status.message
looks like this:"Pod The node had condition: [DiskPressure]."
The "Pod The node..." reads awkward.
What did you expect to happen?
A message like: "The node had condition: [DiskPressure].".
How can we reproduce it (as minimally and precisely as possible)?
node.kubernetes.io/disk-pressure:NoSchedule
). The Pod gets stuck in thePending
phase.kubectl taint node $nodeName node.kubernetes.io/disk-pressure:NoSchedule-
Then, the status of the Pod contains the awkward message.
Anything else we need to know?
No response
Kubernetes version
Cloud provider
OS version
Install tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
The text was updated successfully, but these errors were encountered: