如何在启动 EKS 集群时减少停机时间？
[英]How to reduce the downtime while launching a EKS cluster?
问题描述
I am trying to launch a kubernetes cluster over EKS which would have multiple pods in it.
我正在尝试通过 EKS 启动 kubernetes 集群，其中包含多个 pod。 Once the worker node has maximum pods on it running then a new node launches and the extra pod launches over the new node.一旦工作节点上运行了最大的 pod，就会启动一个新节点，并在新节点上启动额外的 pod。 Launching of a new node takes time and creates a downtime which I want to reduce.启动新节点需要时间并且会造成我想减少的停机时间。 Pod disruption budget is one option but I am not sure how to use it with scaling up of nodes. Pod 中断预算是一种选择，但我不确定如何使用它来扩展节点。
1 个解决方案
解决方案1
2 2020-11-28 15:08:18
A simpler way to approach this would be to have your scaling policies pre-defined to scale up at reasonably lower limits.解决此问题的一种更简单的方法是预先定义您的扩展策略以在合理的较低限制下进行扩展。 This way, let's say if your server reaches 60% of the capacity and triggers a scale up - you would have enough grace time to not face a downtime (since the first one can handle requests while the second one bootstraps) and allow the the new server to come up.这样，假设您的服务器达到 60% 的容量并触发扩展 - 您将有足够的宽限时间来避免停机（因为第一个可以处理请求，而第二个可以引导）并允许新的服务器上来。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.