apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:05:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-56-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-56.ec2.internal
      uid: 503f5b89-81c7-4fc5-988b-c2d00e456216
    resourceVersion: "55162"
    uid: b02710f6-34d7-4bbf-bbcf-2514b0a32aa0
  spec:
    sourcePod: network-check-source-989f8b8dc-rr5zx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:12:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 922.859µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:40:03Z"
    - latency: 1.595466ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:39:03Z"
    - latency: 1.345882ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:38:03Z"
    - latency: 1.223927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:37:03Z"
    - latency: 1.128229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:36:03Z"
    - latency: 781.783µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:35:03Z"
    - latency: 1.147305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:34:03Z"
    - latency: 1.097142ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:33:03Z"
    - latency: 931.693µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:32:03Z"
    - latency: 882.385µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:31:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:05:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-56-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-56.ec2.internal
      uid: 503f5b89-81c7-4fc5-988b-c2d00e456216
    resourceVersion: "56171"
    uid: a7685e79-d6d2-4a28-9988-5ff80a9c5431
  spec:
    sourcePod: network-check-source-989f8b8dc-rr5zx
    targetEndpoint: ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:11:03Z"
      message: 'load-balancer-api-external: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.016572ms
      message: 'load-balancer-api-external: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:41:03Z"
    - latency: 8.511638ms
      message: 'load-balancer-api-external: resolved host name ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:41:03Z"
    - latency: 4.043364ms
      message: 'load-balancer-api-external: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:40:03Z"
    - latency: 9.310097ms
      message: 'load-balancer-api-external: resolved host name ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:40:03Z"
    - latency: 5.191071ms
      message: 'load-balancer-api-external: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:39:03Z"
    - latency: 10.542065ms
      message: 'load-balancer-api-external: resolved host name ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:39:03Z"
    - latency: 4.422997ms
      message: 'load-balancer-api-external: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:38:03Z"
    - latency: 8.510733ms
      message: 'load-balancer-api-external: resolved host name ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:38:03Z"
    - latency: 4.106099ms
      message: 'load-balancer-api-external: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:37:03Z"
    - latency: 8.879961ms
      message: 'load-balancer-api-external: resolved host name ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:37:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:05:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-56-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-56.ec2.internal
      uid: 503f5b89-81c7-4fc5-988b-c2d00e456216
    resourceVersion: "56172"
    uid: 574d900b-5e86-4bbd-a63c-affa64c12363
  spec:
    sourcePod: network-check-source-989f8b8dc-rr5zx
    targetEndpoint: ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:11:03Z"
      message: 'load-balancer-api-internal: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.801876ms
      message: 'load-balancer-api-internal: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:41:03Z"
    - latency: 8.422407ms
      message: 'load-balancer-api-internal: resolved host name ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:41:03Z"
    - latency: 3.842588ms
      message: 'load-balancer-api-internal: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:40:03Z"
    - latency: 9.361282ms
      message: 'load-balancer-api-internal: resolved host name ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:40:03Z"
    - latency: 5.312877ms
      message: 'load-balancer-api-internal: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:39:03Z"
    - latency: 10.595527ms
      message: 'load-balancer-api-internal: resolved host name ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:39:03Z"
    - latency: 4.408701ms
      message: 'load-balancer-api-internal: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:38:03Z"
    - latency: 8.574991ms
      message: 'load-balancer-api-internal: resolved host name ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:38:03Z"
    - latency: 4.13212ms
      message: 'load-balancer-api-internal: tcp connection to ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:37:03Z"
    - latency: 8.93518ms
      message: 'load-balancer-api-internal: resolved host name ab1c86c5d21114f4394b803d40e71a45-3456675746d392c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:37:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:05:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-56-to-network-check-target-ip-10-0-140-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-56.ec2.internal
      uid: 503f5b89-81c7-4fc5-988b-c2d00e456216
    resourceVersion: "55158"
    uid: 3820b7d6-6a04-4300-9ef9-07687bd7871f
  spec:
    sourcePod: network-check-source-989f8b8dc-rr5zx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:12:03Z"
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.713µs
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:40:03Z"
    - latency: 817.24µs
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:39:03Z"
    - latency: 724.08µs
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:38:03Z"
    - latency: 813.779µs
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:37:03Z"
    - latency: 1.04132ms
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:36:03Z"
    - latency: 972.527µs
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:35:03Z"
    - latency: 854.553µs
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:34:03Z"
    - latency: 740.596µs
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:33:03Z"
    - latency: 1.312187ms
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:32:03Z"
    - latency: 706.41µs
      message: 'network-check-target-ip-10-0-140-56: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:31:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:05:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-56-to-network-check-target-ip-10-0-141-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-56.ec2.internal
      uid: 503f5b89-81c7-4fc5-988b-c2d00e456216
    resourceVersion: "55161"
    uid: 2dcfcd22-6790-4800-a6d5-09e5e48fe507
  spec:
    sourcePod: network-check-source-989f8b8dc-rr5zx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:12:03Z"
      message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.211007ms
      message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:40:03Z"
    - latency: 2.190697ms
      message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:39:03Z"
    - latency: 2.197357ms
      message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:38:03Z"
    - latency: 2.117161ms
      message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:37:03Z"
    - latency: 2.09923ms
      message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:36:03Z"
    - latency: 1.976121ms
      message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:35:03Z"
    - latency: 2.210666ms
      message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:34:03Z"
    - latency: 2.19954ms
      message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:33:03Z"
    - latency: 2.2051ms
      message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:32:03Z"
    - latency: 1.96534ms
      message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:31:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:05:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-56-to-network-check-target-ip-10-0-142-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-56.ec2.internal
      uid: 503f5b89-81c7-4fc5-988b-c2d00e456216
    resourceVersion: "55160"
    uid: bbfb143a-ed3f-450e-8cac-c123d0f36270
  spec:
    sourcePod: network-check-source-989f8b8dc-rr5zx
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:12:03Z"
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.922102ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:40:03Z"
    - latency: 1.943995ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:39:03Z"
    - latency: 1.797476ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:38:03Z"
    - latency: 2.13235ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:37:03Z"
    - latency: 1.89876ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:36:03Z"
    - latency: 1.99807ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:35:03Z"
    - latency: 2.002165ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:34:03Z"
    - latency: 1.976313ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:33:03Z"
    - latency: 1.652561ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:32:03Z"
    - latency: 1.693861ms
      message: 'network-check-target-ip-10-0-142-134: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:31:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T19:05:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-56-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-56.ec2.internal
      uid: 503f5b89-81c7-4fc5-988b-c2d00e456216
    resourceVersion: "56169"
    uid: 3e464de6-57b8-4a4c-aee5-e5d6509c339a
  spec:
    sourcePod: network-check-source-989f8b8dc-rr5zx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T19:11:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 849.136µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:41:03Z"
    - latency: 1.71862ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:41:03Z"
    - latency: 1.206405ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:40:03Z"
    - latency: 1.822989ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:40:03Z"
    - latency: 927.397µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:39:03Z"
    - latency: 2.436301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:39:03Z"
    - latency: 780.361µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:38:03Z"
    - latency: 2.034249ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:38:03Z"
    - latency: 907.117µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:37:03Z"
    - latency: 1.854943ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:37:03Z"
kind: List
metadata:
  resourceVersion: ""