Database Deployment on WordPress filling Storage

The current configuration of WordPress database deployment (MySQL), will produce several binlog.00xxxx consuming several GBs of storage on the persistent storage. This will create an increase pressure on storage, which without automatic resizing when reaching the limit, neither an alert system that would trigger a manual action, will lead to downtime/unavailability of instances (which is more likely to affect high traffic websites).

One possible solution to mitigate this issue is to change the MySQL configuration of the affected websites (currently oqi.cern) to have a purge binlogs after some time (eg: set binlog_expire_logs_seconds , see more: https://dev.mysql.com/doc/refman/8.4/en/replication-options-binary-log.html).

Current highly affected instance:
open-quantum-institute.cern