![]() ![]() So, it's obvious that it's important to cleanup all the unused PVCs to save money. Similarly to ephemeral storage also persistent volumes can become source of issues, especially if you're running Kubernetes in some cloud and therefore paying for each PVC you provision. If you want to check what's the current state of storage on node you can run df -h /var/lib on the node itself. If the node start to run low on ephemeral storage, it will become tainted and you will probably find out about that pretty quickly. Running too many pods on the node can also contribute to this issue because ephemeral storage is used for container images, and writeable layers of containers. You can hit the limit pretty quickly which could lead to pods getting evicted or new pods not being able to start on the node. With all the running pods on the nodes, all of them using at least a bit of ephemeral storage for things like logs, cache, scratch space or emptyDir volumes. That being said, if you have very big nodes with lots of memory/CPU, you surely can go higher - possibly even 500 per node as tested here with OpenShift, but if you push the limits, don't be surprised when things start acting up and not just because of insufficient memory or CPU.Īnother issue you might encounter is insufficient ephemeral storage. First of them is number of pods per node, which based on Kubernetes docs should be at most 110. There are some basic limits that every Kubernetes cluster has. So, let's look at some common/basic issues which these forgotten resources can cause: Well, it isn't causing any damage right now, but when things accumulate over time they start having impact on cluster performance and stability. Some forgotten Pods, unused persistent volume, Completed Jobs or maybe old ConfigMap/Secret doesn't matter, or does it? It's just sitting there and I might need it at some point! Why subject yourself to unnecessary pain and trouble when you can setup simple, yet sophisticated rules, automation and monitoring that can keep you cluster tidy and clean without rogue workloads eating your resources or stale objects lying around? Why Bother? ![]() Whether it's etcd, volumes, memory or CPU. As your cluster grows, so does the number of resources, volumes or other API objects and sooner or later you will reach the limits somewhere. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |