apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:21:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-116-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-116.us-east-2.compute.internal
      uid: 98791372-9d24-4c40-81ed-c96b8e1c6938
    resourceVersion: "177750"
    uid: 93dd09f4-7097-49e1-b93b-8303af81ceda
  spec:
    sourcePod: network-check-source-6f78d59f99-l84pf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:28:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.2786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:24:33Z"
    - latency: 1.222512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:23:33Z"
    - latency: 1.144442ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:22:33Z"
    - latency: 1.571589ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:21:33Z"
    - latency: 2.546752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:20:33Z"
    - latency: 1.286473ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:19:33Z"
    - latency: 1.029665ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:18:33Z"
    - latency: 1.378764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:17:33Z"
    - latency: 1.108736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:16:33Z"
    - latency: 946.859µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:15:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:21:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-116-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-116.us-east-2.compute.internal
      uid: 98791372-9d24-4c40-81ed-c96b8e1c6938
    resourceVersion: "183456"
    uid: f685677b-64eb-4a70-a177-125d957e6989
  spec:
    sourcePod: network-check-source-6f78d59f99-l84pf
    targetEndpoint: a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:27:33Z"
      message: 'load-balancer-api-external: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.180188ms
      message: 'load-balancer-api-external: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:27:33Z"
    - latency: 6.921826ms
      message: 'load-balancer-api-external: resolved host name a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:27:33Z"
    - latency: 6.369428ms
      message: 'load-balancer-api-external: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:26:33Z"
    - latency: 6.773331ms
      message: 'load-balancer-api-external: resolved host name a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:26:33Z"
    - latency: 5.645693ms
      message: 'load-balancer-api-external: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:25:33Z"
    - latency: 7.559044ms
      message: 'load-balancer-api-external: resolved host name a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:25:33Z"
    - latency: 6.390471ms
      message: 'load-balancer-api-external: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:24:33Z"
    - latency: 7.806527ms
      message: 'load-balancer-api-external: resolved host name a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:24:33Z"
    - latency: 4.115219ms
      message: 'load-balancer-api-external: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:23:33Z"
    - latency: 6.479065ms
      message: 'load-balancer-api-external: resolved host name a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:23:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:21:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-116-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-116.us-east-2.compute.internal
      uid: 98791372-9d24-4c40-81ed-c96b8e1c6938
    resourceVersion: "183457"
    uid: 4067bc99-aed9-449c-9260-e43484bd74b5
  spec:
    sourcePod: network-check-source-6f78d59f99-l84pf
    targetEndpoint: a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:27:33Z"
      message: 'load-balancer-api-internal: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.249869ms
      message: 'load-balancer-api-internal: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:27:33Z"
    - latency: 6.944982ms
      message: 'load-balancer-api-internal: resolved host name a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:27:33Z"
    - latency: 6.351925ms
      message: 'load-balancer-api-internal: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:26:33Z"
    - latency: 6.700374ms
      message: 'load-balancer-api-internal: resolved host name a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:26:33Z"
    - latency: 6.189874ms
      message: 'load-balancer-api-internal: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:25:33Z"
    - latency: 7.535634ms
      message: 'load-balancer-api-internal: resolved host name a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:25:33Z"
    - latency: 5.635031ms
      message: 'load-balancer-api-internal: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:24:33Z"
    - latency: 7.877988ms
      message: 'load-balancer-api-internal: resolved host name a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:24:33Z"
    - latency: 4.080615ms
      message: 'load-balancer-api-internal: tcp connection to a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:23:33Z"
    - latency: 6.522825ms
      message: 'load-balancer-api-internal: resolved host name a007464b4d36445698c3d48b16618e86-3c06c76dc4d5d9fa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:23:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:21:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-116-to-network-check-target-ip-10-0-131-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-116.us-east-2.compute.internal
      uid: 98791372-9d24-4c40-81ed-c96b8e1c6938
    resourceVersion: "177748"
    uid: 8a8c3ca6-b74c-450a-9895-0e9c8e5b26e5
  spec:
    sourcePod: network-check-source-6f78d59f99-l84pf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:28:33Z"
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.238501ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:24:33Z"
    - latency: 2.267954ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:23:33Z"
    - latency: 2.013195ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:22:33Z"
    - latency: 2.254485ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:21:33Z"
    - latency: 3.92844ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:20:33Z"
    - latency: 2.347748ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:19:33Z"
    - latency: 2.043705ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:18:33Z"
    - latency: 2.181596ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:17:33Z"
    - latency: 2.060047ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:16:33Z"
    - latency: 2.118262ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:15:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:21:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-116-to-network-check-target-ip-10-0-138-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-116.us-east-2.compute.internal
      uid: 98791372-9d24-4c40-81ed-c96b8e1c6938
    resourceVersion: "177749"
    uid: 2f91256f-efd1-4822-9530-715f7ffdebf9
  spec:
    sourcePod: network-check-source-6f78d59f99-l84pf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:28:33Z"
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.16618ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:24:33Z"
    - latency: 2.087026ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:23:33Z"
    - latency: 2.40791ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:22:33Z"
    - latency: 1.936969ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:21:33Z"
    - latency: 3.407184ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:20:33Z"
    - latency: 2.120379ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:19:33Z"
    - latency: 1.949431ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:18:33Z"
    - latency: 2.651137ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:17:33Z"
    - latency: 1.87716ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:16:33Z"
    - latency: 1.785629ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:15:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:21:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-116-to-network-check-target-ip-10-0-142-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-116.us-east-2.compute.internal
      uid: 98791372-9d24-4c40-81ed-c96b8e1c6938
    resourceVersion: "177747"
    uid: d03b4794-7f48-4fd5-8445-7af030c02efb
  spec:
    sourcePod: network-check-source-6f78d59f99-l84pf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:28:33Z"
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 945.659µs
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:24:33Z"
    - latency: 1.295327ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:23:33Z"
    - latency: 1.556646ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:22:33Z"
    - latency: 779.72µs
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:21:33Z"
    - latency: 3.142274ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:20:33Z"
    - latency: 972.321µs
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:19:33Z"
    - latency: 1.007186ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:18:33Z"
    - latency: 1.01317ms
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:17:33Z"
    - latency: 949.541µs
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:16:33Z"
    - latency: 966.46µs
      message: 'network-check-target-ip-10-0-142-116: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:15:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:21:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-116-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-116.us-east-2.compute.internal
      uid: 98791372-9d24-4c40-81ed-c96b8e1c6938
    resourceVersion: "183455"
    uid: 22a6d7cc-f5f0-4665-90b6-daf97795d7bb
  spec:
    sourcePod: network-check-source-6f78d59f99-l84pf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:27:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.070925ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:27:33Z"
    - latency: 1.551971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:27:33Z"
    - latency: 1.108652ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:26:33Z"
    - latency: 1.814684ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:26:33Z"
    - latency: 1.090608ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:25:33Z"
    - latency: 2.043756ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:25:33Z"
    - latency: 1.446797ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:24:33Z"
    - latency: 1.827138ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:24:33Z"
    - latency: 1.050145ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:23:33Z"
    - latency: 1.960645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:23:33Z"
kind: List
metadata:
  resourceVersion: ""