ability to wait on crd deletion before deleting operator
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
Research direction
Start at the tilt down entry point and trace how Kubernetes manifests are sorted and how delete API requests are issued. Compare the proposed default wait, flag and timeout, and operator-specific approaches, then define completion as dependent resources finishing deletion before the operator is removed.
Written by the indexing model from the issue text.
Description
Describe the Feature You Want
In the tilt channel, dougbarth says:
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 downto wait - Add a --wait flag with some
--timeoutflags - 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')
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tilt-dev/tilt
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Tilt at scale Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100