You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The actual type was cache.DeletedFinalStateUnknown, which is sent when events are missed because the watch stream was disconnected when the delete happened.
The object includes a, potentially stale, copy of the object. And since the delete handler is only using this information to remove data from the cache, I suspect the stale object is sufficient to also delete the object. A small handling of this case should cause fewer panics when there are network disconnections or missed events like this.
What you expected to happen:
Could should not panic during normal operation.
How to reproduce it (as minimally and precisely as possible):
Not sure, have seen it a handful of times while deleting services, during E2E testing
Anything else we need to know?:
Environment:
Kubernetes version (use kubectl version): 1.31
Cloud provider or hardware configuration: Azure
OS (e.g: cat /etc/os-release): RHCOS
Kernel (e.g. uname -a):
Install tools:
Network plugin and version (if this is a network-related bug):
Others:
The text was updated successfully, but these errors were encountered:
What happened:
Observed a panic
It was caused by this interface conversion.
The actual type was
cache.DeletedFinalStateUnknown
, which is sent when events are missed because the watch stream was disconnected when the delete happened.The object includes a, potentially stale, copy of the object. And since the delete handler is only using this information to remove data from the cache, I suspect the stale object is sufficient to also delete the object. A small handling of this case should cause fewer panics when there are network disconnections or missed events like this.
What you expected to happen:
Could should not panic during normal operation.
How to reproduce it (as minimally and precisely as possible):
Not sure, have seen it a handful of times while deleting services, during E2E testing
Anything else we need to know?:
Environment:
kubectl version
): 1.31cat /etc/os-release
): RHCOSuname -a
):The text was updated successfully, but these errors were encountered: