Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: allow exclusing of targets #801

Closed
strowi opened this issue Jan 20, 2023 · 3 comments
Closed

feat: allow exclusing of targets #801

strowi opened this issue Jan 20, 2023 · 3 comments

Comments

@strowi
Copy link
Contributor

strowi commented Jan 20, 2023

Hi,

i noticed during testing i often have to delete bigger parts of the k8s-stack. After doing this for a while i noticed that letsencrypt was running into rate-limits, because the ingress would be deleted too.
It would be nice to have the opposite of "-t" to be able to specify excluded resources.

@zerok
Copy link
Contributor

zerok commented May 27, 2024

Hi :) What's your actual workflow? Do you run tk apply, then do manual changes, and combine that with something like tk delete?

@strowi
Copy link
Contributor Author

strowi commented May 27, 2024

Hey ;)

Been a while since i wrote that, but I "think" the actual problem here was me being lazy and wiping ALL secrets (with kubectl delete ...,secrets --all ) from a namespace (because some operator would create those automatically). And letsencrypt was more or less a bad side-effect.

Also it seems i can do what i want with negative-regex (tk apply .. -t '!...') although a little more complicated).

@zerok
Copy link
Contributor

zerok commented May 27, 2024

Yes, that should do it 🙂 I'll close this issue then. If it's still relevant, please reopen 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants