Clean up old log parsers / machines
My security engine currently shows 30 log parsers in
cscli and the console. The log parsers specifically are old LAPI pods. I understand there are options to automatically clean up old agent and bouncer connections though it apparently doesn't apply to LAPI. Is there a way to cause these to be cleaned up automatically? I know I can cscli machine prune but in a kubernetes environment it's expected that pods are ephemeral, so it seems like there should be a function to autodelete or autoprune these.4 Replies
Important Information
Thank you for getting in touch with your support request. To expedite a swift resolution, could you kindly provide the following information? Rest assured, we will respond promptly, and we greatly appreciate your patience. While you wait, please check the links below to see if this issue has been previously addressed. If you have managed to resolve it, please use run the command
/resolve or press the green resolve button below.Log Files
If you possess any log files that you believe could be beneficial, please include them at this time. By default, CrowdSec logs to /var/log/, where you will discover a corresponding log file for each component.
Guide Followed (CrowdSec Official)
If you have diligently followed one of our guides and hit a roadblock, please share the guide with us. This will help us assess if any adjustments are necessary to assist you further.
Screenshots
Please forward any screenshots depicting errors you encounter. Your visuals will provide us with a clear view of the issues you are facing.
© Created By WhyAydan for CrowdSec ❤️
I do see this config value: https://docs.crowdsec.net/docs/next/configuration/crowdsec_configuration/#unregister_on_exit though maybe these old pods are from before it was added.
I'm going to mark this as solved for now, I'll open a new ticket if the problem continues.
Resolving Clean up old log parsers / machines
This has now been resolved. If you think this is a mistake please run
/unresolve
Unresolving Clean up old log parsers / machines
This has now been unresolved.After redeploying the helm chart for a LAPI change, I now see the old LAPI pods, and the new LAPI pods in
cscli machine list. Not sure exactly how the unregister process is supposed to take place, but it didn't seem to work.