2307 lines
93 KiB
HTML
2307 lines
93 KiB
HTML
|
||
<!DOCTYPE HTML>
|
||
<html lang="zh-cn" >
|
||
<head>
|
||
<meta charset="UTF-8">
|
||
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
|
||
<title>4.2.3 网络和集群性能测试 · 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="edge-node-configuration.html" />
|
||
|
||
|
||
<link rel="prev" href="distributed-load-test.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">
|
||
|
||
|
||
2.2 Objects
|
||
|
||
</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>
|
||
|
||
|
||
|
||
</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>
|
||
|
||
|
||
|
||
</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>
|
||
|
||
|
||
|
||
</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>
|
||
|
||
|
||
|
||
</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>
|
||
|
||
|
||
|
||
</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>
|
||
|
||
<li class="chapter " data-level="1.3.2.2" data-path="../guide/docker-cli-to-kubectl.html">
|
||
|
||
<a href="../guide/docker-cli-to-kubectl.html">
|
||
|
||
|
||
3.2.2 docker用户过度到kubectl命令行指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="1.3.3" data-path="../guide/cluster-security-management.html">
|
||
|
||
<a href="../guide/cluster-security-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>
|
||
|
||
|
||
|
||
</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>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="1.3.3.6" data-path="../guide/ip-masq-agent.html">
|
||
|
||
<a href="../guide/ip-masq-agent.html">
|
||
|
||
|
||
3.3.6 IP伪装代理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</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 active" 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 " 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>
|
||
|
||
|
||
|
||
</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>
|
||
|
||
|
||
|
||
</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>
|
||
|
||
|
||
|
||
</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>
|
||
|
||
|
||
|
||
</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">
|
||
|
||
|
||
<li class="chapter " data-level="1.5.2.1" data-path="../usecases/spark-standalone-on-kubernetes.html">
|
||
|
||
<a href="../usecases/spark-standalone-on-kubernetes.html">
|
||
|
||
|
||
5.2.1 Spark standalone on Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="1.5.2.2" data-path="../usecases/running-spark-with-kubernetes-native-scheduler.html">
|
||
|
||
<a href="../usecases/running-spark-with-kubernetes-native-scheduler.html">
|
||
|
||
|
||
5.2.2 运行支持kubernetes原生调度的Spark程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="1.5.3" data-path="../usecases/serverless.html">
|
||
|
||
<a href="../usecases/serverless.html">
|
||
|
||
|
||
5.3 Serverless架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</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.2.3 网络和集群性能测试</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="kubernetes网络和集群性能测试">Kubernetes网络和集群性能测试</h1>
|
||
<h2 id="准备">准备</h2>
|
||
<p><strong>测试环境</strong></p>
|
||
<p>在以下几种环境下进行测试：</p>
|
||
<ul>
|
||
<li>Kubernetes集群node节点上通过Cluster IP方式访问</li>
|
||
<li>Kubernetes集群内部通过service访问</li>
|
||
<li>Kubernetes集群外部通过traefik ingress暴露的地址访问</li>
|
||
</ul>
|
||
<p><strong>测试地址</strong></p>
|
||
<p>Cluster IP: 10.254.149.31</p>
|
||
<p>Service Port：8000</p>
|
||
<p>Ingress Host：traefik.sample-webapp.io</p>
|
||
<p><strong>测试工具</strong></p>
|
||
<ul>
|
||
<li><a href="http://locust.io" target="_blank">Locust</a>：一个简单易用的用户负载测试工具，用来测试web或其他系统能够同时处理的并发用户数。</li>
|
||
<li>curl</li>
|
||
<li><a href="https://github.com/kubernetes/kubernetes/tree/master/test/e2e" target="_blank">kubemark</a></li>
|
||
<li>测试程序：sample-webapp，源码见Github <a href="https://github.com/rootsongjc/distributed-load-testing-using-kubernetes" target="_blank">kubernetes的分布式负载测试</a></li>
|
||
</ul>
|
||
<p><strong>测试说明</strong></p>
|
||
<p>通过向<code>sample-webapp</code>发送curl请求获取响应时间，直接curl后的结果为：</p>
|
||
<pre><code class="lang-Bash">$ curl <span class="hljs-string">"http://10.254.149.31:8000/"</span>
|
||
Welcome to the <span class="hljs-string">"Distributed Load Testing Using Kubernetes"</span> sample web app
|
||
</code></pre>
|
||
<h2 id="网络延迟测试">网络延迟测试</h2>
|
||
<h3 id="场景一、-kubernetes集群node节点上通过cluster-ip访问">场景一、 Kubernetes集群node节点上通过Cluster IP访问</h3>
|
||
<p><strong>测试命令</strong></p>
|
||
<pre><code class="lang-shell">curl -o /dev/null -s -w '%{time_connect} %{time_starttransfer} %{time_total}' "http://10.254.149.31:8000/"
|
||
</code></pre>
|
||
<p><strong>10组测试结果</strong></p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th>No</th>
|
||
<th>time_connect</th>
|
||
<th>time_starttransfer</th>
|
||
<th>time_total</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td>1</td>
|
||
<td>0.000</td>
|
||
<td>0.003</td>
|
||
<td>0.003</td>
|
||
</tr>
|
||
<tr>
|
||
<td>2</td>
|
||
<td>0.000</td>
|
||
<td>0.002</td>
|
||
<td>0.002</td>
|
||
</tr>
|
||
<tr>
|
||
<td>3</td>
|
||
<td>0.000</td>
|
||
<td>0.002</td>
|
||
<td>0.002</td>
|
||
</tr>
|
||
<tr>
|
||
<td>4</td>
|
||
<td>0.000</td>
|
||
<td>0.002</td>
|
||
<td>0.002</td>
|
||
</tr>
|
||
<tr>
|
||
<td>5</td>
|
||
<td>0.000</td>
|
||
<td>0.002</td>
|
||
<td>0.002</td>
|
||
</tr>
|
||
<tr>
|
||
<td>6</td>
|
||
<td>0.000</td>
|
||
<td>0.002</td>
|
||
<td>0.002</td>
|
||
</tr>
|
||
<tr>
|
||
<td>7</td>
|
||
<td>0.000</td>
|
||
<td>0.002</td>
|
||
<td>0.002</td>
|
||
</tr>
|
||
<tr>
|
||
<td>8</td>
|
||
<td>0.000</td>
|
||
<td>0.002</td>
|
||
<td>0.002</td>
|
||
</tr>
|
||
<tr>
|
||
<td>9</td>
|
||
<td>0.000</td>
|
||
<td>0.002</td>
|
||
<td>0.002</td>
|
||
</tr>
|
||
<tr>
|
||
<td>10</td>
|
||
<td>0.000</td>
|
||
<td>0.002</td>
|
||
<td>0.002</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p><strong>平均响应时间：2ms</strong></p>
|
||
<p><strong>时间指标说明</strong></p>
|
||
<p>单位：秒</p>
|
||
<p>time_connect：建立到服务器的 TCP 连接所用的时间</p>
|
||
<p>time_starttransfer：在发出请求之后，Web 服务器返回数据的第一个字节所用的时间</p>
|
||
<p>time_total：完成请求所用的时间</p>
|
||
<h3 id="场景二、kubernetes集群内部通过service访问">场景二、Kubernetes集群内部通过service访问</h3>
|
||
<p><strong>测试命令</strong></p>
|
||
<pre><code class="lang-Shell">curl -o /dev/null -s -w '%{time_connect} %{time_starttransfer} %{time_total}' "http://sample-webapp:8000/"
|
||
</code></pre>
|
||
<p><strong>10组测试结果</strong></p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th>No</th>
|
||
<th>time_connect</th>
|
||
<th>time_starttransfer</th>
|
||
<th>time_total</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td>1</td>
|
||
<td>0.004</td>
|
||
<td>0.006</td>
|
||
<td>0.006</td>
|
||
</tr>
|
||
<tr>
|
||
<td>2</td>
|
||
<td>0.004</td>
|
||
<td>0.006</td>
|
||
<td>0.006</td>
|
||
</tr>
|
||
<tr>
|
||
<td>3</td>
|
||
<td>0.004</td>
|
||
<td>0.006</td>
|
||
<td>0.006</td>
|
||
</tr>
|
||
<tr>
|
||
<td>4</td>
|
||
<td>0.004</td>
|
||
<td>0.006</td>
|
||
<td>0.006</td>
|
||
</tr>
|
||
<tr>
|
||
<td>5</td>
|
||
<td>0.004</td>
|
||
<td>0.006</td>
|
||
<td>0.006</td>
|
||
</tr>
|
||
<tr>
|
||
<td>6</td>
|
||
<td>0.004</td>
|
||
<td>0.006</td>
|
||
<td>0.006</td>
|
||
</tr>
|
||
<tr>
|
||
<td>7</td>
|
||
<td>0.004</td>
|
||
<td>0.006</td>
|
||
<td>0.006</td>
|
||
</tr>
|
||
<tr>
|
||
<td>8</td>
|
||
<td>0.004</td>
|
||
<td>0.006</td>
|
||
<td>0.006</td>
|
||
</tr>
|
||
<tr>
|
||
<td>9</td>
|
||
<td>0.004</td>
|
||
<td>0.006</td>
|
||
<td>0.006</td>
|
||
</tr>
|
||
<tr>
|
||
<td>10</td>
|
||
<td>0.004</td>
|
||
<td>0.006</td>
|
||
<td>0.006</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p><strong>平均响应时间：6ms</strong></p>
|
||
<h3 id="场景三、在公网上通过traefik-ingress访问">场景三、在公网上通过traefik ingress访问</h3>
|
||
<p><strong>测试命令</strong></p>
|
||
<pre><code class="lang-Shell">curl -o /dev/null -s -w '%{time_connect} %{time_starttransfer} %{time_total}' "http://traefik.sample-webapp.io" >>result
|
||
</code></pre>
|
||
<p><strong>10组测试结果</strong></p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th>No</th>
|
||
<th>time_connect</th>
|
||
<th>time_starttransfer</th>
|
||
<th>time_total</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td>1</td>
|
||
<td>0.043</td>
|
||
<td>0.085</td>
|
||
<td>0.085</td>
|
||
</tr>
|
||
<tr>
|
||
<td>2</td>
|
||
<td>0.052</td>
|
||
<td>0.093</td>
|
||
<td>0.093</td>
|
||
</tr>
|
||
<tr>
|
||
<td>3</td>
|
||
<td>0.043</td>
|
||
<td>0.082</td>
|
||
<td>0.082</td>
|
||
</tr>
|
||
<tr>
|
||
<td>4</td>
|
||
<td>0.051</td>
|
||
<td>0.093</td>
|
||
<td>0.093</td>
|
||
</tr>
|
||
<tr>
|
||
<td>5</td>
|
||
<td>0.068</td>
|
||
<td>0.188</td>
|
||
<td>0.188</td>
|
||
</tr>
|
||
<tr>
|
||
<td>6</td>
|
||
<td>0.049</td>
|
||
<td>0.089</td>
|
||
<td>0.089</td>
|
||
</tr>
|
||
<tr>
|
||
<td>7</td>
|
||
<td>0.051</td>
|
||
<td>0.113</td>
|
||
<td>0.113</td>
|
||
</tr>
|
||
<tr>
|
||
<td>8</td>
|
||
<td>0.055</td>
|
||
<td>0.120</td>
|
||
<td>0.120</td>
|
||
</tr>
|
||
<tr>
|
||
<td>9</td>
|
||
<td>0.065</td>
|
||
<td>0.126</td>
|
||
<td>0.127</td>
|
||
</tr>
|
||
<tr>
|
||
<td>10</td>
|
||
<td>0.050</td>
|
||
<td>0.111</td>
|
||
<td>0.111</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p><strong>平均响应时间：110ms</strong></p>
|
||
<h3 id="测试结果">测试结果</h3>
|
||
<p>在这三种场景下的响应时间测试结果如下：</p>
|
||
<ul>
|
||
<li>Kubernetes集群node节点上通过Cluster IP方式访问：2ms</li>
|
||
<li>Kubernetes集群内部通过service访问：6ms</li>
|
||
<li>Kubernetes集群外部通过traefik ingress暴露的地址访问：110ms</li>
|
||
</ul>
|
||
<p><em>注意：执行测试的node节点/Pod与serivce所在的pod的距离（是否在同一台主机上），对前两个场景可以能会有一定影响。</em></p>
|
||
<h2 id="网络性能测试">网络性能测试</h2>
|
||
<p>网络使用flannel的vxlan模式。</p>
|
||
<p>使用iperf进行测试。</p>
|
||
<p>服务端命令：</p>
|
||
<pre><code class="lang-shell">iperf -s -p 12345 -i 1 -M
|
||
</code></pre>
|
||
<p>客户端命令：</p>
|
||
<pre><code class="lang-shell">iperf -c ${server-ip} -p 12345 -i 1 -t 10 -w 20K
|
||
</code></pre>
|
||
<h3 id="场景一、主机之间">场景一、主机之间</h3>
|
||
<pre><code>[ ID] Interval Transfer Bandwidth
|
||
[ 3] 0.0- 1.0 sec 598 MBytes 5.02 Gbits/sec
|
||
[ 3] 1.0- 2.0 sec 637 MBytes 5.35 Gbits/sec
|
||
[ 3] 2.0- 3.0 sec 664 MBytes 5.57 Gbits/sec
|
||
[ 3] 3.0- 4.0 sec 657 MBytes 5.51 Gbits/sec
|
||
[ 3] 4.0- 5.0 sec 641 MBytes 5.38 Gbits/sec
|
||
[ 3] 5.0- 6.0 sec 639 MBytes 5.36 Gbits/sec
|
||
[ 3] 6.0- 7.0 sec 628 MBytes 5.26 Gbits/sec
|
||
[ 3] 7.0- 8.0 sec 649 MBytes 5.44 Gbits/sec
|
||
[ 3] 8.0- 9.0 sec 638 MBytes 5.35 Gbits/sec
|
||
[ 3] 9.0-10.0 sec 652 MBytes 5.47 Gbits/sec
|
||
[ 3] 0.0-10.0 sec 6.25 GBytes 5.37 Gbits/sec
|
||
</code></pre><h3 id="场景二、不同主机的pod之间使用flannel的vxlan模式">场景二、不同主机的Pod之间(使用flannel的vxlan模式)</h3>
|
||
<pre><code>[ ID] Interval Transfer Bandwidth
|
||
[ 3] 0.0- 1.0 sec 372 MBytes 3.12 Gbits/sec
|
||
[ 3] 1.0- 2.0 sec 345 MBytes 2.89 Gbits/sec
|
||
[ 3] 2.0- 3.0 sec 361 MBytes 3.03 Gbits/sec
|
||
[ 3] 3.0- 4.0 sec 397 MBytes 3.33 Gbits/sec
|
||
[ 3] 4.0- 5.0 sec 405 MBytes 3.40 Gbits/sec
|
||
[ 3] 5.0- 6.0 sec 410 MBytes 3.44 Gbits/sec
|
||
[ 3] 6.0- 7.0 sec 404 MBytes 3.39 Gbits/sec
|
||
[ 3] 7.0- 8.0 sec 408 MBytes 3.42 Gbits/sec
|
||
[ 3] 8.0- 9.0 sec 451 MBytes 3.78 Gbits/sec
|
||
[ 3] 9.0-10.0 sec 387 MBytes 3.25 Gbits/sec
|
||
[ 3] 0.0-10.0 sec 3.85 GBytes 3.30 Gbits/sec
|
||
</code></pre><h3 id="场景三、node与非同主机的pod之间（使用flannel的vxlan模式）">场景三、Node与非同主机的Pod之间（使用flannel的vxlan模式）</h3>
|
||
<pre><code>[ ID] Interval Transfer Bandwidth
|
||
[ 3] 0.0- 1.0 sec 372 MBytes 3.12 Gbits/sec
|
||
[ 3] 1.0- 2.0 sec 420 MBytes 3.53 Gbits/sec
|
||
[ 3] 2.0- 3.0 sec 434 MBytes 3.64 Gbits/sec
|
||
[ 3] 3.0- 4.0 sec 409 MBytes 3.43 Gbits/sec
|
||
[ 3] 4.0- 5.0 sec 382 MBytes 3.21 Gbits/sec
|
||
[ 3] 5.0- 6.0 sec 408 MBytes 3.42 Gbits/sec
|
||
[ 3] 6.0- 7.0 sec 403 MBytes 3.38 Gbits/sec
|
||
[ 3] 7.0- 8.0 sec 423 MBytes 3.55 Gbits/sec
|
||
[ 3] 8.0- 9.0 sec 376 MBytes 3.15 Gbits/sec
|
||
[ 3] 9.0-10.0 sec 451 MBytes 3.78 Gbits/sec
|
||
[ 3] 0.0-10.0 sec 3.98 GBytes 3.42 Gbits/sec
|
||
</code></pre><h3 id="场景四、不同主机的pod之间（使用flannel的host-gw模式）">场景四、不同主机的Pod之间（使用flannel的host-gw模式）</h3>
|
||
<pre><code>[ ID] Interval Transfer Bandwidth
|
||
[ 5] 0.0- 1.0 sec 530 MBytes 4.45 Gbits/sec
|
||
[ 5] 1.0- 2.0 sec 576 MBytes 4.84 Gbits/sec
|
||
[ 5] 2.0- 3.0 sec 631 MBytes 5.29 Gbits/sec
|
||
[ 5] 3.0- 4.0 sec 580 MBytes 4.87 Gbits/sec
|
||
[ 5] 4.0- 5.0 sec 627 MBytes 5.26 Gbits/sec
|
||
[ 5] 5.0- 6.0 sec 578 MBytes 4.85 Gbits/sec
|
||
[ 5] 6.0- 7.0 sec 584 MBytes 4.90 Gbits/sec
|
||
[ 5] 7.0- 8.0 sec 571 MBytes 4.79 Gbits/sec
|
||
[ 5] 8.0- 9.0 sec 564 MBytes 4.73 Gbits/sec
|
||
[ 5] 9.0-10.0 sec 572 MBytes 4.80 Gbits/sec
|
||
[ 5] 0.0-10.0 sec 5.68 GBytes 4.88 Gbits/sec
|
||
</code></pre><h3 id="场景五、node与非同主机的pod之间（使用flannel的host-gw模式）">场景五、Node与非同主机的Pod之间（使用flannel的host-gw模式）</h3>
|
||
<pre><code>[ ID] Interval Transfer Bandwidth
|
||
[ 3] 0.0- 1.0 sec 570 MBytes 4.78 Gbits/sec
|
||
[ 3] 1.0- 2.0 sec 552 MBytes 4.63 Gbits/sec
|
||
[ 3] 2.0- 3.0 sec 598 MBytes 5.02 Gbits/sec
|
||
[ 3] 3.0- 4.0 sec 580 MBytes 4.87 Gbits/sec
|
||
[ 3] 4.0- 5.0 sec 590 MBytes 4.95 Gbits/sec
|
||
[ 3] 5.0- 6.0 sec 594 MBytes 4.98 Gbits/sec
|
||
[ 3] 6.0- 7.0 sec 598 MBytes 5.02 Gbits/sec
|
||
[ 3] 7.0- 8.0 sec 606 MBytes 5.08 Gbits/sec
|
||
[ 3] 8.0- 9.0 sec 596 MBytes 5.00 Gbits/sec
|
||
[ 3] 9.0-10.0 sec 604 MBytes 5.07 Gbits/sec
|
||
[ 3] 0.0-10.0 sec 5.75 GBytes 4.94 Gbits/sec
|
||
</code></pre><h3 id="网络性能对比综述">网络性能对比综述</h3>
|
||
<p>使用Flannel的<strong>vxlan</strong>模式实现每个pod一个IP的方式，会比宿主机直接互联的网络性能损耗30%～40%，符合网上流传的测试结论。而flannel的host-gw模式比起宿主机互连的网络性能损耗大约是10%。</p>
|
||
<p>Vxlan会有一个封包解包的过程，所以会对网络性能造成较大的损耗，而host-gw模式是直接使用路由信息，网络损耗小，关于host-gw的架构请访问<a href="https://docs.openshift.com/container-platform/3.4/architecture/additional_concepts/flannel.html" target="_blank">Flannel host-gw architecture</a>。</p>
|
||
<h2 id="kubernete的性能测试">Kubernete的性能测试</h2>
|
||
<p>参考<a href="https://supereagle.github.io/2017/03/09/kubemark/" target="_blank">Kubernetes集群性能测试</a>中的步骤，对kubernetes的性能进行测试。</p>
|
||
<p>我的集群版本是Kubernetes1.6.0，首先克隆代码，将kubernetes目录复制到<code>$GOPATH/src/k8s.io/</code>下然后执行：</p>
|
||
<pre><code class="lang-bash">$ ./hack/generate-bindata.sh
|
||
/usr/<span class="hljs-built_in">local</span>/src/k8s.io/kubernetes /usr/<span class="hljs-built_in">local</span>/src/k8s.io/kubernetes
|
||
Generated bindata file : <span class="hljs-built_in">test</span>/e2e/generated/bindata.go has 13498 <span class="hljs-built_in">test</span>/e2e/generated/bindata.go lines of lovely automated artifacts
|
||
No changes <span class="hljs-keyword">in</span> generated bindata file: pkg/generated/bindata.go
|
||
/usr/<span class="hljs-built_in">local</span>/src/k8s.io/kubernetes
|
||
$ make WHAT=<span class="hljs-string">"test/e2e/e2e.test"</span>
|
||
...
|
||
+++ [0425 17:01:34] Generating bindata:
|
||
<span class="hljs-built_in">test</span>/e2e/generated/gobindata_util.go
|
||
/usr/<span class="hljs-built_in">local</span>/src/k8s.io/kubernetes /usr/<span class="hljs-built_in">local</span>/src/k8s.io/kubernetes/<span class="hljs-built_in">test</span>/e2e/generated
|
||
/usr/<span class="hljs-built_in">local</span>/src/k8s.io/kubernetes/<span class="hljs-built_in">test</span>/e2e/generated
|
||
+++ [0425 17:01:34] Building go targets <span class="hljs-keyword">for</span> linux/amd64:
|
||
<span class="hljs-built_in">test</span>/e2e/e2e.test
|
||
$ make ginkgo
|
||
+++ [0425 17:05:57] Building the toolchain targets:
|
||
k8s.io/kubernetes/hack/cmd/teststale
|
||
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
|
||
+++ [0425 17:05:57] Generating bindata:
|
||
<span class="hljs-built_in">test</span>/e2e/generated/gobindata_util.go
|
||
/usr/<span class="hljs-built_in">local</span>/src/k8s.io/kubernetes /usr/<span class="hljs-built_in">local</span>/src/k8s.io/kubernetes/<span class="hljs-built_in">test</span>/e2e/generated
|
||
/usr/<span class="hljs-built_in">local</span>/src/k8s.io/kubernetes/<span class="hljs-built_in">test</span>/e2e/generated
|
||
+++ [0425 17:05:58] Building go targets <span class="hljs-keyword">for</span> linux/amd64:
|
||
vendor/github.com/onsi/ginkgo/ginkgo
|
||
|
||
$ <span class="hljs-built_in">export</span> KUBERNETES_PROVIDER=<span class="hljs-built_in">local</span>
|
||
$ <span class="hljs-built_in">export</span> KUBECTL_PATH=/usr/bin/kubectl
|
||
$ go run hack/e2e.go -v -test --test_args=<span class="hljs-string">"--host=http://172.20.0.113:8080 --ginkgo.focus=\[Feature:Performance\]"</span> >>log.txt
|
||
</code></pre>
|
||
<p><strong>测试结果</strong></p>
|
||
<pre><code class="lang-bash">Apr 25 18:27:31.461: INFO: API calls latencies: {
|
||
<span class="hljs-string">"apicalls"</span>: [
|
||
{
|
||
<span class="hljs-string">"resource"</span>: <span class="hljs-string">"pods"</span>,
|
||
<span class="hljs-string">"verb"</span>: <span class="hljs-string">"POST"</span>,
|
||
<span class="hljs-string">"latency"</span>: {
|
||
<span class="hljs-string">"Perc50"</span>: 2148000,
|
||
<span class="hljs-string">"Perc90"</span>: 13772000,
|
||
<span class="hljs-string">"Perc99"</span>: 14436000,
|
||
<span class="hljs-string">"Perc100"</span>: 0
|
||
}
|
||
},
|
||
{
|
||
<span class="hljs-string">"resource"</span>: <span class="hljs-string">"services"</span>,
|
||
<span class="hljs-string">"verb"</span>: <span class="hljs-string">"DELETE"</span>,
|
||
<span class="hljs-string">"latency"</span>: {
|
||
<span class="hljs-string">"Perc50"</span>: 9843000,
|
||
<span class="hljs-string">"Perc90"</span>: 11226000,
|
||
<span class="hljs-string">"Perc99"</span>: 12391000,
|
||
<span class="hljs-string">"Perc100"</span>: 0
|
||
}
|
||
},
|
||
...
|
||
Apr 25 18:27:31.461: INFO: [Result:Performance] {
|
||
<span class="hljs-string">"version"</span>: <span class="hljs-string">"v1"</span>,
|
||
<span class="hljs-string">"dataItems"</span>: [
|
||
{
|
||
<span class="hljs-string">"data"</span>: {
|
||
<span class="hljs-string">"Perc50"</span>: 2.148,
|
||
<span class="hljs-string">"Perc90"</span>: 13.772,
|
||
<span class="hljs-string">"Perc99"</span>: 14.436
|
||
},
|
||
<span class="hljs-string">"unit"</span>: <span class="hljs-string">"ms"</span>,
|
||
<span class="hljs-string">"labels"</span>: {
|
||
<span class="hljs-string">"Resource"</span>: <span class="hljs-string">"pods"</span>,
|
||
<span class="hljs-string">"Verb"</span>: <span class="hljs-string">"POST"</span>
|
||
}
|
||
},
|
||
...
|
||
2.857: INFO: Running AfterSuite actions on all node
|
||
Apr 26 10:35:32.857: INFO: Running AfterSuite actions on node 1
|
||
|
||
Ran 2 of 606 Specs <span class="hljs-keyword">in</span> 268.371 seconds
|
||
SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 604 Skipped PASS
|
||
|
||
Ginkgo ran 1 suite <span class="hljs-keyword">in</span> 4m28.667870101s
|
||
Test Suite Passed
|
||
</code></pre>
|
||
<p>从kubemark输出的日志中可以看到<strong>API calls latencies</strong>和<strong>Performance</strong>。</p>
|
||
<p><strong>日志里显示，创建90个pod用时40秒以内，平均创建每个pod耗时0.44秒。</strong></p>
|
||
<h3 id="不同type的资源类型api请求耗时分布">不同type的资源类型API请求耗时分布</h3>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th>Resource</th>
|
||
<th>Verb</th>
|
||
<th>50%</th>
|
||
<th>90%</th>
|
||
<th>99%</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td>services</td>
|
||
<td>DELETE</td>
|
||
<td>8.472ms</td>
|
||
<td>9.841ms</td>
|
||
<td>38.226ms</td>
|
||
</tr>
|
||
<tr>
|
||
<td>endpoints</td>
|
||
<td>PUT</td>
|
||
<td>1.641ms</td>
|
||
<td>3.161ms</td>
|
||
<td>30.715ms</td>
|
||
</tr>
|
||
<tr>
|
||
<td>endpoints</td>
|
||
<td>GET</td>
|
||
<td>931µs</td>
|
||
<td>10.412ms</td>
|
||
<td>27.97ms</td>
|
||
</tr>
|
||
<tr>
|
||
<td>nodes</td>
|
||
<td>PATCH</td>
|
||
<td>4.245ms</td>
|
||
<td>11.117ms</td>
|
||
<td>18.63ms</td>
|
||
</tr>
|
||
<tr>
|
||
<td>pods</td>
|
||
<td>PUT</td>
|
||
<td>2.193ms</td>
|
||
<td>2.619ms</td>
|
||
<td>17.285ms</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p>从<code>log.txt</code>日志中还可以看到更多详细请求的测试指标。</p>
|
||
<figure id="fig1.4.2.3.1"><img src="http://olz1di9xf.bkt.clouddn.com/kubenetes-e2e-test.jpg" alt="kubernetes-dashboard"><figcaption>Figure: kubernetes-dashboard</figcaption></figure>
|
||
<h3 id="注意事项">注意事项</h3>
|
||
<p>测试过程中需要用到docker镜像存储在GCE中，需要翻墙下载，我没看到哪里配置这个镜像的地址。该镜像副本已上传时速云：</p>
|
||
<p>用到的镜像有如下两个：</p>
|
||
<ul>
|
||
<li>gcr.io/google_containers/pause-amd64:3.0</li>
|
||
<li>gcr.io/google_containers/serve_hostname:v1.4</li>
|
||
</ul>
|
||
<p>时速云镜像地址：</p>
|
||
<ul>
|
||
<li>index.tenxcloud.com/jimmy/pause-amd64:3.0</li>
|
||
<li>index.tenxcloud.com/jimmy/serve_hostname:v1.4</li>
|
||
</ul>
|
||
<p>将镜像pull到本地后重新打tag。</p>
|
||
<h2 id="locust测试">Locust测试</h2>
|
||
<p>请求统计</p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th>Method</th>
|
||
<th>Name</th>
|
||
<th># requests</th>
|
||
<th># failures</th>
|
||
<th>Median response time</th>
|
||
<th>Average response time</th>
|
||
<th>Min response time</th>
|
||
<th>Max response time</th>
|
||
<th>Average Content Size</th>
|
||
<th>Requests/s</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td>POST</td>
|
||
<td>/login</td>
|
||
<td>5070</td>
|
||
<td>78</td>
|
||
<td>59000</td>
|
||
<td>80551</td>
|
||
<td>11218</td>
|
||
<td>202140</td>
|
||
<td>54</td>
|
||
<td>1.17</td>
|
||
</tr>
|
||
<tr>
|
||
<td>POST</td>
|
||
<td>/metrics</td>
|
||
<td>5114232</td>
|
||
<td>85879</td>
|
||
<td>63000</td>
|
||
<td>82280</td>
|
||
<td>29518</td>
|
||
<td>331330</td>
|
||
<td>94</td>
|
||
<td>1178.77</td>
|
||
</tr>
|
||
<tr>
|
||
<td>None</td>
|
||
<td>Total</td>
|
||
<td>5119302</td>
|
||
<td>85957</td>
|
||
<td>63000</td>
|
||
<td>82279</td>
|
||
<td>11218</td>
|
||
<td>331330</td>
|
||
<td>94</td>
|
||
<td>1179.94</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p>响应时间分布</p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th>Name</th>
|
||
<th># requests</th>
|
||
<th>50%</th>
|
||
<th>66%</th>
|
||
<th>75%</th>
|
||
<th>80%</th>
|
||
<th>90%</th>
|
||
<th>95%</th>
|
||
<th>98%</th>
|
||
<th>99%</th>
|
||
<th>100%</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td>POST /login</td>
|
||
<td>5070</td>
|
||
<td>59000</td>
|
||
<td>125000</td>
|
||
<td>140000</td>
|
||
<td>148000</td>
|
||
<td>160000</td>
|
||
<td>166000</td>
|
||
<td>174000</td>
|
||
<td>176000</td>
|
||
<td>202140</td>
|
||
</tr>
|
||
<tr>
|
||
<td>POST /metrics</td>
|
||
<td>5114993</td>
|
||
<td>63000</td>
|
||
<td>127000</td>
|
||
<td>142000</td>
|
||
<td>149000</td>
|
||
<td>160000</td>
|
||
<td>166000</td>
|
||
<td>172000</td>
|
||
<td>176000</td>
|
||
<td>331330</td>
|
||
</tr>
|
||
<tr>
|
||
<td>None Total</td>
|
||
<td>5120063</td>
|
||
<td>63000</td>
|
||
<td>127000</td>
|
||
<td>142000</td>
|
||
<td>149000</td>
|
||
<td>160000</td>
|
||
<td>166000</td>
|
||
<td>172000</td>
|
||
<td>176000</td>
|
||
<td>331330</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p>以上两个表格都是瞬时值。请求失败率在2%左右。</p>
|
||
<p>Sample-webapp起了48个pod。</p>
|
||
<p>Locust模拟10万用户，每秒增长100个。</p>
|
||
<figure id="fig1.4.2.3.2"><img src="http://olz1di9xf.bkt.clouddn.com/kubernetes-locust-test.jpg" alt="locust-test"><figcaption>Figure: locust-test</figcaption></figure>
|
||
<p>关于Locust的使用请参考Github：<a href="https://github.com/rootsongjc/distributed-load-testing-using-kubernetes" target="_blank">https://github.com/rootsongjc/distributed-load-testing-using-kubernetes</a></p>
|
||
<h2 id="参考">参考</h2>
|
||
<p><a href="https://testerhome.com/topics/4839" target="_blank">基于 Python 的性能测试工具 locust (与 LR 的简单对比)</a></p>
|
||
<p><a href="http://docs.locust.io/en/latest/what-is-locust.html" target="_blank">Locust docs</a></p>
|
||
<p><a href="http://timd.cn/2015/09/17/locust/" target="_blank">python用户负载测试工具：locust</a></p>
|
||
<p><a href="https://supereagle.github.io/2017/03/09/kubemark/" target="_blank">Kubernetes集群性能测试</a></p>
|
||
<p><a href="http://dockone.io/article/1050" target="_blank">CoreOS是如何将Kubernetes的性能提高10倍的</a></p>
|
||
<p><a href="http://blog.fleeto.us/translation/updates-performance-and-scalability-kubernetes-13-2000-node-60000-pod-clusters" target="_blank">Kubernetes 1.3 的性能和弹性 —— 2000 节点，60,0000 Pod 的集群</a></p>
|
||
<p><a href="http://www.csdn.net/article/2015-07-07/2825155" target="_blank">运用Kubernetes进行分布式负载测试</a></p>
|
||
<p><a href="https://github.com/kubernetes/community/blob/master/contributors/devel/kubemark-guide.md" target="_blank">Kubemark User Guide</a></p>
|
||
<p><a href="https://docs.openshift.com/container-platform/3.4/architecture/additional_concepts/flannel.html" target="_blank">Flannel host-gw architecture</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="distributed-load-test.html" class="navigation navigation-prev " aria-label="Previous page: 4.2.2 分布式负载测试">
|
||
<i class="fa fa-angle-left"></i>
|
||
</a>
|
||
|
||
|
||
<a href="edge-node-configuration.html" class="navigation navigation-next " aria-label="Next page: 4.2.4 边缘节点配置">
|
||
<i class="fa fa-angle-right"></i>
|
||
</a>
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<script>
|
||
var gitbook = gitbook || [];
|
||
gitbook.push(function() {
|
||
gitbook.page.hasChanged({"page":{"title":"4.2.3 网络和集群性能测试","level":"1.4.2.3","depth":3,"next":{"title":"4.2.4 边缘节点配置","level":"1.4.2.4","depth":3,"path":"practice/edge-node-configuration.md","ref":"practice/edge-node-configuration.md","articles":[]},"previous":{"title":"4.2.2 分布式负载测试","level":"1.4.2.2","depth":3,"path":"practice/distributed-load-test.md","ref":"practice/distributed-load-test.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.html#fig1.2.1.1","level":"1.2.1","list_caption":"Figure: 分层架构示意图","alt":"分层架构示意图","nro":7,"url":"../images/kubernetes-layers-arch.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"分层架构示意图","attributes":{},"skip":false,"key":"1.2.1.1"},{"backlink":"concepts/pod-overview.html#fig1.2.2.1.1","level":"1.2.2.1","list_caption":"Figure: pod diagram","alt":"pod diagram","nro":8,"url":"../images/pod-overview.png","index":1,"caption_template":"Figure: _CAPTION_","label":"pod diagram","attributes":{},"skip":false,"key":"1.2.2.1.1"},{"backlink":"concepts/pod.html#fig1.2.2.1.1.1","level":"1.2.2.1.1","list_caption":"Figure: Pod示意图","alt":"Pod示意图","nro":9,"url":"../images/pod-overview.png","index":1,"caption_template":"Figure: _CAPTION_","label":"Pod示意图","attributes":{},"skip":false,"key":"1.2.2.1.1.1"},{"backlink":"concepts/pod.html#fig1.2.2.1.1.2","level":"1.2.2.1.1","list_caption":"Figure: Pod Cheatsheet","alt":"Pod Cheatsheet","nro":10,"url":"../images/kubernetes-pod-cheatsheet.png","index":2,"caption_template":"Figure: _CAPTION_","label":"Pod Cheatsheet","attributes":{},"skip":false,"key":"1.2.2.1.1.2"},{"backlink":"concepts/service.html#fig1.2.2.4.1","level":"1.2.2.4","list_caption":"Figure: userspace代理模式下Service概览图","alt":"userspace代理模式下Service概览图","nro":11,"url":"https://d33wubrfki0l68.cloudfront.net/b8e1022c2dd815d8dd36b1bc4f0cc3ad870a924f/1dd12/images/docs/services-userspace-overview.svg","index":1,"caption_template":"Figure: _CAPTION_","label":"userspace代理模式下Service概览图","attributes":{},"skip":false,"key":"1.2.2.4.1"},{"backlink":"concepts/service.html#fig1.2.2.4.2","level":"1.2.2.4","list_caption":"Figure: iptables代理模式下Service概览图","alt":"iptables代理模式下Service概览图","nro":12,"url":"https://d33wubrfki0l68.cloudfront.net/837afa5715eb31fb9ca6516ec6863e810f437264/42951/images/docs/services-iptables-overview.svg","index":2,"caption_template":"Figure: _CAPTION_","label":"iptables代理模式下Service概览图","attributes":{},"skip":false,"key":"1.2.2.4.2"},{"backlink":"concepts/deployment.html#fig1.2.2.6.1","level":"1.2.2.6","list_caption":"Figure: kubernetes deployment cheatsheet","alt":"kubernetes deployment cheatsheet","nro":13,"url":"../images/deployment-cheatsheet.png","index":1,"caption_template":"Figure: _CAPTION_","label":"kubernetes deployment cheatsheet","attributes":{},"skip":false,"key":"1.2.2.6.1"},{"backlink":"concepts/horizontal-pod-autoscaling.html#fig1.2.2.16.1","level":"1.2.2.16","list_caption":"Figure: horizontal-pod-autoscaler","alt":"horizontal-pod-autoscaler","nro":14,"url":"../images/horizontal-pod-autoscaler.png","index":1,"caption_template":"Figure: _CAPTION_","label":"horizontal-pod-autoscaler","attributes":{},"skip":false,"key":"1.2.2.16.1"},{"backlink":"concepts/label.html#fig1.2.2.17.1","level":"1.2.2.17","list_caption":"Figure: label示意图","alt":"label示意图","nro":15,"url":"../images/labels.png","index":1,"caption_template":"Figure: _CAPTION_","label":"label示意图","attributes":{},"skip":false,"key":"1.2.2.17.1"},{"backlink":"guide/using-kubectl.html#fig1.3.2.1.1","level":"1.3.2.1","list_caption":"Figure: kubectl cheatsheet","alt":"kubectl cheatsheet","nro":16,"url":"../images/kubernetes-kubectl-cheatsheet.png","index":1,"caption_template":"Figure: _CAPTION_","label":"kubectl cheatsheet","attributes":{},"skip":false,"key":"1.3.2.1.1"},{"backlink":"guide/using-kubectl.html#fig1.3.2.1.2","level":"1.3.2.1","list_caption":"Figure: kube-shell页面","alt":"kube-shell页面","nro":17,"url":"../images/kube-shell.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"kube-shell页面","attributes":{},"skip":false,"key":"1.3.2.1.2"},{"backlink":"guide/ip-masq-agent.html#fig1.3.3.6.1","level":"1.3.3.6","list_caption":"Figure: IP伪装代理示意图","alt":"IP伪装代理示意图","nro":18,"url":"../images/ip-masq.png","index":1,"caption_template":"Figure: _CAPTION_","label":"IP伪装代理示意图","attributes":{},"skip":false,"key":"1.3.3.6.1"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig1.3.5.1.1","level":"1.3.5.1","list_caption":"Figure: API","alt":"API","nro":19,"url":"../images/k8s-app-monitor-test-api-doc.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"API","attributes":{},"skip":false,"key":"1.3.5.1.1"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig1.3.5.1.2","level":"1.3.5.1","list_caption":"Figure: wercker","alt":"wercker","nro":20,"url":"../images/k8s-app-monitor-agent-wercker.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"wercker","attributes":{},"skip":false,"key":"1.3.5.1.2"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig1.3.5.1.3","level":"1.3.5.1","list_caption":"Figure: 图表","alt":"图表","nro":21,"url":"../images/k8s-app-monitor-agent.jpg","index":3,"caption_template":"Figure: _CAPTION_","label":"图表","attributes":{},"skip":false,"key":"1.3.5.1.3"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig1.3.5.2.1","level":"1.3.5.2","list_caption":"Figure: spark on yarn with kubernetes","alt":"spark on yarn with kubernetes","nro":22,"url":"../images/spark-on-yarn-with-kubernetes.png","index":1,"caption_template":"Figure: _CAPTION_","label":"spark on yarn with kubernetes","attributes":{},"skip":false,"key":"1.3.5.2.1"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig1.3.5.2.2","level":"1.3.5.2","list_caption":"Figure: Terms","alt":"Terms","nro":23,"url":"../images/terms-in-kubernetes-app-deployment.png","index":2,"caption_template":"Figure: _CAPTION_","label":"Terms","attributes":{},"skip":false,"key":"1.3.5.2.2"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig1.3.5.2.3","level":"1.3.5.2","list_caption":"Figure: 分解步骤解析","alt":"分解步骤解析","nro":24,"url":"../images/migrating-hadoop-yarn-to-kubernetes.png","index":3,"caption_template":"Figure: _CAPTION_","label":"分解步骤解析","attributes":{},"skip":false,"key":"1.3.5.2.3"},{"backlink":"practice/node-installation.html#fig1.4.1.6.1","level":"1.4.1.6","list_caption":"Figure: welcome-nginx","alt":"welcome-nginx","nro":25,"url":"http://olz1di9xf.bkt.clouddn.com/kubernetes-installation-test-nginx.png","index":1,"caption_template":"Figure: _CAPTION_","label":"welcome-nginx","attributes":{},"skip":false,"key":"1.4.1.6.1"},{"backlink":"practice/dashboard-addon-installation.html#fig1.4.1.8.1","level":"1.4.1.8","list_caption":"Figure: kubernetes-dashboard","alt":"kubernetes-dashboard","nro":26,"url":"http://olz1di9xf.bkt.clouddn.com/kubernetes-dashboard-raw.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"kubernetes-dashboard","attributes":{},"skip":false,"key":"1.4.1.8.1"},{"backlink":"practice/heapster-addon-installation.html#fig1.4.1.9.1","level":"1.4.1.9","list_caption":"Figure: dashboard-heapster","alt":"dashboard-heapster","nro":27,"url":"../images/kubernetes-dashboard-with-heapster.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"dashboard-heapster","attributes":{},"skip":false,"key":"1.4.1.9.1"},{"backlink":"practice/heapster-addon-installation.html#fig1.4.1.9.2","level":"1.4.1.9","list_caption":"Figure: grafana","alt":"grafana","nro":28,"url":"../images/kubernetes-heapster-grafana.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"grafana","attributes":{},"skip":false,"key":"1.4.1.9.2"},{"backlink":"practice/heapster-addon-installation.html#fig1.4.1.9.3","level":"1.4.1.9","list_caption":"Figure: kubernetes-influxdb-heapster","alt":"kubernetes-influxdb-heapster","nro":29,"url":"../images/kubernetes-influxdb-heapster.jpg","index":3,"caption_template":"Figure: _CAPTION_","label":"kubernetes-influxdb-heapster","attributes":{},"skip":false,"key":"1.4.1.9.3"},{"backlink":"practice/efk-addon-installation.html#fig1.4.1.10.1","level":"1.4.1.10","list_caption":"Figure: es-setting","alt":"es-setting","nro":30,"url":"../images/es-setting.png","index":1,"caption_template":"Figure: _CAPTION_","label":"es-setting","attributes":{},"skip":false,"key":"1.4.1.10.1"},{"backlink":"practice/efk-addon-installation.html#fig1.4.1.10.2","level":"1.4.1.10","list_caption":"Figure: es-home","alt":"es-home","nro":31,"url":"../images/kubernetes-efk-kibana.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"es-home","attributes":{},"skip":false,"key":"1.4.1.10.2"},{"backlink":"practice/traefik-ingress-installation.html#fig1.4.2.1.1","level":"1.4.2.1","list_caption":"Figure: kubernetes-dashboard","alt":"kubernetes-dashboard","nro":32,"url":"../images/traefik-dashboard.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"kubernetes-dashboard","attributes":{},"skip":false,"key":"1.4.2.1.1"},{"backlink":"practice/traefik-ingress-installation.html#fig1.4.2.1.2","level":"1.4.2.1","list_caption":"Figure: traefik-nginx","alt":"traefik-nginx","nro":33,"url":"../images/traefik-nginx.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"traefik-nginx","attributes":{},"skip":false,"key":"1.4.2.1.2"},{"backlink":"practice/traefik-ingress-installation.html#fig1.4.2.1.3","level":"1.4.2.1","list_caption":"Figure: traefik-guestbook","alt":"traefik-guestbook","nro":34,"url":"../images/traefik-guestbook.jpg","index":3,"caption_template":"Figure: _CAPTION_","label":"traefik-guestbook","attributes":{},"skip":false,"key":"1.4.2.1.3"},{"backlink":"practice/distributed-load-test.html#fig1.4.2.2.1","level":"1.4.2.2","list_caption":"Figure: traefik-dashboard-locust","alt":"traefik-dashboard-locust","nro":35,"url":"../images/traefik-dashboard-locust.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"traefik-dashboard-locust","attributes":{},"skip":false,"key":"1.4.2.2.1"},{"backlink":"practice/distributed-load-test.html#fig1.4.2.2.2","level":"1.4.2.2","list_caption":"Figure: locust-start-swarming","alt":"locust-start-swarming","nro":36,"url":"../images/locust-start-swarming.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"locust-start-swarming","attributes":{},"skip":false,"key":"1.4.2.2.2"},{"backlink":"practice/distributed-load-test.html#fig1.4.2.2.3","level":"1.4.2.2","list_caption":"Figure: sample-webapp-rc","alt":"sample-webapp-rc","nro":37,"url":"../images/sample-webapp-rc.jpg","index":3,"caption_template":"Figure: _CAPTION_","label":"sample-webapp-rc","attributes":{},"skip":false,"key":"1.4.2.2.3"},{"backlink":"practice/distributed-load-test.html#fig1.4.2.2.4","level":"1.4.2.2","list_caption":"Figure: locust-dashboard","alt":"locust-dashboard","nro":38,"url":"../images/locust-dashboard.jpg","index":4,"caption_template":"Figure: _CAPTION_","label":"locust-dashboard","attributes":{},"skip":false,"key":"1.4.2.2.4"},{"backlink":"practice/network-and-cluster-perfermance-test.html#fig1.4.2.3.1","level":"1.4.2.3","list_caption":"Figure: kubernetes-dashboard","alt":"kubernetes-dashboard","nro":39,"url":"http://olz1di9xf.bkt.clouddn.com/kubenetes-e2e-test.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"kubernetes-dashboard","attributes":{},"skip":false,"key":"1.4.2.3.1"},{"backlink":"practice/network-and-cluster-perfermance-test.html#fig1.4.2.3.2","level":"1.4.2.3","list_caption":"Figure: locust-test","alt":"locust-test","nro":40,"url":"http://olz1di9xf.bkt.clouddn.com/kubernetes-locust-test.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"locust-test","attributes":{},"skip":false,"key":"1.4.2.3.2"},{"backlink":"practice/edge-node-configuration.html#fig1.4.2.4.1","level":"1.4.2.4","list_caption":"Figure: 边缘节点架构","alt":"边缘节点架构","nro":41,"url":"../images/kubernetes-edge-node-architecture.png","index":1,"caption_template":"Figure: _CAPTION_","label":"边缘节点架构","attributes":{},"skip":false,"key":"1.4.2.4.1"},{"backlink":"practice/app-log-collection.html#fig1.4.3.2.1","level":"1.4.3.2","list_caption":"Figure: logstash日志收集架构图","alt":"logstash日志收集架构图","nro":42,"url":"../images/filebeat-log-collector.png","index":1,"caption_template":"Figure: _CAPTION_","label":"logstash日志收集架构图","attributes":{},"skip":false,"key":"1.4.3.2.1"},{"backlink":"practice/app-log-collection.html#fig1.4.3.2.2","level":"1.4.3.2","list_caption":"Figure: Kibana页面","alt":"Kibana页面","nro":43,"url":"../images/filebeat-docker-test.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"Kibana页面","attributes":{},"skip":false,"key":"1.4.3.2.2"},{"backlink":"practice/app-log-collection.html#fig1.4.3.2.3","level":"1.4.3.2","list_caption":"Figure: filebeat收集的日志详细信息","alt":"filebeat收集的日志详细信息","nro":44,"url":"../images/kubernetes-filebeat-detail.png","index":3,"caption_template":"Figure: _CAPTION_","label":"filebeat收集的日志详细信息","attributes":{},"skip":false,"key":"1.4.3.2.3"},{"backlink":"practice/monitor.html#fig1.4.3.4.1","level":"1.4.3.4","list_caption":"Figure: Kubernetes集群中的监控","alt":"Kubernetes集群中的监控","nro":45,"url":"../images/monitoring-in-kubernetes.png","index":1,"caption_template":"Figure: _CAPTION_","label":"Kubernetes集群中的监控","attributes":{},"skip":false,"key":"1.4.3.4.1"},{"backlink":"practice/monitor.html#fig1.4.3.4.2","level":"1.4.3.4","list_caption":"Figure: kubernetes的容器命名规则示意图","alt":"kubernetes的容器命名规则示意图","nro":46,"url":"../images/kubernetes-container-naming-rule.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"kubernetes的容器命名规则示意图","attributes":{},"skip":false,"key":"1.4.3.4.2"},{"backlink":"practice/monitor.html#fig1.4.3.4.3","level":"1.4.3.4","list_caption":"Figure: Heapster架构图（改进版）","alt":"Heapster架构图（改进版）","nro":47,"url":"../images/kubernetes-heapster-monitoring.png","index":3,"caption_template":"Figure: _CAPTION_","label":"Heapster架构图（改进版）","attributes":{},"skip":false,"key":"1.4.3.4.3"},{"backlink":"practice/monitor.html#fig1.4.3.4.4","level":"1.4.3.4","list_caption":"Figure: 应用监控架构图","alt":"应用监控架构图","nro":48,"url":"../images/kubernetes-app-monitoring.png","index":4,"caption_template":"Figure: _CAPTION_","label":"应用监控架构图","attributes":{},"skip":false,"key":"1.4.3.4.4"},{"backlink":"practice/monitor.html#fig1.4.3.4.5","level":"1.4.3.4","list_caption":"Figure: 应用拓扑图","alt":"应用拓扑图","nro":49,"url":"../images/weave-scope-service-topology.jpg","index":5,"caption_template":"Figure: _CAPTION_","label":"应用拓扑图","attributes":{},"skip":false,"key":"1.4.3.4.5"},{"backlink":"practice/jenkins-ci-cd.html#fig1.4.3.5.1","level":"1.4.3.5","list_caption":"Figure: 基于Jenkins的持续集成与发布","alt":"基于Jenkins的持续集成与发布","nro":50,"url":"../images/kubernetes-jenkins-ci-cd.png","index":1,"caption_template":"Figure: _CAPTION_","label":"基于Jenkins的持续集成与发布","attributes":{},"skip":false,"key":"1.4.3.5.1"},{"backlink":"practice/data-persistence-problem.html#fig1.4.3.6.1","level":"1.4.3.6","list_caption":"Figure: 日志持久化收集解决方案示意图","alt":"日志持久化收集解决方案示意图","nro":51,"url":"../images/log-persistence-logstash.png","index":1,"caption_template":"Figure: _CAPTION_","label":"日志持久化收集解决方案示意图","attributes":{},"skip":false,"key":"1.4.3.6.1"},{"backlink":"practice/storage-for-containers-using-glusterfs-with-openshift.html#fig1.4.4.1.2.1","level":"1.4.4.1.2","list_caption":"Figure: Screen Shot 2017-03-23 at 21.50.34","alt":"Screen Shot 2017-03-23 at 21.50.34","nro":52,"url":"https://keithtenzer.files.wordpress.com/2017/03/screen-shot-2017-03-23-at-21-50-34.png?w=440","index":1,"caption_template":"Figure: _CAPTION_","label":"Screen Shot 2017-03-23 at 21.50.34","attributes":{},"skip":false,"key":"1.4.4.1.2.1"},{"backlink":"practice/storage-for-containers-using-glusterfs-with-openshift.html#fig1.4.4.1.2.2","level":"1.4.4.1.2","list_caption":"Figure: Screen Shot 2017-03-24 at 11.09.34.png","alt":"Screen Shot 2017-03-24 at 11.09.34.png","nro":53,"url":"https://keithtenzer.files.wordpress.com/2017/03/screen-shot-2017-03-24-at-11-09-341.png?w=440","index":2,"caption_template":"Figure: _CAPTION_","label":"Screen Shot 2017-03-24 at 11.09.34.png","attributes":{},"skip":false,"key":"1.4.4.1.2.2"},{"backlink":"usecases/istio.html#fig1.5.1.1.1","level":"1.5.1.1","list_caption":"Figure: Istio架构图","alt":"Istio架构图","nro":54,"url":"../images/istio-arch.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"Istio架构图","attributes":{},"skip":false,"key":"1.5.1.1.1"},{"backlink":"usecases/istio-installation.html#fig1.5.1.1.1.1","level":"1.5.1.1.1","list_caption":"Figure: BookInfo Sample应用架构图","alt":"BookInfo Sample应用架构图","nro":55,"url":"../images/bookinfo-sample-arch.png","index":1,"caption_template":"Figure: _CAPTION_","label":"BookInfo Sample应用架构图","attributes":{},"skip":false,"key":"1.5.1.1.1.1"},{"backlink":"usecases/istio-installation.html#fig1.5.1.1.1.2","level":"1.5.1.1.1","list_caption":"Figure: BookInfo Sample页面","alt":"BookInfo Sample页面","nro":56,"url":"../images/bookinfo-sample.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"BookInfo Sample页面","attributes":{},"skip":false,"key":"1.5.1.1.1.2"},{"backlink":"usecases/istio-installation.html#fig1.5.1.1.1.3","level":"1.5.1.1.1","list_caption":"Figure: Istio Grafana界面","alt":"Istio Grafana界面","nro":57,"url":"../images/istio-grafana.jpg","index":3,"caption_template":"Figure: _CAPTION_","label":"Istio Grafana界面","attributes":{},"skip":false,"key":"1.5.1.1.1.3"},{"backlink":"usecases/istio-installation.html#fig1.5.1.1.1.4","level":"1.5.1.1.1","list_caption":"Figure: Prometheus页面","alt":"Prometheus页面","nro":58,"url":"../images/istio-prometheus.jpg","index":4,"caption_template":"Figure: _CAPTION_","label":"Prometheus页面","attributes":{},"skip":false,"key":"1.5.1.1.1.4"},{"backlink":"usecases/istio-installation.html#fig1.5.1.1.1.5","level":"1.5.1.1.1","list_caption":"Figure: Zipkin页面","alt":"Zipkin页面","nro":59,"url":"../images/istio-zipkin.jpg","index":5,"caption_template":"Figure: _CAPTION_","label":"Zipkin页面","attributes":{},"skip":false,"key":"1.5.1.1.1.5"},{"backlink":"usecases/istio-installation.html#fig1.5.1.1.1.6","level":"1.5.1.1.1","list_caption":"Figure: ServiceGraph页面","alt":"ServiceGraph页面","nro":60,"url":"../images/istio-servicegraph.jpg","index":6,"caption_template":"Figure: _CAPTION_","label":"ServiceGraph页面","attributes":{},"skip":false,"key":"1.5.1.1.1.6"},{"backlink":"usecases/linkerd.html#fig1.5.1.2.1","level":"1.5.1.2","list_caption":"Figure: source https://linkerd.io","alt":"source https://linkerd.io","nro":61,"url":"https://linkerd.io/images/diagram-individual-instance.png","index":1,"caption_template":"Figure: _CAPTION_","label":"source https://linkerd.io","attributes":{},"skip":false,"key":"1.5.1.2.1"},{"backlink":"usecases/linkerd-user-guide.html#fig1.5.1.2.1.1","level":"1.5.1.2.1","list_caption":"Figure: Jenkins pipeline","alt":"Jenkins pipeline","nro":62,"url":"../images/linkerd-jenkins-pipeline.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"Jenkins pipeline","attributes":{},"skip":false,"key":"1.5.1.2.1.1"},{"backlink":"usecases/linkerd-user-guide.html#fig1.5.1.2.1.2","level":"1.5.1.2.1","list_caption":"Figure: Jenkins config","alt":"Jenkins config","nro":63,"url":"../images/linkerd-jenkins.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"Jenkins config","attributes":{},"skip":false,"key":"1.5.1.2.1.2"},{"backlink":"usecases/linkerd-user-guide.html#fig1.5.1.2.1.3","level":"1.5.1.2.1","list_caption":"Figure: namerd","alt":"namerd","nro":64,"url":"../images/namerd-internal.jpg","index":3,"caption_template":"Figure: _CAPTION_","label":"namerd","attributes":{},"skip":false,"key":"1.5.1.2.1.3"},{"backlink":"usecases/linkerd-user-guide.html#fig1.5.1.2.1.4","level":"1.5.1.2.1","list_caption":"Figure: linkerd监控","alt":"linkerd监控","nro":65,"url":"../images/linkerd-helloworld-outgoing.jpg","index":4,"caption_template":"Figure: _CAPTION_","label":"linkerd监控","attributes":{},"skip":false,"key":"1.5.1.2.1.4"},{"backlink":"usecases/linkerd-user-guide.html#fig1.5.1.2.1.5","level":"1.5.1.2.1","list_caption":"Figure: linkerd监控","alt":"linkerd监控","nro":66,"url":"../images/linkerd-helloworld-incoming.jpg","index":5,"caption_template":"Figure: _CAPTION_","label":"linkerd监控","attributes":{},"skip":false,"key":"1.5.1.2.1.5"},{"backlink":"usecases/linkerd-user-guide.html#fig1.5.1.2.1.6","level":"1.5.1.2.1","list_caption":"Figure: linkerd性能监控","alt":"linkerd性能监控","nro":67,"url":"../images/linkerd-grafana.png","index":6,"caption_template":"Figure: _CAPTION_","label":"linkerd性能监控","attributes":{},"skip":false,"key":"1.5.1.2.1.6"},{"backlink":"usecases/linkerd-user-guide.html#fig1.5.1.2.1.7","level":"1.5.1.2.1","list_caption":"Figure: Linkerd ingress controller","alt":"Linkerd ingress controller","nro":68,"url":"../images/linkerd-ingress-controller.jpg","index":7,"caption_template":"Figure: _CAPTION_","label":"Linkerd ingress controller","attributes":{},"skip":false,"key":"1.5.1.2.1.7"},{"backlink":"usecases/service-discovery-in-microservices.html#fig1.5.1.3.1","level":"1.5.1.3","list_caption":"Figure: 微服务中的服务发现","alt":"微服务中的服务发现","nro":69,"url":"../images/service-discovery-in-microservices.png","index":1,"caption_template":"Figure: _CAPTION_","label":"微服务中的服务发现","attributes":{},"skip":false,"key":"1.5.1.3.1"},{"backlink":"usecases/spark-standalone-on-kubernetes.html#fig1.5.2.1.1","level":"1.5.2.1","list_caption":"Figure: spark master ui","alt":"spark master ui","nro":70,"url":"../images/spark-ui.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"spark master ui","attributes":{},"skip":false,"key":"1.5.2.1.1"},{"backlink":"usecases/spark-standalone-on-kubernetes.html#fig1.5.2.1.2","level":"1.5.2.1","list_caption":"Figure: zeppelin ui","alt":"zeppelin ui","nro":71,"url":"../images/zeppelin-ui.jpg","index":2,"caption_template":"Figure: _CAPTION_","label":"zeppelin ui","attributes":{},"skip":false,"key":"1.5.2.1.2"},{"backlink":"develop/client-go-sample.html#fig1.6.3.1","level":"1.6.3","list_caption":"Figure: 使用kubernetes dashboard进行故障排查","alt":"使用kubernetes dashboard进行故障排查","nro":72,"url":"../images/kubernetes-client-go-sample-update.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"使用kubernetes dashboard进行故障排查","attributes":{},"skip":false,"key":"1.6.3.1"},{"backlink":"appendix/issues.html#fig1.7.2.1","level":"1.7.2","list_caption":"Figure: pvc-storage-limit","alt":"pvc-storage-limit","nro":73,"url":"../images/pvc-storage-limit.jpg","index":1,"caption_template":"Figure: _CAPTION_","label":"pvc-storage-limit","attributes":{},"skip":false,"key":"1.7.2.1"}]},"title":"Kubernetes Handbook","language":"zh-cn","gitbook":"*","description":"Let's play fun with kubernetes!","image-captions":{"caption":"图片 - _CAPTION_"}},"file":{"path":"practice/network-and-cluster-perfermance-test.md","mtime":"2017-08-21T10:23:35.000Z","type":"markdown"},"gitbook":{"version":"3.2.2","time":"2017-09-16T12:56:07.221Z"},"basePath":"..","book":{"language":""}});
|
||
});
|
||
</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>
|
||
|