2026-02-17 02:35:54.433 [INFO][1] typha/cmdwrapper.go 56: Starting /usr/bin/kube-controllers
2026-02-17 02:35:54.474 [INFO][15] kube-controllers/main.go 95: Loaded configuration from environment config=&config.Config{LogLevel:"info", WorkloadEndpointWorkers:1, ProfileWorkers:1, PolicyWorkers:1, NodeWorkers:1, Kubeconfig:"", DatastoreType:"kubernetes"}
2026-02-17 02:35:54.475 [INFO][15] kube-controllers/main.go 119: Ensuring Calico datastore is initialized
2026-02-17 02:35:54.790 [INFO][15] kube-controllers/main.go 144: Calico datastore is initialized
2026-02-17 02:35:54.790 [INFO][15] kube-controllers/main.go 183: Getting initial config snapshot from datastore
2026-02-17 02:35:54.954 [INFO][15] kube-controllers/main.go 186: Got initial config snapshot
2026-02-17 02:35:54.955 [INFO][15] kube-controllers/main.go 200: Starting status report routine
2026-02-17 02:35:54.955 [INFO][15] kube-controllers/main.go 209: Starting Prometheus metrics server on port 9094
2026-02-17 02:35:54.955 [INFO][15] kube-controllers/main.go 518: Starting informer informer=&cache.sharedIndexInformer{indexer:(*cache.cache)(0xc000587800), controller:cache.Controller(nil), processor:(*cache.sharedProcessor)(0xc0000fb810), cacheMutationDetector:cache.dummyMutationDetector{}, listerWatcher:(*cache.ListWatch)(0xc0006f9cb0), objectType:(*v1.Pod)(0xc000341208), objectDescription:"", resyncCheckPeriod:0, defaultEventHandlerResyncPeriod:0, clock:(*clock.RealClock)(0x3f97380), started:false, stopped:false, startedLock:sync.Mutex{_:sync.noCopy{}, mu:sync.Mutex{state:0, sema:0x0}}, blockDeltas:sync.Mutex{_:sync.noCopy{}, mu:sync.Mutex{state:0, sema:0x0}}, watchErrorHandler:(cache.WatchErrorHandlerWithContext)(nil), transform:(cache.TransformFunc)(0x1f197e0)}
2026-02-17 02:35:54.956 [INFO][15] kube-controllers/main.go 518: Starting informer informer=&cache.sharedIndexInformer{indexer:(*cache.cache)(0xc000587830), controller:cache.Controller(nil), processor:(*cache.sharedProcessor)(0xc0000fbdb0), cacheMutationDetector:cache.dummyMutationDetector{}, listerWatcher:(*cache.ListWatch)(0xc0006f9ec0), objectType:(*v1.Node)(0xc000530908), objectDescription:"", resyncCheckPeriod:0, defaultEventHandlerResyncPeriod:0, clock:(*clock.RealClock)(0x3f97380), started:false, stopped:false, startedLock:sync.Mutex{_:sync.noCopy{}, mu:sync.Mutex{state:0, sema:0x0}}, blockDeltas:sync.Mutex{_:sync.noCopy{}, mu:sync.Mutex{state:0, sema:0x0}}, watchErrorHandler:(cache.WatchErrorHandlerWithContext)(nil), transform:(cache.TransformFunc)(nil)}
2026-02-17 02:35:54.956 [INFO][15] kube-controllers/main.go 518: Starting informer informer=&cache.sharedIndexInformer{indexer:(*cache.cache)(0xc000587848), controller:cache.Controller(nil), processor:(*cache.sharedProcessor)(0xc0000fbe00), cacheMutationDetector:cache.dummyMutationDetector{}, listerWatcher:(*cache.ListWatch)(0xc0006800c0), objectType:(*v1.Service)(0xc000631408), objectDescription:"", resyncCheckPeriod:0, defaultEventHandlerResyncPeriod:0, clock:(*clock.RealClock)(0x3f97380), started:false, stopped:false, startedLock:sync.Mutex{_:sync.noCopy{}, mu:sync.Mutex{state:0, sema:0x0}}, blockDeltas:sync.Mutex{_:sync.noCopy{}, mu:sync.Mutex{state:0, sema:0x0}}, watchErrorHandler:(cache.WatchErrorHandlerWithContext)(nil), transform:(cache.TransformFunc)(nil)}
2026-02-17 02:35:54.956 [INFO][15] kube-controllers/main.go 518: Starting informer informer=&cache.sharedIndexInformer{indexer:(*cache.cache)(0xc000587878), controller:cache.Controller(nil), processor:(*cache.sharedProcessor)(0xc0000fbe50), cacheMutationDetector:cache.dummyMutationDetector{}, listerWatcher:(*cache.ListWatch)(0xc0006802d0), objectType:(*v1.Namespace)(0xc000682000), objectDescription:"", resyncCheckPeriod:0, defaultEventHandlerResyncPeriod:0, clock:(*clock.RealClock)(0x3f97380), started:false, stopped:false, startedLock:sync.Mutex{_:sync.noCopy{}, mu:sync.Mutex{state:0, sema:0x0}}, blockDeltas:sync.Mutex{_:sync.noCopy{}, mu:sync.Mutex{state:0, sema:0x0}}, watchErrorHandler:(cache.WatchErrorHandlerWithContext)(nil), transform:(cache.TransformFunc)(nil)}
2026-02-17 02:35:54.957 [INFO][15] kube-controllers/main.go 524: Starting controller ControllerType="Node"
2026-02-17 02:35:54.957 [INFO][15] kube-controllers/main.go 524: Starting controller ControllerType="LoadBalancer"
2026-02-17 02:35:54.957 [INFO][15] kube-controllers/watchersyncer.go 118: Start called
2026-02-17 02:35:54.957 [INFO][15] kube-controllers/watchersyncer.go 158: Sending status update Status=wait-for-ready
2026-02-17 02:35:54.957 [INFO][15] kube-controllers/syncer.go 94: Node controller syncer status updated: wait-for-ready
2026-02-17 02:35:54.957 [INFO][15] kube-controllers/watchersyncer.go 177: Starting main event processing loop
2026-02-17 02:35:54.958 [INFO][15] kube-controllers/watchercache.go 243: Full resync is required ListRoot=".../v3/pc.org/hostendpoints"
2026-02-17 02:35:54.958 [INFO][15] kube-controllers/resources.go 349: Main client watcher loop
2026-02-17 02:35:54.958 [INFO][15] kube-controllers/watchercache.go 243: Full resync is required ListRoot=".../v3/pc.org/nodes"
2026-02-17 02:35:54.958 [INFO][15] kube-controllers/watchercache.go 243: Full resync is required ListRoot=".../v3/pc.org/clusterinformations"
2026-02-17 02:35:54.959 [INFO][15] kube-controllers/watchercache.go 243: Full resync is required ListRoot=".../ipam/v2/assignment/"
2026-02-17 02:35:54.960 [INFO][15] kube-controllers/watchercache.go 243: Full resync is required ListRoot=".../v3/pc.org/ippools"
2026-02-17 02:35:54.964 [INFO][15] kube-controllers/watchercache.go 447: Sending synced update ListRoot=".../v3/pc.org/hostendpoints"
2026-02-17 02:35:54.958 [INFO][15] kube-controllers/controller.go 168: Starting Node controller
2026-02-17 02:35:54.964 [INFO][15] kube-controllers/watchersyncer.go 243: Received InSync event from one of the watcher caches
2026-02-17 02:35:54.964 [INFO][15] kube-controllers/watchersyncer.go 158: Sending status update Status=resync
2026-02-17 02:35:54.964 [INFO][15] kube-controllers/syncer.go 94: Node controller syncer status updated: resync
I0217 02:35:54.964473      15 shared_informer.go:350] "Waiting for caches to sync" controller="nodes"
2026-02-17 02:35:54.965 [INFO][15] kube-controllers/watchercache.go 447: Sending synced update ListRoot=".../v3/pc.org/ippools"
2026-02-17 02:35:54.967 [INFO][15] kube-controllers/watchercache.go 447: Sending synced update ListRoot=".../v3/pc.org/nodes"
2026-02-17 02:35:54.967 [INFO][15] kube-controllers/watchersyncer.go 243: Received InSync event from one of the watcher caches
2026-02-17 02:35:54.967 [INFO][15] kube-controllers/watchersyncer.go 243: Received InSync event from one of the watcher caches
2026-02-17 02:35:54.968 [INFO][15] kube-controllers/watchercache.go 447: Sending synced update ListRoot=".../v3/pc.org/clusterinformations"
2026-02-17 02:35:54.968 [INFO][15] kube-controllers/watchersyncer.go 243: Received InSync event from one of the watcher caches
2026-02-17 02:35:54.971 [INFO][15] kube-controllers/watchercache.go 447: Sending synced update ListRoot=".../ipam/v2/assignment/"
2026-02-17 02:35:54.971 [INFO][15] kube-controllers/watchersyncer.go 243: Received InSync event from one of the watcher caches
2026-02-17 02:35:54.971 [INFO][15] kube-controllers/watchersyncer.go 255: All watchers have sync'd data - sending data and final sync
2026-02-17 02:35:54.971 [INFO][15] kube-controllers/watchersyncer.go 158: Sending status update Status=in-sync
2026-02-17 02:35:54.971 [INFO][15] kube-controllers/syncer.go 94: Node controller syncer status updated: in-sync
2026-02-17 02:35:55.062 [INFO][15] kube-controllers/loadbalancer_controller.go 237: Will run periodic IPAM sync every 5m0s
2026-02-17 02:35:55.063 [INFO][15] kube-controllers/ipam.go 2387: Upgrading any IPAM affinities from older versions.... node="load-balancer"
I0217 02:35:55.065375      15 shared_informer.go:357] "Caches are synced" controller="nodes"
I0217 02:35:55.065456      15 shared_informer.go:350] "Waiting for caches to sync" controller="pods"
I0217 02:35:55.065477      15 shared_informer.go:357] "Caches are synced" controller="pods"
2026-02-17 02:35:55.065 [INFO][15] kube-controllers/hostendpoints.go 149: Will run periodic HostEndpoint sync every 5m0s
2026-02-17 02:35:55.066 [INFO][15] kube-controllers/hostendpoints.go 186: Syncer is InSync, kicking sync channel status=in-sync
2026-02-17 02:35:55.065 [INFO][15] kube-controllers/ipam.go 312: Will run periodic IPAM sync every 7m30s
2026-02-17 02:35:55.066 [INFO][15] kube-controllers/hostendpoints.go 259: Syncing all HostEndpoints
2026-02-17 02:35:55.859 [INFO][15] kube-controllers/ipam.go 2427: No affinities needed to be upgraded.
2026-02-17 02:35:56.067 [INFO][15] kube-controllers/ipam.go 379: Syncer is InSync, kicking sync channel status=in-sync
2026-02-17 02:35:56.861 [INFO][15] kube-controllers/loadbalancer_controller.go 271: Syncer is InSync, kicking sync channel status=in-sync
2026-02-17 02:38:09.788 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.45378497a920b593d72cefa3dbf94fc6b83474d22edc9d9c55d119c98ed6ab8c" ip="10.100.3.2" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-7331/test-rolling-update-controller-m45hr"
2026-02-17 02:38:12.341 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.87a1a4134cce4e88cda658ff341348cf6ebb32825fba8c83067084e2b56e8df9" ip="10.100.89.194" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="webhook-6703/sample-webhook-deployment-7d44fffc8-mcttj"
2026-02-17 02:38:17.159 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.4f14060bbd471a4989c19afafdcbd94b3201a26890908ec1d5d1bc39c624f6a8" ip="10.100.89.195" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-7331/test-rolling-update-deployment-5bd98b4894-l99mn"
2026-02-17 02:38:21.340 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.b77555e45ec7a3edf40efe2323dc05a3fe52d9cb2f5225eeb3b3ce96b7cb48ad" ip="10.100.89.196" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="webhook-5385/sample-webhook-deployment-7d44fffc8-8fv5w"
2026-02-17 02:38:22.342 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.3d47c4fcc705201e25b83a85e1e91ad09416caa438a235445c3b8a9b5ef4dac0" ip="10.100.3.4" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-9541/sample-webhook-deployment-7d44fffc8-r948v"
2026-02-17 02:38:58.540 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.ad4f7948b3064519139feabf26e1f399c39a0f3d0ea3ea2ea75a3076db0c5f36" ip="10.100.3.9" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="subpath-5441/pod-subpath-test-downwardapi-gwwt"
2026-02-17 02:39:00.548 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.e107882c07e729bd12a52d1704226354828a1a615a83fd009cadae89f52908d2" ip="10.100.89.204" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="security-context-test-1647/busybox-user-65534-a9550846-c9d4-42a4-8479-a90c63a68945"
2026-02-17 02:39:10.017 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.e625a45dda0033a049359a20bd3eba652624e4b4beecaa31464fe84a713f1c25" ip="10.100.89.206" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-8167/externalsvc-8664db8f97-skdbz"
2026-02-17 02:39:10.017 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.7aaf34dcd4ba4e39845d412256107f21768bc9d9d2afe717aa576238c8e33463" ip="10.100.3.17" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-8167/externalsvc-8664db8f97-8z687"
2026-02-17 02:39:15.080 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.d956cbfc8d4dc43003d6d744a5373a97f69b180225d1f455ff40d2aa83b80bac" ip="10.100.3.19" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="container-runtime-1265/termination-message-containerd99e8615-9b1c-47b4-8085-86bd18632f8a"
2026-02-17 02:39:15.080 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.42f6506b87f49a1db993f6ae8a98e73bcb3e9493632cae87f19884fc6ae6f9c0" ip="10.100.3.18" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-8167/execpodwldmq"
2026-02-17 02:39:17.082 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.7ab8d477a98155ad398881e8f960f0092cc51f8cd2e68bfe613fcd71e3c7a0d8" ip="10.100.89.205" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="svc-latency-5101/svc-latency-rc-54bb7c7469-tkdzz"
2026-02-17 02:39:29.258 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.8eaf8bdfa03fabc46f09ed31bea26b6deee0bf691d174e8bddecef757fab54bd" ip="10.100.89.211" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="downward-api-1182/downwardapi-volume-1bfe279c-5e3a-4a71-aa57-367ad006e7ef"
2026-02-17 02:39:29.259 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.476655702c741cf81b909e3bde6c50995d9d241ffaad8c59998a4cd71137401b" ip="10.100.89.212" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="security-context-6177/security-context-f6f89d79-0633-4301-ac50-703013585ae3"
2026-02-17 02:39:29.259 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.148fb2c17c2d02c876348345391c9658eeb748e2773fe5bf9635f0506d331492" ip="10.100.89.207" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="container-runtime-56/terminate-cmd-rpac2d2dfbb-2b77-4813-9342-5d579bf7f6cf"
2026-02-17 02:39:33.263 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.860c283aa329d5096a6340d02130dc3066f1750df1ab026943559a2b299705b7" ip="10.100.89.213" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="projected-4699/pod-projected-secrets-0a087b08-06be-4c91-8b8f-ec3ea41e6f1f"
2026-02-17 02:39:33.264 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.48b1311c5d5bf0a4747075f162063a284f3a949e5b4d0641374cd7ab7f50748c" ip="10.100.89.214" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="container-runtime-3347/termination-message-container2abe98ca-873c-4431-81c3-7e781c0a16dc"
2026-02-17 02:39:56.813 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.45e1ed6e52b6281a9201fcc27363ec6885a3e80f0a2e5b345a644876dbc6bdb8" ip="10.100.89.222" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="proxy-4178/proxy-service-l74fp-79454c4f8-hpznd"
2026-02-17 02:39:56.814 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.37594c2b7d71a1a4a84d631a20e1cfc11f11b89b17897292e6b894210f8137ed" ip="10.100.89.219" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-8188/nodeport-test-6b4f5699b8-dcslc"
2026-02-17 02:39:56.814 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.46ebfedd774a78f355b48c324fa8f4a101acd4ec166bdd840e94ad222593a79e" ip="10.100.89.221" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-8188/execpodmsfsw"
2026-02-17 02:39:56.815 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.b1970ccaae2345726a02653c93e87569627e36e2861b6a393900615c5576491a" ip="10.100.3.26" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-8188/nodeport-test-6b4f5699b8-tm45f"
2026-02-17 02:40:14.848 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.5709f24c240d5abf371735b90622b9c15c04bd6b9f4f02f72efda618013b3e94" ip="10.100.89.220" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="aggregator-5374/sample-apiserver-deployment-5bc889656b-hg5cl"
2026-02-17 02:40:36.649 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.2eef2696a15cd02e5a78c398f9bd07b0c946cb1564b8632585aa6b2e2e8c2bbb" ip="10.100.89.228" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="replicaset-7064/test-rs-5lknb"
2026-02-17 02:40:55.067 [INFO][15] kube-controllers/hostendpoints.go 156: Running periodic HostEndpoint sync
2026-02-17 02:40:55.068 [INFO][15] kube-controllers/hostendpoints.go 259: Syncing all HostEndpoints
2026-02-17 02:40:55.068 [INFO][15] kube-controllers/loadbalancer_controller.go 252: Running periodic IPAM sync of Service LoadBalancer
2026-02-17 02:41:07.288 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.95172a40d3f50d68b06abc3ac345b4a2c6ef4a72a80628ffbe1582720a88cb30" ip="10.100.3.35" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="gc-1950/simpletest.rc-fzrkt"
2026-02-17 02:41:07.289 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.4c90f11cd3f50e179b7941b50ab21cefb3520a2fc4d058eda8d4bfc8336ed906" ip="10.100.89.235" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="gc-1950/simpletest.rc-pmj48"
2026-02-17 02:41:30.117 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.d6776232a28c68055d6dd3140706a02376a4847cffdc1c969d191da58cb15a93" ip="10.100.89.237" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="configmap-439/pod-configmaps-b2924af1-297c-48d2-82b5-4d6d949e82da"
2026-02-17 02:42:18.537 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.dbef6d0cf54a34305e7cc96ab1a759b30d313154f4bff5ad479e20ca5eabfda5" ip="10.100.3.39" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="dns-9677/dns-test-0f7b3ee4-de50-4ddb-b58d-3bce437dd84a"
2026-02-17 02:42:32.878 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.c11a86a6f77e10cc40c1d32a36345f1a77597b5fb82553aa08e3fa42b0b43953" ip="10.100.89.245" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="dns-8423/dns-test-36488143-714c-4e2e-aa10-5e74b15e1786"
2026-02-17 02:42:32.878 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.05d4935ed9892b4c0eba13bb8f3464e842120faafd7df4a31b415c764885b50f" ip="10.100.3.44" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="dns-8423/dns-test-e43d87c5-47d5-41b1-8f32-b1a152938fd3"
2026-02-17 02:42:32.878 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.ad65b4038efe1433dc2aab777788eb468c28143d8e433d63c145ff528ba87544" ip="10.100.3.38" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="dns-8423/dns-test-730a5f24-331c-416b-b413-e453816c2f90"
2026-02-17 02:42:44.048 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.6f0fd5b87e7f7424a41d48a038feaf2cf1f487db24423ca6827d208b1ecf0851" ip="10.100.3.48" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="emptydir-wrapper-3342/pod-secrets-be0116a9-d185-493f-baf8-830245335c08"
2026-02-17 02:42:57.046 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.11254938e2d3035e413f02b95325297263ad3dc323e72217a31eb0fa8f35ccec" ip="10.100.3.50" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="endpointslice-7501/pause-pod-0"
2026-02-17 02:42:57.046 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.bb85c25f95a301a58d0842feb55522eace669183200adf0b15713d532a5fd981" ip="10.100.3.49" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="endpointslice-7501/pod1-handle-http-request"
2026-02-17 02:42:57.046 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.39dca4e470ebd8739d9d4e3047f640fbe098169f68ca4e972c42ff7df602d8d1" ip="10.100.89.251" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="endpointslice-7501/pod2-handle-http-request"
2026-02-17 02:43:05.932 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.51874d65d913a2d57ab6e44106ed9099a7eaf6a163c7871fd86d04520cd43651" ip="10.100.89.252" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="replicaset-3944/my-hostname-basic-6185d154-c74d-4064-9e72-c00b7964c33b-f9l7g"
2026-02-17 02:43:16.970 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.10112814d77cf4915162aa684c2492fa43cee6abd70e79084c94646495a0e0e2" ip="10.100.3.57" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-6761/sample-webhook-deployment-7d44fffc8-4slqg"
2026-02-17 02:43:20.977 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.a7e2f2f3f8a5113b71dbbd8953e18bd6529f870f3389faa062e163da42dcd35e" ip="10.100.3.59" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="replication-controller-7996/pod-release-g8pb4"
2026-02-17 02:43:20.978 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.231cc1693c80491b8d9143d7fac65ac00f2fe399a445ceaaacc69363b8cf28e7" ip="10.100.89.254" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="replication-controller-7996/pod-release-bb7qc"
2026-02-17 02:43:25.066 [INFO][15] kube-controllers/ipam.go 298: Marking IPAM for full resync reason="periodic sync"
2026-02-17 02:43:25.066 [INFO][15] kube-controllers/ipam.go 795: Performing a full scan of IPAM allocations to check for leaks and redundant affinities
2026-02-17 02:43:35.013 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.f378fd304e187ef5ee45eee5d35403ff8006f0d8408237e61e51c850a44f3aa5" ip="10.100.89.255" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="replication-controller-5650/rc-test-796px"
2026-02-17 02:43:37.018 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.6c0afb29529aed0876895a3e535a86a94850697fceb74385e2384c3114e91622" ip="10.100.3.5" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="proxy-676/agnhost"
2026-02-17 02:43:42.206 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.e4eec905cf144989033885094f05fc0d6e7e591947d9595dd08b6e4e85b9a602" ip="10.100.3.9" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-2000/test-recreate-deployment-8574476ffd-8pzng"
2026-02-17 02:43:42.206 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.6688fb13341bedc748e09dadd3c3b575706fc9bd01aab5af4c344f4c46e4f364" ip="10.100.3.11" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-s6n5s"
2026-02-17 02:43:42.207 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.92645052affc9dad7224cc7bea10d6516c1c64e22e1617704d44ec869515b102" ip="10.100.3.3" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-fzphx"
2026-02-17 02:43:53.418 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.918b6c8b65af5ad26e48c80f0755f4cf4bd98c40d72ffb8d6603fd8ce371699c" ip="10.100.3.16" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-2000/test-recreate-deployment-68d5bd4dd9-2ttwr"
2026-02-17 02:43:56.499 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.1e4d6763a6fa69567be1584911dd6fdfb6f99cecd5bc6af81e936ad5fd89d205" ip="10.100.89.196" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-8788/webserver-deployment-6bc58496c7-vpx5x"
2026-02-17 02:43:56.499 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.91a7c1a6176bb073353992c44313408d180853e2e2008a59c30c5335eac54e25" ip="10.100.89.209" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-8788/webserver-deployment-6bc58496c7-mftb7"
2026-02-17 02:43:56.499 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.b9241c12a3b7dacfae51e40c5fbb4bad06fc9417316479d36106c85a6b8e5879" ip="10.100.89.212" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-8788/webserver-deployment-76fc67f65c-rg8hz"
2026-02-17 02:43:56.499 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.ba0ef1b4f77c1e5268f914265d9a12b8d51843e382b78d7d50c0552ae9986b07" ip="10.100.89.200" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-8788/webserver-deployment-6bc58496c7-g8nml"
2026-02-17 02:43:56.499 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.3bbea7fea4f2c8937f0e58ad19e9ed5ecb73dc171eb5ed3d41ad3d3f7fbb0a98" ip="10.100.89.195" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-8788/webserver-deployment-6bc58496c7-mzjpk"
2026-02-17 02:43:56.500 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.ce35ccc1b6f84f9decfd150f52bf4a75a122d6a53f667b27b03157dc3a8255da" ip="10.100.89.206" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-8788/webserver-deployment-6bc58496c7-j9ztk"
2026-02-17 02:43:56.500 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.80b0cccc52b92ffce98c672c7d268f403583df7e90279eda85b66bf763b59606" ip="10.100.89.211" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-8788/webserver-deployment-6bc58496c7-qj6kq"
2026-02-17 02:43:56.500 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.9cbb4ec1f2f2e5459ff8881152a8119ed3d600c1d0b2126e1d83a6c4ee14b8e4" ip="10.100.89.207" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-8788/webserver-deployment-76fc67f65c-fc52p"
2026-02-17 02:43:56.500 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.2b51d68647ec7fe5537b2b51bc192c3a786573932b31f2ff71217e2ee1c88aca" ip="10.100.89.208" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-8788/webserver-deployment-6bc58496c7-8nb67"
2026-02-17 02:43:56.500 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.f322392e766ba437ebee2ddfb45b632a8c22b3fa96b33a7a6c489f938adf1b95" ip="10.100.89.204" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-8788/webserver-deployment-76fc67f65c-ggxr5"
2026-02-17 02:43:56.501 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.f5ee2042f58b449bb9ab9dac6fb05d084ecc6ce674595f8d17b153ad3eb63a00" ip="10.100.89.205" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-8788/webserver-deployment-76fc67f65c-pb8z5"
2026-02-17 02:43:56.501 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.80df63c6767097549a381ba2d6df3d3058faef6c33eaaee97891e95c0754d26d" ip="10.100.3.14" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-76fc67f65c-9v7fz"
2026-02-17 02:43:56.501 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.cb885b1b32da01ed1d94bf9dcaf279c1754fd1d1d3fb79d497f72a72a3160af1" ip="10.100.3.7" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-df8hc"
2026-02-17 02:43:56.501 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.0f25c2b88b0d271fa943dc4dba2e20a65fd84ac4960e8572ccd99f8f96bb23d9" ip="10.100.3.26" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-76fc67f65c-rrx9c"
2026-02-17 02:43:56.501 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.316793fff1e16af5df66093ebf2acd8a10e61ece43f31a69fcbc8565f11b1624" ip="10.100.3.8" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-lm7sq"
2026-02-17 02:43:56.501 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.b2d974517a7be80b7f5192bbe5a4888463e722ae3faf7f030616413e7b172568" ip="10.100.3.10" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-76fc67f65c-f5f44"
2026-02-17 02:43:56.502 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.4efa74d35b156e58ce7dad92e7bf95659d9ac822f2ebd8318c9bf815a8e89e42" ip="10.100.3.18" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-mwbhq"
2026-02-17 02:43:56.502 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.ddf41f6c579c1e27e9c48cb7ae23d2a052511378a802792a18d6a96e4d45bce6" ip="10.100.3.19" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-ffcg8"
2026-02-17 02:43:56.502 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.37ab5768d424daf7dd2f75b6e5dd70b4faf24ac9e97650c4a58fa7dd6da09d76" ip="10.100.3.20" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-k9gkz"
2026-02-17 02:43:56.502 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.e28b0fc9daf0821fd8414a42e17e367132d9f9d3b88830f9e74014793d7f84c5" ip="10.100.3.22" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-76fc67f65c-zz9h2"
2026-02-17 02:43:56.502 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.d299b78374e6c47df7e4df8fab365acdb155380a4f770e25b435c9ceebdc11ff" ip="10.100.3.25" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-z8rtv"
2026-02-17 02:43:56.502 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.05a149ea825b89183aa61a639e7a2134284a71ae147bda7a8b429398ddacdf26" ip="10.100.3.6" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-8fcc9"
2026-02-17 02:43:56.503 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.ddb6b34ba280bdc236433eb37a153bced64295701f2e7b9449c74fbeea178be8" ip="10.100.3.13" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-76fc67f65c-l2wzs"
2026-02-17 02:43:56.503 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.a367d317ca1098bc1d8eec9df507e8dd0e45f5b91af89e14f4e634fefdcbcd4b" ip="10.100.3.17" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-5mlxt"
2026-02-17 02:43:56.503 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.edcc680780611815cad7448bf6a36418956a2262f61121adb40569c8629d28ee" ip="10.100.3.23" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-n2nvq"
2026-02-17 02:43:56.503 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.199c52638a4a627896b7b7d82b3803052fa384dc3edf4a1c262f796176249b27" ip="10.100.3.24" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-6bc58496c7-pptcj"
2026-02-17 02:43:56.503 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.176b6dc548180c28a140d045369dda39772c20bd59d76036cdee76d000119062" ip="10.100.3.21" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-76fc67f65c-8dshx"
2026-02-17 02:43:57.905 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.88bdc4635e1171f4c1e5ad19ceeb52e233feeb1ec9b5c3df96282b6aba2bed0d" ip="10.100.3.30" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-8788/webserver-deployment-76fc67f65c-nbr67"
2026-02-17 02:44:02.366 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.f791fcd03b8d2ad650c72f6ffce03f023522875260e4d2a431011e0e59a9c402" ip="10.100.3.27" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-5005/sample-webhook-deployment-7d44fffc8-skxpn"
2026-02-17 02:44:09.301 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.64a4a42b6093105a9e24450efb5f5d5d2ce35bf9d6c257cca852b654b6eba233" ip="10.100.3.34" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-7801/sample-webhook-deployment-7d44fffc8-j8th4"
2026-02-17 02:44:15.617 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.ca5b7432a3f19d7b10dd929a48003188d1e68c793605662810fd99e13642dfcc" ip="10.100.3.32" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="configmap-592/pod-configmaps-a1256d0c-cc4b-48f1-b0c1-5f1f4b19b70d"
2026-02-17 02:44:30.485 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.f38a7f3e1e4434ca78f28929b5d91cdea0e078d6ef275c443f634d4a71023a53" ip="10.100.3.37" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-3794/test-rollover-deployment-8fbb868dd-vsjsg"
2026-02-17 02:44:42.414 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.94cb5904b5d96ebf824d87797e3c4c0bc9c88955eb8ff3d0a9e002572e9b2797" ip="10.100.3.36" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="deployment-3794/test-rollover-controller-kkjhh"
2026-02-17 02:45:03.362 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.772e37ec1e20852de384e24696e29d1750638988036a32f1cf53088b5c53e75c" ip="10.100.89.221" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="dns-2634/dns-test-6c0c6f22-a119-4754-a76f-467af00ab226"
2026-02-17 02:45:03.362 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.a1b413e4c4ca9c718c9595a5601e099bca16ae10bba60bceb2a527b6db1b3ef1" ip="10.100.3.33" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="container-probe-8559/busybox-7078fbad-6c54-42bd-9ba0-a3f9e9d177cf"
2026-02-17 02:45:39.538 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.45907a58652e1d61533a2086482f1c4f1def25cc20229746ff7a62b579cf44e8" ip="10.100.3.40" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-2935/affinity-clusterip-transition-66686d5d57-cpg4g"
2026-02-17 02:45:39.538 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.c4e75b10bbc71cfaebddae79b29225f753979bc272057cd95fda4e990c6c6812" ip="10.100.3.39" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-2935/affinity-clusterip-transition-66686d5d57-cwvx7"
2026-02-17 02:45:39.538 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.6b1b577774a701d7708b8098df78e9b81120a0bdd54d0dfe99ff7f647055b3a3" ip="10.100.89.222" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-2935/affinity-clusterip-transition-66686d5d57-pdq99"
2026-02-17 02:45:49.838 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.807e0136c466d043920c0b84b7fecee101042ffda08d521bfc9b33d685d10831" ip="10.100.3.46" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-3248/sample-webhook-deployment-7d44fffc8-rdj8l"
2026-02-17 02:45:49.838 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.0a536ee13ec693371453ba77aec0d21408d7b1b3bc161360cf0456e234e0f7bf" ip="10.100.3.43" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-2221/sample-webhook-deployment-7d44fffc8-xdfss"
2026-02-17 02:45:55.023 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.60b7e09238935f730599af4ea5b4bb95a5b79562f8384b87f662e3897c5cfa30" ip="10.100.3.45" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-9991/sample-webhook-deployment-7d44fffc8-bbnxv"
2026-02-17 02:45:55.063 [INFO][15] kube-controllers/loadbalancer_controller.go 252: Running periodic IPAM sync of Service LoadBalancer
2026-02-17 02:45:55.066 [INFO][15] kube-controllers/hostendpoints.go 156: Running periodic HostEndpoint sync
2026-02-17 02:45:55.067 [INFO][15] kube-controllers/hostendpoints.go 259: Syncing all HostEndpoints
2026-02-17 02:46:00.746 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.cb831e515691be36180d2b10de9b0f02ce084d74a915ff781765945ddbbb2627" ip="10.100.3.48" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="replication-controller-1989/my-hostname-basic-ee5aa4e1-0044-43d2-b92a-4cce16595850-2k6tt"
2026-02-17 02:46:00.746 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.8af4eb9d0a2ee3634799f3f732326885f48c680ac970e12979044a948f0e67e9" ip="10.100.3.49" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="projected-1201/downwardapi-volume-85ad12ac-be66-4126-a96e-2c9229570564"
2026-02-17 02:46:07.358 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.aec69daca5e8b50c0fd3628c6b0ad30ba0a499cacc53def9062e41e8fe3c3aef" ip="10.100.3.53" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-1855/sample-webhook-deployment-7d44fffc8-bcc4p"
2026-02-17 02:46:37.813 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.91ef0f7ff959e5d94b3676d86ea882df738060d7b2fe448156a0f69d03871719" ip="10.100.3.54" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="replicaset-9098/test-rs-6kmzd"
2026-02-17 02:47:13.429 [INFO][15] kube-controllers/ipam.go 298: Marking IPAM for full resync reason="Batch node deletion"
2026-02-17 02:47:18.433 [INFO][15] kube-controllers/ipam.go 795: Performing a full scan of IPAM allocations to check for leaks and redundant affinities
2026-02-17 02:47:21.993 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.cae0085ad31721307d4c428b74add02ef9660a22327661ba02ce175dbee9b66f" ip="10.100.89.232" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="replicaset-1611/test-rs-7f2c6"
2026-02-17 02:47:21.993 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.35a7fee2640368d73694f1d9dcfa150525819c4508b7fe11094bf283a958a299" ip="10.100.3.9" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="replicaset-1611/test-rs-jzjrc"
2026-02-17 02:47:21.993 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.1ba323361b21987f3bdc20bb05800d69505b7bffaf809131dd831cbde146012b" ip="10.100.3.11" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="replicaset-1611/test-rs-mnfc2"
2026-02-17 02:48:09.589 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.8f7d4af5bf503fa2e8197add55a316121e76329efdc3c59397eec1904367e72e" ip="10.100.3.14" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="replicaset-810/test-rs-r2m2c"
2026-02-17 02:48:09.590 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.0f761c026d0397c3ab112a3075e2954e239b4aff750cb2eef2b576b612147f56" ip="10.100.3.25" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="replicaset-810/test-rs-dp6px"
2026-02-17 02:48:16.656 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.bb52c3a11d267b1b2f2e4277cce876cad5721c5c72e57a0882968ca75434e00d" ip="10.100.89.238" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="kubectl-2687/agnhost-primary-wzrzp"
2026-02-17 02:48:18.659 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.7aa06d2f8cef467e6b89054a0649efaa12bcf731a348c96850e1ac80c051e057" ip="10.100.89.240" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-1953/externalsvc-8664db8f97-bt2f8"
2026-02-17 02:48:18.659 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.9bd899bc2409fdbd18232886f7124847304aefc2244532c00752a19f14ebb97a" ip="10.100.3.18" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-1953/externalsvc-8664db8f97-hgsr7"
2026-02-17 02:48:58.104 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.7991a85f954b5fed1b10dd7faee74c97404625bff971e273dd71e3d0bdbbf6f7" ip="10.100.3.37" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-134/pod1"
2026-02-17 02:49:05.562 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.39864bcb68143a74ab3c40f1ab6d4cb8eee2bc0cfe943332027b615ca9436209" ip="10.100.3.36" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-134/execpodgj7gr"
2026-02-17 02:49:12.989 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.7fc8cf074dfa5397e8e80954ec0a3660b48638755bb22912a4c12396cf720f12" ip="10.100.3.28" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="gc-6317/simpletest.deployment-58dd7ccf6f-c2rr7"
2026-02-17 02:49:12.989 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.3476eb291181650d4002bc6c7d7e997db4a6de2ca828ceae709d3e44a3fde6c7" ip="10.100.89.194" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="gc-6317/simpletest.deployment-58dd7ccf6f-m68th"
2026-02-17 02:49:16.156 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.391ee2a776fc429e1a4eb3b9597c0841fd96901aa30ed1af91a91cdd3557fcd9" ip="10.100.3.38" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="svcaccounts-7572/pod-service-account-mountsa-nomountspec"
2026-02-17 02:49:16.156 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.56479bbfd34ea934b06cff31b8645d33a00c4fc6dc958970b45b85813df24346" ip="10.100.3.44" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="kubectl-1708/update-demo-nautilus-gxdpd"
2026-02-17 02:49:16.157 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.0b76470a534fc8c347bb54b9276407393316b864bdfba0ee42a7d1325b13a0d7" ip="10.100.3.40" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="svcaccounts-7572/pod-service-account-nomountsa-nomountspec"
2026-02-17 02:49:18.158 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.9c5b0452e711d695173d1de5b0778c1c5723623990150bdf66446f8f6d761860" ip="10.100.3.39" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="job-9833/with-backoff-limit-per-index-1-vbz9z"
2026-02-17 02:49:25.836 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.f4bb1ab83983cbf21f8ea015a7ab91576e26f40bf43f62a479a55d32e700f695" ip="10.100.3.43" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="kubectl-1708/update-demo-nautilus-7m2tf"
2026-02-17 02:49:25.836 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.6985304324b0b63a0944df705fa241c16f5b98321c5b10f945a81bf5fc217c9d" ip="10.100.89.196" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="downward-api-6127/downward-api-3e8a94cd-02e8-4427-8711-1828f14e4232"
2026-02-17 02:49:27.841 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.1550fca14baba36a12d9ef967f353ccde9810219d682e6b7062db5ec52613357" ip="10.100.3.45" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="dns-4402/dns-test-ab0ec3db-3d2d-4f82-9e6e-f729a629fae7"
2026-02-17 02:49:36.944 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.7accb484de0b5d6980795813561b319c7b323333b93c7090c026efe9635cb120" ip="10.100.3.49" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-3054/sample-webhook-deployment-7d44fffc8-v47vh"
2026-02-17 02:49:41.830 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.302b0c2b7867c6561d42edd1348c27d100e2011e34637440672cd32d8de763e9" ip="10.100.3.48" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="kubectl-4089/pause"
2026-02-17 02:49:45.340 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.0c3be81567f3466e232f0cd9218a72d3827b77ed15b3d799f282f7e2ea21e3f1" ip="10.100.3.55" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-5423/sample-webhook-deployment-7d44fffc8-2682r"
2026-02-17 02:50:16.639 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.e037d6c8214a9fd45cbf9d0256894a29b5efcf39150bd71132aa4294268dd5be" ip="10.100.3.53" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-202/affinity-nodeport-transition-5794c6cd75-q6nf2"
2026-02-17 02:50:16.639 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.205d5eae8d0d1e43ca7a5dc92a227641861ef1e4e17dca2ffdd6a0d4f336502d" ip="10.100.3.50" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-202/execpod-affinityj2g4q"
2026-02-17 02:50:16.639 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.734c6f51a59de42fb1d97a8f172e46b50f5cc50f3b58b524bc3e5941673675e7" ip="10.100.3.47" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-202/affinity-nodeport-transition-5794c6cd75-cgnfd"
2026-02-17 02:50:17.640 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.93cd05903cf4dc14ea45d57920d236e0020d8537e7d6a43c0ebb87b7ad78072b" ip="10.100.89.208" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-202/affinity-nodeport-transition-5794c6cd75-z2fg7"
2026-02-17 02:50:31.957 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.dc41f79377474db32c526493d74e64f6fe96f759ef44f68d633d37f6513845da" ip="10.100.3.56" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="container-lifecycle-hook-3534/pod-handle-http-request"
2026-02-17 02:50:55.063 [INFO][15] kube-controllers/loadbalancer_controller.go 252: Running periodic IPAM sync of Service LoadBalancer
2026-02-17 02:50:55.066 [INFO][15] kube-controllers/ipam.go 298: Marking IPAM for full resync reason="periodic sync"
2026-02-17 02:50:55.066 [INFO][15] kube-controllers/ipam.go 795: Performing a full scan of IPAM allocations to check for leaks and redundant affinities
2026-02-17 02:50:55.066 [INFO][15] kube-controllers/hostendpoints.go 156: Running periodic HostEndpoint sync
2026-02-17 02:50:55.067 [INFO][15] kube-controllers/hostendpoints.go 259: Syncing all HostEndpoints
2026-02-17 02:51:10.854 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.8606b9d1bf0121cb0780c80bda0aa49e98204d8da1a201f8d6d029b039baa900" ip="10.100.3.12" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="container-probe-4114/busybox-fc55d7ee-58fb-4e41-9714-e337833004e2"
2026-02-17 02:51:45.538 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.2338038c06e460c8e4292fc7cc1133327acc6f0e448f86faee17e77f1b37a59d" ip="10.100.89.221" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-4375/execpodlrhdx"
2026-02-17 02:51:45.538 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.e073ac4b6f15f7db23e6a0f0ce5381102de08bd1f28a916975180ab8d31ce934" ip="10.100.89.218" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-4375/externalname-service-64f6c89d45-745xz"
2026-02-17 02:51:45.539 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.645166dc0e64d3d2a5b18543ffc6ed6c89b6f844e427cb46adb39a8f567f4635" ip="10.100.3.61" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-4375/externalname-service-64f6c89d45-vbgsk"
2026-02-17 02:51:53.758 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.4c63ff9649695135b23070a13b32179537d450a52d9970c86ca85c3385068ea0" ip="10.100.89.223" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="webhook-4783/sample-webhook-deployment-7d44fffc8-m9fwz"
2026-02-17 02:51:58.648 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.f0f299dd5b00cc98a945636b6bbe4e2c0a29f78fc97706a96e3a0855ae943743" ip="10.100.89.222" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="security-context-1591/security-context-959f55c6-f19e-4ae8-a32e-444e73944185"
2026-02-17 02:52:17.957 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.c72076213f4c402aba02a474beb064cb1406e5d61bc35a36f2429d7d9918e7e8" ip="10.100.89.232" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="pods-6948/pod-test"
2026-02-17 02:52:23.962 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.355fa039c301b7f4ac6b593376a6db6d7c2c07ad63690f9b426e719d82f25569" ip="10.100.3.19" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="dns-1201/dns-test-8e2b8283-1cbc-4888-b54a-2f4194839d17"
2026-02-17 02:52:28.631 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.f9565bf872aa63e6d902fa2e621b784dde6402651c758a0108c983b68eb21f11" ip="10.100.89.226" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="crd-webhook-1367/sample-crd-conversion-webhook-deployment-788cb954bd-hxhhx"
2026-02-17 02:52:45.045 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.270be576288c5aceda328d78294f6a35d281209bf04b9a965edc21b6f11ddfc1" ip="10.100.3.20" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-7151/affinity-nodeport-65758f6cfc-vt6x7"
2026-02-17 02:52:45.046 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.cff97d1f03f3cacc65ab9b6bc442b37cb7e512040f60f042d52b948a422c2895" ip="10.100.3.26" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-7151/affinity-nodeport-65758f6cfc-qz5ng"
2026-02-17 02:52:52.947 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.a2b68a5ece191861368140f8bdd0f4d6404959af9735d474e5a01f8a9387c12e" ip="10.100.3.23" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="crd-selectable-fields-4569/sample-crd-conversion-webhook-deployment-788cb954bd-vcdsc"
2026-02-17 02:53:03.619 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.0fa62ab10e580ecb20935a56deada82fa760082f890e1b0608fd69c0a472fdc8" ip="10.100.3.8" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-8029/affinity-clusterip-5d4d4bb77f-mkcfl"
2026-02-17 02:53:03.620 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.2ab81d3252e45725808affe825a383186d8c38fb6ec88796fb1d9cd62eaa1106" ip="10.100.3.7" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-8029/execpod-affinitygsr5k"
2026-02-17 02:53:03.620 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.14c940bdb3badfa7b12a0589f193be3a406fe1ff7c59e3184e1b46bcb9e047c2" ip="10.100.89.230" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-8029/affinity-clusterip-5d4d4bb77f-v56cf"
2026-02-17 02:53:03.620 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.5ce3cb84034750e4e720d1c76057b370dc4e9ef30e7550a198de0163c9785de0" ip="10.100.89.237" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-8029/affinity-clusterip-5d4d4bb77f-wb5pc"
2026-02-17 02:53:26.500 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.bdc7ad71b37c7fff4fdbfbaea3bf6cb4495868bb67d43de94216e7d563a8a714" ip="10.100.3.22" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="dns-3910/dns-test-96a1d269-c687-48c2-930b-ddb3e032b7d7"
2026-02-17 02:53:57.975 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.ea2dd0a7db163519605225780ed8e99d9f14e583cea859f08fff78cf1604553c" ip="10.100.3.37" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="emptydir-9455/pod-sharedvolume-cd221168-d6e0-45a9-a7ea-9cf8fc889312"
2026-02-17 02:55:55.063 [INFO][15] kube-controllers/loadbalancer_controller.go 252: Running periodic IPAM sync of Service LoadBalancer
2026-02-17 02:55:55.067 [INFO][15] kube-controllers/hostendpoints.go 156: Running periodic HostEndpoint sync
2026-02-17 02:55:55.067 [INFO][15] kube-controllers/hostendpoints.go 259: Syncing all HostEndpoints
2026-02-17 02:58:25.070 [INFO][15] kube-controllers/ipam.go 298: Marking IPAM for full resync reason="periodic sync"
2026-02-17 02:58:25.070 [INFO][15] kube-controllers/ipam.go 795: Performing a full scan of IPAM allocations to check for leaks and redundant affinities
2026-02-17 02:59:21.877 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.5d9cb69cc1e37bba10b9bc0d2d1a6a438df15cd78c6e215a153be8a7f69bc4e8" ip="10.100.89.245" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-5684/externalname-service-79bbf54494-nrhf2"
2026-02-17 02:59:21.877 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.0bb5be5bdbb08a2e20415429dacc7957f88e754d542dbc70b2724bac8492e88a" ip="10.100.89.252" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-5684/execpodjz45x"
2026-02-17 02:59:21.877 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.061699dad54c22f8102c413747e3b02e942be99b11fd9b7a545e4838fc4e286e" ip="10.100.3.46" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="pods-8549/client-envvars-9be91a46-2704-425e-b478-4166dd35dc96"
2026-02-17 02:59:21.877 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.15ffafbb0075d3c1349c15290bcecdace2540a2d3eb5512ae5a57d725a06ae67" ip="10.100.3.44" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="services-5684/externalname-service-79bbf54494-zln4l"
2026-02-17 02:59:41.963 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.53df9718ef0e5f9decbd2ba75b342a4c8ef5b8c84536fd23d5c54ce3df51eb79" ip="10.100.3.45" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="var-expansion-8690/var-expansion-beeebc69-ef40-4eaf-9e9f-f542ea8046c5"
2026-02-17 02:59:44.281 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.8394e05a9d903c07f43ea58c81c7198d943681830f78de8ac061268618e1480e" ip="10.100.89.249" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="container-probe-7706/liveness-3ceb3d26-bd21-4806-9c21-c0cfb02c4059"
2026-02-17 03:00:12.499 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.d24ca79858eb73acf1051203fcb3ce57338dcfab8260521ebb1d5ef8a25e6070" ip="10.100.3.51" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="container-lifecycle-hook-6931/pod-handle-http-request"
2026-02-17 03:00:28.336 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.18100fa31bdbf0442cea04c5541805c6ec75235762cdac757f7e8cccf2968db2" ip="10.100.3.55" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="projected-7290/pod-projected-configmaps-100e9884-9213-42fe-b626-61761bffb9d1"
2026-02-17 03:00:33.436 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.1f1c514e395f57b31c7e761db50d24b3216dae598798ef83a805b262f4d1cb03" ip="10.100.89.198" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="services-2664/pod1"
2026-02-17 03:00:44.878 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.6b2d041413cb178a48e2785b2c3a9a750b74a18df8ca7e0f74724e933dc9b2c8" ip="10.100.3.52" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="dns-7654/dns-test-b1cc945c-d8a5-4292-9c1a-ebcdccdf578f"
2026-02-17 03:00:48.208 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.129da7b3eba9a5e7da17cba5380e97769b565c8443dbcad67f99c1bd8122f779" ip="10.100.3.12" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="svcaccounts-3641/pod-service-account-78f3ff37-c650-4fe9-bbdf-03e17c6133c4"
2026-02-17 03:00:48.209 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.ac172209b2bec3970f4848edfcda65798201f8db2d2d7dc55d7d316a9838be76" ip="10.100.3.63" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="statefulset-6154/test-pod"
2026-02-17 03:00:55.066 [INFO][15] kube-controllers/hostendpoints.go 156: Running periodic HostEndpoint sync
2026-02-17 03:00:55.067 [INFO][15] kube-controllers/hostendpoints.go 259: Syncing all HostEndpoints
2026-02-17 03:00:55.694 [INFO][15] kube-controllers/loadbalancer_controller.go 252: Running periodic IPAM sync of Service LoadBalancer
2026-02-17 03:00:56.104 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.e573b0504b61ee0a1316a736591a393d218bd96a8b916efa84e48949d60b2fc2" ip="10.100.3.61" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-8904/sample-webhook-deployment-7d44fffc8-r7q2w"
2026-02-17 03:01:06.687 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.7f00a05ab9f18ecfe7f0b28112eef78a1f60ada8633edbe3bccaee345dc2134d" ip="10.100.3.5" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="webhook-3358/to-be-attached-pod"
2026-02-17 03:01:31.724 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.8f42c72a9e60c5e9b0e669eeae00f1e92dd12f640714bb7304e0098138ae8e32" ip="10.100.89.205" node="kube-xv3bi-default-worker-6rwhs-g6z6l-cltcq" pod="deployment-9886/test-deployment-dcwpb-6dcdd4444f-wnrmw"
2026-02-17 03:01:36.352 [INFO][15] kube-controllers/ipam_allocation.go 176: Candidate IP leak handle="k8s-pod-network.4c94de86c00f741fd55aee6d044f49a5a1ca594d038a926925bae5f64d3f44fb" ip="10.100.3.59" node="kube-xv3bi-default-worker-6rwhs-g6z6l-kpmxt" pod="statefulset-1776/ss2-1"
