5151 lines
302 KiB
HTML
5151 lines
302 KiB
HTML
|
||
<!DOCTYPE HTML>
|
||
<html lang="zh-hans" >
|
||
<head>
|
||
<meta charset="UTF-8">
|
||
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
|
||
<title>Kubernetes 与云原生应用概览 · Kubernetes 中文指南——云原生应用架构实战手册</title>
|
||
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
|
||
<meta name="description" content="">
|
||
<meta name="generator" content="GitBook 3.2.3">
|
||
<meta name="author" content="宋净超（Jimmy Song）">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/style.css">
|
||
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-splitter/splitter.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-page-toc-button/plugin.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-image-captions/image-captions.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-back-to-top-button/plugin.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-search-plus/search.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-tbfed-pagefooter/footer.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-prism/prism-ghcolors.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-lightbox/css/lightbox.min.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-expandable-chapters-small/expandable-chapters-small.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-insert-logo/plugin.css">
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../gitbook/gitbook-plugin-fontsettings/website.css">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<meta name="HandheldFriendly" content="true"/>
|
||
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
|
||
<meta name="apple-mobile-web-app-capable" content="yes">
|
||
<meta name="apple-mobile-web-app-status-bar-style" content="black">
|
||
<link rel="apple-touch-icon-precomposed" sizes="152x152" href="../gitbook/images/apple-touch-icon-precomposed-152.png">
|
||
<link rel="shortcut icon" href="../gitbook/images/favicon.ico" type="image/x-icon">
|
||
|
||
|
||
<link rel="next" href="from-kubernetes-to-cloud-native.html" />
|
||
|
||
|
||
<link rel="prev" href="kubernetes-history.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/book/" 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-definition.html">
|
||
|
||
<a href="cloud-native-definition.html">
|
||
|
||
|
||
<b>2.1.</b>
|
||
|
||
云原生的定义
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.2" data-path="cloud-native-philosophy.html">
|
||
|
||
<a href="cloud-native-philosophy.html">
|
||
|
||
|
||
<b>2.2.</b>
|
||
|
||
云原生的设计哲学
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.3" data-path="kubernetes-history.html">
|
||
|
||
<a href="kubernetes-history.html">
|
||
|
||
|
||
<b>2.3.</b>
|
||
|
||
Kubernetes 的诞生
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter active" data-level="2.4" data-path="kubernetes-and-cloud-native-app-overview.html">
|
||
|
||
<a href="kubernetes-and-cloud-native-app-overview.html">
|
||
|
||
|
||
<b>2.4.</b>
|
||
|
||
Kubernetes 与云原生应用概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.5" data-path="from-kubernetes-to-cloud-native.html">
|
||
|
||
<a href="from-kubernetes-to-cloud-native.html">
|
||
|
||
|
||
<b>2.5.</b>
|
||
|
||
云原生应用之路 —— 从 Kubernetes 到云原生
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6" data-path="define-cloud-native-app.html">
|
||
|
||
<a href="define-cloud-native-app.html">
|
||
|
||
|
||
<b>2.6.</b>
|
||
|
||
定义云原生应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.6.1" data-path="oam.html">
|
||
|
||
<a href="oam.html">
|
||
|
||
|
||
<b>2.6.1.</b>
|
||
|
||
OAM
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.6.1.1" data-path="workload.html">
|
||
|
||
<a href="workload.html">
|
||
|
||
|
||
<b>2.6.1.1.</b>
|
||
|
||
Workload
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.2" data-path="component.html">
|
||
|
||
<a href="component.html">
|
||
|
||
|
||
<b>2.6.1.2.</b>
|
||
|
||
Component
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.3" data-path="trait.html">
|
||
|
||
<a href="trait.html">
|
||
|
||
|
||
<b>2.6.1.3.</b>
|
||
|
||
Trait
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.4" data-path="application-scope.html">
|
||
|
||
<a href="application-scope.html">
|
||
|
||
|
||
<b>2.6.1.4.</b>
|
||
|
||
Application Scope
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.5" data-path="application-configuration.html">
|
||
|
||
<a href="application-configuration.html">
|
||
|
||
|
||
<b>2.6.1.5.</b>
|
||
|
||
Application Configuration
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.2" data-path="crossplane.html">
|
||
|
||
<a href="crossplane.html">
|
||
|
||
|
||
<b>2.6.2.</b>
|
||
|
||
Crossplane
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.7" data-path="cloud-native-programming-languages.html">
|
||
|
||
<a href="cloud-native-programming-languages.html">
|
||
|
||
|
||
<b>2.7.</b>
|
||
|
||
云原生平台配置语言
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.7.1" data-path="cloud-native-programming-language-ballerina.html">
|
||
|
||
<a href="cloud-native-programming-language-ballerina.html">
|
||
|
||
|
||
<b>2.7.1.</b>
|
||
|
||
Ballerina
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.7.2" data-path="cloud-native-programming-language-pulumi.html">
|
||
|
||
<a href="cloud-native-programming-language-pulumi.html">
|
||
|
||
|
||
<b>2.7.2.</b>
|
||
|
||
Pulumi
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.8" data-path="the-future-of-cloud-native.html">
|
||
|
||
<a href="the-future-of-cloud-native.html">
|
||
|
||
|
||
<b>2.8.</b>
|
||
|
||
云原生的未来
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">快速入门</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="3.1" data-path="quick-start.html">
|
||
|
||
<a href="quick-start.html">
|
||
|
||
|
||
<b>3.1.</b>
|
||
|
||
云原生新手入门指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.2" data-path="play-with-kubernetes.html">
|
||
|
||
<a href="play-with-kubernetes.html">
|
||
|
||
|
||
<b>3.2.</b>
|
||
|
||
Play with Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.3" data-path="cloud-native-local-quick-start.html">
|
||
|
||
<a href="cloud-native-local-quick-start.html">
|
||
|
||
|
||
<b>3.3.</b>
|
||
|
||
快速部署一个云原生本地实验环境
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4" data-path="setup-kubernetes-with-rancher-and-aliyun.html">
|
||
|
||
<a href="setup-kubernetes-with-rancher-and-aliyun.html">
|
||
|
||
|
||
<b>3.4.</b>
|
||
|
||
使用 Rancher 在阿里云上部署 Kubenretes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">概念与原理</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="4.1" data-path="../concepts/">
|
||
|
||
<a href="../concepts/">
|
||
|
||
|
||
<b>4.1.</b>
|
||
|
||
Kubernetes 架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.1.1" data-path="../concepts/concepts.html">
|
||
|
||
<a href="../concepts/concepts.html">
|
||
|
||
|
||
<b>4.1.1.</b>
|
||
|
||
Kubernetes 的设计理念
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.1.2" data-path="../concepts/etcd.html">
|
||
|
||
<a href="../concepts/etcd.html">
|
||
|
||
|
||
<b>4.1.2.</b>
|
||
|
||
Etcd 解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.1.3" data-path="../concepts/open-interfaces.html">
|
||
|
||
<a href="../concepts/open-interfaces.html">
|
||
|
||
|
||
<b>4.1.3.</b>
|
||
|
||
开放接口
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.1.3.1" data-path="../concepts/cri.html">
|
||
|
||
<a href="../concepts/cri.html">
|
||
|
||
|
||
<b>4.1.3.1.</b>
|
||
|
||
容器运行时接口（CRI）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.1.3.2" data-path="../concepts/cni.html">
|
||
|
||
<a href="../concepts/cni.html">
|
||
|
||
|
||
<b>4.1.3.2.</b>
|
||
|
||
容器网络接口（CNI）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.1.3.3" data-path="../concepts/csi.html">
|
||
|
||
<a href="../concepts/csi.html">
|
||
|
||
|
||
<b>4.1.3.3.</b>
|
||
|
||
容器存储接口（CSI）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.1.4" data-path="../concepts/objects.html">
|
||
|
||
<a href="../concepts/objects.html">
|
||
|
||
|
||
<b>4.1.4.</b>
|
||
|
||
Kubernetes 中的资源对象
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2" data-path="../concepts/pod-state-and-lifecycle.html">
|
||
|
||
<a href="../concepts/pod-state-and-lifecycle.html">
|
||
|
||
|
||
<b>4.2.</b>
|
||
|
||
Pod 状态与生命周期管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.2.1" data-path="../concepts/pod-overview.html">
|
||
|
||
<a href="../concepts/pod-overview.html">
|
||
|
||
|
||
<b>4.2.1.</b>
|
||
|
||
Pod 概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.2" data-path="../concepts/pod.html">
|
||
|
||
<a href="../concepts/pod.html">
|
||
|
||
|
||
<b>4.2.2.</b>
|
||
|
||
Pod 解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.3" data-path="../concepts/init-containers.html">
|
||
|
||
<a href="../concepts/init-containers.html">
|
||
|
||
|
||
<b>4.2.3.</b>
|
||
|
||
Init 容器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.4" data-path="../concepts/pause-container.html">
|
||
|
||
<a href="../concepts/pause-container.html">
|
||
|
||
|
||
<b>4.2.4.</b>
|
||
|
||
Pause 容器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.5" data-path="../concepts/pod-security-policy.html">
|
||
|
||
<a href="../concepts/pod-security-policy.html">
|
||
|
||
|
||
<b>4.2.5.</b>
|
||
|
||
Pod 安全策略
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.6" data-path="../concepts/pod-lifecycle.html">
|
||
|
||
<a href="../concepts/pod-lifecycle.html">
|
||
|
||
|
||
<b>4.2.6.</b>
|
||
|
||
Pod 的生命周期
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.7" data-path="../concepts/pod-hook.html">
|
||
|
||
<a href="../concepts/pod-hook.html">
|
||
|
||
|
||
<b>4.2.7.</b>
|
||
|
||
Pod Hook
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.8" data-path="../concepts/pod-preset.html">
|
||
|
||
<a href="../concepts/pod-preset.html">
|
||
|
||
|
||
<b>4.2.8.</b>
|
||
|
||
Pod Preset
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.9" data-path="../concepts/pod-disruption-budget.html">
|
||
|
||
<a href="../concepts/pod-disruption-budget.html">
|
||
|
||
|
||
<b>4.2.9.</b>
|
||
|
||
Pod 中断与 PDB（Pod 中断预算）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3" data-path="../concepts/cluster.html">
|
||
|
||
<a href="../concepts/cluster.html">
|
||
|
||
|
||
<b>4.3.</b>
|
||
|
||
集群资源管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.3.1" data-path="../concepts/node.html">
|
||
|
||
<a href="../concepts/node.html">
|
||
|
||
|
||
<b>4.3.1.</b>
|
||
|
||
Node
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.2" data-path="../concepts/namespace.html">
|
||
|
||
<a href="../concepts/namespace.html">
|
||
|
||
|
||
<b>4.3.2.</b>
|
||
|
||
Namespace
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.3" data-path="../concepts/label.html">
|
||
|
||
<a href="../concepts/label.html">
|
||
|
||
|
||
<b>4.3.3.</b>
|
||
|
||
Label
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.4" data-path="../concepts/annotation.html">
|
||
|
||
<a href="../concepts/annotation.html">
|
||
|
||
|
||
<b>4.3.4.</b>
|
||
|
||
Annotation
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.5" data-path="../concepts/taint-and-toleration.html">
|
||
|
||
<a href="../concepts/taint-and-toleration.html">
|
||
|
||
|
||
<b>4.3.5.</b>
|
||
|
||
Taint 和 Toleration（污点和容忍）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.6" data-path="../concepts/garbage-collection.html">
|
||
|
||
<a href="../concepts/garbage-collection.html">
|
||
|
||
|
||
<b>4.3.6.</b>
|
||
|
||
垃圾收集
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4" data-path="../concepts/controllers.html">
|
||
|
||
<a href="../concepts/controllers.html">
|
||
|
||
|
||
<b>4.4.</b>
|
||
|
||
控制器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.4.1" data-path="../concepts/deployment.html">
|
||
|
||
<a href="../concepts/deployment.html">
|
||
|
||
|
||
<b>4.4.1.</b>
|
||
|
||
Deployment
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.2" data-path="../concepts/statefulset.html">
|
||
|
||
<a href="../concepts/statefulset.html">
|
||
|
||
|
||
<b>4.4.2.</b>
|
||
|
||
StatefulSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.3" data-path="../concepts/daemonset.html">
|
||
|
||
<a href="../concepts/daemonset.html">
|
||
|
||
|
||
<b>4.4.3.</b>
|
||
|
||
DaemonSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.4" data-path="../concepts/replicaset.html">
|
||
|
||
<a href="../concepts/replicaset.html">
|
||
|
||
|
||
<b>4.4.4.</b>
|
||
|
||
ReplicationController 和 ReplicaSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.5" data-path="../concepts/job.html">
|
||
|
||
<a href="../concepts/job.html">
|
||
|
||
|
||
<b>4.4.5.</b>
|
||
|
||
Job
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.6" data-path="../concepts/cronjob.html">
|
||
|
||
<a href="../concepts/cronjob.html">
|
||
|
||
|
||
<b>4.4.6.</b>
|
||
|
||
CronJob
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.7" data-path="../concepts/horizontal-pod-autoscaling.html">
|
||
|
||
<a href="../concepts/horizontal-pod-autoscaling.html">
|
||
|
||
|
||
<b>4.4.7.</b>
|
||
|
||
Horizontal Pod Autoscaling
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.4.7.1" data-path="../concepts/custom-metrics-hpa.html">
|
||
|
||
<a href="../concepts/custom-metrics-hpa.html">
|
||
|
||
|
||
<b>4.4.7.1.</b>
|
||
|
||
自定义指标 HPA
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.8" data-path="../concepts/admission-controller.html">
|
||
|
||
<a href="../concepts/admission-controller.html">
|
||
|
||
|
||
<b>4.4.8.</b>
|
||
|
||
准入控制器（Admission Controller）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5" data-path="../concepts/service-discovery.html">
|
||
|
||
<a href="../concepts/service-discovery.html">
|
||
|
||
|
||
<b>4.5.</b>
|
||
|
||
服务发现与路由
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.5.1" data-path="../concepts/service.html">
|
||
|
||
<a href="../concepts/service.html">
|
||
|
||
|
||
<b>4.5.1.</b>
|
||
|
||
Service
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.2" data-path="../concepts/topology-aware-routing.html">
|
||
|
||
<a href="../concepts/topology-aware-routing.html">
|
||
|
||
|
||
<b>4.5.2.</b>
|
||
|
||
拓扑感知路由
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.3" data-path="../concepts/ingress.html">
|
||
|
||
<a href="../concepts/ingress.html">
|
||
|
||
|
||
<b>4.5.3.</b>
|
||
|
||
Ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.5.3.1" data-path="../concepts/traefik-ingress-controller.html">
|
||
|
||
<a href="../concepts/traefik-ingress-controller.html">
|
||
|
||
|
||
<b>4.5.3.1.</b>
|
||
|
||
Traefik Ingress Controller
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.4" data-path="../concepts/gateway.html">
|
||
|
||
<a href="../concepts/gateway.html">
|
||
|
||
|
||
<b>4.5.4.</b>
|
||
|
||
Gateway
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6" data-path="../concepts/authentication-and-permission.html">
|
||
|
||
<a href="../concepts/authentication-and-permission.html">
|
||
|
||
|
||
<b>4.6.</b>
|
||
|
||
身份与权限控制
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.6.1" data-path="../concepts/serviceaccount.html">
|
||
|
||
<a href="../concepts/serviceaccount.html">
|
||
|
||
|
||
<b>4.6.1.</b>
|
||
|
||
ServiceAccount
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6.2" data-path="../concepts/rbac.html">
|
||
|
||
<a href="../concepts/rbac.html">
|
||
|
||
|
||
<b>4.6.2.</b>
|
||
|
||
基于角色的访问控制（RBAC）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6.3" data-path="../concepts/network-policy.html">
|
||
|
||
<a href="../concepts/network-policy.html">
|
||
|
||
|
||
<b>4.6.3.</b>
|
||
|
||
NetworkPolicy
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6.4" data-path="../concepts/spiffe.html">
|
||
|
||
<a href="../concepts/spiffe.html">
|
||
|
||
|
||
<b>4.6.4.</b>
|
||
|
||
SPIFFE
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.6.4.1" data-path="../concepts/spire.html">
|
||
|
||
<a href="../concepts/spire.html">
|
||
|
||
|
||
<b>4.6.4.1.</b>
|
||
|
||
SPIRE
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.7" data-path="../concepts/networking.html">
|
||
|
||
<a href="../concepts/networking.html">
|
||
|
||
|
||
<b>4.7.</b>
|
||
|
||
网络
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.7.1" data-path="../concepts/flannel.html">
|
||
|
||
<a href="../concepts/flannel.html">
|
||
|
||
|
||
<b>4.7.1.</b>
|
||
|
||
扁平网络 Flannel
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.7.2" data-path="../concepts/calico.html">
|
||
|
||
<a href="../concepts/calico.html">
|
||
|
||
|
||
<b>4.7.2.</b>
|
||
|
||
非 Overlay 扁平网络 Calico
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.7.3" data-path="../concepts/cilium.html">
|
||
|
||
<a href="../concepts/cilium.html">
|
||
|
||
|
||
<b>4.7.3.</b>
|
||
|
||
基于 eBPF 的网络 Cilium
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.7.3.1" data-path="../concepts/cilium-concepts.html">
|
||
|
||
<a href="../concepts/cilium-concepts.html">
|
||
|
||
|
||
<b>4.7.3.1.</b>
|
||
|
||
Cilium 架构设计与概念解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.8" data-path="../concepts/storage.html">
|
||
|
||
<a href="../concepts/storage.html">
|
||
|
||
|
||
<b>4.8.</b>
|
||
|
||
存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.8.1" data-path="../concepts/secret.html">
|
||
|
||
<a href="../concepts/secret.html">
|
||
|
||
|
||
<b>4.8.1.</b>
|
||
|
||
Secret
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.8.2" data-path="../concepts/configmap.html">
|
||
|
||
<a href="../concepts/configmap.html">
|
||
|
||
|
||
<b>4.8.2.</b>
|
||
|
||
ConfigMap
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.8.2.1" data-path="../concepts/configmap-hot-update.html">
|
||
|
||
<a href="../concepts/configmap-hot-update.html">
|
||
|
||
|
||
<b>4.8.2.1.</b>
|
||
|
||
ConfigMap 的热更新
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.8.3" data-path="../concepts/volume.html">
|
||
|
||
<a href="../concepts/volume.html">
|
||
|
||
|
||
<b>4.8.3.</b>
|
||
|
||
Volume
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.8.4" data-path="../concepts/persistent-volume.html">
|
||
|
||
<a href="../concepts/persistent-volume.html">
|
||
|
||
|
||
<b>4.8.4.</b>
|
||
|
||
持久化卷（Persistent Volume）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.8.5" data-path="../concepts/storageclass.html">
|
||
|
||
<a href="../concepts/storageclass.html">
|
||
|
||
|
||
<b>4.8.5.</b>
|
||
|
||
Storage Class
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.8.6" data-path="../concepts/local-persistent-storage.html">
|
||
|
||
<a href="../concepts/local-persistent-storage.html">
|
||
|
||
|
||
<b>4.8.6.</b>
|
||
|
||
本地持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.9" data-path="../concepts/extension.html">
|
||
|
||
<a href="../concepts/extension.html">
|
||
|
||
|
||
<b>4.9.</b>
|
||
|
||
集群扩展
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.9.1" data-path="../concepts/custom-resource.html">
|
||
|
||
<a href="../concepts/custom-resource.html">
|
||
|
||
|
||
<b>4.9.1.</b>
|
||
|
||
使用自定义资源扩展 API
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.9.2" data-path="../concepts/crd.html">
|
||
|
||
<a href="../concepts/crd.html">
|
||
|
||
|
||
<b>4.9.2.</b>
|
||
|
||
使用 CRD 扩展 Kubernetes API
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.9.3" data-path="../concepts/aggregated-api-server.html">
|
||
|
||
<a href="../concepts/aggregated-api-server.html">
|
||
|
||
|
||
<b>4.9.3.</b>
|
||
|
||
Aggregated API Server
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.9.4" data-path="../concepts/apiservice.html">
|
||
|
||
<a href="../concepts/apiservice.html">
|
||
|
||
|
||
<b>4.9.4.</b>
|
||
|
||
APIService
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.9.5" data-path="../concepts/service-catalog.html">
|
||
|
||
<a href="../concepts/service-catalog.html">
|
||
|
||
|
||
<b>4.9.5.</b>
|
||
|
||
服务目录（Service Catalog）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.10" data-path="../concepts/multicluster.html">
|
||
|
||
<a href="../concepts/multicluster.html">
|
||
|
||
|
||
<b>4.10.</b>
|
||
|
||
多集群管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.10.1" data-path="../concepts/multi-cluster-services-api.html">
|
||
|
||
<a href="../concepts/multi-cluster-services-api.html">
|
||
|
||
|
||
<b>4.10.1.</b>
|
||
|
||
多集群服务 API（Multi-Cluster Services API）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.10.2" data-path="../practice/federation.html">
|
||
|
||
<a href="../practice/federation.html">
|
||
|
||
|
||
<b>4.10.2.</b>
|
||
|
||
集群联邦（Cluster Federation）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.11" data-path="../concepts/scheduling.html">
|
||
|
||
<a href="../concepts/scheduling.html">
|
||
|
||
|
||
<b>4.11.</b>
|
||
|
||
资源调度
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.11.1" data-path="../concepts/qos.html">
|
||
|
||
<a href="../concepts/qos.html">
|
||
|
||
|
||
<b>4.11.1.</b>
|
||
|
||
服务质量等级（QoS）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">用户指南</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="5.1" data-path="../guide/">
|
||
|
||
<a href="../guide/">
|
||
|
||
|
||
<b>5.1.</b>
|
||
|
||
用户指南概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2" data-path="../guide/resource-configuration.html">
|
||
|
||
<a href="../guide/resource-configuration.html">
|
||
|
||
|
||
<b>5.2.</b>
|
||
|
||
资源对象配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.2.1" data-path="../guide/configure-liveness-readiness-probes.html">
|
||
|
||
<a href="../guide/configure-liveness-readiness-probes.html">
|
||
|
||
|
||
<b>5.2.1.</b>
|
||
|
||
配置 Pod 的 liveness 和 readiness 探针
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.2" data-path="../guide/configure-pod-service-account.html">
|
||
|
||
<a href="../guide/configure-pod-service-account.html">
|
||
|
||
|
||
<b>5.2.2.</b>
|
||
|
||
配置 Pod 的 Service Account
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.3" data-path="../guide/secret-configuration.html">
|
||
|
||
<a href="../guide/secret-configuration.html">
|
||
|
||
|
||
<b>5.2.3.</b>
|
||
|
||
Secret 配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.4" data-path="../guide/resource-quota-management.html">
|
||
|
||
<a href="../guide/resource-quota-management.html">
|
||
|
||
|
||
<b>5.2.4.</b>
|
||
|
||
管理 namespace 中的资源配额
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.3" data-path="../guide/command-usage.html">
|
||
|
||
<a href="../guide/command-usage.html">
|
||
|
||
|
||
<b>5.3.</b>
|
||
|
||
命令使用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.3.1" data-path="../guide/docker-cli-to-kubectl.html">
|
||
|
||
<a href="../guide/docker-cli-to-kubectl.html">
|
||
|
||
|
||
<b>5.3.1.</b>
|
||
|
||
Docker 用户过渡到 kubectl 命令行指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.3.2" data-path="../guide/using-kubectl.html">
|
||
|
||
<a href="../guide/using-kubectl.html">
|
||
|
||
|
||
<b>5.3.2.</b>
|
||
|
||
kubectl 命令概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.3.3" data-path="../guide/kubectl-cheatsheet.html">
|
||
|
||
<a href="../guide/kubectl-cheatsheet.html">
|
||
|
||
|
||
<b>5.3.3.</b>
|
||
|
||
kubectl 命令技巧大全
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.3.4" data-path="../guide/using-etcdctl-to-access-kubernetes-data.html">
|
||
|
||
<a href="../guide/using-etcdctl-to-access-kubernetes-data.html">
|
||
|
||
|
||
<b>5.3.4.</b>
|
||
|
||
使用 etcdctl 访问 Kubernetes 数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4" data-path="../guide/cluster-security-management.html">
|
||
|
||
<a href="../guide/cluster-security-management.html">
|
||
|
||
|
||
<b>5.4.</b>
|
||
|
||
集群安全性管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.4.1" data-path="../guide/managing-tls-in-a-cluster.html">
|
||
|
||
<a href="../guide/managing-tls-in-a-cluster.html">
|
||
|
||
|
||
<b>5.4.1.</b>
|
||
|
||
管理集群中的 TLS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.2" data-path="../guide/kubelet-authentication-authorization.html">
|
||
|
||
<a href="../guide/kubelet-authentication-authorization.html">
|
||
|
||
|
||
<b>5.4.2.</b>
|
||
|
||
kubelet 的认证授权
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.3" data-path="../guide/tls-bootstrapping.html">
|
||
|
||
<a href="../guide/tls-bootstrapping.html">
|
||
|
||
|
||
<b>5.4.3.</b>
|
||
|
||
TLS Bootstrap
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.4" data-path="../guide/kubectl-user-authentication-authorization.html">
|
||
|
||
<a href="../guide/kubectl-user-authentication-authorization.html">
|
||
|
||
|
||
<b>5.4.4.</b>
|
||
|
||
创建用户认证授权的 kubeconfig 文件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.5" data-path="../guide/ip-masq-agent.html">
|
||
|
||
<a href="../guide/ip-masq-agent.html">
|
||
|
||
|
||
<b>5.4.5.</b>
|
||
|
||
IP 伪装代理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.6" data-path="../guide/auth-with-kubeconfig-or-token.html">
|
||
|
||
<a href="../guide/auth-with-kubeconfig-or-token.html">
|
||
|
||
|
||
<b>5.4.6.</b>
|
||
|
||
使用 kubeconfig 或 token 进行用户身份认证
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.7" data-path="../guide/authentication.html">
|
||
|
||
<a href="../guide/authentication.html">
|
||
|
||
|
||
<b>5.4.7.</b>
|
||
|
||
Kubernetes 中的用户与身份认证授权
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.8" data-path="../guide/kubernetes-security-best-practice.html">
|
||
|
||
<a href="../guide/kubernetes-security-best-practice.html">
|
||
|
||
|
||
<b>5.4.8.</b>
|
||
|
||
Kubernetes 集群安全性配置最佳实践
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5" data-path="../guide/access-kubernetes-cluster.html">
|
||
|
||
<a href="../guide/access-kubernetes-cluster.html">
|
||
|
||
|
||
<b>5.5.</b>
|
||
|
||
访问 Kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.5.1" data-path="../guide/access-cluster.html">
|
||
|
||
<a href="../guide/access-cluster.html">
|
||
|
||
|
||
<b>5.5.1.</b>
|
||
|
||
访问集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.2" data-path="../guide/authenticate-across-clusters-kubeconfig.html">
|
||
|
||
<a href="../guide/authenticate-across-clusters-kubeconfig.html">
|
||
|
||
|
||
<b>5.5.2.</b>
|
||
|
||
使用 kubeconfig 文件配置跨集群认证
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.3" data-path="../guide/connecting-to-applications-port-forward.html">
|
||
|
||
<a href="../guide/connecting-to-applications-port-forward.html">
|
||
|
||
|
||
<b>5.5.3.</b>
|
||
|
||
通过端口转发访问集群中的应用程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.4" data-path="../guide/service-access-application-cluster.html">
|
||
|
||
<a href="../guide/service-access-application-cluster.html">
|
||
|
||
|
||
<b>5.5.4.</b>
|
||
|
||
使用 service 访问群集中的应用程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.5" data-path="../guide/accessing-kubernetes-pods-from-outside-of-the-cluster.html">
|
||
|
||
<a href="../guide/accessing-kubernetes-pods-from-outside-of-the-cluster.html">
|
||
|
||
|
||
<b>5.5.5.</b>
|
||
|
||
从外部访问 Kubernetes 中的 Pod
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.6" data-path="../guide/kubernetes-desktop-client.html">
|
||
|
||
<a href="../guide/kubernetes-desktop-client.html">
|
||
|
||
|
||
<b>5.5.6.</b>
|
||
|
||
Lens - Kubernetes IDE
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.7" data-path="../guide/kubernator-kubernetes-ui.html">
|
||
|
||
<a href="../guide/kubernator-kubernetes-ui.html">
|
||
|
||
|
||
<b>5.5.7.</b>
|
||
|
||
Kubernator - 更底层的 Kubernetes UI
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6" data-path="../guide/application-development-deployment-flow.html">
|
||
|
||
<a href="../guide/application-development-deployment-flow.html">
|
||
|
||
|
||
<b>5.6.</b>
|
||
|
||
在 Kubernetes 中开发部署应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.1" data-path="../guide/deploy-applications-in-kubernetes.html">
|
||
|
||
<a href="../guide/deploy-applications-in-kubernetes.html">
|
||
|
||
|
||
<b>5.6.1.</b>
|
||
|
||
适用于 Kubernetes 的应用开发部署流程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.2" data-path="../guide/migrating-hadoop-yarn-to-kubernetes.html">
|
||
|
||
<a href="../guide/migrating-hadoop-yarn-to-kubernetes.html">
|
||
|
||
|
||
<b>5.6.2.</b>
|
||
|
||
迁移传统应用到 Kubernetes 中 —— 以 Hadoop YARN 为例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.3" data-path="../guide/using-statefulset.html">
|
||
|
||
<a href="../guide/using-statefulset.html">
|
||
|
||
|
||
<b>5.6.3.</b>
|
||
|
||
使用 StatefulSet 部署用状态应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">最佳实践</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="6.1" data-path="../practice/">
|
||
|
||
<a href="../practice/">
|
||
|
||
|
||
<b>6.1.</b>
|
||
|
||
最佳实践概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2" data-path="../practice/install-kubernetes-on-centos.html">
|
||
|
||
<a href="../practice/install-kubernetes-on-centos.html">
|
||
|
||
|
||
<b>6.2.</b>
|
||
|
||
在 CentOS 上部署 Kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.2.1" data-path="../practice/create-tls-and-secret-key.html">
|
||
|
||
<a href="../practice/create-tls-and-secret-key.html">
|
||
|
||
|
||
<b>6.2.1.</b>
|
||
|
||
创建 TLS 证书和秘钥
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.2" data-path="../practice/create-kubeconfig.html">
|
||
|
||
<a href="../practice/create-kubeconfig.html">
|
||
|
||
|
||
<b>6.2.2.</b>
|
||
|
||
创建 kubeconfig 文件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.3" data-path="../practice/etcd-cluster-installation.html">
|
||
|
||
<a href="../practice/etcd-cluster-installation.html">
|
||
|
||
|
||
<b>6.2.3.</b>
|
||
|
||
创建高可用 etcd 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.4" data-path="../practice/kubectl-installation.html">
|
||
|
||
<a href="../practice/kubectl-installation.html">
|
||
|
||
|
||
<b>6.2.4.</b>
|
||
|
||
安装 kubectl 命令行工具
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.5" data-path="../practice/master-installation.html">
|
||
|
||
<a href="../practice/master-installation.html">
|
||
|
||
|
||
<b>6.2.5.</b>
|
||
|
||
部署 master 节点
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.6" data-path="../practice/flannel-installation.html">
|
||
|
||
<a href="../practice/flannel-installation.html">
|
||
|
||
|
||
<b>6.2.6.</b>
|
||
|
||
安装 flannel 网络插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.7" data-path="../practice/node-installation.html">
|
||
|
||
<a href="../practice/node-installation.html">
|
||
|
||
|
||
<b>6.2.7.</b>
|
||
|
||
部署 node 节点
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.8" data-path="../practice/kubedns-addon-installation.html">
|
||
|
||
<a href="../practice/kubedns-addon-installation.html">
|
||
|
||
|
||
<b>6.2.8.</b>
|
||
|
||
安装 kubedns 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.9" data-path="../practice/dashboard-addon-installation.html">
|
||
|
||
<a href="../practice/dashboard-addon-installation.html">
|
||
|
||
|
||
<b>6.2.9.</b>
|
||
|
||
安装 dashboard 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.10" data-path="../practice/heapster-addon-installation.html">
|
||
|
||
<a href="../practice/heapster-addon-installation.html">
|
||
|
||
|
||
<b>6.2.10.</b>
|
||
|
||
安装 heapster 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.11" data-path="../practice/efk-addon-installation.html">
|
||
|
||
<a href="../practice/efk-addon-installation.html">
|
||
|
||
|
||
<b>6.2.11.</b>
|
||
|
||
安装 EFK 插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3" data-path="../practice/install-kubernetes-with-kubeadm.html">
|
||
|
||
<a href="../practice/install-kubernetes-with-kubeadm.html">
|
||
|
||
|
||
<b>6.3.</b>
|
||
|
||
生产级的 Kubernetes 简化管理工具 kubeadm
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.3.1" data-path="../practice/install-kubernetes-on-ubuntu-server-16.04-with-kubeadm.html">
|
||
|
||
<a href="../practice/install-kubernetes-on-ubuntu-server-16.04-with-kubeadm.html">
|
||
|
||
|
||
<b>6.3.1.</b>
|
||
|
||
使用 kubeadm 在 Ubuntu Server 16.04 上快速构建测试集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4" data-path="../practice/service-discovery-and-loadbalancing.html">
|
||
|
||
<a href="../practice/service-discovery-and-loadbalancing.html">
|
||
|
||
|
||
<b>6.4.</b>
|
||
|
||
服务发现与负载均衡
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.4.1" data-path="../practice/traefik-ingress-installation.html">
|
||
|
||
<a href="../practice/traefik-ingress-installation.html">
|
||
|
||
|
||
<b>6.4.1.</b>
|
||
|
||
安装 Traefik ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.2" data-path="../practice/distributed-load-test.html">
|
||
|
||
<a href="../practice/distributed-load-test.html">
|
||
|
||
|
||
<b>6.4.2.</b>
|
||
|
||
分布式负载测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.3" data-path="../practice/network-and-cluster-perfermance-test.html">
|
||
|
||
<a href="../practice/network-and-cluster-perfermance-test.html">
|
||
|
||
|
||
<b>6.4.3.</b>
|
||
|
||
网络和集群性能测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.4" data-path="../practice/edge-node-configuration.html">
|
||
|
||
<a href="../practice/edge-node-configuration.html">
|
||
|
||
|
||
<b>6.4.4.</b>
|
||
|
||
边缘节点配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.5" data-path="../practice/nginx-ingress-installation.html">
|
||
|
||
<a href="../practice/nginx-ingress-installation.html">
|
||
|
||
|
||
<b>6.4.5.</b>
|
||
|
||
安装 Nginx ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.6" data-path="../practice/dns-installation.html">
|
||
|
||
<a href="../practice/dns-installation.html">
|
||
|
||
|
||
<b>6.4.6.</b>
|
||
|
||
安装配置 DNS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.4.6.1" data-path="../practice/configuring-dns.html">
|
||
|
||
<a href="../practice/configuring-dns.html">
|
||
|
||
|
||
<b>6.4.6.1.</b>
|
||
|
||
安装配置 Kube-dns
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.6.2" data-path="../practice/coredns.html">
|
||
|
||
<a href="../practice/coredns.html">
|
||
|
||
|
||
<b>6.4.6.2.</b>
|
||
|
||
安装配置 CoreDNS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5" data-path="../practice/operation.html">
|
||
|
||
<a href="../practice/operation.html">
|
||
|
||
|
||
<b>6.5.</b>
|
||
|
||
运维管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.5.1" data-path="../practice/master-ha.html">
|
||
|
||
<a href="../practice/master-ha.html">
|
||
|
||
|
||
<b>6.5.1.</b>
|
||
|
||
Master 节点高可用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.2" data-path="../practice/service-rolling-update.html">
|
||
|
||
<a href="../practice/service-rolling-update.html">
|
||
|
||
|
||
<b>6.5.2.</b>
|
||
|
||
服务滚动升级
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.3" data-path="../practice/app-log-collection.html">
|
||
|
||
<a href="../practice/app-log-collection.html">
|
||
|
||
|
||
<b>6.5.3.</b>
|
||
|
||
应用日志收集
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.4" data-path="../practice/configuration-best-practice.html">
|
||
|
||
<a href="../practice/configuration-best-practice.html">
|
||
|
||
|
||
<b>6.5.4.</b>
|
||
|
||
配置最佳实践
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.5" data-path="../practice/monitor.html">
|
||
|
||
<a href="../practice/monitor.html">
|
||
|
||
|
||
<b>6.5.5.</b>
|
||
|
||
集群及应用监控
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.6" data-path="../practice/data-persistence-problem.html">
|
||
|
||
<a href="../practice/data-persistence-problem.html">
|
||
|
||
|
||
<b>6.5.6.</b>
|
||
|
||
数据持久化问题
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.7" data-path="../practice/manage-compute-resources-container.html">
|
||
|
||
<a href="../practice/manage-compute-resources-container.html">
|
||
|
||
|
||
<b>6.5.7.</b>
|
||
|
||
管理容器的计算资源
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6" data-path="../practice/storage.html">
|
||
|
||
<a href="../practice/storage.html">
|
||
|
||
|
||
<b>6.6.</b>
|
||
|
||
存储管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.1" data-path="../practice/glusterfs.html">
|
||
|
||
<a href="../practice/glusterfs.html">
|
||
|
||
|
||
<b>6.6.1.</b>
|
||
|
||
GlusterFS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.1.1" data-path="../practice/using-glusterfs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-glusterfs-for-persistent-storage.html">
|
||
|
||
|
||
<b>6.6.1.1.</b>
|
||
|
||
使用 GlusterFS 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.1.2" data-path="../practice/using-heketi-gluster-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-heketi-gluster-for-persistent-storage.html">
|
||
|
||
|
||
<b>6.6.1.2.</b>
|
||
|
||
使用 Heketi 作为 Kubernetes 的持久存储 GlusterFS 的 external provisioner
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.1.3" data-path="../practice/storage-for-containers-using-glusterfs-with-openshift.html">
|
||
|
||
<a href="../practice/storage-for-containers-using-glusterfs-with-openshift.html">
|
||
|
||
|
||
<b>6.6.1.3.</b>
|
||
|
||
在 OpenShift 中使用 GlusterFS 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.2" data-path="../practice/glusterd-2.0.html">
|
||
|
||
<a href="../practice/glusterd-2.0.html">
|
||
|
||
|
||
<b>6.6.2.</b>
|
||
|
||
GlusterD-2.0
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.3" data-path="../practice/ceph.html">
|
||
|
||
<a href="../practice/ceph.html">
|
||
|
||
|
||
<b>6.6.3.</b>
|
||
|
||
Ceph
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.3.1" data-path="../practice/ceph-helm-install-guide-zh.html">
|
||
|
||
<a href="../practice/ceph-helm-install-guide-zh.html">
|
||
|
||
|
||
<b>6.6.3.1.</b>
|
||
|
||
用 Helm 托管安装 Ceph 集群并提供后端存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.3.2" data-path="../practice/using-ceph-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-ceph-for-persistent-storage.html">
|
||
|
||
|
||
<b>6.6.3.2.</b>
|
||
|
||
使用 Ceph 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.3.3" data-path="../practice/rbd-provisioner.html">
|
||
|
||
<a href="../practice/rbd-provisioner.html">
|
||
|
||
|
||
<b>6.6.3.3.</b>
|
||
|
||
使用 rbd-provisioner 提供 rbd 持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.4" data-path="../practice/openebs.html">
|
||
|
||
<a href="../practice/openebs.html">
|
||
|
||
|
||
<b>6.6.4.</b>
|
||
|
||
OpenEBS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.4.1" data-path="../practice/using-openebs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-openebs-for-persistent-storage.html">
|
||
|
||
|
||
<b>6.6.4.1.</b>
|
||
|
||
使用 OpenEBS 做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.5" data-path="../practice/rook.html">
|
||
|
||
<a href="../practice/rook.html">
|
||
|
||
|
||
<b>6.6.5.</b>
|
||
|
||
Rook
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6.6" data-path="../practice/nfs.html">
|
||
|
||
<a href="../practice/nfs.html">
|
||
|
||
|
||
<b>6.6.6.</b>
|
||
|
||
NFS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.6.6.1" data-path="../practice/using-nfs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-nfs-for-persistent-storage.html">
|
||
|
||
|
||
<b>6.6.6.1.</b>
|
||
|
||
利用 NFS 动态提供 Kubernetes 后端存储卷
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.7" data-path="../practice/monitoring.html">
|
||
|
||
<a href="../practice/monitoring.html">
|
||
|
||
|
||
<b>6.7.</b>
|
||
|
||
集群与应用监控
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.7.1" data-path="../practice/heapster.html">
|
||
|
||
<a href="../practice/heapster.html">
|
||
|
||
|
||
<b>6.7.1.</b>
|
||
|
||
Heapster
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.7.1.1" data-path="../practice/using-heapster-to-get-object-metrics.html">
|
||
|
||
<a href="../practice/using-heapster-to-get-object-metrics.html">
|
||
|
||
|
||
<b>6.7.1.1.</b>
|
||
|
||
使用 Heapster 获取集群和对象的 metric 数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.7.2" data-path="../practice/prometheus.html">
|
||
|
||
<a href="../practice/prometheus.html">
|
||
|
||
|
||
<b>6.7.2.</b>
|
||
|
||
Prometheus
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.7.2.1" data-path="../practice/using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
||
<a href="../practice/using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
||
|
||
<b>6.7.2.1.</b>
|
||
|
||
使用 Prometheus 监控 Kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.7.2.2" data-path="../practice/promql.html">
|
||
|
||
<a href="../practice/promql.html">
|
||
|
||
|
||
<b>6.7.2.2.</b>
|
||
|
||
Prometheus 查询语言 PromQL 使用说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.8" data-path="../practice/distributed-tracing.html">
|
||
|
||
<a href="../practice/distributed-tracing.html">
|
||
|
||
|
||
<b>6.8.</b>
|
||
|
||
分布式追踪
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.8.1" data-path="../practice/opentracing.html">
|
||
|
||
<a href="../practice/opentracing.html">
|
||
|
||
|
||
<b>6.8.1.</b>
|
||
|
||
OpenTracing
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.9" data-path="../practice/services-management-tool.html">
|
||
|
||
<a href="../practice/services-management-tool.html">
|
||
|
||
|
||
<b>6.9.</b>
|
||
|
||
服务编排管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.9.1" data-path="../practice/helm.html">
|
||
|
||
<a href="../practice/helm.html">
|
||
|
||
|
||
<b>6.9.1.</b>
|
||
|
||
使用 Helm 管理 Kubernetes 应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.9.2" data-path="../practice/create-private-charts-repo.html">
|
||
|
||
<a href="../practice/create-private-charts-repo.html">
|
||
|
||
|
||
<b>6.9.2.</b>
|
||
|
||
构建私有 Chart 仓库
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.10" data-path="../practice/ci-cd.html">
|
||
|
||
<a href="../practice/ci-cd.html">
|
||
|
||
|
||
<b>6.10.</b>
|
||
|
||
持续集成与发布（CI/CD）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.10.1" data-path="../practice/jenkins-ci-cd.html">
|
||
|
||
<a href="../practice/jenkins-ci-cd.html">
|
||
|
||
|
||
<b>6.10.1.</b>
|
||
|
||
使用 Jenkins 进行持续集成与发布
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.10.2" data-path="../practice/drone-ci-cd.html">
|
||
|
||
<a href="../practice/drone-ci-cd.html">
|
||
|
||
|
||
<b>6.10.2.</b>
|
||
|
||
使用 Drone 进行持续集成与发布
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.11" data-path="../practice/update-and-upgrade.html">
|
||
|
||
<a href="../practice/update-and-upgrade.html">
|
||
|
||
|
||
<b>6.11.</b>
|
||
|
||
更新与升级
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.11.1" data-path="../practice/manually-upgrade.html">
|
||
|
||
<a href="../practice/manually-upgrade.html">
|
||
|
||
|
||
<b>6.11.1.</b>
|
||
|
||
手动升级 Kubernetes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.11.2" data-path="../practice/dashboard-upgrade.html">
|
||
|
||
<a href="../practice/dashboard-upgrade.html">
|
||
|
||
|
||
<b>6.11.2.</b>
|
||
|
||
升级 dashboard
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.12" data-path="../practice/controller-extended.html">
|
||
|
||
<a href="../practice/controller-extended.html">
|
||
|
||
|
||
<b>6.12.</b>
|
||
|
||
扩展控制器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.12.1" data-path="../practice/openkruise.html">
|
||
|
||
<a href="../practice/openkruise.html">
|
||
|
||
|
||
<b>6.12.1.</b>
|
||
|
||
OpenKruise
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.12.1.1" data-path="../practice/in-place-update.html">
|
||
|
||
<a href="../practice/in-place-update.html">
|
||
|
||
|
||
<b>6.12.1.1.</b>
|
||
|
||
原地升级
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.13" data-path="../practice/security-policy.html">
|
||
|
||
<a href="../practice/security-policy.html">
|
||
|
||
|
||
<b>6.13.</b>
|
||
|
||
安全策略
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.13.1" data-path="../practice/open-policy-agent.html">
|
||
|
||
<a href="../practice/open-policy-agent.html">
|
||
|
||
|
||
<b>6.13.1.</b>
|
||
|
||
开放策略代理（OPA）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.13.2" data-path="../practice/cloud-native-security.html">
|
||
|
||
<a href="../practice/cloud-native-security.html">
|
||
|
||
|
||
<b>6.13.2.</b>
|
||
|
||
云原生安全
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">服务网格</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="7.1" data-path="../usecases/service-mesh.html">
|
||
|
||
<a href="../usecases/service-mesh.html">
|
||
|
||
|
||
<b>7.1.</b>
|
||
|
||
服务网格（Service Mesh）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2" data-path="../usecases/the-enterprise-path-to-service-mesh-architectures.html">
|
||
|
||
<a href="../usecases/the-enterprise-path-to-service-mesh-architectures.html">
|
||
|
||
|
||
<b>7.2.</b>
|
||
|
||
企业级服务网格架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="7.2.1" data-path="../usecases/service-mesh-fundamental.html">
|
||
|
||
<a href="../usecases/service-mesh-fundamental.html">
|
||
|
||
|
||
<b>7.2.1.</b>
|
||
|
||
服务网格基础
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.2" data-path="../usecases/comparing-service-mesh-technologies.html">
|
||
|
||
<a href="../usecases/comparing-service-mesh-technologies.html">
|
||
|
||
|
||
<b>7.2.2.</b>
|
||
|
||
服务网格技术对比
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.3" data-path="../usecases/service-mesh-vs-api-gateway.html">
|
||
|
||
<a href="../usecases/service-mesh-vs-api-gateway.html">
|
||
|
||
|
||
<b>7.2.3.</b>
|
||
|
||
服务网格对比 API 网关
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.4" data-path="../usecases/service-mesh-adoption-and-evolution.html">
|
||
|
||
<a href="../usecases/service-mesh-adoption-and-evolution.html">
|
||
|
||
|
||
<b>7.2.4.</b>
|
||
|
||
采纳和演进
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.5" data-path="../usecases/service-mesh-customization-and-integration.html">
|
||
|
||
<a href="../usecases/service-mesh-customization-and-integration.html">
|
||
|
||
|
||
<b>7.2.5.</b>
|
||
|
||
定制和集成
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.6" data-path="../usecases/service-mesh-conclusion.html">
|
||
|
||
<a href="../usecases/service-mesh-conclusion.html">
|
||
|
||
|
||
<b>7.2.6.</b>
|
||
|
||
总结
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3" data-path="../usecases/istio.html">
|
||
|
||
<a href="../usecases/istio.html">
|
||
|
||
|
||
<b>7.3.</b>
|
||
|
||
Istio
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="7.3.1" data-path="../usecases/before-using-istio.html">
|
||
|
||
<a href="../usecases/before-using-istio.html">
|
||
|
||
|
||
<b>7.3.1.</b>
|
||
|
||
使用 Istio 前需要考虑的问题
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.2" data-path="../usecases/sidecar-pattern.html">
|
||
|
||
<a href="../usecases/sidecar-pattern.html">
|
||
|
||
|
||
<b>7.3.2.</b>
|
||
|
||
Sidecar 模式
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.3" data-path="../usecases/sidecar-spec-in-istio.html">
|
||
|
||
<a href="../usecases/sidecar-spec-in-istio.html">
|
||
|
||
|
||
<b>7.3.3.</b>
|
||
|
||
Istio 中 sidecar 的注入规范
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.4" data-path="../usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html">
|
||
|
||
<a href="../usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html">
|
||
|
||
|
||
<b>7.3.4.</b>
|
||
|
||
Sidecar 的注入与透明流量劫持
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.5" data-path="../usecases/istio-traffic-routing.html">
|
||
|
||
<a href="../usecases/istio-traffic-routing.html">
|
||
|
||
|
||
<b>7.3.5.</b>
|
||
|
||
Istio 中的流量路由过程详解
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.6" data-path="../usecases/how-to-integrate-istio-with-vm.html">
|
||
|
||
<a href="../usecases/how-to-integrate-istio-with-vm.html">
|
||
|
||
|
||
<b>7.3.6.</b>
|
||
|
||
Istio 如何支持虚拟机
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.7" data-path="../usecases/istio-vm-support.html">
|
||
|
||
<a href="../usecases/istio-vm-support.html">
|
||
|
||
|
||
<b>7.3.7.</b>
|
||
|
||
Istio 支持虚拟机的历史
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.8" data-path="../usecases/istio-community-tips.html">
|
||
|
||
<a href="../usecases/istio-community-tips.html">
|
||
|
||
|
||
<b>7.3.8.</b>
|
||
|
||
如何参与 Istio 社区及注意事项
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.4" data-path="../usecases/envoy.html">
|
||
|
||
<a href="../usecases/envoy.html">
|
||
|
||
|
||
<b>7.4.</b>
|
||
|
||
Envoy
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="7.4.1" data-path="../usecases/envoy-terminology.html">
|
||
|
||
<a href="../usecases/envoy-terminology.html">
|
||
|
||
|
||
<b>7.4.1.</b>
|
||
|
||
Envoy 的架构与基本术语
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.4.2" data-path="../usecases/envoy-front-proxy.html">
|
||
|
||
<a href="../usecases/envoy-front-proxy.html">
|
||
|
||
|
||
<b>7.4.2.</b>
|
||
|
||
Envoy 作为前端代理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.4.3" data-path="../usecases/envoy-mesh-in-kubernetes-tutorial.html">
|
||
|
||
<a href="../usecases/envoy-mesh-in-kubernetes-tutorial.html">
|
||
|
||
|
||
<b>7.4.3.</b>
|
||
|
||
Envoy mesh 教程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">领域应用</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="8.1" data-path="../usecases/">
|
||
|
||
<a href="../usecases/">
|
||
|
||
|
||
<b>8.1.</b>
|
||
|
||
领域应用概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.2" data-path="../usecases/microservices.html">
|
||
|
||
<a href="../usecases/microservices.html">
|
||
|
||
|
||
<b>8.2.</b>
|
||
|
||
微服务架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.2.1" data-path="../usecases/service-discovery-in-microservices.html">
|
||
|
||
<a href="../usecases/service-discovery-in-microservices.html">
|
||
|
||
|
||
<b>8.2.1.</b>
|
||
|
||
微服务中的服务发现
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.2.2" data-path="../usecases/microservices-for-java-developers.html">
|
||
|
||
<a href="../usecases/microservices-for-java-developers.html">
|
||
|
||
|
||
<b>8.2.2.</b>
|
||
|
||
使用 Java 构建微服务并发布到 Kubernetes 平台
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.2.2.1" data-path="../usecases/spring-boot-quick-start-guide.html">
|
||
|
||
<a href="../usecases/spring-boot-quick-start-guide.html">
|
||
|
||
|
||
<b>8.2.2.1.</b>
|
||
|
||
Spring Boot 快速开始指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.3" data-path="../usecases/big-data.html">
|
||
|
||
<a href="../usecases/big-data.html">
|
||
|
||
|
||
<b>8.3.</b>
|
||
|
||
大数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.3.1" data-path="../usecases/spark-on-kubernetes.html">
|
||
|
||
<a href="../usecases/spark-on-kubernetes.html">
|
||
|
||
|
||
<b>8.3.1.</b>
|
||
|
||
Spark 与 Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.3.1.1" data-path="../usecases/spark-standalone-on-kubernetes.html">
|
||
|
||
<a href="../usecases/spark-standalone-on-kubernetes.html">
|
||
|
||
|
||
<b>8.3.1.1.</b>
|
||
|
||
Spark standalone on Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.3.1.2" data-path="../usecases/running-spark-with-kubernetes-native-scheduler.html">
|
||
|
||
<a href="../usecases/running-spark-with-kubernetes-native-scheduler.html">
|
||
|
||
|
||
<b>8.3.1.2.</b>
|
||
|
||
运行支持 Kubernetes 原生调度的 Spark 程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.4" data-path="../usecases/serverless.html">
|
||
|
||
<a href="../usecases/serverless.html">
|
||
|
||
|
||
<b>8.4.</b>
|
||
|
||
Serverless 架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.4.1" data-path="../usecases/understanding-serverless.html">
|
||
|
||
<a href="../usecases/understanding-serverless.html">
|
||
|
||
|
||
<b>8.4.1.</b>
|
||
|
||
理解 Serverless
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.4.2" data-path="../usecases/faas.html">
|
||
|
||
<a href="../usecases/faas.html">
|
||
|
||
|
||
<b>8.4.2.</b>
|
||
|
||
FaaS（函数即服务）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.4.2.1" data-path="../usecases/openfaas-quick-start.html">
|
||
|
||
<a href="../usecases/openfaas-quick-start.html">
|
||
|
||
|
||
<b>8.4.2.1.</b>
|
||
|
||
OpenFaaS 快速入门指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.4.3" data-path="../usecases/knative.html">
|
||
|
||
<a href="../usecases/knative.html">
|
||
|
||
|
||
<b>8.4.3.</b>
|
||
|
||
Knative
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.5" data-path="../usecases/edge-computing.html">
|
||
|
||
<a href="../usecases/edge-computing.html">
|
||
|
||
|
||
<b>8.5.</b>
|
||
|
||
边缘计算
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.6" data-path="../usecases/ai.html">
|
||
|
||
<a href="../usecases/ai.html">
|
||
|
||
|
||
<b>8.6.</b>
|
||
|
||
人工智能
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.7" data-path="../usecases/observability.html">
|
||
|
||
<a href="../usecases/observability.html">
|
||
|
||
|
||
<b>8.7.</b>
|
||
|
||
可观察性
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">开发指南</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="9.1" data-path="../develop/">
|
||
|
||
<a href="../develop/">
|
||
|
||
|
||
<b>9.1.</b>
|
||
|
||
开发指南概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.2" data-path="../develop/sigs-and-working-group.html">
|
||
|
||
<a href="../develop/sigs-and-working-group.html">
|
||
|
||
|
||
<b>9.2.</b>
|
||
|
||
SIG 和工作组
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.3" data-path="../develop/developing-environment.html">
|
||
|
||
<a href="../develop/developing-environment.html">
|
||
|
||
|
||
<b>9.3.</b>
|
||
|
||
开发环境搭建
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.3.1" data-path="../develop/using-vagrant-and-virtualbox-for-development.html">
|
||
|
||
<a href="../develop/using-vagrant-and-virtualbox-for-development.html">
|
||
|
||
|
||
<b>9.3.1.</b>
|
||
|
||
本地分布式开发环境搭建（使用 Vagrant 和 Virtualbox）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.4" data-path="../develop/testing.html">
|
||
|
||
<a href="../develop/testing.html">
|
||
|
||
|
||
<b>9.4.</b>
|
||
|
||
单元测试和集成测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.5" data-path="../develop/client-go-sample.html">
|
||
|
||
<a href="../develop/client-go-sample.html">
|
||
|
||
|
||
<b>9.5.</b>
|
||
|
||
client-go 示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.5.1" data-path="../develop/client-go-informer-sourcecode-analyse.html">
|
||
|
||
<a href="../develop/client-go-informer-sourcecode-analyse.html">
|
||
|
||
|
||
<b>9.5.1.</b>
|
||
|
||
client-go 中的 informer 源码分析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.6" data-path="../develop/operator.html">
|
||
|
||
<a href="../develop/operator.html">
|
||
|
||
|
||
<b>9.6.</b>
|
||
|
||
Operator
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.6.1" data-path="../develop/operator-sdk.html">
|
||
|
||
<a href="../develop/operator-sdk.html">
|
||
|
||
|
||
<b>9.6.1.</b>
|
||
|
||
operator-sdk
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7" data-path="../develop/kubebuilder.html">
|
||
|
||
<a href="../develop/kubebuilder.html">
|
||
|
||
|
||
<b>9.7.</b>
|
||
|
||
kubebuilder
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.7.1" data-path="../develop/kubebuilder-example.html">
|
||
|
||
<a href="../develop/kubebuilder-example.html">
|
||
|
||
|
||
<b>9.7.1.</b>
|
||
|
||
使用 kubebuilder 创建 operator 示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.8" data-path="../develop/advance-developer.html">
|
||
|
||
<a href="../develop/advance-developer.html">
|
||
|
||
|
||
<b>9.8.</b>
|
||
|
||
高级开发指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.9" data-path="../develop/contribute.html">
|
||
|
||
<a href="../develop/contribute.html">
|
||
|
||
|
||
<b>9.9.</b>
|
||
|
||
社区贡献
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.10" data-path="../develop/minikube.html">
|
||
|
||
<a href="../develop/minikube.html">
|
||
|
||
|
||
<b>9.10.</b>
|
||
|
||
Minikube
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">社区及生态</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="10.1" data-path="cncf.html">
|
||
|
||
<a href="cncf.html">
|
||
|
||
|
||
<b>10.1.</b>
|
||
|
||
云原生计算基金会（CNCF）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="10.1.1" data-path="cncf-charter.html">
|
||
|
||
<a href="cncf-charter.html">
|
||
|
||
|
||
<b>10.1.1.</b>
|
||
|
||
CNCF 章程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.2" data-path="cncf-sig.html">
|
||
|
||
<a href="cncf-sig.html">
|
||
|
||
|
||
<b>10.1.2.</b>
|
||
|
||
CNCF 特别兴趣小组（SIG）说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.3" data-path="cncf-sandbox-criteria.html">
|
||
|
||
<a href="cncf-sandbox-criteria.html">
|
||
|
||
|
||
<b>10.1.3.</b>
|
||
|
||
开源项目加入 CNCF Sandbox 的要求
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.4" data-path="cncf-project-governing.html">
|
||
|
||
<a href="cncf-project-governing.html">
|
||
|
||
|
||
<b>10.1.4.</b>
|
||
|
||
CNCF 中的项目治理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.5" data-path="cncf-ambassador.html">
|
||
|
||
<a href="cncf-ambassador.html">
|
||
|
||
|
||
<b>10.1.5.</b>
|
||
|
||
CNCF Ambassador
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.2" data-path="certification.html">
|
||
|
||
<a href="certification.html">
|
||
|
||
|
||
<b>10.2.</b>
|
||
|
||
认证及培训
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="10.2.1" data-path="../appendix/about-kcsp.html">
|
||
|
||
<a href="../appendix/about-kcsp.html">
|
||
|
||
|
||
<b>10.2.1.</b>
|
||
|
||
认证 Kubernetes 服务提供商（KCSP）说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.2.2" data-path="../appendix/about-cka-candidate.html">
|
||
|
||
<a href="../appendix/about-cka-candidate.html">
|
||
|
||
|
||
<b>10.2.2.</b>
|
||
|
||
认证 Kubernetes 管理员（CKA）说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">附录</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="11.1" data-path="../appendix/">
|
||
|
||
<a href="../appendix/">
|
||
|
||
|
||
<b>11.1.</b>
|
||
|
||
附录说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.2" data-path="../appendix/debug-kubernetes-services.html">
|
||
|
||
<a href="../appendix/debug-kubernetes-services.html">
|
||
|
||
|
||
<b>11.2.</b>
|
||
|
||
Kubernetes 中的应用故障排查
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.3" data-path="../appendix/material-share.html">
|
||
|
||
<a href="../appendix/material-share.html">
|
||
|
||
|
||
<b>11.3.</b>
|
||
|
||
Kubernetes 参考资源
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.4" data-path="../appendix/tricks.html">
|
||
|
||
<a href="../appendix/tricks.html">
|
||
|
||
|
||
<b>11.4.</b>
|
||
|
||
Kubernetes 使用技巧
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.5" data-path="../appendix/issues.html">
|
||
|
||
<a href="../appendix/issues.html">
|
||
|
||
|
||
<b>11.5.</b>
|
||
|
||
Kubernetes 相关问题记录
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.6" data-path="../appendix/summary-and-outlook.html">
|
||
|
||
<a href="../appendix/summary-and-outlook.html">
|
||
|
||
|
||
<b>11.6.</b>
|
||
|
||
Kubernetes 及云原生年度总结及展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="11.6.1" data-path="../appendix/kubernetes-and-cloud-native-summary-in-2017-and-outlook-for-2018.html">
|
||
|
||
<a href="../appendix/kubernetes-and-cloud-native-summary-in-2017-and-outlook-for-2018.html">
|
||
|
||
|
||
<b>11.6.1.</b>
|
||
|
||
Kubernetes 与云原生 2017 年年终总结及 2018 年展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.6.2" data-path="../appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html">
|
||
|
||
<a href="../appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html">
|
||
|
||
|
||
<b>11.6.2.</b>
|
||
|
||
Kubernetes 与云原生 2018 年年终总结及 2019 年展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.7" data-path="../appendix/cncf-annual-report.html">
|
||
|
||
<a href="../appendix/cncf-annual-report.html">
|
||
|
||
|
||
<b>11.7.</b>
|
||
|
||
CNCF 年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="11.7.1" data-path="../appendix/cncf-annual-report-2018.html">
|
||
|
||
<a href="../appendix/cncf-annual-report-2018.html">
|
||
|
||
|
||
<b>11.7.1.</b>
|
||
|
||
CNCF 2018 年年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.7.2" data-path="../appendix/cncf-annual-report-2020.html">
|
||
|
||
<a href="../appendix/cncf-annual-report-2020.html">
|
||
|
||
|
||
<b>11.7.2.</b>
|
||
|
||
CNCF 2020 年年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.8" data-path="../GLOSSARY.html">
|
||
|
||
<a href="../GLOSSARY.html">
|
||
|
||
|
||
<b>11.8.</b>
|
||
|
||
术语表
|
||
|
||
</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=".." >Kubernetes 与云原生应用概览</a>
|
||
</h1>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
<div class="page-wrapper" tabindex="-1" role="main">
|
||
<div class="page-inner">
|
||
|
||
<div class="search-plus" id="book-search-results">
|
||
<div class="search-noresults">
|
||
|
||
<section class="normal markdown-section">
|
||
|
||
<h1 id="kubernetes-与云原生应用概览">Kubernetes 与云原生应用概览</h1>
|
||
<p>2017 年 9 月，Mesos 宣布支持 Kubernetes，而在 2017 年 10 月份的 DockerCon EU 上，Docker 公司宣布官方同时支持 Swarm 和 Kubernetes 容器编排，Kubernetes 已然成为容器编排调度的标准。</p>
|
||
<p>作为全书的开头，首先从历史、生态和应用角度介绍一下 Kubernetes 与云原生应用，深入浅出，高屋建瓴，没有深入到具体细节，主要是为了给初次接触 Kubernetes 的小白扫盲，具体细节请参考链接。</p>
|
||
<h2 id="从云计算到微服务再到云原生计算">从云计算到微服务再到云原生计算</h2>
|
||
<p>下面将从云计算的发展历程引入云原生计算，请先看下图：</p>
|
||
<figure id="fig2.4.1"><a href="../images/cloud-computing-evolution-road.jpg" data-lightbox="1796a721-7dba-4b52-a860-b848a743530f" data-title="云计算演进历程"><img src="../images/cloud-computing-evolution-road.jpg" alt="云计算演进历程"></a><figcaption>图 2.4.1：云计算演进历程</figcaption></figure>
|
||
<p>云原生应用到 2020 年将比目前至少翻一番，下图是 Marc Wilczek 的调查报告。</p>
|
||
<figure id="fig2.4.2"><a href="../images/cloud-native-comes-of-age.jpg" data-lightbox="a9e1c901-3767-49f9-b770-8486e89eb329" data-title="来自 Twitter @MarcWilczek"><img src="../images/cloud-native-comes-of-age.jpg" alt="来自 Twitter @MarcWilczek"></a><figcaption>图 2.4.2：来自 Twitter @MarcWilczek</figcaption></figure>
|
||
<h3 id="云计算介绍">云计算介绍</h3>
|
||
<p>云计算包含的内容十分繁杂，也有很多技术和公司牵强附会说自己是云计算公司，说自己是做云的，实际上可能风马牛不相及。说白了，云计算就是一种配置资源的方式，根据资源配置方式的不同我们可以把云计算从宏观上分为以下三种类型：</p>
|
||
<ul>
|
||
<li>IaaS：这是为了想要建立自己的商业模式并进行自定义的客户，例如亚马逊的 EC2、S3 存储、Rackspace 虚拟机等都是 IaaS。</li>
|
||
<li>PaaS：工具和服务的集合，对于想用它来构建自己的应用程序或者想快速得将应用程序部署到生产环境而不必关心底层硬件的用户和开发者来说是特别有用的，比如 Cloud Foundry、Google App Engine、Heroku 等。</li>
|
||
<li>SaaS：终端用户可以直接使用的应用程序。这个就太多，我们生活中用到的很多软件都是 SaaS 服务，只要基于互联网来提供的服务基本都是 SaaS 服务，有的服务是免费的，比如 Google Docs，还有更多的是根据我们购买的 Plan 和使用量付费，比如 GitHub、各种云存储。</li>
|
||
</ul>
|
||
<h3 id="微服务介绍">微服务介绍</h3>
|
||
<p>微服务（Microservices）这个词比较新颖，但是其实这种架构设计理念早就有了。微服务是一种分布式架构设计理念，为了推动细粒度服务的使用，这些服务要能协同工作，每个服务都有自己的生命周期。一个微服务就是一个独立的实体，可以独立的部署在 PAAS 平台上，也可以作为一个独立的进程在主机中运行。服务之间通过 API 访问，修改一个服务不会影响其它服务。</p>
|
||
<p>要想了解微服务的详细内容推荐阅读《微服务设计》（Sam Newman 著），我写过这本书的读书笔记 - <a href="https://jimmysong.io/posts/microservice-reading-notes/" target="_blank">微服务设计读书笔记</a>。</p>
|
||
<p>下文中会谈到 Kubernetes 与微服务的关系，其中 Kubernetes 的 service 天生就适合于微服务。</p>
|
||
<h3 id="云原生概念介绍">云原生概念介绍</h3>
|
||
<p>下面是云原生概念思维导图</p>
|
||
<figure id="fig2.4.3"><a href="../images/cloud-native-architecutre-mindnode.jpg" data-lightbox="48cec90a-52b6-49f8-8358-d1a85c1d9f29" data-title="云原生思维导图"><img src="../images/cloud-native-architecutre-mindnode.jpg" alt="云原生思维导图"></a><figcaption>图 2.4.3：云原生思维导图</figcaption></figure>
|
||
<p>云原生准确来说是一种文化，更是一种潮流，它是云计算的一个必然导向。它的意义在于让云成为云化战略成功的基石，而不是阻碍，如果业务应用上云之后开发和运维人员比原先还痛苦，成本还高的话，这样的云我们宁愿不上。</p>
|
||
<p>自从云的概念开始普及，许多公司都部署了实施云化的策略，纷纷搭建起云平台，希望完成传统应用到云端的迁移。但是这个过程中会遇到一些技术难题，上云以后，效率并没有变得更高，故障也没有迅速定位。</p>
|
||
<p>为了解决传统应用升级缓慢、架构臃肿、不能快速迭代、故障不能快速定位、问题无法快速解决等问题，云原生这一概念横空出世。云原生可以改进应用开发的效率，改变企业的组织结构，甚至会在文化层面上直接影响一个公司的决策。</p>
|
||
<p>另外，云原生也很好地解释了云上运行的应用应该具备什么样的架构特性 —— 敏捷性、可扩展性、故障可恢复性。</p>
|
||
<p>综上所述，云原生应用应该具备以下几个关键词：</p>
|
||
<ul>
|
||
<li>敏捷</li>
|
||
<li>可靠</li>
|
||
<li>高弹性</li>
|
||
<li>易扩展</li>
|
||
<li>故障隔离保护</li>
|
||
<li>不中断业务持续更新</li>
|
||
</ul>
|
||
<p>以上特性也是云原生区别于传统云应用的优势特点。</p>
|
||
<p>从宏观概念上讲，云原生是不同思想的集合，集目前各种热门技术之大成，具体包括如下图所示的几个部分。</p>
|
||
<h2 id="kubernetes-与云原生的关系">Kubernetes 与云原生的关系</h2>
|
||
<p>Kuberentes 可以说是乘着 Docker 和微服务的东风，一经推出便迅速蹿红，它的很多设计思想都契合了微服务和云原生应用的设计法则，这其中最著名的就是开发了 <a href="https://www.heroku.com" target="_blank">Heroku</a> PaaS 平台的工程师们总结的 <a href="https://12factor.net/" target="_blank">Twelve-factor App</a> 了。</p>
|
||
<p>下面我将讲解 Kubernetes 设计时是如何按照了十二因素应用法则，并给出 Kubernetes 中的应用示例，并附上一句话简短的介绍。</p>
|
||
<h3 id="kubernetes-介绍">Kubernetes 介绍</h3>
|
||
<p><a href="http://kubernetes.io" target="_blank">Kubernetes</a> 是 Google 基于 <a href="https://research.google.com/pubs/pub43438.html" target="_blank">Borg</a> 开源的容器编排调度引擎，作为 <a href="http://cncf.io" target="_blank">CNCF</a>（Cloud Native Computing Foundation）最重要的组件之一，它的目标不仅仅是一个编排系统，而是提供一个规范，可以让你来描述集群的架构，定义服务的最终状态，Kubernetes 可以帮你将系统自动得达到和维持在这个状态。</p>
|
||
<p>更直白的说，Kubernetes 用户可以通过编写一个 YAML 或者 json 格式的配置文件，也可以通过工具 / 代码生成或直接请求 Kubernetes API 创建应用，该配置文件中包含了用户想要应用程序保持的状态，不论整个 Kubernetes 集群中的个别主机发生什么问题，都不会影响应用程序的状态，你还可以通过改变该配置文件或请求 Kubernetes API 来改变应用程序的状态。</p>
|
||
<h3 id="12-因素应用">12 因素应用</h3>
|
||
<p>12 因素应用提出已经有几年的时间了，每个人对其可能都有自己的理解，切不可生搬硬套，也不一定所有云原生应用都必须符合这 12 条法则，其中有几条法则可能还有点争议，有人对其的解释和看法不同。</p>
|
||
<p>大家不要孤立的来看这每一个因素，将其与自己软件开发流程联系起来，这 12 个因素大致就是按照软件从开发到交付的流程顺序来写的。</p>
|
||
<figure id="fig2.4.4"><a href="../images/12-factor-app.png" data-lightbox="d930228d-958f-408e-9f84-b9623d3b6317" data-title="十二因素应用"><img src="../images/12-factor-app.png" alt="十二因素应用"></a><figcaption>图 2.4.4：十二因素应用</figcaption></figure>
|
||
<p><strong>1. 基准代码 </strong></p>
|
||
<p>每个代码仓库（repo）都生成 docker image 保存到镜像仓库中，并使用唯一的 ID 管理，在 Jenkins 中使用编译时的 ID。</p>
|
||
<p><strong>2. 依赖 </strong></p>
|
||
<p>显式的声明代码中的依赖，使用软件包管理工具声明，比如 Go 中的 Glide。</p>
|
||
<p><strong>3. 配置 </strong></p>
|
||
<p>将配置与代码分离，应用部署到 Kubernetes 中可以使用容器的环境变量或 ConfigMap 挂载到容器中。</p>
|
||
<p><strong>4. 后端服务 </strong></p>
|
||
<p>把后端服务当作附加资源，实质上是计算存储分离和降低服务耦合，分解单体应用。</p>
|
||
<p><strong>5. 构建、发布、运行 </strong></p>
|
||
<p>严格分离构建和运行，每次修改代码生成新的镜像，重新发布，不能直接修改运行时的代码和配置。</p>
|
||
<p><strong>6. 进程 </strong></p>
|
||
<p>应用程序进程应该是无状态的，这意味着再次重启后还可以计算出原先的状态。</p>
|
||
<p><strong>7. 端口绑定 </strong></p>
|
||
<p>在 Kubernetes 中每个 Pod 都有独立的 IP，每个运行在 Pod 中的应用不必关心端口是否重复，只需在 service 中指定端口，集群内的 service 通过配置互相发现。</p>
|
||
<p><strong>8. 并发 </strong></p>
|
||
<p>每个容器都是一个进程，通过增加容器的副本数实现并发。</p>
|
||
<p><strong>9. 易处理 </strong></p>
|
||
<p>快速启动和优雅终止可最大化健壮性，Kuberentes 优秀的 <a href="https://jimmysong.io/posts/pod-lifecycle/" target="_blank">Pod 生存周期控制</a>。</p>
|
||
<p><strong>10. 开发环境与线上环境等价 </strong></p>
|
||
<p>在 Kubernetes 中可以创建多个 namespace，使用相同的镜像可以很方便的复制一套环境出来，镜像的使用可以很方便的部署一个后端服务。</p>
|
||
<p><strong>11. 日志 </strong></p>
|
||
<p>把日志当作事件流，使用 stdout 输出并收集汇聚起来，例如到 ES 中统一查看。</p>
|
||
<p><strong>12. 管理进程 </strong></p>
|
||
<p>后台管理任务当作一次性进程运行，<code>kubectl exec</code> 进入容器内部操作。</p>
|
||
<p>另外，<a href="https://jimmysong.io/cloud-native-go" target="_blank">Cloud Native Go</a> 这本书的作者，CapitalOne 公司的 Kevin Hoffman 在 TalkingData T11 峰会上的 <a href="https://jimmysong.io/blog/high-level-cloud-native-from-kevin-hoffman/" target="_blank">High Level Cloud Native</a> 的演讲中讲述了云原生应用的 15 个因素，在原先的 12 因素应用的基础上又增加了如下三个因素：</p>
|
||
<p><strong>API 优先 </strong></p>
|
||
<ul>
|
||
<li>服务间的合约</li>
|
||
<li>团队协作的规约</li>
|
||
<li>文档化、规范化</li>
|
||
<li>RESTful 或 RPC</li>
|
||
</ul>
|
||
<p><strong>监控</strong></p>
|
||
<ul>
|
||
<li>实时监控远程应用</li>
|
||
<li>应用性能监控（APM）</li>
|
||
<li>应用健康监控</li>
|
||
<li>系统日志</li>
|
||
<li>不建议在线 Debug</li>
|
||
</ul>
|
||
<p><strong>认证授权</strong></p>
|
||
<ul>
|
||
<li>不要等最后才去考虑应用的安全性</li>
|
||
<li>详细设计、明确声明、文档化</li>
|
||
<li>Bearer token、OAuth、OIDC 认证</li>
|
||
<li>操作审计</li>
|
||
</ul>
|
||
<h2 id="kubernetes-中的资源管理与容器设计模式">Kubernetes 中的资源管理与容器设计模式</h2>
|
||
<p>Kubernetes 通过声明式配置，真正让开发人员能够理解应用的状态，并通过同一份配置可以立马启动一个一模一样的环境，大大提高了应用开发和部署的效率，其中 Kubernetes 设计的多种资源类型可以帮助我们定义应用的运行状态，并使用资源配置来细粒度的明确限制应用的资源使用。</p>
|
||
<p>而容器生态的成熟是 Kubernetes 诞生的前提，在谈到容器的设计模式之前我们先来了解下容器生态，请看下图：</p>
|
||
<figure id="fig2.4.5"><a href="../images/container-ecosystem.png" data-lightbox="7c3556f1-2be9-43e9-b87f-597c8eaa0a63" data-title="容器生态"><img src="../images/container-ecosystem.png" alt="容器生态"></a><figcaption>图 2.4.5：容器生态</figcaption></figure>
|
||
<p>关于 Docker 容器的更多内容请参考 <a href="../appendix/docker-best-practice.md">Docker 最佳实践</a>。</p>
|
||
<h3 id="容器的设计模式">容器的设计模式</h3>
|
||
<p>Kubernetes 提供了多种资源对象，用户可以根据自己应用的特性加以选择。这些对象有：</p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th style="text-align:left">类别</th>
|
||
<th>名称</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td style="text-align:left">资源对象</td>
|
||
<td>Pod、ReplicaSet、ReplicationController、Deployment、StatefulSet、DaemonSet、Job、CronJob、HorizontalPodAutoscaler</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align:left">配置对象</td>
|
||
<td>Node、Namespace、Service、Secret、ConfigMap、Ingress、Label、CustomResourceDefinition、 ServiceAccount</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align:left">存储对象</td>
|
||
<td>Volume、Persistent Volume</td>
|
||
</tr>
|
||
<tr>
|
||
<td style="text-align:left">策略对象</td>
|
||
<td>SecurityContext、ResourceQuota、LimitRange</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p>在 Kubernetes 系统中，<em>Kubernetes 对象</em> 是持久化的条目。Kubernetes 使用这些条目去表示整个集群的状态。特别地，它们描述了如下信息：</p>
|
||
<ul>
|
||
<li>什么容器化应用在运行（以及在哪个 Node 上）</li>
|
||
<li>可以被应用使用的资源</li>
|
||
<li>关于应用如何表现的策略，比如重启策略、升级策略，以及容错策略</li>
|
||
</ul>
|
||
<p>Kubernetes 对象是 “目标性记录” —— 一旦创建对象，Kubernetes 系统将持续工作以确保对象存在。通过创建对象，可以有效地告知 Kubernetes 系统，所需要的集群工作负载看起来是什么样子的，这就是 Kubernetes 集群的 <strong> 期望状态 </strong>。</p>
|
||
<p>详见 <a href="https://jimmysong.io/kubernetes-handbook/concepts/objects.html" target="_blank">Kubernetes Handbook - Objects</a>。</p>
|
||
<h3 id="资源限制与配额">资源限制与配额</h3>
|
||
<p>两层的资源限制与配置</p>
|
||
<ul>
|
||
<li>Pod 级别，最小的资源调度单位</li>
|
||
<li>Namespace 级别，限制资源配额和每个 Pod 的资源使用区间</li>
|
||
</ul>
|
||
<p>请参考 <a href="https://jimmysong.io/posts/kubernetes-resourcequota-limitrange-management/" target="_blank">Kubernetes 中的 ResourceQuota 和 LimitRange 配置资源限额</a></p>
|
||
<h2 id="管理-kubernetes-集群">管理 Kubernetes 集群</h2>
|
||
<p>手工部署 Kubernetes 是一个很艰巨的活，你需要了解网络配置、Docker 的安装与使用、镜像仓库的构建、角色证书的创建、Kubernetes 的基本原理和构成、Kubernetes 应用程序的 yaml 文件编写等。</p>
|
||
<p>我编写了一本 <a href="https://jimmysong.io/kubernetes-handbook/" target="_blank">kubernetes-handbook</a> 可供大家免费阅读，该书记录了本人从零开始学习和使用 Kubernetes 的心路历程，着重于经验分享和总结，同时也会有相关的概念解析，希望能够帮助大家少踩坑，少走弯路。</p>
|
||
<h3 id="部署-kubernetes-集群">部署 Kubernetes 集群</h3>
|
||
<p>使用二进制部署 <code>kubernetes</code> 集群的所有组件和插件，而不是使用 <code>kubeadm</code> 等自动化方式来部署集群，同时开启了集群的 TLS 安全认证，这样可以帮助我们了解系统各组件的交互原理，进而能快速解决实际问题。详见 <a href="../practice/install-kubernetes-on-centos.html">在 CentOS 上部署 Kubernetes 集群</a>。</p>
|
||
<p><strong>集群详情</strong></p>
|
||
<ul>
|
||
<li>Kubernetes 1.6.0</li>
|
||
<li>Docker 1.12.5（使用 yum 安装）</li>
|
||
<li>Etcd 3.1.5</li>
|
||
<li>Flanneld 0.7 vxlan 网络</li>
|
||
<li>TLS 认证通信 (所有组件，如 etcd、kubernetes master 和 node)</li>
|
||
<li>RBAC 授权</li>
|
||
<li>kubelet TLS BootStrapping</li>
|
||
<li>kubedns、dashboard、heapster(influxdb、grafana)、EFK(elasticsearch、fluentd、kibana) 集群插件</li>
|
||
<li>私有 Docker 镜像仓库 <a href="https://github.com/goharbor/harbor" target="_blank">Harbor</a>（请自行部署，Harbor 提供离线安装包，直接使用 docker-compose 启动即可）</li>
|
||
</ul>
|
||
<p><strong>步骤介绍</strong></p>
|
||
<ol>
|
||
<li><a href="../practice/create-tls-and-secret-key.html">创建 TLS 证书和秘钥</a></li>
|
||
<li><a href="../practice/create-kubeconfig.html">创建 kubeconfig 文件</a></li>
|
||
<li><a href="../practice/etcd-cluster-installation.html">创建高可用 etcd 集群</a></li>
|
||
<li><a href="../practice/kubectl-installation.html">安装 kubectl 命令行工具</a></li>
|
||
<li><a href="../practice/master-installation.html">部署 master 节点</a></li>
|
||
<li><a href="../practice/flannel-installation.html">安装 flannel 网络插件</a></li>
|
||
<li><a href="../practice/node-installation.html">部署 node 节点</a></li>
|
||
<li><a href="../practice/kubedns-addon-installation.html">安装 kubedns 插件</a></li>
|
||
<li><a href="../practice/dashboard-addon-installation.html">安装 dashboard 插件</a></li>
|
||
<li><a href="../practice/heapster-addon-installation.html">安装 heapster 插件</a></li>
|
||
<li><a href="../practice/efk-addon-installation.html">安装 EFK 插件</a></li>
|
||
</ol>
|
||
<h3 id="服务发现与负载均衡">服务发现与负载均衡</h3>
|
||
<p>Kubernetes 在设计之初就充分考虑了针对容器的服务发现与负载均衡机制，提供了 Service 资源，并通过 kube-proxy 配合 cloud provider 来适应不同的应用场景。随着 Kubernetes 用户的激增，用户场景的不断丰富，又产生了一些新的负载均衡机制。目前，Kubernetes 中的负载均衡大致可以分为以下几种机制，每种机制都有其特定的应用场景：</p>
|
||
<ul>
|
||
<li><strong>Service</strong>：直接用 Service 提供 cluster 内部的负载均衡，并借助 cloud provider 提供的 LB 提供外部访问</li>
|
||
<li><strong>Ingress</strong>：还是用 Service 提供 cluster 内部的负载均衡，但是通过自定义 LB 提供外部访问</li>
|
||
<li><strong>Service Load Balancer</strong>：把 load balancer 直接跑在容器中，实现 Bare Metal 的 Service Load Balancer</li>
|
||
<li><strong>Custom Load Balancer</strong>：自定义负载均衡，并替代 kube-proxy，一般在物理部署 Kubernetes 时使用，方便接入公司已有的外部服务</li>
|
||
</ul>
|
||
<p>详见 <a href="https://jimmysong.io/kubernetes-handbook/practice/service-discovery-and-loadbalancing.html" target="_blank">Kubernetes Handbook - 服务发现与负载均衡</a>。</p>
|
||
<h3 id="持续集成与发布">持续集成与发布</h3>
|
||
<figure id="fig2.4.6"><a href="../images/kubernetes-jenkins-ci-cd.png" data-lightbox="4f9fbd3e-1a41-4d36-bfa0-19702982cfc0" data-title="使用 Jenkins 进行持续集成与发布流程图"><img src="../images/kubernetes-jenkins-ci-cd.png" alt="使用 Jenkins 进行持续集成与发布流程图"></a><figcaption>图 2.4.6：使用 Jenkins 进行持续集成与发布流程图</figcaption></figure>
|
||
<p>应用构建和发布流程说明：</p>
|
||
<ol>
|
||
<li>用户向 Gitlab 提交代码，代码中必须包含 <code>Dockerfile</code></li>
|
||
<li>将代码提交到远程仓库</li>
|
||
<li>用户在发布应用时需要填写 git 仓库地址和分支、服务类型、服务名称、资源数量、实例个数，确定后触发 Jenkins 自动构建</li>
|
||
<li>Jenkins 的 CI 流水线自动编译代码并打包成 Docker 镜像推送到 Harbor 镜像仓库</li>
|
||
<li>Jenkins 的 CI 流水线中包括了自定义脚本，根据我们已准备好的 Kubernetes 的 YAML 模板，将其中的变量替换成用户输入的选项</li>
|
||
<li>生成应用的 Kubernetes YAML 配置文件</li>
|
||
<li>更新 Ingress 的配置，根据新部署的应用的名称，在 Ingress 的配置文件中增加一条路由信息</li>
|
||
<li>更新 PowerDNS，向其中插入一条 DNS 记录，IP 地址是边缘节点的 IP 地址。关于边缘节点，请查看 <a href="https://jimmysong.io/kubernetes-handbook/practice/edge-node-configuration.html" target="_blank">边缘节点配置</a></li>
|
||
<li>Jenkins 调用 Kubernetes 的 API，部署应用</li>
|
||
</ol>
|
||
<h3 id="日志收集与监控">日志收集与监控</h3>
|
||
<p>基于现有的 ELK 日志收集方案，稍作改造，选用 <a href="https://www.elastic.co/products/beats/filebeat" target="_blank">filebeat</a> 来收集日志，可以作为 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> 的形式跟应用运行在同一个 Pod 中，比较轻量级消耗资源比较少。</p>
|
||
<figure id="fig2.4.7"><a href="../images/filebeat-log-collector-arch.png" data-lightbox="c2bf6cf6-cdbb-4057-9d7a-0b93bfea0fd6" data-title="filebeat 日志收集架构图"><img src="../images/filebeat-log-collector-arch.png" alt="filebeat 日志收集架构图"></a><figcaption>图 2.4.7：filebeat 日志收集架构图</figcaption></figure>
|
||
<p>详见 <a href="https://jimmysong.io/kubernetes-handbook/practice/app-log-collection.html" target="_blank">Kubernetes Handbook - 应用日志收集</a>。</p>
|
||
<h3 id="安全性与权限管理">安全性与权限管理</h3>
|
||
<p>Kubernetes 是一个多租户的云平台，因此必须对用户的权限加以限制，对用户空间进行隔离。Kubernetes 中的隔离主要包括这几种：</p>
|
||
<ul>
|
||
<li>网络隔离：需要使用网络插件，比如 <a href="https://coreos.com/flannel/" target="_blank">flannel</a>, <a href="https://www.projectcalico.org/" target="_blank">calico</a>。</li>
|
||
<li>资源隔离：kubernetes 原生支持资源隔离，pod 就是资源隔离和调度的最小单位，同时使用 <a href="https://jimmysong.io/kubernetes-handbook/concepts/namespace.html" target="_blank">namespace</a> 限制用户空间和资源限额。</li>
|
||
<li>身份隔离：使用 <a href="https://jimmysong.io/kubernetes-handbook/guide/rbac.html" target="_blank">RBAC - 基于角色的访问控制</a>，多租户的身份认证和权限控制。</li>
|
||
</ul>
|
||
<h2 id="如何开发-kubernetes-原生应用步骤介绍">如何开发 Kubernetes 原生应用步骤介绍</h2>
|
||
<p>当我们有了一个 kubernetes 集群后，如何在上面开发和部署应用，应该遵循怎样的流程？下面我将展示如何使用 go 语言开发和部署一个 Kubernetes native 应用，使用 wercker 进行持续集成与持续发布，我将以一个很简单的前后端访问，获取伪造数据并展示的例子来说明。</p>
|
||
<h3 id="云原生应用开发示例">云原生应用开发示例</h3>
|
||
<p>我们将按照如下步骤来开发部署一个 Kubernetes 原生应用并将它部署到 Kubernetes 集群上开放给集群外访问：</p>
|
||
<ol>
|
||
<li>服务 API 的定义</li>
|
||
<li>使用 Go 语言开发 Kubernetes 原生应用</li>
|
||
<li>一个持续构建与发布工具与环境</li>
|
||
<li>使用 traefik 和 VIP 做边缘节点提供外部访问路由</li>
|
||
</ol>
|
||
<p>我写了两个示例用于演示，开发部署一个伪造的 metric 并显示在 web 页面上，包括两个 service：</p>
|
||
<ul>
|
||
<li><a href="https://github.com/rootsongjc/k8s-app-monitor-test" target="_blank">k8s-app-monitor-test</a>：生成模拟的监控数据，发送 http 请求，获取 json 返回值</li>
|
||
<li><a href="https://github.com/rootsongjc/k8s-app-monitor-agent" target="_blank">K8s-app-monitor-agent</a>：获取监控数据并绘图，访问浏览器获取图表</li>
|
||
</ul>
|
||
<p><strong>定义 API 生成 API文档 </strong></p>
|
||
<p>使用 <code>API blueprint</code> 格式，定义 API 文档，格式类似于 markdown，再使用 <a href="https://github.com/danielgtaylor/aglio" target="_blank">aglio</a> 生成 HTML 文档。</p>
|
||
<figure id="fig2.4.8"><a href="../images/k8s-app-monitor-test-api-doc.jpg" data-lightbox="34e3b208-0934-44c4-b482-07d72d1b6f60" data-title="API 文档"><img src="../images/k8s-app-monitor-test-api-doc.jpg" alt="API 文档"></a><figcaption>图 2.4.8：API 文档</figcaption></figure>
|
||
<p>详见：<a href="https://jimmysong.io/posts/creating-cloud-native-app-with-kubernetes/" target="_blank">如何开发部署 Kubernetes Native 应用</a>。</p>
|
||
<h2 id="如何迁移到云原生应用架构">如何迁移到云原生应用架构</h2>
|
||
<p>Pivotal（后被 VMware 收购）是云原生应用的提出者，并推出了 Pivotal Cloud Foundry 云原生应用平台和 <a href="https://spring.io/" target="_blank">Spring</a> 开源 Java 开发框架，成为云原生应用架构中先驱者和探路者。</p>
|
||
<p>原书作于 2015 年，其中的示例主要针对 Java 应用，实际上也适用于任何应用类型，云原生应用架构适用于异构语言的程序开发，不仅仅是针对 Java 语言的程序开发。截止到本人翻译本书时，云原生应用生态系统已经初具规模，<a href="https://cncf.io/" target="_blank">CNCF</a> 成员不断发展壮大，基于云原生的创业公司不断涌现，<a href="https://kubernetes.io/" target="_blank">Kubernetes</a> 引领容器编排潮流，和 Service Mesh 技术（如 <a href="https://linkerd.io/" target="_blank">Linkerd</a> 和 <a href="https://istio.io/" target="_blank">Istio</a>） 的出现，Go 语言的兴起（参考另一本书 <a href="http://rootsongjc.github.io/cloud-native-go" target="_blank">Cloud Native Go</a>）等为我们将应用迁移到云原生架构的提供了更多的方案选择。</p>
|
||
<h3 id="迁移到云原生应用架构指南">迁移到云原生应用架构指南</h3>
|
||
<p>指出了迁移到云原生应用架构需要做出的企业文化、组织架构和技术变革，并给出了迁移指南。</p>
|
||
<p>主要讨论的应用程序架构包括：</p>
|
||
<ul>
|
||
<li>十二因素应用程序：云原生应用程序架构模式的集合</li>
|
||
<li>微服务：独立部署的服务，只做一件事情</li>
|
||
<li>自助服务的敏捷基础设施：快速，可重复和一致地提供应用环境和后台服务的平台</li>
|
||
<li>基于 API 的协作：发布和版本化的 API，允许在云原生应用程序架构中的服务之间进行交互</li>
|
||
<li>抗压性：根据压力变强的系统</li>
|
||
</ul>
|
||
<p>详见：<a href="https://jimmysong.io/migrating-to-cloud-native-application-architectures/" target="_blank">迁移到云原生应用架构</a>。</p>
|
||
<h3 id="迁移案例解析">迁移案例解析</h3>
|
||
<p>迁移步骤示意图如下：</p>
|
||
<figure id="fig2.4.9"><a href="../images/migrating-hadoop-yarn-to-kubernetes.png" data-lightbox="c6054ce1-9999-4541-be28-0deabf3ecaaa" data-title="迁移步骤示意图"><img src="../images/migrating-hadoop-yarn-to-kubernetes.png" alt="迁移步骤示意图"></a><figcaption>图 2.4.9：迁移步骤示意图</figcaption></figure>
|
||
<p>步骤说明：</p>
|
||
<ol>
|
||
<li>将原有应用拆解为服务</li>
|
||
<li>定义服务的接口 / API 通信方式</li>
|
||
<li>编写启动脚本作为容器的进程入口</li>
|
||
<li>准备应用配置文件</li>
|
||
<li>容器化、制作镜像</li>
|
||
<li>准备 Kubernetes YAML 文件</li>
|
||
<li>如果有外置配置文件需要创建 ConfigMap 或 Secret 存储</li>
|
||
</ol>
|
||
<p>详见：<a href="https://jimmysong.io/posts/migrating-hadoop-yarn-to-kubernetes/" target="_blank">迁移传统应用到 Kubernetes 步骤详解 —— 以 Hadoop YARN 为例</a>。</p>
|
||
<h2 id="service-mesh-基本原理和示例介绍">Service Mesh 基本原理和示例介绍</h2>
|
||
<p>Service Mesh 现在一般被翻译作服务网格，目前主流的 Service Mesh 有如下几款：</p>
|
||
<ul>
|
||
<li><a href="https://istio.io" target="_blank">Istio</a>：IBM、Google、Lyft 共同开源，详细文档见 <a href="https://istio.io" target="_blank">Istio 官方文档</a></li>
|
||
<li><a href="https://linkerd.io" target="_blank">Linkerd</a>：原 Twitter 工程师开发，现为 <a href="https://cncf.io" target="_blank">CNCF</a> 中的项目之一</li>
|
||
<li><a href="https://www.envoyproxy.io/" target="_blank">Envoy</a>：Lyft 开源的，可以在 Istio 中使用 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">Sidecar</a> 模式运行</li>
|
||
</ul>
|
||
<p>此外还有很多其它的 Service Mesh 鱼贯而出，请参考 <a href="https://jimmysong.io/awesome-cloud-native" target="_blank">awesome-cloud-native</a>。</p>
|
||
<h3 id="什么是-service-mesh">什么是 Service Mesh</h3>
|
||
<p>如果用一句话来解释什么是 Service Mesh，可以将它比作是应用程序或者说微服务间的 TCP/IP，负责服务之间的网络调用、限流、熔断和监控。对于编写应用程序来说一般无须关心 TCP/IP 这一层（比如通过 HTTP 协议的 RESTful 应用），同样使用 Service Mesh 也就无须关心服务之间的那些原来是通过应用程序或者其他框架实现的事情，比如 Spring Cloud、OSS，现在只要交给 Service Mesh 就可以了。</p>
|
||
<figure id="fig2.4.10"><a href="../images/serivce-mesh-control-plane.png" data-lightbox="a42d65a0-aa99-44a0-9e2a-356fa52b60bf" data-title="service mesh 架构图"><img src="../images/serivce-mesh-control-plane.png" alt="service mesh 架构图"></a><figcaption>图 2.4.10：service mesh 架构图</figcaption></figure>
|
||
<p>详见 <a href="https://jimmysong.io/blog/what-is-a-service-mesh/" target="_blank">什么是 Service Mesh - jimmysong.io</a>。</p>
|
||
<h2 id="使用案例">使用案例</h2>
|
||
<p>Kubernetes 作为云原生计算的基本组件之一，自开源以来热度与日俱增，它可以跟我们的生产结合，擦出很多火花，比如 FaaS 和 Serverless 类应用，都很适合运行在 Kubernetes 上。</p>
|
||
<p>关于 Cloud Native 开源软件生态请参考 <a href="https://jimmysong.io/awesome-cloud-native" target="_blank">Awesome Cloud Native - jimmysong.io</a>。</p>
|
||
<h3 id="devops">DevOps</h3>
|
||
<p>下面是社区中 Kubernetes 开源爱好者的分享内容，我觉得是对 Kubernetes 在 DevOps 中应用的很好的形式值得大家借鉴。</p>
|
||
<p>真正践行 DevOps，让开发人员在掌握自己的开发和测试环境，让环境一致，让开发效率提升，让运维没有堆积如山的 tickets，让监控更加精准，从 Kubernetes 平台开始。</p>
|
||
<p><strong>行动指南</strong></p>
|
||
<ol>
|
||
<li>根据环境（比如开发、测试、生产）划分 <code>namespace</code>，也可以根据项目来划分</li>
|
||
<li>再为每个用户划分一个 <code>namespace</code>、创建一个 <code>serviceaccount</code> 和 <code>kubeconfig</code> 文件，不同 <code>namespace</code> 间的资源隔离，目前不隔离网络，不同 <code>namespace</code> 间的服务可以互相访问</li>
|
||
<li>创建 YAML 模板，降低编写 Kubernetes YAML 文件编写难度</li>
|
||
<li>在 <code>kubectl</code> 命令上再封装一层，增加用户身份设置和环境初始化操作，简化 <code>kubectl</code> 命令和常用功能</li>
|
||
<li>管理员通过 dashboard 查看不同 <code>namespace</code> 的状态，也可以使用它来使操作更便捷</li>
|
||
<li>所有应用的日志统一收集到 ElasticSearch 中，统一日志访问入口</li>
|
||
<li>可以通过 Grafana 查看所有 namespace 中的应用的状态和 kubernetes 集群本身的状态</li>
|
||
<li>需要持久化的数据保存在分布式存储中，例如 GlusterFS 或 Ceph 中</li>
|
||
</ol>
|
||
<p><strong>使用 Kibana 查看日志</strong></p>
|
||
<p>日志字段中包括了应用的标签、容器名称、主机名称、宿主机名称、IP 地址、时间。</p>
|
||
<figure id="fig2.4.11"><a href="../images/filebeat-docker-test.jpg" data-lightbox="5e25c4ad-86c8-4cfb-9f12-f9a6b8876360" data-title="kibana 界面"><img src="../images/filebeat-docker-test.jpg" alt="kibana 界面"></a><figcaption>图 2.4.11：kibana 界面</figcaption></figure>
|
||
<p><strong>使用 Grafana 查看应用状态</strong></p>
|
||
<p><strong>注</strong>：以下监控图片由云原生社区涂小刚提供</p>
|
||
<p>监控分类示意图：</p>
|
||
<figure id="fig2.4.12"><a href="../images/kubernetes-devops-example-grafana-1.png" data-lightbox="4e47d1aa-d6f6-499b-a70d-d641ed95e4c6" data-title="Kubernetes 集群全局监控图 1"><img src="../images/kubernetes-devops-example-grafana-1.png" alt="Kubernetes 集群全局监控图 1"></a><figcaption>图 2.4.12：Kubernetes 集群全局监控图 1</figcaption></figure>
|
||
<p>该监控图可以看到集群硬件使用情况。</p>
|
||
<figure id="fig2.4.13"><a href="../images/kubernetes-devops-example-grafana-2.png" data-lightbox="748478b5-5ed0-4f6d-890e-718d064b91ab" data-title="Kubernetes 全局监控图 2"><img src="../images/kubernetes-devops-example-grafana-2.png" alt="Kubernetes 全局监控图 2"></a><figcaption>图 2.4.13：Kubernetes 全局监控图 2</figcaption></figure>
|
||
<p>该监控可以看到单个用户的 namespace 下的所有资源的使用情况。</p>
|
||
<figure id="fig2.4.14"><a href="../images/kubernetes-devops-example-grafana-3.png" data-lightbox="02268fc4-4d30-43fb-8387-d341a5c91320" data-title="Grafana 界面示意图 3"><img src="../images/kubernetes-devops-example-grafana-3.png" alt="Grafana 界面示意图 3"></a><figcaption>图 2.4.14：Grafana 界面示意图 3</figcaption></figure>
|
||
<h3 id="spark-on-kubernetes">Spark on Kubernetes</h3>
|
||
<p>Spark 原生支持 Standalone、Mesos 和 YARN 资源调度，现已支持 Kubernetes 原生调度，详见 <a href="https://jimmysong.io/spark-on-k8s" target="_blank">Spark on Kubernetes</a>。</p>
|
||
<p><strong>为何要使用 Spark on Kubernetes</strong></p>
|
||
<p>使用 Kubernetes 原生调度的 Spark on Kubernetes 是对原先的 Spark on YARN 和 YARN on Docker 的改变是革命性的，主要表现在以下几点：</p>
|
||
<ol>
|
||
<li><strong>Kubernetes 原生调度 </strong>：不再需要二层调度，直接使用 Kubernetes 的资源调度功能，跟其他应用共用整个 Kubernetes 管理的资源池；</li>
|
||
<li><strong>资源隔离，粒度更细</strong>：原先 YARN 中的 queue 在 Spark on Kubernetes 中已不存在，取而代之的是 Kubernetes 中原生的 namespace，可以为每个用户分别指定一个 namespace，限制用户的资源 quota；</li>
|
||
<li><strong>细粒度的资源分配 </strong>：可以给每个 spark 任务指定资源限制，实际指定多少资源就使用多少资源，因为没有了像 YARN那样的二层调度（圈地式的），所以可以更高效和细粒度的使用资源；</li>
|
||
<li><strong>监控的变革</strong>：因为做到了细粒度的资源分配，所以可以对用户提交的每一个任务做到资源使用的监控，从而判断用户的资源使用情况，所有的 metric 都记录在数据库中，甚至可以为每个用户的每次任务提交计量；</li>
|
||
<li><strong>日志的变革</strong>：用户不再通过 YARN 的 web 页面来查看任务状态，而是通过 pod 的 log 来查看，可将所有的 Kuberentes 中的应用的日志等同看待收集起来，然后可以根据标签查看对应应用的日志；</li>
|
||
</ol>
|
||
<p><strong>如何提交任务</strong></p>
|
||
<p>仍然使用 <code>spark-submit</code> 提交 spark 任务，可以直接指定 Kubernetes API server 地址，下面的命令提交本地 jar 包到 Kubernetes 集群上运行，同时指定了运行任务的用户、提交命名的用户、运行的 excutor 实例数、driver 和 executor 的资源限制、使用的 spark 版本等信息。</p>
|
||
<p>详细使用说明见 <a href="https://jimmysong.io/spark-on-k8s/user-guide.html" target="_blank">Apache Spark on Kubernetes 用户指南 - jimmysong.io</a>。</p>
|
||
<pre class="language-"><code class="lang-bash">./spark-submit <span class="token punctuation">\</span>
|
||
--deploy-mode cluster <span class="token punctuation">\</span>
|
||
--class com.talkingdata.alluxio.hadooptest <span class="token punctuation">\</span>
|
||
--master k8s://https://172.20.0.113:6443 <span class="token punctuation">\</span>
|
||
--kubernetes-namespace spark-cluster <span class="token punctuation">\</span>
|
||
--conf spark.kubernetes.driverEnv.SPARK_USER<span class="token operator">=</span>hadoop <span class="token punctuation">\</span>
|
||
--conf spark.kubernetes.driverEnv.HADOOP_USER_NAME<span class="token operator">=</span>hadoop <span class="token punctuation">\</span>
|
||
--conf spark.executorEnv.HADOOP_USER_NAME<span class="token operator">=</span>hadoop <span class="token punctuation">\</span>
|
||
--conf spark.executorEnv.SPARK_USER<span class="token operator">=</span>hadoop <span class="token punctuation">\</span>
|
||
--conf spark.kubernetes.authenticate.driver.serviceAccountName<span class="token operator">=</span>spark <span class="token punctuation">\</span>
|
||
--conf spark.driver.memory<span class="token operator">=</span>100G <span class="token punctuation">\</span>
|
||
--conf spark.executor.memory<span class="token operator">=</span>10G <span class="token punctuation">\</span>
|
||
--conf spark.driver.cores<span class="token operator">=</span><span class="token number">30</span> <span class="token punctuation">\</span>
|
||
--conf spark.executor.cores<span class="token operator">=</span><span class="token number">2</span> <span class="token punctuation">\</span>
|
||
--conf spark.driver.maxResultSize<span class="token operator">=</span>10240m <span class="token punctuation">\</span>
|
||
--conf spark.kubernetes.driver.limit.cores<span class="token operator">=</span><span class="token number">32</span> <span class="token punctuation">\</span>
|
||
--conf spark.kubernetes.executor.limit.cores<span class="token operator">=</span><span class="token number">3</span> <span class="token punctuation">\</span>
|
||
--conf spark.kubernetes.executor.memoryOverhead<span class="token operator">=</span>2g <span class="token punctuation">\</span>
|
||
--conf spark.executor.instances<span class="token operator">=</span><span class="token number">5</span> <span class="token punctuation">\</span>
|
||
--conf spark.app.name<span class="token operator">=</span>spark-pi <span class="token punctuation">\</span>
|
||
--conf spark.kubernetes.driver.docker.image<span class="token operator">=</span>harbor-001.jimmysong.io/library/spark-driver:v2.1.0-kubernetes-0.3.1-1 <span class="token punctuation">\</span>
|
||
--conf spark.kubernetes.executor.docker.image<span class="token operator">=</span>harbor-001.jimmysong.io/library/spark-executor:v2.1.0-kubernetes-0.3.1-1 <span class="token punctuation">\</span>
|
||
--conf spark.kubernetes.initcontainer.docker.image<span class="token operator">=</span>harbor-001.jimmysong.io/library/spark-init:v2.1.0-kubernetes-0.3.1-1 <span class="token punctuation">\</span>
|
||
--conf spark.kubernetes.resourceStagingServer.uri<span class="token operator">=</span>http://172.20.0.114:31000 <span class="token punctuation">\</span>
|
||
~/Downloads/tendcloud_2.10-1.0.jar
|
||
</code></pre>
|
||
<p><strong>监控</strong></p>
|
||
<p>下图是从 Kubernetes dashboard 上看到的 spark-cluster 这个 namespace 上运行的应用情况。</p>
|
||
<figure id="fig2.4.15"><a href="../images/spark-job-on-kubernetes-example-1.jpg" data-lightbox="c9e6f33d-f3c7-4259-ac57-63fa4ed22a7f" data-title="dashboard"><img src="../images/spark-job-on-kubernetes-example-1.jpg" alt="dashboard"></a><figcaption>图 2.4.15：dashboard</figcaption></figure>
|
||
<p>下图是从 Grafana 监控页面上查看到的某个 executor 资源占用情况。</p>
|
||
<figure id="fig2.4.16"><a href="../images/spark-job-on-kubernetes-example-2.jpg" data-lightbox="cc5519a1-ab93-40ff-b518-d58bed6fea98" data-title="Grafana"><img src="../images/spark-job-on-kubernetes-example-2.jpg" alt="Grafana"></a><figcaption>图 2.4.16：Grafana</figcaption></figure>
|
||
<h2 id="参考">参考</h2>
|
||
<ul>
|
||
<li><a href="https://jimmysong.io/migrating-to-cloud-native-application-architectures" target="_blank">迁移到云原生应用架构指南 - jimmysong.io</a></li>
|
||
<li><a href="https://jimmysong.io/book/cloud-native-go/" target="_blank">Cloud Native Go - jimmysong.io</a></li>
|
||
<li><a href="https://jimmysong.io/book/cloud-native-python/" target="_blank">Cloud Native Python - jimmysong.io</a></li>
|
||
<li><a href="https://istio.io/latest/zh/" target="_blank">Istio 官方文档（中文）- istio.io</a> </li>
|
||
</ul>
|
||
<footer class="page-footer"><span class="copyright">Copyright © 2017-2022 | Distributed under <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/deed.zh" target="_blank">CC BY 4.0</a> | <a href="https://jimmysong.io" target="_blank">jimmysong.io</a> all right reserved.</span><span class="footer-modification"> Updated at
|
||
2022-04-27 04:14: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="kubernetes-history.html" class="navigation navigation-prev " aria-label="Previous page: Kubernetes 的诞生">
|
||
<i class="fa fa-angle-left"></i>
|
||
</a>
|
||
|
||
|
||
<a href="from-kubernetes-to-cloud-native.html" class="navigation navigation-next " aria-label="Next page: 云原生应用之路 —— 从 Kubernetes 到云原生">
|
||
<i class="fa fa-angle-right"></i>
|
||
</a>
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<script>
|
||
var gitbook = gitbook || [];
|
||
gitbook.push(function() {
|
||
gitbook.page.hasChanged({"page":{"title":"Kubernetes 与云原生应用概览","level":"2.4","depth":1,"next":{"title":"云原生应用之路 —— 从 Kubernetes 到云原生","level":"2.5","depth":1,"path":"cloud-native/from-kubernetes-to-cloud-native.md","ref":"cloud-native/from-kubernetes-to-cloud-native.md","articles":[]},"previous":{"title":"Kubernetes 的诞生","level":"2.3","depth":1,"path":"cloud-native/kubernetes-history.md","ref":"cloud-native/kubernetes-history.md","articles":[]},"dir":"ltr"},"config":{"plugins":["github","codesnippet","splitter","page-toc-button","image-captions","editlink","back-to-top-button","-lunr","-search","search-plus","github-buttons@2.1.0","favicon@^0.0.2","tbfed-pagefooter@^0.0.1","3-ba","theme-default","-highlight","prism","prism-themes","lightbox","ga","sitemap-general","hide-element","expandable-chapters-small","insert-logo","adsense"],"styles":{"ebook":"styles/ebook.css","epub":"styles/epub.css","mobi":"styles/mobi.css","pdf":"styles/pdf.css","print":"styles/print.css","website":"styles/website.css"},"pluginsConfig":{"tbfed-pagefooter":{"copyright":"Copyright © 2017-2022 | Distributed under <a href=https://creativecommons.org/licenses/by-nc-sa/4.0/deed.zh>CC BY 4.0</a> | <a href=https://jimmysong.io>jimmysong.io</a>","modify_label":" Updated at ","modify_format":"YYYY-MM-DD HH:mm:ss"},"prism":{"css":["prism-themes/themes/prism-ghcolors.css"]},"github":{"url":"https://github.com/rootsongjc/kubernetes-handbook"},"editlink":{"label":"编辑本页","multilingual":false,"base":"https://github.com/rootsongjc/kubernetes-handbook/blob/master/"},"splitter":{},"adsense":{"client":"ca-pub-4029167986768912","slot":"2445941692","format":"auto","element":".page-inner section","position":"bottom"},"codesnippet":{},"sitemap-general":{"prefix":"https://jimmysong.io/kubernetes-handbook/"},"hide-element":{"elements":[".gitbook-link"]},"fontsettings":{"theme":"white","family":"sans","size":2},"favicon":{"shortcut":"favicon.ico","bookmark":"favicon.ico"},"lightbox":{"jquery":true,"sameUuid":false},"page-toc-button":{},"back-to-top-button":{},"prism-themes":{},"github-buttons":{"repo":"rootsongjc/kubernetes-handbook","types":["star"],"size":"small"},"3-ba":{"configuration":"auto","token":"11f7d254cfa4e0ca44b175c66d379ecc"},"expandable-chapters-small":{},"ga":{"configuration":"auto","token":"UA-93485976-1"},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"theme-default":{"showLevel":true,"styles":{"ebook":"styles/ebook.css","epub":"styles/epub.css","mobi":"styles/mobi.css","pdf":"styles/pdf.css","print":"styles/print.css","website":"styles/website.css"}},"insert-logo":{"style":"background: none; max-height: 100px; min-height: 30px","url":"https://jimmysong.io/images/logo-black-text.png"},"search-plus":{},"image-captions":{"caption":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","variable_name":"_pictures"}},"theme":"default","author":"宋净超（Jimmy Song）","pdf":{"pageNumbers":true,"fontSize":12,"fontFamily":"Arial","paperSize":"a4","chapterMark":"pagebreak","pageBreaksBefore":"/","margin":{"right":62,"left":62,"top":56,"bottom":56}},"structure":{"langs":"LANGS.md","readme":"README.md","glossary":"GLOSSARY.md","summary":"SUMMARY.md"},"variables":{"_pictures":[{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.1","level":"2.4","list_caption":"Figure: 云计算演进历程","alt":"云计算演进历程","nro":1,"url":"../images/cloud-computing-evolution-road.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云计算演进历程","attributes":{},"skip":false,"key":"2.4.1"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.2","level":"2.4","list_caption":"Figure: 来自 Twitter @MarcWilczek","alt":"来自 Twitter @MarcWilczek","nro":2,"url":"../images/cloud-native-comes-of-age.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"来自 Twitter @MarcWilczek","attributes":{},"skip":false,"key":"2.4.2"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.3","level":"2.4","list_caption":"Figure: 云原生思维导图","alt":"云原生思维导图","nro":3,"url":"../images/cloud-native-architecutre-mindnode.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生思维导图","attributes":{},"skip":false,"key":"2.4.3"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.4","level":"2.4","list_caption":"Figure: 十二因素应用","alt":"十二因素应用","nro":4,"url":"../images/12-factor-app.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"十二因素应用","attributes":{},"skip":false,"key":"2.4.4"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.5","level":"2.4","list_caption":"Figure: 容器生态","alt":"容器生态","nro":5,"url":"../images/container-ecosystem.png","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"容器生态","attributes":{},"skip":false,"key":"2.4.5"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.6","level":"2.4","list_caption":"Figure: 使用 Jenkins 进行持续集成与发布流程图","alt":"使用 Jenkins 进行持续集成与发布流程图","nro":6,"url":"../images/kubernetes-jenkins-ci-cd.png","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"使用 Jenkins 进行持续集成与发布流程图","attributes":{},"skip":false,"key":"2.4.6"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.7","level":"2.4","list_caption":"Figure: filebeat 日志收集架构图","alt":"filebeat 日志收集架构图","nro":7,"url":"../images/filebeat-log-collector-arch.png","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"filebeat 日志收集架构图","attributes":{},"skip":false,"key":"2.4.7"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.8","level":"2.4","list_caption":"Figure: API 文档","alt":"API 文档","nro":8,"url":"../images/k8s-app-monitor-test-api-doc.jpg","index":8,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"API 文档","attributes":{},"skip":false,"key":"2.4.8"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.9","level":"2.4","list_caption":"Figure: 迁移步骤示意图","alt":"迁移步骤示意图","nro":9,"url":"../images/migrating-hadoop-yarn-to-kubernetes.png","index":9,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"迁移步骤示意图","attributes":{},"skip":false,"key":"2.4.9"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.10","level":"2.4","list_caption":"Figure: service mesh 架构图","alt":"service mesh 架构图","nro":10,"url":"../images/serivce-mesh-control-plane.png","index":10,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"service mesh 架构图","attributes":{},"skip":false,"key":"2.4.10"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.11","level":"2.4","list_caption":"Figure: kibana 界面","alt":"kibana 界面","nro":11,"url":"../images/filebeat-docker-test.jpg","index":11,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"kibana 界面","attributes":{},"skip":false,"key":"2.4.11"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.12","level":"2.4","list_caption":"Figure: Kubernetes 集群全局监控图 1","alt":"Kubernetes 集群全局监控图 1","nro":12,"url":"../images/kubernetes-devops-example-grafana-1.png","index":12,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 集群全局监控图 1","attributes":{},"skip":false,"key":"2.4.12"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.13","level":"2.4","list_caption":"Figure: Kubernetes 全局监控图 2","alt":"Kubernetes 全局监控图 2","nro":13,"url":"../images/kubernetes-devops-example-grafana-2.png","index":13,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 全局监控图 2","attributes":{},"skip":false,"key":"2.4.13"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.14","level":"2.4","list_caption":"Figure: Grafana 界面示意图 3","alt":"Grafana 界面示意图 3","nro":14,"url":"../images/kubernetes-devops-example-grafana-3.png","index":14,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Grafana 界面示意图 3","attributes":{},"skip":false,"key":"2.4.14"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.15","level":"2.4","list_caption":"Figure: dashboard","alt":"dashboard","nro":15,"url":"../images/spark-job-on-kubernetes-example-1.jpg","index":15,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"dashboard","attributes":{},"skip":false,"key":"2.4.15"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.4.16","level":"2.4","list_caption":"Figure: Grafana","alt":"Grafana","nro":16,"url":"../images/spark-job-on-kubernetes-example-2.jpg","index":16,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Grafana","attributes":{},"skip":false,"key":"2.4.16"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.1","level":"2.5","list_caption":"Figure: 容器生态图","alt":"容器生态图","nro":17,"url":"../images/container-ecosystem.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"容器生态图","attributes":{},"skip":false,"key":"2.5.1"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.2","level":"2.5","list_caption":"Figure: Kubernetes架构","alt":"Kubernetes架构","nro":18,"url":"../images/kubernetes-high-level-component-archtecture.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes架构","attributes":{},"skip":false,"key":"2.5.2"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.3","level":"2.5","list_caption":"Figure: 云原生的核心目标","alt":"云原生的核心目标","nro":19,"url":"../images/cloud-native-core-target.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生的核心目标","attributes":{},"skip":false,"key":"2.5.3"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.4","level":"2.5","list_caption":"Figure: FaaS Landscape","alt":"FaaS Landscape","nro":20,"url":"../images/redpoint-faas-landscape.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"FaaS Landscape","attributes":{},"skip":false,"key":"2.5.4"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.5","level":"2.5","list_caption":"Figure: 运行在 Kubernetes 上的负载（2017 年）","alt":"运行在 Kubernetes 上的负载（2017 年）","nro":21,"url":"../images/0069RVTdgy1fv5mxr6fxtj31kw11q484.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"运行在 Kubernetes 上的负载（2017 年）","attributes":{},"skip":false,"key":"2.5.5"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.6","level":"2.5","list_caption":"Figure: Gartner 技术爆发趋势图（2017 年）","alt":"Gartner 技术爆发趋势图（2017 年）","nro":22,"url":"../images/0069RVTdgy1fv5my2jtxzj315o0z8dkr.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Gartner 技术爆发趋势图（2017 年）","attributes":{},"skip":false,"key":"2.5.6"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.7","level":"2.5","list_caption":"Figure: 微服务的关注点","alt":"微服务的关注点","nro":23,"url":"../images/microservices-concerns.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"微服务的关注点","attributes":{},"skip":false,"key":"2.5.7"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.8","level":"2.5","list_caption":"Figure: 微服务中的两种服务发现方式","alt":"微服务中的两种服务发现方式","nro":24,"url":"../images/service-discovery-in-microservices.png","index":8,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"微服务中的两种服务发现方式","attributes":{},"skip":false,"key":"2.5.8"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.9","level":"2.5","list_caption":"Figure: Cloud Native Features","alt":"Cloud Native Features","nro":25,"url":"https://jimmysong.io/kubernetes-handbook/images/cloud-native-architecutre-mindnode.jpg","index":9,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Cloud Native Features","attributes":{},"skip":false,"key":"2.5.9"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.10","level":"2.5","list_caption":"Figure: Cloud Native Landscape v1.0","alt":"Cloud Native Landscape v1.0","nro":26,"url":"../images/0069RVTdgy1fv5myp6ednj31kw0w0u0x.jpg","index":10,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Cloud Native Landscape v1.0","attributes":{},"skip":false,"key":"2.5.10"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.11","level":"2.5","list_caption":"Figure: 使用 Kubernetes 构建云原生架构应用","alt":"使用 Kubernetes 构建云原生架构应用","nro":27,"url":"../images/building-cloud-native-architecture-with-kubernetes.png","index":11,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"使用 Kubernetes 构建云原生架构应用","attributes":{},"skip":false,"key":"2.5.11"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.12","level":"2.5","list_caption":"Figure: 创建 Kubernetes 原生应用","alt":"创建 Kubernetes 原生应用","nro":28,"url":"../images/creating-kubernetes-native-app.jpg","index":12,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"创建 Kubernetes 原生应用","attributes":{},"skip":false,"key":"2.5.12"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.13","level":"2.5","list_caption":"Figure: istio vs linkerd","alt":"istio vs linkerd","nro":29,"url":"../images/istio-vs-linkerd.jpg","index":13,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"istio vs linkerd","attributes":{},"skip":false,"key":"2.5.13"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.14","level":"2.5","list_caption":"Figure: 部署流水线","alt":"部署流水线","nro":30,"url":"../images/0069RVTdgy1fv5mzj8rj6j318g1ewtfc.jpg","index":14,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"部署流水线","attributes":{},"skip":false,"key":"2.5.14"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.15","level":"2.5","list_caption":"Figure: 使用不同调度器的 Spark on Kubernetes","alt":"使用不同调度器的 Spark on Kubernetes","nro":31,"url":"../images/spark-on-kubernetes-with-different-schedulers.jpg","index":15,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"使用不同调度器的 Spark on Kubernetes","attributes":{},"skip":false,"key":"2.5.15"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.16","level":"2.5","list_caption":"Figure: Kubernetes 解决方案","alt":"Kubernetes 解决方案","nro":32,"url":"../images/0069RVTdgy1fv5mzywc83j31fk1i8qg4.jpg","index":16,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 解决方案","attributes":{},"skip":false,"key":"2.5.16"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.5.17","level":"2.5","list_caption":"Figure: Kubernetes SIG","alt":"Kubernetes SIG","nro":33,"url":"../images/kubernetes-sigs.jpg","index":17,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes SIG","attributes":{},"skip":false,"key":"2.5.17"},{"backlink":"cloud-native/define-cloud-native-app.html#fig2.6.1","level":"2.6","list_caption":"Figure: 云原生应用模型","alt":"云原生应用模型","nro":34,"url":"../images/cloud-native-app-model.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生应用模型","attributes":{},"skip":false,"key":"2.6.1"},{"backlink":"cloud-native/define-cloud-native-app.html#fig2.6.2","level":"2.6","list_caption":"Figure: 云原生应用模型中的目标角色","alt":"云原生应用模型中的目标角色","nro":35,"url":"../images/roles.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生应用模型中的目标角色","attributes":{},"skip":false,"key":"2.6.2"},{"backlink":"cloud-native/oam.html#fig2.6.1.1","level":"2.6.1","list_caption":"Figure: OAM 规范示意图","alt":"OAM 规范示意图","nro":36,"url":"../images/oam-spec.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OAM 规范示意图","attributes":{},"skip":false,"key":"2.6.1.1"},{"backlink":"cloud-native/oam.html#fig2.6.1.2","level":"2.6.1","list_caption":"Figure: OAM 的原理","alt":"OAM 的原理","nro":37,"url":"../images/oam-principle.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OAM 的原理","attributes":{},"skip":false,"key":"2.6.1.2"},{"backlink":"cloud-native/crossplane.html#fig2.6.2.1","level":"2.6.2","list_caption":"Figure: Wordpress 页面","alt":"Wordpress 页面","nro":38,"url":"../images/wordpress.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Wordpress 页面","attributes":{},"skip":false,"key":"2.6.2.1"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.1","level":"2.7.1","list_caption":"Figure: 云原生编程语言ballerina","alt":"云原生编程语言ballerina","nro":39,"url":"../images/philosophy-page-diagrams-top.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生编程语言ballerina","attributes":{},"skip":false,"key":"2.7.1.1"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.2","level":"2.7.1","list_caption":"Figure: 云原生编程语言Ballerina的序列图设计理念","alt":"云原生编程语言Ballerina的序列图设计理念","nro":40,"url":"../images/philosophy-principle-diagrams-01.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生编程语言Ballerina的序列图设计理念","attributes":{},"skip":false,"key":"2.7.1.2"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.3","level":"2.7.1","list_caption":"Figure: 云原生编程语言Ballerina的并发理念","alt":"云原生编程语言Ballerina的并发理念","nro":41,"url":"../images/philosophy-principle-diagrams-02.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生编程语言Ballerina的并发理念","attributes":{},"skip":false,"key":"2.7.1.3"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.4","level":"2.7.1","list_caption":"Figure: 云原生编程语言ballerina运行时架构","alt":"云原生编程语言ballerina运行时架构","nro":42,"url":"../images/philosophy-diagrams-for-site-02.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生编程语言ballerina运行时架构","attributes":{},"skip":false,"key":"2.7.1.4"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.5","level":"2.7.1","list_caption":"Figure: 云原生编程语言ballerina部署架构图","alt":"云原生编程语言ballerina部署架构图","nro":43,"url":"../images/philosophy-diagrams-for-site-03.png","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生编程语言ballerina部署架构图","attributes":{},"skip":false,"key":"2.7.1.5"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.7.1.6","level":"2.7.1","list_caption":"Figure: 云原生编程语言ballerina生命周期架构图","alt":"云原生编程语言ballerina生命周期架构图","nro":44,"url":"../images/philosophy-diagrams-for-site-04.png","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生编程语言ballerina生命周期架构图","attributes":{},"skip":false,"key":"2.7.1.6"},{"backlink":"cloud-native/cloud-native-programming-language-pulumi.html#fig2.7.2.1","level":"2.7.2","list_caption":"Figure: 云原生编程语言Pulumi","alt":"云原生编程语言Pulumi","nro":45,"url":"../images/pulumi.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生编程语言Pulumi","attributes":{},"skip":false,"key":"2.7.2.1"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.1","level":"2.8","list_caption":"Figure: Kubernetes 云原生的操作系统","alt":"Kubernetes 云原生的操作系统","nro":46,"url":"../images/00704eQkgy1frr4z08j6oj31p20w2n6n.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 云原生的操作系统","attributes":{},"skip":false,"key":"2.8.1"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.2","level":"2.8","list_caption":"Figure: 操作系统层次","alt":"操作系统层次","nro":47,"url":"../images/00704eQkgy1frr52hl4eaj31qy15en74.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"操作系统层次","attributes":{},"skip":false,"key":"2.8.2"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.3","level":"2.8","list_caption":"Figure: 云原生景观图","alt":"云原生景观图","nro":48,"url":"../images/00704eQkgy1frr53j3aiuj32fs1dc7wi.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生景观图","attributes":{},"skip":false,"key":"2.8.3"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.4","level":"2.8","list_caption":"Figure: KubeVirt架构图","alt":"KubeVirt架构图","nro":49,"url":"../images/00704eQkgy1frr54de5oyj31qw14qn2x.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"KubeVirt架构图","attributes":{},"skip":false,"key":"2.8.4"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.5","level":"2.8","list_caption":"Figure: Kubernetes中的资源隔离","alt":"Kubernetes中的资源隔离","nro":50,"url":"../images/00704eQkgy1frr54ztql2j329q0zwwlf.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes中的资源隔离","attributes":{},"skip":false,"key":"2.8.5"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.6","level":"2.8","list_caption":"Figure: OpenEBS 控制平面架构","alt":"OpenEBS 控制平面架构","nro":51,"url":"../images/00704eQkgy1frr56m7z2sj31y010y17y.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OpenEBS 控制平面架构","attributes":{},"skip":false,"key":"2.8.6"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.7","level":"2.8","list_caption":"Figure: OpenEBS 的存储卷管理","alt":"OpenEBS 的存储卷管理","nro":52,"url":"../images/00704eQkgy1frr57nm2mnj31xk11qqej.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OpenEBS 的存储卷管理","attributes":{},"skip":false,"key":"2.8.7"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.8","level":"2.8","list_caption":"Figure: Hadoop YARN 迁移到 Kubernetes的示例","alt":"Hadoop YARN 迁移到 Kubernetes的示例","nro":53,"url":"../images/00704eQkgy1frr58ebf2lj323o11219r.jpg","index":8,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Hadoop YARN 迁移到 Kubernetes的示例","attributes":{},"skip":false,"key":"2.8.8"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.9","level":"2.8","list_caption":"Figure: Spark on Yarn with Kubernetes","alt":"Spark on Yarn with Kubernetes","nro":54,"url":"../images/00704eQkgy1frr59gzzwsj32gg16k4qp.jpg","index":9,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Spark on Yarn with Kubernetes","attributes":{},"skip":false,"key":"2.8.9"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.10","level":"2.8","list_caption":"Figure: 云原生与12因素应用","alt":"云原生与12因素应用","nro":55,"url":"../images/00704eQkgy1frr5arzvetj31no12mdre.jpg","index":10,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生与12因素应用","attributes":{},"skip":false,"key":"2.8.10"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.11","level":"2.8","list_caption":"Figure: 云原生编程语言","alt":"云原生编程语言","nro":56,"url":"../images/00704eQkgy1frr5c8bwmtj31ou152qc3.jpg","index":11,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生编程语言","attributes":{},"skip":false,"key":"2.8.11"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.12","level":"2.8","list_caption":"Figure: Gitkube","alt":"Gitkube","nro":57,"url":"../images/00704eQkgy1frr5bulhuhj329m10iwua.jpg","index":12,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Gitkube","attributes":{},"skip":false,"key":"2.8.12"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.13","level":"2.8","list_caption":"Figure: Kuberentes中的流量管理","alt":"Kuberentes中的流量管理","nro":58,"url":"../images/00704eQkgy1frr5dsurx6j320i140tpf.jpg","index":13,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kuberentes中的流量管理","attributes":{},"skip":false,"key":"2.8.13"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.14","level":"2.8","list_caption":"Figure: Istio Service Mesh架构图","alt":"Istio Service Mesh架构图","nro":59,"url":"../images/00704eQkgy1frr5exqm7kj320u18mh2t.jpg","index":14,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Istio Service Mesh架构图","attributes":{},"skip":false,"key":"2.8.14"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.15","level":"2.8","list_caption":"Figure: Service Mesh架构","alt":"Service Mesh架构","nro":60,"url":"../images/00704eQkgy1frr5fxzoltj32f81akqr2.jpg","index":15,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Service Mesh架构","attributes":{},"skip":false,"key":"2.8.15"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.8.16","level":"2.8","list_caption":"Figure: Envoy proxy架构图","alt":"Envoy proxy架构图","nro":61,"url":"../images/envoy-arch.png","index":16,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Envoy proxy架构图","attributes":{},"skip":false,"key":"2.8.16"},{"backlink":"cloud-native/play-with-kubernetes.html#fig3.2.1","level":"3.2","list_caption":"Figure: Play with Kubernetes 网页截图","alt":"Play with Kubernetes 网页截图","nro":62,"url":"../images/play-with-kubernetes.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Play with Kubernetes 网页截图","attributes":{},"skip":false,"key":"3.2.1"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.1","level":"3.3","list_caption":"Figure: Kubernetes dashboard","alt":"Kubernetes dashboard","nro":63,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/dashboard-animation.gif","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes dashboard","attributes":{},"skip":false,"key":"3.3.1"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.2","level":"3.3","list_caption":"Figure: Grafana","alt":"Grafana","nro":64,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/grafana-animation.gif","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Grafana","attributes":{},"skip":false,"key":"3.3.2"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.3","level":"3.3","list_caption":"Figure: Traefik dashboard","alt":"Traefik dashboard","nro":65,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/traefik-ingress.gif","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Traefik dashboard","attributes":{},"skip":false,"key":"3.3.3"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.4","level":"3.3","list_caption":"Figure: bookinfo示例","alt":"bookinfo示例","nro":66,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/bookinfo-demo.gif","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"bookinfo示例","attributes":{},"skip":false,"key":"3.3.4"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.5","level":"3.3","list_caption":"Figure: Kiali页面","alt":"Kiali页面","nro":67,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/kiali.gif","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kiali页面","attributes":{},"skip":false,"key":"3.3.5"},{"backlink":"cloud-native/cloud-native-local-quick-start.html#fig3.3.6","level":"3.3","list_caption":"Figure: Scope页面","alt":"Scope页面","nro":68,"url":"https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster/raw/master/images/weave-scope-animation.gif","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Scope页面","attributes":{},"skip":false,"key":"3.3.6"},{"backlink":"cloud-native/setup-kubernetes-with-rancher-and-aliyun.html#fig3.4.1","level":"3.4","list_caption":"Figure: Rancher 界面","alt":"Rancher 界面","nro":69,"url":"../images/rancher-web.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Rancher 界面","attributes":{},"skip":false,"key":"3.4.1"},{"backlink":"cloud-native/setup-kubernetes-with-rancher-and-aliyun.html#fig3.4.2","level":"3.4","list_caption":"Figure: 自定义节点信息","alt":"自定义节点信息","nro":70,"url":"../images/rancher-customize-node.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"自定义节点信息","attributes":{},"skip":false,"key":"3.4.2"},{"backlink":"cloud-native/setup-kubernetes-with-rancher-and-aliyun.html#fig3.4.3","level":"3.4","list_caption":"Figure: Rancher 集群监控页面","alt":"Rancher 集群监控页面","nro":71,"url":"../images/rancher-cluster.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Rancher 集群监控页面","attributes":{},"skip":false,"key":"3.4.3"},{"backlink":"concepts/index.html#fig4.1.1","level":"4.1","list_caption":"Figure: Borg 架构","alt":"Borg 架构","nro":72,"url":"../images/borg.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Borg 架构","attributes":{},"skip":false,"key":"4.1.1"},{"backlink":"concepts/index.html#fig4.1.2","level":"4.1","list_caption":"Figure: Kubernetes 架构","alt":"Kubernetes 架构","nro":73,"url":"../images/architecture.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 架构","attributes":{},"skip":false,"key":"4.1.2"},{"backlink":"concepts/index.html#fig4.1.3","level":"4.1","list_caption":"Figure: Kuberentes 架构（图片来自于网络）","alt":"Kuberentes 架构（图片来自于网络）","nro":74,"url":"../images/kubernetes-high-level-component-archtecture.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kuberentes 架构（图片来自于网络）","attributes":{},"skip":false,"key":"4.1.3"},{"backlink":"concepts/index.html#fig4.1.4","level":"4.1","list_caption":"Figure: kubernetes 整体架构示意图","alt":"kubernetes 整体架构示意图","nro":75,"url":"../images/kubernetes-whole-arch.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"kubernetes 整体架构示意图","attributes":{},"skip":false,"key":"4.1.4"},{"backlink":"concepts/index.html#fig4.1.5","level":"4.1","list_caption":"Figure: Kubernetes master 架构示意图","alt":"Kubernetes master 架构示意图","nro":76,"url":"../images/kubernetes-master-arch.png","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes master 架构示意图","attributes":{},"skip":false,"key":"4.1.5"},{"backlink":"concepts/index.html#fig4.1.6","level":"4.1","list_caption":"Figure: kubernetes node 架构示意图","alt":"kubernetes node 架构示意图","nro":77,"url":"../images/kubernetes-node-arch.png","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"kubernetes node 架构示意图","attributes":{},"skip":false,"key":"4.1.6"},{"backlink":"concepts/index.html#fig4.1.7","level":"4.1","list_caption":"Figure: Kubernetes 分层架构示意图","alt":"Kubernetes 分层架构示意图","nro":78,"url":"../images/kubernetes-layers-arch.png","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 分层架构示意图","attributes":{},"skip":false,"key":"4.1.7"},{"backlink":"concepts/concepts.html#fig4.1.1.1","level":"4.1.1","list_caption":"Figure: Kubernetes 分层架构示意图","alt":"Kubernetes 分层架构示意图","nro":79,"url":"../images/006tNc79ly1fzniqvmi51j31gq0s0q5u.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 分层架构示意图","attributes":{},"skip":false,"key":"4.1.1.1"},{"backlink":"concepts/cri.html#fig4.1.3.1.1","level":"4.1.3.1","list_caption":"Figure: CRI 架构 - 图片来自 kubernetes blog","alt":"CRI 架构 - 图片来自 kubernetes blog","nro":80,"url":"../images/cri-architecture.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CRI 架构 - 图片来自 kubernetes blog","attributes":{},"skip":false,"key":"4.1.3.1.1"},{"backlink":"concepts/pod-overview.html#fig4.2.1.1","level":"4.2.1","list_caption":"Figure: pod diagram","alt":"pod diagram","nro":81,"url":"../images/pod-overview.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"pod diagram","attributes":{},"skip":false,"key":"4.2.1.1"},{"backlink":"concepts/pod.html#fig4.2.2.1","level":"4.2.2","list_caption":"Figure: Pod Cheatsheet","alt":"Pod Cheatsheet","nro":82,"url":"../images/kubernetes-pod-cheatsheet.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Pod Cheatsheet","attributes":{},"skip":false,"key":"4.2.2.1"},{"backlink":"concepts/pod.html#fig4.2.2.2","level":"4.2.2","list_caption":"Figure: Pod示意图","alt":"Pod示意图","nro":83,"url":"../images/pod-overview.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Pod示意图","attributes":{},"skip":false,"key":"4.2.2.2"},{"backlink":"concepts/pause-container.html#fig4.2.4.1","level":"4.2.4","list_caption":"Figure: Pause容器","alt":"Pause容器","nro":84,"url":"../images/pause-container.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Pause容器","attributes":{},"skip":false,"key":"4.2.4.1"},{"backlink":"concepts/pod-lifecycle.html#fig4.2.6.1","level":"4.2.6","list_caption":"Figure: Pod的生命周期示意图（图片来自网络）","alt":"Pod的生命周期示意图（图片来自网络）","nro":85,"url":"../images/kubernetes-pod-life-cycle.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Pod的生命周期示意图（图片来自网络）","attributes":{},"skip":false,"key":"4.2.6.1"},{"backlink":"concepts/label.html#fig4.3.3.1","level":"4.3.3","list_caption":"Figure: label示意图","alt":"label示意图","nro":86,"url":"../images/labels.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"label示意图","attributes":{},"skip":false,"key":"4.3.3.1"},{"backlink":"concepts/deployment.html#fig4.4.1.1","level":"4.4.1","list_caption":"Figure: kubernetes deployment cheatsheet","alt":"kubernetes deployment cheatsheet","nro":87,"url":"../images/deployment-cheatsheet.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"kubernetes deployment cheatsheet","attributes":{},"skip":false,"key":"4.4.1.1"},{"backlink":"concepts/horizontal-pod-autoscaling.html#fig4.4.7.1","level":"4.4.7","list_caption":"Figure: horizontal-pod-autoscaler","alt":"horizontal-pod-autoscaler","nro":88,"url":"../images/horizontal-pod-autoscaler.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"horizontal-pod-autoscaler","attributes":{},"skip":false,"key":"4.4.7.1"},{"backlink":"concepts/service.html#fig4.5.1.1","level":"4.5.1","list_caption":"Figure: userspace代理模式下Service概览图","alt":"userspace代理模式下Service概览图","nro":89,"url":"../images/services-userspace-overview.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"userspace代理模式下Service概览图","attributes":{},"skip":false,"key":"4.5.1.1"},{"backlink":"concepts/service.html#fig4.5.1.2","level":"4.5.1","list_caption":"Figure: iptables代理模式下Service概览图","alt":"iptables代理模式下Service概览图","nro":90,"url":"../images/services-iptables-overview.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"iptables代理模式下Service概览图","attributes":{},"skip":false,"key":"4.5.1.2"},{"backlink":"concepts/service.html#fig4.5.1.3","level":"4.5.1","list_caption":"Figure: ipvs代理模式下Service概览图","alt":"ipvs代理模式下Service概览图","nro":91,"url":"../images/service-ipvs-overview.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"ipvs代理模式下Service概览图","attributes":{},"skip":false,"key":"4.5.1.3"},{"backlink":"concepts/gateway.html#fig4.5.4.1","level":"4.5.4","list_caption":"Figure: Kubernetes Gateway API 简介","alt":"Kubernetes Gateway API 简介","nro":92,"url":"../images/kubernetes-gateway-api-intro.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes Gateway API 简介","attributes":{},"skip":false,"key":"4.5.4.1"},{"backlink":"concepts/gateway.html#fig4.5.4.2","level":"4.5.4","list_caption":"Figure: 路由绑定示意图","alt":"路由绑定示意图","nro":93,"url":"../images/gateway-api-route-binding.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"路由绑定示意图","attributes":{},"skip":false,"key":"4.5.4.2"},{"backlink":"concepts/gateway.html#fig4.5.4.3","level":"4.5.4","list_caption":"Figure: Gateway API 流程图","alt":"Gateway API 流程图","nro":94,"url":"../images/gateway-api-request-flow.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Gateway API 流程图","attributes":{},"skip":false,"key":"4.5.4.3"},{"backlink":"concepts/spire.html#fig4.6.4.1.1","level":"4.6.4.1","list_caption":"Figure: 服务器和代理","alt":"服务器和代理","nro":95,"url":"../images/server-and-agent.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"服务器和代理","attributes":{},"skip":false,"key":"4.6.4.1.1"},{"backlink":"concepts/spire.html#fig4.6.4.1.2","level":"4.6.4.1","list_caption":"Figure: SPIRE 服务器","alt":"SPIRE 服务器","nro":96,"url":"../images/spire-server.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"SPIRE 服务器","attributes":{},"skip":false,"key":"4.6.4.1.2"},{"backlink":"concepts/spire.html#fig4.6.4.1.3","level":"4.6.4.1","list_caption":"Figure: SPIRE 代理","alt":"SPIRE 代理","nro":97,"url":"../images/spire-agent.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"SPIRE 代理","attributes":{},"skip":false,"key":"4.6.4.1.3"},{"backlink":"concepts/flannel.html#fig4.7.1.1","level":"4.7.1","list_caption":"Figure: flannel 网络架构（图片来自 openshift）","alt":"flannel 网络架构（图片来自 openshift）","nro":98,"url":"../images/flannel-networking.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"flannel 网络架构（图片来自 openshift）","attributes":{},"skip":false,"key":"4.7.1.1"},{"backlink":"concepts/calico.html#fig4.7.2.1","level":"4.7.2","list_caption":"Figure: Calico","alt":"Calico","nro":99,"url":"../images/006tNc79gy1fz65bt7ieej30c90bsgn2.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Calico","attributes":{},"skip":false,"key":"4.7.2.1"},{"backlink":"concepts/calico.html#fig4.7.2.2","level":"4.7.2","list_caption":"Figure: Calico 架构图","alt":"Calico 架构图","nro":100,"url":"../images/calico-architecture.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Calico 架构图","attributes":{},"skip":false,"key":"4.7.2.2"},{"backlink":"concepts/cilium.html#fig4.7.3.1","level":"4.7.3","list_caption":"Figure: Cilium","alt":"Cilium","nro":101,"url":"../images/006tNbRwly1fwqi98i51ij30sc0j80zn.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Cilium","attributes":{},"skip":false,"key":"4.7.3.1"},{"backlink":"concepts/cilium-concepts.html#fig4.7.3.1.1","level":"4.7.3.1","list_caption":"Figure: Cilium 组件(来自 Cilium 官网)","alt":"Cilium 组件(来自 Cilium 官网)","nro":102,"url":"../images/006tNbRwly1fwztvhg0gmj318z143tdv.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Cilium 组件(来自 Cilium 官网)","attributes":{},"skip":false,"key":"4.7.3.1.1"},{"backlink":"concepts/cilium-concepts.html#fig4.7.3.1.2","level":"4.7.3.1","list_caption":"Figure: Cilium 网络配置策略","alt":"Cilium 网络配置策略","nro":103,"url":"../images/006tNbRwly1fwzreaalj6j30dz0dy3z3.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Cilium 网络配置策略","attributes":{},"skip":false,"key":"4.7.3.1.2"},{"backlink":"concepts/service-catalog.html#fig4.9.5.1","level":"4.9.5","list_caption":"Figure: Service Catalog 架构","alt":"Service Catalog 架构","nro":104,"url":"../images/service-catalog-architecture.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Service Catalog 架构","attributes":{},"skip":false,"key":"4.9.5.1"},{"backlink":"concepts/service-catalog.html#fig4.9.5.2","level":"4.9.5","list_caption":"Figure: 列出服务","alt":"列出服务","nro":105,"url":"../images/service-catalog-list.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"列出服务","attributes":{},"skip":false,"key":"4.9.5.2"},{"backlink":"concepts/service-catalog.html#fig4.9.5.3","level":"4.9.5","list_caption":"Figure: 启用一个服务","alt":"启用一个服务","nro":106,"url":"../images/service-catalog-provision.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"启用一个服务","attributes":{},"skip":false,"key":"4.9.5.3"},{"backlink":"concepts/service-catalog.html#fig4.9.5.4","level":"4.9.5","list_caption":"Figure: Bind to a managed service","alt":"Bind to a managed service","nro":107,"url":"../images/service-catalog-bind.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Bind to a managed service","attributes":{},"skip":false,"key":"4.9.5.4"},{"backlink":"concepts/service-catalog.html#fig4.9.5.5","level":"4.9.5","list_caption":"Figure: 映射连接凭证","alt":"映射连接凭证","nro":108,"url":"../images/service-catalog-map.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"映射连接凭证","attributes":{},"skip":false,"key":"4.9.5.5"},{"backlink":"practice/federation.html#fig4.10.2.1","level":"4.10.2","list_caption":"Figure: Kubernetes 集群联邦架构图","alt":"Kubernetes 集群联邦架构图","nro":109,"url":"../images/federation-concepts.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 集群联邦架构图","attributes":{},"skip":false,"key":"4.10.2.1"},{"backlink":"practice/federation.html#fig4.10.2.2","level":"4.10.2","list_caption":"Figure: KubeFed 基础架构","alt":"KubeFed 基础架构","nro":110,"url":"../images/sync-controller.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"KubeFed 基础架构","attributes":{},"skip":false,"key":"4.10.2.2"},{"backlink":"practice/federation.html#fig4.10.2.3","level":"4.10.2","list_caption":"Figure: RSP","alt":"RSP","nro":111,"url":"../images/kubefed-rsp.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"RSP","attributes":{},"skip":false,"key":"4.10.2.3"},{"backlink":"practice/federation.html#fig4.10.2.4","level":"4.10.2","list_caption":"Figure: DNS","alt":"DNS","nro":112,"url":"../images/kubefed-service-dns.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"DNS","attributes":{},"skip":false,"key":"4.10.2.4"},{"backlink":"guide/using-kubectl.html#fig5.3.2.1","level":"5.3.2","list_caption":"Figure: kubectl cheatsheet","alt":"kubectl cheatsheet","nro":113,"url":"../images/kubernetes-kubectl-cheatsheet.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"kubectl cheatsheet","attributes":{},"skip":false,"key":"5.3.2.1"},{"backlink":"guide/using-kubectl.html#fig5.3.2.2","level":"5.3.2","list_caption":"Figure: 增加kubeclt命令的工具（图片来自网络）","alt":"增加kubeclt命令的工具（图片来自网络）","nro":114,"url":"../images/tools-to-supercharge-kubectl.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"增加kubeclt命令的工具（图片来自网络）","attributes":{},"skip":false,"key":"5.3.2.2"},{"backlink":"guide/using-kubectl.html#fig5.3.2.3","level":"5.3.2","list_caption":"Figure: 增强的kubectl命令","alt":"增强的kubectl命令","nro":115,"url":"../images/supercharged-kubectl.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"增强的kubectl命令","attributes":{},"skip":false,"key":"5.3.2.3"},{"backlink":"guide/using-kubectl.html#fig5.3.2.4","level":"5.3.2","list_caption":"Figure: kube-shell页面","alt":"kube-shell页面","nro":116,"url":"../images/kube-shell.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"kube-shell页面","attributes":{},"skip":false,"key":"5.3.2.4"},{"backlink":"guide/ip-masq-agent.html#fig5.4.5.1","level":"5.4.5","list_caption":"Figure: IP伪装代理示意图","alt":"IP伪装代理示意图","nro":117,"url":"../images/ip-masq.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"IP伪装代理示意图","attributes":{},"skip":false,"key":"5.4.5.1"},{"backlink":"guide/auth-with-kubeconfig-or-token.html#fig5.4.6.1","level":"5.4.6","list_caption":"Figure: kubeconfig文件","alt":"kubeconfig文件","nro":118,"url":"../images/brand-kubeconfig-yaml.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"kubeconfig文件","attributes":{},"skip":false,"key":"5.4.6.1"},{"backlink":"guide/authentication.html#fig5.4.7.1","level":"5.4.7","list_caption":"Figure: Kubernetes OpenID Connect Flow","alt":"Kubernetes OpenID Connect Flow","nro":119,"url":"../images/kubernetes-oidc-login.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes OpenID Connect Flow","attributes":{},"skip":false,"key":"5.4.7.1"},{"backlink":"guide/kubernetes-desktop-client.html#fig5.5.6.1","level":"5.5.6","list_caption":"Figure: Lens Kubernetes IDE 界面","alt":"Lens Kubernetes IDE 界面","nro":120,"url":"../images/lens.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Lens Kubernetes IDE 界面","attributes":{},"skip":false,"key":"5.5.6.1"},{"backlink":"guide/kubernator-kubernetes-ui.html#fig5.5.7.1","level":"5.5.7","list_caption":"Figure: Kubernator catalog 页面","alt":"Kubernator catalog 页面","nro":121,"url":"../images/kubernator-catalog.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernator catalog 页面","attributes":{},"skip":false,"key":"5.5.7.1"},{"backlink":"guide/kubernator-kubernetes-ui.html#fig5.5.7.2","level":"5.5.7","list_caption":"Figure: Kubernator rbac 页面","alt":"Kubernator rbac 页面","nro":122,"url":"../images/kubernator-rbac.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernator rbac 页面","attributes":{},"skip":false,"key":"5.5.7.2"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.1","level":"5.6.1","list_caption":"Figure: 流程图","alt":"流程图","nro":123,"url":"../images/how-to-use-kubernetes-with-istio.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"流程图","attributes":{},"skip":false,"key":"5.6.1.1"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.2","level":"5.6.1","list_caption":"Figure: API","alt":"API","nro":124,"url":"../images/k8s-app-monitor-test-api-doc.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"API","attributes":{},"skip":false,"key":"5.6.1.2"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.3","level":"5.6.1","list_caption":"Figure: wercker构建页面","alt":"wercker构建页面","nro":125,"url":"../images/k8s-app-monitor-agent-wercker.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"wercker构建页面","attributes":{},"skip":false,"key":"5.6.1.3"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.4","level":"5.6.1","list_caption":"Figure: 图表","alt":"图表","nro":126,"url":"../images/k8s-app-monitor-agent.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"图表","attributes":{},"skip":false,"key":"5.6.1.4"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.5","level":"5.6.1","list_caption":"Figure: Grafana页面","alt":"Grafana页面","nro":127,"url":"../images/k8s-app-monitor-istio-grafana.png","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Grafana页面","attributes":{},"skip":false,"key":"5.6.1.5"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.6","level":"5.6.1","list_caption":"Figure: servicegraph 页面","alt":"servicegraph 页面","nro":128,"url":"../images/k8s-app-monitor-istio-servicegraph-dotviz.png","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"servicegraph 页面","attributes":{},"skip":false,"key":"5.6.1.6"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig5.6.1.7","level":"5.6.1","list_caption":"Figure: Zipkin页面","alt":"Zipkin页面","nro":129,"url":"../images/k8s-app-monitor-istio-zipkin.png","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Zipkin页面","attributes":{},"skip":false,"key":"5.6.1.7"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig5.6.2.1","level":"5.6.2","list_caption":"Figure: 将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","alt":"将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","nro":130,"url":"../images/migrating-monolith-to-kubernetes.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","attributes":{},"skip":false,"key":"5.6.2.1"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig5.6.2.2","level":"5.6.2","list_caption":"Figure: spark on yarn with kubernetes","alt":"spark on yarn with kubernetes","nro":131,"url":"../images/spark-on-yarn-with-kubernetes.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"spark on yarn with kubernetes","attributes":{},"skip":false,"key":"5.6.2.2"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig5.6.2.3","level":"5.6.2","list_caption":"Figure: Terms","alt":"Terms","nro":132,"url":"../images/terms-in-kubernetes-app-deployment.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Terms","attributes":{},"skip":false,"key":"5.6.2.3"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig5.6.2.4","level":"5.6.2","list_caption":"Figure: 分解步骤解析","alt":"分解步骤解析","nro":133,"url":"../images/migrating-hadoop-yarn-to-kubernetes.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"分解步骤解析","attributes":{},"skip":false,"key":"5.6.2.4"},{"backlink":"practice/node-installation.html#fig6.2.7.1","level":"6.2.7","list_caption":"Figure: nginx欢迎页面","alt":"nginx欢迎页面","nro":134,"url":"../images/kubernetes-installation-test-nginx.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"nginx欢迎页面","attributes":{},"skip":false,"key":"6.2.7.1"},{"backlink":"practice/dashboard-addon-installation.html#fig6.2.9.1","level":"6.2.9","list_caption":"Figure: kubernetes dashboard","alt":"kubernetes dashboard","nro":135,"url":"../images/kubernetes-dashboard-raw.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"kubernetes dashboard","attributes":{},"skip":false,"key":"6.2.9.1"},{"backlink":"practice/dashboard-addon-installation.html#fig6.2.9.2","level":"6.2.9","list_caption":"Figure: V1.6.3版本的dashboard界面","alt":"V1.6.3版本的dashboard界面","nro":136,"url":"../images/dashboard-v163.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"V1.6.3版本的dashboard界面","attributes":{},"skip":false,"key":"6.2.9.2"},{"backlink":"practice/dashboard-addon-installation.html#fig6.2.9.3","level":"6.2.9","list_caption":"Figure: pod无法正常启动","alt":"pod无法正常启动","nro":137,"url":"../images/dashboard-addon-installation001.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"pod无法正常启动","attributes":{},"skip":false,"key":"6.2.9.3"},{"backlink":"practice/heapster-addon-installation.html#fig6.2.10.1","level":"6.2.10","list_caption":"Figure: dashboard-heapster","alt":"dashboard-heapster","nro":138,"url":"../images/kubernetes-dashboard-with-heapster.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"dashboard-heapster","attributes":{},"skip":false,"key":"6.2.10.1"},{"backlink":"practice/heapster-addon-installation.html#fig6.2.10.2","level":"6.2.10","list_caption":"Figure: grafana","alt":"grafana","nro":139,"url":"../images/kubernetes-heapster-grafana.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"grafana","attributes":{},"skip":false,"key":"6.2.10.2"},{"backlink":"practice/heapster-addon-installation.html#fig6.2.10.3","level":"6.2.10","list_caption":"Figure: Influxdb 页面","alt":"Influxdb 页面","nro":140,"url":"../images/kubernetes-influxdb-heapster.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Influxdb 页面","attributes":{},"skip":false,"key":"6.2.10.3"},{"backlink":"practice/heapster-addon-installation.html#fig6.2.10.4","level":"6.2.10","list_caption":"Figure: 修改grafana模板","alt":"修改grafana模板","nro":141,"url":"../images/grafana-dashboard-setting.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"修改grafana模板","attributes":{},"skip":false,"key":"6.2.10.4"},{"backlink":"practice/efk-addon-installation.html#fig6.2.11.1","level":"6.2.11","list_caption":"Figure: es-setting","alt":"es-setting","nro":142,"url":"../images/es-setting.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"es-setting","attributes":{},"skip":false,"key":"6.2.11.1"},{"backlink":"practice/efk-addon-installation.html#fig6.2.11.2","level":"6.2.11","list_caption":"Figure: es-home","alt":"es-home","nro":143,"url":"../images/kubernetes-efk-kibana.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"es-home","attributes":{},"skip":false,"key":"6.2.11.2"},{"backlink":"practice/traefik-ingress-installation.html#fig6.4.1.1","level":"6.4.1","list_caption":"Figure: Terafik dashboard","alt":"Terafik dashboard","nro":144,"url":"../images/traefik-dashboard.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Terafik dashboard","attributes":{},"skip":false,"key":"6.4.1.1"},{"backlink":"practice/traefik-ingress-installation.html#fig6.4.1.2","level":"6.4.1","list_caption":"Figure: Nginx 页面","alt":"Nginx 页面","nro":145,"url":"../images/traefik-nginx.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Nginx 页面","attributes":{},"skip":false,"key":"6.4.1.2"},{"backlink":"practice/traefik-ingress-installation.html#fig6.4.1.3","level":"6.4.1","list_caption":"Figure: Guestbook 页面","alt":"Guestbook 页面","nro":146,"url":"../images/traefik-guestbook.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Guestbook 页面","attributes":{},"skip":false,"key":"6.4.1.3"},{"backlink":"practice/distributed-load-test.html#fig6.4.2.1","level":"6.4.2","list_caption":"Figure: 使用 dashboard 来扩容","alt":"使用 dashboard 来扩容","nro":147,"url":"../images/dashbaord-scale.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"使用 dashboard 来扩容","attributes":{},"skip":false,"key":"6.4.2.1"},{"backlink":"practice/distributed-load-test.html#fig6.4.2.2","level":"6.4.2","list_caption":"Figure: Traefik的UI","alt":"Traefik的UI","nro":148,"url":"../images/traefik-dashboard-locust.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Traefik的UI","attributes":{},"skip":false,"key":"6.4.2.2"},{"backlink":"practice/distributed-load-test.html#fig6.4.2.3","level":"6.4.2","list_caption":"Figure: Locust启动界面","alt":"Locust启动界面","nro":149,"url":"../images/locust-start-swarming.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Locust启动界面","attributes":{},"skip":false,"key":"6.4.2.3"},{"backlink":"practice/distributed-load-test.html#fig6.4.2.4","level":"6.4.2","list_caption":"Figure: Dashboard查看页面","alt":"Dashboard查看页面","nro":150,"url":"../images/sample-webapp-rc.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Dashboard查看页面","attributes":{},"skip":false,"key":"6.4.2.4"},{"backlink":"practice/distributed-load-test.html#fig6.4.2.5","level":"6.4.2","list_caption":"Figure: Locust测试结果页面","alt":"Locust测试结果页面","nro":151,"url":"../images/locust-dashboard.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Locust测试结果页面","attributes":{},"skip":false,"key":"6.4.2.5"},{"backlink":"practice/network-and-cluster-perfermance-test.html#fig6.4.3.1","level":"6.4.3","list_caption":"Figure: Kubernetes dashboard","alt":"Kubernetes dashboard","nro":152,"url":"../images/kubenetes-e2e-test.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes dashboard","attributes":{},"skip":false,"key":"6.4.3.1"},{"backlink":"practice/network-and-cluster-perfermance-test.html#fig6.4.3.2","level":"6.4.3","list_caption":"Figure: locust测试页面","alt":"locust测试页面","nro":153,"url":"../images/kubernetes-locust-test.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"locust测试页面","attributes":{},"skip":false,"key":"6.4.3.2"},{"backlink":"practice/edge-node-configuration.html#fig6.4.4.1","level":"6.4.4","list_caption":"Figure: 边缘节点架构","alt":"边缘节点架构","nro":154,"url":"../images/kubernetes-edge-node-architecture.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"边缘节点架构","attributes":{},"skip":false,"key":"6.4.4.1"},{"backlink":"practice/edge-node-configuration.html#fig6.4.4.2","level":"6.4.4","list_caption":"Figure: 使用域名来访问Kubernetes中的服务","alt":"使用域名来访问Kubernetes中的服务","nro":155,"url":"../images/accessing-kubernetes-services-with-dns-name.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"使用域名来访问Kubernetes中的服务","attributes":{},"skip":false,"key":"6.4.4.2"},{"backlink":"practice/configuring-dns.html#fig6.4.6.1.1","level":"6.4.6.1","list_caption":"Figure: DNS lookup flow","alt":"DNS lookup flow","nro":156,"url":"https://d33wubrfki0l68.cloudfront.net/340889cb80e81dcd19a16bc34697a7907e2b229a/24ad0/docs/tasks/administer-cluster/dns-custom-nameservers/dns.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"DNS lookup flow","attributes":{},"skip":false,"key":"6.4.6.1.1"},{"backlink":"practice/master-ha.html#fig6.5.1.1","level":"6.5.1","list_caption":"Figure: Master HA架构图","alt":"Master HA架构图","nro":157,"url":"../images/master-ha.JPG","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Master HA架构图","attributes":{},"skip":false,"key":"6.5.1.1"},{"backlink":"practice/app-log-collection.html#fig6.5.3.1","level":"6.5.3","list_caption":"Figure: filebeat日志收集架构图","alt":"filebeat日志收集架构图","nro":158,"url":"../images/filebeat-log-collector.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"filebeat日志收集架构图","attributes":{},"skip":false,"key":"6.5.3.1"},{"backlink":"practice/app-log-collection.html#fig6.5.3.2","level":"6.5.3","list_caption":"Figure: Kibana页面","alt":"Kibana页面","nro":159,"url":"../images/filebeat-docker-test.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kibana页面","attributes":{},"skip":false,"key":"6.5.3.2"},{"backlink":"practice/app-log-collection.html#fig6.5.3.3","level":"6.5.3","list_caption":"Figure: filebeat收集的日志详细信息","alt":"filebeat收集的日志详细信息","nro":160,"url":"../images/kubernetes-filebeat-detail.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"filebeat收集的日志详细信息","attributes":{},"skip":false,"key":"6.5.3.3"},{"backlink":"practice/monitor.html#fig6.5.5.1","level":"6.5.5","list_caption":"Figure: Kubernetes集群中的监控","alt":"Kubernetes集群中的监控","nro":161,"url":"../images/monitoring-in-kubernetes.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes集群中的监控","attributes":{},"skip":false,"key":"6.5.5.1"},{"backlink":"practice/monitor.html#fig6.5.5.2","level":"6.5.5","list_caption":"Figure: kubernetes的容器命名规则示意图","alt":"kubernetes的容器命名规则示意图","nro":162,"url":"../images/kubernetes-container-naming-rule.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"kubernetes的容器命名规则示意图","attributes":{},"skip":false,"key":"6.5.5.2"},{"backlink":"practice/monitor.html#fig6.5.5.3","level":"6.5.5","list_caption":"Figure: Heapster架构图（改进版）","alt":"Heapster架构图（改进版）","nro":163,"url":"../images/kubernetes-heapster-monitoring.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Heapster架构图（改进版）","attributes":{},"skip":false,"key":"6.5.5.3"},{"backlink":"practice/monitor.html#fig6.5.5.4","level":"6.5.5","list_caption":"Figure: 应用监控架构图","alt":"应用监控架构图","nro":164,"url":"../images/kubernetes-app-monitoring.png","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"应用监控架构图","attributes":{},"skip":false,"key":"6.5.5.4"},{"backlink":"practice/monitor.html#fig6.5.5.5","level":"6.5.5","list_caption":"Figure: 应用拓扑图","alt":"应用拓扑图","nro":165,"url":"../images/weave-scope-service-topology.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"应用拓扑图","attributes":{},"skip":false,"key":"6.5.5.5"},{"backlink":"practice/data-persistence-problem.html#fig6.5.6.1","level":"6.5.6","list_caption":"Figure: 日志持久化收集解决方案示意图","alt":"日志持久化收集解决方案示意图","nro":166,"url":"../images/log-persistence-logstash.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"日志持久化收集解决方案示意图","attributes":{},"skip":false,"key":"6.5.6.1"},{"backlink":"practice/storage-for-containers-using-glusterfs-with-openshift.html#fig6.6.1.3.1","level":"6.6.1.3","list_caption":"Figure: 创建存储","alt":"创建存储","nro":167,"url":"../images/create-gluster-storage.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"创建存储","attributes":{},"skip":false,"key":"6.6.1.3.1"},{"backlink":"practice/storage-for-containers-using-glusterfs-with-openshift.html#fig6.6.1.3.2","level":"6.6.1.3","list_caption":"Figure: 容器存储","alt":"容器存储","nro":168,"url":"../images/container-storage.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"容器存储","attributes":{},"skip":false,"key":"6.6.1.3.2"},{"backlink":"practice/openebs.html#fig6.6.4.1","level":"6.6.4","list_caption":"Figure: OpenEBS 集群数据平面（图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","alt":"OpenEBS 集群数据平面（图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","nro":169,"url":"../images/OpenEBS-Data-Plane.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OpenEBS 集群数据平面（图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","attributes":{},"skip":false,"key":"6.6.4.1"},{"backlink":"practice/openebs.html#fig6.6.4.2","level":"6.6.4","list_caption":"Figure: OpenEBS 集群的控制平面 (图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","alt":"OpenEBS 集群的控制平面 (图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","nro":170,"url":"../images/OpenEBS-Control-Plane.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OpenEBS 集群的控制平面 (图片来自 https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","attributes":{},"skip":false,"key":"6.6.4.2"},{"backlink":"practice/using-openebs-for-persistent-storage.html#fig6.6.4.1.1","level":"6.6.4.1","list_caption":"Figure: Kubernetes iSCSI架构","alt":"Kubernetes iSCSI架构","nro":171,"url":"../images/iscsi-on-kubernetes.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes iSCSI架构","attributes":{},"skip":false,"key":"6.6.4.1.1"},{"backlink":"practice/using-heapster-to-get-object-metrics.html#fig6.7.1.1.1","level":"6.7.1.1","list_caption":"Figure: Heapster架构图","alt":"Heapster架构图","nro":172,"url":"../images/heapster-architecture.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Heapster架构图","attributes":{},"skip":false,"key":"6.7.1.1.1"},{"backlink":"practice/prometheus.html#fig6.7.2.1","level":"6.7.2","list_caption":"Figure: Prometheus 架构图","alt":"Prometheus 架构图","nro":173,"url":"../images/006tNbRwly1fwcgsn11fej311j0mjadw.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Prometheus 架构图","attributes":{},"skip":false,"key":"6.7.2.1"},{"backlink":"practice/using-prometheus-to-monitor-kuberentes-cluster.html#fig6.7.2.1.1","level":"6.7.2.1","list_caption":"Figure: Grafana页面","alt":"Grafana页面","nro":174,"url":"../images/kubernetes-prometheus-monitoring.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Grafana页面","attributes":{},"skip":false,"key":"6.7.2.1.1"},{"backlink":"practice/promql.html#fig6.7.2.2.1","level":"6.7.2.2","list_caption":"Figure: Prometheus 的查询页面","alt":"Prometheus 的查询页面","nro":175,"url":"../images/006tNbRwly1fwcl7v28rhj30xl0onadv.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Prometheus 的查询页面","attributes":{},"skip":false,"key":"6.7.2.2.1"},{"backlink":"practice/opentracing.html#fig6.8.1.1","level":"6.8.1","list_caption":"Figure: Jaeger UI","alt":"Jaeger UI","nro":176,"url":"../images/006tNbRwly1fwjg48fh7xj31kw0wedrg.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Jaeger UI","attributes":{},"skip":false,"key":"6.8.1.1"},{"backlink":"practice/opentracing.html#fig6.8.1.2","level":"6.8.1","list_caption":"Figure: Chrome Inspector","alt":"Chrome Inspector","nro":177,"url":"../images/006tNbRwly1fwjkfbvfluj30y70hf0y9.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Chrome Inspector","attributes":{},"skip":false,"key":"6.8.1.2"},{"backlink":"practice/helm.html#fig6.9.1.1","level":"6.9.1","list_caption":"Figure: Helm 架构图（来自 IBM Developer Blog）","alt":"Helm 架构图（来自 IBM Developer Blog）","nro":178,"url":"../images/helm-chart.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Helm 架构图（来自 IBM Developer Blog）","attributes":{},"skip":false,"key":"6.9.1.1"},{"backlink":"practice/create-private-charts-repo.html#fig6.9.2.1","level":"6.9.2","list_caption":"Figure: Helm monocular界面","alt":"Helm monocular界面","nro":179,"url":"../images/helm-monocular-jimmysong.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Helm monocular界面","attributes":{},"skip":false,"key":"6.9.2.1"},{"backlink":"practice/ci-cd.html#fig6.10.1","level":"6.10","list_caption":"Figure: Kubernetes 改变了应用的基础架构","alt":"Kubernetes 改变了应用的基础架构","nro":180,"url":"../images/00704eQkgy1fsayashxz3j31c00w6aed.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 改变了应用的基础架构","attributes":{},"skip":false,"key":"6.10.1"},{"backlink":"practice/ci-cd.html#fig6.10.2","level":"6.10","list_caption":"Figure: Kubernetes 中的 CI/CD","alt":"Kubernetes 中的 CI/CD","nro":181,"url":"../images/00704eQkgy1fsayfzk3ezj31bu0tkdky.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 中的 CI/CD","attributes":{},"skip":false,"key":"6.10.2"},{"backlink":"practice/ci-cd.html#fig6.10.3","level":"6.10","list_caption":"Figure: Kubernetes 中的 GitOps 流程示意图","alt":"Kubernetes 中的 GitOps 流程示意图","nro":182,"url":"../images/gitops.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 中的 GitOps 流程示意图","attributes":{},"skip":false,"key":"6.10.3"},{"backlink":"practice/ci-cd.html#fig6.10.4","level":"6.10","list_caption":"Figure: 云原生工作负载","alt":"云原生工作负载","nro":183,"url":"../images/00704eQkgy1fsayrk6vppj31bu0w0gsd.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生工作负载","attributes":{},"skip":false,"key":"6.10.4"},{"backlink":"practice/ci-cd.html#fig6.10.5","level":"6.10","list_caption":"Figure: 云原生工作负载映射到 Kuberentes 原语","alt":"云原生工作负载映射到 Kuberentes 原语","nro":184,"url":"../images/00704eQkgy1fsaytbabxgj31c00w2n4r.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生工作负载映射到 Kuberentes 原语","attributes":{},"skip":false,"key":"6.10.5"},{"backlink":"practice/jenkins-ci-cd.html#fig6.10.1.1","level":"6.10.1","list_caption":"Figure: 基于 Jenkins 的持续集成与发布","alt":"基于 Jenkins 的持续集成与发布","nro":185,"url":"../images/kubernetes-jenkins-ci-cd.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"基于 Jenkins 的持续集成与发布","attributes":{},"skip":false,"key":"6.10.1.1"},{"backlink":"practice/drone-ci-cd.html#fig6.10.2.1","level":"6.10.2","list_caption":"Figure: OAuth 注册","alt":"OAuth 注册","nro":186,"url":"../images/github-oauth-register.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OAuth 注册","attributes":{},"skip":false,"key":"6.10.2.1"},{"backlink":"practice/drone-ci-cd.html#fig6.10.2.2","level":"6.10.2","list_caption":"Figure: OAuth key","alt":"OAuth key","nro":187,"url":"../images/github-oauth-drone-key.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OAuth key","attributes":{},"skip":false,"key":"6.10.2.2"},{"backlink":"practice/drone-ci-cd.html#fig6.10.2.3","level":"6.10.2","list_caption":"Figure: Drone 登陆界面","alt":"Drone 登陆界面","nro":188,"url":"../images/drone-login-github.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Drone 登陆界面","attributes":{},"skip":false,"key":"6.10.2.3"},{"backlink":"practice/drone-ci-cd.html#fig6.10.2.4","level":"6.10.2","list_caption":"Figure: Github 启用 repo 设置","alt":"Github 启用 repo 设置","nro":189,"url":"../images/drone-github-active.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Github 启用 repo 设置","attributes":{},"skip":false,"key":"6.10.2.4"},{"backlink":"practice/drone-ci-cd.html#fig6.10.2.5","level":"6.10.2","list_caption":"Figure: Github 单个 repo 设置","alt":"Github 单个 repo 设置","nro":190,"url":"../images/drone-github-repo-setting.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Github 单个 repo 设置","attributes":{},"skip":false,"key":"6.10.2.5"},{"backlink":"practice/manually-upgrade.html#fig6.11.1.1","level":"6.11.1","list_caption":"Figure: Kubernetes零宕机时间升级建议","alt":"Kubernetes零宕机时间升级建议","nro":191,"url":"../images/zero-downtime-kubernetes-upgrade-tips.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes零宕机时间升级建议","attributes":{},"skip":false,"key":"6.11.1.1"},{"backlink":"practice/manually-upgrade.html#fig6.11.1.2","level":"6.11.1","list_caption":"Figure: Kuberentes API对象的版本演进","alt":"Kuberentes API对象的版本演进","nro":192,"url":"../images/kubernetes-apversions-changes.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kuberentes API对象的版本演进","attributes":{},"skip":false,"key":"6.11.1.2"},{"backlink":"practice/dashboard-upgrade.html#fig6.11.2.1","level":"6.11.2","list_caption":"Figure: 登陆界面","alt":"登陆界面","nro":193,"url":"../images/kubernetes-dashboard-1.7.1-login.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"登陆界面","attributes":{},"skip":false,"key":"6.11.2.1"},{"backlink":"practice/dashboard-upgrade.html#fig6.11.2.2","level":"6.11.2","list_caption":"Figure: Dashboard首页","alt":"Dashboard首页","nro":194,"url":"../images/kubernetes-dashboard-1.7.1-default-page.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Dashboard首页","attributes":{},"skip":false,"key":"6.11.2.2"},{"backlink":"practice/dashboard-upgrade.html#fig6.11.2.3","level":"6.11.2","list_caption":"Figure: Dashboard用户空间页面","alt":"Dashboard用户空间页面","nro":195,"url":"../images/kubernetes-dashboard-1.7.1-brand.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Dashboard用户空间页面","attributes":{},"skip":false,"key":"6.11.2.3"},{"backlink":"practice/dashboard-upgrade.html#fig6.11.2.4","level":"6.11.2","list_caption":"Figure: kubeconfig文件","alt":"kubeconfig文件","nro":196,"url":"../images/brand-kubeconfig-yaml.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"kubeconfig文件","attributes":{},"skip":false,"key":"6.11.2.4"},{"backlink":"practice/open-policy-agent.html#fig6.13.1.1","level":"6.13.1","list_caption":"Figure: OPA 原理图","alt":"OPA 原理图","nro":197,"url":"../images/opa-arch.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OPA 原理图","attributes":{},"skip":false,"key":"6.13.1.1"},{"backlink":"usecases/service-mesh.html#fig7.1.1","level":"7.1","list_caption":"Figure: 下一代异构微服务架构","alt":"下一代异构微服务架构","nro":198,"url":"../images/polyglot-microservices-serivce-mesh.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"下一代异构微服务架构","attributes":{},"skip":false,"key":"7.1.1"},{"backlink":"usecases/service-mesh.html#fig7.1.2","level":"7.1","list_caption":"Figure: Service Mesh 架构图","alt":"Service Mesh 架构图","nro":199,"url":"../images/serivce-mesh-control-plane.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Service Mesh 架构图","attributes":{},"skip":false,"key":"7.1.2"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.1","level":"7.2.1","list_caption":"Figure: 服务网格模型对比","alt":"服务网格模型对比","nro":200,"url":"../images/0069RVTdly1fuafvbnuc7j310a0oqdm9.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"服务网格模型对比","attributes":{},"skip":false,"key":"7.2.1.1"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.2","level":"7.2.1","list_caption":"Figure: 网状网络拓扑","alt":"网状网络拓扑","nro":201,"url":"../images/0069RVTdly1fuaie8jan8j310a0kitem.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"网状网络拓扑","attributes":{},"skip":false,"key":"7.2.1.2"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.3","level":"7.2.1","list_caption":"Figure: 服务网格架构图","alt":"服务网格架构图","nro":202,"url":"../images/0069RVTdly1fuail4d24jj31080rkgr7.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"服务网格架构图","attributes":{},"skip":false,"key":"7.2.1.3"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.4","level":"7.2.1","list_caption":"Figure: Istio Mixer","alt":"Istio Mixer","nro":203,"url":"../images/0069RVTdly1fuam4ln45jj30yu0o6wkc.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Istio Mixer","attributes":{},"skip":false,"key":"7.2.1.4"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.5","level":"7.2.1","list_caption":"Figure: Istio架构图","alt":"Istio架构图","nro":204,"url":"../images/0069RVTdly1fuamvq97cuj30yu0wg7cr.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Istio架构图","attributes":{},"skip":false,"key":"7.2.1.5"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.6","level":"7.2.1","list_caption":"Figure: OSI模型","alt":"OSI模型","nro":205,"url":"../images/0069RVTdly1fuanez4qbtj30v4183n7p.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OSI模型","attributes":{},"skip":false,"key":"7.2.1.6"},{"backlink":"usecases/service-mesh-fundamental.html#fig7.2.1.7","level":"7.2.1","list_caption":"Figure: 在L5解耦","alt":"在L5解耦","nro":206,"url":"../images/006tNbRwly1fubfiiryirj30w20ayjui.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"在L5解耦","attributes":{},"skip":false,"key":"7.2.1.7"},{"backlink":"usecases/comparing-service-mesh-technologies.html#fig7.2.2.1","level":"7.2.2","list_caption":"Figure: 客户端库","alt":"客户端库","nro":207,"url":"../images/006tNbRwly1fubnx0q9bpj30vq0pq465.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"客户端库","attributes":{},"skip":false,"key":"7.2.2.1"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.1","level":"7.2.4","list_caption":"Figure: Service Mesh架构图","alt":"Service Mesh架构图","nro":208,"url":"../images/006tNbRwly1fubs6ts3sgj30vo0osdnj.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Service Mesh架构图","attributes":{},"skip":false,"key":"7.2.4.1"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.2","level":"7.2.4","list_caption":"Figure: Ingress或边缘代理架构图","alt":"Ingress或边缘代理架构图","nro":209,"url":"../images/006tNbRwly1fubsk4v16hj30vo0bq75z.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Ingress或边缘代理架构图","attributes":{},"skip":false,"key":"7.2.4.2"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.3","level":"7.2.4","list_caption":"Figure: 路由器网格架构图","alt":"路由器网格架构图","nro":210,"url":"../images/006tNbRwly1fubsxrph3dj30vq0duq53.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"路由器网格架构图","attributes":{},"skip":false,"key":"7.2.4.3"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.4","level":"7.2.4","list_caption":"Figure: Proxy per Node架构图","alt":"Proxy per Node架构图","nro":211,"url":"../images/006tNbRwly1fubt5a97h7j30vq0bcq5p.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Proxy per Node架构图","attributes":{},"skip":false,"key":"7.2.4.4"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.5","level":"7.2.4","list_caption":"Figure: Sidecar代理/Fabric模型架构图","alt":"Sidecar代理/Fabric模型架构图","nro":212,"url":"../images/006tNbRwly1fubvi0dnhlj30vo0ekwhx.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Sidecar代理/Fabric模型架构图","attributes":{},"skip":false,"key":"7.2.4.5"},{"backlink":"usecases/service-mesh-adoption-and-evolution.html#fig7.2.4.6","level":"7.2.4","list_caption":"Figure: Sidecar代理/控制平面架构图","alt":"Sidecar代理/控制平面架构图","nro":213,"url":"../images/006tNbRwly1fubvr83wvgj30vq0mmdip.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Sidecar代理/控制平面架构图","attributes":{},"skip":false,"key":"7.2.4.6"},{"backlink":"usecases/service-mesh-customization-and-integration.html#fig7.2.5.1","level":"7.2.5","list_caption":"Figure: nginMesh架构图","alt":"nginMesh架构图","nro":214,"url":"../images/006tNbRwly1fucp8yralaj30vu0sijx8.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"nginMesh架构图","attributes":{},"skip":false,"key":"7.2.5.1"},{"backlink":"usecases/service-mesh-customization-and-integration.html#fig7.2.5.2","level":"7.2.5","list_caption":"Figure: SOFAMesh","alt":"SOFAMesh","nro":215,"url":"../images/mosn-with-service-mesh.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"SOFAMesh","attributes":{},"skip":false,"key":"7.2.5.2"},{"backlink":"usecases/istio.html#fig7.3.1","level":"7.3","list_caption":"Figure: Istio的mindmap","alt":"Istio的mindmap","nro":216,"url":"../images/istio-mindmap.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Istio的mindmap","attributes":{},"skip":false,"key":"7.3.1"},{"backlink":"usecases/istio.html#fig7.3.2","level":"7.3","list_caption":"Figure: Istio架构图","alt":"Istio架构图","nro":217,"url":"../images/istio-mesh-arch.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Istio架构图","attributes":{},"skip":false,"key":"7.3.2"},{"backlink":"usecases/sidecar-pattern.html#fig7.3.2.1","level":"7.3.2","list_caption":"Figure: Sidecar 模式示意图","alt":"Sidecar 模式示意图","nro":218,"url":"../images/sidecar-pattern.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Sidecar 模式示意图","attributes":{},"skip":false,"key":"7.3.2.1"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.4.1","level":"7.3.4","list_caption":"Figure: iptables 调用链","alt":"iptables 调用链","nro":219,"url":"../images/iptables.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"iptables 调用链","attributes":{},"skip":false,"key":"7.3.4.1"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.4.2","level":"7.3.4","list_caption":"Figure: IPtables 调用链顺序","alt":"IPtables 调用链顺序","nro":220,"url":"../images/iptables-chains.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"IPtables 调用链顺序","attributes":{},"skip":false,"key":"7.3.4.2"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.4.3","level":"7.3.4","list_caption":"Figure: Sidecar 流量劫持示意图","alt":"Sidecar 流量劫持示意图","nro":221,"url":"../images/envoy-sidecar-traffic-interception-zh-20220424.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Sidecar 流量劫持示意图","attributes":{},"skip":false,"key":"7.3.4.3"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.4.4","level":"7.3.4","list_caption":"Figure: ISTIO_ROUTE iptables 规则流程图","alt":"ISTIO_ROUTE iptables 规则流程图","nro":222,"url":"../images/istio-route-iptables.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"ISTIO_ROUTE iptables 规则流程图","attributes":{},"skip":false,"key":"7.3.4.4"},{"backlink":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html#fig7.3.4.5","level":"7.3.4","list_caption":"Figure: hook-connect 原理示意图","alt":"hook-connect 原理示意图","nro":223,"url":"../images/hook-connect.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"hook-connect 原理示意图","attributes":{},"skip":false,"key":"7.3.4.5"},{"backlink":"usecases/istio-traffic-routing.html#fig7.3.5.1","level":"7.3.5","list_caption":"Figure: Bookinfo 示例","alt":"Bookinfo 示例","nro":224,"url":"../images/bookinfo-sample-arch.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Bookinfo 示例","attributes":{},"skip":false,"key":"7.3.5.1"},{"backlink":"usecases/how-to-integrate-istio-with-vm.html#fig7.3.6.1","level":"7.3.6","list_caption":"Figure: Istio 中的服务注册发现模型","alt":"Istio 中的服务注册发现模型","nro":225,"url":"https://tva1.sinaimg.cn/large/0081Kckwly1gktf3b63j0j30p30ehwf5.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Istio 中的服务注册发现模型","attributes":{},"skip":false,"key":"7.3.6.1"},{"backlink":"usecases/how-to-integrate-istio-with-vm.html#fig7.3.6.2","level":"7.3.6","list_caption":"Figure: Bookinfo 示例中的流量示意图","alt":"Bookinfo 示例中的流量示意图","nro":226,"url":"../images/istio-bookinfo-vm-traffic.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Bookinfo 示例中的流量示意图","attributes":{},"skip":false,"key":"7.3.6.2"},{"backlink":"usecases/istio-vm-support.html#fig7.3.7.1","level":"7.3.7","list_caption":"Figure: 云原生应用的三个阶段","alt":"云原生应用的三个阶段","nro":227,"url":"../images/0081Kckwly1gm0d6t775lj31s80k8go8.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生应用的三个阶段","attributes":{},"skip":false,"key":"7.3.7.1"},{"backlink":"usecases/istio-vm-support.html#fig7.3.7.2","level":"7.3.7","list_caption":"Figure: 图一：从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","alt":"图一：从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","nro":228,"url":"../images/0081Kckwly1gm0d6rogojj30u00yhdil.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"图一：从集成虚拟机到在 mesh 中访问虚拟机中服务的详细流程","attributes":{},"skip":false,"key":"7.3.7.2"},{"backlink":"usecases/istio-vm-support.html#fig7.3.7.3","level":"7.3.7","list_caption":"Figure: 图二：通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","alt":"图二：通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","nro":229,"url":"../images/0081Kckwly1gm0d6qx2o0j30sq0v440v.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"图二：通过配置虚拟机本地 /etc/hosts 访问 mesh 内服务的流程","attributes":{},"skip":false,"key":"7.3.7.3"},{"backlink":"usecases/istio-vm-support.html#fig7.3.7.4","level":"7.3.7","list_caption":"Figure: 图三：引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","alt":"图三：引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","nro":230,"url":"../images/0081Kckwly1gm0d6sgfpxj30oi0rsjt5.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"图三：引入了智能 DNS 代理后虚拟机访问 mesh 内服务的流程","attributes":{},"skip":false,"key":"7.3.7.4"},{"backlink":"usecases/envoy.html#fig7.4.1","level":"7.4","list_caption":"Figure: 负载均衡器的特性以及拓扑类型","alt":"负载均衡器的特性以及拓扑类型","nro":231,"url":"../images/load-balancing-and-proxing.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"负载均衡器的特性以及拓扑类型","attributes":{},"skip":false,"key":"7.4.1"},{"backlink":"usecases/envoy-terminology.html#fig7.4.1.1","level":"7.4.1","list_caption":"Figure: Envoy proxy 架构图","alt":"Envoy proxy 架构图","nro":232,"url":"../images/envoy-arch.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Envoy proxy 架构图","attributes":{},"skip":false,"key":"7.4.1.1"},{"backlink":"usecases/envoy-front-proxy.html#fig7.4.2.1","level":"7.4.2","list_caption":"Figure: Front proxy 部署结构图（转自https://www.envoyproxy.io/docs/envoy/latest/start/sandboxes/front_proxy）","alt":"Front proxy 部署结构图（转自https://www.envoyproxy.io/docs/envoy/latest/start/sandboxes/front_proxy）","nro":233,"url":"../images/envoyproxy-docker-compose.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Front proxy 部署结构图（转自https://www.envoyproxy.io/docs/envoy/latest/start/sandboxes/front_proxy）","attributes":{},"skip":false,"key":"7.4.2.1"},{"backlink":"usecases/envoy-mesh-in-kubernetes-tutorial.html#fig7.4.3.1","level":"7.4.3","list_caption":"Figure: Envoy Mesh架构图","alt":"Envoy Mesh架构图","nro":234,"url":"../images/envoy-mesh-in-kubernetes.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Envoy Mesh架构图","attributes":{},"skip":false,"key":"7.4.3.1"},{"backlink":"usecases/microservices.html#fig8.2.1","level":"8.2","list_caption":"Figure: 微服务关注的部分","alt":"微服务关注的部分","nro":235,"url":"../images/microservices-concerns.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"微服务关注的部分","attributes":{},"skip":false,"key":"8.2.1"},{"backlink":"usecases/service-discovery-in-microservices.html#fig8.2.1.1","level":"8.2.1","list_caption":"Figure: 微服务中的服务发现","alt":"微服务中的服务发现","nro":236,"url":"../images/service-discovery-in-microservices.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"微服务中的服务发现","attributes":{},"skip":false,"key":"8.2.1.1"},{"backlink":"usecases/microservices-for-java-developers.html#fig8.2.2.1","level":"8.2.2","list_caption":"Figure: Spring技术栈","alt":"Spring技术栈","nro":237,"url":"../images/spring-stack.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Spring技术栈","attributes":{},"skip":false,"key":"8.2.2.1"},{"backlink":"usecases/microservices-for-java-developers.html#fig8.2.2.2","level":"8.2.2","list_caption":"Figure: Spring Boot的知识点","alt":"Spring Boot的知识点","nro":238,"url":"../images/spring-boot-note-spots.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Spring Boot的知识点","attributes":{},"skip":false,"key":"8.2.2.2"},{"backlink":"usecases/spark-on-kubernetes.html#fig8.3.1.1","level":"8.3.1","list_caption":"Figure: Spark on yarn with kubernetes","alt":"Spark on yarn with kubernetes","nro":239,"url":"../images/spark-on-yarn-with-kubernetes.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Spark on yarn with kubernetes","attributes":{},"skip":false,"key":"8.3.1.1"},{"backlink":"usecases/spark-on-kubernetes.html#fig8.3.1.2","level":"8.3.1","list_caption":"Figure: 在 kubernetes 上使用多种调度方式","alt":"在 kubernetes 上使用多种调度方式","nro":240,"url":"../images/spark-on-kubernetes-with-different-schedulers.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"在 kubernetes 上使用多种调度方式","attributes":{},"skip":false,"key":"8.3.1.2"},{"backlink":"usecases/spark-standalone-on-kubernetes.html#fig8.3.1.1.1","level":"8.3.1.1","list_caption":"Figure: spark master ui","alt":"spark master ui","nro":241,"url":"../images/spark-ui.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"spark master ui","attributes":{},"skip":false,"key":"8.3.1.1.1"},{"backlink":"usecases/spark-standalone-on-kubernetes.html#fig8.3.1.1.2","level":"8.3.1.1","list_caption":"Figure: zeppelin ui","alt":"zeppelin ui","nro":242,"url":"../images/zeppelin-ui.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"zeppelin ui","attributes":{},"skip":false,"key":"8.3.1.1.2"},{"backlink":"usecases/serverless.html#fig8.4.1","level":"8.4","list_caption":"Figure: Serverless Landscape","alt":"Serverless Landscape","nro":243,"url":"../images/006tNbRwly1fx0ie2kb90j31kw0ynha3.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Serverless Landscape","attributes":{},"skip":false,"key":"8.4.1"},{"backlink":"usecases/serverless.html#fig8.4.2","level":"8.4","list_caption":"Figure: 从物理机到函数计算","alt":"从物理机到函数计算","nro":244,"url":"../images/from-bare-metal-to-functions.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"从物理机到函数计算","attributes":{},"skip":false,"key":"8.4.2"},{"backlink":"usecases/serverless.html#fig8.4.3","level":"8.4","list_caption":"Figure: FaaS Landscape","alt":"FaaS Landscape","nro":245,"url":"../images/redpoint-faas-landscape.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"FaaS Landscape","attributes":{},"skip":false,"key":"8.4.3"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.1","level":"8.4.1","list_caption":"Figure: Serverless 在云原生技术中的地位","alt":"Serverless 在云原生技术中的地位","nro":246,"url":"../images/cloud-landscape-zh.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Serverless 在云原生技术中的地位","attributes":{},"skip":false,"key":"8.4.1.1"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.2","level":"8.4.1","list_caption":"Figure: 服务端软件的运行环境","alt":"服务端软件的运行环境","nro":247,"url":"../images/serverless-server-side-software.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"服务端软件的运行环境","attributes":{},"skip":false,"key":"8.4.1.2"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.3","level":"8.4.1","list_caption":"Figure: FaaS应用架构","alt":"FaaS应用架构","nro":248,"url":"../images/serverless-faas-platform.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"FaaS应用架构","attributes":{},"skip":false,"key":"8.4.1.3"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.4","level":"8.4.1","list_caption":"Figure: Serverless 中的函数定义","alt":"Serverless 中的函数定义","nro":249,"url":"../images/006y8mN6ly1g7ldey3l7gj31ti0mwta9.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Serverless 中的函数定义","attributes":{},"skip":false,"key":"8.4.1.4"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.5","level":"8.4.1","list_caption":"Figure: FaaS 中的函数","alt":"FaaS 中的函数","nro":250,"url":"../images/006y8mN6ly1g7ldhm7bxyj31040u0q5n.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"FaaS 中的函数","attributes":{},"skip":false,"key":"8.4.1.5"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.6","level":"8.4.1","list_caption":"Figure: 传统应用程序架构","alt":"传统应用程序架构","nro":251,"url":"../images/non-serverless-game-arch.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"传统应用程序架构","attributes":{},"skip":false,"key":"8.4.1.6"},{"backlink":"usecases/understanding-serverless.html#fig8.4.1.7","level":"8.4.1","list_caption":"Figure: Serverless架构","alt":"Serverless架构","nro":252,"url":"../images/serverless-game-arch.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Serverless架构","attributes":{},"skip":false,"key":"8.4.1.7"},{"backlink":"usecases/openfaas-quick-start.html#fig8.4.2.1.1","level":"8.4.2.1","list_caption":"Figure: OpenFaaS架构","alt":"OpenFaaS架构","nro":253,"url":"../images/openfaas-arch.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OpenFaaS架构","attributes":{},"skip":false,"key":"8.4.2.1.1"},{"backlink":"usecases/openfaas-quick-start.html#fig8.4.2.1.2","level":"8.4.2.1","list_caption":"Figure: OpenFaaS Prometheus","alt":"OpenFaaS Prometheus","nro":254,"url":"../images/openfaas-prometheus.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OpenFaaS Prometheus","attributes":{},"skip":false,"key":"8.4.2.1.2"},{"backlink":"usecases/openfaas-quick-start.html#fig8.4.2.1.3","level":"8.4.2.1","list_caption":"Figure: OpenFaas Grafana监控","alt":"OpenFaas Grafana监控","nro":255,"url":"../images/openfaas-grafana.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OpenFaas Grafana监控","attributes":{},"skip":false,"key":"8.4.2.1.3"},{"backlink":"usecases/openfaas-quick-start.html#fig8.4.2.1.4","level":"8.4.2.1","list_caption":"Figure: OpenFaas Dashboard","alt":"OpenFaas Dashboard","nro":256,"url":"../images/openfaas-deploy-a-function.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"OpenFaas Dashboard","attributes":{},"skip":false,"key":"8.4.2.1.4"},{"backlink":"usecases/openfaas-quick-start.html#fig8.4.2.1.5","level":"8.4.2.1","list_caption":"Figure: NodeInfo执行结果","alt":"NodeInfo执行结果","nro":257,"url":"../images/openfaas-nodeinfo.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"NodeInfo执行结果","attributes":{},"skip":false,"key":"8.4.2.1.5"},{"backlink":"usecases/knative.html#fig8.4.3.1","level":"8.4.3","list_caption":"Figure: Knative logo","alt":"Knative logo","nro":258,"url":"https://tva1.sinaimg.cn/large/006y8mN6ly1g7pg0iwbzfj30d8080dfp.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Knative logo","attributes":{},"skip":false,"key":"8.4.3.1"},{"backlink":"usecases/knative.html#fig8.4.3.2","level":"8.4.3","list_caption":"Figure: Knative 受众（图片来自 knative.dev）","alt":"Knative 受众（图片来自 knative.dev）","nro":259,"url":"https://tva1.sinaimg.cn/large/006y8mN6ly1g7po5i7cgqj31ap0u075l.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Knative 受众（图片来自 knative.dev）","attributes":{},"skip":false,"key":"8.4.3.2"},{"backlink":"develop/sigs-and-working-group.html#fig9.2.1","level":"9.2","list_caption":"Figure: Kubernetes SIG","alt":"Kubernetes SIG","nro":260,"url":"../images/kubernetes-sigs.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes SIG","attributes":{},"skip":false,"key":"9.2.1"},{"backlink":"develop/testing.html#fig9.4.1","level":"9.4","list_caption":"Figure: test-infra架构图（图片来自官方GitHub）","alt":"test-infra架构图（图片来自官方GitHub）","nro":261,"url":"../images/kubernetes-test-architecture.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"test-infra架构图（图片来自官方GitHub）","attributes":{},"skip":false,"key":"9.4.1"},{"backlink":"develop/client-go-sample.html#fig9.5.1","level":"9.5","list_caption":"Figure: 使用kubernetes dashboard进行故障排查","alt":"使用kubernetes dashboard进行故障排查","nro":262,"url":"../images/kubernetes-client-go-sample-update.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"使用kubernetes dashboard进行故障排查","attributes":{},"skip":false,"key":"9.5.1"},{"backlink":"develop/client-go-informer-sourcecode-analyse.html#fig9.5.1.1","level":"9.5.1","list_caption":"Figure: client-go informer","alt":"client-go informer","nro":263,"url":"../images/client-go-informer.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"client-go informer","attributes":{},"skip":false,"key":"9.5.1.1"},{"backlink":"develop/client-go-informer-sourcecode-analyse.html#fig9.5.1.2","level":"9.5.1","list_caption":"Figure: image","alt":"image","nro":264,"url":"https://github.com/jianlongzhou/client-go-source-analysis/blob/main/deltaFIFO.png?raw=true","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"image","attributes":{},"skip":false,"key":"9.5.1.2"},{"backlink":"develop/client-go-informer-sourcecode-analyse.html#fig9.5.1.3","level":"9.5.1","list_caption":"Figure: 图片来源于网络","alt":"图片来源于网络","nro":265,"url":"https://user-images.githubusercontent.com/41672087/116666278-5981ca00-a9cd-11eb-9570-8ee6eb447d05.png","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"图片来源于网络","attributes":{},"skip":false,"key":"9.5.1.3"},{"backlink":"cloud-native/cncf.html#fig10.1.1","level":"10.1","list_caption":"Figure: CNCF landscape","alt":"CNCF landscape","nro":266,"url":"../images/006tNbRwly1fxmx633ymqj31dp0u0kjn.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF landscape","attributes":{},"skip":false,"key":"10.1.1"},{"backlink":"cloud-native/cncf.html#fig10.1.2","level":"10.1","list_caption":"Figure: CNCF项目成熟度级别","alt":"CNCF项目成熟度级别","nro":267,"url":"../images/cncf-graduation-criteria-v2.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF项目成熟度级别","attributes":{},"skip":false,"key":"10.1.2"},{"backlink":"cloud-native/cncf-charter.html#fig10.1.1.1","level":"10.1.1","list_caption":"Figure: CNCF 组织架构图","alt":"CNCF 组织架构图","nro":268,"url":"../images/cncf-org-arch.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF 组织架构图","attributes":{},"skip":false,"key":"10.1.1.1"},{"backlink":"cloud-native/cncf-charter.html#fig10.1.1.2","level":"10.1.1","list_caption":"Figure: 云原生的理想分层架构","alt":"云原生的理想分层架构","nro":269,"url":"../images/006tKfTcly1ft3zgjlisxj30n70ffjth.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"云原生的理想分层架构","attributes":{},"skip":false,"key":"10.1.1.2"},{"backlink":"cloud-native/cncf-sandbox-criteria.html#fig10.1.3.1","level":"10.1.3","list_caption":"Figure: sandbox 流程","alt":"sandbox 流程","nro":270,"url":"../images/sandbox-process.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"sandbox 流程","attributes":{},"skip":false,"key":"10.1.3.1"},{"backlink":"cloud-native/cncf-project-governing.html#fig10.1.4.1","level":"10.1.4","list_caption":"Figure: CNCF 项目的成熟度分类","alt":"CNCF 项目的成熟度分类","nro":271,"url":"../images/cncf-graduation.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF 项目的成熟度分类","attributes":{},"skip":false,"key":"10.1.4.1"},{"backlink":"cloud-native/cncf-project-governing.html#fig10.1.4.2","level":"10.1.4","list_caption":"Figure: CNCF 中的项目运作","alt":"CNCF 中的项目运作","nro":272,"url":"../images/006tNc79ly1g1yz80ag98j31cs0n2gr7.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF 中的项目运作","attributes":{},"skip":false,"key":"10.1.4.2"},{"backlink":"cloud-native/cncf-project-governing.html#fig10.1.4.3","level":"10.1.4","list_caption":"Figure: CNCF 项目成熟度级别","alt":"CNCF 项目成熟度级别","nro":273,"url":"../images/cncf-graduation-criteria-v2.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF 项目成熟度级别","attributes":{},"skip":false,"key":"10.1.4.3"},{"backlink":"appendix/about-cka-candidate.html#fig10.2.2.1","level":"10.2.2","list_caption":"Figure: cka-question","alt":"cka-question","nro":274,"url":"../images/cka-question.png","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"cka-question","attributes":{},"skip":false,"key":"10.2.2.1"},{"backlink":"appendix/about-cka-candidate.html#fig10.2.2.2","level":"10.2.2","list_caption":"Figure: CKA mindmap","alt":"CKA mindmap","nro":275,"url":"../images/cka-mindmap.png","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CKA mindmap","attributes":{},"skip":false,"key":"10.2.2.2"},{"backlink":"appendix/issues.html#fig11.5.1","level":"11.5","list_caption":"Figure: pvc-storage-limit","alt":"pvc-storage-limit","nro":276,"url":"../images/pvc-storage-limit.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"pvc-storage-limit","attributes":{},"skip":false,"key":"11.5.1"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.1","level":"11.6.2","list_caption":"Figure: Kubernetes 搜索趋势(来自 Google trends)","alt":"Kubernetes 搜索趋势(来自 Google trends)","nro":277,"url":"../images/006tNc79ly1fzne6y4f2ej31q60fedho.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 搜索趋势(来自 Google trends)","attributes":{},"skip":false,"key":"11.6.2.1"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.2","level":"11.6.2","list_caption":"Figure: Kubernetes 的百度指数","alt":"Kubernetes 的百度指数","nro":278,"url":"../images/006tNc79ly1fznegoocmvj31y00hmgon.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Kubernetes 的百度指数","attributes":{},"skip":false,"key":"11.6.2.2"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.3","level":"11.6.2","list_caption":"Figure: Istio 中的 CRD","alt":"Istio 中的 CRD","nro":279,"url":"../images/006tNc79ly1fzna87wmfij30u00zc4qp.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"Istio 中的 CRD","attributes":{},"skip":false,"key":"11.6.2.3"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.4","level":"11.6.2","list_caption":"Figure: 2019 Q1 软件架构趋势 - 来自 InfoQ","alt":"2019 Q1 软件架构趋势 - 来自 InfoQ","nro":280,"url":"../images/006tNc79ly1fzor2k6f7wj313j0u0dl3.jpg","index":4,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"2019 Q1 软件架构趋势 - 来自 InfoQ","attributes":{},"skip":false,"key":"11.6.2.4"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.5","level":"11.6.2","list_caption":"Figure: ServiceMesher 社区 Logo","alt":"ServiceMesher 社区 Logo","nro":281,"url":"../images/006tNc79ly1fznadbp63qj31jt0beq9s.jpg","index":5,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"ServiceMesher 社区 Logo","attributes":{},"skip":false,"key":"11.6.2.5"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.6","level":"11.6.2","list_caption":"Figure: ServiceMesher 社区 2018 年活动一览","alt":"ServiceMesher 社区 2018 年活动一览","nro":282,"url":"../images/006tNc79ly1fzm9vs4o3aj31s00u0x6p.jpg","index":6,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"ServiceMesher 社区 2018 年活动一览","attributes":{},"skip":false,"key":"11.6.2.6"},{"backlink":"appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html#fig11.6.2.7","level":"11.6.2","list_caption":"Figure: CNCF Landscape 中的 Serverless 单元","alt":"CNCF Landscape 中的 Serverless 单元","nro":283,"url":"../images/006tNc79ly1fznbh3vfbwj310f0jxgxj.jpg","index":7,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF Landscape 中的 Serverless 单元","attributes":{},"skip":false,"key":"11.6.2.7"},{"backlink":"appendix/cncf-annual-report-2018.html#fig11.7.1.1","level":"11.7.1","list_caption":"Figure: CNCF 项目成熟度级别","alt":"CNCF 项目成熟度级别","nro":284,"url":"../images/006tNc79ly1g04s0oznytj31tg0ok7ca.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF 项目成熟度级别","attributes":{},"skip":false,"key":"11.7.1.1"},{"backlink":"appendix/cncf-annual-report-2018.html#fig11.7.1.2","level":"11.7.1","list_caption":"Figure: KCSP","alt":"KCSP","nro":285,"url":"../images/006tNc79ly1g04tl97vm4j318v0h7dpt.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"KCSP","attributes":{},"skip":false,"key":"11.7.1.2"},{"backlink":"appendix/cncf-annual-report-2020.html#fig11.7.2.1","level":"11.7.2","list_caption":"Figure: CNCF 会员增长情况","alt":"CNCF 会员增长情况","nro":286,"url":"../images/008eGmZEly1gmhqzaxsy1j31dz0u0acn.jpg","index":1,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"CNCF 会员增长情况","attributes":{},"skip":false,"key":"11.7.2.1"},{"backlink":"appendix/cncf-annual-report-2020.html#fig11.7.2.2","level":"11.7.2","list_caption":"Figure: 新收录的开源项目","alt":"新收录的开源项目","nro":287,"url":"../images/008eGmZEly1gmhrip3dc2j315q0u01e0.jpg","index":2,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"新收录的开源项目","attributes":{},"skip":false,"key":"11.7.2.2"},{"backlink":"appendix/cncf-annual-report-2020.html#fig11.7.2.3","level":"11.7.2","list_caption":"Figure: 项目更新","alt":"项目更新","nro":288,"url":"../images/008eGmZEly1gmhrl3860hj31ob0u0wn4.jpg","index":3,"caption_template":"图 _PAGE_LEVEL_._PAGE_IMAGE_NUMBER_：_CAPTION_","label":"项目更新","attributes":{},"skip":false,"key":"11.7.2.3"}]},"title":"Kubernetes 中文指南——云原生应用架构实战手册","language":"zh-hans","links":{"sidebar":{"回到主页":"https://jimmysong.io","全部书籍":"https://jimmysong.io/book/","云原生开源项目大全":"https://jimmysong.io/awesome-cloud-native/","云原生社区":"https://cloudnative.to"}},"gitbook":"*","description":"Kubernetes Handbook - Kubernetes 中文指南/云原生应用架构实战手册，本书记录了本人从零开始学习和使用 Kubernetes 的心路历程，着重于经验分享和总结，同时也会有相关的概念解析，希望能够帮助大家少踩坑，少走弯路，还会指引大家关注Kubernetes生态周边，如微服务构建、DevOps、大数据应用、Service Mesh、Cloud Native等领域。"},"file":{"path":"cloud-native/kubernetes-and-cloud-native-app-overview.md","mtime":"2022-04-27T04:14:59.054Z","type":"markdown"},"gitbook":{"version":"3.2.3","time":"2022-04-27T04:15:20.734Z"},"basePath":"..","book":{"language":""}});
|
||
});
|
||
</script>
|
||
</div>
|
||
|
||
|
||
<script src="../gitbook/gitbook.js"></script>
|
||
<script src="../gitbook/theme.js"></script>
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-github/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-splitter/splitter.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-page-toc-button/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-editlink/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-back-to-top-button/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-search-plus/jquery.mark.min.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-search-plus/search.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-github-buttons/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-3-ba/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-lightbox/js/lightbox.min.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-ga/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-hide-element/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-expandable-chapters-small/expandable-chapters-small.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-insert-logo/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-adsense/plugin.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-sharing/buttons.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-fontsettings/fontsettings.js"></script>
|
||
|
||
|
||
|
||
</body>
|
||
</html>
|
||
|