apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:55:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-139.us-east-2.compute.internal
      uid: fd6b0234-014a-47a8-b591-e2cdeb3d0dd3
    resourceVersion: "25202"
    uid: 706da9e8-bef3-4607-a134-e6201d677749
  spec:
    sourcePod: network-check-source-6f78d59f99-rsx79
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:02:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.385273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:37:44Z"
    - latency: 1.213822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:36:44Z"
    - latency: 1.275307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:35:44Z"
    - latency: 832.89µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:34:44Z"
    - latency: 1.43971ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:33:44Z"
    - latency: 1.596832ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:32:44Z"
    - latency: 1.226465ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:31:44Z"
    - latency: 1.175956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:30:44Z"
    - latency: 1.150591ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:29:44Z"
    - latency: 1.473114ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:55:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-139.us-east-2.compute.internal
      uid: fd6b0234-014a-47a8-b591-e2cdeb3d0dd3
    resourceVersion: "26792"
    uid: 86dc42fe-3e8b-4ec2-be6b-3cca3c7ef513
  spec:
    sourcePod: network-check-source-6f78d59f99-rsx79
    targetEndpoint: af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:01:44Z"
      message: 'load-balancer-api-external: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.076251ms
      message: 'load-balancer-api-external: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:43:44Z"
    - latency: 8.431035ms
      message: 'load-balancer-api-external: resolved host name af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:43:44Z"
    - latency: 5.170842ms
      message: 'load-balancer-api-external: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:42:44Z"
    - latency: 12.468143ms
      message: 'load-balancer-api-external: resolved host name af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:42:44Z"
    - latency: 5.200154ms
      message: 'load-balancer-api-external: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:41:44Z"
    - latency: 8.55538ms
      message: 'load-balancer-api-external: resolved host name af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:41:44Z"
    - latency: 4.320394ms
      message: 'load-balancer-api-external: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:40:44Z"
    - latency: 9.196033ms
      message: 'load-balancer-api-external: resolved host name af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:40:44Z"
    - latency: 7.538862ms
      message: 'load-balancer-api-external: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:39:44Z"
    - latency: 8.108134ms
      message: 'load-balancer-api-external: resolved host name af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:39:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:55:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-139.us-east-2.compute.internal
      uid: fd6b0234-014a-47a8-b591-e2cdeb3d0dd3
    resourceVersion: "26791"
    uid: f213058e-f521-478b-a1c0-70d28ab17de6
  spec:
    sourcePod: network-check-source-6f78d59f99-rsx79
    targetEndpoint: af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:01:44Z"
      message: 'load-balancer-api-internal: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.079499ms
      message: 'load-balancer-api-internal: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:43:44Z"
    - latency: 8.326303ms
      message: 'load-balancer-api-internal: resolved host name af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:43:44Z"
    - latency: 5.159683ms
      message: 'load-balancer-api-internal: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:42:44Z"
    - latency: 12.396744ms
      message: 'load-balancer-api-internal: resolved host name af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:42:44Z"
    - latency: 4.82102ms
      message: 'load-balancer-api-internal: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:41:44Z"
    - latency: 8.583436ms
      message: 'load-balancer-api-internal: resolved host name af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:41:44Z"
    - latency: 4.333982ms
      message: 'load-balancer-api-internal: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:40:44Z"
    - latency: 9.021465ms
      message: 'load-balancer-api-internal: resolved host name af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:40:44Z"
    - latency: 5.033711ms
      message: 'load-balancer-api-internal: tcp connection to af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:39:44Z"
    - latency: 8.071808ms
      message: 'load-balancer-api-internal: resolved host name af349e164049a4e0e87b002281b4650c-1d6b553153d452e8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:39:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:55:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-139-to-network-check-target-ip-10-0-132-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-139.us-east-2.compute.internal
      uid: fd6b0234-014a-47a8-b591-e2cdeb3d0dd3
    resourceVersion: "25199"
    uid: d1f883f7-95d4-4467-86bd-2f8ed81654ae
  spec:
    sourcePod: network-check-source-6f78d59f99-rsx79
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:02:44Z"
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.977817ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:37:44Z"
    - latency: 2.732505ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:36:44Z"
    - latency: 2.163927ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:35:44Z"
    - latency: 2.218165ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:34:44Z"
    - latency: 2.279238ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:33:44Z"
    - latency: 2.197785ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:32:44Z"
    - latency: 2.22452ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:31:44Z"
    - latency: 2.422164ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:30:44Z"
    - latency: 2.350556ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:29:44Z"
    - latency: 2.286586ms
      message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:55:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-139-to-network-check-target-ip-10-0-137-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-139.us-east-2.compute.internal
      uid: fd6b0234-014a-47a8-b591-e2cdeb3d0dd3
    resourceVersion: "25201"
    uid: 1590428c-4927-44ac-b01f-031f40e23294
  spec:
    sourcePod: network-check-source-6f78d59f99-rsx79
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:02:44Z"
      message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.68772ms
      message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:37:44Z"
    - latency: 1.904009ms
      message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:36:44Z"
    - latency: 2.006537ms
      message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:35:44Z"
    - latency: 2.170621ms
      message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:34:44Z"
    - latency: 1.845307ms
      message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:33:44Z"
    - latency: 2.060854ms
      message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:32:44Z"
    - latency: 2.215488ms
      message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:31:44Z"
    - latency: 2.45748ms
      message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:30:44Z"
    - latency: 1.93176ms
      message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:29:44Z"
    - latency: 1.954028ms
      message: 'network-check-target-ip-10-0-137-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:55:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-139-to-network-check-target-ip-10-0-140-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-139.us-east-2.compute.internal
      uid: fd6b0234-014a-47a8-b591-e2cdeb3d0dd3
    resourceVersion: "25198"
    uid: e791acd2-88bd-449d-89ab-5ef5e1c6ba9e
  spec:
    sourcePod: network-check-source-6f78d59f99-rsx79
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:02:44Z"
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.326µs
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:37:44Z"
    - latency: 894.76µs
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:36:44Z"
    - latency: 830.373µs
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:35:44Z"
    - latency: 1.500369ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:34:44Z"
    - latency: 764.86µs
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:33:44Z"
    - latency: 1.519032ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:32:44Z"
    - latency: 895.838µs
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:31:44Z"
    - latency: 1.561337ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:30:44Z"
    - latency: 1.10848ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:29:44Z"
    - latency: 1.286152ms
      message: 'network-check-target-ip-10-0-140-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:55:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-139.us-east-2.compute.internal
      uid: fd6b0234-014a-47a8-b591-e2cdeb3d0dd3
    resourceVersion: "26790"
    uid: 59671d74-b3eb-475f-af1d-8f989733e772
  spec:
    sourcePod: network-check-source-6f78d59f99-rsx79
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:01:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.116µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:43:44Z"
    - latency: 1.731364ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:43:44Z"
    - latency: 818.777µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:42:44Z"
    - latency: 1.741245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:42:44Z"
    - latency: 1.029298ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:41:44Z"
    - latency: 2.110051ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:41:44Z"
    - latency: 1.217525ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:40:44Z"
    - latency: 2.02911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:40:44Z"
    - latency: 892.632µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:39:44Z"
    - latency: 1.925944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:39:44Z"
kind: List
metadata:
  resourceVersion: ""