We have a large number of services running inside kubernetes that need to have access to clamav, given the sheer number, i dont want to have to run freshclam process on each virtual machine (container), due to the managemeht and monitoring overhead, and the risk of some not updating for variouis reasons.
Is there any easy way i can share the directories containing the definition database on one server image to all the others so i only have one machine to monitor updates on, we can use docker.kubernetes ability to share persistent volumes to do this, we will be running clamav in single file scan mode, and wont be using the daemon, so syncronising restart of the daemon on updates is not required. Sent from Nine<http://www.9folders.com/> DISCLAIMER The information contained in this email and any attachments are confidential. It is intended solely for the individual or entity to whom they are addressed. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The Red Flag Group is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. Any advice, recommendations or opinion contained within this email or its attachments are not to be construed as legal advice.
_______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
