tilt-dev
use crd Established to determine readiness
Describe the Feature You Want
If you deploy a CRD in a Tilt resource, tilt should wait until the Established condition is true before it marks the resource ready and runs its dependencies.
Current Behavior
Currently, if you deploy a CRD with Tilt, tilt will consider it ready as soon as the CRD applies.
Why Do You Want This?
Currently people have to hack around this with local_resource, cf
https://github.com/tilt-dev/tilt/issues/3301
https://github.com/tilt-dev/tilt-extensions/blob/master/helm_remote/Tiltfile
Additional context
Helm has built-in support for this with helm --wait:
https://github.com/helm/helm/issues/11717#issuecomment-1383066316
+1 for this feature, I am adding my use case here. In kubernetes I am deploying Tekton which install a Webhook which takes sometimes to start. Then I am deploying in the same process the tasks and pipelines which are checked by the webhooks. Unfortunatly the tasks and pipelines are not part of the k8_resources known by Tilt so we can't create dependency
