ZH-trans: add 2015-05-00-Weekly-Kubernetes-Community-Hangout.md (#13148)
This commit is contained in:
committed by
Kubernetes Prow Robot
parent
32a140ef7a
commit
3d086ad092
@@ -0,0 +1,121 @@
|
||||
---
|
||||
title: " Kubernetes 社区每周聚会笔记- 2015年5月1日 "
|
||||
date: 2015-05-11
|
||||
slug: weekly-kubernetes-community-hangout
|
||||
url: /blog/2015/05/Weekly-Kubernetes-Community-Hangout
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: " Weekly Kubernetes Community Hangout Notes - May 1 2015 "
|
||||
date: 2015-05-11
|
||||
slug: weekly-kubernetes-community-hangout
|
||||
url: /blog/2015/05/Weekly-Kubernetes-Community-Hangout
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Every week the Kubernetes contributing community meet virtually over Google Hangouts. We want anyone who's interested to know what's discussed in this forum.
|
||||
-->
|
||||
每个星期,Kubernetes 贡献者社区几乎都会在谷歌 Hangouts 上聚会。我们希望任何对此感兴趣的人都能了解这个论坛的讨论内容。
|
||||
|
||||
<!--
|
||||
|
||||
* Simple rolling update - Brendan
|
||||
|
||||
* Rolling update = nice example of why RCs and Pods are good.
|
||||
|
||||
* ...pause… (Brendan needs demo recovery tips from Kelsey)
|
||||
|
||||
* Rolling update has recovery: Cancel update and restart, update continues from where it stopped.
|
||||
|
||||
* New controller gets name of old controller, so appearance is pure update.
|
||||
|
||||
* Can also name versions in update (won't do rename at the end).
|
||||
|
||||
-->
|
||||
|
||||
* 简单的滚动更新 - Brendan
|
||||
|
||||
* 滚动更新 = RCs和Pods很好的例子。
|
||||
|
||||
* ...pause… (Brendan 需要 Kelsey 的演示恢复技巧)
|
||||
|
||||
* 滚动更新具有恢复功能:取消更新并重新启动,更新从停止的地方继续。
|
||||
|
||||
* 新控制器获取旧控制器的名称,因此外观是纯粹的更新。
|
||||
|
||||
* 还可以在 update 中命名版本(最后不会重命名)。
|
||||
|
||||
<!--
|
||||
|
||||
* Rocket demo - CoreOS folks
|
||||
|
||||
* 2 major differences between rocket & docker: Rocket is daemonless & pod-centric.
|
||||
|
||||
* Rocket has AppContainer format as native, but also supports docker image format.
|
||||
|
||||
* Can run AppContainer and docker containers in same pod.
|
||||
|
||||
* Changes are close to merged.
|
||||
|
||||
-->
|
||||
|
||||
* Rocket 演示 - CoreOS 的伙计们
|
||||
|
||||
* Rocket 和 docker 之间的主要区别: Rocket 是无守护进程和以 pod 为中心。。
|
||||
|
||||
* Rocket 具有原生的 AppContainer 格式,但也支持 docker 镜像格式。
|
||||
|
||||
* 可以在同一个 pod 中运行 AppContainer 和 docker 容器。
|
||||
|
||||
* 变更接近于合并。
|
||||
|
||||
<!--
|
||||
|
||||
* demo service accounts and secrets being added to pods - Jordan
|
||||
|
||||
* Problem: It's hard to get a token to talk to the API.
|
||||
|
||||
* New API object: "ServiceAccount"
|
||||
|
||||
* ServiceAccount is namespaced, controller makes sure that at least 1 default service account exists in a namespace.
|
||||
|
||||
* Typed secret "ServiceAccountToken", controller makes sure there is at least 1 default token.
|
||||
|
||||
* DEMO
|
||||
|
||||
* * Can create new service account with ServiceAccountToken. Controller will create token for it.
|
||||
|
||||
* Can create a pod with service account, pods will have service account secret mounted at /var/run/secrets/kubernetes.io/…
|
||||
|
||||
-->
|
||||
|
||||
* 演示 service accounts 和 secrets 被添加到 pod - Jordan
|
||||
|
||||
* 问题:很难获得与API通信的令牌。
|
||||
|
||||
* 新的API对象:"ServiceAccount"
|
||||
|
||||
* ServiceAccount 是命名空间,控制器确保命名空间中至少存在一个个默认 service account。
|
||||
|
||||
* 键入 "ServiceAccountToken",控制器确保至少有一个默认令牌。
|
||||
|
||||
* 演示
|
||||
|
||||
* * 可以使用 ServiceAccountToken 创建新的 service account。控制器将为它创建令牌。
|
||||
|
||||
* 可以创建一个带有 service account 的 pod, pod 将在 /var/run/secrets/kubernets.io/…
|
||||
|
||||
<!--
|
||||
|
||||
* Kubelet running in a container - Paul
|
||||
|
||||
* Kubelet successfully ran pod w/ mounted secret.
|
||||
|
||||
-->
|
||||
|
||||
* Kubelet 在容器中运行 - Paul
|
||||
|
||||
* Kubelet 成功地运行了带有 secret 的 pod。
|
||||
|
||||
Reference in New Issue
Block a user