apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-192-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-192.ec2.internal
      uid: b019ff24-6f27-4d6f-bdb3-d105bda57976
    resourceVersion: "23217"
    uid: 1486fe3c-33c0-4c38-9f33-a5193e768857
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vgwx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 982.151µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:44:16Z"
    - latency: 948.632µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:43:16Z"
    - latency: 926.381µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:16Z"
    - latency: 940.028µ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:16Z"
    - latency: 1.216805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:16Z"
    - latency: 1.028427ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:16Z"
    - latency: 1.292045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:16Z"
    - latency: 1.019223ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:16Z"
    - latency: 1.034248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:16Z"
    - latency: 1.871845ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-192-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-192.ec2.internal
      uid: b019ff24-6f27-4d6f-bdb3-d105bda57976
    resourceVersion: "21728"
    uid: e0fb67ac-0499-4542-b98f-80675fafcbab
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vgwx
    targetEndpoint: a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:29:16Z"
      message: 'load-balancer-api-external: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.373195ms
      message: 'load-balancer-api-external: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:16Z"
    - latency: 9.206321ms
      message: 'load-balancer-api-external: resolved host name a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:41:16Z"
    - latency: 5.58483ms
      message: 'load-balancer-api-external: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:16Z"
    - latency: 8.049952ms
      message: 'load-balancer-api-external: resolved host name a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:40:16Z"
    - latency: 4.547067ms
      message: 'load-balancer-api-external: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:16Z"
    - latency: 8.3765ms
      message: 'load-balancer-api-external: resolved host name a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:39:16Z"
    - latency: 7.25914ms
      message: 'load-balancer-api-external: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:16Z"
    - latency: 7.644056ms
      message: 'load-balancer-api-external: resolved host name a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:38:16Z"
    - latency: 5.918479ms
      message: 'load-balancer-api-external: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:16Z"
    - latency: 9.217302ms
      message: 'load-balancer-api-external: resolved host name a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-192-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-192.ec2.internal
      uid: b019ff24-6f27-4d6f-bdb3-d105bda57976
    resourceVersion: "21729"
    uid: a9d9cd75-db52-499c-aa49-8c3ba39971f0
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vgwx
    targetEndpoint: a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:29:16Z"
      message: 'load-balancer-api-internal: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.52621ms
      message: 'load-balancer-api-internal: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:16Z"
    - latency: 9.185505ms
      message: 'load-balancer-api-internal: resolved host name a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:41:16Z"
    - latency: 5.575273ms
      message: 'load-balancer-api-internal: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:16Z"
    - latency: 7.969833ms
      message: 'load-balancer-api-internal: resolved host name a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:40:16Z"
    - latency: 5.182545ms
      message: 'load-balancer-api-internal: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:16Z"
    - latency: 8.354562ms
      message: 'load-balancer-api-internal: resolved host name a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:39:16Z"
    - latency: 5.268897ms
      message: 'load-balancer-api-internal: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:16Z"
    - latency: 7.568261ms
      message: 'load-balancer-api-internal: resolved host name a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:38:16Z"
    - latency: 5.895751ms
      message: 'load-balancer-api-internal: tcp connection to a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:16Z"
    - latency: 9.274727ms
      message: 'load-balancer-api-internal: resolved host name a555beeea96c6419391f827dbef67bb6-38b55ce0499e5265.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-192-to-network-check-target-ip-10-0-138-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-192.ec2.internal
      uid: b019ff24-6f27-4d6f-bdb3-d105bda57976
    resourceVersion: "23215"
    uid: 8e2891d9-7152-4aa3-be95-c564916ab856
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vgwx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:16Z"
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.29217ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:44:16Z"
    - latency: 2.403327ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:43:16Z"
    - latency: 2.384276ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:16Z"
    - latency: 2.296911ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:16Z"
    - latency: 2.548325ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:16Z"
    - latency: 2.248442ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:16Z"
    - latency: 2.295381ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:16Z"
    - latency: 2.254571ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:16Z"
    - latency: 2.159223ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:16Z"
    - latency: 2.602934ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-192-to-network-check-target-ip-10-0-138-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-192.ec2.internal
      uid: b019ff24-6f27-4d6f-bdb3-d105bda57976
    resourceVersion: "23216"
    uid: 8726770a-4d15-480d-b18d-686d24280e2e
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vgwx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:16Z"
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.572385ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:44:16Z"
    - latency: 2.434125ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:43:16Z"
    - latency: 2.261099ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:16Z"
    - latency: 2.470385ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:16Z"
    - latency: 2.296192ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:16Z"
    - latency: 2.344294ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:16Z"
    - latency: 2.223647ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:16Z"
    - latency: 2.263421ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:16Z"
    - latency: 2.660012ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:16Z"
    - latency: 2.496452ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-192-to-network-check-target-ip-10-0-143-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-192.ec2.internal
      uid: b019ff24-6f27-4d6f-bdb3-d105bda57976
    resourceVersion: "23214"
    uid: 1a280779-cff4-43bb-8be4-60ca303ea120
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vgwx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:30:16Z"
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.440278ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:44:16Z"
    - latency: 1.485707ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:43:16Z"
    - latency: 1.205039ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:16Z"
    - latency: 1.239208ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:16Z"
    - latency: 1.440855ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:16Z"
    - latency: 953.185µs
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:16Z"
    - latency: 1.286795ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:16Z"
    - latency: 884.871µs
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:16Z"
    - latency: 953.853µs
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:16Z"
    - latency: 1.121385ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-192-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-192.ec2.internal
      uid: b019ff24-6f27-4d6f-bdb3-d105bda57976
    resourceVersion: "21727"
    uid: d0bfaa79-c484-4f9d-a1e5-49f97c4858d1
  spec:
    sourcePod: network-check-source-7cbc45fddc-7vgwx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:29:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.169468ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:16Z"
    - latency: 2.022104ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:41:16Z"
    - latency: 1.069996ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:16Z"
    - latency: 1.665619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:40:16Z"
    - latency: 803.218µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:16Z"
    - latency: 1.807222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:39:16Z"
    - latency: 1.421715ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:16Z"
    - latency: 1.859008ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:38:16Z"
    - latency: 986.173µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:16Z"
    - latency: 2.327835ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:16Z"
kind: List
metadata:
  resourceVersion: ""