github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #122351 from sanposhiho/doc-update-for-add

Browse Source 
doc: make it clear that how newly scheduled Pods are interpreted in cluster events
This commit is contained in:
Kubernetes Prow Robot
2023-12-31 08:04:43 +01:00
committed by GitHub
parent 63eb5028ba e1e035e3a8
commit 3be9a8cc73
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
pkg/scheduler/framework/types.go
View File

@@ -65,6 +65,12 @@ type GVK string
// Constants for GVKs. // Constants for GVKs.
const ( const (
// There are a couple of notes about how the scheduler notifies the events of Pods:
// - Add: add events could be triggered by either a newly created Pod or an existing Pod that is scheduled to a Node.
// - Delete: delete events could be triggered by:
// - a Pod that is deleted
// - a Pod that was assumed, but gets un-assumed due to some errors in the binding cycle.
// - an existing Pod that was unscheduled but gets scheduled to a Node.
Pod GVK = "Pod" Pod GVK = "Pod"
Node GVK = "Node" Node GVK = "Node"
PersistentVolume GVK = "PersistentVolume" PersistentVolume GVK = "PersistentVolume"