The question “Kubernetes vs. Docker?” in itself is rather absurd, like comparing apples to oranges. One isn’t an alternative to the other. Quite the contrary, Kubernetes can run without Docker and Docker can function without Kubernetes. But Kubernetes can (and does) benefit greatly from Docker and vice versa.
中文翻译
"“Kubernetes vs. Docker?”这个问题本身相当荒谬,就像比较苹果和橙子一样。它们不是相互替代的。恰恰相反,Kubernetes 可以在没有 Docker 的情况下运行,而 Docker 也可以在没有 Kubernetes 的情况下工作。但 Kubernetes 可以(并且确实)从 Docker 获得很大的好处,反之亦然。"
Docker is a standalone application which can be installed on any computer to run containerized applications. Containerization is an approach of running applications on an OS such that the application is isolated from the rest of the system. You create an illusion for your application that it is getting its very own OS instance, although there may be other containers running on the same system. Docker is what enables us to run, create and manage containers on a single operating system.
中文翻译
Docker 是一个独立的应用程序,可以安装在任何计算机上,用于运行容器化应用程序。容器化是一种在操作系统上运行应用程序的方法,使应用程序与系统的其余部分隔离开来。您为您的应用程序创建了一个假象,让它认为它有自己的操作系统实例,尽管可能在同一系统上运行其他容器。Docker 是让我们能够在单个操作系统上运行、创建和管理容器的工具。
Kubernetes turns it up to eleven. If you have Docker installed on a bunch of hosts (different operating systems), you can leverage Kubernetes. These nodes or Docker hosts can be bare metal servers or virtual machines. Kubernetes can then allow you to automate container provisioning, networking, load-balancing, security and scaling across all these nodes from a single command-line or dashboard. A collection of nodes that are managed by a single Kubernetes instance is referred to as a Kubernetes cluster.
中文翻译
Kubernetes 把它推向了更高级别。如果您在一堆主机上安装了 Docker(不同的操作系统),您可以利用 Kubernetes。这些节点或 Docker 主机可以是裸机服务器或虚拟机。然后,Kubernetes 可以允许您从单个命令行或仪表板自动化容器的配置、网络、负载均衡、安全性和扩展,跨所有这些节点。由单个 Kubernetes 实例管理的一组节点被称为 Kubernetes 集群。
Now, why would you need to have multiple nodes in the first place? The two main motivations behind it are:
中文翻译
那么,为什么首先需要多个节点呢?背后的两个主要动机是
To make the infrastructure more robust — Your application will be online, even if some of the nodes go offline, i.e, High Availability. To make your application more scalable — If workload increases simply spawn more containers and/or add more nodes to your Kubernetes cluster. “Kubernetes automates the process of scaling, managing, updating and removing containers. In other words, it is a container orchestration platform. While Docker is at the heart of the containerization, it enables us to have containers in the first place.
中文翻译
为了使基础设施更加健壮 — 即使一些节点下线,您的应用程序也将在线运行,即实现高可用性。为了使您的应用程序更加可扩展 — 如果工作负载增加,只需生成更多容器和/或添加更多节点到您的 Kubernetes 集群。 "Kubernetes 自动化了扩展、管理、更新和删除容器的过程。换句话说,它是一个容器编排平台。虽然 Docker 是容器化的核心,它使我们能够首次使用容器。
In principle, Kubernetes can work with any containerization technology. Two of the most popular options that Kubernetes can integrate with are rkt and Docker. However, Docker has won the greatest market segment and that has led to a lot of effort in perfecting the integration between Docker and Kubernetes, more than any other containerization technology.
中文翻译
原则上,Kubernetes 可以与任何容器化技术一起使用。Kubernetes 可以与最流行的两种选项集成,分别是 rkt 和 Docker。然而,Docker 赢得了最大的市场份额,这导致了在 Docker 和 Kubernetes 之间完善集成的许多努力,超过了任何其他容器化技术。
Similarly, Docker Inc., the company behind Docker, offers their own container orchestration engine, named Docker Swarm. But even they realized the fact that Kubernetes has risen to the point that even Docker for Desktop (MacOS and Windows) comes with its own Kubernetes distribution.
中文翻译
同样地,Docker Inc.,即 Docker 背后的公司,提供了他们自己的容器编排引擎,名为 Docker Swarm。但即使他们也意识到 Kubernetes 已经崭露头角,以至于即使是 Docker for Desktop(适用于 MacOS 和 Windows)也附带了自己的 Kubernetes 发行版。
If anyone was nervous about adopting Kubernetes for their Docker-based product, that last point would get rid of all of the doubts. Both projects have wholeheartedly embraced each other and have benefited tremendously from this symbiosis.
中文翻译
如果有人对于在其基于 Docker 的产品中采用 Kubernetes 感到紧张,那么最后一点将消除所有疑虑。这两个项目都全力拥抱了彼此,并从这种共生关系中获得了巨大的好处。
These projects are more than technologies, they are a community of people, who, despite their differences, are is composed of some of the brightest minds in the industry. When like-minded individuals collaborate, they exchange bright ideas and learn best practices from one another.
These are some of such ideas that both, Kubernetes and Docker, share:
中文翻译
这些项目不仅仅是技术,它们是一群人的社区,尽管他们之间存在差异,但组成这些社区的人才是该行业中最杰出的一些人。当志同道合的个体合作时,他们交流睿智的思想,并从彼此那里学习最佳实践。
以下是该段话中的关键单词的中文意思:
Their love for microservice based architecture (more on this later). Their love for open source community. Both are largely open source projects. They are largely written in Go which allows them to be shipped as small lightweight binaries. They use human-readable YAML files to specify application stacks and their deployments. In theory, you can learn about one without having a clue about the other. But keep in mind that in practice you will benefit a lot more if you start with the simple case of Docker running on a single machine, and then gradually understand how Kubernetes comes into play.
中文翻译
他们对微服务架构的热爱(稍后会详细介绍)。 他们对开源社区的热爱。它们都是大规模的开源项目。 它们主要是用 Go 语言编写的,这使它们能够作为小型轻量级二进制文件进行发布。 它们使用人类可读的 YAML 文件来指定应用程序堆栈及其部署。 从理论上讲,您可以了解其中一个而对另一个一无所知。但请记住,在实践中,如果您从单台机器上运行 Docker 的简单情况开始,然后逐渐了解 Kubernetes 如何运作,您将受益良多。
Containers are amazing! They allow us to think about services and systems in a completely new and digital way. Both Docker and Kubernetes are here to stay. They are continuously changing to transform themselves into something better in the future. Keep your company involved in the Technology era and implement the containers that your infrastructure needs the most.
中文翻译
容器是令人惊奇的!它们使我们能够以全新的数字方式思考服务和系统。Docker 和 Kubernetes 都将继续存在。它们正在不断变化,以将自己转变为未来更好的东西。让您的公司参与科技时代,并实施您的基础设施最需要的容器。
Designing newer software for a container-centric platform would not only make your apps more scalable but also more future-proof. Sticking to the old VMs might work for now, but a few years down the line you will eventually have to either bear the heavy cost of migrating everything into containers or abandon your projects altogether. Hopefully, now if someone brings up the topic of “Kubernetes vs Docker” you won’t get swept away by jargons.
中文翻译
为容器为中心的平台设计新的软件不仅会使您的应用程序更具可扩展性,而且更具未来可塑性。坚持使用旧的虚拟机可能暂时有效,但几年后,您最终将不得不承担将所有内容迁移到容器中的巨大成本,或者完全放弃您的项目。希望现在如果有人提出“Kubernetes vs Docker”的话题,您不会被术语所迷惑。
Visit the Original source for better insight: Kubernetes vs. Docker
本文作者:yowayimono
本文链接:
版权声明:本博客所有文章除特别声明外,均采用 BY-NC-SA 许可协议。转载请注明出处!