infrastructure: compute, storage, network. This allows cloud providers to have independent feature and patch release cycles, learn how SIG VMware is working to meet this new model on VMware platforms. Agenda 4 (bi-weekly). ● Meeting notes and agenda. ● Meeting recordings. vSphere Cloud Provider vSphere syncup: Wednesdays at 9:00am pacific (monthly, first Wednesday of the month) ● Meeting notes and agenda. ● Meeting recordings. Cluster API Provider vSphere syncup: Mondays at 1:00pm pacific (bi-weekly) ● Meeting notes and agenda. ● Meeting recordings. Github 11 Sessions you should attend this week! Today • 3:40pm

templates │ ├── deployment.yaml │ ├── _helpers.tpl │ ├── hpa.yaml │ ├── ingress.yaml │ ├── NOTES.txt │ ├── serviceaccount.yaml │ ├── service.yaml │ └── tests │ └── test-connec�on 适配的k8s版本 release-0.8 1.20 1.21 release-0.9 1.21 1.22 release-0.10 1.22 1.23 release-0.11 1.23 1.24 release-0.12 1.24 1.25 release-0.13 13 1.26 1.27 1.28 本小节以k8s v1.23版本为例，部署release-0.10版本的prometheus，先下载部署 清单文件到服务器上 # tar -xf kube-prometheus-0.10.0.tar.gz # cd kube-prometheus-0.10.0/manifests # grep -i 'image:' *

18:00 UTC (bi-weekly). ● Meeting notes and agenda. ● Meeting recordings. vSphere Cloud Provider vSphere syncup: Wednesdays at 16:00 UTC (monthly) ● Meeting notes and agenda. ● Meeting recordings. Cluster API Provider vSphere syncup: Wednesdays at 18:00 UTC (bi-weekly) ● Meeting notes and agenda. ● Meeting recordings. Github

kind: ConfigMap metadata: name: {{ include "openservice.fullname" . }}-cfg namespace: {{ .Release.Namespace }} labels: app.kubernetes.io/name: {{ include "openservice.name" . }} helm include "openservice.chart" . }} app.kubernetes.io/instance: {{ .Release.Name }} app.kubernetes.io/managed-by: {{ .Release.Service }} data: config.ini: | [Common] Mode = product kind: StatefulSet metadata: name: {{ include "openservice.fullname" . }} namespace: {{ .Release.Namespace }} labels: app.kubernetes.io/name: {{ include "openservice.name" . }} helm

their respective release branch, release-X.Y. • Official releases (vX.Y.Z): cut from their respective release branch, release-X.Y. • Emergency releases (vX.Y.Z): cut from a new release-X.Y.Z branch branch based on a tag Release Schedule Release1.13 Branch Supported releases 1.10 1.11 1.12 1.13 Agenda 1. The community 2. How to contribute 3. Versioning 4. The easy way to use it 5. Demo 6

com/developer/column/2436 Introduction Challenges with Kubernetes Ø How to provide a fast & reliable way to release stateful service Ø Advanced scheduling to improve service stability Ø Quota management to optimize CLB-Service/Ingress-Controller Efficient and reliable container release Ø Why not RollingUpdate ? Ø What are the advantages of batch gray release ? • more reliable and better control • More flexible • Updating Pod Updated Pod OK StatefulSetPlus StatefulSetPlus Batch Gray Release Key Features: Ø Manual/Auto Batch Gray Release Ø Multi-Batch Rollback Ø Multi-Batch InPlaceUpdate Ø Support HPA, CronHPA

CAICLOUD/RUDDER • 2 CRDs - Release, Release History • 1 控制器器 - Rudder aka Release Controller • 开源 • https://github.com/caicloud/rudder • https://github.com/caicloud/canary-release • https://github.com/caicloud/charts

Manager - Helm Tiller Helm Tiller 1. 负责将 Chart 部署到指定的集群当中，并管理生成的 Release（应用） 2. 支持对 Release 的 更新，删除，回滚 操作 3. 支持对 Release 的资源进行增量更新 4. Release 的状态管理 5. Kubernetes 下属子项目（https://github.com/kubernetes/helm）

【可选】关闭防⽕墙 systemctl stop firewalld 在ansible-client机器上安装ansible 安装ansible ~]# sudo yum install epel-release ~]# sudo yum install ansible 安装jinja2 ~]# easy_install pip ~]# pip2 install jinja2 --upgrade 在ansible-client机器上安装kubespray 下载kubespray TIPS：本⽂下载的是master分⽀，如果⼤家要部署到线上环境，建议下载RELEASE分⽀。笔者撰写本⽂ 时，最新的RELEASE是2.6.0，RELEASE版本下载地址：https://github.com/kubernetes- incubator/kubespray/releases） ~]# git clone 及控制对终极API/实验API的访问。JSON和Protobuf序列化schema遵循相同的schema更改准则——以下所有描述都涵 盖了两种格式。 请注意，API版本控制和软件版本控制仅仅是间接相关的关系。 API and release versioning proposa（API和版本发布 提案）l 描述了API版本控制和软件版本控制之间的关系。 不同的API版本意味着不同程度的稳定性和⽀持。API Changes documentation

Jobs A Pod which runs until the process returns a successful termination Deployments Manages the release rollout of new versions of Pods Singletons A single instance of a Pod which is not replicated or Harbor • Manages Cluster Day 2 - Scaling - Patching - Upgrades - Failures Kubernetes (As a Bosh Release) BOSH (Deploys/Manages VMs) CPI CNI Harbor Private Container Registry Worker Worker Worker Service (PKS) Private and Public Cloud Public Cloud (on GCP) Certified for every K8s release Container Service for Cloud-Native Apps Rapidly deliver and operationalize next generation apps