apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T05:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 4a22ab7d-4e68-4b91-8292-93a9c0eace66
    resourceVersion: "61704"
    uid: 7a941abb-424a-4f87-93b1-6c42d2595178
  spec:
    sourcePod: network-check-source-6f78d59f99-n9hcn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T06:03:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 976.524µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:24:44Z"
    - latency: 1.038673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:23:44Z"
    - latency: 1.140023ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:22:44Z"
    - latency: 1.48111ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:21:44Z"
    - latency: 1.087908ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:20:44Z"
    - latency: 1.200343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:19:44Z"
    - latency: 1.290255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:18:44Z"
    - latency: 1.53102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:17:44Z"
    - latency: 1.000511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:16:44Z"
    - latency: 23.938424ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:15:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T05:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 4a22ab7d-4e68-4b91-8292-93a9c0eace66
    resourceVersion: "65147"
    uid: 653ad2d6-1ce5-438d-ac00-913fbea15d19
  spec:
    sourcePod: network-check-source-6f78d59f99-n9hcn
    targetEndpoint: a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T06:02:44Z"
      message: 'load-balancer-api-external: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.445794ms
      message: 'load-balancer-api-external: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:26:44Z"
    - latency: 6.872037ms
      message: 'load-balancer-api-external: resolved host name a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:26:44Z"
    - latency: 18.122384ms
      message: 'load-balancer-api-external: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:25:44Z"
    - latency: 6.963365ms
      message: 'load-balancer-api-external: resolved host name a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:25:44Z"
    - latency: 17.046826ms
      message: 'load-balancer-api-external: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:24:44Z"
    - latency: 12.017481ms
      message: 'load-balancer-api-external: resolved host name a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:24:44Z"
    - latency: 16.805838ms
      message: 'load-balancer-api-external: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:23:44Z"
    - latency: 6.752146ms
      message: 'load-balancer-api-external: resolved host name a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:23:44Z"
    - latency: 17.96526ms
      message: 'load-balancer-api-external: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:22:44Z"
    - latency: 10.79889ms
      message: 'load-balancer-api-external: resolved host name a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:22:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T05:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 4a22ab7d-4e68-4b91-8292-93a9c0eace66
    resourceVersion: "65146"
    uid: 332d75f8-fa57-4a06-af54-ad3760cb160f
  spec:
    sourcePod: network-check-source-6f78d59f99-n9hcn
    targetEndpoint: a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T06:02:44Z"
      message: 'load-balancer-api-internal: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.196626ms
      message: 'load-balancer-api-internal: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:26:44Z"
    - latency: 6.921347ms
      message: 'load-balancer-api-internal: resolved host name a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:26:44Z"
    - latency: 16.98729ms
      message: 'load-balancer-api-internal: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:25:44Z"
    - latency: 7.024874ms
      message: 'load-balancer-api-internal: resolved host name a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:25:44Z"
    - latency: 17.446503ms
      message: 'load-balancer-api-internal: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:24:44Z"
    - latency: 12.050423ms
      message: 'load-balancer-api-internal: resolved host name a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:24:44Z"
    - latency: 17.577474ms
      message: 'load-balancer-api-internal: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:23:44Z"
    - latency: 6.808214ms
      message: 'load-balancer-api-internal: resolved host name a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:23:44Z"
    - latency: 17.171897ms
      message: 'load-balancer-api-internal: tcp connection to a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:22:44Z"
    - latency: 10.841053ms
      message: 'load-balancer-api-internal: resolved host name a9c3d13d4a20e482d9ec4c335208f836-32a935bf0689107a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:22:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T05:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-network-check-target-ip-10-0-132-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 4a22ab7d-4e68-4b91-8292-93a9c0eace66
    resourceVersion: "61701"
    uid: d717fa70-61d7-4f0f-904c-e5c1354dab94
  spec:
    sourcePod: network-check-source-6f78d59f99-n9hcn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T06:03:44Z"
      message: 'network-check-target-ip-10-0-132-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.285753ms
      message: 'network-check-target-ip-10-0-132-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:24:44Z"
    - latency: 2.323046ms
      message: 'network-check-target-ip-10-0-132-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:23:44Z"
    - latency: 2.483678ms
      message: 'network-check-target-ip-10-0-132-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:22:44Z"
    - latency: 2.16772ms
      message: 'network-check-target-ip-10-0-132-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:21:44Z"
    - latency: 2.664149ms
      message: 'network-check-target-ip-10-0-132-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:20:44Z"
    - latency: 2.223352ms
      message: 'network-check-target-ip-10-0-132-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:19:44Z"
    - latency: 2.745112ms
      message: 'network-check-target-ip-10-0-132-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:18:44Z"
    - latency: 2.951139ms
      message: 'network-check-target-ip-10-0-132-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:17:44Z"
    - latency: 2.480284ms
      message: 'network-check-target-ip-10-0-132-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:16:44Z"
    - latency: 23.895262ms
      message: 'network-check-target-ip-10-0-132-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:15:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T05:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-network-check-target-ip-10-0-138-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 4a22ab7d-4e68-4b91-8292-93a9c0eace66
    resourceVersion: "61702"
    uid: 2cf92e52-1595-40db-bf91-4d0af5f898df
  spec:
    sourcePod: network-check-source-6f78d59f99-n9hcn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T06:03:44Z"
      message: 'network-check-target-ip-10-0-138-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.443222ms
      message: 'network-check-target-ip-10-0-138-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:24:44Z"
    - latency: 2.429267ms
      message: 'network-check-target-ip-10-0-138-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:23:44Z"
    - latency: 2.127702ms
      message: 'network-check-target-ip-10-0-138-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:22:44Z"
    - latency: 2.092123ms
      message: 'network-check-target-ip-10-0-138-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:21:44Z"
    - latency: 2.749ms
      message: 'network-check-target-ip-10-0-138-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:20:44Z"
    - latency: 2.574972ms
      message: 'network-check-target-ip-10-0-138-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:19:44Z"
    - latency: 3.052898ms
      message: 'network-check-target-ip-10-0-138-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:18:44Z"
    - latency: 2.516999ms
      message: 'network-check-target-ip-10-0-138-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:17:44Z"
    - latency: 2.317749ms
      message: 'network-check-target-ip-10-0-138-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:16:44Z"
    - latency: 23.360155ms
      message: 'network-check-target-ip-10-0-138-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:15:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T05:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-network-check-target-ip-10-0-141-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 4a22ab7d-4e68-4b91-8292-93a9c0eace66
    resourceVersion: "61700"
    uid: e55d0e19-b8b1-4501-89c8-20f422091ed5
  spec:
    sourcePod: network-check-source-6f78d59f99-n9hcn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T06:03:44Z"
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.483226ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:24:44Z"
    - latency: 1.223877ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:23:44Z"
    - latency: 1.516371ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:22:44Z"
    - latency: 963.242µs
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:21:44Z"
    - latency: 1.580555ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:20:44Z"
    - latency: 1.123612ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:19:44Z"
    - latency: 2.615719ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:18:44Z"
    - latency: 1.314732ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:17:44Z"
    - latency: 1.337721ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:16:44Z"
    - latency: 25.76766ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:15:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T05:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-67-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-67.ec2.internal
      uid: 4a22ab7d-4e68-4b91-8292-93a9c0eace66
    resourceVersion: "65145"
    uid: f8fe0657-6a3a-4418-b3ed-d9be32bdf91a
  spec:
    sourcePod: network-check-source-6f78d59f99-n9hcn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T06:02:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 975.509µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:26:44Z"
    - latency: 1.759385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:26:44Z"
    - latency: 1.258655ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:25:44Z"
    - latency: 1.776537ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:25:44Z"
    - latency: 1.703798ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:24:44Z"
    - latency: 2.223107ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:24:44Z"
    - latency: 908.499µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:23:44Z"
    - latency: 1.957196ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:23:44Z"
    - latency: 951.74µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T06:22:44Z"
    - latency: 2.390967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T06:22:44Z"
kind: List
metadata:
  resourceVersion: ""