mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-07-30 23:15:14 +00:00
Merge pull request #128353 from sanposhiho/patch-13
fix: register ResourceSlice to allResources
This commit is contained in:
commit
7c56aa5a58
@ -45,7 +45,7 @@ var generation int64
|
|||||||
type ActionType int64
|
type ActionType int64
|
||||||
|
|
||||||
// Constants for ActionTypes.
|
// Constants for ActionTypes.
|
||||||
// Note: When you add a new ActionType, you must update the following:
|
// CAUTION for contributors: When you add a new ActionType, you must update the following:
|
||||||
// - The list of basic, podOnly, and nodeOnly.
|
// - The list of basic, podOnly, and nodeOnly.
|
||||||
// - String() method.
|
// - String() method.
|
||||||
const (
|
const (
|
||||||
@ -145,6 +145,8 @@ type EventResource string
|
|||||||
|
|
||||||
// Constants for GVKs.
|
// Constants for GVKs.
|
||||||
//
|
//
|
||||||
|
// CAUTION for contributors: When you add a new EventResource, you must register a new one to allResources.
|
||||||
|
//
|
||||||
// Note:
|
// Note:
|
||||||
// - UpdatePodXYZ or UpdateNodeXYZ: triggered by updating particular parts of a Pod or a Node, e.g. updatePodLabel.
|
// - UpdatePodXYZ or UpdateNodeXYZ: triggered by updating particular parts of a Pod or a Node, e.g. updatePodLabel.
|
||||||
// Use specific events rather than general ones (updatePodLabel vs update) can make the requeueing process more efficient
|
// Use specific events rather than general ones (updatePodLabel vs update) can make the requeueing process more efficient
|
||||||
@ -221,6 +223,7 @@ var (
|
|||||||
StorageClass,
|
StorageClass,
|
||||||
VolumeAttachment,
|
VolumeAttachment,
|
||||||
ResourceClaim,
|
ResourceClaim,
|
||||||
|
ResourceSlice,
|
||||||
DeviceClass,
|
DeviceClass,
|
||||||
}
|
}
|
||||||
)
|
)
|
||||||
|
Loading…
Reference in New Issue
Block a user