apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T16:11:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 84cdfa27-8128-4aa8-a01c-422f5c52cfce
    resourceVersion: "43179"
    uid: 1dcb3f87-befb-4163-b873-762531410bbf
  spec:
    sourcePod: network-check-source-7f44b6dd87-d987z
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T16:18:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.699233ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:39:26Z"
    - latency: 1.049192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:38:26Z"
    - latency: 1.069413ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:37:26Z"
    - latency: 1.248733ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:36:26Z"
    - latency: 902.672µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:35:26Z"
    - latency: 705.857µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:34:26Z"
    - latency: 986.755µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:33:26Z"
    - latency: 1.130753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:32:26Z"
    - latency: 1.251956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:31:26Z"
    - latency: 1.163728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T16:11:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 84cdfa27-8128-4aa8-a01c-422f5c52cfce
    resourceVersion: "45726"
    uid: dfc12f09-31c9-46c5-bb95-8c10b6f9abfa
  spec:
    sourcePod: network-check-source-7f44b6dd87-d987z
    targetEndpoint: a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T16:17:26Z"
      message: 'load-balancer-api-external: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.781451ms
      message: 'load-balancer-api-external: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:41:26Z"
    - latency: 7.662651ms
      message: 'load-balancer-api-external: resolved host name a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:41:26Z"
    - latency: 3.162866ms
      message: 'load-balancer-api-external: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:40:26Z"
    - latency: 8.134495ms
      message: 'load-balancer-api-external: resolved host name a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:40:26Z"
    - latency: 4.023343ms
      message: 'load-balancer-api-external: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:39:26Z"
    - latency: 10.491513ms
      message: 'load-balancer-api-external: resolved host name a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:39:26Z"
    - latency: 5.252212ms
      message: 'load-balancer-api-external: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:38:26Z"
    - latency: 8.227111ms
      message: 'load-balancer-api-external: resolved host name a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:38:26Z"
    - latency: 4.548986ms
      message: 'load-balancer-api-external: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:37:26Z"
    - latency: 8.004521ms
      message: 'load-balancer-api-external: resolved host name a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T16:11:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 84cdfa27-8128-4aa8-a01c-422f5c52cfce
    resourceVersion: "45727"
    uid: 984bb6cb-a684-48f0-932c-84121d413dd0
  spec:
    sourcePod: network-check-source-7f44b6dd87-d987z
    targetEndpoint: a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T16:17:26Z"
      message: 'load-balancer-api-internal: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.791375ms
      message: 'load-balancer-api-internal: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:41:26Z"
    - latency: 7.695511ms
      message: 'load-balancer-api-internal: resolved host name a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:41:26Z"
    - latency: 2.967794ms
      message: 'load-balancer-api-internal: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:40:26Z"
    - latency: 8.111098ms
      message: 'load-balancer-api-internal: resolved host name a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:40:26Z"
    - latency: 3.5228ms
      message: 'load-balancer-api-internal: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:39:26Z"
    - latency: 10.548518ms
      message: 'load-balancer-api-internal: resolved host name a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:39:26Z"
    - latency: 5.236569ms
      message: 'load-balancer-api-internal: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:38:26Z"
    - latency: 8.129576ms
      message: 'load-balancer-api-internal: resolved host name a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:38:26Z"
    - latency: 4.455899ms
      message: 'load-balancer-api-internal: tcp connection to a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:37:26Z"
    - latency: 8.077344ms
      message: 'load-balancer-api-internal: resolved host name a7b78ebbe7ae14ca3bc07e84e52378aa-ec102ab54875837b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T16:11:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-network-check-target-ip-10-0-132-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 84cdfa27-8128-4aa8-a01c-422f5c52cfce
    resourceVersion: "43177"
    uid: 3ca0f86a-7f1f-4d53-a61a-e3a93a51ace8
  spec:
    sourcePod: network-check-source-7f44b6dd87-d987z
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T16:18:26Z"
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.218089ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:39:26Z"
    - latency: 2.587117ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:38:26Z"
    - latency: 2.283062ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:37:26Z"
    - latency: 1.963077ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:36:26Z"
    - latency: 2.258785ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:35:26Z"
    - latency: 2.086804ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:34:26Z"
    - latency: 2.301229ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:33:26Z"
    - latency: 2.196969ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:32:26Z"
    - latency: 2.004675ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:31:26Z"
    - latency: 2.064917ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T16:11:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-network-check-target-ip-10-0-134-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 84cdfa27-8128-4aa8-a01c-422f5c52cfce
    resourceVersion: "43175"
    uid: 410f8dc6-67f4-4b03-a32f-ac385d91e85b
  spec:
    sourcePod: network-check-source-7f44b6dd87-d987z
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T16:18:26Z"
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 848.127µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:39:26Z"
    - latency: 848.587µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:38:26Z"
    - latency: 826.129µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:37:26Z"
    - latency: 1.155812ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:36:26Z"
    - latency: 1.279935ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:35:26Z"
    - latency: 766.058µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:34:26Z"
    - latency: 738.485µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:33:26Z"
    - latency: 794.518µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:32:26Z"
    - latency: 736.681µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:31:26Z"
    - latency: 808.524µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T16:11:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-network-check-target-ip-10-0-143-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 84cdfa27-8128-4aa8-a01c-422f5c52cfce
    resourceVersion: "43176"
    uid: b21e804c-20d4-46e1-b0f9-9b5eacda8113
  spec:
    sourcePod: network-check-source-7f44b6dd87-d987z
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T16:18:26Z"
      message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.187732ms
      message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:39:26Z"
    - latency: 2.273989ms
      message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:38:26Z"
    - latency: 2.348439ms
      message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:37:26Z"
    - latency: 2.634732ms
      message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:36:26Z"
    - latency: 2.514685ms
      message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:35:26Z"
    - latency: 1.919416ms
      message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:34:26Z"
    - latency: 2.256209ms
      message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:33:26Z"
    - latency: 2.250175ms
      message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:32:26Z"
    - latency: 2.008726ms
      message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:31:26Z"
    - latency: 2.220292ms
      message: 'network-check-target-ip-10-0-143-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-28T16:11:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 84cdfa27-8128-4aa8-a01c-422f5c52cfce
    resourceVersion: "45725"
    uid: 8f1e1153-562b-4e91-a95c-ca300216c85b
  spec:
    sourcePod: network-check-source-7f44b6dd87-d987z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-28T16:17:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.176501ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:41:26Z"
    - latency: 1.641208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:41:26Z"
    - latency: 981.439µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:40:26Z"
    - latency: 1.839317ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:40:26Z"
    - latency: 1.248579ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:39:26Z"
    - latency: 1.759193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:39:26Z"
    - latency: 1.161219ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:38:26Z"
    - latency: 1.707384ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:38:26Z"
    - latency: 771.272µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-28T16:37:26Z"
    - latency: 1.741189ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-28T16:37:26Z"
kind: List
metadata:
  resourceVersion: ""