apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:43:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: d1686d1c-fc07-451d-a55d-86c0a407394b
    resourceVersion: "32233"
    uid: 15cdf9ef-53a6-4ed4-93d1-d0747dacd3ff
  spec:
    sourcePod: network-check-source-7cbc45fddc-js5vv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:50:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 891.117µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:48Z"
    - latency: 1.066756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:48Z"
    - latency: 887.106µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:48Z"
    - latency: 1.443687ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:48Z"
    - latency: 911.569µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:48Z"
    - latency: 914.65µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:48Z"
    - latency: 994.646µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:48Z"
    - latency: 946.548µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:48Z"
    - latency: 1.300769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:48Z"
    - latency: 1.117739ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:43:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: d1686d1c-fc07-451d-a55d-86c0a407394b
    resourceVersion: "32234"
    uid: 79298291-f94b-43c6-8651-b61bbf7889a4
  spec:
    sourcePod: network-check-source-7cbc45fddc-js5vv
    targetEndpoint: ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:49:48Z"
      message: 'load-balancer-api-external: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.045621ms
      message: 'load-balancer-api-external: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:48Z"
    - latency: 7.16848ms
      message: 'load-balancer-api-external: resolved host name ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:25:48Z"
    - latency: 6.018029ms
      message: 'load-balancer-api-external: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:48Z"
    - latency: 8.338662ms
      message: 'load-balancer-api-external: resolved host name ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:24:48Z"
    - latency: 5.414661ms
      message: 'load-balancer-api-external: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:48Z"
    - latency: 8.9348ms
      message: 'load-balancer-api-external: resolved host name ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:23:48Z"
    - latency: 4.75213ms
      message: 'load-balancer-api-external: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:48Z"
    - latency: 10.490867ms
      message: 'load-balancer-api-external: resolved host name ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:22:48Z"
    - latency: 6.528835ms
      message: 'load-balancer-api-external: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:48Z"
    - latency: 8.532494ms
      message: 'load-balancer-api-external: resolved host name ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:21:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:43:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: d1686d1c-fc07-451d-a55d-86c0a407394b
    resourceVersion: "32235"
    uid: e5fc1b39-82df-4f27-9c16-a5615af3beff
  spec:
    sourcePod: network-check-source-7cbc45fddc-js5vv
    targetEndpoint: ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:49:48Z"
      message: 'load-balancer-api-internal: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.072592ms
      message: 'load-balancer-api-internal: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:48Z"
    - latency: 7.290944ms
      message: 'load-balancer-api-internal: resolved host name ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:25:48Z"
    - latency: 5.977239ms
      message: 'load-balancer-api-internal: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:48Z"
    - latency: 8.386312ms
      message: 'load-balancer-api-internal: resolved host name ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:24:48Z"
    - latency: 5.513146ms
      message: 'load-balancer-api-internal: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:48Z"
    - latency: 9.046562ms
      message: 'load-balancer-api-internal: resolved host name ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:23:48Z"
    - latency: 4.822512ms
      message: 'load-balancer-api-internal: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:48Z"
    - latency: 10.450786ms
      message: 'load-balancer-api-internal: resolved host name ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:22:48Z"
    - latency: 6.545676ms
      message: 'load-balancer-api-internal: tcp connection to ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:48Z"
    - latency: 8.556329ms
      message: 'load-balancer-api-internal: resolved host name ab3abe48208ab43a9af0e10ed4bed587-8e9b014bea6a9bf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:21:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:43:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-network-check-target-ip-10-0-131-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: d1686d1c-fc07-451d-a55d-86c0a407394b
    resourceVersion: "32229"
    uid: 6a0b8cc5-e154-482d-9888-0d81a6032663
  spec:
    sourcePod: network-check-source-7cbc45fddc-js5vv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:50:48Z"
      message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.975µs
      message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:48Z"
    - latency: 884.305µs
      message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:48Z"
    - latency: 972.902µs
      message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:48Z"
    - latency: 940.299µs
      message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:48Z"
    - latency: 1.003ms
      message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:48Z"
    - latency: 779.889µs
      message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:48Z"
    - latency: 888.935µs
      message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:48Z"
    - latency: 774.715µs
      message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:48Z"
    - latency: 1.464344ms
      message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:48Z"
    - latency: 841.188µs
      message: 'network-check-target-ip-10-0-131-182: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:43:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-network-check-target-ip-10-0-135-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: d1686d1c-fc07-451d-a55d-86c0a407394b
    resourceVersion: "32231"
    uid: a240ed40-c51e-48ff-97f9-168b3dd4bd2d
  spec:
    sourcePod: network-check-source-7cbc45fddc-js5vv
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:50:48Z"
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.305462ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:48Z"
    - latency: 2.325512ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:48Z"
    - latency: 2.292114ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:48Z"
    - latency: 2.288039ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:48Z"
    - latency: 2.2796ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:48Z"
    - latency: 2.476073ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:48Z"
    - latency: 2.112303ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:48Z"
    - latency: 2.4466ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:48Z"
    - latency: 2.432429ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:48Z"
    - latency: 2.541967ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:43:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-network-check-target-ip-10-0-139-237
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: d1686d1c-fc07-451d-a55d-86c0a407394b
    resourceVersion: "32230"
    uid: 42a943b2-cdfa-499b-9113-a038df5723d5
  spec:
    sourcePod: network-check-source-7cbc45fddc-js5vv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:50:48Z"
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.863353ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:48Z"
    - latency: 1.857784ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:48Z"
    - latency: 1.891383ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:48Z"
    - latency: 1.843516ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:48Z"
    - latency: 1.813457ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:48Z"
    - latency: 1.958647ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:48Z"
    - latency: 2.111513ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:19:48Z"
    - latency: 1.930465ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:18:48Z"
    - latency: 1.90099ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:17:48Z"
    - latency: 1.913759ms
      message: 'network-check-target-ip-10-0-139-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:16:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:43:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-182-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-182.ec2.internal
      uid: d1686d1c-fc07-451d-a55d-86c0a407394b
    resourceVersion: "32232"
    uid: 3674d2c1-b894-4ab4-a992-7022e3479306
  spec:
    sourcePod: network-check-source-7cbc45fddc-js5vv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:49:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.166µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:48Z"
    - latency: 2.116266ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:25:48Z"
    - latency: 1.369986ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:48Z"
    - latency: 1.62971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:24:48Z"
    - latency: 800.379µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:48Z"
    - latency: 1.786137ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:23:48Z"
    - latency: 750.835µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:48Z"
    - latency: 2.226987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:22:48Z"
    - latency: 884.996µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:48Z"
    - latency: 1.850141ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:21:48Z"
kind: List
metadata:
  resourceVersion: ""