3115 lines
159 KiB
HTML
3115 lines
159 KiB
HTML
|
|
||
|
<!DOCTYPE HTML>
|
||
|
<html lang="zh-hans" >
|
||
|
<head>
|
||
|
<meta charset="UTF-8">
|
||
|
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
|
||
|
<title>云原生应用之路——从Kubernetes到Cloud Native · 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.2">
|
||
|
<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-highlight/website.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="../concepts/" />
|
||
|
|
||
|
|
||
|
<link rel="prev" href="kubernetes-and-cloud-native-app-overview.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="header">云原生</li>
|
||
|
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="2.1" data-path="kubernetes-and-cloud-native-app-overview.html">
|
||
|
|
||
|
<a href="kubernetes-and-cloud-native-app-overview.html">
|
||
|
|
||
|
|
||
|
<b>2.1.</b>
|
||
|
|
||
|
Kubernetes与云原生应用概览
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter active" data-level="2.2" data-path="from-kubernetes-to-cloud-native.html">
|
||
|
|
||
|
<a href="from-kubernetes-to-cloud-native.html">
|
||
|
|
||
|
|
||
|
<b>2.2.</b>
|
||
|
|
||
|
云原生应用之路——从Kubernetes到Cloud Native
|
||
|
|
||
|
</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>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.2" data-path="../concepts/concepts.html">
|
||
|
|
||
|
<a href="../concepts/concepts.html">
|
||
|
|
||
|
|
||
|
<b>3.2.</b>
|
||
|
|
||
|
设计理念
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3" data-path="../concepts/objects.html">
|
||
|
|
||
|
<a href="../concepts/objects.html">
|
||
|
|
||
|
|
||
|
<b>3.3.</b>
|
||
|
|
||
|
资源对象与基本概念解析
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="3.3.1" data-path="../concepts/pod-overview.html">
|
||
|
|
||
|
<a href="../concepts/pod-overview.html">
|
||
|
|
||
|
|
||
|
<b>3.3.1.</b>
|
||
|
|
||
|
Pod
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="3.3.1.1" data-path="../concepts/pod.html">
|
||
|
|
||
|
<a href="../concepts/pod.html">
|
||
|
|
||
|
|
||
|
<b>3.3.1.1.</b>
|
||
|
|
||
|
Pod解析
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.1.2" data-path="../concepts/init-containers.html">
|
||
|
|
||
|
<a href="../concepts/init-containers.html">
|
||
|
|
||
|
|
||
|
<b>3.3.1.2.</b>
|
||
|
|
||
|
Init容器
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.1.3" data-path="../concepts/pod-security-policy.html">
|
||
|
|
||
|
<a href="../concepts/pod-security-policy.html">
|
||
|
|
||
|
|
||
|
<b>3.3.1.3.</b>
|
||
|
|
||
|
Pod安全策略
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.1.4" data-path="../concepts/pod-lifecycle.html">
|
||
|
|
||
|
<a href="../concepts/pod-lifecycle.html">
|
||
|
|
||
|
|
||
|
<b>3.3.1.4.</b>
|
||
|
|
||
|
Pod的生命周期
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.1.5" data-path="../concepts/pod-hook.html">
|
||
|
|
||
|
<a href="../concepts/pod-hook.html">
|
||
|
|
||
|
|
||
|
<b>3.3.1.5.</b>
|
||
|
|
||
|
Pod hook
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.1.6" data-path="../concepts/pod-preset.html">
|
||
|
|
||
|
<a href="../concepts/pod-preset.html">
|
||
|
|
||
|
|
||
|
<b>3.3.1.6.</b>
|
||
|
|
||
|
Pod Preset
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.2" data-path="../concepts/node.html">
|
||
|
|
||
|
<a href="../concepts/node.html">
|
||
|
|
||
|
|
||
|
<b>3.3.2.</b>
|
||
|
|
||
|
Node
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.3" data-path="../concepts/namespace.html">
|
||
|
|
||
|
<a href="../concepts/namespace.html">
|
||
|
|
||
|
|
||
|
<b>3.3.3.</b>
|
||
|
|
||
|
Namespace
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.4" data-path="../concepts/service.html">
|
||
|
|
||
|
<a href="../concepts/service.html">
|
||
|
|
||
|
|
||
|
<b>3.3.4.</b>
|
||
|
|
||
|
Service
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.5" data-path="../concepts/volume.html">
|
||
|
|
||
|
<a href="../concepts/volume.html">
|
||
|
|
||
|
|
||
|
<b>3.3.5.</b>
|
||
|
|
||
|
Volume和Persistent Volume
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.6" data-path="../concepts/deployment.html">
|
||
|
|
||
|
<a href="../concepts/deployment.html">
|
||
|
|
||
|
|
||
|
<b>3.3.6.</b>
|
||
|
|
||
|
Deployment
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.7" data-path="../concepts/secret.html">
|
||
|
|
||
|
<a href="../concepts/secret.html">
|
||
|
|
||
|
|
||
|
<b>3.3.7.</b>
|
||
|
|
||
|
Secret
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.8" data-path="../concepts/statefulset.html">
|
||
|
|
||
|
<a href="../concepts/statefulset.html">
|
||
|
|
||
|
|
||
|
<b>3.3.8.</b>
|
||
|
|
||
|
StatefulSet
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.9" data-path="../concepts/daemonset.html">
|
||
|
|
||
|
<a href="../concepts/daemonset.html">
|
||
|
|
||
|
|
||
|
<b>3.3.9.</b>
|
||
|
|
||
|
DaemonSet
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.10" data-path="../concepts/serviceaccount.html">
|
||
|
|
||
|
<a href="../concepts/serviceaccount.html">
|
||
|
|
||
|
|
||
|
<b>3.3.10.</b>
|
||
|
|
||
|
ServiceAccount
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.11" data-path="../concepts/replicaset.html">
|
||
|
|
||
|
<a href="../concepts/replicaset.html">
|
||
|
|
||
|
|
||
|
<b>3.3.11.</b>
|
||
|
|
||
|
ReplicationController和ReplicaSet
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.12" data-path="../concepts/job.html">
|
||
|
|
||
|
<a href="../concepts/job.html">
|
||
|
|
||
|
|
||
|
<b>3.3.12.</b>
|
||
|
|
||
|
Job
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.13" data-path="../concepts/cronjob.html">
|
||
|
|
||
|
<a href="../concepts/cronjob.html">
|
||
|
|
||
|
|
||
|
<b>3.3.13.</b>
|
||
|
|
||
|
CronJob
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.14" data-path="../concepts/ingress.html">
|
||
|
|
||
|
<a href="../concepts/ingress.html">
|
||
|
|
||
|
|
||
|
<b>3.3.14.</b>
|
||
|
|
||
|
Ingress
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="3.3.14.1" data-path="../concepts/traefik-ingress-controller.html">
|
||
|
|
||
|
<a href="../concepts/traefik-ingress-controller.html">
|
||
|
|
||
|
|
||
|
<b>3.3.14.1.</b>
|
||
|
|
||
|
Traefik Ingress Controller
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.15" data-path="../concepts/configmap.html">
|
||
|
|
||
|
<a href="../concepts/configmap.html">
|
||
|
|
||
|
|
||
|
<b>3.3.15.</b>
|
||
|
|
||
|
ConfigMap
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="3.3.15.1" data-path="../concepts/configmap-hot-update.html">
|
||
|
|
||
|
<a href="../concepts/configmap-hot-update.html">
|
||
|
|
||
|
|
||
|
<b>3.3.15.1.</b>
|
||
|
|
||
|
ConfigMap的热更新
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.16" data-path="../concepts/horizontal-pod-autoscaling.html">
|
||
|
|
||
|
<a href="../concepts/horizontal-pod-autoscaling.html">
|
||
|
|
||
|
|
||
|
<b>3.3.16.</b>
|
||
|
|
||
|
Horizontal Pod Autoscaling
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="3.3.16.1" data-path="../concepts/custom-metrics-hpa.html">
|
||
|
|
||
|
<a href="../concepts/custom-metrics-hpa.html">
|
||
|
|
||
|
|
||
|
<b>3.3.16.1.</b>
|
||
|
|
||
|
自定义指标HPA
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.17" data-path="../concepts/label.html">
|
||
|
|
||
|
<a href="../concepts/label.html">
|
||
|
|
||
|
|
||
|
<b>3.3.17.</b>
|
||
|
|
||
|
Label
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.18" data-path="../concepts/garbage-collection.html">
|
||
|
|
||
|
<a href="../concepts/garbage-collection.html">
|
||
|
|
||
|
|
||
|
<b>3.3.18.</b>
|
||
|
|
||
|
垃圾收集
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.19" data-path="../concepts/network-policy.html">
|
||
|
|
||
|
<a href="../concepts/network-policy.html">
|
||
|
|
||
|
|
||
|
<b>3.3.19.</b>
|
||
|
|
||
|
NetworkPolicy
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.20" data-path="../concepts/annotation.html">
|
||
|
|
||
|
<a href="../concepts/annotation.html">
|
||
|
|
||
|
|
||
|
<b>3.3.20.</b>
|
||
|
|
||
|
Annotation
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.21" data-path="../concepts/aggregated-api-server.html">
|
||
|
|
||
|
<a href="../concepts/aggregated-api-server.html">
|
||
|
|
||
|
|
||
|
<b>3.3.21.</b>
|
||
|
|
||
|
Aggregated API Server
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.22" data-path="../concepts/custom-resource.html">
|
||
|
|
||
|
<a href="../concepts/custom-resource.html">
|
||
|
|
||
|
|
||
|
<b>3.3.22.</b>
|
||
|
|
||
|
使用自定义资源扩展API
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="3.3.23" data-path="../concepts/apiservice.html">
|
||
|
|
||
|
<a href="../concepts/apiservice.html">
|
||
|
|
||
|
|
||
|
<b>3.3.23.</b>
|
||
|
|
||
|
APIService
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
<li class="header">用户指南</li>
|
||
|
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="4.1" data-path="../guide/">
|
||
|
|
||
|
<a href="../guide/">
|
||
|
|
||
|
|
||
|
<b>4.1.</b>
|
||
|
|
||
|
用户指南
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="4.2" data-path="../guide/resource-configuration.html">
|
||
|
|
||
|
<a href="../guide/resource-configuration.html">
|
||
|
|
||
|
|
||
|
<b>4.2.</b>
|
||
|
|
||
|
资源对象配置
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="4.2.1" data-path="../guide/configure-liveness-readiness-probes.html">
|
||
|
|
||
|
<a href="../guide/configure-liveness-readiness-probes.html">
|
||
|
|
||
|
|
||
|
<b>4.2.1.</b>
|
||
|
|
||
|
配置Pod的liveness和readiness探针
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="4.2.2" data-path="../guide/configure-pod-service-account.html">
|
||
|
|
||
|
<a href="../guide/configure-pod-service-account.html">
|
||
|
|
||
|
|
||
|
<b>4.2.2.</b>
|
||
|
|
||
|
配置Pod的Service Account
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="4.2.3" data-path="../guide/secret-configuration.html">
|
||
|
|
||
|
<a href="../guide/secret-configuration.html">
|
||
|
|
||
|
|
||
|
<b>4.2.3.</b>
|
||
|
|
||
|
Secret配置
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="4.2.4" data-path="../guide/resource-quota-management.html">
|
||
|
|
||
|
<a href="../guide/resource-quota-management.html">
|
||
|
|
||
|
|
||
|
<b>4.2.4.</b>
|
||
|
|
||
|
管理namespace中的资源配额
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="4.3" data-path="../guide/command-usage.html">
|
||
|
|
||
|
<a href="../guide/command-usage.html">
|
||
|
|
||
|
|
||
|
<b>4.3.</b>
|
||
|
|
||
|
命令使用
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="4.3.1" data-path="../guide/docker-cli-to-kubectl.html">
|
||
|
|
||
|
<a href="../guide/docker-cli-to-kubectl.html">
|
||
|
|
||
|
|
||
|
<b>4.3.1.</b>
|
||
|
|
||
|
docker用户过度到kubectl命令行指南
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="4.3.2" data-path="../guide/using-kubectl.html">
|
||
|
|
||
|
<a href="../guide/using-kubectl.html">
|
||
|
|
||
|
|
||
|
<b>4.3.2.</b>
|
||
|
|
||
|
kubectl命令概览
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="4.3.3" data-path="../guide/kubectl-cheatsheet.html">
|
||
|
|
||
|
<a href="../guide/kubectl-cheatsheet.html">
|
||
|
|
||
|
|
||
|
<b>4.3.3.</b>
|
||
|
|
||
|
kubectl命令技巧大全
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="4.3.4" data-path="../guide/using-etcdctl-to-access-kubernetes-data.html">
|
||
|
|
||
|
<a href="../guide/using-etcdctl-to-access-kubernetes-data.html">
|
||
|
|
||
|
|
||
|
<b>4.3.4.</b>
|
||
|
|
||
|
使用etcdctl访问kuberentes数据
|
||
|
|
||
|
</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/rbac.html">
|
||
|
|
||
|
<a href="../guide/rbac.html">
|
||
|
|
||
|
|
||
|
<b>4.4.5.</b>
|
||
|
|
||
|
RBAC——基于角色的访问控制
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="4.4.6" data-path="../guide/ip-masq-agent.html">
|
||
|
|
||
|
<a href="../guide/ip-masq-agent.html">
|
||
|
|
||
|
|
||
|
<b>4.4.6.</b>
|
||
|
|
||
|
IP伪装代理
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="4.4.7" data-path="../guide/auth-with-kubeconfig-or-token.html">
|
||
|
|
||
|
<a href="../guide/auth-with-kubeconfig-or-token.html">
|
||
|
|
||
|
|
||
|
<b>4.4.7.</b>
|
||
|
|
||
|
使用kubeconfig或token进行用户身份认证
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="4.4.8" data-path="../guide/authentication.html">
|
||
|
|
||
|
<a href="../guide/authentication.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/carbin-mobile-dashboard-for-kubernetes.html">
|
||
|
|
||
|
<a href="../guide/carbin-mobile-dashboard-for-kubernetes.html">
|
||
|
|
||
|
|
||
|
<b>4.5.6.</b>
|
||
|
|
||
|
Carbin - Kuberentes手机客户端
|
||
|
|
||
|
</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>
|
||
|
|
||
|
|
||
|
</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/service-discovery-and-loadbalancing.html">
|
||
|
|
||
|
<a href="../practice/service-discovery-and-loadbalancing.html">
|
||
|
|
||
|
|
||
|
<b>5.3.</b>
|
||
|
|
||
|
服务发现与负载均衡
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="5.3.1" data-path="../practice/traefik-ingress-installation.html">
|
||
|
|
||
|
<a href="../practice/traefik-ingress-installation.html">
|
||
|
|
||
|
|
||
|
<b>5.3.1.</b>
|
||
|
|
||
|
安装Traefik ingress
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.3.2" data-path="../practice/distributed-load-test.html">
|
||
|
|
||
|
<a href="../practice/distributed-load-test.html">
|
||
|
|
||
|
|
||
|
<b>5.3.2.</b>
|
||
|
|
||
|
分布式负载测试
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.3.3" data-path="../practice/network-and-cluster-perfermance-test.html">
|
||
|
|
||
|
<a href="../practice/network-and-cluster-perfermance-test.html">
|
||
|
|
||
|
|
||
|
<b>5.3.3.</b>
|
||
|
|
||
|
网络和集群性能测试
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.3.4" data-path="../practice/edge-node-configuration.html">
|
||
|
|
||
|
<a href="../practice/edge-node-configuration.html">
|
||
|
|
||
|
|
||
|
<b>5.3.4.</b>
|
||
|
|
||
|
边缘节点配置
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.3.5" data-path="../practice/nginx-ingress-installation.html">
|
||
|
|
||
|
<a href="../practice/nginx-ingress-installation.html">
|
||
|
|
||
|
|
||
|
<b>5.3.5.</b>
|
||
|
|
||
|
安装Nginx ingress
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.4" data-path="../practice/operation.html">
|
||
|
|
||
|
<a href="../practice/operation.html">
|
||
|
|
||
|
|
||
|
<b>5.4.</b>
|
||
|
|
||
|
运维管理
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="5.4.1" data-path="../practice/service-rolling-update.html">
|
||
|
|
||
|
<a href="../practice/service-rolling-update.html">
|
||
|
|
||
|
|
||
|
<b>5.4.1.</b>
|
||
|
|
||
|
服务滚动升级
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.4.2" data-path="../practice/app-log-collection.html">
|
||
|
|
||
|
<a href="../practice/app-log-collection.html">
|
||
|
|
||
|
|
||
|
<b>5.4.2.</b>
|
||
|
|
||
|
应用日志收集
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.4.3" data-path="../practice/configuration-best-practice.html">
|
||
|
|
||
|
<a href="../practice/configuration-best-practice.html">
|
||
|
|
||
|
|
||
|
<b>5.4.3.</b>
|
||
|
|
||
|
配置最佳实践
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.4.4" data-path="../practice/monitor.html">
|
||
|
|
||
|
<a href="../practice/monitor.html">
|
||
|
|
||
|
|
||
|
<b>5.4.4.</b>
|
||
|
|
||
|
集群及应用监控
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.4.5" data-path="../practice/data-persistence-problem.html">
|
||
|
|
||
|
<a href="../practice/data-persistence-problem.html">
|
||
|
|
||
|
|
||
|
<b>5.4.5.</b>
|
||
|
|
||
|
数据持久化问题
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.4.6" data-path="../practice/manage-compute-resources-container.html">
|
||
|
|
||
|
<a href="../practice/manage-compute-resources-container.html">
|
||
|
|
||
|
|
||
|
<b>5.4.6.</b>
|
||
|
|
||
|
管理容器的计算资源
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.5" data-path="../practice/storage.html">
|
||
|
|
||
|
<a href="../practice/storage.html">
|
||
|
|
||
|
|
||
|
<b>5.5.</b>
|
||
|
|
||
|
存储管理
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="5.5.1" data-path="../practice/glusterfs.html">
|
||
|
|
||
|
<a href="../practice/glusterfs.html">
|
||
|
|
||
|
|
||
|
<b>5.5.1.</b>
|
||
|
|
||
|
GlusterFS
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="5.5.1.1" data-path="../practice/using-glusterfs-for-persistent-storage.html">
|
||
|
|
||
|
<a href="../practice/using-glusterfs-for-persistent-storage.html">
|
||
|
|
||
|
|
||
|
<b>5.5.1.1.</b>
|
||
|
|
||
|
使用GlusterFS做持久化存储
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.5.1.2" data-path="../practice/storage-for-containers-using-glusterfs-with-openshift.html">
|
||
|
|
||
|
<a href="../practice/storage-for-containers-using-glusterfs-with-openshift.html">
|
||
|
|
||
|
|
||
|
<b>5.5.1.2.</b>
|
||
|
|
||
|
在OpenShift中使用GlusterFS做持久化存储
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.5.2" data-path="../practice/cephfs.html">
|
||
|
|
||
|
<a href="../practice/cephfs.html">
|
||
|
|
||
|
|
||
|
<b>5.5.2.</b>
|
||
|
|
||
|
CephFS
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="5.5.2.1" data-path="../practice/using-ceph-for-persistent-storage.html">
|
||
|
|
||
|
<a href="../practice/using-ceph-for-persistent-storage.html">
|
||
|
|
||
|
|
||
|
<b>5.5.2.1.</b>
|
||
|
|
||
|
使用Ceph做持久化存储
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.6" data-path="../practice/monitoring.html">
|
||
|
|
||
|
<a href="../practice/monitoring.html">
|
||
|
|
||
|
|
||
|
<b>5.6.</b>
|
||
|
|
||
|
集群与应用监控
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="5.6.1" data-path="../practice/heapster.html">
|
||
|
|
||
|
<a href="../practice/heapster.html">
|
||
|
|
||
|
|
||
|
<b>5.6.1.</b>
|
||
|
|
||
|
Heapster
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="5.6.1.1" data-path="../practice/using-heapster-to-get-object-metrics.html">
|
||
|
|
||
|
<a href="../practice/using-heapster-to-get-object-metrics.html">
|
||
|
|
||
|
|
||
|
<b>5.6.1.1.</b>
|
||
|
|
||
|
使用Heapster获取集群和对象的metric数据
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.6.2" data-path="../practice/prometheus.html">
|
||
|
|
||
|
<a href="../practice/prometheus.html">
|
||
|
|
||
|
|
||
|
<b>5.6.2.</b>
|
||
|
|
||
|
Prometheus
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="5.6.2.1" data-path="../practice/using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
|
||
|
<a href="../practice/using-prometheus-to-monitor-kuberentes-cluster.html">
|
||
|
|
||
|
|
||
|
<b>5.6.2.1.</b>
|
||
|
|
||
|
使用Prometheus监控kubernetes集群
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.7" data-path="../practice/services-management-tool.html">
|
||
|
|
||
|
<a href="../practice/services-management-tool.html">
|
||
|
|
||
|
|
||
|
<b>5.7.</b>
|
||
|
|
||
|
服务编排管理
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="5.7.1" data-path="../practice/helm.html">
|
||
|
|
||
|
<a href="../practice/helm.html">
|
||
|
|
||
|
|
||
|
<b>5.7.1.</b>
|
||
|
|
||
|
使用Helm管理kubernetes应用
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.7.2" data-path="../practice/create-private-charts-repo.html">
|
||
|
|
||
|
<a href="../practice/create-private-charts-repo.html">
|
||
|
|
||
|
|
||
|
<b>5.7.2.</b>
|
||
|
|
||
|
构建私有Chart仓库
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.8" data-path="../practice/ci-cd.html">
|
||
|
|
||
|
<a href="../practice/ci-cd.html">
|
||
|
|
||
|
|
||
|
<b>5.8.</b>
|
||
|
|
||
|
持续集成与发布
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="5.8.1" data-path="../practice/jenkins-ci-cd.html">
|
||
|
|
||
|
<a href="../practice/jenkins-ci-cd.html">
|
||
|
|
||
|
|
||
|
<b>5.8.1.</b>
|
||
|
|
||
|
使用Jenkins进行持续集成与发布
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.8.2" data-path="../practice/drone-ci-cd.html">
|
||
|
|
||
|
<a href="../practice/drone-ci-cd.html">
|
||
|
|
||
|
|
||
|
<b>5.8.2.</b>
|
||
|
|
||
|
使用Drone进行持续集成与发布
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.9" data-path="../practice/update-and-upgrade.html">
|
||
|
|
||
|
<a href="../practice/update-and-upgrade.html">
|
||
|
|
||
|
|
||
|
<b>5.9.</b>
|
||
|
|
||
|
更新与升级
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="5.9.1" data-path="../practice/manually-upgrade.html">
|
||
|
|
||
|
<a href="../practice/manually-upgrade.html">
|
||
|
|
||
|
|
||
|
<b>5.9.1.</b>
|
||
|
|
||
|
手动升级kubernetes集群
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="5.9.2" data-path="../practice/dashboard-upgrade.html">
|
||
|
|
||
|
<a href="../practice/dashboard-upgrade.html">
|
||
|
|
||
|
|
||
|
<b>5.9.2.</b>
|
||
|
|
||
|
升级dashboard
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
<li class="header">领域应用</li>
|
||
|
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="6.1" data-path="../usecases/">
|
||
|
|
||
|
<a href="../usecases/">
|
||
|
|
||
|
|
||
|
<b>6.1.</b>
|
||
|
|
||
|
领域应用概览
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="6.2" data-path="../usecases/microservices.html">
|
||
|
|
||
|
<a href="../usecases/microservices.html">
|
||
|
|
||
|
|
||
|
<b>6.2.</b>
|
||
|
|
||
|
微服务架构
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="6.2.1" data-path="../usecases/service-discovery-in-microservices.html">
|
||
|
|
||
|
<a href="../usecases/service-discovery-in-microservices.html">
|
||
|
|
||
|
|
||
|
<b>6.2.1.</b>
|
||
|
|
||
|
微服务中的服务发现
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="6.3" data-path="../usecases/service-mesh.html">
|
||
|
|
||
|
<a href="../usecases/service-mesh.html">
|
||
|
|
||
|
|
||
|
<b>6.3.</b>
|
||
|
|
||
|
Service Mesh 服务网格
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="6.3.1" data-path="../usecases/istio.html">
|
||
|
|
||
|
<a href="../usecases/istio.html">
|
||
|
|
||
|
|
||
|
<b>6.3.1.</b>
|
||
|
|
||
|
Istio
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="6.3.1.1" data-path="../usecases/istio-installation.html">
|
||
|
|
||
|
<a href="../usecases/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="../usecases/configuring-request-routing.html">
|
||
|
|
||
|
<a href="../usecases/configuring-request-routing.html">
|
||
|
|
||
|
|
||
|
<b>6.3.1.2.</b>
|
||
|
|
||
|
配置请求的路由规则
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="6.3.1.3" data-path="../usecases/install-and-expand-istio-mesh.html">
|
||
|
|
||
|
<a href="../usecases/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="../usecases/integrating-vms.html">
|
||
|
|
||
|
<a href="../usecases/integrating-vms.html">
|
||
|
|
||
|
|
||
|
<b>6.3.1.4.</b>
|
||
|
|
||
|
集成虚拟机
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="6.3.2" data-path="../usecases/linkerd.html">
|
||
|
|
||
|
<a href="../usecases/linkerd.html">
|
||
|
|
||
|
|
||
|
<b>6.3.2.</b>
|
||
|
|
||
|
Linkerd
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="6.3.2.1" data-path="../usecases/linkerd-user-guide.html">
|
||
|
|
||
|
<a href="../usecases/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="../usecases/conduit.html">
|
||
|
|
||
|
<a href="../usecases/conduit.html">
|
||
|
|
||
|
|
||
|
<b>6.3.3.</b>
|
||
|
|
||
|
Conduit
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="6.3.3.1" data-path="../usecases/conduit-overview.html">
|
||
|
|
||
|
<a href="../usecases/conduit-overview.html">
|
||
|
|
||
|
|
||
|
<b>6.3.3.1.</b>
|
||
|
|
||
|
Condiut概览
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="6.3.3.2" data-path="../usecases/conduit-installation.html">
|
||
|
|
||
|
<a href="../usecases/conduit-installation.html">
|
||
|
|
||
|
|
||
|
<b>6.3.3.2.</b>
|
||
|
|
||
|
安装Conduit
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="6.4" data-path="../usecases/big-data.html">
|
||
|
|
||
|
<a href="../usecases/big-data.html">
|
||
|
|
||
|
|
||
|
<b>6.4.</b>
|
||
|
|
||
|
大数据
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="6.4.1" data-path="../usecases/spark-standalone-on-kubernetes.html">
|
||
|
|
||
|
<a href="../usecases/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="../usecases/running-spark-with-kubernetes-native-scheduler.html">
|
||
|
|
||
|
<a href="../usecases/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="../usecases/serverless.html">
|
||
|
|
||
|
<a href="../usecases/serverless.html">
|
||
|
|
||
|
|
||
|
<b>6.5.</b>
|
||
|
|
||
|
Serverless架构
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="6.5.1" data-path="../usecases/understanding-serverless.html">
|
||
|
|
||
|
<a href="../usecases/understanding-serverless.html">
|
||
|
|
||
|
|
||
|
<b>6.5.1.</b>
|
||
|
|
||
|
理解Serverless
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="6.5.2" data-path="../usecases/faas.html">
|
||
|
|
||
|
<a href="../usecases/faas.html">
|
||
|
|
||
|
|
||
|
<b>6.5.2.</b>
|
||
|
|
||
|
FaaS-函数即服务
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
<ul class="articles">
|
||
|
|
||
|
|
||
|
<li class="chapter " data-level="6.5.2.1" data-path="../usecases/openfaas.html">
|
||
|
|
||
|
<a href="../usecases/openfaas.html">
|
||
|
|
||
|
|
||
|
<b>6.5.2.1.</b>
|
||
|
|
||
|
OpenFaaS
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="6.6" data-path="../usecases/edge-computing.html">
|
||
|
|
||
|
<a href="../usecases/edge-computing.html">
|
||
|
|
||
|
|
||
|
<b>6.6.</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/testing.html">
|
||
|
|
||
|
<a href="../develop/testing.html">
|
||
|
|
||
|
|
||
|
<b>7.4.</b>
|
||
|
|
||
|
单元测试和集成测试
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="7.5" data-path="../develop/client-go-sample.html">
|
||
|
|
||
|
<a href="../develop/client-go-sample.html">
|
||
|
|
||
|
|
||
|
<b>7.5.</b>
|
||
|
|
||
|
client-go示例
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="7.6" data-path="../develop/contribute.html">
|
||
|
|
||
|
<a href="../develop/contribute.html">
|
||
|
|
||
|
|
||
|
<b>7.6.</b>
|
||
|
|
||
|
社区贡献
|
||
|
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</li>
|
||
|
|
||
|
<li class="chapter " data-level="7.7" data-path="../develop/minikube.html">
|
||
|
|
||
|
<a href="../develop/minikube.html">
|
||
|
|
||
|
|
||
|
<b>7.7.</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>
|
||
|
|
||
|
|
||
|
</ul>
|
||
|
|
||
|
</li>
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
<li class="divider"></li>
|
||
|
|
||
|
<li>
|
||
|
<a href="https://www.gitbook.com" target="blank" class="gitbook-link">
|
||
|
本书使用 GitBook 发布
|
||
|
</a>
|
||
|
</li>
|
||
|
</ul>
|
||
|
|
||
|
|
||
|
</nav>
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
<div class="book-body">
|
||
|
|
||
|
<div class="body-inner">
|
||
|
|
||
|
|
||
|
|
||
|
<div class="book-header" role="navigation">
|
||
|
|
||
|
|
||
|
<!-- Title -->
|
||
|
<h1>
|
||
|
<i class="fa fa-circle-o-notch fa-spin"></i>
|
||
|
<a href=".." >云原生应用之路——从Kubernetes到Cloud Native</a>
|
||
|
</h1>
|
||
|
</div>
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
<div class="page-wrapper" tabindex="-1" role="main">
|
||
|
<div class="page-inner">
|
||
|
|
||
|
<div class="search-plus" id="book-search-results">
|
||
|
<div class="search-noresults">
|
||
|
|
||
|
<section class="normal markdown-section">
|
||
|
|
||
|
<h1 id="云原生应用之路——从kubernetes到cloud-native">云原生应用之路——从Kubernetes到Cloud Native</h1>
|
||
|
<p><strong>从Kubernetes到Cloud Native——云原生应用之路</strong>,这是我最近在 <a href="http://bj2017.archsummit.com/presentation/306" target="_blank">ArchSummit2017北京站</a> 和 <a href="https://www.kubernetes.org.cn/3211.html" target="_blank">数人云&TalkingData合办的Service Mesh is comming meetup</a> 中分享的话题。</p>
|
||
|
<p>本文简要介绍了容器技术发展的路径,为何Kubernetes的出现是容器技术发展到这一步的必然选择,而为何Kuberentes又将成为云原生应用的基石。</p>
|
||
|
<p>我的分享按照这样的主线展开:容器->Kubernetes->微服务->Cloud Native(云原生)->Service Mesh(服务网格)->使用场景->Open Source(开源)。</p>
|
||
|
<h2 id="容器">容器</h2>
|
||
|
<blockquote>
|
||
|
<p>容器——Cloud Native的基石</p>
|
||
|
</blockquote>
|
||
|
<figure id="fig2.2.1"><img src="https://res.cloudinary.com/jimmysong/image/upload/images/cloud-native-container-lab.jpg" alt="Cloud Native容器实验室"><figcaption>图片 - Cloud Native容器实验室</figcaption></figure>
|
||
|
<p>容器最初是通过开发者工具而流行,可以使用它来做隔离的开发测试环境和持续集成环境,这些都是因为容器轻量级,易于配置和使用带来的优势,docker和docker-compose这样的工具极大的方便的了应用开发环境的搭建,开发者就像是化学家一样在其中小心翼翼的进行各种调试和开发。</p>
|
||
|
<p>随着容器的在开发者中的普及,已经大家对CI流程的熟悉,容器周边的各种工具蓬勃发展,俨然形成了一个小生态,在2016年达到顶峰,下面这张是我画的容器生态图:</p>
|
||
|
<figure id="fig2.2.2"><img src="../images/container-ecosystem.png" alt="容器生态图 Container ecosystem"><figcaption>图片 - 容器生态图 Container ecosystem</figcaption></figure>
|
||
|
<p>该生态涵盖了容器应用中从镜像仓库、服务编排、安全管理、持续集成与发布、存储和网络管理等各个方面,随着在单主机中运行容器的成熟,集群管理和容器编排成为容器技术亟待解决的问题。譬如化学家在实验室中研究出来的新产品,如何推向市场,进行大规模生产,成了新的议题。</p>
|
||
|
<h2 id="为什么使用kubernetes">为什么使用Kubernetes</h2>
|
||
|
<blockquote>
|
||
|
<p>Kubernetes——让容器应用进入大规模工业生产。</p>
|
||
|
</blockquote>
|
||
|
<figure id="fig2.2.3"><img src="https://res.cloudinary.com/jimmysong/image/upload/images/cloud-native-oil-well.jpg" alt="Cloud Native油井"><figcaption>图片 - Cloud Native油井</figcaption></figure>
|
||
|
<p><strong>Kubernetes是容器编排系统的事实标准</strong></p>
|
||
|
<p>在单机上运行容器,无法发挥它的最大效能,只有形成集群,才能最大程度发挥容器的良好隔离、资源分配与编排管理的优势,而对于容器的编排管理,Swarm、Mesos和Kubernetes的大战已经基本宣告技术,kubernetes成为了无可争议的赢家。</p>
|
||
|
<p>下面这张图是Kubernetes的架构图(图片来自网络),其中显示了组件之间交互的接口CNI、CRI、OCI等,这些将Kubernetes与某款具体产品解耦,给用户最大的定制程度,使得Kubernetes有机会成为跨云的真正的云原生应用的操作系统。</p>
|
||
|
<figure id="fig2.2.4"><img src="../images/kubernetes-high-level-component-archtecture.jpg" alt="Kuberentes架构"><figcaption>图片 - Kuberentes架构</figcaption></figure>
|
||
|
<p>随着Kubernetes的日趋成熟,“Kubernetes is becoming boring”,基于该“操作系统”之上构建的适用于不同场景的应用将成为新的发展方向,就像我们将石油开采出来后,提炼出汽油、柴油、沥青等等,所有的材料都将找到自己的用途,Kubernetes也是,毕竟我们谁也不是为了部署和管理容器而用Kubernetes,承载其上的应用才是价值之所在。</p>
|
||
|
<p><strong>云原生的核心目标</strong></p>
|
||
|
<figure id="fig2.2.5"><img src="../images/cloud-native-core-target.jpg" alt="Cloud Native Core target"><figcaption>图片 - Cloud Native Core target</figcaption></figure>
|
||
|
<p>云已经可以为我们提供稳定可以唾手可得的基础设施,但是业务上云成了一个难题,Kubernetes的出现与其说是从最初的容器编排解决方案,倒不如说是为了解决应用上云(即云原生应用)这个难题。</p>
|
||
|
<p>包括微服务和FaaS/Serverless架构,都可以作为云原生应用的架构。</p>
|
||
|
<figure id="fig2.2.6"><img src="../images/redpoint-faas-landscape.jpg" alt="FaaS Landscape"><figcaption>图片 - FaaS Landscape</figcaption></figure>
|
||
|
<p>但就2017年为止,kubernetes的主要使用场景也主要作为应用开发测试环境、CI/CD和运行Web应用这几个领域,如下图<a href="http://thenewstack.io" target="_blank">TheNewStack</a>的Kubernetes生态状况调查报告所示。</p>
|
||
|
<figure id="fig2.2.7"><img src="https://res.cloudinary.com/jimmysong/image/upload/images/workloads-running-on-kubernetes-2017-thenewstack.jpg" alt="Workloads running on Kubernetes"><figcaption>图片 - Workloads running on Kubernetes</figcaption></figure>
|
||
|
<p>另外基于Kubernetes的构建PaaS平台和Serverless也处于爆发的准备的阶段,如下图中Gartner的报告中所示:</p>
|
||
|
<figure id="fig2.2.8"><img src="https://res.cloudinary.com/jimmysong/image/upload/images/gartner-hype-cycle-for-emerging-technologies-2017.jpg" alt="Gartner技术爆发趋势图2017"><figcaption>图片 - Gartner技术爆发趋势图2017</figcaption></figure>
|
||
|
<p>当前各大公有云如Google GKE、微软Azure ACS、亚马逊EKS(2018年上线)、VmWare、Pivotal、腾讯云、阿里云等都提供了Kuberentes服务。</p>
|
||
|
<h2 id="微服务">微服务</h2>
|
||
|
<blockquote>
|
||
|
<p>微服务——Cloud Native的应用架构。</p>
|
||
|
</blockquote>
|
||
|
<p>下图是<a href="https://developers.redhat.com/blog/author/bibryam/" target="_blank">Bilgin Ibryam</a>给出的微服务中应该关心的主题,图片来自<a href="https://developers.redhat.com/blog/2016/12/09/spring-cloud-for-microservices-compared-to-kubernetes/" target="_blank">RedHat Developers</a>。</p>
|
||
|
<figure id="fig2.2.9"><img src="../images/microservices-concerns.jpg" alt="Microservices concerns"><figcaption>图片 - Microservices concerns</figcaption></figure>
|
||
|
<p>微服务带给我们很多开发和部署上的灵活性和技术多样性,但是也增加了服务调用的开销、分布式系统管理、调试与服务治理方面的难题。</p>
|
||
|
<p>当前最成熟最完整的微服务框架可以说非<a href="https://spring.io/" target="_blank">Spring</a>莫属,而Spring又仅限于Java语言开发,其架构本身又跟Kubernetes存在很多重合的部分,如何探索将Kubernetes作为微服务架构平台就成为一个热点话题。</p>
|
||
|
<p>就拿微服务中最基础的<strong>服务注册发现</strong>功能来说,其方式分为<strong>客户端服务发现</strong>和<strong>服务端服务发现</strong>两种,Java应用中常用的方式是使用Eureka和Ribbon做服务注册发现和负载均衡,这属于客户端服务发现,而在Kubernetes中则可以使用DNS、Service和Ingress来实现,不需要修改应用代码,直接从网络层面来实现。</p>
|
||
|
<figure id="fig2.2.10"><img src="../images/service-discovery-in-microservices.png" alt="两种服务发现方式"><figcaption>图片 - 两种服务发现方式</figcaption></figure>
|
||
|
<h2 id="cloud-native">Cloud Native</h2>
|
||
|
<blockquote>
|
||
|
<p>DevOps——通向云原生的云梯</p>
|
||
|
</blockquote>
|
||
|
<figure id="fig2.2.11"><img src="https://res.cloudinary.com/jimmysong/image/upload/images/cloud-natvie-pipeline.jpg" alt="Cloud Native Pipeline"><figcaption>图片 - Cloud Native Pipeline</figcaption></figure>
|
||
|
<p>CNCF(云原生计算基金会)给出了云原生应用的三大特征:</p>
|
||
|
<ul>
|
||
|
<li><strong>容器化包装</strong>:软件应用的进程应该包装在容器中独立运行。</li>
|
||
|
<li><strong>动态管理</strong>:通过集中式的编排调度系统来动态的管理和调度。</li>
|
||
|
<li><strong>微服务化</strong>:明确服务间的依赖,互相解耦。</li>
|
||
|
</ul>
|
||
|
<p>下图是我整理的关于云原生所需要的能力和特征。</p>
|
||
|
<figure id="fig2.2.12"><img src="https://jimmysong.io/kubernetes-handbook/images/cloud-native-architecutre-mindnode.jpg" alt="Cloud Native Features"><figcaption>图片 - Cloud Native Features</figcaption></figure>
|
||
|
<p><a href="https://cncf.io" target="_blank">CNCF</a>所托管的应用(目前已达12个),即朝着这个目标发展,其公布的<a href="https://github.com/cncf/landscape" target="_blank">Cloud Native Landscape</a>,给出了云原生生态的参考体系。</p>
|
||
|
<figure id="fig2.2.13"><img src="https://raw.githubusercontent.com/cncf/landscape/master/landscape/CloudNativeLandscape_v1.0.jpg" alt="Cloud Native Landscape v1.0"><figcaption>图片 - Cloud Native Landscape v1.0</figcaption></figure>
|
||
|
<p><strong>使用Kubernetes构建云原生应用</strong></p>
|
||
|
<p>我们都是知道Heroku推出了适用于PaaS的<a href="https://12factor.net/" target="_blank">12 factor app</a>的规范,包括如下要素:</p>
|
||
|
<ol>
|
||
|
<li>基准代码</li>
|
||
|
<li>依赖管理</li>
|
||
|
<li>配置</li>
|
||
|
<li>后端服务</li>
|
||
|
<li>构建,发布,运行</li>
|
||
|
<li>无状态进程</li>
|
||
|
<li>端口绑定</li>
|
||
|
<li>并发</li>
|
||
|
<li>易处理</li>
|
||
|
<li>开发环境与线上环境等价</li>
|
||
|
<li>日志作为事件流</li>
|
||
|
<li>管理进程</li>
|
||
|
</ol>
|
||
|
<p>另外还有补充的三点:</p>
|
||
|
<ul>
|
||
|
<li>API声明管理</li>
|
||
|
<li>认证和授权</li>
|
||
|
<li>监控与告警</li>
|
||
|
</ul>
|
||
|
<p>如果落实的具体的工具,请看下图,使用Kubernetes构建云原生架构:</p>
|
||
|
<figure id="fig2.2.14"><img src="../images/building-cloud-native-architecture-with-kubernetes.png" alt="Building a Cloud Native Architecture with Kubernetes followed 12 factor app"><figcaption>图片 - Building a Cloud Native Architecture with Kubernetes followed 12 factor app</figcaption></figure>
|
||
|
<p>结合这12因素对开发或者改造后的应用适合部署到Kubernetes之上,基本流程如下图所示:</p>
|
||
|
<figure id="fig2.2.15"><img src="../images/creating-kubernetes-native-app.jpg" alt="Creating Kubernetes native app"><figcaption>图片 - Creating Kubernetes native app</figcaption></figure>
|
||
|
<p><strong>迁移到云架构</strong></p>
|
||
|
<p>迁移到云端架构,相对单体架构来说会带来很多挑战。比如自动的持续集成与发布、服务监控的变革、服务暴露、权限的管控等。这些具体细节请参考<strong>Kubernetes-handbook</strong>中的说明:<a href="https://jimmysong.io/kubernetes-handbook" target="_blank">https://jimmysong.io/kubernetes-handbook</a>,在此就不细节展开,另外推荐一本我翻译的由Pivotal出品的电子书——<a href="https://content.pivotal.io/ebooks/migrating-to-cloud-native-application-architectures" target="_blank">Migrating to Cloud Native Application Architectures</a>,地址:<a href="https://jimmysong.io/migrating-to-cloud-native-application-architectures/" target="_blank">https://jimmysong.io/migrating-to-cloud-native-application-architectures/</a>。</p>
|
||
|
<h2 id="service-mesh">Service Mesh</h2>
|
||
|
<blockquote>
|
||
|
<p>Services for show, meshes for a pro.</p>
|
||
|
</blockquote>
|
||
|
<figure id="fig2.2.16"><img src="https://res.cloudinary.com/jimmysong/image/upload/images/service-meshes-pro.jpg" alt="Service Mesh中国社区slogan"><figcaption>图片 - Service Mesh中国社区slogan</figcaption></figure>
|
||
|
<p>Kubernetes中的应用将作为微服务运行,但是Kuberentes本身并没有给出微服务治理的解决方案,比如服务的限流、熔断、良好的灰度发布支持等。</p>
|
||
|
<p><strong>Service mesh可以用来做什么</strong></p>
|
||
|
<ul>
|
||
|
<li>Traffic Management:API网关</li>
|
||
|
<li>Observability:服务调用和性能分析</li>
|
||
|
<li>Policy Enforcment:控制服务访问策略</li>
|
||
|
<li>Service Identity and Security:安全保护</li>
|
||
|
</ul>
|
||
|
<p><strong>Service mesh的特点</strong></p>
|
||
|
<ul>
|
||
|
<li>专用的基础设施层</li>
|
||
|
<li>轻量级高性能网络代理</li>
|
||
|
<li>提供安全的、快速的、可靠地服务间通讯</li>
|
||
|
<li>扩展kubernetes的应用负载均衡机制,实现灰度发布</li>
|
||
|
<li>完全解耦于应用,应用可以无感知,加速应用的微服务和云原生转型</li>
|
||
|
</ul>
|
||
|
<p>使用Service Mesh将可以有效的治理Kuberentes中运行的服务,当前开源的Service Mesh有:</p>
|
||
|
<ul>
|
||
|
<li>Linkderd:<a href="https://linkerd.io" target="_blank">https://linkerd.io</a>,由最早提出Service Mesh的公司<a href="https://buoyant.io" target="_blank">Buoyant</a>开源,创始人来自Twitter</li>
|
||
|
<li>Envoy:<a href="https://www.envoyproxy.io/" target="_blank">https://www.envoyproxy.io/</a>,Lyft开源的,可以在Istio中使用Sidecar模式运行</li>
|
||
|
<li>Istio:<a href="https://istio.io" target="_blank">https://istio.io</a>,由Google、IBM、Lyft联合开发并开源</li>
|
||
|
<li>Conduit:<a href="https://conduit.io" target="_blank">https://conduit.io</a>,同样由Buoyant开源的轻量级的基于Kubernetes的Service Mesh</li>
|
||
|
</ul>
|
||
|
<p>此外还有很多其它的Service Mesh鱼贯而出,请参考<a href="https://jimmysong.io/awesome-cloud-native" target="_blank">awesome-cloud-native</a>。</p>
|
||
|
<p><strong>Istio VS Linkerd</strong></p>
|
||
|
<p>Linkerd和Istio是最早开源的Service Mesh,它们都支持Kubernetes,下面是它们之间的一些特性对比。</p>
|
||
|
<table>
|
||
|
<thead>
|
||
|
<tr>
|
||
|
<th><strong>Feature</strong></th>
|
||
|
<th><strong>Istio</strong></th>
|
||
|
<th><strong>Linkerd</strong></th>
|
||
|
</tr>
|
||
|
</thead>
|
||
|
<tbody>
|
||
|
<tr>
|
||
|
<td>部署架构</td>
|
||
|
<td>Envoy/Sidecar</td>
|
||
|
<td>DaemonSets</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>易用性</td>
|
||
|
<td>复杂</td>
|
||
|
<td>简单</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>支持平台</td>
|
||
|
<td>kuberentes</td>
|
||
|
<td>kubernetes/mesos/Istio/local</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>当前版本</td>
|
||
|
<td>0.3.0</td>
|
||
|
<td>1.3.3</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>是否已有生产部署</td>
|
||
|
<td>否</td>
|
||
|
<td>是</td>
|
||
|
</tr>
|
||
|
</tbody>
|
||
|
</table>
|
||
|
<p>关于两者的架构可以参考各自的官方文档,我只从其在kubernetes上的部署结构来说明其区别。</p>
|
||
|
<figure id="fig2.2.17"><img src="../images/istio-vs-linkerd.jpg" alt="istio vs linkerd"><figcaption>图片 - istio vs linkerd</figcaption></figure>
|
||
|
<p>Istio的组件复杂,可以分别部署的kubernetes集群中,但是作为核心路由组件<strong>Envoy</strong>是以<strong>Sidecar</strong>形式与应用运行在同一个Pod中的,所有进入该Pod中的流量都需要先经过Envoy。</p>
|
||
|
<p>Linker的部署十分简单,本身就是一个镜像,使用Kubernetes的<a href="https://jimmysong.io/kubernetes-handbook/concepts/daemonset.html" target="_blank">DaemonSet</a>方式在每个node节点上运行。</p>
|
||
|
<p>更多信息请参考<a href="https://jimmysong.io/kubernetes-handbook" target="_blank">kubernetes-handbook</a>。</p>
|
||
|
<h2 id="使用场景">使用场景</h2>
|
||
|
<blockquote>
|
||
|
<p>Cloud Native的大规模工业生产</p>
|
||
|
</blockquote>
|
||
|
<figure id="fig2.2.18"><img src="https://res.cloudinary.com/jimmysong/image/upload/images/cloud-native-factory.jpg" alt="Cloud Native factory"><figcaption>图片 - Cloud Native factory</figcaption></figure>
|
||
|
<p><strong>GitOps</strong></p>
|
||
|
<p>给开发者带来最大配置和上线的灵活性,践行DevOps流程,改善研发效率,下图这样的情况将更少发生。</p>
|
||
|
<figure id="fig2.2.19"><img src="https://res.cloudinary.com/jimmysong/image/upload/images/deployment-pipeline-comic.jpg" alt="Deployment pipeline"><figcaption>图片 - Deployment pipeline</figcaption></figure>
|
||
|
<p>我们知道Kubernetes中的所有应用的部署都是基于YAML文件的,这实际上就是一种<strong>Infrastructure as code</strong>,完全可以通过Git来管控基础设施和部署环境的变更。</p>
|
||
|
<p><strong>Big Data</strong></p>
|
||
|
<p>Spark现在已经非官方支持了基于Kuberentes的原生调度,其具有以下特点:</p>
|
||
|
<ul>
|
||
|
<li>Kubernetes原生调度:与yarn、mesos同级</li>
|
||
|
<li>资源隔离,粒度更细:以namespace来划分用户</li>
|
||
|
<li>监控的变革:单次任务资源计量</li>
|
||
|
<li>日志的变革:pod的日志收集</li>
|
||
|
</ul>
|
||
|
<table>
|
||
|
<thead>
|
||
|
<tr>
|
||
|
<th><strong>Feature</strong></th>
|
||
|
<th><strong>Yarn</strong></th>
|
||
|
<th><strong>Kubernetes</strong></th>
|
||
|
</tr>
|
||
|
</thead>
|
||
|
<tbody>
|
||
|
<tr>
|
||
|
<td>queue</td>
|
||
|
<td>queue</td>
|
||
|
<td>namespace</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>instance</td>
|
||
|
<td>ExcutorContainer</td>
|
||
|
<td>Executor Pod</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>network</td>
|
||
|
<td>host</td>
|
||
|
<td>plugin</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>heterogeneous</td>
|
||
|
<td>no</td>
|
||
|
<td>yes</td>
|
||
|
</tr>
|
||
|
<tr>
|
||
|
<td>security</td>
|
||
|
<td>RBAC</td>
|
||
|
<td>ACL</td>
|
||
|
</tr>
|
||
|
</tbody>
|
||
|
</table>
|
||
|
<p>下图是在Kubernetes上运行三种调度方式的spark的单个节点的应用部分对比:</p>
|
||
|
<figure id="fig2.2.20"><img src="../images/spark-on-kubernetes-with-different-schedulers.jpg" alt="Spark on Kubernetes with different schedulers"><figcaption>图片 - Spark on Kubernetes with different schedulers</figcaption></figure>
|
||
|
<p>从上图中可以看到在Kubernetes上使用YARN调度、standalone调度和kubernetes原生调度的方式,每个node节点上的Pod内的spark Executor分布,毫无疑问,使用kubernetes原生调度的spark任务才是最节省资源的。</p>
|
||
|
<p>提交任务的语句看起来会像是这样的:</p>
|
||
|
<pre><code class="lang-bash">./spark-submit \
|
||
|
--deploy-mode cluster \
|
||
|
--class com.talkingdata.alluxio.hadooptest \
|
||
|
--master k8s://https://172.20.0.113:6443 \
|
||
|
--kubernetes-namespace spark-cluster \
|
||
|
--conf spark.kubernetes.driverEnv.SPARK_USER=hadoop \
|
||
|
--conf spark.kubernetes.driverEnv.HADOOP_USER_NAME=hadoop \
|
||
|
--conf spark.executorEnv.HADOOP_USER_NAME=hadoop \
|
||
|
--conf spark.executorEnv.SPARK_USER=hadoop \
|
||
|
--conf spark.kubernetes.authenticate.driver.serviceAccountName=spark \
|
||
|
--conf spark.driver.memory=100G \
|
||
|
--conf spark.executor.memory=10G \
|
||
|
--conf spark.driver.cores=30 \
|
||
|
--conf spark.executor.cores=2 \
|
||
|
--conf spark.driver.maxResultSize=10240m \
|
||
|
--conf spark.kubernetes.driver.limit.cores=32 \
|
||
|
--conf spark.kubernetes.executor.limit.cores=3 \
|
||
|
--conf spark.kubernetes.executor.memoryOverhead=2g \
|
||
|
--conf spark.executor.instances=5 \
|
||
|
--conf spark.app.name=spark-pi \
|
||
|
--conf spark.kubernetes.driver.docker.image=spark-driver:v2.1.0-kubernetes-0.3.1-1 \
|
||
|
--conf spark.kubernetes.executor.docker.image=spark-executor:v2.1.0-kubernetes-0.3.1-1 \
|
||
|
--conf spark.kubernetes.initcontainer.docker.image=spark-init:v2.1.0-kubernetes-0.3.1-1 \
|
||
|
--conf spark.kubernetes.resourceStagingServer.uri=http://172.20.0.114:31000 \
|
||
|
~/Downloads/tendcloud_2.10-1.0.jar
|
||
|
</code></pre>
|
||
|
<p>关于支持Kubernetes原生调度的Spark请参考:<a href="https://jimmysong.io/spark-on-k8s/" target="_blank">https://jimmysong.io/spark-on-k8s/</a></p>
|
||
|
<h2 id="open-source">Open Source</h2>
|
||
|
<blockquote>
|
||
|
<p>Contributing is Not only about code, it is about helping a community.</p>
|
||
|
</blockquote>
|
||
|
<p>下图是我们刚调研准备使用Kubernetes时候的调研方案选择。</p>
|
||
|
<figure id="fig2.2.21"><img src="https://res.cloudinary.com/jimmysong/image/upload/images/kubernetes-solutions-choices.jpg" alt="Kubernetes solutions"><figcaption>图片 - Kubernetes solutions</figcaption></figure>
|
||
|
<p>对于一个初次接触Kubernetes的人来说,看到这样一个庞大的架构选型时会望而生畏,但是Kubernetes的开源社区帮助了我们很多。</p>
|
||
|
<figure id="fig2.2.22"><img src="../images/kubernetes-sigs.jpg" alt="Kubernetes SIG"><figcaption>图片 - Kubernetes SIG</figcaption></figure>
|
||
|
<p>我组建了<strong>K8S&Cloud Native实战</strong>微信群,参与了k8smeetup、KEUC2017、<a href="https://github.com/kubernetes/kubernetes-docs-cn" target="_blank">kubernetes-docs-cn</a> Kubernetes官方中文文档项目。</p>
|
||
|
<p><strong>有用的资料和链接</strong></p>
|
||
|
<ul>
|
||
|
<li>我的博客: <a href="https://jimmysong.io" target="_blank">https://jimmysong.io</a></li>
|
||
|
<li>微信群:k8s&cloud native实战群(见:<a href="https://jimmysong.io/about" target="_blank">https://jimmysong.io/about</a>)</li>
|
||
|
<li>Meetup:k8smeetup</li>
|
||
|
<li>Cloud Native Go - 基于Go和React云原生Web应用开发:<a href="https://jimmysong.io/cloud-native-go" target="_blank">https://jimmysong.io/cloud-native-go</a></li>
|
||
|
<li>Gitbook:<a href="https://jimmysong.io/kubernetes-handbook" target="_blank">https://jimmysong.io/kubernetes-handbook</a></li>
|
||
|
<li>Cloud native开源生态:<a href="https://jimmysong.io/awesome-cloud-native/" target="_blank">https://jimmysong.io/awesome-cloud-native/</a></li>
|
||
|
<li>资料分享整理:<a href="https://github.com/rootsongjc/cloud-native-slides-share" target="_blank">https://github.com/rootsongjc/cloud-native-slides-share</a></li>
|
||
|
<li>迁移到云原生架构:<a href="https://jimmysong.io/migrating-to-cloud-native-application-architectures/" target="_blank">https://jimmysong.io/migrating-to-cloud-native-application-architectures/</a></li>
|
||
|
<li>KubeCon + CloudNativeCon 2018年11月14-15日 上海 </li>
|
||
|
</ul>
|
||
|
<footer class="page-footer"><span class="copyright">Copyright © jimmysong.io 2017 all right reserved,powered by Gitbook</span><span class="footer-modification">Updated:
|
||
|
2017-12-20 19:25:11
|
||
|
</span></footer>
|
||
|
|
||
|
</section>
|
||
|
|
||
|
</div>
|
||
|
<div class="search-results">
|
||
|
<div class="has-results">
|
||
|
|
||
|
<h1 class="search-results-title"><span class='search-results-count'></span> results matching "<span class='search-query'></span>"</h1>
|
||
|
<ul class="search-results-list"></ul>
|
||
|
|
||
|
</div>
|
||
|
<div class="no-results">
|
||
|
|
||
|
<h1 class="search-results-title">No results matching "<span class='search-query'></span>"</h1>
|
||
|
|
||
|
</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
|
||
|
</div>
|
||
|
</div>
|
||
|
|
||
|
</div>
|
||
|
|
||
|
|
||
|
|
||
|
<a href="kubernetes-and-cloud-native-app-overview.html" class="navigation navigation-prev " aria-label="Previous page: Kubernetes与云原生应用概览">
|
||
|
<i class="fa fa-angle-left"></i>
|
||
|
</a>
|
||
|
|
||
|
|
||
|
<a href="../concepts/" class="navigation navigation-next " aria-label="Next page: Kubernetes架构">
|
||
|
<i class="fa fa-angle-right"></i>
|
||
|
</a>
|
||
|
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
<script>
|
||
|
var gitbook = gitbook || [];
|
||
|
gitbook.push(function() {
|
||
|
gitbook.page.hasChanged({"page":{"title":"云原生应用之路——从Kubernetes到Cloud Native","level":"2.2","depth":1,"next":{"title":"Kubernetes架构","level":"3.1","depth":1,"path":"concepts/index.md","ref":"concepts/index.md","articles":[]},"previous":{"title":"Kubernetes与云原生应用概览","level":"2.1","depth":1,"path":"cloud-native/kubernetes-and-cloud-native-app-overview.md","ref":"cloud-native/kubernetes-and-cloud-native-app-overview.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"],"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"pluginsConfig":{"tbfed-pagefooter":{"copyright":"Copyright © jimmysong.io 2017","modify_label":"Updated:","modify_format":"YYYY-MM-DD HH:mm:ss"},"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},"highlight":{},"favicon":{"shortcut":"favicon.ico","bookmark":"favicon.ico"},"page-toc-button":{},"back-to-top-button":{},"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":{"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"showLevel":true},"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":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.1.1","level":"2.1","list_caption":"Figure: 云计算演进历程","alt":"云计算演进历程","nro":1,"url":"../images/cloud-computing-evolution-road.jpg","index":1,"caption_template":"图片 - _CAPTION_","label":"云计算演进历程","attributes":{},"skip":false,"key":"2.1.1"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.1.2","level":"2.1","list_caption":"Figure: 来自Twitter @MarcWilczek","alt":"来自Twitter @MarcWilczek","nro":2,"url":"../images/cloud-native-comes-of-age.jpg","index":2,"caption_template":"图片 - _CAPTION_","label":"来自Twitter @MarcWilczek","attributes":{},"skip":false,"key":"2.1.2"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.1.3","level":"2.1","list_caption":"Figure: Cloud native思维导图","alt":"Cloud native思维导图","nro":3,"url":"../images/cloud-native-architecutre-mindnode.jpg","index":3,"caption_template":"图片 - _CAPTION_","label":"Cloud native思维导图","attributes":{},"skip":false,"key":"2.1.3"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.1.4","level":"2.1","list_caption":"Figure: 十二因素应用","alt":"十二因素应用","nro":4,"url":"../images/12-factor-app.png","index":4,"caption_template":"图片 - _CAPTION_","label":"十二因素应用","attributes":{},"skip":false,"key":"2.1.4"},{"backlink":"cloud-native/kubernetes-and-cloud-native-app-overview.html#fig2.1.5","level":"2.1","list_caption":"Figure: 容器生态","alt":"容器生态","nro":5,"url":"../images/container-ecosystem.png","index
|
||
|
});
|
||
|
</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>
|
||
|
|