Closed mregen closed 2 months ago
Issue has been automatically marked as stale due to inactivity for 90 days. Update the issue to remove label, otherwise it will be automatically closed.
Issue has been automatically marked as stale due to inactivity for 90 days. Update the issue to remove label, otherwise it will be automatically closed.
The delay comes from do_discover_on_discovery_handler, if get_stream returns None. Agent waits for 60 seconds, 60 seconds is hard-coded. // If a connection cannot be established with the Discovery Handler, it will sleep and try again.
Issue has been automatically marked as stale due to inactivity for 90 days. Update the issue to remove label, otherwise it will be automatically closed.
Issue has been automatically marked as stale due to inactivity for 90 days. Update the issue to remove label, otherwise it will be automatically closed.
Describe the bug
After updating a helm chart with new configuration that requires a new start of the discovery handler, it takes one minute after registration until the first discover call is received. Can this delay be configured? If not, can you make it configurable?
Output of
kubectl get pods,akrii,akric -o wide
Kubernetes Version: [K8s]
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Delay from registration to first discover call is in the seconds range after registration or configurable.
Logs (please share snips of applicable logs)
---> 1 minute delay until first discovery call