apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-157-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-157.ec2.internal
      uid: f32eae6f-4043-47bd-b9c7-86b00e275b71
    resourceVersion: "76016"
    uid: 26fe22fb-633f-444b-a795-542409e37c54
  spec:
    sourcePod: network-check-source-7cbc45fddc-6z77t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:08:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.457787ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:04:52Z"
    - latency: 1.20922ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:03:52Z"
    - latency: 1.668746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:02:52Z"
    - latency: 1.112945ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:01:52Z"
    - latency: 1.207456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:00:52Z"
    - latency: 1.315728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:59:52Z"
    - latency: 2.850659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:58:52Z"
    - latency: 1.935054ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:57:52Z"
    - latency: 1.437717ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:56:52Z"
    - latency: 1.336038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:55:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-157-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-157.ec2.internal
      uid: f32eae6f-4043-47bd-b9c7-86b00e275b71
    resourceVersion: "72391"
    uid: 407125f1-4bd3-4d48-a814-a7ba3d2a63b6
  spec:
    sourcePod: network-check-source-7cbc45fddc-6z77t
    targetEndpoint: aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:07:52Z"
      message: 'load-balancer-api-external: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.361478ms
      message: 'load-balancer-api-external: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:01:52Z"
    - latency: 7.747654ms
      message: 'load-balancer-api-external: resolved host name aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:01:52Z"
    - latency: 5.405954ms
      message: 'load-balancer-api-external: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:00:52Z"
    - latency: 8.898453ms
      message: 'load-balancer-api-external: resolved host name aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:00:52Z"
    - latency: 5.32885ms
      message: 'load-balancer-api-external: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:59:52Z"
    - latency: 7.551791ms
      message: 'load-balancer-api-external: resolved host name aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:59:52Z"
    - latency: 5.313003ms
      message: 'load-balancer-api-external: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:58:52Z"
    - latency: 10.793817ms
      message: 'load-balancer-api-external: resolved host name aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:58:52Z"
    - latency: 5.123265ms
      message: 'load-balancer-api-external: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:57:52Z"
    - latency: 8.763392ms
      message: 'load-balancer-api-external: resolved host name aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:57:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-157-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-157.ec2.internal
      uid: f32eae6f-4043-47bd-b9c7-86b00e275b71
    resourceVersion: "72392"
    uid: de997b10-a725-4f55-9895-7f130d6230f9
  spec:
    sourcePod: network-check-source-7cbc45fddc-6z77t
    targetEndpoint: aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:07:52Z"
      message: 'load-balancer-api-internal: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.039106ms
      message: 'load-balancer-api-internal: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:01:52Z"
    - latency: 7.671482ms
      message: 'load-balancer-api-internal: resolved host name aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:01:52Z"
    - latency: 5.37594ms
      message: 'load-balancer-api-internal: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:00:52Z"
    - latency: 8.822417ms
      message: 'load-balancer-api-internal: resolved host name aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:00:52Z"
    - latency: 3.406517ms
      message: 'load-balancer-api-internal: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:59:52Z"
    - latency: 7.246342ms
      message: 'load-balancer-api-internal: resolved host name aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:59:52Z"
    - latency: 6.194067ms
      message: 'load-balancer-api-internal: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:58:52Z"
    - latency: 8.455184ms
      message: 'load-balancer-api-internal: resolved host name aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:58:52Z"
    - latency: 5.518284ms
      message: 'load-balancer-api-internal: tcp connection to aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:57:52Z"
    - latency: 8.694067ms
      message: 'load-balancer-api-internal: resolved host name aa144e26ec4f142299a5555c454f6851-1080550f06171ced.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:57:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-157-to-network-check-target-ip-10-0-133-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-157.ec2.internal
      uid: f32eae6f-4043-47bd-b9c7-86b00e275b71
    resourceVersion: "76015"
    uid: 40ec16ff-56ec-47d5-8a8e-89cff8da966d
  spec:
    sourcePod: network-check-source-7cbc45fddc-6z77t
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:08:52Z"
      message: 'network-check-target-ip-10-0-133-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.50933ms
      message: 'network-check-target-ip-10-0-133-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:04:52Z"
    - latency: 2.135316ms
      message: 'network-check-target-ip-10-0-133-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:03:52Z"
    - latency: 2.351966ms
      message: 'network-check-target-ip-10-0-133-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:02:52Z"
    - latency: 2.646024ms
      message: 'network-check-target-ip-10-0-133-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:01:52Z"
    - latency: 2.255224ms
      message: 'network-check-target-ip-10-0-133-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:00:52Z"
    - latency: 2.439684ms
      message: 'network-check-target-ip-10-0-133-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:59:52Z"
    - latency: 2.60067ms
      message: 'network-check-target-ip-10-0-133-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:58:52Z"
    - latency: 2.412605ms
      message: 'network-check-target-ip-10-0-133-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:57:52Z"
    - latency: 2.257451ms
      message: 'network-check-target-ip-10-0-133-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:56:52Z"
    - latency: 2.319723ms
      message: 'network-check-target-ip-10-0-133-200: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:55:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-157-to-network-check-target-ip-10-0-140-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-157.ec2.internal
      uid: f32eae6f-4043-47bd-b9c7-86b00e275b71
    resourceVersion: "76013"
    uid: e70f630f-9189-4b55-a7a5-4f0de3366a20
  spec:
    sourcePod: network-check-source-7cbc45fddc-6z77t
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:08:52Z"
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.636985ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:04:52Z"
    - latency: 1.079705ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:03:52Z"
    - latency: 849.106µs
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:02:52Z"
    - latency: 1.236406ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:01:52Z"
    - latency: 1.497286ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:00:52Z"
    - latency: 2.147106ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:59:52Z"
    - latency: 1.025236ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:58:52Z"
    - latency: 937.321µs
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:57:52Z"
    - latency: 1.113224ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:56:52Z"
    - latency: 1.6076ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:55:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-157-to-network-check-target-ip-10-0-142-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-157.ec2.internal
      uid: f32eae6f-4043-47bd-b9c7-86b00e275b71
    resourceVersion: "76014"
    uid: 7808c9bf-4485-4ad2-bd88-6be50971ed6a
  spec:
    sourcePod: network-check-source-7cbc45fddc-6z77t
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:08:52Z"
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.45113ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:04:52Z"
    - latency: 2.388692ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:03:52Z"
    - latency: 2.333253ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:02:52Z"
    - latency: 2.076683ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:01:52Z"
    - latency: 1.971808ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:00:52Z"
    - latency: 2.174263ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:59:52Z"
    - latency: 2.357368ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:58:52Z"
    - latency: 2.502012ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:57:52Z"
    - latency: 2.065413ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:56:52Z"
    - latency: 2.335527ms
      message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:55:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-157-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-157.ec2.internal
      uid: f32eae6f-4043-47bd-b9c7-86b00e275b71
    resourceVersion: "72386"
    uid: 11c32ee3-a601-4ca3-acf5-36bca82e78e6
  spec:
    sourcePod: network-check-source-7cbc45fddc-6z77t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:07:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.625µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:01:52Z"
    - latency: 2.205491ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:01:52Z"
    - latency: 960.63µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:00:52Z"
    - latency: 2.324339ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:00:52Z"
    - latency: 916.533µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:59:52Z"
    - latency: 2.058747ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:59:52Z"
    - latency: 1.13055ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:58:52Z"
    - latency: 3.573121ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:58:52Z"
    - latency: 981.381µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:57:52Z"
    - latency: 2.799263ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:57:52Z"
kind: List
metadata:
  resourceVersion: ""