apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:55:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-16-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-16.us-east-2.compute.internal uid: 07b1bff6-5abe-41e7-9ade-f132dd6145fb resourceVersion: "116765" uid: e6fcfc6d-13a8-430f-b3de-d3ceb53ae0f7 spec: sourcePod: network-check-source-6f78d59f99-rw5ms targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T00:02:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.420318ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:21Z" - latency: 1.167595ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:21Z" - latency: 941.883µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:21Z" - latency: 1.644835ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:21Z" - latency: 920.827µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:21Z" - latency: 1.119885ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:21Z" - latency: 1.348873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:21Z" - latency: 959.707µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:21Z" - latency: 960.663µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:43:21Z" - latency: 1.469187ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:42:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:55:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-16-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-16.us-east-2.compute.internal uid: 07b1bff6-5abe-41e7-9ade-f132dd6145fb resourceVersion: "120353" uid: a69909f7-1408-4be4-9f12-079656983978 spec: sourcePod: network-check-source-6f78d59f99-rw5ms targetEndpoint: a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T00:25:22Z" message: 'load-balancer-api-external: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable failures: - latency: 11.467357317s message: 'load-balancer-api-external: failure looking up host a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: dial tcp: lookup a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T00:22:33Z" outages: - end: "2026-10-31T00:23:27Z" endLogs: - latency: 5.035014ms message: 'load-balancer-api-external: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:23:27Z" - latency: 11.467357317s message: 'load-balancer-api-external: failure looking up host a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: dial tcp: lookup a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T00:22:33Z" message: Connectivity restored after 53.885459769s start: "2026-10-31T00:22:33Z" startLogs: - latency: 11.467357317s message: 'load-balancer-api-external: failure looking up host a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: dial tcp: lookup a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T00:22:33Z" successes: - latency: 5.187746ms message: 'load-balancer-api-external: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:55:21Z" - latency: 6.939936ms message: 'load-balancer-api-external: resolved host name a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:55:21Z" - latency: 6.269319ms message: 'load-balancer-api-external: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:54:21Z" - latency: 6.836533ms message: 'load-balancer-api-external: resolved host name a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:54:21Z" - latency: 4.139288ms message: 'load-balancer-api-external: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:53:21Z" - latency: 6.736769ms message: 'load-balancer-api-external: resolved host name a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:53:21Z" - latency: 5.270587ms message: 'load-balancer-api-external: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:21Z" - latency: 8.145854ms message: 'load-balancer-api-external: resolved host name a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:52:21Z" - latency: 6.391618ms message: 'load-balancer-api-external: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:21Z" - latency: 6.296154ms message: 'load-balancer-api-external: resolved host name a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:51:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:55:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-16-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-16.us-east-2.compute.internal uid: 07b1bff6-5abe-41e7-9ade-f132dd6145fb resourceVersion: "120352" uid: 37bcbd91-91f1-4a12-b7e7-106e4118ad46 spec: sourcePod: network-check-source-6f78d59f99-rw5ms targetEndpoint: a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T00:25:22Z" message: 'load-balancer-api-internal: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable failures: - latency: 11.201078896s message: 'load-balancer-api-internal: failure looking up host a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: dial tcp: lookup a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T00:22:33Z" outages: - end: "2026-10-31T00:23:27Z" endLogs: - latency: 5.18853ms message: 'load-balancer-api-internal: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:23:27Z" - latency: 11.201078896s message: 'load-balancer-api-internal: failure looking up host a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: dial tcp: lookup a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T00:22:33Z" message: Connectivity restored after 53.639556664s start: "2026-10-31T00:22:33Z" startLogs: - latency: 11.201078896s message: 'load-balancer-api-internal: failure looking up host a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: dial tcp: lookup a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T00:22:33Z" successes: - latency: 5.198219ms message: 'load-balancer-api-internal: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:55:21Z" - latency: 6.885094ms message: 'load-balancer-api-internal: resolved host name a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:55:21Z" - latency: 6.306337ms message: 'load-balancer-api-internal: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:54:21Z" - latency: 6.793866ms message: 'load-balancer-api-internal: resolved host name a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:54:21Z" - latency: 4.12583ms message: 'load-balancer-api-internal: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:53:21Z" - latency: 6.680778ms message: 'load-balancer-api-internal: resolved host name a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:53:21Z" - latency: 5.313857ms message: 'load-balancer-api-internal: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:21Z" - latency: 8.060554ms message: 'load-balancer-api-internal: resolved host name a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:52:21Z" - latency: 6.27868ms message: 'load-balancer-api-internal: tcp connection to a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:21Z" - latency: 6.264139ms message: 'load-balancer-api-internal: resolved host name a5329a66560b8421d8d01ecdc700f33d-e49c6fec5a6c94eb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:51:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:55:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-16-to-network-check-target-ip-10-0-130-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-16.us-east-2.compute.internal uid: 07b1bff6-5abe-41e7-9ade-f132dd6145fb resourceVersion: "116764" uid: 1924b4d8-f0ad-4087-b72b-8f6d2cd54446 spec: sourcePod: network-check-source-6f78d59f99-rw5ms targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:02:21Z" message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.368184ms message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:21Z" - latency: 2.152158ms message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:21Z" - latency: 1.96488ms message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:21Z" - latency: 2.329655ms message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:21Z" - latency: 1.88737ms message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:21Z" - latency: 2.2875ms message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:21Z" - latency: 2.418358ms message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:21Z" - latency: 2.31676ms message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:21Z" - latency: 1.939832ms message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:43:21Z" - latency: 2.009694ms message: 'network-check-target-ip-10-0-130-152: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:42:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:55:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-16-to-network-check-target-ip-10-0-134-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-16.us-east-2.compute.internal uid: 07b1bff6-5abe-41e7-9ade-f132dd6145fb resourceVersion: "116763" uid: b1bc8aaa-6f5f-4e4b-a229-8ec1d5c59601 spec: sourcePod: network-check-source-6f78d59f99-rw5ms targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:02:21Z" message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.082362ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:21Z" - latency: 2.601536ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:21Z" - latency: 1.946148ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:21Z" - latency: 2.058644ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:21Z" - latency: 2.44279ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:21Z" - latency: 2.498171ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:21Z" - latency: 2.372543ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:21Z" - latency: 2.055933ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:21Z" - latency: 2.199678ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:43:21Z" - latency: 1.944941ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:42:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:55:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-16-to-network-check-target-ip-10-0-143-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-16.us-east-2.compute.internal uid: 07b1bff6-5abe-41e7-9ade-f132dd6145fb resourceVersion: "116762" uid: 4050ea24-a878-43d5-b10e-2d3466958e62 spec: sourcePod: network-check-source-6f78d59f99-rw5ms targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:02:21Z" message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.356µs message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:21Z" - latency: 1.577926ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:21Z" - latency: 1.004046ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:21Z" - latency: 859.258µs message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:21Z" - latency: 990.7µs message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:21Z" - latency: 1.300089ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:21Z" - latency: 1.157983ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:21Z" - latency: 1.123669ms message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:21Z" - latency: 933.549µs message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:43:21Z" - latency: 854.637µs message: 'network-check-target-ip-10-0-143-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:42:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T23:55:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-16-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-16.us-east-2.compute.internal uid: 07b1bff6-5abe-41e7-9ade-f132dd6145fb resourceVersion: "120351" uid: 70b08ec1-5fd4-4c73-a282-17e65af66681 spec: sourcePod: network-check-source-6f78d59f99-rw5ms targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T00:25:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable failures: - latency: 11.256453739s message: 'network-check-target-service-cluster: failure looking up host network-check-target: dial tcp: lookup network-check-target: i/o timeout' reason: DNSError success: false time: "2026-10-31T00:22:33Z" outages: - end: "2026-10-31T00:23:27Z" endLogs: - latency: 1.212775ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:23:27Z" - latency: 11.256453739s message: 'network-check-target-service-cluster: failure looking up host network-check-target: dial tcp: lookup network-check-target: i/o timeout' reason: DNSError success: false time: "2026-10-31T00:22:33Z" message: Connectivity restored after 53.635320927s start: "2026-10-31T00:22:33Z" startLogs: - latency: 11.256453739s message: 'network-check-target-service-cluster: failure looking up host network-check-target: dial tcp: lookup network-check-target: i/o timeout' reason: DNSError success: false time: "2026-10-31T00:22:33Z" successes: - latency: 1.131834ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:55:21Z" - latency: 1.847902ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:55:21Z" - latency: 958.997µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:54:21Z" - latency: 1.796973ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:54:21Z" - latency: 1.022421ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:53:21Z" - latency: 1.74355ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:53:21Z" - latency: 985.767µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:21Z" - latency: 2.143884ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:52:21Z" - latency: 1.430224ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:21Z" - latency: 1.810678ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:51:21Z" kind: List metadata: resourceVersion: ""