apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-6-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-6.ec2.internal
      uid: 6198a1a0-b895-49a6-bb44-aba040d42b78
    resourceVersion: "30496"
    uid: 36841460-7693-46fe-a1bb-071ddadccadb
  spec:
    sourcePod: network-check-source-6f78d59f99-pn7w9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:06:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.023797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:20:23Z"
    - latency: 11.484198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:19:23Z"
    - latency: 1.007422ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:18:23Z"
    - latency: 1.741842ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:17:23Z"
    - latency: 1.118779ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:16:23Z"
    - latency: 1.020367ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:15:23Z"
    - latency: 912.996µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:14:23Z"
    - latency: 914.045µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:13:23Z"
    - latency: 1.129193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:12:23Z"
    - latency: 1.337767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:11:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-6-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-6.ec2.internal
      uid: 6198a1a0-b895-49a6-bb44-aba040d42b78
    resourceVersion: "35277"
    uid: 366e73dd-dcfa-4fe1-b3ba-7a7e749f1dae
  spec:
    sourcePod: network-check-source-6f78d59f99-pn7w9
    targetEndpoint: acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:05:23Z"
      message: 'load-balancer-api-external: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.92948ms
      message: 'load-balancer-api-external: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:23:23Z"
    - latency: 11.154873ms
      message: 'load-balancer-api-external: resolved host name acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:23:23Z"
    - latency: 17.852603ms
      message: 'load-balancer-api-external: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:22:23Z"
    - latency: 7.426206ms
      message: 'load-balancer-api-external: resolved host name acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:22:23Z"
    - latency: 26.388913ms
      message: 'load-balancer-api-external: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:21:23Z"
    - latency: 8.559237ms
      message: 'load-balancer-api-external: resolved host name acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:21:23Z"
    - latency: 13.655462ms
      message: 'load-balancer-api-external: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:20:23Z"
    - latency: 7.861991ms
      message: 'load-balancer-api-external: resolved host name acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:20:23Z"
    - latency: 22.626178ms
      message: 'load-balancer-api-external: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:19:23Z"
    - latency: 32.205393ms
      message: 'load-balancer-api-external: resolved host name acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:19:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-6-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-6.ec2.internal
      uid: 6198a1a0-b895-49a6-bb44-aba040d42b78
    resourceVersion: "35278"
    uid: 0027c1a1-eb81-4576-b84c-0f74c347701c
  spec:
    sourcePod: network-check-source-6f78d59f99-pn7w9
    targetEndpoint: acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:05:23Z"
      message: 'load-balancer-api-internal: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.080561ms
      message: 'load-balancer-api-internal: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:23:23Z"
    - latency: 12.518534ms
      message: 'load-balancer-api-internal: resolved host name acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:23:23Z"
    - latency: 18.652365ms
      message: 'load-balancer-api-internal: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:22:23Z"
    - latency: 7.531911ms
      message: 'load-balancer-api-internal: resolved host name acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:22:23Z"
    - latency: 16.490661ms
      message: 'load-balancer-api-internal: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:21:23Z"
    - latency: 8.607376ms
      message: 'load-balancer-api-internal: resolved host name acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:21:23Z"
    - latency: 17.33152ms
      message: 'load-balancer-api-internal: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:20:23Z"
    - latency: 7.912226ms
      message: 'load-balancer-api-internal: resolved host name acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:20:23Z"
    - latency: 22.787623ms
      message: 'load-balancer-api-internal: tcp connection to acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:19:23Z"
    - latency: 32.52944ms
      message: 'load-balancer-api-internal: resolved host name acc1f94c828394fa693f139ad2774318-8880178ee753190d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:19:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-6-to-network-check-target-ip-10-0-130-237
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-6.ec2.internal
      uid: 6198a1a0-b895-49a6-bb44-aba040d42b78
    resourceVersion: "30492"
    uid: 6f845947-0102-4546-9767-b6c8ea1af8b6
  spec:
    sourcePod: network-check-source-6f78d59f99-pn7w9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:06:23Z"
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.033412ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:20:23Z"
    - latency: 11.459679ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:19:23Z"
    - latency: 2.488163ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:18:23Z"
    - latency: 2.748803ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:17:23Z"
    - latency: 2.288803ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:16:23Z"
    - latency: 2.744738ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:15:23Z"
    - latency: 2.290426ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:14:23Z"
    - latency: 2.266348ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:13:23Z"
    - latency: 2.41945ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:12:23Z"
    - latency: 2.291103ms
      message: 'network-check-target-ip-10-0-130-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:11:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-6-to-network-check-target-ip-10-0-133-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-6.ec2.internal
      uid: 6198a1a0-b895-49a6-bb44-aba040d42b78
    resourceVersion: "30491"
    uid: c90a1fb3-0d87-4bc9-af0a-ceedc7468710
  spec:
    sourcePod: network-check-source-6f78d59f99-pn7w9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:06:23Z"
      message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.86092ms
      message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:20:23Z"
    - latency: 10.724076ms
      message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:19:23Z"
    - latency: 1.02686ms
      message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:18:23Z"
    - latency: 1.429327ms
      message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:17:23Z"
    - latency: 1.023874ms
      message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:16:23Z"
    - latency: 996.697µs
      message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:15:23Z"
    - latency: 1.643567ms
      message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:14:23Z"
    - latency: 964.893µs
      message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:13:23Z"
    - latency: 1.008893ms
      message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:12:23Z"
    - latency: 1.471235ms
      message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:11:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-6-to-network-check-target-ip-10-0-134-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-6.ec2.internal
      uid: 6198a1a0-b895-49a6-bb44-aba040d42b78
    resourceVersion: "30493"
    uid: be473816-0e47-439c-9aa6-1cc2871b326d
  spec:
    sourcePod: network-check-source-6f78d59f99-pn7w9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:06:23Z"
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.02453ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:20:23Z"
    - latency: 11.022627ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:19:23Z"
    - latency: 2.186926ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:18:23Z"
    - latency: 2.130752ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:17:23Z"
    - latency: 2.254559ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:16:23Z"
    - latency: 2.353754ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:15:23Z"
    - latency: 2.606929ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:14:23Z"
    - latency: 2.039291ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:13:23Z"
    - latency: 2.267066ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:12:23Z"
    - latency: 2.197856ms
      message: 'network-check-target-ip-10-0-134-97: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:11:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-6-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-6.ec2.internal
      uid: 6198a1a0-b895-49a6-bb44-aba040d42b78
    resourceVersion: "35276"
    uid: 1c8420de-84b8-4d90-990d-dbb84646c3b7
  spec:
    sourcePod: network-check-source-6f78d59f99-pn7w9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:05:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.143283ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:23:23Z"
    - latency: 4.228638ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:23:23Z"
    - latency: 1.158385ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:22:23Z"
    - latency: 2.10148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:22:23Z"
    - latency: 884.678µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:21:23Z"
    - latency: 1.797694ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:21:23Z"
    - latency: 1.71139ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:20:23Z"
    - latency: 2.219777ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:20:23Z"
    - latency: 2.463706ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:19:23Z"
    - latency: 17.162428ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:19:23Z"
kind: List
metadata:
  resourceVersion: ""