spec: workload: apiVersion: apps/v1 kind: Deployment spec: template: spec: containers: - name: web image: 'php:latest' env: - name: OAM_TEXTURE value: texture.jpg ports: - containerPort: 8001 protocol: TCP $ kubectl get deployment NAME REVISION AGE frontend-c8bb659c5 1 2d15h $ kubectl get components NAME WORKLOAD frontend deployment.apps.k8s.io Component：应用中的一个组成部分，例如容器、 Function或者云服务等 apiVersion: core.oam.dev/v1alpha2 kind: ApplicationConfiguration metadata: name: helloworld spec: components: # 1st component - componentName: frontend traits: - trait: apiVersion: autoscaling/v2beta2

Inception v3 and transfer learning • Automate repeatable ML experiments with containers • Deploy ML components to Kubernetes with Kubeflow • Scale and test ML experiments with Helm • Manage training jobs and Jupyter notebooks • Model serving – serve exported models with TF Serving or Seldon • Additional components for storage, workflow, etc. Artificial Intelligence solves critical life problems Demo: Find Containers Demo: Serving the Model with TF Serving • Options for serving • Wrap model in a web framework (eg – Flask) • Tensorflow Serving • Seldon Demo: Run TensorFlow Training with Kubeflow

全球機房備援設計 台灣區已經備有三個容錯區域 高效能代管式服務 涵蓋Web/App/DB皆有多 樣化代管服務可以組合出 最適架構 自動化部署 與開放平台以及開發環境 整合，加速應用上線 Google Cloud Taiwan 優勢 Google Infrastructure event driven functions web apps & APIs orchestrate containers 隨選生成的K8S叢集 Compute Engine 隨選生成的虛擬機 IaaS and PaaS at Scale Google App Engine #全代管服務 #以容器為基礎 #適合Web應用 #適合Api #全自動擴展+強大的負載平衡 #整合能同步擴展的NoSQL DB Kubernetes ● Kubernetes 是用於自動部署，擴展和管理容器化應用 程序的開源系統 GKE and GKE On-Prem ● Cluster environments are consistent (k8s version, OS image, plug-ins, components configuration) Orchestrate and manage on-prem containers just like GKE in the cloud Consistent

kind: ApplicationConfiguration metadata: name: my-awesome-app spec: components: - componentName: frontend instanceName: web-front-end traits: - name: Ingress properties: - name: path value: "/" Application Configuration：组装与自包含 OAM 加持下的 Kubernetes PaaS K8s 团队 运维 研发 监控报警 灰度发布 日志 扩缩容 负载均衡 web backend Trait Promethus Operator Elasticsearch Operator database Component OpenKruise RDS operator

org/benchmark/kubernetes/ 控制措施 如何查核 如何查核 參考資訊 預設配置 原因理由 如何查核 1. 控制平面元件 (Control Plane Components) 2. etcd 狀態資料庫 3. 控制平面設置 (Control Plane Configuration) 4. 工作節點 (Worker Node) 5. 政策 (Policies) 安全 維運 監控 維運 所需技能: Shell Script, Python, VMware API, CI/CD Tooling 所需技能: Java, .NET, SQL, Web 所需技能: vSphere/vSAN, NSX, OS, PowerCLI, Shell Script 建立平台自動化 能力與服務 將業務需求轉化成 應用程式快速上線 降低基礎架構複雜度

#!/overview? namespace=default 参考： https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/ 02-安装单机版Kubernetes 9 使⽤Kubespray部署⽣产可⽤的Kubernetes集群 （1.11.2） 前提：科学上⽹，或⾃⾏将gcr.io的镜像转成其他镜像仓库的镜像。 DNS是⼀个DNS服务器，它为Kubernetes服务提供DNS记录。 Kubernetes启动的容器会⾃动将该DNS服务器包含在DNS搜索中。 Web UI (Dashboard) Dashboard 是⼀个Kubernetes集群通⽤、基于Web的UI。它允许⽤户管理/排错集群中应⽤程序以及集群本身。 Container Resource Monitoring（容器资源监控） Container restartPolicy 为OnFailure或Never的Pod。 ReplicationController 、 ReplicaSet 以及 Deployment ，Pod预期不会终⽌，例如Web服务器。 ReplicationController仅适⽤于 restartPolicy 为Always的Pod。 DaemonSet ，每台机器都需要运⾏⼀个Pod，因为它们提供特定于机器的系统服务。

● A self-driving approach Motivation: microservices ● Increased operational cost ○ a lot of components ○ dynamic dependencies ○ fast deployment iteration ● Solution: automation Cluster management - SSH - Upgrade container runtime - Upgrade Kubelet Upgrade - master - SSH - Upgrade master components Upgrade - etcd - SSH - Upgrade etcd Upgrade kops AWS, GCP API node1 node2 node3 Rollback Self-hosted Kubernetes? What is self-hosted Kubernetes? ● Kubernetes manages own core components ● Core components deployed as native API objects Self-hosted k8s Architecture Why Self-host Kubernetes

& Teardown Cluster fast and convenient • Add & delete Node at any time • Upgrade Master & Node Components reliably • Canary Rollout • Master & Node Component Versions Management Motivation: Work Order Biz-Cluster: used to deploy our application. • Meta-Cluster: used to set up Biz-Cluster master components. We add Biz-Cluster master nodes to Meta-Cluster. • User: SREs who can setup & upgrade Biz-Cluster Kube-on-Kube-Operator: difference Biz-Cluster CRs and Biz-Cluster master components state, and manage Biz-Cluster master components through Kubernetes resource, such as Deployment, Pod, etc. Work Together

component that leads delivery of the pod to failure Is the cluster healthy 1 Are all software components working fine 2 How many failures occurred on the cluster SLIs on Large k8s Cluster 1. Cluster consequently. 4. Centralized Components Availability A ratio value indicates the time in which the cluster is available. It is used to evaluate the master components. The success standard and reason

be/PH-2FfFD2PU 14 VM VM VM VM Kubernetes Trend Worker Node The Kubernetes Master Node Basic Components Master Node ETCD kube-apiserver kube-controller-manager kube-scheduler • Key/Value Store performance and capacity • Affinity/Anti-Affinity Capable The Kubernetes Worker Node Basic Components Master Node ETCD kube-apiserver kube-controller-manager kube-Scheduler Worker Node CRI-containerd Creates virtual IP for external access • Interfaces with local iptables The Kubernetes Runtime Components • Runtime Objects Component Description Pods A grouping of one or more containers as an atomic