apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: a4ccd86f-62b8-4498-a808-94f7cb729d7d
    resourceVersion: "68726"
    uid: b0999a0b-1e06-4a37-b050-87abfdf7c54b
  spec:
    sourcePod: network-check-source-6f8b768455-7vvrg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:45:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.054724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:13:05Z"
    - latency: 1.257446ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:12:05Z"
    - latency: 1.0992ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:11:05Z"
    - latency: 1.147008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:10:05Z"
    - latency: 958.184µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:09:05Z"
    - latency: 1.726148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:08:05Z"
    - latency: 1.159932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:07:05Z"
    - latency: 1.91512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:06:05Z"
    - latency: 853.558µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:05:05Z"
    - latency: 1.109802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:04:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: a4ccd86f-62b8-4498-a808-94f7cb729d7d
    resourceVersion: "69613"
    uid: e71d0d36-9abc-443e-827e-9ec7dfb68399
  spec:
    sourcePod: network-check-source-6f8b768455-7vvrg
    targetEndpoint: a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:44:06Z"
      message: 'load-balancer-api-external: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.079578ms
      message: 'load-balancer-api-external: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:14:05Z"
    - latency: 8.264032ms
      message: 'load-balancer-api-external: resolved host name a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:14:05Z"
    - latency: 4.202164ms
      message: 'load-balancer-api-external: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:13:05Z"
    - latency: 7.532616ms
      message: 'load-balancer-api-external: resolved host name a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:13:05Z"
    - latency: 4.595534ms
      message: 'load-balancer-api-external: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:12:05Z"
    - latency: 8.550434ms
      message: 'load-balancer-api-external: resolved host name a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:12:05Z"
    - latency: 3.956658ms
      message: 'load-balancer-api-external: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:11:05Z"
    - latency: 8.656881ms
      message: 'load-balancer-api-external: resolved host name a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:11:05Z"
    - latency: 4.407561ms
      message: 'load-balancer-api-external: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:10:05Z"
    - latency: 8.705926ms
      message: 'load-balancer-api-external: resolved host name a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:10:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: a4ccd86f-62b8-4498-a808-94f7cb729d7d
    resourceVersion: "69614"
    uid: 577ad26e-d0ff-4f49-88d7-93401be5dc7a
  spec:
    sourcePod: network-check-source-6f8b768455-7vvrg
    targetEndpoint: a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:44:06Z"
      message: 'load-balancer-api-internal: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.584202ms
      message: 'load-balancer-api-internal: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:14:05Z"
    - latency: 8.181439ms
      message: 'load-balancer-api-internal: resolved host name a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:14:05Z"
    - latency: 4.124278ms
      message: 'load-balancer-api-internal: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:13:05Z"
    - latency: 7.678146ms
      message: 'load-balancer-api-internal: resolved host name a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:13:05Z"
    - latency: 4.587758ms
      message: 'load-balancer-api-internal: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:12:05Z"
    - latency: 8.584883ms
      message: 'load-balancer-api-internal: resolved host name a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:12:05Z"
    - latency: 3.915667ms
      message: 'load-balancer-api-internal: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:11:05Z"
    - latency: 8.673526ms
      message: 'load-balancer-api-internal: resolved host name a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:11:05Z"
    - latency: 5.318626ms
      message: 'load-balancer-api-internal: tcp connection to a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:10:05Z"
    - latency: 8.554111ms
      message: 'load-balancer-api-internal: resolved host name a0037a0881efd4db28f8021b3a5cb012-0a25394657230c38.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:10:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-network-check-target-ip-10-0-131-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: a4ccd86f-62b8-4498-a808-94f7cb729d7d
    resourceVersion: "68723"
    uid: 7c534aba-8831-48ab-8dcb-b142e3df2873
  spec:
    sourcePod: network-check-source-6f8b768455-7vvrg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:45:05Z"
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.465077ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:13:05Z"
    - latency: 854.384µs
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:12:05Z"
    - latency: 1.264829ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:11:05Z"
    - latency: 1.487155ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:10:05Z"
    - latency: 1.166677ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:09:05Z"
    - latency: 1.979844ms
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:08:05Z"
    - latency: 907.098µs
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:07:05Z"
    - latency: 998.942µs
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:06:05Z"
    - latency: 871.472µs
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:05:05Z"
    - latency: 869.423µs
      message: 'network-check-target-ip-10-0-131-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:04:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-network-check-target-ip-10-0-139-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: a4ccd86f-62b8-4498-a808-94f7cb729d7d
    resourceVersion: "68725"
    uid: 0e8dde51-d1fd-49f1-bad6-215f79c7b95e
  spec:
    sourcePod: network-check-source-6f8b768455-7vvrg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:45:05Z"
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.323049ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:13:05Z"
    - latency: 1.983441ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:12:05Z"
    - latency: 2.264003ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:11:05Z"
    - latency: 2.316961ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:10:05Z"
    - latency: 1.961602ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:09:05Z"
    - latency: 2.461313ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:08:05Z"
    - latency: 2.98405ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:07:05Z"
    - latency: 2.525966ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:06:05Z"
    - latency: 1.813918ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:05:05Z"
    - latency: 2.154503ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:04:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-network-check-target-ip-10-0-142-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: a4ccd86f-62b8-4498-a808-94f7cb729d7d
    resourceVersion: "68724"
    uid: 4f019c79-9772-4e6d-b9b3-37e949bb284a
  spec:
    sourcePod: network-check-source-6f8b768455-7vvrg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:45:05Z"
      message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.290318ms
      message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:13:05Z"
    - latency: 1.950898ms
      message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:12:05Z"
    - latency: 2.300568ms
      message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:11:05Z"
    - latency: 2.117385ms
      message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:10:05Z"
    - latency: 1.986321ms
      message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:09:05Z"
    - latency: 2.304604ms
      message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:08:05Z"
    - latency: 2.244592ms
      message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:07:05Z"
    - latency: 2.299575ms
      message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:06:05Z"
    - latency: 2.239464ms
      message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:05:05Z"
    - latency: 2.127025ms
      message: 'network-check-target-ip-10-0-142-170: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:04:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-134-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-134.ec2.internal
      uid: a4ccd86f-62b8-4498-a808-94f7cb729d7d
    resourceVersion: "69612"
    uid: f8a2e9c0-7e00-44ab-bab8-abd555fca7db
  spec:
    sourcePod: network-check-source-6f8b768455-7vvrg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:44:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.149656ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:14:05Z"
    - latency: 1.916663ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:14:05Z"
    - latency: 901.384µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:13:05Z"
    - latency: 2.324636ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:13:05Z"
    - latency: 963.316µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:12:05Z"
    - latency: 1.986883ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:12:05Z"
    - latency: 892.437µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:11:05Z"
    - latency: 1.867243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:11:05Z"
    - latency: 895.113µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T08:10:05Z"
    - latency: 1.842056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T08:10:05Z"
kind: List
metadata:
  resourceVersion: ""