apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:50:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 916d0141-7d7c-4808-9d51-f826b23bbc7b
    resourceVersion: "19381"
    uid: 1cafb7aa-66bb-4afe-ab36-aa996a54399e
  spec:
    sourcePod: network-check-source-6f8b768455-f6twl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:57:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:11:38Z"
    - latency: 1.159799ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:10:38Z"
    - latency: 851.902µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:09:38Z"
    - latency: 819.848µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:08:38Z"
    - latency: 757.575µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:07:38Z"
    - latency: 751.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:06:38Z"
    - latency: 788.386µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:05:38Z"
    - latency: 889.241µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:04:38Z"
    - latency: 1.450697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:03:38Z"
    - latency: 890.269µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:02:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:50:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 916d0141-7d7c-4808-9d51-f826b23bbc7b
    resourceVersion: "20718"
    uid: 007c6c08-2543-4b2b-9a5e-6b208277df9a
  spec:
    sourcePod: network-check-source-6f8b768455-f6twl
    targetEndpoint: a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:56:38Z"
      message: 'load-balancer-api-external: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.755727ms
      message: 'load-balancer-api-external: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:14:38Z"
    - latency: 8.643614ms
      message: 'load-balancer-api-external: resolved host name a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:14:38Z"
    - latency: 5.102638ms
      message: 'load-balancer-api-external: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:13:38Z"
    - latency: 8.207416ms
      message: 'load-balancer-api-external: resolved host name a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:13:38Z"
    - latency: 4.235504ms
      message: 'load-balancer-api-external: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:12:38Z"
    - latency: 8.586487ms
      message: 'load-balancer-api-external: resolved host name a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:12:38Z"
    - latency: 4.909573ms
      message: 'load-balancer-api-external: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:11:38Z"
    - latency: 8.53729ms
      message: 'load-balancer-api-external: resolved host name a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:11:38Z"
    - latency: 3.697642ms
      message: 'load-balancer-api-external: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:10:38Z"
    - latency: 7.78606ms
      message: 'load-balancer-api-external: resolved host name a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:10:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:50:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 916d0141-7d7c-4808-9d51-f826b23bbc7b
    resourceVersion: "20719"
    uid: eb3d86ff-5e79-4b3a-bf21-7dd3d7a0c741
  spec:
    sourcePod: network-check-source-6f8b768455-f6twl
    targetEndpoint: a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:56:38Z"
      message: 'load-balancer-api-internal: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.804544ms
      message: 'load-balancer-api-internal: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:14:38Z"
    - latency: 8.716703ms
      message: 'load-balancer-api-internal: resolved host name a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:14:38Z"
    - latency: 5.103654ms
      message: 'load-balancer-api-internal: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:13:38Z"
    - latency: 8.228726ms
      message: 'load-balancer-api-internal: resolved host name a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:13:38Z"
    - latency: 4.299364ms
      message: 'load-balancer-api-internal: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:12:38Z"
    - latency: 8.644181ms
      message: 'load-balancer-api-internal: resolved host name a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:12:38Z"
    - latency: 4.10406ms
      message: 'load-balancer-api-internal: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:11:38Z"
    - latency: 8.596643ms
      message: 'load-balancer-api-internal: resolved host name a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:11:38Z"
    - latency: 4.289053ms
      message: 'load-balancer-api-internal: tcp connection to a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:10:38Z"
    - latency: 7.751109ms
      message: 'load-balancer-api-internal: resolved host name a4c91cb6cb40d417aab7ae4ae30f802c-562a9a17b3ee54d1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:10:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:50:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-network-check-target-ip-10-0-128-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 916d0141-7d7c-4808-9d51-f826b23bbc7b
    resourceVersion: "19378"
    uid: 9bb70077-5c8c-4899-990b-18cf67f4a9ed
  spec:
    sourcePod: network-check-source-6f8b768455-f6twl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:57:38Z"
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 749.662µs
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:11:38Z"
    - latency: 881.933µs
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:10:38Z"
    - latency: 850.118µs
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:09:38Z"
    - latency: 819.577µs
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:08:38Z"
    - latency: 796.562µs
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:07:38Z"
    - latency: 794.927µs
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:06:38Z"
    - latency: 919.221µs
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:05:38Z"
    - latency: 826.846µs
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:04:38Z"
    - latency: 1.122569ms
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:03:38Z"
    - latency: 797.771µs
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:02:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:50:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-network-check-target-ip-10-0-138-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 916d0141-7d7c-4808-9d51-f826b23bbc7b
    resourceVersion: "19379"
    uid: 2d608908-6e33-4fbc-95d8-12d4cce16a1f
  spec:
    sourcePod: network-check-source-6f8b768455-f6twl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:57:38Z"
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.081046ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:11:38Z"
    - latency: 2.328472ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:10:38Z"
    - latency: 2.319682ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:09:38Z"
    - latency: 2.065625ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:08:38Z"
    - latency: 2.482722ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:07:38Z"
    - latency: 2.088159ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:06:38Z"
    - latency: 2.138537ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:05:38Z"
    - latency: 2.394416ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:04:38Z"
    - latency: 2.816236ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:03:38Z"
    - latency: 2.086178ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:02:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:50:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-network-check-target-ip-10-0-141-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 916d0141-7d7c-4808-9d51-f826b23bbc7b
    resourceVersion: "19380"
    uid: eb358ecf-85d6-42ae-bf0c-4072666a2410
  spec:
    sourcePod: network-check-source-6f8b768455-f6twl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:57:38Z"
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.922015ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:11:38Z"
    - latency: 2.114846ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:10:38Z"
    - latency: 1.992957ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:09:38Z"
    - latency: 2.481733ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:08:38Z"
    - latency: 1.851809ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:07:38Z"
    - latency: 2.062516ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:06:38Z"
    - latency: 2.021925ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:05:38Z"
    - latency: 1.934517ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:04:38Z"
    - latency: 2.626126ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:03:38Z"
    - latency: 2.203085ms
      message: 'network-check-target-ip-10-0-141-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:02:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:50:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 916d0141-7d7c-4808-9d51-f826b23bbc7b
    resourceVersion: "20717"
    uid: 684358f5-be06-410e-b990-65c18658bc83
  spec:
    sourcePod: network-check-source-6f8b768455-f6twl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:56:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.037872ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:14:38Z"
    - latency: 2.005576ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:14:38Z"
    - latency: 1.183159ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:13:38Z"
    - latency: 1.857095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:13:38Z"
    - latency: 1.309251ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:12:38Z"
    - latency: 1.964481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:12:38Z"
    - latency: 1.057301ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:11:38Z"
    - latency: 1.839991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:11:38Z"
    - latency: 828.803µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T09:10:38Z"
    - latency: 1.746804ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T09:10:38Z"
kind: List
metadata:
  resourceVersion: ""