github/client-go
1
0
Fork 0
mirror of https://github.com/kubernetes/client-go.git synced 2025-06-26 15:12:06 +00:00
Code Issues Projects Releases Wiki Activity

Clarify that OnUpdate can mask delete and recreate

Browse Source 
Kubernetes-commit: ff543ddfc09adf3d0abdf42f9d9fbd57c3ab4b43
This commit is contained in:
matte21 2019-10-28 14:12:22 +01:00 committed by Kubernetes Publisher
parent 926e1ee119
commit 85843e6e02
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
tools/cache/shared_informer.go vendored
View File

@ -106,7 +106,18 @@ import (
// and index updates happen before such a prescribed notification.
// For a given SharedInformer and client, the notifications are
// 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
// is not engineered to deal well with a large backlog of