Readiness utility should be able to support extension

[iocanel]

Currently the readiness utility only supports kubernetes resources.

We should use the spi in order to optionally extend the behavior to openshift, knative etc resources.

[rohanKanojia]

Umm, I think we do have Readiness supported for OpenShift resources[0].

https://github.com/fabric8io/kubernetes-client/blob/master/openshift-client/src/main/java/io/fabric8/openshift/client/internal/readiness/OpenShiftReadiness.java

[iocanel]

That's awesome!
I think that we need to use the spi, so that we have a signle readiness utility exposed.

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[shawkins]

Removing the never stale. We should determine if this worth pursuing on its own, or if it's sufficient to point people towards using their own predicate (not via an spi) for isReady and use watiForCondition instead of waitUntilReady - along with some further javadocs for isReady and waitUntilReady.

Given some of the confusion with what isReady is supposed to do (#3474), it may be best just to direct people toward using their own predicates and leave the built-in readiness as is for now.

It does appear some of the extension models have status ready and/or replica fields - it would be nice where applicable to at least put a static method for that resource type on the XXXClient interface.

[manusa]

isReady is an internal, subjective concept of the Fabric8 client which might or might not match what other tools consider as a Ready Kubernetes object (kubectl, Kubernetes dashboard(s), and so on).

We should encourage users to rely on the waitUntilConditon and other methods.

Given some of the confusion with what isReady is supposed to do (#3474), it may be best just to direct people toward using their own predicates and leave the built-in readiness as is for now.

So yes, +1.

It does appear some of the extension models have status ready and/or replica fields - it would be nice where applicable to at least put a static method for that resource type on the XXXClient interface.

I think this is aligned with the similar #3586 (and #3816)