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
{{ message }}
This repository has been archived by the owner on Oct 3, 2020. It is now read-only.
Kube-janitor is a very good tool to remove dangling resources. It would be good if it can integrate resource deletion notifications feature also. for ex. If kube-janitor deletes a namespace then user should get a notification for the same.
Start with notification channels like Email, Slack. Later more channels can be added.
The text was updated successfully, but these errors were encountered:
That would be helpful.
Looking at this flag --resource-context-hook it seems to run each cycle while some objects are annotated with a ttl.
Is it possible to know that now items have been deleted and something could be done with those items? then it'd be already possible to do a lot
I didn’t write back here but I use a hook in janitor to check the events, if entries with the delete notification have been created by janitor then some external APIs are called to cleanup non k8s resources which are related (in our case vault roles for a namespace)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Kube-janitor is a very good tool to remove dangling resources. It would be good if it can integrate resource deletion notifications feature also. for ex. If kube-janitor deletes a namespace then user should get a notification for the same.
Start with notification channels like Email, Slack. Later more channels can be added.
The text was updated successfully, but these errors were encountered: