Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix(daemon): handle tombstone objects in subnet and service delete handlers

When a Kubernetes informer reconnects after a watch interruption, it may
deliver a cache.DeletedFinalStateUnknown tombstone instead of the typed
object. enqueueDeleteSubnet and enqueueDeleteService passed the raw obj
directly into the work queue without unwrapping tombstones, causing the
type assertions in reconcileRouters and reconcileServices to fail
silently, which means delete events were dropped and stale routes or
iptables rules were never cleaned up.

Add the same tombstone handling pattern already used by
enqueueDeleteProviderNetwork in the same file.

Signed-off-by: Mengxin Liu <liumengxinfly@gmail.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Mengxin Liu <liumengxinfly@gmail.com>