英文:
EKS nodes scaling to 0
问题
如果集群中没有节点（即自动扩展组将节点设置为0），EKS中不同的服务（如kube-proxy等）是如何运行的？这些服务不是需要节点才能运行吗？
英文:
I have a question about EKS scaling nodes to 0. If there are no nodes in the cluster(which means auto scaling group set nodes to 0) how are different services running in EKS . like kube-proxy etc?
Shouldn't these services need a node in order to run?
答案1
得分: 2
EKS节点扩展仅适用于工作节点。
AWS 在托管的 AWS 帐户中管理控制平面。您无法在您的帐户中看到这些节点。
Amazon EKS 控制平面包括运行 Kubernetes 软件的控制平面节点，例如 etcd 和 Kubernetes API 服务器。控制平面在由 AWS 管理的帐户中运行，Kubernetes API 通过与您的集群关联的 Amazon EKS 终端节点公开。每个 Amazon EKS 集群控制平面都是单租户和独特的，并在其自己的一组 Amazon EC2 实例上运行。
所有由 etcd 节点和相关的 Amazon EBS 卷存储的数据都使用 AWS KMS 进行加密。集群控制平面在多个可用区进行规划，并由弹性负载均衡网络负载均衡器提供前端。Amazon EKS 还会在您的 VPC 子网中预置弹性网络接口，以提供控制平面实例与节点之间的连接（例如，以支持 kubectl exec logs 代理数据流）。
查看这里。
英文:
EKS node scaling is only for worker nodes.
AWS manages control plane in a AWS managed account. You don't see those nodes in your account.
> The Amazon EKS control plane consists of control plane nodes that run the Kubernetes software, such as etcd and the Kubernetes API server. The control plane runs in an account managed by AWS, and the Kubernetes API is exposed via the Amazon EKS endpoint associated with your cluster. Each Amazon EKS cluster control plane is single-tenant and unique, and runs on its own set of Amazon EC2 instances.
>
> All of the data stored by the etcd nodes and associated Amazon EBS
> volumes is encrypted using AWS KMS. The cluster control plane is
> provisioned across multiple Availability Zones and fronted by an
> Elastic Load Balancing Network Load Balancer. Amazon EKS also
> provisions elastic network interfaces in your VPC subnets to provide
> connectivity from the control plane instances to the nodes (for
> example, to support kubectl exec logs proxy data flows).
Check here
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论