1520 lines
77 KiB
HTML
1520 lines
77 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.3.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="monitor.html" />
|
||
|
|
||
|
|
||
|
<link rel="prev" href="app-log-collection.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 主要概念
|
||
|
|
||
|
</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>
|
||
|
|
||
|
|
||
|
</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>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.3" data-path="../guide/">
|
||
|
|
||
|
<a href="../guide/">
|
||
|
|
||
|
|
||
|
3. 用户指南
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.3.1" data-path="../guide/resource-configuration.html">
|
||
|
|
||
|
<a href="../guide/resource-configuration.html">
|
||
|
|
||
|
|
||
|
3.1 资源配置
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.3.1.1" data-path="../guide/configure-liveness-readiness-probes.html">
|
||
|
|
||
|
<a href="../guide/configure-liveness-readiness-probes.html">
|
||
|
|
||
|
|
||
|
3.1.1 配置Pod的liveness和readiness探针
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.3.1.2" data-path="../guide/configure-pod-service-account.html">
|
||
|
|
||
|
<a href="../guide/configure-pod-service-account.html">
|
||
|
|
||
|
|
||
|
3.1.2 配置Pod的Service Account
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.3.2" data-path="../guide/command-usage.html">
|
||
|
|
||
|
<a href="../guide/command-usage.html">
|
||
|
|
||
|
|
||
|
3.2 命令使用
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.3.2.1" data-path="../guide/using-kubectl.html">
|
||
|
|
||
|
<a href="../guide/using-kubectl.html">
|
||
|
|
||
|
|
||
|
3.2.1 使用kubectl
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.3.3" data-path="../guide/cluster-management.html">
|
||
|
|
||
|
<a href="../guide/cluster-management.html">
|
||
|
|
||
|
|
||
|
3.3 集群管理
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.3.3.1" data-path="../guide/managing-tls-in-a-cluster.html">
|
||
|
|
||
|
<a href="../guide/managing-tls-in-a-cluster.html">
|
||
|
|
||
|
|
||
|
3.3.1 管理集群中的TLS
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</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>
|
||
|
|
||
|
|
||
|
</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 active" 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>
|
||
|
|
||
|
|
||
|
</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>
|
||
|
|
||
|
|
||
|
</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-on-kubernetes.html">
|
||
|
|
||
|
<a href="../usecases/spark-on-kubernetes.html">
|
||
|
|
||
|
|
||
|
5.2.1 Spark on Kubernetes
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.6" data-path="../develop/">
|
||
|
|
||
|
<a href="../develop/">
|
||
|
|
||
|
|
||
|
6. 开发指南
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.6.1" data-path="../develop/developing-environment.html">
|
||
|
|
||
|
<a href="../develop/developing-environment.html">
|
||
|
|
||
|
|
||
|
6.1 开发环境搭建
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.6.2" data-path="../develop/testing.html">
|
||
|
|
||
|
<a href="../develop/testing.html">
|
||
|
|
||
|
|
||
|
6.2 单元测试和集成测试
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.6.3" data-path="../develop/client-go-sample.html">
|
||
|
|
||
|
<a href="../develop/client-go-sample.html">
|
||
|
|
||
|
|
||
|
6.3 client-go示例
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.6.4" data-path="../develop/contribute.html">
|
||
|
|
||
|
<a href="../develop/contribute.html">
|
||
|
|
||
|
|
||
|
6.4 社区贡献
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.7" data-path="../appendix/">
|
||
|
|
||
|
<a href="../appendix/">
|
||
|
|
||
|
|
||
|
7. 附录
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.7.1" data-path="../appendix/docker-best-practice.html">
|
||
|
|
||
|
<a href="../appendix/docker-best-practice.html">
|
||
|
|
||
|
|
||
|
7.1 Docker最佳实践
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.7.2" data-path="../appendix/issues.html">
|
||
|
|
||
|
<a href="../appendix/issues.html">
|
||
|
|
||
|
|
||
|
7.2 问题记录
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.7.3" data-path="../appendix/tricks.html">
|
||
|
|
||
|
<a href="../appendix/tricks.html">
|
||
|
|
||
|
|
||
|
7.3 使用技巧
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
<li class="divider"></li>
|
||
|
|
||
|
<li>
|
||
|
<a href="https://www.gitbook.com" target="blank" class="gitbook-link">
|
||
|
本書使用 GitBook 釋出
|
||
|
</a>
|
||
|
</li>
|
||
|
</ul>
|
||
|
|
||
|
|
||
|
</nav>
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
<div class="book-body">
|
||
|
|
||
|
<div class="body-inner">
|
||
|
|
||
|
|
||
|
|
||
|
<div class="book-header" role="navigation">
|
||
|
|
||
|
|
||
|
<!-- Title -->
|
||
|
<h1>
|
||
|
<i class="fa fa-circle-o-notch fa-spin"></i>
|
||
|
<a href=".." >4.3.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="配置最佳实践">配置最佳实践</h1>
|
||
|
<p>本文档旨在汇总和强调用户指南、快速开始文档和示例中的最佳实践。该文档会很活跃并持续更新中。如果你觉得很有用的最佳实践但是本文档中没有包含,欢迎给我们提Pull Request。</p>
|
||
|
<h2 id="通用配置建议">通用配置建议</h2>
|
||
|
<ul>
|
||
|
<li>定义配置文件的时候,指定最新的稳定API版本(目前是V1)。</li>
|
||
|
<li>在配置文件push到集群之前应该保存在版本控制系统中。这样当需要的时候能够快速回滚,必要的时候也可以快速的创建集群。</li>
|
||
|
<li>使用YAML格式而不是JSON格式的配置文件。在大多数场景下它们都可以作为数据交换格式,但是YAML格式比起JSON更易读和配置。</li>
|
||
|
<li>尽量将相关的对象放在同一个配置文件里。这样比分成多个文件更容易管理。参考<a href="https://github.com/kubernetes/kubernetes/tree/master/examples/guestbook/all-in-one/guestbook-all-in-one.yaml" target="_blank">guestbook-all-in-one.yaml</a>文件中的配置(注意,尽管你可以在使用<code>kubectl</code>命令时指定配置文件目录,你也可以在配置文件目录下执行<code>kubectl create</code>——查看下面的详细信息)。</li>
|
||
|
<li>为了简化和最小化配置,也为了防止错误发生,不要指定不必要的默认配置。例如,省略掉<code>ReplicationController</code>的selector和label,如果你希望它们跟<code>podTemplate</code>中的label一样的话,因为那些配置默认是<code>podTemplate</code>的label产生的。更多信息请查看 <a href="https://github.com/kubernetes/kubernetes/tree/master/examples/guestbook/" target="_blank">guestbook app</a> 的yaml文件和 <a href="https://github.com/kubernetes/kubernetes/tree/master/examples/guestbook/frontend-deployment.yaml" target="_blank">examples</a> 。</li>
|
||
|
<li>将资源对象的描述放在一个annotation中可以更好的内省。</li>
|
||
|
</ul>
|
||
|
<h2 id="裸的pods-vs-replication-controllers和-jobs">裸的Pods vs Replication Controllers和 Jobs</h2>
|
||
|
<ul>
|
||
|
<li>如果有其他方式替代“裸的“ pod(如没有绑定到<a href="https://kubernetes.io/docs/user-guide/replication-controller" target="_blank">replication controller </a>上的pod),那么就使用其他选择。在node节点出现故障时,裸奔的pod不会被重新调度。Replication Controller总是会重新创建pod,除了明确指定了<a href="https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy" target="_blank"><code>restartPolicy: Never</code></a> 的场景。<a href="https://kubernetes.io/docs/concepts/jobs/run-to-completion-finite-workloads/" target="_blank">Job</a> 也许是比较合适的选择。</li>
|
||
|
</ul>
|
||
|
<h2 id="services">Services</h2>
|
||
|
<ul>
|
||
|
<li>通常最好在创建相关的<a href="https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/" target="_blank">replication controllers</a>之前先创建<a href="https://kubernetes.io/docs/concepts/services-networking/service/" target="_blank">service</a> ,你也可以在创建Replication Controller的时候不指定replica数量(默认是1),创建service后,在通过Replication Controller来扩容。这样可以在扩容很多个replica之前先确认pod是正常的。</li>
|
||
|
<li>除非十分必要的情况下(如运行一个node daemon),不要使用<code>hostPort</code>(用来指定暴露在主机上的端口号)。当你给Pod绑定了一个<code>hostPort</code>,该pod可被调度到的主机的受限了,因为端口冲突。如果是为了调试目的来通过端口访问的话,你可以使用 <a href="https://kubernetes.io/docs/tasks/access-kubernetes-api/http-proxy-access-api/" target="_blank">kubectl proxy and apiserver proxy</a> 或者 <a href="https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/" target="_blank">kubectl port-forward</a>。你可使用 <a href="https://kubernetes.io/docs/concepts/services-networking/service/" target="_blank">Service</a> 来对外暴露服务。如果你确实需要将pod的端口暴露到主机上,考虑使用 <a href="https://kubernetes.io/docs/user-guide/services/#type-nodeport" target="_blank">NodePort</a> service。</li>
|
||
|
<li>跟<code>hostPort</code>一样的原因,避免使用 <code>hostNetwork</code>。</li>
|
||
|
<li>如果你不需要kube-proxy的负载均衡的话,可以考虑使用使用<a href="https://kubernetes.io/docs/user-guide/services/#headless-services" target="_blank">headless services</a>。</li>
|
||
|
</ul>
|
||
|
<h2 id="使用label">使用Label</h2>
|
||
|
<ul>
|
||
|
<li><p>定义 <a href="https://kubernetes.io/docs/user-guide/labels/" target="_blank">labels</a> 来指定应用或Deployment的 <strong>semantic attributes</strong> 。例如,不是将label附加到一组pod来显式表示某些服务(例如,<code>service:myservice</code>),或者显式地表示管理pod的replication controller(例如,<code>controller:mycontroller</code>),附加label应该是标示语义属性的标签, 例如<code>{app:myapp,tier:frontend,phase:test,deployment:v3}</code>。 这将允许您选择适合上下文的对象组——例如,所有的”tier:frontend“pod的服务或app是“myapp”的所有“测试”阶段组件。 有关此方法的示例,请参阅<a href="https://github.com/kubernetes/kubernetes/tree/master/examples/guestbook/" target="_blank">guestbook</a>应用程序。</p>
|
||
|
<p>可以通过简单地从其service的选择器中省略特定于发行版本的标签,而不是更新服务的选择器来完全匹配replication controller的选择器,来实现跨越多个部署的服务,例如滚动更新。</p>
|
||
|
</li>
|
||
|
<li><p>为了滚动升级的方便,在Replication Controller的名字中包含版本信息,例如作为名字的后缀。设置一个<code>version</code>标签页是很有用的。滚动更新创建一个新的controller而不是修改现有的controller。因此,version含混不清的controller名字就可能带来问题。查看<a href="https://kubernetes.io/docs/tasks/run-application/rolling-update-replication-controller/" target="_blank">Rolling Update Replication Controller</a>文档获取更多关于滚动升级命令的信息。</p>
|
||
|
<p>注意 <a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment/" target="_blank">Deployment</a> 对象不需要再管理 replication controller 的版本名。Deployment 中描述了对象的期望状态,如果对spec的更改被应用了话,Deployment controller 会以控制的速率来更改实际状态到期望状态。(Deployment目前是 <a href="https://kubernetes.io/docs/concepts/overview/kubernetes-api/#api-groups" target="_blank"><code>extensions</code> API Group</a>的一部分)。</p>
|
||
|
</li>
|
||
|
<li><p>利用label做调试。因为Kubernetes replication controller和service使用label来匹配pods,这允许你通过移除pod中的label的方式将其从一个controller或者service中移除,原来的controller会创建一个新的pod来取代移除的pod。这是一个很有用的方式,帮你在一个隔离的环境中调试之前的“活着的” pod。查看 <a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/" target="_blank"><code>kubectl label</code></a> 命令。</p>
|
||
|
</li>
|
||
|
</ul>
|
||
|
<h2 id="容器镜像">容器镜像</h2>
|
||
|
<ul>
|
||
|
<li><p><a href="https://kubernetes.io/docs/concepts/containers/images/" target="_blank">默认容器镜像拉取策略</a> 是 <code>IfNotPresent</code>, 当本地已存在该镜像的时候 <a href="https://kubernetes.io/docs/admin/kubelet/" target="_blank">Kubelet</a> 不会再从镜像仓库拉取。如果你希望总是从镜像仓库中拉取镜像的话,在yaml文件中指定镜像拉取策略为<code>Always</code>( <code>imagePullPolicy: Always</code>)或者指定镜像的tag为 <code>:latest</code> 。</p>
|
||
|
<p>如果你没有将镜像标签指定为<code>:latest</code>,例如指定为<code>myimage:v1</code>,当该标签的镜像进行了更新,kubelet也不会拉取该镜像。你可以在每次镜像更新后都生成一个新的tag(例如<code>myimage:v2</code>),在配置文件中明确指定该版本。</p>
|
||
|
<p><strong>注意:</strong> 在生产环境下部署容器应该尽量避免使用<code>:latest</code>标签,因为这样很难追溯到底运行的是哪个版本的容器和回滚。</p>
|
||
|
</li>
|
||
|
</ul>
|
||
|
<h2 id="使用kubectl">使用kubectl</h2>
|
||
|
<ul>
|
||
|
<li>尽量使用 <code>kubectl create -f <directory></code> 。kubeclt会自动查找该目录下的所有后缀名为<code>.yaml</code>、<code>.yml</code>和<code>.json</code>文件并将它们传递给<code>create</code>命令。</li>
|
||
|
<li>使用 <code>kubectl delete</code> 而不是 <code>stop</code>. <code>Delete</code> 是 <code>stop</code>的超集,<code>stop</code> 已经被弃用。</li>
|
||
|
<li>使用 kubectl bulk 操作(通过文件或者label)来get和delete。查看<a href="https://kubernetes.io/docs/user-guide/labels/#label-selectors" target="_blank">label selectors </a>和 <a href="https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#using-labels-effectively" target="_blank">using labels effectively</a>。</li>
|
||
|
<li>使用 <code>kubectl run</code> 和 <code>expose</code> 命令快速创建只有单个容器的Deployment。查看 <a href="https://kubernetes.io/docs/user-guide/quick-start/" target="_blank">quick start guide</a>中的示例。</li>
|
||
|
</ul>
|
||
|
<h2 id="参考">参考</h2>
|
||
|
<p><a href="https://kubernetes.io/docs/concepts/configuration/overview/" target="_blank">Configuration Best Practices</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-04 14:20:45
|
||
|
</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="app-log-collection.html" class="navigation navigation-prev " aria-label="Previous page: 4.3.2 应用日志收集">
|
||
|
<i class="fa fa-angle-left"></i>
|
||
|
</a>
|
||
|
|
||
|
|
||
|
<a href="monitor.html" class="navigation navigation-next " aria-label="Next page: 4.3.4 集群及应用监控">
|
||
|
<i class="fa fa-angle-right"></i>
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
<script>
|
||
|
var gitbook = gitbook || [];
|
||
|
gitbook.push(function() {
|
||
|
gitbook.page.hasChanged({"page":{"title":"4.3.3 配置最佳实践","level":"1.4.3.3","depth":3,"next":{"title":"4.3.4 集群及应用监控","level":"1.4.3.4","depth":3,"path":"practice/monitor.md","ref":"practice/monitor.md","articles":[]},"previous":{"title":"4.3.2 应用日志收集","level":"1.4.3.2","depth":3,"path":"practice/app-log-collection.md","ref":"practice/app-log-collection.md","articles":[]},"dir":"ltr"},"config":{"plugins":["github","codesnippet","splitter","page-toc-button","image-captions","page-footer-ex","editlink","-lunr","-search","search-plus","livereload"],"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/"},"livereload":{},"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":"index.html#fig1.1.1","level":"1.1","list_caption":"Figure: wercker status","alt":"wercker status","nro":1,"url":"https://app.wercker.com/status/b8b69e593784e17ddcfd1286adfd8f3c/s/master","index":1,"caption_template":"Figure: _CAPTION_","label":"wercker status","attributes":{},"title":"wercker status","skip":false,"key":"1.1.1"},{"backlink":"concepts/index.html#fig1.2.1","level":"1.2","list_caption":"Figure: Borg架构","alt":"Borg架构","nro":2,"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":3,"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":4,"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":5,"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":6,"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.
|
||
|
});
|
||
|
</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-livereload/plugin.js"></script>
|
||
|
|
||
|
|
||
|
|
||
|
<script src="../gitbook/gitbook-plugin-sharing/buttons.js"></script>
|
||
|
|
||
|
|
||
|
|
||
|
<script src="../gitbook/gitbook-plugin-fontsettings/fontsettings.js"></script>
|
||
|
|
||
|
|
||
|
|
||
|
</body>
|
||
|
</html>
|
||
|
|