-
Notifications
You must be signed in to change notification settings - Fork 9
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
[Bug] Kubernetes discovery - targets not being removed after pods tear down #634
Comments
@grzesuav are there any exceptions that appear in the Cryostat container logs at the time (or within some seconds after) you scale down or delete one of these deployments? And could you paste the output from:
|
I see some various errors in cryostat logs, will continue tomorrow to provide more details |
So actually today I see the same targets as in #634 (comment) where the pods aren't ther for many hours. attaching logs which apper now when I am trying to connect. @andrewazores what is the name of the kubernetes discovery logger ? Maybe I can filter logs related to that to find something intertesting ? |
I think the Logger's name should be |
Current Behavior
Currently in the topology/target selection I can still see old/nonexisting targets in the vew, even like 5 minutes after pods stopped
Expected Behavior
Non-running pods are removed
Steps To Reproduce
as you can see, replicaset
f459568bf
is quite old, and it does not currently any running podEnvironment
Anything else?
No response
The text was updated successfully, but these errors were encountered: