apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:27:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: 9b4928d4-e05d-48dc-9e6c-33d6779400cd
    resourceVersion: "66883"
    uid: 3476c7d6-5bcb-4b16-a0b3-98ddc1e6a4c1
  spec:
    sourcePod: network-check-source-6f8b768455-whk78
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:34:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.321103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:59Z"
    - latency: 1.007707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:59Z"
    - latency: 1.015396ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:59Z"
    - latency: 951.462µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:59Z"
    - latency: 995.895µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:59Z"
    - latency: 1.122617ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:57:59Z"
    - latency: 821.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:56:59Z"
    - latency: 1.361632ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:55:59Z"
    - latency: 937.98µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:54:59Z"
    - latency: 1.170393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:53:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:27:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: 9b4928d4-e05d-48dc-9e6c-33d6779400cd
    resourceVersion: "67501"
    uid: 062d1f9e-3a8c-498b-bc28-078e63e3b799
  spec:
    sourcePod: network-check-source-6f8b768455-whk78
    targetEndpoint: a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:33:59Z"
      message: 'load-balancer-api-external: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.271152ms
      message: 'load-balancer-api-external: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:59Z"
    - latency: 7.359856ms
      message: 'load-balancer-api-external: resolved host name a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:03:59Z"
    - latency: 4.590635ms
      message: 'load-balancer-api-external: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:59Z"
    - latency: 7.164143ms
      message: 'load-balancer-api-external: resolved host name a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:02:59Z"
    - latency: 8.207862ms
      message: 'load-balancer-api-external: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:59Z"
    - latency: 6.667946ms
      message: 'load-balancer-api-external: resolved host name a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:01:59Z"
    - latency: 4.713445ms
      message: 'load-balancer-api-external: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:59Z"
    - latency: 6.487598ms
      message: 'load-balancer-api-external: resolved host name a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:00:59Z"
    - latency: 4.763913ms
      message: 'load-balancer-api-external: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:59Z"
    - latency: 6.375769ms
      message: 'load-balancer-api-external: resolved host name a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T11:59:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:27:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: 9b4928d4-e05d-48dc-9e6c-33d6779400cd
    resourceVersion: "67502"
    uid: b1429dfd-8773-4676-885f-b4104a046a7a
  spec:
    sourcePod: network-check-source-6f8b768455-whk78
    targetEndpoint: a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:33:59Z"
      message: 'load-balancer-api-internal: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.753523ms
      message: 'load-balancer-api-internal: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:59Z"
    - latency: 7.43257ms
      message: 'load-balancer-api-internal: resolved host name a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:03:59Z"
    - latency: 4.495548ms
      message: 'load-balancer-api-internal: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:59Z"
    - latency: 7.218712ms
      message: 'load-balancer-api-internal: resolved host name a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:02:59Z"
    - latency: 4.175623ms
      message: 'load-balancer-api-internal: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:59Z"
    - latency: 6.543705ms
      message: 'load-balancer-api-internal: resolved host name a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:01:59Z"
    - latency: 4.703423ms
      message: 'load-balancer-api-internal: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:59Z"
    - latency: 6.434731ms
      message: 'load-balancer-api-internal: resolved host name a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:00:59Z"
    - latency: 4.201011ms
      message: 'load-balancer-api-internal: tcp connection to a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:59Z"
    - latency: 6.182185ms
      message: 'load-balancer-api-internal: resolved host name a926cc575da784c0b95c31ff5e2b8dd3-6c8a9e93633f1a51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T11:59:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:27:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-network-check-target-ip-10-0-132-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: 9b4928d4-e05d-48dc-9e6c-33d6779400cd
    resourceVersion: "66881"
    uid: 83de6b80-4260-40f7-a10d-58f0670869f0
  spec:
    sourcePod: network-check-source-6f8b768455-whk78
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:34:59Z"
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.672158ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:59Z"
    - latency: 2.361543ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:59Z"
    - latency: 2.370919ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:59Z"
    - latency: 2.468117ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:59Z"
    - latency: 3.027208ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:59Z"
    - latency: 2.558731ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:57:59Z"
    - latency: 2.470148ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:56:59Z"
    - latency: 2.391471ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:55:59Z"
    - latency: 2.676944ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:54:59Z"
    - latency: 2.550928ms
      message: 'network-check-target-ip-10-0-132-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:53:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:27:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-network-check-target-ip-10-0-135-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: 9b4928d4-e05d-48dc-9e6c-33d6779400cd
    resourceVersion: "66880"
    uid: f5a1862b-59c1-4a96-9fe6-72378fdd62ff
  spec:
    sourcePod: network-check-source-6f8b768455-whk78
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:34:59Z"
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.143218ms
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:59Z"
    - latency: 1.164269ms
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:59Z"
    - latency: 774.91µs
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:59Z"
    - latency: 1.297418ms
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:59Z"
    - latency: 968.067µs
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:59Z"
    - latency: 899.085µs
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:57:59Z"
    - latency: 1.031608ms
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:56:59Z"
    - latency: 692.019µs
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:55:59Z"
    - latency: 835.098µs
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:54:59Z"
    - latency: 726.766µs
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:53:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:27:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-network-check-target-ip-10-0-138-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: 9b4928d4-e05d-48dc-9e6c-33d6779400cd
    resourceVersion: "66882"
    uid: c447530e-050f-43ff-864a-0fa7b8ed5695
  spec:
    sourcePod: network-check-source-6f8b768455-whk78
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:34:59Z"
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.100092ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:59Z"
    - latency: 2.090506ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:59Z"
    - latency: 2.137596ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:59Z"
    - latency: 2.365138ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:59Z"
    - latency: 2.199258ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:58:59Z"
    - latency: 2.163209ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:57:59Z"
    - latency: 1.959011ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:56:59Z"
    - latency: 2.848916ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:55:59Z"
    - latency: 2.622552ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:54:59Z"
    - latency: 2.502683ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:53:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:27:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: 9b4928d4-e05d-48dc-9e6c-33d6779400cd
    resourceVersion: "67500"
    uid: 1016f547-b8e1-4727-9ea7-82957aa33981
  spec:
    sourcePod: network-check-source-6f8b768455-whk78
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:33:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.067µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:03:59Z"
    - latency: 1.776427ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:03:59Z"
    - latency: 927.189µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:02:59Z"
    - latency: 1.985261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:02:59Z"
    - latency: 809.148µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:01:59Z"
    - latency: 1.841878ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:01:59Z"
    - latency: 901.019µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:00:59Z"
    - latency: 1.735973ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:00:59Z"
    - latency: 978.988µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T11:59:59Z"
    - latency: 1.672551ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T11:59:59Z"
kind: List
metadata:
  resourceVersion: ""