1545 lines
80 KiB
HTML
1545 lines
80 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>2.2.9 DaemonSet · 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="serviceaccount.html" />
|
||
|
|
||
|
|
||
|
<link rel="prev" href="statefulset.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="./">
|
||
|
|
||
|
<a href="./">
|
||
|
|
||
|
|
||
|
2. 概念原理
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.2.1" data-path="concepts.html">
|
||
|
|
||
|
<a href="concepts.html">
|
||
|
|
||
|
|
||
|
2.1 设计理念
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2" data-path="objects.html">
|
||
|
|
||
|
<a href="objects.html">
|
||
|
|
||
|
|
||
|
2.2 主要概念
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.1" data-path="pod-overview.html">
|
||
|
|
||
|
<a href="pod-overview.html">
|
||
|
|
||
|
|
||
|
2.2.1 Pod
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.1.1" data-path="pod.html">
|
||
|
|
||
|
<a href="pod.html">
|
||
|
|
||
|
|
||
|
2.2.1.1 Pod解析
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.2" data-path="node.html">
|
||
|
|
||
|
<a href="node.html">
|
||
|
|
||
|
|
||
|
2.2.2 Node
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.3" data-path="namespace.html">
|
||
|
|
||
|
<a href="namespace.html">
|
||
|
|
||
|
|
||
|
2.2.3 Namespace
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.4" data-path="service.html">
|
||
|
|
||
|
<a href="service.html">
|
||
|
|
||
|
|
||
|
2.2.4 Service
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.5" data-path="volume.html">
|
||
|
|
||
|
<a href="volume.html">
|
||
|
|
||
|
|
||
|
2.2.5 Volume和Persistent Volume
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.6" data-path="deployment.html">
|
||
|
|
||
|
<a href="deployment.html">
|
||
|
|
||
|
|
||
|
2.2.6 Deployment
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.7" data-path="secret.html">
|
||
|
|
||
|
<a href="secret.html">
|
||
|
|
||
|
|
||
|
2.2.7 Secret
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.8" data-path="statefulset.html">
|
||
|
|
||
|
<a href="statefulset.html">
|
||
|
|
||
|
|
||
|
2.2.8 StatefulSet
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter active" data-level="1.2.2.9" data-path="daemonset.html">
|
||
|
|
||
|
<a href="daemonset.html">
|
||
|
|
||
|
|
||
|
2.2.9 DaemonSet
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.10" data-path="serviceaccount.html">
|
||
|
|
||
|
<a href="serviceaccount.html">
|
||
|
|
||
|
|
||
|
2.2.10 ServiceAccount
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.11" data-path="replicaset.html">
|
||
|
|
||
|
<a href="replicaset.html">
|
||
|
|
||
|
|
||
|
2.2.11 ReplicationController和ReplicaSet
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.12" data-path="job.html">
|
||
|
|
||
|
<a href="job.html">
|
||
|
|
||
|
|
||
|
2.2.12 Job
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.13" data-path="cronjob.html">
|
||
|
|
||
|
<a href="cronjob.html">
|
||
|
|
||
|
|
||
|
2.2.13 CronJob
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.14" data-path="ingress.html">
|
||
|
|
||
|
<a href="ingress.html">
|
||
|
|
||
|
|
||
|
2.2.14 Ingress
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.15" data-path="configmap.html">
|
||
|
|
||
|
<a href="configmap.html">
|
||
|
|
||
|
|
||
|
2.2.15 ConfigMap
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.16" data-path="horizontal-pod-autoscaling.html">
|
||
|
|
||
|
<a href="horizontal-pod-autoscaling.html">
|
||
|
|
||
|
|
||
|
2.2.16 Horizontal Pod Autoscaling
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.2.2.17" data-path="label.html">
|
||
|
|
||
|
<a href="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="../practice/">
|
||
|
|
||
|
<a href="../practice/">
|
||
|
|
||
|
|
||
|
4. 最佳实践
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.4.1" data-path="../practice/install-kbernetes1.6-on-centos.html">
|
||
|
|
||
|
<a href="../practice/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="../practice/create-tls-and-secret-key.html">
|
||
|
|
||
|
<a href="../practice/create-tls-and-secret-key.html">
|
||
|
|
||
|
|
||
|
4.1.1 创建TLS证书和秘钥
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.1.2" data-path="../practice/create-kubeconfig.html">
|
||
|
|
||
|
<a href="../practice/create-kubeconfig.html">
|
||
|
|
||
|
|
||
|
4.1.2 创建kubeconfig文件
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.1.3" data-path="../practice/etcd-cluster-installation.html">
|
||
|
|
||
|
<a href="../practice/etcd-cluster-installation.html">
|
||
|
|
||
|
|
||
|
4.1.3 创建高可用etcd集群
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.1.4" data-path="../practice/kubectl-installation.html">
|
||
|
|
||
|
<a href="../practice/kubectl-installation.html">
|
||
|
|
||
|
|
||
|
4.1.4 安装kubectl命令行工具
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.1.5" data-path="../practice/master-installation.html">
|
||
|
|
||
|
<a href="../practice/master-installation.html">
|
||
|
|
||
|
|
||
|
4.1.5 部署master节点
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.1.6" data-path="../practice/node-installation.html">
|
||
|
|
||
|
<a href="../practice/node-installation.html">
|
||
|
|
||
|
|
||
|
4.1.6 部署node节点
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.1.7" data-path="../practice/kubedns-addon-installation.html">
|
||
|
|
||
|
<a href="../practice/kubedns-addon-installation.html">
|
||
|
|
||
|
|
||
|
4.1.7 安装kubedns插件
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.1.8" data-path="../practice/dashboard-addon-installation.html">
|
||
|
|
||
|
<a href="../practice/dashboard-addon-installation.html">
|
||
|
|
||
|
|
||
|
4.1.8 安装dashboard插件
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.1.9" data-path="../practice/heapster-addon-installation.html">
|
||
|
|
||
|
<a href="../practice/heapster-addon-installation.html">
|
||
|
|
||
|
|
||
|
4.1.9 安装heapster插件
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.1.10" data-path="../practice/efk-addon-installation.html">
|
||
|
|
||
|
<a href="../practice/efk-addon-installation.html">
|
||
|
|
||
|
|
||
|
4.1.10 安装EFK插件
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.2" data-path="../practice/service-discovery-and-loadbalancing.html">
|
||
|
|
||
|
<a href="../practice/service-discovery-and-loadbalancing.html">
|
||
|
|
||
|
|
||
|
4.2 服务发现与负载均衡
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.4.2.1" data-path="../practice/traefik-ingress-installation.html">
|
||
|
|
||
|
<a href="../practice/traefik-ingress-installation.html">
|
||
|
|
||
|
|
||
|
4.2.1 安装Traefik ingress
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.2.2" data-path="../practice/distributed-load-test.html">
|
||
|
|
||
|
<a href="../practice/distributed-load-test.html">
|
||
|
|
||
|
|
||
|
4.2.2 分布式负载测试
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.2.3" data-path="../practice/network-and-cluster-perfermance-test.html">
|
||
|
|
||
|
<a href="../practice/network-and-cluster-perfermance-test.html">
|
||
|
|
||
|
|
||
|
4.2.3 网络和集群性能测试
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.2.4" data-path="../practice/edge-node-configuration.html">
|
||
|
|
||
|
<a href="../practice/edge-node-configuration.html">
|
||
|
|
||
|
|
||
|
4.2.4 边缘节点配置
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.3" data-path="../practice/operation.html">
|
||
|
|
||
|
<a href="../practice/operation.html">
|
||
|
|
||
|
|
||
|
4.3 运维管理
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.4.3.1" data-path="../practice/service-rolling-update.html">
|
||
|
|
||
|
<a href="../practice/service-rolling-update.html">
|
||
|
|
||
|
|
||
|
4.3.1 服务滚动升级
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.3.2" data-path="../practice/app-log-collection.html">
|
||
|
|
||
|
<a href="../practice/app-log-collection.html">
|
||
|
|
||
|
|
||
|
4.3.2 应用日志收集
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.3.3" data-path="../practice/configuration-best-practice.html">
|
||
|
|
||
|
<a href="../practice/configuration-best-practice.html">
|
||
|
|
||
|
|
||
|
4.3.3 配置最佳实践
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.3.4" data-path="../practice/monitor.html">
|
||
|
|
||
|
<a href="../practice/monitor.html">
|
||
|
|
||
|
|
||
|
4.3.4 集群及应用监控
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.3.5" data-path="../practice/jenkins-ci-cd.html">
|
||
|
|
||
|
<a href="../practice/jenkins-ci-cd.html">
|
||
|
|
||
|
|
||
|
4.3.5 使用Jenkins进行持续构建与发布
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.3.6" data-path="../practice/data-persistence-problem.html">
|
||
|
|
||
|
<a href="../practice/data-persistence-problem.html">
|
||
|
|
||
|
|
||
|
4.3.6 数据持久化问题
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="1.4.4" data-path="../practice/storage.html">
|
||
|
|
||
|
<a href="../practice/storage.html">
|
||
|
|
||
|
|
||
|
4.4 存储管理
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.4.4.1" data-path="../practice/glusterfs.html">
|
||
|
|
||
|
<a href="../practice/glusterfs.html">
|
||
|
|
||
|
|
||
|
4.4.1 GlusterFS
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="1.4.4.1.1" data-path="../practice/using-glusterfs-for-persistent-storage.html">
|
||
|
|
||
|
<a href="../practice/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="../practice/storage-for-containers-using-glusterfs-with-openshift.html">
|
||
|
|
||
|
<a href="../practice/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=".." >2.2.9 DaemonSet</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="daemonset">DaemonSet</h1>
|
||
|
<h2 id="什么是-daemonset?">什么是 DaemonSet?</h2>
|
||
|
<p> <em>DaemonSet</em> 确保全部(或者一些)Node 上运行一个 Pod 的副本。当有 Node 加入集群时,也会为他们新增一个 Pod 。当有 Node 从集群移除时,这些 Pod 也会被回收。删除 DaemonSet 将会删除它创建的所有 Pod。</p>
|
||
|
<p>使用 DaemonSet 的一些典型用法:</p>
|
||
|
<ul>
|
||
|
<li>运行集群存储 daemon,例如在每个 Node 上运行 <code>glusterd</code>、<code>ceph</code>。</li>
|
||
|
<li>在每个 Node 上运行日志收集 daemon,例如<code>fluentd</code>、<code>logstash</code>。</li>
|
||
|
<li>在每个 Node 上运行监控 daemon,例如 <a href="https://github.com/prometheus/node_exporter" target="_blank">Prometheus Node Exporter</a>、<code>collectd</code>、Datadog 代理、New Relic 代理,或 Ganglia <code>gmond</code>。</li>
|
||
|
</ul>
|
||
|
<p>一个简单的用法是,在所有的 Node 上都存在一个 DaemonSet,将被作为每种类型的 daemon 使用。
|
||
|
一个稍微复杂的用法可能是,对单独的每种类型的 daemon 使用多个 DaemonSet,但具有不同的标志,和/或对不同硬件类型具有不同的内存、CPU要求。</p>
|
||
|
<h2 id="编写-daemonset-spec">编写 DaemonSet Spec</h2>
|
||
|
<h3 id="必需字段">必需字段</h3>
|
||
|
<p>和其它所有 Kubernetes 配置一样,DaemonSet 需要 <code>apiVersion</code>、<code>kind</code> 和 <code>metadata</code>字段。有关配置文件的通用信息,详见文档 <a href="https://kubernetes.io/docs/user-guide/deploying-applications/" target="_blank">部署应用</a>、<a href="https://kubernetes.io/docs/user-guide/configuring-containers/" target="_blank">配置容器</a> 和 <a href="https://kubernetes.io/docs/concepts/tools/kubectl/object-management-overview/" target="_blank">资源管理</a> 。</p>
|
||
|
<p>DaemonSet 也需要一个 <a href="https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status" target="_blank"><code>.spec</code></a> 配置段。</p>
|
||
|
<h3 id="pod-模板">Pod 模板</h3>
|
||
|
<p><code>.spec</code> 唯一必需的字段是 <code>.spec.template</code>。</p>
|
||
|
<p><code>.spec.template</code> 是一个 <a href="https://kubernetes.io/docs/user-guide/replication-controller/#pod-template" target="_blank">Pod 模板</a>。
|
||
|
它与 <a href="https://kubernetes.io/docs/user-guide/pods" target="_blank">Pod</a> 具有相同的 schema,除了它是嵌套的,而且不具有 <code>apiVersion</code> 或 <code>kind</code> 字段。</p>
|
||
|
<p>Pod 除了必须字段外,在 DaemonSet 中的 Pod 模板必须指定合理的标签(查看 <a href="#pod-selector">pod selector</a>)。</p>
|
||
|
<p>在 DaemonSet 中的 Pod 模板必需具有一个值为 <code>Always</code> 的 <a href="https://kubernetes.io/docs/user-guide/pod-states" target="_blank"><code>RestartPolicy</code></a>,或者未指定它的值,默认是 <code>Always</code>。</p>
|
||
|
<h3 id="pod-selector">Pod Selector</h3>
|
||
|
<p><code>.spec.selector</code> 字段表示 Pod Selector,它与 <a href="https://kubernetes.io/docs/concepts/jobs/run-to-completion-finite-workloads/" target="_blank">Job</a> 或其它资源的 <code>.sper.selector</code> 的原理是相同的。</p>
|
||
|
<p><code>spec.selector</code> 表示一个对象,它由如下两个字段组成:</p>
|
||
|
<ul>
|
||
|
<li><code>matchLabels</code> - 与 <a href="https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/" target="_blank">ReplicationController</a> 的 <code>.spec.selector</code> 的原理相同。</li>
|
||
|
<li><code>matchExpressions</code> - 允许构建更加复杂的 Selector,可以通过指定 key、value 列表,以及与 key 和 value 列表的相关的操作符。</li>
|
||
|
</ul>
|
||
|
<p>当上述两个字段都指定时,结果表示的是 AND 关系。</p>
|
||
|
<p>如果指定了 <code>.spec.selector</code>,必须与 <code>.spec.template.metadata.labels</code> 相匹配。如果没有指定,它们默认是等价的。如果与它们配置的不匹配,则会被 API 拒绝。</p>
|
||
|
<p>如果 Pod 的 label 与 selector 匹配,或者直接基于其它的 DaemonSet、或者 Controller(例如 ReplicationController),也不可以创建任何 Pod。
|
||
|
否则 DaemonSet Controller 将认为那些 Pod 是它创建的。Kubernetes 不会阻止这样做。一个场景是,可能希望在一个具有不同值的、用来测试用的 Node 上手动创建 Pod。</p>
|
||
|
<h3 id="仅在相同的-node-上运行-pod">仅在相同的 Node 上运行 Pod</h3>
|
||
|
<p>如果指定了 <code>.spec.template.spec.nodeSelector</code>,DaemonSet Controller 将在能够匹配上 <a href="https://kubernetes.io/docs/concepts/configuration/assign-pod-node/" target="_blank">Node Selector</a> 的 Node 上创建 Pod。
|
||
|
类似这种情况,可以指定 <code>.spec.template.spec.affinity</code>,然后 DaemonSet Controller 将在能够匹配上 <a href="https://kubernetes.io/docs/concepts/configuration/assign-pod-node/" target="_blank">Node Affinity</a> 的 Node 上创建 Pod。
|
||
|
如果根本就没有指定,则 DaemonSet Controller 将在所有 Node 上创建 Pod。</p>
|
||
|
<h2 id="如果调度-daemon-pod">如果调度 Daemon Pod</h2>
|
||
|
<p>正常情况下,Pod 运行在哪个机器上是由 Kubernetes 调度器进行选择的。然而,由 Daemon Controller 创建的 Pod 已经确定了在哪个机器上(Pod 创建时指定了 <code>.spec.nodeName</code>),因此:</p>
|
||
|
<ul>
|
||
|
<li>DaemonSet Controller 并不关心一个 Node 的 <a href="https://kubernetes.io/docs/admin/node/#manual-node-administration" target="_blank"><code>unschedulable</code></a> 字段。</li>
|
||
|
<li>DaemonSet Controller 可以创建 Pod,即使调度器还没有被启动,这对集群启动是非常有帮助的。</li>
|
||
|
</ul>
|
||
|
<p>Daemon Pod 关心 <a href="https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature" target="_blank">Taint 和 Toleration</a>,它们会为没有指定 <code>tolerationSeconds</code> 的 <code>node.alpha.kubernetes.io/notReady</code> 和 <code>node.alpha.kubernetes.io/unreachable</code> 的 Taint,而创建具有 <code>NoExecute</code> 的 Toleration。这确保了当 alpha 特性的 <code>TaintBasedEvictions</code> 被启用,当 Node 出现故障,比如网络分区,这时它们将不会被清除掉(当 <code>TaintBasedEvictions</code> 特性没有启用,在这些场景下也不会被清除,但会因为 NodeController 的硬编码行为而被清除,Toleration 是不会的)。</p>
|
||
|
<h2 id="与-daemon-pod-通信">与 Daemon Pod 通信</h2>
|
||
|
<p>与 DaemonSet 中的 Pod 进行通信,几种可能的模式如下:</p>
|
||
|
<ul>
|
||
|
<li><strong>Push</strong>:配置 DaemonSet 中的 Pod 向其它 Service 发送更新,例如统计数据库。它们没有客户端。</li>
|
||
|
<li><strong>NodeIP 和已知端口</strong>:DaemonSet 中的 Pod 可以使用 <code>hostPort</code>,从而可以通过 Node IP 访问到 Pod。客户端能通过某种方法知道 Node IP 列表,并且基于此也可以知道端口。</li>
|
||
|
<li><strong>DNS</strong>:创建具有相同 Pod Selector 的 <a href="https://kubernetes.io/docs/user-guide/services/#headless-services" target="_blank">Headless Service</a>,然后通过使用 <code>endpoints</code> 资源或从 DNS 检索到多个 A 记录来发现 DaemonSet。</li>
|
||
|
<li><strong>Service</strong>:创建具有相同 Pod Selector 的 Service,并使用该 Service 访问到某个随机 Node 上的 daemon。(没有办法访问到特定 Node)</li>
|
||
|
</ul>
|
||
|
<h2 id="更新-daemonset">更新 DaemonSet</h2>
|
||
|
<p>如果修改了 Node Label,DaemonSet 将立刻向新匹配上的 Node 添加 Pod,同时删除新近无法匹配上的 Node 上的 Pod。</p>
|
||
|
<p>可以修改 DaemonSet 创建的 Pod。然而,不允许对 Pod 的所有字段进行更新。当下次 Node(即使具有相同的名称)被创建时,DaemonSet Controller 还会使用最初的模板。</p>
|
||
|
<p>可以删除一个 DaemonSet。如果使用 <code>kubectl</code> 并指定 <code>--cascade=false</code> 选项,则 Pod 将被保留在 Node 上。然后可以创建具有不同模板的新 DaemonSet。具有不同模板的新 DaemonSet 将鞥能够通过 Label 匹配识别所有已经存在的 Pod。它不会修改或删除它们,即使是错误匹配了 Pod 模板。通过删除 Pod 或者 删除 Node,可以强制创建新的 Pod。</p>
|
||
|
<p>在 Kubernetes 1.6 或以后版本,可以在 DaemonSet 上 <a href="https://kubernetes.io/docs/tasks/manage-daemon/update-daemon-set/" target="_blank">执行滚动升级</a>。</p>
|
||
|
<h3 id="init-脚本">init 脚本</h3>
|
||
|
<p>很可能通过直接在一个 Node 上启动 daemon 进程(例如,使用 <code>init</code>、<code>upstartd</code>、或 <code>systemd</code>)。这非常好,然而基于 DaemonSet 来运行这些进程有如下一些好处:</p>
|
||
|
<ul>
|
||
|
<li>像对待应用程序一样,具备为 daemon 提供监控和管理日志的能力。</li>
|
||
|
<li>为 daemon 和应用城西使用相同的配置语言和工具(如 Pod 模板、<code>kubectl</code>)。</li>
|
||
|
<li>Kubernetes 未来版本可能会支持对 DaemonSet 创建 Pod 与 Node升级工作流进行集成。</li>
|
||
|
<li>在资源受限的容器中运行 daemon,能够增加 daemon 和应用容器的隔离性。然而这也实现了在容器中运行 daemon,但却不能在 Pod 中运行(例如,直接基于 Docker 启动)。</li>
|
||
|
</ul>
|
||
|
<h3 id="裸-pod">裸 Pod</h3>
|
||
|
<p>可能要直接创建 Pod,同时指定其运行在特定的 Node 上。
|
||
|
然而,DaemonSet 替换了由于任何原因被删除或终止的 Pod,例如 Node 失败、例行节点维护,比如内和升级。由于这个原因,我们应该使用 DaemonSet 而不是单独创建 Pod。</p>
|
||
|
<h3 id="静态-pod">静态 Pod</h3>
|
||
|
<p>很可能,通过在一个指定目录下编写文件来创建 Pod,该目录受 Kubelet 所监视。这些 Pod 被称为 <a href="https://kubernetes.io/docs/concepts/cluster-administration/static-pod/" target="_blank">静态 Pod</a>。
|
||
|
不像 DaemonSet,静态 Pod 不受 kubectl 和 其它 Kubernetes API 客户端管理。静态 Pod 不依赖于 apiserver,这使得它们在集群启动的情况下非常有用。
|
||
|
而且,未来静态 Pod 可能会被废弃掉。</p>
|
||
|
<h3 id="replication-controller">Replication Controller</h3>
|
||
|
<p>DaemonSet 与 <a href="https://kubernetes.io/docs/user-guide/replication-controller" target="_blank">Replication Controller</a> 非常类似,它们都能创建 Pod,这些 Pod 都具有不期望被终止的进程(例如,Web 服务器、存储服务器)。
|
||
|
为无状态的 Service 使用 Replication Controller,像 frontend,实现对副本的数量进行扩缩容、平滑升级,比之于精确控制 Pod 运行在某个主机上要重要得多。需要 Pod 副本总是运行在全部或特定主机上,并需要先于其他 Pod 启动,当这被认为非常重要时,应该使用 Daemon Controller。</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-11 12:36:39
|
||
|
</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="statefulset.html" class="navigation navigation-prev " aria-label="Previous page: 2.2.8 StatefulSet">
|
||
|
<i class="fa fa-angle-left"></i>
|
||
|
</a>
|
||
|
|
||
|
|
||
|
<a href="serviceaccount.html" class="navigation navigation-next " aria-label="Next page: 2.2.10 ServiceAccount">
|
||
|
<i class="fa fa-angle-right"></i>
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
<script>
|
||
|
var gitbook = gitbook || [];
|
||
|
gitbook.push(function() {
|
||
|
gitbook.page.hasChanged({"page":{"title":"2.2.9 DaemonSet","level":"1.2.2.9","depth":3,"next":{"title":"2.2.10 ServiceAccount","level":"1.2.2.10","depth":3,"path":"concepts/serviceaccount.md","ref":"concepts/serviceaccount.md","articles":[]},"previous":{"title":"2.2.8 StatefulSet","level":"1.2.2.8","depth":3,"path":"concepts/statefulset.md","ref":"concepts/statefulset.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.2","list_caption":"Fi
|
||
|
});
|
||
|
</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>
|
||
|
|