Scaling a Multi-Tenant k8s Cluster in a Telco
Scaling a Multi-Tenant k8s Cluster in a Telco Pablo Moncada October 28, 2020 About MasMovil group ● 4th telecom company in Spain ● Provides voice and broadband services to +12M customers ● Several0 码力 | 6 页 | 640.05 KB | 1 年前3Cilium v1.10 Documentation
contact k8s api-server In the Cilium agent logs you will see: level=info msg="Establishing connection to apiserver" host="https://10.96.0.1:443" subsys=k8s level=error msg="Unable to contact k8s api-server" ipAddr="https://10.96.0.1:443" subsys=k8s level=fatal msg="Unable to initialize Kubernetes subsystem" error="unable to create k8s client: unable to create k8s client: Get https://10.96.0.1:443/api/ Important Please ensure that you are running version 1.7.9 [https://github.com/aws/amazon-vpc-cni- k8s/releases/tag/v1.7.9] or newer of the AWS VPC CNI plugin to guarantee compatibility with Cilium. The0 码力 | 1307 页 | 19.26 MB | 1 年前3Cilium v1.5 Documentation
The DaemonSet will automa�cally install itself as Kubernetes CNI plugin. K8s 1.15 K8s 1.14 K8s 1.13 K8s 1.12 K8s 1.11 K8s 1.10 kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1 The DaemonSet will automa�cally install itself as Kubernetes CNI plugin. K8s 1.15 K8s 1.14 K8s 1.13 K8s 1.12 K8s 1.11 K8s 1.10 kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1 during the bootstrapping phase of Cilium. For Docker as container runtime: K8s 1.15 K8s 1.14 K8s 1.13 K8s 1.12 K8s 1.11 K8s 1.10 kubectl apply -f https://raw.githubusercontent.com/cilium/cilium/v10 码力 | 740 页 | 12.52 MB | 1 年前3Cilium v1.9 Documentation
contact k8s api-server In the Cilum agent logs you will see: level=info msg="Establishing connection to apiserver" host="https://10.96.0.1:443" subsys=k8s level=error msg="Unable to contact k8s api-server" ipAddr="https://10.96.0.1:443" subsys=k8s level=fatal msg="Unable to initialize Kubernetes subsystem" error="unable to create k8s client: unable to create k8s client: Get https://10.96.0.1:443/api/ "ipam": { "type": "calico-ipam" }, "policy": { "type": "k8s" }, "kubernetes": { "kubeconfig": "/etc/cni/net.d/calico-kubeconfig"0 码力 | 1263 页 | 18.62 MB | 1 年前3Cilium v1.8 Documentation
contact k8s api-server In the Cilum agent logs you will see: level=info msg="Establishing connection to apiserver" host="https://10.96.0.1:443" subsys=k8s level=error msg="Unable to contact k8s api-server" ipAddr="https://10.96.0.1:443" subsys=k8s level=fatal msg="Unable to initialize Kubernetes subsystem" error="unable to create k8s client: unable to create k8s client: Get https://10.96.0.1:443/api/ "ipam": { "type": "calico-ipam" }, "policy": { "type": "k8s" }, "kubernetes": { "kubeconfig": "/etc/cni/net.d/calico-kubeconfig"0 码力 | 1124 页 | 21.33 MB | 1 年前3Cilium v1.6 Documentation
--kubernetes-version 1.10.3 : Kubernetes version that is to be installed. Please note [Kops 1.9 officially supports k8s version 1.9] --cloud-labels "Team=Dev,Owner=Admin" : Labels for your cluster ${NAME} : Name of the "ipam": { "type": "calico-ipam" }, "policy": { "type": "k8s" }, "kubernetes": { "kubeconfig": "/etc/cni/net.d/calico-kubeconfig" Disabled 104 k8s:io.cilium.k8s.policy.cluster=default 10.15.233.139 ready k8s:io.cilium.k8s.policy.serviceaccount=coredns0 码力 | 734 页 | 11.45 MB | 1 年前3Cilium v1.7 Documentation
contact k8s api-server In the Cilum agent logs you will see: level=info msg="Establishing connection to apiserver" host="https://10.96.0.1:443" subsys=k8s level=error msg="Unable to contact k8s api-server" ipAddr="https://10.96.0.1:443" subsys=k8s level=fatal msg="Unable to initialize Kubernetes subsystem" error="unable to create k8s client: unable to create k8s client: Get https://10.96.0.1:443/api/ "ipam": { "type": "calico-ipam" }, "policy": { "type": "k8s" }, "kubernetes": { "kubeconfig": "/etc/cni/net.d/calico-kubeconfig"0 码力 | 885 页 | 12.41 MB | 1 年前3Cilium v1.11 Documentation
contact k8s api-server In the Cilium agent logs you will see: level=info msg="Establishing connection to apiserver" host="https://10.96.0.1:443" subsys=k8s level=error msg="Unable to contact k8s api-server" ipAddr="https://10.96.0.1:443" subsys=k8s level=fatal msg="Unable to initialize Kubernetes subsystem" error="unable to create k8s client: unable to create k8s client: Get https://10.96.0.1:443/api/ Important Please ensure that you are running version 1.7.9 [https://github.com/aws/amazon-vpc-cni- k8s/releases/tag/v1.7.9] or newer of the AWS VPC CNI plugin to guarantee compatibility with Cilium. $0 码力 | 1373 页 | 19.37 MB | 1 年前3openEuler 21.09 技术白皮书
功能,策略配置淘汰的冷内存交换到用户态存储,用户无感知,性能 优于内核态 swap。 夯实云化基座 容器操作系统 KubeOS:云原生场景,实现 OS 容器化部署、运维,提供与业务容器一致的基于 K8S 的管理体验。 • 安全容器方案:iSulad + shimv2 + StratoVirt 安全容器方案,相比传统 docker + qemu 方案,底噪和启动时间 优化 40%。 • 双平面部署工具 MySQL、Redis、Nginx 等)和 CPU 消耗且时延不敏感的业务(如 AI 离线训练) 混合部署,包括容器与容器、容器与进程、容器与虚机、虚机与虚机混合部署等多种场景。 容器操作系统 云原生是云计算发展的下一跳、k8s 事实上已经成为云原生软件基础设施的底座。业界主流操作系统厂商都推出了针对 云原生场景的 OS,如 Rehat RCHOS,AWS BottleRocket 等,实现 OS 容器化部署、运维,提供与业务容器一致的管理和 容器化部署、运维,提供与业务容器一致的管理和 运维体验。 openEuler 适应云原生发展趋势,推出容器化操作系统 KubeOS,实现云原生集群 OS 的统一容器化管理,具备如下特点: 1. OS 容器化管理、对接 K8S,原子化的生命周期管理; 2. OS 轻量化裁剪,减少不必要的冗余包,可实现快速升级、替换等。 容器和容器混部 进程和容器混部 Linux Kernel cgroup 容器和虚机混部0 码力 | 35 页 | 3.72 MB | 1 年前3openEuler 22.03-LTS 技术白皮书
障敏感的数据优先使用高可靠内存,降 低宕机率,提升可靠性(技术预览特性)。 夯实云化基座 • 容器操作系统 KubeOS:云原生场景,实现 OS 容器化部署、运维,提供与业务容器一致的基于 K8s 的管理体验。 • 安全容器方案:iSulad+shimv2+StratoVirt 安全容器方案,相比传统 Docker+Qemu 方案,底噪和启动时间优化 40%。 • 双平面部署工具 eggo:ARM/x86 (Cloud) Global- Manager Local- Controller Local- Controller 智能协同 管理协同 边缘南向服务 服务协同 数据协同 网络协同 K8s OS Core 通信 Kit 容器引擎 KubeEdge (Cloud) EdgeMesh Agent KubeEdge (Edge) Sedna (Edge) CloudCore 适用于对交互类等时延敏感型业务(比如 MySQL、Redis、Nginx 等)和 CPU 消耗且时延不敏感业务(如 AI 离线训练) 的容器混合部署。 容器操作系统 云原生是云计算发展的下一跳、K8s 事实上已经成为云原生软件基础设施的底座。业界主流操作系统厂商都推出了针 对云原生场景的 OS,如 Rehat RCHOS、AWS BottleRocket 等,实现 OS 容器化部署、运维,提供与业务容器一致的管理0 码力 | 17 页 | 6.52 MB | 1 年前3
共 20 条
- 1
- 2