apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:12:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-22-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-22.ec2.internal
      uid: a4f38ca9-11d8-42db-a21a-c15bbda58f60
    resourceVersion: "63443"
    uid: b6eabbd7-ae6e-4298-9f69-dc07600fc6bb
  spec:
    sourcePod: network-check-source-6f8b768455-v76ts
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:19: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.029967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:47:23Z"
    - latency: 1.152858ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:46:23Z"
    - latency: 1.425011ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:45:23Z"
    - latency: 1.117737ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:23Z"
    - latency: 948.47µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:43:23Z"
    - latency: 1.390155ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:42:23Z"
    - latency: 981.763µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:41:23Z"
    - latency: 751.847µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:40:23Z"
    - latency: 1.288252ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:39:23Z"
    - latency: 957.584µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:38:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:12:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-22-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-22.ec2.internal
      uid: a4f38ca9-11d8-42db-a21a-c15bbda58f60
    resourceVersion: "64083"
    uid: e993a53e-9fa8-4b97-9cf6-2560f84f74ec
  spec:
    sourcePod: network-check-source-6f8b768455-v76ts
    targetEndpoint: a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:18:23Z"
      message: 'load-balancer-api-external: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.831004ms
      message: 'load-balancer-api-external: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:48:23Z"
    - latency: 12.313235ms
      message: 'load-balancer-api-external: resolved host name a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:48:23Z"
    - latency: 5.675598ms
      message: 'load-balancer-api-external: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:47:23Z"
    - latency: 16.015151ms
      message: 'load-balancer-api-external: resolved host name a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:47:23Z"
    - latency: 3.856326ms
      message: 'load-balancer-api-external: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:46:23Z"
    - latency: 9.237452ms
      message: 'load-balancer-api-external: resolved host name a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:46:23Z"
    - latency: 6.620449ms
      message: 'load-balancer-api-external: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:45:23Z"
    - latency: 13.774457ms
      message: 'load-balancer-api-external: resolved host name a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:45:23Z"
    - latency: 4.667923ms
      message: 'load-balancer-api-external: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:23Z"
    - latency: 9.248541ms
      message: 'load-balancer-api-external: resolved host name a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:44:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:12:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-22-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-22.ec2.internal
      uid: a4f38ca9-11d8-42db-a21a-c15bbda58f60
    resourceVersion: "64084"
    uid: b00972ec-0a2e-419b-9db2-95b0b18e73ef
  spec:
    sourcePod: network-check-source-6f8b768455-v76ts
    targetEndpoint: a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:18:23Z"
      message: 'load-balancer-api-internal: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.786019ms
      message: 'load-balancer-api-internal: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:48:23Z"
    - latency: 12.362993ms
      message: 'load-balancer-api-internal: resolved host name a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:48:23Z"
    - latency: 3.709818ms
      message: 'load-balancer-api-internal: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:47:23Z"
    - latency: 15.962953ms
      message: 'load-balancer-api-internal: resolved host name a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:47:23Z"
    - latency: 4.351022ms
      message: 'load-balancer-api-internal: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:46:23Z"
    - latency: 9.334962ms
      message: 'load-balancer-api-internal: resolved host name a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:46:23Z"
    - latency: 7.035859ms
      message: 'load-balancer-api-internal: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:45:23Z"
    - latency: 13.83729ms
      message: 'load-balancer-api-internal: resolved host name a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:45:23Z"
    - latency: 4.692367ms
      message: 'load-balancer-api-internal: tcp connection to a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:23Z"
    - latency: 9.374977ms
      message: 'load-balancer-api-internal: resolved host name a076f929e6e26432680cee0b22388f88-42d64be0a4f07f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:44:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:12:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-22-to-network-check-target-ip-10-0-128-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-22.ec2.internal
      uid: a4f38ca9-11d8-42db-a21a-c15bbda58f60
    resourceVersion: "63441"
    uid: d776d6ec-2675-485f-8d4d-21b109e91c3a
  spec:
    sourcePod: network-check-source-6f8b768455-v76ts
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:19:23Z"
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.991524ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:47:23Z"
    - latency: 2.020641ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:46:23Z"
    - latency: 2.153826ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:45:23Z"
    - latency: 1.953774ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:23Z"
    - latency: 2.123535ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:43:23Z"
    - latency: 2.087543ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:42:23Z"
    - latency: 2.356953ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:41:23Z"
    - latency: 1.779718ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:40:23Z"
    - latency: 1.982438ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:39:23Z"
    - latency: 1.749653ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:38:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:12:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-22-to-network-check-target-ip-10-0-133-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-22.ec2.internal
      uid: a4f38ca9-11d8-42db-a21a-c15bbda58f60
    resourceVersion: "63442"
    uid: 9871852f-c4ab-40f5-b8b9-1a4aa14b06a6
  spec:
    sourcePod: network-check-source-6f8b768455-v76ts
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:19:23Z"
      message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.275055ms
      message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:47:23Z"
    - latency: 2.454876ms
      message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:46:23Z"
    - latency: 2.965435ms
      message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:45:23Z"
    - latency: 2.051696ms
      message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:23Z"
    - latency: 2.187614ms
      message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:43:23Z"
    - latency: 2.840634ms
      message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:42:23Z"
    - latency: 2.413415ms
      message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:41:23Z"
    - latency: 2.188675ms
      message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:40:23Z"
    - latency: 1.999508ms
      message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:39:23Z"
    - latency: 2.389665ms
      message: 'network-check-target-ip-10-0-133-98: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:38:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:12:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-22-to-network-check-target-ip-10-0-142-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-22.ec2.internal
      uid: a4f38ca9-11d8-42db-a21a-c15bbda58f60
    resourceVersion: "63440"
    uid: 14c38fbf-1fc3-44b5-a64a-328c8284680c
  spec:
    sourcePod: network-check-source-6f8b768455-v76ts
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:19:23Z"
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 847.589µs
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:47:23Z"
    - latency: 783.934µs
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:46:23Z"
    - latency: 1.038424ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:45:23Z"
    - latency: 975.979µs
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:23Z"
    - latency: 1.130573ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:43:23Z"
    - latency: 1.202712ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:42:23Z"
    - latency: 843.549µs
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:41:23Z"
    - latency: 833.971µs
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:40:23Z"
    - latency: 1.483058ms
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:39:23Z"
    - latency: 916.88µs
      message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:38:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T14:12:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-22-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-22.ec2.internal
      uid: a4f38ca9-11d8-42db-a21a-c15bbda58f60
    resourceVersion: "64082"
    uid: 0f239c5b-c072-4fed-a981-e1f5ec58fe0c
  spec:
    sourcePod: network-check-source-6f8b768455-v76ts
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T14:18:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.020134ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:48:23Z"
    - latency: 1.583496ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:48:23Z"
    - latency: 1.165009ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:47:23Z"
    - latency: 1.854419ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:47:23Z"
    - latency: 846.188µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:46:23Z"
    - latency: 1.786001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:46:23Z"
    - latency: 928.096µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:45:23Z"
    - latency: 2.286949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:45:23Z"
    - latency: 905.267µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T14:44:23Z"
    - latency: 1.822147ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T14:44:23Z"
kind: List
metadata:
  resourceVersion: ""