mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
translated
This commit is contained in:
geekpi
parent
4d3e457b6f
commit
92077ca4dd
@ -1,72 +0,0 @@
|
||||
translating---geekpi
|
||||
|
||||
Kubernetes: Why does it matter?
|
||||
============================================================
|
||||
|
||||
### The Kubernetes platform for running containerized workloads takes on some of the heavy lifting when developing and deploying cloud-native applications.
|
||||
|
||||
|
||||
|
||||
>Image by : opensource.com
|
||||
|
||||
Developing and deploying cloud-native applications has become very popular—for very good reasons. There are clear advantages to a process that allows rapid deployment and continuous delivery of bug fixes and new features, but there's a chicken-and-egg problem no one talks about: How do you get there from here? Building the infrastructure and developing processes to develop and maintain cloud-native applications—all from scratch—are non-trivial, time-intensive tasks.
|
||||
|
||||
[Kubernetes][3], a relatively new platform for running containerized workloads, addresses these problems. Originally an internal project within Google, Kubernetes was donated to the [Cloud Native Computing Foundation][4] in 2015 and has attracted developers from the open source community around the world. Kubernetes' design is based on 15 years of experience in running both production and development workloads. Since it is open source, anyone can download and use it and realize its benefits.
|
||||
|
||||
So why is such a big fuss being made over Kubernetes? I believe that it hits a sweet spot between an Infrastructure as a Service (IaaS) solution, like OpenStack, and a full Platform as a Service (PaaS) resource where the lower-level runtime implementation is completely controlled by a vendor. Kubernetes provides the benefits of both worlds: abstractions to manage infrastructure, as well as tools and features to drill down to bare metal for troubleshooting.
|
||||
|
||||
### IaaS vs. PaaS
|
||||
|
||||
OpenStack is classified by most people as an IaaS solution, where pools of physical resources, such as processors, networking, and storage, are allocated and shared among different users. Isolation between users is implemented using traditional, hardware-based virtualization.
|
||||
|
||||
OpenStack's REST API allows infrastructure to be created automatically using code, but therein lies the problem. The output of the IaaS product is yet more infrastructure. There's not much in the way of services to support and manage the extra infrastructure once it has been created. After a certain point, it becomes a lot of work to manage the low-level infrastructure, such as servers and IP addresses, produced by OpenStack. One well-known outcome is virtual machine (VM) sprawl, but the same concept applies to networks, cryptographic keys, and storage volumes. This leaves less time for developers to work on building and maintaining an application.
|
||||
|
||||
Like other cluster-based solutions, Kubernetes operates at the individual server level to implement horizontal scaling. New servers can be added easily and workloads scheduled on the hardware immediately. Similarly, servers can be removed from the cluster when they're not being utilized effectively or when maintenance is needed. Orchestration activities, such as job scheduling, health monitoring, and maintaining high availability, are other tasks automatically handled by Kubernetes.
|
||||
|
||||
Networking is another area that can be difficult to reliably orchestrate in an IaaS environment. Communication of IP addresses between services to link microservices can be particularly tricky. Kubernetes implements IP address management, load balancing, service discovery, and DNS name registration to provide a headache-free, transparent networking environment within the cluster.
|
||||
|
||||
### Designed for deployment
|
||||
|
||||
Once you have created the environment to run your application, there is the small matter of deploying it. Reliably deploying an application is one of those tasks that's easily said, but not easily done—not in the slightest. The huge advantage that Kubernetes has over other environments is that deployment is a first-class citizen.
|
||||
|
||||
There is a single command, using the Kubernetes command-line interface (CLI), that takes a description of the application and installs it on the cluster. Kubernetes implements the entire application lifecycle from initial deployment, rolling out new releases as well as rolling them back—a critical feature when things go wrong. In-progress deployments can also be paused and resumed. The advantage of having existing, built-in tools and support for application deployment, rather than building a deployment system yourself, cannot be overstated. Kubernetes users do not have to reinvent the application deployment wheel nor discover what a difficult task it is.
|
||||
|
||||
Kubernetes also has the facility to monitor the status of an in-progress deployment. While you can write this in an IaaS environment, like the deployment process itself, it's a surprisingly difficult task where corner cases abound.
|
||||
|
||||
### Designed for DevOps
|
||||
|
||||
As you gain more experience in developing and deploying applications for Kubernetes, you will be traveling the same path that Google and others have before you. You'll discover there are several Kubernetes features that are essential to effectively developing and troubleshooting a multi-service application.
|
||||
|
||||
First, Kubernetes' ability to easily examine the logs or SSH (secure shell) into a running service is vitally important. With a single command line invocation, an administrator can examine the logs of a service running under Kubernetes. This may sound like a simple task, but in an IaaS environment it's not easy unless you have already put some work into it. Large applications often have hardware and personnel dedicated just for log collection and analysis. Logging in Kubernetes may not replace a full-featured logging and metrics solution, but it provides enough to enable basic troubleshooting.
|
||||
|
||||
Second, Kubernetes offers built-in secret management. Another hitch known by teams who have developed their own deployment systems from scratch is that deploying sensitive data, such as passwords and API tokens, securely to VMs is hard. By making secrets first-class citizens, Kubernetes stops your team from inventing its own insecure, buggy secret-distribution system or just hardcoding credentials in deployment scripts.
|
||||
|
||||
Finally, there is a slew of features in Kubernetes for automatically scaling, load-balancing, and restarting your application. Again, these features are tempting targets for developers to write when using IaaS or bare metal. Scaling and health checks for your Kubernetes application are declared in the service definition, and Kubernetes ensures that the correct number of instances is running and healthy.
|
||||
|
||||
### Conclusion
|
||||
|
||||
The differences between IaaS and PaaS systems are enormous, including that PaaS can save a vast amount of development and debugging time. As a PaaS, Kubernetes implements a potent and effective set of features to help you develop, deploy, and debug cloud-native applications. Its architecture and design represent decades of hard-won experience that can your team can take advantage of—for free.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
作者简介：
|
||||
|
||||
Tim Potter - Tim is a senior software engineer working at Hewlett Packard Enterprise. He has been a contributor to free and open source software for nearly two decades working on a variety of projects including Samba, Wireshark, OpenPegasus, and Docker. Tim blogs at https://elegantinfrastructure.com/ about Docker, Kubernetes and other infrastructure-related topics.
|
||||
|
||||
-----
|
||||
|
||||
|
||||
via: https://opensource.com/article/17/6/introducing-kubernetes
|
||||
|
||||
作者：[ Tim Potter][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://opensource.com/users/tpot
|
||||
[1]:https://opensource.com/article/17/6/introducing-kubernetes?rate=RPoUoHXYQXbTb7DHQCDsHgR1ZcfLSoquZ8xVZzfMtxM
|
||||
[2]:https://opensource.com/user/63281/feed
|
||||
[3]:https://kubernetes.io/
|
||||
[4]:https://www.cncf.io/
|
||||
[5]:https://opensource.com/users/tpot
|
||||
70
translated/tech/20170629 Kubernetes Why does it matter.md
Normal file
70
translated/tech/20170629 Kubernetes Why does it matter.md
Normal file
@ -0,0 +1,70 @@
|
||||
Kubernetes：为什么这么重要？
|
||||
============================================================
|
||||
|
||||
### 运行容器化负载的 Kubernetes 平台在开发和部署云原生应用程序时将会承担一定作用。
|
||||
|
||||
|
||||
|
||||
>图片来源： opensource.com
|
||||
|
||||
由于非常好的原因，开发和部署云原生云应用程序已经变得非常受欢迎。对于一个允许快速部署和连续交付 bug 修复和新功能的过程来说，它有明显的优势，但是没有人会谈到鸡和鸡蛋问题：你从这里到达那里？构建基础设施和开发流程来开发和维护云原生应用程序（从头开始）是不简单的，耗时的任务。
|
||||
|
||||
[Kubernetes][3] 是一个相对较新的运行容器化负载的平台，它解决了这些问题。它原本是 Google 内部的一个项目，Kubernetes 在 2015 年被捐赠给了[云云原生计算基金会][4]，并吸引了来自世界各地开源社区的开发人员。 Kubernetes 的设计基于 15 年的运行生产和开发负载的经验。由于它是开源的，任何人都可以下载并使用它，并实现其优点。
|
||||
|
||||
那么为什么 Kubernetes 会有这么大的惊喜呢？我相信它在基础架构即服务 （IaaS），像 OpenStack 和完整的平台即服务 （PaaS）的资源之间达到了最佳平衡，它的底层运行时实现完全由供应商控制。Kubernetes 提供了两个优势：管理基础设施的抽象，以及深入裸机进行故障排除的工具和功能。
|
||||
|
||||
### IaaS 与 PaaS
|
||||
|
||||
OpenStack 被大多数人分类为 IaaS 解决方案，其中物理资源池（如处理器、网络和存储）在不同用户之间分配和共享。使用传统的基于硬件的虚拟化实现用户之间的隔离。
|
||||
|
||||
OpenStack 的 REST API 允许使用代码自动创建基础架构，但是这就是问题。IaaS 产品输出的是更多的基础设施。创建后，支持和管理额外基础设施的服务方式并不多。在一定程度上，OpenStack 生产的底层基础架构（如服务器和 IP 地址）成为管理工作的重中之重。一个众所周知的结果是虚拟机（VM）扩张，但是同样的概念适用于网络、加密密钥和存储卷。这样，开发人员可以减少建立和维护应用程序的时间。
|
||||
|
||||
像其他基于集群的解决方案一样，Kubernetes 以单个服务器级别运行，以实现水平缩放。它可以轻松添加新的服务器，并立即在硬件上安排负载。类似地，当服务器没有被有效利用或需要维护时，可以从集群中删除服务器。编排活动，如工作调度、健康监测和维护高可用性是 Kubernetes 自动处理的其他任务。
|
||||
|
||||
网络是另一个可能难以在 IaaS 环境中可靠编排的领域。微服务之间通过 IP 地址通信可能是很棘手的。Kubernetes 实现了 IP 地址管理、负载均衡、服务发现和 DNS 名称注册，以在集群内提供无痛、透明的网络环境。
|
||||
|
||||
### 专为部署而设计
|
||||
|
||||
一旦创建了运行应用程序的环境，部署就是一件小事了。可靠地部署一个应用程序是其中一个很容易说出来但并不容易做到的任务 - 它并不是最简单的。Kubernetes 相对其他环境的巨大优势是部署是一等公民。
|
||||
|
||||
有一个使用 Kubernetes 命令行界面 （CLI） 的命令，该接口描述应用程序并将其安装在群集上。Kubernetes 从初始部署实现了应用程序的整个生命周期，推出新版本以及回滚 - 当一个关键功能出现问题时。进行中的部署也可以暂停和恢复。拥有现有的、内置的工具和支持应用程序部署的优点，而不用自己构建部署系统，这一点是不容小觑的。Kubernetes 用户既不必重新发明应用程序部署的轮子，也不会发现这是一项艰巨的任务。
|
||||
|
||||
Kubernetes 还可以监控进行中的部署状态。虽然你可以在 IaaS 环境中编写这个，例如部署过程本身，但这是一个非常困难的任务，这样的情况还比比皆是。
|
||||
|
||||
### 专为 DevOps 而设计
|
||||
|
||||
随着你在开发和部署 Kubernetes 应用程序方面获得更多经验，你将沿着与 Google 和其他人相同的路径前行。你将发现有几种 Kubernetes 功能对于有效地开发和多服务程序的故障排除是非常重要的。
|
||||
|
||||
首先，Kubernetes 能够通过日志或 SSH（安全 shell）轻松检查正在运行的服务的能力非常重要。通过单一命令行调用，管理员可以检查在 Kubernetes 下运行的服务的日志。这可能听起来像一个简单的任务，但在 IaaS 环境中，除非你已经做了一些工作，否则这并不容易。大型应用程序通常具有专门用于日志收集和分析的硬件和人员。登录 Kubernetes 可能不能替代完整功能的日志和度量解决方案，但它足以提供基本的故障排除。
|
||||
|
||||
第二，Kubernetes 提供内置的秘密管理。从头开发自己的部署系统的团队知道的另一个问题是，将敏感数据（如密码和 API 令牌）安全地部署到虚拟机上很困难。通过将秘密变成一等公民，Kubernetes 阻止你的团队发明自己的不安全的方法、错误的秘密分发系统或在部署脚本中硬编码的凭据。
|
||||
|
||||
最后，Kubernetes 有一些功能用于自动缩放、负载均衡和重新启动应用程序。同样，这些功能是开发人员在使用 IaaS 或裸机时要编写的。你的 Kubernetes 应用程序的缩放和运行状况检查在服务定义中声明，而 Kubernetes 确保正确数量的实例健康运行。
|
||||
|
||||
### 总结
|
||||
|
||||
IaaS 和 PaaS 系统之间的差异是巨大的，包括 PaaS 可以节省大量的开发和调试时间。作为 PaaS，Kubernetes 实现了强大而有效的功能，可帮助你开发、部署和调试云原生应用程序。它的架构和设计代表了数十年的难得的经验，让你的团队能够免费获得好处。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
作者简介：
|
||||
|
||||
Tim Potter - Tim 是 Hewlett Packard Enterprise 的高级软件工程师。近二十年来，他一直致力于免费和开源软件的开发工作，其中包括 Samba、Wireshark、OpenPegasus 和 Docker 等多个项目。Tim博客在 https://elegantinfrastructure.com/ ，关于 Docker、Kubernetes 和其他基础设施相关主题。
|
||||
|
||||
-----
|
||||
|
||||
|
||||
via: https://opensource.com/article/17/6/introducing-kubernetes
|
||||
|
||||
作者：[ Tim Potter][a]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://opensource.com/users/tpot
|
||||
[1]:https://opensource.com/article/17/6/introducing-kubernetes?rate=RPoUoHXYQXbTb7DHQCDsHgR1ZcfLSoquZ8xVZzfMtxM
|
||||
[2]:https://opensource.com/user/63281/feed
|
||||
[3]:https://kubernetes.io/
|
||||
[4]:https://www.cncf.io/
|
||||
[5]:https://opensource.com/users/tpot
|
||||
Loading…
Reference in New Issue
Block a user