WordPress database error: [Disk full (/tmp/#sql-temptable-1-0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_options`

WordPress database error: [Disk full (/tmp/#sql-temptable-1-0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_options`

WordPress database error: [Disk full (/tmp/#sql-temptable-1-0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW COLUMNS FROM `wp_cptch_whitelist` LIKE 'ip_from_int'

WordPress database error: [Disk full (/tmp/#sql-temptable-1-0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_options`

The Kubernetes 110 pod limit per node – My Personal Blog
Cloud Kubernetes

The Kubernetes 110 pod limit per node

by Kubovy

The maximum pods per node has a hard limit of 110. After a bit of googling I found #23349. Since in my config I have few bit larger nodes I definitely would like to increase this hard limit.

This can be done by setting the --max-pods in kubelet and restarting the service. For microk8s the configuration file can be found:

/var/snap/microk8s/current/args/kubelet

Add line to the bottom (limit to 200 pods):

--max-pods=200

And restart the service:

$ service snap.microk8s.daemon-kubelet restart

PS: This needs to be done on each node.

2 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

WordPress database error: [Disk full (/tmp/#sql-temptable-1-0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW COLUMNS FROM `wp_cptch_whitelist` LIKE 'ip_from_int'

WordPress database error: [Disk full (/tmp/#sql-temptable-1-0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_options`

Copyright © Jan Kubovy. All rights reserved. Theme: Blog Elite by Themesaga