5379 lines
342 KiB
HTML
5379 lines
342 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>Deployment · Kubernetes Handbook - Kubernetes中文指南/云原生应用架构实践手册 by Jimmy Song(宋净超)</title>
|
||
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
|
||
<meta name="description" content="">
|
||
<meta name="generator" content="GitBook 3.2.3">
|
||
<meta name="author" content="Jimmy Song(宋净超)">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/style.css">
|
||
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-splitter/splitter.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-page-toc-button/plugin.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-image-captions/image-captions.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-back-to-top-button/plugin.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-search-plus/search.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-tbfed-pagefooter/footer.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-prism/prism-ghcolors.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-lightbox/css/lightbox.min.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-alerts/style.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="statefulset.html" />
|
||
|
||
|
||
<link rel="prev" href="controllers.html" />
|
||
|
||
|
||
|
||
<link rel="shortcut icon" href='../favicon.ico' type="image/x-icon">
|
||
|
||
|
||
<link rel="bookmark" href='../favicon.ico' type="image/x-icon">
|
||
|
||
|
||
|
||
|
||
<style>
|
||
@media only screen and (max-width: 640px) {
|
||
.book-header .hidden-mobile {
|
||
display: none;
|
||
}
|
||
}
|
||
</style>
|
||
<script>
|
||
window["gitbook-plugin-github-buttons"] = {"repo":"rootsongjc/kubernetes-handbook","types":["star"],"size":"small"};
|
||
</script>
|
||
|
||
</head>
|
||
<body>
|
||
|
||
<div class="book">
|
||
<div class="book-summary">
|
||
|
||
|
||
<div id="book-search-input" role="search">
|
||
<input type="text" placeholder="输入并搜索" />
|
||
</div>
|
||
|
||
|
||
<nav role="navigation">
|
||
|
||
|
||
|
||
<ul class="summary">
|
||
|
||
|
||
|
||
|
||
<li>
|
||
<a href="https://jimmysong.io" target="_blank" class="custom-link">回到主页</a>
|
||
</li>
|
||
|
||
|
||
<li>
|
||
<a href="https://jimmysong.io/awesome-cloud-native" target="_blank" class="custom-link">云原生开源项目大全</a>
|
||
</li>
|
||
|
||
|
||
<li>
|
||
<a href="https://cloudnative.to" target="_blank" class="custom-link">云原生社区</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="divider"></li>
|
||
|
||
|
||
|
||
|
||
<li class="header">前言</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="1.1" data-path="../">
|
||
|
||
<a href="../">
|
||
|
||
|
||
<b>1.1.</b>
|
||
|
||
序言
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">云原生</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="2.1" data-path="../cloud-native/cloud-native-definition.html">
|
||
|
||
<a href="../cloud-native/cloud-native-definition.html">
|
||
|
||
|
||
<b>2.1.</b>
|
||
|
||
云原生(Cloud Native)的定义
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.2" data-path="../cloud-native/cloud-native-philosophy.html">
|
||
|
||
<a href="../cloud-native/cloud-native-philosophy.html">
|
||
|
||
|
||
<b>2.2.</b>
|
||
|
||
云原生的设计哲学
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.3" data-path="../cloud-native/quick-start.html">
|
||
|
||
<a href="../cloud-native/quick-start.html">
|
||
|
||
|
||
<b>2.3.</b>
|
||
|
||
云原生新手入门指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.4" data-path="../cloud-native/play-with-kubernetes.html">
|
||
|
||
<a href="../cloud-native/play-with-kubernetes.html">
|
||
|
||
|
||
<b>2.4.</b>
|
||
|
||
Play with Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.5" data-path="../cloud-native/cloud-native-local-quick-start.html">
|
||
|
||
<a href="../cloud-native/cloud-native-local-quick-start.html">
|
||
|
||
|
||
<b>2.5.</b>
|
||
|
||
快速部署一个云原生本地实验环境
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6" data-path="../cloud-native/setup-kubernetes-with-rancher-and-aliyun.html">
|
||
|
||
<a href="../cloud-native/setup-kubernetes-with-rancher-and-aliyun.html">
|
||
|
||
|
||
<b>2.6.</b>
|
||
|
||
使用 Rancher 在阿里云上部署 Kubenretes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.7" data-path="../cloud-native/kubernetes-and-cloud-native-app-overview.html">
|
||
|
||
<a href="../cloud-native/kubernetes-and-cloud-native-app-overview.html">
|
||
|
||
|
||
<b>2.7.</b>
|
||
|
||
Kubernetes 与云原生应用概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.8" data-path="../cloud-native/from-kubernetes-to-cloud-native.html">
|
||
|
||
<a href="../cloud-native/from-kubernetes-to-cloud-native.html">
|
||
|
||
|
||
<b>2.8.</b>
|
||
|
||
云原生应用之路 —— 从 Kubernetes 到 Cloud Native
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.9" data-path="../cloud-native/define-cloud-native-app.html">
|
||
|
||
<a href="../cloud-native/define-cloud-native-app.html">
|
||
|
||
|
||
<b>2.9.</b>
|
||
|
||
定义云原生应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.9.1" data-path="../cloud-native/oam.html">
|
||
|
||
<a href="../cloud-native/oam.html">
|
||
|
||
|
||
<b>2.9.1.</b>
|
||
|
||
OAM
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.9.1.1" data-path="../cloud-native/workload.html">
|
||
|
||
<a href="../cloud-native/workload.html">
|
||
|
||
|
||
<b>2.9.1.1.</b>
|
||
|
||
Workload
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.9.1.2" data-path="../cloud-native/component.html">
|
||
|
||
<a href="../cloud-native/component.html">
|
||
|
||
|
||
<b>2.9.1.2.</b>
|
||
|
||
Component
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.9.1.3" data-path="../cloud-native/trait.html">
|
||
|
||
<a href="../cloud-native/trait.html">
|
||
|
||
|
||
<b>2.9.1.3.</b>
|
||
|
||
Trait
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.9.1.4" data-path="../cloud-native/application-scope.html">
|
||
|
||
<a href="../cloud-native/application-scope.html">
|
||
|
||
|
||
<b>2.9.1.4.</b>
|
||
|
||
Application Scope
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.9.1.5" data-path="../cloud-native/application-configuration.html">
|
||
|
||
<a href="../cloud-native/application-configuration.html">
|
||
|
||
|
||
<b>2.9.1.5.</b>
|
||
|
||
Application Configuration
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.9.2" data-path="../cloud-native/crossplane.html">
|
||
|
||
<a href="../cloud-native/crossplane.html">
|
||
|
||
|
||
<b>2.9.2.</b>
|
||
|
||
Crossplane
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.10" data-path="../cloud-native/cloud-native-programming-languages.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-languages.html">
|
||
|
||
|
||
<b>2.10.</b>
|
||
|
||
云原生编程语言
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.10.1" data-path="../cloud-native/cloud-native-programming-language-ballerina.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-language-ballerina.html">
|
||
|
||
|
||
<b>2.10.1.</b>
|
||
|
||
云原生编程语言 Ballerina
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.10.2" data-path="../cloud-native/cloud-native-programming-language-pulumi.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-language-pulumi.html">
|
||
|
||
|
||
<b>2.10.2.</b>
|
||
|
||
云原生编程语言 Pulumi
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.11" data-path="../cloud-native/the-future-of-cloud-native.html">
|
||
|
||
<a href="../cloud-native/the-future-of-cloud-native.html">
|
||
|
||
|
||
<b>2.11.</b>
|
||
|
||
云原生的未来
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">概念与原理</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="3.1" data-path="./">
|
||
|
||
<a href="./">
|
||
|
||
|
||
<b>3.1.</b>
|
||
|
||
Kubernetes 架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.1.1" data-path="concepts.html">
|
||
|
||
<a href="concepts.html">
|
||
|
||
|
||
<b>3.1.1.</b>
|
||
|
||
设计理念
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.1.2" data-path="etcd.html">
|
||
|
||
<a href="etcd.html">
|
||
|
||
|
||
<b>3.1.2.</b>
|
||
|
||
Etcd 解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.1.3" data-path="open-interfaces.html">
|
||
|
||
<a href="open-interfaces.html">
|
||
|
||
|
||
<b>3.1.3.</b>
|
||
|
||
开放接口
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.1.3.1" data-path="cri.html">
|
||
|
||
<a href="cri.html">
|
||
|
||
|
||
<b>3.1.3.1.</b>
|
||
|
||
CRI - Container Runtime Interface(容器运行时接口)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.1.3.2" data-path="cni.html">
|
||
|
||
<a href="cni.html">
|
||
|
||
|
||
<b>3.1.3.2.</b>
|
||
|
||
CNI - Container Network Interface(容器网络接口)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.1.3.3" data-path="csi.html">
|
||
|
||
<a href="csi.html">
|
||
|
||
|
||
<b>3.1.3.3.</b>
|
||
|
||
CSI - Container Storage Interface(容器存储接口)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.2" data-path="networking.html">
|
||
|
||
<a href="networking.html">
|
||
|
||
|
||
<b>3.2.</b>
|
||
|
||
Kubernetes 中的网络
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.2.1" data-path="flannel.html">
|
||
|
||
<a href="flannel.html">
|
||
|
||
|
||
<b>3.2.1.</b>
|
||
|
||
Kubernetes 中的网络解析 —— 以 flannel 为例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.2.2" data-path="calico.html">
|
||
|
||
<a href="calico.html">
|
||
|
||
|
||
<b>3.2.2.</b>
|
||
|
||
Kubernetes 中的网络解析 —— 以 calico 为例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.2.3" data-path="cilium.html">
|
||
|
||
<a href="cilium.html">
|
||
|
||
|
||
<b>3.2.3.</b>
|
||
|
||
具备 API 感知的网络和安全性管理开源软件 Cilium
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.2.3.1" data-path="cilium-concepts.html">
|
||
|
||
<a href="cilium-concepts.html">
|
||
|
||
|
||
<b>3.2.3.1.</b>
|
||
|
||
Cilium 架构设计与概念解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.3" data-path="objects.html">
|
||
|
||
<a href="objects.html">
|
||
|
||
|
||
<b>3.3.</b>
|
||
|
||
资源对象与基本概念解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4" data-path="pod-state-and-lifecycle.html">
|
||
|
||
<a href="pod-state-and-lifecycle.html">
|
||
|
||
|
||
<b>3.4.</b>
|
||
|
||
Pod 状态与生命周期管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.4.1" data-path="pod-overview.html">
|
||
|
||
<a href="pod-overview.html">
|
||
|
||
|
||
<b>3.4.1.</b>
|
||
|
||
Pod 概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.2" data-path="pod.html">
|
||
|
||
<a href="pod.html">
|
||
|
||
|
||
<b>3.4.2.</b>
|
||
|
||
Pod 解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.3" data-path="init-containers.html">
|
||
|
||
<a href="init-containers.html">
|
||
|
||
|
||
<b>3.4.3.</b>
|
||
|
||
Init 容器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.4" data-path="pause-container.html">
|
||
|
||
<a href="pause-container.html">
|
||
|
||
|
||
<b>3.4.4.</b>
|
||
|
||
Pause 容器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.5" data-path="pod-security-policy.html">
|
||
|
||
<a href="pod-security-policy.html">
|
||
|
||
|
||
<b>3.4.5.</b>
|
||
|
||
Pod 安全策略
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.6" data-path="pod-lifecycle.html">
|
||
|
||
<a href="pod-lifecycle.html">
|
||
|
||
|
||
<b>3.4.6.</b>
|
||
|
||
Pod 的生命周期
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.7" data-path="pod-hook.html">
|
||
|
||
<a href="pod-hook.html">
|
||
|
||
|
||
<b>3.4.7.</b>
|
||
|
||
Pod Hook
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.8" data-path="pod-preset.html">
|
||
|
||
<a href="pod-preset.html">
|
||
|
||
|
||
<b>3.4.8.</b>
|
||
|
||
Pod Preset
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.9" data-path="pod-disruption-budget.html">
|
||
|
||
<a href="pod-disruption-budget.html">
|
||
|
||
|
||
<b>3.4.9.</b>
|
||
|
||
Pod 中断与 PDB(Pod 中断预算)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5" data-path="cluster.html">
|
||
|
||
<a href="cluster.html">
|
||
|
||
|
||
<b>3.5.</b>
|
||
|
||
集群资源管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.5.1" data-path="node.html">
|
||
|
||
<a href="node.html">
|
||
|
||
|
||
<b>3.5.1.</b>
|
||
|
||
Node
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5.2" data-path="namespace.html">
|
||
|
||
<a href="namespace.html">
|
||
|
||
|
||
<b>3.5.2.</b>
|
||
|
||
Namespace
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5.3" data-path="label.html">
|
||
|
||
<a href="label.html">
|
||
|
||
|
||
<b>3.5.3.</b>
|
||
|
||
Label
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5.4" data-path="annotation.html">
|
||
|
||
<a href="annotation.html">
|
||
|
||
|
||
<b>3.5.4.</b>
|
||
|
||
Annotation
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5.5" data-path="taint-and-toleration.html">
|
||
|
||
<a href="taint-and-toleration.html">
|
||
|
||
|
||
<b>3.5.5.</b>
|
||
|
||
Taint 和 Toleration(污点和容忍)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5.6" data-path="garbage-collection.html">
|
||
|
||
<a href="garbage-collection.html">
|
||
|
||
|
||
<b>3.5.6.</b>
|
||
|
||
垃圾收集
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6" data-path="controllers.html">
|
||
|
||
<a href="controllers.html">
|
||
|
||
|
||
<b>3.6.</b>
|
||
|
||
控制器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter active" data-level="3.6.1" data-path="deployment.html">
|
||
|
||
<a href="deployment.html">
|
||
|
||
|
||
<b>3.6.1.</b>
|
||
|
||
Deployment
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.2" data-path="statefulset.html">
|
||
|
||
<a href="statefulset.html">
|
||
|
||
|
||
<b>3.6.2.</b>
|
||
|
||
StatefulSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.3" data-path="daemonset.html">
|
||
|
||
<a href="daemonset.html">
|
||
|
||
|
||
<b>3.6.3.</b>
|
||
|
||
DaemonSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.4" data-path="replicaset.html">
|
||
|
||
<a href="replicaset.html">
|
||
|
||
|
||
<b>3.6.4.</b>
|
||
|
||
ReplicationController 和 ReplicaSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.5" data-path="job.html">
|
||
|
||
<a href="job.html">
|
||
|
||
|
||
<b>3.6.5.</b>
|
||
|
||
Job
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.6" data-path="cronjob.html">
|
||
|
||
<a href="cronjob.html">
|
||
|
||
|
||
<b>3.6.6.</b>
|
||
|
||
CronJob
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.7" data-path="horizontal-pod-autoscaling.html">
|
||
|
||
<a href="horizontal-pod-autoscaling.html">
|
||
|
||
|
||
<b>3.6.7.</b>
|
||
|
||
Horizontal Pod Autoscaling
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.6.7.1" data-path="custom-metrics-hpa.html">
|
||
|
||
<a href="custom-metrics-hpa.html">
|
||
|
||
|
||
<b>3.6.7.1.</b>
|
||
|
||
自定义指标 HPA
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.8" data-path="admission-controller.html">
|
||
|
||
<a href="admission-controller.html">
|
||
|
||
|
||
<b>3.6.8.</b>
|
||
|
||
准入控制器(Admission Controller)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.7" data-path="service-discovery.html">
|
||
|
||
<a href="service-discovery.html">
|
||
|
||
|
||
<b>3.7.</b>
|
||
|
||
服务发现
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.7.1" data-path="service.html">
|
||
|
||
<a href="service.html">
|
||
|
||
|
||
<b>3.7.1.</b>
|
||
|
||
Service
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.7.2" data-path="ingress.html">
|
||
|
||
<a href="ingress.html">
|
||
|
||
|
||
<b>3.7.2.</b>
|
||
|
||
Ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.7.2.1" data-path="traefik-ingress-controller.html">
|
||
|
||
<a href="traefik-ingress-controller.html">
|
||
|
||
|
||
<b>3.7.2.1.</b>
|
||
|
||
Traefik Ingress Controller
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.8" data-path="authentication-and-permission.html">
|
||
|
||
<a href="authentication-and-permission.html">
|
||
|
||
|
||
<b>3.8.</b>
|
||
|
||
身份与权限控制
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.8.1" data-path="serviceaccount.html">
|
||
|
||
<a href="serviceaccount.html">
|
||
|
||
|
||
<b>3.8.1.</b>
|
||
|
||
ServiceAccount
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.8.2" data-path="rbac.html">
|
||
|
||
<a href="rbac.html">
|
||
|
||
|
||
<b>3.8.2.</b>
|
||
|
||
RBAC—— 基于角色的访问控制
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.8.3" data-path="network-policy.html">
|
||
|
||
<a href="network-policy.html">
|
||
|
||
|
||
<b>3.8.3.</b>
|
||
|
||
NetworkPolicy
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9" data-path="storage.html">
|
||
|
||
<a href="storage.html">
|
||
|
||
|
||
<b>3.9.</b>
|
||
|
||
存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.9.1" data-path="secret.html">
|
||
|
||
<a href="secret.html">
|
||
|
||
|
||
<b>3.9.1.</b>
|
||
|
||
Secret
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9.2" data-path="configmap.html">
|
||
|
||
<a href="configmap.html">
|
||
|
||
|
||
<b>3.9.2.</b>
|
||
|
||
ConfigMap
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.9.2.1" data-path="configmap-hot-update.html">
|
||
|
||
<a href="configmap-hot-update.html">
|
||
|
||
|
||
<b>3.9.2.1.</b>
|
||
|
||
ConfigMap 的热更新
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9.3" data-path="volume.html">
|
||
|
||
<a href="volume.html">
|
||
|
||
|
||
<b>3.9.3.</b>
|
||
|
||
Volume
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9.4" data-path="persistent-volume.html">
|
||
|
||
<a href="persistent-volume.html">
|
||
|
||
|
||
<b>3.9.4.</b>
|
||
|
||
Persistent Volume(持久化卷)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9.5" data-path="storageclass.html">
|
||
|
||
<a href="storageclass.html">
|
||
|
||
|
||
<b>3.9.5.</b>
|
||
|
||
Storage Class
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9.6" data-path="local-persistent-storage.html">
|
||
|
||
<a href="local-persistent-storage.html">
|
||
|
||
|
||
<b>3.9.6.</b>
|
||
|
||
本地持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.10" data-path="extension.html">
|
||
|
||
<a href="extension.html">
|
||
|
||
|
||
<b>3.10.</b>
|
||
|
||
集群扩展
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.10.1" data-path="custom-resource.html">
|
||
|
||
<a href="custom-resource.html">
|
||
|
||
|
||
<b>3.10.1.</b>
|
||
|
||
使用自定义资源扩展 API
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.10.2" data-path="crd.html">
|
||
|
||
<a href="crd.html">
|
||
|
||
|
||
<b>3.10.2.</b>
|
||
|
||
使用 CRD 扩展 Kubernetes API
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.10.3" data-path="aggregated-api-server.html">
|
||
|
||
<a href="aggregated-api-server.html">
|
||
|
||
|
||
<b>3.10.3.</b>
|
||
|
||
Aggregated API Server
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.10.4" data-path="apiservice.html">
|
||
|
||
<a href="apiservice.html">
|
||
|
||
|
||
<b>3.10.4.</b>
|
||
|
||
APIService
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.10.5" data-path="service-catalog.html">
|
||
|
||
<a href="service-catalog.html">
|
||
|
||
|
||
<b>3.10.5.</b>
|
||
|
||
Service Catalog
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.11" data-path="scheduling.html">
|
||
|
||
<a href="scheduling.html">
|
||
|
||
|
||
<b>3.11.</b>
|
||
|
||
资源调度
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.11.1" data-path="qos.html">
|
||
|
||
<a href="qos.html">
|
||
|
||
|
||
<b>3.11.1.</b>
|
||
|
||
QoS(服务质量等级)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">用户指南</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="4.1" data-path="../guide/">
|
||
|
||
<a href="../guide/">
|
||
|
||
|
||
<b>4.1.</b>
|
||
|
||
用户指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2" data-path="../guide/resource-configuration.html">
|
||
|
||
<a href="../guide/resource-configuration.html">
|
||
|
||
|
||
<b>4.2.</b>
|
||
|
||
资源对象配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.2.1" data-path="../guide/configure-liveness-readiness-probes.html">
|
||
|
||
<a href="../guide/configure-liveness-readiness-probes.html">
|
||
|
||
|
||
<b>4.2.1.</b>
|
||
|
||
配置 Pod 的 liveness 和 readiness 探针
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.2" data-path="../guide/configure-pod-service-account.html">
|
||
|
||
<a href="../guide/configure-pod-service-account.html">
|
||
|
||
|
||
<b>4.2.2.</b>
|
||
|
||
配置 Pod 的 Service Account
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.3" data-path="../guide/secret-configuration.html">
|
||
|
||
<a href="../guide/secret-configuration.html">
|
||
|
||
|
||
<b>4.2.3.</b>
|
||
|
||
Secret 配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.4" data-path="../guide/resource-quota-management.html">
|
||
|
||
<a href="../guide/resource-quota-management.html">
|
||
|
||
|
||
<b>4.2.4.</b>
|
||
|
||
管理 namespace 中的资源配额
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3" data-path="../guide/command-usage.html">
|
||
|
||
<a href="../guide/command-usage.html">
|
||
|
||
|
||
<b>4.3.</b>
|
||
|
||
命令使用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.3.1" data-path="../guide/docker-cli-to-kubectl.html">
|
||
|
||
<a href="../guide/docker-cli-to-kubectl.html">
|
||
|
||
|
||
<b>4.3.1.</b>
|
||
|
||
Docker 用户过渡到 kubectl 命令行指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.2" data-path="../guide/using-kubectl.html">
|
||
|
||
<a href="../guide/using-kubectl.html">
|
||
|
||
|
||
<b>4.3.2.</b>
|
||
|
||
kubectl 命令概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.3" data-path="../guide/kubectl-cheatsheet.html">
|
||
|
||
<a href="../guide/kubectl-cheatsheet.html">
|
||
|
||
|
||
<b>4.3.3.</b>
|
||
|
||
kubectl 命令技巧大全
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.4" data-path="../guide/using-etcdctl-to-access-kubernetes-data.html">
|
||
|
||
<a href="../guide/using-etcdctl-to-access-kubernetes-data.html">
|
||
|
||
|
||
<b>4.3.4.</b>
|
||
|
||
使用 etcdctl 访问 kubernetes 数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4" data-path="../guide/cluster-security-management.html">
|
||
|
||
<a href="../guide/cluster-security-management.html">
|
||
|
||
|
||
<b>4.4.</b>
|
||
|
||
集群安全性管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.4.1" data-path="../guide/managing-tls-in-a-cluster.html">
|
||
|
||
<a href="../guide/managing-tls-in-a-cluster.html">
|
||
|
||
|
||
<b>4.4.1.</b>
|
||
|
||
管理集群中的 TLS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.2" data-path="../guide/kubelet-authentication-authorization.html">
|
||
|
||
<a href="../guide/kubelet-authentication-authorization.html">
|
||
|
||
|
||
<b>4.4.2.</b>
|
||
|
||
kubelet 的认证授权
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.3" data-path="../guide/tls-bootstrapping.html">
|
||
|
||
<a href="../guide/tls-bootstrapping.html">
|
||
|
||
|
||
<b>4.4.3.</b>
|
||
|
||
TLS Bootstrap
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.4" data-path="../guide/kubectl-user-authentication-authorization.html">
|
||
|
||
<a href="../guide/kubectl-user-authentication-authorization.html">
|
||
|
||
|
||
<b>4.4.4.</b>
|
||
|
||
创建用户认证授权的 kubeconfig 文件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.5" data-path="../guide/ip-masq-agent.html">
|
||
|
||
<a href="../guide/ip-masq-agent.html">
|
||
|
||
|
||
<b>4.4.5.</b>
|
||
|
||
IP 伪装代理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.6" data-path="../guide/auth-with-kubeconfig-or-token.html">
|
||
|
||
<a href="../guide/auth-with-kubeconfig-or-token.html">
|
||
|
||
|
||
<b>4.4.6.</b>
|
||
|
||
使用 kubeconfig 或 token 进行用户身份认证
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.7" data-path="../guide/authentication.html">
|
||
|
||
<a href="../guide/authentication.html">
|
||
|
||
|
||
<b>4.4.7.</b>
|
||
|
||
Kubernetes 中的用户与身份认证授权
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.8" data-path="../guide/kubernetes-security-best-practice.html">
|
||
|
||
<a href="../guide/kubernetes-security-best-practice.html">
|
||
|
||
|
||
<b>4.4.8.</b>
|
||
|
||
Kubernetes 集群安全性配置最佳实践
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5" data-path="../guide/access-kubernetes-cluster.html">
|
||
|
||
<a href="../guide/access-kubernetes-cluster.html">
|
||
|
||
|
||
<b>4.5.</b>
|
||
|
||
访问 Kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.5.1" data-path="../guide/access-cluster.html">
|
||
|
||
<a href="../guide/access-cluster.html">
|
||
|
||
|
||
<b>4.5.1.</b>
|
||
|
||
访问集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.2" data-path="../guide/authenticate-across-clusters-kubeconfig.html">
|
||
|
||
<a href="../guide/authenticate-across-clusters-kubeconfig.html">
|
||
|
||
|
||
<b>4.5.2.</b>
|
||
|
||
使用 kubeconfig 文件配置跨集群认证
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.3" data-path="../guide/connecting-to-applications-port-forward.html">
|
||
|
||
<a href="../guide/connecting-to-applications-port-forward.html">
|
||
|
||
|
||
<b>4.5.3.</b>
|
||
|
||
通过端口转发访问集群中的应用程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.4" data-path="../guide/service-access-application-cluster.html">
|
||
|
||
<a href="../guide/service-access-application-cluster.html">
|
||
|
||
|
||
<b>4.5.4.</b>
|
||
|
||
使用 service 访问群集中的应用程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.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>4.5.5.</b>
|
||
|
||
从外部访问 Kubernetes 中的 Pod
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.6" data-path="../guide/cabin-mobile-dashboard-for-kubernetes.html">
|
||
|
||
<a href="../guide/cabin-mobile-dashboard-for-kubernetes.html">
|
||
|
||
|
||
<b>4.5.6.</b>
|
||
|
||
Cabin - Kubernetes 手机客户端
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.7" data-path="../guide/kubernetes-desktop-client.html">
|
||
|
||
<a href="../guide/kubernetes-desktop-client.html">
|
||
|
||
|
||
<b>4.5.7.</b>
|
||
|
||
Lens - Kubernetes IDE/桌面客户端
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.8" data-path="../guide/kubernator-kubernetes-ui.html">
|
||
|
||
<a href="../guide/kubernator-kubernetes-ui.html">
|
||
|
||
|
||
<b>4.5.8.</b>
|
||
|
||
Kubernator - 更底层的 Kubernetes UI
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6" data-path="../guide/application-development-deployment-flow.html">
|
||
|
||
<a href="../guide/application-development-deployment-flow.html">
|
||
|
||
|
||
<b>4.6.</b>
|
||
|
||
在 Kubernetes 中开发部署应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.6.1" data-path="../guide/deploy-applications-in-kubernetes.html">
|
||
|
||
<a href="../guide/deploy-applications-in-kubernetes.html">
|
||
|
||
|
||
<b>4.6.1.</b>
|
||
|
||
适用于 kubernetes 的应用开发部署流程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6.2" data-path="../guide/migrating-hadoop-yarn-to-kubernetes.html">
|
||
|
||
<a href="../guide/migrating-hadoop-yarn-to-kubernetes.html">
|
||
|
||
|
||
<b>4.6.2.</b>
|
||
|
||
迁移传统应用到 Kubernetes 中 —— 以 Hadoop YARN 为例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6.3" data-path="../guide/using-statefulset.html">
|
||
|
||
<a href="../guide/using-statefulset.html">
|
||
|
||
|
||
<b>4.6.3.</b>
|
||
|
||
使用 StatefulSet 部署用状态应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">最佳实践</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="5.1" data-path="../practice/">
|
||
|
||
<a href="../practice/">
|
||
|
||
|
||
<b>5.1.</b>
|
||
|
||
最佳实践概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2" data-path="../practice/install-kubernetes-on-centos.html">
|
||
|
||
<a href="../practice/install-kubernetes-on-centos.html">
|
||
|
||
|
||
<b>5.2.</b>
|
||
|
||
在 CentOS 上部署 Kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.2.1" data-path="../practice/create-tls-and-secret-key.html">
|
||
|
||
<a href="../practice/create-tls-and-secret-key.html">
|
||
|
||
|
||
<b>5.2.1.</b>
|
||
|
||
创建 TLS 证书和秘钥
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.2" data-path="../practice/create-kubeconfig.html">
|
||
|
||
<a href="../practice/create-kubeconfig.html">
|
||
|
||
|
||
<b>5.2.2.</b>
|
||
|
||
创建 kubeconfig 文件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.3" data-path="../practice/etcd-cluster-installation.html">
|
||
|
||
<a href="../practice/etcd-cluster-installation.html">
|
||
|
||
|
||
<b>5.2.3.</b>
|
||
|
||
创建高可用 etcd 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.4" data-path="../practice/kubectl-installation.html">
|
||
|
||
<a href="../practice/kubectl-installation.html">
|
||
|
||
|
||
<b>5.2.4.</b>
|
||
|
||
安装 kubectl 命令行工具
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.5" data-path="../practice/master-installation.html">
|
||
|
||
<a href="../practice/master-installation.html">
|
||
|
||
|
||
<b>5.2.5.</b>
|
||
|
||
部署 master 节点
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.6" data-path="../practice/flannel-installation.html">
|
||
|
||
<a href="../practice/flannel-installation.html">
|
||
|
||
|
||
<b>5.2.6.</b>
|
||
|
||
安装 flannel 网络插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.7" data-path="../practice/node-installation.html">
|
||
|
||
<a href="../practice/node-installation.html">
|
||
|
||
|
||
<b>5.2.7.</b>
|
||
|
||
部署 node 节点
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.8" data-path="../practice/kubedns-addon-installation.html">
|
||
|
||
<a href="../practice/kubedns-addon-installation.html">
|
||
|
||
|
||
<b>5.2.8.</b>
|
||
|
||
安装 kubedns 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.9" data-path="../practice/dashboard-addon-installation.html">
|
||
|
||
<a href="../practice/dashboard-addon-installation.html">
|
||
|
||
|
||
<b>5.2.9.</b>
|
||
|
||
安装 dashboard 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.10" data-path="../practice/heapster-addon-installation.html">
|
||
|
||
<a href="../practice/heapster-addon-installation.html">
|
||
|
||
|
||
<b>5.2.10.</b>
|
||
|
||
安装 heapster 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.11" data-path="../practice/efk-addon-installation.html">
|
||
|
||
<a href="../practice/efk-addon-installation.html">
|
||
|
||
|
||
<b>5.2.11.</b>
|
||
|
||
安装 EFK 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.3" data-path="../practice/install-kubernetes-with-kubeadm.html">
|
||
|
||
<a href="../practice/install-kubernetes-with-kubeadm.html">
|
||
|
||
|
||
<b>5.3.</b>
|
||
|
||
生产级的 Kubernetes 简化管理工具 kubeadm
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.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>5.3.1.</b>
|
||
|
||
使用 kubeadm 在 Ubuntu Server 16.04 上快速构建测试集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4" data-path="../practice/service-discovery-and-loadbalancing.html">
|
||
|
||
<a href="../practice/service-discovery-and-loadbalancing.html">
|
||
|
||
|
||
<b>5.4.</b>
|
||
|
||
服务发现与负载均衡
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.4.1" data-path="../practice/traefik-ingress-installation.html">
|
||
|
||
<a href="../practice/traefik-ingress-installation.html">
|
||
|
||
|
||
<b>5.4.1.</b>
|
||
|
||
安装 Traefik ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.2" data-path="../practice/distributed-load-test.html">
|
||
|
||
<a href="../practice/distributed-load-test.html">
|
||
|
||
|
||
<b>5.4.2.</b>
|
||
|
||
分布式负载测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.3" data-path="../practice/network-and-cluster-perfermance-test.html">
|
||
|
||
<a href="../practice/network-and-cluster-perfermance-test.html">
|
||
|
||
|
||
<b>5.4.3.</b>
|
||
|
||
网络和集群性能测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.4" data-path="../practice/edge-node-configuration.html">
|
||
|
||
<a href="../practice/edge-node-configuration.html">
|
||
|
||
|
||
<b>5.4.4.</b>
|
||
|
||
边缘节点配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.5" data-path="../practice/nginx-ingress-installation.html">
|
||
|
||
<a href="../practice/nginx-ingress-installation.html">
|
||
|
||
|
||
<b>5.4.5.</b>
|
||
|
||
安装 Nginx ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.6" data-path="../practice/dns-installation.html">
|
||
|
||
<a href="../practice/dns-installation.html">
|
||
|
||
|
||
<b>5.4.6.</b>
|
||
|
||
安装配置 DNS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.4.6.1" data-path="../practice/configuring-dns.html">
|
||
|
||
<a href="../practice/configuring-dns.html">
|
||
|
||
|
||
<b>5.4.6.1.</b>
|
||
|
||
安装配置 Kube-dns
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.6.2" data-path="../practice/coredns.html">
|
||
|
||
<a href="../practice/coredns.html">
|
||
|
||
|
||
<b>5.4.6.2.</b>
|
||
|
||
安装配置 CoreDNS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5" data-path="../practice/operation.html">
|
||
|
||
<a href="../practice/operation.html">
|
||
|
||
|
||
<b>5.5.</b>
|
||
|
||
运维管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.5.1" data-path="../practice/master-ha.html">
|
||
|
||
<a href="../practice/master-ha.html">
|
||
|
||
|
||
<b>5.5.1.</b>
|
||
|
||
Master 节点高可用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.2" data-path="../practice/service-rolling-update.html">
|
||
|
||
<a href="../practice/service-rolling-update.html">
|
||
|
||
|
||
<b>5.5.2.</b>
|
||
|
||
服务滚动升级
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.3" data-path="../practice/app-log-collection.html">
|
||
|
||
<a href="../practice/app-log-collection.html">
|
||
|
||
|
||
<b>5.5.3.</b>
|
||
|
||
应用日志收集
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.4" data-path="../practice/configuration-best-practice.html">
|
||
|
||
<a href="../practice/configuration-best-practice.html">
|
||
|
||
|
||
<b>5.5.4.</b>
|
||
|
||
配置最佳实践
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.5" data-path="../practice/monitor.html">
|
||
|
||
<a href="../practice/monitor.html">
|
||
|
||
|
||
<b>5.5.5.</b>
|
||
|
||
集群及应用监控
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.6" data-path="../practice/data-persistence-problem.html">
|
||
|
||
<a href="../practice/data-persistence-problem.html">
|
||
|
||
|
||
<b>5.5.6.</b>
|
||
|
||
数据持久化问题
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.7" data-path="../practice/manage-compute-resources-container.html">
|
||
|
||
<a href="../practice/manage-compute-resources-container.html">
|
||
|
||
|
||
<b>5.5.7.</b>
|
||
|
||
管理容器的计算资源
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.8" data-path="../practice/federation.html">
|
||
|
||
<a href="../practice/federation.html">
|
||
|
||
|
||
<b>5.5.8.</b>
|
||
|
||
集群联邦
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6" data-path="../practice/storage.html">
|
||
|
||
<a href="../practice/storage.html">
|
||
|
||
|
||
<b>5.6.</b>
|
||
|
||
存储管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.1" data-path="../practice/glusterfs.html">
|
||
|
||
<a href="../practice/glusterfs.html">
|
||
|
||
|
||
<b>5.6.1.</b>
|
||
|
||
GlusterFS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.1.1" data-path="../practice/using-glusterfs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-glusterfs-for-persistent-storage.html">
|
||
|
||
|
||
<b>5.6.1.1.</b>
|
||
|
||
使用 GlusterFS 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.1.2" data-path="../practice/using-heketi-gluster-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-heketi-gluster-for-persistent-storage.html">
|
||
|
||
|
||
<b>5.6.1.2.</b>
|
||
|
||
使用 Heketi 作为 Kubernetes 的持久存储 GlusterFS 的 external provisioner
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.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>5.6.1.3.</b>
|
||
|
||
在 OpenShift 中使用 GlusterFS 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.2" data-path="../practice/glusterd-2.0.html">
|
||
|
||
<a href="../practice/glusterd-2.0.html">
|
||
|
||
|
||
<b>5.6.2.</b>
|
||
|
||
GlusterD-2.0
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.3" data-path="../practice/ceph.html">
|
||
|
||
<a href="../practice/ceph.html">
|
||
|
||
|
||
<b>5.6.3.</b>
|
||
|
||
Ceph
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.3.1" data-path="../practice/ceph-helm-install-guide-zh.html">
|
||
|
||
<a href="../practice/ceph-helm-install-guide-zh.html">
|
||
|
||
|
||
<b>5.6.3.1.</b>
|
||
|
||
用 Helm 托管安装 Ceph 集群并提供后端存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.3.2" data-path="../practice/using-ceph-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-ceph-for-persistent-storage.html">
|
||
|
||
|
||
<b>5.6.3.2.</b>
|
||
|
||
使用 Ceph 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.3.3" data-path="../practice/rbd-provisioner.html">
|
||
|
||
<a href="../practice/rbd-provisioner.html">
|
||
|
||
|
||
<b>5.6.3.3.</b>
|
||
|
||
使用 rbd-provisioner 提供 rbd 持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.4" data-path="../practice/openebs.html">
|
||
|
||
<a href="../practice/openebs.html">
|
||
|
||
|
||
<b>5.6.4.</b>
|
||
|
||
OpenEBS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.4.1" data-path="../practice/using-openebs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-openebs-for-persistent-storage.html">
|
||
|
||
|
||
<b>5.6.4.1.</b>
|
||
|
||
使用 OpenEBS 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.5" data-path="../practice/rook.html">
|
||
|
||
<a href="../practice/rook.html">
|
||
|
||
|
||
<b>5.6.5.</b>
|
||
|
||
Rook
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.6" data-path="../practice/nfs.html">
|
||
|
||
<a href="../practice/nfs.html">
|
||
|
||
|
||
<b>5.6.6.</b>
|
||
|
||
NFS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.6.1" data-path="../practice/using-nfs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-nfs-for-persistent-storage.html">
|
||
|
||
|
||
<b>5.6.6.1.</b>
|
||
|
||
利用 NFS 动态提供 Kubernetes 后端存储卷
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.7" data-path="../practice/monitoring.html">
|
||
|
||
<a href="../practice/monitoring.html">
|
||
|
||
|
||
<b>5.7.</b>
|
||
|
||
集群与应用监控
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.7.1" data-path="../practice/heapster.html">
|
||
|
||
<a href="../practice/heapster.html">
|
||
|
||
|
||
<b>5.7.1.</b>
|
||
|
||
Heapster
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.7.1.1" data-path="../practice/using-heapster-to-get-object-metrics.html">
|
||
|
||
<a href="../practice/using-heapster-to-get-object-metrics.html">
|
||
|
||
|
||
<b>5.7.1.1.</b>
|
||
|
||
使用 Heapster 获取集群和对象的 metric 数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.7.2" data-path="../practice/prometheus.html">
|
||
|
||
<a href="../practice/prometheus.html">
|
||
|
||
|
||
<b>5.7.2.</b>
|
||
|
||
Prometheus
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.7.2.1" data-path="../practice/using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
||
<a href="../practice/using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
||
|
||
<b>5.7.2.1.</b>
|
||
|
||
使用 Prometheus 监控 kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.7.2.2" data-path="../practice/promql.html">
|
||
|
||
<a href="../practice/promql.html">
|
||
|
||
|
||
<b>5.7.2.2.</b>
|
||
|
||
Prometheus 查询语言 PromQL 使用说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.7.3" data-path="../practice/vistio-visualize-your-istio-mesh.html">
|
||
|
||
<a href="../practice/vistio-visualize-your-istio-mesh.html">
|
||
|
||
|
||
<b>5.7.3.</b>
|
||
|
||
使用 Vistio 监控 Istio 服务网格中的流量
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.8" data-path="../practice/distributed-tracing.html">
|
||
|
||
<a href="../practice/distributed-tracing.html">
|
||
|
||
|
||
<b>5.8.</b>
|
||
|
||
分布式跟踪
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.8.1" data-path="../practice/opentracing.html">
|
||
|
||
<a href="../practice/opentracing.html">
|
||
|
||
|
||
<b>5.8.1.</b>
|
||
|
||
OpenTracing
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.9" data-path="../practice/services-management-tool.html">
|
||
|
||
<a href="../practice/services-management-tool.html">
|
||
|
||
|
||
<b>5.9.</b>
|
||
|
||
服务编排管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.9.1" data-path="../practice/helm.html">
|
||
|
||
<a href="../practice/helm.html">
|
||
|
||
|
||
<b>5.9.1.</b>
|
||
|
||
使用 Helm 管理 Kubernetes 应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.9.2" data-path="../practice/create-private-charts-repo.html">
|
||
|
||
<a href="../practice/create-private-charts-repo.html">
|
||
|
||
|
||
<b>5.9.2.</b>
|
||
|
||
构建私有 Chart 仓库
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.10" data-path="../practice/ci-cd.html">
|
||
|
||
<a href="../practice/ci-cd.html">
|
||
|
||
|
||
<b>5.10.</b>
|
||
|
||
持续集成与发布
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.10.1" data-path="../practice/jenkins-ci-cd.html">
|
||
|
||
<a href="../practice/jenkins-ci-cd.html">
|
||
|
||
|
||
<b>5.10.1.</b>
|
||
|
||
使用 Jenkins 进行持续集成与发布
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.10.2" data-path="../practice/drone-ci-cd.html">
|
||
|
||
<a href="../practice/drone-ci-cd.html">
|
||
|
||
|
||
<b>5.10.2.</b>
|
||
|
||
使用 Drone 进行持续集成与发布
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.11" data-path="../practice/update-and-upgrade.html">
|
||
|
||
<a href="../practice/update-and-upgrade.html">
|
||
|
||
|
||
<b>5.11.</b>
|
||
|
||
更新与升级
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.11.1" data-path="../practice/manually-upgrade.html">
|
||
|
||
<a href="../practice/manually-upgrade.html">
|
||
|
||
|
||
<b>5.11.1.</b>
|
||
|
||
手动升级 Kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.11.2" data-path="../practice/dashboard-upgrade.html">
|
||
|
||
<a href="../practice/dashboard-upgrade.html">
|
||
|
||
|
||
<b>5.11.2.</b>
|
||
|
||
升级 dashboard
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.12" data-path="../practice/controller-extended.html">
|
||
|
||
<a href="../practice/controller-extended.html">
|
||
|
||
|
||
<b>5.12.</b>
|
||
|
||
扩展控制器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.12.1" data-path="../practice/openkruise.html">
|
||
|
||
<a href="../practice/openkruise.html">
|
||
|
||
|
||
<b>5.12.1.</b>
|
||
|
||
OpenKruise
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.12.1.1" data-path="../practice/in-place-update.html">
|
||
|
||
<a href="../practice/in-place-update.html">
|
||
|
||
|
||
<b>5.12.1.1.</b>
|
||
|
||
原地升级
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">领域应用</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="6.1" data-path="../usecases/">
|
||
|
||
<a href="../usecases/">
|
||
|
||
|
||
<b>6.1.</b>
|
||
|
||
领域应用概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2" data-path="../usecases/microservices.html">
|
||
|
||
<a href="../usecases/microservices.html">
|
||
|
||
|
||
<b>6.2.</b>
|
||
|
||
微服务架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.2.1" data-path="../usecases/service-discovery-in-microservices.html">
|
||
|
||
<a href="../usecases/service-discovery-in-microservices.html">
|
||
|
||
|
||
<b>6.2.1.</b>
|
||
|
||
微服务中的服务发现
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.2" data-path="../usecases/microservices-for-java-developers.html">
|
||
|
||
<a href="../usecases/microservices-for-java-developers.html">
|
||
|
||
|
||
<b>6.2.2.</b>
|
||
|
||
使用 Java 构建微服务并发布到 Kubernetes 平台
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.2.2.1" data-path="../usecases/spring-boot-quick-start-guide.html">
|
||
|
||
<a href="../usecases/spring-boot-quick-start-guide.html">
|
||
|
||
|
||
<b>6.2.2.1.</b>
|
||
|
||
Spring Boot 快速开始指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3" data-path="../usecases/observability.html">
|
||
|
||
<a href="../usecases/observability.html">
|
||
|
||
|
||
<b>6.3.</b>
|
||
|
||
可观察性
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4" data-path="../usecases/service-mesh.html">
|
||
|
||
<a href="../usecases/service-mesh.html">
|
||
|
||
|
||
<b>6.4.</b>
|
||
|
||
Service Mesh 服务网格
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.4.1" data-path="../usecases/the-enterprise-path-to-service-mesh-architectures.html">
|
||
|
||
<a href="../usecases/the-enterprise-path-to-service-mesh-architectures.html">
|
||
|
||
|
||
<b>6.4.1.</b>
|
||
|
||
企业级服务网格架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.4.1.1" data-path="../usecases/service-mesh-fundamental.html">
|
||
|
||
<a href="../usecases/service-mesh-fundamental.html">
|
||
|
||
|
||
<b>6.4.1.1.</b>
|
||
|
||
Service Mesh 基础
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.1.2" data-path="../usecases/comparing-service-mesh-technologies.html">
|
||
|
||
<a href="../usecases/comparing-service-mesh-technologies.html">
|
||
|
||
|
||
<b>6.4.1.2.</b>
|
||
|
||
Service Mesh 技术对比
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.1.3" data-path="../usecases/service-mesh-adoption-and-evolution.html">
|
||
|
||
<a href="../usecases/service-mesh-adoption-and-evolution.html">
|
||
|
||
|
||
<b>6.4.1.3.</b>
|
||
|
||
采纳和演进
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.1.4" data-path="../usecases/service-mesh-customization-and-integration.html">
|
||
|
||
<a href="../usecases/service-mesh-customization-and-integration.html">
|
||
|
||
|
||
<b>6.4.1.4.</b>
|
||
|
||
定制和集成
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.1.5" data-path="../usecases/service-mesh-conclusion.html">
|
||
|
||
<a href="../usecases/service-mesh-conclusion.html">
|
||
|
||
|
||
<b>6.4.1.5.</b>
|
||
|
||
总结
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.2" data-path="../usecases/istio.html">
|
||
|
||
<a href="../usecases/istio.html">
|
||
|
||
|
||
<b>6.4.2.</b>
|
||
|
||
Istio
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.4.2.1" data-path="../usecases/istio-installation.html">
|
||
|
||
<a href="../usecases/istio-installation.html">
|
||
|
||
|
||
<b>6.4.2.1.</b>
|
||
|
||
安装并试用 Istio service mesh
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.2.2" data-path="../usecases/sidecar-spec-in-istio.html">
|
||
|
||
<a href="../usecases/sidecar-spec-in-istio.html">
|
||
|
||
|
||
<b>6.4.2.2.</b>
|
||
|
||
Istio 中 sidecar 的注入规范及示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.2.3" data-path="../usecases/istio-community-tips.html">
|
||
|
||
<a href="../usecases/istio-community-tips.html">
|
||
|
||
|
||
<b>6.4.2.3.</b>
|
||
|
||
如何参与 Istio 社区及注意事项
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.2.4" data-path="../usecases/istio-tutorials-collection.html">
|
||
|
||
<a href="../usecases/istio-tutorials-collection.html">
|
||
|
||
|
||
<b>6.4.2.4.</b>
|
||
|
||
Istio 免费学习资源汇总
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.2.5" data-path="../usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html">
|
||
|
||
<a href="../usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html">
|
||
|
||
|
||
<b>6.4.2.5.</b>
|
||
|
||
Sidecar 的注入与流量劫持
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.2.6" data-path="../usecases/envoy-sidecar-routing-of-istio-service-mesh-deep-dive.html">
|
||
|
||
<a href="../usecases/envoy-sidecar-routing-of-istio-service-mesh-deep-dive.html">
|
||
|
||
|
||
<b>6.4.2.6.</b>
|
||
|
||
Envoy Sidecar 代理的路由转发
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.2.7" data-path="../usecases/how-to-integrate-istio-with-vm.html">
|
||
|
||
<a href="../usecases/how-to-integrate-istio-with-vm.html">
|
||
|
||
|
||
<b>6.4.2.7.</b>
|
||
|
||
Istio 如何支持虚拟机
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.2.8" data-path="../usecases/istio-vm-support.html">
|
||
|
||
<a href="../usecases/istio-vm-support.html">
|
||
|
||
|
||
<b>6.4.2.8.</b>
|
||
|
||
Istio 支持虚拟机的历史
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.3" data-path="../usecases/linkerd.html">
|
||
|
||
<a href="../usecases/linkerd.html">
|
||
|
||
|
||
<b>6.4.3.</b>
|
||
|
||
Linkerd
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.4.3.1" data-path="../usecases/linkerd-user-guide.html">
|
||
|
||
<a href="../usecases/linkerd-user-guide.html">
|
||
|
||
|
||
<b>6.4.3.1.</b>
|
||
|
||
Linkerd 使用指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.4" data-path="../usecases/conduit.html">
|
||
|
||
<a href="../usecases/conduit.html">
|
||
|
||
|
||
<b>6.4.4.</b>
|
||
|
||
Conduit
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.4.4.1" data-path="../usecases/conduit-overview.html">
|
||
|
||
<a href="../usecases/conduit-overview.html">
|
||
|
||
|
||
<b>6.4.4.1.</b>
|
||
|
||
Condiut 概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.4.2" data-path="../usecases/conduit-installation.html">
|
||
|
||
<a href="../usecases/conduit-installation.html">
|
||
|
||
|
||
<b>6.4.4.2.</b>
|
||
|
||
安装 Conduit
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.5" data-path="../usecases/envoy.html">
|
||
|
||
<a href="../usecases/envoy.html">
|
||
|
||
|
||
<b>6.4.5.</b>
|
||
|
||
Envoy
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.4.5.1" data-path="../usecases/envoy-terminology.html">
|
||
|
||
<a href="../usecases/envoy-terminology.html">
|
||
|
||
|
||
<b>6.4.5.1.</b>
|
||
|
||
Envoy 的架构与基本术语
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.5.2" data-path="../usecases/envoy-front-proxy.html">
|
||
|
||
<a href="../usecases/envoy-front-proxy.html">
|
||
|
||
|
||
<b>6.4.5.2.</b>
|
||
|
||
Envoy 作为前端代理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.5.3" data-path="../usecases/envoy-mesh-in-kubernetes-tutorial.html">
|
||
|
||
<a href="../usecases/envoy-mesh-in-kubernetes-tutorial.html">
|
||
|
||
|
||
<b>6.4.5.3.</b>
|
||
|
||
Envoy mesh 教程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.6" data-path="../usecases/mosn.html">
|
||
|
||
<a href="../usecases/mosn.html">
|
||
|
||
|
||
<b>6.4.6.</b>
|
||
|
||
MOSN
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5" data-path="../usecases/big-data.html">
|
||
|
||
<a href="../usecases/big-data.html">
|
||
|
||
|
||
<b>6.5.</b>
|
||
|
||
大数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.5.1" data-path="../usecases/spark-standalone-on-kubernetes.html">
|
||
|
||
<a href="../usecases/spark-standalone-on-kubernetes.html">
|
||
|
||
|
||
<b>6.5.1.</b>
|
||
|
||
Spark standalone on Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.2" data-path="../usecases/running-spark-with-kubernetes-native-scheduler.html">
|
||
|
||
<a href="../usecases/running-spark-with-kubernetes-native-scheduler.html">
|
||
|
||
|
||
<b>6.5.2.</b>
|
||
|
||
运行支持 Kubernetes 原生调度的 Spark 程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6" data-path="../usecases/serverless.html">
|
||
|
||
<a href="../usecases/serverless.html">
|
||
|
||
|
||
<b>6.6.</b>
|
||
|
||
Serverless 架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.1" data-path="../usecases/understanding-serverless.html">
|
||
|
||
<a href="../usecases/understanding-serverless.html">
|
||
|
||
|
||
<b>6.6.1.</b>
|
||
|
||
理解 Serverless
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.2" data-path="../usecases/faas.html">
|
||
|
||
<a href="../usecases/faas.html">
|
||
|
||
|
||
<b>6.6.2.</b>
|
||
|
||
FaaS(函数即服务)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.2.1" data-path="../usecases/openfaas-quick-start.html">
|
||
|
||
<a href="../usecases/openfaas-quick-start.html">
|
||
|
||
|
||
<b>6.6.2.1.</b>
|
||
|
||
OpenFaaS 快速入门指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.3" data-path="../usecases/knative.html">
|
||
|
||
<a href="../usecases/knative.html">
|
||
|
||
|
||
<b>6.6.3.</b>
|
||
|
||
Knative
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.7" data-path="../usecases/edge-computing.html">
|
||
|
||
<a href="../usecases/edge-computing.html">
|
||
|
||
|
||
<b>6.7.</b>
|
||
|
||
边缘计算
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.8" data-path="../usecases/ai.html">
|
||
|
||
<a href="../usecases/ai.html">
|
||
|
||
|
||
<b>6.8.</b>
|
||
|
||
人工智能
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">开发指南</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="7.1" data-path="../develop/">
|
||
|
||
<a href="../develop/">
|
||
|
||
|
||
<b>7.1.</b>
|
||
|
||
开发指南概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2" data-path="../develop/sigs-and-working-group.html">
|
||
|
||
<a href="../develop/sigs-and-working-group.html">
|
||
|
||
|
||
<b>7.2.</b>
|
||
|
||
SIG 和工作组
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3" data-path="../develop/developing-environment.html">
|
||
|
||
<a href="../develop/developing-environment.html">
|
||
|
||
|
||
<b>7.3.</b>
|
||
|
||
开发环境搭建
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="7.3.1" data-path="../develop/using-vagrant-and-virtualbox-for-development.html">
|
||
|
||
<a href="../develop/using-vagrant-and-virtualbox-for-development.html">
|
||
|
||
|
||
<b>7.3.1.</b>
|
||
|
||
本地分布式开发环境搭建(使用 Vagrant 和 Virtualbox)
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.4" data-path="../develop/testing.html">
|
||
|
||
<a href="../develop/testing.html">
|
||
|
||
|
||
<b>7.4.</b>
|
||
|
||
单元测试和集成测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.5" data-path="../develop/client-go-sample.html">
|
||
|
||
<a href="../develop/client-go-sample.html">
|
||
|
||
|
||
<b>7.5.</b>
|
||
|
||
client-go 示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.6" data-path="../develop/operator.html">
|
||
|
||
<a href="../develop/operator.html">
|
||
|
||
|
||
<b>7.6.</b>
|
||
|
||
Operator
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="7.6.1" data-path="../develop/operator-sdk.html">
|
||
|
||
<a href="../develop/operator-sdk.html">
|
||
|
||
|
||
<b>7.6.1.</b>
|
||
|
||
operator-sdk
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.7" data-path="../develop/kubebuilder.html">
|
||
|
||
<a href="../develop/kubebuilder.html">
|
||
|
||
|
||
<b>7.7.</b>
|
||
|
||
kubebuilder
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="7.7.1" data-path="../develop/kubebuilder-example.html">
|
||
|
||
<a href="../develop/kubebuilder-example.html">
|
||
|
||
|
||
<b>7.7.1.</b>
|
||
|
||
使用 kubebuilder 创建 operator 示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.8" data-path="../develop/advance-developer.html">
|
||
|
||
<a href="../develop/advance-developer.html">
|
||
|
||
|
||
<b>7.8.</b>
|
||
|
||
高级开发指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.9" data-path="../develop/contribute.html">
|
||
|
||
<a href="../develop/contribute.html">
|
||
|
||
|
||
<b>7.9.</b>
|
||
|
||
社区贡献
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.10" data-path="../develop/minikube.html">
|
||
|
||
<a href="../develop/minikube.html">
|
||
|
||
|
||
<b>7.10.</b>
|
||
|
||
Minikube
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">CNCF(云原生计算基金会)</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="8.1" data-path="../cloud-native/cncf.html">
|
||
|
||
<a href="../cloud-native/cncf.html">
|
||
|
||
|
||
<b>8.1.</b>
|
||
|
||
CNCF - 云原生计算基金会简介
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.2" data-path="../cloud-native/cncf-charter.html">
|
||
|
||
<a href="../cloud-native/cncf-charter.html">
|
||
|
||
|
||
<b>8.2.</b>
|
||
|
||
CNCF 章程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.3" data-path="../cloud-native/cncf-sig.html">
|
||
|
||
<a href="../cloud-native/cncf-sig.html">
|
||
|
||
|
||
<b>8.3.</b>
|
||
|
||
CNCF 特别兴趣小组(SIG)说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.4" data-path="../cloud-native/cncf-sandbox-criteria.html">
|
||
|
||
<a href="../cloud-native/cncf-sandbox-criteria.html">
|
||
|
||
|
||
<b>8.4.</b>
|
||
|
||
开源项目加入 CNCF Sandbox 的要求
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.5" data-path="../cloud-native/cncf-project-governing.html">
|
||
|
||
<a href="../cloud-native/cncf-project-governing.html">
|
||
|
||
|
||
<b>8.5.</b>
|
||
|
||
CNCF 中的项目治理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.6" data-path="../cloud-native/cncf-ambassador.html">
|
||
|
||
<a href="../cloud-native/cncf-ambassador.html">
|
||
|
||
|
||
<b>8.6.</b>
|
||
|
||
CNCF Ambassador
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">附录</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="9.1" data-path="../appendix/">
|
||
|
||
<a href="../appendix/">
|
||
|
||
|
||
<b>9.1.</b>
|
||
|
||
附录说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.2" data-path="../appendix/debug-kubernetes-services.html">
|
||
|
||
<a href="../appendix/debug-kubernetes-services.html">
|
||
|
||
|
||
<b>9.2.</b>
|
||
|
||
Kubernetes 中的应用故障排查
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.3" data-path="../appendix/material-share.html">
|
||
|
||
<a href="../appendix/material-share.html">
|
||
|
||
|
||
<b>9.3.</b>
|
||
|
||
Kubernetes 相关资讯和情报链接
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.4" data-path="../appendix/docker-best-practice.html">
|
||
|
||
<a href="../appendix/docker-best-practice.html">
|
||
|
||
|
||
<b>9.4.</b>
|
||
|
||
Docker 最佳实践
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.5" data-path="../appendix/tricks.html">
|
||
|
||
<a href="../appendix/tricks.html">
|
||
|
||
|
||
<b>9.5.</b>
|
||
|
||
使用技巧
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.6" data-path="../appendix/issues.html">
|
||
|
||
<a href="../appendix/issues.html">
|
||
|
||
|
||
<b>9.6.</b>
|
||
|
||
问题记录
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7" data-path="../appendix/kubernetes-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-changelog.html">
|
||
|
||
|
||
<b>9.7.</b>
|
||
|
||
Kubernetes 版本更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.7.1" data-path="../appendix/kubernetes-1.7-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.7-changelog.html">
|
||
|
||
|
||
<b>9.7.1.</b>
|
||
|
||
Kubernetes1.7 更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7.2" data-path="../appendix/kubernetes-1.8-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.8-changelog.html">
|
||
|
||
|
||
<b>9.7.2.</b>
|
||
|
||
Kubernetes1.8 更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7.3" data-path="../appendix/kubernetes-1.9-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.9-changelog.html">
|
||
|
||
|
||
<b>9.7.3.</b>
|
||
|
||
Kubernetes1.9 更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7.4" data-path="../appendix/kubernetes-1.10-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.10-changelog.html">
|
||
|
||
|
||
<b>9.7.4.</b>
|
||
|
||
Kubernetes1.10 更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7.5" data-path="../appendix/kubernetes-1.11-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.11-changelog.html">
|
||
|
||
|
||
<b>9.7.5.</b>
|
||
|
||
Kubernetes1.11 更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7.6" data-path="../appendix/kubernetes-1.12-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.12-changelog.html">
|
||
|
||
|
||
<b>9.7.6.</b>
|
||
|
||
Kubernetes1.12 更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7.7" data-path="../appendix/kubernetes-1.13-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.13-changelog.html">
|
||
|
||
|
||
<b>9.7.7.</b>
|
||
|
||
Kubernetes1.13 更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7.8" data-path="../appendix/kubernetes-1.14-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.14-changelog.html">
|
||
|
||
|
||
<b>9.7.8.</b>
|
||
|
||
Kubernetes1.14 更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7.9" data-path="../appendix/kubernetes-1.15-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.15-changelog.html">
|
||
|
||
|
||
<b>9.7.9.</b>
|
||
|
||
Kubernetes1.15 更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7.10" data-path="../appendix/kubernetes-1.16-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.16-changelog.html">
|
||
|
||
|
||
<b>9.7.10.</b>
|
||
|
||
Kubernetes1.16 更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7.11" data-path="../appendix/kubernetes-1.17-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.17-changelog.html">
|
||
|
||
|
||
<b>9.7.11.</b>
|
||
|
||
Kubernetes1.17 更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.8" data-path="../appendix/summary-and-outlook.html">
|
||
|
||
<a href="../appendix/summary-and-outlook.html">
|
||
|
||
|
||
<b>9.8.</b>
|
||
|
||
Kubernetes 及云原生年度总结及展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.8.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>9.8.1.</b>
|
||
|
||
Kubernetes 与云原生 2017 年年终总结及 2018 年展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.8.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>9.8.2.</b>
|
||
|
||
Kubernetes 与云原生 2018 年年终总结及 2019 年展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.9" data-path="../appendix/cncf-annual-report.html">
|
||
|
||
<a href="../appendix/cncf-annual-report.html">
|
||
|
||
|
||
<b>9.9.</b>
|
||
|
||
CNCF 年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.9.1" data-path="../appendix/cncf-annual-report-2018.html">
|
||
|
||
<a href="../appendix/cncf-annual-report-2018.html">
|
||
|
||
|
||
<b>9.9.1.</b>
|
||
|
||
CNCF 2018 年年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.10" data-path="../appendix/about-kcsp.html">
|
||
|
||
<a href="../appendix/about-kcsp.html">
|
||
|
||
|
||
<b>9.10.</b>
|
||
|
||
Kubernetes 认证服务提供商(KCSP)说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.11" data-path="../appendix/about-cka-candidate.html">
|
||
|
||
<a href="../appendix/about-cka-candidate.html">
|
||
|
||
|
||
<b>9.11.</b>
|
||
|
||
认证 Kubernetes 管理员(CKA)说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</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=".." >Deployment</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="deployment">Deployment</h1>
|
||
<p>Deployment 为 Pod 和 ReplicaSet 提供了一个声明式定义(declarative)方法,用来替代以前的 ReplicationController 来方便的管理应用。典型的应用场景包括:</p>
|
||
<ul>
|
||
<li>定义 Deployment 来创建 Pod 和 ReplicaSet</li>
|
||
<li>滚动升级和回滚应用</li>
|
||
<li>扩容和缩容</li>
|
||
<li>暂停和继续 Deployment</li>
|
||
</ul>
|
||
<p>比如一个简单的 nginx 应用可以定义为:</p>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> extensions/v1beta1
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> Deployment
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> nginx<span class="token punctuation">-</span>deployment
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">replicas</span><span class="token punctuation">:</span> <span class="token number">3</span>
|
||
<span class="token key atrule">template</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">labels</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">app</span><span class="token punctuation">:</span> nginx
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">containers</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">name</span><span class="token punctuation">:</span> nginx
|
||
<span class="token key atrule">image</span><span class="token punctuation">:</span> nginx<span class="token punctuation">:</span>1.7.9
|
||
<span class="token key atrule">ports</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">containerPort</span><span class="token punctuation">:</span> <span class="token number">80</span>
|
||
</code></pre>
|
||
<p>扩容:</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl scale deployment nginx-deployment --replicas <span class="token number">10</span>
|
||
</code></pre>
|
||
<p>如果集群支持 horizontal pod autoscaling 的话,还可以为 Deployment 设置自动扩展:</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl autoscale deployment nginx-deployment --min<span class="token operator">=</span><span class="token number">10</span> --max<span class="token operator">=</span><span class="token number">15</span> --cpu-percent<span class="token operator">=</span><span class="token number">80</span>
|
||
</code></pre>
|
||
<p>更新镜像也比较简单:</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl <span class="token builtin class-name">set</span> image deployment/nginx-deployment <span class="token assign-left variable">nginx</span><span class="token operator">=</span>nginx:1.9.1
|
||
</code></pre>
|
||
<p>回滚:</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl rollout undo deployment/nginx-deployment
|
||
</code></pre>
|
||
<h2 id="deployment-结构示意图">Deployment 结构示意图</h2>
|
||
<figure id="fig3.6.1.1"><a href="../images/deployment-cheatsheet.png" data-lightbox="a91908cd-96ce-4930-ab58-02bcdaeead78" data-title="kubernetes deployment cheatsheet"><img src="../images/deployment-cheatsheet.png" alt="kubernetes deployment cheatsheet"></a><figcaption>图 3.6.1.1:kubernetes deployment cheatsheet</figcaption></figure>
|
||
<h2 id="deployment-概念详细解析">Deployment 概念详细解析</h2>
|
||
<p>本文翻译自 kubernetes 官方文档:<a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment" target="_blank">https://kubernetes.io/docs/concepts/workloads/controllers/deployment</a></p>
|
||
<p>根据 2017 年 5 月 10 日的 Commit 8481c02 翻译。</p>
|
||
<h2 id="deployment-是什么?">Deployment 是什么?</h2>
|
||
<p>Deployment 为 Pod 和 Replica Set(下一代 Replication Controller)提供声明式更新。</p>
|
||
<p>您只需要在 Deployment 中描述您想要的目标状态是什么,Deployment controller 就会帮您将 Pod 和 ReplicaSet 的实际状态改变到您的目标状态。您可以定义一个全新的 Deployment 来创建 ReplicaSet 或者删除已有的 Deployment 并创建一个新的来替换。</p>
|
||
<p><strong>注意</strong>:您不该手动管理由 Deployment 创建的 ReplicaSet,否则您就篡越了 Deployment controller 的职责!下文罗列了 Deployment 对象中已经覆盖了所有的用例。如果未有覆盖您所有需要的用例,请直接在 Kubernetes 的代码库中提 issue。</p>
|
||
<p>典型的用例如下:</p>
|
||
<ul>
|
||
<li>使用 Deployment 来创建 ReplicaSet。ReplicaSet 在后台创建 pod。检查启动状态,看它是成功还是失败。</li>
|
||
<li>然后,通过更新 Deployment 的 PodTemplateSpec 字段来声明 Pod 的新状态。这会创建一个新的 ReplicaSet,Deployment 会按照控制的速率将 pod 从旧的 ReplicaSet 移动到新的 ReplicaSet 中。</li>
|
||
<li>如果当前状态不稳定,回滚到之前的 Deployment revision。每次回滚都会更新 Deployment 的 revision。</li>
|
||
<li>扩容 Deployment 以满足更高的负载。</li>
|
||
<li>暂停 Deployment 来应用 PodTemplateSpec 的多个修复,然后恢复上线。</li>
|
||
<li>根据 Deployment 的状态判断上线是否 hang 住了。</li>
|
||
<li>清除旧的不必要的 ReplicaSet。</li>
|
||
</ul>
|
||
<h2 id="创建-deployment">创建 Deployment</h2>
|
||
<p>下面是一个 Deployment 示例,它创建了一个 ReplicaSet 来启动 3 个 nginx pod。</p>
|
||
<p>下载示例文件并执行命令:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl create -f https://kubernetes.io/docs/user-guide/nginx-deployment.yaml --record
|
||
deployment <span class="token string">"nginx-deployment"</span> created
|
||
</code></pre>
|
||
<p>将 kubectl 的<code>--record</code>的 flag 设置为<code>true</code> 可以在 annotation 中记录当前命令创建或者升级了该资源。这在未来会很有用,例如,查看在每个 Deployment revision 中执行了哪些命令。</p>
|
||
<p>然后立即执行 <code>get</code> 将获得如下结果:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get deployments
|
||
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
||
nginx-deployment <span class="token number">3</span> <span class="token number">0</span> <span class="token number">0</span> <span class="token number">0</span> 1s
|
||
</code></pre>
|
||
<p>输出结果表明我们希望的 repalica 数是 3(根据 deployment 中的<code>.spec.replicas</code>配置)当前 replica 数(<code>.status.replicas</code>)是 0, 最新的 replica 数(<code>.status.updatedReplicas</code>)是 0,可用的 replica 数(<code>.status.availableReplicas</code>)是 0。</p>
|
||
<p>过几秒后再执行 <code>get</code> 命令,将获得如下输出:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get deployments
|
||
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
||
nginx-deployment <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> 18s
|
||
</code></pre>
|
||
<p>我们可以看到 Deployment 已经创建了 3 个 replica,所有的 replica 都已经是最新的了(包含最新的 pod template),可用的(根据 Deployment 中的<code>.spec.minReadySeconds</code>声明,处于已就绪状态的 pod 的最少个数)。执行<code>kubectl get rs</code>和<code>kubectl get pods</code>会显示 Replica Set(RS)和 Pod 已创建。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get rs
|
||
NAME DESIRED CURRENT READY AGE
|
||
nginx-deployment-2035384211 <span class="token number">3</span> <span class="token number">3</span> <span class="token number">0</span> 18s
|
||
</code></pre>
|
||
<p>您可能会注意到 ReplicaSet 的名字总是<code><span class="token tag"><span class="token tag"><span class="token punctuation"><</span>Deployment</span> <span class="token attr-name">的名字</span><span class="token punctuation">></span></span>-<span class="token tag"><span class="token tag"><span class="token punctuation"><</span>pod</span> <span class="token attr-name">template</span> <span class="token attr-name">的</span> <span class="token attr-name">hash</span> <span class="token attr-name">值</span><span class="token punctuation">></span></span></code>。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get pods --show-labels
|
||
NAME READY STATUS RESTARTS AGE LABELS
|
||
nginx-deployment-2035384211-7ci7o <span class="token number">1</span>/1 Running <span class="token number">0</span> 18s <span class="token assign-left variable">app</span><span class="token operator">=</span>nginx,pod-template-hash<span class="token operator">=</span><span class="token number">2035384211</span>
|
||
nginx-deployment-2035384211-kzszj <span class="token number">1</span>/1 Running <span class="token number">0</span> 18s <span class="token assign-left variable">app</span><span class="token operator">=</span>nginx,pod-template-hash<span class="token operator">=</span><span class="token number">2035384211</span>
|
||
nginx-deployment-2035384211-qqcnn <span class="token number">1</span>/1 Running <span class="token number">0</span> 18s <span class="token assign-left variable">app</span><span class="token operator">=</span>nginx,pod-template-hash<span class="token operator">=</span><span class="token number">2035384211</span>
|
||
</code></pre>
|
||
<p>刚创建的 Replica Set 将保证总是有 3 个 nginx 的 pod 存在。</p>
|
||
<p><strong>注意:</strong> 您必须在 Deployment 中的 selector 指定正确的 pod template label(在该示例中是 <code>app = nginx</code>),不要跟其他的 controller 的 selector 中指定的 pod template label 搞混了(包括 Deployment、Replica Set、Replication Controller 等)。<strong>Kubernetes 本身并不会阻止您任意指定 pod template label</strong>,但是如果您真的这么做了,这些 controller 之间会相互打架,并可能导致不正确的行为。</p>
|
||
<h3 id="pod-template-hash-label">Pod-template-hash label</h3>
|
||
<p><strong>注意</strong>:这个 label 不是用户指定的!</p>
|
||
<p>注意上面示例输出中的 pod label 里的 pod-template-hash label。当 Deployment 创建或者接管 ReplicaSet 时,Deployment controller 会自动为 Pod 添加 pod-template-hash label。这样做的目的是防止 Deployment 的子 ReplicaSet 的 pod 名字重复。通过将 ReplicaSet 的 PodTemplate 进行哈希散列,使用生成的哈希值作为 label 的值,并添加到 ReplicaSet selector 里、 pod template label 和 ReplicaSet 管理中的 Pod 上。</p>
|
||
<h2 id="更新-deployment">更新 Deployment</h2>
|
||
<p><strong>注意:</strong>Deployment 的 rollout 当且仅当 Deployment 的 pod template(例如 <code>.spec.template</code>)中的 label 更新或者镜像更改时被触发。其他更新,例如扩容 Deployment 不会触发 rollout。</p>
|
||
<p>假如我们现在想要让 nginx pod 使用 <code>nginx:1.9.1</code> 的镜像来代替原来的 <code>nginx:1.7.9</code> 的镜像。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl <span class="token builtin class-name">set</span> image deployment/nginx-deployment <span class="token assign-left variable">nginx</span><span class="token operator">=</span>nginx:1.9.1
|
||
deployment <span class="token string">"nginx-deployment"</span> image updated
|
||
</code></pre>
|
||
<p>我们可以使用<code>edit</code>命令来编辑 Deployment,修改<code>.spec.template.spec.containers [0].image</code>,将<code>nginx:1.7.9</code>改写成<code>nginx:1.9.1</code>。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl edit deployment/nginx-deployment
|
||
deployment <span class="token string">"nginx-deployment"</span> edited
|
||
</code></pre>
|
||
<p>查看 rollout 的状态,只要执行:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl rollout status deployment/nginx-deployment
|
||
Waiting <span class="token keyword">for</span> rollout to finish: <span class="token number">2</span> out of <span class="token number">3</span> new replicas have been updated<span class="token punctuation">..</span>.
|
||
deployment <span class="token string">"nginx-deployment"</span> successfully rolled out
|
||
</code></pre>
|
||
<p>Rollout 成功后,<code>get</code>Deployment:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get deployments
|
||
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
||
nginx-deployment <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> 36s
|
||
</code></pre>
|
||
<p>UP-TO-DATE 的 replica 的数目已经达到了配置中要求的数目。</p>
|
||
<p>CURRENT 的 replica 数表示 Deployment 管理的 replica 数量,AVAILABLE 的 replica 数是当前可用的 replica 数量。</p>
|
||
<p>我们通过执行 <code>kubectl get rs</code> 可以看到 Deployment 更新了 Pod,通过创建一个新的 ReplicaSet 并扩容了 3 个 replica,同时将原来的 ReplicaSet 缩容到了 0 个 replica。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get rs
|
||
NAME DESIRED CURRENT READY AGE
|
||
nginx-deployment-1564180365 <span class="token number">3</span> <span class="token number">3</span> <span class="token number">0</span> 6s
|
||
nginx-deployment-2035384211 <span class="token number">0</span> <span class="token number">0</span> <span class="token number">0</span> 36s
|
||
</code></pre>
|
||
<p>执行<code>get pods</code>只会看到当前的新的 pod:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get pods
|
||
NAME READY STATUS RESTARTS AGE
|
||
nginx-deployment-1564180365-khku8 <span class="token number">1</span>/1 Running <span class="token number">0</span> 14s
|
||
nginx-deployment-1564180365-nacti <span class="token number">1</span>/1 Running <span class="token number">0</span> 14s
|
||
nginx-deployment-1564180365-z9gth <span class="token number">1</span>/1 Running <span class="token number">0</span> 14s
|
||
</code></pre>
|
||
<p>下次更新这些 pod 的时候,只需要更新 Deployment 中的 pod 的 template 即可。</p>
|
||
<p>Deployment 可以保证在升级时只有一定数量的 Pod 是 down 的。默认的,它会确保至少有比期望的 Pod 数量少一个是 up 状态(最多一个不可用)。</p>
|
||
<p>Deployment 同时也可以确保只创建出超过期望数量的一定数量的 Pod。默认的,它会确保最多比期望的 Pod 数量多一个的 Pod 是 up 的(最多 1 个 surge )。</p>
|
||
<p><strong>在未来的 Kuberentes 版本中,将从 1-1 变成 25%-25%。</strong></p>
|
||
<p>例如,如果您自己看下上面的 Deployment,您会发现,开始创建一个新的 Pod,然后删除一些旧的 Pod 再创建一个新的。当新的 Pod 创建出来之前不会杀掉旧的 Pod。这样能够确保可用的 Pod 数量至少有 2 个,Pod 的总数最多 4 个。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl describe deployments
|
||
Name: nginx-deployment
|
||
Namespace: default
|
||
CreationTimestamp: Tue, <span class="token number">15</span> Mar <span class="token number">2016</span> <span class="token number">12</span>:01:06 -0700
|
||
Labels: <span class="token assign-left variable">app</span><span class="token operator">=</span>nginx
|
||
Selector: <span class="token assign-left variable">app</span><span class="token operator">=</span>nginx
|
||
Replicas: <span class="token number">3</span> updated <span class="token operator">|</span> <span class="token number">3</span> total <span class="token operator">|</span> <span class="token number">3</span> available <span class="token operator">|</span> <span class="token number">0</span> unavailable
|
||
StrategyType: RollingUpdate
|
||
MinReadySeconds: <span class="token number">0</span>
|
||
RollingUpdateStrategy: <span class="token number">1</span> max unavailable, <span class="token number">1</span> max surge
|
||
OldReplicaSets: <span class="token operator"><</span>none<span class="token operator">></span>
|
||
NewReplicaSet: nginx-deployment-1564180365 <span class="token punctuation">(</span><span class="token number">3</span>/3 replicas created<span class="token punctuation">)</span>
|
||
Events:
|
||
FirstSeen LastSeen Count From SubobjectPath Type Reason Message
|
||
--------- -------- ----- ---- ------------- -------- ------ -------
|
||
36s 36s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-2035384211 to <span class="token number">3</span>
|
||
23s 23s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-1564180365 to <span class="token number">1</span>
|
||
23s 23s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled down replica <span class="token builtin class-name">set</span> nginx-deployment-2035384211 to <span class="token number">2</span>
|
||
23s 23s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-1564180365 to <span class="token number">2</span>
|
||
21s 21s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled down replica <span class="token builtin class-name">set</span> nginx-deployment-2035384211 to <span class="token number">0</span>
|
||
21s 21s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-1564180365 to <span class="token number">3</span>
|
||
</code></pre>
|
||
<p>我们可以看到当我们刚开始创建这个 Deployment 的时候,创建了一个 ReplicaSet(nginx-deployment-2035384211),并直接扩容到了 3 个 replica。</p>
|
||
<p>当我们更新这个 Deployment 的时候,它会创建一个新的 ReplicaSet(nginx-deployment-1564180365),将它扩容到 1 个 replica,然后缩容原先的 ReplicaSet 到 2 个 replica,此时满足至少 2 个 Pod 是可用状态,同一时刻最多有 4 个 Pod 处于创建的状态。</p>
|
||
<p>接着继续使用相同的 rolling update 策略扩容新的 ReplicaSet 和缩容旧的 ReplicaSet。最终,将会在新的 ReplicaSet 中有 3 个可用的 replica,旧的 ReplicaSet 的 replica 数目变成 0。</p>
|
||
<h3 id="rollover(多个-rollout-并行)">Rollover(多个 rollout 并行)</h3>
|
||
<p>每当 Deployment controller 观测到有新的 deployment 被创建时,如果没有已存在的 ReplicaSet 来创建期望个数的 Pod 的话,就会创建出一个新的 ReplicaSet 来做这件事。已存在的 ReplicaSet 控制 label 与 <code>.spec.selector</code> 匹配但是 template 跟 <code>.spec.template</code> 不匹配的 Pod 缩容。最终,新的 ReplicaSet 将会扩容出 <code>.spec.replicas</code> 指定数目的 Pod,旧的 ReplicaSet 会缩容到 0。</p>
|
||
<p>如果您更新了一个的已存在并正在进行中的 Deployment,每次更新 Deployment 都会创建一个新的 ReplicaSet 并扩容它,同时回滚之前扩容的 ReplicaSet —— 将它添加到旧的 ReplicaSet 列表中,开始缩容。</p>
|
||
<p>例如,假如您创建了一个有 5 个 <code>niginx:1.7.9</code> replica 的 Deployment,但是当还只有 3 个 <code>nginx:1.7.9</code> 的 replica 创建出来的时候您就开始更新含有 5 个 <code>nginx:1.9.1</code> replica 的 Deployment。在这种情况下,Deployment 会立即杀掉已创建的 3 个 <code>nginx:1.7.9</code> 的 Pod,并开始创建 <code>nginx:1.9.1</code> 的 Pod。它不会等到所有的 5 个 <code>nginx:1.7.9</code> 的 Pod 都创建完成后才开始改变航道。</p>
|
||
<h3 id="label-selector-更新">Label selector 更新</h3>
|
||
<p>我们通常不鼓励更新 label selector,我们建议事先规划好您的 selector。</p>
|
||
<p>任何情况下,只要您想要执行 label selector 的更新,请一定要谨慎并确认您已经预料到所有可能因此导致的后果。</p>
|
||
<ul>
|
||
<li>增添 selector 需要同时在 Deployment 的 spec 中更新新的 label,否则将返回校验错误。此更改是不可覆盖的,这意味着新的 selector 不会选择使用旧 selector 创建的 ReplicaSet 和 Pod,从而导致所有旧版本的 ReplicaSet 都被丢弃,并创建新的 ReplicaSet。</li>
|
||
<li>更新 selector,即更改 selector key 的当前值,将导致跟增添 selector 同样的后果。</li>
|
||
<li>删除 selector,即删除 Deployment selector 中的已有的 key,不需要对 Pod template label 做任何更改,现有的 ReplicaSet 也不会成为孤儿,但是请注意,删除的 label 仍然存在于现有的 Pod 和 ReplicaSet 中。</li>
|
||
</ul>
|
||
<h2 id="回退-deployment">回退 Deployment</h2>
|
||
<p>有时候您可能想回退一个 Deployment,例如,当 Deployment 不稳定时,比如一直 crash looping。</p>
|
||
<p>默认情况下,kubernetes 会在系统中保存前两次的 Deployment 的 rollout 历史记录,以便您可以随时回退(您可以修改 <code>revision history limit</code> 来更改保存的 revision 数)。</p>
|
||
<p><strong>注意:</strong>只要 Deployment 的 rollout 被触发就会创建一个 revision。也就是说当且仅当 Deployment 的 Pod template(如 <code>.spec.template</code>)被更改,例如更新 template 中的 label 和容器镜像时,就会创建出一个新的 revision。</p>
|
||
<p>其他的更新,比如扩容 Deployment 不会创建 revision—— 因此我们可以很方便的手动或者自动扩容。这意味着当您回退到历史 revision 时,只有 Deployment 中的 Pod template 部分才会回退。</p>
|
||
<p>假设我们在更新 Deployment 的时候犯了一个拼写错误,将镜像的名字写成了 <code>nginx:1.91</code>,而正确的名字应该是 <code>nginx:1.9.1</code>:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl <span class="token builtin class-name">set</span> image deployment/nginx-deployment <span class="token assign-left variable">nginx</span><span class="token operator">=</span>nginx:1.91
|
||
deployment <span class="token string">"nginx-deployment"</span> image updated
|
||
</code></pre>
|
||
<p>Rollout 将会卡住。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl rollout status deployments nginx-deployment
|
||
Waiting <span class="token keyword">for</span> rollout to finish: <span class="token number">2</span> out of <span class="token number">3</span> new replicas have been updated<span class="token punctuation">..</span>.
|
||
</code></pre>
|
||
<p>按住 Ctrl-C 停止上面的 rollout 状态监控。</p>
|
||
<p>您会看到旧的 replica(nginx-deployment-1564180365 和 nginx-deployment-2035384211)和新的 replica (nginx-deployment-3066724191)数目都是 2 个。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get rs
|
||
NAME DESIRED CURRENT READY AGE
|
||
nginx-deployment-1564180365 <span class="token number">2</span> <span class="token number">2</span> <span class="token number">0</span> 25s
|
||
nginx-deployment-2035384211 <span class="token number">0</span> <span class="token number">0</span> <span class="token number">0</span> 36s
|
||
nginx-deployment-3066724191 <span class="token number">2</span> <span class="token number">2</span> <span class="token number">2</span> 6s
|
||
</code></pre>
|
||
<p>看下创建 Pod,您会看到有两个新的 ReplicaSet 创建的 Pod 处于 ImagePullBackOff 状态,循环拉取镜像。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get pods
|
||
NAME READY STATUS RESTARTS AGE
|
||
nginx-deployment-1564180365-70iae <span class="token number">1</span>/1 Running <span class="token number">0</span> 25s
|
||
nginx-deployment-1564180365-jbqqo <span class="token number">1</span>/1 Running <span class="token number">0</span> 25s
|
||
nginx-deployment-3066724191-08mng <span class="token number">0</span>/1 ImagePullBackOff <span class="token number">0</span> 6s
|
||
nginx-deployment-3066724191-eocby <span class="token number">0</span>/1 ImagePullBackOff <span class="token number">0</span> 6s
|
||
</code></pre>
|
||
<p>注意,Deployment controller 会自动停止坏的 rollout,并停止扩容新的 ReplicaSet。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl describe deployment
|
||
Name: nginx-deployment
|
||
Namespace: default
|
||
CreationTimestamp: Tue, <span class="token number">15</span> Mar <span class="token number">2016</span> <span class="token number">14</span>:48:04 -0700
|
||
Labels: <span class="token assign-left variable">app</span><span class="token operator">=</span>nginx
|
||
Selector: <span class="token assign-left variable">app</span><span class="token operator">=</span>nginx
|
||
Replicas: <span class="token number">2</span> updated <span class="token operator">|</span> <span class="token number">3</span> total <span class="token operator">|</span> <span class="token number">2</span> available <span class="token operator">|</span> <span class="token number">2</span> unavailable
|
||
StrategyType: RollingUpdate
|
||
MinReadySeconds: <span class="token number">0</span>
|
||
RollingUpdateStrategy: <span class="token number">1</span> max unavailable, <span class="token number">1</span> max surge
|
||
OldReplicaSets: nginx-deployment-1564180365 <span class="token punctuation">(</span><span class="token number">2</span>/2 replicas created<span class="token punctuation">)</span>
|
||
NewReplicaSet: nginx-deployment-3066724191 <span class="token punctuation">(</span><span class="token number">2</span>/2 replicas created<span class="token punctuation">)</span>
|
||
Events:
|
||
FirstSeen LastSeen Count From SubobjectPath Type Reason Message
|
||
--------- -------- ----- ---- ------------- -------- ------ -------
|
||
1m 1m <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-2035384211 to <span class="token number">3</span>
|
||
22s 22s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-1564180365 to <span class="token number">1</span>
|
||
22s 22s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled down replica <span class="token builtin class-name">set</span> nginx-deployment-2035384211 to <span class="token number">2</span>
|
||
22s 22s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-1564180365 to <span class="token number">2</span>
|
||
21s 21s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled down replica <span class="token builtin class-name">set</span> nginx-deployment-2035384211 to <span class="token number">0</span>
|
||
21s 21s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-1564180365 to <span class="token number">3</span>
|
||
13s 13s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-3066724191 to <span class="token number">1</span>
|
||
13s 13s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled down replica <span class="token builtin class-name">set</span> nginx-deployment-1564180365 to <span class="token number">2</span>
|
||
13s 13s <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-3066724191 to <span class="token number">2</span>
|
||
</code></pre>
|
||
<p>为了修复这个问题,我们需要回退到稳定的 Deployment revision。</p>
|
||
<h3 id="检查-deployment-升级的历史记录">检查 Deployment 升级的历史记录</h3>
|
||
<p>首先,检查下 Deployment 的 revision:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl rollout <span class="token function">history</span> deployment/nginx-deployment
|
||
deployments <span class="token string">"nginx-deployment"</span><span class="token builtin class-name">:</span>
|
||
REVISION CHANGE-CAUSE
|
||
<span class="token number">1</span> kubectl create -f https://kubernetes.io/docs/user-guide/nginx-deployment.yaml--record
|
||
<span class="token number">2</span> kubectl <span class="token builtin class-name">set</span> image deployment/nginx-deployment <span class="token assign-left variable">nginx</span><span class="token operator">=</span>nginx:1.9.1
|
||
<span class="token number">3</span> kubectl <span class="token builtin class-name">set</span> image deployment/nginx-deployment <span class="token assign-left variable">nginx</span><span class="token operator">=</span>nginx:1.91
|
||
</code></pre>
|
||
<p>因为我们创建 Deployment 的时候使用了<code>--record</code> 参数可以记录命令,我们可以很方便的查看每次 revision 的变化。</p>
|
||
<p>查看单个 revision 的详细信息:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl rollout <span class="token function">history</span> deployment/nginx-deployment --revision<span class="token operator">=</span><span class="token number">2</span>
|
||
deployments <span class="token string">"nginx-deployment"</span> revision <span class="token number">2</span>
|
||
Labels: <span class="token assign-left variable">app</span><span class="token operator">=</span>nginx
|
||
pod-template-hash<span class="token operator">=</span><span class="token number">1159050644</span>
|
||
Annotations: kubernetes.io/change-cause<span class="token operator">=</span>kubectl <span class="token builtin class-name">set</span> image deployment/nginx-deployment <span class="token assign-left variable">nginx</span><span class="token operator">=</span>nginx:1.9.1
|
||
Containers:
|
||
nginx:
|
||
Image: nginx:1.9.1
|
||
Port: <span class="token number">80</span>/TCP
|
||
QoS Tier:
|
||
cpu: BestEffort
|
||
memory: BestEffort
|
||
Environment Variables: <span class="token operator"><</span>none<span class="token operator">></span>
|
||
No volumes.
|
||
</code></pre>
|
||
<h3 id="回退到历史版本">回退到历史版本</h3>
|
||
<p>现在,我们可以决定回退当前的 rollout 到之前的版本:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl rollout undo deployment/nginx-deployment
|
||
deployment <span class="token string">"nginx-deployment"</span> rolled back
|
||
</code></pre>
|
||
<p>也可以使用<code>--revision</code>参数指定某个历史版本:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl rollout undo deployment/nginx-deployment --to-revision<span class="token operator">=</span><span class="token number">2</span>
|
||
deployment <span class="token string">"nginx-deployment"</span> rolled back
|
||
</code></pre>
|
||
<p>该 Deployment 现在已经回退到了先前的稳定版本。如您所见,Deployment controller 产生了一个回退到 revison 2 的<code>DeploymentRollback</code>的 event。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get deployment
|
||
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
||
nginx-deployment <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> 30m
|
||
|
||
$ kubectl describe deployment
|
||
Name: nginx-deployment
|
||
Namespace: default
|
||
CreationTimestamp: Tue, <span class="token number">15</span> Mar <span class="token number">2016</span> <span class="token number">14</span>:48:04 -0700
|
||
Labels: <span class="token assign-left variable">app</span><span class="token operator">=</span>nginx
|
||
Selector: <span class="token assign-left variable">app</span><span class="token operator">=</span>nginx
|
||
Replicas: <span class="token number">3</span> updated <span class="token operator">|</span> <span class="token number">3</span> total <span class="token operator">|</span> <span class="token number">3</span> available <span class="token operator">|</span> <span class="token number">0</span> unavailable
|
||
StrategyType: RollingUpdate
|
||
MinReadySeconds: <span class="token number">0</span>
|
||
RollingUpdateStrategy: <span class="token number">1</span> max unavailable, <span class="token number">1</span> max surge
|
||
OldReplicaSets: <span class="token operator"><</span>none<span class="token operator">></span>
|
||
NewReplicaSet: nginx-deployment-1564180365 <span class="token punctuation">(</span><span class="token number">3</span>/3 replicas created<span class="token punctuation">)</span>
|
||
Events:
|
||
FirstSeen LastSeen Count From SubobjectPath Type Reason Message
|
||
--------- -------- ----- ---- ------------- -------- ------ -------
|
||
30m 30m <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-2035384211 to <span class="token number">3</span>
|
||
29m 29m <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-1564180365 to <span class="token number">1</span>
|
||
29m 29m <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled down replica <span class="token builtin class-name">set</span> nginx-deployment-2035384211 to <span class="token number">2</span>
|
||
29m 29m <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-1564180365 to <span class="token number">2</span>
|
||
29m 29m <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled down replica <span class="token builtin class-name">set</span> nginx-deployment-2035384211 to <span class="token number">0</span>
|
||
29m 29m <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-3066724191 to <span class="token number">2</span>
|
||
29m 29m <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-3066724191 to <span class="token number">1</span>
|
||
29m 29m <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled down replica <span class="token builtin class-name">set</span> nginx-deployment-1564180365 to <span class="token number">2</span>
|
||
2m 2m <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled down replica <span class="token builtin class-name">set</span> nginx-deployment-3066724191 to <span class="token number">0</span>
|
||
2m 2m <span class="token number">1</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal DeploymentRollback Rolled back deployment <span class="token string">"nginx-deployment"</span> to revision <span class="token number">2</span>
|
||
29m 2m <span class="token number">2</span> <span class="token punctuation">{</span>deployment-controller<span class="token punctuation">}</span> Normal ScalingReplicaSet Scaled up replica <span class="token builtin class-name">set</span> nginx-deployment-1564180365 to <span class="token number">3</span>
|
||
</code></pre>
|
||
<h3 id="清理-policy">清理 Policy</h3>
|
||
<p>您可以通过设置 <code>.spec.revisonHistoryLimit</code> 项来指定 deployment 最多保留多少 revision 历史记录。默认的会保留所有的 revision;如果将该项设置为 0,Deployment 就不允许回退了。</p>
|
||
<h2 id="deployment-扩容">Deployment 扩容</h2>
|
||
<p>您可以使用以下命令扩容 Deployment:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl scale deployment nginx-deployment --replicas <span class="token number">10</span>
|
||
deployment <span class="token string">"nginx-deployment"</span> scaled
|
||
</code></pre>
|
||
<p>假设您的集群中启用了 <a href="https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough" target="_blank">horizontal pod autoscaling</a>,您可以给 Deployment 设置一个 autoscaler,基于当前 Pod 的 CPU 利用率选择最少和最多的 Pod 数。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl autoscale deployment nginx-deployment --min<span class="token operator">=</span><span class="token number">10</span> --max<span class="token operator">=</span><span class="token number">15</span> --cpu-percent<span class="token operator">=</span><span class="token number">80</span>
|
||
deployment <span class="token string">"nginx-deployment"</span> autoscaled
|
||
</code></pre>
|
||
<h3 id="比例扩容">比例扩容</h3>
|
||
<p>RollingUpdate Deployment 支持同时运行一个应用的多个版本。或者 autoscaler 扩 容 RollingUpdate Deployment 的时候,正在中途的 rollout(进行中或者已经暂停的),为了降低风险,Deployment controller 将会平衡已存在的活动中的 ReplicaSet(有 Pod 的 ReplicaSet)和新加入的 replica。这被称为比例扩容。</p>
|
||
<p>例如,您正在运行中含有 10 个 replica 的 Deployment。maxSurge=3,maxUnavailable=2。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get deploy
|
||
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
||
nginx-deployment <span class="token number">10</span> <span class="token number">10</span> <span class="token number">10</span> <span class="token number">10</span> 50s
|
||
</code></pre>
|
||
<p>您更新了一个镜像,而在集群内部无法解析。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl <span class="token builtin class-name">set</span> image deploy/nginx-deployment <span class="token assign-left variable">nginx</span><span class="token operator">=</span>nginx:sometag
|
||
deployment <span class="token string">"nginx-deployment"</span> image updated
|
||
</code></pre>
|
||
<p>镜像更新启动了一个包含 ReplicaSet nginx-deployment-1989198191 的新的 rollout,但是它被阻塞了,因为我们上面提到的 maxUnavailable。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get rs
|
||
NAME DESIRED CURRENT READY AGE
|
||
nginx-deployment-1989198191 <span class="token number">5</span> <span class="token number">5</span> <span class="token number">0</span> 9s
|
||
nginx-deployment-618515232 <span class="token number">8</span> <span class="token number">8</span> <span class="token number">8</span> 1m
|
||
</code></pre>
|
||
<p>然后发起了一个新的 Deployment 扩容请求。autoscaler 将 Deployment 的 repllica 数目增加到了 15 个。Deployment controller 需要判断在哪里增加这 5 个新的 replica。如果我们没有谁用比例扩容,所有的 5 个 replica 都会加到一个新的 ReplicaSet 中。如果使用比例扩容,新添加的 replica 将传播到所有的 ReplicaSet 中。大的部分加入 replica 数最多的 ReplicaSet 中,小的部分加入到 replica 数少的 ReplciaSet 中。0 个 replica 的 ReplicaSet 不会被扩容。</p>
|
||
<p>在我们上面的例子中,3 个 replica 将添加到旧的 ReplicaSet 中,2 个 replica 将添加到新的 ReplicaSet 中。rollout 进程最终会将所有的 replica 移动到新的 ReplicaSet 中,假设新的 replica 成为健康状态。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get deploy
|
||
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
||
nginx-deployment <span class="token number">15</span> <span class="token number">18</span> <span class="token number">7</span> <span class="token number">8</span> 7m
|
||
$ kubectl get rs
|
||
NAME DESIRED CURRENT READY AGE
|
||
nginx-deployment-1989198191 <span class="token number">7</span> <span class="token number">7</span> <span class="token number">0</span> 7m
|
||
nginx-deployment-618515232 <span class="token number">11</span> <span class="token number">11</span> <span class="token number">11</span> 7m
|
||
</code></pre>
|
||
<h2 id="删除-autoscale">删除 autoscale</h2>
|
||
<pre class="language-"><code class="lang-bash">kubectl get hpa
|
||
kubectl delete hpa <span class="token variable">${name of hpa}</span>
|
||
</code></pre>
|
||
<h2 id="暂停和恢复-deployment">暂停和恢复 Deployment</h2>
|
||
<p>您可以在发出一次或多次更新前暂停一个 Deployment,然后再恢复它。这样您就能在 Deployment 暂停期间进行多次修复工作,而不会发出不必要的 rollout。</p>
|
||
<p>例如使用刚刚创建 Deployment:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl get deploy
|
||
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
||
nginx <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> 1m
|
||
<span class="token punctuation">[</span>mkargaki@dhcp129-211 kubernetes<span class="token punctuation">]</span>$ kubectl get rs
|
||
NAME DESIRED CURRENT READY AGE
|
||
nginx-2142116321 <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> 1m
|
||
</code></pre>
|
||
<p>使用以下命令暂停 Deployment:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl rollout pause deployment/nginx-deployment
|
||
deployment <span class="token string">"nginx-deployment"</span> paused
|
||
</code></pre>
|
||
<p>然后更新 Deplyment 中的镜像:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl <span class="token builtin class-name">set</span> image deploy/nginx <span class="token assign-left variable">nginx</span><span class="token operator">=</span>nginx:1.9.1
|
||
deployment <span class="token string">"nginx-deployment"</span> image updated
|
||
</code></pre>
|
||
<p>注意新的 rollout 启动了:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl rollout <span class="token function">history</span> deploy/nginx
|
||
deployments <span class="token string">"nginx"</span>
|
||
REVISION CHANGE-CAUSE
|
||
<span class="token number">1</span> <span class="token operator"><</span>none<span class="token operator">></span>
|
||
|
||
$ kubectl get rs
|
||
NAME DESIRED CURRENT READY AGE
|
||
nginx-2142116321 <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> 2m
|
||
</code></pre>
|
||
<p>您可以进行任意多次更新,例如更新使用的资源:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl <span class="token builtin class-name">set</span> resources deployment nginx -c<span class="token operator">=</span>nginx --limits<span class="token operator">=</span>cpu<span class="token operator">=</span>200m,memory<span class="token operator">=</span>512Mi
|
||
deployment <span class="token string">"nginx"</span> resource requirements updated
|
||
</code></pre>
|
||
<p>Deployment 暂停前的初始状态将继续它的功能,而不会对 Deployment 的更新产生任何影响,只要 Deployment 是暂停的。</p>
|
||
<p>最后,恢复这个 Deployment,观察完成更新的 ReplicaSet 已经创建出来了:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl rollout resume deploy nginx
|
||
deployment <span class="token string">"nginx"</span> resumed
|
||
$ KUBECTL get rs -w
|
||
NAME DESIRED CURRENT READY AGE
|
||
nginx-2142116321 <span class="token number">2</span> <span class="token number">2</span> <span class="token number">2</span> 2m
|
||
nginx-3926361531 <span class="token number">2</span> <span class="token number">2</span> <span class="token number">0</span> 6s
|
||
nginx-3926361531 <span class="token number">2</span> <span class="token number">2</span> <span class="token number">1</span> 18s
|
||
nginx-2142116321 <span class="token number">1</span> <span class="token number">2</span> <span class="token number">2</span> 2m
|
||
nginx-2142116321 <span class="token number">1</span> <span class="token number">2</span> <span class="token number">2</span> 2m
|
||
nginx-3926361531 <span class="token number">3</span> <span class="token number">2</span> <span class="token number">1</span> 18s
|
||
nginx-3926361531 <span class="token number">3</span> <span class="token number">2</span> <span class="token number">1</span> 18s
|
||
nginx-2142116321 <span class="token number">1</span> <span class="token number">1</span> <span class="token number">1</span> 2m
|
||
nginx-3926361531 <span class="token number">3</span> <span class="token number">3</span> <span class="token number">1</span> 18s
|
||
nginx-3926361531 <span class="token number">3</span> <span class="token number">3</span> <span class="token number">2</span> 19s
|
||
nginx-2142116321 <span class="token number">0</span> <span class="token number">1</span> <span class="token number">1</span> 2m
|
||
nginx-2142116321 <span class="token number">0</span> <span class="token number">1</span> <span class="token number">1</span> 2m
|
||
nginx-2142116321 <span class="token number">0</span> <span class="token number">0</span> <span class="token number">0</span> 2m
|
||
nginx-3926361531 <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> 20s
|
||
^C
|
||
$ KUBECTL get rs
|
||
NAME DESIRED CURRENT READY AGE
|
||
nginx-2142116321 <span class="token number">0</span> <span class="token number">0</span> <span class="token number">0</span> 2m
|
||
nginx-3926361531 <span class="token number">3</span> <span class="token number">3</span> <span class="token number">3</span> 28s
|
||
</code></pre>
|
||
<p><strong>注意:</strong>在恢复 Deployment 之前您无法回退一个已经暂停的 Deployment。</p>
|
||
<h2 id="deployment-状态">Deployment 状态</h2>
|
||
<p>Deployment 在生命周期中有多种状态。在创建一个新的 ReplicaSet 的时候它可以是 <a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment#progressing-deployment" target="_blank">progressing</a> 状态, <a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment#complete-deployment" target="_blank">complete</a> 状态,或者 <a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment#failed-deployment" target="_blank">fail to progress</a> 状态。</p>
|
||
<h3 id="进行中的-deployment">进行中的 Deployment</h3>
|
||
<p>Kubernetes 将执行过下列任务之一的 Deployment 标记为 <em>progressing</em> 状态:</p>
|
||
<ul>
|
||
<li>Deployment 正在创建新的 ReplicaSet 过程中。</li>
|
||
<li>Deployment 正在扩容一个已有的 ReplicaSet。</li>
|
||
<li>Deployment 正在缩容一个已有的 ReplicaSet。</li>
|
||
<li>有新的可用的 pod 出现。</li>
|
||
</ul>
|
||
<p>您可以使用 <code>kubectl rollout status</code> 命令监控 Deployment 的进度。</p>
|
||
<h3 id="完成的-deployment">完成的 Deployment</h3>
|
||
<p>Kubernetes 将包括以下特性的 Deployment 标记为 <em>complete</em> 状态:</p>
|
||
<ul>
|
||
<li>Deployment 最小可用。最小可用意味着 Deployment 的可用 replica 个数等于或者超过 Deployment 策略中的期望个数。</li>
|
||
<li>所有与该 Deployment 相关的 replica 都被更新到了您指定版本,也就说更新完成。</li>
|
||
<li>该 Deployment 中没有旧的 Pod 存在。</li>
|
||
</ul>
|
||
<p>您可以用 <code>kubectl rollout status</code> 命令查看 Deployment 是否完成。如果 rollout 成功完成,<code>kubectl rollout status</code> 将返回一个 0 值的 Exit Code。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl rollout status deploy/nginx
|
||
Waiting <span class="token keyword">for</span> rollout to finish: <span class="token number">2</span> of <span class="token number">3</span> updated replicas are available<span class="token punctuation">..</span>.
|
||
deployment <span class="token string">"nginx"</span> successfully rolled out
|
||
$ <span class="token builtin class-name">echo</span> <span class="token variable">$?</span>
|
||
<span class="token number">0</span>
|
||
</code></pre>
|
||
<h3 id="失败的-deployment">失败的 Deployment</h3>
|
||
<p>您的 Deployment 在尝试部署新的 ReplicaSet 的时候可能卡住,永远也不会完成。这可能是因为以下几个因素引起的:</p>
|
||
<ul>
|
||
<li>无效的引用</li>
|
||
<li>不可读的 probe failure</li>
|
||
<li>镜像拉取错误</li>
|
||
<li>权限不够</li>
|
||
<li>范围限制</li>
|
||
<li>程序运行时配置错误</li>
|
||
</ul>
|
||
<p>探测这种情况的一种方式是,在您的 Deployment spec 中指定 <a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment#progress-deadline-seconds" target="_blank"><code>spec.progressDeadlineSeconds</code></a>。<code>spec.progressDeadlineSeconds</code> 表示 Deployment controller 等待多少秒才能确定(通过 Deployment status)Deployment 进程是卡住的。</p>
|
||
<p>下面的 <code>kubectl</code> 命令设置 <code>progressDeadlineSeconds</code> 使 controller 在 Deployment 在进度卡住 10 分钟后报告:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl patch deployment/nginx-deployment -p <span class="token string">'{"spec":{"progressDeadlineSeconds":600}}'</span>
|
||
<span class="token string">"nginx-deployment"</span> patched
|
||
</code></pre>
|
||
<p>当超过截止时间后,Deployment controller 会在 Deployment 的<code>status.conditions</code> 中增加一条 DeploymentCondition,它包括如下属性:</p>
|
||
<ul>
|
||
<li>Type=Progressing</li>
|
||
<li>Status=False</li>
|
||
<li>Reason=ProgressDeadlineExceeded</li>
|
||
</ul>
|
||
<p><strong>注意:</strong>kubernetes 除了报告 <code>Reason=ProgressDeadlineExceeded</code> 状态信息外不会对卡住的 Deployment 做任何操作。更高层次的协调器可以利用它并采取相应行动,例如,回滚 Deployment 到之前的版本。</p>
|
||
<p><strong>注意:</strong>如果您暂停了一个 Deployment,在暂停的这段时间内 kubernetnes 不会检查您指定的 deadline。您可以在 Deployment 的 rollout 途中安全的暂停它,然后再恢复它,这不会触发超过 deadline 的状态。</p>
|
||
<p>您可能在使用 Deployment 的时候遇到一些短暂的错误,这些可能是由于您设置了太短的 timeout,也有可能是因为各种其他错误导致的短暂错误。例如,假设您使用了无效的引用。当您 Describe Deployment 的时候可能会注意到如下信息:</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl describe deployment nginx-deployment
|
||
<span class="token operator"><</span><span class="token punctuation">..</span>.<span class="token operator">></span>
|
||
Conditions:
|
||
Type Status Reason
|
||
---- ------ ------
|
||
Available True MinimumReplicasAvailable
|
||
Progressing True ReplicaSetUpdated
|
||
ReplicaFailure True FailedCreate
|
||
<span class="token operator"><</span><span class="token punctuation">..</span>.<span class="token operator">></span>
|
||
</code></pre>
|
||
<p>执行<code>kubectl get deployment nginx-deployment -o yaml</code>,Deployement 的状态可能看起来像这个样子:</p>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">status</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">availableReplicas</span><span class="token punctuation">:</span> <span class="token number">2</span>
|
||
<span class="token key atrule">conditions</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">lastTransitionTime</span><span class="token punctuation">:</span> <span class="token datetime number">2016-10-04T12:25:39Z</span>
|
||
<span class="token key atrule">lastUpdateTime</span><span class="token punctuation">:</span> <span class="token datetime number">2016-10-04T12:25:39Z</span>
|
||
<span class="token key atrule">message</span><span class="token punctuation">:</span> Replica set "nginx<span class="token punctuation">-</span>deployment<span class="token punctuation">-</span>4262182780" is progressing.
|
||
<span class="token key atrule">reason</span><span class="token punctuation">:</span> ReplicaSetUpdated
|
||
<span class="token key atrule">status</span><span class="token punctuation">:</span> <span class="token string">"True"</span>
|
||
<span class="token key atrule">type</span><span class="token punctuation">:</span> Progressing
|
||
<span class="token punctuation">-</span> <span class="token key atrule">lastTransitionTime</span><span class="token punctuation">:</span> <span class="token datetime number">2016-10-04T12:25:42Z</span>
|
||
<span class="token key atrule">lastUpdateTime</span><span class="token punctuation">:</span> <span class="token datetime number">2016-10-04T12:25:42Z</span>
|
||
<span class="token key atrule">message</span><span class="token punctuation">:</span> Deployment has minimum availability.
|
||
<span class="token key atrule">reason</span><span class="token punctuation">:</span> MinimumReplicasAvailable
|
||
<span class="token key atrule">status</span><span class="token punctuation">:</span> <span class="token string">"True"</span>
|
||
<span class="token key atrule">type</span><span class="token punctuation">:</span> Available
|
||
<span class="token punctuation">-</span> <span class="token key atrule">lastTransitionTime</span><span class="token punctuation">:</span> <span class="token datetime number">2016-10-04T12:25:39Z</span>
|
||
<span class="token key atrule">lastUpdateTime</span><span class="token punctuation">:</span> <span class="token datetime number">2016-10-04T12:25:39Z</span>
|
||
<span class="token key atrule">message</span><span class="token punctuation">:</span> 'Error creating<span class="token punctuation">:</span> <span class="token key atrule">pods "nginx-deployment-4262182780-" is forbidden</span><span class="token punctuation">:</span> <span class="token key atrule">exceeded quota</span><span class="token punctuation">:</span>
|
||
object<span class="token punctuation">-</span>counts<span class="token punctuation">,</span> <span class="token key atrule">requested</span><span class="token punctuation">:</span> pods=1<span class="token punctuation">,</span> <span class="token key atrule">used</span><span class="token punctuation">:</span> pods=3<span class="token punctuation">,</span> <span class="token key atrule">limited</span><span class="token punctuation">:</span> pods=2'
|
||
<span class="token key atrule">reason</span><span class="token punctuation">:</span> FailedCreate
|
||
<span class="token key atrule">status</span><span class="token punctuation">:</span> <span class="token string">"True"</span>
|
||
<span class="token key atrule">type</span><span class="token punctuation">:</span> ReplicaFailure
|
||
<span class="token key atrule">observedGeneration</span><span class="token punctuation">:</span> <span class="token number">3</span>
|
||
<span class="token key atrule">replicas</span><span class="token punctuation">:</span> <span class="token number">2</span>
|
||
<span class="token key atrule">unavailableReplicas</span><span class="token punctuation">:</span> <span class="token number">2</span>
|
||
</code></pre>
|
||
<p>最终,一旦超过 Deployment 进程的 deadline,kubernetes 会更新状态和导致 Progressing 状态的原因:</p>
|
||
<pre class="language-"><code class="lang-bash">Conditions:
|
||
Type Status Reason
|
||
---- ------ ------
|
||
Available True MinimumReplicasAvailable
|
||
Progressing False ProgressDeadlineExceeded
|
||
ReplicaFailure True FailedCreate
|
||
</code></pre>
|
||
<p>您可以通过缩容 Deployment 的方式解决配额不足的问题,或者增加您的 namespace 的配额。如果您满足了配额条件后,Deployment controller 就会完成您的 Deployment rollout,您将看到 Deployment 的状态更新为成功状态(<code>Status=True</code>并且<code>Reason=NewReplicaSetAvailable</code>)。</p>
|
||
<pre class="language-"><code class="lang-bash">Conditions:
|
||
Type Status Reason
|
||
---- ------ ------
|
||
Available True MinimumReplicasAvailable
|
||
Progressing True NewReplicaSetAvailable
|
||
</code></pre>
|
||
<p><code>Type=Available</code>、 <code>Status=True</code> 意味着您的 Deployment 有最小可用性。 最小可用性是在 Deployment 策略中指定的参数。<code>Type=Progressing</code> 、 <code>Status=True</code> 意味着您的 Deployment 或者在部署过程中,或者已经成功部署,达到了期望的最少的可用 replica 数量(查看特定状态的 Reason—— 在我们的例子中 <code>Reason=NewReplicaSetAvailable</code> 意味着 Deployment 已经完成)。</p>
|
||
<p>您可以使用 <code>kubectl rollout status</code> 命令查看 Deployment 进程是否失败。当 Deployment 过程超过了 deadline,<code>kubectl rollout status</code> 将返回非 0 的 exit code。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl rollout status deploy/nginx
|
||
Waiting <span class="token keyword">for</span> rollout to finish: <span class="token number">2</span> out of <span class="token number">3</span> new replicas have been updated<span class="token punctuation">..</span>.
|
||
error: deployment <span class="token string">"nginx"</span> exceeded its progress deadline
|
||
$ <span class="token builtin class-name">echo</span> <span class="token variable">$?</span>
|
||
<span class="token number">1</span>
|
||
</code></pre>
|
||
<h3 id="操作失败的-deployment">操作失败的 Deployment</h3>
|
||
<p>所有对完成的 Deployment 的操作都适用于失败的 Deployment。您可以对它扩 / 缩容,回退到历史版本,您甚至可以多次暂停它来应用 Deployment pod template。</p>
|
||
<h2 id="清理-policy">清理 Policy</h2>
|
||
<p>您可以设置 Deployment 中的 <code>.spec.revisionHistoryLimit</code> 项来指定保留多少旧的 ReplicaSet。 余下的将在后台被当作垃圾收集。默认的,所有的 revision 历史就都会被保留。在未来的版本中,将会更改为 2。</p>
|
||
<p><strong>注意:</strong>将该值设置为 0,将导致所有的 Deployment 历史记录都会被清除,该 Deployment 就无法再回退了。</p>
|
||
<h2 id="用例">用例</h2>
|
||
<h3 id="金丝雀-deployment">金丝雀 Deployment</h3>
|
||
<p>如果您想要使用 Deployment 对部分用户或服务器发布 release,您可以创建多个 Deployment,每个 Deployment 对应一个 release,参照 <a href="https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#canary-deployments" target="_blank">managing resources</a> 中对金丝雀模式的描述。</p>
|
||
<h2 id="编写-deployment-spec">编写 Deployment Spec</h2>
|
||
<p>在所有的 Kubernetes 配置中,Deployment 也需要 <code>apiVersion</code>,<code>kind</code> 和 <code>metadata</code> 这些配置项。配置文件的通用使用说明查看 <a href="https://kubernetes.io/docs/tasks/run-application/run-stateless-application-deployment/" target="_blank">部署应用</a>,配置容器,和使用 kubectl 管理资源文档。</p>
|
||
<h3 id="pod-template">Pod Template</h3>
|
||
<p><code>.spec.template</code> 是 <code>.spec</code> 中唯一要求的字段。</p>
|
||
<p><code>.spec.template</code> 是 <a href="https://kubernetes.io/docs/user-guide/replication-controller/#pod-template" target="_blank">pod template</a>. 它跟 <a href="https://kubernetes.io/docs/user-guide/pods" target="_blank">Pod</a> 有一模一样的 schema,除了它是嵌套的并且不需要 <code>apiVersion</code> 和 <code>kind</code> 字段。</p>
|
||
<p>另外为了划分 Pod 的范围,Deployment 中的 pod template 必须指定适当的 label(不要跟其他 controller 重复了,参考 <a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment#selector" target="_blank">selector</a>)和适当的重启策略。</p>
|
||
<p><a href="https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle" target="_blank"><code>.spec.template.spec.restartPolicy</code></a> 可以设置为 <code>Always</code> , 如果不指定的话这就是默认配置。</p>
|
||
<h3 id="replicas">Replicas</h3>
|
||
<p><code>.spec.replicas</code> 是可以选字段,指定期望的 pod 数量,默认是 1。</p>
|
||
<h3 id="selector">Selector</h3>
|
||
<p><code>.spec.selector</code> 是可选字段,用来指定 <a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/labels" target="_blank">label selector</a> ,圈定 Deployment 管理的 pod 范围。</p>
|
||
<p>如果被指定, <code>.spec.selector</code> 必须匹配 <code>.spec.template.metadata.labels</code>,否则它将被 API 拒绝。如果 <code>.spec.selector</code> 没有被指定, <code>.spec.selector.matchLabels</code> 默认是 <code>.spec.template.metadata.labels</code>。</p>
|
||
<p>在 Pod 的 template 跟 <code>.spec.template</code> 不同或者数量超过了 <code>.spec.replicas</code> 规定的数量的情况下,Deployment 会杀掉 label 跟 selector 不同的 Pod。</p>
|
||
<p><strong>注意:</strong>您不应该再创建其他 label 跟这个 selector 匹配的 pod,或者通过其他 Deployment,或者通过其他 Controller,例如 ReplicaSet 和 ReplicationController。否则该 Deployment 会被把它们当成都是自己创建的。Kubernetes 不会阻止您这么做。</p>
|
||
<p>如果您有多个 controller 使用了重复的 selector,controller 们就会互相打架并导致不正确的行为。</p>
|
||
<h3 id="策略">策略</h3>
|
||
<p><code>.spec.strategy</code> 指定新的 Pod 替换旧的 Pod 的策略。 <code>.spec.strategy.type</code> 可以是 "Recreate" 或者是 "RollingUpdate"。"RollingUpdate" 是默认值。</p>
|
||
<h4 id="recreate-deployment">Recreate Deployment</h4>
|
||
<p><code>.spec.strategy.type==Recreate</code> 时,在创建出新的 Pod 之前会先杀掉所有已存在的 Pod。</p>
|
||
<h4 id="rolling-update-deployment">Rolling Update Deployment</h4>
|
||
<p><code>.spec.strategy.type==RollingUpdate</code> 时,Deployment 使用 <a href="https://kubernetes.io/docs/tasks/run-application/rolling-update-replication-controller" target="_blank">rolling update</a> 的方式更新 Pod 。您可以指定 <code>maxUnavailable</code> 和 <code>maxSurge</code> 来控制 rolling update 进程。</p>
|
||
<h5 id="max-unavailable">Max Unavailable</h5>
|
||
<p><code>.spec.strategy.rollingUpdate.maxUnavailable</code> 是可选配置项,用来指定在升级过程中不可用 Pod 的最大数量。该值可以是一个绝对值(例如 5),也可以是期望 Pod 数量的百分比(例如 10%)。通过计算百分比的绝对值向下取整。如果 <code>.spec.strategy.rollingUpdate.maxSurge</code> 为 0 时,这个值不可以为 0。默认值是 1。</p>
|
||
<p>例如,该值设置成 30%,启动 rolling update 后旧的 ReplicatSet 将会立即缩容到期望的 Pod 数量的 70%。新的 Pod ready 后,随着新的 ReplicaSet 的扩容,旧的 ReplicaSet 会进一步缩容,确保在升级的所有时刻可以用的 Pod 数量至少是期望 Pod 数量的 70%。</p>
|
||
<h5 id="max-surge">Max Surge</h5>
|
||
<p><code>.spec.strategy.rollingUpdate.maxSurge</code> 是可选配置项,用来指定可以超过期望的 Pod 数量的最大个数。该值可以是一个绝对值(例如 5)或者是期望的 Pod 数量的百分比(例如 10%)。当 <code>MaxUnavailable</code> 为 0 时该值不可以为 0。通过百分比计算的绝对值向上取整。默认值是 1。</p>
|
||
<p>例如,该值设置成 30%,启动 rolling update 后新的 ReplicatSet 将会立即扩容,新老 Pod 的总数不能超过期望的 Pod 数量的 130%。旧的 Pod 被杀掉后,新的 ReplicaSet 将继续扩容,旧的 ReplicaSet 会进一步缩容,确保在升级的所有时刻所有的 Pod 数量和不会超过期望 Pod 数量的 130%。</p>
|
||
<h3 id="progress-deadline-seconds">Progress Deadline Seconds</h3>
|
||
<p><code>.spec.progressDeadlineSeconds</code> 是可选配置项,用来指定在系统报告 Deployment 的 <a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment#failed-deployment" target="_blank">failed progressing</a> —— 表现为 resource 的状态中 <code>type=Progressing</code>、<code>Status=False</code>、 <code>Reason=ProgressDeadlineExceeded</code> 前可以等待的 Deployment 进行的秒数。Deployment controller 会继续重试该 Deployment。未来,在实现了自动回滚后, deployment controller 在观察到这种状态时就会自动回滚。</p>
|
||
<p>如果设置该参数,该值必须大于 <code>.spec.minReadySeconds</code>。</p>
|
||
<h3 id="min-ready-seconds">Min Ready Seconds</h3>
|
||
<p><code>.spec.minReadySeconds</code> 是一个可选配置项,用来指定没有任何容器 crash 的 Pod 并被认为是可用状态的最小秒数。默认是 0(Pod 在 ready 后就会被认为是可用状态)。进一步了解什么什么后 Pod 会被认为是 ready 状态,参阅 <a href="https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes" target="_blank">Container Probes</a>。</p>
|
||
<h3 id="rollback-to">Rollback To</h3>
|
||
<p><code>.spec.rollbackTo</code> 是一个可以选配置项,用来配置 Deployment 回退的配置。设置该参数将触发回退操作,每次回退完成后,该值就会被清除。</p>
|
||
<h4 id="revision">Revision</h4>
|
||
<p><code>.spec.rollbackTo.revision</code> 是一个可选配置项,用来指定回退到的 revision。默认是 0,意味着回退到上一个 revision。</p>
|
||
<h3 id="revision-history-limit">Revision History Limit</h3>
|
||
<p>Deployment revision history 存储在它控制的 ReplicaSets 中。</p>
|
||
<p><code>.spec.revisionHistoryLimit</code> 是一个可选配置项,用来指定可以保留的旧的 ReplicaSet 数量。该理想值取决于心 Deployment 的频率和稳定性。如果该值没有设置的话,默认所有旧的 Replicaset 或会被保留,将资源存储在 etcd 中,是用 <code>kubectl get rs</code> 查看输出。每个 Deployment 的该配置都保存在 ReplicaSet 中,然而,一旦您删除的旧的 RepelicaSet,您的 Deployment 就无法再回退到那个 revison 了。</p>
|
||
<p>如果您将该值设置为 0,所有具有 0 个 replica 的 ReplicaSet 都会被删除。在这种情况下,新的 Deployment rollout 无法撤销,因为 revision history 都被清理掉了。</p>
|
||
<h3 id="paused">Paused</h3>
|
||
<p><code>.spec.paused</code> 是可以可选配置项,boolean 值。用来指定暂停和恢复 Deployment。Paused 和没有 paused 的 Deployment 之间的唯一区别就是,所有对 paused deployment 中的 PodTemplateSpec 的修改都不会触发新的 rollout。Deployment 被创建之后默认是非 paused。 </p>
|
||
<footer class="page-footer"><span class="copyright"><a href="https://mp.weixin.qq.com/s/vWlSdzz2MNdXRr0sd2-LFg" target="_blank">加入云原生社区</a><p></p>Copyright © 2017-2020 | Distributed under <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/deed.zh" target="_blank">CC BY 4.0</a> | <a href="https://jimmysong.io" target="_blank">jimmysong.io</a> all right reserved,powered by Gitbook</span><span class="footer-modification"> Updated at
|
||
2020-12-29 01:47:59
|
||
</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="controllers.html" class="navigation navigation-prev " aria-label="Previous page: 控制器">
|
||
<i class="fa fa-angle-left"></i>
|
||
</a>
|
||
|
||
|
||
<a href="statefulset.html" class="navigation navigation-next " aria-label="Next page: StatefulSet">
|
||
<i class="fa fa-angle-right"></i>
|
||
</a>
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<script>
|
||
var gitbook = gitbook || [];
|
||
gitbook.push(function() {
|
||
gitbook.page.hasChanged({"page":{"title":"Deployment","level":"3.6.1","depth":2,"next":{"title":"StatefulSet","level":"3.6.2","depth":2,"path":"concepts/statefulset.md","ref":"concepts/statefulset.md","articles":[]},"previous":{"title":"控制器","level":"3.6","depth":1,"path":"concepts/controllers.md","ref":"concepts/controllers.md","articles":[{"title":"Deployment","level":"3.6.1","depth":2,"path":"concepts/deployment.md","ref":"concepts/deployment.md","articles":[]},{"title":"StatefulSet","level":"3.6.2","depth":2,"path":"concepts/statefulset.md","ref":"concepts/statefulset.md","articles":[]},{"title":"DaemonSet","level":"3.6.3","depth":2,"path":"concepts/daemonset.md","ref":"concepts/daemonset.md","articles":[]},{"title":"ReplicationController 和 ReplicaSet","level":"3.6.4","depth":2,"path":"concepts/replicaset.md","ref":"concepts/replicaset.md","articles":[]},{"title":"Job","level":"3.6.5","depth":2,"path":"concepts/job.md","ref":"concepts/job.md","articles":[]},{"title":"CronJob","level":"3.6.6","depth":2,"path":"concepts/cronjob.md","ref":"concepts/cronjob.md","articles":[]},{"title":"Horizontal Pod Autoscaling","level":"3.6.7","depth":2,"path":"concepts/horizontal-pod-autoscaling.md","ref":"concepts/horizontal-pod-autoscaling.md","articles":[{"title":"自定义指标 HPA","level":"3.6.7.1","depth":3,"path":"concepts/custom-metrics-hpa.md","ref":"concepts/custom-metrics-hpa.md","articles":[]}]},{"title":"准入控制器(Admission Controller)","level":"3.6.8","depth":2,"path":"concepts/admission-controller.md","ref":"concepts/admission-controller.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","sitemap-general","lightbox","ga","alerts"],"styles":{"ebook":"styles/ebook.css","epub":"styles/epub.css","mobi":"styles/mobi.css","pdf":"styles/pdf.css","print":"styles/print.css","website":"styles/website.css"},"pluginsConfig":{"tbfed-pagefooter":{"copyright":"<a href=https://mp.weixin.qq.com/s/vWlSdzz2MNdXRr0sd2-LFg>加入云原生社区</a></p>Copyright © 2017-2020 | Distributed under <a href=https://creativecommons.org/licenses/by-nc-sa/4.0/deed.zh>CC BY 4.0</a> | <a href=https://jimmysong.io>jimmysong.io</a>","modify_label":" Updated at ","modify_format":"YYYY-MM-DD HH:mm:ss"},"prism":{"css":["prism-themes/themes/prism-ghcolors.css"]},"github":{"url":"https://github.com/rootsongjc/kubernetes-handbook"},"editlink":{"label":"编辑本页","multilingual":false,"base":"https://github.com/rootsongjc/kubernetes-handbook/blob/master/"},"splitter":{},"codesnippet":{},"sitemap-general":{"prefix":"https://jimmysong.io/kubernetes-handbook/"},"fontsettings":{"theme":"white","family":"sans","size":2},"favicon":{"shortcut":"favicon.ico","bookmark":"favicon.ico"},"lightbox":{"jquery":true,"sameUuid":false},"page-toc-button":{},"back-to-top-button":{},"prism-themes":{},"alerts":{},"github-buttons":{"repo":"rootsongjc/kubernetes-handbook","types":["star"],"size":"small"},"3-ba":{"configuration":"auto","token":"11f7d254cfa4e0ca44b175c66d379ecc"},"ga":{"configuration":"auto","token":"UA-93485976-1"},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"theme-default":{"showLevel":true,"styles":{"ebook":"styles/ebook.css","epub":"styles/epub.css","mobi":"styles/mobi.css","pdf":"styles/pdf.css","print":"styles/print.css","website":"styles/website.css"}},"search-plus":{},"image-captions":{"caption":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","variable_name":"_pictures"}},"theme":"default","author":"Jimmy Song(宋净超)","pdf":{"pageNumbers":true,"fontSize":12,"fontFamily":"Arial","paperSize":"a4","chapterMark":"pagebreak","pageBreaksBefore":"/","margin":{"right":62,"left":62,"top":56,"bottom":56}},"structure":{"langs":"LANGS.md","readme":"README.md","glossary":"GLOSSARY.md","summary":"SUMMARY.md"},"variables":{"_pictures":[{"backlink":"index.html#fig1.1.1","level":"1.1","list_caption":"Figure: Stargazers over time","alt":"Stargazers over time","nro":1,"url":"https://starcharts.herokuapp.com/rootsongjc/kubernetes-handbook.svg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Stargazers over time","attributes":{},"skip":false,"key":"1.1.1"},{"backlink":"cloud-native/play-with-kubernetes.html#fig2.4.1","level":"2.4","list_caption":"Figure: Play with Kubernetes网页截图","alt":"Play with Kubernetes网页截图","nro":2,"url":"../images/play-with-kubernetes.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Play with Kubernetes网页截图","attributes":{},"skip":false,"key":"2.4.1"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig2.5.1","level":"2.5","list_caption":"Figure: Kubernetes dashboard","alt":"Kubernetes dashboard","nro":3,"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":"2.5.1"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig2.5.2","level":"2.5","list_caption":"Figure: Grafana","alt":"Grafana","nro":4,"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":"2.5.2"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig2.5.3","level":"2.5","list_caption":"Figure: Traefik dashboard","alt":"Traefik dashboard","nro":5,"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":"2.5.3"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig2.5.4","level":"2.5","list_caption":"Figure: bookinfo示例","alt":"bookinfo示例","nro":6,"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":"2.5.4"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig2.5.5","level":"2.5","list_caption":"Figure: vistio视图动画","alt":"vistio视图动画","nro":7,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/vistio-animation.gif","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"vistio视图动画","attributes":{},"skip":false,"key":"2.5.5"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig2.5.6","level":"2.5","list_caption":"Figure: Kiali页面","alt":"Kiali页面","nro":8,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/kiali.gif","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kiali页面","attributes":{},"skip":false,"key":"2.5.6"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig2.5.7","level":"2.5","list_caption":"Figure: Scope页面","alt":"Scope页面","nro":9,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/weave-scope-animation.gif","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Scope页面","attributes":{},"skip":false,"key":"2.5.7"},{"backlink":"cloud-native/setup-kubernetes-with-rancher-and-aliyun.html#fig2.6.1","level":"2.6","list_caption":"Figure: Rancher 界面","alt":"Rancher 界面","nro":10,"url":"../images/rancher-web.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Rancher 界面","attributes":{},"skip":false,"key":"2.6.1"},{"backlink":"cloud-native/setup-kubernetes-with-rancher-and-aliyun.html#fig2.6.2","level":"2.6","list_caption":"Figure: 自定义节点信息","alt":"自定义节点信息","nro":11,"url":"../images/rancher-customize-node.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"自定义节点信息","attributes":{},"skip":false,"key":"2.6.2"},{"backlink":"cloud-native/setup-kubernetes-with-rancher-and-aliyun.html#fig2.6.3","level":"2.6","list_caption":"Figure: Rancher 集群监控页面","alt":"Rancher 集群监控页面","nro":12,"url":"../images/rancher-cluster.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Rancher 集群监控页面","attributes":{},"skip":false,"key":"2.6.3"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.1","level":"2.7","list_caption":"Figure: 云计算演进历程","alt":"云计算演进历程","nro":13,"url":"../images/cloud-computing-evolution-road.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云计算演进历程","attributes":{},"skip":false,"key":"2.7.1"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.2","level":"2.7","list_caption":"Figure: 来自Twitter @MarcWilczek","alt":"来自Twitter @MarcWilczek","nro":14,"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.7.2"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.3","level":"2.7","list_caption":"Figure: Cloud native思维导图","alt":"Cloud native思维导图","nro":15,"url":"../images/cloud-native-architecutre-mindnode.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Cloud native思维导图","attributes":{},"skip":false,"key":"2.7.3"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.4","level":"2.7","list_caption":"Figure: 十二因素应用","alt":"十二因素应用","nro":16,"url":"../images/12-factor-app.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"十二因素应用","attributes":{},"skip":false,"key":"2.7.4"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.5","level":"2.7","list_caption":"Figure: 容器生态","alt":"容器生态","nro":17,"url":"../images/container-ecosystem.png","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"容器生态","attributes":{},"skip":false,"key":"2.7.5"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.6","level":"2.7","list_caption":"Figure: 使用Jenkins进行持续集成与发布流程图","alt":"使用Jenkins进行持续集成与发布流程图","nro":18,"url":"../images/kubernetes-jenkins-ci-cd.png","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"使用Jenkins进行持续集成与发布流程图","attributes":{},"skip":false,"key":"2.7.6"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.7","level":"2.7","list_caption":"Figure: filebeat日志收集架构图","alt":"filebeat日志收集架构图","nro":19,"url":"../images/filebeat-log-collector-arch.png","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"filebeat日志收集架构图","attributes":{},"skip":false,"key":"2.7.7"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.8","level":"2.7","list_caption":"Figure: API文档","alt":"API文档","nro":20,"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.7.8"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.9","level":"2.7","list_caption":"Figure: 迁移步骤示意图","alt":"迁移步骤示意图","nro":21,"url":"../images/migrating-hadoop-yarn-to-kubernetes.png","index":9,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"迁移步骤示意图","attributes":{},"skip":false,"key":"2.7.9"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.10","level":"2.7","list_caption":"Figure: service mesh架构图","alt":"service mesh架构图","nro":22,"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.7.10"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.11","level":"2.7","list_caption":"Figure: kibana界面","alt":"kibana界面","nro":23,"url":"../images/filebeat-docker-test.jpg","index":11,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kibana界面","attributes":{},"skip":false,"key":"2.7.11"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.12","level":"2.7","list_caption":"Figure: Grafana界面示意图1","alt":"Grafana界面示意图1","nro":24,"url":"../images/kubernetes-devops-example-grafana-1.png","index":12,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Grafana界面示意图1","attributes":{},"skip":false,"key":"2.7.12"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.13","level":"2.7","list_caption":"Figure: Grafana界面示意图2","alt":"Grafana界面示意图2","nro":25,"url":"../images/kubernetes-devops-example-grafana-2.png","index":13,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Grafana界面示意图2","attributes":{},"skip":false,"key":"2.7.13"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.14","level":"2.7","list_caption":"Figure: Grafana界面示意图3","alt":"Grafana界面示意图3","nro":26,"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.7.14"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.15","level":"2.7","list_caption":"Figure: dashboard","alt":"dashboard","nro":27,"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.7.15"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.7.16","level":"2.7","list_caption":"Figure: Grafana","alt":"Grafana","nro":28,"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.7.16"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.1","level":"2.8","list_caption":"Figure: 容器生态图 Container ecosystem","alt":"容器生态图 Container ecosystem","nro":29,"url":"../images/container-ecosystem.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"容器生态图 Container ecosystem","attributes":{},"skip":false,"key":"2.8.1"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.2","level":"2.8","list_caption":"Figure: Kubernetes架构","alt":"Kubernetes架构","nro":30,"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.8.2"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.3","level":"2.8","list_caption":"Figure: Cloud Native Core target","alt":"Cloud Native Core target","nro":31,"url":"../images/cloud-native-core-target.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Cloud Native Core target","attributes":{},"skip":false,"key":"2.8.3"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.4","level":"2.8","list_caption":"Figure: FaaS Landscape","alt":"FaaS Landscape","nro":32,"url":"../images/redpoint-faas-landscape.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"FaaS Landscape","attributes":{},"skip":false,"key":"2.8.4"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.5","level":"2.8","list_caption":"Figure: Workloads running on Kubernetes","alt":"Workloads running on Kubernetes","nro":33,"url":"../images/0069RVTdgy1fv5mxr6fxtj31kw11q484.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Workloads running on Kubernetes","attributes":{},"skip":false,"key":"2.8.5"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.6","level":"2.8","list_caption":"Figure: Gartner技术爆发趋势图2017","alt":"Gartner技术爆发趋势图2017","nro":34,"url":"../images/0069RVTdgy1fv5my2jtxzj315o0z8dkr.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Gartner技术爆发趋势图2017","attributes":{},"skip":false,"key":"2.8.6"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.7","level":"2.8","list_caption":"Figure: Microservices concerns","alt":"Microservices concerns","nro":35,"url":"../images/microservices-concerns.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Microservices concerns","attributes":{},"skip":false,"key":"2.8.7"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.8","level":"2.8","list_caption":"Figure: 两种服务发现方式","alt":"两种服务发现方式","nro":36,"url":"../images/service-discovery-in-microservices.png","index":8,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"两种服务发现方式","attributes":{},"skip":false,"key":"2.8.8"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.9","level":"2.8","list_caption":"Figure: Cloud Native Features","alt":"Cloud Native Features","nro":37,"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.8.9"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.10","level":"2.8","list_caption":"Figure: Cloud Native Landscape v1.0","alt":"Cloud Native Landscape v1.0","nro":38,"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.8.10"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.11","level":"2.8","list_caption":"Figure: Building a Cloud Native Architecture with Kubernetes followed 12 factor app","alt":"Building a Cloud Native Architecture with Kubernetes followed 12 factor app","nro":39,"url":"../images/building-cloud-native-architecture-with-kubernetes.png","index":11,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Building a Cloud Native Architecture with Kubernetes followed 12 factor app","attributes":{},"skip":false,"key":"2.8.11"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.12","level":"2.8","list_caption":"Figure: Creating Kubernetes native app","alt":"Creating Kubernetes native app","nro":40,"url":"../images/creating-kubernetes-native-app.jpg","index":12,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Creating Kubernetes native app","attributes":{},"skip":false,"key":"2.8.12"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.13","level":"2.8","list_caption":"Figure: istio vs linkerd","alt":"istio vs linkerd","nro":41,"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.8.13"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.14","level":"2.8","list_caption":"Figure: Deployment pipeline","alt":"Deployment pipeline","nro":42,"url":"../images/0069RVTdgy1fv5mzj8rj6j318g1ewtfc.jpg","index":14,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Deployment pipeline","attributes":{},"skip":false,"key":"2.8.14"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.15","level":"2.8","list_caption":"Figure: Spark on Kubernetes with different schedulers","alt":"Spark on Kubernetes with different schedulers","nro":43,"url":"../images/spark-on-kubernetes-with-different-schedulers.jpg","index":15,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Spark on Kubernetes with different schedulers","attributes":{},"skip":false,"key":"2.8.15"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.16","level":"2.8","list_caption":"Figure: Kubernetes solutions","alt":"Kubernetes solutions","nro":44,"url":"../images/0069RVTdgy1fv5mzywc83j31fk1i8qg4.jpg","index":16,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes solutions","attributes":{},"skip":false,"key":"2.8.16"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.8.17","level":"2.8","list_caption":"Figure: Kubernetes SIG","alt":"Kubernetes SIG","nro":45,"url":"../images/kubernetes-sigs.jpg","index":17,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes SIG","attributes":{},"skip":false,"key":"2.8.17"},{"backlink":"cloud-native/define-cloud-native-app.html#fig2.9.1","level":"2.9","list_caption":"Figure: 云原生应用模型","alt":"云原生应用模型","nro":46,"url":"../images/cloud-native-app-model.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生应用模型","attributes":{},"skip":false,"key":"2.9.1"},{"backlink":"cloud-native/define-cloud-native-app.html#fig2.9.2","level":"2.9","list_caption":"Figure: 云原生应用模型中的目标角色","alt":"云原生应用模型中的目标角色","nro":47,"url":"../images/roles.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生应用模型中的目标角色","attributes":{},"skip":false,"key":"2.9.2"},{"backlink":"cloud-native/oam.html#fig2.9.1.1","level":"2.9.1","list_caption":"Figure: OAM 规范示意图","alt":"OAM 规范示意图","nro":48,"url":"../images/oam-spec.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OAM 规范示意图","attributes":{},"skip":false,"key":"2.9.1.1"},{"backlink":"cloud-native/oam.html#fig2.9.1.2","level":"2.9.1","list_caption":"Figure: OAM 的原理","alt":"OAM 的原理","nro":49,"url":"../images/oam-principle.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OAM 的原理","attributes":{},"skip":false,"key":"2.9.1.2"},{"backlink":"cloud-native/crossplane.html#fig2.9.2.1","level":"2.9.2","list_caption":"Figure: Wordpress 页面","alt":"Wordpress 页面","nro":50,"url":"../images/wordpress.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Wordpress 页面","attributes":{},"skip":false,"key":"2.9.2.1"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.10.1.1","level":"2.10.1","list_caption":"Figure: 云原生编程语言ballerina","alt":"云原生编程语言ballerina","nro":51,"url":"../images/philosophy-page-diagrams-top.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言ballerina","attributes":{},"skip":false,"key":"2.10.1.1"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.10.1.2","level":"2.10.1","list_caption":"Figure: 云原生编程语言Ballerina的序列图设计理念","alt":"云原生编程语言Ballerina的序列图设计理念","nro":52,"url":"../images/philosophy-principle-diagrams-01.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言Ballerina的序列图设计理念","attributes":{},"skip":false,"key":"2.10.1.2"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.10.1.3","level":"2.10.1","list_caption":"Figure: 云原生编程语言Ballerina的并发理念","alt":"云原生编程语言Ballerina的并发理念","nro":53,"url":"../images/philosophy-principle-diagrams-02.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言Ballerina的并发理念","attributes":{},"skip":false,"key":"2.10.1.3"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.10.1.4","level":"2.10.1","list_caption":"Figure: 云原生编程语言ballerina运行时架构","alt":"云原生编程语言ballerina运行时架构","nro":54,"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.10.1.4"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.10.1.5","level":"2.10.1","list_caption":"Figure: 云原生编程语言ballerina部署架构图","alt":"云原生编程语言ballerina部署架构图","nro":55,"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.10.1.5"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.10.1.6","level":"2.10.1","list_caption":"Figure: 云原生编程语言ballerina生命周期架构图","alt":"云原生编程语言ballerina生命周期架构图","nro":56,"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.10.1.6"},{"backlink":"cloud-native/cloud-native-programming-language-pulumi.html#fig2.10.2.1","level":"2.10.2","list_caption":"Figure: 云原生编程语言Pulumi","alt":"云原生编程语言Pulumi","nro":57,"url":"../images/00704eQkgy1fsm4v0a6qwj30xc0m8t9d.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言Pulumi","attributes":{},"skip":false,"key":"2.10.2.1"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.1","level":"2.11","list_caption":"Figure: Kubernetes 云原生的操作系统","alt":"Kubernetes 云原生的操作系统","nro":58,"url":"../images/00704eQkgy1frr4z08j6oj31p20w2n6n.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 云原生的操作系统","attributes":{},"skip":false,"key":"2.11.1"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.2","level":"2.11","list_caption":"Figure: 操作系统层次","alt":"操作系统层次","nro":59,"url":"../images/00704eQkgy1frr52hl4eaj31qy15en74.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"操作系统层次","attributes":{},"skip":false,"key":"2.11.2"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.3","level":"2.11","list_caption":"Figure: 云原生景观图","alt":"云原生景观图","nro":60,"url":"../images/00704eQkgy1frr53j3aiuj32fs1dc7wi.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生景观图","attributes":{},"skip":false,"key":"2.11.3"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.4","level":"2.11","list_caption":"Figure: KubeVirt架构图","alt":"KubeVirt架构图","nro":61,"url":"../images/00704eQkgy1frr54de5oyj31qw14qn2x.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"KubeVirt架构图","attributes":{},"skip":false,"key":"2.11.4"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.5","level":"2.11","list_caption":"Figure: Kubernetes中的资源隔离","alt":"Kubernetes中的资源隔离","nro":62,"url":"../images/00704eQkgy1frr54ztql2j329q0zwwlf.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes中的资源隔离","attributes":{},"skip":false,"key":"2.11.5"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.6","level":"2.11","list_caption":"Figure: OpenEBS 控制平面架构","alt":"OpenEBS 控制平面架构","nro":63,"url":"../images/00704eQkgy1frr56m7z2sj31y010y17y.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenEBS 控制平面架构","attributes":{},"skip":false,"key":"2.11.6"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.7","level":"2.11","list_caption":"Figure: OpenEBS 的存储卷管理","alt":"OpenEBS 的存储卷管理","nro":64,"url":"../images/00704eQkgy1frr57nm2mnj31xk11qqej.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenEBS 的存储卷管理","attributes":{},"skip":false,"key":"2.11.7"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.8","level":"2.11","list_caption":"Figure: Hadoop YARN 迁移到 Kubernetes的示例","alt":"Hadoop YARN 迁移到 Kubernetes的示例","nro":65,"url":"../images/00704eQkgy1frr58ebf2lj323o11219r.jpg","index":8,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Hadoop YARN 迁移到 Kubernetes的示例","attributes":{},"skip":false,"key":"2.11.8"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.9","level":"2.11","list_caption":"Figure: Spark on Yarn with Kubernetes","alt":"Spark on Yarn with Kubernetes","nro":66,"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.11.9"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.10","level":"2.11","list_caption":"Figure: 云原生与12因素应用","alt":"云原生与12因素应用","nro":67,"url":"../images/00704eQkgy1frr5arzvetj31no12mdre.jpg","index":10,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生与12因素应用","attributes":{},"skip":false,"key":"2.11.10"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.11","level":"2.11","list_caption":"Figure: 云原生编程语言","alt":"云原生编程语言","nro":68,"url":"../images/00704eQkgy1frr5c8bwmtj31ou152qc3.jpg","index":11,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生编程语言","attributes":{},"skip":false,"key":"2.11.11"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.12","level":"2.11","list_caption":"Figure: Gitkube","alt":"Gitkube","nro":69,"url":"../images/00704eQkgy1frr5bulhuhj329m10iwua.jpg","index":12,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Gitkube","attributes":{},"skip":false,"key":"2.11.12"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.13","level":"2.11","list_caption":"Figure: Kuberentes中的流量管理","alt":"Kuberentes中的流量管理","nro":70,"url":"../images/00704eQkgy1frr5dsurx6j320i140tpf.jpg","index":13,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kuberentes中的流量管理","attributes":{},"skip":false,"key":"2.11.13"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.14","level":"2.11","list_caption":"Figure: Istio Service Mesh架构图","alt":"Istio Service Mesh架构图","nro":71,"url":"../images/00704eQkgy1frr5exqm7kj320u18mh2t.jpg","index":14,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio Service Mesh架构图","attributes":{},"skip":false,"key":"2.11.14"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.15","level":"2.11","list_caption":"Figure: Service Mesh架构","alt":"Service Mesh架构","nro":72,"url":"../images/00704eQkgy1frr5fxzoltj32f81akqr2.jpg","index":15,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Service Mesh架构","attributes":{},"skip":false,"key":"2.11.15"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.11.16","level":"2.11","list_caption":"Figure: Envoy proxy架构图","alt":"Envoy proxy架构图","nro":73,"url":"../images/envoy-arch.png","index":16,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Envoy proxy架构图","attributes":{},"skip":false,"key":"2.11.16"},{"backlink":"concepts/index.html#fig3.1.1","level":"3.1","list_caption":"Figure: Borg架构","alt":"Borg架构","nro":74,"url":"../images/borg.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Borg架构","attributes":{},"skip":false,"key":"3.1.1"},{"backlink":"concepts/index.html#fig3.1.2","level":"3.1","list_caption":"Figure: Kubernetes架构","alt":"Kubernetes架构","nro":75,"url":"../images/architecture.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes架构","attributes":{},"skip":false,"key":"3.1.2"},{"backlink":"concepts/index.html#fig3.1.3","level":"3.1","list_caption":"Figure: Kuberentes架构(图片来自于网络)","alt":"Kuberentes架构(图片来自于网络)","nro":76,"url":"../images/kubernetes-high-level-component-archtecture.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kuberentes架构(图片来自于网络)","attributes":{},"skip":false,"key":"3.1.3"},{"backlink":"concepts/index.html#fig3.1.4","level":"3.1","list_caption":"Figure: kubernetes整体架构示意图","alt":"kubernetes整体架构示意图","nro":77,"url":"../images/kubernetes-whole-arch.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes整体架构示意图","attributes":{},"skip":false,"key":"3.1.4"},{"backlink":"concepts/index.html#fig3.1.5","level":"3.1","list_caption":"Figure: Kubernetes master架构示意图","alt":"Kubernetes master架构示意图","nro":78,"url":"../images/kubernetes-master-arch.png","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes master架构示意图","attributes":{},"skip":false,"key":"3.1.5"},{"backlink":"concepts/index.html#fig3.1.6","level":"3.1","list_caption":"Figure: kubernetes node架构示意图","alt":"kubernetes node架构示意图","nro":79,"url":"../images/kubernetes-node-arch.png","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes node架构示意图","attributes":{},"skip":false,"key":"3.1.6"},{"backlink":"concepts/index.html#fig3.1.7","level":"3.1","list_caption":"Figure: Kubernetes分层架构示意图","alt":"Kubernetes分层架构示意图","nro":80,"url":"../images/kubernetes-layers-arch.png","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes分层架构示意图","attributes":{},"skip":false,"key":"3.1.7"},{"backlink":"concepts/concepts.html#fig3.1.1.1","level":"3.1.1","list_caption":"Figure: Kubernetes 分层架构示意图","alt":"Kubernetes 分层架构示意图","nro":81,"url":"../images/006tNc79ly1fzniqvmi51j31gq0s0q5u.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 分层架构示意图","attributes":{},"skip":false,"key":"3.1.1.1"},{"backlink":"concepts/open-interfaces.html#fig3.1.3.1","level":"3.1.3","list_caption":"Figure: 开放接口","alt":"开放接口","nro":82,"url":"../images/open-interfaces.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"开放接口","attributes":{},"skip":false,"key":"3.1.3.1"},{"backlink":"concepts/cri.html#fig3.1.3.1.1","level":"3.1.3.1","list_caption":"Figure: CRI架构-图片来自kubernetes blog","alt":"CRI架构-图片来自kubernetes blog","nro":83,"url":"../images/cri-architecture.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CRI架构-图片来自kubernetes blog","attributes":{},"skip":false,"key":"3.1.3.1.1"},{"backlink":"concepts/flannel.html#fig3.2.1.1","level":"3.2.1","list_caption":"Figure: flannel网络架构(图片来自openshift)","alt":"flannel网络架构(图片来自openshift)","nro":84,"url":"../images/flannel-networking.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"flannel网络架构(图片来自openshift)","attributes":{},"skip":false,"key":"3.2.1.1"},{"backlink":"concepts/calico.html#fig3.2.2.1","level":"3.2.2","list_caption":"Figure: Calico","alt":"Calico","nro":85,"url":"../images/006tNc79gy1fz65bt7ieej30c90bsgn2.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Calico","attributes":{},"skip":false,"key":"3.2.2.1"},{"backlink":"concepts/calico.html#fig3.2.2.2","level":"3.2.2","list_caption":"Figure: CRI架构-图片来自https://www.jianshu.com/p/f0177b84de66","alt":"CRI架构-图片来自https://www.jianshu.com/p/f0177b84de66","nro":86,"url":"../images/calico.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CRI架构-图片来自https://www.jianshu.com/p/f0177b84de66","attributes":{},"skip":false,"key":"3.2.2.2"},{"backlink":"concepts/cilium.html#fig3.2.3.1","level":"3.2.3","list_caption":"Figure: Cilium","alt":"Cilium","nro":87,"url":"../images/006tNbRwly1fwqi98i51ij30sc0j80zn.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Cilium","attributes":{},"skip":false,"key":"3.2.3.1"},{"backlink":"concepts/cilium-concepts.html#fig3.2.3.1.1","level":"3.2.3.1","list_caption":"Figure: Cilium 组件(来自 Cilium 官网)","alt":"Cilium 组件(来自 Cilium 官网)","nro":88,"url":"../images/006tNbRwly1fwztvhg0gmj318z143tdv.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Cilium 组件(来自 Cilium 官网)","attributes":{},"skip":false,"key":"3.2.3.1.1"},{"backlink":"concepts/cilium-concepts.html#fig3.2.3.1.2","level":"3.2.3.1","list_caption":"Figure: Cilium 网络配置策略","alt":"Cilium 网络配置策略","nro":89,"url":"../images/006tNbRwly1fwzreaalj6j30dz0dy3z3.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Cilium 网络配置策略","attributes":{},"skip":false,"key":"3.2.3.1.2"},{"backlink":"concepts/pod-overview.html#fig3.4.1.1","level":"3.4.1","list_caption":"Figure: pod diagram","alt":"pod diagram","nro":90,"url":"../images/pod-overview.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"pod diagram","attributes":{},"skip":false,"key":"3.4.1.1"},{"backlink":"concepts/pod.html#fig3.4.2.1","level":"3.4.2","list_caption":"Figure: Pod示意图","alt":"Pod示意图","nro":91,"url":"../images/pod-overview.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Pod示意图","attributes":{},"skip":false,"key":"3.4.2.1"},{"backlink":"concepts/pod.html#fig3.4.2.2","level":"3.4.2","list_caption":"Figure: Pod Cheatsheet","alt":"Pod Cheatsheet","nro":92,"url":"../images/kubernetes-pod-cheatsheet.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Pod Cheatsheet","attributes":{},"skip":false,"key":"3.4.2.2"},{"backlink":"concepts/pause-container.html#fig3.4.4.1","level":"3.4.4","list_caption":"Figure: Pause容器","alt":"Pause容器","nro":93,"url":"../images/pause-container.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Pause容器","attributes":{},"skip":false,"key":"3.4.4.1"},{"backlink":"concepts/pod-lifecycle.html#fig3.4.6.1","level":"3.4.6","list_caption":"Figure: Pod的生命周期示意图(图片来自网络)","alt":"Pod的生命周期示意图(图片来自网络)","nro":94,"url":"../images/kubernetes-pod-life-cycle.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Pod的生命周期示意图(图片来自网络)","attributes":{},"skip":false,"key":"3.4.6.1"},{"backlink":"concepts/label.html#fig3.5.3.1","level":"3.5.3","list_caption":"Figure: label示意图","alt":"label示意图","nro":95,"url":"../images/labels.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"label示意图","attributes":{},"skip":false,"key":"3.5.3.1"},{"backlink":"concepts/deployment.html#fig3.6.1.1","level":"3.6.1","list_caption":"Figure: kubernetes deployment cheatsheet","alt":"kubernetes deployment cheatsheet","nro":96,"url":"../images/deployment-cheatsheet.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes deployment cheatsheet","attributes":{},"skip":false,"key":"3.6.1.1"},{"backlink":"concepts/horizontal-pod-autoscaling.html#fig3.6.7.1","level":"3.6.7","list_caption":"Figure: horizontal-pod-autoscaler","alt":"horizontal-pod-autoscaler","nro":97,"url":"../images/horizontal-pod-autoscaler.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"horizontal-pod-autoscaler","attributes":{},"skip":false,"key":"3.6.7.1"},{"backlink":"concepts/service.html#fig3.7.1.1","level":"3.7.1","list_caption":"Figure: userspace代理模式下Service概览图","alt":"userspace代理模式下Service概览图","nro":98,"url":"../images/services-userspace-overview.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"userspace代理模式下Service概览图","attributes":{},"skip":false,"key":"3.7.1.1"},{"backlink":"concepts/service.html#fig3.7.1.2","level":"3.7.1","list_caption":"Figure: iptables代理模式下Service概览图","alt":"iptables代理模式下Service概览图","nro":99,"url":"../images/services-iptables-overview.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"iptables代理模式下Service概览图","attributes":{},"skip":false,"key":"3.7.1.2"},{"backlink":"concepts/service.html#fig3.7.1.3","level":"3.7.1","list_caption":"Figure: ipvs代理模式下Service概览图","alt":"ipvs代理模式下Service概览图","nro":100,"url":"../images/service-ipvs-overview.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"ipvs代理模式下Service概览图","attributes":{},"skip":false,"key":"3.7.1.3"},{"backlink":"concepts/service-catalog.html#fig3.10.5.1","level":"3.10.5","list_caption":"Figure: Service Catalog Architecture","alt":"Service Catalog Architecture","nro":101,"url":"../images/service-catalog-architecture.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Service Catalog Architecture","attributes":{},"skip":false,"key":"3.10.5.1"},{"backlink":"concepts/service-catalog.html#fig3.10.5.2","level":"3.10.5","list_caption":"Figure: List Services","alt":"List Services","nro":102,"url":"../images/service-catalog-list.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"List Services","attributes":{},"skip":false,"key":"3.10.5.2"},{"backlink":"concepts/service-catalog.html#fig3.10.5.3","level":"3.10.5","list_caption":"Figure: Provision a Service","alt":"Provision a Service","nro":103,"url":"../images/service-catalog-provision.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Provision a Service","attributes":{},"skip":false,"key":"3.10.5.3"},{"backlink":"concepts/service-catalog.html#fig3.10.5.4","level":"3.10.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":"3.10.5.4"},{"backlink":"concepts/service-catalog.html#fig3.10.5.5","level":"3.10.5","list_caption":"Figure: Map connection credentials","alt":"Map connection credentials","nro":105,"url":"../images/service-catalog-map.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Map connection credentials","attributes":{},"skip":false,"key":"3.10.5.5"},{"backlink":"guide/using-kubectl.html#fig4.3.2.1","level":"4.3.2","list_caption":"Figure: kubectl cheatsheet","alt":"kubectl cheatsheet","nro":106,"url":"../images/kubernetes-kubectl-cheatsheet.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubectl cheatsheet","attributes":{},"skip":false,"key":"4.3.2.1"},{"backlink":"guide/using-kubectl.html#fig4.3.2.2","level":"4.3.2","list_caption":"Figure: 增加kubeclt命令的工具(图片来自网络)","alt":"增加kubeclt命令的工具(图片来自网络)","nro":107,"url":"../images/tools-to-supercharge-kubectl.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"增加kubeclt命令的工具(图片来自网络)","attributes":{},"skip":false,"key":"4.3.2.2"},{"backlink":"guide/using-kubectl.html#fig4.3.2.3","level":"4.3.2","list_caption":"Figure: 增强的kubectl命令","alt":"增强的kubectl命令","nro":108,"url":"../images/supercharged-kubectl.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"增强的kubectl命令","attributes":{},"skip":false,"key":"4.3.2.3"},{"backlink":"guide/using-kubectl.html#fig4.3.2.4","level":"4.3.2","list_caption":"Figure: kube-shell页面","alt":"kube-shell页面","nro":109,"url":"../images/kube-shell.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kube-shell页面","attributes":{},"skip":false,"key":"4.3.2.4"},{"backlink":"guide/ip-masq-agent.html#fig4.4.5.1","level":"4.4.5","list_caption":"Figure: IP伪装代理示意图","alt":"IP伪装代理示意图","nro":110,"url":"../images/ip-masq.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"IP伪装代理示意图","attributes":{},"skip":false,"key":"4.4.5.1"},{"backlink":"guide/auth-with-kubeconfig-or-token.html#fig4.4.6.1","level":"4.4.6","list_caption":"Figure: kubeconfig文件","alt":"kubeconfig文件","nro":111,"url":"../images/brand-kubeconfig-yaml.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubeconfig文件","attributes":{},"skip":false,"key":"4.4.6.1"},{"backlink":"guide/authentication.html#fig4.4.7.1","level":"4.4.7","list_caption":"Figure: Kubernetes OpenID Connect Flow","alt":"Kubernetes OpenID Connect Flow","nro":112,"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":"4.4.7.1"},{"backlink":"guide/cabin-mobile-dashboard-for-kubernetes.html#fig4.5.6.1","level":"4.5.6","list_caption":"Figure: App Store","alt":"App Store","nro":113,"url":"../images/cabin-kubernetes-mobile-dashboard-1.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"App Store","attributes":{},"skip":false,"key":"4.5.6.1"},{"backlink":"guide/cabin-mobile-dashboard-for-kubernetes.html#fig4.5.6.2","level":"4.5.6","list_caption":"Figure: 在手机上操作Kubernetes集群","alt":"在手机上操作Kubernetes集群","nro":114,"url":"../images/cabin-kubernetes-mobile-dashboard-4.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"在手机上操作Kubernetes集群","attributes":{},"skip":false,"key":"4.5.6.2"},{"backlink":"guide/kubernetes-desktop-client.html#fig4.5.7.1","level":"4.5.7","list_caption":"Figure: Lens Kubernetes IDE 界面","alt":"Lens Kubernetes IDE 界面","nro":115,"url":"../images/lens.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Lens Kubernetes IDE 界面","attributes":{},"skip":false,"key":"4.5.7.1"},{"backlink":"guide/kubernator-kubernetes-ui.html#fig4.5.8.1","level":"4.5.8","list_caption":"Figure: Kubernator catalog 页面","alt":"Kubernator catalog 页面","nro":116,"url":"../images/kubernator-catalog.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernator catalog 页面","attributes":{},"skip":false,"key":"4.5.8.1"},{"backlink":"guide/kubernator-kubernetes-ui.html#fig4.5.8.2","level":"4.5.8","list_caption":"Figure: Kubernator rbac 页面","alt":"Kubernator rbac 页面","nro":117,"url":"../images/kubernator-rbac.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernator rbac 页面","attributes":{},"skip":false,"key":"4.5.8.2"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.1","level":"4.6.1","list_caption":"Figure: 流程图","alt":"流程图","nro":118,"url":"../images/how-to-use-kubernetes-with-istio.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"流程图","attributes":{},"skip":false,"key":"4.6.1.1"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.2","level":"4.6.1","list_caption":"Figure: API","alt":"API","nro":119,"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":"4.6.1.2"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.3","level":"4.6.1","list_caption":"Figure: wercker构建页面","alt":"wercker构建页面","nro":120,"url":"../images/k8s-app-monitor-agent-wercker.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"wercker构建页面","attributes":{},"skip":false,"key":"4.6.1.3"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.4","level":"4.6.1","list_caption":"Figure: 图表","alt":"图表","nro":121,"url":"../images/k8s-app-monitor-agent.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"图表","attributes":{},"skip":false,"key":"4.6.1.4"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.5","level":"4.6.1","list_caption":"Figure: Grafana页面","alt":"Grafana页面","nro":122,"url":"../images/k8s-app-monitor-istio-grafana.png","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Grafana页面","attributes":{},"skip":false,"key":"4.6.1.5"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.6","level":"4.6.1","list_caption":"Figure: servicegraph页面","alt":"servicegraph页面","nro":123,"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":"4.6.1.6"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.7","level":"4.6.1","list_caption":"Figure: Zipkin页面","alt":"Zipkin页面","nro":124,"url":"../images/k8s-app-monitor-istio-zipkin.png","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Zipkin页面","attributes":{},"skip":false,"key":"4.6.1.7"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig4.6.2.1","level":"4.6.2","list_caption":"Figure: 将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","alt":"将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","nro":125,"url":"../images/migrating-monolith-to-kubernetes.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","attributes":{},"skip":false,"key":"4.6.2.1"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig4.6.2.2","level":"4.6.2","list_caption":"Figure: spark on yarn with kubernetes","alt":"spark on yarn with kubernetes","nro":126,"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":"4.6.2.2"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig4.6.2.3","level":"4.6.2","list_caption":"Figure: Terms","alt":"Terms","nro":127,"url":"../images/terms-in-kubernetes-app-deployment.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Terms","attributes":{},"skip":false,"key":"4.6.2.3"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig4.6.2.4","level":"4.6.2","list_caption":"Figure: 分解步骤解析","alt":"分解步骤解析","nro":128,"url":"../images/migrating-hadoop-yarn-to-kubernetes.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"分解步骤解析","attributes":{},"skip":false,"key":"4.6.2.4"},{"backlink":"practice/node-installation.html#fig5.2.7.1","level":"5.2.7","list_caption":"Figure: nginx欢迎页面","alt":"nginx欢迎页面","nro":129,"url":"../images/kubernetes-installation-test-nginx.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"nginx欢迎页面","attributes":{},"skip":false,"key":"5.2.7.1"},{"backlink":"practice/dashboard-addon-installation.html#fig5.2.9.1","level":"5.2.9","list_caption":"Figure: kubernetes dashboard","alt":"kubernetes dashboard","nro":130,"url":"../images/kubernetes-dashboard-raw.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes dashboard","attributes":{},"skip":false,"key":"5.2.9.1"},{"backlink":"practice/dashboard-addon-installation.html#fig5.2.9.2","level":"5.2.9","list_caption":"Figure: V1.6.3版本的dashboard界面","alt":"V1.6.3版本的dashboard界面","nro":131,"url":"../images/dashboard-v163.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"V1.6.3版本的dashboard界面","attributes":{},"skip":false,"key":"5.2.9.2"},{"backlink":"practice/dashboard-addon-installation.html#fig5.2.9.3","level":"5.2.9","list_caption":"Figure: pod无法正常启动","alt":"pod无法正常启动","nro":132,"url":"../images/dashboard-addon-installation001.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"pod无法正常启动","attributes":{},"skip":false,"key":"5.2.9.3"},{"backlink":"practice/heapster-addon-installation.html#fig5.2.10.1","level":"5.2.10","list_caption":"Figure: dashboard-heapster","alt":"dashboard-heapster","nro":133,"url":"../images/kubernetes-dashboard-with-heapster.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"dashboard-heapster","attributes":{},"skip":false,"key":"5.2.10.1"},{"backlink":"practice/heapster-addon-installation.html#fig5.2.10.2","level":"5.2.10","list_caption":"Figure: grafana","alt":"grafana","nro":134,"url":"../images/kubernetes-heapster-grafana.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"grafana","attributes":{},"skip":false,"key":"5.2.10.2"},{"backlink":"practice/heapster-addon-installation.html#fig5.2.10.3","level":"5.2.10","list_caption":"Figure: kubernetes-influxdb-heapster","alt":"kubernetes-influxdb-heapster","nro":135,"url":"../images/kubernetes-influxdb-heapster.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes-influxdb-heapster","attributes":{},"skip":false,"key":"5.2.10.3"},{"backlink":"practice/heapster-addon-installation.html#fig5.2.10.4","level":"5.2.10","list_caption":"Figure: 修改grafana模板","alt":"修改grafana模板","nro":136,"url":"../images/grafana-dashboard-setting.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"修改grafana模板","attributes":{},"skip":false,"key":"5.2.10.4"},{"backlink":"practice/efk-addon-installation.html#fig5.2.11.1","level":"5.2.11","list_caption":"Figure: es-setting","alt":"es-setting","nro":137,"url":"../images/es-setting.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"es-setting","attributes":{},"skip":false,"key":"5.2.11.1"},{"backlink":"practice/efk-addon-installation.html#fig5.2.11.2","level":"5.2.11","list_caption":"Figure: es-home","alt":"es-home","nro":138,"url":"../images/kubernetes-efk-kibana.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"es-home","attributes":{},"skip":false,"key":"5.2.11.2"},{"backlink":"practice/traefik-ingress-installation.html#fig5.4.1.1","level":"5.4.1","list_caption":"Figure: kubernetes-dashboard","alt":"kubernetes-dashboard","nro":139,"url":"../images/traefik-dashboard.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes-dashboard","attributes":{},"skip":false,"key":"5.4.1.1"},{"backlink":"practice/traefik-ingress-installation.html#fig5.4.1.2","level":"5.4.1","list_caption":"Figure: traefik-nginx","alt":"traefik-nginx","nro":140,"url":"../images/traefik-nginx.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"traefik-nginx","attributes":{},"skip":false,"key":"5.4.1.2"},{"backlink":"practice/traefik-ingress-installation.html#fig5.4.1.3","level":"5.4.1","list_caption":"Figure: traefik-guestbook","alt":"traefik-guestbook","nro":141,"url":"../images/traefik-guestbook.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"traefik-guestbook","attributes":{},"skip":false,"key":"5.4.1.3"},{"backlink":"practice/distributed-load-test.html#fig5.4.2.1","level":"5.4.2","list_caption":"Figure: 使用dashboard来扩容","alt":"使用dashboard来扩容","nro":142,"url":"../images/dashbaord-scale.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"使用dashboard来扩容","attributes":{},"skip":false,"key":"5.4.2.1"},{"backlink":"practice/distributed-load-test.html#fig5.4.2.2","level":"5.4.2","list_caption":"Figure: Traefik的UI","alt":"Traefik的UI","nro":143,"url":"../images/traefik-dashboard-locust.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Traefik的UI","attributes":{},"skip":false,"key":"5.4.2.2"},{"backlink":"practice/distributed-load-test.html#fig5.4.2.3","level":"5.4.2","list_caption":"Figure: Locust启动界面","alt":"Locust启动界面","nro":144,"url":"../images/locust-start-swarming.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Locust启动界面","attributes":{},"skip":false,"key":"5.4.2.3"},{"backlink":"practice/distributed-load-test.html#fig5.4.2.4","level":"5.4.2","list_caption":"Figure: Dashboard查看页面","alt":"Dashboard查看页面","nro":145,"url":"../images/sample-webapp-rc.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Dashboard查看页面","attributes":{},"skip":false,"key":"5.4.2.4"},{"backlink":"practice/distributed-load-test.html#fig5.4.2.5","level":"5.4.2","list_caption":"Figure: Locust测试结果页面","alt":"Locust测试结果页面","nro":146,"url":"../images/locust-dashboard.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Locust测试结果页面","attributes":{},"skip":false,"key":"5.4.2.5"},{"backlink":"practice/network-and-cluster-perfermance-test.html#fig5.4.3.1","level":"5.4.3","list_caption":"Figure: kubernetes-dashboard","alt":"kubernetes-dashboard","nro":147,"url":"../images/kubenetes-e2e-test.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes-dashboard","attributes":{},"skip":false,"key":"5.4.3.1"},{"backlink":"practice/network-and-cluster-perfermance-test.html#fig5.4.3.2","level":"5.4.3","list_caption":"Figure: locust测试页面","alt":"locust测试页面","nro":148,"url":"../images/kubernetes-locust-test.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"locust测试页面","attributes":{},"skip":false,"key":"5.4.3.2"},{"backlink":"practice/edge-node-configuration.html#fig5.4.4.1","level":"5.4.4","list_caption":"Figure: 边缘节点架构","alt":"边缘节点架构","nro":149,"url":"../images/kubernetes-edge-node-architecture.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"边缘节点架构","attributes":{},"skip":false,"key":"5.4.4.1"},{"backlink":"practice/edge-node-configuration.html#fig5.4.4.2","level":"5.4.4","list_caption":"Figure: 使用域名来访问Kubernetes中的服务","alt":"使用域名来访问Kubernetes中的服务","nro":150,"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":"5.4.4.2"},{"backlink":"practice/configuring-dns.html#fig5.4.6.1.1","level":"5.4.6.1","list_caption":"Figure: DNS lookup flow","alt":"DNS lookup flow","nro":151,"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":"5.4.6.1.1"},{"backlink":"practice/master-ha.html#fig5.5.1.1","level":"5.5.1","list_caption":"Figure: Master HA架构图","alt":"Master HA架构图","nro":152,"url":"../images/master-ha.JPG","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Master HA架构图","attributes":{},"skip":false,"key":"5.5.1.1"},{"backlink":"practice/app-log-collection.html#fig5.5.3.1","level":"5.5.3","list_caption":"Figure: filebeat日志收集架构图","alt":"filebeat日志收集架构图","nro":153,"url":"../images/filebeat-log-collector.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"filebeat日志收集架构图","attributes":{},"skip":false,"key":"5.5.3.1"},{"backlink":"practice/app-log-collection.html#fig5.5.3.2","level":"5.5.3","list_caption":"Figure: Kibana页面","alt":"Kibana页面","nro":154,"url":"../images/filebeat-docker-test.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kibana页面","attributes":{},"skip":false,"key":"5.5.3.2"},{"backlink":"practice/app-log-collection.html#fig5.5.3.3","level":"5.5.3","list_caption":"Figure: filebeat收集的日志详细信息","alt":"filebeat收集的日志详细信息","nro":155,"url":"../images/kubernetes-filebeat-detail.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"filebeat收集的日志详细信息","attributes":{},"skip":false,"key":"5.5.3.3"},{"backlink":"practice/monitor.html#fig5.5.5.1","level":"5.5.5","list_caption":"Figure: Kubernetes集群中的监控","alt":"Kubernetes集群中的监控","nro":156,"url":"../images/monitoring-in-kubernetes.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes集群中的监控","attributes":{},"skip":false,"key":"5.5.5.1"},{"backlink":"practice/monitor.html#fig5.5.5.2","level":"5.5.5","list_caption":"Figure: kubernetes的容器命名规则示意图","alt":"kubernetes的容器命名规则示意图","nro":157,"url":"../images/kubernetes-container-naming-rule.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubernetes的容器命名规则示意图","attributes":{},"skip":false,"key":"5.5.5.2"},{"backlink":"practice/monitor.html#fig5.5.5.3","level":"5.5.5","list_caption":"Figure: Heapster架构图(改进版)","alt":"Heapster架构图(改进版)","nro":158,"url":"../images/kubernetes-heapster-monitoring.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Heapster架构图(改进版)","attributes":{},"skip":false,"key":"5.5.5.3"},{"backlink":"practice/monitor.html#fig5.5.5.4","level":"5.5.5","list_caption":"Figure: 应用监控架构图","alt":"应用监控架构图","nro":159,"url":"../images/kubernetes-app-monitoring.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"应用监控架构图","attributes":{},"skip":false,"key":"5.5.5.4"},{"backlink":"practice/monitor.html#fig5.5.5.5","level":"5.5.5","list_caption":"Figure: 应用拓扑图","alt":"应用拓扑图","nro":160,"url":"../images/weave-scope-service-topology.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"应用拓扑图","attributes":{},"skip":false,"key":"5.5.5.5"},{"backlink":"practice/data-persistence-problem.html#fig5.5.6.1","level":"5.5.6","list_caption":"Figure: 日志持久化收集解决方案示意图","alt":"日志持久化收集解决方案示意图","nro":161,"url":"../images/log-persistence-logstash.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"日志持久化收集解决方案示意图","attributes":{},"skip":false,"key":"5.5.6.1"},{"backlink":"practice/storage-for-containers-using-glusterfs-with-openshift.html#fig5.6.1.3.1","level":"5.6.1.3","list_caption":"Figure: 创建存储","alt":"创建存储","nro":162,"url":"../images/create-gluster-storage.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"创建存储","attributes":{},"skip":false,"key":"5.6.1.3.1"},{"backlink":"practice/storage-for-containers-using-glusterfs-with-openshift.html#fig5.6.1.3.2","level":"5.6.1.3","list_caption":"Figure: Screen Shot 2017-03-24 at 11.09.34.png","alt":"Screen Shot 2017-03-24 at 11.09.34.png","nro":163,"url":"https://keithtenzer.files.wordpress.com/2017/03/screen-shot-2017-03-24-at-11-09-341.png?w=440","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Screen Shot 2017-03-24 at 11.09.34.png","attributes":{},"skip":false,"key":"5.6.1.3.2"},{"backlink":"practice/openebs.html#fig5.6.4.1","level":"5.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":164,"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":"5.6.4.1"},{"backlink":"practice/openebs.html#fig5.6.4.2","level":"5.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":165,"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":"5.6.4.2"},{"backlink":"practice/using-openebs-for-persistent-storage.html#fig5.6.4.1.1","level":"5.6.4.1","list_caption":"Figure: Kubernetes iSCSI架构","alt":"Kubernetes iSCSI架构","nro":166,"url":"../images/iscsi-on-kubernetes.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes iSCSI架构","attributes":{},"skip":false,"key":"5.6.4.1.1"},{"backlink":"practice/using-heapster-to-get-object-metrics.html#fig5.7.1.1.1","level":"5.7.1.1","list_caption":"Figure: Heapster架构图","alt":"Heapster架构图","nro":167,"url":"../images/heapster-architecture.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Heapster架构图","attributes":{},"skip":false,"key":"5.7.1.1.1"},{"backlink":"practice/prometheus.html#fig5.7.2.1","level":"5.7.2","list_caption":"Figure: Prometheus 架构图","alt":"Prometheus 架构图","nro":168,"url":"../images/006tNbRwly1fwcgsn11fej311j0mjadw.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Prometheus 架构图","attributes":{},"skip":false,"key":"5.7.2.1"},{"backlink":"practice/using-prometheus-to-monitor-kuberentes-cluster.html#fig5.7.2.1.1","level":"5.7.2.1","list_caption":"Figure: Grafana页面","alt":"Grafana页面","nro":169,"url":"../images/kubernetes-prometheus-monitoring.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Grafana页面","attributes":{},"skip":false,"key":"5.7.2.1.1"},{"backlink":"practice/promql.html#fig5.7.2.2.1","level":"5.7.2.2","list_caption":"Figure: Prometheus 的查询页面","alt":"Prometheus 的查询页面","nro":170,"url":"../images/006tNbRwly1fwcl7v28rhj30xl0onadv.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Prometheus 的查询页面","attributes":{},"skip":false,"key":"5.7.2.2.1"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.1","level":"5.7.3","list_caption":"Figure: Vistio的集群级别可视化","alt":"Vistio的集群级别可视化","nro":171,"url":"../images/00704eQkgy1fshft5oxlwj318g0pe0wp.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Vistio的集群级别可视化","attributes":{},"skip":false,"key":"5.7.3.1"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.2","level":"5.7.3","list_caption":"Figure: Prometheus查询","alt":"Prometheus查询","nro":172,"url":"../images/00704eQkgy1fshg0vw25ij318g0jzqjq.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Prometheus查询","attributes":{},"skip":false,"key":"5.7.3.2"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.3","level":"5.7.3","list_caption":"Figure: vistio-api的期望输出","alt":"vistio-api的期望输出","nro":173,"url":"../images/00704eQkgy1fshi61t04oj310q17c0y1.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"vistio-api的期望输出","attributes":{},"skip":false,"key":"5.7.3.3"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.4","level":"5.7.3","list_caption":"Figure: Vistio主页面","alt":"Vistio主页面","nro":174,"url":"../images/00704eQkgy1fshi98duzgj318g0l2406.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Vistio主页面","attributes":{},"skip":false,"key":"5.7.3.4"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.5","level":"5.7.3","list_caption":"Figure: istio mesh的网络流量","alt":"istio mesh的网络流量","nro":175,"url":"../images/00704eQkgy1fshibdwcj3j318g0p8th1.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"istio mesh的网络流量","attributes":{},"skip":false,"key":"5.7.3.5"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.6","level":"5.7.3","list_caption":"Figure: 查明网络问题","alt":"查明网络问题","nro":176,"url":"../images/00704eQkgy1fshicc7or1j318g0p8ahr.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"查明网络问题","attributes":{},"skip":false,"key":"5.7.3.6"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.7","level":"5.7.3","list_caption":"Figure: vistio api的不正确输出","alt":"vistio api的不正确输出","nro":177,"url":"../images/00704eQkgy1fshie7wxkyj30ks0f4myd.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"vistio api的不正确输出","attributes":{},"skip":false,"key":"5.7.3.7"},{"backlink":"practice/opentracing.html#fig5.8.1.1","level":"5.8.1","list_caption":"Figure: Jaeger UI","alt":"Jaeger UI","nro":178,"url":"../images/006tNbRwly1fwjg48fh7xj31kw0wedrg.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Jaeger UI","attributes":{},"skip":false,"key":"5.8.1.1"},{"backlink":"practice/opentracing.html#fig5.8.1.2","level":"5.8.1","list_caption":"Figure: Chrome Inspector","alt":"Chrome Inspector","nro":179,"url":"../images/006tNbRwly1fwjkfbvfluj30y70hf0y9.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Chrome Inspector","attributes":{},"skip":false,"key":"5.8.1.2"},{"backlink":"practice/helm.html#fig5.9.1.1","level":"5.9.1","list_caption":"Figure: Helm 架构图(来自 IBM Developer Blog)","alt":"Helm 架构图(来自 IBM Developer Blog)","nro":180,"url":"../images/helm-chart.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Helm 架构图(来自 IBM Developer Blog)","attributes":{},"skip":false,"key":"5.9.1.1"},{"backlink":"practice/create-private-charts-repo.html#fig5.9.2.1","level":"5.9.2","list_caption":"Figure: Helm monocular界面","alt":"Helm monocular界面","nro":181,"url":"../images/helm-monocular-jimmysong.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Helm monocular界面","attributes":{},"skip":false,"key":"5.9.2.1"},{"backlink":"practice/ci-cd.html#fig5.10.1","level":"5.10","list_caption":"Figure: CI/CD with Kubernetes","alt":"CI/CD with Kubernetes","nro":182,"url":"../images/00704eQkgy1fsaxszh01vj30da0j2jvn.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CI/CD with Kubernetes","attributes":{},"skip":false,"key":"5.10.1"},{"backlink":"practice/ci-cd.html#fig5.10.2","level":"5.10","list_caption":"Figure: Kubernetes改变了应用的基础架构","alt":"Kubernetes改变了应用的基础架构","nro":183,"url":"../images/00704eQkgy1fsayashxz3j31c00w6aed.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes改变了应用的基础架构","attributes":{},"skip":false,"key":"5.10.2"},{"backlink":"practice/ci-cd.html#fig5.10.3","level":"5.10","list_caption":"Figure: Kubernetes中的CI/CD","alt":"Kubernetes中的CI/CD","nro":184,"url":"../images/00704eQkgy1fsayfzk3ezj31bu0tkdky.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes中的CI/CD","attributes":{},"skip":false,"key":"5.10.3"},{"backlink":"practice/ci-cd.html#fig5.10.4","level":"5.10","list_caption":"Figure: 云原生工作负载","alt":"云原生工作负载","nro":185,"url":"../images/00704eQkgy1fsayrk6vppj31bu0w0gsd.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生工作负载","attributes":{},"skip":false,"key":"5.10.4"},{"backlink":"practice/ci-cd.html#fig5.10.5","level":"5.10","list_caption":"Figure: 云原生工作负载映射到Kuberentes原语","alt":"云原生工作负载映射到Kuberentes原语","nro":186,"url":"../images/00704eQkgy1fsaytbabxgj31c00w2n4r.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生工作负载映射到Kuberentes原语","attributes":{},"skip":false,"key":"5.10.5"},{"backlink":"practice/ci-cd.html#fig5.10.6","level":"5.10","list_caption":"Figure: spinnaker中的组件及角色交互关系","alt":"spinnaker中的组件及角色交互关系","nro":187,"url":"../images/00704eQkgy1fsaz2wirz9j31bs0vygsb.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"spinnaker中的组件及角色交互关系","attributes":{},"skip":false,"key":"5.10.6"},{"backlink":"practice/ci-cd.html#fig5.10.7","level":"5.10","list_caption":"Figure: Spinnaker部署流水线","alt":"Spinnaker部署流水线","nro":188,"url":"../images/00704eQkgy1fsaz3yo227j31c60mgdim.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Spinnaker部署流水线","attributes":{},"skip":false,"key":"5.10.7"},{"backlink":"practice/ci-cd.html#fig5.10.8","level":"5.10","list_caption":"Figure: Spinnaker的预发布流水线","alt":"Spinnaker的预发布流水线","nro":189,"url":"../images/00704eQkgy1fsaz50k2atj31bs0mitbn.jpg","index":8,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Spinnaker的预发布流水线","attributes":{},"skip":false,"key":"5.10.8"},{"backlink":"practice/ci-cd.html#fig5.10.9","level":"5.10","list_caption":"Figure: Spinnaker的生产流水线","alt":"Spinnaker的生产流水线","nro":190,"url":"../images/00704eQkgy1fsaz5n5qs9j31by0motbm.jpg","index":9,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Spinnaker的生产流水线","attributes":{},"skip":false,"key":"5.10.9"},{"backlink":"practice/ci-cd.html#fig5.10.10","level":"5.10","list_caption":"Figure: 可观察性","alt":"可观察性","nro":191,"url":"../images/00704eQkgy1fsazabn0b9j31by0w6791.jpg","index":10,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"可观察性","attributes":{},"skip":false,"key":"5.10.10"},{"backlink":"practice/ci-cd.html#fig5.10.11","level":"5.10","list_caption":"Figure: Prometheus生态系统中的组件","alt":"Prometheus生态系统中的组件","nro":192,"url":"../images/00704eQkgy1fsazcclee6j31c20w6n5y.jpg","index":11,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Prometheus生态系统中的组件","attributes":{},"skip":false,"key":"5.10.11"},{"backlink":"practice/jenkins-ci-cd.html#fig5.10.1.1","level":"5.10.1","list_caption":"Figure: 基于Jenkins的持续集成与发布","alt":"基于Jenkins的持续集成与发布","nro":193,"url":"../images/kubernetes-jenkins-ci-cd.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"基于Jenkins的持续集成与发布","attributes":{},"skip":false,"key":"5.10.1.1"},{"backlink":"practice/drone-ci-cd.html#fig5.10.2.1","level":"5.10.2","list_caption":"Figure: OAuth注册","alt":"OAuth注册","nro":194,"url":"../images/github-oauth-register.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OAuth注册","attributes":{},"skip":false,"key":"5.10.2.1"},{"backlink":"practice/drone-ci-cd.html#fig5.10.2.2","level":"5.10.2","list_caption":"Figure: OAuth key","alt":"OAuth key","nro":195,"url":"../images/github-oauth-drone-key.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OAuth key","attributes":{},"skip":false,"key":"5.10.2.2"},{"backlink":"practice/drone-ci-cd.html#fig5.10.2.3","level":"5.10.2","list_caption":"Figure: Drone登陆界面","alt":"Drone登陆界面","nro":196,"url":"../images/drone-login-github.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Drone登陆界面","attributes":{},"skip":false,"key":"5.10.2.3"},{"backlink":"practice/drone-ci-cd.html#fig5.10.2.4","level":"5.10.2","list_caption":"Figure: Github启用repo设置","alt":"Github启用repo设置","nro":197,"url":"../images/drone-github-active.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Github启用repo设置","attributes":{},"skip":false,"key":"5.10.2.4"},{"backlink":"practice/drone-ci-cd.html#fig5.10.2.5","level":"5.10.2","list_caption":"Figure: Github单个repo设置","alt":"Github单个repo设置","nro":198,"url":"../images/drone-github-repo-setting.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Github单个repo设置","attributes":{},"skip":false,"key":"5.10.2.5"},{"backlink":"practice/manually-upgrade.html#fig5.11.1.1","level":"5.11.1","list_caption":"Figure: Kubernetes零宕机时间升级建议","alt":"Kubernetes零宕机时间升级建议","nro":199,"url":"../images/zero-downtime-kubernetes-upgrade-tips.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes零宕机时间升级建议","attributes":{},"skip":false,"key":"5.11.1.1"},{"backlink":"practice/manually-upgrade.html#fig5.11.1.2","level":"5.11.1","list_caption":"Figure: Kuberentes API对象的版本演进","alt":"Kuberentes API对象的版本演进","nro":200,"url":"../images/kubernetes-apversions-changes.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kuberentes API对象的版本演进","attributes":{},"skip":false,"key":"5.11.1.2"},{"backlink":"practice/dashboard-upgrade.html#fig5.11.2.1","level":"5.11.2","list_caption":"Figure: 登陆界面","alt":"登陆界面","nro":201,"url":"../images/kubernetes-dashboard-1.7.1-login.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"登陆界面","attributes":{},"skip":false,"key":"5.11.2.1"},{"backlink":"practice/dashboard-upgrade.html#fig5.11.2.2","level":"5.11.2","list_caption":"Figure: Dashboard首页","alt":"Dashboard首页","nro":202,"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":"5.11.2.2"},{"backlink":"practice/dashboard-upgrade.html#fig5.11.2.3","level":"5.11.2","list_caption":"Figure: Dashboard用户空间页面","alt":"Dashboard用户空间页面","nro":203,"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":"5.11.2.3"},{"backlink":"practice/dashboard-upgrade.html#fig5.11.2.4","level":"5.11.2","list_caption":"Figure: kubeconfig文件","alt":"kubeconfig文件","nro":204,"url":"../images/brand-kubeconfig-yaml.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"kubeconfig文件","attributes":{},"skip":false,"key":"5.11.2.4"},{"backlink":"usecases/microservices.html#fig6.2.1","level":"6.2","list_caption":"Figure: 微服务关注的部分","alt":"微服务关注的部分","nro":205,"url":"../images/microservices-concerns.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"微服务关注的部分","attributes":{},"skip":false,"key":"6.2.1"},{"backlink":"usecases/service-discovery-in-microservices.html#fig6.2.1.1","level":"6.2.1","list_caption":"Figure: 微服务中的服务发现","alt":"微服务中的服务发现","nro":206,"url":"../images/service-discovery-in-microservices.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"微服务中的服务发现","attributes":{},"skip":false,"key":"6.2.1.1"},{"backlink":"usecases/microservices-for-java-developers.html#fig6.2.2.1","level":"6.2.2","list_caption":"Figure: Spring技术栈","alt":"Spring技术栈","nro":207,"url":"../images/spring-stack.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Spring技术栈","attributes":{},"skip":false,"key":"6.2.2.1"},{"backlink":"usecases/microservices-for-java-developers.html#fig6.2.2.2","level":"6.2.2","list_caption":"Figure: Spring Boot的知识点","alt":"Spring Boot的知识点","nro":208,"url":"../images/spring-boot-note-spots.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Spring Boot的知识点","attributes":{},"skip":false,"key":"6.2.2.2"},{"backlink":"usecases/service-mesh.html#fig6.4.1","level":"6.4","list_caption":"Figure: 下一代异构微服务架构","alt":"下一代异构微服务架构","nro":209,"url":"../images/polyglot-microservices-serivce-mesh.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"下一代异构微服务架构","attributes":{},"skip":false,"key":"6.4.1"},{"backlink":"usecases/service-mesh.html#fig6.4.2","level":"6.4","list_caption":"Figure: Service Mesh 架构图","alt":"Service Mesh 架构图","nro":210,"url":"../images/serivce-mesh-control-plane.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Service Mesh 架构图","attributes":{},"skip":false,"key":"6.4.2"},{"backlink":"usecases/service-mesh.html#fig6.4.3","level":"6.4","list_caption":"Figure: Istio vs linkerd","alt":"Istio vs linkerd","nro":211,"url":"../images/istio-vs-linkerd.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio vs linkerd","attributes":{},"skip":false,"key":"6.4.3"},{"backlink":"usecases/service-mesh-fundamental.html#fig6.4.1.1.1","level":"6.4.1.1","list_caption":"Figure: Service Mesh模型对比","alt":"Service Mesh模型对比","nro":212,"url":"../images/0069RVTdly1fuafvbnuc7j310a0oqdm9.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Service Mesh模型对比","attributes":{},"skip":false,"key":"6.4.1.1.1"},{"backlink":"usecases/service-mesh-fundamental.html#fig6.4.1.1.2","level":"6.4.1.1","list_caption":"Figure: 网状网络拓扑","alt":"网状网络拓扑","nro":213,"url":"../images/0069RVTdly1fuaie8jan8j310a0kitem.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"网状网络拓扑","attributes":{},"skip":false,"key":"6.4.1.1.2"},{"backlink":"usecases/service-mesh-fundamental.html#fig6.4.1.1.3","level":"6.4.1.1","list_caption":"Figure: Service Mesh架构图","alt":"Service Mesh架构图","nro":214,"url":"../images/0069RVTdly1fuail4d24jj31080rkgr7.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Service Mesh架构图","attributes":{},"skip":false,"key":"6.4.1.1.3"},{"backlink":"usecases/service-mesh-fundamental.html#fig6.4.1.1.4","level":"6.4.1.1","list_caption":"Figure: Istio Mixer","alt":"Istio Mixer","nro":215,"url":"../images/0069RVTdly1fuam4ln45jj30yu0o6wkc.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio Mixer","attributes":{},"skip":false,"key":"6.4.1.1.4"},{"backlink":"usecases/service-mesh-fundamental.html#fig6.4.1.1.5","level":"6.4.1.1","list_caption":"Figure: Istio架构图","alt":"Istio架构图","nro":216,"url":"../images/0069RVTdly1fuamvq97cuj30yu0wg7cr.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio架构图","attributes":{},"skip":false,"key":"6.4.1.1.5"},{"backlink":"usecases/service-mesh-fundamental.html#fig6.4.1.1.6","level":"6.4.1.1","list_caption":"Figure: OSI模型","alt":"OSI模型","nro":217,"url":"../images/0069RVTdly1fuanez4qbtj30v4183n7p.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OSI模型","attributes":{},"skip":false,"key":"6.4.1.1.6"},{"backlink":"usecases/service-mesh-fundamental.html#fig6.4.1.1.7","level":"6.4.1.1","list_caption":"Figure: 在L5解耦","alt":"在L5解耦","nro":218,"url":"../images/006tNbRwly1fubfiiryirj30w20ayjui.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"在L5解耦","attributes":{},"skip":false,"key":"6.4.1.1.7"},{"backlink":"usecases/comparing-service-mesh-technologies.html#fig6.4.1.2.1","level":"6.4.1.2","list_caption":"Figure: 客户端库","alt":"客户端库","nro":219,"url":"../images/006tNbRwly1fubnx0q9bpj30vq0pq465.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"客户端库","attributes":{},"skip":false,"key":"6.4.1.2.1"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig6.4.1.3.1","level":"6.4.1.3","list_caption":"Figure: Service Mesh架构图","alt":"Service Mesh架构图","nro":220,"url":"../images/006tNbRwly1fubs6ts3sgj30vo0osdnj.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Service Mesh架构图","attributes":{},"skip":false,"key":"6.4.1.3.1"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig6.4.1.3.2","level":"6.4.1.3","list_caption":"Figure: Ingress或边缘代理架构图","alt":"Ingress或边缘代理架构图","nro":221,"url":"../images/006tNbRwly1fubsk4v16hj30vo0bq75z.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Ingress或边缘代理架构图","attributes":{},"skip":false,"key":"6.4.1.3.2"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig6.4.1.3.3","level":"6.4.1.3","list_caption":"Figure: 路由器网格架构图","alt":"路由器网格架构图","nro":222,"url":"../images/006tNbRwly1fubsxrph3dj30vq0duq53.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"路由器网格架构图","attributes":{},"skip":false,"key":"6.4.1.3.3"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig6.4.1.3.4","level":"6.4.1.3","list_caption":"Figure: Proxy per Node架构图","alt":"Proxy per Node架构图","nro":223,"url":"../images/006tNbRwly1fubt5a97h7j30vq0bcq5p.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Proxy per Node架构图","attributes":{},"skip":false,"key":"6.4.1.3.4"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig6.4.1.3.5","level":"6.4.1.3","list_caption":"Figure: Sidecar代理/Fabric模型架构图","alt":"Sidecar代理/Fabric模型架构图","nro":224,"url":"../images/006tNbRwly1fubvi0dnhlj30vo0ekwhx.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Sidecar代理/Fabric模型架构图","attributes":{},"skip":false,"key":"6.4.1.3.5"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig6.4.1.3.6","level":"6.4.1.3","list_caption":"Figure: Sidecar代理/控制平面架构图","alt":"Sidecar代理/控制平面架构图","nro":225,"url":"../images/006tNbRwly1fubvr83wvgj30vq0mmdip.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Sidecar代理/控制平面架构图","attributes":{},"skip":false,"key":"6.4.1.3.6"},{"backlink":"usecases/service-mesh-customization-and-integration.html#fig6.4.1.4.1","level":"6.4.1.4","list_caption":"Figure: nginMesh架构图","alt":"nginMesh架构图","nro":226,"url":"../images/006tNbRwly1fucp8yralaj30vu0sijx8.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"nginMesh架构图","attributes":{},"skip":false,"key":"6.4.1.4.1"},{"backlink":"usecases/service-mesh-customization-and-integration.html#fig6.4.1.4.2","level":"6.4.1.4","list_caption":"Figure: Mixer adapter","alt":"Mixer adapter","nro":227,"url":"../images/006tNbRwly1fucplat3l9j30vo0lw43l.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Mixer adapter","attributes":{},"skip":false,"key":"6.4.1.4.2"},{"backlink":"usecases/service-mesh-customization-and-integration.html#fig6.4.1.4.3","level":"6.4.1.4","list_caption":"Figure: SOFAMesh","alt":"SOFAMesh","nro":228,"url":"../images/mosn-with-service-mesh.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"SOFAMesh","attributes":{},"skip":false,"key":"6.4.1.4.3"},{"backlink":"usecases/service-mesh-customization-and-integration.html#fig6.4.1.4.4","level":"6.4.1.4","list_caption":"Figure: SOFAMosn模块架构图","alt":"SOFAMosn模块架构图","nro":229,"url":"../images/006tNbRwly1fucpc5fn8wj31kw0sfdnu.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"SOFAMosn模块架构图","attributes":{},"skip":false,"key":"6.4.1.4.4"},{"backlink":"usecases/istio.html#fig6.4.2.1","level":"6.4.2","list_caption":"Figure: Istio的mindmap","alt":"Istio的mindmap","nro":230,"url":"../images/istio-mindmap.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio的mindmap","attributes":{},"skip":false,"key":"6.4.2.1"},{"backlink":"usecases/istio.html#fig6.4.2.2","level":"6.4.2","list_caption":"Figure: Istio架构图","alt":"Istio架构图","nro":231,"url":"../images/istio-mesh-arch.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio架构图","attributes":{},"skip":false,"key":"6.4.2.2"},{"backlink":"usecases/istio-installation.html#fig6.4.2.1.1","level":"6.4.2.1","list_caption":"Figure: Istio 在 Kubernetes 中的部署架构图","alt":"Istio 在 Kubernetes 中的部署架构图","nro":232,"url":"../images/istio-deployment-architecture-diagram.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio 在 Kubernetes 中的部署架构图","attributes":{},"skip":false,"key":"6.4.2.1.1"},{"backlink":"usecases/istio-installation.html#fig6.4.2.1.2","level":"6.4.2.1","list_caption":"Figure: BookInfo Sample应用架构图","alt":"BookInfo Sample应用架构图","nro":233,"url":"../images/bookinfo-sample-arch.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"BookInfo Sample应用架构图","attributes":{},"skip":false,"key":"6.4.2.1.2"},{"backlink":"usecases/istio-installation.html#fig6.4.2.1.3","level":"6.4.2.1","list_caption":"Figure: BookInfo Sample页面","alt":"BookInfo Sample页面","nro":234,"url":"../images/bookinfo-sample.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"BookInfo Sample页面","attributes":{},"skip":false,"key":"6.4.2.1.3"},{"backlink":"usecases/istio-installation.html#fig6.4.2.1.4","level":"6.4.2.1","list_caption":"Figure: Istio Grafana界面","alt":"Istio Grafana界面","nro":235,"url":"../images/istio-grafana.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio Grafana界面","attributes":{},"skip":false,"key":"6.4.2.1.4"},{"backlink":"usecases/istio-installation.html#fig6.4.2.1.5","level":"6.4.2.1","list_caption":"Figure: Prometheus页面","alt":"Prometheus页面","nro":236,"url":"../images/istio-prometheus.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Prometheus页面","attributes":{},"skip":false,"key":"6.4.2.1.5"},{"backlink":"usecases/istio-installation.html#fig6.4.2.1.6","level":"6.4.2.1","list_caption":"Figure: Zipkin页面","alt":"Zipkin页面","nro":237,"url":"../images/istio-zipkin.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Zipkin页面","attributes":{},"skip":false,"key":"6.4.2.1.6"},{"backlink":"usecases/istio-installation.html#fig6.4.2.1.7","level":"6.4.2.1","list_caption":"Figure: ServiceGraph页面","alt":"ServiceGraph页面","nro":238,"url":"../images/istio-servicegraph.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"ServiceGraph页面","attributes":{},"skip":false,"key":"6.4.2.1.7"},{"backlink":"usecases/istio-tutorials-collection.html#fig6.4.2.4.1","level":"6.4.2.4","list_caption":"Figure: katacoda","alt":"katacoda","nro":239,"url":"../images/006tNc79gy1ftwe77v4u5j31kw0ziwtw.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"katacoda","attributes":{},"skip":false,"key":"6.4.2.4.1"},{"backlink":"usecases/istio-tutorials-collection.html#fig6.4.2.4.2","level":"6.4.2.4","list_caption":"Figure: weavescope","alt":"weavescope","nro":240,"url":"../images/006tNc79gy1ftwhtmzhfej31kw0ziww1.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"weavescope","attributes":{},"skip":false,"key":"6.4.2.4.2"},{"backlink":"usecases/istio-tutorials-collection.html#fig6.4.2.4.3","level":"6.4.2.4","list_caption":"Figure: weavescope","alt":"weavescope","nro":241,"url":"../images/006tNc79gy1ftwhvtu1vxj31kw0zitvc.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"weavescope","attributes":{},"skip":false,"key":"6.4.2.4.3"},{"backlink":"usecases/istio-tutorials-collection.html#fig6.4.2.4.4","level":"6.4.2.4","list_caption":"Figure: Red Hat","alt":"Red Hat","nro":242,"url":"../images/006tNc79gy1ftwiolw1tyj31kw0zib29.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Red Hat","attributes":{},"skip":false,"key":"6.4.2.4.4"},{"backlink":"usecases/istio-tutorials-collection.html#fig6.4.2.4.5","level":"6.4.2.4","list_caption":"Figure: Red Hat developers","alt":"Red Hat developers","nro":243,"url":"../images/006tNc79gy1ftwjyxiw1pj31kw0zi4qp.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Red Hat developers","attributes":{},"skip":false,"key":"6.4.2.4.5"},{"backlink":"usecases/istio-tutorials-collection.html#fig6.4.2.4.6","level":"6.4.2.4","list_caption":"Figure: IBM developerWorks","alt":"IBM developerWorks","nro":244,"url":"../images/006tNc79gy1ftweryj0zrj31kw0zix6q.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"IBM developerWorks","attributes":{},"skip":false,"key":"6.4.2.4.6"},{"backlink":"usecases/istio-tutorials-collection.html#fig6.4.2.4.7","level":"6.4.2.4","list_caption":"Figure: IBM developers","alt":"IBM developers","nro":245,"url":"../images/006tNc79gy1ftwesjg1e2j31kw0s8woq.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"IBM developers","attributes":{},"skip":false,"key":"6.4.2.4.7"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig6.4.2.5.1","level":"6.4.2.5","list_caption":"Figure: Sidecar 模式示意图","alt":"Sidecar 模式示意图","nro":246,"url":"../images/sidecar-pattern.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Sidecar 模式示意图","attributes":{},"skip":false,"key":"6.4.2.5.1"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig6.4.2.5.2","level":"6.4.2.5","list_caption":"Figure: Sidecar 流量劫持示意图","alt":"Sidecar 流量劫持示意图","nro":247,"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":"6.4.2.5.2"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig6.4.2.5.3","level":"6.4.2.5","list_caption":"Figure: iptables 调用链","alt":"iptables 调用链","nro":248,"url":"../images/iptables.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"iptables 调用链","attributes":{},"skip":false,"key":"6.4.2.5.3"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig6.4.2.5.4","level":"6.4.2.5","list_caption":"Figure: hook-connect 原理示意图","alt":"hook-connect 原理示意图","nro":249,"url":"../images/hook-connect.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"hook-connect 原理示意图","attributes":{},"skip":false,"key":"6.4.2.5.4"},{"backlink":"usecases/envoy-sidecar-routing-of-istio-service-mesh-deep-dive.html#fig6.4.2.6.1","level":"6.4.2.6","list_caption":"Figure: Bookinfo 示例","alt":"Bookinfo 示例","nro":250,"url":"../images/006tNbRwgy1fvlwjd3302j31bo0ro0x5.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Bookinfo 示例","attributes":{},"skip":false,"key":"6.4.2.6.1"},{"backlink":"usecases/how-to-integrate-istio-with-vm.html#fig6.4.2.7.1","level":"6.4.2.7","list_caption":"Figure: Istio 中的服务注册发现模型","alt":"Istio 中的服务注册发现模型","nro":251,"url":"https://tva1.sinaimg.cn/large/0081Kckwly1gktf3b63j0j30p30ehwf5.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio 中的服务注册发现模型","attributes":{},"skip":false,"key":"6.4.2.7.1"},{"backlink":"usecases/how-to-integrate-istio-with-vm.html#fig6.4.2.7.2","level":"6.4.2.7","list_caption":"Figure: Bookinfo 示例中的流量示意图","alt":"Bookinfo 示例中的流量示意图","nro":252,"url":"../images/istio-bookinfo-vm-traffic.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Bookinfo 示例中的流量示意图","attributes":{},"skip":false,"key":"6.4.2.7.2"},{"backlink":"usecases/how-to-integrate-istio-with-vm.html#fig6.4.2.7.3","level":"6.4.2.7","list_caption":"Figure: Istio 支持虚拟机 Demo 视频","alt":"Istio 支持虚拟机 Demo 视频","nro":253,"url":"../images/istio-vm-demo-video.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio 支持虚拟机 Demo 视频","attributes":{},"skip":false,"key":"6.4.2.7.3"},{"backlink":"usecases/istio-vm-support.html#fig6.4.2.8.1","level":"6.4.2.8","list_caption":"Figure: 云原生应用的三个阶段","alt":"云原生应用的三个阶段","nro":254,"url":"../images/0081Kckwly1gm0d6t775lj31s80k8go8.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生应用的三个阶段","attributes":{},"skip":false,"key":"6.4.2.8.1"},{"backlink":"usecases/istio-vm-support.html#fig6.4.2.8.2","level":"6.4.2.8","list_caption":"Figure: 图一:从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","alt":"图一:从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","nro":255,"url":"../images/0081Kckwly1gm0d6rogojj30u00yhdil.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"图一:从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","attributes":{},"skip":false,"key":"6.4.2.8.2"},{"backlink":"usecases/istio-vm-support.html#fig6.4.2.8.3","level":"6.4.2.8","list_caption":"Figure: 图二:通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","alt":"图二:通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","nro":256,"url":"../images/0081Kckwly1gm0d6qx2o0j30sq0v440v.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"图二:通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","attributes":{},"skip":false,"key":"6.4.2.8.3"},{"backlink":"usecases/istio-vm-support.html#fig6.4.2.8.4","level":"6.4.2.8","list_caption":"Figure: 图三:引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","alt":"图三:引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","nro":257,"url":"../images/0081Kckwly1gm0d6sgfpxj30oi0rsjt5.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"图三:引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","attributes":{},"skip":false,"key":"6.4.2.8.4"},{"backlink":"usecases/linkerd.html#fig6.4.3.1","level":"6.4.3","list_caption":"Figure: source https://linkerd.io","alt":"source https://linkerd.io","nro":258,"url":"../images/diagram-individual-instance.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"source https://linkerd.io","attributes":{},"skip":false,"key":"6.4.3.1"},{"backlink":"usecases/linkerd.html#fig6.4.3.2","level":"6.4.3","list_caption":"Figure: Linkerd 部署架构(图片来自https://buoyant.io/2016/10/14/a-service-mesh-for-kubernetes-part-ii-pods-are-great-until-theyre-not/)","alt":"Linkerd 部署架构(图片来自https://buoyant.io/2016/10/14/a-service-mesh-for-kubernetes-part-ii-pods-are-great-until-theyre-not/)","nro":259,"url":"https://buoyant.io/wp-content/uploads/2017/07/buoyant-k8s-daemonset-mesh.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Linkerd 部署架构(图片来自https://buoyant.io/2016/10/14/a-service-mesh-for-kubernetes-part-ii-pods-are-great-until-theyre-not/)","attributes":{},"skip":false,"key":"6.4.3.2"},{"backlink":"usecases/linkerd.html#fig6.4.3.3","level":"6.4.3","list_caption":"Figure: 基于 dtab 的路由规则配置阶段发布","alt":"基于 dtab 的路由规则配置阶段发布","nro":260,"url":"https://buoyant.io/wp-content/uploads/2017/07/buoyant-4_override.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"基于 dtab 的路由规则配置阶段发布","attributes":{},"skip":false,"key":"6.4.3.3"},{"backlink":"usecases/linkerd.html#fig6.4.3.4","level":"6.4.3","list_caption":"Figure: Linkerd ingress controller","alt":"Linkerd ingress controller","nro":261,"url":"https://buoyant.io/wp-content/uploads/2017/07/buoyant-k8s-hello-world-ingress-controller-1.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Linkerd ingress controller","attributes":{},"skip":false,"key":"6.4.3.4"},{"backlink":"usecases/linkerd-user-guide.html#fig6.4.3.1.1","level":"6.4.3.1","list_caption":"Figure: Jenkins pipeline","alt":"Jenkins pipeline","nro":262,"url":"../images/linkerd-jenkins-pipeline.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Jenkins pipeline","attributes":{},"skip":false,"key":"6.4.3.1.1"},{"backlink":"usecases/linkerd-user-guide.html#fig6.4.3.1.2","level":"6.4.3.1","list_caption":"Figure: Jenkins config","alt":"Jenkins config","nro":263,"url":"../images/linkerd-jenkins.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Jenkins config","attributes":{},"skip":false,"key":"6.4.3.1.2"},{"backlink":"usecases/linkerd-user-guide.html#fig6.4.3.1.3","level":"6.4.3.1","list_caption":"Figure: namerd","alt":"namerd","nro":264,"url":"../images/namerd-internal.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"namerd","attributes":{},"skip":false,"key":"6.4.3.1.3"},{"backlink":"usecases/linkerd-user-guide.html#fig6.4.3.1.4","level":"6.4.3.1","list_caption":"Figure: linkerd监控","alt":"linkerd监控","nro":265,"url":"../images/linkerd-helloworld-outgoing.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"linkerd监控","attributes":{},"skip":false,"key":"6.4.3.1.4"},{"backlink":"usecases/linkerd-user-guide.html#fig6.4.3.1.5","level":"6.4.3.1","list_caption":"Figure: linkerd监控","alt":"linkerd监控","nro":266,"url":"../images/linkerd-helloworld-incoming.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"linkerd监控","attributes":{},"skip":false,"key":"6.4.3.1.5"},{"backlink":"usecases/linkerd-user-guide.html#fig6.4.3.1.6","level":"6.4.3.1","list_caption":"Figure: linkerd性能监控","alt":"linkerd性能监控","nro":267,"url":"../images/linkerd-grafana.png","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"linkerd性能监控","attributes":{},"skip":false,"key":"6.4.3.1.6"},{"backlink":"usecases/linkerd-user-guide.html#fig6.4.3.1.7","level":"6.4.3.1","list_caption":"Figure: Linkerd ingress controller","alt":"Linkerd ingress controller","nro":268,"url":"../images/linkerd-ingress-controller.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Linkerd ingress controller","attributes":{},"skip":false,"key":"6.4.3.1.7"},{"backlink":"usecases/conduit-installation.html#fig6.4.4.2.1","level":"6.4.4.2","list_caption":"Figure: Conduit dashboard","alt":"Conduit dashboard","nro":269,"url":"../images/conduit-dashboard.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Conduit dashboard","attributes":{},"skip":false,"key":"6.4.4.2.1"},{"backlink":"usecases/envoy.html#fig6.4.5.1","level":"6.4.5","list_caption":"Figure: 负载均衡器的特性以及拓扑类型","alt":"负载均衡器的特性以及拓扑类型","nro":270,"url":"../images/load-balancing-and-proxing.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"负载均衡器的特性以及拓扑类型","attributes":{},"skip":false,"key":"6.4.5.1"},{"backlink":"usecases/envoy-terminology.html#fig6.4.5.1.1","level":"6.4.5.1","list_caption":"Figure: Envoy proxy 架构图","alt":"Envoy proxy 架构图","nro":271,"url":"../images/envoy-arch.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Envoy proxy 架构图","attributes":{},"skip":false,"key":"6.4.5.1.1"},{"backlink":"usecases/envoy-front-proxy.html#fig6.4.5.2.1","level":"6.4.5.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":272,"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":"6.4.5.2.1"},{"backlink":"usecases/envoy-mesh-in-kubernetes-tutorial.html#fig6.4.5.3.1","level":"6.4.5.3","list_caption":"Figure: Envoy Mesh架构图","alt":"Envoy Mesh架构图","nro":273,"url":"../images/envoy-mesh-in-kubernetes.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Envoy Mesh架构图","attributes":{},"skip":false,"key":"6.4.5.3.1"},{"backlink":"usecases/big-data.html#fig6.5.1","level":"6.5","list_caption":"Figure: Spark on yarn with kubernetes","alt":"Spark on yarn with kubernetes","nro":274,"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":"6.5.1"},{"backlink":"usecases/big-data.html#fig6.5.2","level":"6.5","list_caption":"Figure: 在kubernetes上使用多种调度方式","alt":"在kubernetes上使用多种调度方式","nro":275,"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":"6.5.2"},{"backlink":"usecases/spark-standalone-on-kubernetes.html#fig6.5.1.1","level":"6.5.1","list_caption":"Figure: spark master ui","alt":"spark master ui","nro":276,"url":"../images/spark-ui.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"spark master ui","attributes":{},"skip":false,"key":"6.5.1.1"},{"backlink":"usecases/spark-standalone-on-kubernetes.html#fig6.5.1.2","level":"6.5.1","list_caption":"Figure: zeppelin ui","alt":"zeppelin ui","nro":277,"url":"../images/zeppelin-ui.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"zeppelin ui","attributes":{},"skip":false,"key":"6.5.1.2"},{"backlink":"usecases/serverless.html#fig6.6.1","level":"6.6","list_caption":"Figure: Serverless Landscape","alt":"Serverless Landscape","nro":278,"url":"../images/006tNbRwly1fx0ie2kb90j31kw0ynha3.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Serverless Landscape","attributes":{},"skip":false,"key":"6.6.1"},{"backlink":"usecases/serverless.html#fig6.6.2","level":"6.6","list_caption":"Figure: 从物理机到函数计算","alt":"从物理机到函数计算","nro":279,"url":"../images/from-bare-metal-to-functions.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"从物理机到函数计算","attributes":{},"skip":false,"key":"6.6.2"},{"backlink":"usecases/serverless.html#fig6.6.3","level":"6.6","list_caption":"Figure: FaaS Landscape","alt":"FaaS Landscape","nro":280,"url":"../images/redpoint-faas-landscape.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"FaaS Landscape","attributes":{},"skip":false,"key":"6.6.3"},{"backlink":"usecases/understanding-serverless.html#fig6.6.1.1","level":"6.6.1","list_caption":"Figure: Serverless 在云原生技术中的地位","alt":"Serverless 在云原生技术中的地位","nro":281,"url":"../images/cloud-landscape-zh.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Serverless 在云原生技术中的地位","attributes":{},"skip":false,"key":"6.6.1.1"},{"backlink":"usecases/understanding-serverless.html#fig6.6.1.2","level":"6.6.1","list_caption":"Figure: 服务端软件的运行环境","alt":"服务端软件的运行环境","nro":282,"url":"../images/serverless-server-side-software.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"服务端软件的运行环境","attributes":{},"skip":false,"key":"6.6.1.2"},{"backlink":"usecases/understanding-serverless.html#fig6.6.1.3","level":"6.6.1","list_caption":"Figure: FaaS应用架构","alt":"FaaS应用架构","nro":283,"url":"../images/serverless-faas-platform.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"FaaS应用架构","attributes":{},"skip":false,"key":"6.6.1.3"},{"backlink":"usecases/understanding-serverless.html#fig6.6.1.4","level":"6.6.1","list_caption":"Figure: Serverless 中的函数定义","alt":"Serverless 中的函数定义","nro":284,"url":"../images/006y8mN6ly1g7ldey3l7gj31ti0mwta9.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Serverless 中的函数定义","attributes":{},"skip":false,"key":"6.6.1.4"},{"backlink":"usecases/understanding-serverless.html#fig6.6.1.5","level":"6.6.1","list_caption":"Figure: FaaS 中的函数","alt":"FaaS 中的函数","nro":285,"url":"../images/006y8mN6ly1g7ldhm7bxyj31040u0q5n.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"FaaS 中的函数","attributes":{},"skip":false,"key":"6.6.1.5"},{"backlink":"usecases/understanding-serverless.html#fig6.6.1.6","level":"6.6.1","list_caption":"Figure: 传统应用程序架构","alt":"传统应用程序架构","nro":286,"url":"../images/non-serverless-game-arch.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"传统应用程序架构","attributes":{},"skip":false,"key":"6.6.1.6"},{"backlink":"usecases/understanding-serverless.html#fig6.6.1.7","level":"6.6.1","list_caption":"Figure: Serverless架构","alt":"Serverless架构","nro":287,"url":"../images/serverless-game-arch.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Serverless架构","attributes":{},"skip":false,"key":"6.6.1.7"},{"backlink":"usecases/openfaas-quick-start.html#fig6.6.2.1.1","level":"6.6.2.1","list_caption":"Figure: OpenFaaS架构","alt":"OpenFaaS架构","nro":288,"url":"../images/openfaas-arch.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenFaaS架构","attributes":{},"skip":false,"key":"6.6.2.1.1"},{"backlink":"usecases/openfaas-quick-start.html#fig6.6.2.1.2","level":"6.6.2.1","list_caption":"Figure: OpenFaaS Prometheus","alt":"OpenFaaS Prometheus","nro":289,"url":"../images/openfaas-prometheus.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenFaaS Prometheus","attributes":{},"skip":false,"key":"6.6.2.1.2"},{"backlink":"usecases/openfaas-quick-start.html#fig6.6.2.1.3","level":"6.6.2.1","list_caption":"Figure: OpenFaas Grafana监控","alt":"OpenFaas Grafana监控","nro":290,"url":"../images/openfaas-grafana.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenFaas Grafana监控","attributes":{},"skip":false,"key":"6.6.2.1.3"},{"backlink":"usecases/openfaas-quick-start.html#fig6.6.2.1.4","level":"6.6.2.1","list_caption":"Figure: OpenFaas Dashboard","alt":"OpenFaas Dashboard","nro":291,"url":"../images/openfaas-deploy-a-function.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"OpenFaas Dashboard","attributes":{},"skip":false,"key":"6.6.2.1.4"},{"backlink":"usecases/openfaas-quick-start.html#fig6.6.2.1.5","level":"6.6.2.1","list_caption":"Figure: NodeInfo执行结果","alt":"NodeInfo执行结果","nro":292,"url":"../images/openfaas-nodeinfo.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"NodeInfo执行结果","attributes":{},"skip":false,"key":"6.6.2.1.5"},{"backlink":"usecases/knative.html#fig6.6.3.1","level":"6.6.3","list_caption":"Figure: Knative logo","alt":"Knative logo","nro":293,"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":"6.6.3.1"},{"backlink":"usecases/knative.html#fig6.6.3.2","level":"6.6.3","list_caption":"Figure: Knative 受众(图片来自 knative.dev)","alt":"Knative 受众(图片来自 knative.dev)","nro":294,"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":"6.6.3.2"},{"backlink":"usecases/edge-computing.html#fig6.7.1","level":"6.7","list_caption":"Figure: KubeEdge logo","alt":"KubeEdge logo","nro":295,"url":"https://tva1.sinaimg.cn/large/006y8mN6ly1g7vfsugr2fj306y06yjra.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"KubeEdge logo","attributes":{},"skip":false,"key":"6.7.1"},{"backlink":"develop/sigs-and-working-group.html#fig7.2.1","level":"7.2","list_caption":"Figure: Kubernetes SIG","alt":"Kubernetes SIG","nro":296,"url":"../images/kubernetes-sigs.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes SIG","attributes":{},"skip":false,"key":"7.2.1"},{"backlink":"develop/testing.html#fig7.4.1","level":"7.4","list_caption":"Figure: test-infra架构图(图片来自官方GitHub)","alt":"test-infra架构图(图片来自官方GitHub)","nro":297,"url":"../images/kubernetes-test-architecture.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"test-infra架构图(图片来自官方GitHub)","attributes":{},"skip":false,"key":"7.4.1"},{"backlink":"develop/client-go-sample.html#fig7.5.1","level":"7.5","list_caption":"Figure: 使用kubernetes dashboard进行故障排查","alt":"使用kubernetes dashboard进行故障排查","nro":298,"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":"7.5.1"},{"backlink":"cloud-native/cncf.html#fig8.1.1","level":"8.1","list_caption":"Figure: CNCF landscape","alt":"CNCF landscape","nro":299,"url":"../images/006tNbRwly1fxmx633ymqj31dp0u0kjn.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF landscape","attributes":{},"skip":false,"key":"8.1.1"},{"backlink":"cloud-native/cncf.html#fig8.1.2","level":"8.1","list_caption":"Figure: CNCF项目成熟度级别","alt":"CNCF项目成熟度级别","nro":300,"url":"../images/cncf-graduation-criteria-v2.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF项目成熟度级别","attributes":{},"skip":false,"key":"8.1.2"},{"backlink":"cloud-native/cncf-charter.html#fig8.2.1","level":"8.2","list_caption":"Figure: CNCF 组织架构图","alt":"CNCF 组织架构图","nro":301,"url":"../images/cncf-org-arch.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF 组织架构图","attributes":{},"skip":false,"key":"8.2.1"},{"backlink":"cloud-native/cncf-charter.html#fig8.2.2","level":"8.2","list_caption":"Figure: 云原生的理想分层架构","alt":"云原生的理想分层架构","nro":302,"url":"../images/006tKfTcly1ft3zgjlisxj30n70ffjth.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"云原生的理想分层架构","attributes":{},"skip":false,"key":"8.2.2"},{"backlink":"cloud-native/cncf-sandbox-criteria.html#fig8.4.1","level":"8.4","list_caption":"Figure: sandbox 流程","alt":"sandbox 流程","nro":303,"url":"../images/sandbox-process.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"sandbox 流程","attributes":{},"skip":false,"key":"8.4.1"},{"backlink":"cloud-native/cncf-project-governing.html#fig8.5.1","level":"8.5","list_caption":"Figure: CNCF 项目的成熟度分类","alt":"CNCF 项目的成熟度分类","nro":304,"url":"../images/cncf-graduation.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF 项目的成熟度分类","attributes":{},"skip":false,"key":"8.5.1"},{"backlink":"cloud-native/cncf-project-governing.html#fig8.5.2","level":"8.5","list_caption":"Figure: CNCF中的项目运作","alt":"CNCF中的项目运作","nro":305,"url":"../images/006tNc79ly1g1yz80ag98j31cs0n2gr7.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF中的项目运作","attributes":{},"skip":false,"key":"8.5.2"},{"backlink":"cloud-native/cncf-project-governing.html#fig8.5.3","level":"8.5","list_caption":"Figure: CNCF项目成熟度级别","alt":"CNCF项目成熟度级别","nro":306,"url":"../images/cncf-graduation-criteria-v2.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF项目成熟度级别","attributes":{},"skip":false,"key":"8.5.3"},{"backlink":"appendix/material-share.html#fig9.3.1","level":"9.3","list_caption":"Figure: Kubernetes 资源图标示例","alt":"Kubernetes 资源图标示例","nro":307,"url":"../images/006tNc79ly1fzmnolp5ghj30z90u0gwf.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 资源图标示例","attributes":{},"skip":false,"key":"9.3.1"},{"backlink":"appendix/issues.html#fig9.6.1","level":"9.6","list_caption":"Figure: pvc-storage-limit","alt":"pvc-storage-limit","nro":308,"url":"../images/pvc-storage-limit.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"pvc-storage-limit","attributes":{},"skip":false,"key":"9.6.1"},{"backlink":"appendix/kubernetes-1.14-changelog.html#fig9.7.8.1","level":"9.7.8","list_caption":"Figure: 大鱿鱼:kubectl log","alt":"大鱿鱼:kubectl log","nro":309,"url":"../images/006tKfTcly1g1gbdpsdbgj303c03cwel.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"大鱿鱼:kubectl log","attributes":{},"skip":false,"key":"9.7.8.1"},{"backlink":"appendix/kubernetes-1.14-changelog.html#fig9.7.8.2","level":"9.7.8","list_caption":"Figure: Kubernetes 吉祥物 kubee-cuddle","alt":"Kubernetes 吉祥物 kubee-cuddle","nro":310,"url":"../images/006tKfTcly1g1gbjvx2ugj305k05mmx9.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 吉祥物 kubee-cuddle","attributes":{},"skip":false,"key":"9.7.8.2"},{"backlink":"appendix/kubernetes-1.15-changelog.html#fig9.7.9.1","level":"9.7.9","list_caption":"Figure: KubeAdmin Logo","alt":"KubeAdmin Logo","nro":311,"url":"https://d33wubrfki0l68.cloudfront.net/285b361256db9bb624c22ff9cd32557b4bc61aba/759c7/images/blog/2019-06-19-kubernetes-1-15-release-announcement/kubeadm-logo.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"KubeAdmin Logo","attributes":{},"skip":false,"key":"9.7.9.1"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig9.8.2.1","level":"9.8.2","list_caption":"Figure: Kubernetes 搜索趋势(来自 Google trends)","alt":"Kubernetes 搜索趋势(来自 Google trends)","nro":312,"url":"../images/006tNc79ly1fzne6y4f2ej31q60fedho.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 搜索趋势(来自 Google trends)","attributes":{},"skip":false,"key":"9.8.2.1"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig9.8.2.2","level":"9.8.2","list_caption":"Figure: Kubernetes 的百度指数","alt":"Kubernetes 的百度指数","nro":313,"url":"../images/006tNc79ly1fznegoocmvj31y00hmgon.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Kubernetes 的百度指数","attributes":{},"skip":false,"key":"9.8.2.2"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig9.8.2.3","level":"9.8.2","list_caption":"Figure: Istio 中的 CRD","alt":"Istio 中的 CRD","nro":314,"url":"../images/006tNc79ly1fzna87wmfij30u00zc4qp.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"Istio 中的 CRD","attributes":{},"skip":false,"key":"9.8.2.3"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig9.8.2.4","level":"9.8.2","list_caption":"Figure: 2019 Q1 软件架构趋势 - 来自 InfoQ","alt":"2019 Q1 软件架构趋势 - 来自 InfoQ","nro":315,"url":"../images/006tNc79ly1fzor2k6f7wj313j0u0dl3.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"2019 Q1 软件架构趋势 - 来自 InfoQ","attributes":{},"skip":false,"key":"9.8.2.4"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig9.8.2.5","level":"9.8.2","list_caption":"Figure: ServiceMesher 社区 Logo","alt":"ServiceMesher 社区 Logo","nro":316,"url":"../images/006tNc79ly1fznadbp63qj31jt0beq9s.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"ServiceMesher 社区 Logo","attributes":{},"skip":false,"key":"9.8.2.5"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig9.8.2.6","level":"9.8.2","list_caption":"Figure: ServiceMesher社区2018年活动一览","alt":"ServiceMesher社区2018年活动一览","nro":317,"url":"../images/006tNc79ly1fzm9vs4o3aj31s00u0x6p.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"ServiceMesher社区2018年活动一览","attributes":{},"skip":false,"key":"9.8.2.6"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig9.8.2.7","level":"9.8.2","list_caption":"Figure: CNCF Landscape 中的 Serverless 单元","alt":"CNCF Landscape 中的 Serverless 单元","nro":318,"url":"../images/006tNc79ly1fznbh3vfbwj310f0jxgxj.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF Landscape 中的 Serverless 单元","attributes":{},"skip":false,"key":"9.8.2.7"},{"backlink":"appendix/cncf-annual-report-2018.html#fig9.9.1.1","level":"9.9.1","list_caption":"Figure: CNCF 项目成熟度级别","alt":"CNCF 项目成熟度级别","nro":319,"url":"../images/006tNc79ly1g04s0oznytj31tg0ok7ca.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CNCF 项目成熟度级别","attributes":{},"skip":false,"key":"9.9.1.1"},{"backlink":"appendix/cncf-annual-report-2018.html#fig9.9.1.2","level":"9.9.1","list_caption":"Figure: KCSP","alt":"KCSP","nro":320,"url":"../images/006tNc79ly1g04tl97vm4j318v0h7dpt.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"KCSP","attributes":{},"skip":false,"key":"9.9.1.2"},{"backlink":"appendix/about-cka-candidate.html#fig9.11.1","level":"9.11","list_caption":"Figure: cka-question","alt":"cka-question","nro":321,"url":"../images/cka-question.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"cka-question","attributes":{},"skip":false,"key":"9.11.1"},{"backlink":"appendix/about-cka-candidate.html#fig9.11.2","level":"9.11","list_caption":"Figure: CKA mindmap","alt":"CKA mindmap","nro":322,"url":"../images/cka-mindmap.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_:_CAPTION_","label":"CKA mindmap","attributes":{},"skip":false,"key":"9.11.2"}]},"title":"Kubernetes Handbook - Kubernetes中文指南/云原生应用架构实践手册 by Jimmy Song(宋净超)","language":"zh-hans","links":{"sidebar":{"回到主页":"https://jimmysong.io","云原生开源项目大全":"https://jimmysong.io/awesome-cloud-native","云原生社区":"https://cloudnative.to"}},"gitbook":"*","description":"Kubernetes Handbook - Kubernetes中文指南/云原生应用架构实践手册,本书记录了本人从零开始学习和使用Kubernetes的心路历程,着重于经验分享和总结,同时也会有相关的概念解析,希望能够帮助大家少踩坑,少走弯路,还会指引大家关注Kubernetes生态周边,如微服务构建、DevOps、大数据应用、Service Mesh、Cloud Native等领域。"},"file":{"path":"concepts/deployment.md","mtime":"2020-12-29T01:47:59.550Z","type":"markdown"},"gitbook":{"version":"3.2.3","time":"2020-12-29T01:49:11.463Z"},"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-alerts/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-sharing/buttons.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-fontsettings/fontsettings.js"></script>
|
||
|
||
|
||
|
||
</body>
|
||
</html>
|
||
|