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