Kubernetes部署 [英] Kubernetes Deployments

问题描述

在致力于创建一个使用Kubernetes进行微服务部署的平台时，我们希望对Kubernetes部署对象具有依赖性.但是，我们看到了文档 http://kubernetes.io/v1.1 /docs/user-guide/deployments.html 表示以下内容:请注意，部署对象实际上具有API版本v1alpha1.Alpha对象可能会更改，甚至在将来的软件版本中也会停止使用" 我想知道我们是否应该继续使用Deployment概念来进行部署，本质上是滚动更新还是因为它可能会中断或更改，所以我们是否应该自己重新实现相同的概念，例如创建带有新标签的rc，使用以下方法创建新的容器然后分别使用旧标签和新标签的不同标签，通过从旧标签上缓慢移除吊舱并将新吊舱缓慢添加到新包装中来按比例缩小旧包装. 部署的计划或提议的变更是什么，或者该概念正在消失以寻求更好的概念? 我也想知道为什么OpenShift不使用Deployment对象，那时它还没有准备好吗?

While working on creating a platform that will do microservice deployments using Kubernetes, we want to take a Dependency on the Kubernetes Deployment Object. However, we saw the documentation http://kubernetes.io/v1.1/docs/user-guide/deployments.html says the following "Note that Deployment objects effectively have API version v1alpha1. Alpha objects may change or even be discontinued in future software releases" I am wondering if we should go about using the Deployment concept to do our deployments, essentially rolling updates or since it could be discontinued or change, should we just reimplement the same concepts ourselves like , creating a rc with new labels, create new pods with different labels then both old rc and new rc, scale down the old rc by slowly removing pods from the old rc and slowly adding new pods into the new rc. What is the plan or proposed changes for Deployment or that concept is going away for a better concept ? Also i am wondering why OpenShift did not use the Deployment object, was it not ready at that time ?

推荐答案

到目前为止，部署概念已移至"v1beta1".该概念很可能会继续，因为它是一种声明性方法(与使用较早的复制控制器的命令性方法等).

As of now, the Deployment concept has been moved to "v1beta1". The concept will most probably be continued, because it is a declarative approach (vs. the imperative approach with the older replication controller etc.).

无法透露任何有关OpenShift的信息，但是在GKE上，它对我来说效果很好！

Can't tell anything about OpenShift but on GKE it works for me pretty well!

这篇关于Kubernetes部署的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！