4605 lines
258 KiB
HTML
4605 lines
258 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>Istio 教程 · Kubernetes Handbook - jimmysong.io</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-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="linkerd.html" />
|
||
|
||
|
||
<link rel="prev" href="istio-community-tips.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">Jimmy Song</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="chapter " data-level="1.2" data-path="../cloud-native/cncf.html">
|
||
|
||
<a href="../cloud-native/cncf.html">
|
||
|
||
|
||
<b>1.2.</b>
|
||
|
||
CNCF - 云原生计算基金会简介
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">云原生</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="2.1" data-path="../cloud-native/play-with-kubernetes.html">
|
||
|
||
<a href="../cloud-native/play-with-kubernetes.html">
|
||
|
||
|
||
<b>2.1.</b>
|
||
|
||
Play with Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.2" data-path="../cloud-native/kubernetes-and-cloud-native-app-overview.html">
|
||
|
||
<a href="../cloud-native/kubernetes-and-cloud-native-app-overview.html">
|
||
|
||
|
||
<b>2.2.</b>
|
||
|
||
Kubernetes与云原生应用概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.3" data-path="../cloud-native/from-kubernetes-to-cloud-native.html">
|
||
|
||
<a href="../cloud-native/from-kubernetes-to-cloud-native.html">
|
||
|
||
|
||
<b>2.3.</b>
|
||
|
||
云原生应用之路——从Kubernetes到Cloud Native
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.4" data-path="../cloud-native/cloud-native-programming-languages.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-languages.html">
|
||
|
||
|
||
<b>2.4.</b>
|
||
|
||
云原生编程语言
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="2.4.1" data-path="../cloud-native/cloud-native-programming-language-ballerina.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-language-ballerina.html">
|
||
|
||
|
||
<b>2.4.1.</b>
|
||
|
||
云原生编程语言Ballerina
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.4.2" data-path="../cloud-native/cloud-native-programming-language-pulumi.html">
|
||
|
||
<a href="../cloud-native/cloud-native-programming-language-pulumi.html">
|
||
|
||
|
||
<b>2.4.2.</b>
|
||
|
||
云原生编程语言Pulumi
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="2.5" data-path="../cloud-native/the-future-of-cloud-native.html">
|
||
|
||
<a href="../cloud-native/the-future-of-cloud-native.html">
|
||
|
||
|
||
<b>2.5.</b>
|
||
|
||
云原生的未来
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">概念与原理</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="3.1" data-path="../concepts/">
|
||
|
||
<a href="../concepts/">
|
||
|
||
|
||
<b>3.1.</b>
|
||
|
||
Kubernetes架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.1.1" data-path="../concepts/concepts.html">
|
||
|
||
<a href="../concepts/concepts.html">
|
||
|
||
|
||
<b>3.1.1.</b>
|
||
|
||
设计理念
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.1.2" data-path="../concepts/etcd.html">
|
||
|
||
<a href="../concepts/etcd.html">
|
||
|
||
|
||
<b>3.1.2.</b>
|
||
|
||
Etcd解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.1.3" data-path="../concepts/open-interfaces.html">
|
||
|
||
<a href="../concepts/open-interfaces.html">
|
||
|
||
|
||
<b>3.1.3.</b>
|
||
|
||
开放接口
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.1.3.1" data-path="../concepts/cri.html">
|
||
|
||
<a href="../concepts/cri.html">
|
||
|
||
|
||
<b>3.1.3.1.</b>
|
||
|
||
CRI - Container Runtime Interface（容器运行时接口）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.1.3.2" data-path="../concepts/cni.html">
|
||
|
||
<a href="../concepts/cni.html">
|
||
|
||
|
||
<b>3.1.3.2.</b>
|
||
|
||
CNI - Container Network Interface（容器网络接口）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.1.3.3" data-path="../concepts/csi.html">
|
||
|
||
<a href="../concepts/csi.html">
|
||
|
||
|
||
<b>3.1.3.3.</b>
|
||
|
||
CSI - Container Storage Interface（容器存储接口）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.2" >
|
||
|
||
<span>
|
||
|
||
|
||
<b>3.2.</b>
|
||
|
||
Kubernetes中的网络
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.2.1" data-path="../concepts/networking.html">
|
||
|
||
<a href="../concepts/networking.html">
|
||
|
||
|
||
<b>3.2.1.</b>
|
||
|
||
Kubernetes中的网络解析——以flannel为例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.2.2" data-path="../concepts/calico.html">
|
||
|
||
<a href="../concepts/calico.html">
|
||
|
||
|
||
<b>3.2.2.</b>
|
||
|
||
Kubernetes中的网络解析——以calico为例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.3" data-path="../concepts/objects.html">
|
||
|
||
<a href="../concepts/objects.html">
|
||
|
||
|
||
<b>3.3.</b>
|
||
|
||
资源对象与基本概念解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4" data-path="../concepts/pod-state-and-lifecycle.html">
|
||
|
||
<a href="../concepts/pod-state-and-lifecycle.html">
|
||
|
||
|
||
<b>3.4.</b>
|
||
|
||
Pod状态与生命周期管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.4.1" data-path="../concepts/pod-overview.html">
|
||
|
||
<a href="../concepts/pod-overview.html">
|
||
|
||
|
||
<b>3.4.1.</b>
|
||
|
||
Pod概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.2" data-path="../concepts/pod.html">
|
||
|
||
<a href="../concepts/pod.html">
|
||
|
||
|
||
<b>3.4.2.</b>
|
||
|
||
Pod解析
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.3" data-path="../concepts/init-containers.html">
|
||
|
||
<a href="../concepts/init-containers.html">
|
||
|
||
|
||
<b>3.4.3.</b>
|
||
|
||
Init容器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.4" data-path="../concepts/pause-container.html">
|
||
|
||
<a href="../concepts/pause-container.html">
|
||
|
||
|
||
<b>3.4.4.</b>
|
||
|
||
Pause容器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.5" data-path="../concepts/pod-security-policy.html">
|
||
|
||
<a href="../concepts/pod-security-policy.html">
|
||
|
||
|
||
<b>3.4.5.</b>
|
||
|
||
Pod安全策略
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.6" data-path="../concepts/pod-lifecycle.html">
|
||
|
||
<a href="../concepts/pod-lifecycle.html">
|
||
|
||
|
||
<b>3.4.6.</b>
|
||
|
||
Pod的生命周期
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.7" data-path="../concepts/pod-hook.html">
|
||
|
||
<a href="../concepts/pod-hook.html">
|
||
|
||
|
||
<b>3.4.7.</b>
|
||
|
||
Pod Hook
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.8" data-path="../concepts/pod-preset.html">
|
||
|
||
<a href="../concepts/pod-preset.html">
|
||
|
||
|
||
<b>3.4.8.</b>
|
||
|
||
Pod Preset
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.4.9" data-path="../concepts/pod-disruption-budget.html">
|
||
|
||
<a href="../concepts/pod-disruption-budget.html">
|
||
|
||
|
||
<b>3.4.9.</b>
|
||
|
||
Pod中断与PDB（Pod中断预算）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5" data-path="../concepts/cluster.html">
|
||
|
||
<a href="../concepts/cluster.html">
|
||
|
||
|
||
<b>3.5.</b>
|
||
|
||
集群资源管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.5.1" data-path="../concepts/node.html">
|
||
|
||
<a href="../concepts/node.html">
|
||
|
||
|
||
<b>3.5.1.</b>
|
||
|
||
Node
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5.2" data-path="../concepts/namespace.html">
|
||
|
||
<a href="../concepts/namespace.html">
|
||
|
||
|
||
<b>3.5.2.</b>
|
||
|
||
Namespace
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5.3" data-path="../concepts/label.html">
|
||
|
||
<a href="../concepts/label.html">
|
||
|
||
|
||
<b>3.5.3.</b>
|
||
|
||
Label
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5.4" data-path="../concepts/annotation.html">
|
||
|
||
<a href="../concepts/annotation.html">
|
||
|
||
|
||
<b>3.5.4.</b>
|
||
|
||
Annotation
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5.5" data-path="../concepts/taint-and-toleration.html">
|
||
|
||
<a href="../concepts/taint-and-toleration.html">
|
||
|
||
|
||
<b>3.5.5.</b>
|
||
|
||
Taint和Toleration（污点和容忍）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.5.6" data-path="../concepts/garbage-collection.html">
|
||
|
||
<a href="../concepts/garbage-collection.html">
|
||
|
||
|
||
<b>3.5.6.</b>
|
||
|
||
垃圾收集
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6" data-path="../concepts/controllers.html">
|
||
|
||
<a href="../concepts/controllers.html">
|
||
|
||
|
||
<b>3.6.</b>
|
||
|
||
控制器
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.6.1" data-path="../concepts/deployment.html">
|
||
|
||
<a href="../concepts/deployment.html">
|
||
|
||
|
||
<b>3.6.1.</b>
|
||
|
||
Deployment
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.2" data-path="../concepts/statefulset.html">
|
||
|
||
<a href="../concepts/statefulset.html">
|
||
|
||
|
||
<b>3.6.2.</b>
|
||
|
||
StatefulSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.3" data-path="../concepts/daemonset.html">
|
||
|
||
<a href="../concepts/daemonset.html">
|
||
|
||
|
||
<b>3.6.3.</b>
|
||
|
||
DaemonSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.4" data-path="../concepts/replicaset.html">
|
||
|
||
<a href="../concepts/replicaset.html">
|
||
|
||
|
||
<b>3.6.4.</b>
|
||
|
||
ReplicationController和ReplicaSet
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.5" data-path="../concepts/job.html">
|
||
|
||
<a href="../concepts/job.html">
|
||
|
||
|
||
<b>3.6.5.</b>
|
||
|
||
Job
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.6" data-path="../concepts/cronjob.html">
|
||
|
||
<a href="../concepts/cronjob.html">
|
||
|
||
|
||
<b>3.6.6.</b>
|
||
|
||
CronJob
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.6.7" data-path="../concepts/horizontal-pod-autoscaling.html">
|
||
|
||
<a href="../concepts/horizontal-pod-autoscaling.html">
|
||
|
||
|
||
<b>3.6.7.</b>
|
||
|
||
Horizontal Pod Autoscaling
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.6.7.1" data-path="../concepts/custom-metrics-hpa.html">
|
||
|
||
<a href="../concepts/custom-metrics-hpa.html">
|
||
|
||
|
||
<b>3.6.7.1.</b>
|
||
|
||
自定义指标HPA
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.7" data-path="../concepts/service-discovery.html">
|
||
|
||
<a href="../concepts/service-discovery.html">
|
||
|
||
|
||
<b>3.7.</b>
|
||
|
||
服务发现
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.7.1" data-path="../concepts/service.html">
|
||
|
||
<a href="../concepts/service.html">
|
||
|
||
|
||
<b>3.7.1.</b>
|
||
|
||
Service
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.7.2" data-path="../concepts/ingress.html">
|
||
|
||
<a href="../concepts/ingress.html">
|
||
|
||
|
||
<b>3.7.2.</b>
|
||
|
||
Ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.7.2.1" data-path="../concepts/traefik-ingress-controller.html">
|
||
|
||
<a href="../concepts/traefik-ingress-controller.html">
|
||
|
||
|
||
<b>3.7.2.1.</b>
|
||
|
||
Traefik Ingress Controller
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.8" data-path="../concepts/authentication-and-permission.html">
|
||
|
||
<a href="../concepts/authentication-and-permission.html">
|
||
|
||
|
||
<b>3.8.</b>
|
||
|
||
身份与权限控制
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.8.1" data-path="../concepts/serviceaccount.html">
|
||
|
||
<a href="../concepts/serviceaccount.html">
|
||
|
||
|
||
<b>3.8.1.</b>
|
||
|
||
ServiceAccount
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.8.2" data-path="../concepts/rbac.html">
|
||
|
||
<a href="../concepts/rbac.html">
|
||
|
||
|
||
<b>3.8.2.</b>
|
||
|
||
RBAC——基于角色的访问控制
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.8.3" data-path="../concepts/network-policy.html">
|
||
|
||
<a href="../concepts/network-policy.html">
|
||
|
||
|
||
<b>3.8.3.</b>
|
||
|
||
NetworkPolicy
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9" data-path="../concepts/storage.html">
|
||
|
||
<a href="../concepts/storage.html">
|
||
|
||
|
||
<b>3.9.</b>
|
||
|
||
存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.9.1" data-path="../concepts/secret.html">
|
||
|
||
<a href="../concepts/secret.html">
|
||
|
||
|
||
<b>3.9.1.</b>
|
||
|
||
Secret
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9.2" data-path="../concepts/configmap.html">
|
||
|
||
<a href="../concepts/configmap.html">
|
||
|
||
|
||
<b>3.9.2.</b>
|
||
|
||
ConfigMap
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.9.2.1" data-path="../concepts/configmap-hot-update.html">
|
||
|
||
<a href="../concepts/configmap-hot-update.html">
|
||
|
||
|
||
<b>3.9.2.1.</b>
|
||
|
||
ConfigMap的热更新
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9.3" data-path="../concepts/volume.html">
|
||
|
||
<a href="../concepts/volume.html">
|
||
|
||
|
||
<b>3.9.3.</b>
|
||
|
||
Volume
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9.4" data-path="../concepts/persistent-volume.html">
|
||
|
||
<a href="../concepts/persistent-volume.html">
|
||
|
||
|
||
<b>3.9.4.</b>
|
||
|
||
Persistent Volume（持久化卷）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9.5" data-path="../concepts/storageclass.html">
|
||
|
||
<a href="../concepts/storageclass.html">
|
||
|
||
|
||
<b>3.9.5.</b>
|
||
|
||
Storage Class
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.9.6" data-path="../concepts/local-persistent-storage.html">
|
||
|
||
<a href="../concepts/local-persistent-storage.html">
|
||
|
||
|
||
<b>3.9.6.</b>
|
||
|
||
本地持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.10" data-path="../concepts/extension.html">
|
||
|
||
<a href="../concepts/extension.html">
|
||
|
||
|
||
<b>3.10.</b>
|
||
|
||
集群扩展
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="3.10.1" data-path="../concepts/custom-resource.html">
|
||
|
||
<a href="../concepts/custom-resource.html">
|
||
|
||
|
||
<b>3.10.1.</b>
|
||
|
||
使用自定义资源扩展API
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.10.2" data-path="../concepts/aggregated-api-server.html">
|
||
|
||
<a href="../concepts/aggregated-api-server.html">
|
||
|
||
|
||
<b>3.10.2.</b>
|
||
|
||
Aggregated API Server
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.10.3" data-path="../concepts/apiservice.html">
|
||
|
||
<a href="../concepts/apiservice.html">
|
||
|
||
|
||
<b>3.10.3.</b>
|
||
|
||
APIService
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.10.4" data-path="../concepts/service-catalog.html">
|
||
|
||
<a href="../concepts/service-catalog.html">
|
||
|
||
|
||
<b>3.10.4.</b>
|
||
|
||
Service Catalog
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="3.11" data-path="../concepts/scheduling.html">
|
||
|
||
<a href="../concepts/scheduling.html">
|
||
|
||
|
||
<b>3.11.</b>
|
||
|
||
资源调度
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">用户指南</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="4.1" data-path="../guide/">
|
||
|
||
<a href="../guide/">
|
||
|
||
|
||
<b>4.1.</b>
|
||
|
||
用户指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2" data-path="../guide/resource-configuration.html">
|
||
|
||
<a href="../guide/resource-configuration.html">
|
||
|
||
|
||
<b>4.2.</b>
|
||
|
||
资源对象配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.2.1" data-path="../guide/configure-liveness-readiness-probes.html">
|
||
|
||
<a href="../guide/configure-liveness-readiness-probes.html">
|
||
|
||
|
||
<b>4.2.1.</b>
|
||
|
||
配置Pod的liveness和readiness探针
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.2" data-path="../guide/configure-pod-service-account.html">
|
||
|
||
<a href="../guide/configure-pod-service-account.html">
|
||
|
||
|
||
<b>4.2.2.</b>
|
||
|
||
配置Pod的Service Account
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.3" data-path="../guide/secret-configuration.html">
|
||
|
||
<a href="../guide/secret-configuration.html">
|
||
|
||
|
||
<b>4.2.3.</b>
|
||
|
||
Secret配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.2.4" data-path="../guide/resource-quota-management.html">
|
||
|
||
<a href="../guide/resource-quota-management.html">
|
||
|
||
|
||
<b>4.2.4.</b>
|
||
|
||
管理namespace中的资源配额
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3" data-path="../guide/command-usage.html">
|
||
|
||
<a href="../guide/command-usage.html">
|
||
|
||
|
||
<b>4.3.</b>
|
||
|
||
命令使用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.3.1" data-path="../guide/docker-cli-to-kubectl.html">
|
||
|
||
<a href="../guide/docker-cli-to-kubectl.html">
|
||
|
||
|
||
<b>4.3.1.</b>
|
||
|
||
docker用户过度到kubectl命令行指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.2" data-path="../guide/using-kubectl.html">
|
||
|
||
<a href="../guide/using-kubectl.html">
|
||
|
||
|
||
<b>4.3.2.</b>
|
||
|
||
kubectl命令概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.3" data-path="../guide/kubectl-cheatsheet.html">
|
||
|
||
<a href="../guide/kubectl-cheatsheet.html">
|
||
|
||
|
||
<b>4.3.3.</b>
|
||
|
||
kubectl命令技巧大全
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.3.4" data-path="../guide/using-etcdctl-to-access-kubernetes-data.html">
|
||
|
||
<a href="../guide/using-etcdctl-to-access-kubernetes-data.html">
|
||
|
||
|
||
<b>4.3.4.</b>
|
||
|
||
使用etcdctl访问kubernetes数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4" data-path="../guide/cluster-security-management.html">
|
||
|
||
<a href="../guide/cluster-security-management.html">
|
||
|
||
|
||
<b>4.4.</b>
|
||
|
||
集群安全性管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.4.1" data-path="../guide/managing-tls-in-a-cluster.html">
|
||
|
||
<a href="../guide/managing-tls-in-a-cluster.html">
|
||
|
||
|
||
<b>4.4.1.</b>
|
||
|
||
管理集群中的TLS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.2" data-path="../guide/kubelet-authentication-authorization.html">
|
||
|
||
<a href="../guide/kubelet-authentication-authorization.html">
|
||
|
||
|
||
<b>4.4.2.</b>
|
||
|
||
kubelet的认证授权
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.3" data-path="../guide/tls-bootstrapping.html">
|
||
|
||
<a href="../guide/tls-bootstrapping.html">
|
||
|
||
|
||
<b>4.4.3.</b>
|
||
|
||
TLS bootstrap
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.4" data-path="../guide/kubectl-user-authentication-authorization.html">
|
||
|
||
<a href="../guide/kubectl-user-authentication-authorization.html">
|
||
|
||
|
||
<b>4.4.4.</b>
|
||
|
||
创建用户认证授权的kubeconfig文件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.5" data-path="../guide/ip-masq-agent.html">
|
||
|
||
<a href="../guide/ip-masq-agent.html">
|
||
|
||
|
||
<b>4.4.5.</b>
|
||
|
||
IP伪装代理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.6" data-path="../guide/auth-with-kubeconfig-or-token.html">
|
||
|
||
<a href="../guide/auth-with-kubeconfig-or-token.html">
|
||
|
||
|
||
<b>4.4.6.</b>
|
||
|
||
使用kubeconfig或token进行用户身份认证
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.7" data-path="../guide/authentication.html">
|
||
|
||
<a href="../guide/authentication.html">
|
||
|
||
|
||
<b>4.4.7.</b>
|
||
|
||
Kubernetes中的用户与身份认证授权
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.4.8" data-path="../guide/kubernetes-security-best-practice.html">
|
||
|
||
<a href="../guide/kubernetes-security-best-practice.html">
|
||
|
||
|
||
<b>4.4.8.</b>
|
||
|
||
Kubernetes集群安全性配置最佳实践
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5" data-path="../guide/access-kubernetes-cluster.html">
|
||
|
||
<a href="../guide/access-kubernetes-cluster.html">
|
||
|
||
|
||
<b>4.5.</b>
|
||
|
||
访问Kubernetes集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.5.1" data-path="../guide/access-cluster.html">
|
||
|
||
<a href="../guide/access-cluster.html">
|
||
|
||
|
||
<b>4.5.1.</b>
|
||
|
||
访问集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.2" data-path="../guide/authenticate-across-clusters-kubeconfig.html">
|
||
|
||
<a href="../guide/authenticate-across-clusters-kubeconfig.html">
|
||
|
||
|
||
<b>4.5.2.</b>
|
||
|
||
使用kubeconfig文件配置跨集群认证
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.3" data-path="../guide/connecting-to-applications-port-forward.html">
|
||
|
||
<a href="../guide/connecting-to-applications-port-forward.html">
|
||
|
||
|
||
<b>4.5.3.</b>
|
||
|
||
通过端口转发访问集群中的应用程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.4" data-path="../guide/service-access-application-cluster.html">
|
||
|
||
<a href="../guide/service-access-application-cluster.html">
|
||
|
||
|
||
<b>4.5.4.</b>
|
||
|
||
使用service访问群集中的应用程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.5" data-path="../guide/accessing-kubernetes-pods-from-outside-of-the-cluster.html">
|
||
|
||
<a href="../guide/accessing-kubernetes-pods-from-outside-of-the-cluster.html">
|
||
|
||
|
||
<b>4.5.5.</b>
|
||
|
||
从外部访问Kubernetes中的Pod
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.6" data-path="../guide/cabin-mobile-dashboard-for-kubernetes.html">
|
||
|
||
<a href="../guide/cabin-mobile-dashboard-for-kubernetes.html">
|
||
|
||
|
||
<b>4.5.6.</b>
|
||
|
||
Cabin - Kubernetes手机客户端
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.7" data-path="../guide/kubernetes-desktop-client.html">
|
||
|
||
<a href="../guide/kubernetes-desktop-client.html">
|
||
|
||
|
||
<b>4.5.7.</b>
|
||
|
||
Kubernetic - Kubernetes桌面客户端
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.5.8" data-path="../guide/kubernator-kubernetes-ui.html">
|
||
|
||
<a href="../guide/kubernator-kubernetes-ui.html">
|
||
|
||
|
||
<b>4.5.8.</b>
|
||
|
||
Kubernator - 更底层的Kubernetes UI
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6" data-path="../guide/application-development-deployment-flow.html">
|
||
|
||
<a href="../guide/application-development-deployment-flow.html">
|
||
|
||
|
||
<b>4.6.</b>
|
||
|
||
在Kubernetes中开发部署应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="4.6.1" data-path="../guide/deploy-applications-in-kubernetes.html">
|
||
|
||
<a href="../guide/deploy-applications-in-kubernetes.html">
|
||
|
||
|
||
<b>4.6.1.</b>
|
||
|
||
适用于kubernetes的应用开发部署流程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6.2" data-path="../guide/migrating-hadoop-yarn-to-kubernetes.html">
|
||
|
||
<a href="../guide/migrating-hadoop-yarn-to-kubernetes.html">
|
||
|
||
|
||
<b>4.6.2.</b>
|
||
|
||
迁移传统应用到Kubernetes中——以Hadoop YARN为例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="4.6.3" data-path="../guide/using-statefulset.html">
|
||
|
||
<a href="../guide/using-statefulset.html">
|
||
|
||
|
||
<b>4.6.3.</b>
|
||
|
||
使用StatefulSet部署用状态应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">最佳实践</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="5.1" data-path="../practice/">
|
||
|
||
<a href="../practice/">
|
||
|
||
|
||
<b>5.1.</b>
|
||
|
||
最佳实践概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2" data-path="../practice/install-kubernetes-on-centos.html">
|
||
|
||
<a href="../practice/install-kubernetes-on-centos.html">
|
||
|
||
|
||
<b>5.2.</b>
|
||
|
||
在CentOS上部署Kubernetes集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.2.1" data-path="../practice/create-tls-and-secret-key.html">
|
||
|
||
<a href="../practice/create-tls-and-secret-key.html">
|
||
|
||
|
||
<b>5.2.1.</b>
|
||
|
||
创建TLS证书和秘钥
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.2" data-path="../practice/create-kubeconfig.html">
|
||
|
||
<a href="../practice/create-kubeconfig.html">
|
||
|
||
|
||
<b>5.2.2.</b>
|
||
|
||
创建kubeconfig文件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.3" data-path="../practice/etcd-cluster-installation.html">
|
||
|
||
<a href="../practice/etcd-cluster-installation.html">
|
||
|
||
|
||
<b>5.2.3.</b>
|
||
|
||
创建高可用etcd集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.4" data-path="../practice/kubectl-installation.html">
|
||
|
||
<a href="../practice/kubectl-installation.html">
|
||
|
||
|
||
<b>5.2.4.</b>
|
||
|
||
安装kubectl命令行工具
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.5" data-path="../practice/master-installation.html">
|
||
|
||
<a href="../practice/master-installation.html">
|
||
|
||
|
||
<b>5.2.5.</b>
|
||
|
||
部署master节点
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.6" data-path="../practice/flannel-installation.html">
|
||
|
||
<a href="../practice/flannel-installation.html">
|
||
|
||
|
||
<b>5.2.6.</b>
|
||
|
||
安装flannel网络插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.7" data-path="../practice/node-installation.html">
|
||
|
||
<a href="../practice/node-installation.html">
|
||
|
||
|
||
<b>5.2.7.</b>
|
||
|
||
部署node节点
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.8" data-path="../practice/kubedns-addon-installation.html">
|
||
|
||
<a href="../practice/kubedns-addon-installation.html">
|
||
|
||
|
||
<b>5.2.8.</b>
|
||
|
||
安装kubedns插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.9" data-path="../practice/dashboard-addon-installation.html">
|
||
|
||
<a href="../practice/dashboard-addon-installation.html">
|
||
|
||
|
||
<b>5.2.9.</b>
|
||
|
||
安装dashboard插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.10" data-path="../practice/heapster-addon-installation.html">
|
||
|
||
<a href="../practice/heapster-addon-installation.html">
|
||
|
||
|
||
<b>5.2.10.</b>
|
||
|
||
安装heapster插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.2.11" data-path="../practice/efk-addon-installation.html">
|
||
|
||
<a href="../practice/efk-addon-installation.html">
|
||
|
||
|
||
<b>5.2.11.</b>
|
||
|
||
安装EFK插件
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.3" data-path="../practice/install-kubernetes-with-kubeadm.html">
|
||
|
||
<a href="../practice/install-kubernetes-with-kubeadm.html">
|
||
|
||
|
||
<b>5.3.</b>
|
||
|
||
使用kubeadm快速构建测试集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.3.1" data-path="../practice/install-kubernetes-on-ubuntu-server-16.04-with-kubeadm.html">
|
||
|
||
<a href="../practice/install-kubernetes-on-ubuntu-server-16.04-with-kubeadm.html">
|
||
|
||
|
||
<b>5.3.1.</b>
|
||
|
||
使用kubeadm在Ubuntu Server 16.04上快速构建测试集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4" data-path="../practice/service-discovery-and-loadbalancing.html">
|
||
|
||
<a href="../practice/service-discovery-and-loadbalancing.html">
|
||
|
||
|
||
<b>5.4.</b>
|
||
|
||
服务发现与负载均衡
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.4.1" data-path="../practice/traefik-ingress-installation.html">
|
||
|
||
<a href="../practice/traefik-ingress-installation.html">
|
||
|
||
|
||
<b>5.4.1.</b>
|
||
|
||
安装Traefik ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.2" data-path="../practice/distributed-load-test.html">
|
||
|
||
<a href="../practice/distributed-load-test.html">
|
||
|
||
|
||
<b>5.4.2.</b>
|
||
|
||
分布式负载测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.3" data-path="../practice/network-and-cluster-perfermance-test.html">
|
||
|
||
<a href="../practice/network-and-cluster-perfermance-test.html">
|
||
|
||
|
||
<b>5.4.3.</b>
|
||
|
||
网络和集群性能测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.4" data-path="../practice/edge-node-configuration.html">
|
||
|
||
<a href="../practice/edge-node-configuration.html">
|
||
|
||
|
||
<b>5.4.4.</b>
|
||
|
||
边缘节点配置
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.5" data-path="../practice/nginx-ingress-installation.html">
|
||
|
||
<a href="../practice/nginx-ingress-installation.html">
|
||
|
||
|
||
<b>5.4.5.</b>
|
||
|
||
安装Nginx ingress
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.6" data-path="../practice/dns-installation.html">
|
||
|
||
<a href="../practice/dns-installation.html">
|
||
|
||
|
||
<b>5.4.6.</b>
|
||
|
||
安装配置DNS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.4.6.1" data-path="../practice/configuring-dns.html">
|
||
|
||
<a href="../practice/configuring-dns.html">
|
||
|
||
|
||
<b>5.4.6.1.</b>
|
||
|
||
安装配置Kube-dns
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.4.6.2" data-path="../practice/coredns.html">
|
||
|
||
<a href="../practice/coredns.html">
|
||
|
||
|
||
<b>5.4.6.2.</b>
|
||
|
||
安装配置CoreDNS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5" data-path="../practice/operation.html">
|
||
|
||
<a href="../practice/operation.html">
|
||
|
||
|
||
<b>5.5.</b>
|
||
|
||
运维管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.5.1" data-path="../practice/master-ha.html">
|
||
|
||
<a href="../practice/master-ha.html">
|
||
|
||
|
||
<b>5.5.1.</b>
|
||
|
||
Master节点高可用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.2" data-path="../practice/service-rolling-update.html">
|
||
|
||
<a href="../practice/service-rolling-update.html">
|
||
|
||
|
||
<b>5.5.2.</b>
|
||
|
||
服务滚动升级
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.3" data-path="../practice/app-log-collection.html">
|
||
|
||
<a href="../practice/app-log-collection.html">
|
||
|
||
|
||
<b>5.5.3.</b>
|
||
|
||
应用日志收集
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.4" data-path="../practice/configuration-best-practice.html">
|
||
|
||
<a href="../practice/configuration-best-practice.html">
|
||
|
||
|
||
<b>5.5.4.</b>
|
||
|
||
配置最佳实践
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.5" data-path="../practice/monitor.html">
|
||
|
||
<a href="../practice/monitor.html">
|
||
|
||
|
||
<b>5.5.5.</b>
|
||
|
||
集群及应用监控
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.6" data-path="../practice/data-persistence-problem.html">
|
||
|
||
<a href="../practice/data-persistence-problem.html">
|
||
|
||
|
||
<b>5.5.6.</b>
|
||
|
||
数据持久化问题
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.7" data-path="../practice/manage-compute-resources-container.html">
|
||
|
||
<a href="../practice/manage-compute-resources-container.html">
|
||
|
||
|
||
<b>5.5.7.</b>
|
||
|
||
管理容器的计算资源
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.5.8" data-path="../practice/federation.html">
|
||
|
||
<a href="../practice/federation.html">
|
||
|
||
|
||
<b>5.5.8.</b>
|
||
|
||
集群联邦
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6" data-path="../practice/storage.html">
|
||
|
||
<a href="../practice/storage.html">
|
||
|
||
|
||
<b>5.6.</b>
|
||
|
||
存储管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.1" data-path="../practice/glusterfs.html">
|
||
|
||
<a href="../practice/glusterfs.html">
|
||
|
||
|
||
<b>5.6.1.</b>
|
||
|
||
GlusterFS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.1.1" data-path="../practice/using-glusterfs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-glusterfs-for-persistent-storage.html">
|
||
|
||
|
||
<b>5.6.1.1.</b>
|
||
|
||
使用GlusterFS做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.1.2" data-path="../practice/using-heketi-gluster-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-heketi-gluster-for-persistent-storage.html">
|
||
|
||
|
||
<b>5.6.1.2.</b>
|
||
|
||
使用Heketi作为kubernetes的持久存储GlusterFS的external provisioner
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.1.3" data-path="../practice/storage-for-containers-using-glusterfs-with-openshift.html">
|
||
|
||
<a href="../practice/storage-for-containers-using-glusterfs-with-openshift.html">
|
||
|
||
|
||
<b>5.6.1.3.</b>
|
||
|
||
在OpenShift中使用GlusterFS做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.2" data-path="../practice/glusterd-2.0.html">
|
||
|
||
<a href="../practice/glusterd-2.0.html">
|
||
|
||
|
||
<b>5.6.2.</b>
|
||
|
||
GlusterD-2.0
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.3" data-path="../practice/ceph.html">
|
||
|
||
<a href="../practice/ceph.html">
|
||
|
||
|
||
<b>5.6.3.</b>
|
||
|
||
Ceph
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.3.1" data-path="../practice/ceph-helm-install-guide-zh.html">
|
||
|
||
<a href="../practice/ceph-helm-install-guide-zh.html">
|
||
|
||
|
||
<b>5.6.3.1.</b>
|
||
|
||
用Helm托管安装Ceph集群并提供后端存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.3.2" data-path="../practice/using-ceph-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-ceph-for-persistent-storage.html">
|
||
|
||
|
||
<b>5.6.3.2.</b>
|
||
|
||
使用Ceph做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.4" data-path="../practice/openebs.html">
|
||
|
||
<a href="../practice/openebs.html">
|
||
|
||
|
||
<b>5.6.4.</b>
|
||
|
||
OpenEBS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.4.1" data-path="../practice/using-openebs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-openebs-for-persistent-storage.html">
|
||
|
||
|
||
<b>5.6.4.1.</b>
|
||
|
||
使用OpenEBS做持久化存储
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.5" data-path="../practice/rook.html">
|
||
|
||
<a href="../practice/rook.html">
|
||
|
||
|
||
<b>5.6.5.</b>
|
||
|
||
Rook
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.6.6" data-path="../practice/nfs.html">
|
||
|
||
<a href="../practice/nfs.html">
|
||
|
||
|
||
<b>5.6.6.</b>
|
||
|
||
NFS
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.6.6.1" data-path="../practice/using-nfs-for-persistent-storage.html">
|
||
|
||
<a href="../practice/using-nfs-for-persistent-storage.html">
|
||
|
||
|
||
<b>5.6.6.1.</b>
|
||
|
||
利用NFS动态提供Kubernetes后端存储卷
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.7" data-path="../practice/monitoring.html">
|
||
|
||
<a href="../practice/monitoring.html">
|
||
|
||
|
||
<b>5.7.</b>
|
||
|
||
集群与应用监控
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.7.1" data-path="../practice/heapster.html">
|
||
|
||
<a href="../practice/heapster.html">
|
||
|
||
|
||
<b>5.7.1.</b>
|
||
|
||
Heapster
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.7.1.1" data-path="../practice/using-heapster-to-get-object-metrics.html">
|
||
|
||
<a href="../practice/using-heapster-to-get-object-metrics.html">
|
||
|
||
|
||
<b>5.7.1.1.</b>
|
||
|
||
使用Heapster获取集群和对象的metric数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.7.2" data-path="../practice/prometheus.html">
|
||
|
||
<a href="../practice/prometheus.html">
|
||
|
||
|
||
<b>5.7.2.</b>
|
||
|
||
Prometheus
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.7.2.1" data-path="../practice/using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
||
<a href="../practice/using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
||
|
||
<b>5.7.2.1.</b>
|
||
|
||
使用Prometheus监控kubernetes集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.7.3" data-path="../practice/vistio-visualize-your-istio-mesh.html">
|
||
|
||
<a href="../practice/vistio-visualize-your-istio-mesh.html">
|
||
|
||
|
||
<b>5.7.3.</b>
|
||
|
||
使用Vistio监控Istio服务网格中的流量
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.8" data-path="../practice/services-management-tool.html">
|
||
|
||
<a href="../practice/services-management-tool.html">
|
||
|
||
|
||
<b>5.8.</b>
|
||
|
||
服务编排管理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.8.1" data-path="../practice/helm.html">
|
||
|
||
<a href="../practice/helm.html">
|
||
|
||
|
||
<b>5.8.1.</b>
|
||
|
||
使用Helm管理kubernetes应用
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.8.2" data-path="../practice/create-private-charts-repo.html">
|
||
|
||
<a href="../practice/create-private-charts-repo.html">
|
||
|
||
|
||
<b>5.8.2.</b>
|
||
|
||
构建私有Chart仓库
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.9" data-path="../practice/ci-cd.html">
|
||
|
||
<a href="../practice/ci-cd.html">
|
||
|
||
|
||
<b>5.9.</b>
|
||
|
||
持续集成与发布
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.9.1" data-path="../practice/jenkins-ci-cd.html">
|
||
|
||
<a href="../practice/jenkins-ci-cd.html">
|
||
|
||
|
||
<b>5.9.1.</b>
|
||
|
||
使用Jenkins进行持续集成与发布
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.9.2" data-path="../practice/drone-ci-cd.html">
|
||
|
||
<a href="../practice/drone-ci-cd.html">
|
||
|
||
|
||
<b>5.9.2.</b>
|
||
|
||
使用Drone进行持续集成与发布
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.10" data-path="../practice/update-and-upgrade.html">
|
||
|
||
<a href="../practice/update-and-upgrade.html">
|
||
|
||
|
||
<b>5.10.</b>
|
||
|
||
更新与升级
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="5.10.1" data-path="../practice/manually-upgrade.html">
|
||
|
||
<a href="../practice/manually-upgrade.html">
|
||
|
||
|
||
<b>5.10.1.</b>
|
||
|
||
手动升级Kubernetes集群
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="5.10.2" data-path="../practice/dashboard-upgrade.html">
|
||
|
||
<a href="../practice/dashboard-upgrade.html">
|
||
|
||
|
||
<b>5.10.2.</b>
|
||
|
||
升级dashboard
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">领域应用</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="6.1" data-path="./">
|
||
|
||
<a href="./">
|
||
|
||
|
||
<b>6.1.</b>
|
||
|
||
领域应用概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2" data-path="microservices.html">
|
||
|
||
<a href="microservices.html">
|
||
|
||
|
||
<b>6.2.</b>
|
||
|
||
微服务架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.2.1" data-path="service-discovery-in-microservices.html">
|
||
|
||
<a href="service-discovery-in-microservices.html">
|
||
|
||
|
||
<b>6.2.1.</b>
|
||
|
||
微服务中的服务发现
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.2.2" data-path="microservices-for-java-developers.html">
|
||
|
||
<a href="microservices-for-java-developers.html">
|
||
|
||
|
||
<b>6.2.2.</b>
|
||
|
||
使用Java构建微服务并发布到Kubernetes平台
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.2.2.1" data-path="spring-boot-quick-start-guide.html">
|
||
|
||
<a href="spring-boot-quick-start-guide.html">
|
||
|
||
|
||
<b>6.2.2.1.</b>
|
||
|
||
Spring Boot快速开始指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3" data-path="service-mesh.html">
|
||
|
||
<a href="service-mesh.html">
|
||
|
||
|
||
<b>6.3.</b>
|
||
|
||
Service Mesh 服务网格
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.3.1" data-path="istio.html">
|
||
|
||
<a href="istio.html">
|
||
|
||
|
||
<b>6.3.1.</b>
|
||
|
||
Istio
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.3.1.1" data-path="istio-installation.html">
|
||
|
||
<a href="istio-installation.html">
|
||
|
||
|
||
<b>6.3.1.1.</b>
|
||
|
||
安装并试用Istio service mesh
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3.1.2" data-path="configuring-request-routing.html">
|
||
|
||
<a href="configuring-request-routing.html">
|
||
|
||
|
||
<b>6.3.1.2.</b>
|
||
|
||
配置请求的路由规则
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3.1.3" data-path="install-and-expand-istio-mesh.html">
|
||
|
||
<a href="install-and-expand-istio-mesh.html">
|
||
|
||
|
||
<b>6.3.1.3.</b>
|
||
|
||
安装和拓展Istio service mesh
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3.1.4" data-path="integrating-vms.html">
|
||
|
||
<a href="integrating-vms.html">
|
||
|
||
|
||
<b>6.3.1.4.</b>
|
||
|
||
集成虚拟机
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3.1.5" data-path="sidecar-spec-in-istio.html">
|
||
|
||
<a href="sidecar-spec-in-istio.html">
|
||
|
||
|
||
<b>6.3.1.5.</b>
|
||
|
||
Istio中sidecar的注入规范及示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3.1.6" data-path="istio-community-tips.html">
|
||
|
||
<a href="istio-community-tips.html">
|
||
|
||
|
||
<b>6.3.1.6.</b>
|
||
|
||
如何参与Istio社区及注意事项
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter active" data-level="6.3.1.7" data-path="istio-tutorial.html">
|
||
|
||
<a href="istio-tutorial.html">
|
||
|
||
|
||
<b>6.3.1.7.</b>
|
||
|
||
Istio 教程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3.2" data-path="linkerd.html">
|
||
|
||
<a href="linkerd.html">
|
||
|
||
|
||
<b>6.3.2.</b>
|
||
|
||
Linkerd
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.3.2.1" data-path="linkerd-user-guide.html">
|
||
|
||
<a href="linkerd-user-guide.html">
|
||
|
||
|
||
<b>6.3.2.1.</b>
|
||
|
||
Linkerd 使用指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3.3" data-path="conduit.html">
|
||
|
||
<a href="conduit.html">
|
||
|
||
|
||
<b>6.3.3.</b>
|
||
|
||
Conduit
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.3.3.1" data-path="conduit-overview.html">
|
||
|
||
<a href="conduit-overview.html">
|
||
|
||
|
||
<b>6.3.3.1.</b>
|
||
|
||
Condiut概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3.3.2" data-path="conduit-installation.html">
|
||
|
||
<a href="conduit-installation.html">
|
||
|
||
|
||
<b>6.3.3.2.</b>
|
||
|
||
安装Conduit
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3.4" data-path="envoy.html">
|
||
|
||
<a href="envoy.html">
|
||
|
||
|
||
<b>6.3.4.</b>
|
||
|
||
Envoy
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.3.4.1" data-path="envoy-terminology.html">
|
||
|
||
<a href="envoy-terminology.html">
|
||
|
||
|
||
<b>6.3.4.1.</b>
|
||
|
||
Envoy的架构与基本术语
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3.4.2" data-path="envoy-front-proxy.html">
|
||
|
||
<a href="envoy-front-proxy.html">
|
||
|
||
|
||
<b>6.3.4.2.</b>
|
||
|
||
Envoy作为前端代理
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.3.4.3" data-path="envoy-mesh-in-kubernetes-tutorial.html">
|
||
|
||
<a href="envoy-mesh-in-kubernetes-tutorial.html">
|
||
|
||
|
||
<b>6.3.4.3.</b>
|
||
|
||
Envoy mesh教程
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4" data-path="big-data.html">
|
||
|
||
<a href="big-data.html">
|
||
|
||
|
||
<b>6.4.</b>
|
||
|
||
大数据
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.4.1" data-path="spark-standalone-on-kubernetes.html">
|
||
|
||
<a href="spark-standalone-on-kubernetes.html">
|
||
|
||
|
||
<b>6.4.1.</b>
|
||
|
||
Spark standalone on Kubernetes
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.4.2" data-path="running-spark-with-kubernetes-native-scheduler.html">
|
||
|
||
<a href="running-spark-with-kubernetes-native-scheduler.html">
|
||
|
||
|
||
<b>6.4.2.</b>
|
||
|
||
运行支持Kubernetes原生调度的Spark程序
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5" data-path="serverless.html">
|
||
|
||
<a href="serverless.html">
|
||
|
||
|
||
<b>6.5.</b>
|
||
|
||
Serverless架构
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.5.1" data-path="understanding-serverless.html">
|
||
|
||
<a href="understanding-serverless.html">
|
||
|
||
|
||
<b>6.5.1.</b>
|
||
|
||
理解Serverless
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.5.2" data-path="faas.html">
|
||
|
||
<a href="faas.html">
|
||
|
||
|
||
<b>6.5.2.</b>
|
||
|
||
FaaS-函数即服务
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="6.5.2.1" data-path="openfaas-quick-start.html">
|
||
|
||
<a href="openfaas-quick-start.html">
|
||
|
||
|
||
<b>6.5.2.1.</b>
|
||
|
||
OpenFaaS快速入门指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.6" data-path="edge-computing.html">
|
||
|
||
<a href="edge-computing.html">
|
||
|
||
|
||
<b>6.6.</b>
|
||
|
||
边缘计算
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="6.7" data-path="ai.html">
|
||
|
||
<a href="ai.html">
|
||
|
||
|
||
<b>6.7.</b>
|
||
|
||
人工智能
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">开发指南</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="7.1" data-path="../develop/">
|
||
|
||
<a href="../develop/">
|
||
|
||
|
||
<b>7.1.</b>
|
||
|
||
开发指南概览
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.2" data-path="../develop/sigs-and-working-group.html">
|
||
|
||
<a href="../develop/sigs-and-working-group.html">
|
||
|
||
|
||
<b>7.2.</b>
|
||
|
||
SIG和工作组
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.3" data-path="../develop/developing-environment.html">
|
||
|
||
<a href="../develop/developing-environment.html">
|
||
|
||
|
||
<b>7.3.</b>
|
||
|
||
开发环境搭建
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.4" data-path="../develop/using-vagrant-and-virtualbox-for-development.html">
|
||
|
||
<a href="../develop/using-vagrant-and-virtualbox-for-development.html">
|
||
|
||
|
||
<b>7.4.</b>
|
||
|
||
本地分布式开发环境搭建（使用Vagrant和Virtualbox）
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.5" data-path="../develop/testing.html">
|
||
|
||
<a href="../develop/testing.html">
|
||
|
||
|
||
<b>7.5.</b>
|
||
|
||
单元测试和集成测试
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.6" data-path="../develop/client-go-sample.html">
|
||
|
||
<a href="../develop/client-go-sample.html">
|
||
|
||
|
||
<b>7.6.</b>
|
||
|
||
client-go示例
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.7" data-path="../develop/operator.html">
|
||
|
||
<a href="../develop/operator.html">
|
||
|
||
|
||
<b>7.7.</b>
|
||
|
||
Operator
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.8" data-path="../develop/operator-sdk.html">
|
||
|
||
<a href="../develop/operator-sdk.html">
|
||
|
||
|
||
<b>7.8.</b>
|
||
|
||
operator-sdk
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.9" data-path="../develop/advance-developer.html">
|
||
|
||
<a href="../develop/advance-developer.html">
|
||
|
||
|
||
<b>7.9.</b>
|
||
|
||
高级开发指南
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.10" data-path="../develop/contribute.html">
|
||
|
||
<a href="../develop/contribute.html">
|
||
|
||
|
||
<b>7.10.</b>
|
||
|
||
社区贡献
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="7.11" data-path="../develop/minikube.html">
|
||
|
||
<a href="../develop/minikube.html">
|
||
|
||
|
||
<b>7.11.</b>
|
||
|
||
Minikube
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="header">附录</li>
|
||
|
||
|
||
|
||
<li class="chapter " data-level="8.1" data-path="../appendix/">
|
||
|
||
<a href="../appendix/">
|
||
|
||
|
||
<b>8.1.</b>
|
||
|
||
附录说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.2" data-path="../appendix/debug-kubernetes-services.html">
|
||
|
||
<a href="../appendix/debug-kubernetes-services.html">
|
||
|
||
|
||
<b>8.2.</b>
|
||
|
||
Kubernetes中的应用故障排查
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.3" data-path="../appendix/material-share.html">
|
||
|
||
<a href="../appendix/material-share.html">
|
||
|
||
|
||
<b>8.3.</b>
|
||
|
||
Kubernetes相关资讯和情报链接
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.4" data-path="../appendix/docker-best-practice.html">
|
||
|
||
<a href="../appendix/docker-best-practice.html">
|
||
|
||
|
||
<b>8.4.</b>
|
||
|
||
Docker最佳实践
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.5" data-path="../appendix/tricks.html">
|
||
|
||
<a href="../appendix/tricks.html">
|
||
|
||
|
||
<b>8.5.</b>
|
||
|
||
使用技巧
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.6" data-path="../appendix/issues.html">
|
||
|
||
<a href="../appendix/issues.html">
|
||
|
||
|
||
<b>8.6.</b>
|
||
|
||
问题记录
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.7" data-path="../appendix/kubernetes-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-changelog.html">
|
||
|
||
|
||
<b>8.7.</b>
|
||
|
||
Kubernetes版本更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.7.1" data-path="../appendix/kubernetes-1.7-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.7-changelog.html">
|
||
|
||
|
||
<b>8.7.1.</b>
|
||
|
||
Kubernetes1.7更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.7.2" data-path="../appendix/kubernetes-1.8-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.8-changelog.html">
|
||
|
||
|
||
<b>8.7.2.</b>
|
||
|
||
Kubernetes1.8更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.7.3" data-path="../appendix/kubernetes-1.9-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.9-changelog.html">
|
||
|
||
|
||
<b>8.7.3.</b>
|
||
|
||
Kubernetes1.9更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.7.4" data-path="../appendix/kubernetes-1.10-changelog.html">
|
||
|
||
<a href="../appendix/kubernetes-1.10-changelog.html">
|
||
|
||
|
||
<b>8.7.4.</b>
|
||
|
||
Kubernetes1.10更新日志
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.8" data-path="../appendix/summary-and-outlook.html">
|
||
|
||
<a href="../appendix/summary-and-outlook.html">
|
||
|
||
|
||
<b>8.8.</b>
|
||
|
||
Kubernetes及云原生年度总结及展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<ul class="articles">
|
||
|
||
|
||
<li class="chapter " data-level="8.8.1" data-path="../appendix/kubernetes-and-cloud-native-summary-in-2017-and-outlook-for-2018.html">
|
||
|
||
<a href="../appendix/kubernetes-and-cloud-native-summary-in-2017-and-outlook-for-2018.html">
|
||
|
||
|
||
<b>8.8.1.</b>
|
||
|
||
Kubernetes与云原生2017年年终总结及2018年展望
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.9" data-path="../appendix/about-kcsp.html">
|
||
|
||
<a href="../appendix/about-kcsp.html">
|
||
|
||
|
||
<b>8.9.</b>
|
||
|
||
Kubernetes认证服务提供商（KCSP）说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
<li class="chapter " data-level="8.10" data-path="../appendix/about-cka-candidate.html">
|
||
|
||
<a href="../appendix/about-cka-candidate.html">
|
||
|
||
|
||
<b>8.10.</b>
|
||
|
||
认证Kubernetes管理员（CKA）说明
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
<li class="divider"></li>
|
||
|
||
<li>
|
||
<a href="https://www.gitbook.com" target="blank" class="gitbook-link">
|
||
本书使用 GitBook 发布
|
||
</a>
|
||
</li>
|
||
</ul>
|
||
|
||
|
||
</nav>
|
||
|
||
|
||
</div>
|
||
|
||
<div class="book-body">
|
||
|
||
<div class="body-inner">
|
||
|
||
|
||
|
||
<div class="book-header" role="navigation">
|
||
|
||
|
||
<!-- Title -->
|
||
<h1>
|
||
<i class="fa fa-circle-o-notch fa-spin"></i>
|
||
<a href=".." >Istio 教程</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="istio-教程">Istio 教程</h1>
|
||
<p>本文是 Istio 管理 Java 微服务的案例教程，使用的所有工具和软件全部基于开源方案，替换了 <a href="https://github.com/redhat-developer-demos/istio-tutorial" target="_blank">redhat-developer-demos/istio-tutorial</a> 中的 minishift 环境，使用 <a href="https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster" target="_blank">kubernetes-vagrant-centos-cluster</a> 替代，沿用了原有的微服务示例，使用 Zipkin 做分布式追踪而不是 Jaeger。</p>
|
||
<p>本文中的代码和 YAML 文件见 <a href="https://github.com/rootsongjc/istio-tutorial" target="_blank">https://github.com/rootsongjc/istio-tutorial</a>。</p>
|
||
<h2 id="准备环境">准备环境</h2>
|
||
<p>在进行本教程前需要先准备以下工具和环境。</p>
|
||
<ul>
|
||
<li>8G 以上内存</li>
|
||
<li>Vagrant 2.0+</li>
|
||
<li>Virtualbox 5.0 +</li>
|
||
<li>提前下载 kubernetes1.9.1 的 release 压缩包</li>
|
||
<li>docker 1.12+</li>
|
||
<li>kubectl 1.9.1+</li>
|
||
<li>maven 3.5.2+</li>
|
||
<li>istioctl 0.7.1</li>
|
||
<li>git</li>
|
||
<li>curl、gzip、tar</li>
|
||
<li><a href="https://github.com/johanhaleby/kubetail" target="_blank">kubetail</a></li>
|
||
<li><a href="https://github.com/JoeDog/siege" target="_blank">siege</a></li>
|
||
</ul>
|
||
<h2 id="安装-kubernetes">安装 Kubernetes</h2>
|
||
<p>请参考 <a href="https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster" target="_blank">kubernetes-vagrant-centos-cluster</a> 在本地启动拥有三个节点的 kubernetes 集群。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">git</span> clone https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster.git
|
||
<span class="token function">cd</span> kubernetes-vagrant-centos-cluster
|
||
vagrant up
|
||
</code></pre>
|
||
<h2 id="安装-istio">安装 Istio</h2>
|
||
<p>在 <a href="https://github.com/rootsongjc/kubernetes-vagrant-centos-cluster" target="_blank">kubernetes-vagrant-centos-cluster</a> 中的包含 Istio 0.7.1 的安装 YAML 文件，运行下面的命令安装 Istio。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl apply -f addon/istio/
|
||
</code></pre>
|
||
<p><strong>运行示例</strong></p>
|
||
<pre class="language-"><code class="lang-bash">kubectl apply -n default -f <span class="token operator"><</span><span class="token punctuation">(</span>istioctl kube-inject -f yaml/istio-bookinfo/bookinfo.yaml<span class="token punctuation">)</span>
|
||
</code></pre>
|
||
<p>在您自己的本地主机的<code>/etc/hosts</code>文件中增加如下配置项。</p>
|
||
<pre class="language-"><code class="lang-ini">172.17.8.102 grafana.istio.jimmysong.io
|
||
172.17.8.102 servicegraph.istio.jimmysong.io
|
||
172.17.8.102 zipkin.istio.jimmysong.io
|
||
</code></pre>
|
||
<p>我们可以通过下面的URL地址访问以上的服务。</p>
|
||
<table>
|
||
<thead>
|
||
<tr>
|
||
<th>Service</th>
|
||
<th>URL</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td>grafana</td>
|
||
<td><a href="http://grafana.istio.jimmysong.io" target="_blank">http://grafana.istio.jimmysong.io</a></td>
|
||
</tr>
|
||
<tr>
|
||
<td>servicegraph</td>
|
||
<td><a href="http://servicegraph.istio.jimmysong.io/dotviz" target="_blank">http://servicegraph.istio.jimmysong.io/dotviz</a>，<a href="http://servicegraph.istio.jimmysong.io/graph" target="_blank">http://servicegraph.istio.jimmysong.io/graph</a></td>
|
||
</tr>
|
||
<tr>
|
||
<td>zipkin</td>
|
||
<td><a href="http://zipkin.istio.jimmysong.io" target="_blank">http://zipkin.istio.jimmysong.io</a></td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
<p>详细信息请参阅 <a href="https://istio.io/docs/guides/bookinfo.html" target="_blank">https://istio.io/docs/guides/bookinfo.html</a></p>
|
||
<h2 id="部署示例应用">部署示例应用</h2>
|
||
<p>在打包成镜像部署到 kubernetes 集群上运行之前，我们先在本地运行所有示例。</p>
|
||
<p>本教程中三个服务之间的依赖关系如下：</p>
|
||
<pre class="language-"><code class="lang-ini">customer → preference → recommendation
|
||
</code></pre>
|
||
<p><code>customer</code> 和 <code>preference</code> 微服务是基于 Spring Boot 构建的，<code>recommendation</code> 微服务是基于 <a href="https://vertx.io" target="_blank">vert.x</a> 构建的。</p>
|
||
<p><code>customer</code> 和 <code>preference</code> 微服务的 <code>pom.xml</code> 文件中都引入了 OpenTracing 和 Jeager 的依赖。</p>
|
||
<pre class="language-"><code class="lang-xml"><span class="token tag"><span class="token tag"><span class="token punctuation"><</span>dependency</span><span class="token punctuation">></span></span>
|
||
<span class="token tag"><span class="token tag"><span class="token punctuation"><</span>groupId</span><span class="token punctuation">></span></span>io.opentracing.contrib<span class="token tag"><span class="token tag"><span class="token punctuation"></</span>groupId</span><span class="token punctuation">></span></span>
|
||
<span class="token tag"><span class="token tag"><span class="token punctuation"><</span>artifactId</span><span class="token punctuation">></span></span>opentracing-spring-cloud-starter<span class="token tag"><span class="token tag"><span class="token punctuation"></</span>artifactId</span><span class="token punctuation">></span></span>
|
||
<span class="token tag"><span class="token tag"><span class="token punctuation"><</span>version</span><span class="token punctuation">></span></span>0.1.7<span class="token tag"><span class="token tag"><span class="token punctuation"></</span>version</span><span class="token punctuation">></span></span>
|
||
<span class="token tag"><span class="token tag"><span class="token punctuation"></</span>dependency</span><span class="token punctuation">></span></span>
|
||
<span class="token tag"><span class="token tag"><span class="token punctuation"><</span>dependency</span><span class="token punctuation">></span></span>
|
||
<span class="token tag"><span class="token tag"><span class="token punctuation"><</span>groupId</span><span class="token punctuation">></span></span>com.uber.jaeger<span class="token tag"><span class="token tag"><span class="token punctuation"></</span>groupId</span><span class="token punctuation">></span></span>
|
||
<span class="token tag"><span class="token tag"><span class="token punctuation"><</span>artifactId</span><span class="token punctuation">></span></span>jaeger-tracerresolver<span class="token tag"><span class="token tag"><span class="token punctuation"></</span>artifactId</span><span class="token punctuation">></span></span>
|
||
<span class="token tag"><span class="token tag"><span class="token punctuation"><</span>version</span><span class="token punctuation">></span></span>0.25.0<span class="token tag"><span class="token tag"><span class="token punctuation"></</span>version</span><span class="token punctuation">></span></span>
|
||
<span class="token tag"><span class="token tag"><span class="token punctuation"></</span>dependency</span><span class="token punctuation">></span></span>
|
||
</code></pre>
|
||
<h3 id="本地运行">本地运行</h3>
|
||
<p>我们首先在本地确定所有的微服务都可以正常运行，然后再打包镜像在 kubernetes 集群上运行。</p>
|
||
<h4 id="启动-jaeger">启动 Jaeger</h4>
|
||
<p>使用 docker 来运行 jagger。</p>
|
||
<pre class="language-"><code class="lang-bash">docker run -d \
|
||
--rm \
|
||
-p5775:5775/udp \
|
||
-p6831:6831/udp \
|
||
-p6832:6832/udp \
|
||
-p16686:16686 \
|
||
-p14268:14268 \
|
||
jaegertracing/all-in-one:1.3
|
||
</code></pre>
|
||
<p>Jaeger UI 地址 <a href="http://localhost:16686" target="_blank">http://localhost:16686</a></p>
|
||
<h4 id="customer">Customer</h4>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">cd</span> customer/java/springboot
|
||
JAEGER_SERVICE_NAME<span class="token operator">=</span>customer mvn \
|
||
spring-boot:run \
|
||
-Drun.arguments<span class="token operator">=</span><span class="token string">"--spring.config.location=src/main/resources/application-local.properties"</span>
|
||
</code></pre>
|
||
<p>服务访问地址： <a href="http://localhost:8280" target="_blank">http://localhost:8280</a></p>
|
||
<h4 id="preference">Preference</h4>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">cd</span> preference/java/springboot
|
||
JAEGER_SERVICE_NAME<span class="token operator">=</span>preference mvn \
|
||
spring-boot:run \
|
||
-Drun.arguments<span class="token operator">=</span><span class="token string">"--spring.config.location=src/main/resources/application-local.properties"</span>
|
||
</code></pre>
|
||
<p>服务访问地址：<a href="http://localhost:8180" target="_blank">http://localhost:8180</a></p>
|
||
<h4 id="recommendation">Recommendation</h4>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">cd</span> recommendation/java/vertx
|
||
mvn vertx:run
|
||
</code></pre>
|
||
<p>服务访问地址：<a href="http://localhost:8080" target="_blank">http://localhost:8080</a></p>
|
||
<p>所有服务都启动之后，此时访问 <a href="http://localhost:8280" target="_blank">http://localhost:8280</a> 将会看到如下输出。</p>
|
||
<pre class="language-"><code class="lang-bash">customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'unknown'</span><span class="token keyword">:</span> 1
|
||
</code></pre>
|
||
<p>每访问一次最后的数字就会加 1。</p>
|
||
<h4 id="jaeger">Jaeger</h4>
|
||
<p>此时访问 <a href="http://localhost:16686" target="_blank">http://localhost:16686</a> 将看到 Jaeger query UI，所有应用将 metrics 发送到 Jeager 中。</p>
|
||
<p>可以在 Jaeger UI 中搜索 <code>customer</code> 和 <code>preference</code> service 的 trace 并查看每次请求的 tracing。</p>
|
||
<figure id="fig6.3.1.7.1"><img src="../images/jaeger-query-ui.png" alt="Jaeger query UI"><figcaption>图片 - Jaeger query UI</figcaption></figure>
|
||
<h3 id="构建镜像">构建镜像</h3>
|
||
<p>在本地运行测试无误之后就可以构建镜像了。本教程中的容器镜像都是在 <a href="https://hub.docker.com/r/fabric8/java-jboss-openjdk8-jdk/~/dockerfile/" target="_blank">fabric8/java-jboss-openjdk8-jdk</a> 的基础上构建的。只要将 Java 应用构建出 Jar 包然后放到 <code>/deployments</code> 目录下基础镜像就可以自动帮我们运行，所以我们看到着几个应用的 <code>Dockerfile</code> 文件中都没有执行入口，真正的执行入口是 <a href="https://github.com/fabric8io-images/java/blob/master/images/jboss/openjdk8/jdk/run-java.sh" target="_blank">run-java.sh</a>。</p>
|
||
<h4 id="customer">Customer</h4>
|
||
<p>构建 Customer 镜像。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">cd</span> customer/java/springboot
|
||
mvn clean package
|
||
docker build -t jimmysong/istio-tutorial-customer:v1 <span class="token keyword">.</span>
|
||
docker push jimmysong/istio-tutorial-customer:v1
|
||
</code></pre>
|
||
<p>第一次构建和上传需要花费一点时间，下一次构建就会很快。</p>
|
||
<h4 id="preference">Preference</h4>
|
||
<p>构建 Preference 镜像。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">cd</span> preference/java/springboot
|
||
mvn clean package
|
||
docker build -t jimmysong/istio-tutorial-preference:v1 <span class="token keyword">.</span>
|
||
docker push jimmysong/istio-tutorial-preference:v1
|
||
</code></pre>
|
||
<h4 id="recommendation">Recommendation</h4>
|
||
<p>构建 Recommendation 镜像。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">cd</span> recommendation/java/vertx
|
||
mvn clean package
|
||
docker build -t jimmysong/istio-tutorial-recommendation:v1 <span class="token keyword">.</span>
|
||
docker push jimmysong/istio-tutorial-recommendation:v1
|
||
</code></pre>
|
||
<p>现在三个 docker 镜像都构建完成了，我们检查一下。</p>
|
||
<pre class="language-"><code class="lang-bash">$ docker images <span class="token operator">|</span> <span class="token function">grep</span> istio-tutorial
|
||
REPOSITORY TAG IMAGE ID CREATED SIZE
|
||
jimmysong/istio-tutorial-recommendation v1 d31dd858c300 51 seconds ago 443MB
|
||
jimmysong/istio-tutorial-preference v1 e5f0be361477 6 minutes ago 459MB
|
||
jimmysong/istio-tutorial-customer v1 d9601692673e 13 minutes ago 459MB
|
||
</code></pre>
|
||
<h3 id="部署到-kubernetes">部署到 Kubernetes</h3>
|
||
<p>使用下面的命令将以上服务部署到 kubernetes。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token comment" spellcheck="true"># create new namespace</span>
|
||
kubectl create ns istio-tutorial
|
||
|
||
<span class="token comment" spellcheck="true"># deploy recommendation</span>
|
||
kubectl apply -f <span class="token operator"><</span><span class="token punctuation">(</span>istioctl kube-inject -f recommendation/kubernetes/Deployment.yml<span class="token punctuation">)</span> -n istio-tutorial
|
||
kubectl apply -f recommendation/kubernetes/Service.yml
|
||
|
||
<span class="token comment" spellcheck="true"># deploy preferrence</span>
|
||
kubectl apply -f <span class="token operator"><</span><span class="token punctuation">(</span>istioctl kube-inject -f preference/kubernetes/Deployment.yml<span class="token punctuation">)</span> -n istio-tutorial
|
||
kubectl apply -f preference/kubernetes/Service.yml
|
||
|
||
<span class="token comment" spellcheck="true"># deploy customer</span>
|
||
kubectl apply -f <span class="token operator"><</span><span class="token punctuation">(</span>istioctl kube-inject -f customer/kubernetes/Deployment.yml<span class="token punctuation">)</span> -n istio-tutorial
|
||
kubectl apply -f customer/kubernetes/Service.yml
|
||
</code></pre>
|
||
<p><strong>注意：</strong><code>preference</code> 和 <code>customer</code> 应用启动速度比较慢，我们将 livenessProb 配置中的 <code>initialDelaySeconds</code> 设置为 <strong>20</strong> 秒。</p>
|
||
<p>查看 Pod 启动状态：</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl get pod -w -n istio-tutorial
|
||
</code></pre>
|
||
<h3 id="增加-ingress-配置">增加 Ingress 配置</h3>
|
||
<p>为了在 kubernetes 集群外部访问 customer 服务，我们需要增加 ingress 配置。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl apply -f ingress/ingress.yaml
|
||
</code></pre>
|
||
<p>修改本地的 <code>/etc/hosts</code> 文件，增加一条配置。</p>
|
||
<pre class="language-"><code class="lang-ini">172.17.8.102 customer.istio-tutorial.jimmysong.io
|
||
</code></pre>
|
||
<p>现在访问 <a href="http://customer.istio-tutorial.jimmysong.io" target="_blank">http://customer.istio-tutorial.jimmysong.io</a> 将看到如下输出：</p>
|
||
<pre class="language-"><code class="lang-ini"><span class="token constant">customer</span> <span class="token attr-value"><span class="token punctuation">=</span>> preference => recommendation v1 from '6fc97476f8-m2ntp': 1</span>
|
||
</code></pre>
|
||
<p>批量访问该地址。</p>
|
||
<pre class="language-"><code class="lang-bash">./bin/poll_customer.sh
|
||
</code></pre>
|
||
<p>访问 <a href="http://servicegraph.istio.jimmysong.io/dotviz" target="_blank">http://servicegraph.istio.jimmysong.io/dotviz</a> 查看服务的分布式追踪和依赖关系。</p>
|
||
<figure id="fig6.3.1.7.2"><img src="../images/istio-tutorial-zipkin-trace.png" alt="分布式追踪"><figcaption>图片 - 分布式追踪</figcaption></figure>
|
||
<figure id="fig6.3.1.7.3"><img src="../images/istio-tutorial-zipkin-dependency.png" alt="依赖关系"><figcaption>图片 - 依赖关系</figcaption></figure>
|
||
<p>访问 <a href="http://servicegraph.istio.jimmysong.io/dotviz" target="_blank">http://servicegraph.istio.jimmysong.io/dotviz</a> 查看服务间的关系图和 QPS。</p>
|
||
<figure id="fig6.3.1.7.4"><img src="../images/istio-tutorial-serivcegraph-dotviz.png" alt="服务关系图和QPS"><figcaption>图片 - 服务关系图和QPS</figcaption></figure>
|
||
<p>访问 <a href="http://grafana.istio.jimmysong.io" target="_blank">http://grafana.istio.jimmysong.io</a> 查看 Service Mesh 的监控信息。</p>
|
||
<figure id="fig6.3.1.7.5"><img src="../images/istio-tutorial-grafana.png" alt="Grafana 监控"><figcaption>图片 - Grafana 监控</figcaption></figure>
|
||
<h2 id="istio-使用示例">Istio 使用示例</h2>
|
||
<p>为了试用 Istio 中的各种功能，我们需要为应用构建多个版本，我们为 recommendation 构建 v2 版本的镜像，看看如何使用 Istio 控制微服务的流量。</p>
|
||
<h3 id="构建-recommendationv2">构建 recommendation:v2</h3>
|
||
<p>我们将构建新版的 <code>recommendation</code> 服务的镜像，并观察 <code>customer</code> 对不同版本的 <code>recommendataion</code> 服务的访问频率。</p>
|
||
<p>修改 <code>recommendation/java/vertx/src/main/java/com/redhat/developer/demos/recommendation/RecommendationVerticle.java</code> 程序中代码。</p>
|
||
<p>将 <code>private static final String RESPONSE_STRING_FORMAT = "recommendation v1 from '%s': %d\n";</code> 修改为 <code>private static final String RESPONSE_STRING_FORMAT = "recommendation v2 from '%s': %d\n";</code></p>
|
||
<p>并构建 <code>recommendation:v2</code> 镜像。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">cd</span> recommendation/java/vertx
|
||
mvn clean package
|
||
docker build -t jimmysong/istio-tutorial-recommendation:v2 <span class="token keyword">.</span>
|
||
docker push jimmysong/istio-tutorial-recommendation:v2
|
||
</code></pre>
|
||
<p>将应用部署到 kubernetes。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token comment" spellcheck="true"># deploy recommendation</span>
|
||
kubectl apply -f <span class="token operator"><</span><span class="token punctuation">(</span>istioctl kube-inject -f recommendation/kubernetes/Deployment-v2.yml<span class="token punctuation">)</span> -n istio-tutorial
|
||
</code></pre>
|
||
<p>现在再访问 <code>customer</code> 服务，将看到如下输出：</p>
|
||
<pre class="language-"><code class="lang-bash">$ bin/poll_customer.sh
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-5xs27'</span><span class="token keyword">:</span> 1
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 3581
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-5xs27'</span><span class="token keyword">:</span> 2
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 3582
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-5xs27'</span><span class="token keyword">:</span> 3
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 3583
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-5xs27'</span><span class="token keyword">:</span> 4
|
||
</code></pre>
|
||
<p>我们可以看到 v1 和 v2 版本的 <code>recommendation</code> 服务会被间隔访问到。</p>
|
||
<p>我们再将 v2 版本的 <code>recommendation</code> 实例数设置成 2 个。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl scale --replicas<span class="token operator">=</span>2 deployment/recommendation-v2 -n istio-tutorial
|
||
kubectl get pod -w -n istio-tutorial
|
||
</code></pre>
|
||
<p>观察 <code>recommendation-v2</code> Pod 达到两个之后再访问 <code>customer</code> 服务。</p>
|
||
<pre class="language-"><code class="lang-bash">$ bin/poll_customer.sh
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-j9fgj'</span><span class="token keyword">:</span> 1
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-5xs27'</span><span class="token keyword">:</span> 71
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 3651
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-j9fgj'</span><span class="token keyword">:</span> 2
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-5xs27'</span><span class="token keyword">:</span> 72
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 3652
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-j9fgj'</span><span class="token keyword">:</span> 3
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-5xs27'</span><span class="token keyword">:</span> 73
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 3653
|
||
</code></pre>
|
||
<p>观察输出中 v1 和 v2 版本 <code>recommendation</code> 的访问频率。</p>
|
||
<p>将 <code>recommendataion</code> 服务的实例数恢复为 1。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl scale --replicas<span class="token operator">=</span>1 deployment/recommendation-v2
|
||
</code></pre>
|
||
<h3 id="修改-istio-routerules">修改 Istio RouteRules</h3>
|
||
<p>以下所有路有规则都是针对 <code>recommendation</code> 服务，并在 repo 的根目录下执行。</p>
|
||
<p><strong>将所有流量打给 v2</strong></p>
|
||
<p>下面将演示如何动态的划分不同版本服务间的流量，将所有的流量都打到 <code>recommendation:v2</code>。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-recommendation-v2.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>现在再访问 <code>customer</code> 服务将看到所有的流量都会打到 <code>recommendation:v2</code>。</p>
|
||
<p>删除 RouteRules 后再访问 <code>customer</code> 服务将看到又恢复了 v1 和 v2 版本的 <code>recommendation</code> 服务的间隔访问。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete routerule recommendation-default
|
||
</code></pre>
|
||
<p><strong>切分流量</strong></p>
|
||
<p>将 90% 的流量给 v1，10% 的流量给 v2。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-recommendation-v1_and_v2.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>执行<code>bin/poll_customer.sh</code> 观察访问情况。</p>
|
||
<p>要想动态切分流量只要修改 RouteRules 中的 <code>weight</code> 配置即可。</p>
|
||
<pre class="language-"><code class="lang-yaml"><span class="token key atrule">apiVersion</span><span class="token punctuation">:</span> config.istio.io/v1alpha2
|
||
<span class="token key atrule">kind</span><span class="token punctuation">:</span> RouteRule
|
||
<span class="token key atrule">metadata</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> recommendation<span class="token punctuation">-</span>v1<span class="token punctuation">-</span>v2
|
||
<span class="token key atrule">spec</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">destination</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">namespace</span><span class="token punctuation">:</span> istio<span class="token punctuation">-</span>tutorial
|
||
<span class="token key atrule">name</span><span class="token punctuation">:</span> recommendation
|
||
<span class="token key atrule">precedence</span><span class="token punctuation">:</span> <span class="token number">5</span>
|
||
<span class="token key atrule">route</span><span class="token punctuation">:</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">labels</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">version</span><span class="token punctuation">:</span> v1
|
||
<span class="token key atrule">weight</span><span class="token punctuation">:</span> <span class="token number">90</span>
|
||
<span class="token punctuation">-</span> <span class="token key atrule">labels</span><span class="token punctuation">:</span>
|
||
<span class="token key atrule">version</span><span class="token punctuation">:</span> v2
|
||
<span class="token key atrule">weight</span><span class="token punctuation">:</span> <span class="token number">10</span>
|
||
</code></pre>
|
||
<p>因为 RouteRule 有优先级，为了继续后面的实验，在验证完成后删除该 RouteRule。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete routerule recommendation-v1-v2 -n istio-tutorial
|
||
</code></pre>
|
||
<h3 id="故障注入">故障注入</h3>
|
||
<p>有时候我们为了增强系统的健壮性，需要对系统做混沌工程，故意注入故障，并保障服务可以自动处理这些故障。</p>
|
||
<p><strong>注入 HTTP 503 错误</strong></p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-recommendation-503.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>有 50% 的几率报 503 错误。</p>
|
||
<pre class="language-"><code class="lang-bash">$ bin/poll_customer.sh
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-5xs27'</span><span class="token keyword">:</span> 135
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 503 preference <span class="token operator">=</span><span class="token operator">></span> 503 fault filter abort
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 3860
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 503 preference <span class="token operator">=</span><span class="token operator">></span> 503 fault filter abort
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 503 preference <span class="token operator">=</span><span class="token operator">></span> 503 fault filter abort
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-5xs27'</span><span class="token keyword">:</span> 136
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 3861
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 503 preference <span class="token operator">=</span><span class="token operator">></span> 503 fault filter abort
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 503 preference <span class="token operator">=</span><span class="token operator">></span> 503 fault filter abort
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'77b9f6cc68-5xs27'</span><span class="token keyword">:</span> 137
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 503 preference <span class="token operator">=</span><span class="token operator">></span> 503 fault filter abort
|
||
</code></pre>
|
||
<p>清理 RouteRule。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete routerule recommendation-503 -n istio-tutorial
|
||
</code></pre>
|
||
<h3 id="增加延迟">增加延迟</h3>
|
||
<p>增加服务的访问延迟。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-recommendation-delay.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>会有 50% 的几率访问 <code>recommendation</code> 服务有 7 秒的延迟。百分比和延迟时间可以在 RouteRule 中配置。</p>
|
||
<p>清理 RouteRule。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete routerule recommendation-delay -n istio-tutorial
|
||
</code></pre>
|
||
<h3 id="重试">重试</h3>
|
||
<p>让服务不是直接失败，而是增加重试机制。</p>
|
||
<p>我们下面将同时应用两条 RouteRule，让访问 <code>recommendation</code> 服务时有 50% 的几率出现 503 错误，并在出现错误的时候尝试访问 v2 版本，超时时间为 2 秒。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-recommendation-v2_503.yml -n istio-tutorial
|
||
istioctl create -f istiofiles/route-rule-recommendation-v2_retry.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>执行 <code>bin/poll_customer.sh</code> 我们看到一开始有些 503 错误，然后所有的流量都流向了 v2。</p>
|
||
<p>清理 RouteRules。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete routerule recommendation-v2-retry -n istio-tutorial
|
||
istioctl delete routerule recommendation-v2-503 -n istio-tutorial
|
||
</code></pre>
|
||
<h3 id="超时">超时</h3>
|
||
<p>设置超时时间，只有服务访问超时才认定服务访问失败。</p>
|
||
<p>取消注释 <code>recommendation/java/vertx/src/main/java/com/redhat/developer/demos/recommendation/RecommendationVerticle.java</code> 中的下面一行，增加超时时间为 3 秒。</p>
|
||
<pre class="language-"><code class="lang-java">router<span class="token punctuation">.</span><span class="token function">get</span><span class="token punctuation">(</span><span class="token string">"/"</span><span class="token punctuation">)</span><span class="token punctuation">.</span><span class="token function">handler</span><span class="token punctuation">(</span><span class="token keyword">this</span><span class="token operator">:</span><span class="token operator">:</span>timeout<span class="token punctuation">)</span><span class="token punctuation">;</span>
|
||
</code></pre>
|
||
<p>重新生成镜像。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">cd</span> recommendation/java/vertx
|
||
mvn clean package
|
||
docker build -t jimmysong/istio-tutorial-recommendation:v2 <span class="token keyword">.</span>
|
||
docker push jimmysong/istio-tutorial-recommendation:v2
|
||
</code></pre>
|
||
<p>重新部署到 kubernetes。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl delete -f recommendation/kubernetes/Deployment-v2.yml
|
||
</code></pre>
|
||
<p>因为我们重新构建的镜像使用了同样的名字和 tag，而之前在 <code>Deployment-v2.yml</code> 中配置的镜像拉取策略是 <code>IfNotPresent</code>，这样的话即使我们构建了新的镜像也无法应用到集群上，因此将镜像拉取策略改成 <code>Always</code> 确保每次启动 Pod 的时候都会拉取镜像。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl apply -f <span class="token operator"><</span><span class="token punctuation">(</span>istioctl kube-inject -f recommendation/kubernetes/Deployment-v2.yml<span class="token punctuation">)</span> -n istio-tutorial
|
||
</code></pre>
|
||
<p>启用超时 RouteRules。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-recommendation-timeout.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>访问 <code>customer</code> 服务将看到如下输出：</p>
|
||
<pre class="language-"><code class="lang-bash">$ bin/poll_customer.sh
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 503 preference <span class="token operator">=</span><span class="token operator">></span> 504 upstream request <span class="token function">timeout</span>
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 4002
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 503 preference <span class="token operator">=</span><span class="token operator">></span> 504 upstream request <span class="token function">timeout</span>
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 4003
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 503 preference <span class="token operator">=</span><span class="token operator">></span> 504 upstream request <span class="token function">timeout</span>
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 4004
|
||
</code></pre>
|
||
<p>清理 RouteRules。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete routerule recommendation-timeout -n istio-tutorial
|
||
</code></pre>
|
||
<h3 id="基于-user-agent-的智能路由（金丝雀发布）">基于 user-agent 的智能路由（金丝雀发布）</h3>
|
||
<p>User-agent 是一个字符串，其中包含了浏览器的信息，访问 <a href="https://www.whoishostingthis.com/tools/user-agent" target="_blank">https://www.whoishostingthis.com/tools/user-agent</a> 获取你的 user-agent。</p>
|
||
<p>我的 user-agent 是：</p>
|
||
<pre class="language-"><code class="lang-ini">Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
|
||
</code></pre>
|
||
<p>将所有的流量打到 v1。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-recommendation-v1.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>将使用 Safari 浏览器访问的流量打到 v2。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-safari-recommendation-v2.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>谁用 Safari 或者 Chrome（Chrome 浏览器的 user-agent 中也包含 Safari 字段）访问 <a href="http://customer.istio-tutorial.jimmysong.io/" target="_blank">http://customer.istio-tutorial.jimmysong.io/</a> 在经过 3 秒钟（我们在前面重新编译 v2 镜像，设置了 3 秒超时时间）后将看到访问 v2 的输出。</p>
|
||
<p>或者使用 curl 访问。</p>
|
||
<pre class="language-"><code class="lang-bash">curl -A Safari http://customer.istio-tutorial.jimmysong.io/
|
||
curl -A Firefox http://customer.istio-tutorial.jimmysong.io/
|
||
</code></pre>
|
||
<p>观察返回的结果。</p>
|
||
<p>将移动端用户的流量导到 v2。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-mobile-recommendation-v2.yml -n istio-tutorial
|
||
|
||
curl -A <span class="token string">"Mozilla/5.0 (iPhone; U; CPU iPhone OS 4(KHTML, like Gecko) Version/5.0.2 Mobile/8J2 Safari/6533.18.5"</span> http://customer.istio-tutorial.jimmysong.io/
|
||
</code></pre>
|
||
<p>观察输出的结果。</p>
|
||
<p>清理 RouteRules。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete routerule recommendation-mobile -n istio-tutorial
|
||
istioctl delete routerule recommendation-safari -n istio-tutorial
|
||
istioctl delete routerule recommendation-default -n istio-tutorial
|
||
</code></pre>
|
||
<h3 id="镜像流量">镜像流量</h3>
|
||
<p>确保当前至少运行了两个版本的 <code>recommendation</code> 服务，并且没有 RouteRule。</p>
|
||
<p>注：可以使用 <code>istioctl get routerule</code> 获取 RouteRule。</p>
|
||
<p>设置流量镜像，将所有 v1 的流量都被镜像到 v2。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-recommendation-v1-mirror-v2.yml -n istio-tutorial
|
||
bin/poll_customer.sh
|
||
</code></pre>
|
||
<p>查看 recommendation-v2 的日志。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl logs -f `oc get pods<span class="token operator">|</span><span class="token function">grep</span> recommendation-v2<span class="token operator">|</span><span class="token function">awk</span> <span class="token string">'{ print <span class="token variable">$1</span> }'</span>` -c recommendation
|
||
</code></pre>
|
||
<h3 id="访问控制">访问控制</h3>
|
||
<p>Istio 可以设置服务访问的黑白名单，如果没有权限的话会返回 HTTP 404 Not Found。</p>
|
||
<h4 id="白名单">白名单</h4>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/acl-whitelist.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>此时访问 <code>customer</code> 服务。</p>
|
||
<pre class="language-"><code class="lang-bash">$ bin/poll_customer.sh
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 404 NOT_FOUND:preferencewhitelist.listchecker.istio-tutorial:customer is not whitelisted
|
||
</code></pre>
|
||
<p>重置环境。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete -f istiofiles/acl-whitelist.yml -n istio-tutorial
|
||
</code></pre>
|
||
<h4 id="黑名单">黑名单</h4>
|
||
<p>设置黑名单，所有位于黑名单中的流量将获得 403 Forbidden 返回码。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/acl-blacklist.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>此时访问 <code>customer</code> 服务。</p>
|
||
<pre class="language-"><code class="lang-bash">$ bin/poll_customer.sh
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 403 PERMISSION_DENIED:denycustomerhandler.denier.istio-tutorial:Not allowed
|
||
</code></pre>
|
||
<p>重置环境。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete -f istiofiles/acl-blacklist.yml -n istio-tutorial
|
||
</code></pre>
|
||
<h3 id="负载均衡">负载均衡</h3>
|
||
<p>Kubernetes 中默认的负载均衡策略是 round-robin，当然我们可以使用 Istio 把它修改成 random。</p>
|
||
<p>增加 v1 的实例数。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl scale deployment recommendation-v1 --replicas<span class="token operator">=</span>2 -n istio-tutorial
|
||
</code></pre>
|
||
<p>持续访问 <code>customer</code> 服务。</p>
|
||
<pre class="language-"><code class="lang-bash">bin/poll_customer.sh
|
||
</code></pre>
|
||
<p>保持前台输出，观察流量的行为。</p>
|
||
<p>应用负载均衡策略。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/recommendation_lb_policy_app.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>观察一段时间流量的行为后，重置环境。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete -f istiofiles/recommendation_lb_policy_app.yml -n istio-tutorial
|
||
kubectl scale deployment recommendation-v1 --replicas<span class="token operator">=</span>1 -n istio-tutorial
|
||
</code></pre>
|
||
<h3 id="速率限制">速率限制</h3>
|
||
<p>暂时不可用</p>
|
||
<h3 id="断路器">断路器</h3>
|
||
<p>当达到最大连接数和最大挂起请求数时快速失败。</p>
|
||
<p>将流量在 v1 和 v2 之间均分。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-recommendation-v1_and_v2_50_50.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>未开启断路器的时候启动负载测试。</p>
|
||
<pre class="language-"><code class="lang-bash">$ siege -r 2 -c 20 -v customer.istio-tutorial.jimmysong.io
|
||
New configuration template added to /Users/jimmysong/.siege
|
||
Run siege -C to view the current settings <span class="token keyword">in</span> that <span class="token function">file</span>
|
||
** SIEGE 4.0.4
|
||
** Preparing 20 concurrent <span class="token function">users</span> <span class="token keyword">for</span> battle.
|
||
The server is now under siege<span class="token punctuation">..</span>.
|
||
HTTP/1.1 200 0.10 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.12 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.13 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.13 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.13 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.17 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.12 secs: 74 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.14 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.15 secs: 74 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.15 secs: 74 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.17 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.17 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.20 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.20 secs: 74 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.05 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.12 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.15 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.25 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.26 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.14 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.58 secs: 74 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 6.15 secs: 74 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 6.16 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.03 secs: 74 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 6.06 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 6.04 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.11 secs: 74 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.09 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 6.15 secs: 74 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 6.71 secs: 74 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 3.52 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
^C
|
||
Lifting the server siege<span class="token punctuation">..</span>.
|
||
Transactions: 31 hits
|
||
Availability: 100.00 %
|
||
Elapsed time: 7.99 secs
|
||
Data transferred: 0.00 MB
|
||
Response time: 2.99 secs
|
||
Transaction rate: 3.88 trans/sec
|
||
Throughput: 0.00 MB/sec
|
||
Concurrency: 11.60
|
||
Successful transactions: 31
|
||
Failed transactions: 0
|
||
Longest transaction: 6.71
|
||
Shortest transaction: 0.05
|
||
</code></pre>
|
||
<p>所有的请求都成功了，但是性能很差，因为 v2 版本设置了 3 秒的超时时间。</p>
|
||
<p>我们启用下断路器。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/recommendation_cb_policy_version_v2.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>重新测试一下。</p>
|
||
<pre class="language-"><code class="lang-bash">$ siege -r 2 -c 20 -v customer.istio-tutorial.jimmysong.io
|
||
** SIEGE 4.0.4
|
||
** Preparing 20 concurrent <span class="token function">users</span> <span class="token keyword">for</span> battle.
|
||
The server is now under siege<span class="token punctuation">..</span>.
|
||
HTTP/1.1 200 0.07 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.07 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.07 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.12 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.12 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.16 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.16 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.21 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.21 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.24 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.24 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.14 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.29 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.13 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.18 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.13 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.11 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.39 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.24 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.44 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.43 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.44 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.40 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.47 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.42 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.42 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.06 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.07 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.15 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.12 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.57 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.18 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.52 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.65 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.42 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.09 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.43 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 503 0.04 secs: 92 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 4.15 secs: 74 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
HTTP/1.1 200 0.01 secs: 75 bytes <span class="token operator">==</span><span class="token operator">></span> GET /
|
||
|
||
Transactions: 19 hits
|
||
Availability: 47.50 %
|
||
Elapsed time: 4.16 secs
|
||
Data transferred: 0.00 MB
|
||
Response time: 0.72 secs
|
||
Transaction rate: 4.57 trans/sec
|
||
Throughput: 0.00 MB/sec
|
||
Concurrency: 3.31
|
||
Successful transactions: 19
|
||
Failed transactions: 21
|
||
Longest transaction: 4.15
|
||
Shortest transaction: 0.01
|
||
</code></pre>
|
||
<p>我们可以看到在启用了断路器后各项性能都有提高。</p>
|
||
<p>清理配置。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete routerule recommendation-v1-v2 -n istio-tutorial
|
||
istioctl delete -f istiofiles/recommendation_cb_policy_version_v2.yml -n istio-tutorial
|
||
</code></pre>
|
||
<h3 id="pool-ejection">Pool Ejection</h3>
|
||
<p>所谓的 Pool Ejection 就是当某些实例出现错误（如返回 5xx 错误码）临时将该实例弹出一段时间后（窗口期，可配置），然后再将其加入到负载均衡池中。我们的例子中配置的窗口期是 15 秒。</p>
|
||
<p>将 v1 和 v2 的流量均分。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/route-rule-recommendation-v1_and_v2_50_50.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>增加 v2 的实例个数。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl scale deployment recommendation-v2 --replicas<span class="token operator">=</span>2 -n istio-tutorial
|
||
kubectl get pods -w
|
||
</code></pre>
|
||
<p>等待所有的 Pod 的状态都启动完成。</p>
|
||
<p>现在到 v2 的容器中操作。</p>
|
||
<pre class="language-"><code class="lang-bash">$ kubectl <span class="token function">exec</span> recommendation-v2-785465d9cd-225ms -c recommendation /bin/bash
|
||
$ curl localhost:8080/misbehave
|
||
Following requests to <span class="token string">'/'</span> will <span class="token keyword">return</span> a 503
|
||
</code></pre>
|
||
<p>增加 Pool Ejection 配置。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/recommendation_cb_policy_pool_ejection.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>此时再访问 <code>customer</code> 服务。</p>
|
||
<pre class="language-"><code class="lang-bash">$ bin/poll_customer.sh
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 10505
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'785465d9cd-225ms'</span><span class="token keyword">:</span> 2407
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 10506
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'785465d9cd-225ms'</span><span class="token keyword">:</span> 2408
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 10507
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 10508
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v1 from <span class="token string">'6fc97476f8-m2ntp'</span><span class="token keyword">:</span> 10509
|
||
customer <span class="token operator">=</span><span class="token operator">></span> 503 preference <span class="token operator">=</span><span class="token operator">></span> 503 recommendation misbehavior from <span class="token string">'785465d9cd-ldc6j'</span>
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'785465d9cd-225ms'</span><span class="token keyword">:</span> 2409
|
||
customer <span class="token operator">=</span><span class="token operator">></span> preference <span class="token operator">=</span><span class="token operator">></span> recommendation v2 from <span class="token string">'785465d9cd-225ms'</span><span class="token keyword">:</span> 2410
|
||
</code></pre>
|
||
<p>我们看到窗口期生效了，当出现 503 错误后至少 15 秒后才会出现第二次。</p>
|
||
<p>即使有了负载均衡池弹出策略对于系统的弹性来说依然还不够，如果你的服务有多个可用实例，可以将<strong>断路器</strong>、<strong>重试</strong>、<strong>Pool Ejection</strong> 等策略组合起来使用。</p>
|
||
<p>例如在以上的 Pool Ejection 的基础上增加重试策略。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl replace -f istiofiles/route-rule-recommendation-v1_and_v2_retry.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>现在再访问 <code>customer</code> 服务就看不到 503 错误了。</p>
|
||
<p>清理配置。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl scale deployment recommendation-v2 --replicas<span class="token operator">=</span>1 -n istio-tutorial
|
||
istioctl delete routerule recommendation-v1-v2 -n istio-tutorial
|
||
istioctl delete -f istiofiles/recommendation_cb_policy_pool_ejection.yml -n istio-tutorial
|
||
</code></pre>
|
||
<h3 id="egress">Egress</h3>
|
||
<p>Egress 是用来配置 Istio serivce mesh 中的服务对外部服务的访问策略。</p>
|
||
<p>具体配置请参考 <a href="http://istio.doczh.cn/docs/tasks/traffic-management/egress.html" target="_blank">控制 Egress 流量</a>。</p>
|
||
<p>以下示例还有问题，无法正常工作。</p>
|
||
<p>构建示例镜像 egresshttpbin。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">cd</span> egress/egresshttpbin/
|
||
mvn clean package
|
||
docker build -t jimmysong/istio-tutorial-egresshttpbin:v1 <span class="token keyword">.</span>
|
||
docker push jimmysong/istio-tutorial-egresshttpbin:v1
|
||
</code></pre>
|
||
<p>部署到 Kubernetes。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl apply -f <span class="token operator"><</span><span class="token punctuation">(</span>istioctl kube-inject -f egress/egresshttpbin/src/main/kubernetes/Deployment.yml<span class="token punctuation">)</span> -n istio-toturial
|
||
kubectl create -f egress/egresshttpbin/src/main/kubernetes/Service.yml
|
||
</code></pre>
|
||
<p>为了在 kubernetes 集群外部访问到该服务，修改增加 ingress 配置并修改本地的<code>/etc/hosts</code> 文件，我们在前面已经完成了，此处不再赘述。</p>
|
||
<p>构建示例镜像 egressgithub。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">cd</span> egress/egressgithub
|
||
mvn clean package
|
||
docker build -t jimmysong/istio-tutorial-egressgithub:v1 <span class="token keyword">.</span>
|
||
docker push jimmysong/istio-tutorial-egressgithub:v1
|
||
</code></pre>
|
||
<p>部署到 Kubernetes。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl apply -f <span class="token operator"><</span><span class="token punctuation">(</span>istioctl kube-inject -f egress/egressgithub/src/main/kubernetes/Deployment.yml<span class="token punctuation">)</span> -n istio-tutorial
|
||
kubectl create -f egress/egressgithub/src/main/kubernetes/Service.yml
|
||
</code></pre>
|
||
<p>增加 Egress 配置。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/egress_httpbin.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>到 egresshttpbin 容器中测试。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl <span class="token function">exec</span> -it <span class="token punctuation">$(</span>oc get pods -o jsonpath<span class="token operator">=</span><span class="token string">"{.items[*].metadata.name}"</span> -l app<span class="token operator">=</span>egresshttpbin,version<span class="token operator">=</span>v1<span class="token punctuation">)</span> -c egresshttpbin /bin/bash
|
||
|
||
curl localhost:8080
|
||
|
||
curl httpbin.org/user-agent
|
||
|
||
curl httpbin.org/headers
|
||
|
||
<span class="token keyword">exit</span>
|
||
</code></pre>
|
||
<p>增加对 <a href="https://jimmysong.io" target="_blank">jimmysong.io</a> 的 egress 配置。</p>
|
||
<pre class="language-"><code class="lang-bash"><span class="token function">cat</span> <span class="token operator"><<</span>EOF <span class="token operator">|</span> istioctl create -f -
|
||
apiVersion: config.istio.io/v1alpha2
|
||
kind: EgressRule
|
||
metadata:
|
||
name: jimmysong-egress-rule
|
||
namespace: istio-tutorial
|
||
spec:
|
||
destination:
|
||
service: jimmysong.io
|
||
ports:
|
||
- port: 443
|
||
protocol: https
|
||
EOF
|
||
</code></pre>
|
||
<p>增加 Egress 配置。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl create -f istiofiles/egress_github.yml -n istio-tutorial
|
||
</code></pre>
|
||
<p>到 egressgithub 容器中测试。</p>
|
||
<pre class="language-"><code class="lang-bash">kubectl <span class="token function">exec</span> -it <span class="token punctuation">$(</span>oc get pods -o jsonpath<span class="token operator">=</span><span class="token string">"{.items[*].metadata.name}"</span> -l app<span class="token operator">=</span>egressgithub,version<span class="token operator">=</span>v1<span class="token punctuation">)</span> -c egressgithub /bin/bash
|
||
|
||
curl http://jimmysong:443
|
||
|
||
<span class="token keyword">exit</span>
|
||
</code></pre>
|
||
<p>清理环境。</p>
|
||
<pre class="language-"><code class="lang-bash">istioctl delete egressrule httpbin-egress-rule jimmysong-egress-rule github-egress-rule -n istio-tutorial
|
||
</code></pre>
|
||
<h2 id="参考">参考</h2>
|
||
<ul>
|
||
<li><a href="https://github.com/redhat-developer-demos/istio-tutorial" target="_blank">https://github.com/redhat-developer-demos/istio-tutorial</a></li>
|
||
<li><a href="https://developers.redhat.com/books/introducing-istio-service-mesh-microservices/" target="_blank">Book - Introducing Istio Service Mesh for Microservices</a> </li>
|
||
</ul>
|
||
<footer class="page-footer"><span class="copyright">Copyright © jimmysong.io 2017-2018 all right reserved，powered by Gitbook</span><span class="footer-modification">Updated at
|
||
2018-04-19 10:16:19
|
||
</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="istio-community-tips.html" class="navigation navigation-prev " aria-label="Previous page: 如何参与Istio社区及注意事项">
|
||
<i class="fa fa-angle-left"></i>
|
||
</a>
|
||
|
||
|
||
<a href="linkerd.html" class="navigation navigation-next " aria-label="Next page: Linkerd">
|
||
<i class="fa fa-angle-right"></i>
|
||
</a>
|
||
|
||
|
||
|
||
</div>
|
||
|
||
<script>
|
||
var gitbook = gitbook || [];
|
||
gitbook.push(function() {
|
||
gitbook.page.hasChanged({"page":{"title":"Istio 教程","level":"6.3.1.7","depth":3,"next":{"title":"Linkerd","level":"6.3.2","depth":2,"path":"usecases/linkerd.md","ref":"usecases/linkerd.md","articles":[{"title":"Linkerd 使用指南","level":"6.3.2.1","depth":3,"path":"usecases/linkerd-user-guide.md","ref":"usecases/linkerd-user-guide.md","articles":[]}]},"previous":{"title":"如何参与Istio社区及注意事项","level":"6.3.1.6","depth":3,"path":"usecases/istio-community-tips.md","ref":"usecases/istio-community-tips.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"],"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 © jimmysong.io 2017-2018","modify_label":"Updated at ","modify_format":"YYYY-MM-DD HH:mm:ss"},"prism":{"css":["prism-themes/themes/prism-ghcolors.css"]},"github":{"url":"https://github.com/rootsongjc/kubernetes-handbook"},"editlink":{"label":"编辑本页","multilingual":false,"base":"https://github.com/rootsongjc/kubernetes-handbook/blob/master/"},"splitter":{},"codesnippet":{},"fontsettings":{"theme":"white","family":"sans","size":2},"favicon":{"shortcut":"favicon.ico","bookmark":"favicon.ico"},"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"},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"theme-default":{"showLevel":true,"styles":{"ebook":"styles/ebook.css","epub":"styles/epub.css","mobi":"styles/mobi.css","pdf":"styles/pdf.css","print":"styles/print.css","website":"styles/website.css"}},"search-plus":{},"image-captions":{"caption":"图片 - _CAPTION_","variable_name":"_pictures"}},"theme":"default","author":"Jimmy Song","pdf":{"pageNumbers":true,"fontSize":12,"fontFamily":"Arial","paperSize":"a4","chapterMark":"pagebreak","pageBreaksBefore":"/","margin":{"right":62,"left":62,"top":56,"bottom":56}},"structure":{"langs":"LANGS.md","readme":"README.md","glossary":"GLOSSARY.md","summary":"SUMMARY.md"},"variables":{"_pictures":[{"backlink":"index.html#fig1.1.1","level":"1.1","list_caption":"Figure: Stargazers over time","alt":"Stargazers over time","nro":1,"url":"https://starcharts.herokuapp.com/rootsongjc/kubernetes-handbook.svg","index":1,"caption_template":"图片 - _CAPTION_","label":"Stargazers over time","attributes":{},"skip":false,"key":"1.1.1"},{"backlink":"cloud-native/cncf.html#fig1.2.1","level":"1.2","list_caption":"Figure: CNCF landscape","alt":"CNCF landscape","nro":2,"url":"https://github.com/cncf/landscape/raw/master/landscape/CloudNativeLandscape_latest.png","index":1,"caption_template":"图片 - _CAPTION_","label":"CNCF landscape","attributes":{},"skip":false,"key":"1.2.1"},{"backlink":"cloud-native/cncf.html#fig1.2.2","level":"1.2","list_caption":"Figure: CNCF项目成熟度级别","alt":"CNCF项目成熟度级别","nro":3,"url":"../images/cncf-graduation-criteria.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"CNCF项目成熟度级别","attributes":{},"skip":false,"key":"1.2.2"},{"backlink":"cloud-native/play-with-kubernetes.html#fig2.1.1","level":"2.1","list_caption":"Figure: Play with Kubernetes网页截图","alt":"Play with Kubernetes网页截图","nro":4,"url":"../images/play-with-kubernetes.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Play with Kubernetes网页截图","attributes":{},"skip":false,"key":"2.1.1"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.1","level":"2.2","list_caption":"Figure: 云计算演进历程","alt":"云计算演进历程","nro":5,"url":"../images/cloud-computing-evolution-road.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"云计算演进历程","attributes":{},"skip":false,"key":"2.2.1"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.2","level":"2.2","list_caption":"Figure: 来自Twitter @MarcWilczek","alt":"来自Twitter @MarcWilczek","nro":6,"url":"../images/cloud-native-comes-of-age.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"来自Twitter @MarcWilczek","attributes":{},"skip":false,"key":"2.2.2"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.3","level":"2.2","list_caption":"Figure: Cloud native思维导图","alt":"Cloud native思维导图","nro":7,"url":"../images/cloud-native-architecutre-mindnode.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"Cloud native思维导图","attributes":{},"skip":false,"key":"2.2.3"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.4","level":"2.2","list_caption":"Figure: 十二因素应用","alt":"十二因素应用","nro":8,"url":"../images/12-factor-app.png","index":4,"caption_template":"图片 - _CAPTION_","label":"十二因素应用","attributes":{},"skip":false,"key":"2.2.4"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.5","level":"2.2","list_caption":"Figure: 容器生态","alt":"容器生态","nro":9,"url":"../images/container-ecosystem.png","index":5,"caption_template":"图片 - _CAPTION_","label":"容器生态","attributes":{},"skip":false,"key":"2.2.5"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.6","level":"2.2","list_caption":"Figure: 使用Jenkins进行持续集成与发布流程图","alt":"使用Jenkins进行持续集成与发布流程图","nro":10,"url":"../images/kubernetes-jenkins-ci-cd.png","index":6,"caption_template":"图片 - _CAPTION_","label":"使用Jenkins进行持续集成与发布流程图","attributes":{},"skip":false,"key":"2.2.6"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.7","level":"2.2","list_caption":"Figure: filebeat日志收集架构图","alt":"filebeat日志收集架构图","nro":11,"url":"../images/filebeat-log-collector-arch.png","index":7,"caption_template":"图片 - _CAPTION_","label":"filebeat日志收集架构图","attributes":{},"skip":false,"key":"2.2.7"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.8","level":"2.2","list_caption":"Figure: API文档","alt":"API文档","nro":12,"url":"../images/k8s-app-monitor-test-api-doc.jpg","index":8,"caption_template":"图片 - _CAPTION_","label":"API文档","attributes":{},"skip":false,"key":"2.2.8"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.9","level":"2.2","list_caption":"Figure: 迁移步骤示意图","alt":"迁移步骤示意图","nro":13,"url":"../images/migrating-hadoop-yarn-to-kubernetes.png","index":9,"caption_template":"图片 - _CAPTION_","label":"迁移步骤示意图","attributes":{},"skip":false,"key":"2.2.9"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.10","level":"2.2","list_caption":"Figure: service mesh架构图","alt":"service mesh架构图","nro":14,"url":"../images/serivce-mesh-control-plane.png","index":10,"caption_template":"图片 - _CAPTION_","label":"service mesh架构图","attributes":{},"skip":false,"key":"2.2.10"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.11","level":"2.2","list_caption":"Figure: kibana界面","alt":"kibana界面","nro":15,"url":"../images/filebeat-docker-test.jpg","index":11,"caption_template":"图片 - _CAPTION_","label":"kibana界面","attributes":{},"skip":false,"key":"2.2.11"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.12","level":"2.2","list_caption":"Figure: Grafana界面示意图1","alt":"Grafana界面示意图1","nro":16,"url":"../images/kubernetes-devops-example-grafana-1.png","index":12,"caption_template":"图片 - _CAPTION_","label":"Grafana界面示意图1","attributes":{},"skip":false,"key":"2.2.12"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.13","level":"2.2","list_caption":"Figure: Grafana界面示意图2","alt":"Grafana界面示意图2","nro":17,"url":"../images/kubernetes-devops-example-grafana-2.png","index":13,"caption_template":"图片 - _CAPTION_","label":"Grafana界面示意图2","attributes":{},"skip":false,"key":"2.2.13"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.14","level":"2.2","list_caption":"Figure: Grafana界面示意图3","alt":"Grafana界面示意图3","nro":18,"url":"../images/kubernetes-devops-example-grafana-3.png","index":14,"caption_template":"图片 - _CAPTION_","label":"Grafana界面示意图3","attributes":{},"skip":false,"key":"2.2.14"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.15","level":"2.2","list_caption":"Figure: dashboard","alt":"dashboard","nro":19,"url":"../images/spark-job-on-kubernetes-example-1.jpg","index":15,"caption_template":"图片 - _CAPTION_","label":"dashboard","attributes":{},"skip":false,"key":"2.2.15"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.2.16","level":"2.2","list_caption":"Figure: Grafana","alt":"Grafana","nro":20,"url":"../images/spark-job-on-kubernetes-example-2.jpg","index":16,"caption_template":"图片 - _CAPTION_","label":"Grafana","attributes":{},"skip":false,"key":"2.2.16"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.1","level":"2.3","list_caption":"Figure: Cloud Native容器实验室","alt":"Cloud Native容器实验室","nro":21,"url":"https://res.cloudinary.com/jimmysong/image/upload/images/cloud-native-container-lab.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Cloud Native容器实验室","attributes":{},"skip":false,"key":"2.3.1"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.2","level":"2.3","list_caption":"Figure: 容器生态图 Container ecosystem","alt":"容器生态图 Container ecosystem","nro":22,"url":"../images/container-ecosystem.png","index":2,"caption_template":"图片 - _CAPTION_","label":"容器生态图 Container ecosystem","attributes":{},"skip":false,"key":"2.3.2"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.3","level":"2.3","list_caption":"Figure: Cloud Native油井","alt":"Cloud Native油井","nro":23,"url":"https://res.cloudinary.com/jimmysong/image/upload/images/cloud-native-oil-well.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"Cloud Native油井","attributes":{},"skip":false,"key":"2.3.3"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.4","level":"2.3","list_caption":"Figure: Kubernetes架构","alt":"Kubernetes架构","nro":24,"url":"../images/kubernetes-high-level-component-archtecture.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"Kubernetes架构","attributes":{},"skip":false,"key":"2.3.4"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.5","level":"2.3","list_caption":"Figure: Cloud Native Core target","alt":"Cloud Native Core target","nro":25,"url":"../images/cloud-native-core-target.jpg","index":5,"caption_template":"图片 - _CAPTION_","label":"Cloud Native Core target","attributes":{},"skip":false,"key":"2.3.5"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.6","level":"2.3","list_caption":"Figure: FaaS Landscape","alt":"FaaS Landscape","nro":26,"url":"../images/redpoint-faas-landscape.jpg","index":6,"caption_template":"图片 - _CAPTION_","label":"FaaS Landscape","attributes":{},"skip":false,"key":"2.3.6"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.7","level":"2.3","list_caption":"Figure: Workloads running on Kubernetes","alt":"Workloads running on Kubernetes","nro":27,"url":"https://res.cloudinary.com/jimmysong/image/upload/images/workloads-running-on-kubernetes-2017-thenewstack.jpg","index":7,"caption_template":"图片 - _CAPTION_","label":"Workloads running on Kubernetes","attributes":{},"skip":false,"key":"2.3.7"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.8","level":"2.3","list_caption":"Figure: Gartner技术爆发趋势图2017","alt":"Gartner技术爆发趋势图2017","nro":28,"url":"https://res.cloudinary.com/jimmysong/image/upload/images/gartner-hype-cycle-for-emerging-technologies-2017.jpg","index":8,"caption_template":"图片 - _CAPTION_","label":"Gartner技术爆发趋势图2017","attributes":{},"skip":false,"key":"2.3.8"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.9","level":"2.3","list_caption":"Figure: Microservices concerns","alt":"Microservices concerns","nro":29,"url":"../images/microservices-concerns.jpg","index":9,"caption_template":"图片 - _CAPTION_","label":"Microservices concerns","attributes":{},"skip":false,"key":"2.3.9"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.10","level":"2.3","list_caption":"Figure: 两种服务发现方式","alt":"两种服务发现方式","nro":30,"url":"../images/service-discovery-in-microservices.png","index":10,"caption_template":"图片 - _CAPTION_","label":"两种服务发现方式","attributes":{},"skip":false,"key":"2.3.10"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.11","level":"2.3","list_caption":"Figure: Cloud Native Pipeline","alt":"Cloud Native Pipeline","nro":31,"url":"https://res.cloudinary.com/jimmysong/image/upload/images/cloud-natvie-pipeline.jpg","index":11,"caption_template":"图片 - _CAPTION_","label":"Cloud Native Pipeline","attributes":{},"skip":false,"key":"2.3.11"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.12","level":"2.3","list_caption":"Figure: Cloud Native Features","alt":"Cloud Native Features","nro":32,"url":"https://jimmysong.io/kubernetes-handbook/images/cloud-native-architecutre-mindnode.jpg","index":12,"caption_template":"图片 - _CAPTION_","label":"Cloud Native Features","attributes":{},"skip":false,"key":"2.3.12"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.13","level":"2.3","list_caption":"Figure: Cloud Native Landscape v1.0","alt":"Cloud Native Landscape v1.0","nro":33,"url":"https://raw.githubusercontent.com/cncf/landscape/master/landscape/CloudNativeLandscape_v1.0.jpg","index":13,"caption_template":"图片 - _CAPTION_","label":"Cloud Native Landscape v1.0","attributes":{},"skip":false,"key":"2.3.13"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.14","level":"2.3","list_caption":"Figure: Building a Cloud Native Architecture with Kubernetes followed 12 factor app","alt":"Building a Cloud Native Architecture with Kubernetes followed 12 factor app","nro":34,"url":"../images/building-cloud-native-architecture-with-kubernetes.png","index":14,"caption_template":"图片 - _CAPTION_","label":"Building a Cloud Native Architecture with Kubernetes followed 12 factor app","attributes":{},"skip":false,"key":"2.3.14"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.15","level":"2.3","list_caption":"Figure: Creating Kubernetes native app","alt":"Creating Kubernetes native app","nro":35,"url":"../images/creating-kubernetes-native-app.jpg","index":15,"caption_template":"图片 - _CAPTION_","label":"Creating Kubernetes native app","attributes":{},"skip":false,"key":"2.3.15"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.16","level":"2.3","list_caption":"Figure: Service Mesh中国社区slogan","alt":"Service Mesh中国社区slogan","nro":36,"url":"https://res.cloudinary.com/jimmysong/image/upload/images/service-meshes-pro.jpg","index":16,"caption_template":"图片 - _CAPTION_","label":"Service Mesh中国社区slogan","attributes":{},"skip":false,"key":"2.3.16"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.17","level":"2.3","list_caption":"Figure: istio vs linkerd","alt":"istio vs linkerd","nro":37,"url":"../images/istio-vs-linkerd.jpg","index":17,"caption_template":"图片 - _CAPTION_","label":"istio vs linkerd","attributes":{},"skip":false,"key":"2.3.17"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.18","level":"2.3","list_caption":"Figure: Cloud Native factory","alt":"Cloud Native factory","nro":38,"url":"https://res.cloudinary.com/jimmysong/image/upload/images/cloud-native-factory.jpg","index":18,"caption_template":"图片 - _CAPTION_","label":"Cloud Native factory","attributes":{},"skip":false,"key":"2.3.18"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.19","level":"2.3","list_caption":"Figure: Deployment pipeline","alt":"Deployment pipeline","nro":39,"url":"https://res.cloudinary.com/jimmysong/image/upload/images/deployment-pipeline-comic.jpg","index":19,"caption_template":"图片 - _CAPTION_","label":"Deployment pipeline","attributes":{},"skip":false,"key":"2.3.19"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.20","level":"2.3","list_caption":"Figure: Spark on Kubernetes with different schedulers","alt":"Spark on Kubernetes with different schedulers","nro":40,"url":"../images/spark-on-kubernetes-with-different-schedulers.jpg","index":20,"caption_template":"图片 - _CAPTION_","label":"Spark on Kubernetes with different schedulers","attributes":{},"skip":false,"key":"2.3.20"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.21","level":"2.3","list_caption":"Figure: Kubernetes solutions","alt":"Kubernetes solutions","nro":41,"url":"https://res.cloudinary.com/jimmysong/image/upload/images/kubernetes-solutions-choices.jpg","index":21,"caption_template":"图片 - _CAPTION_","label":"Kubernetes solutions","attributes":{},"skip":false,"key":"2.3.21"},{"backlink":"cloud-native/from-kubernetes-to-cloud-native.html#fig2.3.22","level":"2.3","list_caption":"Figure: Kubernetes SIG","alt":"Kubernetes SIG","nro":42,"url":"../images/kubernetes-sigs.jpg","index":22,"caption_template":"图片 - _CAPTION_","label":"Kubernetes SIG","attributes":{},"skip":false,"key":"2.3.22"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.4.1.1","level":"2.4.1","list_caption":"Figure: 云原生编程语言ballerina","alt":"云原生编程语言ballerina","nro":43,"url":"../images/philosophy-page-diagrams-top.png","index":1,"caption_template":"图片 - _CAPTION_","label":"云原生编程语言ballerina","attributes":{},"skip":false,"key":"2.4.1.1"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.4.1.2","level":"2.4.1","list_caption":"Figure: 云原生编程语言Ballerina的序列图设计理念","alt":"云原生编程语言Ballerina的序列图设计理念","nro":44,"url":"../images/philosophy-principle-diagrams-01.png","index":2,"caption_template":"图片 - _CAPTION_","label":"云原生编程语言Ballerina的序列图设计理念","attributes":{},"skip":false,"key":"2.4.1.2"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.4.1.3","level":"2.4.1","list_caption":"Figure: 云原生编程语言Ballerina的并发理念","alt":"云原生编程语言Ballerina的并发理念","nro":45,"url":"../images/philosophy-principle-diagrams-02.png","index":3,"caption_template":"图片 - _CAPTION_","label":"云原生编程语言Ballerina的并发理念","attributes":{},"skip":false,"key":"2.4.1.3"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.4.1.4","level":"2.4.1","list_caption":"Figure: 云原生编程语言ballerina运行时架构","alt":"云原生编程语言ballerina运行时架构","nro":46,"url":"../images/philosophy-diagrams-for-site-02.png","index":4,"caption_template":"图片 - _CAPTION_","label":"云原生编程语言ballerina运行时架构","attributes":{},"skip":false,"key":"2.4.1.4"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.4.1.5","level":"2.4.1","list_caption":"Figure: 云原生编程语言ballerina部署架构图","alt":"云原生编程语言ballerina部署架构图","nro":47,"url":"../images/philosophy-diagrams-for-site-03.png","index":5,"caption_template":"图片 - _CAPTION_","label":"云原生编程语言ballerina部署架构图","attributes":{},"skip":false,"key":"2.4.1.5"},{"backlink":"cloud-native/cloud-native-programming-language-ballerina.html#fig2.4.1.6","level":"2.4.1","list_caption":"Figure: 云原生编程语言ballerina生命周期架构图","alt":"云原生编程语言ballerina生命周期架构图","nro":48,"url":"../images/philosophy-diagrams-for-site-04.png","index":6,"caption_template":"图片 - _CAPTION_","label":"云原生编程语言ballerina生命周期架构图","attributes":{},"skip":false,"key":"2.4.1.6"},{"backlink":"cloud-native/cloud-native-programming-language-pulumi.html#fig2.4.2.1","level":"2.4.2","list_caption":"Figure: 云原生编程语言Pulumi","alt":"云原生编程语言Pulumi","nro":49,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsm4v0a6qwj30xc0m8t9d.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"云原生编程语言Pulumi","attributes":{},"skip":false,"key":"2.4.2.1"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.5.1","level":"2.5","list_caption":"Figure: Kubernetes 云原生的操作系统","alt":"Kubernetes 云原生的操作系统","nro":50,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1frr4z08j6oj31p20w2n6n.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Kubernetes 云原生的操作系统","attributes":{},"skip":false,"key":"2.5.1"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.5.2","level":"2.5","list_caption":"Figure: 操作系统层次","alt":"操作系统层次","nro":51,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1frr52hl4eaj31qy15en74.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"操作系统层次","attributes":{},"skip":false,"key":"2.5.2"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.5.3","level":"2.5","list_caption":"Figure: 云原生景观图","alt":"云原生景观图","nro":52,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1frr53j3aiuj32fs1dc7wi.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"云原生景观图","attributes":{},"skip":false,"key":"2.5.3"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.5.4","level":"2.5","list_caption":"Figure: KubeVirt架构图","alt":"KubeVirt架构图","nro":53,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1frr54de5oyj31qw14qn2x.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"KubeVirt架构图","attributes":{},"skip":false,"key":"2.5.4"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.5.5","level":"2.5","list_caption":"Figure: Kubernetes中的资源隔离","alt":"Kubernetes中的资源隔离","nro":54,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1frr54ztql2j329q0zwwlf.jpg","index":5,"caption_template":"图片 - _CAPTION_","label":"Kubernetes中的资源隔离","attributes":{},"skip":false,"key":"2.5.5"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.5.6","level":"2.5","list_caption":"Figure: Istio Service Mesh架构图","alt":"Istio Service Mesh架构图","nro":55,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1frr5exqm7kj320u18mh2t.jpg","index":6,"caption_template":"图片 - _CAPTION_","label":"Istio Service Mesh架构图","attributes":{},"skip":false,"key":"2.5.6"},{"backlink":"cloud-native/the-future-of-cloud-native.html#fig2.5.7","level":"2.5","list_caption":"Figure: Envoy proxy架构图","alt":"Envoy proxy架构图","nro":56,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1frr5gloob0j31vi18017p.jpg","index":7,"caption_template":"图片 - _CAPTION_","label":"Envoy proxy架构图","attributes":{},"skip":false,"key":"2.5.7"},{"backlink":"concepts/index.html#fig3.1.1","level":"3.1","list_caption":"Figure: Borg架构","alt":"Borg架构","nro":57,"url":"../images/borg.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Borg架构","attributes":{},"skip":false,"key":"3.1.1"},{"backlink":"concepts/index.html#fig3.1.2","level":"3.1","list_caption":"Figure: Kubernetes架构","alt":"Kubernetes架构","nro":58,"url":"../images/architecture.png","index":2,"caption_template":"图片 - _CAPTION_","label":"Kubernetes架构","attributes":{},"skip":false,"key":"3.1.2"},{"backlink":"concepts/index.html#fig3.1.3","level":"3.1","list_caption":"Figure: Kuberentes架构（图片来自于网络）","alt":"Kuberentes架构（图片来自于网络）","nro":59,"url":"../images/kubernetes-high-level-component-archtecture.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"Kuberentes架构（图片来自于网络）","attributes":{},"skip":false,"key":"3.1.3"},{"backlink":"concepts/index.html#fig3.1.4","level":"3.1","list_caption":"Figure: kubernetes整体架构示意图","alt":"kubernetes整体架构示意图","nro":60,"url":"../images/kubernetes-whole-arch.png","index":4,"caption_template":"图片 - _CAPTION_","label":"kubernetes整体架构示意图","attributes":{},"skip":false,"key":"3.1.4"},{"backlink":"concepts/index.html#fig3.1.5","level":"3.1","list_caption":"Figure: Kubernetes master架构示意图","alt":"Kubernetes master架构示意图","nro":61,"url":"../images/kubernetes-master-arch.png","index":5,"caption_template":"图片 - _CAPTION_","label":"Kubernetes master架构示意图","attributes":{},"skip":false,"key":"3.1.5"},{"backlink":"concepts/index.html#fig3.1.6","level":"3.1","list_caption":"Figure: kubernetes node架构示意图","alt":"kubernetes node架构示意图","nro":62,"url":"../images/kubernetes-node-arch.png","index":6,"caption_template":"图片 - _CAPTION_","label":"kubernetes node架构示意图","attributes":{},"skip":false,"key":"3.1.6"},{"backlink":"concepts/index.html#fig3.1.7","level":"3.1","list_caption":"Figure: Kubernetes分层架构示意图","alt":"Kubernetes分层架构示意图","nro":63,"url":"../images/kubernetes-layers-arch.jpg","index":7,"caption_template":"图片 - _CAPTION_","label":"Kubernetes分层架构示意图","attributes":{},"skip":false,"key":"3.1.7"},{"backlink":"concepts/concepts.html#fig3.1.1.1","level":"3.1.1","list_caption":"Figure: 分层架构示意图","alt":"分层架构示意图","nro":64,"url":"../images/kubernetes-layers-arch.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"分层架构示意图","attributes":{},"skip":false,"key":"3.1.1.1"},{"backlink":"concepts/open-interfaces.html#fig3.1.3.1","level":"3.1.3","list_caption":"Figure: 开放接口","alt":"开放接口","nro":65,"url":"../images/open-interfaces.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"开放接口","attributes":{},"skip":false,"key":"3.1.3.1"},{"backlink":"concepts/cri.html#fig3.1.3.1.1","level":"3.1.3.1","list_caption":"Figure: CRI架构-图片来自kubernetes blog","alt":"CRI架构-图片来自kubernetes blog","nro":66,"url":"../images/cri-architecture.png","index":1,"caption_template":"图片 - _CAPTION_","label":"CRI架构-图片来自kubernetes blog","attributes":{},"skip":false,"key":"3.1.3.1.1"},{"backlink":"concepts/networking.html#fig3.2.1.1","level":"3.2.1","list_caption":"Figure: flannel网络架构（图片来自openshift）","alt":"flannel网络架构（图片来自openshift）","nro":67,"url":"../images/flannel-networking.png","index":1,"caption_template":"图片 - _CAPTION_","label":"flannel网络架构（图片来自openshift）","attributes":{},"skip":false,"key":"3.2.1.1"},{"backlink":"concepts/calico.html#fig3.2.2.1","level":"3.2.2","list_caption":"Figure: CRI架构-图片来自https://www.jianshu.com/p/f0177b84de66","alt":"CRI架构-图片来自https://www.jianshu.com/p/f0177b84de66","nro":68,"url":"../images/calico.png","index":1,"caption_template":"图片 - _CAPTION_","label":"CRI架构-图片来自https://www.jianshu.com/p/f0177b84de66","attributes":{},"skip":false,"key":"3.2.2.1"},{"backlink":"concepts/pod-overview.html#fig3.4.1.1","level":"3.4.1","list_caption":"Figure: pod diagram","alt":"pod diagram","nro":69,"url":"../images/pod-overview.png","index":1,"caption_template":"图片 - _CAPTION_","label":"pod diagram","attributes":{},"skip":false,"key":"3.4.1.1"},{"backlink":"concepts/pod.html#fig3.4.2.1","level":"3.4.2","list_caption":"Figure: Pod示意图","alt":"Pod示意图","nro":70,"url":"../images/pod-overview.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Pod示意图","attributes":{},"skip":false,"key":"3.4.2.1"},{"backlink":"concepts/pod.html#fig3.4.2.2","level":"3.4.2","list_caption":"Figure: Pod Cheatsheet","alt":"Pod Cheatsheet","nro":71,"url":"../images/kubernetes-pod-cheatsheet.png","index":2,"caption_template":"图片 - _CAPTION_","label":"Pod Cheatsheet","attributes":{},"skip":false,"key":"3.4.2.2"},{"backlink":"concepts/pause-container.html#fig3.4.4.1","level":"3.4.4","list_caption":"Figure: Pause容器","alt":"Pause容器","nro":72,"url":"../images/pause-container.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Pause容器","attributes":{},"skip":false,"key":"3.4.4.1"},{"backlink":"concepts/pod-lifecycle.html#fig3.4.6.1","level":"3.4.6","list_caption":"Figure: Pod的生命周期示意图（图片来自网络）","alt":"Pod的生命周期示意图（图片来自网络）","nro":73,"url":"../images/kubernetes-pod-life-cycle.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Pod的生命周期示意图（图片来自网络）","attributes":{},"skip":false,"key":"3.4.6.1"},{"backlink":"concepts/label.html#fig3.5.3.1","level":"3.5.3","list_caption":"Figure: label示意图","alt":"label示意图","nro":74,"url":"../images/labels.png","index":1,"caption_template":"图片 - _CAPTION_","label":"label示意图","attributes":{},"skip":false,"key":"3.5.3.1"},{"backlink":"concepts/deployment.html#fig3.6.1.1","level":"3.6.1","list_caption":"Figure: kubernetes deployment cheatsheet","alt":"kubernetes deployment cheatsheet","nro":75,"url":"../images/deployment-cheatsheet.png","index":1,"caption_template":"图片 - _CAPTION_","label":"kubernetes deployment cheatsheet","attributes":{},"skip":false,"key":"3.6.1.1"},{"backlink":"concepts/horizontal-pod-autoscaling.html#fig3.6.7.1","level":"3.6.7","list_caption":"Figure: horizontal-pod-autoscaler","alt":"horizontal-pod-autoscaler","nro":76,"url":"../images/horizontal-pod-autoscaler.png","index":1,"caption_template":"图片 - _CAPTION_","label":"horizontal-pod-autoscaler","attributes":{},"skip":false,"key":"3.6.7.1"},{"backlink":"concepts/service.html#fig3.7.1.1","level":"3.7.1","list_caption":"Figure: userspace代理模式下Service概览图","alt":"userspace代理模式下Service概览图","nro":77,"url":"../images/services-userspace-overview.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"userspace代理模式下Service概览图","attributes":{},"skip":false,"key":"3.7.1.1"},{"backlink":"concepts/service.html#fig3.7.1.2","level":"3.7.1","list_caption":"Figure: iptables代理模式下Service概览图","alt":"iptables代理模式下Service概览图","nro":78,"url":"../images/services-iptables-overview.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"iptables代理模式下Service概览图","attributes":{},"skip":false,"key":"3.7.1.2"},{"backlink":"concepts/service-catalog.html#fig3.10.4.1","level":"3.10.4","list_caption":"Figure: Service Catalog Architecture","alt":"Service Catalog Architecture","nro":79,"url":"../images/service-catalog-architecture.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Service Catalog Architecture","attributes":{},"skip":false,"key":"3.10.4.1"},{"backlink":"concepts/service-catalog.html#fig3.10.4.2","level":"3.10.4","list_caption":"Figure: List Services","alt":"List Services","nro":80,"url":"../images/service-catalog-list.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"List Services","attributes":{},"skip":false,"key":"3.10.4.2"},{"backlink":"concepts/service-catalog.html#fig3.10.4.3","level":"3.10.4","list_caption":"Figure: Provision a Service","alt":"Provision a Service","nro":81,"url":"../images/service-catalog-provision.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"Provision a Service","attributes":{},"skip":false,"key":"3.10.4.3"},{"backlink":"concepts/service-catalog.html#fig3.10.4.4","level":"3.10.4","list_caption":"Figure: Bind to a managed service","alt":"Bind to a managed service","nro":82,"url":"../images/service-catalog-bind.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"Bind to a managed service","attributes":{},"skip":false,"key":"3.10.4.4"},{"backlink":"concepts/service-catalog.html#fig3.10.4.5","level":"3.10.4","list_caption":"Figure: Map connection credentials","alt":"Map connection credentials","nro":83,"url":"../images/service-catalog-map.jpg","index":5,"caption_template":"图片 - _CAPTION_","label":"Map connection credentials","attributes":{},"skip":false,"key":"3.10.4.5"},{"backlink":"guide/using-kubectl.html#fig4.3.2.1","level":"4.3.2","list_caption":"Figure: kubectl cheatsheet","alt":"kubectl cheatsheet","nro":84,"url":"../images/kubernetes-kubectl-cheatsheet.png","index":1,"caption_template":"图片 - _CAPTION_","label":"kubectl cheatsheet","attributes":{},"skip":false,"key":"4.3.2.1"},{"backlink":"guide/using-kubectl.html#fig4.3.2.2","level":"4.3.2","list_caption":"Figure: 增加kubeclt命令的工具（图片来自网络）","alt":"增加kubeclt命令的工具（图片来自网络）","nro":85,"url":"../images/tools-to-supercharge-kubectl.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"增加kubeclt命令的工具（图片来自网络）","attributes":{},"skip":false,"key":"4.3.2.2"},{"backlink":"guide/using-kubectl.html#fig4.3.2.3","level":"4.3.2","list_caption":"Figure: 增强的kubectl命令","alt":"增强的kubectl命令","nro":86,"url":"../images/supercharged-kubectl.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"增强的kubectl命令","attributes":{},"skip":false,"key":"4.3.2.3"},{"backlink":"guide/using-kubectl.html#fig4.3.2.4","level":"4.3.2","list_caption":"Figure: kube-shell页面","alt":"kube-shell页面","nro":87,"url":"../images/kube-shell.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"kube-shell页面","attributes":{},"skip":false,"key":"4.3.2.4"},{"backlink":"guide/ip-masq-agent.html#fig4.4.5.1","level":"4.4.5","list_caption":"Figure: IP伪装代理示意图","alt":"IP伪装代理示意图","nro":88,"url":"../images/ip-masq.png","index":1,"caption_template":"图片 - _CAPTION_","label":"IP伪装代理示意图","attributes":{},"skip":false,"key":"4.4.5.1"},{"backlink":"guide/auth-with-kubeconfig-or-token.html#fig4.4.6.1","level":"4.4.6","list_caption":"Figure: kubeconfig文件","alt":"kubeconfig文件","nro":89,"url":"../images/brand-kubeconfig-yaml.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"kubeconfig文件","attributes":{},"skip":false,"key":"4.4.6.1"},{"backlink":"guide/authentication.html#fig4.4.7.1","level":"4.4.7","list_caption":"Figure: Kubernetes OpenID Connect Flow","alt":"Kubernetes OpenID Connect Flow","nro":90,"url":"../images/kubernetes-oidc-login.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Kubernetes OpenID Connect Flow","attributes":{},"skip":false,"key":"4.4.7.1"},{"backlink":"guide/cabin-mobile-dashboard-for-kubernetes.html#fig4.5.6.1","level":"4.5.6","list_caption":"Figure: App Store","alt":"App Store","nro":91,"url":"../images/cabin-kubernetes-mobile-dashboard-1.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"App Store","attributes":{},"skip":false,"key":"4.5.6.1"},{"backlink":"guide/cabin-mobile-dashboard-for-kubernetes.html#fig4.5.6.2","level":"4.5.6","list_caption":"Figure: 在手机上操作Kubernetes集群","alt":"在手机上操作Kubernetes集群","nro":92,"url":"../images/cabin-kubernetes-mobile-dashboard-4.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"在手机上操作Kubernetes集群","attributes":{},"skip":false,"key":"4.5.6.2"},{"backlink":"guide/kubernetes-desktop-client.html#fig4.5.7.1","level":"4.5.7","list_caption":"Figure: Kubernetic客户端","alt":"Kubernetic客户端","nro":93,"url":"../images/kubernetic-desktop-ui.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Kubernetic客户端","attributes":{},"skip":false,"key":"4.5.7.1"},{"backlink":"guide/kubernator-kubernetes-ui.html#fig4.5.8.1","level":"4.5.8","list_caption":"Figure: Kubernator catalog页面","alt":"Kubernator catalog页面","nro":94,"url":"../images/kubernator-catalog.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Kubernator catalog页面","attributes":{},"skip":false,"key":"4.5.8.1"},{"backlink":"guide/kubernator-kubernetes-ui.html#fig4.5.8.2","level":"4.5.8","list_caption":"Figure: Kubernator rbac页面","alt":"Kubernator rbac页面","nro":95,"url":"../images/kubernator-rbac.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"Kubernator rbac页面","attributes":{},"skip":false,"key":"4.5.8.2"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.1","level":"4.6.1","list_caption":"Figure: 流程图","alt":"流程图","nro":96,"url":"../images/how-to-use-kubernetes-with-istio.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"流程图","attributes":{},"skip":false,"key":"4.6.1.1"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.2","level":"4.6.1","list_caption":"Figure: API","alt":"API","nro":97,"url":"../images/k8s-app-monitor-test-api-doc.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"API","attributes":{},"skip":false,"key":"4.6.1.2"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.3","level":"4.6.1","list_caption":"Figure: wercker构建页面","alt":"wercker构建页面","nro":98,"url":"../images/k8s-app-monitor-agent-wercker.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"wercker构建页面","attributes":{},"skip":false,"key":"4.6.1.3"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.4","level":"4.6.1","list_caption":"Figure: 图表","alt":"图表","nro":99,"url":"../images/k8s-app-monitor-agent.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"图表","attributes":{},"skip":false,"key":"4.6.1.4"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.5","level":"4.6.1","list_caption":"Figure: Grafana页面","alt":"Grafana页面","nro":100,"url":"../images/k8s-app-monitor-istio-grafana.png","index":5,"caption_template":"图片 - _CAPTION_","label":"Grafana页面","attributes":{},"skip":false,"key":"4.6.1.5"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.6","level":"4.6.1","list_caption":"Figure: servicegraph页面","alt":"servicegraph页面","nro":101,"url":"../images/k8s-app-monitor-istio-servicegraph-dotviz.png","index":6,"caption_template":"图片 - _CAPTION_","label":"servicegraph页面","attributes":{},"skip":false,"key":"4.6.1.6"},{"backlink":"guide/deploy-applications-in-kubernetes.html#fig4.6.1.7","level":"4.6.1","list_caption":"Figure: Zipkin页面","alt":"Zipkin页面","nro":102,"url":"../images/k8s-app-monitor-istio-zipkin.png","index":7,"caption_template":"图片 - _CAPTION_","label":"Zipkin页面","attributes":{},"skip":false,"key":"4.6.1.7"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig4.6.2.1","level":"4.6.2","list_caption":"Figure: 将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","alt":"将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","nro":103,"url":"../images/migrating-monolith-to-kubernetes.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"将单体应用迁移到云原生(图片来自DevOpsDay Toronto)","attributes":{},"skip":false,"key":"4.6.2.1"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig4.6.2.2","level":"4.6.2","list_caption":"Figure: spark on yarn with kubernetes","alt":"spark on yarn with kubernetes","nro":104,"url":"../images/spark-on-yarn-with-kubernetes.png","index":2,"caption_template":"图片 - _CAPTION_","label":"spark on yarn with kubernetes","attributes":{},"skip":false,"key":"4.6.2.2"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig4.6.2.3","level":"4.6.2","list_caption":"Figure: Terms","alt":"Terms","nro":105,"url":"../images/terms-in-kubernetes-app-deployment.png","index":3,"caption_template":"图片 - _CAPTION_","label":"Terms","attributes":{},"skip":false,"key":"4.6.2.3"},{"backlink":"guide/migrating-hadoop-yarn-to-kubernetes.html#fig4.6.2.4","level":"4.6.2","list_caption":"Figure: 分解步骤解析","alt":"分解步骤解析","nro":106,"url":"../images/migrating-hadoop-yarn-to-kubernetes.png","index":4,"caption_template":"图片 - _CAPTION_","label":"分解步骤解析","attributes":{},"skip":false,"key":"4.6.2.4"},{"backlink":"practice/node-installation.html#fig5.2.7.1","level":"5.2.7","list_caption":"Figure: welcome nginx","alt":"welcome nginx","nro":107,"url":"../images/kubernetes-installation-test-nginx.png","index":1,"caption_template":"图片 - _CAPTION_","label":"welcome nginx","attributes":{},"skip":false,"key":"5.2.7.1"},{"backlink":"practice/dashboard-addon-installation.html#fig5.2.9.1","level":"5.2.9","list_caption":"Figure: kubernetes dashboard","alt":"kubernetes dashboard","nro":108,"url":"../images/kubernetes-dashboard-raw.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"kubernetes dashboard","attributes":{},"skip":false,"key":"5.2.9.1"},{"backlink":"practice/dashboard-addon-installation.html#fig5.2.9.2","level":"5.2.9","list_caption":"Figure: V1.6.3版本的dashboard界面","alt":"V1.6.3版本的dashboard界面","nro":109,"url":"../images/dashboard-v163.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"V1.6.3版本的dashboard界面","attributes":{},"skip":false,"key":"5.2.9.2"},{"backlink":"practice/dashboard-addon-installation.html#fig5.2.9.3","level":"5.2.9","list_caption":"Figure: pod无法正常启动","alt":"pod无法正常启动","nro":110,"url":"../images/dashboard-addon-installation001.png","index":3,"caption_template":"图片 - _CAPTION_","label":"pod无法正常启动","attributes":{},"skip":false,"key":"5.2.9.3"},{"backlink":"practice/heapster-addon-installation.html#fig5.2.10.1","level":"5.2.10","list_caption":"Figure: dashboard-heapster","alt":"dashboard-heapster","nro":111,"url":"../images/kubernetes-dashboard-with-heapster.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"dashboard-heapster","attributes":{},"skip":false,"key":"5.2.10.1"},{"backlink":"practice/heapster-addon-installation.html#fig5.2.10.2","level":"5.2.10","list_caption":"Figure: grafana","alt":"grafana","nro":112,"url":"../images/kubernetes-heapster-grafana.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"grafana","attributes":{},"skip":false,"key":"5.2.10.2"},{"backlink":"practice/heapster-addon-installation.html#fig5.2.10.3","level":"5.2.10","list_caption":"Figure: kubernetes-influxdb-heapster","alt":"kubernetes-influxdb-heapster","nro":113,"url":"../images/kubernetes-influxdb-heapster.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"kubernetes-influxdb-heapster","attributes":{},"skip":false,"key":"5.2.10.3"},{"backlink":"practice/heapster-addon-installation.html#fig5.2.10.4","level":"5.2.10","list_caption":"Figure: 修改grafana模板","alt":"修改grafana模板","nro":114,"url":"../images/grafana-dashboard-setting.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"修改grafana模板","attributes":{},"skip":false,"key":"5.2.10.4"},{"backlink":"practice/efk-addon-installation.html#fig5.2.11.1","level":"5.2.11","list_caption":"Figure: es-setting","alt":"es-setting","nro":115,"url":"../images/es-setting.png","index":1,"caption_template":"图片 - _CAPTION_","label":"es-setting","attributes":{},"skip":false,"key":"5.2.11.1"},{"backlink":"practice/efk-addon-installation.html#fig5.2.11.2","level":"5.2.11","list_caption":"Figure: es-home","alt":"es-home","nro":116,"url":"../images/kubernetes-efk-kibana.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"es-home","attributes":{},"skip":false,"key":"5.2.11.2"},{"backlink":"practice/traefik-ingress-installation.html#fig5.4.1.1","level":"5.4.1","list_caption":"Figure: kubernetes-dashboard","alt":"kubernetes-dashboard","nro":117,"url":"../images/traefik-dashboard.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"kubernetes-dashboard","attributes":{},"skip":false,"key":"5.4.1.1"},{"backlink":"practice/traefik-ingress-installation.html#fig5.4.1.2","level":"5.4.1","list_caption":"Figure: traefik-nginx","alt":"traefik-nginx","nro":118,"url":"../images/traefik-nginx.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"traefik-nginx","attributes":{},"skip":false,"key":"5.4.1.2"},{"backlink":"practice/traefik-ingress-installation.html#fig5.4.1.3","level":"5.4.1","list_caption":"Figure: traefik-guestbook","alt":"traefik-guestbook","nro":119,"url":"../images/traefik-guestbook.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"traefik-guestbook","attributes":{},"skip":false,"key":"5.4.1.3"},{"backlink":"practice/distributed-load-test.html#fig5.4.2.1","level":"5.4.2","list_caption":"Figure: 使用dashboard来扩容","alt":"使用dashboard来扩容","nro":120,"url":"../images/dashbaord-scale.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"使用dashboard来扩容","attributes":{},"skip":false,"key":"5.4.2.1"},{"backlink":"practice/distributed-load-test.html#fig5.4.2.2","level":"5.4.2","list_caption":"Figure: Traefik的UI","alt":"Traefik的UI","nro":121,"url":"../images/traefik-dashboard-locust.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"Traefik的UI","attributes":{},"skip":false,"key":"5.4.2.2"},{"backlink":"practice/distributed-load-test.html#fig5.4.2.3","level":"5.4.2","list_caption":"Figure: Locust启动界面","alt":"Locust启动界面","nro":122,"url":"../images/locust-start-swarming.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"Locust启动界面","attributes":{},"skip":false,"key":"5.4.2.3"},{"backlink":"practice/distributed-load-test.html#fig5.4.2.4","level":"5.4.2","list_caption":"Figure: Dashboard查看页面","alt":"Dashboard查看页面","nro":123,"url":"../images/sample-webapp-rc.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"Dashboard查看页面","attributes":{},"skip":false,"key":"5.4.2.4"},{"backlink":"practice/distributed-load-test.html#fig5.4.2.5","level":"5.4.2","list_caption":"Figure: Locust测试结果页面","alt":"Locust测试结果页面","nro":124,"url":"../images/locust-dashboard.jpg","index":5,"caption_template":"图片 - _CAPTION_","label":"Locust测试结果页面","attributes":{},"skip":false,"key":"5.4.2.5"},{"backlink":"practice/network-and-cluster-perfermance-test.html#fig5.4.3.1","level":"5.4.3","list_caption":"Figure: kubernetes-dashboard","alt":"kubernetes-dashboard","nro":125,"url":"../images/kubenetes-e2e-test.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"kubernetes-dashboard","attributes":{},"skip":false,"key":"5.4.3.1"},{"backlink":"practice/network-and-cluster-perfermance-test.html#fig5.4.3.2","level":"5.4.3","list_caption":"Figure: locust测试页面","alt":"locust测试页面","nro":126,"url":"../images/kubernetes-locust-test.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"locust测试页面","attributes":{},"skip":false,"key":"5.4.3.2"},{"backlink":"practice/edge-node-configuration.html#fig5.4.4.1","level":"5.4.4","list_caption":"Figure: 边缘节点架构","alt":"边缘节点架构","nro":127,"url":"../images/kubernetes-edge-node-architecture.png","index":1,"caption_template":"图片 - _CAPTION_","label":"边缘节点架构","attributes":{},"skip":false,"key":"5.4.4.1"},{"backlink":"practice/edge-node-configuration.html#fig5.4.4.2","level":"5.4.4","list_caption":"Figure: 使用域名来访问Kubernetes中的服务","alt":"使用域名来访问Kubernetes中的服务","nro":128,"url":"../images/accessing-kubernetes-services-with-dns-name.png","index":2,"caption_template":"图片 - _CAPTION_","label":"使用域名来访问Kubernetes中的服务","attributes":{},"skip":false,"key":"5.4.4.2"},{"backlink":"practice/configuring-dns.html#fig5.4.6.1.1","level":"5.4.6.1","list_caption":"Figure: DNS lookup flow","alt":"DNS lookup flow","nro":129,"url":"https://d33wubrfki0l68.cloudfront.net/340889cb80e81dcd19a16bc34697a7907e2b229a/24ad0/docs/tasks/administer-cluster/dns-custom-nameservers/dns.png","index":1,"caption_template":"图片 - _CAPTION_","label":"DNS lookup flow","attributes":{},"skip":false,"key":"5.4.6.1.1"},{"backlink":"practice/master-ha.html#fig5.5.1.1","level":"5.5.1","list_caption":"Figure: Master HA架构图","alt":"Master HA架构图","nro":130,"url":"../images/master-ha.JPG","index":1,"caption_template":"图片 - _CAPTION_","label":"Master HA架构图","attributes":{},"skip":false,"key":"5.5.1.1"},{"backlink":"practice/app-log-collection.html#fig5.5.3.1","level":"5.5.3","list_caption":"Figure: filebeat日志收集架构图","alt":"filebeat日志收集架构图","nro":131,"url":"../images/filebeat-log-collector.png","index":1,"caption_template":"图片 - _CAPTION_","label":"filebeat日志收集架构图","attributes":{},"skip":false,"key":"5.5.3.1"},{"backlink":"practice/app-log-collection.html#fig5.5.3.2","level":"5.5.3","list_caption":"Figure: Kibana页面","alt":"Kibana页面","nro":132,"url":"../images/filebeat-docker-test.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"Kibana页面","attributes":{},"skip":false,"key":"5.5.3.2"},{"backlink":"practice/app-log-collection.html#fig5.5.3.3","level":"5.5.3","list_caption":"Figure: filebeat收集的日志详细信息","alt":"filebeat收集的日志详细信息","nro":133,"url":"../images/kubernetes-filebeat-detail.png","index":3,"caption_template":"图片 - _CAPTION_","label":"filebeat收集的日志详细信息","attributes":{},"skip":false,"key":"5.5.3.3"},{"backlink":"practice/monitor.html#fig5.5.5.1","level":"5.5.5","list_caption":"Figure: Kubernetes集群中的监控","alt":"Kubernetes集群中的监控","nro":134,"url":"../images/monitoring-in-kubernetes.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Kubernetes集群中的监控","attributes":{},"skip":false,"key":"5.5.5.1"},{"backlink":"practice/monitor.html#fig5.5.5.2","level":"5.5.5","list_caption":"Figure: kubernetes的容器命名规则示意图","alt":"kubernetes的容器命名规则示意图","nro":135,"url":"../images/kubernetes-container-naming-rule.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"kubernetes的容器命名规则示意图","attributes":{},"skip":false,"key":"5.5.5.2"},{"backlink":"practice/monitor.html#fig5.5.5.3","level":"5.5.5","list_caption":"Figure: Heapster架构图（改进版）","alt":"Heapster架构图（改进版）","nro":136,"url":"../images/kubernetes-heapster-monitoring.png","index":3,"caption_template":"图片 - _CAPTION_","label":"Heapster架构图（改进版）","attributes":{},"skip":false,"key":"5.5.5.3"},{"backlink":"practice/monitor.html#fig5.5.5.4","level":"5.5.5","list_caption":"Figure: 应用监控架构图","alt":"应用监控架构图","nro":137,"url":"../images/kubernetes-app-monitoring.png","index":4,"caption_template":"图片 - _CAPTION_","label":"应用监控架构图","attributes":{},"skip":false,"key":"5.5.5.4"},{"backlink":"practice/monitor.html#fig5.5.5.5","level":"5.5.5","list_caption":"Figure: 应用拓扑图","alt":"应用拓扑图","nro":138,"url":"../images/weave-scope-service-topology.jpg","index":5,"caption_template":"图片 - _CAPTION_","label":"应用拓扑图","attributes":{},"skip":false,"key":"5.5.5.5"},{"backlink":"practice/data-persistence-problem.html#fig5.5.6.1","level":"5.5.6","list_caption":"Figure: 日志持久化收集解决方案示意图","alt":"日志持久化收集解决方案示意图","nro":139,"url":"../images/log-persistence-logstash.png","index":1,"caption_template":"图片 - _CAPTION_","label":"日志持久化收集解决方案示意图","attributes":{},"skip":false,"key":"5.5.6.1"},{"backlink":"practice/storage-for-containers-using-glusterfs-with-openshift.html#fig5.6.1.3.1","level":"5.6.1.3","list_caption":"Figure: 创建存储","alt":"创建存储","nro":140,"url":"../images/create-gluster-storage.png","index":1,"caption_template":"图片 - _CAPTION_","label":"创建存储","attributes":{},"skip":false,"key":"5.6.1.3.1"},{"backlink":"practice/storage-for-containers-using-glusterfs-with-openshift.html#fig5.6.1.3.2","level":"5.6.1.3","list_caption":"Figure: Screen Shot 2017-03-24 at 11.09.34.png","alt":"Screen Shot 2017-03-24 at 11.09.34.png","nro":141,"url":"https://keithtenzer.files.wordpress.com/2017/03/screen-shot-2017-03-24-at-11-09-341.png?w=440","index":2,"caption_template":"图片 - _CAPTION_","label":"Screen Shot 2017-03-24 at 11.09.34.png","attributes":{},"skip":false,"key":"5.6.1.3.2"},{"backlink":"practice/openebs.html#fig5.6.4.1","level":"5.6.4","list_caption":"Figure: OpenEBS集群数据平面（图片来自https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","alt":"OpenEBS集群数据平面（图片来自https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","nro":142,"url":"../images/OpenEBS-Data-Plane.png","index":1,"caption_template":"图片 - _CAPTION_","label":"OpenEBS集群数据平面（图片来自https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","attributes":{},"skip":false,"key":"5.6.4.1"},{"backlink":"practice/openebs.html#fig5.6.4.2","level":"5.6.4","list_caption":"Figure: OpenEBS集群的控制平面(图片来自https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","alt":"OpenEBS集群的控制平面(图片来自https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","nro":143,"url":"../images/OpenEBS-Control-Plane.png","index":2,"caption_template":"图片 - _CAPTION_","label":"OpenEBS集群的控制平面(图片来自https://github.com/openebs/openebs/blob/master/contribute/design/README.md）","attributes":{},"skip":false,"key":"5.6.4.2"},{"backlink":"practice/using-openebs-for-persistent-storage.html#fig5.6.4.1.1","level":"5.6.4.1","list_caption":"Figure: Kubernetes iSCSI架构","alt":"Kubernetes iSCSI架构","nro":144,"url":"../images/iscsi-on-kubernetes.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Kubernetes iSCSI架构","attributes":{},"skip":false,"key":"5.6.4.1.1"},{"backlink":"practice/using-heapster-to-get-object-metrics.html#fig5.7.1.1.1","level":"5.7.1.1","list_caption":"Figure: Heapster架构图","alt":"Heapster架构图","nro":145,"url":"../images/heapster-architecture.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Heapster架构图","attributes":{},"skip":false,"key":"5.7.1.1.1"},{"backlink":"practice/prometheus.html#fig5.7.2.1","level":"5.7.2","list_caption":"Figure: Prometheus 架构图","alt":"Prometheus 架构图","nro":146,"url":"../images/prometheus-architecture.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Prometheus 架构图","attributes":{},"skip":false,"key":"5.7.2.1"},{"backlink":"practice/using-prometheus-to-monitor-kuberentes-cluster.html#fig5.7.2.1.1","level":"5.7.2.1","list_caption":"Figure: Grafana页面","alt":"Grafana页面","nro":147,"url":"../images/kubernetes-prometheus-monitoring.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Grafana页面","attributes":{},"skip":false,"key":"5.7.2.1.1"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.1","level":"5.7.3","list_caption":"Figure: Vistio的集群级别可视化","alt":"Vistio的集群级别可视化","nro":148,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fshft5oxlwj318g0pe0wp.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Vistio的集群级别可视化","attributes":{},"skip":false,"key":"5.7.3.1"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.2","level":"5.7.3","list_caption":"Figure: Prometheus查询","alt":"Prometheus查询","nro":149,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fshg0vw25ij318g0jzqjq.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"Prometheus查询","attributes":{},"skip":false,"key":"5.7.3.2"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.3","level":"5.7.3","list_caption":"Figure: vistio-api的期望输出","alt":"vistio-api的期望输出","nro":150,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fshi61t04oj310q17c0y1.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"vistio-api的期望输出","attributes":{},"skip":false,"key":"5.7.3.3"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.4","level":"5.7.3","list_caption":"Figure: Vistio主页面","alt":"Vistio主页面","nro":151,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fshi98duzgj318g0l2406.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"Vistio主页面","attributes":{},"skip":false,"key":"5.7.3.4"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.5","level":"5.7.3","list_caption":"Figure: istio mesh的网络流量","alt":"istio mesh的网络流量","nro":152,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fshibdwcj3j318g0p8th1.jpg","index":5,"caption_template":"图片 - _CAPTION_","label":"istio mesh的网络流量","attributes":{},"skip":false,"key":"5.7.3.5"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.6","level":"5.7.3","list_caption":"Figure: 查明网络问题","alt":"查明网络问题","nro":153,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fshicc7or1j318g0p8ahr.jpg","index":6,"caption_template":"图片 - _CAPTION_","label":"查明网络问题","attributes":{},"skip":false,"key":"5.7.3.6"},{"backlink":"practice/vistio-visualize-your-istio-mesh.html#fig5.7.3.7","level":"5.7.3","list_caption":"Figure: vistio api的不正确输出","alt":"vistio api的不正确输出","nro":154,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fshie7wxkyj30ks0f4myd.jpg","index":7,"caption_template":"图片 - _CAPTION_","label":"vistio api的不正确输出","attributes":{},"skip":false,"key":"5.7.3.7"},{"backlink":"practice/helm.html#fig5.8.1.1","level":"5.8.1","list_caption":"Figure: Helm chart源","alt":"Helm chart源","nro":155,"url":"../images/helm-charts-repository.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Helm chart源","attributes":{},"skip":false,"key":"5.8.1.1"},{"backlink":"practice/helm.html#fig5.8.1.2","level":"5.8.1","list_caption":"Figure: TODO应用的Web页面","alt":"TODO应用的Web页面","nro":156,"url":"../images/helm-mean-todo-aholic.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"TODO应用的Web页面","attributes":{},"skip":false,"key":"5.8.1.2"},{"backlink":"practice/create-private-charts-repo.html#fig5.8.2.1","level":"5.8.2","list_caption":"Figure: Helm monocular界面","alt":"Helm monocular界面","nro":157,"url":"../images/helm-monocular-jimmysong.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Helm monocular界面","attributes":{},"skip":false,"key":"5.8.2.1"},{"backlink":"practice/ci-cd.html#fig5.9.1","level":"5.9","list_caption":"Figure: CI/CD with Kubernetes","alt":"CI/CD with Kubernetes","nro":158,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsaxszh01vj30da0j2jvn.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"CI/CD with Kubernetes","attributes":{},"skip":false,"key":"5.9.1"},{"backlink":"practice/ci-cd.html#fig5.9.2","level":"5.9","list_caption":"Figure: Kubernetes改变了应用的基础架构","alt":"Kubernetes改变了应用的基础架构","nro":159,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsayashxz3j31c00w6aed.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"Kubernetes改变了应用的基础架构","attributes":{},"skip":false,"key":"5.9.2"},{"backlink":"practice/ci-cd.html#fig5.9.3","level":"5.9","list_caption":"Figure: Kubernetes中的CI/CD","alt":"Kubernetes中的CI/CD","nro":160,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsayfzk3ezj31bu0tkdky.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"Kubernetes中的CI/CD","attributes":{},"skip":false,"key":"5.9.3"},{"backlink":"practice/ci-cd.html#fig5.9.4","level":"5.9","list_caption":"Figure: 云原生工作负载","alt":"云原生工作负载","nro":161,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsayrk6vppj31bu0w0gsd.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"云原生工作负载","attributes":{},"skip":false,"key":"5.9.4"},{"backlink":"practice/ci-cd.html#fig5.9.5","level":"5.9","list_caption":"Figure: 云原生工作负载映射到Kuberentes原语","alt":"云原生工作负载映射到Kuberentes原语","nro":162,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsaytbabxgj31c00w2n4r.jpg","index":5,"caption_template":"图片 - _CAPTION_","label":"云原生工作负载映射到Kuberentes原语","attributes":{},"skip":false,"key":"5.9.5"},{"backlink":"practice/ci-cd.html#fig5.9.6","level":"5.9","list_caption":"Figure: spinnaker中的组件及角色交互关系","alt":"spinnaker中的组件及角色交互关系","nro":163,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsaz2wirz9j31bs0vygsb.jpg","index":6,"caption_template":"图片 - _CAPTION_","label":"spinnaker中的组件及角色交互关系","attributes":{},"skip":false,"key":"5.9.6"},{"backlink":"practice/ci-cd.html#fig5.9.7","level":"5.9","list_caption":"Figure: Spinnaker部署流水线","alt":"Spinnaker部署流水线","nro":164,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsaz3yo227j31c60mgdim.jpg","index":7,"caption_template":"图片 - _CAPTION_","label":"Spinnaker部署流水线","attributes":{},"skip":false,"key":"5.9.7"},{"backlink":"practice/ci-cd.html#fig5.9.8","level":"5.9","list_caption":"Figure: Spinnaker的预发布流水线","alt":"Spinnaker的预发布流水线","nro":165,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsaz50k2atj31bs0mitbn.jpg","index":8,"caption_template":"图片 - _CAPTION_","label":"Spinnaker的预发布流水线","attributes":{},"skip":false,"key":"5.9.8"},{"backlink":"practice/ci-cd.html#fig5.9.9","level":"5.9","list_caption":"Figure: Spinnaker的生产流水线","alt":"Spinnaker的生产流水线","nro":166,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsaz5n5qs9j31by0motbm.jpg","index":9,"caption_template":"图片 - _CAPTION_","label":"Spinnaker的生产流水线","attributes":{},"skip":false,"key":"5.9.9"},{"backlink":"practice/ci-cd.html#fig5.9.10","level":"5.9","list_caption":"Figure: 可观察性","alt":"可观察性","nro":167,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsazabn0b9j31by0w6791.jpg","index":10,"caption_template":"图片 - _CAPTION_","label":"可观察性","attributes":{},"skip":false,"key":"5.9.10"},{"backlink":"practice/ci-cd.html#fig5.9.11","level":"5.9","list_caption":"Figure: Prometheus生态系统中的组件","alt":"Prometheus生态系统中的组件","nro":168,"url":"https://ws1.sinaimg.cn/large/00704eQkgy1fsazcclee6j31c20w6n5y.jpg","index":11,"caption_template":"图片 - _CAPTION_","label":"Prometheus生态系统中的组件","attributes":{},"skip":false,"key":"5.9.11"},{"backlink":"practice/jenkins-ci-cd.html#fig5.9.1.1","level":"5.9.1","list_caption":"Figure: 基于Jenkins的持续集成与发布","alt":"基于Jenkins的持续集成与发布","nro":169,"url":"../images/kubernetes-jenkins-ci-cd.png","index":1,"caption_template":"图片 - _CAPTION_","label":"基于Jenkins的持续集成与发布","attributes":{},"skip":false,"key":"5.9.1.1"},{"backlink":"practice/drone-ci-cd.html#fig5.9.2.1","level":"5.9.2","list_caption":"Figure: OAuth注册","alt":"OAuth注册","nro":170,"url":"../images/github-oauth-register.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"OAuth注册","attributes":{},"skip":false,"key":"5.9.2.1"},{"backlink":"practice/drone-ci-cd.html#fig5.9.2.2","level":"5.9.2","list_caption":"Figure: OAuth key","alt":"OAuth key","nro":171,"url":"../images/github-oauth-drone-key.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"OAuth key","attributes":{},"skip":false,"key":"5.9.2.2"},{"backlink":"practice/drone-ci-cd.html#fig5.9.2.3","level":"5.9.2","list_caption":"Figure: Drone登陆界面","alt":"Drone登陆界面","nro":172,"url":"../images/drone-login-github.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"Drone登陆界面","attributes":{},"skip":false,"key":"5.9.2.3"},{"backlink":"practice/drone-ci-cd.html#fig5.9.2.4","level":"5.9.2","list_caption":"Figure: Github启用repo设置","alt":"Github启用repo设置","nro":173,"url":"../images/drone-github-active.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"Github启用repo设置","attributes":{},"skip":false,"key":"5.9.2.4"},{"backlink":"practice/drone-ci-cd.html#fig5.9.2.5","level":"5.9.2","list_caption":"Figure: Github单个repo设置","alt":"Github单个repo设置","nro":174,"url":"../images/drone-github-repo-setting.jpg","index":5,"caption_template":"图片 - _CAPTION_","label":"Github单个repo设置","attributes":{},"skip":false,"key":"5.9.2.5"},{"backlink":"practice/manually-upgrade.html#fig5.10.1.1","level":"5.10.1","list_caption":"Figure: Kubernetes零宕机时间升级建议","alt":"Kubernetes零宕机时间升级建议","nro":175,"url":"../images/zero-downtime-kubernetes-upgrade-tips.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Kubernetes零宕机时间升级建议","attributes":{},"skip":false,"key":"5.10.1.1"},{"backlink":"practice/manually-upgrade.html#fig5.10.1.2","level":"5.10.1","list_caption":"Figure: Kuberentes API对象的版本演进","alt":"Kuberentes API对象的版本演进","nro":176,"url":"../images/kubernetes-apversions-changes.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"Kuberentes API对象的版本演进","attributes":{},"skip":false,"key":"5.10.1.2"},{"backlink":"practice/dashboard-upgrade.html#fig5.10.2.1","level":"5.10.2","list_caption":"Figure: 登陆界面","alt":"登陆界面","nro":177,"url":"../images/kubernetes-dashboard-1.7.1-login.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"登陆界面","attributes":{},"skip":false,"key":"5.10.2.1"},{"backlink":"practice/dashboard-upgrade.html#fig5.10.2.2","level":"5.10.2","list_caption":"Figure: 首页","alt":"首页","nro":178,"url":"../images/kubernetes-dashboard-1.7.1-default-page.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"首页","attributes":{},"skip":false,"key":"5.10.2.2"},{"backlink":"practice/dashboard-upgrade.html#fig5.10.2.3","level":"5.10.2","list_caption":"Figure: 用户空间","alt":"用户空间","nro":179,"url":"../images/kubernetes-dashboard-1.7.1-brand.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"用户空间","attributes":{},"skip":false,"key":"5.10.2.3"},{"backlink":"practice/dashboard-upgrade.html#fig5.10.2.4","level":"5.10.2","list_caption":"Figure: kubeconfig文件","alt":"kubeconfig文件","nro":180,"url":"../images/brand-kubeconfig-yaml.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"kubeconfig文件","attributes":{},"skip":false,"key":"5.10.2.4"},{"backlink":"usecases/microservices.html#fig6.2.1","level":"6.2","list_caption":"Figure: 微服务关注的部分","alt":"微服务关注的部分","nro":181,"url":"../images/microservices-concerns.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"微服务关注的部分","attributes":{},"skip":false,"key":"6.2.1"},{"backlink":"usecases/service-discovery-in-microservices.html#fig6.2.1.1","level":"6.2.1","list_caption":"Figure: 微服务中的服务发现","alt":"微服务中的服务发现","nro":182,"url":"../images/service-discovery-in-microservices.png","index":1,"caption_template":"图片 - _CAPTION_","label":"微服务中的服务发现","attributes":{},"skip":false,"key":"6.2.1.1"},{"backlink":"usecases/microservices-for-java-developers.html#fig6.2.2.1","level":"6.2.2","list_caption":"Figure: Spring技术栈","alt":"Spring技术栈","nro":183,"url":"../images/spring-stack.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Spring技术栈","attributes":{},"skip":false,"key":"6.2.2.1"},{"backlink":"usecases/microservices-for-java-developers.html#fig6.2.2.2","level":"6.2.2","list_caption":"Figure: Spring Boot的知识点","alt":"Spring Boot的知识点","nro":184,"url":"../images/spring-boot-note-spots.png","index":2,"caption_template":"图片 - _CAPTION_","label":"Spring Boot的知识点","attributes":{},"skip":false,"key":"6.2.2.2"},{"backlink":"usecases/service-mesh.html#fig6.3.1","level":"6.3","list_caption":"Figure: 下一代异构微服务架构","alt":"下一代异构微服务架构","nro":185,"url":"../images/polyglot-microservices-serivce-mesh.png","index":1,"caption_template":"图片 - _CAPTION_","label":"下一代异构微服务架构","attributes":{},"skip":false,"key":"6.3.1"},{"backlink":"usecases/service-mesh.html#fig6.3.2","level":"6.3","list_caption":"Figure: Service Mesh 架构图","alt":"Service Mesh 架构图","nro":186,"url":"../images/serivce-mesh-control-plane.png","index":2,"caption_template":"图片 - _CAPTION_","label":"Service Mesh 架构图","attributes":{},"skip":false,"key":"6.3.2"},{"backlink":"usecases/service-mesh.html#fig6.3.3","level":"6.3","list_caption":"Figure: Istio vs linkerd","alt":"Istio vs linkerd","nro":187,"url":"../images/istio-vs-linkerd.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"Istio vs linkerd","attributes":{},"skip":false,"key":"6.3.3"},{"backlink":"usecases/istio.html#fig6.3.1.1","level":"6.3.1","list_caption":"Figure: Istio的mindmap","alt":"Istio的mindmap","nro":188,"url":"../images/istio-mindmap.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Istio的mindmap","attributes":{},"skip":false,"key":"6.3.1.1"},{"backlink":"usecases/istio.html#fig6.3.1.2","level":"6.3.1","list_caption":"Figure: Istio架构图","alt":"Istio架构图","nro":189,"url":"../images/istio-arch-v0.1.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"Istio架构图","attributes":{},"skip":false,"key":"6.3.1.2"},{"backlink":"usecases/istio.html#fig6.3.1.3","level":"6.3.1","list_caption":"Figure: Istio的控制平面和数据平面","alt":"Istio的控制平面和数据平面","nro":190,"url":"../images/istio-arch.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"Istio的控制平面和数据平面","attributes":{},"skip":false,"key":"6.3.1.3"},{"backlink":"usecases/istio-installation.html#fig6.3.1.1.1","level":"6.3.1.1","list_caption":"Figure: Istio 在 Kubernetes 中的部署架构图","alt":"Istio 在 Kubernetes 中的部署架构图","nro":191,"url":"../images/istio-deployment-architecture-diagram.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Istio 在 Kubernetes 中的部署架构图","attributes":{},"skip":false,"key":"6.3.1.1.1"},{"backlink":"usecases/istio-installation.html#fig6.3.1.1.2","level":"6.3.1.1","list_caption":"Figure: BookInfo Sample应用架构图","alt":"BookInfo Sample应用架构图","nro":192,"url":"../images/bookinfo-sample-arch.png","index":2,"caption_template":"图片 - _CAPTION_","label":"BookInfo Sample应用架构图","attributes":{},"skip":false,"key":"6.3.1.1.2"},{"backlink":"usecases/istio-installation.html#fig6.3.1.1.3","level":"6.3.1.1","list_caption":"Figure: BookInfo Sample页面","alt":"BookInfo Sample页面","nro":193,"url":"../images/bookinfo-sample.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"BookInfo Sample页面","attributes":{},"skip":false,"key":"6.3.1.1.3"},{"backlink":"usecases/istio-installation.html#fig6.3.1.1.4","level":"6.3.1.1","list_caption":"Figure: Istio Grafana界面","alt":"Istio Grafana界面","nro":194,"url":"../images/istio-grafana.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"Istio Grafana界面","attributes":{},"skip":false,"key":"6.3.1.1.4"},{"backlink":"usecases/istio-installation.html#fig6.3.1.1.5","level":"6.3.1.1","list_caption":"Figure: Prometheus页面","alt":"Prometheus页面","nro":195,"url":"../images/istio-prometheus.jpg","index":5,"caption_template":"图片 - _CAPTION_","label":"Prometheus页面","attributes":{},"skip":false,"key":"6.3.1.1.5"},{"backlink":"usecases/istio-installation.html#fig6.3.1.1.6","level":"6.3.1.1","list_caption":"Figure: Zipkin页面","alt":"Zipkin页面","nro":196,"url":"../images/istio-zipkin.jpg","index":6,"caption_template":"图片 - _CAPTION_","label":"Zipkin页面","attributes":{},"skip":false,"key":"6.3.1.1.6"},{"backlink":"usecases/istio-installation.html#fig6.3.1.1.7","level":"6.3.1.1","list_caption":"Figure: ServiceGraph页面","alt":"ServiceGraph页面","nro":197,"url":"../images/istio-servicegraph.jpg","index":7,"caption_template":"图片 - _CAPTION_","label":"ServiceGraph页面","attributes":{},"skip":false,"key":"6.3.1.1.7"},{"backlink":"usecases/install-and-expand-istio-mesh.html#fig6.3.1.3.1","level":"6.3.1.3","list_caption":"Figure: BookInfo","alt":"BookInfo","nro":198,"url":"../images/noistio.png","index":1,"caption_template":"图片 - _CAPTION_","label":"BookInfo","attributes":{},"skip":false,"key":"6.3.1.3.1"},{"backlink":"usecases/install-and-expand-istio-mesh.html#fig6.3.1.3.2","level":"6.3.1.3","list_caption":"Figure: BookInfo","alt":"BookInfo","nro":199,"url":"../images/noistio.png","index":2,"caption_template":"图片 - _CAPTION_","label":"BookInfo","attributes":{},"skip":false,"key":"6.3.1.3.2"},{"backlink":"usecases/integrating-vms.html#fig6.3.1.4.1","level":"6.3.1.4","list_caption":"Figure: Bookinfo应用的拓展Mesh","alt":"Bookinfo应用的拓展Mesh","nro":200,"url":"../images/istio-mesh-expansion.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Bookinfo应用的拓展Mesh","attributes":{},"skip":false,"key":"6.3.1.4.1"},{"backlink":"usecases/istio-tutorial.html#fig6.3.1.7.1","level":"6.3.1.7","list_caption":"Figure: Jaeger query UI","alt":"Jaeger query UI","nro":201,"url":"../images/jaeger-query-ui.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Jaeger query UI","attributes":{},"skip":false,"key":"6.3.1.7.1"},{"backlink":"usecases/istio-tutorial.html#fig6.3.1.7.2","level":"6.3.1.7","list_caption":"Figure: 分布式追踪","alt":"分布式追踪","nro":202,"url":"../images/istio-tutorial-zipkin-trace.png","index":2,"caption_template":"图片 - _CAPTION_","label":"分布式追踪","attributes":{},"skip":false,"key":"6.3.1.7.2"},{"backlink":"usecases/istio-tutorial.html#fig6.3.1.7.3","level":"6.3.1.7","list_caption":"Figure: 依赖关系","alt":"依赖关系","nro":203,"url":"../images/istio-tutorial-zipkin-dependency.png","index":3,"caption_template":"图片 - _CAPTION_","label":"依赖关系","attributes":{},"skip":false,"key":"6.3.1.7.3"},{"backlink":"usecases/istio-tutorial.html#fig6.3.1.7.4","level":"6.3.1.7","list_caption":"Figure: 服务关系图和QPS","alt":"服务关系图和QPS","nro":204,"url":"../images/istio-tutorial-serivcegraph-dotviz.png","index":4,"caption_template":"图片 - _CAPTION_","label":"服务关系图和QPS","attributes":{},"skip":false,"key":"6.3.1.7.4"},{"backlink":"usecases/istio-tutorial.html#fig6.3.1.7.5","level":"6.3.1.7","list_caption":"Figure: Grafana 监控","alt":"Grafana 监控","nro":205,"url":"../images/istio-tutorial-grafana.png","index":5,"caption_template":"图片 - _CAPTION_","label":"Grafana 监控","attributes":{},"skip":false,"key":"6.3.1.7.5"},{"backlink":"usecases/linkerd.html#fig6.3.2.1","level":"6.3.2","list_caption":"Figure: source https://linkerd.io","alt":"source https://linkerd.io","nro":206,"url":"../images/diagram-individual-instance.png","index":1,"caption_template":"图片 - _CAPTION_","label":"source https://linkerd.io","attributes":{},"skip":false,"key":"6.3.2.1"},{"backlink":"usecases/linkerd.html#fig6.3.2.2","level":"6.3.2","list_caption":"Figure: Linkerd 部署架构（图片来自https://buoyant.io/2016/10/14/a-service-mesh-for-kubernetes-part-ii-pods-are-great-until-theyre-not/）","alt":"Linkerd 部署架构（图片来自https://buoyant.io/2016/10/14/a-service-mesh-for-kubernetes-part-ii-pods-are-great-until-theyre-not/）","nro":207,"url":"https://buoyant.io/wp-content/uploads/2017/07/buoyant-k8s-daemonset-mesh.png","index":2,"caption_template":"图片 - _CAPTION_","label":"Linkerd 部署架构（图片来自https://buoyant.io/2016/10/14/a-service-mesh-for-kubernetes-part-ii-pods-are-great-until-theyre-not/）","attributes":{},"skip":false,"key":"6.3.2.2"},{"backlink":"usecases/linkerd.html#fig6.3.2.3","level":"6.3.2","list_caption":"Figure: 基于 dtab 的路由规则配置阶段发布","alt":"基于 dtab 的路由规则配置阶段发布","nro":208,"url":"https://buoyant.io/wp-content/uploads/2017/07/buoyant-4_override.png","index":3,"caption_template":"图片 - _CAPTION_","label":"基于 dtab 的路由规则配置阶段发布","attributes":{},"skip":false,"key":"6.3.2.3"},{"backlink":"usecases/linkerd.html#fig6.3.2.4","level":"6.3.2","list_caption":"Figure: Linkerd ingress controller","alt":"Linkerd ingress controller","nro":209,"url":"https://buoyant.io/wp-content/uploads/2017/07/buoyant-k8s-hello-world-ingress-controller-1.png","index":4,"caption_template":"图片 - _CAPTION_","label":"Linkerd ingress controller","attributes":{},"skip":false,"key":"6.3.2.4"},{"backlink":"usecases/linkerd-user-guide.html#fig6.3.2.1.1","level":"6.3.2.1","list_caption":"Figure: Jenkins pipeline","alt":"Jenkins pipeline","nro":210,"url":"../images/linkerd-jenkins-pipeline.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Jenkins pipeline","attributes":{},"skip":false,"key":"6.3.2.1.1"},{"backlink":"usecases/linkerd-user-guide.html#fig6.3.2.1.2","level":"6.3.2.1","list_caption":"Figure: Jenkins config","alt":"Jenkins config","nro":211,"url":"../images/linkerd-jenkins.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"Jenkins config","attributes":{},"skip":false,"key":"6.3.2.1.2"},{"backlink":"usecases/linkerd-user-guide.html#fig6.3.2.1.3","level":"6.3.2.1","list_caption":"Figure: namerd","alt":"namerd","nro":212,"url":"../images/namerd-internal.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"namerd","attributes":{},"skip":false,"key":"6.3.2.1.3"},{"backlink":"usecases/linkerd-user-guide.html#fig6.3.2.1.4","level":"6.3.2.1","list_caption":"Figure: linkerd监控","alt":"linkerd监控","nro":213,"url":"../images/linkerd-helloworld-outgoing.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"linkerd监控","attributes":{},"skip":false,"key":"6.3.2.1.4"},{"backlink":"usecases/linkerd-user-guide.html#fig6.3.2.1.5","level":"6.3.2.1","list_caption":"Figure: linkerd监控","alt":"linkerd监控","nro":214,"url":"../images/linkerd-helloworld-incoming.jpg","index":5,"caption_template":"图片 - _CAPTION_","label":"linkerd监控","attributes":{},"skip":false,"key":"6.3.2.1.5"},{"backlink":"usecases/linkerd-user-guide.html#fig6.3.2.1.6","level":"6.3.2.1","list_caption":"Figure: linkerd性能监控","alt":"linkerd性能监控","nro":215,"url":"../images/linkerd-grafana.png","index":6,"caption_template":"图片 - _CAPTION_","label":"linkerd性能监控","attributes":{},"skip":false,"key":"6.3.2.1.6"},{"backlink":"usecases/linkerd-user-guide.html#fig6.3.2.1.7","level":"6.3.2.1","list_caption":"Figure: Linkerd ingress controller","alt":"Linkerd ingress controller","nro":216,"url":"../images/linkerd-ingress-controller.jpg","index":7,"caption_template":"图片 - _CAPTION_","label":"Linkerd ingress controller","attributes":{},"skip":false,"key":"6.3.2.1.7"},{"backlink":"usecases/conduit-installation.html#fig6.3.3.2.1","level":"6.3.3.2","list_caption":"Figure: Conduit dashboard","alt":"Conduit dashboard","nro":217,"url":"../images/conduit-dashboard.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Conduit dashboard","attributes":{},"skip":false,"key":"6.3.3.2.1"},{"backlink":"usecases/envoy.html#fig6.3.4.1","level":"6.3.4","list_caption":"Figure: 负载均衡器的特性以及拓扑类型","alt":"负载均衡器的特性以及拓扑类型","nro":218,"url":"../images/load-balancing-and-proxing.png","index":1,"caption_template":"图片 - _CAPTION_","label":"负载均衡器的特性以及拓扑类型","attributes":{},"skip":false,"key":"6.3.4.1"},{"backlink":"usecases/envoy-terminology.html#fig6.3.4.1.1","level":"6.3.4.1","list_caption":"Figure: Envoy proxy 架构图","alt":"Envoy proxy 架构图","nro":219,"url":"../images/envoy-arch-v0.1.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Envoy proxy 架构图","attributes":{},"skip":false,"key":"6.3.4.1.1"},{"backlink":"usecases/envoy-front-proxy.html#fig6.3.4.2.1","level":"6.3.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":220,"url":"../images/envoyproxy-docker-compose.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Front proxy 部署结构图（转自https://www.envoyproxy.io/docs/envoy/latest/start/sandboxes/front_proxy）","attributes":{},"skip":false,"key":"6.3.4.2.1"},{"backlink":"usecases/envoy-mesh-in-kubernetes-tutorial.html#fig6.3.4.3.1","level":"6.3.4.3","list_caption":"Figure: Envoy Mesh架构图","alt":"Envoy Mesh架构图","nro":221,"url":"../images/envoy-mesh-in-kubernetes.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Envoy Mesh架构图","attributes":{},"skip":false,"key":"6.3.4.3.1"},{"backlink":"usecases/big-data.html#fig6.4.1","level":"6.4","list_caption":"Figure: Spark on yarn with kubernetes","alt":"Spark on yarn with kubernetes","nro":222,"url":"../images/spark-on-yarn-with-kubernetes.png","index":1,"caption_template":"图片 - _CAPTION_","label":"Spark on yarn with kubernetes","attributes":{},"skip":false,"key":"6.4.1"},{"backlink":"usecases/big-data.html#fig6.4.2","level":"6.4","list_caption":"Figure: 在kubernetes上使用多种调度方式","alt":"在kubernetes上使用多种调度方式","nro":223,"url":"../images/spark-on-kubernetes-with-different-schedulers.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"在kubernetes上使用多种调度方式","attributes":{},"skip":false,"key":"6.4.2"},{"backlink":"usecases/spark-standalone-on-kubernetes.html#fig6.4.1.1","level":"6.4.1","list_caption":"Figure: spark master ui","alt":"spark master ui","nro":224,"url":"../images/spark-ui.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"spark master ui","attributes":{},"skip":false,"key":"6.4.1.1"},{"backlink":"usecases/spark-standalone-on-kubernetes.html#fig6.4.1.2","level":"6.4.1","list_caption":"Figure: zeppelin ui","alt":"zeppelin ui","nro":225,"url":"../images/zeppelin-ui.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"zeppelin ui","attributes":{},"skip":false,"key":"6.4.1.2"},{"backlink":"usecases/serverless.html#fig6.5.1","level":"6.5","list_caption":"Figure: 从物理机到函数计算","alt":"从物理机到函数计算","nro":226,"url":"../images/from-bare-metal-to-functions.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"从物理机到函数计算","attributes":{},"skip":false,"key":"6.5.1"},{"backlink":"usecases/serverless.html#fig6.5.2","level":"6.5","list_caption":"Figure: FaaS Landscape","alt":"FaaS Landscape","nro":227,"url":"../images/redpoint-faas-landscape.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"FaaS Landscape","attributes":{},"skip":false,"key":"6.5.2"},{"backlink":"usecases/understanding-serverless.html#fig6.5.1.1","level":"6.5.1","list_caption":"Figure: 服务端软件的运行环境","alt":"服务端软件的运行环境","nro":228,"url":"../images/serverless-server-side-software.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"服务端软件的运行环境","attributes":{},"skip":false,"key":"6.5.1.1"},{"backlink":"usecases/understanding-serverless.html#fig6.5.1.2","level":"6.5.1","list_caption":"Figure: FaaS应用架构","alt":"FaaS应用架构","nro":229,"url":"../images/serverless-faas-platform.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"FaaS应用架构","attributes":{},"skip":false,"key":"6.5.1.2"},{"backlink":"usecases/understanding-serverless.html#fig6.5.1.3","level":"6.5.1","list_caption":"Figure: 传统应用程序架构","alt":"传统应用程序架构","nro":230,"url":"../images/non-serverless-game-arch.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"传统应用程序架构","attributes":{},"skip":false,"key":"6.5.1.3"},{"backlink":"usecases/understanding-serverless.html#fig6.5.1.4","level":"6.5.1","list_caption":"Figure: Serverless架构","alt":"Serverless架构","nro":231,"url":"../images/serverless-game-arch.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"Serverless架构","attributes":{},"skip":false,"key":"6.5.1.4"},{"backlink":"usecases/openfaas-quick-start.html#fig6.5.2.1.1","level":"6.5.2.1","list_caption":"Figure: OpenFaaS架构","alt":"OpenFaaS架构","nro":232,"url":"../images/openfaas-arch.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"OpenFaaS架构","attributes":{},"skip":false,"key":"6.5.2.1.1"},{"backlink":"usecases/openfaas-quick-start.html#fig6.5.2.1.2","level":"6.5.2.1","list_caption":"Figure: OpenFaaS Prometheus","alt":"OpenFaaS Prometheus","nro":233,"url":"../images/openfaas-prometheus.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"OpenFaaS Prometheus","attributes":{},"skip":false,"key":"6.5.2.1.2"},{"backlink":"usecases/openfaas-quick-start.html#fig6.5.2.1.3","level":"6.5.2.1","list_caption":"Figure: OpenFaas Grafana监控","alt":"OpenFaas Grafana监控","nro":234,"url":"../images/openfaas-grafana.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"OpenFaas Grafana监控","attributes":{},"skip":false,"key":"6.5.2.1.3"},{"backlink":"usecases/openfaas-quick-start.html#fig6.5.2.1.4","level":"6.5.2.1","list_caption":"Figure: OpenFaas Dashboard","alt":"OpenFaas Dashboard","nro":235,"url":"../images/openfaas-deploy-a-function.jpg","index":4,"caption_template":"图片 - _CAPTION_","label":"OpenFaas Dashboard","attributes":{},"skip":false,"key":"6.5.2.1.4"},{"backlink":"usecases/openfaas-quick-start.html#fig6.5.2.1.5","level":"6.5.2.1","list_caption":"Figure: NodeInfo执行结果","alt":"NodeInfo执行结果","nro":236,"url":"../images/openfaas-nodeinfo.jpg","index":5,"caption_template":"图片 - _CAPTION_","label":"NodeInfo执行结果","attributes":{},"skip":false,"key":"6.5.2.1.5"},{"backlink":"develop/sigs-and-working-group.html#fig7.2.1","level":"7.2","list_caption":"Figure: Kubernetes SIG","alt":"Kubernetes SIG","nro":237,"url":"../images/kubernetes-sigs.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"Kubernetes SIG","attributes":{},"skip":false,"key":"7.2.1"},{"backlink":"develop/testing.html#fig7.5.1","level":"7.5","list_caption":"Figure: test-infra架构图（图片来自官方GitHub）","alt":"test-infra架构图（图片来自官方GitHub）","nro":238,"url":"../images/kubernetes-test-architecture.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"test-infra架构图（图片来自官方GitHub）","attributes":{},"skip":false,"key":"7.5.1"},{"backlink":"develop/client-go-sample.html#fig7.6.1","level":"7.6","list_caption":"Figure: 使用kubernetes dashboard进行故障排查","alt":"使用kubernetes dashboard进行故障排查","nro":239,"url":"../images/kubernetes-client-go-sample-update.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"使用kubernetes dashboard进行故障排查","attributes":{},"skip":false,"key":"7.6.1"},{"backlink":"appendix/issues.html#fig8.6.1","level":"8.6","list_caption":"Figure: pvc-storage-limit","alt":"pvc-storage-limit","nro":240,"url":"../images/pvc-storage-limit.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"pvc-storage-limit","attributes":{},"skip":false,"key":"8.6.1"},{"backlink":"appendix/about-cka-candidate.html#fig8.10.1","level":"8.10","list_caption":"Figure: cka-question","alt":"cka-question","nro":241,"url":"../images/cka-question.png","index":1,"caption_template":"图片 - _CAPTION_","label":"cka-question","attributes":{},"skip":false,"key":"8.10.1"},{"backlink":"appendix/about-cka-candidate.html#fig8.10.2","level":"8.10","list_caption":"Figure: CKA mindmap","alt":"CKA mindmap","nro":242,"url":"../images/cka-mindmap.png","index":2,"caption_template":"图片 - _CAPTION_","label":"CKA mindmap","attributes":{},"skip":false,"key":"8.10.2"}]},"title":"Kubernetes Handbook - jimmysong.io","language":"zh-hans","links":{"sidebar":{"Jimmy Song":"https://jimmysong.io"}},"gitbook":"*","description":"Kubernetes中文指南/实践手册|kubernetes handbook|jimmysong.io|宋净超"},"file":{"path":"usecases/istio-tutorial.md","mtime":"2018-04-19T02:16:19.447Z","type":"markdown"},"gitbook":{"version":"3.2.3","time":"2018-06-29T09:09:31.094Z"},"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-sharing/buttons.js"></script>
|
||
|
||
|
||
|
||
<script src="../gitbook/gitbook-plugin-fontsettings/fontsettings.js"></script>
|
||
|
||
|
||
|
||
</body>
|
||
</html>
|
||
|