如何增加Google kubernetes引擎上主节点的大小? [英] How can I increase the size of master node on google kubernetes engine?

查看:73
本文介绍了如何增加Google kubernetes引擎上主节点的大小?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在寻找增加GKE上主节点VM大小的方法.

I'm looking for a way to increase the master node VM size on GKE.

https://kubernetes .io/docs/admin/cluster-large/#size-of-master-and-master-components ,建议对于11-100个节点的群集,我们应使用n1-standard-4 VM Kubernetes大师.

On https://kubernetes.io/docs/admin/cluster-large/#size-of-master-and-master-components it suggests that for a cluster of 11-100 nodes we should be using an n1-standard-4 VM for Kubernetes master.

但是,由于群集开始时较小,并且已经增长到此大小,这是否意味着我们陷入了主力不足的主节点的困境?通过上面的链接:

However, since the cluster has started out smaller, and since grown to this size, does that mean that we're stuck with an underpowered master node? From the above link:

请注意,这些主节点的大小目前仅在集群启动时设置,如果以后再放大或缩小集群(例如,手动删除或添加节点,或使用集群自动缩放器),则不会进行调整"

Note that these master node sizes are currently only set at cluster startup time, and are not adjusted if you later scale your cluster up or down (e.g. manually removing or adding nodes, or using a cluster autoscaler)"

那么,有什么办法可以增加母版的大小?

So, is there any way to increase the size of the master?

推荐答案

您指出的Kubernetes文档是正确的,并且应该修改,因为master确实可以扩展.

The Kubernetes documentation that you pointed out is NOT correct and should be modified since the master actually scales.

首先请注意,如果群集的行为稳定且性能良好,则用户无需担心Google Cloud如何以及何时调整主数据库的大小.

First of all notice that how and when Google Cloud takes care of resizing the master should not be a concern for users if the behaviour of the cluster is stable and performant.

这是一项托管服务,因此某些细节不是公开的,例如,主机的大小调整方式以及使用的算法不共享.

It is a managed service and therefore some details are not public, for example how the master is resized and which algorithms are used are not shared.

此外,在自动定标器GKE中没有有关主计算机的机器类型的信息或免责声明

Moreover there is no information or disclaimer regarding the machine type of the master in the autoscaler GKE official documentation and it if the master was not able to resize since it would have been an action potentially disruptive for the cluster health.

主虚拟机将自动缩放,升级,备份和保护"

"Master VM is automatically scaled, upgraded, backed up and secured"

但是,如果需要,您可以测试行为:

However if you want you can test the behavior:

  • 创建具有一个节点的集群

  • Create a cluster having one node

添加10个节点

暂时无法访问主服务器,对API的调用将解决错误

The master will be not reachable for a moment and a call to the API will resolve in an error

   $ gcloud container clusters get-credentials cluster-1 --zone us-central1-a --project **-**
   Fetching cluster endpoint and auth data.
   WARNING: cluster cluster-1 is not running. The kubernetes API may not be available.

  • 检查日志,您会注意到在日志中将显示主升级"条目

  • Inspect the logs, you will notice that in the logs will be present an entry "master upgrade"

    有一个功能请求,要求改进Google云文档,您可以决定对其加注星标以便接收更新.

    There is an feature request asking to Improve the Google cloud documentation, you can decide to star it in order to receive updates.

    另一方面,为了修复Kubernetes文档,我打开了公开问题 Github.

    On the other hand to fix the Kubernetes documentation I opened a public issue on Github.

    这篇关于如何增加Google kubernetes引擎上主节点的大小?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

  • 查看全文
    登录 关闭
    扫码关注1秒登录
    发送“验证码”获取 | 15天全站免登陆