Kubernetes v1.4.0-alpha.3發布,Google云平臺的開源容器集群管理系統

jopen 8年前發布 | 10K 次閱讀 Google 云平臺 Kubernetes

Kubernetes是Google開源的容器集群管理系統,其提供應用部署、維護、 擴展機制等功能。利用Kubernetes能方便地管理跨機器運行容器化的應用。

如果你曾經用過Docker容器技術部署容器,那么可以將Docker看成Kubernetes內部使用的低級別組件。Kubernetes不僅僅支持Docker,還支持Rocket,這是另一種容器技術。

使用Kubernetes可以:

  • 自動化容器的部署和復制
  • 隨時擴展或收縮容器規模
  • 將容器組織成組,并且提供容器間的負載均衡
  • 很容易地升級應用程序容器的新版本
  • 提供容器彈性,如果容器失效就替換它,等等...

更新日志

Moved init-container feature from alpha to beta. (#31026@erictune)

  • Security Action Required:
  • This only applies to you if you use the PodSecurityPolicy feature. You are using that feature if kubectl get podsecuritypolicy returns one or more objects. If it returns an error, you are not using it.
  • If there are any pods with the key pods.beta.kubernetes.io/init-containers, then that pod may not have been filtered by the PodSecurityPolicy. You should find such pods and either delete them or audit them to ensure they do not use features that you intend to be blocked by PodSecurityPolicy.
  • Explanation of Feature
  • In 1.3, an init container is specified with this annotation key
  • on the pod or pod template: pods.alpha.kubernetes.io/init-containers.
  • In 1.4, either that key or this key: pods.beta.kubernetes.io/init-containers,
  • can be used.
  • When you GET an object, you will see both annotation keys with the same values.
  • You can safely roll back from 1.4 to 1.3, and things with init-containers
  • will still work (pods, deployments, etc).
  • If you are running 1.3, only use the alpha annotation, or it may be lost when
  • rolling forward.
  • The status has moved from annotation key
  • 更多日志見:CHANGELOG

下載

本站原創,轉載時保留以下信息:
本文轉自:深度開源(open-open.com)
原文地址:http://www.baiduhome.net/news/view/35c28224

 

 本文由用戶 jopen 自行上傳分享,僅供網友學習交流。所有權歸原作者,若您的權利被侵害,請聯系管理員。
 轉載本站原創文章,請注明出處,并保留原始鏈接、圖片水印。
 本站是一個以用戶分享為主的開源技術平臺,歡迎各類分享!