Readiness checks in the deployment process

Is your feature request related to a problem? Please describe.
First of all thanks for the great project ! I am currently looking into how I could deploy a postgres instance with it, therefore I would like to deploy an operator (https://github.com/zalando/postgres-operator) together with a minimal cluster configuration.
For that I just copied the files listed for manual deployment in the tutorial section of the Zalando Operator into my ServiceBrokerConfiguration and added the minimal-postgres-manifest Configuration.
The problem I am facing is that when the Configuration for the postgres cluster (a Custom Resource, defined as a template in the Service Broker configuration) gets deployed the postgres operator will not be fully up and running and the CRDs will not be installed. So I will always get an unknown resource error ( “Provision call failed: no matches for kind "postgresql" in version "acid.zalan.do/v1” “). The problem is that it takes a few seconds for the operator to start and install the resources, so by the time the Service Broker deploys the configuration for a cluster, it will not be done.

Describe the solution you'd like
Best case would be to be able to define readiness checks (like the ones for service instances) so that the following templates will only be deployed after the readiness check passes.

Describe alternatives you've considered
Alternatively the solution that works for me is to deploy the operator before hand and only let the service broker deploy the configurations.

[spjmurray]

Sounds like we need to take what we have (create a bunch of stuff, do readiness check), into a set of steps (each creating stuff and doing readiness checks). Then you can make the transition between steps a barrier. Yep, I'm game!