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

Namespace deletion is not monitored #2

Open
rascasoft opened this issue Dec 29, 2021 · 0 comments
Open

Namespace deletion is not monitored #2

rascasoft opened this issue Dec 29, 2021 · 0 comments

Comments

@rascasoft
Copy link
Collaborator

If you want to monitor a namespace that does not exists, vessel starts correctly anyways and once you start creating new resources, it correctly detects them:

12/29/2021 04:27:28 [watch_ha][INFO] -> mynamespace::Deployment::nginx-deployment
12/29/2021 04:27:28 [loggers][INFO] Handler 'on_event' succeeded.
12/29/2021 04:27:30 [watch_ha][INFO] -> mynamespace::Deployment::nginx-deployment
12/29/2021 04:27:30 [loggers][INFO] Handler 'on_event' succeeded.

And you get the results of the scan inside the database, so you can query and see them correclty.
Problem comes when you delete the namespace (and not the single resource, which works): change is not detected and you still get the issues inside the queries, even if the resource(s) does not exists anymore.

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

No branches or pull requests

1 participant