Artur Zych
Artur Zych
> I would really prefer if we would implement the short term solution described by @chrischdi here [#11960 (comment)](https://github.com/kubernetes-sigs/cluster-api/issues/11960#issuecomment-2751307042) instead. > > With the current PR users have to set...
> > Besides only helping with some scenarios (as stated in the original comment) > > Which additional scenarios would you like to cover? Our idea was to just retry...
Looking at `Progressing` condition and assuming a user perspective, I think I'd be expecting it to be `True` when there is reconciliation going on and we're trying to transition to...
> > Looking at Progressing condition and assuming a user perspective, I think I'd be expecting it to be True when there is reconciliation going on and we're trying to...
Make sure to discuss: https://github.com/operator-framework/kubectl-operator/pull/220#discussion_r1973356442 and https://github.com/operator-framework/kubectl-operator/pull/220#discussion_r1973364583
also, some context for the ideas driving olmv1 commands up to this point: https://github.com/operator-framework/kubectl-operator/pull/225#issuecomment-2710087085 (see general comments section)
One idea worth investigating would be to use the newly introduced /metas endpoint to get filtered (and cached) results we need rather then filtering full-catalog client-side, which should mitigate catalog-size...
@joelanford WDYT? are there any additional considerations with this approach?
@joelanford I agree that this might be a valid concern in non-installation scenarios, though I also wonder that if we'd ever end up in an interrupted state that would prevent...