-
Notifications
You must be signed in to change notification settings - Fork 41.6k
Closed
Closed
Copy link
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Description
What happened?
This is a follow up from: #116702 (comment)
Update of a Pod for in-place update of Pod Resources feature is constructing the updated pod and may get to the race with other update operations on this Pod.
/sig node
KEP: kubernetes/enhancements#1287
What did you expect to happen?
See the linked comment. The issue is not trivial and may require a bigger refactoring of the logic.
How can we reproduce it (as minimally and precisely as possible)?
no repro available at this moment. Likely resizing Pod around Pod Termination may result in "un-terminating" of the Pod.
Anything else we need to know?
No response
Kubernetes version
1.27
Cloud provider
Any
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 hereInstall tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Type
Projects
Status
Done
Status
Done
Status
Done