5223 lines
310 KiB
HTML
5223 lines
310 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>Sidecar 的注入与透明流量劫持 · 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="istio-traffic-routing.html" />
|
||
|
||
|
||
<link rel="prev" href="sidecar-spec-in-istio.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/docs/" target="_blank" class="custom-link">全部书籍</a>
|
||
</li>
|
||
|
||
|
||
<li>
|
||
<a href="https://jimmysong.io/awesome-cloud-native/" target="_blank" class="custom-link">云原生开源项目大全</a>
|
||
</li>
|
||
|
||
|
||
<li>
|
||
<a href="https://cloudnative.to" target="_blank" class="custom-link">云原生社区</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="divider"></li>
|
||
|
||
|
||
|
||
|
||
<li class="header">前言</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="1.1" data-path="../">
|
||
|
||
<a href="../">
|
||
|
||
|
||
<b>1.1.</b>
|
||
|
||
序言
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">云原生</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="2.1" data-path="../cloud-native/cloud-native-definition.html">
|
||
|
||
<a href="../cloud-native/cloud-native-definition.html">
|
||
|
||
|
||
<b>2.1.</b>
|
||
|
||
云原生的定义
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.2" data-path="../cloud-native/cloud-native-philosophy.html">
|
||
|
||
<a href="../cloud-native/cloud-native-philosophy.html">
|
||
|
||
|
||
<b>2.2.</b>
|
||
|
||
云原生的设计哲学
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.3" data-path="../cloud-native/kubernetes-history.html">
|
||
|
||
<a href="../cloud-native/kubernetes-history.html">
|
||
|
||
|
||
<b>2.3.</b>
|
||
|
||
Kubernetes 的诞生
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.4" data-path="../cloud-native/kubernetes-and-cloud-native-app-overview.html">
|
||
|
||
<a href="../cloud-native/kubernetes-and-cloud-native-app-overview.html">
|
||
|
||
|
||
<b>2.4.</b>
|
||
|
||
Kubernetes 与云原生应用概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.5" data-path="../cloud-native/from-kubernetes-to-cloud-native.html">
|
||
|
||
<a href="../cloud-native/from-kubernetes-to-cloud-native.html">
|
||
|
||
|
||
<b>2.5.</b>
|
||
|
||
云原生应用之路 —— 从 Kubernetes 到云原生
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6" data-path="../cloud-native/define-cloud-native-app.html">
|
||
|
||
<a href="../cloud-native/define-cloud-native-app.html">
|
||
|
||
|
||
<b>2.6.</b>
|
||
|
||
定义云原生应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.6.1" data-path="../cloud-native/oam.html">
|
||
|
||
<a href="../cloud-native/oam.html">
|
||
|
||
|
||
<b>2.6.1.</b>
|
||
|
||
OAM
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.6.1.1" data-path="../cloud-native/workload.html">
|
||
|
||
<a href="../cloud-native/workload.html">
|
||
|
||
|
||
<b>2.6.1.1.</b>
|
||
|
||
Workload
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.2" data-path="../cloud-native/component.html">
|
||
|
||
<a href="../cloud-native/component.html">
|
||
|
||
|
||
<b>2.6.1.2.</b>
|
||
|
||
Component
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.3" data-path="../cloud-native/trait.html">
|
||
|
||
<a href="../cloud-native/trait.html">
|
||
|
||
|
||
<b>2.6.1.3.</b>
|
||
|
||
Trait
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.4" data-path="../cloud-native/application-scope.html">
|
||
|
||
<a href="../cloud-native/application-scope.html">
|
||
|
||
|
||
<b>2.6.1.4.</b>
|
||
|
||
Application Scope
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.1.5" data-path="../cloud-native/application-configuration.html">
|
||
|
||
<a href="../cloud-native/application-configuration.html">
|
||
|
||
|
||
<b>2.6.1.5.</b>
|
||
|
||
Application Configuration
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.6.2" data-path="../cloud-native/crossplane.html">
|
||
|
||
<a href="../cloud-native/crossplane.html">
|
||
|
||
|
||
<b>2.6.2.</b>
|
||
|
||
Crossplane
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.7" data-path="../cloud-native/cloud-native-programming-languages.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-languages.html">
|
||
|
||
|
||
<b>2.7.</b>
|
||
|
||
云原生平台配置语言
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.7.1" data-path="../cloud-native/cloud-native-programming-language-ballerina.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-language-ballerina.html">
|
||
|
||
|
||
<b>2.7.1.</b>
|
||
|
||
Ballerina
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.7.2" data-path="../cloud-native/cloud-native-programming-language-pulumi.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-language-pulumi.html">
|
||
|
||
|
||
<b>2.7.2.</b>
|
||
|
||
Pulumi
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.8" data-path="../cloud-native/the-future-of-cloud-native.html">
|
||
|
||
<a href="../cloud-native/the-future-of-cloud-native.html">
|
||
|
||
|
||
<b>2.8.</b>
|
||
|
||
云原生的未来
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">快速入门</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="3.1" data-path="../cloud-native/quick-start.html">
|
||
|
||
<a href="../cloud-native/quick-start.html">
|
||
|
||
|
||
<b>3.1.</b>
|
||
|
||
云原生新手入门指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.2" data-path="../cloud-native/play-with-kubernetes.html">
|
||
|
||
<a href="../cloud-native/play-with-kubernetes.html">
|
||
|
||
|
||
<b>3.2.</b>
|
||
|
||
Play with Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.3" data-path="../cloud-native/cloud-native-local-quick-start.html">
|
||
|
||
<a href="../cloud-native/cloud-native-local-quick-start.html">
|
||
|
||
|
||
<b>3.3.</b>
|
||
|
||
快速部署一个云原生本地实验环境
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4" data-path="../cloud-native/setup-kubernetes-with-rancher-and-aliyun.html">
|
||
|
||
<a href="../cloud-native/setup-kubernetes-with-rancher-and-aliyun.html">
|
||
|
||
|
||
<b>3.4.</b>
|
||
|
||
使用 Rancher 在阿里云上部署 Kubenretes 集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">概念与原理</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="4.1" data-path="../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="service-mesh.html">
|
||
|
||
<a href="service-mesh.html">
|
||
|
||
|
||
<b>7.1.</b>
|
||
|
||
服务网格（Service Mesh）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2" data-path="the-enterprise-path-to-service-mesh-architectures.html">
|
||
|
||
<a href="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="service-mesh-fundamental.html">
|
||
|
||
<a href="service-mesh-fundamental.html">
|
||
|
||
|
||
<b>7.2.1.</b>
|
||
|
||
服务网格基础
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.2" data-path="comparing-service-mesh-technologies.html">
|
||
|
||
<a href="comparing-service-mesh-technologies.html">
|
||
|
||
|
||
<b>7.2.2.</b>
|
||
|
||
服务网格技术对比
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.3" data-path="service-mesh-vs-api-gateway.html">
|
||
|
||
<a href="service-mesh-vs-api-gateway.html">
|
||
|
||
|
||
<b>7.2.3.</b>
|
||
|
||
服务网格对比 API 网关
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.4" data-path="service-mesh-adoption-and-evolution.html">
|
||
|
||
<a href="service-mesh-adoption-and-evolution.html">
|
||
|
||
|
||
<b>7.2.4.</b>
|
||
|
||
采纳和演进
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.5" data-path="service-mesh-customization-and-integration.html">
|
||
|
||
<a href="service-mesh-customization-and-integration.html">
|
||
|
||
|
||
<b>7.2.5.</b>
|
||
|
||
定制和集成
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2.6" data-path="service-mesh-conclusion.html">
|
||
|
||
<a href="service-mesh-conclusion.html">
|
||
|
||
|
||
<b>7.2.6.</b>
|
||
|
||
总结
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3" data-path="istio.html">
|
||
|
||
<a href="istio.html">
|
||
|
||
|
||
<b>7.3.</b>
|
||
|
||
Istio
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="7.3.1" data-path="before-using-istio.html">
|
||
|
||
<a href="before-using-istio.html">
|
||
|
||
|
||
<b>7.3.1.</b>
|
||
|
||
使用 Istio 前需要考虑的问题
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.2" data-path="sidecar-pattern.html">
|
||
|
||
<a href="sidecar-pattern.html">
|
||
|
||
|
||
<b>7.3.2.</b>
|
||
|
||
Sidecar 模式
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.3" data-path="sidecar-spec-in-istio.html">
|
||
|
||
<a href="sidecar-spec-in-istio.html">
|
||
|
||
|
||
<b>7.3.3.</b>
|
||
|
||
Istio 中 sidecar 的注入规范
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter active" data-level="7.3.4" data-path="understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.html">
|
||
|
||
<a href="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="istio-traffic-routing.html">
|
||
|
||
<a href="istio-traffic-routing.html">
|
||
|
||
|
||
<b>7.3.5.</b>
|
||
|
||
Istio 中的流量路由过程详解
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.6" data-path="how-to-integrate-istio-with-vm.html">
|
||
|
||
<a href="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="istio-vm-support.html">
|
||
|
||
<a href="istio-vm-support.html">
|
||
|
||
|
||
<b>7.3.7.</b>
|
||
|
||
Istio 支持虚拟机的历史
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3.8" data-path="istio-community-tips.html">
|
||
|
||
<a href="istio-community-tips.html">
|
||
|
||
|
||
<b>7.3.8.</b>
|
||
|
||
如何参与 Istio 社区及注意事项
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.4" data-path="envoy.html">
|
||
|
||
<a href="envoy.html">
|
||
|
||
|
||
<b>7.4.</b>
|
||
|
||
Envoy
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="7.4.1" data-path="envoy-terminology.html">
|
||
|
||
<a href="envoy-terminology.html">
|
||
|
||
|
||
<b>7.4.1.</b>
|
||
|
||
Envoy 的架构与基本术语
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.4.2" data-path="envoy-front-proxy.html">
|
||
|
||
<a href="envoy-front-proxy.html">
|
||
|
||
|
||
<b>7.4.2.</b>
|
||
|
||
Envoy 作为前端代理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.4.3" data-path="envoy-mesh-in-kubernetes-tutorial.html">
|
||
|
||
<a href="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="./">
|
||
|
||
<a href="./">
|
||
|
||
|
||
<b>8.1.</b>
|
||
|
||
领域应用概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.2" data-path="microservices.html">
|
||
|
||
<a href="microservices.html">
|
||
|
||
|
||
<b>8.2.</b>
|
||
|
||
微服务架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.2.1" data-path="service-discovery-in-microservices.html">
|
||
|
||
<a href="service-discovery-in-microservices.html">
|
||
|
||
|
||
<b>8.2.1.</b>
|
||
|
||
微服务中的服务发现
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.2.2" data-path="microservices-for-java-developers.html">
|
||
|
||
<a href="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="spring-boot-quick-start-guide.html">
|
||
|
||
<a href="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="big-data.html">
|
||
|
||
<a href="big-data.html">
|
||
|
||
|
||
<b>8.3.</b>
|
||
|
||
大数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.3.1" data-path="spark-on-kubernetes.html">
|
||
|
||
<a href="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="spark-standalone-on-kubernetes.html">
|
||
|
||
<a href="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="running-spark-with-kubernetes-native-scheduler.html">
|
||
|
||
<a href="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="serverless.html">
|
||
|
||
<a href="serverless.html">
|
||
|
||
|
||
<b>8.4.</b>
|
||
|
||
Serverless 架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.4.1" data-path="understanding-serverless.html">
|
||
|
||
<a href="understanding-serverless.html">
|
||
|
||
|
||
<b>8.4.1.</b>
|
||
|
||
理解 Serverless
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.4.2" data-path="faas.html">
|
||
|
||
<a href="faas.html">
|
||
|
||
|
||
<b>8.4.2.</b>
|
||
|
||
FaaS（函数即服务）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.4.2.1" data-path="openfaas-quick-start.html">
|
||
|
||
<a href="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="knative.html">
|
||
|
||
<a href="knative.html">
|
||
|
||
|
||
<b>8.4.3.</b>
|
||
|
||
Knative
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.5" data-path="edge-computing.html">
|
||
|
||
<a href="edge-computing.html">
|
||
|
||
|
||
<b>8.5.</b>
|
||
|
||
边缘计算
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.6" data-path="ai.html">
|
||
|
||
<a href="ai.html">
|
||
|
||
|
||
<b>8.6.</b>
|
||
|
||
人工智能
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.7" data-path="observability.html">
|
||
|
||
<a href="observability.html">
|
||
|
||
|
||
<b>8.7.</b>
|
||
|
||
可观察性
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">开发指南</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="9.1" data-path="../develop/">
|
||
|
||
<a href="../develop/">
|
||
|
||
|
||
<b>9.1.</b>
|
||
|
||
开发指南概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.2" data-path="../develop/sigs-and-working-group.html">
|
||
|
||
<a href="../develop/sigs-and-working-group.html">
|
||
|
||
|
||
<b>9.2.</b>
|
||
|
||
SIG 和工作组
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.3" data-path="../develop/developing-environment.html">
|
||
|
||
<a href="../develop/developing-environment.html">
|
||
|
||
|
||
<b>9.3.</b>
|
||
|
||
开发环境搭建
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.3.1" data-path="../develop/using-vagrant-and-virtualbox-for-development.html">
|
||
|
||
<a href="../develop/using-vagrant-and-virtualbox-for-development.html">
|
||
|
||
|
||
<b>9.3.1.</b>
|
||
|
||
本地分布式开发环境搭建（使用 Vagrant 和 Virtualbox）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.4" data-path="../develop/testing.html">
|
||
|
||
<a href="../develop/testing.html">
|
||
|
||
|
||
<b>9.4.</b>
|
||
|
||
单元测试和集成测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.5" data-path="../develop/client-go-sample.html">
|
||
|
||
<a href="../develop/client-go-sample.html">
|
||
|
||
|
||
<b>9.5.</b>
|
||
|
||
client-go 示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.5.1" data-path="../develop/client-go-informer-sourcecode-analyse.html">
|
||
|
||
<a href="../develop/client-go-informer-sourcecode-analyse.html">
|
||
|
||
|
||
<b>9.5.1.</b>
|
||
|
||
client-go 中的 informer 源码分析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.6" data-path="../develop/operator.html">
|
||
|
||
<a href="../develop/operator.html">
|
||
|
||
|
||
<b>9.6.</b>
|
||
|
||
Operator
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.6.1" data-path="../develop/operator-sdk.html">
|
||
|
||
<a href="../develop/operator-sdk.html">
|
||
|
||
|
||
<b>9.6.1.</b>
|
||
|
||
operator-sdk
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.7" data-path="../develop/kubebuilder.html">
|
||
|
||
<a href="../develop/kubebuilder.html">
|
||
|
||
|
||
<b>9.7.</b>
|
||
|
||
kubebuilder
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="9.7.1" data-path="../develop/kubebuilder-example.html">
|
||
|
||
<a href="../develop/kubebuilder-example.html">
|
||
|
||
|
||
<b>9.7.1.</b>
|
||
|
||
使用 kubebuilder 创建 operator 示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.8" data-path="../develop/advance-developer.html">
|
||
|
||
<a href="../develop/advance-developer.html">
|
||
|
||
|
||
<b>9.8.</b>
|
||
|
||
高级开发指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.9" data-path="../develop/contribute.html">
|
||
|
||
<a href="../develop/contribute.html">
|
||
|
||
|
||
<b>9.9.</b>
|
||
|
||
社区贡献
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="9.10" data-path="../develop/minikube.html">
|
||
|
||
<a href="../develop/minikube.html">
|
||
|
||
|
||
<b>9.10.</b>
|
||
|
||
Minikube
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">社区及生态</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="10.1" data-path="../cloud-native/cncf.html">
|
||
|
||
<a href="../cloud-native/cncf.html">
|
||
|
||
|
||
<b>10.1.</b>
|
||
|
||
云原生计算基金会（CNCF）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="10.1.1" data-path="../cloud-native/cncf-charter.html">
|
||
|
||
<a href="../cloud-native/cncf-charter.html">
|
||
|
||
|
||
<b>10.1.1.</b>
|
||
|
||
CNCF 章程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.2" data-path="../cloud-native/cncf-sig.html">
|
||
|
||
<a href="../cloud-native/cncf-sig.html">
|
||
|
||
|
||
<b>10.1.2.</b>
|
||
|
||
CNCF 特别兴趣小组（SIG）说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.3" data-path="../cloud-native/cncf-sandbox-criteria.html">
|
||
|
||
<a href="../cloud-native/cncf-sandbox-criteria.html">
|
||
|
||
|
||
<b>10.1.3.</b>
|
||
|
||
开源项目加入 CNCF Sandbox 的要求
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.4" data-path="../cloud-native/cncf-project-governing.html">
|
||
|
||
<a href="../cloud-native/cncf-project-governing.html">
|
||
|
||
|
||
<b>10.1.4.</b>
|
||
|
||
CNCF 中的项目治理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.1.5" data-path="../cloud-native/cncf-ambassador.html">
|
||
|
||
<a href="../cloud-native/cncf-ambassador.html">
|
||
|
||
|
||
<b>10.1.5.</b>
|
||
|
||
CNCF Ambassador
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.2" data-path="../cloud-native/certification.html">
|
||
|
||
<a href="../cloud-native/certification.html">
|
||
|
||
|
||
<b>10.2.</b>
|
||
|
||
认证及培训
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="10.2.1" data-path="../appendix/about-kcsp.html">
|
||
|
||
<a href="../appendix/about-kcsp.html">
|
||
|
||
|
||
<b>10.2.1.</b>
|
||
|
||
认证 Kubernetes 服务提供商（KCSP）说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="10.2.2" data-path="../appendix/about-cka-candidate.html">
|
||
|
||
<a href="../appendix/about-cka-candidate.html">
|
||
|
||
|
||
<b>10.2.2.</b>
|
||
|
||
认证 Kubernetes 管理员（CKA）说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">附录</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="11.1" data-path="../appendix/">
|
||
|
||
<a href="../appendix/">
|
||
|
||
|
||
<b>11.1.</b>
|
||
|
||
附录说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.2" data-path="../appendix/debug-kubernetes-services.html">
|
||
|
||
<a href="../appendix/debug-kubernetes-services.html">
|
||
|
||
|
||
<b>11.2.</b>
|
||
|
||
Kubernetes 中的应用故障排查
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.3" data-path="../appendix/material-share.html">
|
||
|
||
<a href="../appendix/material-share.html">
|
||
|
||
|
||
<b>11.3.</b>
|
||
|
||
Kubernetes 参考资源
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.4" data-path="../appendix/tricks.html">
|
||
|
||
<a href="../appendix/tricks.html">
|
||
|
||
|
||
<b>11.4.</b>
|
||
|
||
Kubernetes 使用技巧
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.5" data-path="../appendix/issues.html">
|
||
|
||
<a href="../appendix/issues.html">
|
||
|
||
|
||
<b>11.5.</b>
|
||
|
||
Kubernetes 相关问题记录
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.6" data-path="../appendix/summary-and-outlook.html">
|
||
|
||
<a href="../appendix/summary-and-outlook.html">
|
||
|
||
|
||
<b>11.6.</b>
|
||
|
||
Kubernetes 及云原生年度总结及展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="11.6.1" data-path="../appendix/kubernetes-and-cloud-native-summary-in-2017-and-outlook-for-2018.html">
|
||
|
||
<a href="../appendix/kubernetes-and-cloud-native-summary-in-2017-and-outlook-for-2018.html">
|
||
|
||
|
||
<b>11.6.1.</b>
|
||
|
||
Kubernetes 与云原生 2017 年年终总结及 2018 年展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.6.2" data-path="../appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html">
|
||
|
||
<a href="../appendix/kubernetes-and-cloud-native-summary-in-2018-and-outlook-for-2019.html">
|
||
|
||
|
||
<b>11.6.2.</b>
|
||
|
||
Kubernetes 与云原生 2018 年年终总结及 2019 年展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.7" data-path="../appendix/cncf-annual-report.html">
|
||
|
||
<a href="../appendix/cncf-annual-report.html">
|
||
|
||
|
||
<b>11.7.</b>
|
||
|
||
CNCF 年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="11.7.1" data-path="../appendix/cncf-annual-report-2018.html">
|
||
|
||
<a href="../appendix/cncf-annual-report-2018.html">
|
||
|
||
|
||
<b>11.7.1.</b>
|
||
|
||
CNCF 2018 年年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="11.7.2" data-path="../appendix/cncf-annual-report-2020.html">
|
||
|
||
<a href="../appendix/cncf-annual-report-2020.html">
|
||
|
||
|
||
<b>11.7.2.</b>
|
||
|
||
CNCF 2020 年年度报告解读
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="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=".." >Sidecar 的注入与透明流量劫持</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="sidecar-的注入与透明流量劫持">Sidecar 的注入与透明流量劫持</h1>
|
||
<p>Istio 中提供了以下两种 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> 注入方式：</p>
|
||
<ul>
|
||
<li>使用 <code>istioctl</code> 手动注入。</li>
|
||
<li>基于 Kubernetes 的 <a href="https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/" target="_blank">突变 webhook 准入控制器（mutating webhook addmission controller</a> 的自动 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> 注入方式。</li>
|
||
</ul>
|
||
<p>不论是手动注入还是自动注入，<a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> 的注入过程都需要遵循如下步骤：</p>
|
||
<ol>
|
||
<li>Kubernetes 需要了解待注入的 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> 所连接的 Istio 集群及其配置；</li>
|
||
<li>Kubernetes 需要了解待注入的 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> 容器本身的配置，如镜像地址、启动参数等；</li>
|
||
<li>Kubernetes 根据 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> 注入模板和以上配置填充 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> 的配置参数，将以上配置注入到应用容器的一侧；</li>
|
||
</ol>
|
||
<p>使用下面的命令可以手动注入 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a>。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl kube-inject -f <span class="token variable">${YAML_FILE}</span> <span class="token operator">|</span> kuebectl apply -f -
|
||
</code></pre>
|
||
<p>该命令会使用 Istio 内置的 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> 配置来注入，下面使用 Istio详细配置请参考 <a href="https://istio.io/docs/setup/additional-setup/sidecar-injection/#manual-sidecar-injection" target="_blank">Istio 官网</a>。</p>
|
||
<p>注入完成后您将看到 Istio 为原有 pod template 注入了 <code>initContainer</code> 及 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> proxy相关的配置。</p>
|
||
<h2 id="init-容器">Init 容器</h2>
|
||
<p>Init 容器是一种专用容器，它在应用程序容器启动之前运行，用来包含一些应用镜像中不存在的实用工具或安装脚本。</p>
|
||
<p>一个 Pod 中可以指定多个 Init 容器，如果指定了多个，那么 Init 容器将会按顺序依次运行。只有当前面的 Init 容器必须运行成功后，才可以运行下一个 Init 容器。当所有的 Init 容器运行完成后，Kubernetes 才初始化 Pod 和运行应用容器。</p>
|
||
<p>Init 容器使用 Linux Namespace，所以相对应用程序容器来说具有不同的文件系统视图。因此，它们能够具有访问 Secret 的权限，而应用程序容器则不能。</p>
|
||
<p>在 Pod 启动过程中，Init 容器会按顺序在网络和数据卷初始化之后启动。每个容器必须在下一个容器启动之前成功退出。如果由于运行时或失败退出，将导致容器启动失败，它会根据 Pod 的 <code>restartPolicy</code> 指定的策略进行重试。然而，如果 Pod 的 <code>restartPolicy</code> 设置为 Always，Init 容器失败时会使用 <code>RestartPolicy</code> 策略。</p>
|
||
<p>在所有的 Init 容器没有成功之前，Pod 将不会变成 <code>Ready</code> 状态。Init 容器的端口将不会在 Service中进行聚集。 正在初始化中的 Pod 处于 <code>Pending</code> 状态，但应该会将 <code>Initializing</code> 状态设置为 true。Init 容器运行完成以后就会自动终止。</p>
|
||
<p>关于 Init 容器的详细信息请参考 <a href="https://jimmysong.io/kubernetes-handbook/concepts/init-containers.html" target="_blank">Init 容器 - Kubernetes 中文指南/云原生应用架构实践手册</a>。</p>
|
||
<h2 id="sidecar-注入示例分析">Sidecar 注入示例分析</h2>
|
||
<p>本文我们将以 Istio 官方示例 <code>bookinfo</code> 中 <code>reivews</code> 服务为例，来接讲解 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">Sidecar</a> 容器注入的额流程，每个注入了 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">Sidecar</a> 的 Pod 中除了原先应用的应用本身的容器外，都会多出来这样两个容器：</p>
|
||
<ul>
|
||
<li><code>istio-init</code>：用于给 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">Sidecar</a> 容器即 Envoy 代理做初始化，设置 iptables 端口转发</li>
|
||
<li><code>istio-proxy</code>：Envoy 代理容器，运行 Envoy 代理</li>
|
||
</ul>
|
||
<p>接下来将分别解析下这两个容器。</p>
|
||
<h3 id="init-容器解析">Init 容器解析</h3>
|
||
<p>Istio 在 Pod 中注入的 Init 容器名为 <code>istio-init</code>，如果你查看 <code>reviews</code> Deployment 配置，你将看到其中 <code>initContaienrs</code> 的启动参数：</p>
|
||
<pre class="language-"><code class="lang-bash"> initContainers:
|
||
- name: istio-init
|
||
image: docker.io/istio/proxyv2:1.13.1
|
||
args:
|
||
- istio-iptables
|
||
- <span class="token string">'-p'</span>
|
||
- <span class="token string">'15001'</span>
|
||
- <span class="token string">'-z'</span>
|
||
- <span class="token string">'15006'</span>
|
||
- <span class="token string">'-u'</span>
|
||
- <span class="token string">'1337'</span>
|
||
- <span class="token string">'-m'</span>
|
||
- REDIRECT
|
||
- <span class="token string">'-i'</span>
|
||
- <span class="token string">'*'</span>
|
||
- <span class="token string">'-x'</span>
|
||
- <span class="token string">''</span>
|
||
- <span class="token string">'-b'</span>
|
||
- <span class="token string">'*'</span>
|
||
- <span class="token string">'-d'</span>
|
||
- <span class="token number">15090,15021</span>,15020
|
||
</code></pre>
|
||
<p>我们看到 <code>istio-init</code> 容器的入口是 <code>istio-iptables</code> 命令，该命令是用于初始化路由表的。</p>
|
||
<h3 id="init-容器启动入口">Init 容器启动入口</h3>
|
||
<p>Init 容器的启动入口是 <code>/usr/local/bin/istio-iptable</code> 命令，该命令的用法如下：</p>
|
||
<pre class="language-"><code class="lang-bash">$ istio-iptables -p PORT -u <span class="token environment constant">UID</span> -g GID <span class="token punctuation">[</span>-m mode<span class="token punctuation">]</span> <span class="token punctuation">[</span>-b ports<span class="token punctuation">]</span> <span class="token punctuation">[</span>-d ports<span class="token punctuation">]</span> <span class="token punctuation">[</span>-i CIDR<span class="token punctuation">]</span> <span class="token punctuation">[</span>-x CIDR<span class="token punctuation">]</span> <span class="token punctuation">[</span>-h<span class="token punctuation">]</span>
|
||
-p: 指定重定向所有 TCP 流量的 Envoy 端口（默认为 <span class="token variable">$ENVOY_PORT</span> <span class="token operator">=</span> <span class="token number">15001</span>）
|
||
-u: 指定未应用重定向的用户的 <span class="token environment constant">UID</span>。通常，这是代理容器的 <span class="token environment constant">UID</span>（默认为 <span class="token variable">$ENVOY_USER</span> 的 uid，istio_proxy 的 uid 或 <span class="token number">1337</span>）
|
||
-g: 指定未应用重定向的用户的 GID。（与 -u param 相同的默认值）
|
||
-m: 指定入站连接重定向到 Envoy 的模式，“REDIRECT” 或 “TPROXY”（默认为 <span class="token variable">$ISTIO_INBOUND_INTERCEPTION_MODE</span><span class="token punctuation">)</span>
|
||
-b: 逗号分隔的入站端口列表，其流量将重定向到 Envoy（可选）。使用通配符 “*” 表示重定向所有端口。为空时表示禁用所有入站重定向（默认为 <span class="token variable">$ISTIO_INBOUND_PORTS</span>）
|
||
-d: 指定要从重定向到 Envoy 中排除（可选）的入站端口列表，以逗号格式分隔。使用通配符“*” 表示重定向所有入站流量（默认为 <span class="token variable">$ISTIO_LOCAL_EXCLUDE_PORTS</span>）
|
||
-i: 指定重定向到 Envoy（可选）的 IP 地址范围，以逗号分隔的 CIDR 格式列表。使用通配符 “*” 表示重定向所有出站流量。空列表将禁用所有出站重定向（默认为 <span class="token variable">$ISTIO_SERVICE_CIDR</span>）
|
||
-x: 指定将从重定向中排除的 IP 地址范围，以逗号分隔的 CIDR 格式列表。使用通配符 “*” 表示重定向所有出站流量（默认为 <span class="token variable">$ISTIO_SERVICE_EXCLUDE_CIDR</span>）。
|
||
-z: 所有入站 TCP 流量重定向端口（默认为 <span class="token variable">$INBOUND_CAPTURE_PORT</span> <span class="token number">15006</span>）
|
||
</code></pre>
|
||
<p>关于该命令的详细代码请<a href="https://github.com/istio/istio/blob/master/tools/istio-iptables/pkg/cmd/root.go" target="_blank">查看 GitHub：<code>tools/istio-iptables/pkg/cmd/root.go</code></a>。</p>
|
||
<p>再参考 <code>istio-init</code> 容器的启动参数，完整的启动命令如下：</p>
|
||
<pre class="language-"><code class="lang-bash">$ /usr/local/bin/istio-iptables -p <span class="token number">15001</span> -z <span class="token number">15006</span> -u <span class="token number">1337</span> -m REDIRECT -i <span class="token string">'*'</span> -x <span class="token string">""</span> -b * -d <span class="token string">"15090,15201,15020"</span>
|
||
</code></pre>
|
||
<p>该容器存在的意义就是让 Envoy 代理可以拦截所有的进出 Pod 的流量，即将入站流量重定向到 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">Sidecar</a>，再拦截应用容器的出站流量经过 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">Sidecar</a> 处理后再出站。</p>
|
||
<p><strong>命令解析</strong></p>
|
||
<p>这条启动命令的作用是：</p>
|
||
<ul>
|
||
<li>将应用容器的所有流量都转发到 Envoy 的 15006 端口。</li>
|
||
<li>使用 <code>istio-proxy</code> 用户身份运行， UID 为 1337，即 Envoy 所处的用户空间，这也是 <code>istio-proxy</code> 容器默认使用的用户，见 YAML 配置中的 <code>runAsUser</code> 字段。</li>
|
||
<li>使用默认的 <code>REDIRECT</code> 模式来重定向流量。</li>
|
||
<li>将所有出站流量都重定向到 Envoy 代理。</li>
|
||
<li>将除了 15090、15201、15020 端口以外的所有端口的流量重定向到 Envoy 代理。</li>
|
||
</ul>
|
||
<p>因为 Init 容器初始化完毕后就会自动终止，因为我们无法登陆到容器中查看 iptables 信息，但是 Init 容器初始化结果会保留到应用容器和 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">Sidecar</a> 容器中。</p>
|
||
<h3 id="istio-proxy-容器解析">istio-proxy 容器解析</h3>
|
||
<p>为了查看 iptables 配置，我们需要登陆到 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">Sidecar</a> 容器中使用 root 用户来查看，因为 <code>kubectl</code> 无法使用特权模式来远程操作 docker 容器，所以我们需要登陆到 <code>reviews</code> Pod 所在的主机上使用 <code>docker</code> 命令登陆容器中查看。</p>
|
||
<p>查看 <code>reviews</code> Pod 所在的主机。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl -n default get pod -l <span class="token assign-left variable">app</span><span class="token operator">=</span>reviews -o wide
|
||
NAME READY STATUS RESTARTS AGE IP NODE
|
||
reviews-v1-745ffc55b7-2l2lw <span class="token number">2</span>/2 Running <span class="token number">0</span> 1d <span class="token number">172.33</span>.78.10 node3
|
||
</code></pre>
|
||
<p>从输出结果中可以看到该 Pod 运行在 <code>node3</code> 上，使用 <code>vagrant</code> 命令登陆到 <code>node3</code> 主机中并切换为 root 用户。</p>
|
||
<pre class="language-"><code class="lang-bash">$ vagrant <span class="token function">ssh</span> node3
|
||
$ <span class="token function">sudo</span> -i
|
||
</code></pre>
|
||
<p>查看 iptables 配置，列出 NAT（网络地址转换）表的所有规则，因为在 Init 容器启动的时候选择给 <code>istio-iptables.sh</code> 传递的参数中指定将入站流量重定向到 Envoy 的模式为 “REDIRECT”，因此在 iptables 中将只有 NAT 表的规格配置，如果选择 <code>TPROXY</code> 还会有 <code>mangle</code> 表配置。<code>iptables</code> 命令的详细用法请参考 <a href="https://wangchujiang.com/linux-command/c/iptables.html" target="_blank">iptables</a>，规则配置请参考 <a href="http://www.zsythink.net/archives/1517" target="_blank">iptables 规则配置</a>。</p>
|
||
<h2 id="理解-iptables">理解 iptables</h2>
|
||
<p><code>iptables</code> 是 Linux 内核中的防火墙软件 netfilter 的管理工具，位于用户空间，同时也是 netfilter 的一部分。Netfilter 位于内核空间，不仅有网络地址转换的功能，也具备数据包内容修改、以及数据包过滤等防火墙功能。</p>
|
||
<p>在了解 Init 容器初始化的 iptables 之前，我们先来了解下 iptables 和规则配置。</p>
|
||
<p>下图展示了 iptables 调用链。</p>
|
||
<figure id="fig7.3.4.1"><a href="../images/iptables.jpg" data-lightbox="b0fbdbd8-a0d6-4c43-afac-92355e3a1675" data-title="iptables 调用链"><img src="../images/iptables.jpg" alt="iptables 调用链"></a><figcaption>图 7.3.4.1：iptables 调用链</figcaption></figure>
|
||
<h3 id="iptables-中的表">iptables 中的表</h3>
|
||
<p>Init 容器中使用的的 iptables 版本是 <code>v1.6.0</code>，共包含 5 张表：</p>
|
||
<ol>
|
||
<li><code>raw</code> 用于配置数据包，<code>raw</code> 中的数据包不会被系统跟踪。</li>
|
||
<li><code>filter</code> 是用于存放所有与防火墙相关操作的默认表。</li>
|
||
<li><code>nat</code> 用于 <a href="https://en.wikipedia.org/wiki/Network_address_translation" target="_blank">网络地址转换</a>（例如：端口转发）。</li>
|
||
<li><code>mangle</code> 用于对特定数据包的修改（参考<a href="https://en.wikipedia.org/wiki/Mangled_packet" target="_blank">损坏数据包</a>）。</li>
|
||
<li><code>security</code> 用于<a href="https://wiki.archlinux.org/index.php/Security#Mandatory_access_control" target="_blank">强制访问控制</a> 网络规则。</li>
|
||
</ol>
|
||
<p><strong>注</strong>：在本示例中只用到了 <code>nat</code> 表。</p>
|
||
<p>不同的表中的具有的链类型如下表所示：</p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th>规则名称</th>
|
||
<th>raw</th>
|
||
<th>filter</th>
|
||
<th>nat</th>
|
||
<th>mangle</th>
|
||
<th>security</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td>PREROUTING</td>
|
||
<td>✓</td>
|
||
<td></td>
|
||
<td>✓</td>
|
||
<td>✓</td>
|
||
<td></td>
|
||
</tr>
|
||
<tr>
|
||
<td>INPUT</td>
|
||
<td></td>
|
||
<td>✓</td>
|
||
<td>✓</td>
|
||
<td>✓</td>
|
||
<td>✓</td>
|
||
</tr>
|
||
<tr>
|
||
<td>OUTPUT</td>
|
||
<td></td>
|
||
<td>✓</td>
|
||
<td>✓</td>
|
||
<td>✓</td>
|
||
<td>✓</td>
|
||
</tr>
|
||
<tr>
|
||
<td>POSTROUTING</td>
|
||
<td></td>
|
||
<td></td>
|
||
<td>✓</td>
|
||
<td>✓</td>
|
||
<td></td>
|
||
</tr>
|
||
<tr>
|
||
<td>FORWARD</td>
|
||
<td>✓</td>
|
||
<td>✓</td>
|
||
<td></td>
|
||
<td>✓</td>
|
||
<td>✓</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p>下图是 iptables 的调用链顺序。</p>
|
||
<figure id="fig7.3.4.2"><a href="../images/iptables-chains.jpg" data-lightbox="aa9f1259-2bac-4def-b3c8-8b7414504ee6" data-title="IPtables 调用链顺序"><img src="../images/iptables-chains.jpg" alt="IPtables 调用链顺序"></a><figcaption>图 7.3.4.2：IPtables 调用链顺序</figcaption></figure>
|
||
<h3 id="iptables-命令">iptables 命令</h3>
|
||
<p><code>iptables</code> 命令的主要用途是修改这些表中的规则。<code>iptables</code> 命令格式如下：</p>
|
||
<pre class="language-"><code class="lang-bash">$ iptables <span class="token punctuation">[</span>-t 表名<span class="token punctuation">]</span> 命令选项［链名<span class="token punctuation">]</span>［条件匹配］<span class="token punctuation">[</span>-j 目标动作或跳转］
|
||
</code></pre>
|
||
<p>Init 容器中的 <code>/istio-iptables.sh</code> 启动入口脚本就是执行 iptables 初始化的。</p>
|
||
<h3 id="理解-iptables-规则">理解 iptables 规则</h3>
|
||
<p>查看 <code>istio-proxy</code> 容器中的默认的 iptables 规则，默认查看的是 filter 表中的规则。</p>
|
||
<pre class="language-"><code class="lang-bash">$ iptables -L -v
|
||
Chain INPUT <span class="token punctuation">(</span>policy ACCEPT 350K packets, 63M bytes<span class="token punctuation">)</span>
|
||
pkts bytes target prot opt <span class="token keyword">in</span> out <span class="token builtin class-name">source</span> destination
|
||
|
||
Chain FORWARD <span class="token punctuation">(</span>policy ACCEPT <span class="token number">0</span> packets, <span class="token number">0</span> bytes<span class="token punctuation">)</span>
|
||
pkts bytes target prot opt <span class="token keyword">in</span> out <span class="token builtin class-name">source</span> destination
|
||
|
||
Chain OUTPUT <span class="token punctuation">(</span>policy ACCEPT 18M packets, 1916M bytes<span class="token punctuation">)</span>
|
||
pkts bytes target prot opt <span class="token keyword">in</span> out <span class="token builtin class-name">source</span> destination
|
||
</code></pre>
|
||
<p>我们看到三个默认的链，分别是 INPUT、FORWARD 和 OUTPUT，每个链中的第一行输出表示链名称（在本例中为 INPUT/FORWARD/OUTPUT），后跟默认策略（ACCEPT）。</p>
|
||
<p>每条链中都可以添加多条规则，规则是按照顺序从前到后执行的。我们来看下规则的表头定义。</p>
|
||
<ul>
|
||
<li><strong>pkts</strong>：处理过的匹配的报文数量</li>
|
||
<li><strong>bytes</strong>：累计处理的报文大小（字节数）</li>
|
||
<li><strong>target</strong>：如果报文与规则匹配，指定目标就会被执行。</li>
|
||
<li><strong>prot</strong>：协议，例如 <code>tdp</code>、<code>udp</code>、<code>icmp</code> 和 <code>all</code>。</li>
|
||
<li><strong>opt</strong>：很少使用，这一列用于显示 IP 选项。</li>
|
||
<li><strong>in</strong>：入站网卡。</li>
|
||
<li><strong>out</strong>：出站网卡。</li>
|
||
<li><strong>source</strong>：流量的源 IP 地址或子网，后者是 <code>anywhere</code>。</li>
|
||
<li><strong>destination</strong>：流量的目的地 IP 地址或子网，或者是 <code>anywhere</code>。</li>
|
||
</ul>
|
||
<p>还有一列没有表头，显示在最后，表示规则的选项，作为规则的扩展匹配条件，用来补充前面的几列中的配置。<code>prot</code>、<code>opt</code>、<code>in</code>、<code>out</code>、<code>source</code> 和 <code>destination</code> 和显示在 <code>destination</code> 后面的没有表头的一列扩展条件共同组成匹配规则。当流量匹配这些规则后就会执行 <code>target</code>。</p>
|
||
<p><strong>target 支持的类型</strong></p>
|
||
<p><code>target</code> 类型包括 ACCEPT<code>、REJECT</code>、<code>DROP</code>、<code>LOG</code> 、<code>SNAT</code>、<code>MASQUERADE</code>、<code>DNAT</code>、<code>REDIRECT</code>、<code>RETURN</code> 或者跳转到其他规则等。只要执行到某一条链中只有按照顺序有一条规则匹配后就可以确定报文的去向了，除了 <code>RETURN</code> 类型，类似编程语言中的 <code>return</code> 语句，返回到它的调用点，继续执行下一条规则。<code>target</code> 支持的配置详解请参考 <a href="http://www.zsythink.net/archives/1199" target="_blank">iptables 详解（1）：iptables 概念</a>。</p>
|
||
<p>从输出结果中可以看到 Init 容器没有在 iptables 的默认链路中创建任何规则，而是创建了新的链路。</p>
|
||
<h2 id="查看-iptables-nat-表中注入的规则">查看 iptables nat 表中注入的规则</h2>
|
||
<p>Init 容器通过向 iptables nat 表中注入转发规则来劫持流量的，下图显示的是三个 reviews 服务示例中的某一个 Pod，其中有 init 容器、应用容器和 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> 容器，图中展示了 iptables 流量劫持的详细过程。</p>
|
||
<figure id="fig7.3.4.3"><a href="../images/envoy-sidecar-traffic-interception-zh-20220424.jpg" data-lightbox="fd76ea98-101b-4413-8c49-fab9579cdf05" data-title="Sidecar 流量劫持示意图"><img src="../images/envoy-sidecar-traffic-interception-zh-20220424.jpg" alt="Sidecar 流量劫持示意图"></a><figcaption>图 7.3.4.3：<a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">Sidecar</a> 流量劫持示意图</figcaption></figure>
|
||
<p>Init 容器启动时命令行参数中指定了 <code>REDIRECT</code> 模式，因此只创建了 NAT 表规则，接下来我们查看下 NAT 表中创建的规则，这是全文中的<strong>重点部分</strong>，前面讲了那么多都是为它做铺垫的。</p>
|
||
<h3 id="进入到-reviews-pod">进入到 reviews pod</h3>
|
||
<p>Reviews 服务有三个版本，我们进入到其中任意一个版本，例如 reviews-1，首先你需要搞清楚这个 pod 运行在哪个节点上，知道那个容器的具体 ID，然后使用 SSH 登录那个节点，使用 <code>ps</code> 命令查看到那个容器的具体 PID，使用 <code>nsenter</code> 命令进入该容器。</p>
|
||
<pre class="language-"><code class="lang-sh">nsenter -t<span class="token punctuation">{</span>PID<span class="token punctuation">}</span> -n
|
||
</code></pre>
|
||
<p><strong>为什么不直接使用 kubectl 进入容器？</strong></p>
|
||
<p>Istio 向 pod 中自动注入的 <a href="../GLOSSARY.html#sidecar" class="glossary-term" title="Sidecar，全称 Sidecar proxy，为在应用程序旁运行的单独的进程，它可以为应用程序添加许多功能，而无需在应用程序中添加额外的第三方组件，或修改应用程序的代码或配置。">sidecar</a> 容器（名为 <code>istio-proxy</code>）其中默认的用户是 <code>istio-proxy</code>，该用户没有权限查看路由表规则，即当你在该容器中运行 <code>iptabes</code> 命令时会得到 <code>iptables -t nat -L -v</code> 这样的结果，而且你又没有 root 权限。对于 reviews 容器也是一样，默认用户的 UID 是 <code>1000</code>，而且这个用户又没有名字，一样也无法切换为 root 用户，系统中默认没有安装 iptabels 命令。所以我们只能登录到 Pod 的宿主节点上，使用 <code>nsenter</code> 命令进入容器内部。</p>
|
||
<h3 id="查看路由表">查看路由表</h3>
|
||
<p>下面是查看 nat 表中的规则，其中链的名字中包含 <code>ISTIO</code> 前缀的是由 Init 容器注入的，规则匹配是根据下面显示的顺序来执行的，其中会有多次跳转。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token comment"># PREROUTING 链：用于目标地址转换（DNAT），将所有入站 TCP 流量跳转到 ISTIO_INBOUND 链上。</span>
|
||
Chain PREROUTING <span class="token punctuation">(</span>policy ACCEPT <span class="token number">2701</span> packets, 162K bytes<span class="token punctuation">)</span>
|
||
pkts bytes target prot opt <span class="token keyword">in</span> out <span class="token builtin class-name">source</span> destination
|
||
<span class="token number">2701</span> 162K ISTIO_INBOUND tcp -- any any anywhere anywhere
|
||
|
||
<span class="token comment"># INPUT 链：处理输入数据包，非 TCP 流量将继续 OUTPUT 链。</span>
|
||
Chain INPUT <span class="token punctuation">(</span>policy ACCEPT <span class="token number">2701</span> packets, 162K bytes<span class="token punctuation">)</span>
|
||
pkts bytes target prot opt <span class="token keyword">in</span> out <span class="token builtin class-name">source</span> destination
|
||
|
||
<span class="token comment"># OUTPUT 链：将所有出站数据包跳转到 ISTIO_OUTPUT 链上。</span>
|
||
Chain OUTPUT <span class="token punctuation">(</span>policy ACCEPT <span class="token number">79</span> packets, <span class="token number">6761</span> bytes<span class="token punctuation">)</span>
|
||
pkts bytes target prot opt <span class="token keyword">in</span> out <span class="token builtin class-name">source</span> destination
|
||
<span class="token number">15</span> <span class="token number">900</span> ISTIO_OUTPUT tcp -- any any anywhere anywhere
|
||
|
||
<span class="token comment"># POSTROUTING 链：所有数据包流出网卡时都要先进入 POSTROUTING 链，内核根据数据包目的地判断是否需要转发出去，我们看到此处未做任何处理。</span>
|
||
Chain POSTROUTING <span class="token punctuation">(</span>policy ACCEPT <span class="token number">79</span> packets, <span class="token number">6761</span> bytes<span class="token punctuation">)</span>
|
||
pkts bytes target prot opt <span class="token keyword">in</span> out <span class="token builtin class-name">source</span> destination
|
||
|
||
<span class="token comment"># ISTIO_INBOUND 链：将所有入站流量重定向到 ISTIO_IN_REDIRECT 链上。目的地为 15090（Prometheus 使用）和 15020（Ingress gateway 使用，用于 Pilot 健康检查）端口的流量除外，发送到以上两个端口的流量将返回 iptables 规则链的调用点，即 PREROUTING 链的后继 POSTROUTING 后直接调用原始目的地。</span>
|
||
Chain ISTIO_INBOUND <span class="token punctuation">(</span><span class="token number">1</span> references<span class="token punctuation">)</span>
|
||
pkts bytes target prot opt <span class="token keyword">in</span> out <span class="token builtin class-name">source</span> destination
|
||
<span class="token number">0</span> <span class="token number">0</span> RETURN tcp -- any any anywhere anywhere tcp dpt:ssh
|
||
<span class="token number">2</span> <span class="token number">120</span> RETURN tcp -- any any anywhere anywhere tcp dpt:15090
|
||
<span class="token number">2699</span> 162K RETURN tcp -- any any anywhere anywhere tcp dpt:15020
|
||
<span class="token number">0</span> <span class="token number">0</span> ISTIO_IN_REDIRECT tcp -- any any anywhere anywhere
|
||
|
||
<span class="token comment"># ISTIO_IN_REDIRECT 链：将所有的入站流量跳转到本地的 15006 端口，至此成功的拦截了流量到 sidecar 代理的 Inbound Handler 中。</span>
|
||
Chain ISTIO_IN_REDIRECT <span class="token punctuation">(</span><span class="token number">3</span> references<span class="token punctuation">)</span>
|
||
pkts bytes target prot opt <span class="token keyword">in</span> out <span class="token builtin class-name">source</span> destination
|
||
<span class="token number">0</span> <span class="token number">0</span> REDIRECT tcp -- any any anywhere anywhere redir ports <span class="token number">15006</span>
|
||
|
||
<span class="token comment"># ISTIO_OUTPUT 链：规则比较复杂，将在下文解释</span>
|
||
Chain ISTIO_OUTPUT <span class="token punctuation">(</span><span class="token number">1</span> references<span class="token punctuation">)</span>
|
||
pkts bytes target prot opt <span class="token keyword">in</span> out <span class="token builtin class-name">source</span> destination
|
||
<span class="token number">0</span> <span class="token number">0</span> RETURN all -- any lo <span class="token number">127.0</span>.0.6 anywhere <span class="token comment">#规则1</span>
|
||
<span class="token number">0</span> <span class="token number">0</span> ISTIO_IN_REDIRECT all -- any lo anywhere <span class="token operator">!</span>localhost owner <span class="token environment constant">UID</span> match <span class="token number">1337</span> <span class="token comment">#规则2</span>
|
||
<span class="token number">0</span> <span class="token number">0</span> RETURN all -- any lo anywhere anywhere <span class="token operator">!</span> owner <span class="token environment constant">UID</span> match <span class="token number">1337</span> <span class="token comment">#规则3</span>
|
||
<span class="token number">15</span> <span class="token number">900</span> RETURN all -- any any anywhere anywhere owner <span class="token environment constant">UID</span> match <span class="token number">1337</span> <span class="token comment">#规则4</span>
|
||
<span class="token number">0</span> <span class="token number">0</span> ISTIO_IN_REDIRECT all -- any lo anywhere <span class="token operator">!</span>localhost owner GID match <span class="token number">1337</span> <span class="token comment">#规则5</span>
|
||
<span class="token number">0</span> <span class="token number">0</span> RETURN all -- any lo anywhere anywhere <span class="token operator">!</span> owner GID match <span class="token number">1337</span> <span class="token comment">#规则6</span>
|
||
<span class="token number">0</span> <span class="token number">0</span> RETURN all -- any any anywhere anywhere owner GID match <span class="token number">1337</span> <span class="token comment">#规则7</span>
|
||
<span class="token number">0</span> <span class="token number">0</span> RETURN all -- any any anywhere localhost <span class="token comment">#规则8</span>
|
||
<span class="token number">0</span> <span class="token number">0</span> ISTIO_REDIRECT all -- any any anywhere anywhere <span class="token comment">#规则9</span>
|
||
|
||
<span class="token comment"># ISTIO_REDIRECT 链：将所有流量重定向到 Envoy 代理的 15001 端口。</span>
|
||
Chain ISTIO_REDIRECT <span class="token punctuation">(</span><span class="token number">1</span> references<span class="token punctuation">)</span>
|
||
pkts bytes target prot opt <span class="token keyword">in</span> out <span class="token builtin class-name">source</span> destination
|
||
<span class="token number">0</span> <span class="token number">0</span> REDIRECT tcp -- any any anywhere anywhere redir ports <span class="token number">15001</span>
|
||
</code></pre>
|
||
<p>这里着重需要解释的是 <code>ISTIO_OUTPUT</code> 链中的 9 条规则，为了便于阅读，我将以上规则中的部分内容使用表格的形式来展示如下：</p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th><strong>规则</strong></th>
|
||
<th><strong>target</strong></th>
|
||
<th><strong>in</strong></th>
|
||
<th><strong>out</strong></th>
|
||
<th><strong>source</strong></th>
|
||
<th><strong>destination</strong></th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td>1</td>
|
||
<td>RETURN</td>
|
||
<td>any</td>
|
||
<td>lo</td>
|
||
<td>127.0.0.6</td>
|
||
<td>anywhere</td>
|
||
</tr>
|
||
<tr>
|
||
<td>2</td>
|
||
<td>ISTIO_IN_REDIRECT</td>
|
||
<td>any</td>
|
||
<td>lo</td>
|
||
<td>anywhere</td>
|
||
<td>!localhost owner UID match 1337</td>
|
||
</tr>
|
||
<tr>
|
||
<td>3</td>
|
||
<td>RETURN</td>
|
||
<td>any</td>
|
||
<td>lo</td>
|
||
<td>anywhere</td>
|
||
<td>anywhere !owner UID match 1337</td>
|
||
</tr>
|
||
<tr>
|
||
<td>4</td>
|
||
<td>RETURN</td>
|
||
<td>any</td>
|
||
<td>any</td>
|
||
<td>anywhere</td>
|
||
<td>anywhere owner UID match 1337</td>
|
||
</tr>
|
||
<tr>
|
||
<td>5</td>
|
||
<td>ISTIO_IN_REDIRECT</td>
|
||
<td>any</td>
|
||
<td>lo</td>
|
||
<td>anywhere</td>
|
||
<td>!localhost owner GID match 1337</td>
|
||
</tr>
|
||
<tr>
|
||
<td>6</td>
|
||
<td>RETURN</td>
|
||
<td>any</td>
|
||
<td>lo</td>
|
||
<td>anywhere</td>
|
||
<td>anywhere !owner GID match 1337</td>
|
||
</tr>
|
||
<tr>
|
||
<td>7</td>
|
||
<td>RETURN</td>
|
||
<td>any</td>
|
||
<td>any</td>
|
||
<td>anywhere</td>
|
||
<td>anywhere owner GID match 1337</td>
|
||
</tr>
|
||
<tr>
|
||
<td>8</td>
|
||
<td>RETURN</td>
|
||
<td>any</td>
|
||
<td>any</td>
|
||
<td>anywhere</td>
|
||
<td>localhost</td>
|
||
</tr>
|
||
<tr>
|
||
<td>9</td>
|
||
<td>ISTIO_REDIRECT</td>
|
||
<td>any</td>
|
||
<td>any</td>
|
||
<td>anywhere</td>
|
||
<td>anywhere</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p>下图展示了 <code>ISTIO_ROUTE</code> 规则的详细流程。</p>
|
||
<figure id="fig7.3.4.4"><a href="../images/istio-route-iptables.jpg" data-lightbox="4dd40bd3-d502-4aa9-ae82-f60e5f308d2c" data-title="ISTIO_ROUTE iptables 规则流程图"><img src="../images/istio-route-iptables.jpg" alt="ISTIO_ROUTE iptables 规则流程图"></a><figcaption>图 7.3.4.4：ISTIO_ROUTE iptables 规则流程图</figcaption></figure>
|
||
<p>我将按照规则的出现顺序来解释每条规则的目的、对应文章开头图示中的步骤及详情。其中规则 5、6、7 是分别对规则 2、3、4 的应用范围扩大（从 UID 扩大为 GID），作用是类似的，将合并解释。注意，其中的规则是按顺序执行的，也就是说排序越靠后的规则将作为默认值。出站网卡（out）为 <code>lo</code> （本地回环地址，loopback 接口）时，表示流量的目的地是本地 Pod，对于 Pod 向外部发送的流量就不会经过这个接口。所有 <code>review</code> Pod 的出站流量只适用于规则 4、7、8、9。</p>
|
||
<p><strong>规则 1</strong></p>
|
||
<ul>
|
||
<li>目的：<strong>透传</strong> Envoy 代理发送到本地应用容器的流量，使其绕过 Envoy 代理，直达应用容器。</li>
|
||
<li>对应图示中的步骤：6 到 7。</li>
|
||
<li>详情：该规则使得所有来自 <code>127.0.0.6</code>（该 IP 地址将在下文解释） 的请求，跳出该链，返回 iptables 的调用点（即 <code>OUTPUT</code>）后继续执行其余路由规则，即 <code>POSTROUTING</code> 规则，把流量发送到任意目的地址，如本地 Pod 内的应用容器。如果没有这条规则，由 Pod 内 Envoy 代理发出的对 Pod 内容器访问的流量将会执行下一条规则，即规则 2，流量将再次进入到了 Inbound Handler 中，从而形成了死循环。将这条规则放在第一位可以避免流量在 Inbound Handler 中死循环的问题。</li>
|
||
</ul>
|
||
<p><strong>规则 2、5</strong></p>
|
||
<ul>
|
||
<li>目的：处理 Envoy 代理发出的站内流量（Pod 内部的流量），但不是对 localhost 的请求，通过后续规则将其转发给 Envoy 代理的 Inbound Handler。该规则适用于 Pod 对自身 IP 地址调用的场景。</li>
|
||
<li>对应图示中的步骤：6 到 7。</li>
|
||
<li>详情：如果流量的目的地非 localhost，且数据包是由 1337 UID（即 <code>istio-proxy</code> 用户，Envoy 代理）发出的，流量将被经过 <code>ISTIO_IN_REDIRECT</code> 最终转发到 Envoy 的 Inbound Handler。</li>
|
||
</ul>
|
||
<p><strong>规则 3、6</strong></p>
|
||
<ul>
|
||
<li>目的：<strong>透传</strong> Pod 内的应用容器的站内流量。适用于在应用容器中发出的对本地 Pod 的流量。</li>
|
||
<li>详情：如果流量不是由 Envoy 用户发出的，那么就跳出该链，返回 <code>OUTPUT</code> 调用 <code>POSTROUTING</code>，直达目的地。</li>
|
||
</ul>
|
||
<p><strong>规则 4、7</strong></p>
|
||
<ul>
|
||
<li>目的：<strong>透传</strong> Envoy 代理发出的出站请求。</li>
|
||
<li>对应图示中的步骤：14 到 15。</li>
|
||
<li>详情：如果请求是由 Envoy 代理发出的，则返回 <code>OUTPUT</code> 继续调用 <code>POSTROUTING</code> 规则，最终直接访问目的地。</li>
|
||
</ul>
|
||
<p><strong>规则 8</strong></p>
|
||
<ul>
|
||
<li>目的：<strong>透传</strong> Pod 内部对 localhost 的请求。</li>
|
||
<li>详情：如果请求的目的地是 localhost，则返回 OUTPUT 调用 <code>POSTROUTING</code>，直接访问 localhost。</li>
|
||
</ul>
|
||
<p><strong>规则 9</strong></p>
|
||
<ul>
|
||
<li>目的：所有其他的流量将被转发到 <code>ISTIO_REDIRECT</code> 后，最终达到 Envoy 代理的 Outbound Handler。</li>
|
||
</ul>
|
||
<p>以上规则避免了 Envoy 代理到应用程序的路由在 iptables 规则中的死循环，保障了流量可以被正确的路由到 Envoy 代理上，也可以发出真正的出站请求。</p>
|
||
<p><strong>关于 RETURN target</strong></p>
|
||
<p>你可能留意到上述规则中有很多 RETURN target，它的意思是，指定到这条规则时，跳出该规则链，返回 iptables 的调用点（在我们的例子中即 <code>OUTPUT</code>）后继续执行其余路由规则，在我们的例子中即 <code>POSTROUTING</code> 规则，把流量发送到任意目的地址，你可以把它直观的理解为<strong>透传</strong>。</p>
|
||
<p><strong>关于 127.0.0.6 IP 地址</strong></p>
|
||
<p>127.0.0.6 这个 IP 是 Istio 中默认的 <code>InboundPassthroughClusterIpv4</code>，在 Istio 的代码中指定。即流量在进入 Envoy 代理后被绑定的 IP 地址，作用是让 Outbound 流量重新发送到 Pod 中的应用容器，即 <strong>Passthought（透传），绕过 Outbound Handler</strong>。该流量是对 Pod 自身的访问，而不是真正的对外流量。至于为什么选择这个 IP 作为流量透传，请参考 <a href="https://github.com/istio/istio/issues/29603" target="_blank">Istio Issue-29603</a>。</p>
|
||
<h2 id="使用-iptables-做流量劫持时存在的问题">使用 iptables 做流量劫持时存在的问题</h2>
|
||
<p>目前 Istio 使用 iptables 实现透明劫持，主要存在以下三个问题：</p>
|
||
<ol>
|
||
<li>需要借助于 conntrack 模块实现连接跟踪，在连接数较多的情况下，会造成较大的消耗，同时可能会造成 track 表满的情况，为了避免这个问题，业内有关闭 conntrack 的做法。</li>
|
||
<li>iptables 属于常用模块，全局生效，不能显式的禁止相关联的修改，可管控性比较差。</li>
|
||
<li>iptables 重定向流量本质上是通过 loopback 交换数据，outbond 流量将两次穿越协议栈，在大并发场景下会损失转发性能。</li>
|
||
</ol>
|
||
<p>上述几个问题并非在所有场景中都存在，比方说某些场景下，连接数并不多，且 NAT 表未被使用到的情况下，iptables 是一个满足要求的简单方案。为了适配更加广泛的场景，透明劫持需要解决上述三个问题。</p>
|
||
<h2 id="透明劫持方案优化">透明劫持方案优化</h2>
|
||
<p>为了优化 Istio 中的透明流量劫持的性能，业界提出了以下方案。</p>
|
||
<p><strong>使用 Merbridge 开源项目利用 <a href="../GLOSSARY.html#ebpf" class="glossary-term" title="eBPF 是扩展的柏克莱封包过滤器（extented Berkeley Packet Filter）的缩写，它是类 Unix 系统上数据链路层的一种原始接口，提供原始链路层封包的收发，除此之外，如果网卡驱动支持洪泛模式，那么它可以让网卡处于此种模式，这样可以收到网络上的所有包，不管他们的目的地是不是所在主机。">eBPF</a> 劫持流量</strong></p>
|
||
<p><a href="https://github.com/merbridge/merbridge" target="_blank">Merbridge</a> 是由 DaoCloud 在 2022 年初开源的的一款利用 <a href="../GLOSSARY.html#ebpf" class="glossary-term" title="eBPF 是扩展的柏克莱封包过滤器（extented Berkeley Packet Filter）的缩写，它是类 Unix 系统上数据链路层的一种原始接口，提供原始链路层封包的收发，除此之外，如果网卡驱动支持洪泛模式，那么它可以让网卡处于此种模式，这样可以收到网络上的所有包，不管他们的目的地是不是所在主机。">eBPF</a> 加速 Istio 服务网格的插件。使用 Merbridge 可以在一定程度上优化数据平面的网络性能。</p>
|
||
<p>Merbridge 利用 <a href="../GLOSSARY.html#ebpf" class="glossary-term" title="eBPF 是扩展的柏克莱封包过滤器（extented Berkeley Packet Filter）的缩写，它是类 Unix 系统上数据链路层的一种原始接口，提供原始链路层封包的收发，除此之外，如果网卡驱动支持洪泛模式，那么它可以让网卡处于此种模式，这样可以收到网络上的所有包，不管他们的目的地是不是所在主机。">eBPF</a> 的 sockops 和 redir 能力，可以直接将数据包从 inbound socket 传输到 outbound socket。<a href="../GLOSSARY.html#ebpf" class="glossary-term" title="eBPF 是扩展的柏克莱封包过滤器（extented Berkeley Packet Filter）的缩写，它是类 Unix 系统上数据链路层的一种原始接口，提供原始链路层封包的收发，除此之外，如果网卡驱动支持洪泛模式，那么它可以让网卡处于此种模式，这样可以收到网络上的所有包，不管他们的目的地是不是所在主机。">eBPF</a> 提供了 <code>bpf_msg_redirect_hash</code> 函数可以直接转发应用程序的数据包。</p>
|
||
<p>详见 <a href="https://jimmysong.io/istio-handbook/ecosystem/merbridge.html" target="_blank">Istio 服务网格 —— 云原生应用网络构建指南</a>。</p>
|
||
<p><strong>使用 tproxy 处理 inbound 流量</strong></p>
|
||
<p>tproxy 可以用于 inbound 流量的重定向，且无需改变报文中的目的 IP/端口，不需要执行连接跟踪，不会出现 conntrack 模块创建大量连接的问题。受限于内核版本，tproxy 应用于 outbound 存在一定缺陷。目前 Istio 支持通过 tproxy 处理 inbound 流量。</p>
|
||
<p><strong>使用 hook connect 处理 outbound 流量</strong></p>
|
||
<p>为了适配更多应用场景，outbound 方向通过 hook connect 来实现，实现原理如下：</p>
|
||
<figure id="fig7.3.4.5"><a href="../images/hook-connect.jpg" data-lightbox="d3c689b0-0dd2-4244-a247-e5bea7c4c00c" data-title="hook-connect 原理示意图"><img src="../images/hook-connect.jpg" alt="hook-connect 原理示意图"></a><figcaption>图 7.3.4.5：hook-connect 原理示意图</figcaption></figure>
|
||
<p>无论采用哪种透明劫持方案，均需要解决获取真实目的 IP/端口的问题，使用 iptables 方案通过 getsockopt 方式获取，tproxy 可以直接读取目的地址，通过修改调用接口，hook connect 方案读取方式类似于tproxy。</p>
|
||
<p>实现透明劫持后，在内核版本满足要求（4.16以上）的前提下，通过 sockmap 可以缩短报文穿越路径，进而改善 outbound 方向的转发性能。</p>
|
||
<h2 id="参考">参考</h2>
|
||
<ul>
|
||
<li><a href="https://istio.io/docs/ops/diagnostic-tools/proxy-cmd/" target="_blank">Debugging Envoy and Istiod - istio.io</a></li>
|
||
<li><a href="https://istio.io/latest/zh/blog/2019/data-plane-setup/" target="_blank">揭开 Istio Sidecar 注入模型的神秘面纱 - istio.io</a></li>
|
||
<li><a href="https://mosn.io/docs/products/structure/traffic-hijack/" target="_blank">MOSN 作为 Sidecar 使用时的流量劫持方案 - mosn.io</a></li>
|
||
<li><a href="https://jimmysong.io/blog/sidecar-injection-iptables-and-traffic-routing/" target="_blank">Istio 中的 Sidecar 注入、透明流量劫持及流量路由过程详解 - jimmysong.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-05-11 04:24:00
|
||
</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="sidecar-spec-in-istio.html" class="navigation navigation-prev " aria-label="Previous page: Istio 中 sidecar 的注入规范">
|
||
<i class="fa fa-angle-left"></i>
|
||
</a>
|
||
|
||
|
||
<a href="istio-traffic-routing.html" class="navigation navigation-next " aria-label="Next page: Istio 中的流量路由过程详解">
|
||
<i class="fa fa-angle-right"></i>
|
||
</a>
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<script>
|
||
var gitbook = gitbook || [];
|
||
gitbook.push(function() {
|
||
gitbook.page.hasChanged({"page":{"title":"Sidecar 的注入与透明流量劫持","level":"7.3.4","depth":2,"next":{"title":"Istio 中的流量路由过程详解","level":"7.3.5","depth":2,"path":"usecases/istio-traffic-routing.md","ref":"usecases/istio-traffic-routing.md","articles":[]},"previous":{"title":"Istio 中 sidecar 的注入规范","level":"7.3.3","depth":2,"path":"usecases/sidecar-spec-in-istio.md","ref":"usecases/sidecar-spec-in-istio.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/docs/","云原生开源项目大全":"https://jimmysong.io/awesome-cloud-native/","云原生社区":"https://cloudnative.to"}},"gitbook":"*","description":"Kubernetes Handbook - Kubernetes 中文指南/云原生应用架构实战手册，本书记录了本人从零开始学习和使用 Kubernetes 的心路历程，着重于经验分享和总结，同时也会有相关的概念解析，希望能够帮助大家少踩坑，少走弯路，还会指引大家关注Kubernetes生态周边，如微服务构建、DevOps、大数据应用、Service Mesh、Cloud Native等领域。"},"file":{"path":"usecases/understand-sidecar-injection-and-traffic-hijack-in-istio-service-mesh.md","mtime":"2022-05-11T04:24:00.221Z","type":"markdown"},"gitbook":{"version":"3.2.3","time":"2022-05-11T04:24:30.193Z"},"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>
|
||
|