2017-08-21 18:44:34 +08:00
<!DOCTYPE HTML>
< html lang = "zh-cn" >
< head >
< meta charset = "UTF-8" >
< meta content = "text/html; charset=utf-8" http-equiv = "Content-Type" >
< title > 4.3.4 集群及应用监控 · Kubernetes Handbook< / title >
< meta http-equiv = "X-UA-Compatible" content = "IE=edge" / >
< meta name = "description" content = "" >
< meta name = "generator" content = "GitBook 3.2.2" >
< meta name = "author" content = "Jimmy Song" >
< link rel = "stylesheet" href = "../gitbook/style.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-splitter/splitter.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-page-toc-button/plugin.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-image-captions/image-captions.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-page-footer-ex/style/plugin.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-search-plus/search.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-highlight/website.css" >
< link rel = "stylesheet" href = "../gitbook/gitbook-plugin-fontsettings/website.css" >
< meta name = "HandheldFriendly" content = "true" / >
< meta name = "viewport" content = "width=device-width, initial-scale=1, user-scalable=no" >
< meta name = "apple-mobile-web-app-capable" content = "yes" >
< meta name = "apple-mobile-web-app-status-bar-style" content = "black" >
< link rel = "apple-touch-icon-precomposed" sizes = "152x152" href = "../gitbook/images/apple-touch-icon-precomposed-152.png" >
< link rel = "shortcut icon" href = "../gitbook/images/favicon.ico" type = "image/x-icon" >
< link rel = "next" href = "jenkins-ci-cd.html" / >
< link rel = "prev" href = "configuration-best-practice.html" / >
< / head >
< body >
< div class = "book" >
< div class = "book-summary" >
< div id = "book-search-input" role = "search" >
< input type = "text" placeholder = "輸入並搜尋" / >
< / div >
< nav role = "navigation" >
< ul class = "summary" >
< li class = "chapter " data-level = "1.1" data-path = "../" >
< a href = "../" >
1. 前言
< / a >
< / li >
< li class = "chapter " data-level = "1.2" data-path = "../concepts/" >
< a href = "../concepts/" >
2. 概念原理
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.2.1" data-path = "../concepts/concepts.html" >
< a href = "../concepts/concepts.html" >
2.1 设计理念
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2" data-path = "../concepts/objects.html" >
< a href = "../concepts/objects.html" >
2017-09-03 13:29:38 +08:00
2.2 Objects
2017-08-21 18:44:34 +08:00
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.2.2.1" data-path = "../concepts/pod-overview.html" >
< a href = "../concepts/pod-overview.html" >
2.2.1 Pod
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.2.2.1.1" data-path = "../concepts/pod.html" >
< a href = "../concepts/pod.html" >
2.2.1.1 Pod解析
< / a >
2017-08-31 23:28:33 +08:00
< / li >
< li class = "chapter " data-level = "1.2.2.1.2" data-path = "../concepts/init-containers.html" >
< a href = "../concepts/init-containers.html" >
2.2.1.2 Init容器
< / a >
2017-09-03 15:58:39 +08:00
< / li >
< li class = "chapter " data-level = "1.2.2.1.3" data-path = "../concepts/pod-security-policy.html" >
< a href = "../concepts/pod-security-policy.html" >
2.2.1.3 Pod安全策略
< / a >
2017-08-21 18:44:34 +08:00
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.2.2.2" data-path = "../concepts/node.html" >
< a href = "../concepts/node.html" >
2.2.2 Node
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.3" data-path = "../concepts/namespace.html" >
< a href = "../concepts/namespace.html" >
2.2.3 Namespace
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.4" data-path = "../concepts/service.html" >
< a href = "../concepts/service.html" >
2.2.4 Service
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.5" data-path = "../concepts/volume.html" >
< a href = "../concepts/volume.html" >
2.2.5 Volume和Persistent Volume
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.6" data-path = "../concepts/deployment.html" >
< a href = "../concepts/deployment.html" >
2.2.6 Deployment
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.7" data-path = "../concepts/secret.html" >
< a href = "../concepts/secret.html" >
2.2.7 Secret
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.8" data-path = "../concepts/statefulset.html" >
< a href = "../concepts/statefulset.html" >
2.2.8 StatefulSet
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.9" data-path = "../concepts/daemonset.html" >
< a href = "../concepts/daemonset.html" >
2.2.9 DaemonSet
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.10" data-path = "../concepts/serviceaccount.html" >
< a href = "../concepts/serviceaccount.html" >
2.2.10 ServiceAccount
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.11" data-path = "../concepts/replicaset.html" >
< a href = "../concepts/replicaset.html" >
2.2.11 ReplicationController和ReplicaSet
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.12" data-path = "../concepts/job.html" >
< a href = "../concepts/job.html" >
2.2.12 Job
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.13" data-path = "../concepts/cronjob.html" >
< a href = "../concepts/cronjob.html" >
2.2.13 CronJob
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.14" data-path = "../concepts/ingress.html" >
< a href = "../concepts/ingress.html" >
2.2.14 Ingress
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.15" data-path = "../concepts/configmap.html" >
< a href = "../concepts/configmap.html" >
2.2.15 ConfigMap
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.16" data-path = "../concepts/horizontal-pod-autoscaling.html" >
< a href = "../concepts/horizontal-pod-autoscaling.html" >
2.2.16 Horizontal Pod Autoscaling
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.17" data-path = "../concepts/label.html" >
< a href = "../concepts/label.html" >
2.2.17 Label
< / a >
2017-09-03 15:58:39 +08:00
< / li >
< li class = "chapter " data-level = "1.2.2.18" data-path = "../concepts/garbage-collection.html" >
< a href = "../concepts/garbage-collection.html" >
2.2.18 垃圾收集
< / a >
< / li >
< li class = "chapter " data-level = "1.2.2.19" data-path = "../concepts/network-policy.html" >
< a href = "../concepts/network-policy.html" >
2.2.19 NetworkPolicy
< / a >
2017-08-21 18:44:34 +08:00
< / li >
< / ul >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3" data-path = "../guide/" >
< a href = "../guide/" >
3. 用户指南
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.1" data-path = "../guide/resource-configuration.html" >
< a href = "../guide/resource-configuration.html" >
3.1 资源配置
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.1.1" data-path = "../guide/configure-liveness-readiness-probes.html" >
< a href = "../guide/configure-liveness-readiness-probes.html" >
3.1.1 配置Pod的liveness和readiness探针
< / a >
< / li >
< li class = "chapter " data-level = "1.3.1.2" data-path = "../guide/configure-pod-service-account.html" >
< a href = "../guide/configure-pod-service-account.html" >
3.1.2 配置Pod的Service Account
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3.2" data-path = "../guide/command-usage.html" >
< a href = "../guide/command-usage.html" >
3.2 命令使用
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.2.1" data-path = "../guide/using-kubectl.html" >
< a href = "../guide/using-kubectl.html" >
3.2.1 使用kubectl
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3.3" data-path = "../guide/cluster-management.html" >
< a href = "../guide/cluster-management.html" >
3.3 集群管理
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.3.1" data-path = "../guide/managing-tls-in-a-cluster.html" >
< a href = "../guide/managing-tls-in-a-cluster.html" >
3.3.1 管理集群中的TLS
< / a >
< / li >
< li class = "chapter " data-level = "1.3.3.2" data-path = "../guide/kubelet-authentication-authorization.html" >
< a href = "../guide/kubelet-authentication-authorization.html" >
3.3.2 kubelet的认证授权
< / a >
< / li >
< li class = "chapter " data-level = "1.3.3.3" data-path = "../guide/tls-bootstrapping.html" >
< a href = "../guide/tls-bootstrapping.html" >
3.3.3 TLS bootstrap
< / a >
2017-08-31 14:23:44 +08:00
< / li >
< li class = "chapter " data-level = "1.3.3.4" data-path = "../guide/kubectl-user-authentication-authorization.html" >
< a href = "../guide/kubectl-user-authentication-authorization.html" >
3.3.4 kubectl的用户认证授权
< / a >
< / li >
< li class = "chapter " data-level = "1.3.3.5" data-path = "../guide/rbac.html" >
< a href = "../guide/rbac.html" >
3.3.5 RBAC——基于角色的访问控制
< / a >
2017-08-21 18:44:34 +08:00
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3.4" data-path = "../guide/access-kubernetes-cluster.html" >
< a href = "../guide/access-kubernetes-cluster.html" >
3.4 访问 Kubernetes 集群
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.4.1" data-path = "../guide/access-cluster.html" >
< a href = "../guide/access-cluster.html" >
3.4.1 访问集群
< / a >
< / li >
< li class = "chapter " data-level = "1.3.4.2" data-path = "../guide/authenticate-across-clusters-kubeconfig.html" >
< a href = "../guide/authenticate-across-clusters-kubeconfig.html" >
3.4.2 使用 kubeconfig 文件配置跨集群认证
< / a >
< / li >
< li class = "chapter " data-level = "1.3.4.3" data-path = "../guide/connecting-to-applications-port-forward.html" >
< a href = "../guide/connecting-to-applications-port-forward.html" >
3.4.3 通过端口转发访问集群中的应用程序
< / a >
< / li >
< li class = "chapter " data-level = "1.3.4.4" data-path = "../guide/service-access-application-cluster.html" >
< a href = "../guide/service-access-application-cluster.html" >
3.4.4 使用 service 访问群集中的应用程序
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.3.5" data-path = "../guide/application-development-deployment-flow.html" >
< a href = "../guide/application-development-deployment-flow.html" >
3.5 在kubernetes中开发部署应用
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.3.5.1" data-path = "../guide/deploy-applications-in-kubernetes.html" >
< a href = "../guide/deploy-applications-in-kubernetes.html" >
3.5.1 适用于kubernetes的应用开发部署流程
< / a >
< / li >
< li class = "chapter " data-level = "1.3.5.2" data-path = "../guide/migrating-hadoop-yarn-to-kubernetes.html" >
< a href = "../guide/migrating-hadoop-yarn-to-kubernetes.html" >
3.5.2 迁移传统应用到kubernetes中——以Hadoop YARN为例
< / a >
< / li >
< / ul >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4" data-path = "./" >
< a href = "./" >
4. 最佳实践
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.1" data-path = "install-kbernetes1.6-on-centos.html" >
< a href = "install-kbernetes1.6-on-centos.html" >
4.1 在CentOS上部署kubernetes1.6集群
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.1.1" data-path = "create-tls-and-secret-key.html" >
< a href = "create-tls-and-secret-key.html" >
4.1.1 创建TLS证书和秘钥
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.2" data-path = "create-kubeconfig.html" >
< a href = "create-kubeconfig.html" >
4.1.2 创建kubeconfig文件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.3" data-path = "etcd-cluster-installation.html" >
< a href = "etcd-cluster-installation.html" >
4.1.3 创建高可用etcd集群
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.4" data-path = "kubectl-installation.html" >
< a href = "kubectl-installation.html" >
4.1.4 安装kubectl命令行工具
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.5" data-path = "master-installation.html" >
< a href = "master-installation.html" >
4.1.5 部署master节点
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.6" data-path = "node-installation.html" >
< a href = "node-installation.html" >
4.1.6 部署node节点
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.7" data-path = "kubedns-addon-installation.html" >
< a href = "kubedns-addon-installation.html" >
4.1.7 安装kubedns插件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.8" data-path = "dashboard-addon-installation.html" >
< a href = "dashboard-addon-installation.html" >
4.1.8 安装dashboard插件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.9" data-path = "heapster-addon-installation.html" >
< a href = "heapster-addon-installation.html" >
4.1.9 安装heapster插件
< / a >
< / li >
< li class = "chapter " data-level = "1.4.1.10" data-path = "efk-addon-installation.html" >
< a href = "efk-addon-installation.html" >
4.1.10 安装EFK插件
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4.2" data-path = "service-discovery-and-loadbalancing.html" >
< a href = "service-discovery-and-loadbalancing.html" >
4.2 服务发现与负载均衡
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.2.1" data-path = "traefik-ingress-installation.html" >
< a href = "traefik-ingress-installation.html" >
4.2.1 安装Traefik ingress
< / a >
< / li >
< li class = "chapter " data-level = "1.4.2.2" data-path = "distributed-load-test.html" >
< a href = "distributed-load-test.html" >
4.2.2 分布式负载测试
< / a >
< / li >
< li class = "chapter " data-level = "1.4.2.3" data-path = "network-and-cluster-perfermance-test.html" >
< a href = "network-and-cluster-perfermance-test.html" >
4.2.3 网络和集群性能测试
< / a >
< / li >
< li class = "chapter " data-level = "1.4.2.4" data-path = "edge-node-configuration.html" >
< a href = "edge-node-configuration.html" >
4.2.4 边缘节点配置
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4.3" data-path = "operation.html" >
< a href = "operation.html" >
4.3 运维管理
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.3.1" data-path = "service-rolling-update.html" >
< a href = "service-rolling-update.html" >
4.3.1 服务滚动升级
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.2" data-path = "app-log-collection.html" >
< a href = "app-log-collection.html" >
4.3.2 应用日志收集
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.3" data-path = "configuration-best-practice.html" >
< a href = "configuration-best-practice.html" >
4.3.3 配置最佳实践
< / a >
< / li >
< li class = "chapter active" data-level = "1.4.3.4" data-path = "monitor.html" >
< a href = "monitor.html" >
4.3.4 集群及应用监控
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.5" data-path = "jenkins-ci-cd.html" >
< a href = "jenkins-ci-cd.html" >
4.3.5 使用Jenkins进行持续构建与发布
< / a >
< / li >
< li class = "chapter " data-level = "1.4.3.6" data-path = "data-persistence-problem.html" >
< a href = "data-persistence-problem.html" >
4.3.6 数据持久化问题
< / a >
2017-09-03 15:58:39 +08:00
< / li >
< li class = "chapter " data-level = "1.4.3.7" data-path = "manage-compute-resources-container.html" >
< a href = "manage-compute-resources-container.html" >
4.3.7 管理容器的计算资源
< / a >
2017-08-21 18:44:34 +08:00
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4.4" data-path = "storage.html" >
< a href = "storage.html" >
4.4 存储管理
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.4.1" data-path = "glusterfs.html" >
< a href = "glusterfs.html" >
4.4.1 GlusterFS
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.4.1.1" data-path = "using-glusterfs-for-persistent-storage.html" >
< a href = "using-glusterfs-for-persistent-storage.html" >
4.4.1.1 使用GlusterFS做持久化存储
< / a >
< / li >
< li class = "chapter " data-level = "1.4.4.1.2" data-path = "storage-for-containers-using-glusterfs-with-openshift.html" >
< a href = "storage-for-containers-using-glusterfs-with-openshift.html" >
4.4.1.2 在OpenShift中使用GlusterFS做持久化存储
< / a >
2017-09-01 21:04:51 +08:00
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.4.4.2" data-path = "cephfs.html" >
< a href = "cephfs.html" >
4.4.2 CephFS
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.4.4.2.1" data-path = "using-ceph-for-persistent-storage.html" >
< a href = "using-ceph-for-persistent-storage.html" >
4.4.2.1 使用Ceph做持久化存储
< / a >
2017-08-21 18:44:34 +08:00
< / li >
< / ul >
< / li >
< / ul >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.5" data-path = "../usecases/" >
< a href = "../usecases/" >
5. 领域应用
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.5.1" data-path = "../usecases/microservices.html" >
< a href = "../usecases/microservices.html" >
5.1 微服务架构
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.5.1.1" data-path = "../usecases/istio.html" >
< a href = "../usecases/istio.html" >
5.1.1 Istio
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.5.1.1.1" data-path = "../usecases/istio-installation.html" >
< a href = "../usecases/istio-installation.html" >
5.1.1.1 安装istio
< / a >
< / li >
< li class = "chapter " data-level = "1.5.1.1.2" data-path = "../usecases/configuring-request-routing.html" >
< a href = "../usecases/configuring-request-routing.html" >
5.1.1.2 配置请求的路由规则
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.5.1.2" data-path = "../usecases/linkerd.html" >
< a href = "../usecases/linkerd.html" >
5.1.2 Linkerd
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.5.1.2.1" data-path = "../usecases/linkerd-user-guide.html" >
< a href = "../usecases/linkerd-user-guide.html" >
5.1.2.1 Linkerd 使用指南
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.5.1.3" data-path = "../usecases/service-discovery-in-microservices.html" >
< a href = "../usecases/service-discovery-in-microservices.html" >
5.1.3 微服务中的服务发现
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.5.2" data-path = "../usecases/big-data.html" >
< a href = "../usecases/big-data.html" >
5.2 大数据
< / a >
< ul class = "articles" >
2017-08-30 14:20:52 +08:00
< li class = "chapter " data-level = "1.5.2.1" data-path = "../usecases/spark-standalone-on-kubernetes.html" >
2017-08-21 18:44:34 +08:00
2017-08-30 14:20:52 +08:00
< a href = "../usecases/spark-standalone-on-kubernetes.html" >
2017-08-21 18:44:34 +08:00
2017-08-30 14:20:52 +08:00
5.2.1 Spark standalone on Kubernetes
2017-08-21 18:44:34 +08:00
< / a >
2017-08-31 14:23:44 +08:00
< / li >
< li class = "chapter " data-level = "1.5.2.2" data-path = "../usecases/support-spark-natively-in-kubernetes.html" >
< a href = "../usecases/support-spark-natively-in-kubernetes.html" >
5.2.2 运行支持kubernetes原生调度的Spark程序
< / a >
2017-08-21 18:44:34 +08:00
< / li >
< / ul >
2017-08-30 16:52:33 +08:00
< / li >
< li class = "chapter " data-level = "1.5.3" data-path = "../usecases/serverless.html" >
< a href = "../usecases/serverless.html" >
5.3 Serverless架构
< / a >
2017-08-21 18:44:34 +08:00
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.6" data-path = "../develop/" >
< a href = "../develop/" >
6. 开发指南
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.6.1" data-path = "../develop/developing-environment.html" >
< a href = "../develop/developing-environment.html" >
6.1 开发环境搭建
< / a >
< / li >
< li class = "chapter " data-level = "1.6.2" data-path = "../develop/testing.html" >
< a href = "../develop/testing.html" >
6.2 单元测试和集成测试
< / a >
< / li >
< li class = "chapter " data-level = "1.6.3" data-path = "../develop/client-go-sample.html" >
< a href = "../develop/client-go-sample.html" >
6.3 client-go示例
< / a >
< / li >
< li class = "chapter " data-level = "1.6.4" data-path = "../develop/contribute.html" >
< a href = "../develop/contribute.html" >
6.4 社区贡献
< / a >
< / li >
< / ul >
< / li >
< li class = "chapter " data-level = "1.7" data-path = "../appendix/" >
< a href = "../appendix/" >
7. 附录
< / a >
< ul class = "articles" >
< li class = "chapter " data-level = "1.7.1" data-path = "../appendix/docker-best-practice.html" >
< a href = "../appendix/docker-best-practice.html" >
7.1 Docker最佳实践
< / a >
< / li >
< li class = "chapter " data-level = "1.7.2" data-path = "../appendix/issues.html" >
< a href = "../appendix/issues.html" >
7.2 问题记录
< / a >
< / li >
< li class = "chapter " data-level = "1.7.3" data-path = "../appendix/tricks.html" >
< a href = "../appendix/tricks.html" >
7.3 使用技巧
< / a >
< / li >
< / ul >
< / li >
< li class = "divider" > < / li >
< li >
< a href = "https://www.gitbook.com" target = "blank" class = "gitbook-link" >
本書使用 GitBook 釋出
< / a >
< / li >
< / ul >
< / nav >
< / div >
< div class = "book-body" >
< div class = "body-inner" >
< div class = "book-header" role = "navigation" >
<!-- Title -->
< h1 >
< i class = "fa fa-circle-o-notch fa-spin" > < / i >
< a href = ".." > 4.3.4 集群及应用监控< / a >
< / h1 >
< / div >
< div class = "page-wrapper" tabindex = "-1" role = "main" >
< div class = "page-inner" >
< div class = "search-plus" id = "book-search-results" >
< div class = "search-noresults" >
< section class = "normal markdown-section" >
< h1 id = "集群及应用监控" > 集 群 及 应 用 监 控 < / h1 >
< p > 在 前 面 的 < a href = "heapster-addon-installation.html" > 安 装 heapster插 件 < / a > 章 节 ， 我 们 已 经 谈 到 Kubernetes本 身 提 供 了 监 控 插 件 作 为 集 群 和 容 器 监 控 的 选 择 ， 但 是 在 实 际 使 用 中 ， 因 为 种 种 原 因 ， 再 考 虑 到 跟 我 们 自 身 的 监 控 系 统 集 成 ， 我 们 准 备 重 新 造 轮 子 。 < / p >
< p > 针 对 kubernetes集 群 和 应 用 的 监 控 ， 相 较 于 传 统 的 虚 拟 机 和 物 理 机 的 监 控 有 很 多 不 同 ， 因 此 对 于 传 统 监 控 需 要 有 很 多 改 造 的 地 方 ， 需 要 关 注 以 下 三 个 方 面 ： < / p >
< ul >
< li > Kubernetes集 群 本 身 的 监 控 ， 主 要 是 kubernetes的 各 个 组 件 < / li >
< li > kubernetes集 群 中 Pod的 监 控 ， Pod的 CPU、 内 存 、 网 络 、 磁 盘 等 监 控 < / li >
< li > 集 群 内 部 应 用 的 监 控 ， 针 对 应 用 本 身 的 监 控 < / li >
< / ul >
< h2 id = "kubernetes集群中的监控" > Kubernetes集 群 中 的 监 控 < / h2 >
< figure id = "fig1.4.3.4.1" > < img src = "../images/monitoring-in-kubernetes.png" alt = "Kubernetes集群中的监控" > < figcaption > Figure: Kubernetes集 群 中 的 监 控 < / figcaption > < / figure >
< p > 跟 物 理 机 器 和 虚 拟 机 的 监 控 不 同 ， 在 kuberntes集 群 中 的 监 控 复 杂 度 更 高 一 些 ， 因 为 多 了 一 个 虚 拟 化 层 ， 当 然 这 个 跟 直 接 监 控 docker容 器 又 不 一 样 ， kubernetes在 docker之 上 又 抽 象 了 一 层 service的 概 念 。 < / p >
< p > 在 kubernetes中 的 监 控 需 要 考 虑 到 这 几 个 方 面 ： < / p >
< ul >
< li > 应 该 给 Pod打 上 哪 些 label， 这 些 label将 成 为 监 控 的 metrics。 < / li >
< li > 当 应 用 的 Pod漂 移 了 之 后 怎 么 办 ？ 因 为 要 考 虑 到 Pod的 生 命 周 期 比 虚 拟 机 和 物 理 机 短 的 多 ， 如 何 持 续 监 控 应 用 的 状 态 ？ < / li >
< li > 更 多 的 监 控 项 ， kubernetes本 身 、 容 器 、 应 用 等 。 < / li >
< li > 监 控 指 标 的 来 源 ， 是 通 过 heapster收 集 后 汇 聚 还 是 直 接 从 每 台 主 机 的 docker上 取 ？ < / li >
< / ul >
< h2 id = "容器的命名规则" > 容 器 的 命 名 规 则 < / h2 >
< p > 首 先 我 们 需 要 清 楚 使 用 cAdvisor收 集 的 数 据 的 格 式 和 字 段 信 息 。 < / p >
< p > 当 我 们 通 过 cAdvisor获 取 到 了 容 器 的 信 息 后 ， 例 如 访 问 < code > ${NODE_IP}:4194/api/v1.3/docker< / code > 获 取 的 json结 果 中 的 某 个 容 器 包 含 如 下 字 段 ： < / p >
< pre > < code class = "lang-json" > < span class = "hljs-string" > " labels" < / span > : {
< span class = "hljs-string" > " annotation.io.kubernetes.container.hash" < / span > : < span class = "hljs-string" > " f47f0602" < / span > ,
< span class = "hljs-string" > " annotation.io.kubernetes.container.ports" < / span > : < span class = "hljs-string" > " [{\" containerPort\" :80,\" protocol\" :\" TCP\" }]" < / span > ,
< span class = "hljs-string" > " annotation.io.kubernetes.container.restartCount" < / span > : < span class = "hljs-string" > " 0" < / span > ,
< span class = "hljs-string" > " annotation.io.kubernetes.container.terminationMessagePath" < / span > : < span class = "hljs-string" > " /dev/termination-log" < / span > ,
< span class = "hljs-string" > " annotation.io.kubernetes.container.terminationMessagePolicy" < / span > : < span class = "hljs-string" > " File" < / span > ,
< span class = "hljs-string" > " annotation.io.kubernetes.pod.terminationGracePeriod" < / span > : < span class = "hljs-string" > " 30" < / span > ,
< span class = "hljs-string" > " io.kubernetes.container.logpath" < / span > : < span class = "hljs-string" > " /var/log/pods/d8a2e995-3617-11e7-a4b0-ecf4bbe5d414/php-redis_0.log" < / span > ,
< span class = "hljs-string" > " io.kubernetes.container.name" < / span > : < span class = "hljs-string" > " php-redis" < / span > ,
< span class = "hljs-string" > " io.kubernetes.docker.type" < / span > : < span class = "hljs-string" > " container" < / span > ,
< span class = "hljs-string" > " io.kubernetes.pod.name" < / span > : < span class = "hljs-string" > " frontend-2337258262-771lz" < / span > ,
< span class = "hljs-string" > " io.kubernetes.pod.namespace" < / span > : < span class = "hljs-string" > " default" < / span > ,
< span class = "hljs-string" > " io.kubernetes.pod.uid" < / span > : < span class = "hljs-string" > " d8a2e995-3617-11e7-a4b0-ecf4bbe5d414" < / span > ,
< span class = "hljs-string" > " io.kubernetes.sandbox.id" < / span > : < span class = "hljs-string" > " 843a0f018c0cef2a5451434713ea3f409f0debc2101d2264227e814ca0745677" < / span >
},
< / code > < / pre >
< p > 这 些 信 息 其 实 都 是 kubernetes创 建 容 器 时 给 docker container打 的 < code > Labels< / code > ， 使 用 < code > docker inspect $conainer_name< / code > 命 令 同 样 可 以 看 到 上 述 信 息 。 < / p >
< p > 你 是 否 想 过 这 些 label跟 容 器 的 名 字 有 什 么 关 系 ？ 当 你 在 node节 点 上 执 行 < code > docker ps< / code > 看 到 的 容 器 名 字 又 对 应 哪 个 应 用 的 Pod呢 ？ < / p >
< p > 在 kubernetes代 码 中 pkg/kubelet/dockertools/docker.go中 的 BuildDockerName方 法 定 义 了 容 器 的 名 称 规 范 。 < / p >
< p > 这 段 容 器 名 称 定 义 代 码 如 下 ： < / p >
< pre > < code class = "lang-go" > < span class = "hljs-comment" > // Creates a name which can be reversed to identify both full pod name and container name.< / span >
< span class = "hljs-comment" > // This function returns stable name, unique name and a unique id.< / span >
< span class = "hljs-comment" > // Although rand.Uint32() is not really unique, but it' s enough for us because error will< / span >
< span class = "hljs-comment" > // only occur when instances of the same container in the same pod have the same UID. The< / span >
< span class = "hljs-comment" > // chance is really slim.< / span >
< span class = "hljs-keyword" > func< / span > BuildDockerName(dockerName KubeletContainerName, container *v1.Container) (< span class = "hljs-keyword" > string< / span > , < span class = "hljs-keyword" > string< / span > , < span class = "hljs-keyword" > string< / span > ) {
containerName := dockerName.ContainerName + < span class = "hljs-string" > " ." < / span > + strconv.FormatUint(kubecontainer.HashContainerLegacy(container), < span class = "hljs-number" > 16< / span > )
stableName := fmt.Sprintf(< span class = "hljs-string" > " %s_%s_%s_%s" < / span > ,
containerNamePrefix,
containerName,
dockerName.PodFullName,
dockerName.PodUID)
UID := fmt.Sprintf(< span class = "hljs-string" > " %08x" < / span > , rand.Uint32())
< span class = "hljs-keyword" > return< / span > stableName, fmt.Sprintf(< span class = "hljs-string" > " %s_%s" < / span > , stableName, UID), UID
}
< span class = "hljs-comment" > // Unpacks a container name, returning the pod full name and container name we would have used to< / span >
< span class = "hljs-comment" > // construct the docker name. If we are unable to parse the name, an error is returned.< / span >
< span class = "hljs-keyword" > func< / span > ParseDockerName(name < span class = "hljs-keyword" > string< / span > ) (dockerName *KubeletContainerName, hash < span class = "hljs-keyword" > uint64< / span > , err error) {
< span class = "hljs-comment" > // For some reason docker appears to be appending ' /' to names.< / span >
< span class = "hljs-comment" > // If it' s there, strip it.< / span >
name = strings.TrimPrefix(name, < span class = "hljs-string" > " /" < / span > )
parts := strings.Split(name, < span class = "hljs-string" > " _" < / span > )
< span class = "hljs-keyword" > if< / span > < span class = "hljs-built_in" > len< / span > (parts) == < span class = "hljs-number" > 0< / span > || parts[< span class = "hljs-number" > 0< / span > ] != containerNamePrefix {
err = fmt.Errorf(< span class = "hljs-string" > " failed to parse Docker container name %q into parts" < / span > , name)
< span class = "hljs-keyword" > return< / span > < span class = "hljs-literal" > nil< / span > , < span class = "hljs-number" > 0< / span > , err
}
< span class = "hljs-keyword" > if< / span > < span class = "hljs-built_in" > len< / span > (parts) < < span class = "hljs-number" > 6< / span > {
< span class = "hljs-comment" > // We have at least 5 fields. We may have more in the future.< / span >
< span class = "hljs-comment" > // Anything with less fields than this is not something we can< / span >
< span class = "hljs-comment" > // manage.< / span >
glog.Warningf(< span class = "hljs-string" > " found a container with the %q prefix, but too few fields (%d): %q" < / span > , containerNamePrefix, < span class = "hljs-built_in" > len< / span > (parts), name)
err = fmt.Errorf(< span class = "hljs-string" > " Docker container name %q has less parts than expected %v" < / span > , name, parts)
< span class = "hljs-keyword" > return< / span > < span class = "hljs-literal" > nil< / span > , < span class = "hljs-number" > 0< / span > , err
}
nameParts := strings.Split(parts[< span class = "hljs-number" > 1< / span > ], < span class = "hljs-string" > " ." < / span > )
containerName := nameParts[< span class = "hljs-number" > 0< / span > ]
< span class = "hljs-keyword" > if< / span > < span class = "hljs-built_in" > len< / span > (nameParts) > < span class = "hljs-number" > 1< / span > {
hash, err = strconv.ParseUint(nameParts[< span class = "hljs-number" > 1< / span > ], < span class = "hljs-number" > 16< / span > , < span class = "hljs-number" > 32< / span > )
< span class = "hljs-keyword" > if< / span > err != < span class = "hljs-literal" > nil< / span > {
glog.Warningf(< span class = "hljs-string" > " invalid container hash %q in container %q" < / span > , nameParts[< span class = "hljs-number" > 1< / span > ], name)
}
}
podFullName := parts[< span class = "hljs-number" > 2< / span > ] + < span class = "hljs-string" > " _" < / span > + parts[< span class = "hljs-number" > 3< / span > ]
podUID := types.UID(parts[< span class = "hljs-number" > 4< / span > ])
< span class = "hljs-keyword" > return< / span > & KubeletContainerName{podFullName, podUID, containerName}, hash, < span class = "hljs-literal" > nil< / span >
}
< / code > < / pre >
< p > 我 们 可 以 看 到 容 器 名 称 中 包 含 如 下 几 个 字 段 ， 中 间 用 下 划 线 隔 开 ， 至 少 有 6个 字 段 ， 未 来 可 能 添 加 更 多 字 段 。 < / p >
< p > 下 面 的 是 四 个 基 本 字 段 。 < / p >
< pre > < code > containerNamePrefix_containerName_PodFullName_PodUID
< / code > < / pre > < p > 所 有 kubernetes启 动 的 容 器 的 containerNamePrefix都 是 k8s。 < / p >
< p > Kubernetes启 动 的 docker容 器 的 容 器 名 称 规 范 ， 下 面 以 官 方 示 例 guestbook为 例 ， Deployment 名 为 frontend中 启 动 的 名 为 php-redis的 docker容 器 的 副 本 书 为 3。 < / p >
< p > Deployment frontend的 配 置 如 下 ： < / p >
< pre > < code class = "lang-yaml" > < span class = "hljs-attr" > apiVersion:< / span > extensions/v1beta1
< span class = "hljs-attr" > kind:< / span > Deployment
< span class = "hljs-attr" > metadata:< / span >
< span class = "hljs-attr" > name:< / span > frontend
< span class = "hljs-attr" > spec:< / span >
< span class = "hljs-attr" > template:< / span >
< span class = "hljs-attr" > metadata:< / span >
< span class = "hljs-attr" > labels:< / span >
< span class = "hljs-attr" > app:< / span > guestbook
< span class = "hljs-attr" > tier:< / span > frontend
< span class = "hljs-attr" > spec:< / span >
< span class = "hljs-attr" > containers:< / span >
< span class = "hljs-attr" > - name:< / span > php-redis
< span class = "hljs-attr" > image:< / span > bj-xg-oam-docker-hub< span class = "hljs-bullet" > -001.< / span > tendcloud.com/library/gb-frontend:v4
< span class = "hljs-attr" > resources:< / span >
< span class = "hljs-attr" > requests:< / span >
< span class = "hljs-attr" > cpu:< / span > < span class = "hljs-number" > 100< / span > m
< span class = "hljs-attr" > memory:< / span > < span class = "hljs-number" > 100< / span > Mi
< span class = "hljs-attr" > env:< / span >
< span class = "hljs-attr" > - name:< / span > GET_HOSTS_FROM
< span class = "hljs-attr" > value:< / span > dns
< span class = "hljs-attr" > ports:< / span >
< span class = "hljs-attr" > - containerPort:< / span > < span class = "hljs-number" > 80< / span >
< / code > < / pre >
< p > 我 们 选 取 三 个 实 例 中 的 一 个 运 行 php-redis的 docker容 器 。 < / p >
< pre > < code > k8s_php-redis_frontend-2337258262-154p7_default_d8a2e2dd-3617-11e7-a4b0-ecf4bbe5d414_0
< / code > < / pre > < ul >
< li > containerNamePrefix： k8s< / li >
< li > containerName： php-redis< / li >
< li > podFullName： frontend-2337258262-154p7< / li >
< li > computeHash： 154p7< / li >
< li > deploymentName： frontend< / li >
< li > replicaSetName： frontend-2337258262< / li >
< li > namespace： default< / li >
< li > podUID： d8a2e2dd-3617-11e7-a4b0-ecf4bbe5d414< / li >
< / ul >
< p > kubernetes容 器 命 名 规 则 解 析 ， 见 下 图 所 示 。 < / p >
< figure id = "fig1.4.3.4.2" > < img src = "../images/kubernetes-container-naming-rule.jpg" alt = "kubernetes的容器命名规则示意图" > < figcaption > Figure: kubernetes的 容 器 命 名 规 则 示 意 图 < / figcaption > < / figure >
< h2 id = "使用heapster进行集群监控" > 使 用 Heapster进 行 集 群 监 控 < / h2 >
< p > < a href = "https://github.com/kubernetes/heapster" target = "_blank" > Heapster< / a > 是 kubernetes官 方 提 供 的 监 控 方 案 ， 我 们 在 前 面 的 章 节 中 已 经 讲 解 了 如 何 部 署 和 使 用 heapster， 见 < a href = "heapster-addon-installation.html" > 安 装 Heapster插 件 < / a > 。 < / p >
< p > 但 是 Grafana显 示 的 指 标 只 根 据 Namespace和 Pod两 层 来 分 类 ， 实 在 有 些 单 薄 ， 我 们 希 望 通 过 应 用 的 label增 加 service这 一 层 分 类 。 架 构 图 如 下 ： < / p >
< figure id = "fig1.4.3.4.3" > < img src = "../images/kubernetes-heapster-monitoring.png" alt = "Heapster架构图（改进版）" > < figcaption > Figure: Heapster架 构 图 （ 改 进 版 ） < / figcaption > < / figure >
< p > 在 不 改 变 原 有 架 构 的 基 础 上 ， 通 过 应 用 的 label来 区 分 不 同 应 用 的 pod。 < / p >
< h2 id = "应用监控" > 应 用 监 控 < / h2 >
< p > Kubernetes中 应 用 的 监 控 架 构 如 图 ： < / p >
< figure id = "fig1.4.3.4.4" > < img src = "../images/kubernetes-app-monitoring.png" alt = "应用监控架构图" > < figcaption > Figure: 应 用 监 控 架 构 图 < / figcaption > < / figure >
< p > 这 种 方 式 有 以 下 几 个 要 点 ： < / p >
< ul >
< li > 访 问 kubernetes API获 取 应 用 Pod的 IP和 端 口 < / li >
< li > Pod labels作 为 监 控 metric的 tag< / li >
< li > 直 接 访 问 应 用 的 Pod的 IP和 端 口 获 取 应 用 监 控 数 据 < / li >
< li > metrics发 送 到 < a href = "https://github.com/talkingdata/owl" target = "_blank" > OWL< / a > 中 存 储 和 展 示 < / li >
< / ul >
< h2 id = "应用拓扑状态图" > 应 用 拓 扑 状 态 图 < / h2 >
< p > 对 于 复 杂 的 应 用 编 排 和 依 赖 关 系 ， 我 们 希 望 能 够 有 清 晰 的 图 标 一 览 应 用 状 态 和 拓 扑 关 系 ， 因 此 我 们 用 到 了 Weaveworks开 源 的 < a href = "https://github.com/weaveworks/scope" target = "_blank" > scope< / a > 。 < / p >
< p > < strong > 安 装 scope< / strong > < / p >
< p > 我 们 在 kubernetes集 群 上 使 用 standalone方 式 安 装 ， 详 情 参 考 < a href = "https://www.weave.works/docs/scope/latest/installing/#k8s" target = "_blank" > Installing Weave Scope< / a > 。 < / p >
< p > 使 用 < a href = "../manifests/weave/scope.yaml" > scope.yaml< / a > 文 件 安 装 scope， 该 服 务 安 装 在 < code > kube-system< / code > namespace下 。 < / p >
< pre > < code class = "lang-Bash" > $ kubectl apply < span class = "hljs-_" > -f< / span > scope.yaml
< / code > < / pre >
< p > 创 建 一 个 新 的 Ingress： < code > kube-system.yaml< / code > ， 配 置 如 下 ： < / p >
< pre > < code class = "lang-yaml" > < span class = "hljs-attr" > apiVersion:< / span > extensions/v1beta1
< span class = "hljs-attr" > kind:< / span > Ingress
< span class = "hljs-attr" > metadata:< / span >
< span class = "hljs-attr" > name:< / span > traefik-ingress
< span class = "hljs-attr" > namespace:< / span > kube-system
< span class = "hljs-attr" > spec:< / span >
< span class = "hljs-attr" > rules:< / span >
< span class = "hljs-attr" > - host:< / span > scope.weave.io
< span class = "hljs-attr" > http:< / span >
< span class = "hljs-attr" > paths:< / span >
< span class = "hljs-attr" > - path:< / span > /
< span class = "hljs-attr" > backend:< / span >
< span class = "hljs-attr" > serviceName:< / span > weave-scope-app
< span class = "hljs-attr" > servicePort:< / span > < span class = "hljs-number" > 80< / span >
< / code > < / pre >
< p > 执 行 < code > kubectl apply -f kube-system.yaml< / code > 后 在 你 的 主 机 上 的 < code > /etc/hosts< / code > 文 件 中 添 加 一 条 记 录 ： < / p >
< pre > < code > 172.20.0.119 scope.weave.io
< / code > < / pre > < p > 在 浏 览 器 中 访 问 < code > scope.weave.io< / code > 就 可 以 访 问 到 scope了 ， 详 见 < a href = "edge-node-configuration.html" > 边 缘 节 点 配 置 < / a > 。 < / p >
< figure id = "fig1.4.3.4.5" > < img src = "../images/weave-scope-service-topology.jpg" alt = "应用拓扑图" > < figcaption > Figure: 应 用 拓 扑 图 < / figcaption > < / figure >
< p > 如 上 图 所 示 ， scope可 以 监 控 kubernetes集 群 中 的 一 系 列 资 源 的 状 态 、 资 源 使 用 情 况 、 应 用 拓 扑 、 scale、 还 可 以 直 接 通 过 浏 览 器 进 入 容 器 内 部 调 试 等 。 < / p >
< h2 id = "参考" > 参 考 < / h2 >
< p > < a href = "https://www.datadoghq.com/blog/monitoring-kubernetes-era/" target = "_blank" > Monitoring in the Kubernetes Era< / a > < / p >
< footer class = "page-footer-ex" > < span class = "page-footer-ex-copyright" > for GitBook< / span >                       < span class = "page-footer-ex-footer-update" > update
2017-08-21 18:23:35
< / span > < / footer >
< / section >
< / div >
< div class = "search-results" >
< div class = "has-results" >
< h1 class = "search-results-title" > < span class = 'search-results-count' > < / span > results matching "< span class = 'search-query' > < / span > "< / h1 >
< ul class = "search-results-list" > < / ul >
< / div >
< div class = "no-results" >
< h1 class = "search-results-title" > No results matching "< span class = 'search-query' > < / span > "< / h1 >
< / div >
< / div >
< / div >
< / div >
< / div >
< / div >
< a href = "configuration-best-practice.html" class = "navigation navigation-prev " aria-label = "Previous page: 4.3.3 配置最佳实践" >
< i class = "fa fa-angle-left" > < / i >
< / a >
< a href = "jenkins-ci-cd.html" class = "navigation navigation-next " aria-label = "Next page: 4.3.5 使用Jenkins进行持续构建与发布" >
< i class = "fa fa-angle-right" > < / i >
< / a >
< / div >
< script >
var gitbook = gitbook || [];
gitbook.push(function() {
2017-09-06 22:17:23 +08:00
gitbook.page.hasChanged({"page":{"title":"4.3.4 集群及应用监控","level":"1.4.3.4","depth":3,"next":{"title":"4.3.5 使用Jenkins进行持续构建与发布","level":"1.4.3.5","depth":3,"path":"practice/jenkins-ci-cd.md","ref":"practice/jenkins-ci-cd.md","articles":[]},"previous":{"title":"4.3.3 配置最佳实践","level":"1.4.3.3","depth":3,"path":"practice/configuration-best-practice.md","ref":"practice/configuration-best-practice.md","articles":[]},"dir":"ltr"},"config":{"plugins":["github","codesnippet","splitter","page-toc-button","image-captions","page-footer-ex","editlink","-lunr","-search","search-plus"],"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"pluginsConfig":{"github":{"url":"https://github.com/rootsongjc/kubernetes-handbook"},"editlink":{"label":"编辑本页","multilingual":false,"base":"https://github.com/rootsongjc/kubernetes-handbook/blob/master/"},"page-footer-ex":{"copyright":"for GitBook","update_format":"YYYY-MM-DD HH:mm:ss","update_label":"update"},"splitter":{},"codesnippet":{},"fontsettings":{"theme":"white","family":"sans","size":2},"highlight":{},"page-toc-button":{},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"theme-default":{"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"showLevel":false},"search-plus":{},"image-captions":{"variable_name":"_pictures"}},"page-footer-ex":{"copyright":"Jimmy Song","update_label":"最后更新：","update_format":"YYYY-MM-DD HH:mm:ss"},"theme":"default","author":"Jimmy Song","pdf":{"pageNumbers":true,"fontSize":12,"fontFamily":"Arial","paperSize":"a4","chapterMark":"pagebreak","pageBreaksBefore":"/","margin":{"right":62,"left":62,"top":56,"bottom":56}},"structure":{"langs":"LANGS.md","readme":"README.md","glossary":"GLOSSARY.md","summary":"SUMMARY.md"},"variables":{"_pictures":[{"backlink":"concepts/index.html#fig1.2.1","level":"1.2","list_caption":"Figure: Borg架构","alt":"Borg架构","nro":1,"url":"../images/borg.png","index":1,"caption_template":"Figure: _CAPTION_","label":"Borg架构","attributes":{},"skip":false,"key":"1.2.1"},{"backlink":"concepts/index.html#fig1.2.2","level":"1.2","list_caption":"Figure: Kubernetes架构","alt":"Kubernetes架构","nro":2,"url":"../images/architecture.png","index":2,"caption_template":"Figure: _CAPTION_","label":"Kubernetes架构","attributes":{},"skip":false,"key":"1.2.2"},{"backlink":"concepts/index.html#fig1.2.3","level":"1.2","list_caption":"Figure: kubernetes整体架构示意图","alt":"kubernetes整体架构示意图","nro":3,"url":"../images/kubernetes-whole-arch.png","index":3,"caption_template":"Figure: _CAPTION_","label":"kubernetes整体架构示意图","attributes":{},"skip":false,"key":"1.2.3"},{"backlink":"concepts/index.html#fig1.2.4","level":"1.2","list_caption":"Figure: Kubernetes master架构示意图","alt":"Kubernetes master架构示意图","nro":4,"url":"../images/kubernetes-master-arch.png","index":4,"caption_template":"Figure: _CAPTION_","label":"Kubernetes master架构示意图","attributes":{},"skip":false,"key":"1.2.4"},{"backlink":"concepts/index.html#fig1.2.5","level":"1.2","list_caption":"Figure: kubernetes node架构示意图","alt":"kubernetes node架构示意图","nro":5,"url":"../images/kubernetes-node-arch.png","index":5,"caption_template":"Figure: _CAPTION_","label":"kubernetes node架构示意图","attributes":{},"skip":false,"key":"1.2.5"},{"backlink":"concepts/index.html#fig1.2.6","level":"1.2","list_caption":"Figure: Kubernetes分层架构示意图","alt":"Kubernetes分层架构示意图","nro":6,"url":"../images/kubernetes-layers-arch.jpg","index":6,"caption_template":"Figure: _CAPTION_","label":"Kubernetes分层架构示意图","attributes":{},"skip":false,"key":"1.2.6"},{"backlink":"concepts/concepts.h
2017-08-21 18:44:34 +08:00
});
< / script >
< / div >
< script src = "../gitbook/gitbook.js" > < / script >
< script src = "../gitbook/theme.js" > < / script >
< script src = "../gitbook/gitbook-plugin-github/plugin.js" > < / script >
< script src = "../gitbook/gitbook-plugin-splitter/splitter.js" > < / script >
< script src = "../gitbook/gitbook-plugin-page-toc-button/plugin.js" > < / script >
< script src = "../gitbook/gitbook-plugin-editlink/plugin.js" > < / script >
< script src = "../gitbook/gitbook-plugin-search-plus/jquery.mark.min.js" > < / script >
< script src = "../gitbook/gitbook-plugin-search-plus/search.js" > < / script >
< script src = "../gitbook/gitbook-plugin-sharing/buttons.js" > < / script >
< script src = "../gitbook/gitbook-plugin-fontsettings/fontsettings.js" > < / script >
< / body >
< / html >
