apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:16:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: cbb7cae2-3d7d-4843-829f-7204fbd4084c
    resourceVersion: "30513"
    uid: a3107e77-9fa3-4308-a5ab-95c6e296bd3c
  spec:
    sourcePod: network-check-source-7cbc45fddc-mc9hh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:23: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.479866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:33Z"
    - latency: 832.575µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:33Z"
    - latency: 1.167711ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:33Z"
    - latency: 967.658µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:33Z"
    - latency: 1.136596ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:33Z"
    - latency: 1.438564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:33Z"
    - latency: 1.024551ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:33Z"
    - latency: 1.124165ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:33Z"
    - latency: 1.200721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:33Z"
    - latency: 1.200721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:16:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: cbb7cae2-3d7d-4843-829f-7204fbd4084c
    resourceVersion: "29641"
    uid: 5d012ce9-365f-42a6-930c-070be5488070
  spec:
    sourcePod: network-check-source-7cbc45fddc-mc9hh
    targetEndpoint: a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:22:33Z"
      message: 'load-balancer-api-external: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.889292ms
      message: 'load-balancer-api-external: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:33Z"
    - latency: 8.304203ms
      message: 'load-balancer-api-external: resolved host name a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:41:33Z"
    - latency: 7.24597ms
      message: 'load-balancer-api-external: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:33Z"
    - latency: 6.485651ms
      message: 'load-balancer-api-external: resolved host name a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:40:33Z"
    - latency: 5.377705ms
      message: 'load-balancer-api-external: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:33Z"
    - latency: 8.849856ms
      message: 'load-balancer-api-external: resolved host name a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:39:33Z"
    - latency: 3.237843ms
      message: 'load-balancer-api-external: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:33Z"
    - latency: 6.947473ms
      message: 'load-balancer-api-external: resolved host name a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:38:33Z"
    - latency: 3.900058ms
      message: 'load-balancer-api-external: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:33Z"
    - latency: 6.908133ms
      message: 'load-balancer-api-external: resolved host name a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:16:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: cbb7cae2-3d7d-4843-829f-7204fbd4084c
    resourceVersion: "29640"
    uid: 4538579e-d9cf-4dbd-9f27-353259108400
  spec:
    sourcePod: network-check-source-7cbc45fddc-mc9hh
    targetEndpoint: a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:22:33Z"
      message: 'load-balancer-api-internal: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.497857ms
      message: 'load-balancer-api-internal: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:33Z"
    - latency: 8.218391ms
      message: 'load-balancer-api-internal: resolved host name a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:41:33Z"
    - latency: 8.187793ms
      message: 'load-balancer-api-internal: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:33Z"
    - latency: 6.395353ms
      message: 'load-balancer-api-internal: resolved host name a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:40:33Z"
    - latency: 5.436753ms
      message: 'load-balancer-api-internal: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:33Z"
    - latency: 8.875657ms
      message: 'load-balancer-api-internal: resolved host name a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:39:33Z"
    - latency: 4.571553ms
      message: 'load-balancer-api-internal: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:33Z"
    - latency: 6.987737ms
      message: 'load-balancer-api-internal: resolved host name a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:38:33Z"
    - latency: 14.120155ms
      message: 'load-balancer-api-internal: tcp connection to a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:33Z"
    - latency: 6.864882ms
      message: 'load-balancer-api-internal: resolved host name a9384569567024149a386871a3167c8d-f03daf81e58c2ac6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:16:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-ip-10-0-129-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: cbb7cae2-3d7d-4843-829f-7204fbd4084c
    resourceVersion: "30510"
    uid: 593c7753-4335-4889-bbc9-0400f13ce484
  spec:
    sourcePod: network-check-source-7cbc45fddc-mc9hh
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:23:33Z"
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 942.529µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:33Z"
    - latency: 862.511µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:33Z"
    - latency: 955.715µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:33Z"
    - latency: 1.094829ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:33Z"
    - latency: 937.461µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:33Z"
    - latency: 906.035µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:33Z"
    - latency: 986.27µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:33Z"
    - latency: 980.353µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:33Z"
    - latency: 994.847µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:33Z"
    - latency: 994.847µs
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:16:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-ip-10-0-137-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: cbb7cae2-3d7d-4843-829f-7204fbd4084c
    resourceVersion: "30511"
    uid: 5c421594-cfb1-4849-a673-7748d0a16a9e
  spec:
    sourcePod: network-check-source-7cbc45fddc-mc9hh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:23:33Z"
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.198601ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:33Z"
    - latency: 1.669428ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:33Z"
    - latency: 2.201041ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:33Z"
    - latency: 1.927013ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:33Z"
    - latency: 2.251105ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:33Z"
    - latency: 1.797607ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:33Z"
    - latency: 1.915341ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:33Z"
    - latency: 2.113876ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:33Z"
    - latency: 2.19565ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:33Z"
    - latency: 2.19565ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:16:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-ip-10-0-140-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: cbb7cae2-3d7d-4843-829f-7204fbd4084c
    resourceVersion: "30512"
    uid: b49a77f7-52e5-45e4-9aa3-087a09b4266b
  spec:
    sourcePod: network-check-source-7cbc45fddc-mc9hh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:23:33Z"
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.952005ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:33Z"
    - latency: 2.252467ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:33Z"
    - latency: 2.397265ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:33Z"
    - latency: 2.307028ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:33Z"
    - latency: 2.374884ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:33Z"
    - latency: 2.198508ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:33Z"
    - latency: 2.471099ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:33Z"
    - latency: 2.258941ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:33Z"
    - latency: 2.304206ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:33Z"
    - latency: 2.304206ms
      message: 'network-check-target-ip-10-0-140-217: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:16:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-222.ec2.internal
      uid: cbb7cae2-3d7d-4843-829f-7204fbd4084c
    resourceVersion: "29639"
    uid: d351defe-0a78-4bfb-9d06-ebfbbd6666ff
  spec:
    sourcePod: network-check-source-7cbc45fddc-mc9hh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:22:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.048µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:33Z"
    - latency: 2.156333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:41:33Z"
    - latency: 907.343µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:33Z"
    - latency: 1.775648ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:40:33Z"
    - latency: 985.967µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:33Z"
    - latency: 2.020857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:39:33Z"
    - latency: 868.728µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:33Z"
    - latency: 1.814443ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:38:33Z"
    - latency: 1.488937ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:33Z"
    - latency: 1.762012ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:33Z"
kind: List
metadata:
  resourceVersion: ""