2080 lines
89 KiB
HTML
2080 lines
89 KiB
HTML
|
|
||
|
<!DOCTYPE HTML>
|
||
|
<html lang="zh-hans" >
|
||
|
<head>
|
||
|
<meta charset="UTF-8">
|
||
|
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
|
||
|
<title>4.3.9 使用Heapster获取集群和对象的metric数据 · 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-back-to-top-button/plugin.css">
|
||
|
|
||
|
|
||
|
|
||
|
<link rel="stylesheet" href="../gitbook/gitbook-plugin-search-plus/search.css">
|
||
|
|
||
|
|
||
|
|
||
|
<link rel="stylesheet" href="../gitbook/gitbook-plugin-tbfed-pagefooter/footer.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="storage.html" />
|
||
|
|
||
|
|
||
|
<link rel="prev" href="using-prometheus-to-monitor-kuberentes-cluster.html" />
|
||
|
|
||
|
|
||
|
|
||
|
<link rel="shortcut icon" href='../favicon.ico' type="image/x-icon">
|
||
|
|
||
|
|
||
|
<link rel="bookmark" href='../favicon.ico' type="image/x-icon">
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
<style>
|
||
|
@media only screen and (max-width: 640px) {
|
||
|
.book-header .hidden-mobile {
|
||
|
display: none;
|
||
|
}
|
||
|
}
|
||
|
</style>
|
||
|
<script>
|
||
|
window["gitbook-plugin-github-buttons"] = {"repo":"rootsongjc/kubernetes-handbook","types":["star"],"size":"small"};
|
||
|
</script>
|
||
|
|
||
|
</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>
|
||
|
<a href="https://jimmysong.io" target="_blank" class="custom-link">Home</a>
|
||
|
</li>
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
<li class="divider"></li>
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
<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>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.1.4" data-path="../concepts/pod-lifecycle.html">
|
||
|
|
||
|
<a href="../concepts/pod-lifecycle.html">
|
||
|
|
||
|
|
||
|
2.2.1.4 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>
|
||
|
|
||
|
<li class="chapter " data-level="1.3.1.3" data-path="../guide/secret-configuration.html">
|
||
|
|
||
|
<a href="../guide/secret-configuration.html">
|
||
|
|
||
|
|
||
|
3.1.3 Secret配置
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.3.1.4" data-path="../guide/resource-quota-management.html">
|
||
|
|
||
|
<a href="../guide/resource-quota-management.html">
|
||
|
|
||
|
|
||
|
3.2.3 管理namespace中的资源配额
|
||
|
|
||
|
</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 " 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>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.3.8" data-path="using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
|
||
|
<a href="using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
|
||
|
|
||
|
4.3.8 使用Prometheus监控kubernetes集群
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter active" data-level="1.4.3.9" data-path="using-heapster-to-get-object-metrics.html">
|
||
|
|
||
|
<a href="using-heapster-to-get-object-metrics.html">
|
||
|
|
||
|
|
||
|
4.3.9 使用Heapster获取集群和对象的metric数据
|
||
|
|
||
|
</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/service-discovery-in-microservices.html">
|
||
|
|
||
|
<a href="../usecases/service-discovery-in-microservices.html">
|
||
|
|
||
|
|
||
|
5.1.1 微服务中的服务发现
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.5.2" data-path="../usecases/service-mesh.html">
|
||
|
|
||
|
<a href="../usecases/service-mesh.html">
|
||
|
|
||
|
|
||
|
5.2 Service Mesh 服务网格
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.5.2.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.2.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.2.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.2.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.2.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>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.5.3" 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.3.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.3.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.4" 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>
|
||
|
|
||
|
<li class="chapter " data-level="1.7.4" data-path="../appendix/debug-kubernetes-services.html">
|
||
|
|
||
|
<a href="../appendix/debug-kubernetes-services.html">
|
||
|
|
||
|
|
||
|
7.4 kubernetes service中的故障排查
|
||
|
|
||
|
</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.9 使用Heapster获取集群和对象的metric数据</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="使用heapster获取集群对象的metric数据">使用Heapster获取集群对象的metric数据</h1>
|
||
|
<p>Heapster作为kubernetes安装过程中默认安装的一个插件,见<a href="practice/heapster-addon-installation.md">安装heapster插件</a>。这对于集群监控十分有用,同时在<a href="../concepts/horizontal-pod-autoscaling.html">Horizontal Pod Autoscaling</a>中也用到了,HPA将Heapster作为<code>Resource Metrics API</code>,向其获取metric,做法是在<code>kube-controller-manager</code> 中配置<code>--api-server</code>指向<a href="https://github.com/kubernetes/kube-aggregator" target="_blank">kube-aggregator</a>,也可以使用heapster来实现,通过在启动heapster的时候指定<code>--api-server=true</code>。</p>
|
||
|
<p>Heapster可以收集Node节点上的cAdvisor数据,还可以按照kubernetes的资源类型来集合资源,比如Pod、Namespace域,可以分别获取它们的CPU、内存、网络和磁盘的metric。默认的metric数据聚合时间间隔是1分钟。</p>
|
||
|
<h2 id="架构">架构</h2>
|
||
|
<p>下面是Heapster架构图:</p>
|
||
|
<figure id="fig1.4.3.9.1"><img src="../images/heapster-architecture.png" alt="Heapster架构图"><figcaption>图片 - Heapster架构图</figcaption></figure>
|
||
|
<p><a href="https://github.com/kubernetes/heapster" target="_blank">Heapser</a>是用Go语言开发Kubernetes集群计算资源使用情况的数据采集工具,编译后可以直接以一个二进制文件运行,通过向heapster传递的参数来指定数据采集行为,这些数据可以选择多种sink方式,例如Graphite、influxDB、OpenTSDB、ElasticSearch、Kafka等。</p>
|
||
|
<h2 id="使用案例">使用案例</h2>
|
||
|
<p>Heapster使用起来很简单,本身就是二进制文件,直接使用命令行启动,也可以放在容器里运行,在作为kubernetes插件运行时,我们是直接放在容器中的,见<a href="practice/heapster-addon-installation.md">安装heapster插件</a>。</p>
|
||
|
<h3 id="运行">运行</h3>
|
||
|
<p>下面是heapster的启动参数:</p>
|
||
|
<table>
|
||
|
<thead>
|
||
|
<tr>
|
||
|
<th><strong>Flag</strong></th>
|
||
|
<th><strong>Description</strong></th>
|
||
|
</tr>
|
||
|
</thead>
|
||
|
<tbody>
|
||
|
<tr>
|
||
|
<td>--allowed-users string</td>
|
||
|
<td>comma-separated list of allowed users</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--alsologtostderr</td>
|
||
|
<td>log to standard error as well as files</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--api-server</td>
|
||
|
<td>Enable API server for the Metrics API. If set, the Metrics API will be served on --insecure-port (internally) and --secure-port (externally).</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--authentication-kubeconfig string</td>
|
||
|
<td>kubeconfig file pointing at the 'core' kubernetes server with enough rights to create <a href="http://tokenaccessreviews.authentication.k8s.io" target="_blank">tokenaccessreviews.authentication.k8s.io</a>.</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--authentication-token-webhook-cache-ttl duration</td>
|
||
|
<td>The duration to cache responses from the webhook token authenticator. (default 10s)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--authorization-kubeconfig string</td>
|
||
|
<td>kubeconfig file pointing at the 'core' kubernetes server with enough rights to create <a href="http://subjectaccessreviews.authorization.k8s.io" target="_blank">subjectaccessreviews.authorization.k8s.io</a>.</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--authorization-webhook-cache-authorized-ttl duration</td>
|
||
|
<td>The duration to cache 'authorized' responses from the webhook authorizer. (default 10s)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--authorization-webhook-cache-unauthorized-ttl duration</td>
|
||
|
<td>The duration to cache 'unauthorized' responses from the webhook authorizer. (default 10s)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--bind-address ip</td>
|
||
|
<td>The IP address on which to listen for the --secure-port port. The associated interface(s) must be reachable by the rest of the cluster, and by CLI/web clients. If blank, all interfaces will be used (0.0.0.0). (default 0.0.0.0)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--cert-dir string</td>
|
||
|
<td>The directory where the TLS certs are located (by default /var/run/kubernetes). If --tls-cert-file and --tls-private-key-file are provided, this flag will be ignored. (default "/var/run/kubernetes")</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--client-ca-file string</td>
|
||
|
<td>If set, any request presenting a client certificate signed by one of the authorities in the client-ca-file is authenticated with an identity corresponding to the CommonName of the client certificate.</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--contention-profiling</td>
|
||
|
<td>Enable contention profiling. Requires --profiling to be set to work.</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--disable-export</td>
|
||
|
<td>Disable exporting metrics in api/v1/metric-export</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--enable-swagger-ui</td>
|
||
|
<td>Enables swagger ui on the apiserver at /swagger-ui</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--heapster-port int</td>
|
||
|
<td>port used by the Heapster-specific APIs (default 8082)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--historical-source string</td>
|
||
|
<td>which source type to use for the historical API (should be exactly the same as one of the sink URIs), or empty to disable the historical API</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--label-seperator string</td>
|
||
|
<td>seperator used for joining labels (default ",")</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--listen-ip string</td>
|
||
|
<td>IP to listen on, defaults to all IPs</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--log-backtrace-at traceLocation</td>
|
||
|
<td>when logging hits line file:N, emit a stack trace (default :0)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--log-dir string</td>
|
||
|
<td>If non-empty, write log files in this directory</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--log-flush-frequency duration</td>
|
||
|
<td>Maximum number of seconds between log flushes (default 5s)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--logtostderr</td>
|
||
|
<td>log to standard error instead of files (default true)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--max-procs int</td>
|
||
|
<td>max number of CPUs that can be used simultaneously. Less than 1 for default (number of cores)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--metric-resolution duration</td>
|
||
|
<td>The resolution at which heapster will retain metrics. (default 1m0s)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--profiling</td>
|
||
|
<td>Enable profiling via web interface host:port/debug/pprof/ (default true)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--requestheader-allowed-names stringSlice</td>
|
||
|
<td>List of client certificate common names to allow to provide usernames in headers specified by --requestheader-username-headers. If empty, any client certificate validated by the authorities in --requestheader-client-ca-file is allowed.</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--requestheader-client-ca-file string</td>
|
||
|
<td>Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--requestheader-extra-headers-prefix stringSlice</td>
|
||
|
<td>List of request header prefixes to inspect. X-Remote-Extra- is suggested. (default [x-remote-extra-])</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--requestheader-group-headers stringSlice</td>
|
||
|
<td>List of request headers to inspect for groups. X-Remote-Group is suggested. (default [x-remote-group])</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--requestheader-username-headers stringSlice</td>
|
||
|
<td>List of request headers to inspect for usernames. X-Remote-User is common. (default [x-remote-user])</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--secure-port int</td>
|
||
|
<td>The port on which to serve HTTPS with authentication and authorization. If 0, don't serve HTTPS at all. (default 6443)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--sink *flags.Uris</td>
|
||
|
<td>external sink(s) that receive data (default [])</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--source *flags.Uris</td>
|
||
|
<td>source(s) to watch (default [])</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--stderrthreshold severity</td>
|
||
|
<td>logs at or above this threshold go to stderr (default 2)</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--tls-ca-file string</td>
|
||
|
<td>If set, this certificate authority will used for secure access from Admission Controllers. This must be a valid PEM-encoded CA bundle. Altneratively, the certificate authority can be appended to the certificate provided by --tls-cert-file.</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--tls-cert string</td>
|
||
|
<td>file containing TLS certificate</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--tls-cert-file string</td>
|
||
|
<td>File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to /var/run/kubernetes.</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--tls-client-ca string</td>
|
||
|
<td>file containing TLS client CA for client cert validation</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--tls-key string</td>
|
||
|
<td>file containing TLS key</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--tls-private-key-file string</td>
|
||
|
<td>File containing the default x509 private key matching --tls-cert-file.</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--tls-sni-cert-key namedCertKey</td>
|
||
|
<td>A pair of x509 certificate and private key file paths, optionally suffixed with a list of domain patterns which are fully qualified domain names, possibly with prefixed wildcard segments. If no domain patterns are provided, the names of the certificate are extracted. Non-wildcard matches trump over wildcard matches, explicit domain patterns trump over extracted names. For multiple key/certificate pairs, use the --tls-sni-cert-key multiple times. Examples: "example.key,example.crt" or "*.foo.com,foo.com:foo.key,foo.crt". (default [])</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--v Level</td>
|
||
|
<td>log level for V logs</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--version</td>
|
||
|
<td>print version info and exit</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>--vmodule moduleSpec</td>
|
||
|
<td>comma-separated list of pattern=N settings for file-filtered logging</td>
|
||
|
</tr>
|
||
|
</tbody>
|
||
|
</table>
|
||
|
<p><strong>Version</strong></p>
|
||
|
<p>version: v1.4.0
|
||
|
commit: 546ab66f</p>
|
||
|
<h3 id="api使用">API使用</h3>
|
||
|
<p>Heapster提供RESTful API接口,下面以获取<code>spark-cluster</code> namespace的memory usage为例讲解Heapster API的使用。</p>
|
||
|
<p><strong>构造URL地址</strong></p>
|
||
|
<p><a href="https://172.20.0.113:6443/api/v1/proxy/namespaces/kube-system/services/heapster/api/v1/model/namespaces/spark-cluster/metrics/memory/usage?start=2017-10-16T09:14:00Z&end=2017-10-16T09:16:00Z" target="_blank">https://172.20.0.113:6443/api/v1/proxy/namespaces/kube-system/services/heapster/api/v1/model/namespaces/spark-cluster/metrics/memory/usage?start=2017-10-16T09:14:00Z&end=2017-10-16T09:16:00Z</a></p>
|
||
|
<p><strong>结果</strong></p>
|
||
|
<p>访问该地址获取的结果是这样的:</p>
|
||
|
<pre><code class="lang-json">{
|
||
|
<span class="hljs-string">"metrics"</span>: [
|
||
|
{
|
||
|
<span class="hljs-string">"timestamp"</span>: <span class="hljs-string">"2017-10-16T09:14:00Z"</span>,
|
||
|
<span class="hljs-string">"value"</span>: <span class="hljs-number">322592768</span>
|
||
|
},
|
||
|
{
|
||
|
<span class="hljs-string">"timestamp"</span>: <span class="hljs-string">"2017-10-16T09:15:00Z"</span>,
|
||
|
<span class="hljs-string">"value"</span>: <span class="hljs-number">322592768</span>
|
||
|
},
|
||
|
{
|
||
|
<span class="hljs-string">"timestamp"</span>: <span class="hljs-string">"2017-10-16T09:16:00Z"</span>,
|
||
|
<span class="hljs-string">"value"</span>: <span class="hljs-number">322592768</span>
|
||
|
}
|
||
|
],
|
||
|
<span class="hljs-string">"latestTimestamp"</span>: <span class="hljs-string">"2017-10-16T09:16:00Z"</span>
|
||
|
}
|
||
|
</code></pre>
|
||
|
<p>注意:Heapster中查询的所有值都是以最小单位为单位,比如CPU为1milicore,内存为B。</p>
|
||
|
<ol>
|
||
|
<li><strong>第一部分:Heapster API地址</strong></li>
|
||
|
</ol>
|
||
|
<p><a href="https://172.20.0.113:6443/api/v1/proxy/namespaces/kube-system/services/heapster/" target="_blank">https://172.20.0.113:6443/api/v1/proxy/namespaces/kube-system/services/heapster/</a></p>
|
||
|
<p>可以使用下面的命令获取:</p>
|
||
|
<pre><code class="lang-bash">$ kubectl cluster-info
|
||
|
Heapster is running at https://172.20.0.113:6443/api/v1/proxy/namespaces/kube-system/services/heapster
|
||
|
...
|
||
|
</code></pre>
|
||
|
<ol>
|
||
|
<li><strong>第二部分:Heapster API参数</strong></li>
|
||
|
</ol>
|
||
|
<p><code>/api/v1/model/namespaces/spark-cluster/metrics/memory/usage</code></p>
|
||
|
<p>表示查询的是<code>spark-cluster</code> namespace中的<code>memory/usage</code>的metrics。</p>
|
||
|
<ol>
|
||
|
<li><strong>第三部分:时间片</strong></li>
|
||
|
</ol>
|
||
|
<p>查询参数为时间片:包括start和end。</p>
|
||
|
<p><code>?start=2017-10-16T09:14:00Z&end=2017-10-16T09:16:00Z</code></p>
|
||
|
<p>使用<code>RFC-3339</code>时间格式,在Linux系统中可以这样获取:</p>
|
||
|
<pre><code class="lang-bash">$ date --rfc-3339=<span class="hljs-string">"seconds"</span>
|
||
|
2017-10-16 17:23:20+08:00
|
||
|
</code></pre>
|
||
|
<p>该时间中的空格替换成T,最后的<code>+08:00</code>替换成Z代表时区。可以只指定start时间,end时间自动设置为当前时间。</p>
|
||
|
<h2 id="参考">参考</h2>
|
||
|
<ul>
|
||
|
<li><a href="https://github.com/kubernetes/metrics" target="_blank">kubernetes metrics</a></li>
|
||
|
<li><a href="https://github.com/kubernetes/heapster/blob/master/docs/model.md" target="_blank">Heapster metric model</a></li>
|
||
|
<li><a href="https://github.com/kubernetes/heapster/blob/master/docs/storage-schema.md" target="_blank">Heapster storage schema</a> </li>
|
||
|
</ul>
|
||
|
<footer class="page-footer"><span class="copyright">Copyright © jimmysong.io 2017 all right reserved,powered by Gitbook</span><span class="footer-modification">Updated:
|
||
|
2017-10-16 17:33:11
|
||
|
</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="using-prometheus-to-monitor-kuberentes-cluster.html" class="navigation navigation-prev " aria-label="Previous page: 4.3.8 使用Prometheus监控kubernetes集群">
|
||
|
<i class="fa fa-angle-left"></i>
|
||
|
</a>
|
||
|
|
||
|
|
||
|
<a href="storage.html" class="navigation navigation-next " aria-label="Next page: 4.4 存储管理">
|
||
|
<i class="fa fa-angle-right"></i>
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
<script>
|
||
|
var gitbook = gitbook || [];
|
||
|
gitbook.push(function() {
|
||
|
gitbook.page.hasChanged({"page":{"title":"4.3.9 使用Heapster获取集群和对象的metric数据","level":"1.4.3.9","depth":3,"next":{"title":"4.4 存储管理","level":"1.4.4","depth":2,"path":"practice/storage.md","ref":"practice/storage.md","articles":[{"title":"4.4.1 GlusterFS","level":"1.4.4.1","depth":3,"path":"practice/glusterfs.md","ref":"practice/glusterfs.md","articles":[{"title":"4.4.1.1 使用GlusterFS做持久化存储","level":"1.4.4.1.1","depth":4,"path":"practice/using-glusterfs-for-persistent-storage.md","ref":"practice/using-glusterfs-for-persistent-storage.md","articles":[]},{"title":"4.4.1.2 在OpenShift中使用GlusterFS做持久化存储","level":"1.4.4.1.2","depth":4,"path":"practice/storage-for-containers-using-glusterfs-with-openshift.md","ref":"practice/storage-for-containers-using-glusterfs-with-openshift.md","articles":[]}]},{"title":"4.4.2 CephFS","level":"1.4.4.2","depth":3,"path":"practice/cephfs.md","ref":"practice/cephfs.md","articles":[{"title":"4.4.2.1 使用Ceph做持久化存储","level":"1.4.4.2.1","depth":4,"path":"practice/using-ceph-for-persistent-storage.md","ref":"practice/using-ceph-for-persistent-storage.md","articles":[]}]}]},"previous":{"title":"4.3.8 使用Prometheus监控kubernetes集群","level":"1.4.3.8","depth":3,"path":"practice/using-prometheus-to-monitor-kuberentes-cluster.md","ref":"practice/using-prometheus-to-monitor-kuberentes-cluster.md","articles":[]},"dir":"ltr"},"config":{"plugins":["github","codesnippet","splitter","page-toc-button","image-captions","editlink","back-to-top-button","-lunr","-search","search-plus","github-buttons@2.1.0","favicon@^0.0.2","tbfed-pagefooter@^0.0.1","3-ba"],"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":{"tbfed-pagefooter":{"copyright":"Copyright © jimmysong.io 2017","modify_label":"Updated:","modify_format":"YYYY-MM-DD HH:mm:ss"},"github":{"url":"https://github.com/rootsongjc/kubernetes-handbook"},"editlink":{"label":"编辑本页","multilingual":false,"base":"https://github.com/rootsongjc/kubernetes-handbook/blob/master/"},"splitter":{},"codesnippet":{},"fontsettings":{"theme":"white","family":"sans","size":2},"highlight":{},"favicon":{"shortcut":"favicon.ico","bookmark":"favicon.ico"},"page-toc-button":{},"back-to-top-button":{},"github-buttons":{"repo":"rootsongjc/kubernetes-handbook","types":["star"],"size":"small"},"3-ba":{"configuration":"auto","token":"11f7d254cfa4e0ca44b175c66d379ecc"},"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":{"caption":"图片 - _CAPTION_","variable_name":"_pictures"}},"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":"图片 - _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":"图片 - _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整体架构示意图"
|
||
|
});
|
||
|
</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-back-to-top-button/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-github-buttons/plugin.js"></script>
|
||
|
|
||
|
|
||
|
|
||
|
<script src="../gitbook/gitbook-plugin-3-ba/plugin.js"></script>
|
||
|
|
||
|
|
||
|
|
||
|
<script src="../gitbook/gitbook-plugin-sharing/buttons.js"></script>
|
||
|
|
||
|
|
||
|
|
||
|
<script src="../gitbook/gitbook-plugin-fontsettings/fontsettings.js"></script>
|
||
|
|
||
|
|
||
|
|
||
|
</body>
|
||
|
</html>
|
||
|
|