Current RAN DU validator policy CR does not check for pod stability, which allows issues like OCPBUGS-65953 to occur without obvious feedback to the user.  Who likely assumes deployed spoke is in a good state if all policies are compliant but some pods don't settle into a good state.

If possible, the validator policy should wait to see if all pods (or at least critical ones for RAN DU and cluster operation)
are stable running, and not stuck in crash loop, or init, etc.

    

All versions of the Validator source-cr

    

Always when there are broken pods
    

    1. Deploy RAN DU spoke with source-cr policies configure
    2. Observe that the volidator policy goes compliant even if pods are not in a stable state after policies are applied successfully
    3.
    

validator does not monitor for pod  stability
    

validator CR should include checks for pods to be "stable enough" before changing to compliant state