At times, we may question the high costs of Cloud providers. However, when constructing infrastructure, the Total Cost of Ownership (TCO) is a crucial factor that must be considered. To maintain a favorable TCO, various measures must be taken, and there are numerous online discussions available on cost optimization.<\/p>\n
In this article, we will explore one method of maintaining a reasonable number of worker nodes by adjusting application requests. In Kubernetes, the request and limit features are utilized to manage resources efficiently. By specifying resource requests for containers in a Pod, the kube-scheduler can determine which node to allocate the Pod to.<\/p>\n
Request configuration is crucial for cost optimization. If requests are set too high, nodes may be provisioned to allocate PODs with excessive resource requests, leading to the wastage of compute resources and a loss of money for the cloud provider.<\/span><\/p>\n In many articles on cost optimization, the resource aspect is often overlooked. It is necessary to review the resources allocated, requested, and utilized for Namespaces in your Kubernetes cluster. However, doing this manually can be a tedious process. Fortunately, all of this information can be obtained from metrics, and dashboards can be created to display this data.<\/p>\n We will cover the following in this article:<\/p>\n