"canary" "environment" : "dev" , "environment" : "qa" , "environment" : "production" "tier" : "frontend" , "tier" : "backend" , "tier" : "cache" "partition" : "customerA" , "partition" : "customerB" production tier != frontend 前者选择所有与key = environment 并且value = production 的资源。后者选择key = tier 并且value不等 于 frontend ，以及key不等于 tier 的所有资源。可使⽤ , 过滤是⽣产环境中（ production ）⾮前端（ frontend ）的资源： environment=production n,tier!=frontend 。 Set-based requirement Set-based label requirement允许根据⼀组Value过滤Key。⽀持三种运算符： in 、 notin 和 exists （只有Key标识 符）。 例如： environment in (production, qa) tier notin (frontend, backend)

Component Deployment Function apiVersion: core.oam.dev/v1alpha2 kind: Component metadata: name: frontend annotations: description: Container workload spec: workload: apiVersion: apps/v1 kind: Deployment protocol: TCP $ kubectl get deployment NAME REVISION AGE frontend-c8bb659c5 1 2d15h $ kubectl get components NAME WORKLOAD frontend deployment.apps.k8s.io Component：应用中的一个组成部分，例如容器、 Function或者云服务等 Function或者云服务等 应用组件 运维能力 扩容策略 发布策略 分批策略 访问控制 流量配置 Deployment Function - componentName: frontend traits: - trait: apiVersion: autoscaling/v2beta2 kind: HorizontalPodAutoscaler spec: minReplicas:

nodePort: 30080 # 设置映射端⼝为 30080 14 selector: 15 app: wordpress 16 tier: frontend 17 --- 18 apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2 19 kind: Deployment wordpress 29 tier: frontend 30 strategy: 31 type: Recreate 32 template: 33 metadata: 34 labels: 35 app: wordpress 36 tier: frontend 37 spec: 38 targetPort: 80 12 selector: 3. 部署WordPress容器组 89 13 app: wordpress 14 tier: frontend 15 --- 16 apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2 17 kind: Deployment

2015- Now 2010- Now 2012- Now Bare metals Way to Kubernetes Search Grid Hadoop PoP Database Frontend VM Kubernetes plays magic api etcd kind: metadata: spec: control loop control loop control

kind: ApplicationConfiguration metadata: name: my-awesome-app spec: components: - componentName: frontend instanceName: web-front-end traits: - name: Ingress properties: - name: path value: "/" applicationScopes:

simplified ● Simply cluster life cycle management ○ E.g. updates ● Upstream improvements in Kubernetes directly translate to improvements in managing Kubernetes Simplify Node Bootstrap On-host requirements

master结点的6443/tcp端口即可。 高可用集群拓扑图： ★先配置HA高可用的反向代理 本例中vip为10.99.1.54（三台master ip为10.99.1.51~53）使用haproxy做反向代理 frontend k8s_api_tcp_6443 bind *:6443 mode tcp default_backend my_k8s_cluster_6443 backend