mirror of
https://github.com/kubernetes/client-go.git
synced 2025-06-27 15:39:39 +00:00
Clarify that OnUpdate can mask delete and recreate
Kubernetes-commit: ff543ddfc09adf3d0abdf42f9d9fbd57c3ab4b43
This commit is contained in:
parent
926e1ee119
commit
85843e6e02
13
tools/cache/shared_informer.go
vendored
13
tools/cache/shared_informer.go
vendored
@ -106,7 +106,18 @@ import (
|
|||||||
// and index updates happen before such a prescribed notification.
|
// and index updates happen before such a prescribed notification.
|
||||||
// For a given SharedInformer and client, the notifications are
|
// For a given SharedInformer and client, the notifications are
|
||||||
// delivered sequentially. For a given SharedInformer, client, and
|
// delivered sequentially. For a given SharedInformer, client, and
|
||||||
// object ID, the notifications are delivered in order.
|
// object ID, the notifications are delivered in order. Because
|
||||||
|
// `ObjectMeta.UID` has no role in identifying objects, if an object
|
||||||
|
// O1 with ID (e.g. namespace and name) X and `ObjectMeta.UID` U1 in
|
||||||
|
// the SharedInformer's local cache is deleted and shortly after
|
||||||
|
// another relevant object O2 with ID X and `ObjectMeta.UID` U2 is
|
||||||
|
// created a client has no guarantee of seeing O1's deletion and
|
||||||
|
// O2's creation as two separate notifications, it might as well
|
||||||
|
// receive a single update notification where the old object is O1
|
||||||
|
// and the new object is O2. Clients that need to detect such cases
|
||||||
|
// might do so by comparing the `ObjectMeta.UID` field of the old
|
||||||
|
// and the new object in the code that handles update notifications
|
||||||
|
// (i.e. `OnUpdate` method of ResourceEventHandler).
|
||||||
//
|
//
|
||||||
// A client must process each notification promptly; a SharedInformer
|
// A client must process each notification promptly; a SharedInformer
|
||||||
// is not engineered to deal well with a large backlog of
|
// is not engineered to deal well with a large backlog of
|
||||||
|
Loading…
Reference in New Issue
Block a user