本文介绍了GKE kubernetes上的节点大小的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们使用两个标准类型为2的节点运行集群:7.5Gb和2vCPU

We run our cluster with two nodes of type standard 2: 7.5Gb and 2vCPU

在GKE上是否有任何建议的最小群集大小.我认为没有真正的主人,因为这是一项托管的服务"?

are there any recommended minimum size for a cluster on GKE. I assume there is no real master as this is a managed "service"?

我正在努力应对资源限制.

I'm struggling to deal with resource limits.

推荐答案

没有建议的最小大小.但是,广告连播具有 CPU和内存的请求和限制.

There is no recommended minimum size. However, pods have both CPU and memory requests and limits.

请求定义一个节点上必须有多少可用CPU/内存,以便可以在该节点上调度pod;然后,该金额将预留给该广告连播,在安排下一个广告连播时不会被视为免费".
另一方面,限制定义了广告连播可以请求的最大数量-这些可能会被过度使用.

Requests define how much free CPU/memory there must be on a node so a pod can be scheduled there; that amount is then reserved for that pod and won't be considered 'free' for scheduling of a next pod.
On the other hand, limits define the maximum amount a pod can ask for - these can be overcommitted.

尝试查看您的kubectl describe nodes输出,其中列出了所有Pod及其请求和限制.默认情况下,请求量为100m(核心的10%)-如果您知道某些吊舱不需要那么多,请将其设置得较低.然后,您将能够在一个节点上安排更多的Pod,或者至少计算出所需的节点数.

Try looking at your kubectl describe nodes output, which lists all pods and their requests and limits. By default, the requests are 100m (10% of a core) - if you know that some of your pods don't need that much, set this lower. Then you will be able to schedule more pods on a node or at least work out the number of nodes you need.

这篇关于GKE kubernetes上的节点大小的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-28 03:47