DiskPressure 使节点崩溃 [英] DiskPressure crashing the node
问题描述
DiskPressure 的真正含义是什么以及如何在容器创建过程中在 Kubernetes 中避免它?
What does DiskPressure really means and how it can be avoided in kubernetes during container creation?
似乎当我在一个节点上创建一个新容器时,很有可能由于压力而导致整个节点崩溃......
Seemingly when I creating a new container on a node there is a high chance that it is crashing the whole node because of the pressure...
推荐答案
来自 文档 您会发现 DiskPressure
在以下情况下会引发:
From the documentation you'll find that DiskPressure
raises when:
节点的根文件系统或映像文件系统上的可用磁盘空间和 inode 已满足驱逐阈值
Available disk space and inodes on either the node’s root filesytem or image filesystem has satisfied an eviction threshold
在出现这些问题时了解节点的状况有些重要(还剩多少空间/inode,...),了解相关的容器映像也很重要.这可以通过一些基本的系统监控来完成(请参阅资源使用监控).
Learning about the conditions of your nodes whenever these issues occur is somewhat important (how much space/inodes are left, ...) and also learning about the related container images is important. This can be done with some basic system monitoring (see the Resource Usage Monitoring).
了解条件后,您应该考虑调整--low-diskspace-threshold-mb
、--image-gc-high-threshold
和--image-gc-low-threshold
你的参数 kubelet,以便始终有足够的空间用于正常操作,或者考虑为您的节点提供更多空间,具体取决于需求.
Once you know about the conditions, you should consider to adjust the --low-diskspace-threshold-mb
, --image-gc-high-threshold
and --image-gc-low-threshold
parameters of you kubelet, so that there's always enough space for normal operation, or consider to provision more space for you nodes, depending on the requirements.
这篇关于DiskPressure 使节点崩溃的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!