Open bb03 opened 7 months ago
Hmmm... What does helm version
show?
version.BuildInfo{Version:"v3.13.3", GitCommit:"c8b948945e52abba22ff885446a1486cb5fd3474", GitTreeState:"clean", GoVersion:"go1.21.5"}
(deleted a previous comment, i misunderstood something about the bug report)
hmmm...i can reproduce this in https://app.circleci.com/pipelines/github/tilt-dev/tilt-extensions/1504/workflows/1e98f416-7181-4bcc-b789-cf8d0b18f32c/jobs/3578, though not sure what's going on.
ya, i think this is just tilt assuming the process got stuck and killing the process. we should have a more graceful shutdown, but for now, you can do something like:
update_settings(k8s_upsert_timeout_secs=120)
to give it a longer timeout.
Thanks Nick! Your workaround did the trick. Would you like me to keep this ticket open regarding having a more graceful shutdown? Or a more user-friendly timeout message?
Setup: Kubernetes cluster:
kind v0.20.0 go1.20.5 linux/amd64
Python version:Python 3.9.16
With this file as kyverno-test.tilt
Repro steps I ran the following commands in this order
On step 4 I'm seeing the following issue
And then on step 5 I see this
Adding --delete-namespaces to the delete command - step 4, resulted in
Expected outcomes I would like to understand why the helm-delete-helper failed to delete the kyverno resourcess, and if possible, can tilt handle these types of errors so that all resources created by a tilt up get cleaned up. Thank you!