apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T13:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-142.ec2.internal
      uid: 215b94e7-aa7e-4736-afdf-d308c1967863
    resourceVersion: "43220"
    uid: f87fbdef-621b-4442-8551-e1a64620375f
  spec:
    sourcePod: network-check-source-7f44b6dd87-d8lss
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T13:12:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.416µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:33:10Z"
    - latency: 968.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:32:10Z"
    - latency: 1.309066ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:31:10Z"
    - latency: 952.175µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:30:10Z"
    - latency: 1.469319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:29:10Z"
    - latency: 964.725µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:28:10Z"
    - latency: 953.657µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:27:10Z"
    - latency: 995.48µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:26:10Z"
    - latency: 1.050892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:25:10Z"
    - latency: 1.013534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:24:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T13:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-142.ec2.internal
      uid: 215b94e7-aa7e-4736-afdf-d308c1967863
    resourceVersion: "45509"
    uid: 068eebee-25c9-459e-832d-d0008bbbe8b9
  spec:
    sourcePod: network-check-source-7f44b6dd87-d8lss
    targetEndpoint: a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T13:11:10Z"
      message: 'load-balancer-api-external: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.952078ms
      message: 'load-balancer-api-external: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:35:10Z"
    - latency: 7.522923ms
      message: 'load-balancer-api-external: resolved host name a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:35:10Z"
    - latency: 5.321018ms
      message: 'load-balancer-api-external: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:34:10Z"
    - latency: 7.928652ms
      message: 'load-balancer-api-external: resolved host name a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:34:10Z"
    - latency: 4.016973ms
      message: 'load-balancer-api-external: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:33:10Z"
    - latency: 8.901132ms
      message: 'load-balancer-api-external: resolved host name a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:33:10Z"
    - latency: 5.609662ms
      message: 'load-balancer-api-external: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:32:10Z"
    - latency: 9.761093ms
      message: 'load-balancer-api-external: resolved host name a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:32:10Z"
    - latency: 3.558397ms
      message: 'load-balancer-api-external: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:31:10Z"
    - latency: 12.176457ms
      message: 'load-balancer-api-external: resolved host name a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:31:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T13:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-142.ec2.internal
      uid: 215b94e7-aa7e-4736-afdf-d308c1967863
    resourceVersion: "45508"
    uid: ae49e275-d08e-433b-a43a-054b3543c872
  spec:
    sourcePod: network-check-source-7f44b6dd87-d8lss
    targetEndpoint: a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T13:11:10Z"
      message: 'load-balancer-api-internal: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.931222ms
      message: 'load-balancer-api-internal: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:35:10Z"
    - latency: 7.549674ms
      message: 'load-balancer-api-internal: resolved host name a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:35:10Z"
    - latency: 5.37232ms
      message: 'load-balancer-api-internal: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:34:10Z"
    - latency: 7.988114ms
      message: 'load-balancer-api-internal: resolved host name a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:34:10Z"
    - latency: 4.287493ms
      message: 'load-balancer-api-internal: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:33:10Z"
    - latency: 8.935616ms
      message: 'load-balancer-api-internal: resolved host name a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:33:10Z"
    - latency: 3.662236ms
      message: 'load-balancer-api-internal: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:32:10Z"
    - latency: 9.791091ms
      message: 'load-balancer-api-internal: resolved host name a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:32:10Z"
    - latency: 3.035522ms
      message: 'load-balancer-api-internal: tcp connection to a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:31:10Z"
    - latency: 12.203225ms
      message: 'load-balancer-api-internal: resolved host name a9e0b5309f9174a80993606e8fe8f467-5d904207e1cd598a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:31:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T13:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-142-to-network-check-target-ip-10-0-133-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-142.ec2.internal
      uid: 215b94e7-aa7e-4736-afdf-d308c1967863
    resourceVersion: "43218"
    uid: 32ccc056-d185-498d-85bb-8701748265ed
  spec:
    sourcePod: network-check-source-7f44b6dd87-d8lss
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T13:12:10Z"
      message: 'network-check-target-ip-10-0-133-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.266016ms
      message: 'network-check-target-ip-10-0-133-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:33:10Z"
    - latency: 2.457432ms
      message: 'network-check-target-ip-10-0-133-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:32:10Z"
    - latency: 2.173728ms
      message: 'network-check-target-ip-10-0-133-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:31:10Z"
    - latency: 2.302846ms
      message: 'network-check-target-ip-10-0-133-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:30:10Z"
    - latency: 2.566122ms
      message: 'network-check-target-ip-10-0-133-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:29:10Z"
    - latency: 1.794109ms
      message: 'network-check-target-ip-10-0-133-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:28:10Z"
    - latency: 2.21369ms
      message: 'network-check-target-ip-10-0-133-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:27:10Z"
    - latency: 1.971645ms
      message: 'network-check-target-ip-10-0-133-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:26:10Z"
    - latency: 2.019978ms
      message: 'network-check-target-ip-10-0-133-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:25:10Z"
    - latency: 1.97624ms
      message: 'network-check-target-ip-10-0-133-64: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:24:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T13:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-142-to-network-check-target-ip-10-0-140-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-142.ec2.internal
      uid: 215b94e7-aa7e-4736-afdf-d308c1967863
    resourceVersion: "43219"
    uid: ea7ffc97-b137-4709-a88f-9ceb50af748c
  spec:
    sourcePod: network-check-source-7f44b6dd87-d8lss
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T13:12:10Z"
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.173815ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:33:10Z"
    - latency: 2.582244ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:32:10Z"
    - latency: 1.845777ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:31:10Z"
    - latency: 2.196987ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:30:10Z"
    - latency: 2.19133ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:29:10Z"
    - latency: 2.032396ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:28:10Z"
    - latency: 2.104562ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:27:10Z"
    - latency: 2.239002ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:26:10Z"
    - latency: 2.01371ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:25:10Z"
    - latency: 2.118428ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:24:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T13:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-142-to-network-check-target-ip-10-0-143-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-142.ec2.internal
      uid: 215b94e7-aa7e-4736-afdf-d308c1967863
    resourceVersion: "43217"
    uid: 07f87426-762e-4b7f-8310-3192a7c3e7ff
  spec:
    sourcePod: network-check-source-7f44b6dd87-d8lss
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T13:12:10Z"
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.249503ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:33:10Z"
    - latency: 968.936µs
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:32:10Z"
    - latency: 1.488853ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:31:10Z"
    - latency: 821.126µs
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:30:10Z"
    - latency: 733.246µs
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:29:10Z"
    - latency: 1.145623ms
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:28:10Z"
    - latency: 813.934µs
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:27:10Z"
    - latency: 853.47µs
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:26:10Z"
    - latency: 809.079µs
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:25:10Z"
    - latency: 821.242µs
      message: 'network-check-target-ip-10-0-143-142: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:24:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T13:05:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-142.ec2.internal
      uid: 215b94e7-aa7e-4736-afdf-d308c1967863
    resourceVersion: "45507"
    uid: 835bf436-258a-4dfe-851c-32a231978774
  spec:
    sourcePod: network-check-source-7f44b6dd87-d8lss
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T13:11:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 676.555µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:35:10Z"
    - latency: 1.534561ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:35:10Z"
    - latency: 883.192µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:34:10Z"
    - latency: 1.890225ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:34:10Z"
    - latency: 689.892µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:33:10Z"
    - latency: 2.085817ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:33:10Z"
    - latency: 957.358µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:32:10Z"
    - latency: 1.601722ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:32:10Z"
    - latency: 779.391µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T13:31:10Z"
    - latency: 1.602752ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T13:31:10Z"
kind: List
metadata:
  resourceVersion: ""