This message was deleted.

Kubernetes writes lots of events to the datastore all the time, so it will always be writing. If you are using the embedded etcd (which I guess is the default), that will probably be the reason.

I’ve done some further investigation and found that Kubernetes generates a large number of INSERT operations into the kine table. To persist Kubernetes object states. Each transaction is committed individually, which means it must first be written to the WAL (Write-Ahead Log) file—resulting in significant disk write activity. I tested two approaches to reduce this: • tmpfs (RAM disk): • This eliminates disk writes entirely, but introduces the need for periodic database backups to retain at least some persistence in case of a Kubernetes shutdown or crash. • External database (PostgreSQL): • I used PostgreSQL as the backing datastore and experimented with enabling wal_compression to reduce the size of WAL files. However, this had minimal-medium impact on the overall disk write volume.