You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’ve been playing with a k8s operator to create a ClickHouse cluster based on a CRD being installed by Tilt. Creating the cluster works well, but when I run tilt down, the operator is deleted before the cluster is torn down, causing the next usage of tilt up to fail.
Current Behavior
currently, tilt down sorts all the kubernetes manifests in reverse order, and issues delete API requests
it does not wait on one resource to finish deleting before it waits for the next one.
Possible solutions
Change the default behavior of tilt down to wait
Add a --wait flag with some --timeout flags
detect the CRD / operator case in particular, and adjust for that
Current Workaround
You can hack in deletion in a particular order with something like:
if config.tilt_subcommand == 'down':
local('kubectl delete my-resource --all')
The text was updated successfully, but these errors were encountered:
Describe the Feature You Want
In the tilt channel, dougbarth says:
Current Behavior
currently,
tilt down
sorts all the kubernetes manifests in reverse order, and issues delete API requestsit does not wait on one resource to finish deleting before it waits for the next one.
Possible solutions
tilt down
to wait--timeout
flagsCurrent Workaround
You can hack in deletion in a particular order with something like:
The text was updated successfully, but these errors were encountered: