3.7发布时，相关的vxlan标准未规定使用哪个端口号，所以大多数厂商 使用8472/udp端口，后来IANA分配了4789/udp作为vxlan的目的端口 VTEP（Vxlan Tunnel End Point）vxlan隧道终端节点，实现vxlan报文的封装/解封 装 VxLAN头部： 8 bit 24 bit 24 bit 8 bit vxlan tag Reserved VNI Reserved ├── ingress.yaml │ ├── NOTES.txt │ ├── serviceaccount.yaml │ ├── service.yaml │ └── tests │ └── test-connec�on.yaml └── values.yaml # helm package --version 1.0.2 test-chart

$value }}" {{- end }} spec: accessModes: {{- range .Values.persistentVolume.accessModes }} - {{ . | quote }} {{- end }} resources: Values.persistentVolume.storageClass }}" {{- end }} {{- end }} {{- else }} - name: data emptyDir: {} {{- end }} vi influxdb2/templates/job-setup-admin.yaml Values.serviceAccount.annotations }} annotations: {{- toYaml . | nindent 4 }} {{- end }} {{- end }} Step4. templates/configmap.yaml vi openservice/templates/configmap.yaml apiVersion:

{{ Region }}.compute.internal {{ end }} vpcDHDCPOptionsAssociation/{{ ClusterName }}: vpc: vpc/{{ ClusterName }} dhcpOptions: dhcpOptions/{{ ClusterName }} {{ end }} # -------------------------- {{ ClusterName }} autoscalingGroup: autoscalingGroup/{{ $m.Name }}.masters.{{ ClusterName }} {{ end }} # --------------------------------------------------------------- # Zones (Availability Zones) {{ Region }}.compute.internal {{ end }} vpcDHDCPOptionsAssociation/{{ ClusterName }}: vpc: vpc/{{ ClusterName }} dhcpOptions: dhcpOptions/{{ ClusterName }} {{ end }} # --------------------------

What happened about the cluster 1 Is there something unexpected happened in the cluster 2 What end users did in the cluster How to locate failure 1 Which component is going wrong 2 Which component Failure caused by cluster itself RuntimeError, ImageFailed, Unscheduled, KubeletDelay... End Users Failure caused by end users ContainerCrashLoopBackOff, FailedPostStartHook, Unhealthy… Trace system Increase Detect the unhealthy machines timely and fix problems automatically。 The infrastructure Log Event End User Storage Analysis Platform Trace Report Weakness The trace system Data Collect: Collect Audit

容器云设计--多集群支持的容器云 • 多集群，一平台 Router1 Router2 K8S-2 K8S-1 Console Front End Console Back End Registry Dev/Ops/Admin End User Builder 12 Service Name K8S Cluster IP app01.xpaas.lenovo.com 172

Second row winner Final winner Tease before commercial break End of last show Time 1 week - 1 hour 8 min 15 min 15 min 20min End of show Participants API Requests Application architecture

TensorBoard instance • Autoscaling will create / remove VMs as needed to save cost Demo: Create End to End ML Pipelines with Argo Demo: Rapid prototyping with self-service Jupyter notebook from JupyterHub

Can be clustered across Master Nodes • Contains all state known about cluster • Kubernetes Front-end Control Plane • Provides RESTful interface • Returns state objects as JSON • Provides core control Container Service for Cloud-Native Apps Rapidly deliver and operationalize next generation apps End User Experience • Installation and clusters creation Deploy OpsMgr OVA Upload PKS tile Deploy

go-template='{{range.status.containerStatuses}}{{"Container Name: "}}{{.name}}{ {"\r\nLastState: "}}{{.lastState}}{{end}}' simmemleak-hra99 Container Name: simmemleak LastState: map[terminated:map[exitCode:137 reason:OOM API中的顶级资源。 有关API对象的更多详细信息，请访问： Service API object 。 For More Information 阅读 Connecting a Front End to a Back End Using a Service 。 原⽂ https://kubernetes.io/docs/concepts/services-networking/service/ 26-Service

from 3 VMs in 2015 to 10,000+ VMs today Our Journey to The Land of Containers Project X By the end of 2016, we started our Kubernetes journey by developing a deployment tool called Project X. The