Closed as not planned
Description
What happened?
The time when kubelet receives the pod creation request is much later than the time when scheduler scheduling is successful.
The log is as follows:
scheduler:
I1115 04:12:00.190703 10 schedule_one.go:286] "Successfully bound pod to node" pod="kube-system/registry-6cc84d4599-d7v2z" node="master1" evaluatedNodes=1 feasibleNodes=1
kubelet:
I1115 04:47:49.244673 504031 kubelet.go:2430] "SyncLoop ADD" source="api" pods=["kube-system/registry-6cc84d4599-d7v2z"]
What did you expect to happen?
Kubelet should watch pod changes in time.
How can we reproduce it (as minimally and precisely as possible)?
N/A
Anything else we need to know?
No response
Kubernetes version
$ kubectl version
# paste output here
1.31
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
Categorizes issue or PR as a support question.Denotes an issue or PR that has aged beyond stale and will be auto-closed.Indicates an issue or PR lacks a `triage/foo` label and requires one.Categorizes an issue or PR as relevant to SIG Node.Indicates an issue needs more information in order to work on it.
Type
Projects
Status
Done