apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-174-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-174.ec2.internal
      uid: 6078b177-3eef-4a77-8642-083a6cd5d9c2
    resourceVersion: "21961"
    uid: 6a7193b1-09fa-4a7f-8f0f-41f80709a582
  spec:
    sourcePod: network-check-source-56499946bc-cbzhj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:55:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.354µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:24Z"
    - latency: 955.299µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:24Z"
    - latency: 894.074µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:07:24Z"
    - latency: 1.081586ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:24Z"
    - latency: 1.069825ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:24Z"
    - latency: 842.39µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:24Z"
    - latency: 969.43µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:24Z"
    - latency: 1.081405ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:24Z"
    - latency: 1.169598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:01:24Z"
    - latency: 987.446µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:00:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-174-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-174.ec2.internal
      uid: 6078b177-3eef-4a77-8642-083a6cd5d9c2
    resourceVersion: "20581"
    uid: e418d0af-8c86-4c94-8a9b-7830b5fddd95
  spec:
    sourcePod: network-check-source-56499946bc-cbzhj
    targetEndpoint: a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:54:24Z"
      message: 'load-balancer-api-external: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.191747ms
      message: 'load-balancer-api-external: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:24Z"
    - latency: 8.378697ms
      message: 'load-balancer-api-external: resolved host name a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:06:24Z"
    - latency: 5.429186ms
      message: 'load-balancer-api-external: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:24Z"
    - latency: 10.526806ms
      message: 'load-balancer-api-external: resolved host name a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:05:24Z"
    - latency: 6.225565ms
      message: 'load-balancer-api-external: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:24Z"
    - latency: 10.248122ms
      message: 'load-balancer-api-external: resolved host name a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:04:24Z"
    - latency: 5.611798ms
      message: 'load-balancer-api-external: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:24Z"
    - latency: 8.473084ms
      message: 'load-balancer-api-external: resolved host name a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:03:24Z"
    - latency: 5.458572ms
      message: 'load-balancer-api-external: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:24Z"
    - latency: 13.035369ms
      message: 'load-balancer-api-external: resolved host name a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:02:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-174-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-174.ec2.internal
      uid: 6078b177-3eef-4a77-8642-083a6cd5d9c2
    resourceVersion: "20582"
    uid: 81fdfa0f-cb91-4ba2-bc62-d815c1b1bb1f
  spec:
    sourcePod: network-check-source-56499946bc-cbzhj
    targetEndpoint: a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:54:24Z"
      message: 'load-balancer-api-internal: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.62277ms
      message: 'load-balancer-api-internal: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:24Z"
    - latency: 8.297054ms
      message: 'load-balancer-api-internal: resolved host name a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:06:24Z"
    - latency: 5.510963ms
      message: 'load-balancer-api-internal: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:24Z"
    - latency: 10.498697ms
      message: 'load-balancer-api-internal: resolved host name a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:05:24Z"
    - latency: 6.22543ms
      message: 'load-balancer-api-internal: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:24Z"
    - latency: 10.164241ms
      message: 'load-balancer-api-internal: resolved host name a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:04:24Z"
    - latency: 5.522689ms
      message: 'load-balancer-api-internal: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:24Z"
    - latency: 8.434872ms
      message: 'load-balancer-api-internal: resolved host name a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:03:24Z"
    - latency: 5.343379ms
      message: 'load-balancer-api-internal: tcp connection to a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:24Z"
    - latency: 12.999835ms
      message: 'load-balancer-api-internal: resolved host name a6e3bb7b8b2fd4cd6bc8285119898723-5b2688f4c1069f6a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:02:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-174-to-network-check-target-ip-10-0-133-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-174.ec2.internal
      uid: 6078b177-3eef-4a77-8642-083a6cd5d9c2
    resourceVersion: "21959"
    uid: 0334ac16-ca57-45fe-ba97-804e4988c59e
  spec:
    sourcePod: network-check-source-56499946bc-cbzhj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:55:24Z"
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.047978ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:24Z"
    - latency: 2.218011ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:24Z"
    - latency: 2.208159ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:07:24Z"
    - latency: 2.318749ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:24Z"
    - latency: 2.427345ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:24Z"
    - latency: 2.199069ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:24Z"
    - latency: 2.360042ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:24Z"
    - latency: 2.523302ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:24Z"
    - latency: 2.372372ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:01:24Z"
    - latency: 2.184249ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:00:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-174-to-network-check-target-ip-10-0-136-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-174.ec2.internal
      uid: 6078b177-3eef-4a77-8642-083a6cd5d9c2
    resourceVersion: "21960"
    uid: 0633eb46-7f25-4d8e-ab2f-ad9adc846ddf
  spec:
    sourcePod: network-check-source-56499946bc-cbzhj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:55:24Z"
      message: 'network-check-target-ip-10-0-136-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.827759ms
      message: 'network-check-target-ip-10-0-136-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:24Z"
    - latency: 1.742383ms
      message: 'network-check-target-ip-10-0-136-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:24Z"
    - latency: 1.890752ms
      message: 'network-check-target-ip-10-0-136-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:07:24Z"
    - latency: 1.840108ms
      message: 'network-check-target-ip-10-0-136-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:24Z"
    - latency: 2.083314ms
      message: 'network-check-target-ip-10-0-136-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:24Z"
    - latency: 1.902884ms
      message: 'network-check-target-ip-10-0-136-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:24Z"
    - latency: 2.014362ms
      message: 'network-check-target-ip-10-0-136-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:24Z"
    - latency: 2.041065ms
      message: 'network-check-target-ip-10-0-136-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:24Z"
    - latency: 1.986105ms
      message: 'network-check-target-ip-10-0-136-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:01:24Z"
    - latency: 2.058567ms
      message: 'network-check-target-ip-10-0-136-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:00:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-174-to-network-check-target-ip-10-0-140-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-174.ec2.internal
      uid: 6078b177-3eef-4a77-8642-083a6cd5d9c2
    resourceVersion: "21958"
    uid: 2da79484-9e95-4adc-a79b-ac14ed44411c
  spec:
    sourcePod: network-check-source-56499946bc-cbzhj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:55:24Z"
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.279849ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:09:24Z"
    - latency: 874.194µs
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:08:24Z"
    - latency: 858.24µs
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:07:24Z"
    - latency: 1.175599ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:24Z"
    - latency: 895.336µs
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:24Z"
    - latency: 822.719µs
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:24Z"
    - latency: 1.067781ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:24Z"
    - latency: 851.296µs
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:24Z"
    - latency: 1.721628ms
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:01:24Z"
    - latency: 758.143µs
      message: 'network-check-target-ip-10-0-140-174: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:00:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:48:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-174-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-174.ec2.internal
      uid: 6078b177-3eef-4a77-8642-083a6cd5d9c2
    resourceVersion: "20580"
    uid: e2a9fafc-378a-4e29-b6fb-abdc8966f420
  spec:
    sourcePod: network-check-source-56499946bc-cbzhj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:54:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.237µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:06:24Z"
    - latency: 1.903908ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:06:24Z"
    - latency: 914.811µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:05:24Z"
    - latency: 1.735772ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:05:24Z"
    - latency: 1.082785ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:04:24Z"
    - latency: 1.80199ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:04:24Z"
    - latency: 1.13539ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:03:24Z"
    - latency: 1.916905ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:03:24Z"
    - latency: 1.143303ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T14:02:24Z"
    - latency: 1.598761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T14:02:24Z"
kind: List
metadata:
  resourceVersion: ""