apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T12:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-238.ec2.internal
      uid: 6682cc7c-3459-434e-9180-352abfc45998
    resourceVersion: "18364"
    uid: 9678e5c0-585c-4b1a-a51a-0dee5b129ec1
  spec:
    sourcePod: network-check-source-7f44b6dd87-wlq67
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T12:22:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.888µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:29:07Z"
    - latency: 884.956µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:28:07Z"
    - latency: 1.252833ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:27:07Z"
    - latency: 952.396µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:26:07Z"
    - latency: 1.112601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:25:07Z"
    - latency: 1.056695ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:24:07Z"
    - latency: 999.627µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:23:07Z"
    - latency: 880.854µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:22:07Z"
    - latency: 917.872µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:21:07Z"
    - latency: 881.896µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:20:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T12:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-238.ec2.internal
      uid: 6682cc7c-3459-434e-9180-352abfc45998
    resourceVersion: "20474"
    uid: 6bd145f7-56ec-4b5f-a4c3-9662cd97e5c8
  spec:
    sourcePod: network-check-source-7f44b6dd87-wlq67
    targetEndpoint: a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T12:21:07Z"
      message: 'load-balancer-api-external: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.805754ms
      message: 'load-balancer-api-external: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:33:07Z"
    - latency: 7.526391ms
      message: 'load-balancer-api-external: resolved host name a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:33:07Z"
    - latency: 4.888963ms
      message: 'load-balancer-api-external: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:32:07Z"
    - latency: 7.889132ms
      message: 'load-balancer-api-external: resolved host name a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:32:07Z"
    - latency: 5.432538ms
      message: 'load-balancer-api-external: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:31:07Z"
    - latency: 7.709571ms
      message: 'load-balancer-api-external: resolved host name a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:31:07Z"
    - latency: 4.785821ms
      message: 'load-balancer-api-external: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:30:07Z"
    - latency: 8.282734ms
      message: 'load-balancer-api-external: resolved host name a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:30:07Z"
    - latency: 4.407061ms
      message: 'load-balancer-api-external: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:29:07Z"
    - latency: 8.308977ms
      message: 'load-balancer-api-external: resolved host name a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:29:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T12:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-238.ec2.internal
      uid: 6682cc7c-3459-434e-9180-352abfc45998
    resourceVersion: "20475"
    uid: 6891ec8c-2106-497d-8fea-f7eab9e607c7
  spec:
    sourcePod: network-check-source-7f44b6dd87-wlq67
    targetEndpoint: a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T12:21:07Z"
      message: 'load-balancer-api-internal: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.410109ms
      message: 'load-balancer-api-internal: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:33:07Z"
    - latency: 7.626554ms
      message: 'load-balancer-api-internal: resolved host name a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:33:07Z"
    - latency: 4.097071ms
      message: 'load-balancer-api-internal: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:32:07Z"
    - latency: 7.783784ms
      message: 'load-balancer-api-internal: resolved host name a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:32:07Z"
    - latency: 5.413967ms
      message: 'load-balancer-api-internal: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:31:07Z"
    - latency: 7.863374ms
      message: 'load-balancer-api-internal: resolved host name a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:31:07Z"
    - latency: 4.776251ms
      message: 'load-balancer-api-internal: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:30:07Z"
    - latency: 8.264697ms
      message: 'load-balancer-api-internal: resolved host name a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:30:07Z"
    - latency: 4.87213ms
      message: 'load-balancer-api-internal: tcp connection to a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:29:07Z"
    - latency: 8.415543ms
      message: 'load-balancer-api-internal: resolved host name a016746890bdf4448812110a803825f2-bd9b274d12ee7c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:29:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T12:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-238-to-network-check-target-ip-10-0-130-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-238.ec2.internal
      uid: 6682cc7c-3459-434e-9180-352abfc45998
    resourceVersion: "18362"
    uid: 8aa3c439-8d6e-48e2-985d-cc8652954dff
  spec:
    sourcePod: network-check-source-7f44b6dd87-wlq67
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T12:22:07Z"
      message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.050111ms
      message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:29:07Z"
    - latency: 2.202576ms
      message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:28:07Z"
    - latency: 2.351052ms
      message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:27:07Z"
    - latency: 2.22049ms
      message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:26:07Z"
    - latency: 2.292047ms
      message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:25:07Z"
    - latency: 2.525138ms
      message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:24:07Z"
    - latency: 2.219259ms
      message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:23:07Z"
    - latency: 2.142971ms
      message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:22:07Z"
    - latency: 2.254707ms
      message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:21:07Z"
    - latency: 2.271063ms
      message: 'network-check-target-ip-10-0-130-54: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:20:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T12:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-238-to-network-check-target-ip-10-0-134-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-238.ec2.internal
      uid: 6682cc7c-3459-434e-9180-352abfc45998
    resourceVersion: "18363"
    uid: 8c43692f-2869-4ed9-8f84-7da8a9cfc3a8
  spec:
    sourcePod: network-check-source-7f44b6dd87-wlq67
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T12:22:07Z"
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.183353ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:29:07Z"
    - latency: 2.459289ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:28:07Z"
    - latency: 2.125825ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:27:07Z"
    - latency: 2.246825ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:26:07Z"
    - latency: 2.072041ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:25:07Z"
    - latency: 2.117773ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:24:07Z"
    - latency: 2.203215ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:23:07Z"
    - latency: 2.001446ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:22:07Z"
    - latency: 2.208919ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:21:07Z"
    - latency: 2.235581ms
      message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:20:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T12:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-238-to-network-check-target-ip-10-0-140-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-238.ec2.internal
      uid: 6682cc7c-3459-434e-9180-352abfc45998
    resourceVersion: "18361"
    uid: e2e4807f-3ab6-4cd6-8baa-34359836fb01
  spec:
    sourcePod: network-check-source-7f44b6dd87-wlq67
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T12:22:07Z"
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 811.239µs
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:29:07Z"
    - latency: 957.315µs
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:28:07Z"
    - latency: 934.981µs
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:27:07Z"
    - latency: 754.351µs
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:26:07Z"
    - latency: 1.497158ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:25:07Z"
    - latency: 873.65µs
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:24:07Z"
    - latency: 1.153768ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:23:07Z"
    - latency: 1.252282ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:22:07Z"
    - latency: 864.564µs
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:21:07Z"
    - latency: 917.499µs
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:20:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T12:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-238.ec2.internal
      uid: 6682cc7c-3459-434e-9180-352abfc45998
    resourceVersion: "20473"
    uid: f4b8dc92-e902-49c6-bcfa-ed4b591c7ea8
  spec:
    sourcePod: network-check-source-7f44b6dd87-wlq67
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T12:21:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 770.183µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:33:07Z"
    - latency: 1.756659ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:33:07Z"
    - latency: 746.595µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:32:07Z"
    - latency: 1.698743ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:32:07Z"
    - latency: 907.47µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:31:07Z"
    - latency: 1.614193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:31:07Z"
    - latency: 796.508µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:30:07Z"
    - latency: 2.19694ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:30:07Z"
    - latency: 1.283346ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T12:29:07Z"
    - latency: 1.739741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T12:29:07Z"
kind: List
metadata:
  resourceVersion: ""