apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:39:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-165-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-165.ec2.internal
      uid: a2da1e96-4450-41ac-9904-47639c8099ee
    resourceVersion: "69548"
    uid: 81bcd3a7-0e00-492e-b27b-a547e6a06fc9
  spec:
    sourcePod: network-check-source-7cbc45fddc-rlwbq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:46:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.378706ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:14:50Z"
    - latency: 1.063929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:13:50Z"
    - latency: 1.076751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:12:50Z"
    - latency: 1.24299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:11:50Z"
    - latency: 1.058281ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:10:50Z"
    - latency: 1.001678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:09:50Z"
    - latency: 1.364594ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:08:50Z"
    - latency: 978.715µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:07:50Z"
    - latency: 1.023393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:06:50Z"
    - latency: 1.049794ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:05:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:39:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-165-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-165.ec2.internal
      uid: a2da1e96-4450-41ac-9904-47639c8099ee
    resourceVersion: "70634"
    uid: 923b6835-09c3-4a9e-b576-ebf80d494803
  spec:
    sourcePod: network-check-source-7cbc45fddc-rlwbq
    targetEndpoint: ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:45:50Z"
      message: 'load-balancer-api-external: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.353889ms
      message: 'load-balancer-api-external: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:15:50Z"
    - latency: 9.902601ms
      message: 'load-balancer-api-external: resolved host name ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:15:50Z"
    - latency: 6.644613ms
      message: 'load-balancer-api-external: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:14:50Z"
    - latency: 9.232456ms
      message: 'load-balancer-api-external: resolved host name ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:14:50Z"
    - latency: 6.915452ms
      message: 'load-balancer-api-external: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:13:50Z"
    - latency: 9.657249ms
      message: 'load-balancer-api-external: resolved host name ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:13:50Z"
    - latency: 4.480355ms
      message: 'load-balancer-api-external: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:12:50Z"
    - latency: 7.803638ms
      message: 'load-balancer-api-external: resolved host name ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:12:50Z"
    - latency: 4.384348ms
      message: 'load-balancer-api-external: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:11:50Z"
    - latency: 12.86968ms
      message: 'load-balancer-api-external: resolved host name ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:11:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:39:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-165-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-165.ec2.internal
      uid: a2da1e96-4450-41ac-9904-47639c8099ee
    resourceVersion: "70635"
    uid: 1add3907-9076-4871-9b33-fdfa2faba1b5
  spec:
    sourcePod: network-check-source-7cbc45fddc-rlwbq
    targetEndpoint: ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:45:50Z"
      message: 'load-balancer-api-internal: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.348188ms
      message: 'load-balancer-api-internal: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:15:50Z"
    - latency: 9.937605ms
      message: 'load-balancer-api-internal: resolved host name ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:15:50Z"
    - latency: 5.793781ms
      message: 'load-balancer-api-internal: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:14:50Z"
    - latency: 9.194913ms
      message: 'load-balancer-api-internal: resolved host name ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:14:50Z"
    - latency: 6.904602ms
      message: 'load-balancer-api-internal: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:13:50Z"
    - latency: 9.52493ms
      message: 'load-balancer-api-internal: resolved host name ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:13:50Z"
    - latency: 4.46955ms
      message: 'load-balancer-api-internal: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:12:50Z"
    - latency: 7.89331ms
      message: 'load-balancer-api-internal: resolved host name ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:12:50Z"
    - latency: 5.143824ms
      message: 'load-balancer-api-internal: tcp connection to ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:11:50Z"
    - latency: 12.734075ms
      message: 'load-balancer-api-internal: resolved host name ae1816883ad954ee5afc5799a3cd800a-0b8454607affef76.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:11:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:39:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-165-to-network-check-target-ip-10-0-129-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-165.ec2.internal
      uid: a2da1e96-4450-41ac-9904-47639c8099ee
    resourceVersion: "69545"
    uid: 01eed195-845f-40fe-b408-c2d8017a5309
  spec:
    sourcePod: network-check-source-7cbc45fddc-rlwbq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:46:50Z"
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.145261ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:14:50Z"
    - latency: 2.660508ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:13:50Z"
    - latency: 2.290294ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:12:50Z"
    - latency: 2.364163ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:11:50Z"
    - latency: 2.561167ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:10:50Z"
    - latency: 2.194585ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:09:50Z"
    - latency: 2.794054ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:08:50Z"
    - latency: 2.401281ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:07:50Z"
    - latency: 2.372035ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:06:50Z"
    - latency: 2.501746ms
      message: 'network-check-target-ip-10-0-129-220: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:05:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:39:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-165-to-network-check-target-ip-10-0-138-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-165.ec2.internal
      uid: a2da1e96-4450-41ac-9904-47639c8099ee
    resourceVersion: "69547"
    uid: 8a94ba93-6058-4034-832b-ffb29bd0d338
  spec:
    sourcePod: network-check-source-7cbc45fddc-rlwbq
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:46:50Z"
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.581814ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:14:50Z"
    - latency: 2.425799ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:13:50Z"
    - latency: 2.436944ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:12:50Z"
    - latency: 2.551508ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:11:50Z"
    - latency: 2.526672ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:10:50Z"
    - latency: 2.543055ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:09:50Z"
    - latency: 2.691974ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:08:50Z"
    - latency: 2.624325ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:07:50Z"
    - latency: 2.581271ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:06:50Z"
    - latency: 2.400598ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:05:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:39:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-165-to-network-check-target-ip-10-0-142-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-165.ec2.internal
      uid: a2da1e96-4450-41ac-9904-47639c8099ee
    resourceVersion: "69546"
    uid: 441373be-f2fb-4fb6-995d-4129aa9d0916
  spec:
    sourcePod: network-check-source-7cbc45fddc-rlwbq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:46:50Z"
      message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.514387ms
      message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:14:50Z"
    - latency: 1.310774ms
      message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:13:50Z"
    - latency: 1.747436ms
      message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:12:50Z"
    - latency: 1.02275ms
      message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:11:50Z"
    - latency: 1.43174ms
      message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:10:50Z"
    - latency: 921.654µs
      message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:09:50Z"
    - latency: 1.031079ms
      message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:08:50Z"
    - latency: 929.688µs
      message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:07:50Z"
    - latency: 919.479µs
      message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:06:50Z"
    - latency: 1.457246ms
      message: 'network-check-target-ip-10-0-142-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:05:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T10:39:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-165-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-165.ec2.internal
      uid: a2da1e96-4450-41ac-9904-47639c8099ee
    resourceVersion: "70633"
    uid: ed86cfca-4929-48b1-a435-d884ff58fde0
  spec:
    sourcePod: network-check-source-7cbc45fddc-rlwbq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:45:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.06075ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:15:50Z"
    - latency: 2.096306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:15:50Z"
    - latency: 919.381µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:14:50Z"
    - latency: 2.066153ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:14:50Z"
    - latency: 910.042µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:13:50Z"
    - latency: 1.758321ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:13:50Z"
    - latency: 869.191µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:12:50Z"
    - latency: 2.26107ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:12:50Z"
    - latency: 1.013285ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T11:11:50Z"
    - latency: 1.900054ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T11:11:50Z"
kind: List
metadata:
  resourceVersion: ""