5311 lines
318 KiB
HTML
5311 lines
318 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>Volume · Kubernetes Handbook - Kubernetes 中文指南/云原生应用架构实践手册 · Jimmy Song</title>
|
||
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
|
||
<meta name="description" content="">
|
||
<meta name="generator" content="GitBook 3.2.3">
|
||
<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-prism/prism-ghcolors.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-lightbox/css/lightbox.min.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="persistent-volume.html" />
|
||
|
||
|
||
<link rel="prev" href="configmap-hot-update.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">回到主页</a>
|
||
</li>
|
||
|
||
|
||
<li>
|
||
<a href="https://jimmysong.io/awesome-cloud-native" target="_blank" class="custom-link">云原生开源项目大全</a>
|
||
</li>
|
||
|
||
|
||
<li>
|
||
<a href="https://cloudnative.to" target="_blank" class="custom-link">云原生社区</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="divider"></li>
|
||
|
||
|
||
|
||
|
||
<li class="header">前言</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="1.1" data-path="../">
|
||
|
||
<a href="../">
|
||
|
||
|
||
<b>1.1.</b>
|
||
|
||
序言
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">云原生</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="2.1" data-path="../cloud-native/cloud-native-definition.html">
|
||
|
||
<a href="../cloud-native/cloud-native-definition.html">
|
||
|
||
|
||
<b>2.1.</b>
|
||
|
||
云原生(Cloud Native)的定义
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.2" data-path="../cloud-native/cloud-native-philosophy.html">
|
||
|
||
<a href="../cloud-native/cloud-native-philosophy.html">
|
||
|
||
|
||
<b>2.2.</b>
|
||
|
||
云原生的设计哲学
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.3" data-path="../cloud-native/kubernetes-history.html">
|
||
|
||
<a href="../cloud-native/kubernetes-history.html">
|
||
|
||
|
||
<b>2.3.</b>
|
||
|
||
Kubernetes 的诞生
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.4" data-path="../cloud-native/kubernetes-and-cloud-native-app-overview.html">
|
||
|
||
<a href="../cloud-native/kubernetes-and-cloud-native-app-overview.html">
|
||
|
||
|
||
<b>2.4.</b>
|
||
|
||
Kubernetes 与云原生应用概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.5" data-path="../cloud-native/from-kubernetes-to-cloud-native.html">
|
||
|
||
<a href="../cloud-native/from-kubernetes-to-cloud-native.html">
|
||
|
||
|
||
<b>2.5.</b>
|
||
|
||
云原生应用之路 —— 从 Kubernetes 到云原生
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6" data-path="../cloud-native/define-cloud-native-app.html">
|
||
|
||
<a href="../cloud-native/define-cloud-native-app.html">
|
||
|
||
|
||
<b>2.6.</b>
|
||
|
||
定义云原生应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.6.1" data-path="../cloud-native/oam.html">
|
||
|
||
<a href="../cloud-native/oam.html">
|
||
|
||
|
||
<b>2.6.1.</b>
|
||
|
||
OAM
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.6.1.1" data-path="../cloud-native/workload.html">
|
||
|
||
<a href="../cloud-native/workload.html">
|
||
|
||
|
||
<b>2.6.1.1.</b>
|
||
|
||
Workload
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.2" data-path="../cloud-native/component.html">
|
||
|
||
<a href="../cloud-native/component.html">
|
||
|
||
|
||
<b>2.6.1.2.</b>
|
||
|
||
Component
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.3" data-path="../cloud-native/trait.html">
|
||
|
||
<a href="../cloud-native/trait.html">
|
||
|
||
|
||
<b>2.6.1.3.</b>
|
||
|
||
Trait
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.4" data-path="../cloud-native/application-scope.html">
|
||
|
||
<a href="../cloud-native/application-scope.html">
|
||
|
||
|
||
<b>2.6.1.4.</b>
|
||
|
||
Application Scope
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.5" data-path="../cloud-native/application-configuration.html">
|
||
|
||
<a href="../cloud-native/application-configuration.html">
|
||
|
||
|
||
<b>2.6.1.5.</b>
|
||
|
||
Application Configuration
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.2" data-path="../cloud-native/crossplane.html">
|
||
|
||
<a href="../cloud-native/crossplane.html">
|
||
|
||
|
||
<b>2.6.2.</b>
|
||
|
||
Crossplane
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.7" data-path="../cloud-native/cloud-native-programming-languages.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-languages.html">
|
||
|
||
|
||
<b>2.7.</b>
|
||
|
||
云原生平台配置语言
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.7.1" data-path="../cloud-native/cloud-native-programming-language-ballerina.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-language-ballerina.html">
|
||
|
||
|
||
<b>2.7.1.</b>
|
||
|
||
Ballerina
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.7.2" data-path="../cloud-native/cloud-native-programming-language-pulumi.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-language-pulumi.html">
|
||
|
||
|
||
<b>2.7.2.</b>
|
||
|
||
Pulumi
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.8" data-path="../cloud-native/the-future-of-cloud-native.html">
|
||
|
||
<a href="../cloud-native/the-future-of-cloud-native.html">
|
||
|
||
|
||
<b>2.8.</b>
|
||
|
||
云原生的未来
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">快速入门</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="3.1" data-path="../cloud-native/quick-start.html">
|
||
|
||
<a href="../cloud-native/quick-start.html">
|
||
|
||
|
||
<b>3.1.</b>
|
||
|
||
云原生新手入门指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.2" data-path="../cloud-native/play-with-kubernetes.html">
|
||
|
||
<a href="../cloud-native/play-with-kubernetes.html">
|
||
|
||
|
||
<b>3.2.</b>
|
||
|
||
Play with Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.3" data-path="../cloud-native/cloud-native-local-quick-start.html">
|
||
|
||
<a href="../cloud-native/cloud-native-local-quick-start.html">
|
||
|
||
|
||
<b>3.3.</b>
|
||
|
||
快速部署一个云原生本地实验环境
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4" data-path="../cloud-native/setup-kubernetes-with-rancher-and-aliyun.html">
|
||
|
||
<a href="../cloud-native/setup-kubernetes-with-rancher-and-aliyun.html">
|
||
|
||
|
||
<b>3.4.</b>
|
||
|
||
使用 Rancher 在阿里云上部署 Kubenretes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">概念与原理</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="4.1" data-path="./">
|
||
|
||
<a href="./">
|
||
|
||
|
||
<b>4.1.</b>
|
||
|
||
Kubernetes 架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.1.1" data-path="concepts.html">
|
||
|
||
<a href="concepts.html">
|
||
|
||
|
||
<b>4.1.1.</b>
|
||
|
||
Kubernetes 的设计理念
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.1.2" data-path="etcd.html">
|
||
|
||
<a href="etcd.html">
|
||
|
||
|
||
<b>4.1.2.</b>
|
||
|
||
Etcd 解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.1.3" data-path="open-interfaces.html">
|
||
|
||
<a href="open-interfaces.html">
|
||
|
||
|
||
<b>4.1.3.</b>
|
||
|
||
开放接口
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.1.3.1" data-path="cri.html">
|
||
|
||
<a href="cri.html">
|
||
|
||
|
||
<b>4.1.3.1.</b>
|
||
|
||
容器运行时接口(CRI)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.1.3.2" data-path="cni.html">
|
||
|
||
<a href="cni.html">
|
||
|
||
|
||
<b>4.1.3.2.</b>
|
||
|
||
容器网络接口(CNI)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.1.3.3" data-path="csi.html">
|
||
|
||
<a href="csi.html">
|
||
|
||
|
||
<b>4.1.3.3.</b>
|
||
|
||
容器存储接口(CSI)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.1.4" data-path="objects.html">
|
||
|
||
<a href="objects.html">
|
||
|
||
|
||
<b>4.1.4.</b>
|
||
|
||
Kubernetes 中的资源对象
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2" data-path="pod-state-and-lifecycle.html">
|
||
|
||
<a href="pod-state-and-lifecycle.html">
|
||
|
||
|
||
<b>4.2.</b>
|
||
|
||
Pod 状态与生命周期管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.2.1" data-path="pod-overview.html">
|
||
|
||
<a href="pod-overview.html">
|
||
|
||
|
||
<b>4.2.1.</b>
|
||
|
||
Pod 概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.2" data-path="pod.html">
|
||
|
||
<a href="pod.html">
|
||
|
||
|
||
<b>4.2.2.</b>
|
||
|
||
Pod 解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.3" data-path="init-containers.html">
|
||
|
||
<a href="init-containers.html">
|
||
|
||
|
||
<b>4.2.3.</b>
|
||
|
||
Init 容器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.4" data-path="pause-container.html">
|
||
|
||
<a href="pause-container.html">
|
||
|
||
|
||
<b>4.2.4.</b>
|
||
|
||
Pause 容器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.5" data-path="pod-security-policy.html">
|
||
|
||
<a href="pod-security-policy.html">
|
||
|
||
|
||
<b>4.2.5.</b>
|
||
|
||
Pod 安全策略
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.6" data-path="pod-lifecycle.html">
|
||
|
||
<a href="pod-lifecycle.html">
|
||
|
||
|
||
<b>4.2.6.</b>
|
||
|
||
Pod 的生命周期
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.7" data-path="pod-hook.html">
|
||
|
||
<a href="pod-hook.html">
|
||
|
||
|
||
<b>4.2.7.</b>
|
||
|
||
Pod Hook
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.8" data-path="pod-preset.html">
|
||
|
||
<a href="pod-preset.html">
|
||
|
||
|
||
<b>4.2.8.</b>
|
||
|
||
Pod Preset
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.9" data-path="pod-disruption-budget.html">
|
||
|
||
<a href="pod-disruption-budget.html">
|
||
|
||
|
||
<b>4.2.9.</b>
|
||
|
||
Pod 中断与 PDB(Pod 中断预算)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3" data-path="cluster.html">
|
||
|
||
<a href="cluster.html">
|
||
|
||
|
||
<b>4.3.</b>
|
||
|
||
集群资源管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.3.1" data-path="node.html">
|
||
|
||
<a href="node.html">
|
||
|
||
|
||
<b>4.3.1.</b>
|
||
|
||
Node
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.2" data-path="namespace.html">
|
||
|
||
<a href="namespace.html">
|
||
|
||
|
||
<b>4.3.2.</b>
|
||
|
||
Namespace
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.3" data-path="label.html">
|
||
|
||
<a href="label.html">
|
||
|
||
|
||
<b>4.3.3.</b>
|
||
|
||
Label
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.4" data-path="annotation.html">
|
||
|
||
<a href="annotation.html">
|
||
|
||
|
||
<b>4.3.4.</b>
|
||
|
||
Annotation
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.5" data-path="taint-and-toleration.html">
|
||
|
||
<a href="taint-and-toleration.html">
|
||
|
||
|
||
<b>4.3.5.</b>
|
||
|
||
Taint 和 Toleration(污点和容忍)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.6" data-path="garbage-collection.html">
|
||
|
||
<a href="garbage-collection.html">
|
||
|
||
|
||
<b>4.3.6.</b>
|
||
|
||
垃圾收集
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4" data-path="controllers.html">
|
||
|
||
<a href="controllers.html">
|
||
|
||
|
||
<b>4.4.</b>
|
||
|
||
控制器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.4.1" data-path="deployment.html">
|
||
|
||
<a href="deployment.html">
|
||
|
||
|
||
<b>4.4.1.</b>
|
||
|
||
Deployment
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.2" data-path="statefulset.html">
|
||
|
||
<a href="statefulset.html">
|
||
|
||
|
||
<b>4.4.2.</b>
|
||
|
||
StatefulSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.3" data-path="daemonset.html">
|
||
|
||
<a href="daemonset.html">
|
||
|
||
|
||
<b>4.4.3.</b>
|
||
|
||
DaemonSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.4" data-path="replicaset.html">
|
||
|
||
<a href="replicaset.html">
|
||
|
||
|
||
<b>4.4.4.</b>
|
||
|
||
ReplicationController 和 ReplicaSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.5" data-path="job.html">
|
||
|
||
<a href="job.html">
|
||
|
||
|
||
<b>4.4.5.</b>
|
||
|
||
Job
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.6" data-path="cronjob.html">
|
||
|
||
<a href="cronjob.html">
|
||
|
||
|
||
<b>4.4.6.</b>
|
||
|
||
CronJob
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.7" data-path="horizontal-pod-autoscaling.html">
|
||
|
||
<a href="horizontal-pod-autoscaling.html">
|
||
|
||
|
||
<b>4.4.7.</b>
|
||
|
||
Horizontal Pod Autoscaling
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.4.7.1" data-path="custom-metrics-hpa.html">
|
||
|
||
<a href="custom-metrics-hpa.html">
|
||
|
||
|
||
<b>4.4.7.1.</b>
|
||
|
||
自定义指标 HPA
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.8" data-path="admission-controller.html">
|
||
|
||
<a href="admission-controller.html">
|
||
|
||
|
||
<b>4.4.8.</b>
|
||
|
||
准入控制器(Admission Controller)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5" data-path="service-discovery.html">
|
||
|
||
<a href="service-discovery.html">
|
||
|
||
|
||
<b>4.5.</b>
|
||
|
||
服务发现与路由
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.5.1" data-path="service.html">
|
||
|
||
<a href="service.html">
|
||
|
||
|
||
<b>4.5.1.</b>
|
||
|
||
Service
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.2" data-path="topology-aware-routing.html">
|
||
|
||
<a href="topology-aware-routing.html">
|
||
|
||
|
||
<b>4.5.2.</b>
|
||
|
||
拓扑感知路由
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.3" data-path="ingress.html">
|
||
|
||
<a href="ingress.html">
|
||
|
||
|
||
<b>4.5.3.</b>
|
||
|
||
Ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.5.3.1" data-path="traefik-ingress-controller.html">
|
||
|
||
<a href="traefik-ingress-controller.html">
|
||
|
||
|
||
<b>4.5.3.1.</b>
|
||
|
||
Traefik Ingress Controller
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.4" data-path="gateway.html">
|
||
|
||
<a href="gateway.html">
|
||
|
||
|
||
<b>4.5.4.</b>
|
||
|
||
Gateway
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6" data-path="authentication-and-permission.html">
|
||
|
||
<a href="authentication-and-permission.html">
|
||
|
||
|
||
<b>4.6.</b>
|
||
|
||
身份与权限控制
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.6.1" data-path="serviceaccount.html">
|
||
|
||
<a href="serviceaccount.html">
|
||
|
||
|
||
<b>4.6.1.</b>
|
||
|
||
ServiceAccount
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6.2" data-path="rbac.html">
|
||
|
||
<a href="rbac.html">
|
||
|
||
|
||
<b>4.6.2.</b>
|
||
|
||
基于角色的访问控制(RBAC)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6.3" data-path="network-policy.html">
|
||
|
||
<a href="network-policy.html">
|
||
|
||
|
||
<b>4.6.3.</b>
|
||
|
||
NetworkPolicy
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.7" data-path="networking.html">
|
||
|
||
<a href="networking.html">
|
||
|
||
|
||
<b>4.7.</b>
|
||
|
||
网络
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.7.1" data-path="flannel.html">
|
||
|
||
<a href="flannel.html">
|
||
|
||
|
||
<b>4.7.1.</b>
|
||
|
||
扁平网络 Flannel
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.7.2" data-path="calico.html">
|
||
|
||
<a href="calico.html">
|
||
|
||
|
||
<b>4.7.2.</b>
|
||
|
||
非 Overlay 扁平网络 Calico
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.7.3" data-path="cilium.html">
|
||
|
||
<a href="cilium.html">
|
||
|
||
|
||
<b>4.7.3.</b>
|
||
|
||
基于 eBPF 的网络 Cilium
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.7.3.1" data-path="cilium-concepts.html">
|
||
|
||
<a href="cilium-concepts.html">
|
||
|
||
|
||
<b>4.7.3.1.</b>
|
||
|
||
Cilium 架构设计与概念解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.8" data-path="storage.html">
|
||
|
||
<a href="storage.html">
|
||
|
||
|
||
<b>4.8.</b>
|
||
|
||
存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.8.1" data-path="secret.html">
|
||
|
||
<a href="secret.html">
|
||
|
||
|
||
<b>4.8.1.</b>
|
||
|
||
Secret
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.8.2" data-path="configmap.html">
|
||
|
||
<a href="configmap.html">
|
||
|
||
|
||
<b>4.8.2.</b>
|
||
|
||
ConfigMap
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.8.2.1" data-path="configmap-hot-update.html">
|
||
|
||
<a href="configmap-hot-update.html">
|
||
|
||
|
||
<b>4.8.2.1.</b>
|
||
|
||
ConfigMap 的热更新
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter active" data-level="4.8.3" data-path="volume.html">
|
||
|
||
<a href="volume.html">
|
||
|
||
|
||
<b>4.8.3.</b>
|
||
|
||
Volume
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.8.4" data-path="persistent-volume.html">
|
||
|
||
<a href="persistent-volume.html">
|
||
|
||
|
||
<b>4.8.4.</b>
|
||
|
||
持久化卷(Persistent Volume)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.8.5" data-path="storageclass.html">
|
||
|
||
<a href="storageclass.html">
|
||
|
||
|
||
<b>4.8.5.</b>
|
||
|
||
Storage Class
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.8.6" data-path="local-persistent-storage.html">
|
||
|
||
<a href="local-persistent-storage.html">
|
||
|
||
|
||
<b>4.8.6.</b>
|
||
|
||
本地持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.9" data-path="extension.html">
|
||
|
||
<a href="extension.html">
|
||
|
||
|
||
<b>4.9.</b>
|
||
|
||
集群扩展
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.9.1" data-path="custom-resource.html">
|
||
|
||
<a href="custom-resource.html">
|
||
|
||
|
||
<b>4.9.1.</b>
|
||
|
||
使用自定义资源扩展 API
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.9.2" data-path="crd.html">
|
||
|
||
<a href="crd.html">
|
||
|
||
|
||
<b>4.9.2.</b>
|
||
|
||
使用 CRD 扩展 Kubernetes API
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.9.3" data-path="aggregated-api-server.html">
|
||
|
||
<a href="aggregated-api-server.html">
|
||
|
||
|
||
<b>4.9.3.</b>
|
||
|
||
Aggregated API Server
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.9.4" data-path="apiservice.html">
|
||
|
||
<a href="apiservice.html">
|
||
|
||
|
||
<b>4.9.4.</b>
|
||
|
||
APIService
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.9.5" data-path="service-catalog.html">
|
||
|
||
<a href="service-catalog.html">
|
||
|
||
|
||
<b>4.9.5.</b>
|
||
|
||
服务目录(Service Catalog)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.10" data-path="multicluster.html">
|
||
|
||
<a href="multicluster.html">
|
||
|
||
|
||
<b>4.10.</b>
|
||
|
||
多集群管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.10.1" data-path="multi-cluster-services-api.html">
|
||
|
||
<a href="multi-cluster-services-api.html">
|
||
|
||
|
||
<b>4.10.1.</b>
|
||
|
||
多集群服务 API(Multi-Cluster Services API)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.10.2" data-path="../practice/federation.html">
|
||
|
||
<a href="../practice/federation.html">
|
||
|
||
|
||
<b>4.10.2.</b>
|
||
|
||
集群联邦(Cluster Federation)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.11" data-path="scheduling.html">
|
||
|
||
<a href="scheduling.html">
|
||
|
||
|
||
<b>4.11.</b>
|
||
|
||
资源调度
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.11.1" data-path="qos.html">
|
||
|
||
<a href="qos.html">
|
||
|
||
|
||
<b>4.11.1.</b>
|
||
|
||
服务质量等级(QoS)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">用户指南</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="5.1" data-path="../guide/">
|
||
|
||
<a href="../guide/">
|
||
|
||
|
||
<b>5.1.</b>
|
||
|
||
用户指南概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2" data-path="../guide/resource-configuration.html">
|
||
|
||
<a href="../guide/resource-configuration.html">
|
||
|
||
|
||
<b>5.2.</b>
|
||
|
||
资源对象配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.2.1" data-path="../guide/configure-liveness-readiness-probes.html">
|
||
|
||
<a href="../guide/configure-liveness-readiness-probes.html">
|
||
|
||
|
||
<b>5.2.1.</b>
|
||
|
||
配置 Pod 的 liveness 和 readiness 探针
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.2" data-path="../guide/configure-pod-service-account.html">
|
||
|
||
<a href="../guide/configure-pod-service-account.html">
|
||
|
||
|
||
<b>5.2.2.</b>
|
||
|
||
配置 Pod 的 Service Account
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.3" data-path="../guide/secret-configuration.html">
|
||
|
||
<a href="../guide/secret-configuration.html">
|
||
|
||
|
||
<b>5.2.3.</b>
|
||
|
||
Secret 配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.4" data-path="../guide/resource-quota-management.html">
|
||
|
||
<a href="../guide/resource-quota-management.html">
|
||
|
||
|
||
<b>5.2.4.</b>
|
||
|
||
管理 namespace 中的资源配额
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.3" data-path="../guide/command-usage.html">
|
||
|
||
<a href="../guide/command-usage.html">
|
||
|
||
|
||
<b>5.3.</b>
|
||
|
||
命令使用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.3.1" data-path="../guide/docker-cli-to-kubectl.html">
|
||
|
||
<a href="../guide/docker-cli-to-kubectl.html">
|
||
|
||
|
||
<b>5.3.1.</b>
|
||
|
||
Docker 用户过渡到 kubectl 命令行指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.3.2" data-path="../guide/using-kubectl.html">
|
||
|
||
<a href="../guide/using-kubectl.html">
|
||
|
||
|
||
<b>5.3.2.</b>
|
||
|
||
kubectl 命令概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.3.3" data-path="../guide/kubectl-cheatsheet.html">
|
||
|
||
<a href="../guide/kubectl-cheatsheet.html">
|
||
|
||
|
||
<b>5.3.3.</b>
|
||
|
||
kubectl 命令技巧大全
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.3.4" data-path="../guide/using-etcdctl-to-access-kubernetes-data.html">
|
||
|
||
<a href="../guide/using-etcdctl-to-access-kubernetes-data.html">
|
||
|
||
|
||
<b>5.3.4.</b>
|
||
|
||
使用 etcdctl 访问 Kubernetes 数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4" data-path="../guide/cluster-security-management.html">
|
||
|
||
<a href="../guide/cluster-security-management.html">
|
||
|
||
|
||
<b>5.4.</b>
|
||
|
||
集群安全性管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.4.1" data-path="../guide/managing-tls-in-a-cluster.html">
|
||
|
||
<a href="../guide/managing-tls-in-a-cluster.html">
|
||
|
||
|
||
<b>5.4.1.</b>
|
||
|
||
管理集群中的 TLS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.2" data-path="../guide/kubelet-authentication-authorization.html">
|
||
|
||
<a href="../guide/kubelet-authentication-authorization.html">
|
||
|
||
|
||
<b>5.4.2.</b>
|
||
|
||
kubelet 的认证授权
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.3" data-path="../guide/tls-bootstrapping.html">
|
||
|
||
<a href="../guide/tls-bootstrapping.html">
|
||
|
||
|
||
<b>5.4.3.</b>
|
||
|
||
TLS Bootstrap
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.4" data-path="../guide/kubectl-user-authentication-authorization.html">
|
||
|
||
<a href="../guide/kubectl-user-authentication-authorization.html">
|
||
|
||
|
||
<b>5.4.4.</b>
|
||
|
||
创建用户认证授权的 kubeconfig 文件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.5" data-path="../guide/ip-masq-agent.html">
|
||
|
||
<a href="../guide/ip-masq-agent.html">
|
||
|
||
|
||
<b>5.4.5.</b>
|
||
|
||
IP 伪装代理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.6" data-path="../guide/auth-with-kubeconfig-or-token.html">
|
||
|
||
<a href="../guide/auth-with-kubeconfig-or-token.html">
|
||
|
||
|
||
<b>5.4.6.</b>
|
||
|
||
使用 kubeconfig 或 token 进行用户身份认证
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.7" data-path="../guide/authentication.html">
|
||
|
||
<a href="../guide/authentication.html">
|
||
|
||
|
||
<b>5.4.7.</b>
|
||
|
||
Kubernetes 中的用户与身份认证授权
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.8" data-path="../guide/kubernetes-security-best-practice.html">
|
||
|
||
<a href="../guide/kubernetes-security-best-practice.html">
|
||
|
||
|
||
<b>5.4.8.</b>
|
||
|
||
Kubernetes 集群安全性配置最佳实践
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5" data-path="../guide/access-kubernetes-cluster.html">
|
||
|
||
<a href="../guide/access-kubernetes-cluster.html">
|
||
|
||
|
||
<b>5.5.</b>
|
||
|
||
访问 Kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.5.1" data-path="../guide/access-cluster.html">
|
||
|
||
<a href="../guide/access-cluster.html">
|
||
|
||
|
||
<b>5.5.1.</b>
|
||
|
||
访问集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.2" data-path="../guide/authenticate-across-clusters-kubeconfig.html">
|
||
|
||
<a href="../guide/authenticate-across-clusters-kubeconfig.html">
|
||
|
||
|
||
<b>5.5.2.</b>
|
||
|
||
使用 kubeconfig 文件配置跨集群认证
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.3" data-path="../guide/connecting-to-applications-port-forward.html">
|
||
|
||
<a href="../guide/connecting-to-applications-port-forward.html">
|
||
|
||
|
||
<b>5.5.3.</b>
|
||
|
||
通过端口转发访问集群中的应用程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.4" data-path="../guide/service-access-application-cluster.html">
|
||
|
||
<a href="../guide/service-access-application-cluster.html">
|
||
|
||
|
||
<b>5.5.4.</b>
|
||
|
||
使用 service 访问群集中的应用程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.5" data-path="../guide/accessing-kubernetes-pods-from-outside-of-the-cluster.html">
|
||
|
||
<a href="../guide/accessing-kubernetes-pods-from-outside-of-the-cluster.html">
|
||
|
||
|
||
<b>5.5.5.</b>
|
||
|
||
从外部访问 Kubernetes 中的 Pod
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.6" data-path="../guide/kubernetes-desktop-client.html">
|
||
|
||
<a href="../guide/kubernetes-desktop-client.html">
|
||
|
||
|
||
<b>5.5.6.</b>
|
||
|
||
Lens - Kubernetes IDE
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.7" data-path="../guide/kubernator-kubernetes-ui.html">
|
||
|
||
<a href="../guide/kubernator-kubernetes-ui.html">
|
||
|
||
|
||
<b>5.5.7.</b>
|
||
|
||
Kubernator - 更底层的 Kubernetes UI
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6" data-path="../guide/application-development-deployment-flow.html">
|
||
|
||
<a href="../guide/application-development-deployment-flow.html">
|
||
|
||
|
||
<b>5.6.</b>
|
||
|
||
在 Kubernetes 中开发部署应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.1" data-path="../guide/deploy-applications-in-kubernetes.html">
|
||
|
||
<a href="../guide/deploy-applications-in-kubernetes.html">
|
||
|
||
|
||
<b>5.6.1.</b>
|
||
|
||
适用于 Kubernetes 的应用开发部署流程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.2" data-path="../guide/migrating-hadoop-yarn-to-kubernetes.html">
|
||
|
||
<a href="../guide/migrating-hadoop-yarn-to-kubernetes.html">
|
||
|
||
|
||
<b>5.6.2.</b>
|
||
|
||
迁移传统应用到 Kubernetes 中 —— 以 Hadoop YARN 为例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.3" data-path="../guide/using-statefulset.html">
|
||
|
||
<a href="../guide/using-statefulset.html">
|
||
|
||
|
||
<b>5.6.3.</b>
|
||
|
||
使用 StatefulSet 部署用状态应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">最佳实践</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="6.1" data-path="../practice/">
|
||
|
||
<a href="../practice/">
|
||
|
||
|
||
<b>6.1.</b>
|
||
|
||
最佳实践概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2" data-path="../practice/install-kubernetes-on-centos.html">
|
||
|
||
<a href="../practice/install-kubernetes-on-centos.html">
|
||
|
||
|
||
<b>6.2.</b>
|
||
|
||
在 CentOS 上部署 Kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.2.1" data-path="../practice/create-tls-and-secret-key.html">
|
||
|
||
<a href="../practice/create-tls-and-secret-key.html">
|
||
|
||
|
||
<b>6.2.1.</b>
|
||
|
||
创建 TLS 证书和秘钥
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.2" data-path="../practice/create-kubeconfig.html">
|
||
|
||
<a href="../practice/create-kubeconfig.html">
|
||
|
||
|
||
<b>6.2.2.</b>
|
||
|
||
创建 kubeconfig 文件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.3" data-path="../practice/etcd-cluster-installation.html">
|
||
|
||
<a href="../practice/etcd-cluster-installation.html">
|
||
|
||
|
||
<b>6.2.3.</b>
|
||
|
||
创建高可用 etcd 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.4" data-path="../practice/kubectl-installation.html">
|
||
|
||
<a href="../practice/kubectl-installation.html">
|
||
|
||
|
||
<b>6.2.4.</b>
|
||
|
||
安装 kubectl 命令行工具
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.5" data-path="../practice/master-installation.html">
|
||
|
||
<a href="../practice/master-installation.html">
|
||
|
||
|
||
<b>6.2.5.</b>
|
||
|
||
部署 master 节点
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.6" data-path="../practice/flannel-installation.html">
|
||
|
||
<a href="../practice/flannel-installation.html">
|
||
|
||
|
||
<b>6.2.6.</b>
|
||
|
||
安装 flannel 网络插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.7" data-path="../practice/node-installation.html">
|
||
|
||
<a href="../practice/node-installation.html">
|
||
|
||
|
||
<b>6.2.7.</b>
|
||
|
||
部署 node 节点
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.8" data-path="../practice/kubedns-addon-installation.html">
|
||
|
||
<a href="../practice/kubedns-addon-installation.html">
|
||
|
||
|
||
<b>6.2.8.</b>
|
||
|
||
安装 kubedns 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.9" data-path="../practice/dashboard-addon-installation.html">
|
||
|
||
<a href="../practice/dashboard-addon-installation.html">
|
||
|
||
|
||
<b>6.2.9.</b>
|
||
|
||
安装 dashboard 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.10" data-path="../practice/heapster-addon-installation.html">
|
||
|
||
<a href="../practice/heapster-addon-installation.html">
|
||
|
||
|
||
<b>6.2.10.</b>
|
||
|
||
安装 heapster 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.11" data-path="../practice/efk-addon-installation.html">
|
||
|
||
<a href="../practice/efk-addon-installation.html">
|
||
|
||
|
||
<b>6.2.11.</b>
|
||
|
||
安装 EFK 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3" data-path="../practice/install-kubernetes-with-kubeadm.html">
|
||
|
||
<a href="../practice/install-kubernetes-with-kubeadm.html">
|
||
|
||
|
||
<b>6.3.</b>
|
||
|
||
生产级的 Kubernetes 简化管理工具 kubeadm
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.3.1" data-path="../practice/install-kubernetes-on-ubuntu-server-16.04-with-kubeadm.html">
|
||
|
||
<a href="../practice/install-kubernetes-on-ubuntu-server-16.04-with-kubeadm.html">
|
||
|
||
|
||
<b>6.3.1.</b>
|
||
|
||
使用 kubeadm 在 Ubuntu Server 16.04 上快速构建测试集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4" data-path="../practice/service-discovery-and-loadbalancing.html">
|
||
|
||
<a href="../practice/service-discovery-and-loadbalancing.html">
|
||
|
||
|
||
<b>6.4.</b>
|
||
|
||
服务发现与负载均衡
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.4.1" data-path="../practice/traefik-ingress-installation.html">
|
||
|
||
<a href="../practice/traefik-ingress-installation.html">
|
||
|
||
|
||
<b>6.4.1.</b>
|
||
|
||
安装 Traefik ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.2" data-path="../practice/distributed-load-test.html">
|
||
|
||
<a href="../practice/distributed-load-test.html">
|
||
|
||
|
||
<b>6.4.2.</b>
|
||
|
||
分布式负载测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.3" data-path="../practice/network-and-cluster-perfermance-test.html">
|
||
|
||
<a href="../practice/network-and-cluster-perfermance-test.html">
|
||
|
||
|
||
<b>6.4.3.</b>
|
||
|
||
网络和集群性能测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.4" data-path="../practice/edge-node-configuration.html">
|
||
|
||
<a href="../practice/edge-node-configuration.html">
|
||
|
||
|
||
<b>6.4.4.</b>
|
||
|
||
边缘节点配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.5" data-path="../practice/nginx-ingress-installation.html">
|
||
|
||
<a href="../practice/nginx-ingress-installation.html">
|
||
|
||
|
||
<b>6.4.5.</b>
|
||
|
||
安装 Nginx ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.6" data-path="../practice/dns-installation.html">
|
||
|
||
<a href="../practice/dns-installation.html">
|
||
|
||
|
||
<b>6.4.6.</b>
|
||
|
||
安装配置 DNS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.4.6.1" data-path="../practice/configuring-dns.html">
|
||
|
||
<a href="../practice/configuring-dns.html">
|
||
|
||
|
||
<b>6.4.6.1.</b>
|
||
|
||
安装配置 Kube-dns
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.6.2" data-path="../practice/coredns.html">
|
||
|
||
<a href="../practice/coredns.html">
|
||
|
||
|
||
<b>6.4.6.2.</b>
|
||
|
||
安装配置 CoreDNS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5" data-path="../practice/operation.html">
|
||
|
||
<a href="../practice/operation.html">
|
||
|
||
|
||
<b>6.5.</b>
|
||
|
||
运维管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.5.1" data-path="../practice/master-ha.html">
|
||
|
||
<a href="../practice/master-ha.html">
|
||
|
||
|
||
<b>6.5.1.</b>
|
||
|
||
Master 节点高可用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.2" data-path="../practice/service-rolling-update.html">
|
||
|
||
<a href="../practice/service-rolling-update.html">
|
||
|
||
|
||
<b>6.5.2.</b>
|
||
|
||
服务滚动升级
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.3" data-path="../practice/app-log-collection.html">
|
||
|
||
<a href="../practice/app-log-collection.html">
|
||
|
||
|
||
<b>6.5.3.</b>
|
||
|
||
应用日志收集
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.4" data-path="../practice/configuration-best-practice.html">
|
||
|
||
<a href="../practice/configuration-best-practice.html">
|
||
|
||
|
||
<b>6.5.4.</b>
|
||
|
||
配置最佳实践
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.5" data-path="../practice/monitor.html">
|
||
|
||
<a href="../practice/monitor.html">
|
||
|
||
|
||
<b>6.5.5.</b>
|
||
|
||
集群及应用监控
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.6" data-path="../practice/data-persistence-problem.html">
|
||
|
||
<a href="../practice/data-persistence-problem.html">
|
||
|
||
|
||
<b>6.5.6.</b>
|
||
|
||
数据持久化问题
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.7" data-path="../practice/manage-compute-resources-container.html">
|
||
|
||
<a href="../practice/manage-compute-resources-container.html">
|
||
|
||
|
||
<b>6.5.7.</b>
|
||
|
||
管理容器的计算资源
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6" data-path="../practice/storage.html">
|
||
|
||
<a href="../practice/storage.html">
|
||
|
||
|
||
<b>6.6.</b>
|
||
|
||
存储管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.1" data-path="../practice/glusterfs.html">
|
||
|
||
<a href="../practice/glusterfs.html">
|
||
|
||
|
||
<b>6.6.1.</b>
|
||
|
||
GlusterFS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.1.1" data-path="../practice/using-glusterfs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-glusterfs-for-persistent-storage.html">
|
||
|
||
|
||
<b>6.6.1.1.</b>
|
||
|
||
使用 GlusterFS 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.1.2" data-path="../practice/using-heketi-gluster-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-heketi-gluster-for-persistent-storage.html">
|
||
|
||
|
||
<b>6.6.1.2.</b>
|
||
|
||
使用 Heketi 作为 Kubernetes 的持久存储 GlusterFS 的 external provisioner
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.1.3" data-path="../practice/storage-for-containers-using-glusterfs-with-openshift.html">
|
||
|
||
<a href="../practice/storage-for-containers-using-glusterfs-with-openshift.html">
|
||
|
||
|
||
<b>6.6.1.3.</b>
|
||
|
||
在 OpenShift 中使用 GlusterFS 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.2" data-path="../practice/glusterd-2.0.html">
|
||
|
||
<a href="../practice/glusterd-2.0.html">
|
||
|
||
|
||
<b>6.6.2.</b>
|
||
|
||
GlusterD-2.0
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.3" data-path="../practice/ceph.html">
|
||
|
||
<a href="../practice/ceph.html">
|
||
|
||
|
||
<b>6.6.3.</b>
|
||
|
||
Ceph
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.3.1" data-path="../practice/ceph-helm-install-guide-zh.html">
|
||
|
||
<a href="../practice/ceph-helm-install-guide-zh.html">
|
||
|
||
|
||
<b>6.6.3.1.</b>
|
||
|
||
用 Helm 托管安装 Ceph 集群并提供后端存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.3.2" data-path="../practice/using-ceph-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-ceph-for-persistent-storage.html">
|
||
|
||
|
||
<b>6.6.3.2.</b>
|
||
|
||
使用 Ceph 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.3.3" data-path="../practice/rbd-provisioner.html">
|
||
|
||
<a href="../practice/rbd-provisioner.html">
|
||
|
||
|
||
<b>6.6.3.3.</b>
|
||
|
||
使用 rbd-provisioner 提供 rbd 持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.4" data-path="../practice/openebs.html">
|
||
|
||
<a href="../practice/openebs.html">
|
||
|
||
|
||
<b>6.6.4.</b>
|
||
|
||
OpenEBS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.4.1" data-path="../practice/using-openebs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-openebs-for-persistent-storage.html">
|
||
|
||
|
||
<b>6.6.4.1.</b>
|
||
|
||
使用 OpenEBS 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.5" data-path="../practice/rook.html">
|
||
|
||
<a href="../practice/rook.html">
|
||
|
||
|
||
<b>6.6.5.</b>
|
||
|
||
Rook
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.6" data-path="../practice/nfs.html">
|
||
|
||
<a href="../practice/nfs.html">
|
||
|
||
|
||
<b>6.6.6.</b>
|
||
|
||
NFS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.6.1" data-path="../practice/using-nfs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-nfs-for-persistent-storage.html">
|
||
|
||
|
||
<b>6.6.6.1.</b>
|
||
|
||
利用 NFS 动态提供 Kubernetes 后端存储卷
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.7" data-path="../practice/monitoring.html">
|
||
|
||
<a href="../practice/monitoring.html">
|
||
|
||
|
||
<b>6.7.</b>
|
||
|
||
集群与应用监控
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.7.1" data-path="../practice/heapster.html">
|
||
|
||
<a href="../practice/heapster.html">
|
||
|
||
|
||
<b>6.7.1.</b>
|
||
|
||
Heapster
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.7.1.1" data-path="../practice/using-heapster-to-get-object-metrics.html">
|
||
|
||
<a href="../practice/using-heapster-to-get-object-metrics.html">
|
||
|
||
|
||
<b>6.7.1.1.</b>
|
||
|
||
使用 Heapster 获取集群和对象的 metric 数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.7.2" data-path="../practice/prometheus.html">
|
||
|
||
<a href="../practice/prometheus.html">
|
||
|
||
|
||
<b>6.7.2.</b>
|
||
|
||
Prometheus
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.7.2.1" data-path="../practice/using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
||
<a href="../practice/using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
||
|
||
<b>6.7.2.1.</b>
|
||
|
||
使用 Prometheus 监控 Kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.7.2.2" data-path="../practice/promql.html">
|
||
|
||
<a href="../practice/promql.html">
|
||
|
||
|
||
<b>6.7.2.2.</b>
|
||
|
||
Prometheus 查询语言 PromQL 使用说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.8" data-path="../practice/distributed-tracing.html">
|
||
|
||
<a href="../practice/distributed-tracing.html">
|
||
|
||
|
||
<b>6.8.</b>
|
||
|
||
分布式追踪
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.8.1" data-path="../practice/opentracing.html">
|
||
|
||
<a href="../practice/opentracing.html">
|
||
|
||
|
||
<b>6.8.1.</b>
|
||
|
||
OpenTracing
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.9" data-path="../practice/services-management-tool.html">
|
||
|
||
<a href="../practice/services-management-tool.html">
|
||
|
||
|
||
<b>6.9.</b>
|
||
|
||
服务编排管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.9.1" data-path="../practice/helm.html">
|
||
|
||
<a href="../practice/helm.html">
|
||
|
||
|
||
<b>6.9.1.</b>
|
||
|
||
使用 Helm 管理 Kubernetes 应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.9.2" data-path="../practice/create-private-charts-repo.html">
|
||
|
||
<a href="../practice/create-private-charts-repo.html">
|
||
|
||
|
||
<b>6.9.2.</b>
|
||
|
||
构建私有 Chart 仓库
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.10" data-path="../practice/ci-cd.html">
|
||
|
||
<a href="../practice/ci-cd.html">
|
||
|
||
|
||
<b>6.10.</b>
|
||
|
||
持续集成与发布(CI/CD)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.10.1" data-path="../practice/jenkins-ci-cd.html">
|
||
|
||
<a href="../practice/jenkins-ci-cd.html">
|
||
|
||
|
||
<b>6.10.1.</b>
|
||
|
||
使用 Jenkins 进行持续集成与发布
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.10.2" data-path="../practice/drone-ci-cd.html">
|
||
|
||
<a href="../practice/drone-ci-cd.html">
|
||
|
||
|
||
<b>6.10.2.</b>
|
||
|
||
使用 Drone 进行持续集成与发布
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.11" data-path="../practice/update-and-upgrade.html">
|
||
|
||
<a href="../practice/update-and-upgrade.html">
|
||
|
||
|
||
<b>6.11.</b>
|
||
|
||
更新与升级
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.11.1" data-path="../practice/manually-upgrade.html">
|
||
|
||
<a href="../practice/manually-upgrade.html">
|
||
|
||
|
||
<b>6.11.1.</b>
|
||
|
||
手动升级 Kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.11.2" data-path="../practice/dashboard-upgrade.html">
|
||
|
||
<a href="../practice/dashboard-upgrade.html">
|
||
|
||
|
||
<b>6.11.2.</b>
|
||
|
||
升级 dashboard
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.12" data-path="../practice/controller-extended.html">
|
||
|
||
<a href="../practice/controller-extended.html">
|
||
|
||
|
||
<b>6.12.</b>
|
||
|
||
扩展控制器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.12.1" data-path="../practice/openkruise.html">
|
||
|
||
<a href="../practice/openkruise.html">
|
||
|
||
|
||
<b>6.12.1.</b>
|
||
|
||
OpenKruise
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.12.1.1" data-path="../practice/in-place-update.html">
|
||
|
||
<a href="../practice/in-place-update.html">
|
||
|
||
|
||
<b>6.12.1.1.</b>
|
||
|
||
原地升级
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.13" data-path="../practice/security-policy.html">
|
||
|
||
<a href="../practice/security-policy.html">
|
||
|
||
|
||
<b>6.13.</b>
|
||
|
||
安全策略
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.13.1" data-path="../practice/open-policy-agent.html">
|
||
|
||
<a href="../practice/open-policy-agent.html">
|
||
|
||
|
||
<b>6.13.1.</b>
|
||
|
||
开放策略代理(OPA)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.13.2" data-path="../practice/cloud-native-security.html">
|
||
|
||
<a href="../practice/cloud-native-security.html">
|
||
|
||
|
||
<b>6.13.2.</b>
|
||
|
||
云原生安全
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">服务网格</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="7.1" data-path="../usecases/service-mesh.html">
|
||
|
||
<a href="../usecases/service-mesh.html">
|
||
|
||
|
||
<b>7.1.</b>
|
||
|
||
服务网格(Service Mesh)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2" data-path="../usecases/the-enterprise-path-to-service-mesh-architectures.html">
|
||
|
||
<a href="../usecases/the-enterprise-path-to-service-mesh-architectures.html">
|
||
|
||
|
||
<b>7.2.</b>
|
||
|
||
企业级服务网格架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="7.2.1" data-path="../usecases/service-mesh-fundamental.html">
|
||
|
||
<a href="../usecases/service-mesh-fundamental.html">
|
||
|
||
|
||
<b>7.2.1.</b>
|
||
|
||
服务网格基础
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.2" data-path="../usecases/comparing-service-mesh-technologies.html">
|
||
|
||
<a href="../usecases/comparing-service-mesh-technologies.html">
|
||
|
||
|
||
<b>7.2.2.</b>
|
||
|
||
服务网格技术对比
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.3" data-path="../usecases/service-mesh-vs-api-gateway.html">
|
||
|
||
<a href="../usecases/service-mesh-vs-api-gateway.html">
|
||
|
||
|
||
<b>7.2.3.</b>
|
||
|
||
服务网格对比 API 网关
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.4" data-path="../usecases/service-mesh-adoption-and-evolution.html">
|
||
|
||
<a href="../usecases/service-mesh-adoption-and-evolution.html">
|
||
|
||
|
||
<b>7.2.4.</b>
|
||
|
||
采纳和演进
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.5" data-path="../usecases/service-mesh-customization-and-integration.html">
|
||
|
||
<a href="../usecases/service-mesh-customization-and-integration.html">
|
||
|
||
|
||
<b>7.2.5.</b>
|
||
|
||
定制和集成
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.6" data-path="../usecases/service-mesh-conclusion.html">
|
||
|
||
<a href="../usecases/service-mesh-conclusion.html">
|
||
|
||
|
||
<b>7.2.6.</b>
|
||
|
||
总结
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3" data-path="../usecases/istio.html">
|
||
|
||
<a href="../usecases/istio.html">
|
||
|
||
|
||
<b>7.3.</b>
|
||
|
||
Istio
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="7.3.1" data-path="../usecases/before-using-istio.html">
|
||
|
||
<a href="../usecases/before-using-istio.html">
|
||
|
||
|
||
<b>7.3.1.</b>
|
||
|
||
使用 Istio 前需要考虑的问题
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.2" data-path="../usecases/sidecar-spec-in-istio.html">
|
||
|
||
<a href="../usecases/sidecar-spec-in-istio.html">
|
||
|
||
|
||
<b>7.3.2.</b>
|
||
|
||
Istio 中 sidecar 的注入规范及示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.3" data-path="../usecases/istio-community-tips.html">
|
||
|
||
<a href="../usecases/istio-community-tips.html">
|
||
|
||
|
||
<b>7.3.3.</b>
|
||
|
||
如何参与 Istio 社区及注意事项
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.4" data-path="../usecases/istio-tutorials-collection.html">
|
||
|
||
<a href="../usecases/istio-tutorials-collection.html">
|
||
|
||
|
||
<b>7.3.4.</b>
|
||
|
||
Istio 免费学习资源汇总
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.5" data-path="../usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html">
|
||
|
||
<a href="../usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html">
|
||
|
||
|
||
<b>7.3.5.</b>
|
||
|
||
Sidecar 的注入与流量劫持
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.6" data-path="../usecases/envoy-sidecar-routing-of-istio-service-mesh-deep-dive.html">
|
||
|
||
<a href="../usecases/envoy-sidecar-routing-of-istio-service-mesh-deep-dive.html">
|
||
|
||
|
||
<b>7.3.6.</b>
|
||
|
||
Envoy Sidecar 代理的路由转发
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.7" data-path="../usecases/how-to-integrate-istio-with-vm.html">
|
||
|
||
<a href="../usecases/how-to-integrate-istio-with-vm.html">
|
||
|
||
|
||
<b>7.3.7.</b>
|
||
|
||
Istio 如何支持虚拟机
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.8" data-path="../usecases/istio-vm-support.html">
|
||
|
||
<a href="../usecases/istio-vm-support.html">
|
||
|
||
|
||
<b>7.3.8.</b>
|
||
|
||
Istio 支持虚拟机的历史
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.4" data-path="../usecases/envoy.html">
|
||
|
||
<a href="../usecases/envoy.html">
|
||
|
||
|
||
<b>7.4.</b>
|
||
|
||
Envoy
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="7.4.1" data-path="../usecases/envoy-terminology.html">
|
||
|
||
<a href="../usecases/envoy-terminology.html">
|
||
|
||
|
||
<b>7.4.1.</b>
|
||
|
||
Envoy 的架构与基本术语
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.4.2" data-path="../usecases/envoy-front-proxy.html">
|
||
|
||
<a href="../usecases/envoy-front-proxy.html">
|
||
|
||
|
||
<b>7.4.2.</b>
|
||
|
||
Envoy 作为前端代理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.4.3" data-path="../usecases/envoy-mesh-in-kubernetes-tutorial.html">
|
||
|
||
<a href="../usecases/envoy-mesh-in-kubernetes-tutorial.html">
|
||
|
||
|
||
<b>7.4.3.</b>
|
||
|
||
Envoy mesh 教程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">领域应用</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="8.1" data-path="../usecases/">
|
||
|
||
<a href="../usecases/">
|
||
|
||
|
||
<b>8.1.</b>
|
||
|
||
领域应用概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.2" data-path="../usecases/microservices.html">
|
||
|
||
<a href="../usecases/microservices.html">
|
||
|
||
|
||
<b>8.2.</b>
|
||
|
||
微服务架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.2.1" data-path="../usecases/service-discovery-in-microservices.html">
|
||
|
||
<a href="../usecases/service-discovery-in-microservices.html">
|
||
|
||
|
||
<b>8.2.1.</b>
|
||
|
||
微服务中的服务发现
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.2.2" data-path="../usecases/microservices-for-java-developers.html">
|
||
|
||
<a href="../usecases/microservices-for-java-developers.html">
|
||
|
||
|
||
<b>8.2.2.</b>
|
||
|
||
使用 Java 构建微服务并发布到 Kubernetes 平台
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.2.2.1" data-path="../usecases/spring-boot-quick-start-guide.html">
|
||
|
||
<a href="../usecases/spring-boot-quick-start-guide.html">
|
||
|
||
|
||
<b>8.2.2.1.</b>
|
||
|
||
Spring Boot 快速开始指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.3" data-path="../usecases/big-data.html">
|
||
|
||
<a href="../usecases/big-data.html">
|
||
|
||
|
||
<b>8.3.</b>
|
||
|
||
大数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.3.1" data-path="../usecases/spark-on-kubernetes.html">
|
||
|
||
<a href="../usecases/spark-on-kubernetes.html">
|
||
|
||
|
||
<b>8.3.1.</b>
|
||
|
||
Spark 与 Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.3.1.1" data-path="../usecases/spark-standalone-on-kubernetes.html">
|
||
|
||
<a href="../usecases/spark-standalone-on-kubernetes.html">
|
||
|
||
|
||
<b>8.3.1.1.</b>
|
||
|
||
Spark standalone on Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.3.1.2" data-path="../usecases/running-spark-with-kubernetes-native-scheduler.html">
|
||
|
||
<a href="../usecases/running-spark-with-kubernetes-native-scheduler.html">
|
||
|
||
|
||
<b>8.3.1.2.</b>
|
||
|
||
运行支持 Kubernetes 原生调度的 Spark 程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.4" data-path="../usecases/serverless.html">
|
||
|
||
<a href="../usecases/serverless.html">
|
||
|
||
|
||
<b>8.4.</b>
|
||
|
||
Serverless 架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.4.1" data-path="../usecases/understanding-serverless.html">
|
||
|
||
<a href="../usecases/understanding-serverless.html">
|
||
|
||
|
||
<b>8.4.1.</b>
|
||
|
||
理解 Serverless
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.4.2" data-path="../usecases/faas.html">
|
||
|
||
<a href="../usecases/faas.html">
|
||
|
||
|
||
<b>8.4.2.</b>
|
||
|
||
FaaS(函数即服务)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.4.2.1" data-path="../usecases/openfaas-quick-start.html">
|
||
|
||
<a href="../usecases/openfaas-quick-start.html">
|
||
|
||
|
||
<b>8.4.2.1.</b>
|
||
|
||
OpenFaaS 快速入门指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.4.3" data-path="../usecases/knative.html">
|
||
|
||
<a href="../usecases/knative.html">
|
||
|
||
|
||
<b>8.4.3.</b>
|
||
|
||
Knative
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.5" data-path="../usecases/edge-computing.html">
|
||
|
||
<a href="../usecases/edge-computing.html">
|
||
|
||
|
||
<b>8.5.</b>
|
||
|
||
边缘计算
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.6" data-path="../usecases/ai.html">
|
||
|
||
<a href="../usecases/ai.html">
|
||
|
||
|
||
<b>8.6.</b>
|
||
|
||
人工智能
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.7" data-path="../usecases/observability.html">
|
||
|
||
<a href="../usecases/observability.html">
|
||
|
||
|
||
<b>8.7.</b>
|
||
|
||
可观察性
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">开发指南</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="9.1" data-path="../develop/">
|
||
|
||
<a href="../develop/">
|
||
|
||
|
||
<b>9.1.</b>
|
||
|
||
开发指南概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.2" data-path="../develop/sigs-and-working-group.html">
|
||
|
||
<a href="../develop/sigs-and-working-group.html">
|
||
|
||
|
||
<b>9.2.</b>
|
||
|
||
SIG 和工作组
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.3" data-path="../develop/developing-environment.html">
|
||
|
||
<a href="../develop/developing-environment.html">
|
||
|
||
|
||
<b>9.3.</b>
|
||
|
||
开发环境搭建
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.3.1" data-path="../develop/using-vagrant-and-virtualbox-for-development.html">
|
||
|
||
<a href="../develop/using-vagrant-and-virtualbox-for-development.html">
|
||
|
||
|
||
<b>9.3.1.</b>
|
||
|
||
本地分布式开发环境搭建(使用 Vagrant 和 Virtualbox)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.4" data-path="../develop/testing.html">
|
||
|
||
<a href="../develop/testing.html">
|
||
|
||
|
||
<b>9.4.</b>
|
||
|
||
单元测试和集成测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.5" data-path="../develop/client-go-sample.html">
|
||
|
||
<a href="../develop/client-go-sample.html">
|
||
|
||
|
||
<b>9.5.</b>
|
||
|
||
client-go 示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.5.1" data-path="../develop/client-go-informer-sourcecode-analyse.html">
|
||
|
||
<a href="../develop/client-go-informer-sourcecode-analyse.html">
|
||
|
||
|
||
<b>9.5.1.</b>
|
||
|
||
client-go 中的 informer 源码分析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.6" data-path="../develop/operator.html">
|
||
|
||
<a href="../develop/operator.html">
|
||
|
||
|
||
<b>9.6.</b>
|
||
|
||
Operator
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.6.1" data-path="../develop/operator-sdk.html">
|
||
|
||
<a href="../develop/operator-sdk.html">
|
||
|
||
|
||
<b>9.6.1.</b>
|
||
|
||
operator-sdk
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7" data-path="../develop/kubebuilder.html">
|
||
|
||
<a href="../develop/kubebuilder.html">
|
||
|
||
|
||
<b>9.7.</b>
|
||
|
||
kubebuilder
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.7.1" data-path="../develop/kubebuilder-example.html">
|
||
|
||
<a href="../develop/kubebuilder-example.html">
|
||
|
||
|
||
<b>9.7.1.</b>
|
||
|
||
使用 kubebuilder 创建 operator 示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.8" data-path="../develop/advance-developer.html">
|
||
|
||
<a href="../develop/advance-developer.html">
|
||
|
||
|
||
<b>9.8.</b>
|
||
|
||
高级开发指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.9" data-path="../develop/contribute.html">
|
||
|
||
<a href="../develop/contribute.html">
|
||
|
||
|
||
<b>9.9.</b>
|
||
|
||
社区贡献
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.10" data-path="../develop/minikube.html">
|
||
|
||
<a href="../develop/minikube.html">
|
||
|
||
|
||
<b>9.10.</b>
|
||
|
||
Minikube
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">社区及生态</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="10.1" data-path="../cloud-native/cncf.html">
|
||
|
||
<a href="../cloud-native/cncf.html">
|
||
|
||
|
||
<b>10.1.</b>
|
||
|
||
云原生计算基金会(CNCF)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="10.1.1" data-path="../cloud-native/cncf-charter.html">
|
||
|
||
<a href="../cloud-native/cncf-charter.html">
|
||
|
||
|
||
<b>10.1.1.</b>
|
||
|
||
CNCF 章程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.2" data-path="../cloud-native/cncf-sig.html">
|
||
|
||
<a href="../cloud-native/cncf-sig.html">
|
||
|
||
|
||
<b>10.1.2.</b>
|
||
|
||
CNCF 特别兴趣小组(SIG)说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.3" data-path="../cloud-native/cncf-sandbox-criteria.html">
|
||
|
||
<a href="../cloud-native/cncf-sandbox-criteria.html">
|
||
|
||
|
||
<b>10.1.3.</b>
|
||
|
||
开源项目加入 CNCF Sandbox 的要求
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.4" data-path="../cloud-native/cncf-project-governing.html">
|
||
|
||
<a href="../cloud-native/cncf-project-governing.html">
|
||
|
||
|
||
<b>10.1.4.</b>
|
||
|
||
CNCF 中的项目治理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.5" data-path="../cloud-native/cncf-ambassador.html">
|
||
|
||
<a href="../cloud-native/cncf-ambassador.html">
|
||
|
||
|
||
<b>10.1.5.</b>
|
||
|
||
CNCF Ambassador
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.2" data-path="../cloud-native/certification.html">
|
||
|
||
<a href="../cloud-native/certification.html">
|
||
|
||
|
||
<b>10.2.</b>
|
||
|
||
认证及培训
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="10.2.1" data-path="../appendix/about-kcsp.html">
|
||
|
||
<a href="../appendix/about-kcsp.html">
|
||
|
||
|
||
<b>10.2.1.</b>
|
||
|
||
认证 Kubernetes 服务提供商(KCSP)说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.2.2" data-path="../appendix/about-cka-candidate.html">
|
||
|
||
<a href="../appendix/about-cka-candidate.html">
|
||
|
||
|
||
<b>10.2.2.</b>
|
||
|
||
认证 Kubernetes 管理员(CKA)说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">附录</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="11.1" data-path="../appendix/">
|
||
|
||
<a href="../appendix/">
|
||
|
||
|
||
<b>11.1.</b>
|
||
|
||
附录说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.2" data-path="../appendix/debug-kubernetes-services.html">
|
||
|
||
<a href="../appendix/debug-kubernetes-services.html">
|
||
|
||
|
||
<b>11.2.</b>
|
||
|
||
Kubernetes 中的应用故障排查
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.3" data-path="../appendix/material-share.html">
|
||
|
||
<a href="../appendix/material-share.html">
|
||
|
||
|
||
<b>11.3.</b>
|
||
|
||
Kubernetes 相关资讯和情报链接
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.4" data-path="../appendix/docker-best-practice.html">
|
||
|
||
<a href="../appendix/docker-best-practice.html">
|
||
|
||
|
||
<b>11.4.</b>
|
||
|
||
Docker 最佳实践
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.5" data-path="../appendix/tricks.html">
|
||
|
||
<a href="../appendix/tricks.html">
|
||
|
||
|
||
<b>11.5.</b>
|
||
|
||
Kubernetes 使用技巧
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.6" data-path="../appendix/issues.html">
|
||
|
||
<a href="../appendix/issues.html">
|
||
|
||
|
||
<b>11.6.</b>
|
||
|
||
Kubernetes 相关问题记录
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.7" data-path="../appendix/summary-and-outlook.html">
|
||
|
||
<a href="../appendix/summary-and-outlook.html">
|
||
|
||
|
||
<b>11.7.</b>
|
||
|
||
Kubernetes 及云原生年度总结及展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="11.7.1" data-path="../appendix/kubernetes-and-cloud-native-summary-in-2017-and-outlook-for-2018.html">
|
||
|
||
<a href="../appendix/kubernetes-and-cloud-native-summary-in-2017-and-outlook-for-2018.html">
|
||
|
||
|
||
<b>11.7.1.</b>
|
||
|
||
Kubernetes 与云原生 2017 年年终总结及 2018 年展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.7.2" data-path="../appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html">
|
||
|
||
<a href="../appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html">
|
||
|
||
|
||
<b>11.7.2.</b>
|
||
|
||
Kubernetes 与云原生 2018 年年终总结及 2019 年展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.8" data-path="../appendix/cncf-annual-report.html">
|
||
|
||
<a href="../appendix/cncf-annual-report.html">
|
||
|
||
|
||
<b>11.8.</b>
|
||
|
||
CNCF 年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="11.8.1" data-path="../appendix/cncf-annual-report-2018.html">
|
||
|
||
<a href="../appendix/cncf-annual-report-2018.html">
|
||
|
||
|
||
<b>11.8.1.</b>
|
||
|
||
CNCF 2018 年年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.8.2" data-path="../appendix/cncf-annual-report-2020.html">
|
||
|
||
<a href="../appendix/cncf-annual-report-2020.html">
|
||
|
||
|
||
<b>11.8.2.</b>
|
||
|
||
CNCF 2020 年年度报告解读
|
||
|
||
</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=".." >Volume</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="volume">Volume</h1>
|
||
<p>容器磁盘上的文件的生命周期是短暂的,这就使得在容器中运行重要应用时会出现一些问题。首先,当容器崩溃时,kubelet 会重启它,但是容器中的文件将丢失——容器以干净的状态(镜像最初的状态)重新启动。其次,在 <code>Pod</code> 中同时运行多个容器时,这些容器之间通常需要共享文件。Kubernetes 中的 <code>Volume</code> 抽象就很好的解决了这些问题。</p>
|
||
<p>建议先熟悉 <a href="https://kubernetes.io/docs/user-guide/pods" target="_blank">pod</a>。</p>
|
||
<h2 id="背景">背景</h2>
|
||
<p>Docker 中也有一个 <a href="https://docs.docker.com/engine/admin/volumes/" target="_blank">volume</a> 的概念,尽管它稍微宽松一些,管理也很少。在 Docker 中,卷就像是磁盘或是另一个容器中的一个目录。它的生命周期不受管理,直到最近才有了 local-disk-backed 卷。Docker 现在提供了卷驱动程序,但是功能还非常有限(例如Docker1.7只允许每个容器使用一个卷驱动,并且无法给卷传递参数)。</p>
|
||
<p>另一方面,Kubernetes 中的卷有明确的寿命——与封装它的 Pod 相同。所以,卷的生命比 Pod 中的所有容器都长,当这个容器重启时数据仍然得以保存。当然,当 Pod 不再存在时,卷也将不复存在。也许更重要的是,Kubernetes 支持多种类型的卷,Pod 可以同时使用任意数量的卷。</p>
|
||
<p>卷的核心是目录,可能还包含了一些数据,可以通过 pod 中的容器来访问。该目录是如何形成的、支持该目录的介质以及其内容取决于所使用的特定卷类型。</p>
|
||
<p>要使用卷,需要为 pod 指定为卷(<code>spec.volumes</code> 字段)以及将它挂载到容器的位置(<code>spec.containers.volumeMounts</code> 字段)。</p>
|
||
<p>容器中的进程看到的是由其 Docker 镜像和卷组成的文件系统视图。<a href="https://docs.docker.com/userguide/dockerimages/" target="_blank">Docker 镜像</a>位于文件系统层次结构的根目录,任何卷都被挂载在镜像的指定路径中。卷无法挂载到其他卷上或与其他卷有硬连接。Pod 中的每个容器都必须独立指定每个卷的挂载位置。</p>
|
||
<h2 id="卷的类型">卷的类型</h2>
|
||
<p>Kubernetes 支持以下类型的卷:</p>
|
||
<ul>
|
||
<li><code>awsElasticBlockStore</code></li>
|
||
<li><code>azureDisk</code></li>
|
||
<li><code>azureFile</code></li>
|
||
<li><code>cephfs</code></li>
|
||
<li><code>csi</code></li>
|
||
<li><code>downwardAPI</code></li>
|
||
<li><code>emptyDir</code></li>
|
||
<li><code>fc</code> (fibre channel)</li>
|
||
<li><code>flocker</code></li>
|
||
<li><code>gcePersistentDisk</code></li>
|
||
<li><code>gitRepo</code></li>
|
||
<li><code>glusterfs</code></li>
|
||
<li><code>hostPath</code></li>
|
||
<li><code>iscsi</code></li>
|
||
<li><code>local</code></li>
|
||
<li><code>nfs</code></li>
|
||
<li><code>persistentVolumeClaim</code></li>
|
||
<li><code>projected</code></li>
|
||
<li><code>portworxVolume</code></li>
|
||
<li><code>quobyte</code></li>
|
||
<li><code>rbd</code></li>
|
||
<li><code>scaleIO</code></li>
|
||
<li><code>secret</code></li>
|
||
<li><code>storageos</code></li>
|
||
<li><code>vsphereVolume</code></li>
|
||
</ul>
|
||
<p>我们欢迎额外贡献。</p>
|
||
<h3 id="awselasticblockstore">awsElasticBlockStore</h3>
|
||
<p><code>awsElasticBlockStore</code> 卷将Amazon Web Services(AWS)EBS Volume 挂载到您的容器中。与 <code>emptyDir</code> 类型会在删除 Pod 时被清除不同,EBS 卷的的内容会保留下来,仅仅是被卸载。这意味着 EBS 卷可以预先填充数据,并且可以在数据包之间“切换”数据。</p>
|
||
<p><strong>重要提示</strong>:您必须使用 <code>aws ec2 create-volume</code> 或 AWS API 创建 EBS 卷,才能使用它。</p>
|
||
<p>使用 awsElasticBlockStore 卷时有一些限制:</p>
|
||
<ul>
|
||
<li>运行 Pod 的节点必须是 AWS EC2 实例</li>
|
||
<li>这些实例需要与 EBS 卷位于相同的区域和可用区域</li>
|
||
<li>EBS 仅支持卷和 EC2 实例的一对一的挂载</li>
|
||
</ul>
|
||
<h4 id="创建-ebs-卷">创建 EBS 卷</h4>
|
||
<p>在 pod 中使用的 EBS 卷之前,您需要先创建它。</p>
|
||
<pre class="language-"><code class="lang-bash">aws ec2 create-volume --availability-zone<span class="token operator">=</span>eu-west-1a --size<span class="token operator">=</span><span class="token number">10</span> --volume-type<span class="token operator">=</span>gp2
|
||
</code></pre>
|
||
<p>确保区域与您启动集群的区域相匹配(并且检查大小和 EBS 卷类型是否适合您的使用!)</p>
|
||
<h3 id="aws-ebs-示例配置">AWS EBS 示例配置</h3>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>ebs
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">image</span><span class="token punctuation">:</span> k8s.gcr.io/test<span class="token punctuation">-</span>webserver
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>container
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">mountPath</span><span class="token punctuation">:</span> /test<span class="token punctuation">-</span>ebs
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>volume
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>volume
|
||
<span class="token comment"># This AWS EBS volume must already exist.</span>
|
||
<span class="token key atrule">awsElasticBlockStore</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">volumeID</span><span class="token punctuation">:</span> <volume<span class="token punctuation">-</span>id<span class="token punctuation">></span>
|
||
<span class="token key atrule">fsType</span><span class="token punctuation">:</span> ext4
|
||
</code></pre>
|
||
<h3 id="azuredisk">azureDisk</h3>
|
||
<p><code>AzureDisk</code> 用于将 Microsoft Azure <a href="https://azure.microsoft.com/zh-cn/documentation/articles/virtual-machines-linux-about-disks-vhds" target="_blank">Data Disk</a> 挂载到 Pod 中。</p>
|
||
<h3 id="azurefile">azureFile</h3>
|
||
<p><code>azureFile</code> 用于将 Microsoft Azure File Volume(SMB 2.1 和 3.0)挂载到 Pod 中。</p>
|
||
<h3 id="cephfs">cephfs</h3>
|
||
<p><code>cephfs</code> 卷允许将现有的 CephFS 卷挂载到您的容器中。不像 <code>emptyDir</code>,当删除 Pod 时被删除,<code>cephfs</code> 卷的内容将被保留,卷仅仅是被卸载。这意味着 CephFS 卷可以预先填充数据,并且可以在数据包之间“切换”数据。 CephFS 可以被多个写设备同时挂载。</p>
|
||
<p><strong>重要提示</strong>:您必须先拥有自己的 Ceph 服务器,然后才能使用它。</p>
|
||
<h3 id="csi">csi</h3>
|
||
<p>CSI 代表<a href="https://github.com/container-storage-interface/spec/blob/master/spec.md" target="_blank">容器存储接口</a>,CSI 试图建立一个行业标准接口的规范,借助 CSI 容器编排系统(CO)可以将任意存储系统暴露给自己的容器工作负载。有关详细信息,请查看<a href="https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/container-storage-interface.md" target="_blank">设计方案</a>。</p>
|
||
<p><code>csi</code> 卷类型是一种 in-tree 的 CSI 卷插件,用于 Pod 与在同一节点上运行的外部 CSI 卷驱动程序交互。部署 CSI 兼容卷驱动后,用户可以使用 <code>csi</code> 作为卷类型来挂载驱动提供的存储。</p>
|
||
<p>CSI 持久化卷支持是在 Kubernetes v1.9 中引入的,作为一个 alpha 特性,必须由集群管理员明确启用。换句话说,集群管理员需要在 apiserver、controller-manager 和 kubelet 组件的 “<code>--feature-gates =</code>” 标志中加上 “<code>CSIPersistentVolume = true</code>”。</p>
|
||
<p>CSI 持久化卷具有以下字段可供用户指定:</p>
|
||
<ul>
|
||
<li><code>driver</code>:一个字符串值,指定要使用的卷驱动程序的名称。必须少于 63 个字符,并以一个字符开头。驱动程序名称可以包含 “<code>.</code>”、“<code>-</code> ”、“<code>_</code>” 或数字。</li>
|
||
<li><code>volumeHandle</code>:一个字符串值,唯一标识从 CSI 卷插件的 <code>CreateVolume</code> 调用返回的卷名。随后在卷驱动程序的所有后续调用中使用卷句柄来引用该卷。</li>
|
||
<li><code>readOnly</code>:一个可选的布尔值,指示卷是否被发布为只读。默认是 false。</li>
|
||
</ul>
|
||
<h3 id="downwardapi">downwardAPI</h3>
|
||
<p><code>downwardAPI</code> 卷用于使向下 API 数据(downward API data)对应用程序可用。它挂载一个目录,并将请求的数据写入纯文本文件。</p>
|
||
<p>参考 <a href="https://kubernetes.io/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/" target="_blank"><code>downwardAPI</code> 卷示例</a>查看详细信息。</p>
|
||
<h3 id="emptydir">emptyDir</h3>
|
||
<p>当 Pod 被分配给节点时,首先创建 <code>emptyDir</code> 卷,并且只要该 Pod 在该节点上运行,该卷就会存在。正如卷的名字所述,它最初是空的。Pod 中的容器可以读取和写入 <code>emptyDir</code> 卷中的相同文件,尽管该卷可以挂载到每个容器中的相同或不同路径上。当出于任何原因从节点中删除 Pod 时,<code>emptyDir</code> 中的数据将被永久删除。</p>
|
||
<p><strong>注意</strong>:容器崩溃不会从节点中移除 pod,因此 <code>emptyDir</code> 卷中的数据在容器崩溃时是安全的。</p>
|
||
<p><code>emptyDir</code> 的用法有:</p>
|
||
<ul>
|
||
<li>暂存空间,例如用于基于磁盘的合并排序</li>
|
||
<li>用作长时间计算崩溃恢复时的检查点</li>
|
||
<li>Web服务器容器提供数据时,保存内容管理器容器提取的文件</li>
|
||
</ul>
|
||
<h4 id="pod-示例">Pod 示例</h4>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>pd
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">image</span><span class="token punctuation">:</span> k8s.gcr.io/test<span class="token punctuation">-</span>webserver
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>container
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">mountPath</span><span class="token punctuation">:</span> /cache
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> cache<span class="token punctuation">-</span>volume
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> cache<span class="token punctuation">-</span>volume
|
||
<span class="token key atrule">emptyDir</span><span class="token punctuation">:</span> <span class="token punctuation">{</span><span class="token punctuation">}</span>
|
||
</code></pre>
|
||
<h3 id="fc-fibre-channel">fc (fibre channel)</h3>
|
||
<p>fc 卷允许将现有的 <code>fc</code> 卷挂载到 pod 中。您可以使用卷配置中的 <code>targetWWN</code> 参数指定单个或多个目标全球通用名称(World Wide Name)。如果指定了多个 WWN,则 targetWWN 期望这些 WWN 来自多路径连接。</p>
|
||
<p><strong>重要提示</strong>:您必须配置 FC SAN 区域划分,并预先将这些 LUN(卷)分配并屏蔽到目标 WWN,以便 Kubernetes 主机可以访问它们。</p>
|
||
<p>参考 <a href="https://github.com/kubernetes/examples/tree/master/staging/volumes/fibre_channel" target="_blank">FC 示例</a>获取详细信息。</p>
|
||
<h3 id="flocker">flocker</h3>
|
||
<p>Flocker 是一款开源的集群容器数据卷管理器。它提供了由各种存储后端支持的数据卷的管理和编排。</p>
|
||
<p><code>flocker</code> 允许将 Flocker 数据集挂载到 pod 中。如果数据集在 Flocker 中不存在,则需要先使用 Flocker CLI 或使用 Flocker API 创建数据集。如果数据集已经存在,它将被 Flocker 重新连接到 pod 被调度的节点上。这意味着数据可以根据需要在数据包之间“切换”。</p>
|
||
<p><strong>重要提示</strong>:您必须先运行自己的 Flocker 安装程序才能使用它。</p>
|
||
<p>参考 <a href="https://github.com/kubernetes/examples/tree/master/staging/volumes/flocker" target="_blank">Flocker 示例</a>获取更多详细信息。</p>
|
||
<h3 id="gcepersistentdisk">gcePersistentDisk</h3>
|
||
<p><code>gcePersistentDisk</code> 卷将 Google Compute Engine(GCE)<a href="http://cloud.google.com/compute/docs/disks" target="_blank">Persistent Disk</a> 挂载到您的容器中。与删除 Pod 时删除的 <code>emptyDir</code> 不同,PD 的内容被保留,只是卸载了卷。这意味着 PD 可以预先填充数据,并且数据可以在 Pod 之间“切换”。</p>
|
||
<p><strong>重要提示</strong>:您必须先使用 gcloud 或 GCE API 或 UI 创建一个 PD,然后才能使用它。</p>
|
||
<p>使用 <code>gcePersistentDisk</code> 时有一些限制:</p>
|
||
<ul>
|
||
<li>运行 Pod 的节点必须是 GCE 虚拟机</li>
|
||
<li>那些虚拟机需要在与 PD 一样在 GCE 项目和区域中</li>
|
||
</ul>
|
||
<p>PD 的一个特点是它们可以同时被多个用户以只读方式挂载。这意味着您可以预先使用您的数据集填充 PD,然后根据需要给多个 Pod 中并行提供。不幸的是,只能由单个消费者以读写模式挂载 PD,而不允许同时写入。
|
||
在由 ReplicationController 控制的 pod 上使用 PD 将会失败,除非 PD 是只读的或者副本数是 0 或 1。</p>
|
||
<h4 id="创建-pd">创建 PD</h4>
|
||
<p>在您在 pod 中使用 GCE PD 之前,需要先创建它。</p>
|
||
<pre class="language-"><code class="lang-bash">gcloud compute disks create --size<span class="token operator">=</span>500GB --zone<span class="token operator">=</span>us-central1-a my-data-disk
|
||
</code></pre>
|
||
<h4 id="pod-示例">Pod 示例</h4>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>pd
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">image</span><span class="token punctuation">:</span> k8s.gcr.io/test<span class="token punctuation">-</span>webserver
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>container
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">mountPath</span><span class="token punctuation">:</span> /test<span class="token punctuation">-</span>pd
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>volume
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>volume
|
||
<span class="token comment"># This GCE PD must already exist.</span>
|
||
<span class="token key atrule">gcePersistentDisk</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">pdName</span><span class="token punctuation">:</span> my<span class="token punctuation">-</span>data<span class="token punctuation">-</span>disk
|
||
<span class="token key atrule">fsType</span><span class="token punctuation">:</span> ext4
|
||
</code></pre>
|
||
<h3 id="gitrepo">gitRepo</h3>
|
||
<p><code>gitRepo</code> 卷是一个可以演示卷插件功能的示例。它会挂载一个空目录并将 git 存储库克隆到您的容器中。将来,这样的卷可能会转移到一个更加分离的模型,而不是为每个这样的用例扩展 Kubernetes API。</p>
|
||
<p>下面是 gitRepo 卷示例:</p>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> server
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">image</span><span class="token punctuation">:</span> nginx
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> nginx
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">mountPath</span><span class="token punctuation">:</span> /mypath
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> git<span class="token punctuation">-</span>volume
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> git<span class="token punctuation">-</span>volume
|
||
<span class="token key atrule">gitRepo</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">repository</span><span class="token punctuation">:</span> <span class="token string">"git@somewhere:me/my-git-repository.git"</span>
|
||
<span class="token key atrule">revision</span><span class="token punctuation">:</span> <span class="token string">"22f1d8406d464b0c0874075539c1f2e96c253775"</span>
|
||
</code></pre>
|
||
<h3 id="glusterfs">glusterfs</h3>
|
||
<p><code>glusterfs</code> 卷允许将 <a href="http://www.gluster.org" target="_blank">Glusterfs</a>(一个开放源代码的网络文件系统)卷挂载到您的集群中。与删除 Pod 时删除的 <code>emptyDir</code> 不同,<code>glusterfs</code> 卷的内容将被保留,而卷仅仅被卸载。这意味着 glusterfs 卷可以预先填充数据,并且可以在数据包之间“切换”数据。 GlusterFS 可以同时由多个写入挂载。</p>
|
||
<p><strong>重要提示</strong>:您必须先自行安装 GlusterFS,才能使用它。</p>
|
||
<h3 id="hostpath">hostPath</h3>
|
||
<p><code>hostPath</code> 卷将主机节点的文件系统中的文件或目录挂载到集群中。该功能大多数 Pod 都用不到,但它为某些应用程序提供了一个强大的解决方法。</p>
|
||
<p>例如,<code>hostPath</code> 的用途如下:</p>
|
||
<ul>
|
||
<li>运行需要访问 Docker 内部的容器;使用 <code>/var/lib/docker</code> 的 <code>hostPath</code></li>
|
||
<li>在容器中运行 cAdvisor;使用 <code>/dev/cgroups</code> 的 <code>hostPath</code></li>
|
||
<li>允许 pod 指定给定的 hostPath 是否应该在 pod 运行之前存在,是否应该创建,以及它应该以什么形式存在</li>
|
||
</ul>
|
||
<p>除了所需的 <code>path</code> 属性之外,用户还可以为 <code>hostPath</code> 卷指定 <code>type</code>。</p>
|
||
<p><code>type</code> 字段支持以下值:</p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th style="text-align:left">值</th>
|
||
<th style="text-align:left">行为</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td style="text-align:left"></td>
|
||
<td style="text-align:left">空字符串(默认)用于向后兼容,这意味着在挂载 hostPath 卷之前不会执行任何检查。</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align:left"><code>DirectoryOrCreate</code></td>
|
||
<td style="text-align:left">如果在给定的路径上没有任何东西存在,那么将根据需要在那里创建一个空目录,权限设置为 0755,与 Kubelet 具有相同的组和所有权。</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align:left"><code>Directory</code></td>
|
||
<td style="text-align:left">给定的路径下必须存在目录</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align:left"><code>FileOrCreate</code></td>
|
||
<td style="text-align:left">如果在给定的路径上没有任何东西存在,那么会根据需要创建一个空文件,权限设置为 0644,与 Kubelet 具有相同的组和所有权。</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align:left"><code>File</code></td>
|
||
<td style="text-align:left">给定的路径下必须存在文件</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align:left"><code>Socket</code></td>
|
||
<td style="text-align:left">给定的路径下必须存在 UNIX 套接字</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align:left"><code>CharDevice</code></td>
|
||
<td style="text-align:left">给定的路径下必须存在字符设备</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align:left"><code>BlockDevice</code></td>
|
||
<td style="text-align:left">给定的路径下必须存在块设备</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p>使用这种卷类型是请注意,因为:</p>
|
||
<ul>
|
||
<li>由于每个节点上的文件都不同,具有相同配置(例如从 podTemplate 创建的)的 pod 在不同节点上的行为可能会有所不同</li>
|
||
<li>当 Kubernetes 按照计划添加资源感知调度时,将无法考虑 <code>hostPath</code> 使用的资源</li>
|
||
<li>在底层主机上创建的文件或目录只能由 root 写入。您需要在特权容器中以 root 身份运行进程,或修改主机上的文件权限以便写入 <code>hostPath</code> 卷</li>
|
||
</ul>
|
||
<h4 id="pod-示例">Pod 示例</h4>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>pd
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">image</span><span class="token punctuation">:</span> k8s.gcr.io/test<span class="token punctuation">-</span>webserver
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>container
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">mountPath</span><span class="token punctuation">:</span> /test<span class="token punctuation">-</span>pd
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>volume
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>volume
|
||
<span class="token key atrule">hostPath</span><span class="token punctuation">:</span>
|
||
<span class="token comment"># directory location on host</span>
|
||
<span class="token key atrule">path</span><span class="token punctuation">:</span> /data
|
||
<span class="token comment"># this field is optional</span>
|
||
<span class="token key atrule">type</span><span class="token punctuation">:</span> Directory
|
||
</code></pre>
|
||
<h3 id="iscsi">iscsi</h3>
|
||
<p><code>iscsi</code> 卷允许将现有的 iSCSI(SCSI over IP)卷挂载到容器中。不像 <code>emptyDir</code>,删除 Pod 时 <code>iscsi</code> 卷的内容将被保留,卷仅仅是被卸载。这意味着 iscsi 卷可以预先填充数据,并且这些数据可以在 pod 之间“切换”。</p>
|
||
<p><strong>重要提示</strong>:必须先创建自己的 iSCSI 服务器,然后才能使用它。</p>
|
||
<p>iSCSI 的一个特点是它可以同时被多个用户以只读方式安装。这意味着您可以预先使用您的数据集填充卷,然后根据需要向多个额 pod 同时提供。不幸的是,iSCSI 卷只能由单个使用者以读写模式挂载——不允许同时写入。</p>
|
||
<h3 id="local">local</h3>
|
||
<p>这个 alpha 功能要求启用 <code>PersistentLocalVolumes</code> feature gate。</p>
|
||
<p><strong>注意</strong>:从 1.9 开始,<code>VolumeScheduling</code> feature gate 也必须启用。</p>
|
||
<p><code>local</code> 卷表示挂载的本地存储设备,如磁盘、分区或目录。</p>
|
||
<p>本地卷只能用作静态创建的 PersistentVolume。</p>
|
||
<p>与 HostPath 卷相比,local 卷可以以持久的方式使用,而无需手动将 pod 调度到节点上,因为系统会通过查看 PersistentVolume 上的节点关联性来了解卷的节点约束。</p>
|
||
<p>但是,local 卷仍然受底层节点的可用性影响,并不适用于所有应用程序。</p>
|
||
<p>以下是使用 <code>local</code> 卷的示例 PersistentVolume 规范:</p>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> PersistentVolume
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> example<span class="token punctuation">-</span>pv
|
||
<span class="token key atrule">annotations</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">"volume.alpha.kubernetes.io/node-affinity"</span><span class="token punctuation">:</span> '<span class="token punctuation">{</span>
|
||
<span class="token key atrule">"requiredDuringSchedulingIgnoredDuringExecution"</span><span class="token punctuation">:</span> <span class="token punctuation">{</span>
|
||
<span class="token key atrule">"nodeSelectorTerms"</span><span class="token punctuation">:</span> <span class="token punctuation">[</span>
|
||
<span class="token punctuation">{</span> <span class="token key atrule">"matchExpressions"</span><span class="token punctuation">:</span> <span class="token punctuation">[</span>
|
||
<span class="token punctuation">{</span> <span class="token key atrule">"key"</span><span class="token punctuation">:</span> <span class="token string">"kubernetes.io/hostname"</span><span class="token punctuation">,</span>
|
||
<span class="token key atrule">"operator"</span><span class="token punctuation">:</span> <span class="token string">"In"</span><span class="token punctuation">,</span>
|
||
<span class="token key atrule">"values"</span><span class="token punctuation">:</span> <span class="token punctuation">[</span><span class="token string">"example-node"</span><span class="token punctuation">]</span>
|
||
<span class="token punctuation">}</span>
|
||
<span class="token punctuation">]</span><span class="token punctuation">}</span>
|
||
<span class="token punctuation">]</span><span class="token punctuation">}</span>
|
||
<span class="token punctuation">}</span>'
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">capacity</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">storage</span><span class="token punctuation">:</span> 100Gi
|
||
<span class="token key atrule">accessModes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> ReadWriteOnce
|
||
<span class="token key atrule">persistentVolumeReclaimPolicy</span><span class="token punctuation">:</span> Delete
|
||
<span class="token key atrule">storageClassName</span><span class="token punctuation">:</span> local<span class="token punctuation">-</span>storage
|
||
<span class="token key atrule">local</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">path</span><span class="token punctuation">:</span> /mnt/disks/ssd1
|
||
</code></pre>
|
||
<p><strong>注意</strong>:本地 PersistentVolume 清理和删除需要手动干预,无外部提供程序。</p>
|
||
<p>从 1.9 开始,本地卷绑定可以被延迟,直到通过具有 StorageClass 中的 <code>WaitForFirstConsumer</code> 设置为<code>volumeBindingMode</code> 的 pod 开始调度。请参阅示例。延迟卷绑定可确保卷绑定决策也可以使用任何其他节点约束(例如节点资源需求,节点选择器,pod 亲和性和 pod 反亲和性)进行评估。</p>
|
||
<p>有关 <code>local</code> 卷类型的详细信息,请参见<a href="https://github.com/kubernetes-incubator/external-storage/tree/master/local-volume" target="_blank">本地持久化存储用户指南</a>。</p>
|
||
<h3 id="nfs">nfs</h3>
|
||
<p><code>nfs</code> 卷允许将现有的 NFS(网络文件系统)共享挂载到您的容器中。不像 <code>emptyDir</code>,当删除 Pod 时,<code>nfs</code> 卷的内容被保留,卷仅仅是被卸载。这意味着 NFS 卷可以预填充数据,并且可以在 pod 之间“切换”数据。 NFS 可以被多个写入者同时挂载。</p>
|
||
<p><strong>重要提示</strong>:您必须先拥有自己的 NFS 服务器才能使用它,然后才能使用它。</p>
|
||
<p>有关更多详细信息,请参见 <a href="https://github.com/kubernetes/examples/tree/master/staging/volumes/nfs" target="_blank">NFS 示例</a>。</p>
|
||
<h3 id="persistentvolumeclaim">persistentVolumeClaim</h3>
|
||
<p><code>persistentVolumeClaim</code> 卷用于将 <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/" target="_blank">PersistentVolume</a> 挂载到容器中。PersistentVolumes 是在用户不知道特定云环境的细节的情况下“声明”持久化存储(例如 GCE PersistentDisk 或 iSCSI 卷)的一种方式。</p>
|
||
<p>有关更多详细信息,请参阅 <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/" target="_blank">PersistentVolumes 示例</a>。</p>
|
||
<h3 id="projected">projected</h3>
|
||
<p><code>projected</code> 卷将几个现有的卷源映射到同一个目录中。</p>
|
||
<p>目前,可以映射以下类型的卷来源:</p>
|
||
<ul>
|
||
<li><a href="#secret"><code>secret</code></a></li>
|
||
<li><a href="#downwardapi"><code>downwardAPI</code></a></li>
|
||
<li><code>configMap</code></li>
|
||
</ul>
|
||
<p>所有来源都必须在与 pod 相同的命名空间中。</p>
|
||
<h4 id="带有-secret、downward-api-和-configmap-的-pod">带有 secret、downward API 和 configmap 的 pod</h4>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> volume<span class="token punctuation">-</span>test
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> container<span class="token punctuation">-</span>test
|
||
<span class="token key atrule">image</span><span class="token punctuation">:</span> busybox
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> all<span class="token punctuation">-</span>in<span class="token punctuation">-</span>one
|
||
<span class="token key atrule">mountPath</span><span class="token punctuation">:</span> <span class="token string">"/projected-volume"</span>
|
||
<span class="token key atrule">readOnly</span><span class="token punctuation">:</span> <span class="token boolean important">true</span>
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> all<span class="token punctuation">-</span>in<span class="token punctuation">-</span>one
|
||
<span class="token key atrule">projected</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">sources</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">secret</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> mysecret
|
||
<span class="token key atrule">items</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">key</span><span class="token punctuation">:</span> username
|
||
<span class="token key atrule">path</span><span class="token punctuation">:</span> my<span class="token punctuation">-</span>group/my<span class="token punctuation">-</span>username
|
||
<span class="token punctuation">-</span> <span class="token key atrule">downwardAPI</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">items</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">path</span><span class="token punctuation">:</span> <span class="token string">"labels"</span>
|
||
<span class="token key atrule">fieldRef</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">fieldPath</span><span class="token punctuation">:</span> metadata.labels
|
||
<span class="token punctuation">-</span> <span class="token key atrule">path</span><span class="token punctuation">:</span> <span class="token string">"cpu_limit"</span>
|
||
<span class="token key atrule">resourceFieldRef</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containerName</span><span class="token punctuation">:</span> container<span class="token punctuation">-</span>test
|
||
<span class="token key atrule">resource</span><span class="token punctuation">:</span> limits.cpu
|
||
<span class="token punctuation">-</span> <span class="token key atrule">configMap</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> myconfigmap
|
||
<span class="token key atrule">items</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">key</span><span class="token punctuation">:</span> config
|
||
<span class="token key atrule">path</span><span class="token punctuation">:</span> my<span class="token punctuation">-</span>group/my<span class="token punctuation">-</span>config
|
||
</code></pre>
|
||
<h4 id="使用非默认权限模式设置多个-secret-的示例-pod">使用非默认权限模式设置多个 secret 的示例 pod</h4>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> volume<span class="token punctuation">-</span>test
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> container<span class="token punctuation">-</span>test
|
||
<span class="token key atrule">image</span><span class="token punctuation">:</span> busybox
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> all<span class="token punctuation">-</span>in<span class="token punctuation">-</span>one
|
||
<span class="token key atrule">mountPath</span><span class="token punctuation">:</span> <span class="token string">"/projected-volume"</span>
|
||
<span class="token key atrule">readOnly</span><span class="token punctuation">:</span> <span class="token boolean important">true</span>
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> all<span class="token punctuation">-</span>in<span class="token punctuation">-</span>one
|
||
<span class="token key atrule">projected</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">sources</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">secret</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> mysecret
|
||
<span class="token key atrule">items</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">key</span><span class="token punctuation">:</span> username
|
||
<span class="token key atrule">path</span><span class="token punctuation">:</span> my<span class="token punctuation">-</span>group/my<span class="token punctuation">-</span>username
|
||
<span class="token punctuation">-</span> <span class="token key atrule">secret</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> mysecret2
|
||
<span class="token key atrule">items</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">key</span><span class="token punctuation">:</span> password
|
||
<span class="token key atrule">path</span><span class="token punctuation">:</span> my<span class="token punctuation">-</span>group/my<span class="token punctuation">-</span>password
|
||
<span class="token key atrule">mode</span><span class="token punctuation">:</span> <span class="token number">511</span>
|
||
</code></pre>
|
||
<p>每个映射的卷来源在 <code>sources</code> 下的规格中列出。除了以下两个例外,参数几乎相同:</p>
|
||
<ul>
|
||
<li>对于 secret,<code>secretName</code> 字段已经被更改为 <code>name</code> 以与 ConfigMap 命名一致。</li>
|
||
<li><code>defaultMode</code> 只能在映射级别指定,而不能针对每个卷源指定。但是,如上所述,您可以明确设置每个映射的 <code>mode</code>。</li>
|
||
</ul>
|
||
<h3 id="portworxvolume">portworxVolume</h3>
|
||
<p><code>portworxVolume</code> 是一个与 Kubernetes 一起,以超融合模式运行的弹性块存储层。Portwork 指纹存储在服务器中,基于功能的分层,以及跨多个服务器聚合容量。 Portworx 在虚拟机或裸机 Linux 节点上运行。</p>
|
||
<p><code>portworxVolume</code> 可以通过 Kubernetes 动态创建,也可以在 Kubernetes pod 中预先设置和引用。</p>
|
||
<p>以下是一个引用预先配置的 PortworxVolume 的示例 pod:</p>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>portworx<span class="token punctuation">-</span>volume<span class="token punctuation">-</span>pod
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">image</span><span class="token punctuation">:</span> k8s.gcr.io/test<span class="token punctuation">-</span>webserver
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>container
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">mountPath</span><span class="token punctuation">:</span> /mnt
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> pxvol
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> pxvol
|
||
<span class="token comment"># This Portworx volume must already exist.</span>
|
||
<span class="token key atrule">portworxVolume</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">volumeID</span><span class="token punctuation">:</span> <span class="token string">"pxvol"</span>
|
||
<span class="token key atrule">fsType</span><span class="token punctuation">:</span> <span class="token string">"<fs-type>"</span>
|
||
</code></pre>
|
||
<p><strong>重要提示</strong>:在 pod 中使用之前,请确保您有一个名为 <code>pxvol</code> 的现有 PortworxVolume。</p>
|
||
<h3 id="quobyte">quobyte</h3>
|
||
<p><code>quobyte</code> 卷允许将现有的 <a href="http://www.quobyte.com" target="_blank">Quobyte</a> 卷挂载到容器中。</p>
|
||
<p><strong>重要提示</strong>:您必须先创建自己的 Quobyte 安装程序,然后才能使用它。</p>
|
||
<h3 id="rbd">rbd</h3>
|
||
<p><code>rbd</code> 卷允许将 Rados Block Device 卷挂载到容器中。不像 <code>emptyDir</code>,删除 Pod 时 <code>rbd</code>卷的内容被保留,卷仅仅被卸载。这意味着 RBD 卷可以预先填充数据,并且可以在 pod 之间“切换”数据。</p>
|
||
<p><strong>重要提示</strong>:您必须先自行安装 Ceph,然后才能使用 RBD。</p>
|
||
<p>RBD 的一个特点是它可以同时为多个用户以只读方式挂载。这意味着可以预先使用您的数据集填充卷,然后根据需要同时为多个 pod 并行提供。不幸的是,RBD 卷只能由单个用户以读写模式安装——不允许同时写入。</p>
|
||
<h3 id="scaleio">scaleIO</h3>
|
||
<p>ScaleIO 是一个基于软件的存储平台,可以使用现有的硬件来创建可扩展的共享块网络存储集群。<code>scaleIO</code> 卷插件允许已部署的 pod 访问现有的 ScaleIO 卷(或者它可以为持久性卷声明动态调配新卷,请参阅 <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/#scaleio" target="_blank">ScaleIO 持久卷</a>)。</p>
|
||
<p><strong>重要提示</strong>:您必须有一个已经配置好的 ScaleIO 集群,并和创建的卷一同运行,然后才能使用它们。</p>
|
||
<p>以下是使用 ScaleIO 的示例 pod 配置:</p>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> pod<span class="token punctuation">-</span><span class="token number">0</span>
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">image</span><span class="token punctuation">:</span> k8s.gcr.io/test<span class="token punctuation">-</span>webserver
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> pod<span class="token punctuation">-</span><span class="token number">0</span>
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">mountPath</span><span class="token punctuation">:</span> /test<span class="token punctuation">-</span>pd
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> vol<span class="token punctuation">-</span><span class="token number">0</span>
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> vol<span class="token punctuation">-</span><span class="token number">0</span>
|
||
<span class="token key atrule">scaleIO</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">gateway</span><span class="token punctuation">:</span> https<span class="token punctuation">:</span>//localhost<span class="token punctuation">:</span>443/api
|
||
<span class="token key atrule">system</span><span class="token punctuation">:</span> scaleio
|
||
<span class="token key atrule">protectionDomain</span><span class="token punctuation">:</span> sd0
|
||
<span class="token key atrule">storagePool</span><span class="token punctuation">:</span> sp1
|
||
<span class="token key atrule">volumeName</span><span class="token punctuation">:</span> vol<span class="token punctuation">-</span><span class="token number">0</span>
|
||
<span class="token key atrule">secretRef</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> sio<span class="token punctuation">-</span>secret
|
||
<span class="token key atrule">fsType</span><span class="token punctuation">:</span> xfs
|
||
</code></pre>
|
||
<p>有关更多详细信息,请参阅 <a href="https://github.com/kubernetes/examples/tree/master/staging/volumes/scaleio" target="_blank">ScaleIO 示例</a>。</p>
|
||
<h3 id="secret">secret</h3>
|
||
<p><code>secret</code> 卷用于将敏感信息(如密码)传递到 pod。您可以将 secret 存储在 Kubernetes API 中,并将它们挂载为文件,以供 Pod 使用,而无需直接连接到 Kubernetes。 <code>secret</code> 卷由 tmpfs(一个 RAM 支持的文件系统)支持,所以它们永远不会写入非易失性存储器。</p>
|
||
<p><strong>重要提示</strong>:您必须先在 Kubernetes API 中创建一个 secret,然后才能使用它。</p>
|
||
<h3 id="storageos">storageOS</h3>
|
||
<p><code>storageos</code> 卷允许将现有的 <a href="https://www.storageos.com" target="_blank">StorageOS</a> 卷挂载到容器中。</p>
|
||
<p>StorageOS 在 Kubernetes 环境中以容器方式运行,使本地或附加存储可以从 Kubernetes 集群中的任何节点访问。可以复制数据以防止节点故障。精简配置和压缩可以提高利用率并降低成本。</p>
|
||
<p>StorageOS 的核心是为容器提供块存储,可以通过文件系统访问。</p>
|
||
<p>StorageOS 容器需要 64 位 Linux,没有额外的依赖关系。可以使用免费的开发者许可证。</p>
|
||
<p><strong>重要提示</strong>:您必须在每个要访问 StorageOS 卷的节点上运行 StorageOS 容器,或者为该池提供存储容量。相关的安装说明,请参阅 <a href="https://docs.storageos.com" target="_blank">StorageOS文档</a>。</p>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">labels</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> redis
|
||
<span class="token key atrule">role</span><span class="token punctuation">:</span> master
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>storageos<span class="token punctuation">-</span>redis
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> master
|
||
<span class="token key atrule">image</span><span class="token punctuation">:</span> kubernetes/redis<span class="token punctuation">:</span>v1
|
||
<span class="token key atrule">env</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> MASTER
|
||
<span class="token key atrule">value</span><span class="token punctuation">:</span> <span class="token string">"true"</span>
|
||
<span class="token key atrule">ports</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">containerPort</span><span class="token punctuation">:</span> <span class="token number">6379</span>
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">mountPath</span><span class="token punctuation">:</span> /redis<span class="token punctuation">-</span>master<span class="token punctuation">-</span>data
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> redis<span class="token punctuation">-</span>data
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> redis<span class="token punctuation">-</span>data
|
||
<span class="token key atrule">storageos</span><span class="token punctuation">:</span>
|
||
<span class="token comment"># The `redis-vol01` volume must already exist within StorageOS in the `default` namespace.</span>
|
||
<span class="token key atrule">volumeName</span><span class="token punctuation">:</span> redis<span class="token punctuation">-</span>vol01
|
||
<span class="token key atrule">fsType</span><span class="token punctuation">:</span> ext4
|
||
</code></pre>
|
||
<h3 id="vspherevolume">vsphereVolume</h3>
|
||
<p><strong>先决条件</strong>:配置了 vSphere Cloud Provider 的 Kubernetes。有关云提供商的配置,请参阅 <a href="https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/" target="_blank">vSphere 入门指南</a>。</p>
|
||
<p><code>vsphereVolume</code> 用于将 vSphere VMDK 卷挂载到 Pod 中。卷的内容在卸载时会被保留。支持 VMFS 和 VSAN 数据存储。</p>
|
||
<p><strong>重要提示</strong>:在 Pod 中使用它之前,您必须使用以下一种方法创建 VMDK。</p>
|
||
<h4 id="创建-vmdk-卷">创建 VMDK 卷</h4>
|
||
<p>选择以下方法之一来创建 VMDK。</p>
|
||
<p>首先进入 ESX,然后使用以下命令创建一个 VMDK:</p>
|
||
<pre class="language-"><code class="lang-bash">vmkfstools -c 2G /vmfs/volumes/DatastoreName/volumes/myDisk.vmdk
|
||
</code></pre>
|
||
<p>使用下列命令创建一个 VMDK:</p>
|
||
<pre class="language-"><code class="lang-bash">vmware-vdiskmanager -c -t <span class="token number">0</span> -s 40GB -a lsilogic myDisk.vmdk
|
||
</code></pre>
|
||
<h4 id="vsphere-vmdk-示例配置">vSphere VMDK 示例配置</h4>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>vmdk
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">image</span><span class="token punctuation">:</span> k8s.gcr.io/test<span class="token punctuation">-</span>webserver
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>container
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">mountPath</span><span class="token punctuation">:</span> /test<span class="token punctuation">-</span>vmdk
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>volume
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> test<span class="token punctuation">-</span>volume
|
||
<span class="token comment"># This VMDK volume must already exist.</span>
|
||
<span class="token key atrule">vsphereVolume</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">volumePath</span><span class="token punctuation">:</span> <span class="token string">"[DatastoreName] volumes/myDisk"</span>
|
||
<span class="token key atrule">fsType</span><span class="token punctuation">:</span> ext4
|
||
</code></pre>
|
||
<p>更多的例子可以在<a href="https://github.com/kubernetes/examples/tree/master/staging/volumes/vsphere" target="_blank">这里</a>找到。</p>
|
||
<h2 id="使用-subpath">使用 subPath</h2>
|
||
<p>有时,在单个容器中共享一个卷用于多个用途是有用的。<code>volumeMounts.subPath</code> 属性可用于在引用的卷内而不是其根目录中指定子路径。</p>
|
||
<p>下面是一个使用单个共享卷的 LAMP 堆栈(Linux Apache Mysql PHP)的示例。 HTML 内容被映射到它的 html 目录,数据库将被存储在它的 mysql 目录中:</p>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Pod
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> my<span class="token punctuation">-</span>lamp<span class="token punctuation">-</span>site
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> mysql
|
||
<span class="token key atrule">image</span><span class="token punctuation">:</span> mysql
|
||
<span class="token key atrule">env</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> MYSQL_ROOT_PASSWORD
|
||
<span class="token key atrule">value</span><span class="token punctuation">:</span> <span class="token string">"rootpasswd"</span>
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">mountPath</span><span class="token punctuation">:</span> /var/lib/mysql
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> site<span class="token punctuation">-</span>data
|
||
<span class="token key atrule">subPath</span><span class="token punctuation">:</span> mysql
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> php
|
||
<span class="token key atrule">image</span><span class="token punctuation">:</span> php<span class="token punctuation">:</span>7.0<span class="token punctuation">-</span>apache
|
||
<span class="token key atrule">volumeMounts</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">mountPath</span><span class="token punctuation">:</span> /var/www/html
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> site<span class="token punctuation">-</span>data
|
||
<span class="token key atrule">subPath</span><span class="token punctuation">:</span> html
|
||
<span class="token key atrule">volumes</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> site<span class="token punctuation">-</span>data
|
||
<span class="token key atrule">persistentVolumeClaim</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">claimName</span><span class="token punctuation">:</span> my<span class="token punctuation">-</span>lamp<span class="token punctuation">-</span>site<span class="token punctuation">-</span>data
|
||
</code></pre>
|
||
<h2 id="资源">资源</h2>
|
||
<p><code>emptyDir</code> 卷的存储介质(磁盘、SSD 等)由保存在 kubelet 根目录的文件系统的介质(通常是 <code>/var/lib/kubelet</code>)决定。 <code>emptyDir</code> 或 <code>hostPath</code> 卷可占用多少空间并没有限制,容器之间或 Pod 之间也没有隔离。</p>
|
||
<p>在将来,我们预计 <code>emptyDir</code> 和 <code>hostPath</code> 卷将能够使用 <a href="https://kubernetes.io/docs/user-guide/compute-resources" target="_blank">resource</a> 规范请求一定的空间,并选择要使用的介质,适用于具有多种媒体类型的集群。</p>
|
||
<h2 id="out-of-tree-卷插件">Out-of-Tree 卷插件</h2>
|
||
<p>除了之前列出的卷类型之外,存储供应商可以创建自定义插件而不将其添加到 Kubernetes 存储库中。可以通过使用 <code>FlexVolume</code> 插件来实现。</p>
|
||
<p><code>FlexVolume</code>使用户能够将供应商卷挂载到容器中。供应商插件是使用驱动程序实现的,该驱动程序支持由 <code>FlexVolume</code> API定义的一系列卷命令。驱动程序必须安装在每个节点的预定义卷插件路径中。</p>
|
||
<h2 id="挂载传播">挂载传播</h2>
|
||
<p><strong>注意</strong>:挂载传播是 Kubernetes 1.8 中的一个 alpha 特性,在将来的版本中可能会重新设计甚至删除。</p>
|
||
<p>挂载传播允许将由容器挂载的卷共享到同一个 Pod 中的其他容器上,甚至是同一节点上的其他 Pod。</p>
|
||
<p>如果禁用 MountPropagation 功能,则不会传播 pod 中的卷挂载。也就是说,容器按照 <a href="https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt" target="_blank">Linux内核文档</a>中所述的 <code>private</code> 挂载传播运行。</p>
|
||
<p>要启用此功能,请在 <code>--feature-gates</code> 命令行选项中指定 <code>MountPropagation = true</code>。启用时,容器的 <code>volumeMounts</code> 字段有一个新的 <code>mountPropagation</code> 子字段。它的值为:</p>
|
||
<ul>
|
||
<li><p><code>HostToContainer</code>:此卷挂载将接收所有后续挂载到此卷或其任何子目录的挂载。这是 MountPropagation 功能启用时的默认模式。</p>
|
||
<p>同样的,如果任何带有 <code>Bidirectional</code> 挂载传播的 pod 挂载到同一个卷上,带有 <code>HostToContainer</code> 挂载传播的容器将会看到它。</p>
|
||
<p>该模式等同于<a href="https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt" target="_blank">Linux内核文档</a>中描述的 <code>rslave</code> 挂载传播。</p>
|
||
</li>
|
||
<li><p><code>Bidirectional</code> 卷挂载与 <code>HostToContainer</code> 挂载相同。另外,由容器创建的所有卷挂载将被传播回主机和所有使用相同卷的容器的所有容器。</p>
|
||
<p>此模式的一个典型用例是带有 Flex 卷驱动器或需要使用 HostPath 卷在主机上挂载某些内容的 pod。</p>
|
||
<p>该模式等同于 <a href="https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt" target="_blank">Linux内核文档</a>中所述的 <code>rshared</code> 挂载传播。</p>
|
||
</li>
|
||
</ul>
|
||
<p><strong>小心</strong>:双向挂载传播可能是危险的。它可能会损坏主机操作系统,因此只能在特权容器中使用。强烈建议熟悉 Linux 内核行为。另外,容器在 Pod 中创建的任何卷挂载必须在容器终止时销毁(卸载)。</p>
|
||
<h2 id="参考">参考</h2>
|
||
<ul>
|
||
<li><p><a href="https://kubernetes.io/docs/concepts/storage/volumes/" target="_blank">Volumes - kubernetes.io</a></p>
|
||
</li>
|
||
<li><p><a href="https://kubernetes.io/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/" target="_blank">使用持久化卷来部署 WordPress 和 MySQL - kubernetes.io</a></p>
|
||
</li>
|
||
</ul>
|
||
<footer class="page-footer"><span class="copyright"><a href="https://mp.weixin.qq.com/s/vWlSdzz2MNdXRr0sd2-LFg" target="_blank">加入云原生社区</a><p></p>Copyright © 2017-2021 | Distributed under <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/deed.zh" target="_blank">CC BY 4.0</a> | <a href="https://jimmysong.io" target="_blank">jimmysong.io</a> all right reserved,powered by Gitbook</span><span class="footer-modification"> Updated at
|
||
2022-01-18 02:29:37
|
||
</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="configmap-hot-update.html" class="navigation navigation-prev " aria-label="Previous page: ConfigMap 的热更新">
|
||
<i class="fa fa-angle-left"></i>
|
||
</a>
|
||
|
||
|
||
<a href="persistent-volume.html" class="navigation navigation-next " aria-label="Next page: 持久化卷(Persistent Volume)">
|
||
<i class="fa fa-angle-right"></i>
|
||
</a>
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<script>
|
||
var gitbook = gitbook || [];
|
||
gitbook.push(function() {
|
||
gitbook.page.hasChanged({"page":{"title":"Volume","level":"4.8.3","depth":2,"next":{"title":"持久化卷(Persistent Volume)","level":"4.8.4","depth":2,"path":"concepts/persistent-volume.md","ref":"concepts/persistent-volume.md","articles":[]},"previous":{"title":"ConfigMap 的热更新","level":"4.8.2.1","depth":3,"path":"concepts/configmap-hot-update.md","ref":"concepts/configmap-hot-update.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","theme-default","-highlight","prism","prism-themes","lightbox","ga","sitemap-general"],"styles":{"ebook":"styles/ebook.css","epub":"styles/epub.css","mobi":"styles/mobi.css","pdf":"styles/pdf.css","print":"styles/print.css","website":"styles/website.css"},"pluginsConfig":{"tbfed-pagefooter":{"copyright":"<a href=https://mp.weixin.qq.com/s/vWlSdzz2MNdXRr0sd2-LFg>加入云原生社区</a></p>Copyright © 2017-2021 | Distributed under <a href=https://creativecommons.org/licenses/by-nc-sa/4.0/deed.zh>CC BY 4.0</a> | <a href=https://jimmysong.io>jimmysong.io</a>","modify_label":" Updated at ","modify_format":"YYYY-MM-DD HH:mm:ss"},"prism":{"css":["prism-themes/themes/prism-ghcolors.css"]},"github":{"url":"https://github.com/rootsongjc/kubernetes-handbook"},"editlink":{"label":"编辑本页","multilingual":false,"base":"https://github.com/rootsongjc/kubernetes-handbook/blob/master/"},"splitter":{},"codesnippet":{},"sitemap-general":{"prefix":"https://jimmysong.io/kubernetes-handbook/"},"fontsettings":{"theme":"white","family":"sans","size":2},"favicon":{"shortcut":"favicon.ico","bookmark":"favicon.ico"},"lightbox":{"jquery":true,"sameUuid":false},"page-toc-button":{},"back-to-top-button":{},"prism-themes":{},"github-buttons":{"repo":"rootsongjc/kubernetes-handbook","types":["star"],"size":"small"},"3-ba":{"configuration":"auto","token":"11f7d254cfa4e0ca44b175c66d379ecc"},"ga":{"configuration":"auto","token":"UA-93485976-1"},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"theme-default":{"showLevel":true,"styles":{"ebook":"styles/ebook.css","epub":"styles/epub.css","mobi":"styles/mobi.css","pdf":"styles/pdf.css","print":"styles/print.css","website":"styles/website.css"}},"search-plus":{},"image-captions":{"caption":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_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":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.1","level":"2.4","list_caption":"Figure: 云计算演进历程","alt":"云计算演进历程","nro":1,"url":"../images/cloud-computing-evolution-road.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云计算演进历程","attributes":{},"skip":false,"key":"2.4.1"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.2","level":"2.4","list_caption":"Figure: 来自 Twitter @MarcWilczek","alt":"来自 Twitter @MarcWilczek","nro":2,"url":"../images/cloud-native-comes-of-age.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"来自 Twitter @MarcWilczek","attributes":{},"skip":false,"key":"2.4.2"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.3","level":"2.4","list_caption":"Figure: 云原生思维导图","alt":"云原生思维导图","nro":3,"url":"../images/cloud-native-architecutre-mindnode.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生思维导图","attributes":{},"skip":false,"key":"2.4.3"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.4","level":"2.4","list_caption":"Figure: 十二因素应用","alt":"十二因素应用","nro":4,"url":"../images/12-factor-app.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"十二因素应用","attributes":{},"skip":false,"key":"2.4.4"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.5","level":"2.4","list_caption":"Figure: 容器生态","alt":"容器生态","nro":5,"url":"../images/container-ecosystem.png","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"容器生态","attributes":{},"skip":false,"key":"2.4.5"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.6","level":"2.4","list_caption":"Figure: 使用 Jenkins 进行持续集成与发布流程图","alt":"使用 Jenkins 进行持续集成与发布流程图","nro":6,"url":"../images/kubernetes-jenkins-ci-cd.png","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"使用 Jenkins 进行持续集成与发布流程图","attributes":{},"skip":false,"key":"2.4.6"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.7","level":"2.4","list_caption":"Figure: filebeat 日志收集架构图","alt":"filebeat 日志收集架构图","nro":7,"url":"../images/filebeat-log-collector-arch.png","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"filebeat 日志收集架构图","attributes":{},"skip":false,"key":"2.4.7"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.8","level":"2.4","list_caption":"Figure: API 文档","alt":"API 文档","nro":8,"url":"../images/k8s-app-monitor-test-api-doc.jpg","index":8,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"API 文档","attributes":{},"skip":false,"key":"2.4.8"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.9","level":"2.4","list_caption":"Figure: 迁移步骤示意图","alt":"迁移步骤示意图","nro":9,"url":"../images/migrating-hadoop-yarn-to-kubernetes.png","index":9,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"迁移步骤示意图","attributes":{},"skip":false,"key":"2.4.9"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.10","level":"2.4","list_caption":"Figure: service mesh 架构图","alt":"service mesh 架构图","nro":10,"url":"../images/serivce-mesh-control-plane.png","index":10,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"service mesh 架构图","attributes":{},"skip":false,"key":"2.4.10"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.11","level":"2.4","list_caption":"Figure: kibana 界面","alt":"kibana 界面","nro":11,"url":"../images/filebeat-docker-test.jpg","index":11,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kibana 界面","attributes":{},"skip":false,"key":"2.4.11"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.12","level":"2.4","list_caption":"Figure: Grafana 界面示意图 1","alt":"Grafana 界面示意图 1","nro":12,"url":"../images/kubernetes-devops-example-grafana-1.png","index":12,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Grafana 界面示意图 1","attributes":{},"skip":false,"key":"2.4.12"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.13","level":"2.4","list_caption":"Figure: Grafana 界面示意图 2","alt":"Grafana 界面示意图 2","nro":13,"url":"../images/kubernetes-devops-example-grafana-2.png","index":13,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Grafana 界面示意图 2","attributes":{},"skip":false,"key":"2.4.13"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.14","level":"2.4","list_caption":"Figure: Grafana 界面示意图 3","alt":"Grafana 界面示意图 3","nro":14,"url":"../images/kubernetes-devops-example-grafana-3.png","index":14,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Grafana 界面示意图 3","attributes":{},"skip":false,"key":"2.4.14"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.15","level":"2.4","list_caption":"Figure: dashboard","alt":"dashboard","nro":15,"url":"../images/spark-job-on-kubernetes-example-1.jpg","index":15,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"dashboard","attributes":{},"skip":false,"key":"2.4.15"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.16","level":"2.4","list_caption":"Figure: Grafana","alt":"Grafana","nro":16,"url":"../images/spark-job-on-kubernetes-example-2.jpg","index":16,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Grafana","attributes":{},"skip":false,"key":"2.4.16"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.1","level":"2.5","list_caption":"Figure: 容器生态图","alt":"容器生态图","nro":17,"url":"../images/container-ecosystem.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"容器生态图","attributes":{},"skip":false,"key":"2.5.1"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.2","level":"2.5","list_caption":"Figure: Kubernetes架构","alt":"Kubernetes架构","nro":18,"url":"../images/kubernetes-high-level-component-archtecture.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes架构","attributes":{},"skip":false,"key":"2.5.2"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.3","level":"2.5","list_caption":"Figure: 云原生的核心目标","alt":"云原生的核心目标","nro":19,"url":"../images/cloud-native-core-target.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生的核心目标","attributes":{},"skip":false,"key":"2.5.3"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.4","level":"2.5","list_caption":"Figure: FaaS Landscape","alt":"FaaS Landscape","nro":20,"url":"../images/redpoint-faas-landscape.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"FaaS Landscape","attributes":{},"skip":false,"key":"2.5.4"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.5","level":"2.5","list_caption":"Figure: 运行在 Kubernetes 上的负载(2017 年)","alt":"运行在 Kubernetes 上的负载(2017 年)","nro":21,"url":"../images/0069RVTdgy1fv5mxr6fxtj31kw11q484.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"运行在 Kubernetes 上的负载(2017 年)","attributes":{},"skip":false,"key":"2.5.5"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.6","level":"2.5","list_caption":"Figure: Gartner 技术爆发趋势图(2017 年)","alt":"Gartner 技术爆发趋势图(2017 年)","nro":22,"url":"../images/0069RVTdgy1fv5my2jtxzj315o0z8dkr.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Gartner 技术爆发趋势图(2017 年)","attributes":{},"skip":false,"key":"2.5.6"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.7","level":"2.5","list_caption":"Figure: 微服务的关注点","alt":"微服务的关注点","nro":23,"url":"../images/microservices-concerns.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"微服务的关注点","attributes":{},"skip":false,"key":"2.5.7"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.8","level":"2.5","list_caption":"Figure: 微服务中的两种服务发现方式","alt":"微服务中的两种服务发现方式","nro":24,"url":"../images/service-discovery-in-microservices.png","index":8,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"微服务中的两种服务发现方式","attributes":{},"skip":false,"key":"2.5.8"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.9","level":"2.5","list_caption":"Figure: Cloud Native Features","alt":"Cloud Native Features","nro":25,"url":"https://jimmysong.io/kubernetes-handbook/images/cloud-native-architecutre-mindnode.jpg","index":9,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Cloud Native Features","attributes":{},"skip":false,"key":"2.5.9"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.10","level":"2.5","list_caption":"Figure: Cloud Native Landscape v1.0","alt":"Cloud Native Landscape v1.0","nro":26,"url":"../images/0069RVTdgy1fv5myp6ednj31kw0w0u0x.jpg","index":10,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Cloud Native Landscape v1.0","attributes":{},"skip":false,"key":"2.5.10"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.11","level":"2.5","list_caption":"Figure: 使用 Kubernetes 构建云原生架构应用","alt":"使用 Kubernetes 构建云原生架构应用","nro":27,"url":"../images/building-cloud-native-architecture-with-kubernetes.png","index":11,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"使用 Kubernetes 构建云原生架构应用","attributes":{},"skip":false,"key":"2.5.11"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.12","level":"2.5","list_caption":"Figure: 创建 Kubernetes 原生应用","alt":"创建 Kubernetes 原生应用","nro":28,"url":"../images/creating-kubernetes-native-app.jpg","index":12,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"创建 Kubernetes 原生应用","attributes":{},"skip":false,"key":"2.5.12"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.13","level":"2.5","list_caption":"Figure: istio vs linkerd","alt":"istio vs linkerd","nro":29,"url":"../images/istio-vs-linkerd.jpg","index":13,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"istio vs linkerd","attributes":{},"skip":false,"key":"2.5.13"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.14","level":"2.5","list_caption":"Figure: 部署流水线","alt":"部署流水线","nro":30,"url":"../images/0069RVTdgy1fv5mzj8rj6j318g1ewtfc.jpg","index":14,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"部署流水线","attributes":{},"skip":false,"key":"2.5.14"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.15","level":"2.5","list_caption":"Figure: 使用不同调度器的 Spark on Kubernetes","alt":"使用不同调度器的 Spark on Kubernetes","nro":31,"url":"../images/spark-on-kubernetes-with-different-schedulers.jpg","index":15,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"使用不同调度器的 Spark on Kubernetes","attributes":{},"skip":false,"key":"2.5.15"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.16","level":"2.5","list_caption":"Figure: Kubernetes 解决方案","alt":"Kubernetes 解决方案","nro":32,"url":"../images/0069RVTdgy1fv5mzywc83j31fk1i8qg4.jpg","index":16,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 解决方案","attributes":{},"skip":false,"key":"2.5.16"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.17","level":"2.5","list_caption":"Figure: Kubernetes SIG","alt":"Kubernetes SIG","nro":33,"url":"../images/kubernetes-sigs.jpg","index":17,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes SIG","attributes":{},"skip":false,"key":"2.5.17"},{"backlink":"cloud-native/define-cloud-native-app.html#fig2.6.1","level":"2.6","list_caption":"Figure: 云原生应用模型","alt":"云原生应用模型","nro":34,"url":"../images/cloud-native-app-model.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生应用模型","attributes":{},"skip":false,"key":"2.6.1"},{"backlink":"cloud-native/define-cloud-native-app.html#fig2.6.2","level":"2.6","list_caption":"Figure: 云原生应用模型中的目标角色","alt":"云原生应用模型中的目标角色","nro":35,"url":"../images/roles.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生应用模型中的目标角色","attributes":{},"skip":false,"key":"2.6.2"},{"backlink":"cloud-native/oam.html#fig2.6.1.1","level":"2.6.1","list_caption":"Figure: OAM 规范示意图","alt":"OAM 规范示意图","nro":36,"url":"../images/oam-spec.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OAM 规范示意图","attributes":{},"skip":false,"key":"2.6.1.1"},{"backlink":"cloud-native/oam.html#fig2.6.1.2","level":"2.6.1","list_caption":"Figure: OAM 的原理","alt":"OAM 的原理","nro":37,"url":"../images/oam-principle.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OAM 的原理","attributes":{},"skip":false,"key":"2.6.1.2"},{"backlink":"cloud-native/crossplane.html#fig2.6.2.1","level":"2.6.2","list_caption":"Figure: Wordpress 页面","alt":"Wordpress 页面","nro":38,"url":"../images/wordpress.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Wordpress 页面","attributes":{},"skip":false,"key":"2.6.2.1"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.1","level":"2.7.1","list_caption":"Figure: 云原生编程语言ballerina","alt":"云原生编程语言ballerina","nro":39,"url":"../images/philosophy-page-diagrams-top.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言ballerina","attributes":{},"skip":false,"key":"2.7.1.1"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.2","level":"2.7.1","list_caption":"Figure: 云原生编程语言Ballerina的序列图设计理念","alt":"云原生编程语言Ballerina的序列图设计理念","nro":40,"url":"../images/philosophy-principle-diagrams-01.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言Ballerina的序列图设计理念","attributes":{},"skip":false,"key":"2.7.1.2"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.3","level":"2.7.1","list_caption":"Figure: 云原生编程语言Ballerina的并发理念","alt":"云原生编程语言Ballerina的并发理念","nro":41,"url":"../images/philosophy-principle-diagrams-02.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言Ballerina的并发理念","attributes":{},"skip":false,"key":"2.7.1.3"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.4","level":"2.7.1","list_caption":"Figure: 云原生编程语言ballerina运行时架构","alt":"云原生编程语言ballerina运行时架构","nro":42,"url":"../images/philosophy-diagrams-for-site-02.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言ballerina运行时架构","attributes":{},"skip":false,"key":"2.7.1.4"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.5","level":"2.7.1","list_caption":"Figure: 云原生编程语言ballerina部署架构图","alt":"云原生编程语言ballerina部署架构图","nro":43,"url":"../images/philosophy-diagrams-for-site-03.png","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言ballerina部署架构图","attributes":{},"skip":false,"key":"2.7.1.5"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.6","level":"2.7.1","list_caption":"Figure: 云原生编程语言ballerina生命周期架构图","alt":"云原生编程语言ballerina生命周期架构图","nro":44,"url":"../images/philosophy-diagrams-for-site-04.png","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言ballerina生命周期架构图","attributes":{},"skip":false,"key":"2.7.1.6"},{"backlink":"cloud-native/cloud-native-programming-language-pulumi.html#fig2.7.2.1","level":"2.7.2","list_caption":"Figure: 云原生编程语言Pulumi","alt":"云原生编程语言Pulumi","nro":45,"url":"../images/pulumi.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言Pulumi","attributes":{},"skip":false,"key":"2.7.2.1"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.1","level":"2.8","list_caption":"Figure: Kubernetes 云原生的操作系统","alt":"Kubernetes 云原生的操作系统","nro":46,"url":"../images/00704eQkgy1frr4z08j6oj31p20w2n6n.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 云原生的操作系统","attributes":{},"skip":false,"key":"2.8.1"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.2","level":"2.8","list_caption":"Figure: 操作系统层次","alt":"操作系统层次","nro":47,"url":"../images/00704eQkgy1frr52hl4eaj31qy15en74.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"操作系统层次","attributes":{},"skip":false,"key":"2.8.2"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.3","level":"2.8","list_caption":"Figure: 云原生景观图","alt":"云原生景观图","nro":48,"url":"../images/00704eQkgy1frr53j3aiuj32fs1dc7wi.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生景观图","attributes":{},"skip":false,"key":"2.8.3"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.4","level":"2.8","list_caption":"Figure: KubeVirt架构图","alt":"KubeVirt架构图","nro":49,"url":"../images/00704eQkgy1frr54de5oyj31qw14qn2x.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"KubeVirt架构图","attributes":{},"skip":false,"key":"2.8.4"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.5","level":"2.8","list_caption":"Figure: Kubernetes中的资源隔离","alt":"Kubernetes中的资源隔离","nro":50,"url":"../images/00704eQkgy1frr54ztql2j329q0zwwlf.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes中的资源隔离","attributes":{},"skip":false,"key":"2.8.5"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.6","level":"2.8","list_caption":"Figure: OpenEBS 控制平面架构","alt":"OpenEBS 控制平面架构","nro":51,"url":"../images/00704eQkgy1frr56m7z2sj31y010y17y.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenEBS 控制平面架构","attributes":{},"skip":false,"key":"2.8.6"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.7","level":"2.8","list_caption":"Figure: OpenEBS 的存储卷管理","alt":"OpenEBS 的存储卷管理","nro":52,"url":"../images/00704eQkgy1frr57nm2mnj31xk11qqej.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenEBS 的存储卷管理","attributes":{},"skip":false,"key":"2.8.7"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.8","level":"2.8","list_caption":"Figure: Hadoop YARN 迁移到 Kubernetes的示例","alt":"Hadoop YARN 迁移到 Kubernetes的示例","nro":53,"url":"../images/00704eQkgy1frr58ebf2lj323o11219r.jpg","index":8,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Hadoop YARN 迁移到 Kubernetes的示例","attributes":{},"skip":false,"key":"2.8.8"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.9","level":"2.8","list_caption":"Figure: Spark on Yarn with Kubernetes","alt":"Spark on Yarn with Kubernetes","nro":54,"url":"../images/00704eQkgy1frr59gzzwsj32gg16k4qp.jpg","index":9,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Spark on Yarn with Kubernetes","attributes":{},"skip":false,"key":"2.8.9"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.10","level":"2.8","list_caption":"Figure: 云原生与12因素应用","alt":"云原生与12因素应用","nro":55,"url":"../images/00704eQkgy1frr5arzvetj31no12mdre.jpg","index":10,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生与12因素应用","attributes":{},"skip":false,"key":"2.8.10"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.11","level":"2.8","list_caption":"Figure: 云原生编程语言","alt":"云原生编程语言","nro":56,"url":"../images/00704eQkgy1frr5c8bwmtj31ou152qc3.jpg","index":11,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言","attributes":{},"skip":false,"key":"2.8.11"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.12","level":"2.8","list_caption":"Figure: Gitkube","alt":"Gitkube","nro":57,"url":"../images/00704eQkgy1frr5bulhuhj329m10iwua.jpg","index":12,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Gitkube","attributes":{},"skip":false,"key":"2.8.12"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.13","level":"2.8","list_caption":"Figure: Kuberentes中的流量管理","alt":"Kuberentes中的流量管理","nro":58,"url":"../images/00704eQkgy1frr5dsurx6j320i140tpf.jpg","index":13,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kuberentes中的流量管理","attributes":{},"skip":false,"key":"2.8.13"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.14","level":"2.8","list_caption":"Figure: Istio Service Mesh架构图","alt":"Istio Service Mesh架构图","nro":59,"url":"../images/00704eQkgy1frr5exqm7kj320u18mh2t.jpg","index":14,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio Service Mesh架构图","attributes":{},"skip":false,"key":"2.8.14"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.15","level":"2.8","list_caption":"Figure: Service Mesh架构","alt":"Service Mesh架构","nro":60,"url":"../images/00704eQkgy1frr5fxzoltj32f81akqr2.jpg","index":15,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Service Mesh架构","attributes":{},"skip":false,"key":"2.8.15"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.16","level":"2.8","list_caption":"Figure: Envoy proxy架构图","alt":"Envoy proxy架构图","nro":61,"url":"../images/envoy-arch.png","index":16,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Envoy proxy架构图","attributes":{},"skip":false,"key":"2.8.16"},{"backlink":"cloud-native/play-with-kubernetes.html#fig3.2.1","level":"3.2","list_caption":"Figure: Play with Kubernetes 网页截图","alt":"Play with Kubernetes 网页截图","nro":62,"url":"../images/play-with-kubernetes.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Play with Kubernetes 网页截图","attributes":{},"skip":false,"key":"3.2.1"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.1","level":"3.3","list_caption":"Figure: Kubernetes dashboard","alt":"Kubernetes dashboard","nro":63,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/dashboard-animation.gif","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes dashboard","attributes":{},"skip":false,"key":"3.3.1"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.2","level":"3.3","list_caption":"Figure: Grafana","alt":"Grafana","nro":64,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/grafana-animation.gif","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Grafana","attributes":{},"skip":false,"key":"3.3.2"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.3","level":"3.3","list_caption":"Figure: Traefik dashboard","alt":"Traefik dashboard","nro":65,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/traefik-ingress.gif","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Traefik dashboard","attributes":{},"skip":false,"key":"3.3.3"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.4","level":"3.3","list_caption":"Figure: bookinfo示例","alt":"bookinfo示例","nro":66,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/bookinfo-demo.gif","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"bookinfo示例","attributes":{},"skip":false,"key":"3.3.4"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.5","level":"3.3","list_caption":"Figure: Kiali页面","alt":"Kiali页面","nro":67,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/kiali.gif","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kiali页面","attributes":{},"skip":false,"key":"3.3.5"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.6","level":"3.3","list_caption":"Figure: Scope页面","alt":"Scope页面","nro":68,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/weave-scope-animation.gif","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Scope页面","attributes":{},"skip":false,"key":"3.3.6"},{"backlink":"cloud-native/setup-kubernetes-with-rancher-and-aliyun.html#fig3.4.1","level":"3.4","list_caption":"Figure: Rancher 界面","alt":"Rancher 界面","nro":69,"url":"../images/rancher-web.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Rancher 界面","attributes":{},"skip":false,"key":"3.4.1"},{"backlink":"cloud-native/setup-kubernetes-with-rancher-and-aliyun.html#fig3.4.2","level":"3.4","list_caption":"Figure: 自定义节点信息","alt":"自定义节点信息","nro":70,"url":"../images/rancher-customize-node.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"自定义节点信息","attributes":{},"skip":false,"key":"3.4.2"},{"backlink":"cloud-native/setup-kubernetes-with-rancher-and-aliyun.html#fig3.4.3","level":"3.4","list_caption":"Figure: Rancher 集群监控页面","alt":"Rancher 集群监控页面","nro":71,"url":"../images/rancher-cluster.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Rancher 集群监控页面","attributes":{},"skip":false,"key":"3.4.3"},{"backlink":"concepts/index.html#fig4.1.1","level":"4.1","list_caption":"Figure: Borg 架构","alt":"Borg 架构","nro":72,"url":"../images/borg.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Borg 架构","attributes":{},"skip":false,"key":"4.1.1"},{"backlink":"concepts/index.html#fig4.1.2","level":"4.1","list_caption":"Figure: Kubernetes 架构","alt":"Kubernetes 架构","nro":73,"url":"../images/architecture.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 架构","attributes":{},"skip":false,"key":"4.1.2"},{"backlink":"concepts/index.html#fig4.1.3","level":"4.1","list_caption":"Figure: Kuberentes 架构(图片来自于网络)","alt":"Kuberentes 架构(图片来自于网络)","nro":74,"url":"../images/kubernetes-high-level-component-archtecture.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kuberentes 架构(图片来自于网络)","attributes":{},"skip":false,"key":"4.1.3"},{"backlink":"concepts/index.html#fig4.1.4","level":"4.1","list_caption":"Figure: kubernetes 整体架构示意图","alt":"kubernetes 整体架构示意图","nro":75,"url":"../images/kubernetes-whole-arch.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes 整体架构示意图","attributes":{},"skip":false,"key":"4.1.4"},{"backlink":"concepts/index.html#fig4.1.5","level":"4.1","list_caption":"Figure: Kubernetes master 架构示意图","alt":"Kubernetes master 架构示意图","nro":76,"url":"../images/kubernetes-master-arch.png","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes master 架构示意图","attributes":{},"skip":false,"key":"4.1.5"},{"backlink":"concepts/index.html#fig4.1.6","level":"4.1","list_caption":"Figure: kubernetes node 架构示意图","alt":"kubernetes node 架构示意图","nro":77,"url":"../images/kubernetes-node-arch.png","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes node 架构示意图","attributes":{},"skip":false,"key":"4.1.6"},{"backlink":"concepts/index.html#fig4.1.7","level":"4.1","list_caption":"Figure: Kubernetes 分层架构示意图","alt":"Kubernetes 分层架构示意图","nro":78,"url":"../images/kubernetes-layers-arch.png","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 分层架构示意图","attributes":{},"skip":false,"key":"4.1.7"},{"backlink":"concepts/concepts.html#fig4.1.1.1","level":"4.1.1","list_caption":"Figure: Kubernetes 分层架构示意图","alt":"Kubernetes 分层架构示意图","nro":79,"url":"../images/006tNc79ly1fzniqvmi51j31gq0s0q5u.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 分层架构示意图","attributes":{},"skip":false,"key":"4.1.1.1"},{"backlink":"concepts/cri.html#fig4.1.3.1.1","level":"4.1.3.1","list_caption":"Figure: CRI 架构 - 图片来自 kubernetes blog","alt":"CRI 架构 - 图片来自 kubernetes blog","nro":80,"url":"../images/cri-architecture.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CRI 架构 - 图片来自 kubernetes blog","attributes":{},"skip":false,"key":"4.1.3.1.1"},{"backlink":"concepts/pod-overview.html#fig4.2.1.1","level":"4.2.1","list_caption":"Figure: pod diagram","alt":"pod diagram","nro":81,"url":"../images/pod-overview.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"pod diagram","attributes":{},"skip":false,"key":"4.2.1.1"},{"backlink":"concepts/pod.html#fig4.2.2.1","level":"4.2.2","list_caption":"Figure: Pod Cheatsheet","alt":"Pod Cheatsheet","nro":82,"url":"../images/kubernetes-pod-cheatsheet.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Pod Cheatsheet","attributes":{},"skip":false,"key":"4.2.2.1"},{"backlink":"concepts/pod.html#fig4.2.2.2","level":"4.2.2","list_caption":"Figure: Pod示意图","alt":"Pod示意图","nro":83,"url":"../images/pod-overview.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Pod示意图","attributes":{},"skip":false,"key":"4.2.2.2"},{"backlink":"concepts/pause-container.html#fig4.2.4.1","level":"4.2.4","list_caption":"Figure: Pause容器","alt":"Pause容器","nro":84,"url":"../images/pause-container.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Pause容器","attributes":{},"skip":false,"key":"4.2.4.1"},{"backlink":"concepts/pod-lifecycle.html#fig4.2.6.1","level":"4.2.6","list_caption":"Figure: Pod的生命周期示意图(图片来自网络)","alt":"Pod的生命周期示意图(图片来自网络)","nro":85,"url":"../images/kubernetes-pod-life-cycle.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Pod的生命周期示意图(图片来自网络)","attributes":{},"skip":false,"key":"4.2.6.1"},{"backlink":"concepts/label.html#fig4.3.3.1","level":"4.3.3","list_caption":"Figure: label示意图","alt":"label示意图","nro":86,"url":"../images/labels.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"label示意图","attributes":{},"skip":false,"key":"4.3.3.1"},{"backlink":"concepts/deployment.html#fig4.4.1.1","level":"4.4.1","list_caption":"Figure: kubernetes deployment cheatsheet","alt":"kubernetes deployment cheatsheet","nro":87,"url":"../images/deployment-cheatsheet.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes deployment cheatsheet","attributes":{},"skip":false,"key":"4.4.1.1"},{"backlink":"concepts/horizontal-pod-autoscaling.html#fig4.4.7.1","level":"4.4.7","list_caption":"Figure: horizontal-pod-autoscaler","alt":"horizontal-pod-autoscaler","nro":88,"url":"../images/horizontal-pod-autoscaler.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"horizontal-pod-autoscaler","attributes":{},"skip":false,"key":"4.4.7.1"},{"backlink":"concepts/service.html#fig4.5.1.1","level":"4.5.1","list_caption":"Figure: userspace代理模式下Service概览图","alt":"userspace代理模式下Service概览图","nro":89,"url":"../images/services-userspace-overview.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"userspace代理模式下Service概览图","attributes":{},"skip":false,"key":"4.5.1.1"},{"backlink":"concepts/service.html#fig4.5.1.2","level":"4.5.1","list_caption":"Figure: iptables代理模式下Service概览图","alt":"iptables代理模式下Service概览图","nro":90,"url":"../images/services-iptables-overview.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"iptables代理模式下Service概览图","attributes":{},"skip":false,"key":"4.5.1.2"},{"backlink":"concepts/service.html#fig4.5.1.3","level":"4.5.1","list_caption":"Figure: ipvs代理模式下Service概览图","alt":"ipvs代理模式下Service概览图","nro":91,"url":"../images/service-ipvs-overview.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"ipvs代理模式下Service概览图","attributes":{},"skip":false,"key":"4.5.1.3"},{"backlink":"concepts/gateway.html#fig4.5.4.1","level":"4.5.4","list_caption":"Figure: Kubernetes Gateway API 简介","alt":"Kubernetes Gateway API 简介","nro":92,"url":"../images/kubernetes-gateway-api-intro.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes Gateway API 简介","attributes":{},"skip":false,"key":"4.5.4.1"},{"backlink":"concepts/gateway.html#fig4.5.4.2","level":"4.5.4","list_caption":"Figure: 路由绑定示意图","alt":"路由绑定示意图","nro":93,"url":"../images/gateway-api-route-binding.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"路由绑定示意图","attributes":{},"skip":false,"key":"4.5.4.2"},{"backlink":"concepts/gateway.html#fig4.5.4.3","level":"4.5.4","list_caption":"Figure: Gateway API 流程图","alt":"Gateway API 流程图","nro":94,"url":"../images/gateway-api-request-flow.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Gateway API 流程图","attributes":{},"skip":false,"key":"4.5.4.3"},{"backlink":"concepts/flannel.html#fig4.7.1.1","level":"4.7.1","list_caption":"Figure: flannel 网络架构(图片来自 openshift)","alt":"flannel 网络架构(图片来自 openshift)","nro":95,"url":"../images/flannel-networking.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"flannel 网络架构(图片来自 openshift)","attributes":{},"skip":false,"key":"4.7.1.1"},{"backlink":"concepts/calico.html#fig4.7.2.1","level":"4.7.2","list_caption":"Figure: Calico","alt":"Calico","nro":96,"url":"../images/006tNc79gy1fz65bt7ieej30c90bsgn2.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Calico","attributes":{},"skip":false,"key":"4.7.2.1"},{"backlink":"concepts/calico.html#fig4.7.2.2","level":"4.7.2","list_caption":"Figure: Calico 架构图","alt":"Calico 架构图","nro":97,"url":"../images/calico-architecture.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Calico 架构图","attributes":{},"skip":false,"key":"4.7.2.2"},{"backlink":"concepts/cilium.html#fig4.7.3.1","level":"4.7.3","list_caption":"Figure: Cilium","alt":"Cilium","nro":98,"url":"../images/006tNbRwly1fwqi98i51ij30sc0j80zn.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Cilium","attributes":{},"skip":false,"key":"4.7.3.1"},{"backlink":"concepts/cilium-concepts.html#fig4.7.3.1.1","level":"4.7.3.1","list_caption":"Figure: Cilium 组件(来自 Cilium 官网)","alt":"Cilium 组件(来自 Cilium 官网)","nro":99,"url":"../images/006tNbRwly1fwztvhg0gmj318z143tdv.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Cilium 组件(来自 Cilium 官网)","attributes":{},"skip":false,"key":"4.7.3.1.1"},{"backlink":"concepts/cilium-concepts.html#fig4.7.3.1.2","level":"4.7.3.1","list_caption":"Figure: Cilium 网络配置策略","alt":"Cilium 网络配置策略","nro":100,"url":"../images/006tNbRwly1fwzreaalj6j30dz0dy3z3.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Cilium 网络配置策略","attributes":{},"skip":false,"key":"4.7.3.1.2"},{"backlink":"concepts/service-catalog.html#fig4.9.5.1","level":"4.9.5","list_caption":"Figure: Service Catalog 架构","alt":"Service Catalog 架构","nro":101,"url":"../images/service-catalog-architecture.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Service Catalog 架构","attributes":{},"skip":false,"key":"4.9.5.1"},{"backlink":"concepts/service-catalog.html#fig4.9.5.2","level":"4.9.5","list_caption":"Figure: 列出服务","alt":"列出服务","nro":102,"url":"../images/service-catalog-list.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"列出服务","attributes":{},"skip":false,"key":"4.9.5.2"},{"backlink":"concepts/service-catalog.html#fig4.9.5.3","level":"4.9.5","list_caption":"Figure: 启用一个服务","alt":"启用一个服务","nro":103,"url":"../images/service-catalog-provision.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"启用一个服务","attributes":{},"skip":false,"key":"4.9.5.3"},{"backlink":"concepts/service-catalog.html#fig4.9.5.4","level":"4.9.5","list_caption":"Figure: Bind to a managed service","alt":"Bind to a managed service","nro":104,"url":"../images/service-catalog-bind.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Bind to a managed service","attributes":{},"skip":false,"key":"4.9.5.4"},{"backlink":"concepts/service-catalog.html#fig4.9.5.5","level":"4.9.5","list_caption":"Figure: 映射连接凭证","alt":"映射连接凭证","nro":105,"url":"../images/service-catalog-map.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"映射连接凭证","attributes":{},"skip":false,"key":"4.9.5.5"},{"backlink":"practice/federation.html#fig4.10.2.1","level":"4.10.2","list_caption":"Figure: Kubernetes 集群联邦架构图","alt":"Kubernetes 集群联邦架构图","nro":106,"url":"../images/federation-concepts.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 集群联邦架构图","attributes":{},"skip":false,"key":"4.10.2.1"},{"backlink":"practice/federation.html#fig4.10.2.2","level":"4.10.2","list_caption":"Figure: KubeFed 基础架构","alt":"KubeFed 基础架构","nro":107,"url":"../images/sync-controller.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"KubeFed 基础架构","attributes":{},"skip":false,"key":"4.10.2.2"},{"backlink":"practice/federation.html#fig4.10.2.3","level":"4.10.2","list_caption":"Figure: RSP","alt":"RSP","nro":108,"url":"../images/kubefed-rsp.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"RSP","attributes":{},"skip":false,"key":"4.10.2.3"},{"backlink":"practice/federation.html#fig4.10.2.4","level":"4.10.2","list_caption":"Figure: DNS","alt":"DNS","nro":109,"url":"../images/kubefed-service-dns.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"DNS","attributes":{},"skip":false,"key":"4.10.2.4"},{"backlink":"guide/using-kubectl.html#fig5.3.2.1","level":"5.3.2","list_caption":"Figure: kubectl cheatsheet","alt":"kubectl cheatsheet","nro":110,"url":"../images/kubernetes-kubectl-cheatsheet.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubectl cheatsheet","attributes":{},"skip":false,"key":"5.3.2.1"},{"backlink":"guide/using-kubectl.html#fig5.3.2.2","level":"5.3.2","list_caption":"Figure: 增加kubeclt命令的工具(图片来自网络)","alt":"增加kubeclt命令的工具(图片来自网络)","nro":111,"url":"../images/tools-to-supercharge-kubectl.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"增加kubeclt命令的工具(图片来自网络)","attributes":{},"skip":false,"key":"5.3.2.2"},{"backlink":"guide/using-kubectl.html#fig5.3.2.3","level":"5.3.2","list_caption":"Figure: 增强的kubectl命令","alt":"增强的kubectl命令","nro":112,"url":"../images/supercharged-kubectl.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"增强的kubectl命令","attributes":{},"skip":false,"key":"5.3.2.3"},{"backlink":"guide/using-kubectl.html#fig5.3.2.4","level":"5.3.2","list_caption":"Figure: kube-shell页面","alt":"kube-shell页面","nro":113,"url":"../images/kube-shell.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kube-shell页面","attributes":{},"skip":false,"key":"5.3.2.4"},{"backlink":"guide/ip-masq-agent.html#fig5.4.5.1","level":"5.4.5","list_caption":"Figure: IP伪装代理示意图","alt":"IP伪装代理示意图","nro":114,"url":"../images/ip-masq.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"IP伪装代理示意图","attributes":{},"skip":false,"key":"5.4.5.1"},{"backlink":"guide/auth-with-kubeconfig-or-token.html#fig5.4.6.1","level":"5.4.6","list_caption":"Figure: kubeconfig文件","alt":"kubeconfig文件","nro":115,"url":"../images/brand-kubeconfig-yaml.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubeconfig文件","attributes":{},"skip":false,"key":"5.4.6.1"},{"backlink":"guide/authentication.html#fig5.4.7.1","level":"5.4.7","list_caption":"Figure: Kubernetes OpenID Connect Flow","alt":"Kubernetes OpenID Connect Flow","nro":116,"url":"../images/kubernetes-oidc-login.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes OpenID Connect Flow","attributes":{},"skip":false,"key":"5.4.7.1"},{"backlink":"guide/kubernetes-desktop-client.html#fig5.5.6.1","level":"5.5.6","list_caption":"Figure: Lens Kubernetes IDE 界面","alt":"Lens Kubernetes IDE 界面","nro":117,"url":"../images/lens.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Lens Kubernetes IDE 界面","attributes":{},"skip":false,"key":"5.5.6.1"},{"backlink":"guide/kubernator-kubernetes-ui.html#fig5.5.7.1","level":"5.5.7","list_caption":"Figure: Kubernator catalog 页面","alt":"Kubernator catalog 页面","nro":118,"url":"../images/kubernator-catalog.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernator catalog 页面","attributes":{},"skip":false,"key":"5.5.7.1"},{"backlink":"guide/kubernator-kubernetes-ui.html#fig5.5.7.2","level":"5.5.7","list_caption":"Figure: Kubernator rbac 页面","alt":"Kubernator rbac 页面","nro":119,"url":"../images/kubernator-rbac.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernator rbac 页面","attributes":{},"skip":false,"key":"5.5.7.2"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.1","level":"5.6.1","list_caption":"Figure: 流程图","alt":"流程图","nro":120,"url":"../images/how-to-use-kubernetes-with-istio.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"流程图","attributes":{},"skip":false,"key":"5.6.1.1"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.2","level":"5.6.1","list_caption":"Figure: API","alt":"API","nro":121,"url":"../images/k8s-app-monitor-test-api-doc.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"API","attributes":{},"skip":false,"key":"5.6.1.2"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.3","level":"5.6.1","list_caption":"Figure: wercker构建页面","alt":"wercker构建页面","nro":122,"url":"../images/k8s-app-monitor-agent-wercker.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"wercker构建页面","attributes":{},"skip":false,"key":"5.6.1.3"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.4","level":"5.6.1","list_caption":"Figure: 图表","alt":"图表","nro":123,"url":"../images/k8s-app-monitor-agent.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"图表","attributes":{},"skip":false,"key":"5.6.1.4"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.5","level":"5.6.1","list_caption":"Figure: Grafana页面","alt":"Grafana页面","nro":124,"url":"../images/k8s-app-monitor-istio-grafana.png","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Grafana页面","attributes":{},"skip":false,"key":"5.6.1.5"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.6","level":"5.6.1","list_caption":"Figure: servicegraph 页面","alt":"servicegraph 页面","nro":125,"url":"../images/k8s-app-monitor-istio-servicegraph-dotviz.png","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"servicegraph 页面","attributes":{},"skip":false,"key":"5.6.1.6"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.7","level":"5.6.1","list_caption":"Figure: Zipkin页面","alt":"Zipkin页面","nro":126,"url":"../images/k8s-app-monitor-istio-zipkin.png","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Zipkin页面","attributes":{},"skip":false,"key":"5.6.1.7"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig5.6.2.1","level":"5.6.2","list_caption":"Figure: 将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","alt":"将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","nro":127,"url":"../images/migrating-monolith-to-kubernetes.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","attributes":{},"skip":false,"key":"5.6.2.1"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig5.6.2.2","level":"5.6.2","list_caption":"Figure: spark on yarn with kubernetes","alt":"spark on yarn with kubernetes","nro":128,"url":"../images/spark-on-yarn-with-kubernetes.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"spark on yarn with kubernetes","attributes":{},"skip":false,"key":"5.6.2.2"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig5.6.2.3","level":"5.6.2","list_caption":"Figure: Terms","alt":"Terms","nro":129,"url":"../images/terms-in-kubernetes-app-deployment.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Terms","attributes":{},"skip":false,"key":"5.6.2.3"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig5.6.2.4","level":"5.6.2","list_caption":"Figure: 分解步骤解析","alt":"分解步骤解析","nro":130,"url":"../images/migrating-hadoop-yarn-to-kubernetes.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"分解步骤解析","attributes":{},"skip":false,"key":"5.6.2.4"},{"backlink":"practice/node-installation.html#fig6.2.7.1","level":"6.2.7","list_caption":"Figure: nginx欢迎页面","alt":"nginx欢迎页面","nro":131,"url":"../images/kubernetes-installation-test-nginx.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"nginx欢迎页面","attributes":{},"skip":false,"key":"6.2.7.1"},{"backlink":"practice/dashboard-addon-installation.html#fig6.2.9.1","level":"6.2.9","list_caption":"Figure: kubernetes dashboard","alt":"kubernetes dashboard","nro":132,"url":"../images/kubernetes-dashboard-raw.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes dashboard","attributes":{},"skip":false,"key":"6.2.9.1"},{"backlink":"practice/dashboard-addon-installation.html#fig6.2.9.2","level":"6.2.9","list_caption":"Figure: V1.6.3版本的dashboard界面","alt":"V1.6.3版本的dashboard界面","nro":133,"url":"../images/dashboard-v163.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"V1.6.3版本的dashboard界面","attributes":{},"skip":false,"key":"6.2.9.2"},{"backlink":"practice/dashboard-addon-installation.html#fig6.2.9.3","level":"6.2.9","list_caption":"Figure: pod无法正常启动","alt":"pod无法正常启动","nro":134,"url":"../images/dashboard-addon-installation001.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"pod无法正常启动","attributes":{},"skip":false,"key":"6.2.9.3"},{"backlink":"practice/heapster-addon-installation.html#fig6.2.10.1","level":"6.2.10","list_caption":"Figure: dashboard-heapster","alt":"dashboard-heapster","nro":135,"url":"../images/kubernetes-dashboard-with-heapster.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"dashboard-heapster","attributes":{},"skip":false,"key":"6.2.10.1"},{"backlink":"practice/heapster-addon-installation.html#fig6.2.10.2","level":"6.2.10","list_caption":"Figure: grafana","alt":"grafana","nro":136,"url":"../images/kubernetes-heapster-grafana.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"grafana","attributes":{},"skip":false,"key":"6.2.10.2"},{"backlink":"practice/heapster-addon-installation.html#fig6.2.10.3","level":"6.2.10","list_caption":"Figure: Influxdb 页面","alt":"Influxdb 页面","nro":137,"url":"../images/kubernetes-influxdb-heapster.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Influxdb 页面","attributes":{},"skip":false,"key":"6.2.10.3"},{"backlink":"practice/heapster-addon-installation.html#fig6.2.10.4","level":"6.2.10","list_caption":"Figure: 修改grafana模板","alt":"修改grafana模板","nro":138,"url":"../images/grafana-dashboard-setting.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"修改grafana模板","attributes":{},"skip":false,"key":"6.2.10.4"},{"backlink":"practice/efk-addon-installation.html#fig6.2.11.1","level":"6.2.11","list_caption":"Figure: es-setting","alt":"es-setting","nro":139,"url":"../images/es-setting.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"es-setting","attributes":{},"skip":false,"key":"6.2.11.1"},{"backlink":"practice/efk-addon-installation.html#fig6.2.11.2","level":"6.2.11","list_caption":"Figure: es-home","alt":"es-home","nro":140,"url":"../images/kubernetes-efk-kibana.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"es-home","attributes":{},"skip":false,"key":"6.2.11.2"},{"backlink":"practice/traefik-ingress-installation.html#fig6.4.1.1","level":"6.4.1","list_caption":"Figure: Terafik dashboard","alt":"Terafik dashboard","nro":141,"url":"../images/traefik-dashboard.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Terafik dashboard","attributes":{},"skip":false,"key":"6.4.1.1"},{"backlink":"practice/traefik-ingress-installation.html#fig6.4.1.2","level":"6.4.1","list_caption":"Figure: Nginx 页面","alt":"Nginx 页面","nro":142,"url":"../images/traefik-nginx.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Nginx 页面","attributes":{},"skip":false,"key":"6.4.1.2"},{"backlink":"practice/traefik-ingress-installation.html#fig6.4.1.3","level":"6.4.1","list_caption":"Figure: Guestbook 页面","alt":"Guestbook 页面","nro":143,"url":"../images/traefik-guestbook.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Guestbook 页面","attributes":{},"skip":false,"key":"6.4.1.3"},{"backlink":"practice/distributed-load-test.html#fig6.4.2.1","level":"6.4.2","list_caption":"Figure: 使用 dashboard 来扩容","alt":"使用 dashboard 来扩容","nro":144,"url":"../images/dashbaord-scale.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"使用 dashboard 来扩容","attributes":{},"skip":false,"key":"6.4.2.1"},{"backlink":"practice/distributed-load-test.html#fig6.4.2.2","level":"6.4.2","list_caption":"Figure: Traefik的UI","alt":"Traefik的UI","nro":145,"url":"../images/traefik-dashboard-locust.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Traefik的UI","attributes":{},"skip":false,"key":"6.4.2.2"},{"backlink":"practice/distributed-load-test.html#fig6.4.2.3","level":"6.4.2","list_caption":"Figure: Locust启动界面","alt":"Locust启动界面","nro":146,"url":"../images/locust-start-swarming.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Locust启动界面","attributes":{},"skip":false,"key":"6.4.2.3"},{"backlink":"practice/distributed-load-test.html#fig6.4.2.4","level":"6.4.2","list_caption":"Figure: Dashboard查看页面","alt":"Dashboard查看页面","nro":147,"url":"../images/sample-webapp-rc.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Dashboard查看页面","attributes":{},"skip":false,"key":"6.4.2.4"},{"backlink":"practice/distributed-load-test.html#fig6.4.2.5","level":"6.4.2","list_caption":"Figure: Locust测试结果页面","alt":"Locust测试结果页面","nro":148,"url":"../images/locust-dashboard.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Locust测试结果页面","attributes":{},"skip":false,"key":"6.4.2.5"},{"backlink":"practice/network-and-cluster-perfermance-test.html#fig6.4.3.1","level":"6.4.3","list_caption":"Figure: Kubernetes dashboard","alt":"Kubernetes dashboard","nro":149,"url":"../images/kubenetes-e2e-test.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes dashboard","attributes":{},"skip":false,"key":"6.4.3.1"},{"backlink":"practice/network-and-cluster-perfermance-test.html#fig6.4.3.2","level":"6.4.3","list_caption":"Figure: locust测试页面","alt":"locust测试页面","nro":150,"url":"../images/kubernetes-locust-test.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"locust测试页面","attributes":{},"skip":false,"key":"6.4.3.2"},{"backlink":"practice/edge-node-configuration.html#fig6.4.4.1","level":"6.4.4","list_caption":"Figure: 边缘节点架构","alt":"边缘节点架构","nro":151,"url":"../images/kubernetes-edge-node-architecture.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"边缘节点架构","attributes":{},"skip":false,"key":"6.4.4.1"},{"backlink":"practice/edge-node-configuration.html#fig6.4.4.2","level":"6.4.4","list_caption":"Figure: 使用域名来访问Kubernetes中的服务","alt":"使用域名来访问Kubernetes中的服务","nro":152,"url":"../images/accessing-kubernetes-services-with-dns-name.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"使用域名来访问Kubernetes中的服务","attributes":{},"skip":false,"key":"6.4.4.2"},{"backlink":"practice/configuring-dns.html#fig6.4.6.1.1","level":"6.4.6.1","list_caption":"Figure: DNS lookup flow","alt":"DNS lookup flow","nro":153,"url":"https://d33wubrfki0l68.cloudfront.net/340889cb80e81dcd19a16bc34697a7907e2b229a/24ad0/docs/tasks/administer-cluster/dns-custom-nameservers/dns.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"DNS lookup flow","attributes":{},"skip":false,"key":"6.4.6.1.1"},{"backlink":"practice/master-ha.html#fig6.5.1.1","level":"6.5.1","list_caption":"Figure: Master HA架构图","alt":"Master HA架构图","nro":154,"url":"../images/master-ha.JPG","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Master HA架构图","attributes":{},"skip":false,"key":"6.5.1.1"},{"backlink":"practice/app-log-collection.html#fig6.5.3.1","level":"6.5.3","list_caption":"Figure: filebeat日志收集架构图","alt":"filebeat日志收集架构图","nro":155,"url":"../images/filebeat-log-collector.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"filebeat日志收集架构图","attributes":{},"skip":false,"key":"6.5.3.1"},{"backlink":"practice/app-log-collection.html#fig6.5.3.2","level":"6.5.3","list_caption":"Figure: Kibana页面","alt":"Kibana页面","nro":156,"url":"../images/filebeat-docker-test.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kibana页面","attributes":{},"skip":false,"key":"6.5.3.2"},{"backlink":"practice/app-log-collection.html#fig6.5.3.3","level":"6.5.3","list_caption":"Figure: filebeat收集的日志详细信息","alt":"filebeat收集的日志详细信息","nro":157,"url":"../images/kubernetes-filebeat-detail.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"filebeat收集的日志详细信息","attributes":{},"skip":false,"key":"6.5.3.3"},{"backlink":"practice/monitor.html#fig6.5.5.1","level":"6.5.5","list_caption":"Figure: Kubernetes集群中的监控","alt":"Kubernetes集群中的监控","nro":158,"url":"../images/monitoring-in-kubernetes.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes集群中的监控","attributes":{},"skip":false,"key":"6.5.5.1"},{"backlink":"practice/monitor.html#fig6.5.5.2","level":"6.5.5","list_caption":"Figure: kubernetes的容器命名规则示意图","alt":"kubernetes的容器命名规则示意图","nro":159,"url":"../images/kubernetes-container-naming-rule.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes的容器命名规则示意图","attributes":{},"skip":false,"key":"6.5.5.2"},{"backlink":"practice/monitor.html#fig6.5.5.3","level":"6.5.5","list_caption":"Figure: Heapster架构图(改进版)","alt":"Heapster架构图(改进版)","nro":160,"url":"../images/kubernetes-heapster-monitoring.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Heapster架构图(改进版)","attributes":{},"skip":false,"key":"6.5.5.3"},{"backlink":"practice/monitor.html#fig6.5.5.4","level":"6.5.5","list_caption":"Figure: 应用监控架构图","alt":"应用监控架构图","nro":161,"url":"../images/kubernetes-app-monitoring.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"应用监控架构图","attributes":{},"skip":false,"key":"6.5.5.4"},{"backlink":"practice/monitor.html#fig6.5.5.5","level":"6.5.5","list_caption":"Figure: 应用拓扑图","alt":"应用拓扑图","nro":162,"url":"../images/weave-scope-service-topology.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"应用拓扑图","attributes":{},"skip":false,"key":"6.5.5.5"},{"backlink":"practice/data-persistence-problem.html#fig6.5.6.1","level":"6.5.6","list_caption":"Figure: 日志持久化收集解决方案示意图","alt":"日志持久化收集解决方案示意图","nro":163,"url":"../images/log-persistence-logstash.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"日志持久化收集解决方案示意图","attributes":{},"skip":false,"key":"6.5.6.1"},{"backlink":"practice/storage-for-containers-using-glusterfs-with-openshift.html#fig6.6.1.3.1","level":"6.6.1.3","list_caption":"Figure: 创建存储","alt":"创建存储","nro":164,"url":"../images/create-gluster-storage.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"创建存储","attributes":{},"skip":false,"key":"6.6.1.3.1"},{"backlink":"practice/storage-for-containers-using-glusterfs-with-openshift.html#fig6.6.1.3.2","level":"6.6.1.3","list_caption":"Figure: 容器存储","alt":"容器存储","nro":165,"url":"../images/container-storage.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"容器存储","attributes":{},"skip":false,"key":"6.6.1.3.2"},{"backlink":"practice/openebs.html#fig6.6.4.1","level":"6.6.4","list_caption":"Figure: OpenEBS 集群数据平面(图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md)","alt":"OpenEBS 集群数据平面(图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md)","nro":166,"url":"../images/OpenEBS-Data-Plane.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenEBS 集群数据平面(图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md)","attributes":{},"skip":false,"key":"6.6.4.1"},{"backlink":"practice/openebs.html#fig6.6.4.2","level":"6.6.4","list_caption":"Figure: OpenEBS 集群的控制平面 (图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md)","alt":"OpenEBS 集群的控制平面 (图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md)","nro":167,"url":"../images/OpenEBS-Control-Plane.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenEBS 集群的控制平面 (图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md)","attributes":{},"skip":false,"key":"6.6.4.2"},{"backlink":"practice/using-openebs-for-persistent-storage.html#fig6.6.4.1.1","level":"6.6.4.1","list_caption":"Figure: Kubernetes iSCSI架构","alt":"Kubernetes iSCSI架构","nro":168,"url":"../images/iscsi-on-kubernetes.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes iSCSI架构","attributes":{},"skip":false,"key":"6.6.4.1.1"},{"backlink":"practice/using-heapster-to-get-object-metrics.html#fig6.7.1.1.1","level":"6.7.1.1","list_caption":"Figure: Heapster架构图","alt":"Heapster架构图","nro":169,"url":"../images/heapster-architecture.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Heapster架构图","attributes":{},"skip":false,"key":"6.7.1.1.1"},{"backlink":"practice/prometheus.html#fig6.7.2.1","level":"6.7.2","list_caption":"Figure: Prometheus 架构图","alt":"Prometheus 架构图","nro":170,"url":"../images/006tNbRwly1fwcgsn11fej311j0mjadw.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Prometheus 架构图","attributes":{},"skip":false,"key":"6.7.2.1"},{"backlink":"practice/using-prometheus-to-monitor-kuberentes-cluster.html#fig6.7.2.1.1","level":"6.7.2.1","list_caption":"Figure: Grafana页面","alt":"Grafana页面","nro":171,"url":"../images/kubernetes-prometheus-monitoring.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Grafana页面","attributes":{},"skip":false,"key":"6.7.2.1.1"},{"backlink":"practice/promql.html#fig6.7.2.2.1","level":"6.7.2.2","list_caption":"Figure: Prometheus 的查询页面","alt":"Prometheus 的查询页面","nro":172,"url":"../images/006tNbRwly1fwcl7v28rhj30xl0onadv.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Prometheus 的查询页面","attributes":{},"skip":false,"key":"6.7.2.2.1"},{"backlink":"practice/opentracing.html#fig6.8.1.1","level":"6.8.1","list_caption":"Figure: Jaeger UI","alt":"Jaeger UI","nro":173,"url":"../images/006tNbRwly1fwjg48fh7xj31kw0wedrg.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Jaeger UI","attributes":{},"skip":false,"key":"6.8.1.1"},{"backlink":"practice/opentracing.html#fig6.8.1.2","level":"6.8.1","list_caption":"Figure: Chrome Inspector","alt":"Chrome Inspector","nro":174,"url":"../images/006tNbRwly1fwjkfbvfluj30y70hf0y9.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Chrome Inspector","attributes":{},"skip":false,"key":"6.8.1.2"},{"backlink":"practice/helm.html#fig6.9.1.1","level":"6.9.1","list_caption":"Figure: Helm 架构图(来自 IBM Developer Blog)","alt":"Helm 架构图(来自 IBM Developer Blog)","nro":175,"url":"../images/helm-chart.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Helm 架构图(来自 IBM Developer Blog)","attributes":{},"skip":false,"key":"6.9.1.1"},{"backlink":"practice/create-private-charts-repo.html#fig6.9.2.1","level":"6.9.2","list_caption":"Figure: Helm monocular界面","alt":"Helm monocular界面","nro":176,"url":"../images/helm-monocular-jimmysong.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Helm monocular界面","attributes":{},"skip":false,"key":"6.9.2.1"},{"backlink":"practice/ci-cd.html#fig6.10.1","level":"6.10","list_caption":"Figure: Kubernetes 改变了应用的基础架构","alt":"Kubernetes 改变了应用的基础架构","nro":177,"url":"../images/00704eQkgy1fsayashxz3j31c00w6aed.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 改变了应用的基础架构","attributes":{},"skip":false,"key":"6.10.1"},{"backlink":"practice/ci-cd.html#fig6.10.2","level":"6.10","list_caption":"Figure: Kubernetes 中的 CI/CD","alt":"Kubernetes 中的 CI/CD","nro":178,"url":"../images/00704eQkgy1fsayfzk3ezj31bu0tkdky.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 中的 CI/CD","attributes":{},"skip":false,"key":"6.10.2"},{"backlink":"practice/ci-cd.html#fig6.10.3","level":"6.10","list_caption":"Figure: Kubernetes 中的 GitOps 流程示意图","alt":"Kubernetes 中的 GitOps 流程示意图","nro":179,"url":"../images/gitops.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 中的 GitOps 流程示意图","attributes":{},"skip":false,"key":"6.10.3"},{"backlink":"practice/ci-cd.html#fig6.10.4","level":"6.10","list_caption":"Figure: 云原生工作负载","alt":"云原生工作负载","nro":180,"url":"../images/00704eQkgy1fsayrk6vppj31bu0w0gsd.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生工作负载","attributes":{},"skip":false,"key":"6.10.4"},{"backlink":"practice/ci-cd.html#fig6.10.5","level":"6.10","list_caption":"Figure: 云原生工作负载映射到 Kuberentes 原语","alt":"云原生工作负载映射到 Kuberentes 原语","nro":181,"url":"../images/00704eQkgy1fsaytbabxgj31c00w2n4r.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生工作负载映射到 Kuberentes 原语","attributes":{},"skip":false,"key":"6.10.5"},{"backlink":"practice/jenkins-ci-cd.html#fig6.10.1.1","level":"6.10.1","list_caption":"Figure: 基于 Jenkins 的持续集成与发布","alt":"基于 Jenkins 的持续集成与发布","nro":182,"url":"../images/kubernetes-jenkins-ci-cd.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"基于 Jenkins 的持续集成与发布","attributes":{},"skip":false,"key":"6.10.1.1"},{"backlink":"practice/drone-ci-cd.html#fig6.10.2.1","level":"6.10.2","list_caption":"Figure: OAuth 注册","alt":"OAuth 注册","nro":183,"url":"../images/github-oauth-register.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OAuth 注册","attributes":{},"skip":false,"key":"6.10.2.1"},{"backlink":"practice/drone-ci-cd.html#fig6.10.2.2","level":"6.10.2","list_caption":"Figure: OAuth key","alt":"OAuth key","nro":184,"url":"../images/github-oauth-drone-key.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OAuth key","attributes":{},"skip":false,"key":"6.10.2.2"},{"backlink":"practice/drone-ci-cd.html#fig6.10.2.3","level":"6.10.2","list_caption":"Figure: Drone 登陆界面","alt":"Drone 登陆界面","nro":185,"url":"../images/drone-login-github.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Drone 登陆界面","attributes":{},"skip":false,"key":"6.10.2.3"},{"backlink":"practice/drone-ci-cd.html#fig6.10.2.4","level":"6.10.2","list_caption":"Figure: Github 启用 repo 设置","alt":"Github 启用 repo 设置","nro":186,"url":"../images/drone-github-active.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Github 启用 repo 设置","attributes":{},"skip":false,"key":"6.10.2.4"},{"backlink":"practice/drone-ci-cd.html#fig6.10.2.5","level":"6.10.2","list_caption":"Figure: Github 单个 repo 设置","alt":"Github 单个 repo 设置","nro":187,"url":"../images/drone-github-repo-setting.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Github 单个 repo 设置","attributes":{},"skip":false,"key":"6.10.2.5"},{"backlink":"practice/manually-upgrade.html#fig6.11.1.1","level":"6.11.1","list_caption":"Figure: Kubernetes零宕机时间升级建议","alt":"Kubernetes零宕机时间升级建议","nro":188,"url":"../images/zero-downtime-kubernetes-upgrade-tips.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes零宕机时间升级建议","attributes":{},"skip":false,"key":"6.11.1.1"},{"backlink":"practice/manually-upgrade.html#fig6.11.1.2","level":"6.11.1","list_caption":"Figure: Kuberentes API对象的版本演进","alt":"Kuberentes API对象的版本演进","nro":189,"url":"../images/kubernetes-apversions-changes.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kuberentes API对象的版本演进","attributes":{},"skip":false,"key":"6.11.1.2"},{"backlink":"practice/dashboard-upgrade.html#fig6.11.2.1","level":"6.11.2","list_caption":"Figure: 登陆界面","alt":"登陆界面","nro":190,"url":"../images/kubernetes-dashboard-1.7.1-login.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"登陆界面","attributes":{},"skip":false,"key":"6.11.2.1"},{"backlink":"practice/dashboard-upgrade.html#fig6.11.2.2","level":"6.11.2","list_caption":"Figure: Dashboard首页","alt":"Dashboard首页","nro":191,"url":"../images/kubernetes-dashboard-1.7.1-default-page.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Dashboard首页","attributes":{},"skip":false,"key":"6.11.2.2"},{"backlink":"practice/dashboard-upgrade.html#fig6.11.2.3","level":"6.11.2","list_caption":"Figure: Dashboard用户空间页面","alt":"Dashboard用户空间页面","nro":192,"url":"../images/kubernetes-dashboard-1.7.1-brand.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Dashboard用户空间页面","attributes":{},"skip":false,"key":"6.11.2.3"},{"backlink":"practice/dashboard-upgrade.html#fig6.11.2.4","level":"6.11.2","list_caption":"Figure: kubeconfig文件","alt":"kubeconfig文件","nro":193,"url":"../images/brand-kubeconfig-yaml.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubeconfig文件","attributes":{},"skip":false,"key":"6.11.2.4"},{"backlink":"practice/open-policy-agent.html#fig6.13.1.1","level":"6.13.1","list_caption":"Figure: OPA 原理图","alt":"OPA 原理图","nro":194,"url":"../images/opa-arch.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OPA 原理图","attributes":{},"skip":false,"key":"6.13.1.1"},{"backlink":"usecases/service-mesh.html#fig7.1.1","level":"7.1","list_caption":"Figure: 下一代异构微服务架构","alt":"下一代异构微服务架构","nro":195,"url":"../images/polyglot-microservices-serivce-mesh.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"下一代异构微服务架构","attributes":{},"skip":false,"key":"7.1.1"},{"backlink":"usecases/service-mesh.html#fig7.1.2","level":"7.1","list_caption":"Figure: Service Mesh 架构图","alt":"Service Mesh 架构图","nro":196,"url":"../images/serivce-mesh-control-plane.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Service Mesh 架构图","attributes":{},"skip":false,"key":"7.1.2"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.1","level":"7.2.1","list_caption":"Figure: 服务网格模型对比","alt":"服务网格模型对比","nro":197,"url":"../images/0069RVTdly1fuafvbnuc7j310a0oqdm9.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"服务网格模型对比","attributes":{},"skip":false,"key":"7.2.1.1"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.2","level":"7.2.1","list_caption":"Figure: 网状网络拓扑","alt":"网状网络拓扑","nro":198,"url":"../images/0069RVTdly1fuaie8jan8j310a0kitem.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"网状网络拓扑","attributes":{},"skip":false,"key":"7.2.1.2"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.3","level":"7.2.1","list_caption":"Figure: 服务网格架构图","alt":"服务网格架构图","nro":199,"url":"../images/0069RVTdly1fuail4d24jj31080rkgr7.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"服务网格架构图","attributes":{},"skip":false,"key":"7.2.1.3"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.4","level":"7.2.1","list_caption":"Figure: Istio Mixer","alt":"Istio Mixer","nro":200,"url":"../images/0069RVTdly1fuam4ln45jj30yu0o6wkc.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio Mixer","attributes":{},"skip":false,"key":"7.2.1.4"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.5","level":"7.2.1","list_caption":"Figure: Istio架构图","alt":"Istio架构图","nro":201,"url":"../images/0069RVTdly1fuamvq97cuj30yu0wg7cr.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio架构图","attributes":{},"skip":false,"key":"7.2.1.5"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.6","level":"7.2.1","list_caption":"Figure: OSI模型","alt":"OSI模型","nro":202,"url":"../images/0069RVTdly1fuanez4qbtj30v4183n7p.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OSI模型","attributes":{},"skip":false,"key":"7.2.1.6"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.7","level":"7.2.1","list_caption":"Figure: 在L5解耦","alt":"在L5解耦","nro":203,"url":"../images/006tNbRwly1fubfiiryirj30w20ayjui.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"在L5解耦","attributes":{},"skip":false,"key":"7.2.1.7"},{"backlink":"usecases/comparing-service-mesh-technologies.html#fig7.2.2.1","level":"7.2.2","list_caption":"Figure: 客户端库","alt":"客户端库","nro":204,"url":"../images/006tNbRwly1fubnx0q9bpj30vq0pq465.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"客户端库","attributes":{},"skip":false,"key":"7.2.2.1"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.1","level":"7.2.4","list_caption":"Figure: Service Mesh架构图","alt":"Service Mesh架构图","nro":205,"url":"../images/006tNbRwly1fubs6ts3sgj30vo0osdnj.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Service Mesh架构图","attributes":{},"skip":false,"key":"7.2.4.1"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.2","level":"7.2.4","list_caption":"Figure: Ingress或边缘代理架构图","alt":"Ingress或边缘代理架构图","nro":206,"url":"../images/006tNbRwly1fubsk4v16hj30vo0bq75z.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Ingress或边缘代理架构图","attributes":{},"skip":false,"key":"7.2.4.2"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.3","level":"7.2.4","list_caption":"Figure: 路由器网格架构图","alt":"路由器网格架构图","nro":207,"url":"../images/006tNbRwly1fubsxrph3dj30vq0duq53.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"路由器网格架构图","attributes":{},"skip":false,"key":"7.2.4.3"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.4","level":"7.2.4","list_caption":"Figure: Proxy per Node架构图","alt":"Proxy per Node架构图","nro":208,"url":"../images/006tNbRwly1fubt5a97h7j30vq0bcq5p.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Proxy per Node架构图","attributes":{},"skip":false,"key":"7.2.4.4"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.5","level":"7.2.4","list_caption":"Figure: Sidecar代理/Fabric模型架构图","alt":"Sidecar代理/Fabric模型架构图","nro":209,"url":"../images/006tNbRwly1fubvi0dnhlj30vo0ekwhx.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Sidecar代理/Fabric模型架构图","attributes":{},"skip":false,"key":"7.2.4.5"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.6","level":"7.2.4","list_caption":"Figure: Sidecar代理/控制平面架构图","alt":"Sidecar代理/控制平面架构图","nro":210,"url":"../images/006tNbRwly1fubvr83wvgj30vq0mmdip.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Sidecar代理/控制平面架构图","attributes":{},"skip":false,"key":"7.2.4.6"},{"backlink":"usecases/service-mesh-customization-and-integration.html#fig7.2.5.1","level":"7.2.5","list_caption":"Figure: nginMesh架构图","alt":"nginMesh架构图","nro":211,"url":"../images/006tNbRwly1fucp8yralaj30vu0sijx8.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"nginMesh架构图","attributes":{},"skip":false,"key":"7.2.5.1"},{"backlink":"usecases/service-mesh-customization-and-integration.html#fig7.2.5.2","level":"7.2.5","list_caption":"Figure: SOFAMesh","alt":"SOFAMesh","nro":212,"url":"../images/mosn-with-service-mesh.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"SOFAMesh","attributes":{},"skip":false,"key":"7.2.5.2"},{"backlink":"usecases/istio.html#fig7.3.1","level":"7.3","list_caption":"Figure: Istio的mindmap","alt":"Istio的mindmap","nro":213,"url":"../images/istio-mindmap.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio的mindmap","attributes":{},"skip":false,"key":"7.3.1"},{"backlink":"usecases/istio.html#fig7.3.2","level":"7.3","list_caption":"Figure: Istio架构图","alt":"Istio架构图","nro":214,"url":"../images/istio-mesh-arch.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio架构图","attributes":{},"skip":false,"key":"7.3.2"},{"backlink":"usecases/istio-tutorials-collection.html#fig7.3.4.1","level":"7.3.4","list_caption":"Figure: Tetrate Istio 基础教程","alt":"Tetrate Istio 基础教程","nro":215,"url":"../images/tetrate-istio-fundamentals.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Tetrate Istio 基础教程","attributes":{},"skip":false,"key":"7.3.4.1"},{"backlink":"usecases/istio-tutorials-collection.html#fig7.3.4.2","level":"7.3.4","list_caption":"Figure: katacoda","alt":"katacoda","nro":216,"url":"../images/006tNc79gy1ftwe77v4u5j31kw0ziwtw.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"katacoda","attributes":{},"skip":false,"key":"7.3.4.2"},{"backlink":"usecases/istio-tutorials-collection.html#fig7.3.4.3","level":"7.3.4","list_caption":"Figure: weavescope","alt":"weavescope","nro":217,"url":"../images/006tNc79gy1ftwhtmzhfej31kw0ziww1.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"weavescope","attributes":{},"skip":false,"key":"7.3.4.3"},{"backlink":"usecases/istio-tutorials-collection.html#fig7.3.4.4","level":"7.3.4","list_caption":"Figure: weavescope","alt":"weavescope","nro":218,"url":"../images/006tNc79gy1ftwhvtu1vxj31kw0zitvc.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"weavescope","attributes":{},"skip":false,"key":"7.3.4.4"},{"backlink":"usecases/istio-tutorials-collection.html#fig7.3.4.5","level":"7.3.4","list_caption":"Figure: Red Hat","alt":"Red Hat","nro":219,"url":"../images/006tNc79gy1ftwiolw1tyj31kw0zib29.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Red Hat","attributes":{},"skip":false,"key":"7.3.4.5"},{"backlink":"usecases/istio-tutorials-collection.html#fig7.3.4.6","level":"7.3.4","list_caption":"Figure: Red Hat developers","alt":"Red Hat developers","nro":220,"url":"../images/006tNc79gy1ftwjyxiw1pj31kw0zi4qp.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Red Hat developers","attributes":{},"skip":false,"key":"7.3.4.6"},{"backlink":"usecases/istio-tutorials-collection.html#fig7.3.4.7","level":"7.3.4","list_caption":"Figure: IBM developerWorks","alt":"IBM developerWorks","nro":221,"url":"../images/006tNc79gy1ftweryj0zrj31kw0zix6q.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"IBM developerWorks","attributes":{},"skip":false,"key":"7.3.4.7"},{"backlink":"usecases/istio-tutorials-collection.html#fig7.3.4.8","level":"7.3.4","list_caption":"Figure: IBM developers","alt":"IBM developers","nro":222,"url":"../images/006tNc79gy1ftwesjg1e2j31kw0s8woq.jpg","index":8,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"IBM developers","attributes":{},"skip":false,"key":"7.3.4.8"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.5.1","level":"7.3.5","list_caption":"Figure: Sidecar 模式示意图","alt":"Sidecar 模式示意图","nro":223,"url":"../images/sidecar-pattern.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Sidecar 模式示意图","attributes":{},"skip":false,"key":"7.3.5.1"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.5.2","level":"7.3.5","list_caption":"Figure: Sidecar 流量劫持示意图","alt":"Sidecar 流量劫持示意图","nro":224,"url":"../images/envoy-sidecar-traffic-interception-jimmysong-blog.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Sidecar 流量劫持示意图","attributes":{},"skip":false,"key":"7.3.5.2"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.5.3","level":"7.3.5","list_caption":"Figure: iptables 调用链","alt":"iptables 调用链","nro":225,"url":"../images/iptables.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"iptables 调用链","attributes":{},"skip":false,"key":"7.3.5.3"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.5.4","level":"7.3.5","list_caption":"Figure: hook-connect 原理示意图","alt":"hook-connect 原理示意图","nro":226,"url":"../images/hook-connect.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"hook-connect 原理示意图","attributes":{},"skip":false,"key":"7.3.5.4"},{"backlink":"usecases/envoy-sidecar-routing-of-istio-service-mesh-deep-dive.html#fig7.3.6.1","level":"7.3.6","list_caption":"Figure: Bookinfo 示例","alt":"Bookinfo 示例","nro":227,"url":"../images/006tNbRwgy1fvlwjd3302j31bo0ro0x5.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Bookinfo 示例","attributes":{},"skip":false,"key":"7.3.6.1"},{"backlink":"usecases/how-to-integrate-istio-with-vm.html#fig7.3.7.1","level":"7.3.7","list_caption":"Figure: Istio 中的服务注册发现模型","alt":"Istio 中的服务注册发现模型","nro":228,"url":"https://tva1.sinaimg.cn/large/0081Kckwly1gktf3b63j0j30p30ehwf5.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio 中的服务注册发现模型","attributes":{},"skip":false,"key":"7.3.7.1"},{"backlink":"usecases/how-to-integrate-istio-with-vm.html#fig7.3.7.2","level":"7.3.7","list_caption":"Figure: Bookinfo 示例中的流量示意图","alt":"Bookinfo 示例中的流量示意图","nro":229,"url":"../images/istio-bookinfo-vm-traffic.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Bookinfo 示例中的流量示意图","attributes":{},"skip":false,"key":"7.3.7.2"},{"backlink":"usecases/istio-vm-support.html#fig7.3.8.1","level":"7.3.8","list_caption":"Figure: 云原生应用的三个阶段","alt":"云原生应用的三个阶段","nro":230,"url":"../images/0081Kckwly1gm0d6t775lj31s80k8go8.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生应用的三个阶段","attributes":{},"skip":false,"key":"7.3.8.1"},{"backlink":"usecases/istio-vm-support.html#fig7.3.8.2","level":"7.3.8","list_caption":"Figure: 图一:从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","alt":"图一:从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","nro":231,"url":"../images/0081Kckwly1gm0d6rogojj30u00yhdil.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"图一:从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","attributes":{},"skip":false,"key":"7.3.8.2"},{"backlink":"usecases/istio-vm-support.html#fig7.3.8.3","level":"7.3.8","list_caption":"Figure: 图二:通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","alt":"图二:通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","nro":232,"url":"../images/0081Kckwly1gm0d6qx2o0j30sq0v440v.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"图二:通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","attributes":{},"skip":false,"key":"7.3.8.3"},{"backlink":"usecases/istio-vm-support.html#fig7.3.8.4","level":"7.3.8","list_caption":"Figure: 图三:引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","alt":"图三:引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","nro":233,"url":"../images/0081Kckwly1gm0d6sgfpxj30oi0rsjt5.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"图三:引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","attributes":{},"skip":false,"key":"7.3.8.4"},{"backlink":"usecases/envoy.html#fig7.4.1","level":"7.4","list_caption":"Figure: 负载均衡器的特性以及拓扑类型","alt":"负载均衡器的特性以及拓扑类型","nro":234,"url":"../images/load-balancing-and-proxing.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"负载均衡器的特性以及拓扑类型","attributes":{},"skip":false,"key":"7.4.1"},{"backlink":"usecases/envoy-terminology.html#fig7.4.1.1","level":"7.4.1","list_caption":"Figure: Envoy proxy 架构图","alt":"Envoy proxy 架构图","nro":235,"url":"../images/envoy-arch.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Envoy proxy 架构图","attributes":{},"skip":false,"key":"7.4.1.1"},{"backlink":"usecases/envoy-front-proxy.html#fig7.4.2.1","level":"7.4.2","list_caption":"Figure: Front proxy 部署结构图(转自https://www.envoyproxy.io/docs/envoy/latest/start/sandboxes/front_proxy)","alt":"Front proxy 部署结构图(转自https://www.envoyproxy.io/docs/envoy/latest/start/sandboxes/front_proxy)","nro":236,"url":"../images/envoyproxy-docker-compose.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Front proxy 部署结构图(转自https://www.envoyproxy.io/docs/envoy/latest/start/sandboxes/front_proxy)","attributes":{},"skip":false,"key":"7.4.2.1"},{"backlink":"usecases/envoy-mesh-in-kubernetes-tutorial.html#fig7.4.3.1","level":"7.4.3","list_caption":"Figure: Envoy Mesh架构图","alt":"Envoy Mesh架构图","nro":237,"url":"../images/envoy-mesh-in-kubernetes.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Envoy Mesh架构图","attributes":{},"skip":false,"key":"7.4.3.1"},{"backlink":"usecases/microservices.html#fig8.2.1","level":"8.2","list_caption":"Figure: 微服务关注的部分","alt":"微服务关注的部分","nro":238,"url":"../images/microservices-concerns.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"微服务关注的部分","attributes":{},"skip":false,"key":"8.2.1"},{"backlink":"usecases/service-discovery-in-microservices.html#fig8.2.1.1","level":"8.2.1","list_caption":"Figure: 微服务中的服务发现","alt":"微服务中的服务发现","nro":239,"url":"../images/service-discovery-in-microservices.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"微服务中的服务发现","attributes":{},"skip":false,"key":"8.2.1.1"},{"backlink":"usecases/microservices-for-java-developers.html#fig8.2.2.1","level":"8.2.2","list_caption":"Figure: Spring技术栈","alt":"Spring技术栈","nro":240,"url":"../images/spring-stack.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Spring技术栈","attributes":{},"skip":false,"key":"8.2.2.1"},{"backlink":"usecases/microservices-for-java-developers.html#fig8.2.2.2","level":"8.2.2","list_caption":"Figure: Spring Boot的知识点","alt":"Spring Boot的知识点","nro":241,"url":"../images/spring-boot-note-spots.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Spring Boot的知识点","attributes":{},"skip":false,"key":"8.2.2.2"},{"backlink":"usecases/spark-on-kubernetes.html#fig8.3.1.1","level":"8.3.1","list_caption":"Figure: Spark on yarn with kubernetes","alt":"Spark on yarn with kubernetes","nro":242,"url":"../images/spark-on-yarn-with-kubernetes.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Spark on yarn with kubernetes","attributes":{},"skip":false,"key":"8.3.1.1"},{"backlink":"usecases/spark-on-kubernetes.html#fig8.3.1.2","level":"8.3.1","list_caption":"Figure: 在 kubernetes 上使用多种调度方式","alt":"在 kubernetes 上使用多种调度方式","nro":243,"url":"../images/spark-on-kubernetes-with-different-schedulers.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"在 kubernetes 上使用多种调度方式","attributes":{},"skip":false,"key":"8.3.1.2"},{"backlink":"usecases/spark-standalone-on-kubernetes.html#fig8.3.1.1.1","level":"8.3.1.1","list_caption":"Figure: spark master ui","alt":"spark master ui","nro":244,"url":"../images/spark-ui.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"spark master ui","attributes":{},"skip":false,"key":"8.3.1.1.1"},{"backlink":"usecases/spark-standalone-on-kubernetes.html#fig8.3.1.1.2","level":"8.3.1.1","list_caption":"Figure: zeppelin ui","alt":"zeppelin ui","nro":245,"url":"../images/zeppelin-ui.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"zeppelin ui","attributes":{},"skip":false,"key":"8.3.1.1.2"},{"backlink":"usecases/serverless.html#fig8.4.1","level":"8.4","list_caption":"Figure: Serverless Landscape","alt":"Serverless Landscape","nro":246,"url":"../images/006tNbRwly1fx0ie2kb90j31kw0ynha3.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Serverless Landscape","attributes":{},"skip":false,"key":"8.4.1"},{"backlink":"usecases/serverless.html#fig8.4.2","level":"8.4","list_caption":"Figure: 从物理机到函数计算","alt":"从物理机到函数计算","nro":247,"url":"../images/from-bare-metal-to-functions.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"从物理机到函数计算","attributes":{},"skip":false,"key":"8.4.2"},{"backlink":"usecases/serverless.html#fig8.4.3","level":"8.4","list_caption":"Figure: FaaS Landscape","alt":"FaaS Landscape","nro":248,"url":"../images/redpoint-faas-landscape.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"FaaS Landscape","attributes":{},"skip":false,"key":"8.4.3"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.1","level":"8.4.1","list_caption":"Figure: Serverless 在云原生技术中的地位","alt":"Serverless 在云原生技术中的地位","nro":249,"url":"../images/cloud-landscape-zh.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Serverless 在云原生技术中的地位","attributes":{},"skip":false,"key":"8.4.1.1"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.2","level":"8.4.1","list_caption":"Figure: 服务端软件的运行环境","alt":"服务端软件的运行环境","nro":250,"url":"../images/serverless-server-side-software.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"服务端软件的运行环境","attributes":{},"skip":false,"key":"8.4.1.2"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.3","level":"8.4.1","list_caption":"Figure: FaaS应用架构","alt":"FaaS应用架构","nro":251,"url":"../images/serverless-faas-platform.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"FaaS应用架构","attributes":{},"skip":false,"key":"8.4.1.3"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.4","level":"8.4.1","list_caption":"Figure: Serverless 中的函数定义","alt":"Serverless 中的函数定义","nro":252,"url":"../images/006y8mN6ly1g7ldey3l7gj31ti0mwta9.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Serverless 中的函数定义","attributes":{},"skip":false,"key":"8.4.1.4"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.5","level":"8.4.1","list_caption":"Figure: FaaS 中的函数","alt":"FaaS 中的函数","nro":253,"url":"../images/006y8mN6ly1g7ldhm7bxyj31040u0q5n.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"FaaS 中的函数","attributes":{},"skip":false,"key":"8.4.1.5"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.6","level":"8.4.1","list_caption":"Figure: 传统应用程序架构","alt":"传统应用程序架构","nro":254,"url":"../images/non-serverless-game-arch.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"传统应用程序架构","attributes":{},"skip":false,"key":"8.4.1.6"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.7","level":"8.4.1","list_caption":"Figure: Serverless架构","alt":"Serverless架构","nro":255,"url":"../images/serverless-game-arch.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Serverless架构","attributes":{},"skip":false,"key":"8.4.1.7"},{"backlink":"usecases/openfaas-quick-start.html#fig8.4.2.1.1","level":"8.4.2.1","list_caption":"Figure: OpenFaaS架构","alt":"OpenFaaS架构","nro":256,"url":"../images/openfaas-arch.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenFaaS架构","attributes":{},"skip":false,"key":"8.4.2.1.1"},{"backlink":"usecases/openfaas-quick-start.html#fig8.4.2.1.2","level":"8.4.2.1","list_caption":"Figure: OpenFaaS Prometheus","alt":"OpenFaaS Prometheus","nro":257,"url":"../images/openfaas-prometheus.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenFaaS Prometheus","attributes":{},"skip":false,"key":"8.4.2.1.2"},{"backlink":"usecases/openfaas-quick-start.html#fig8.4.2.1.3","level":"8.4.2.1","list_caption":"Figure: OpenFaas Grafana监控","alt":"OpenFaas Grafana监控","nro":258,"url":"../images/openfaas-grafana.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenFaas Grafana监控","attributes":{},"skip":false,"key":"8.4.2.1.3"},{"backlink":"usecases/openfaas-quick-start.html#fig8.4.2.1.4","level":"8.4.2.1","list_caption":"Figure: OpenFaas Dashboard","alt":"OpenFaas Dashboard","nro":259,"url":"../images/openfaas-deploy-a-function.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenFaas Dashboard","attributes":{},"skip":false,"key":"8.4.2.1.4"},{"backlink":"usecases/openfaas-quick-start.html#fig8.4.2.1.5","level":"8.4.2.1","list_caption":"Figure: NodeInfo执行结果","alt":"NodeInfo执行结果","nro":260,"url":"../images/openfaas-nodeinfo.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"NodeInfo执行结果","attributes":{},"skip":false,"key":"8.4.2.1.5"},{"backlink":"usecases/knative.html#fig8.4.3.1","level":"8.4.3","list_caption":"Figure: Knative logo","alt":"Knative logo","nro":261,"url":"https://tva1.sinaimg.cn/large/006y8mN6ly1g7pg0iwbzfj30d8080dfp.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Knative logo","attributes":{},"skip":false,"key":"8.4.3.1"},{"backlink":"usecases/knative.html#fig8.4.3.2","level":"8.4.3","list_caption":"Figure: Knative 受众(图片来自 knative.dev)","alt":"Knative 受众(图片来自 knative.dev)","nro":262,"url":"https://tva1.sinaimg.cn/large/006y8mN6ly1g7po5i7cgqj31ap0u075l.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Knative 受众(图片来自 knative.dev)","attributes":{},"skip":false,"key":"8.4.3.2"},{"backlink":"develop/sigs-and-working-group.html#fig9.2.1","level":"9.2","list_caption":"Figure: Kubernetes SIG","alt":"Kubernetes SIG","nro":263,"url":"../images/kubernetes-sigs.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes SIG","attributes":{},"skip":false,"key":"9.2.1"},{"backlink":"develop/testing.html#fig9.4.1","level":"9.4","list_caption":"Figure: test-infra架构图(图片来自官方GitHub)","alt":"test-infra架构图(图片来自官方GitHub)","nro":264,"url":"../images/kubernetes-test-architecture.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"test-infra架构图(图片来自官方GitHub)","attributes":{},"skip":false,"key":"9.4.1"},{"backlink":"develop/client-go-sample.html#fig9.5.1","level":"9.5","list_caption":"Figure: 使用kubernetes dashboard进行故障排查","alt":"使用kubernetes dashboard进行故障排查","nro":265,"url":"../images/kubernetes-client-go-sample-update.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"使用kubernetes dashboard进行故障排查","attributes":{},"skip":false,"key":"9.5.1"},{"backlink":"develop/client-go-informer-sourcecode-analyse.html#fig9.5.1.1","level":"9.5.1","list_caption":"Figure: client-go informer","alt":"client-go informer","nro":266,"url":"../images/client-go-informer.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"client-go informer","attributes":{},"skip":false,"key":"9.5.1.1"},{"backlink":"develop/client-go-informer-sourcecode-analyse.html#fig9.5.1.2","level":"9.5.1","list_caption":"Figure: image","alt":"image","nro":267,"url":"https://github.com/jianlongzhou/client-go-source-analysis/blob/main/deltaFIFO.png?raw=true","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"image","attributes":{},"skip":false,"key":"9.5.1.2"},{"backlink":"develop/client-go-informer-sourcecode-analyse.html#fig9.5.1.3","level":"9.5.1","list_caption":"Figure: 图片来源于网络","alt":"图片来源于网络","nro":268,"url":"https://user-images.githubusercontent.com/41672087/116666278-5981ca00-a9cd-11eb-9570-8ee6eb447d05.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"图片来源于网络","attributes":{},"skip":false,"key":"9.5.1.3"},{"backlink":"cloud-native/cncf.html#fig10.1.1","level":"10.1","list_caption":"Figure: CNCF landscape","alt":"CNCF landscape","nro":269,"url":"../images/006tNbRwly1fxmx633ymqj31dp0u0kjn.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF landscape","attributes":{},"skip":false,"key":"10.1.1"},{"backlink":"cloud-native/cncf.html#fig10.1.2","level":"10.1","list_caption":"Figure: CNCF项目成熟度级别","alt":"CNCF项目成熟度级别","nro":270,"url":"../images/cncf-graduation-criteria-v2.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF项目成熟度级别","attributes":{},"skip":false,"key":"10.1.2"},{"backlink":"cloud-native/cncf-charter.html#fig10.1.1.1","level":"10.1.1","list_caption":"Figure: CNCF 组织架构图","alt":"CNCF 组织架构图","nro":271,"url":"../images/cncf-org-arch.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF 组织架构图","attributes":{},"skip":false,"key":"10.1.1.1"},{"backlink":"cloud-native/cncf-charter.html#fig10.1.1.2","level":"10.1.1","list_caption":"Figure: 云原生的理想分层架构","alt":"云原生的理想分层架构","nro":272,"url":"../images/006tKfTcly1ft3zgjlisxj30n70ffjth.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生的理想分层架构","attributes":{},"skip":false,"key":"10.1.1.2"},{"backlink":"cloud-native/cncf-sandbox-criteria.html#fig10.1.3.1","level":"10.1.3","list_caption":"Figure: sandbox 流程","alt":"sandbox 流程","nro":273,"url":"../images/sandbox-process.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"sandbox 流程","attributes":{},"skip":false,"key":"10.1.3.1"},{"backlink":"cloud-native/cncf-project-governing.html#fig10.1.4.1","level":"10.1.4","list_caption":"Figure: CNCF 项目的成熟度分类","alt":"CNCF 项目的成熟度分类","nro":274,"url":"../images/cncf-graduation.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF 项目的成熟度分类","attributes":{},"skip":false,"key":"10.1.4.1"},{"backlink":"cloud-native/cncf-project-governing.html#fig10.1.4.2","level":"10.1.4","list_caption":"Figure: CNCF中的项目运作","alt":"CNCF中的项目运作","nro":275,"url":"../images/006tNc79ly1g1yz80ag98j31cs0n2gr7.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF中的项目运作","attributes":{},"skip":false,"key":"10.1.4.2"},{"backlink":"cloud-native/cncf-project-governing.html#fig10.1.4.3","level":"10.1.4","list_caption":"Figure: CNCF项目成熟度级别","alt":"CNCF项目成熟度级别","nro":276,"url":"../images/cncf-graduation-criteria-v2.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF项目成熟度级别","attributes":{},"skip":false,"key":"10.1.4.3"},{"backlink":"appendix/about-cka-candidate.html#fig10.2.2.1","level":"10.2.2","list_caption":"Figure: cka-question","alt":"cka-question","nro":277,"url":"../images/cka-question.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"cka-question","attributes":{},"skip":false,"key":"10.2.2.1"},{"backlink":"appendix/about-cka-candidate.html#fig10.2.2.2","level":"10.2.2","list_caption":"Figure: CKA mindmap","alt":"CKA mindmap","nro":278,"url":"../images/cka-mindmap.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CKA mindmap","attributes":{},"skip":false,"key":"10.2.2.2"},{"backlink":"appendix/material-share.html#fig11.3.1","level":"11.3","list_caption":"Figure: Kubernetes 资源图标示例","alt":"Kubernetes 资源图标示例","nro":279,"url":"../images/006tNc79ly1fzmnolp5ghj30z90u0gwf.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 资源图标示例","attributes":{},"skip":false,"key":"11.3.1"},{"backlink":"appendix/issues.html#fig11.6.1","level":"11.6","list_caption":"Figure: pvc-storage-limit","alt":"pvc-storage-limit","nro":280,"url":"../images/pvc-storage-limit.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"pvc-storage-limit","attributes":{},"skip":false,"key":"11.6.1"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.7.2.1","level":"11.7.2","list_caption":"Figure: Kubernetes 搜索趋势(来自 Google trends)","alt":"Kubernetes 搜索趋势(来自 Google trends)","nro":281,"url":"../images/006tNc79ly1fzne6y4f2ej31q60fedho.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 搜索趋势(来自 Google trends)","attributes":{},"skip":false,"key":"11.7.2.1"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.7.2.2","level":"11.7.2","list_caption":"Figure: Kubernetes 的百度指数","alt":"Kubernetes 的百度指数","nro":282,"url":"../images/006tNc79ly1fznegoocmvj31y00hmgon.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 的百度指数","attributes":{},"skip":false,"key":"11.7.2.2"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.7.2.3","level":"11.7.2","list_caption":"Figure: Istio 中的 CRD","alt":"Istio 中的 CRD","nro":283,"url":"../images/006tNc79ly1fzna87wmfij30u00zc4qp.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio 中的 CRD","attributes":{},"skip":false,"key":"11.7.2.3"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.7.2.4","level":"11.7.2","list_caption":"Figure: 2019 Q1 软件架构趋势 - 来自 InfoQ","alt":"2019 Q1 软件架构趋势 - 来自 InfoQ","nro":284,"url":"../images/006tNc79ly1fzor2k6f7wj313j0u0dl3.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"2019 Q1 软件架构趋势 - 来自 InfoQ","attributes":{},"skip":false,"key":"11.7.2.4"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.7.2.5","level":"11.7.2","list_caption":"Figure: ServiceMesher 社区 Logo","alt":"ServiceMesher 社区 Logo","nro":285,"url":"../images/006tNc79ly1fznadbp63qj31jt0beq9s.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"ServiceMesher 社区 Logo","attributes":{},"skip":false,"key":"11.7.2.5"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.7.2.6","level":"11.7.2","list_caption":"Figure: ServiceMesher 社区 2018 年活动一览","alt":"ServiceMesher 社区 2018 年活动一览","nro":286,"url":"../images/006tNc79ly1fzm9vs4o3aj31s00u0x6p.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"ServiceMesher 社区 2018 年活动一览","attributes":{},"skip":false,"key":"11.7.2.6"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.7.2.7","level":"11.7.2","list_caption":"Figure: CNCF Landscape 中的 Serverless 单元","alt":"CNCF Landscape 中的 Serverless 单元","nro":287,"url":"../images/006tNc79ly1fznbh3vfbwj310f0jxgxj.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF Landscape 中的 Serverless 单元","attributes":{},"skip":false,"key":"11.7.2.7"},{"backlink":"appendix/cncf-annual-report-2018.html#fig11.8.1.1","level":"11.8.1","list_caption":"Figure: CNCF 项目成熟度级别","alt":"CNCF 项目成熟度级别","nro":288,"url":"../images/006tNc79ly1g04s0oznytj31tg0ok7ca.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF 项目成熟度级别","attributes":{},"skip":false,"key":"11.8.1.1"},{"backlink":"appendix/cncf-annual-report-2018.html#fig11.8.1.2","level":"11.8.1","list_caption":"Figure: KCSP","alt":"KCSP","nro":289,"url":"../images/006tNc79ly1g04tl97vm4j318v0h7dpt.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"KCSP","attributes":{},"skip":false,"key":"11.8.1.2"},{"backlink":"appendix/cncf-annual-report-2020.html#fig11.8.2.1","level":"11.8.2","list_caption":"Figure: CNCF 会员增长情况","alt":"CNCF 会员增长情况","nro":290,"url":"../images/008eGmZEly1gmhqzaxsy1j31dz0u0acn.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF 会员增长情况","attributes":{},"skip":false,"key":"11.8.2.1"},{"backlink":"appendix/cncf-annual-report-2020.html#fig11.8.2.2","level":"11.8.2","list_caption":"Figure: 新收录的开源项目","alt":"新收录的开源项目","nro":291,"url":"../images/008eGmZEly1gmhrip3dc2j315q0u01e0.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"新收录的开源项目","attributes":{},"skip":false,"key":"11.8.2.2"},{"backlink":"appendix/cncf-annual-report-2020.html#fig11.8.2.3","level":"11.8.2","list_caption":"Figure: 项目更新","alt":"项目更新","nro":292,"url":"../images/008eGmZEly1gmhrl3860hj31ob0u0wn4.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"项目更新","attributes":{},"skip":false,"key":"11.8.2.3"}]},"title":"Kubernetes Handbook - Kubernetes 中文指南/云原生应用架构实践手册 · Jimmy Song","language":"zh-hans","links":{"sidebar":{"回到主页":"https://jimmysong.io","云原生开源项目大全":"https://jimmysong.io/awesome-cloud-native","云原生社区":"https://cloudnative.to"}},"gitbook":"*","description":"Kubernetes Handbook - Kubernetes 中文指南/云原生应用架构实践手册,本书记录了本人从零开始学习和使用 Kubernetes 的心路历程,着重于经验分享和总结,同时也会有相关的概念解析,希望能够帮助大家少踩坑,少走弯路,还会指引大家关注Kubernetes生态周边,如微服务构建、DevOps、大数据应用、Service Mesh、Cloud Native等领域。"},"file":{"path":"concepts/volume.md","mtime":"2022-01-18T02:29:37.928Z","type":"markdown"},"gitbook":{"version":"3.2.3","time":"2022-01-18T02:30:06.400Z"},"basePath":"..","book":{"language":""}});
|
||
});
|
||
</script>
|
||
</div>
|
||
|
||
|
||
<script src="../gitbook/gitbook.js"></script>
|
||
<script src="../gitbook/theme.js"></script>
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-github/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-splitter/splitter.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-page-toc-button/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-editlink/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-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-lightbox/js/lightbox.min.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-ga/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-sharing/buttons.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-fontsettings/fontsettings.js"></script>
|
||
|
||
|
||
|
||
</body>
|
||
</html>
|
||
|