apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-253-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-253.ec2.internal
      uid: a85aa910-25aa-47a0-8f70-709be47c6d41
    resourceVersion: "44308"
    uid: 676292ac-fd92-45bc-918d-02930ae0d631
  spec:
    sourcePod: network-check-source-7f44b6dd87-sm4mw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:20:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.13662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:48:09Z"
    - latency: 796.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:47:09Z"
    - latency: 1.237364ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:46:09Z"
    - latency: 1.146325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:45:09Z"
    - latency: 1.157224ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:44:09Z"
    - latency: 1.13281ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:43:09Z"
    - latency: 895.892µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:42:09Z"
    - latency: 1.100155ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:41:09Z"
    - latency: 1.108844ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:40:09Z"
    - latency: 923.937µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:39:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-253-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-253.ec2.internal
      uid: a85aa910-25aa-47a0-8f70-709be47c6d41
    resourceVersion: "45283"
    uid: 8f604567-def5-4db1-ba5c-e1e74740e826
  spec:
    sourcePod: network-check-source-7f44b6dd87-sm4mw
    targetEndpoint: a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:19:09Z"
      message: 'load-balancer-api-external: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.010336ms
      message: 'load-balancer-api-external: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:49:09Z"
    - latency: 8.196472ms
      message: 'load-balancer-api-external: resolved host name a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:49:09Z"
    - latency: 5.331263ms
      message: 'load-balancer-api-external: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:48:09Z"
    - latency: 8.700276ms
      message: 'load-balancer-api-external: resolved host name a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:48:09Z"
    - latency: 4.194461ms
      message: 'load-balancer-api-external: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:47:09Z"
    - latency: 8.174079ms
      message: 'load-balancer-api-external: resolved host name a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:47:09Z"
    - latency: 4.430665ms
      message: 'load-balancer-api-external: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:46:09Z"
    - latency: 9.502334ms
      message: 'load-balancer-api-external: resolved host name a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:46:09Z"
    - latency: 5.006512ms
      message: 'load-balancer-api-external: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:45:09Z"
    - latency: 8.678757ms
      message: 'load-balancer-api-external: resolved host name a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:45:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-253-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-253.ec2.internal
      uid: a85aa910-25aa-47a0-8f70-709be47c6d41
    resourceVersion: "45284"
    uid: 56d04c31-ebf8-49b8-b337-b61c9086f769
  spec:
    sourcePod: network-check-source-7f44b6dd87-sm4mw
    targetEndpoint: a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:19:09Z"
      message: 'load-balancer-api-internal: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.045431ms
      message: 'load-balancer-api-internal: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:49:09Z"
    - latency: 8.179377ms
      message: 'load-balancer-api-internal: resolved host name a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:49:09Z"
    - latency: 5.071012ms
      message: 'load-balancer-api-internal: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:48:09Z"
    - latency: 8.744389ms
      message: 'load-balancer-api-internal: resolved host name a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:48:09Z"
    - latency: 3.258637ms
      message: 'load-balancer-api-internal: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:47:09Z"
    - latency: 8.212571ms
      message: 'load-balancer-api-internal: resolved host name a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:47:09Z"
    - latency: 4.844344ms
      message: 'load-balancer-api-internal: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:46:09Z"
    - latency: 9.478142ms
      message: 'load-balancer-api-internal: resolved host name a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:46:09Z"
    - latency: 5.039203ms
      message: 'load-balancer-api-internal: tcp connection to a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:45:09Z"
    - latency: 8.779892ms
      message: 'load-balancer-api-internal: resolved host name a16394cb3141b4bf1a61ceeba6686bd6-e9007485a6b3ab7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:45:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-253-to-network-check-target-ip-10-0-138-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-253.ec2.internal
      uid: a85aa910-25aa-47a0-8f70-709be47c6d41
    resourceVersion: "44306"
    uid: e7219388-7658-4fde-a75f-be1e1e8b4e9b
  spec:
    sourcePod: network-check-source-7f44b6dd87-sm4mw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:20:09Z"
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.110118ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:48:09Z"
    - latency: 1.803129ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:47:09Z"
    - latency: 2.274538ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:46:09Z"
    - latency: 2.088498ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:45:09Z"
    - latency: 2.026957ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:44:09Z"
    - latency: 2.037216ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:43:09Z"
    - latency: 2.293583ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:42:09Z"
    - latency: 2.169458ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:41:09Z"
    - latency: 1.922558ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:40:09Z"
    - latency: 1.958431ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:39:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-253-to-network-check-target-ip-10-0-139-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-253.ec2.internal
      uid: a85aa910-25aa-47a0-8f70-709be47c6d41
    resourceVersion: "44307"
    uid: 78112608-2cd5-4135-aa42-1f8e3d4faa25
  spec:
    sourcePod: network-check-source-7f44b6dd87-sm4mw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:20:09Z"
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.990557ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:48:09Z"
    - latency: 1.836117ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:47:09Z"
    - latency: 1.76638ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:46:09Z"
    - latency: 1.87017ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:45:09Z"
    - latency: 1.823823ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:44:09Z"
    - latency: 2.079526ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:43:09Z"
    - latency: 1.922401ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:42:09Z"
    - latency: 1.93064ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:41:09Z"
    - latency: 1.873072ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:40:09Z"
    - latency: 1.915682ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:39:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-253-to-network-check-target-ip-10-0-140-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-253.ec2.internal
      uid: a85aa910-25aa-47a0-8f70-709be47c6d41
    resourceVersion: "44305"
    uid: c4e4624e-2b29-4986-bf4b-b32aa7a9d071
  spec:
    sourcePod: network-check-source-7f44b6dd87-sm4mw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:20:09Z"
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.258µs
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:48:09Z"
    - latency: 1.083044ms
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:47:09Z"
    - latency: 751.59µs
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:46:09Z"
    - latency: 858.989µs
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:45:09Z"
    - latency: 795.019µs
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:44:09Z"
    - latency: 958.688µs
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:43:09Z"
    - latency: 906.485µs
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:42:09Z"
    - latency: 844.938µs
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:41:09Z"
    - latency: 864.076µs
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:40:09Z"
    - latency: 875.041µs
      message: 'network-check-target-ip-10-0-140-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:39:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T10:13:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-253-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-253.ec2.internal
      uid: a85aa910-25aa-47a0-8f70-709be47c6d41
    resourceVersion: "45281"
    uid: 18a0d91a-7633-44fe-88bd-cbc754323455
  spec:
    sourcePod: network-check-source-7f44b6dd87-sm4mw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T10:19:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.123µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:49:09Z"
    - latency: 1.580185ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:49:09Z"
    - latency: 843.035µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:48:09Z"
    - latency: 1.611745ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:48:09Z"
    - latency: 808.441µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:47:09Z"
    - latency: 1.872656ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:47:09Z"
    - latency: 896.832µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:46:09Z"
    - latency: 1.748901ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:46:09Z"
    - latency: 787.631µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T10:45:09Z"
    - latency: 2.007961ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T10:45:09Z"
kind: List
metadata:
  resourceVersion: ""