underlying tier of high availability and automated placement options, for both control plane and worker nodes. 2 levels of scheduling and resource management are active. ​Currently no automatic scheduling scheduler continuously pull pods off the queue, evaluates the pod’s requirements, and assigns it to a worker node. 6 Kubenetes scheduling What does the scheduler do: As pod are created, they are place in queue, evaluates the pod’s requirements, and assigns it to a worker node. Placement Decision Stages: 1. Filter out impossible worker nodes a. Filters are called predicates - extensible in code with a

underlying tier of high availability and automated placement options, for both control plane and worker nodes. 2 levels of scheduling and resource management are active. Currently no automatic scheduling scheduler continuously pull pods off the queue, evaluates the pod’s requirements, and assigns it to a worker node. 6 Kubenetes scheduling What does the scheduler do: As pod are created, they are place in queue, evaluates the pod’s requirements, and assigns it to a worker node. Placement Decision Stages: 1. Filter out impossible worker nodes a. Filters are called predicates - extensible in code with

Pod (~1:1) • Replicas = QTY of Pods that must be running Worker Node Worker Node Worker Node Kubernetes Master Node (Master & etcd nodes) API K K K App_Y.yaml ContainerImage1 Replicas: 1 ContainerImage2 ContainerImage2 Replicas: 2 https://youtu.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 • Leader based clustering • Can be clustered across Master Nodes • Contains all state known about cluster • Kubernetes Front-end Control Plane • Provides RESTful

parameter - IAM for Pods - New Amazon EKS Regions: Ningxia 研发中 - Amazon EKS on Fargate - Managed Nodes - Managed add-ons - DNS resolution of Amazon EKS private endpoints - New Amazon EKS Regions: reserved. Amazon Confidential eksctl–安装管理 Amazon EKS 集群的利器 • 最简单的命令行创建集群工具 eksctl create cluster –nodes=4 • 在GitHub上已开源 https://eksctl.io/ • 由Weave 和 AWS 共同构建 • Amazon EKS 官方支持的CLI工具 © 2019, Amazon 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Amazon Confidential 配置 worker nodes AWS CloudFormation eksctl Partners …更多 Terraform Pulumi Rancher © 2019, Amazon Web Services

需通过⾸云集群管理⻚⾯进⾏上述操作 创建集群 进⼊集群⻚⾯ -> 右上⻆点击创建集群 设置集群名称 -> 选择虚拟数据中⼼ -> 选择集群私⽹ip⽹段 -> 选择计费⽅式-> 设置master节点 - > 设置worker节点 -> 选择HA配置 -> 选择集群公⽹ip -> 设置集群ssh登录密码 -> 确认⽆误后点击 确认 2.使⽤须知 集群管理 1.简介 2.使⽤须知 3.操作说明 4 5 8 添加worker节点 进⼊集群⻚⾯ -> 选择需要操作的集群 -> 点击集群扩容 核对集群ID -> 选择增加节点类型为worker -> 选择计算类型与规格 -> 添加云盘（可不选）-> 设置 添加数量 -> 输⼊登录⽤户密码 -> 核对⽆误后，点击确定进⾏添加 9 进⼊节点查看⻚⾯ -> 选择对应集群，新添加节点状态由创建中 -> 正常代表添加成功 删除worker节点（master节点不可移除） 删除worker节点（master节点不可移除） 进⼊节点查看⻚⾯ -> 选择对应集群，选择要删除的worker节点 -> 点击删除 10 点击删除后，仔细阅读提示后，没问题点击确认执⾏删除操作 进⼊节点查看⻚⾯ -> 选择对应集群，删除节点状态由删除中 -> 节点消失代表删除成功 11 设置节点调度 进⼊节点查看⻚⾯ -> 选择对应集群 -> 选择要设置的节点 -> 设置是否可调度 仔细阅读提示，没问题后点击确认

How to manage so many clusters ,resources and businesses How to ensure load balancing of cluster nodes 1 2 Improper resource requests 3 Multi-tenant resource preemption How to expand horizontally more Cluster2 Business 1 Business 2 Business 3 Business N … How to ensure load balancing of cluster nodes ？ Dynamic-Scheduler Node1 Node2 Kube-scheduler Pod Request Load Level Request Load Level Real based on the resource request of Pod. However, in many cases, some nodes have low resource requests but high load, while some nodes have high resource requests but low load. Dynamic-Scheduler Node1

Production environment: • Dozens of Cluster • 5k+ Nodes / Cluster • 10k+ Nodes / largest Cluster • Testing environment • Hundreds of Cluster for CI/CD • 500+ Nodes / Cluster Background: Operation Requirements Rollout • Master & Node Component Versions Management Motivation: Work Order Deployment Worker Order • Upgrade Nodes Versions • Upgrade Node 10.10.10.1 • Upgrade docker • Upgrade kubelet • Upgrade Node • Agile, flexible and convenient Node-Operator: Overview • User: SREs who can scale & offline Nodes through posting Machine CRs. • Node-Operator: difference Machine and Node state, manage Node

requirements § Config Maps § Daemon Sets § Deployments § Events § Endpoints § Ingress § Jobs § Nodes § Namespaces § Pods § Persistent Volumes § Replica Sets § Secrets § Services § Stateful Sets… guarantees about the ordering and uniqueness of these Pods • A DaemonSet ensures that all (or some) Nodes run a copy of a Pod • In OpenWhisk, we deploy strictly mangaged objects as StatefulSet or DaemonSet: Affinity type – Node Affinity – Pod Affinity Demo Steps 1. Create a namespace 2. Label worker nodes to execute user actions 3. Create a mycluster.yaml file to customize the deployment 4

Kubernetes基础结构介绍 Kubernetes Master架构组成： 8 www.h3c.com Confidential 秘密 88 Kubernetes基础结构介绍 Kubernetes Node（Worker）架构组成： 9 www.h3c.com Confidential 秘密 99 Kubernetes基础架构介绍 01 02 Kubernetes基本概念和术语介绍 04 Kubernetes技术在H3Cloud 象。数据存储采用的是键值对存储。保存了整个集群的状态。 11 www.h3c.com Confidential 秘密 11 11 K8s基本概念和术语介绍（Node） 工作节点（Node/Worker）： Node是集群的工作节点，运行具体的Pod，当某个Node宕机时，其工作负载会被Master自动转移到其他Node节点上。 默认情况下kubelet会向Master注册自己。一旦Node 查看资源对象 kubectl get pods kubectl get rc，service,node 3.描述资源对象的详细信息（定位问题时需要用到，请重点掌握） kubectl describe nodes kubectl describe pod kubectl describe 4. 删除资源对象 kubectl delete –f

inventory/mycluster/hosts.ini cluster.yml ⼤概20分钟左右，Kubernetes即可安装完毕。 验证 验证1：查看Node状态 ]# kubectl get nodes NAME STATUS ROLES AGE VERSION node1 Ready master,node 2m ⼤多数Kubernetes资源（例如：Pod、Service、Replication Controllers等）都在某些Namespace中。但Namespace资 源本身并不在Namespace中。低级资源（例如： nodes 和persistentVolumes）也不在任何Namespace中。事件是⼀个 例外：它们可能有也可能没有Namespace，具体取决于事件的对象。 08-Namespace 25 L Kubelet authentication and/or authorization 来保护kubelet API。 12-Master与Node的通信 34 apiserver -> nodes, pods, and services 从apiserver到Node、Pod或Service的连接默认为纯HTTP连接，因此不会被认证或加密。可通过将 https: 前缀添加到 到API