apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T12:42:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: 0b83a5b8-e4ff-45cc-a126-4620fb2c0a1a
    resourceVersion: "63157"
    uid: d3987c40-f559-4cd6-8730-56ec7c0e224a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hcnc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T12:49:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 916.652µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:24:35Z"
    - latency: 1.434529ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:23:35Z"
    - latency: 871.664µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:22:35Z"
    - latency: 1.261998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:21:35Z"
    - latency: 976.569µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:20:35Z"
    - latency: 1.109006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:19:35Z"
    - latency: 1.183916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:18:35Z"
    - latency: 1.116978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:17:35Z"
    - latency: 952.856µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:16:35Z"
    - latency: 1.034451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:15:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T12:42:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: 0b83a5b8-e4ff-45cc-a126-4620fb2c0a1a
    resourceVersion: "63159"
    uid: 06a098da-4474-4bdb-9501-b913c7ca5999
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hcnc
    targetEndpoint: a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T12:48:35Z"
      message: 'load-balancer-api-external: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.01485ms
      message: 'load-balancer-api-external: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:24:35Z"
    - latency: 9.637252ms
      message: 'load-balancer-api-external: resolved host name a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:24:35Z"
    - latency: 3.995908ms
      message: 'load-balancer-api-external: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:23:35Z"
    - latency: 8.814585ms
      message: 'load-balancer-api-external: resolved host name a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:23:35Z"
    - latency: 4.26566ms
      message: 'load-balancer-api-external: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:22:35Z"
    - latency: 8.26576ms
      message: 'load-balancer-api-external: resolved host name a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:22:35Z"
    - latency: 6.132852ms
      message: 'load-balancer-api-external: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:21:35Z"
    - latency: 8.517934ms
      message: 'load-balancer-api-external: resolved host name a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:21:35Z"
    - latency: 5.753243ms
      message: 'load-balancer-api-external: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:20:35Z"
    - latency: 8.254804ms
      message: 'load-balancer-api-external: resolved host name a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:20:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T12:42:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: 0b83a5b8-e4ff-45cc-a126-4620fb2c0a1a
    resourceVersion: "63158"
    uid: 36aa1150-7cee-497f-9fe6-48fc30991e03
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hcnc
    targetEndpoint: a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T12:48:35Z"
      message: 'load-balancer-api-internal: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.450902ms
      message: 'load-balancer-api-internal: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:24:35Z"
    - latency: 9.587686ms
      message: 'load-balancer-api-internal: resolved host name a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:24:35Z"
    - latency: 4.020512ms
      message: 'load-balancer-api-internal: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:23:35Z"
    - latency: 8.762848ms
      message: 'load-balancer-api-internal: resolved host name a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:23:35Z"
    - latency: 4.267282ms
      message: 'load-balancer-api-internal: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:22:35Z"
    - latency: 8.201477ms
      message: 'load-balancer-api-internal: resolved host name a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:22:35Z"
    - latency: 6.204071ms
      message: 'load-balancer-api-internal: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:21:35Z"
    - latency: 8.460104ms
      message: 'load-balancer-api-internal: resolved host name a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:21:35Z"
    - latency: 5.758202ms
      message: 'load-balancer-api-internal: tcp connection to a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:20:35Z"
    - latency: 8.204775ms
      message: 'load-balancer-api-internal: resolved host name a339d6e189ee447489b3538f39e06a82-c6f2ee5d14fcd145.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:20:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T12:42:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-network-check-target-ip-10-0-128-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: 0b83a5b8-e4ff-45cc-a126-4620fb2c0a1a
    resourceVersion: "63153"
    uid: ff6fb590-9d9b-45ec-8e31-4780770cdd4f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hcnc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T12:49:35Z"
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.132331ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:24:35Z"
    - latency: 1.526449ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:23:35Z"
    - latency: 1.157621ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:22:35Z"
    - latency: 1.14417ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:21:35Z"
    - latency: 960.327µs
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:20:35Z"
    - latency: 831.122µs
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:19:35Z"
    - latency: 1.081623ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:18:35Z"
    - latency: 1.227577ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:17:35Z"
    - latency: 831.591µs
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:16:35Z"
    - latency: 1.000045ms
      message: 'network-check-target-ip-10-0-128-197: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:15:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T12:42:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-network-check-target-ip-10-0-130-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: 0b83a5b8-e4ff-45cc-a126-4620fb2c0a1a
    resourceVersion: "63155"
    uid: 2f69b3bd-edb8-4890-9bc2-1652b3f15814
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hcnc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T12:49:35Z"
      message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.598416ms
      message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:24:35Z"
    - latency: 2.531465ms
      message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:23:35Z"
    - latency: 2.488008ms
      message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:22:35Z"
    - latency: 2.286873ms
      message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:21:35Z"
    - latency: 2.593718ms
      message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:20:35Z"
    - latency: 2.280956ms
      message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:19:35Z"
    - latency: 2.592949ms
      message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:18:35Z"
    - latency: 2.330315ms
      message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:17:35Z"
    - latency: 2.727134ms
      message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:16:35Z"
    - latency: 2.531057ms
      message: 'network-check-target-ip-10-0-130-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:15:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T12:42:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-network-check-target-ip-10-0-140-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: 0b83a5b8-e4ff-45cc-a126-4620fb2c0a1a
    resourceVersion: "63154"
    uid: 188c8fdd-429f-4098-822f-79c18b92fe6f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hcnc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T12:49:35Z"
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.624125ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:24:35Z"
    - latency: 2.562369ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:23:35Z"
    - latency: 2.178711ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:22:35Z"
    - latency: 2.059127ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:21:35Z"
    - latency: 2.11244ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:20:35Z"
    - latency: 2.203785ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:19:35Z"
    - latency: 2.242884ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:18:35Z"
    - latency: 2.391535ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:17:35Z"
    - latency: 2.436361ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:16:35Z"
    - latency: 2.421512ms
      message: 'network-check-target-ip-10-0-140-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:15:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T12:42:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-197-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-197.ec2.internal
      uid: 0b83a5b8-e4ff-45cc-a126-4620fb2c0a1a
    resourceVersion: "63156"
    uid: 6a12bf4b-aa2e-4bbd-9e52-0b3eb8612ac6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9hcnc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T12:48:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.128974ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:24:35Z"
    - latency: 1.929652ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:24:35Z"
    - latency: 855.543µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:23:35Z"
    - latency: 2.137021ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:23:35Z"
    - latency: 883.83µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:22:35Z"
    - latency: 1.753262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:22:35Z"
    - latency: 934.443µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:21:35Z"
    - latency: 1.858303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:21:35Z"
    - latency: 852.956µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T13:20:35Z"
    - latency: 1.721689ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T13:20:35Z"
kind: List
metadata:
  resourceVersion: ""