mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
commit
1b425f862c
@ -1,67 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (5 reasons to use Kubernetes)
|
||||
[#]: via: (https://opensource.com/article/19/6/reasons-kubernetes)
|
||||
[#]: author: (Daniel Oh https://opensource.com/users/daniel-oh)
|
||||
|
||||
5 reasons to use Kubernetes
|
||||
======
|
||||
Kubernetes solves some of the most common problems development and
|
||||
operations teams see every day.
|
||||
![][1]
|
||||
|
||||
[Kubernetes][2] is the de facto open source container orchestration tool for enterprises. It provides application deployment, scaling, container management, and other capabilities, and it enables enterprises to optimize hardware resource utilization and increase production uptime through fault-tolerant functionality at speed. The project was initially developed by Google, which donated the project to the [Cloud-Native Computing Foundation][3]. In 2018, it became the first CNCF project to [graduate][4].
|
||||
|
||||
This is all well and good, but it doesn't explain why development and operations should invest their valuable time and effort in Kubernetes. The reason Kubernetes is so useful is that it helps dev and ops quickly solve the problems they struggle with every day.
|
||||
|
||||
Following are five ways Kubernetes' capabilities help dev and ops professionals address their most common problems.
|
||||
|
||||
### 1\. Vendor-agnostic
|
||||
|
||||
Many public cloud providers not only serve managed Kubernetes services but also lots of cloud products built on top of those services for on-premises application container orchestration. Being vendor-agnostic enables operators to design, build, and manage multi-cloud and hybrid cloud platforms easily and safely without risk of vendor lock-in. Kubernetes also eliminates the ops team's worries about a complex multi/hybrid cloud strategy.
|
||||
|
||||
### 2\. Service discovery
|
||||
|
||||
To develop microservices applications, Java developers must control service availability (in terms of whether the application is ready to serve a function) and ensure the service continues living, without any exceptions, in response to the client's requests. Kubernetes' [service discovery feature][5] means developers don't have to manage these things on their own anymore.
|
||||
|
||||
### 3\. Invocation
|
||||
|
||||
How would your DevOps initiative deploy polyglot, cloud-native apps over thousands of virtual machines? Ideally, dev and ops could trigger deployments for bug fixes, function enhancements, new features, and security patches. Kubernetes' [deployment feature][6] automates this daily work. More importantly, it enables advanced deployment strategies, such as [blue-green and canary][7] deployments.
|
||||
|
||||
### 4\. Elasticity
|
||||
|
||||
Autoscaling is the key capability needed to handle massive workloads in cloud environments. By building a container platform, you can increase system reliability for end users. [Kubernetes Horizontal Pod Autoscaler][8] (HPA) allows a cluster to increase or decrease the number of applications (or Pods) to deal with peak traffic or performance spikes, reducing concerns about unexpected system outages.
|
||||
|
||||
### 5\. Resilience
|
||||
|
||||
In a modern application architecture, failure-handling codes should be considered to control unexpected errors and recover from them quickly. But it takes a lot of time and effort for developers to simulate all the occasional errors. Kubernetes' [ReplicaSet][9] helps developers solve this problem by ensuring a specified number of Pods are kept alive continuously.
|
||||
|
||||
### Conclusion
|
||||
|
||||
Kubernetes enables enterprises to solve common dev and ops problems easily, quickly, and safely. It also provides other benefits, such as building a seamless multi/hybrid cloud strategy, saving infrastructure costs, and speeding time to market.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/6/reasons-kubernetes
|
||||
|
||||
作者:[Daniel Oh][a]
|
||||
选题:[lujun9972][b]
|
||||
译者:[译者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/daniel-oh
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/ship_wheel_gear_devops_kubernetes.png?itok=xm4a74Kv
|
||||
[2]: https://opensource.com/resources/what-is-kubernetes
|
||||
[3]: https://www.cncf.io/projects/
|
||||
[4]: https://www.cncf.io/blog/2018/03/06/kubernetes-first-cncf-project-graduate/
|
||||
[5]: https://kubernetes.io/docs/concepts/services-networking/service/
|
||||
[6]: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/
|
||||
[7]: https://opensource.com/article/17/5/colorful-deployments
|
||||
[8]: https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
|
||||
[9]: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
|
66
translated/tech/20190607 5 reasons to use Kubernetes.md
Normal file
66
translated/tech/20190607 5 reasons to use Kubernetes.md
Normal file
@ -0,0 +1,66 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (5 reasons to use Kubernetes)
|
||||
[#]: via: (https://opensource.com/article/19/6/reasons-kubernetes)
|
||||
[#]: author: (Daniel Oh https://opensource.com/users/daniel-oh)
|
||||
|
||||
使用 Kubernetes 的 5 个理由
|
||||
======
|
||||
Kubernetes 解决了一些开发和运维团队每天关注的的常见问题。
|
||||
![][1]
|
||||
|
||||
[Kubernetes][2] 是企业事实上的开源容器编排工具。它提供了应用部署、扩展、容器管理和其他功能,使企业能够通过容错能力快速优化硬件资源利用率并延长生产环境运行时间。该项目最初由谷歌开发,并将该项目捐赠给[云原生计算基金会][3]。2018年,它成为第一个从 CNCF [毕业][4]的项目。
|
||||
|
||||
这一切都很好,但它并不能解释为什么开发和运维应该在 Kubernetes 上投入宝贵的时间和精力。Kubernetes 之所以如此有用,是因为它有助于开发者和运维人员迅速解决他们每天都在努力解决的问题。
|
||||
|
||||
以下是 Kubernetes 帮助开发者和运维人员解决他们最常见问题的五种能力。
|
||||
|
||||
### 1\. 厂商无关
|
||||
|
||||
许多公有云提供商不仅提供托管 Kubernetes 服务,还提供许多基于这些服务构建的云产品,来用于本地应用容器编排。由于与供应商无关,使运营商能够轻松、安全地设计、构建和管理多云和混合云平台,而不会有供应商锁定的风险。Kubernetes 还消除了运维团队对复杂的多云/混合云战略的担忧。
|
||||
|
||||
### 2\. 服务发现
|
||||
|
||||
为了开发微服务应用,Java 开发人员必须控制服务可用性(就应用是否可以提供服务而言),并确保服务持续存在,而没有任何例外,以响应客户端的请求。Kubernetes 的[服务发现功能][5]意味着开发人员不再需要自己管理这些东西。
|
||||
|
||||
### 3\. 触发
|
||||
|
||||
你的 DevOps 会如何在上千台虚拟机上部署多语言、云原生应用?理想情况下啊,开发和运维会在 bug 修复、功能增强、新功能、安全更新时触发部署。Kubernetes 的[部署功能][6]会自动化这个每日工作。更重要的时,它支持高级部署策略,例如[蓝绿部署和金丝雀部署][7]。
|
||||
|
||||
### 4\. 可伸缩性
|
||||
|
||||
自动扩展是处理云环境中大量工作负载所需的关键功能。通过构建容器平台,你可以为终端用户提高系统可靠性。[Kubernetes Horizontal Pod Autoscaler][8](HPA)允许一个集群增加或减少应用程序(或 Pod)的数量,以应对峰值流量或性能峰值,从而减少对意外系统中断的担忧。
|
||||
|
||||
### 5\. 容错性
|
||||
|
||||
在现代应用体系结构中,应考虑故障处理代码来控制意外错误并快速从中恢复。但是开发人员需要花费大量的时间和精力来模拟偶然的错误。Kubernetes 的 [ReplicaSet][9] 通过确保指定数量的 Pod 持续保持活动来帮助开发人员解决此问题。
|
||||
|
||||
### 结论
|
||||
|
||||
Kubernetes 使企业能够轻松、快速、安全地解决常见的开发和运维问题。它还提供其他好处,例如构建无缝的多云/混合云战略,节省基础架构成本以及加快产品上市时间。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/6/reasons-kubernetes
|
||||
|
||||
作者:[Daniel Oh][a]
|
||||
选题:[lujun9972][b]
|
||||
译者:[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/daniel-oh
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/ship_wheel_gear_devops_kubernetes.png?itok=xm4a74Kv
|
||||
[2]: https://opensource.com/resources/what-is-kubernetes
|
||||
[3]: https://www.cncf.io/projects/
|
||||
[4]: https://www.cncf.io/blog/2018/03/06/kubernetes-first-cncf-project-graduate/
|
||||
[5]: https://kubernetes.io/docs/concepts/services-networking/service/
|
||||
[6]: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/
|
||||
[7]: https://opensource.com/article/17/5/colorful-deployments
|
||||
[8]: https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
|
||||
[9]: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
|
Loading…
Reference in New Issue
Block a user