apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-19-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-19.ec2.internal
      uid: 8dcd17c7-7a94-4dec-9626-bec34cd67a19
    resourceVersion: "76781"
    uid: 072d2467-1168-4ee4-a902-5c929700efb7
  spec:
    sourcePod: network-check-source-6f78d59f99-lvg49
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:49:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.062766ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:20:29Z"
    - latency: 1.105954ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:19:29Z"
    - latency: 1.004163ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:18:29Z"
    - latency: 1.138022ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:17:29Z"
    - latency: 1.128762ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:16:29Z"
    - latency: 1.487353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:15:29Z"
    - latency: 919.311µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:14:29Z"
    - latency: 1.046622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:13:29Z"
    - latency: 866.757µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:12:29Z"
    - latency: 1.182038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:11:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-19-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-19.ec2.internal
      uid: 8dcd17c7-7a94-4dec-9626-bec34cd67a19
    resourceVersion: "72594"
    uid: a9aebbb8-6c5f-48e0-9733-22a8336dafd9
  spec:
    sourcePod: network-check-source-6f78d59f99-lvg49
    targetEndpoint: a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:48:29Z"
      message: 'load-balancer-api-external: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.978466ms
      message: 'load-balancer-api-external: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:18:29Z"
    - latency: 7.614289ms
      message: 'load-balancer-api-external: resolved host name a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:18:29Z"
    - latency: 18.904796ms
      message: 'load-balancer-api-external: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:17:29Z"
    - latency: 7.076812ms
      message: 'load-balancer-api-external: resolved host name a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:17:29Z"
    - latency: 15.47438ms
      message: 'load-balancer-api-external: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:16:29Z"
    - latency: 7.846764ms
      message: 'load-balancer-api-external: resolved host name a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:16:29Z"
    - latency: 16.676768ms
      message: 'load-balancer-api-external: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:15:29Z"
    - latency: 16.003151ms
      message: 'load-balancer-api-external: resolved host name a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:15:29Z"
    - latency: 18.15712ms
      message: 'load-balancer-api-external: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:14:29Z"
    - latency: 8.34038ms
      message: 'load-balancer-api-external: resolved host name a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:14:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-19-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-19.ec2.internal
      uid: 8dcd17c7-7a94-4dec-9626-bec34cd67a19
    resourceVersion: "72593"
    uid: 9f08198b-8688-4f49-a564-f653eb9c6bf4
  spec:
    sourcePod: network-check-source-6f78d59f99-lvg49
    targetEndpoint: a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:48:29Z"
      message: 'load-balancer-api-internal: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.532183ms
      message: 'load-balancer-api-internal: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:18:29Z"
    - latency: 7.52554ms
      message: 'load-balancer-api-internal: resolved host name a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:18:29Z"
    - latency: 14.98826ms
      message: 'load-balancer-api-internal: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:17:29Z"
    - latency: 7.053656ms
      message: 'load-balancer-api-internal: resolved host name a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:17:29Z"
    - latency: 16.45842ms
      message: 'load-balancer-api-internal: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:16:29Z"
    - latency: 7.897772ms
      message: 'load-balancer-api-internal: resolved host name a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:16:29Z"
    - latency: 16.85331ms
      message: 'load-balancer-api-internal: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:15:29Z"
    - latency: 15.97195ms
      message: 'load-balancer-api-internal: resolved host name a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:15:29Z"
    - latency: 18.184988ms
      message: 'load-balancer-api-internal: tcp connection to a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:14:29Z"
    - latency: 8.20475ms
      message: 'load-balancer-api-internal: resolved host name a0fff080e3e6c4ded82a54374be45751-bf7e91f880d0c75f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:14:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-19-to-network-check-target-ip-10-0-134-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-19.ec2.internal
      uid: 8dcd17c7-7a94-4dec-9626-bec34cd67a19
    resourceVersion: "76780"
    uid: a6a568e1-a2d8-446a-8729-f5fd65ae5ea7
  spec:
    sourcePod: network-check-source-6f78d59f99-lvg49
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:49:29Z"
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.939652ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:20:29Z"
    - latency: 2.486696ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:19:29Z"
    - latency: 2.823238ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:18:29Z"
    - latency: 2.44251ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:17:29Z"
    - latency: 2.334825ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:16:29Z"
    - latency: 2.35873ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:15:29Z"
    - latency: 1.989713ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:14:29Z"
    - latency: 2.291445ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:13:29Z"
    - latency: 2.06098ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:12:29Z"
    - latency: 2.022282ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:11:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-19-to-network-check-target-ip-10-0-139-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-19.ec2.internal
      uid: 8dcd17c7-7a94-4dec-9626-bec34cd67a19
    resourceVersion: "76778"
    uid: 0ed796b5-72d7-444d-ba6f-3e75f122abf2
  spec:
    sourcePod: network-check-source-6f78d59f99-lvg49
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:49:29Z"
      message: 'network-check-target-ip-10-0-139-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 931.545µs
      message: 'network-check-target-ip-10-0-139-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:20:29Z"
    - latency: 1.380837ms
      message: 'network-check-target-ip-10-0-139-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:19:29Z"
    - latency: 842.316µs
      message: 'network-check-target-ip-10-0-139-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:18:29Z"
    - latency: 854.099µs
      message: 'network-check-target-ip-10-0-139-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:17:29Z"
    - latency: 797.937µs
      message: 'network-check-target-ip-10-0-139-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:16:29Z"
    - latency: 1.151377ms
      message: 'network-check-target-ip-10-0-139-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:15:29Z"
    - latency: 1.024427ms
      message: 'network-check-target-ip-10-0-139-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:14:29Z"
    - latency: 877.809µs
      message: 'network-check-target-ip-10-0-139-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:13:29Z"
    - latency: 1.120223ms
      message: 'network-check-target-ip-10-0-139-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:12:29Z"
    - latency: 981.375µs
      message: 'network-check-target-ip-10-0-139-19: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:11:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-19-to-network-check-target-ip-10-0-141-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-19.ec2.internal
      uid: 8dcd17c7-7a94-4dec-9626-bec34cd67a19
    resourceVersion: "76779"
    uid: 4fb033a5-3046-4cf0-b41c-4cbf5d246e37
  spec:
    sourcePod: network-check-source-6f78d59f99-lvg49
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:49:29Z"
      message: 'network-check-target-ip-10-0-141-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.685564ms
      message: 'network-check-target-ip-10-0-141-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:20:29Z"
    - latency: 1.878597ms
      message: 'network-check-target-ip-10-0-141-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:19:29Z"
    - latency: 1.514903ms
      message: 'network-check-target-ip-10-0-141-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:18:29Z"
    - latency: 2.11507ms
      message: 'network-check-target-ip-10-0-141-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:17:29Z"
    - latency: 1.89208ms
      message: 'network-check-target-ip-10-0-141-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:16:29Z"
    - latency: 1.511746ms
      message: 'network-check-target-ip-10-0-141-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:15:29Z"
    - latency: 1.938211ms
      message: 'network-check-target-ip-10-0-141-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:14:29Z"
    - latency: 2.251796ms
      message: 'network-check-target-ip-10-0-141-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:13:29Z"
    - latency: 1.924653ms
      message: 'network-check-target-ip-10-0-141-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:12:29Z"
    - latency: 2.006873ms
      message: 'network-check-target-ip-10-0-141-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:11:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-19-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-19.ec2.internal
      uid: 8dcd17c7-7a94-4dec-9626-bec34cd67a19
    resourceVersion: "72592"
    uid: 783e8e22-1156-43bd-885b-1633023a0c3c
  spec:
    sourcePod: network-check-source-6f78d59f99-lvg49
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:48:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 891.567µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:18:29Z"
    - latency: 3.213858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:18:29Z"
    - latency: 935.604µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:17:29Z"
    - latency: 1.770824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:17:29Z"
    - latency: 1.291583ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:16:29Z"
    - latency: 1.772789ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:16:29Z"
    - latency: 840.773µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:15:29Z"
    - latency: 1.783687ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:15:29Z"
    - latency: 729.975µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:14:29Z"
    - latency: 2.032474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:14:29Z"
kind: List
metadata:
  resourceVersion: ""