简体   繁体   English

容器和 Kube.netes 是 IaaS 还是 PaaS?

[英]Are Containers and Kubernetes IaaS or PaaS?

Since we don't need to configure most of the Infrastructure services for Containers and Kube.netes, still we have ability to manage different Infrastructure services.由于我们不需要为容器和 Kube.netes 配置大部分基础设施服务,我们仍然有能力管理不同的基础设施服务。 Does this make them Infrastructure as a Service or Platform as a Service?这会使它们成为基础架构即服务还是平台即服务?

kubernetes is considered PaaS when the control p lane components : the scheduler, the API server, ETCD (key-value metadata)and controller are managed by the provider some examples are Microsoft AKS , Google GKE , AWS EKS . kubernetes 被认为是 PaaS,当控制通道组件:调度程序、API 服务器、ETCD(键值元数据)和controller 、Google GKE由 AWS AKS提供商管理。 It is considered IaaS if you built and maintain all the components如果您构建和维护所有组件,则将其视为 IaaS

Kubernetes is neither IaaS nor PaaS. Kubernetes 既不是 IaaS 也不是 PaaS。 It's a container orchestration engine which makes it more like a Container As A Service or CaaS.它是一个容器编排引擎,使它更像一个容器即服务或 CaaS。

You need a IaaS layer below kubernetes to provide it VMs like for example AWS EC2 or bare metal servers.您需要在 kubernetes 下方的 IaaS 层为其提供 VM,例如 AWS EC2 或裸机服务器。

Kubernetes can be used as a platform for building Platform As a Service on top of it and CloudFoundry on Kubernetes is an example of a PaaS built on kubernetes. Kubernetes 可用作在其上构建平台即服务的平台,Kubernetes 上的CloudFoundry是构建在 kubernetes 上的 PaaS 示例。

I have to dissent a bit with the answer here above.我不得不对上面的答案持不同意见。 All technical definitions are quite meticolous, but are often a model to explain what's in place, and so they can change over time or overlap a bit.所有的技术定义都非常细致,但通常是 model 来解释什么是适当的,因此它们可以随着时间的推移而改变或稍微重叠。

A couple of years ago there was no "Container as a Service" or "CaaS" whatsoever.几年前,还没有任何“容器即服务”或“CaaS”。 Container platforms, were just called "PaaS", or "Platform as a Service".容器平台,被称为“PaaS”,或“平台即服务”。 At some point "PaaS" became ambiguous because there were many platforms usable by developers that fit "PaaS" definition: amongst these PaaS techonolgies, some were in turn running on Kube.netes platform, which was also defined as PaaS.在某些时候,“PaaS”变得模棱两可,因为开发人员可以使用许多符合“PaaS”定义的平台:在这些 PaaS 技术中,有些又运行在 Kube.netes 平台上,该平台也被定义为 PaaS。

Somebody felt the need to distinguish the two concepts in order to better communicate with developers if they had to choose between a more abstract platform, or to directly rely upon container orchestration (most widespread Kube.netes).有人觉得有必要区分这两个概念,以便在开发人员必须在更抽象的平台之间进行选择或直接依赖容器编排(最流行的 Kube.netes)时更好地与开发人员沟通。 So, distinction between PaaS and CaaS was introduced.因此,介绍了 PaaS 和 CaaS 之间的区别。

This is how it happened that in previous definition Kube.netes and container orchestration in general were defined simply as "PaaS".这就是在之前的定义中 Kube.netes 和容器编排通常被简单地定义为“PaaS”的原因。 And nowadays they are called "CaaS".现在它们被称为“CaaS”。

Instead Infrastructure as a Service, or simply "IaaS", is the infrastructure layer upon which Kube.netes runs: namely the virtual machine instances into which the Kube.netes nodes are implemented, the.network connectivity part, and other basic elements. Infrastructure as a Service,或简称为“IaaS”,是运行 Kube.netes 的基础设施层:即在其中实现 Kube.netes 节点的虚拟机实例、.network 连接部分和其他基本元素。

Beware: happens that these definitions are used in a different manner over time by VENDORS , that tend to mix a bit of commercial pushing (ie towards a new product) into what is presented just as a technical overview article.当心:供应商会随着时间的推移以不同的方式使用这些定义,这往往会将一些商业推动(即针对新产品)混合到作为技术概述文章呈现的内容中。 Don't be fooled;不要被愚弄了; ;-) ;-)

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

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