apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-184-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-184.ec2.internal
      uid: fb6540f3-d181-42d7-9c7c-d8cd724d34a6
    resourceVersion: "39192"
    uid: 8b91b111-7583-4bf1-a20f-4895034a6602
  spec:
    sourcePod: network-check-source-7cbc45fddc-s6b9s
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:21:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.026µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:03:59Z"
    - latency: 912.655µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:02:59Z"
    - latency: 927.334µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:01:59Z"
    - latency: 1.245604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:00:59Z"
    - latency: 1.071874ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:59:59Z"
    - latency: 1.026445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:58:59Z"
    - latency: 1.023385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:57:59Z"
    - latency: 969.671µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:56:59Z"
    - latency: 1.06179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:55:59Z"
    - latency: 959.641µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-184-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-184.ec2.internal
      uid: fb6540f3-d181-42d7-9c7c-d8cd724d34a6
    resourceVersion: "38708"
    uid: 8b7ddaac-14b4-4ea0-9d6f-44c05d48578b
  spec:
    sourcePod: network-check-source-7cbc45fddc-s6b9s
    targetEndpoint: a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:20:59Z"
      message: 'load-balancer-api-external: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.735625ms
      message: 'load-balancer-api-external: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:02:59Z"
    - latency: 8.92541ms
      message: 'load-balancer-api-external: resolved host name a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:02:59Z"
    - latency: 5.010191ms
      message: 'load-balancer-api-external: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:01:59Z"
    - latency: 8.925324ms
      message: 'load-balancer-api-external: resolved host name a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:01:59Z"
    - latency: 5.06848ms
      message: 'load-balancer-api-external: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:00:59Z"
    - latency: 8.387444ms
      message: 'load-balancer-api-external: resolved host name a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:00:59Z"
    - latency: 4.160136ms
      message: 'load-balancer-api-external: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:59:59Z"
    - latency: 10.554542ms
      message: 'load-balancer-api-external: resolved host name a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:59:59Z"
    - latency: 4.114799ms
      message: 'load-balancer-api-external: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:58:59Z"
    - latency: 12.266743ms
      message: 'load-balancer-api-external: resolved host name a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:58:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-184-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-184.ec2.internal
      uid: fb6540f3-d181-42d7-9c7c-d8cd724d34a6
    resourceVersion: "38707"
    uid: 86bc747d-ca9b-47e8-8c2a-c30d656643d5
  spec:
    sourcePod: network-check-source-7cbc45fddc-s6b9s
    targetEndpoint: a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:20:59Z"
      message: 'load-balancer-api-internal: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.728759ms
      message: 'load-balancer-api-internal: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:02:59Z"
    - latency: 8.894628ms
      message: 'load-balancer-api-internal: resolved host name a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:02:59Z"
    - latency: 4.978002ms
      message: 'load-balancer-api-internal: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:01:59Z"
    - latency: 8.991685ms
      message: 'load-balancer-api-internal: resolved host name a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:01:59Z"
    - latency: 5.057835ms
      message: 'load-balancer-api-internal: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:00:59Z"
    - latency: 8.508765ms
      message: 'load-balancer-api-internal: resolved host name a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:00:59Z"
    - latency: 4.182689ms
      message: 'load-balancer-api-internal: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:59:59Z"
    - latency: 10.635599ms
      message: 'load-balancer-api-internal: resolved host name a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:59:59Z"
    - latency: 3.919226ms
      message: 'load-balancer-api-internal: tcp connection to a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:58:59Z"
    - latency: 12.326187ms
      message: 'load-balancer-api-internal: resolved host name a367969050034466eb7b42d9afe1497b-0adc4b021b967367.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:58:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-184-to-network-check-target-ip-10-0-128-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-184.ec2.internal
      uid: fb6540f3-d181-42d7-9c7c-d8cd724d34a6
    resourceVersion: "39189"
    uid: 22165d81-4ac5-4091-b7d9-f6c1ae364f8c
  spec:
    sourcePod: network-check-source-7cbc45fddc-s6b9s
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:21:59Z"
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.626µs
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:03:59Z"
    - latency: 1.023719ms
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:02:59Z"
    - latency: 878.72µs
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:01:59Z"
    - latency: 1.334283ms
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:00:59Z"
    - latency: 1.407675ms
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:59:59Z"
    - latency: 877.071µs
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:58:59Z"
    - latency: 816.804µs
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:57:59Z"
    - latency: 776.319µs
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:56:59Z"
    - latency: 790.008µs
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:55:59Z"
    - latency: 871.772µs
      message: 'network-check-target-ip-10-0-128-184: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-184-to-network-check-target-ip-10-0-135-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-184.ec2.internal
      uid: fb6540f3-d181-42d7-9c7c-d8cd724d34a6
    resourceVersion: "39191"
    uid: d8ebaa3c-015d-4f46-acbb-8ed20d9bd623
  spec:
    sourcePod: network-check-source-7cbc45fddc-s6b9s
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:21:59Z"
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.227406ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:03:59Z"
    - latency: 2.287968ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:02:59Z"
    - latency: 2.284756ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:01:59Z"
    - latency: 2.339497ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:00:59Z"
    - latency: 2.504877ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:59:59Z"
    - latency: 2.177191ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:58:59Z"
    - latency: 2.307722ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:57:59Z"
    - latency: 2.115346ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:56:59Z"
    - latency: 2.224773ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:55:59Z"
    - latency: 2.135482ms
      message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-184-to-network-check-target-ip-10-0-142-246
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-184.ec2.internal
      uid: fb6540f3-d181-42d7-9c7c-d8cd724d34a6
    resourceVersion: "39190"
    uid: faa27160-0f9a-4ce0-ac51-24c76839f4cf
  spec:
    sourcePod: network-check-source-7cbc45fddc-s6b9s
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:21:59Z"
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.825162ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:03:59Z"
    - latency: 1.8556ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:02:59Z"
    - latency: 2.295967ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:01:59Z"
    - latency: 1.901518ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:00:59Z"
    - latency: 1.706156ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:59:59Z"
    - latency: 1.717043ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:58:59Z"
    - latency: 1.800247ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:57:59Z"
    - latency: 3.623055ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:56:59Z"
    - latency: 1.674951ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:55:59Z"
    - latency: 1.800566ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:14:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-184-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-184.ec2.internal
      uid: fb6540f3-d181-42d7-9c7c-d8cd724d34a6
    resourceVersion: "38706"
    uid: 8c5a6386-5309-46a4-bffb-ac0b7a3312a1
  spec:
    sourcePod: network-check-source-7cbc45fddc-s6b9s
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:20:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 987.766µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:02:59Z"
    - latency: 1.862541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:02:59Z"
    - latency: 767.828µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:01:59Z"
    - latency: 1.767565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:01:59Z"
    - latency: 698.888µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T00:00:59Z"
    - latency: 1.661737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T00:00:59Z"
    - latency: 1.167338ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:59:59Z"
    - latency: 1.677173ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:59:59Z"
    - latency: 894.05µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:58:59Z"
    - latency: 1.758299ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:58:59Z"
kind: List
metadata:
  resourceVersion: ""