apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T02:43:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 7155770c-4caf-4e28-b6b2-a82ac885b5a7
    resourceVersion: "70717"
    uid: 61dd7091-2f64-4871-9ca0-70b0ba0f69d0
  spec:
    sourcePod: network-check-source-6f8b768455-bgkf2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T02:50:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 806.762µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:18:49Z"
    - latency: 1.091456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:17:49Z"
    - latency: 1.132136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:16:49Z"
    - latency: 1.014345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:15:49Z"
    - latency: 942.779µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:14:49Z"
    - latency: 1.065866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:13:49Z"
    - latency: 966.122µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:12:49Z"
    - latency: 1.148929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:11:49Z"
    - latency: 1.167639ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:10:49Z"
    - latency: 942.904µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T02:43:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 7155770c-4caf-4e28-b6b2-a82ac885b5a7
    resourceVersion: "71581"
    uid: 699a381b-dabb-41df-b4a9-486ff4b75217
  spec:
    sourcePod: network-check-source-6f8b768455-bgkf2
    targetEndpoint: abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T02:49:49Z"
      message: 'load-balancer-api-external: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.91088ms
      message: 'load-balancer-api-external: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:19:49Z"
    - latency: 8.421128ms
      message: 'load-balancer-api-external: resolved host name abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:19:49Z"
    - latency: 6.102272ms
      message: 'load-balancer-api-external: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:18:49Z"
    - latency: 9.359685ms
      message: 'load-balancer-api-external: resolved host name abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:18:49Z"
    - latency: 5.194843ms
      message: 'load-balancer-api-external: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:17:49Z"
    - latency: 8.358562ms
      message: 'load-balancer-api-external: resolved host name abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:17:49Z"
    - latency: 3.920994ms
      message: 'load-balancer-api-external: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:16:49Z"
    - latency: 8.653203ms
      message: 'load-balancer-api-external: resolved host name abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:16:49Z"
    - latency: 5.421155ms
      message: 'load-balancer-api-external: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:15:49Z"
    - latency: 8.241323ms
      message: 'load-balancer-api-external: resolved host name abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:15:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T02:43:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 7155770c-4caf-4e28-b6b2-a82ac885b5a7
    resourceVersion: "71582"
    uid: f37e3227-2a68-432e-a119-756eb3f0f980
  spec:
    sourcePod: network-check-source-6f8b768455-bgkf2
    targetEndpoint: abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T02:49:49Z"
      message: 'load-balancer-api-internal: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.903478ms
      message: 'load-balancer-api-internal: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:19:49Z"
    - latency: 8.497353ms
      message: 'load-balancer-api-internal: resolved host name abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:19:49Z"
    - latency: 6.079576ms
      message: 'load-balancer-api-internal: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:18:49Z"
    - latency: 9.408772ms
      message: 'load-balancer-api-internal: resolved host name abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:18:49Z"
    - latency: 5.138986ms
      message: 'load-balancer-api-internal: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:17:49Z"
    - latency: 8.462803ms
      message: 'load-balancer-api-internal: resolved host name abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:17:49Z"
    - latency: 3.911205ms
      message: 'load-balancer-api-internal: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:16:49Z"
    - latency: 8.734837ms
      message: 'load-balancer-api-internal: resolved host name abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:16:49Z"
    - latency: 4.488155ms
      message: 'load-balancer-api-internal: tcp connection to abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:15:49Z"
    - latency: 8.324144ms
      message: 'load-balancer-api-internal: resolved host name abb419bcaa9e2429abab7423a0b1143c-3a8bdfc1191f99b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:15:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T02:43:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-network-check-target-ip-10-0-128-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 7155770c-4caf-4e28-b6b2-a82ac885b5a7
    resourceVersion: "70716"
    uid: b93e5f87-b617-4a72-8865-dfa0882b915f
  spec:
    sourcePod: network-check-source-6f8b768455-bgkf2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T02:50:49Z"
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.46288ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:18:49Z"
    - latency: 2.324194ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:17:49Z"
    - latency: 2.278244ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:16:49Z"
    - latency: 1.908032ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:15:49Z"
    - latency: 2.084091ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:14:49Z"
    - latency: 2.483382ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:13:49Z"
    - latency: 2.985048ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:12:49Z"
    - latency: 2.415646ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:11:49Z"
    - latency: 2.880591ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:10:49Z"
    - latency: 2.525392ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T02:43:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-network-check-target-ip-10-0-130-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 7155770c-4caf-4e28-b6b2-a82ac885b5a7
    resourceVersion: "70714"
    uid: 98f22bc7-c8b2-40a6-ab8b-92587a966393
  spec:
    sourcePod: network-check-source-6f8b768455-bgkf2
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T02:50:49Z"
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.681µs
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:18:49Z"
    - latency: 1.266923ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:17:49Z"
    - latency: 995.016µs
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:16:49Z"
    - latency: 935.603µs
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:15:49Z"
    - latency: 949.5µs
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:14:49Z"
    - latency: 1.02342ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:13:49Z"
    - latency: 1.417889ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:12:49Z"
    - latency: 900.39µs
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:11:49Z"
    - latency: 2.014142ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:10:49Z"
    - latency: 1.044103ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T02:43:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-network-check-target-ip-10-0-141-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 7155770c-4caf-4e28-b6b2-a82ac885b5a7
    resourceVersion: "70715"
    uid: cfd4a9a5-7258-45ac-83ad-028adf567215
  spec:
    sourcePod: network-check-source-6f8b768455-bgkf2
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T02:50:49Z"
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.262881ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:18:49Z"
    - latency: 2.413745ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:17:49Z"
    - latency: 2.258184ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:16:49Z"
    - latency: 2.451533ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:15:49Z"
    - latency: 2.589752ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:14:49Z"
    - latency: 2.567358ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:13:49Z"
    - latency: 3.144958ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:12:49Z"
    - latency: 2.474912ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:11:49Z"
    - latency: 3.001786ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:10:49Z"
    - latency: 2.283073ms
      message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T02:43:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-57-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-57.ec2.internal
      uid: 7155770c-4caf-4e28-b6b2-a82ac885b5a7
    resourceVersion: "71580"
    uid: 12be5ec0-7c1f-401d-a249-d6acd10f2d06
  spec:
    sourcePod: network-check-source-6f8b768455-bgkf2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T02:49:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.169929ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:19:49Z"
    - latency: 1.939484ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:19:49Z"
    - latency: 996.535µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:18:49Z"
    - latency: 2.27469ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:18:49Z"
    - latency: 1.075082ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:17:49Z"
    - latency: 1.8816ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:17:49Z"
    - latency: 860.105µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:16:49Z"
    - latency: 1.742745ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:16:49Z"
    - latency: 1.164505ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T03:15:49Z"
    - latency: 1.675053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T03:15:49Z"
kind: List
metadata:
  resourceVersion: ""