简体   繁体   English

单个 Kubernetes 实例上的多个客户端的多个 Pod

[英]Multiple Pods for multiple clients on a single Kubernetes Instance

I'm trying to wrap my head around how/if Kubernetes manages multiple Pods in terms of a clustered client model.我试图围绕 Kubernetes 如何/是否根据集群客户端模型管理多个 Pod 进行思考。 Based on this documentation Multi-container it sounds as though Kubernetes is only concerned with the health of a pod and the containers within it.根据这个文档Multi-container听起来好像 Kubernetes 只关心 pod 和其中的容器的健康状况。 This means that a single Kubernetes instance could manage multiple client's pods, which contain containers running that client's applications, microservices etc.这意味着单个 Kubernetes 实例可以管理多个客户端的 pod,其中包含运行该客户端应用程序、微服务等的容器。 在此处输入图片说明

Is this correct?这样对吗?

Please see my diagram for a clearer idea of what I'm asking.请查看我的图表以更清楚地了解我的要求。

The diagram has the right idea, but not quite the right terminology.该图有正确的想法,但不是完全正确的术语。

The diagram would be more accurate if the "Pod" label was replaced with "Namespace", and the "Container" label was replaced with "Pod".如果将“Pod”标签替换为“Namespace”,并将“Container”标签替换为“Pod”,则图表会更准确。

A single Kubernetes cluster is intended to be able to support multi-tenancy, where the workloads of individual clients can run with proper security, resource allocation, isolation, and other important tenancy management attributes.单个 Kubernetes 集群旨在能够支持多租户,其中各个客户端的工作负载可以以适当的安全性、资源分配、隔离和其他重要的租户管理属性运行。

The unit of tenancy, however, is a namespace- a logical layer of abstraction in which are deployed workloads, usually for an individual client- not a pod, and the unit of replication for workload processing is the pod (comprising one or more containers), not an individual container.然而,租户单元是一个命名空间——一个逻辑抽象层,其中部署了工作负载,通常用于单个客户端——而不是 pod,工作负载处理的复制单元是 pod(包含一个或多个容器) ,不是单个容器。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM