Closed raghavendra-talur closed 2 months ago
I would rather not do this, we are bloating up
-o wide
and also conditions have their ObservedGeneration that could be stale (we have one such instance with the peer ready condition already) as compared to the resource Generation.
Ack, I mainly did this because when the protection fails due to an error at the vrg layer, available shows true in DRPC and without looking at the protected condition we can't tell if something is wrong.
Updated the PR to fix just the existing issue.
I would rather not do this, we are bloating up
-o wide
and also conditions have their ObservedGeneration that could be stale (we have one such instance with the peer ready condition already) as compared to the resource Generation.