konk-service-operator should check that apiservice is ready before marking itself ready

[drewwells]

KONK service operator will deploy apiregistration objects pointing to the apiservice. We can verify apiservice readiness with kubectl. kubectl get apiservice tends not to be a good check of actual readiness. It will report ready even when there's no endpoints matching the service. Requesting the kind directly will verify availability ie. until kubectl get contact.example.infoblox.com; do sleep 5s; done

Helm operator then should mark the CR status ready which will let users verify their resources are deployed correctly to KONK. CR status does not currently verify pod availability, see
operator-framework/operator-sdk#4102

[drewwells]

kubectl wait --for condition=ready apiservice {name}