4807 lines
284 KiB
HTML
4807 lines
284 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>Kubernetes 的设计理念 · Kubernetes 中文指南——云原生应用架构实战手册</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-expandable-chapters-small/expandable-chapters-small.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-insert-logo/plugin.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="etcd.html" />
|
||
|
||
|
||
<link rel="prev" href="./" />
|
||
|
||
|
||
|
||
<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>
|
||
|
||
云原生的定义
|
||
|
||
</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 active" 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 " 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/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.4.</b>
|
||
|
||
Sidecar 的注入与流量劫持
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.5" data-path="../usecases/how-to-integrate-istio-with-vm.html">
|
||
|
||
<a href="../usecases/how-to-integrate-istio-with-vm.html">
|
||
|
||
|
||
<b>7.3.5.</b>
|
||
|
||
Istio 如何支持虚拟机
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.6" data-path="../usecases/istio-vm-support.html">
|
||
|
||
<a href="../usecases/istio-vm-support.html">
|
||
|
||
|
||
<b>7.3.6.</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/tricks.html">
|
||
|
||
<a href="../appendix/tricks.html">
|
||
|
||
|
||
<b>11.4.</b>
|
||
|
||
Kubernetes 使用技巧
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.5" data-path="../appendix/issues.html">
|
||
|
||
<a href="../appendix/issues.html">
|
||
|
||
|
||
<b>11.5.</b>
|
||
|
||
Kubernetes 相关问题记录
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.6" data-path="../appendix/summary-and-outlook.html">
|
||
|
||
<a href="../appendix/summary-and-outlook.html">
|
||
|
||
|
||
<b>11.6.</b>
|
||
|
||
Kubernetes 及云原生年度总结及展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="11.6.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.6.1.</b>
|
||
|
||
Kubernetes 与云原生 2017 年年终总结及 2018 年展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.6.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.6.2.</b>
|
||
|
||
Kubernetes 与云原生 2018 年年终总结及 2019 年展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.7" data-path="../appendix/cncf-annual-report.html">
|
||
|
||
<a href="../appendix/cncf-annual-report.html">
|
||
|
||
|
||
<b>11.7.</b>
|
||
|
||
CNCF 年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="11.7.1" data-path="../appendix/cncf-annual-report-2018.html">
|
||
|
||
<a href="../appendix/cncf-annual-report-2018.html">
|
||
|
||
|
||
<b>11.7.1.</b>
|
||
|
||
CNCF 2018 年年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.7.2" data-path="../appendix/cncf-annual-report-2020.html">
|
||
|
||
<a href="../appendix/cncf-annual-report-2020.html">
|
||
|
||
|
||
<b>11.7.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=".." >Kubernetes 的设计理念</a>
|
||
</h1>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
<div class="page-wrapper" tabindex="-1" role="main">
|
||
<div class="page-inner">
|
||
|
||
<div class="search-plus" id="book-search-results">
|
||
<div class="search-noresults">
|
||
|
||
<section class="normal markdown-section">
|
||
|
||
<h1 id="kubernetes-的设计理念">Kubernetes 的设计理念</h1>
|
||
<p>这一章将介绍 Kubernetes 的设计理念及基本概念。</p>
|
||
<h3 id="kubernetes-设计理念与分布式系统">Kubernetes 设计理念与分布式系统</h3>
|
||
<p>分析和理解 Kubernetes 的设计理念可以使我们更深入地了解 Kubernetes 系统，更好地利用它管理分布式部署的云原生应用，另一方面也可以让我们借鉴其在分布式系统设计方面的经验。</p>
|
||
<h3 id="分层架构">分层架构</h3>
|
||
<p>Kubernetes 设计理念和功能其实就是一个类似 Linux 的分层架构，如下图所示</p>
|
||
<figure id="fig4.1.1.1"><a href="../images/006tNc79ly1fzniqvmi51j31gq0s0q5u.jpg" data-lightbox="e16c8d34-0b51-4ecb-ae9e-06e0cb2d0dbc" data-title="Kubernetes 分层架构示意图"><img src="../images/006tNc79ly1fzniqvmi51j31gq0s0q5u.jpg" alt="Kubernetes 分层架构示意图"></a><figcaption>图 4.1.1.1：Kubernetes 分层架构示意图</figcaption></figure>
|
||
<ul>
|
||
<li>核心层：Kubernetes 最核心的功能，对外提供 API 构建高层的应用，对内提供插件式应用执行环境</li>
|
||
<li>应用层：部署（无状态应用、有状态应用、批处理任务、集群应用等）和路由（服务发现、DNS 解析等）</li>
|
||
<li>管理层：系统度量（如基础设施、容器和网络的度量），自动化（如自动扩展、动态 Provision 等）以及策略管理（RBAC、Quota、PSP、NetworkPolicy 等）</li>
|
||
<li>接口层：kubectl 命令行工具、客户端 SDK 以及集群联邦</li>
|
||
<li>生态系统：在接口层之上的庞大容器集群管理调度的生态系统，可以划分为两个范畴<ul>
|
||
<li>Kubernetes 外部：日志、监控、配置管理、CI、CD、Workflow、FaaS、OTS 应用、ChatOps 等</li>
|
||
<li>Kubernetes 内部：CRI、CNI、CVI、镜像仓库、Cloud Provider、集群自身的配置和管理等</li>
|
||
</ul>
|
||
</li>
|
||
</ul>
|
||
<h3 id="api-设计原则">API 设计原则</h3>
|
||
<p>对于云计算系统，系统 API 实际上处于系统设计的统领地位，正如本文前面所说，Kubernetes 集群系统每支持一项新功能，引入一项新技术，一定会新引入对应的 API 对象，支持对该功能的管理操作，理解掌握的 API，就好比抓住了 Kubernetes 系统的牛鼻子。Kubernetes 系统 API 的设计有以下几条原则：</p>
|
||
<ol>
|
||
<li><strong>所有 API 应该是声明式的</strong>。正如前文所说，声明式的操作，相对于命令式操作，对于重复操作的效果是稳定的，这对于容易出现数据丢失或重复的分布式环境来说是很重要的。另外，声明式操作更容易被用户使用，可以使系统向用户隐藏实现的细节，隐藏实现的细节的同时，也就保留了系统未来持续优化的可能性。此外，声明式的 API，同时隐含了所有的 API 对象都是名词性质的，例如 Service、Volume 这些 API 都是名词，这些名词描述了用户所期望得到的一个目标分布式对象。 </li>
|
||
<li><strong>API 对象是彼此互补而且可组合的</strong>。这里面实际是鼓励 API 对象尽量实现面向对象设计时的要求，即 “高内聚，松耦合”，对业务相关的概念有一个合适的分解，提高分解出来的对象的可重用性。事实上，Kubernetes 这种分布式系统管理平台，也是一种业务系统，只不过它的业务就是调度和管理容器服务。 </li>
|
||
<li><strong>高层 API 以操作意图为基础设计</strong>。如何能够设计好 API，跟如何能用面向对象的方法设计好应用系统有相通的地方，高层设计一定是从业务出发，而不是过早的从技术实现出发。因此，针对 Kubernetes 的高层 API 设计，一定是以 Kubernetes 的业务为基础出发，也就是以系统调度管理容器的操作意图为基础设计。 </li>
|
||
<li><strong>低层 API 根据高层 API 的控制需要设计</strong>。设计实现低层 API 的目的，是为了被高层 API 使用，考虑减少冗余、提高重用性的目的，低层 API 的设计也要以需求为基础，要尽量抵抗受技术实现影响的诱惑。 </li>
|
||
<li><strong>尽量避免简单封装，不要有在外部 API 无法显式知道的内部隐藏的机制</strong>。简单的封装，实际没有提供新的功能，反而增加了对所封装 API 的依赖性。内部隐藏的机制也是非常不利于系统维护的设计方式，例如 StatefulSet 和 ReplicaSet，本来就是两种 Pod 集合，那么 Kubernetes 就用不同 API 对象来定义它们，而不会说只用同一个 ReplicaSet，内部通过特殊的算法再来区分这个 ReplicaSet 是有状态的还是无状态。 </li>
|
||
<li><strong>API 操作复杂度与对象数量成正比</strong>。这一条主要是从系统性能角度考虑，要保证整个系统随着系统规模的扩大，性能不会迅速变慢到无法使用，那么最低的限定就是 API 的操作复杂度不能超过 O(N)，N 是对象的数量，否则系统就不具备水平伸缩性了。 </li>
|
||
<li><strong>API 对象状态不能依赖于网络连接状态</strong>。由于众所周知，在分布式环境下，网络连接断开是经常发生的事情，因此要保证 API 对象状态能应对网络的不稳定，API 对象的状态就不能依赖于网络连接状态。 </li>
|
||
<li><strong>尽量避免让操作机制依赖于全局状态，因为在分布式系统中要保证全局状态的同步是非常困难的</strong>。</li>
|
||
</ol>
|
||
<h3 id="控制机制设计原则">控制机制设计原则</h3>
|
||
<ul>
|
||
<li><strong>控制逻辑应该只依赖于当前状态</strong>。这是为了保证分布式系统的稳定可靠，对于经常出现局部错误的分布式系统，如果控制逻辑只依赖当前状态，那么就非常容易将一个暂时出现故障的系统恢复到正常状态，因为你只要将该系统重置到某个稳定状态，就可以自信的知道系统的所有控制逻辑会开始按照正常方式运行。 </li>
|
||
<li><strong>假设任何错误的可能，并做容错处理</strong>。在一个分布式系统中出现局部和临时错误是大概率事件。错误可能来自于物理系统故障，外部系统故障也可能来自于系统自身的代码错误，依靠自己实现的代码不会出错来保证系统稳定其实也是难以实现的，因此要设计对任何可能错误的容错处理。 </li>
|
||
<li><strong>尽量避免复杂状态机，控制逻辑不要依赖无法监控的内部状态</strong>。因为分布式系统各个子系统都是不能严格通过程序内部保持同步的，所以如果两个子系统的控制逻辑如果互相有影响，那么子系统就一定要能互相访问到影响控制逻辑的状态，否则，就等同于系统里存在不确定的控制逻辑。 </li>
|
||
<li><strong>假设任何操作都可能被任何操作对象拒绝，甚至被错误解析</strong>。由于分布式系统的复杂性以及各子系统的相对独立性，不同子系统经常来自不同的开发团队，所以不能奢望任何操作被另一个子系统以正确的方式处理，要保证出现错误的时候，操作级别的错误不会影响到系统稳定性。 </li>
|
||
<li><strong>每个模块都可以在出错后自动恢复</strong>。由于分布式系统中无法保证系统各个模块是始终连接的，因此每个模块要有自我修复的能力，保证不会因为连接不到其他模块而自我崩溃。 </li>
|
||
<li><strong>每个模块都可以在必要时优雅地降级服务</strong>。所谓优雅地降级服务，是对系统鲁棒性的要求，即要求在设计实现模块时划分清楚基本功能和高级功能，保证基本功能不会依赖高级功能，这样同时就保证了不会因为高级功能出现故障而导致整个模块崩溃。根据这种理念实现的系统，也更容易快速地增加新的高级功能，因为不必担心引入高级功能影响原有的基本功能。</li>
|
||
</ul>
|
||
<h2 id="kubernetes-的核心技术概念和-api-对象">Kubernetes 的核心技术概念和 API 对象</h2>
|
||
<p>API 对象是 Kubernetes 集群中的管理操作单元。Kubernetes 集群系统每支持一项新功能，引入一项新技术，一定会新引入对应的 API 对象，支持对该功能的管理操作。例如副本集 Replica Set 对应的 API 对象是 RS。</p>
|
||
<p>每个 API 对象都有 3 大类属性：元数据 metadata、规范 spec 和状态 status。元数据是用来标识 API 对象的，每个对象都至少有 3 个元数据：namespace，name 和 uid；除此以外还有各种各样的标签 labels 用来标识和匹配不同的对象，例如用户可以用标签 env 来标识区分不同的服务部署环境，分别用 env=dev、env=testing、env=production 来标识开发、测试、生产的不同服务。规范描述了用户期望 Kubernetes 集群中的分布式系统达到的理想状态（Desired State），例如用户可以通过复制控制器 Replication Controller 设置期望的 Pod 副本数为 3；status 描述了系统实际当前达到的状态（Status），例如系统当前实际的 Pod 副本数为 2；那么复制控制器当前的程序逻辑就是自动启动新的 Pod，争取达到副本数为 3。</p>
|
||
<p>Kubernetes 中所有的配置都是通过 API 对象的 spec 去设置的，也就是用户通过配置系统的理想状态来改变系统，这是 Kubernetes 重要设计理念之一，即所有的操作都是声明式（Declarative）的而不是命令式（Imperative）的。声明式操作在分布式系统中的好处是稳定，不怕丢操作或运行多次，例如设置副本数为 3 的操作运行多次也还是一个结果，而给副本数加 1 的操作就不是声明式的，运行多次结果就错了。</p>
|
||
<h3 id="pod">Pod</h3>
|
||
<p>Kubernetes 有很多技术概念，同时对应很多 API 对象，最重要的也是最基础的是 Pod。Pod 是在 Kubernetes 集群中运行部署应用或服务的最小单元，它是可以支持多容器的。Pod 的设计理念是支持多个容器在一个 Pod 中共享网络地址和文件系统，可以通过进程间通信和文件共享这种简单高效的方式组合完成服务。Pod 对多容器的支持是 K8 最基础的设计理念。比如你运行一个操作系统发行版的软件仓库，一个 Nginx 容器用来发布软件，另一个容器专门用来从源仓库做同步，这两个容器的镜像不太可能是一个团队开发的，但是他们一块儿工作才能提供一个微服务；这种情况下，不同的团队各自开发构建自己的容器镜像，在部署的时候组合成一个微服务对外提供服务。</p>
|
||
<p>Pod 是 Kubernetes 集群中所有业务类型的基础，可以看作运行在 Kubernetes 集群中的小机器人，不同类型的业务就需要不同类型的小机器人去执行。目前 Kubernetes 中的业务主要可以分为长期伺服型（long-running）、批处理型（batch）、节点后台支撑型（node-daemon）和有状态应用型（stateful application）；分别对应的小机器人控制器为 Deployment、Job、DaemonSet 和 StatefulSet，本文后面会一一介绍。</p>
|
||
<h3 id="副本控制器（replication-controller，rc）">副本控制器（Replication Controller，RC）</h3>
|
||
<p>RC 是 Kubernetes 集群中最早的保证 Pod 高可用的 API 对象。通过监控运行中的 Pod 来保证集群中运行指定数目的 Pod 副本。指定的数目可以是多个也可以是 1 个；少于指定数目，RC 就会启动运行新的 Pod 副本；多于指定数目，RC 就会杀死多余的 Pod 副本。即使在指定数目为 1 的情况下，通过 RC 运行 Pod 也比直接运行 Pod 更明智，因为 RC 也可以发挥它高可用的能力，保证永远有 1 个 Pod 在运行。RC 是 Kubernetes 较早期的技术概念，只适用于长期伺服型的业务类型，比如控制小机器人提供高可用的 Web 服务。</p>
|
||
<h3 id="副本集（replica-set，rs）">副本集（Replica Set，RS）</h3>
|
||
<p>RS 是新一代 RC，提供同样的高可用能力，区别主要在于 RS 后来居上，能支持更多种类的匹配模式。副本集对象一般不单独使用，而是作为 Deployment 的理想状态参数使用。</p>
|
||
<h3 id="部署（deployment）">部署（Deployment）</h3>
|
||
<p>部署表示用户对 Kubernetes 集群的一次更新操作。部署是一个比 RS 应用模式更广的 API 对象，可以是创建一个新的服务，更新一个新的服务，也可以是滚动升级一个服务。滚动升级一个服务，实际是创建一个新的 RS，然后逐渐将新 RS 中副本数增加到理想状态，将旧 RS 中的副本数减小到 0 的复合操作；这样一个复合操作用一个 RS 是不太好描述的，所以用一个更通用的 Deployment 来描述。以 Kubernetes 的发展方向，未来对所有长期伺服型的的业务的管理，都会通过 Deployment 来管理。</p>
|
||
<h3 id="服务（service）">服务（Service）</h3>
|
||
<p>RC、RS 和 Deployment 只是保证了支撑服务的微服务 Pod 的数量，但是没有解决如何访问这些服务的问题。一个 Pod 只是一个运行服务的实例，随时可能在一个节点上停止，在另一个节点以一个新的 IP 启动一个新的 Pod，因此不能以确定的 IP 和端口号提供服务。要稳定地提供服务需要服务发现和负载均衡能力。服务发现完成的工作，是针对客户端访问的服务，找到对应的的后端服务实例。在 K8 集群中，客户端需要访问的服务就是 Service 对象。每个 Service 会对应一个集群内部有效的虚拟 IP，集群内部通过虚拟 IP 访问一个服务。在 Kubernetes 集群中微服务的负载均衡是由 Kube-proxy 实现的。Kube-proxy 是 Kubernetes 集群内部的负载均衡器。它是一个分布式代理服务器，在 Kubernetes 的每个节点上都有一个；这一设计体现了它的伸缩性优势，需要访问服务的节点越多，提供负载均衡能力的 Kube-proxy 就越多，高可用节点也随之增多。与之相比，我们平时在服务器端做个反向代理做负载均衡，还要进一步解决反向代理的负载均衡和高可用问题。</p>
|
||
<h3 id="任务（job）">任务（Job）</h3>
|
||
<p>Job 是 Kubernetes 用来控制批处理型任务的 API 对象。批处理业务与长期伺服业务的主要区别是批处理业务的运行有头有尾，而长期伺服业务在用户不停止的情况下永远运行。Job 管理的 Pod 根据用户的设置把任务成功完成就自动退出了。成功完成的标志根据不同的 spec.completions 策略而不同：单 Pod 型任务有一个 Pod 成功就标志完成；定数成功型任务保证有 N 个任务全部成功；工作队列型任务根据应用确认的全局成功而标志成功。</p>
|
||
<h3 id="后台支撑服务集（daemonset）">后台支撑服务集（DaemonSet）</h3>
|
||
<p>长期伺服型和批处理型服务的核心在业务应用，可能有些节点运行多个同类业务的 Pod，有些节点上又没有这类 Pod 运行；而后台支撑型服务的核心关注点在 Kubernetes 集群中的节点（物理机或虚拟机），要保证每个节点上都有一个此类 Pod 运行。节点可能是所有集群节点也可能是通过 nodeSelector 选定的一些特定节点。典型的后台支撑型服务包括，存储，日志和监控等在每个节点上支持 Kubernetes 集群运行的服务。</p>
|
||
<h3 id="有状态服务集（statefulset）">有状态服务集（StatefulSet）</h3>
|
||
<p>Kubernetes 在 1.3 版本里发布了 Alpha 版的 PetSet 功能，在 1.5 版本里将 PetSet 功能升级到了 Beta 版本，并重新命名为 StatefulSet，最终在 1.9 版本里成为正式 GA 版本。在云原生应用的体系里，有下面两组近义词；第一组是无状态（stateless）、牲畜（cattle）、无名（nameless）、可丢弃（disposable）；第二组是有状态（stateful）、宠物（pet）、有名（having name）、不可丢弃（non-disposable）。RC 和 RS 主要是控制提供无状态服务的，其所控制的 Pod 的名字是随机设置的，一个 Pod 出故障了就被丢弃掉，在另一个地方重启一个新的 Pod，名字变了。名字和启动在哪儿都不重要，重要的只是 Pod 总数；而 StatefulSet 是用来控制有状态服务，StatefulSet 中的每个 Pod 的名字都是事先确定的，不能更改。StatefulSet 中 Pod 的名字的作用，并不是《千与千寻》的人性原因，而是关联与该 Pod 对应的状态。</p>
|
||
<p>对于 RC 和 RS 中的 Pod，一般不挂载存储或者挂载共享存储，保存的是所有 Pod 共享的状态，Pod 像牲畜一样没有分别（这似乎也确实意味着失去了人性特征）；对于 StatefulSet 中的 Pod，每个 Pod 挂载自己独立的存储，如果一个 Pod 出现故障，从其他节点启动一个同样名字的 Pod，要挂载上原来 Pod 的存储继续以它的状态提供服务。</p>
|
||
<p>适合于 StatefulSet 的业务包括数据库服务 MySQL 和 PostgreSQL，集群化管理服务 ZooKeeper、etcd 等有状态服务。StatefulSet 的另一种典型应用场景是作为一种比普通容器更稳定可靠的模拟虚拟机的机制。传统的虚拟机正是一种有状态的宠物，运维人员需要不断地维护它，容器刚开始流行时，我们用容器来模拟虚拟机使用，所有状态都保存在容器里，而这已被证明是非常不安全、不可靠的。使用 StatefulSet，Pod 仍然可以通过漂移到不同节点提供高可用，而存储也可以通过外挂的存储来提供高可靠性，StatefulSet 做的只是将确定的 Pod 与确定的存储关联起来保证状态的连续性。</p>
|
||
<h3 id="集群联邦（federation）">集群联邦（Federation）</h3>
|
||
<p>Kubernetes 在 1.3 版本里发布了 beta 版的 Federation 功能。在云计算环境中，服务的作用距离范围从近到远一般可以有：同主机（Host，Node）、跨主机同可用区（Available Zone）、跨可用区同地区（Region）、跨地区同服务商（Cloud Service Provider）、跨云平台。Kubernetes 的设计定位是单一集群在同一个地域内，因为同一个地区的网络性能才能满足 Kubernetes 的调度和计算存储连接要求。而联合集群服务就是为提供跨 Region 跨服务商 Kubernetes 集群服务而设计的。</p>
|
||
<p>每个 Kubernetes Federation 有自己的分布式存储、API Server 和 Controller Manager。用户可以通过 Federation 的 API Server 注册该 Federation 的成员 Kubernetes Cluster。当用户通过 Federation 的 API Server 创建、更改 API 对象时，Federation API Server 会在自己所有注册的子 Kubernetes Cluster 都创建一份对应的 API 对象。在提供业务请求服务时，Kubernetes Federation 会先在自己的各个子 Cluster 之间做负载均衡，而对于发送到某个具体 Kubernetes Cluster 的业务请求，会依照这个 Kubernetes Cluster 独立提供服务时一样的调度模式去做 Kubernetes Cluster 内部的负载均衡。而 Cluster 之间的负载均衡是通过域名服务的负载均衡来实现的。</p>
|
||
<p>Federation V1 的设计是尽量不影响 Kubernetes Cluster 现有的工作机制，这样对于每个子 Kubernetes 集群来说，并不需要更外层的有一个 Kubernetes Federation，也就是意味着所有现有的 Kubernetes 代码和机制不需要因为 Federation 功能有任何变化。</p>
|
||
<p>目前正在开发的 Federation V2，在保留现有 Kubernetes API 的同时，会开发新的 Federation 专用的 API 接口，详细内容可以在 <a href="https://github.com/kubernetes/community/tree/master/sig-multicluster" target="_blank">这里</a> 找到。</p>
|
||
<h3 id="存储卷（volume）">存储卷（Volume）</h3>
|
||
<p>Kubernetes 集群中的存储卷跟 Docker 的存储卷有些类似，只不过 Docker 的存储卷作用范围为一个容器，而 Kubernetes 的存储卷的生命周期和作用范围是一个 Pod。每个 Pod 中声明的存储卷由 Pod 中的所有容器共享。Kubernetes 支持非常多的存储卷类型，特别的，支持多种公有云平台的存储，包括 AWS，Google 和 Azure 云；支持多种分布式存储包括 GlusterFS 和 Ceph；也支持较容易使用的主机本地目录 emptyDir, hostPath 和 NFS。Kubernetes 还支持使用 Persistent Volume Claim 即 PVC 这种逻辑存储，使用这种存储，使得存储的使用者可以忽略后台的实际存储技术（例如 AWS，Google 或 GlusterFS 和 Ceph），而将有关存储实际技术的配置交给存储管理员通过 Persistent Volume 来配置。</p>
|
||
<h3 id="持久存储卷（persistent-volume，pv）和持久存储卷声明（persistent-volume-claim，pvc）">持久存储卷（Persistent Volume，PV）和持久存储卷声明（Persistent Volume Claim，PVC）</h3>
|
||
<p>PV 和 PVC 使得 Kubernetes 集群具备了存储的逻辑抽象能力，使得在配置 Pod 的逻辑里可以忽略对实际后台存储技术的配置，而把这项配置的工作交给 PV 的配置者，即集群的管理者。存储的 PV 和 PVC 的这种关系，跟计算的 Node 和 Pod 的关系是非常类似的；PV 和 Node 是资源的提供者，根据集群的基础设施变化而变化，由 Kubernetes 集群管理员配置；而 PVC 和 Pod 是资源的使用者，根据业务服务的需求变化而变化，有 Kubernetes 集群的使用者即服务的管理员来配置。</p>
|
||
<h3 id="节点（node）">节点（Node）</h3>
|
||
<p>Kubernetes 集群中的计算能力由 Node 提供，最初 Node 称为服务节点 Minion，后来改名为 Node。Kubernetes 集群中的 Node 也就等同于 Mesos 集群中的 Slave 节点，是所有 Pod 运行所在的工作主机，可以是物理机也可以是虚拟机。不论是物理机还是虚拟机，工作主机的统一特征是上面要运行 kubelet 管理节点上运行的容器。</p>
|
||
<h3 id="密钥对象（secret）">密钥对象（Secret）</h3>
|
||
<p>Secret 是用来保存和传递密码、密钥、认证凭证这些敏感信息的对象。使用 Secret 的好处是可以避免把敏感信息明文写在配置文件里。在 Kubernetes 集群中配置和使用服务不可避免的要用到各种敏感信息实现登录、认证等功能，例如访问 AWS 存储的用户名密码。为了避免将类似的敏感信息明文写在所有需要使用的配置文件中，可以将这些信息存入一个 Secret 对象，而在配置文件中通过 Secret 对象引用这些敏感信息。这种方式的好处包括：意图明确，避免重复，减少暴漏机会。</p>
|
||
<h3 id="用户帐户（user-account）和服务帐户（service-account）">用户帐户（User Account）和服务帐户（Service Account）</h3>
|
||
<p>顾名思义，用户帐户为人提供账户标识，而服务账户为计算机进程和 Kubernetes 集群中运行的 Pod 提供账户标识。用户帐户和服务帐户的一个区别是作用范围；用户帐户对应的是人的身份，人的身份与服务的 namespace 无关，所以用户账户是跨 namespace 的；而服务帐户对应的是一个运行中程序的身份，与特定 namespace 是相关的。</p>
|
||
<h3 id="命名空间（namespace）">命名空间（Namespace）</h3>
|
||
<p>命名空间为 Kubernetes 集群提供虚拟的隔离作用，Kubernetes 集群初始有两个命名空间，分别是默认命名空间 default 和系统命名空间 kube-system，除此以外，管理员可以可以创建新的命名空间满足需要。</p>
|
||
<h3 id="rbac-访问授权">RBAC 访问授权</h3>
|
||
<p>Kubernetes 在 1.3 版本中发布了 alpha 版的基于角色的访问控制（Role-based Access Control，RBAC）的授权模式。相对于基于属性的访问控制（Attribute-based Access Control，ABAC），RBAC 主要是引入了角色（Role）和角色绑定（RoleBinding）的抽象概念。在 ABAC 中，Kubernetes 集群中的访问策略只能跟用户直接关联；而在 RBAC 中，访问策略可以跟某个角色关联，具体的用户在跟一个或多个角色相关联。显然，RBAC 像其他新功能一样，每次引入新功能，都会引入新的 API 对象，从而引入新的概念抽象，而这一新的概念抽象一定会使集群服务管理和使用更容易扩展和重用。</p>
|
||
<h2 id="总结">总结</h2>
|
||
<p>从 Kubernetes 的系统架构、技术概念和设计理念，我们可以看到 Kubernetes 系统最核心的两个设计理念：一个是 <strong>容错性</strong>，一个是 <strong>易扩展性</strong>。容错性实际是保证 Kubernetes 系统稳定性和安全性的基础，易扩展性是保证 Kubernetes 对变更友好，可以快速迭代增加新功能的基础。</p>
|
||
<p>按照分布式系统一致性算法 Paxos 发明人计算机科学家 <a href="http://research.microsoft.com/users/lamport/pubs/pubs.html" target="_blank">Leslie Lamport</a> 的理念，一个分布式系统有两类特性：安全性 Safety 和活性 Liveness。安全性保证系统的稳定，保证系统不会崩溃，不会出现业务错误，不会做坏事，是严格约束的；活性使得系统可以提供功能，提高性能，增加易用性，让系统可以在用户 “看到的时间内” 做些好事，是尽力而为的。Kubernetes 系统的设计理念正好与 Lamport 安全性与活性的理念不谋而合，也正是因为 Kubernetes 在引入功能和技术的时候，非常好地划分了安全性和活性，才可以让 Kubernetes 能有这么快版本迭代，快速引入像 RBAC、Federation 和 PetSet 这种新功能。</p>
|
||
<h2 id="参考">参考</h2>
|
||
<ul>
|
||
<li><a href="https://www.infoq.cn/article/kubernetes-and-cloud-native-applications-part01/" target="_blank">《Kubernetes 与云原生应用》系列之 Kubernetes 的系统架构与设计理念</a></li>
|
||
</ul>
|
||
<footer class="page-footer"><span class="copyright">Copyright © 2017-2022 | 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.</span><span class="footer-modification"> Updated at
|
||
2022-04-07 02:52:22
|
||
</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="./" class="navigation navigation-prev " aria-label="Previous page: Kubernetes 架构">
|
||
<i class="fa fa-angle-left"></i>
|
||
</a>
|
||
|
||
|
||
<a href="etcd.html" class="navigation navigation-next " aria-label="Next page: Etcd 解析">
|
||
<i class="fa fa-angle-right"></i>
|
||
</a>
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<script>
|
||
var gitbook = gitbook || [];
|
||
gitbook.push(function() {
|
||
gitbook.page.hasChanged({"page":{"title":"Kubernetes 的设计理念","level":"4.1.1","depth":2,"next":{"title":"Etcd 解析","level":"4.1.2","depth":2,"path":"concepts/etcd.md","ref":"concepts/etcd.md","articles":[]},"previous":{"title":"Kubernetes 架构","level":"4.1","depth":1,"path":"concepts/index.md","ref":"concepts/index.md","articles":[{"title":"Kubernetes 的设计理念","level":"4.1.1","depth":2,"path":"concepts/concepts.md","ref":"concepts/concepts.md","articles":[]},{"title":"Etcd 解析","level":"4.1.2","depth":2,"path":"concepts/etcd.md","ref":"concepts/etcd.md","articles":[]},{"title":"开放接口","level":"4.1.3","depth":2,"path":"concepts/open-interfaces.md","ref":"concepts/open-interfaces.md","articles":[{"title":"容器运行时接口（CRI）","level":"4.1.3.1","depth":3,"path":"concepts/cri.md","ref":"concepts/cri.md","articles":[]},{"title":"容器网络接口（CNI）","level":"4.1.3.2","depth":3,"path":"concepts/cni.md","ref":"concepts/cni.md","articles":[]},{"title":"容器存储接口（CSI）","level":"4.1.3.3","depth":3,"path":"concepts/csi.md","ref":"concepts/csi.md","articles":[]}]},{"title":"Kubernetes 中的资源对象","level":"4.1.4","depth":2,"path":"concepts/objects.md","ref":"concepts/objects.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","hide-element","expandable-chapters-small","insert-logo","adsense"],"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":"Copyright © 2017-2022 | 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":{},"adsense":{"client":"ca-pub-4029167986768912","slot":"2445941692","format":"auto","element":".page-inner section","position":"bottom"},"codesnippet":{},"sitemap-general":{"prefix":"https://jimmysong.io/kubernetes-handbook/"},"hide-element":{"elements":[".gitbook-link"]},"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"},"expandable-chapters-small":{},"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"}},"insert-logo":{"style":"background: none; max-height: 100px; min-height: 30px","url":"https://jimmysong.io/images/logo-black-text.png"},"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: Kubernetes 集群全局监控图 1","alt":"Kubernetes 集群全局监控图 1","nro":12,"url":"../images/kubernetes-devops-example-grafana-1.png","index":12,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 集群全局监控图 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: Kubernetes 全局监控图 2","alt":"Kubernetes 全局监控图 2","nro":13,"url":"../images/kubernetes-devops-example-grafana-2.png","index":13,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 全局监控图 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/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.4.1","level":"7.3.4","list_caption":"Figure: Sidecar 模式示意图","alt":"Sidecar 模式示意图","nro":215,"url":"../images/sidecar-pattern.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Sidecar 模式示意图","attributes":{},"skip":false,"key":"7.3.4.1"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.4.2","level":"7.3.4","list_caption":"Figure: Sidecar 流量劫持示意图","alt":"Sidecar 流量劫持示意图","nro":216,"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.4.2"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.4.3","level":"7.3.4","list_caption":"Figure: iptables 调用链","alt":"iptables 调用链","nro":217,"url":"../images/iptables.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"iptables 调用链","attributes":{},"skip":false,"key":"7.3.4.3"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.4.4","level":"7.3.4","list_caption":"Figure: hook-connect 原理示意图","alt":"hook-connect 原理示意图","nro":218,"url":"../images/hook-connect.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"hook-connect 原理示意图","attributes":{},"skip":false,"key":"7.3.4.4"},{"backlink":"usecases/how-to-integrate-istio-with-vm.html#fig7.3.5.1","level":"7.3.5","list_caption":"Figure: Istio 中的服务注册发现模型","alt":"Istio 中的服务注册发现模型","nro":219,"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.5.1"},{"backlink":"usecases/how-to-integrate-istio-with-vm.html#fig7.3.5.2","level":"7.3.5","list_caption":"Figure: Bookinfo 示例中的流量示意图","alt":"Bookinfo 示例中的流量示意图","nro":220,"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.5.2"},{"backlink":"usecases/istio-vm-support.html#fig7.3.6.1","level":"7.3.6","list_caption":"Figure: 云原生应用的三个阶段","alt":"云原生应用的三个阶段","nro":221,"url":"../images/0081Kckwly1gm0d6t775lj31s80k8go8.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生应用的三个阶段","attributes":{},"skip":false,"key":"7.3.6.1"},{"backlink":"usecases/istio-vm-support.html#fig7.3.6.2","level":"7.3.6","list_caption":"Figure: 图一：从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","alt":"图一：从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","nro":222,"url":"../images/0081Kckwly1gm0d6rogojj30u00yhdil.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"图一：从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","attributes":{},"skip":false,"key":"7.3.6.2"},{"backlink":"usecases/istio-vm-support.html#fig7.3.6.3","level":"7.3.6","list_caption":"Figure: 图二：通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","alt":"图二：通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","nro":223,"url":"../images/0081Kckwly1gm0d6qx2o0j30sq0v440v.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"图二：通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","attributes":{},"skip":false,"key":"7.3.6.3"},{"backlink":"usecases/istio-vm-support.html#fig7.3.6.4","level":"7.3.6","list_caption":"Figure: 图三：引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","alt":"图三：引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","nro":224,"url":"../images/0081Kckwly1gm0d6sgfpxj30oi0rsjt5.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"图三：引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","attributes":{},"skip":false,"key":"7.3.6.4"},{"backlink":"usecases/envoy.html#fig7.4.1","level":"7.4","list_caption":"Figure: 负载均衡器的特性以及拓扑类型","alt":"负载均衡器的特性以及拓扑类型","nro":225,"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":226,"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":227,"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":228,"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":229,"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":230,"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":231,"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":232,"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":233,"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":234,"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":235,"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":236,"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":237,"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":238,"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":239,"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":240,"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":241,"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":242,"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":243,"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":244,"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":245,"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":246,"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":247,"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":248,"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":249,"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":250,"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":251,"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":252,"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":253,"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":254,"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":255,"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":256,"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":257,"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":258,"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":259,"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":260,"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":261,"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":262,"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":263,"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":264,"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":265,"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":266,"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":267,"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":268,"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":269,"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/issues.html#fig11.5.1","level":"11.5","list_caption":"Figure: pvc-storage-limit","alt":"pvc-storage-limit","nro":270,"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.5.1"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.1","level":"11.6.2","list_caption":"Figure: Kubernetes 搜索趋势(来自 Google trends)","alt":"Kubernetes 搜索趋势(来自 Google trends)","nro":271,"url":"../images/006tNc79ly1fzne6y4f2ej31q60fedho.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 搜索趋势(来自 Google trends)","attributes":{},"skip":false,"key":"11.6.2.1"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.2","level":"11.6.2","list_caption":"Figure: Kubernetes 的百度指数","alt":"Kubernetes 的百度指数","nro":272,"url":"../images/006tNc79ly1fznegoocmvj31y00hmgon.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 的百度指数","attributes":{},"skip":false,"key":"11.6.2.2"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.3","level":"11.6.2","list_caption":"Figure: Istio 中的 CRD","alt":"Istio 中的 CRD","nro":273,"url":"../images/006tNc79ly1fzna87wmfij30u00zc4qp.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Istio 中的 CRD","attributes":{},"skip":false,"key":"11.6.2.3"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.4","level":"11.6.2","list_caption":"Figure: 2019 Q1 软件架构趋势 - 来自 InfoQ","alt":"2019 Q1 软件架构趋势 - 来自 InfoQ","nro":274,"url":"../images/006tNc79ly1fzor2k6f7wj313j0u0dl3.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"2019 Q1 软件架构趋势 - 来自 InfoQ","attributes":{},"skip":false,"key":"11.6.2.4"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.5","level":"11.6.2","list_caption":"Figure: ServiceMesher 社区 Logo","alt":"ServiceMesher 社区 Logo","nro":275,"url":"../images/006tNc79ly1fznadbp63qj31jt0beq9s.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"ServiceMesher 社区 Logo","attributes":{},"skip":false,"key":"11.6.2.5"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.6","level":"11.6.2","list_caption":"Figure: ServiceMesher 社区 2018 年活动一览","alt":"ServiceMesher 社区 2018 年活动一览","nro":276,"url":"../images/006tNc79ly1fzm9vs4o3aj31s00u0x6p.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"ServiceMesher 社区 2018 年活动一览","attributes":{},"skip":false,"key":"11.6.2.6"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.7","level":"11.6.2","list_caption":"Figure: CNCF Landscape 中的 Serverless 单元","alt":"CNCF Landscape 中的 Serverless 单元","nro":277,"url":"../images/006tNc79ly1fznbh3vfbwj310f0jxgxj.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF Landscape 中的 Serverless 单元","attributes":{},"skip":false,"key":"11.6.2.7"},{"backlink":"appendix/cncf-annual-report-2018.html#fig11.7.1.1","level":"11.7.1","list_caption":"Figure: CNCF 项目成熟度级别","alt":"CNCF 项目成熟度级别","nro":278,"url":"../images/006tNc79ly1g04s0oznytj31tg0ok7ca.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF 项目成熟度级别","attributes":{},"skip":false,"key":"11.7.1.1"},{"backlink":"appendix/cncf-annual-report-2018.html#fig11.7.1.2","level":"11.7.1","list_caption":"Figure: KCSP","alt":"KCSP","nro":279,"url":"../images/006tNc79ly1g04tl97vm4j318v0h7dpt.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"KCSP","attributes":{},"skip":false,"key":"11.7.1.2"},{"backlink":"appendix/cncf-annual-report-2020.html#fig11.7.2.1","level":"11.7.2","list_caption":"Figure: CNCF 会员增长情况","alt":"CNCF 会员增长情况","nro":280,"url":"../images/008eGmZEly1gmhqzaxsy1j31dz0u0acn.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF 会员增长情况","attributes":{},"skip":false,"key":"11.7.2.1"},{"backlink":"appendix/cncf-annual-report-2020.html#fig11.7.2.2","level":"11.7.2","list_caption":"Figure: 新收录的开源项目","alt":"新收录的开源项目","nro":281,"url":"../images/008eGmZEly1gmhrip3dc2j315q0u01e0.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"新收录的开源项目","attributes":{},"skip":false,"key":"11.7.2.2"},{"backlink":"appendix/cncf-annual-report-2020.html#fig11.7.2.3","level":"11.7.2","list_caption":"Figure: 项目更新","alt":"项目更新","nro":282,"url":"../images/008eGmZEly1gmhrl3860hj31ob0u0wn4.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"项目更新","attributes":{},"skip":false,"key":"11.7.2.3"}]},"title":"Kubernetes 中文指南——云原生应用架构实战手册","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/concepts.md","mtime":"2022-04-07T02:52:22.457Z","type":"markdown"},"gitbook":{"version":"3.2.3","time":"2022-04-07T02:52:46.237Z"},"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-hide-element/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-expandable-chapters-small/expandable-chapters-small.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-insert-logo/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-adsense/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-sharing/buttons.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-fontsettings/fontsettings.js"></script>
|
||
|
||
|
||
|
||
</body>
|
||
</html>
|
||
|