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 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.
The text was updated successfully, but these errors were encountered:
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).
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.
The text was updated successfully, but these errors were encountered: