apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:13:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-142.ec2.internal
      uid: df0b8829-a67e-4944-820d-fea4fe37f62d
    resourceVersion: "67375"
    uid: b717b0ca-d9b0-4d00-95fc-dd3a93c9cab9
  spec:
    sourcePod: network-check-source-6f8b768455-4n827
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:20:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.362µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:57Z"
    - latency: 858.377µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:57Z"
    - latency: 851.493µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:46:57Z"
    - latency: 792.593µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:45:57Z"
    - latency: 1.04035ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:44:57Z"
    - latency: 1.26613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:43:57Z"
    - latency: 1.050394ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:42:57Z"
    - latency: 882.664µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:41:57Z"
    - latency: 884.188µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:40:57Z"
    - latency: 1.392616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:39:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:13:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-142.ec2.internal
      uid: df0b8829-a67e-4944-820d-fea4fe37f62d
    resourceVersion: "68587"
    uid: 22fe5408-d664-450c-9579-164b295ac211
  spec:
    sourcePod: network-check-source-6f8b768455-4n827
    targetEndpoint: a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:19:57Z"
      message: 'load-balancer-api-external: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.34265ms
      message: 'load-balancer-api-external: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:57Z"
    - latency: 8.028132ms
      message: 'load-balancer-api-external: resolved host name a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:49:57Z"
    - latency: 4.793294ms
      message: 'load-balancer-api-external: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:57Z"
    - latency: 11.30533ms
      message: 'load-balancer-api-external: resolved host name a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:48:57Z"
    - latency: 3.706278ms
      message: 'load-balancer-api-external: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:57Z"
    - latency: 6.410078ms
      message: 'load-balancer-api-external: resolved host name a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:47:57Z"
    - latency: 4.099055ms
      message: 'load-balancer-api-external: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:46:57Z"
    - latency: 7.81792ms
      message: 'load-balancer-api-external: resolved host name a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:46:57Z"
    - latency: 4.699295ms
      message: 'load-balancer-api-external: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:45:57Z"
    - latency: 9.174518ms
      message: 'load-balancer-api-external: resolved host name a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:45:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:13:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-142.ec2.internal
      uid: df0b8829-a67e-4944-820d-fea4fe37f62d
    resourceVersion: "68588"
    uid: d9b67da2-17f1-4fca-af45-0724b982b8e6
  spec:
    sourcePod: network-check-source-6f8b768455-4n827
    targetEndpoint: a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:19:57Z"
      message: 'load-balancer-api-internal: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.488515ms
      message: 'load-balancer-api-internal: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:57Z"
    - latency: 8.003346ms
      message: 'load-balancer-api-internal: resolved host name a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:49:57Z"
    - latency: 4.382202ms
      message: 'load-balancer-api-internal: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:57Z"
    - latency: 11.264409ms
      message: 'load-balancer-api-internal: resolved host name a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:48:57Z"
    - latency: 3.726076ms
      message: 'load-balancer-api-internal: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:57Z"
    - latency: 6.364359ms
      message: 'load-balancer-api-internal: resolved host name a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:47:57Z"
    - latency: 4.502335ms
      message: 'load-balancer-api-internal: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:46:57Z"
    - latency: 7.780194ms
      message: 'load-balancer-api-internal: resolved host name a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:46:57Z"
    - latency: 4.709435ms
      message: 'load-balancer-api-internal: tcp connection to a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:45:57Z"
    - latency: 9.144145ms
      message: 'load-balancer-api-internal: resolved host name a41b8f0ee2acd4f9499aff8c86845b2a-73d027a4b27ddab6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:45:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:13:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-142-to-network-check-target-ip-10-0-131-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-142.ec2.internal
      uid: df0b8829-a67e-4944-820d-fea4fe37f62d
    resourceVersion: "67373"
    uid: 6d5ca934-01aa-4c53-83ae-2716ee65c9c9
  spec:
    sourcePod: network-check-source-6f8b768455-4n827
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:20:57Z"
      message: 'network-check-target-ip-10-0-131-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.260285ms
      message: 'network-check-target-ip-10-0-131-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:57Z"
    - latency: 2.472979ms
      message: 'network-check-target-ip-10-0-131-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:57Z"
    - latency: 2.375649ms
      message: 'network-check-target-ip-10-0-131-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:46:57Z"
    - latency: 2.496819ms
      message: 'network-check-target-ip-10-0-131-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:45:57Z"
    - latency: 2.554445ms
      message: 'network-check-target-ip-10-0-131-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:44:57Z"
    - latency: 2.24456ms
      message: 'network-check-target-ip-10-0-131-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:43:57Z"
    - latency: 2.591692ms
      message: 'network-check-target-ip-10-0-131-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:42:57Z"
    - latency: 2.858007ms
      message: 'network-check-target-ip-10-0-131-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:41:57Z"
    - latency: 2.936942ms
      message: 'network-check-target-ip-10-0-131-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:40:57Z"
    - latency: 2.541899ms
      message: 'network-check-target-ip-10-0-131-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:39:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:13:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-142-to-network-check-target-ip-10-0-134-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-142.ec2.internal
      uid: df0b8829-a67e-4944-820d-fea4fe37f62d
    resourceVersion: "67374"
    uid: 276cbd7d-64e6-4aa5-bbaf-d8e384f5851b
  spec:
    sourcePod: network-check-source-6f8b768455-4n827
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:20:57Z"
      message: 'network-check-target-ip-10-0-134-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.275998ms
      message: 'network-check-target-ip-10-0-134-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:57Z"
    - latency: 2.640104ms
      message: 'network-check-target-ip-10-0-134-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:57Z"
    - latency: 2.313756ms
      message: 'network-check-target-ip-10-0-134-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:46:57Z"
    - latency: 2.332487ms
      message: 'network-check-target-ip-10-0-134-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:45:57Z"
    - latency: 2.223271ms
      message: 'network-check-target-ip-10-0-134-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:44:57Z"
    - latency: 2.320381ms
      message: 'network-check-target-ip-10-0-134-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:43:57Z"
    - latency: 2.345649ms
      message: 'network-check-target-ip-10-0-134-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:42:57Z"
    - latency: 2.165732ms
      message: 'network-check-target-ip-10-0-134-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:41:57Z"
    - latency: 2.561862ms
      message: 'network-check-target-ip-10-0-134-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:40:57Z"
    - latency: 2.535271ms
      message: 'network-check-target-ip-10-0-134-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:39:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:13:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-142-to-network-check-target-ip-10-0-140-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-142.ec2.internal
      uid: df0b8829-a67e-4944-820d-fea4fe37f62d
    resourceVersion: "67372"
    uid: e0f02c52-763f-45d4-badd-2ef48502cc2e
  spec:
    sourcePod: network-check-source-6f8b768455-4n827
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:20:57Z"
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.452376ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:57Z"
    - latency: 895.864µs
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:57Z"
    - latency: 897.357µs
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:46:57Z"
    - latency: 1.064617ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:45:57Z"
    - latency: 821.516µs
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:44:57Z"
    - latency: 905.478µs
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:43:57Z"
    - latency: 1.00371ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:42:57Z"
    - latency: 1.078931ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:41:57Z"
    - latency: 1.439483ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:40:57Z"
    - latency: 892.702µs
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:39:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:13:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-142.ec2.internal
      uid: df0b8829-a67e-4944-820d-fea4fe37f62d
    resourceVersion: "68586"
    uid: e5277ee0-d419-4ad2-9490-b43d173d4fc0
  spec:
    sourcePod: network-check-source-6f8b768455-4n827
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:19:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 872.024µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:57Z"
    - latency: 2.630411ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:49:57Z"
    - latency: 1.163361ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:57Z"
    - latency: 2.14575ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:48:57Z"
    - latency: 999.987µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:57Z"
    - latency: 1.561425ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:47:57Z"
    - latency: 919.409µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:46:57Z"
    - latency: 1.943799ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:46:57Z"
    - latency: 895.72µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:45:57Z"
    - latency: 1.455056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:45:57Z"
kind: List
metadata:
  resourceVersion: ""