diff --git a/.vuepress/components/AdSenseBanner.vue b/.vuepress/components/AdSenseBanner.vue
index c3adf3d..eb89805 100644
--- a/.vuepress/components/AdSenseBanner.vue
+++ b/.vuepress/components/AdSenseBanner.vue
@@ -1,5 +1,5 @@
 <template>
-  <div class="adsense-banner">
+  <div class="adsense-banner" @click="$sendGaEvent('AdSense', 'AdSenseBanner', 'AdSenseBanner')">
     <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
     <!-- 正文-横幅 -->
     <ins class="adsbygoogle"
diff --git a/.vuepress/components/AdSenseLeftTop.vue b/.vuepress/components/AdSenseLeftTop.vue
new file mode 100644
index 0000000..e309c05
--- /dev/null
+++ b/.vuepress/components/AdSenseLeftTop.vue
@@ -0,0 +1,26 @@
+<template>
+  <div class="adsense-left-top" @click="$sendGaEvent('AdSense', 'AdSenseLeftTop', 'AdSenseLeftTop')">
+    <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
+    <!-- AdsenseLeftTop -->
+    <ins class="adsbygoogle"
+        style="display:block;min-width:100px;max-width:500px;width:100%;height:80px"
+        data-ad-client="ca-pub-3313149841665250"
+        data-ad-slot="4275606991"></ins>
+    <script>
+        (adsbygoogle = window.adsbygoogle || []).push({});
+    </script>
+  </div>
+</template>
+
+<script>
+export default {
+
+}
+</script>
+
+<style scoped>
+.adsense-left-top {
+  width: 100%;
+  /* background-color: grey; */
+}
+</style>
diff --git a/.vuepress/components/AdSensePageBottom.vue b/.vuepress/components/AdSensePageBottom.vue
new file mode 100644
index 0000000..b827331
--- /dev/null
+++ b/.vuepress/components/AdSensePageBottom.vue
@@ -0,0 +1,29 @@
+<template>
+  <div class="adsense-page-bottom" @click="$sendGaEvent('AdSense', 'AdSensePageBottom', 'AdSensePageBottom')">
+    <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
+    <!-- AdSensePageBottom -->
+    <ins class="adsbygoogle"
+        style="display:inline-block;min-width:200px;max-width:1000px;width:100%;height:180px"
+        data-ad-client="ca-pub-3313149841665250"
+        data-ad-slot="9035294879"
+        ></ins>
+        <!-- data-ad-format="auto"
+        data-full-width-responsive="false" -->
+    <script>
+        (adsbygoogle = window.adsbygoogle || []).push({});
+    </script>
+  </div>
+</template>
+
+<script>
+export default {
+
+}
+</script>
+
+<style scoped>
+.adsense-page-bottom {
+  /* padding-right: 2px; */
+  border: 1px solid #d7dae2;
+}
+</style>
diff --git a/.vuepress/components/AdSensePageBottomInline.vue b/.vuepress/components/AdSensePageBottomInline.vue
new file mode 100644
index 0000000..10f1aec
--- /dev/null
+++ b/.vuepress/components/AdSensePageBottomInline.vue
@@ -0,0 +1,27 @@
+<template>
+  <div class="adsense-page-bottom-inline">
+    <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
+    <!-- PageBottomInline -->
+    <ins class="adsbygoogle"
+        style="display:inline-block;min-width:200px;max-width:1000px;width:100%;height:160px"
+        data-ad-client="ca-pub-3313149841665250"
+        data-ad-slot="8977269331"></ins>
+    <script>
+        (adsbygoogle = window.adsbygoogle || []).push({});
+    </script>
+  </div>
+</template>
+
+<script>
+export default {
+
+}
+</script>
+
+<style scoped>
+.adsense-page-bottom-inline {
+  border: 1px solid #d7dae2;
+  height: 160px;
+  overflow: hidden;
+}
+</style>
diff --git a/.vuepress/components/AdSensePageTop.vue b/.vuepress/components/AdSensePageTop.vue
index 21f9bc9..51f136c 100644
--- a/.vuepress/components/AdSensePageTop.vue
+++ b/.vuepress/components/AdSensePageTop.vue
@@ -1,5 +1,5 @@
 <template>
-  <div class="adsense-page-top">
+  <div class="adsense-page-top" @click.capture="$sendGaEvent('AdSense', 'AdSensePageTop', 'AdSensePageTop')">
     <!-- <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
     <ins class="adsbygoogle"
         style="display:block; text-align:center;"
@@ -32,6 +32,10 @@ export default {
 <style scoped>
 .adsense-page-top {
   /* background-color: green; */
-  opacity: 0.2;
+  cursor: pointer;
+  padding-right: 2px;
+  border: 1px solid #d7dae2;
+  height: 124px !important;
+  overflow: hidden;
 }
 </style>
diff --git a/.vuepress/components/AdSenseParagraph.vue b/.vuepress/components/AdSenseParagraph.vue
index a9ec317..26de813 100644
--- a/.vuepress/components/AdSenseParagraph.vue
+++ b/.vuepress/components/AdSenseParagraph.vue
@@ -1,5 +1,5 @@
 <template>
-  <div class="adsense-paragraph">
+  <div class="adsense-paragraph" @click="$sendGaEvent('AdSense', 'AdSenseParagraph', 'AdSenseParagraph')">
     <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
     <ins class="adsbygoogle"
         style="display:block; text-align:center;"
@@ -22,5 +22,7 @@ export default {
 <style scoped>
 .adsense-paragraph {
   /* background-color: grey; */
+  padding-right: 2px;
+  border: 1px solid #d7dae2;
 }
 </style>
diff --git a/.vuepress/components/AdSenseRightSide.vue b/.vuepress/components/AdSenseRightSide.vue
index 1abbb90..e17d218 100644
--- a/.vuepress/components/AdSenseRightSide.vue
+++ b/.vuepress/components/AdSenseRightSide.vue
@@ -1,13 +1,14 @@
 <template>
-  <div class="adsense-right">
+  <div class="adsense-right" @click="$sendGaEvent('AdSense', 'AdSenseRightSide', 'AdSenseRightSide')">
     <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
     <!-- 右侧垂直 -->
     <ins class="adsbygoogle"
-        style="display:block"
+        style="display:block; height: 40vh; max-width: calc(50vw - 720px); min-width: 200px;"
         data-ad-client="ca-pub-3313149841665250"
         data-ad-slot="2638666669"
-        data-ad-format="auto"
-        data-full-width-responsive="true"></ins>
+    ></ins>
+    <!-- data-ad-format="auto"
+        data-full-width-responsive="true" -->
     <script>
         (adsbygoogle = window.adsbygoogle || []).push({});
     </script>
@@ -28,11 +29,11 @@ export default {
 
 .adsense-right {
   width: 500px;
-  max-width: calc(50vw - 690px);
-  height: 50vh;
+  max-width: calc(50vw - 720px);
+  height: 40vh;
   position: fixed;
-  top: 10vh;
-  right: 0.2rem;
+  bottom: 80px;
+  right: 10px;
   /* background-color: grey; */
 }
 
diff --git a/.vuepress/components/AdSenseSquare.vue b/.vuepress/components/AdSenseSquare.vue
index 828419e..499c11b 100644
--- a/.vuepress/components/AdSenseSquare.vue
+++ b/.vuepress/components/AdSenseSquare.vue
@@ -1,5 +1,5 @@
 <template>
-  <div>
+  <div @click="$sendGaEvent('AdSense', 'AdSenseSquare', 'AdSenseSquare')">
     <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
     <!-- 正方形-正文 -->
     <ins class="adsbygoogle"
diff --git a/.vuepress/components/AdSenseTitle.vue b/.vuepress/components/AdSenseTitle.vue
new file mode 100644
index 0000000..52873c7
--- /dev/null
+++ b/.vuepress/components/AdSenseTitle.vue
@@ -0,0 +1,35 @@
+<template>
+  <div class="adsense-under-title" @click="$sendGaEvent('AdSense', 'AdSensePageTopUnderTitle', 'AdSensePageTopUnderTitle')">
+    <!-- <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script> -->
+    <!-- PageTopUnderTitle -->
+    <!-- <ins class="adsbygoogle"
+        style="display:inline-block;min-width:200px;max-width:1000px;width:100%;height:50px"
+        data-ad-client="ca-pub-3313149841665250"
+        data-ad-slot="1677363818"></ins>
+    <script>
+        (adsbygoogle = window.adsbygoogle || []).push({});
+    </script> -->
+    <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
+    <ins class="adsbygoogle"
+        style="display:block"
+        data-ad-format="fluid"
+        data-ad-layout-key="-i0-3+1f-3d+2z"
+        data-ad-client="ca-pub-3313149841665250"
+        data-ad-slot="3534684042"></ins>
+    <script>
+        (adsbygoogle = window.adsbygoogle || []).push({});
+    </script>
+  </div>
+</template>
+
+<script>
+export default {
+
+}
+</script>
+
+<style scoped>
+.adsense-under-title {
+  border: 1px solid #d7dae2;
+}
+</style>
diff --git a/.vuepress/components/AdSenseVertical.vue b/.vuepress/components/AdSenseVertical.vue
index 05cafae..3b02a68 100644
--- a/.vuepress/components/AdSenseVertical.vue
+++ b/.vuepress/components/AdSenseVertical.vue
@@ -1,5 +1,5 @@
 <template>
-  <div>
+  <div @click="$sendGaEvent('AdSense', 'AdSenseVertical', 'AdSenseVertical')">
     <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
     <!-- 正文-垂直 -->
     <ins class="adsbygoogle"
diff --git a/.vuepress/enhanceApp.js b/.vuepress/enhanceApp.js
index 9037fd5..a7bcc0b 100644
--- a/.vuepress/enhanceApp.js
+++ b/.vuepress/enhanceApp.js
@@ -31,4 +31,18 @@ export default ({
       tablet: '719px 959px'
     }
   })
+  Vue.prototype.$sendGaEvent = function (category, action, label) {
+    let e = {
+      hitType: 'event',
+      eventCategory: category,
+      eventAction: action,
+      eventLabel: label
+    }
+    if (window.ga) {
+      window.ga('send', e);
+      // console.log('openOutboundLink Event', e)
+    } else {
+      console.log('开发环境，不发送 ga event', e)
+    }
+  }
 }
diff --git a/.vuepress/theme/components/Navbar.vue b/.vuepress/theme/components/Navbar.vue
index 1f62eb3..ab01ca9 100644
--- a/.vuepress/theme/components/Navbar.vue
+++ b/.vuepress/theme/components/Navbar.vue
@@ -24,6 +24,7 @@
         <a href="/learning/">
           <span style="color: #42b983;">提供K8S免费教程</span>
         </a>
+        <a href="https://webscan.qianxin.com/safe/detail/?query=kuboard.cn"><img border="0" src="https://webscan.qianxin.com/api/authcode?code=ab3ebe0592248d28477251ecaf72154f" style="display: none;"/></a>
         <!-- <span style="color: #2c3e50;">|</span>
         <a href="/support/#%E5%BE%AE%E6%9C%8D%E5%8A%A1%E8%90%BD%E5%9C%B0%E5%92%A8%E8%AF%A2">
           <span style="color: #007af5;">微服务落地咨询</span>
diff --git a/.vuepress/theme/components/Page.vue b/.vuepress/theme/components/Page.vue
index 3354391..c47bbe2 100644
--- a/.vuepress/theme/components/Page.vue
+++ b/.vuepress/theme/components/Page.vue
@@ -1,13 +1,16 @@
 <template>
   <main class="page">
     <div class="page-nav" style="max-width: 1000px; margin-top: 56px;">
-      <AdSensePageTop></AdSensePageTop>
+      <!-- <AdSensePageTop></AdSensePageTop> -->
     </div>
     <!-- <AdsenseParagraph></AdsenseParagraph> -->
     <slot name="top"/>
 
-    <Content class="theme-default-content" style="padding-top: 0; margin-top: 0;"/>
+    <Content class="theme-default-content" style="padding-top: 0; margin-top: 0; padding-bottom: 1rem;"/>
 
+    <div class="page-nav" style="max-width: 1000px; padding-top:0;">
+      <AdSensePageBottomInline/>
+    </div>
     <!-- <el-divider>加入 Kuboard 社群</el-divider> -->
 
     <div style="margin: auto; width: 182px;">
@@ -77,7 +80,6 @@
           →
         </span>
       </p>
-      <AdSenseParagraph></AdSenseParagraph>
     </div>
     <div>
     </div>
diff --git a/.vuepress/theme/components/Sidebar.vue b/.vuepress/theme/components/Sidebar.vue
index 3c4fc1a..a2d8b8c 100644
--- a/.vuepress/theme/components/Sidebar.vue
+++ b/.vuepress/theme/components/Sidebar.vue
@@ -1,12 +1,13 @@
 <template>
   <aside class="sidebar">
+    <AdSenseLeftTop />
     <slot name="top"/>
     <SidebarLinks :depth="0" :items="items"/>
     <slot name="bottom"/>
     <div style="text-align: center; margin-top: 5vh;">
-      <a target="_blank" :href="`http://demo.kuboard.cn/#/dashboard?k8sToken=${$site.themeConfig.kuboardToken}`">
+      <!-- <a target="_blank" :href="`http://demo.kuboard.cn/#/dashboard?k8sToken=${$site.themeConfig.kuboardToken}`">
         <img style="width: 242px; border: 1px solid #d7dae2;" src="/images/logo-main.png" alt="Kuboard_快速在Kubernetes上落地微服务"/>
-      </a>
+      </a> -->
 
       <p>
         <strong>
@@ -20,11 +21,11 @@
       </div>
       <p>
       </p>
-      <strong>在线答疑</strong>
+      <!-- <strong>在线答疑</strong>
       <Qq/>
       <p>
         <img src="/images/kuboard_qq.png" style="width: 120px;" alt="Kubernetes教程：QQ群在线答疑"/>
-      </p>
+      </p> -->
     </div>
     <el-divider >Kuboard</el-divider>
     <div style="height: 2rem;"></div>
diff --git a/.vuepress/theme/layouts/LearningLayout.vue b/.vuepress/theme/layouts/LearningLayout.vue
index 98e207b..b08cea2 100644
--- a/.vuepress/theme/layouts/LearningLayout.vue
+++ b/.vuepress/theme/layouts/LearningLayout.vue
@@ -35,7 +35,7 @@
         <div style="display: inline-block; vertical-align: top;">
           <li><span style="color: red; font-weight: 500;">免费</span> Kubernetes 教程，绝不降低品质</li>
           <!-- <li><span style="color: red; font-weight: 500;">在线答疑</span> 扫第一个二维码完成打赏，扫第二个进微信群聊</li> -->
-          <li><Qq></Qq> <span style="color: red; font-weight: 500;">在线答疑</span>，也可以扫描左侧导航<span style="color: red; font-weight: 500;">下方</span>的二维码加群</li>
+          <li><Qq></Qq> <span style="color: red; font-weight: 500;">在线答疑</span>，也可以扫描本文末尾的二维码加群</li>
           
           <!-- <li>根据答疑反馈，<span style="color: red; font-weight: 500;">不断完善</span> 教程</li> -->
         </div>
diff --git a/guide/README.md b/guide/README.md
index e4e4b00..c804b8d 100644
--- a/guide/README.md
+++ b/guide/README.md
@@ -5,6 +5,8 @@ description: 熟悉Kuboard_on_Kubernetes_的最佳途径。
 
 # 使用手册
 
+<AdSenseTitle/>
+
 **Kuboard 的设计目标**
 
 * 降低 Kubernetes 学习门槛，让初学者先把 Kubernetes 用起来，再逐步理解 Kubernetes 中的各种概念
diff --git a/guide/cluster/computing.md b/guide/cluster/computing.md
index 569e5d5..38b005f 100644
--- a/guide/cluster/computing.md
+++ b/guide/cluster/computing.md
@@ -8,6 +8,8 @@ meta:
 
 # 计算资源管理
 
+<AdSenseTitle/>
+
 ## 前提
 
 必须具备如下条件：
diff --git a/guide/cluster/namespace.md b/guide/cluster/namespace.md
index 1e1e395..6639fe9 100644
--- a/guide/cluster/namespace.md
+++ b/guide/cluster/namespace.md
@@ -5,6 +5,8 @@ description: 使用Kuboard管理Kubernetes名称空间。
 
 # 名称空间管理
 
+<AdSenseTitle/>
+
 ## 创建名称空间
 
 ### 前提
diff --git a/guide/cluster/storage.md b/guide/cluster/storage.md
index 5689811..7e33294 100644
--- a/guide/cluster/storage.md
+++ b/guide/cluster/storage.md
@@ -5,6 +5,8 @@ description: 使用Kuboard管理Kubernetes存储类StorageClass
 
 # 存储空间管理
 
+<AdSenseTitle/>
+
 ## 创建存储类
 
 前提
diff --git a/guide/diagonize/events.md b/guide/diagonize/events.md
index f4b71fd..6c8025c 100644
--- a/guide/diagonize/events.md
+++ b/guide/diagonize/events.md
@@ -4,6 +4,8 @@ description: 使用Kuboard监听Kubernetes集群的最新事件_并通过这些
 
 # 集群事件
 
+<AdSenseTitle/>
+
 通过观察 Kuberetes 集群事件，可以快速诊断部署时发生的问题。
 
 Kuboard 建立了与 kubernetes apiserver 的长连接，可以在第一时间将集群中的事件更新以通知的形式显示在 dashboad 上。
diff --git a/guide/diagonize/logs.md b/guide/diagonize/logs.md
index 09f159c..0ff28ba 100644
--- a/guide/diagonize/logs.md
+++ b/guide/diagonize/logs.md
@@ -4,7 +4,7 @@ description: 使用Kuboard打开并跟踪容器组的最新日志，以便对Kub
 
 # 日志及终端
 
-
+<AdSenseTitle/>
 
 # 日志
 
diff --git a/guide/diagonize/port-forward.md b/guide/diagonize/port-forward.md
index b5deabc..4a1071e 100644
--- a/guide/diagonize/port-forward.md
+++ b/guide/diagonize/port-forward.md
@@ -4,6 +4,8 @@ description: 使用Kuboard对Kubernetes上容器组的端口进行转发。
 
 # 端口转发
 
+<AdSenseTitle/>
+
 微服务环境中，各个服务都通过 TCP / UDP 端口的形式提供访问。按调用者所在位置、通信协议的形式来划分，大致有如下几种情况：
 
 | 调用者所在位置 | 通信协议     | 临时性 | 常见场景                                                     | 推荐配置方式                                                 |
diff --git a/guide/example/busybox.md b/guide/example/busybox.md
index aa46ea8..9c1684b 100644
--- a/guide/example/busybox.md
+++ b/guide/example/busybox.md
@@ -5,6 +5,8 @@ description: 使用Kuboard向Kubernetes部署一个最简单的Deployment
 
 # 部署 busybox
 
+<AdSenseTitle/>
+
 ## 前提
 
 必须具备如下条件：
diff --git a/guide/example/import.md b/guide/example/import.md
index 609df94..cd00c30 100644
--- a/guide/example/import.md
+++ b/guide/example/import.md
@@ -5,6 +5,8 @@ description: 通过Kuboard将一个预先定义好的SpringCloud微服务样例
 
 # 导入 example 微服务
 
+<AdSenseTitle/>
+
 ## 前提
 
 必须具备如下条件：
diff --git a/guide/example/monitor.md b/guide/example/monitor.md
index f5da5b8..c25a77f 100644
--- a/guide/example/monitor.md
+++ b/guide/example/monitor.md
@@ -5,6 +5,8 @@ description: 使用Kuboard在Kubernetes上安装监控套件，并对example微
 
 # 监控 example <Badge text="alpha" type="warn"/>
 
+<AdSenseTitle/>
+
 ## 前提
 
 必须具备如下条件：
diff --git a/guide/monitor/README.md b/guide/monitor/README.md
index ce68052..f1af4ba 100644
--- a/guide/monitor/README.md
+++ b/guide/monitor/README.md
@@ -4,6 +4,8 @@ description: Kuboard中的Kubernetes监控套件
 
 # 监控套件 <Badge text="alpha" type="warn"/>
 
+<AdSenseTitle/>
+
 作者已经在自己的多个项目中使用了监控套件，但是由于在使用时，需要针对具体的项目做少量的定制，因此，监控套件目前还处于 alpha 状态。
 
 监控套件分全局监控套件和局部监控套件两种类型：
diff --git a/guide/monitor/apis.md b/guide/monitor/apis.md
index 56df042..db141f0 100644
--- a/guide/monitor/apis.md
+++ b/guide/monitor/apis.md
@@ -4,6 +4,8 @@ description: 如何基于KuboardAPI实现自定义的Kubernetes监控套件
 
 # 自定义监控套件 <Badge text="alpha" type="warn"/>
 
+<AdSenseTitle/>
+
 文档建设中...
 
 > * 请参考 [监控 example](/guide/example/monitor.html) <Badge text="alpha" type="warn"/> 体验 Kuboard 在监控套件方面的设想
diff --git a/guide/namespace/adjustion.md b/guide/namespace/adjustion.md
index 3e68f2e..0da3954 100644
--- a/guide/namespace/adjustion.md
+++ b/guide/namespace/adjustion.md
@@ -4,7 +4,7 @@ description: 使用Kuboard对Kubernetes 行日常调整_包括_批量删除容
 
 # 日常调整
 
-
+<AdSenseTitle/>
 
 ## 前提
 
diff --git a/guide/namespace/configMap.md b/guide/namespace/configMap.md
index 9f0e20c..81a1926 100644
--- a/guide/namespace/configMap.md
+++ b/guide/namespace/configMap.md
@@ -4,6 +4,8 @@ description: 使用Kuboard配置Kubernetes_ConfigMap
 
 # 配置ConfigMap
 
+<AdSenseTitle/>
+
 配置： Kubernetes ConfigMap
 
 # 查看配置列表
diff --git a/guide/namespace/multi-env.md b/guide/namespace/multi-env.md
index 8669959..ca44380 100644
--- a/guide/namespace/multi-env.md
+++ b/guide/namespace/multi-env.md
@@ -4,6 +4,8 @@ description: 使用Kuboard将Kubernetes名称空间中安装的应用程序配
 
 # 多环境
 
+<AdSenseTitle/>
+
 在实际开发项目的过程中，我们必然会碰到如下场景：
 
 1. 创建一个开发环境，并在其中完成应用部署
diff --git a/guide/namespace/pvc.md b/guide/namespace/pvc.md
index 6c190f7..04817ce 100644
--- a/guide/namespace/pvc.md
+++ b/guide/namespace/pvc.md
@@ -4,6 +4,8 @@ description: 使用Kuboard配置Kubernetes的存储卷声明Persistent_Volume_Cl
 
 # 存储卷声明
 
+<AdSenseTitle/>
+
 存储卷声明： Kubernetes Persistent Volume Claim
 
 
diff --git a/guide/namespace/secrets.md b/guide/namespace/secrets.md
index a02925e..0685ee0 100644
--- a/guide/namespace/secrets.md
+++ b/guide/namespace/secrets.md
@@ -4,7 +4,7 @@ description: 使用Kuboard配置Kubernetes_Secrets
 
 # Secrets
 
-
+<AdSenseTitle/>
 
 # 查看 Secrets 列表
 
diff --git a/guide/namespace/workload.md b/guide/namespace/workload.md
index 4fb2da7..24cface 100644
--- a/guide/namespace/workload.md
+++ b/guide/namespace/workload.md
@@ -4,7 +4,7 @@ description: Kuboard_on_Kubernetes_工作负载编辑器_无需编写YAML文件
 
 # 工作负载
 
-
+<AdSenseTitle/>
 
 ## 创建/查看/编辑工作负载
 
diff --git a/install/config-kubectl.md b/install/config-kubectl.md
index 724d031..0151048 100644
--- a/install/config-kubectl.md
+++ b/install/config-kubectl.md
@@ -8,6 +8,8 @@ meta:
 
 # 配置Kubectl
 
+<AdSenseTitle/>
+
 > 参考文档： Kubernetes官网文档 [Organizing Cluster Access Using kubeconfig Files](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/)、[Configure Access to Multiple Clusters](https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/)
 
 `kubectl` 命令行工具从配置文件kubeconfig中查找用于调用 API Server 接口的信息：
diff --git a/install/history-k8s/install-k8s-1.15.1.md b/install/history-k8s/install-k8s-1.15.1.md
index 81482ac..3a69dfa 100644
--- a/install/history-k8s/install-k8s-1.15.1.md
+++ b/install/history-k8s/install-k8s-1.15.1.md
@@ -4,6 +4,8 @@ description: 使用 kubeadm 安装 Kubernetes v1.15.1 的集群，单Master节
 
 # 最值得参考的 Kubernetes 安装文档在这里
 
+<AdSenseTitle/>
+
 ## 文档特点
 
 **网上那么多 Kubernetes 安装文档，为什么这篇文档更有参考价值？**
diff --git a/install/history-k8s/install-k8s-1.15.2.md b/install/history-k8s/install-k8s-1.15.2.md
index 990952b..2a1a51f 100644
--- a/install/history-k8s/install-k8s-1.15.2.md
+++ b/install/history-k8s/install-k8s-1.15.2.md
@@ -4,6 +4,8 @@ description: Kubernetes 最新稳定版 v1.15.2 的快速安装文档。该文
 
 # 最值得参考的 Kubernetes 安装文档在这里
 
+<AdSenseTitle/>
+
 ## 文档特点
 
 **网上那么多 Kubernetes 安装文档，为什么这篇文档更有参考价值？**
diff --git a/install/history-k8s/install-k8s-1.15.3.md b/install/history-k8s/install-k8s-1.15.3.md
index c1eca51..05c921b 100644
--- a/install/history-k8s/install-k8s-1.15.3.md
+++ b/install/history-k8s/install-k8s-1.15.3.md
@@ -25,6 +25,8 @@ storyBook:
 
 # 使用 kubeadm 安装 kubernetes v1.15.3
 
+<AdSenseTitle/>
+
 <script>
 
 export default {
diff --git a/install/history-k8s/install-k8s-1.15.4.md b/install/history-k8s/install-k8s-1.15.4.md
index 3c5c0c1..8904c0f 100644
--- a/install/history-k8s/install-k8s-1.15.4.md
+++ b/install/history-k8s/install-k8s-1.15.4.md
@@ -26,6 +26,8 @@ storyBook:
 
 # 使用 kubeadm 安装 kubernetes v1.15.4
 
+<AdSenseTitle/>
+
 <script>
 
 export default {
diff --git a/install/history-k8s/install-k8s-1.16.0.md b/install/history-k8s/install-k8s-1.16.0.md
index 50a2a4b..a94f412 100644
--- a/install/history-k8s/install-k8s-1.16.0.md
+++ b/install/history-k8s/install-k8s-1.16.0.md
@@ -29,6 +29,8 @@ meta:
 
 # 使用kubeadm安装kubernetes_v1.16.0
 
+<AdSenseTitle/>
+
 <script>
 
 export default {
diff --git a/install/install-dashboard-upgrade.md b/install/install-dashboard-upgrade.md
index 49ebe4d..d84d7a7 100644
--- a/install/install-dashboard-upgrade.md
+++ b/install/install-dashboard-upgrade.md
@@ -8,6 +8,8 @@ meta:
 
 # 升级Kuboard
 
+<AdSenseTitle/>
+
 ## 最新版本
 
 [查看最新版本及更新日志](/support/change-log/v1.0.x.html)
diff --git a/install/install-dashboard.md b/install/install-dashboard.md
index 6f79439..52433c7 100644
--- a/install/install-dashboard.md
+++ b/install/install-dashboard.md
@@ -22,6 +22,8 @@ meta:
 
 # 安装Kuboard
 
+<AdSenseTitle/>
+
 <!-- <StoryBook>
 
 <div slot="overview"> -->
diff --git a/install/install-docker-desktop.md b/install/install-docker-desktop.md
index 3db7dbb..600ea83 100644
--- a/install/install-docker-desktop.md
+++ b/install/install-docker-desktop.md
@@ -8,6 +8,8 @@ meta:
 
 # 安装Kubernetes测试集群Win_Mac
 
+<AdSenseTitle/>
+
 只需要一台笔记本/台式机，就可以拥有一台用于学习的 Kubernetes 集群。单台机器可以用于学习 Kubernetes，但是，单台机器始终玩不出集群的感觉...
 
 ## 前提
diff --git a/install/install-k8s-dashboard.md b/install/install-k8s-dashboard.md
index 17a6904..2b72fb2 100644
--- a/install/install-k8s-dashboard.md
+++ b/install/install-k8s-dashboard.md
@@ -8,6 +8,8 @@ meta:
 
 # 安装Kubernetes Dashboard
 
+<AdSenseTitle/>
+
 > 参考文档： [Web UI (Dashboard)](https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/)
 
 Kubernetes Dashboard 是 Kubernetes 的官方 Web UI。使用 Kubernetes Dashboard，您可以：
diff --git a/install/install-k8s-upgrade.md b/install/install-k8s-upgrade.md
index 1684d5b..0b48143 100644
--- a/install/install-k8s-upgrade.md
+++ b/install/install-k8s-upgrade.md
@@ -8,6 +8,8 @@ meta:
 
 # Kubernetes爆发严重漏洞_可能影响所有开源版本_请尽快升级
 
+<AdSenseTitle/>
+
 参考文档：Info Q 文章 [Kubernetes 爆发严重漏洞：可能影响所有开源版本](https://www.infoq.cn/article/2lxylPOCU4cf9MR2S5fp)
 参考文档：51CTO 安全频道 [Kubernetes的严重漏洞将所有服务器暴露在DoS攻击面前!](http://netsecurity.51cto.com/art/201908/601671.htm)
 
diff --git a/install/install-k8s.md b/install/install-k8s.md
index fd2b7d0..674869c 100644
--- a/install/install-k8s.md
+++ b/install/install-k8s.md
@@ -29,6 +29,8 @@ meta:
 
 # 使用kubeadm安装kubernetes_v1.16.1
 
+<AdSenseTitle/>
+
 <script>
 
 export default {
diff --git a/install/install-kubectl.md b/install/install-kubectl.md
index 7aef440..5d2f2ad 100644
--- a/install/install-kubectl.md
+++ b/install/install-kubectl.md
@@ -9,6 +9,8 @@ meta:
 
 # 安装Kubectl
 
+<AdSenseTitle/>
+
 日常工作中，您可能需要在自己的笔记本电脑上执行 kubectl 命令以管理远程 Linux 服务器上的 Kubernetes 集群。
 
 ::: tip
diff --git a/install/install-kubernetes.md b/install/install-kubernetes.md
index e835067..20b1cb9 100644
--- a/install/install-kubernetes.md
+++ b/install/install-kubernetes.md
@@ -26,6 +26,8 @@ meta:
 
 # 安装Kubernetes高可用
 
+<AdSenseTitle/>
+
 <!-- <StoryBook>
 
 <div slot="overview"> -->
diff --git a/install/upgrade-k8s/1.15.x-1.15.4.md b/install/upgrade-k8s/1.15.x-1.15.4.md
index 97a72e3..fd8a299 100644
--- a/install/upgrade-k8s/1.15.x-1.15.4.md
+++ b/install/upgrade-k8s/1.15.x-1.15.4.md
@@ -8,6 +8,8 @@ meta:
 
 # K8S从1.15.x升级到 1.15.4
 
+<AdSenseTitle/>
+
 参考文档： kubernetes 官网文档 [kubeadm upgrade](https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/)
 
 
diff --git a/install/upgrade-k8s/1.15.x-1.16.x.md b/install/upgrade-k8s/1.15.x-1.16.x.md
index dc5ee59..10b89f7 100644
--- a/install/upgrade-k8s/1.15.x-1.16.x.md
+++ b/install/upgrade-k8s/1.15.x-1.16.x.md
@@ -8,6 +8,8 @@ meta:
 
 # K8S从1.15.x(1.16.x)升级到 1.16.x
 
+<AdSenseTitle/>
+
 参考文档： kubernetes 官网文档 [kubeadm upgrade](https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/)
 
 本文描述了如何从 kubernetes v1.15.x（或1.16.x）升级到 Kubernetes v1.16.y，前提是，您的 Kubernetes 集群是使用 kubeadm 安装的。
@@ -52,6 +54,10 @@ yum list --showduplicates kubeadm --disableexcludes=kubernetes
   ```
   执行命令 `kubeadm version`，以验证升级结果
 
+  ::: danger 替换 1.16.x 中的 x
+  本文中，所有碰到 1.16.x 的地方，都要将其中的 x 替换为您前面查询到的最新补丁号
+  :::
+
 * 在第一个 master 节点上执行命令 `kubeadm upgrade plan`，输出结果如下所示：
 
   ``` {9,24,25,26,27,28,29}
diff --git a/learning/README.md b/learning/README.md
index 0992d48..6501dbc 100644
--- a/learning/README.md
+++ b/learning/README.md
@@ -10,6 +10,8 @@ meta:
 
 # Kubernetes免费中文教程
 
+<AdSenseTitle/>
+
 
 本教程的主要依据是：Kubernetes 官网文档，以及使用 Kubernetes 落地 Spring Cloud 微服务并投产的实战经验。适用人群：
 * Kubernetes 初学者
diff --git a/learning/k8s-advanced/index.md b/learning/k8s-advanced/index.md
index b52c953..67757b4 100644
--- a/learning/k8s-advanced/index.md
+++ b/learning/k8s-advanced/index.md
@@ -6,6 +6,8 @@ description: Kubernetes教程_高级篇_主要涉及日志采集_安全_监控_
 
 # Kubernetes教程深入篇
 
+<AdSenseTitle/>
+
 Kubernetes教程的深入篇部分，主要涉及的内容有如下几个方面：
 
 * [问题诊断](./ts/application.html)
diff --git a/learning/k8s-advanced/logs/basic.md b/learning/k8s-advanced/logs/basic.md
index 2012121..2f0e7c5 100644
--- a/learning/k8s-advanced/logs/basic.md
+++ b/learning/k8s-advanced/logs/basic.md
@@ -9,6 +9,8 @@ meta:
 
 # 基本的日志
 
+<AdSenseTitle/>
+
 本章节中，您将了解到如何在 Kubernetes 中使用最基本的日志，此时，日志信息将输出到标准输出流（standard output stream）。请参考下面的例子，该例子中的 Pod 包含一个容器，该容器每秒钟向标准输出写入一些文本内容：
 
 <<< @/.vuepress/public/statics/learning/logs/counter-pod.yaml
diff --git a/learning/k8s-advanced/logs/cluster.md b/learning/k8s-advanced/logs/cluster.md
index a8e05b8..43fad1d 100644
--- a/learning/k8s-advanced/logs/cluster.md
+++ b/learning/k8s-advanced/logs/cluster.md
@@ -9,6 +9,8 @@ meta:
 
 # 集群级别的日志
 
+<AdSenseTitle/>
+
 Kubernetes 中并不默认提供集群级别的日志，不过，有许多种途径可以和集群级别的日志整合。例如：
 * 在每个节点上配置日志代理
 * 在应用程序的 Pod 中包含一个专门用于收集日志的 sidecar 容器
diff --git a/learning/k8s-advanced/logs/elk.md b/learning/k8s-advanced/logs/elk.md
index b8ad27e..6df4995 100644
--- a/learning/k8s-advanced/logs/elk.md
+++ b/learning/k8s-advanced/logs/elk.md
@@ -9,4 +9,6 @@ meta:
 
 # 使用ELK作为集群级别的日志
 
+<AdSenseTitle/>
+
 待更新 ...
diff --git a/learning/k8s-advanced/logs/index.md b/learning/k8s-advanced/logs/index.md
index 1fa1c7a..6c6c8aa 100644
--- a/learning/k8s-advanced/logs/index.md
+++ b/learning/k8s-advanced/logs/index.md
@@ -9,6 +9,8 @@ meta:
 
 # 日志架构
 
+<AdSenseTitle/>
+
 > 参考文档： [Logging Architecture](https://kubernetes.io/docs/concepts/cluster-administration/logging/)
 
 当集群中出现任何问题时，应用程序日志和系统日志是非常有效的定位问题的手段，可以让我们知道集群中正在发生的事情。绝大多数的应用程序都有日志机制，主流的容器引擎也都支持某种形式的日志。对容器化应用程序来说，最简单也是被采纳得最多的一种日志方式是，将日志写入到标准输出流（例如，Java中的 `System.out.println` 语句，或 log4j 中的 Console Appender）和标准错误流里（例如，Java中的 `System.error.println` 语句）
diff --git a/learning/k8s-advanced/logs/node.md b/learning/k8s-advanced/logs/node.md
index dd8ff19..5be128f 100644
--- a/learning/k8s-advanced/logs/node.md
+++ b/learning/k8s-advanced/logs/node.md
@@ -9,6 +9,8 @@ meta:
 
 # 节点级别的日志
 
+<AdSenseTitle/>
+
 ## 日志存储
 
 ![Kubernetes_教程_节点级别的日志](./node.assets/logging-node-level.png)
diff --git a/learning/k8s-advanced/schedule/index.md b/learning/k8s-advanced/schedule/index.md
index c703246..78cbf59 100644
--- a/learning/k8s-advanced/schedule/index.md
+++ b/learning/k8s-advanced/schedule/index.md
@@ -9,6 +9,8 @@ meta:
 
 # 调度
 
+<AdSenseTitle/>
+
 > 参考文档： [Kubernetes Scheduler](https://kubernetes.io/docs/concepts/scheduling/kube-scheduler/)
 
 在Kubernetes中，调度（Scheduling），指的是为 Pod 找到一个合适的节点，并由该节点上的 kubelet 运行 Pod。
diff --git a/learning/k8s-advanced/ts/application.md b/learning/k8s-advanced/ts/application.md
index 024a629..df2be11 100644
--- a/learning/k8s-advanced/ts/application.md
+++ b/learning/k8s-advanced/ts/application.md
@@ -9,6 +9,8 @@ meta:
 
 # 诊断应用程序
 
+<AdSenseTitle/>
+
 > 参考文档： [Troubleshoot Applications](https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/)
 
 本文档可帮助您诊断部署到Kubernetes中的应用程序所出现的问题。如果仍然解决不了，请加本文末尾的QQ群答疑。也可以了解 [更多支持方式](/support/)
diff --git a/learning/k8s-advanced/ts/cluster.md b/learning/k8s-advanced/ts/cluster.md
index 5de791f..6fa8d26 100644
--- a/learning/k8s-advanced/ts/cluster.md
+++ b/learning/k8s-advanced/ts/cluster.md
@@ -9,6 +9,8 @@ meta:
 
 # 诊断集群问题
 
+<AdSenseTitle/>
+
 > 参考文档：[Troubleshoot Clusters](https://kubernetes.io/docs/tasks/debug-application-cluster/debug-cluster/)
 
 本文主要是关于如何诊断集群出现的问题，此时，假设您已经经过排查，确认当前碰到问题的 root cause（问题的根源）不是应用程序的问题。参考 [诊断应用程序](./application.html)。
diff --git a/learning/k8s-basics/deploy-app.md b/learning/k8s-basics/deploy-app.md
index 7d1c0d2..9ca4d57 100644
--- a/learning/k8s-basics/deploy-app.md
+++ b/learning/k8s-basics/deploy-app.md
@@ -9,6 +9,8 @@ meta:
 
 # 1.部署一个应用程序
 
+<AdSenseTitle/>
+
 本文翻译自 Kubernetes 官网 [Using kubectl to Create a Deployment](https://kubernetes.io/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro/) ，并有所改写
 
 ### 前提
diff --git a/learning/k8s-basics/explore.md b/learning/k8s-basics/explore.md
index 7272020..ccc52be 100644
--- a/learning/k8s-basics/explore.md
+++ b/learning/k8s-basics/explore.md
@@ -9,6 +9,8 @@ meta:
 
 # 2.查看Pods/Nodes
 
+<AdSenseTitle/>
+
 本文翻译自 Kubernetes 官网 [Viewing Pods and Nodes](https://kubernetes.io/docs/tutorials/kubernetes-basics/explore/explore-intro/) ，并有所改写
 
 ## 目标
diff --git a/learning/k8s-basics/expose.md b/learning/k8s-basics/expose.md
index 7319d74..f5c93de 100644
--- a/learning/k8s-basics/expose.md
+++ b/learning/k8s-basics/expose.md
@@ -9,6 +9,8 @@ meta:
 
 # 3.公布应用程序
 
+<AdSenseTitle/>
+
 本文翻译自 Kubernetes 官网 [Using a Service to Expose Your App](https://kubernetes.io/docs/tutorials/kubernetes-basics/expose/expose-intro/) ，并有所改写
 
 ## 目标
diff --git a/learning/k8s-basics/k8s-core-concepts.md b/learning/k8s-basics/k8s-core-concepts.md
index b9d88e1..8c803df 100644
--- a/learning/k8s-basics/k8s-core-concepts.md
+++ b/learning/k8s-basics/k8s-core-concepts.md
@@ -9,6 +9,8 @@ meta:
 
 # 6.复习Kubernetes核心概念
 
+<AdSenseTitle/>
+
 > 转载信息：
 >
 > 译者：崔婧雯
diff --git a/learning/k8s-basics/kubernetes-basics.md b/learning/k8s-basics/kubernetes-basics.md
index e511f45..150f9e2 100644
--- a/learning/k8s-basics/kubernetes-basics.md
+++ b/learning/k8s-basics/kubernetes-basics.md
@@ -9,6 +9,8 @@ meta:
 
 # 0.学习Kubernetes基础知识
 
+<AdSenseTitle/>
+
 本文翻译自 Kubernetes 官网 [Learn Kubernetes Basics](https://kubernetes.io/docs/tutorials/kubernetes-basics/) ，并有所改写
 
 相信很多初学者在入门 Kubernetes (以下简称k8s)时，都会被各种英文单词所困扰(例如：Deployment、Pod、Service等)，这些名词在被翻译后也往往失去了原意，更不能体现出他们的相互关系。笔者在刚开始学习k8s时也遭遇到这种困境。但是，任何复杂的系统都是发源于最基本的公式或定理，k8s虽然庞大且复杂，不过只要抓住一些基本的脉络(一些最基本的组件的定义及使用)，入门便也是毫不费劲。
diff --git a/learning/k8s-basics/scale.md b/learning/k8s-basics/scale.md
index 3e59bd8..d0937ff 100644
--- a/learning/k8s-basics/scale.md
+++ b/learning/k8s-basics/scale.md
@@ -9,6 +9,8 @@ meta:
 
 # 4.伸缩应用程序
 
+<AdSenseTitle/>
+
 本文翻译自 Kubernetes 官网 [Running Multiple Instances of Your App](https://kubernetes.io/docs/tutorials/kubernetes-basics/scale/scale-intro/) ，并有所改写
 
 ## 目标
diff --git a/learning/k8s-basics/update.md b/learning/k8s-basics/update.md
index 6abff21..9e8b34c 100644
--- a/learning/k8s-basics/update.md
+++ b/learning/k8s-basics/update.md
@@ -9,6 +9,8 @@ meta:
 
 # 5.执行滚动更新
 
+<AdSenseTitle/>
+
 本文翻译自 Kubernetes 官网 [Performing a Rolling Update](https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/) ，并有所改写
 
 ## 目标
diff --git a/learning/k8s-bg/architecture/com-m-n.md b/learning/k8s-bg/architecture/com-m-n.md
index 2ea2057..0ebe797 100644
--- a/learning/k8s-bg/architecture/com-m-n.md
+++ b/learning/k8s-bg/architecture/com-m-n.md
@@ -10,6 +10,8 @@ meta:
 
 # Master to Cluster
 
+<AdSenseTitle/>
+
 从 master（apiserver）到Cluster存在着两条主要的通信路径：
 * apiserver 访问集群中每个节点上的 kubelet 进程
 * 使用 apiserver 的 proxy 功能，从 apiserver 访问集群中的任意节点、Pod、Service
diff --git a/learning/k8s-bg/architecture/com-n-m.md b/learning/k8s-bg/architecture/com-n-m.md
index f901067..7af0642 100644
--- a/learning/k8s-bg/architecture/com-n-m.md
+++ b/learning/k8s-bg/architecture/com-n-m.md
@@ -9,6 +9,8 @@ meta:
 
 # Cluster to Master
 
+<AdSenseTitle/>
+
 所有从集群访问 Master 节点的通信，都是针对 apiserver 的（没有任何其他 master 组件发布远程调用接口）。通常安装 Kubernetes 时，apiserver 监听 HTTPS 端口（443），并且配置了一种或多种 [客户端认证方式 authentication](https://kubernetes.io/docs/reference/access-authn-authz/authentication/)。至少需要配置一种形式的 [授权方式 authorization](https://kubernetes.io/docs/reference/access-authn-authz/authorization/)，尤其是 [匿名访问 anonymous requests](https://kubernetes.io/docs/reference/access-authn-authz/authentication/#anonymous-requests) 或 [Service Account Tokens](https://kubernetes.io/docs/reference/access-authn-authz/authentication/#service-account-tokens) 被启用的情况下。
 
 节点上必须配置集群（apiserver）的公钥根证书（public root certificate），此时，在提供有效的客户端身份认证的情况下，节点可以安全地访问 APIServer。例如，在 Google Kubernetes Engine 的一个默认 Kubernetes 安装里，通过客户端证书为 kubelet 提供客户端身份认证。请参考 [kubelet TLS bootstrapping](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/)，了解如何自动为 kubelet 提供客户端证书。
diff --git a/learning/k8s-bg/architecture/com.md b/learning/k8s-bg/architecture/com.md
index 6a7db9a..d2fcae9 100644
--- a/learning/k8s-bg/architecture/com.md
+++ b/learning/k8s-bg/architecture/com.md
@@ -9,6 +9,8 @@ meta:
 
 # Master-Node之间的通信
 
+<AdSenseTitle/>
+
 本文描述了Kubernetes集群和Master节点（实际上是 apiserver）之间的通信路径。用户在自定义集群的安装之前，或者调整集群的网络配置之前必须理解这部分内容。例如：
 * 从 [安装Kubernetes单Master节点](/install/install-k8s.html) 的安装结果调整到 [安装Kubernetes高可用](/install/install-kubernetes.html) 的安装结果
 * 将公网 IP 地址上的机器作为节点加入到 Kubernetes 集群
diff --git a/learning/k8s-bg/architecture/controller.md b/learning/k8s-bg/architecture/controller.md
index fef7b5c..e7a5447 100644
--- a/learning/k8s-bg/architecture/controller.md
+++ b/learning/k8s-bg/architecture/controller.md
@@ -9,6 +9,8 @@ meta:
 
 # 控制器
 
+<AdSenseTitle/>
+
 在机器人技术和自动化技术中，**控制循环** 是一个控制系统状态的无限循环。房间里的恒温器就是**控制循环**的一个例子
 
 * 在恒温器上设定好目标温度，就是在告诉该 **控制循环** 你想要的 ***目标状态***。
diff --git a/learning/k8s-bg/architecture/nodes-mgmt.md b/learning/k8s-bg/architecture/nodes-mgmt.md
index 06a5f80..700c576 100644
--- a/learning/k8s-bg/architecture/nodes-mgmt.md
+++ b/learning/k8s-bg/architecture/nodes-mgmt.md
@@ -9,6 +9,8 @@ meta:
 
 # 节点管理
 
+<AdSenseTitle/>
+
 与 Pod 和 Service 不一样，节点并不是由 Kubernetes 创建的，节点由云供应商（例如，Google Compute Engine、阿里云等）创建，或者节点已经存在于您的物理机/虚拟机的资源池。向 Kubernetes 中创建节点时，仅仅是创建了一个描述该节点的 API 对象。节点 API 对象创建成功后，Kubernetes将检查该节点是否有效。例如，假设您创建如下节点信息：
 
 ``` yaml
diff --git a/learning/k8s-bg/architecture/nodes.md b/learning/k8s-bg/architecture/nodes.md
index b385919..d6fa9b3 100644
--- a/learning/k8s-bg/architecture/nodes.md
+++ b/learning/k8s-bg/architecture/nodes.md
@@ -9,6 +9,8 @@ meta:
 
 # 节点
 
+<AdSenseTitle/>
+
 Kubernetes中节点（node）指的是一个工作机器，曾经叫做 `minion`。不同的集群中，节点可能是虚拟机也可能是物理机。每个节点都由 master 组件管理，并包含了运行 Pod（容器组）所需的服务。这些服务包括：
 * [容器引擎](/learning/k8s-bg/component.html#容器引擎)
 * kubelet
diff --git a/learning/k8s-bg/component.md b/learning/k8s-bg/component.md
index cd6c257..0e3d0ac 100644
--- a/learning/k8s-bg/component.md
+++ b/learning/k8s-bg/component.md
@@ -9,6 +9,8 @@ meta:
 
 # Kubernetes组件
 
+<AdSenseTitle/>
+
 > 参考文档： [Kubernetes Components](https://kubernetes.io/docs/concepts/overview/components/)
 
 本文档描述了 Kubernetes 的主要组件。
diff --git a/learning/k8s-bg/what-is-k8s.md b/learning/k8s-bg/what-is-k8s.md
index 14f6270..7b6a2e6 100644
--- a/learning/k8s-bg/what-is-k8s.md
+++ b/learning/k8s-bg/what-is-k8s.md
@@ -9,6 +9,8 @@ meta:
 
 # Kubernetes介绍
 
+<AdSenseTitle/>
+
 > 参考文档： [What is Kubernetes](https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/)
 
 Kubernetes是一个可以移植、可扩展的开源平台，使用 [声明式的配置](/learning/k8s-intermediate/workload/wl-deployment/#deployment-概述) 并依据配置信息自动地执行容器化应用程序的管理。在所有的容器编排工具中（类似的还有 docker swarm / mesos等），Kubernetes的生态系统更大、增长更快，有更多的支持、服务和工具可供用户选择。
diff --git a/learning/k8s-intermediate/config/assign-pod-node.md b/learning/k8s-intermediate/config/assign-pod-node.md
index 64fb6fa..00857c8 100644
--- a/learning/k8s-intermediate/config/assign-pod-node.md
+++ b/learning/k8s-intermediate/config/assign-pod-node.md
@@ -9,6 +9,8 @@ meta:
 
 # 将容器组调度到指定的节点
 
+<AdSenseTitle/>
+
 参考文档： Kubernetes 官网 [Assigning Pods to Nodes](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/)
 
 ## 概述
diff --git a/learning/k8s-intermediate/config/computing-resource.md b/learning/k8s-intermediate/config/computing-resource.md
index ec77f31..8b8a695 100644
--- a/learning/k8s-intermediate/config/computing-resource.md
+++ b/learning/k8s-intermediate/config/computing-resource.md
@@ -9,6 +9,8 @@ meta:
 
 # 管理容器的计算资源
 
+<AdSenseTitle/>
+
 参考文档： Kubernetes 官网 [Managing Compute Resources for Containers](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/)
 
 ## 概述
diff --git a/learning/k8s-intermediate/config/config-map.md b/learning/k8s-intermediate/config/config-map.md
index 0b978a6..a058f15 100644
--- a/learning/k8s-intermediate/config/config-map.md
+++ b/learning/k8s-intermediate/config/config-map.md
@@ -9,6 +9,8 @@ meta:
 
 # 使用ConfigMap配置您的应用程序
 
+<AdSenseTitle/>
+
 本文参考了 Kubernetes 官网 [Configure a Pod to Use a ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap)，并有所改写
 
 Kubernetes ConfigMap 可以将配置信息和容器镜像解耦，以使得容器化的应用程序可移植。本文提供了一系列的实例，解释如何通过 Kuboard 创建 ConfigMap 以及如何使用 ConfigMap 中的数据配置 Pod（容器组）。
diff --git a/learning/k8s-intermediate/config/sec-ctx/con-cap.md b/learning/k8s-intermediate/config/sec-ctx/con-cap.md
index e2bf1b0..dbfb2b8 100644
--- a/learning/k8s-intermediate/config/sec-ctx/con-cap.md
+++ b/learning/k8s-intermediate/config/sec-ctx/con-cap.md
@@ -9,6 +9,8 @@ meta:
 
 # 为容器设置Linux Capabilities
 
+<AdSenseTitle/>
+
 使用 [Linux Capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html) 可以为容器内的进程授予某些特定的权限（而不是 root 用户的所有权限）。在容器定义的 `securityContext` 中添加 `capabilities` 字段，可以向容器添加或删除 Linux Capability。
 
 本文后续章节中，先运行一个不包含 `capabilities` 字段的容器，观察容器内进程的 linux capabilities 位图的情况；然后在运行一个包含 `capabilities` 字段的容器，比较其 linux capabilities 位图与前者的不同。
diff --git a/learning/k8s-intermediate/config/sec-ctx/con-kuboard.md b/learning/k8s-intermediate/config/sec-ctx/con-kuboard.md
index 4b8d050..ce55d70 100644
--- a/learning/k8s-intermediate/config/sec-ctx/con-kuboard.md
+++ b/learning/k8s-intermediate/config/sec-ctx/con-kuboard.md
@@ -9,6 +9,8 @@ meta:
 
 # Kuboard中容器的Security Context
 
+<AdSenseTitle/>
+
 通过 Kuboard，可以直接设定 Deployment、StatefulSet、DaemonSet 等中容器的 securityContext 的内容。在 Kuboard 工作负载编辑器界面中点击 **容器组的更多设定** 按钮，可查看到容器的 Security Context 设置界面，如下图所示：
 
 ![Kubernetes教程_Kuboard中设置容器的SecurityContext](./con-kuboard.assets/image-20191005230605496.png)
@@ -28,4 +30,3 @@ meta:
 | procMount                                    | string                                                      | procMount 代表了容器的 proc mount 的类型。默认值是 `DefaultProcMount`（使用容器引擎的默认值）。该字段需要激活 Kubernetes 的ProcMountType 特性 |
 | capabilities                                 | <div style="width: 80px;">add: array<br />drop: array</div> | 为容器进程 add/drop Linux capabilities。默认使用容器引擎的设定。更多内容请参考 [为容器设置Linux Capabilities](./con-cap.html) |
 | seLinuxOptions                               |                                                             | 此字段设定的 SELinux 上下文将被应用到 Pod 中所有容器。如果不指定，容器引擎将为每个容器分配一个随机的 SELinux 上下文。<font color="grey">也可以在Pod的SecurityContext中设定，如果 Pod 和容器的 securityContext 中都设定了这个字段，则对该容器来说以容器中的设置为准。</font> |
-
diff --git a/learning/k8s-intermediate/config/sec-ctx/con-sel.md b/learning/k8s-intermediate/config/sec-ctx/con-sel.md
index 330f4de..62dd4e6 100644
--- a/learning/k8s-intermediate/config/sec-ctx/con-sel.md
+++ b/learning/k8s-intermediate/config/sec-ctx/con-sel.md
@@ -9,6 +9,8 @@ meta:
 
 # 为容器设置SELinux标签
 
+<AdSenseTitle/>
+
 Pod 或容器定义的 `securityContext` 中 `seLinuxOptions` 字段是一个 [SELinuxOptions](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.16/#selinuxoptions-v1-core) 对象，该字段可用于为容器指定 SELinux 标签。如下所示：
 
 ``` yaml
diff --git a/learning/k8s-intermediate/config/sec-ctx/con.md b/learning/k8s-intermediate/config/sec-ctx/con.md
index 9b7ee9d..c53f557 100644
--- a/learning/k8s-intermediate/config/sec-ctx/con.md
+++ b/learning/k8s-intermediate/config/sec-ctx/con.md
@@ -9,6 +9,8 @@ meta:
 
 # 为容器设置Security Context
 
+<AdSenseTitle/>
+
 容器的定义中包含 `securityContext` 字段，该字段接受 [SecurityContext](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.16/#securitycontext-v1-core) 对象。通过指定该字段，可以为容器设定安全相关的配置，当该字段的配置与 Pod 级别的 `securityContext` 配置相冲突时，容器级别的配置将覆盖 Pod 级别的配置。容器级别的 `securityContext` 不影响 Pod 中的数据卷。
 
 下面的示例中的 Pod 包含一个 Container，且 Pod 和 Container 都有定义 `securityContext` 字段：
diff --git a/learning/k8s-intermediate/config/sec-ctx/index.md b/learning/k8s-intermediate/config/sec-ctx/index.md
index 97f62e0..2b4ebb2 100644
--- a/learning/k8s-intermediate/config/sec-ctx/index.md
+++ b/learning/k8s-intermediate/config/sec-ctx/index.md
@@ -10,6 +10,8 @@ meta:
 
 # 概述
 
+<AdSenseTitle/>
+
 > 参考文档：Kubernetes 官网文档 [Configure a Security Context for a Pod or Container](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#assign-selinux-labels-to-a-container)
 
 Security Context（安全上下文）用来限制容器对宿主节点的可访问范围，以避免容器非法操作宿主节点的系统级别的内容，使得节点的系统或者节点上其他容器组受到影响。
diff --git a/learning/k8s-intermediate/config/sec-ctx/pod-kuboard.md b/learning/k8s-intermediate/config/sec-ctx/pod-kuboard.md
index 911b860..dc5ae63 100644
--- a/learning/k8s-intermediate/config/sec-ctx/pod-kuboard.md
+++ b/learning/k8s-intermediate/config/sec-ctx/pod-kuboard.md
@@ -9,6 +9,8 @@ meta:
 
 # Kuboard中Pod的Security Context
 
+<AdSenseTitle/>
+
 通过 Kuboard，可以直接设定 Deployment、StatefulSet、DaemonSet 等中 Pod 模板的 securityContext 的内容。在 Kuboard 工作负载编辑器界面中点击 **容器组的更多设定** 按钮，可查看到 Pod 的 Security Context 设置界面，如下图所示：
 
 ![Kubernetes教程_Kuboard中Pod的SecurityContext](./pod-kuboard.assets/image-20191004221427371.png)
diff --git a/learning/k8s-intermediate/config/sec-ctx/pod.md b/learning/k8s-intermediate/config/sec-ctx/pod.md
index eb7a858..e07a1eb 100644
--- a/learning/k8s-intermediate/config/sec-ctx/pod.md
+++ b/learning/k8s-intermediate/config/sec-ctx/pod.md
@@ -9,6 +9,8 @@ meta:
 
 # 为Pod设置Security Context
 
+<AdSenseTitle/>
+
 在 Pod 的定义中增加 `securityContext` 字段，即可为 Pod 指定 Security 相关的设定。 `securityContext` 字段是一个 [PodSecurityContext](./pod-kuboard.html) 对象。通过该字段指定的内容将对该 Pod 中所有的容器生效。
 
 ## Pod示例
diff --git a/learning/k8s-intermediate/config/sec-ctx/volumes.md b/learning/k8s-intermediate/config/sec-ctx/volumes.md
index 2c1f1e4..16cb870 100644
--- a/learning/k8s-intermediate/config/sec-ctx/volumes.md
+++ b/learning/k8s-intermediate/config/sec-ctx/volumes.md
@@ -9,6 +9,8 @@ meta:
 
 # 关于数据卷
 
+<AdSenseTitle/>
+
 Pod 的 securityContext 作用于 Pod 中所有的容器，同时对 Pod 的数据卷也同样生效。具体来说，`fsGroup` 和 `seLinuxOptions` 将被按照如下方式应用到 Pod 中的数据卷：
 * `fsGroup`：对于支持 ownership 管理的数据卷，通过 `fsGroup` 指定的 GID 将被设置为该数据卷的 owner，并且可被 `fsGroup` 写入。更多细节请参考 [Ownership Management design document](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/volume-ownership-management.md)
 * `seLinuxOptions`：对于支持 SELinux 标签的数据卷，将按照 `seLinuxOptions` 的设定重新打标签，以使 Pod 可以访问数据卷内容。通常您只需要设置 `seLinuxOptions` 中 `level` 这一部分内容。该设定为 Pod 中所有容器及数据卷设置 [Multi-Category Security (MCS)](https://selinuxproject.org/page/NB_MLS) 标签。
diff --git a/learning/k8s-intermediate/config/secrets/create-generator.md b/learning/k8s-intermediate/config/secrets/create-generator.md
index c0ba539..6e8b419 100644
--- a/learning/k8s-intermediate/config/secrets/create-generator.md
+++ b/learning/k8s-intermediate/config/secrets/create-generator.md
@@ -9,6 +9,8 @@ meta:
 
 # 创建Secret（使用Generator）
 
+<AdSenseTitle/>
+
 从 kubernetes v1.14 开始，kubectl 集成了 [Kustomize](https://kustomize.io/)。通过 Kustomize，您可以使用 generator（Kustomize 的概念）创建 Secret，并保存到 API Server。Generator 必须在 `kustomization.yaml` 文件中指定。
 
 ::: tip
diff --git a/learning/k8s-intermediate/config/secrets/create-kubectl.md b/learning/k8s-intermediate/config/secrets/create-kubectl.md
index eec3f1d..867c7ee 100644
--- a/learning/k8s-intermediate/config/secrets/create-kubectl.md
+++ b/learning/k8s-intermediate/config/secrets/create-kubectl.md
@@ -9,6 +9,8 @@ meta:
 
 # 创建Secret（使用kubectl）
 
+<AdSenseTitle/>
+
 假设某个 Pod 需要访问数据库。在您执行 kubectl 命令所在机器的当前目录，创建文件 `./username.txt` 文件和 `./password.txt` 暂存数据库的用户名和密码，后续我们根据这两个文件配置 kubernetes secrets。
 
 ```sh
diff --git a/learning/k8s-intermediate/config/secrets/create-kuboard.md b/learning/k8s-intermediate/config/secrets/create-kuboard.md
index c370de0..0ae000e 100644
--- a/learning/k8s-intermediate/config/secrets/create-kuboard.md
+++ b/learning/k8s-intermediate/config/secrets/create-kuboard.md
@@ -9,6 +9,8 @@ meta:
 
 # 创建Secret（使用Kuboard）
 
+<AdSenseTitle/>
+
 本文简要描述如何在 Kuboard 中创建 Kubernetes Secret。
 
 Kubernetes Secret 必须从属于某一个名称空间，进入 Kuboard 名称空间界面，Secret 列表在名称空间的左上角。如下图所示：
diff --git a/learning/k8s-intermediate/config/secrets/create-manually.md b/learning/k8s-intermediate/config/secrets/create-manually.md
index 37986be..40fadad 100644
--- a/learning/k8s-intermediate/config/secrets/create-manually.md
+++ b/learning/k8s-intermediate/config/secrets/create-manually.md
@@ -9,6 +9,8 @@ meta:
 
 # 创建Secret（手动）
 
+<AdSenseTitle/>
+
 和创建其他类型的 API 对象（Pod、Deployment、StatefulSet、ConfigMap 等）一样，您也可以先在 yaml 文件中定义好 Secret，然后通过 `kubectl apply -f` 命令创建。此时，您可以通过如下两种方式在 yaml 文件中定义 Secret：
 * **data**：使用 data 字段时，取值的内容必须是 base64 编码的
 * **stringData**：使用 stringData 时，更为方便，您可以直接将取值以明文的方式写在 yaml 文件中
diff --git a/learning/k8s-intermediate/config/secrets/decode-edit.md b/learning/k8s-intermediate/config/secrets/decode-edit.md
index 3530faa..33c4e11 100644
--- a/learning/k8s-intermediate/config/secrets/decode-edit.md
+++ b/learning/k8s-intermediate/config/secrets/decode-edit.md
@@ -9,6 +9,8 @@ meta:
 
 # 解码和编辑Secret
 
+<AdSenseTitle/>
+
 ## 解码Secret
 
 Secret 中的信息可以通过 `kubectl get secret` 命令获取。例如，执行命令 `kubectl get secret mysecret -o yaml
diff --git a/learning/k8s-intermediate/config/secrets/index.md b/learning/k8s-intermediate/config/secrets/index.md
index b16cca9..88055cc 100644
--- a/learning/k8s-intermediate/config/secrets/index.md
+++ b/learning/k8s-intermediate/config/secrets/index.md
@@ -9,6 +9,8 @@ meta:
 
 # Secret概述
 
+<AdSenseTitle/>
+
 参考文档： Kubernetes 官网文档 [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/)
 
 ## 概述
diff --git a/learning/k8s-intermediate/config/secrets/use-case-ingress-tls.md b/learning/k8s-intermediate/config/secrets/use-case-ingress-tls.md
index 48a65d4..2f2c61c 100644
--- a/learning/k8s-intermediate/config/secrets/use-case-ingress-tls.md
+++ b/learning/k8s-intermediate/config/secrets/use-case-ingress-tls.md
@@ -9,7 +9,7 @@ meta:
 
 # 使用Secret存储Ingress TLS证书
 
-
+<AdSenseTitle/>
 
 可以直接在 Ingress 中配置 HTTPS 证书，使得你的网站支持 HTTPS 协议。
 
diff --git a/learning/k8s-intermediate/config/taints-toleration/index.md b/learning/k8s-intermediate/config/taints-toleration/index.md
index da7810f..dba686f 100644
--- a/learning/k8s-intermediate/config/taints-toleration/index.md
+++ b/learning/k8s-intermediate/config/taints-toleration/index.md
@@ -10,6 +10,8 @@ meta:
 
 # 概述
 
+<AdSenseTitle/>
+
 > 参考文档： Kubernetes 官网文档 [Taints and Tolerations](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/)
 
 Pod 中存在属性 [Node selector / Node affinity](/learning/k8s-intermediate/config/assign-pod-node.html)，用于将 Pod 指定到合适的节点。
diff --git a/learning/k8s-intermediate/config/taints-toleration/taint-based-evictions.md b/learning/k8s-intermediate/config/taints-toleration/taint-based-evictions.md
index fffb6e4..377ff00 100644
--- a/learning/k8s-intermediate/config/taints-toleration/taint-based-evictions.md
+++ b/learning/k8s-intermediate/config/taints-toleration/taint-based-evictions.md
@@ -10,6 +10,8 @@ meta:
 
 # 基于污点的驱逐（TaintBasedEviction）
 
+<AdSenseTitle/>
+
 在前面的章节中，我们描述了 [NoExecute](/learning/k8s-intermediate/config/taints-toleration/#污点与容忍的匹配) 的污点效果，该效果将对已经运行在节点上的 Pod 施加如下影响：
 * 不容忍该污点的 Pod 将立刻被驱逐
 * 容忍该污点的 Pod 在未指定 `tolerationSeconds` 的情况下，将继续在该节点上运行
diff --git a/learning/k8s-intermediate/config/taints-toleration/taint-nodes-by-condition.md b/learning/k8s-intermediate/config/taints-toleration/taint-nodes-by-condition.md
index bcd9d0a..28e7518 100644
--- a/learning/k8s-intermediate/config/taints-toleration/taint-nodes-by-condition.md
+++ b/learning/k8s-intermediate/config/taints-toleration/taint-nodes-by-condition.md
@@ -10,6 +10,8 @@ meta:
 
 # 条件化的污点（TaintNodesByCondition）
 
+<AdSenseTitle/>
+
 自 Kubernetes 1.12 开始，`TaintNodesByCondition` 这个特性进入 beta 阶段，此时节点控制器自动根据 Node Condition 为节点创建对应的污点。调度器则不去检查 Node conditions，而是检查节点的污点，因此 Node Condition 不再直接影响到调度程序。用户通过为 Pod 添加容忍，可以选择性地忽略节点的某些问题（以 Node Condition 呈现的问题）。
 
 `TaintNodesByCondition` 这个特性只会为节点添加 `NoSchedule` 效果的污点。`TaintBasedEviction` （Kubernetes 1.13 开始默认生效）则为节点添加 `NoExecute` 效果的污点，参考 [TaintBasedEviction](./taint-based-evictions.html)。
diff --git a/learning/k8s-intermediate/config/taints-toleration/use-case.md b/learning/k8s-intermediate/config/taints-toleration/use-case.md
index e3bf8b8..73a92e9 100644
--- a/learning/k8s-intermediate/config/taints-toleration/use-case.md
+++ b/learning/k8s-intermediate/config/taints-toleration/use-case.md
@@ -10,6 +10,8 @@ meta:
 
 # 使用案例
 
+<AdSenseTitle/>
+
 污点和容忍使用起来非常灵活，可以用于：
 * 避免 Pod 被调度到某些特定的节点
 * 从节点上驱逐本不应该在该节点运行的 Pod
diff --git a/learning/k8s-intermediate/container/env.md b/learning/k8s-intermediate/container/env.md
index f0c40a0..7d68593 100644
--- a/learning/k8s-intermediate/container/env.md
+++ b/learning/k8s-intermediate/container/env.md
@@ -9,6 +9,8 @@ meta:
 
 # 容器的环境变量
 
+<AdSenseTitle/>
+
 > 参考文档： [Container Environment Variables](https://kubernetes.io/docs/concepts/containers/container-environment-variables/)
 
 Kubernetes为容器提供了一系列重要的资源：
diff --git a/learning/k8s-intermediate/container/images.md b/learning/k8s-intermediate/container/images.md
index d897867..ddad655 100644
--- a/learning/k8s-intermediate/container/images.md
+++ b/learning/k8s-intermediate/container/images.md
@@ -9,6 +9,8 @@ meta:
 
 # 容器镜像
 
+<AdSenseTitle/>
+
 在 Kubernetes 的 Pod 中使用容器镜像之前，您必须将其推送到一个镜像仓库（或者使用仓库中已经有的容器镜像）。在 Kubernetes 的 Pod 定义中定义容器时，必须指定容器所使用的镜像，容器中的 `image` 字段支持与 `docker` 命令一样的语法，包括私有镜像仓库和标签。
 
 例如：`my-registry.example.com:5000/example/web-example:v1.0.1` 由如下几个部分组成：
diff --git a/learning/k8s-intermediate/container/lifecycle-p.md b/learning/k8s-intermediate/container/lifecycle-p.md
index cc059fc..987464b 100644
--- a/learning/k8s-intermediate/container/lifecycle-p.md
+++ b/learning/k8s-intermediate/container/lifecycle-p.md
@@ -9,6 +9,8 @@ meta:
 
 # 容器生命周期事件处理
 
+<AdSenseTitle/>
+
 > 参考文档： [Attach Handlers to Container Lifecycle Events](https://kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/)
 
 Kubernetes 中支持容器的 postStart 和 preStop 事件，本文阐述了如何向容器添加生命周期事件处理程序（handler）。
diff --git a/learning/k8s-intermediate/container/lifecycle.md b/learning/k8s-intermediate/container/lifecycle.md
index e508bc9..8c46f4b 100644
--- a/learning/k8s-intermediate/container/lifecycle.md
+++ b/learning/k8s-intermediate/container/lifecycle.md
@@ -9,6 +9,8 @@ meta:
 
 # 容器生命周期
 
+<AdSenseTitle/>
+
 > 参考文档： [Container Lifecycle Hooks](https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/)
 
 本文描述了 kubelet 管理的容器如何使用容器生命周期钩子执行指定的代码。
diff --git a/learning/k8s-intermediate/container/runtime.md b/learning/k8s-intermediate/container/runtime.md
index eb207aa..8debb6d 100644
--- a/learning/k8s-intermediate/container/runtime.md
+++ b/learning/k8s-intermediate/container/runtime.md
@@ -9,6 +9,8 @@ meta:
 
 # Runtime Class
 
+<AdSenseTitle/>
+
 > 参考文档： [Runtime Class](https://kubernetes.io/docs/concepts/containers/runtime-class/)
 
 特性状态：Kubernetes v1.14 <Badge type="warning">beta</Badge>
diff --git a/learning/k8s-intermediate/persistent/nfs.md b/learning/k8s-intermediate/persistent/nfs.md
index c1686d2..983452d 100644
--- a/learning/k8s-intermediate/persistent/nfs.md
+++ b/learning/k8s-intermediate/persistent/nfs.md
@@ -9,6 +9,8 @@ meta:
 
 # 搭建NFS Server
 
+<AdSenseTitle/>
+
 ## 背景
 
 Kubernetes 对 Pod 进行调度时，以当时集群中各节点的可用资源作为主要依据，自动选择某一个可用的节点，并将 Pod 分配到该节点上。在这种情况下，Pod 中容器数据的持久化如果存储在所在节点的磁盘上，就会产生不可预知的问题，例如，当 Pod 出现故障，Kubernetes 重新调度之后，Pod 所在的新节点上，并不存在上一次 Pod 运行时所在节点上的数据。
diff --git a/learning/k8s-intermediate/persistent/pv.md b/learning/k8s-intermediate/persistent/pv.md
index df9ce9e..d50fdd6 100644
--- a/learning/k8s-intermediate/persistent/pv.md
+++ b/learning/k8s-intermediate/persistent/pv.md
@@ -9,6 +9,8 @@ meta:
 
 # 存储卷PersistentVolume
 
+<AdSenseTitle/>
+
 参考文档： Kubernetes 官方文档 [Persistent Volumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/)
 
 ## 概述
diff --git a/learning/k8s-intermediate/persistent/selection.md b/learning/k8s-intermediate/persistent/selection.md
index 46532c9..e987aa3 100644
--- a/learning/k8s-intermediate/persistent/selection.md
+++ b/learning/k8s-intermediate/persistent/selection.md
@@ -8,6 +8,7 @@ meta:
 
 # 数据卷类型如何选择
 
+<AdSenseTitle/>
 
 # 存储卷类型如何选择
 
diff --git a/learning/k8s-intermediate/persistent/storage-class.md b/learning/k8s-intermediate/persistent/storage-class.md
index 5021d4b..a7d1998 100644
--- a/learning/k8s-intermediate/persistent/storage-class.md
+++ b/learning/k8s-intermediate/persistent/storage-class.md
@@ -9,6 +9,8 @@ meta:
 
 # 存储类StorageClass
 
+<AdSenseTitle/>
+
 参考文档： Kubernetes 官网 [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/)
 
 ## 存储类概述
diff --git a/learning/k8s-intermediate/persistent/volume-mount-point.md b/learning/k8s-intermediate/persistent/volume-mount-point.md
index d58c530..bf6f280 100644
--- a/learning/k8s-intermediate/persistent/volume-mount-point.md
+++ b/learning/k8s-intermediate/persistent/volume-mount-point.md
@@ -8,6 +8,8 @@ meta:
 
 # 数据卷-挂载
 
+<AdSenseTitle/>
+
 参考文档： Kubernetes 官网文档 [Volumes](https://kubernetes.io/docs/concepts/storage/volumes/)
 
 ## 容器内路径
diff --git a/learning/k8s-intermediate/persistent/volume.md b/learning/k8s-intermediate/persistent/volume.md
index f585d48..21cf3b1 100644
--- a/learning/k8s-intermediate/persistent/volume.md
+++ b/learning/k8s-intermediate/persistent/volume.md
@@ -9,6 +9,8 @@ meta:
 
 # 数据卷Volume
 
+<AdSenseTitle/>
+
 参考文档： Kubernetes 官网文档 [Volumes](https://kubernetes.io/docs/concepts/storage/volumes/)
 
 ## 数据卷概述
diff --git a/learning/k8s-intermediate/private-registry.md b/learning/k8s-intermediate/private-registry.md
index c457190..16b884e 100644
--- a/learning/k8s-intermediate/private-registry.md
+++ b/learning/k8s-intermediate/private-registry.md
@@ -9,6 +9,8 @@ meta:
 
 # 使用私有仓库中的docker镜像
 
+<AdSenseTitle/>
+
 企业通常会因为如下几个原因，需要搭建自己的私有 docker registry：
 * 限制 docker 镜像的分发范围，例如：只允许在内网分发，或者只允许被授权的用户获取 docker 镜像
 * 提高推送 docker 镜像以及抓取 docker 镜像时的网络传输速度
diff --git a/learning/k8s-intermediate/service/cni.md b/learning/k8s-intermediate/service/cni.md
index 661678e..57ca34f 100644
--- a/learning/k8s-intermediate/service/cni.md
+++ b/learning/k8s-intermediate/service/cni.md
@@ -9,6 +9,8 @@ meta:
 
 # 如何选择网络插件
 
+<AdSenseTitle/>
+
 本文转载自： [kubernetes网络插件对比分析（flannel、calico、weave）](https://www.toutiao.com/a6708893686517727748/)
 
 原文作者：残花花败柳柳
diff --git a/learning/k8s-intermediate/service/connecting.md b/learning/k8s-intermediate/service/connecting.md
index f70494f..b552bca 100644
--- a/learning/k8s-intermediate/service/connecting.md
+++ b/learning/k8s-intermediate/service/connecting.md
@@ -9,6 +9,8 @@ meta:
 
 # Service连接应用程序
 
+<AdSenseTitle/>
+
 参考文档： Kubernetes 官网文档 [Connecting Applications with Services](https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/)
 
 ## Kubernetes 的网络模型
diff --git a/learning/k8s-intermediate/service/dns.md b/learning/k8s-intermediate/service/dns.md
index cc092b8..ee57d45 100644
--- a/learning/k8s-intermediate/service/dns.md
+++ b/learning/k8s-intermediate/service/dns.md
@@ -9,6 +9,8 @@ meta:
 
 # Service/Pod的DNS
 
+<AdSenseTitle/>
+
 参考文档： Kubernetes 官网文档 [DNS for Services and Pods](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/)
 
 本文介绍了 Kubernetes 中的 DNS 分配方式
diff --git a/learning/k8s-intermediate/service/ingress.md b/learning/k8s-intermediate/service/ingress.md
index 2c13233..19a2bed 100644
--- a/learning/k8s-intermediate/service/ingress.md
+++ b/learning/k8s-intermediate/service/ingress.md
@@ -9,6 +9,8 @@ meta:
 
 # Ingress通过互联网访问您的应用
 
+<AdSenseTitle/>
+
 参考文档：
 * Kubernetes 官网 [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/)
 * Kubernetes 官网 [Ingress Controllers](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/)
diff --git a/learning/k8s-intermediate/service/service-details.md b/learning/k8s-intermediate/service/service-details.md
index 7033ffd..ef02ece 100644
--- a/learning/k8s-intermediate/service/service-details.md
+++ b/learning/k8s-intermediate/service/service-details.md
@@ -9,6 +9,8 @@ meta:
 
 # Service详细描述
 
+<AdSenseTitle/>
+
 参考文档：Kubernetes 官网文档：[Service](https://kubernetes.io/docs/concepts/services-networking/service/)
 
 ## 创建 Service
diff --git a/learning/k8s-intermediate/service/service-types.md b/learning/k8s-intermediate/service/service-types.md
index e098e8e..3978606 100644
--- a/learning/k8s-intermediate/service/service-types.md
+++ b/learning/k8s-intermediate/service/service-types.md
@@ -9,6 +9,8 @@ meta:
 
 # 发布Service
 
+<AdSenseTitle/>
+
 Kubernetes Service 支持的不同访问方式。
 
 ## Service 类型
diff --git a/learning/k8s-intermediate/service/service.md b/learning/k8s-intermediate/service/service.md
index e144cd0..bad4383 100644
--- a/learning/k8s-intermediate/service/service.md
+++ b/learning/k8s-intermediate/service/service.md
@@ -9,6 +9,8 @@ meta:
 
 # Service概述
 
+<AdSenseTitle/>
+
 参考文档：Kubernetes 官网文档：[Service](https://kubernetes.io/docs/concepts/services-networking/service/)
 
 ## 为何需要 Service
diff --git a/learning/k8s-intermediate/workload/init-container.md b/learning/k8s-intermediate/workload/init-container.md
index 64e0f66..1e8cc1a 100644
--- a/learning/k8s-intermediate/workload/init-container.md
+++ b/learning/k8s-intermediate/workload/init-container.md
@@ -11,6 +11,8 @@ meta:
 
 参考文档： Kubernetes 官网 [Init Containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/)
 
+<AdSenseTitle/>
+
 ## 初始化容器介绍
 
 Pod 可以包含多个工作容器，也可以包含一个或多个初始化容器，初始化容器在工作容器启动之前执行。
diff --git a/learning/k8s-intermediate/workload/pod-kuboard.md b/learning/k8s-intermediate/workload/pod-kuboard.md
index 252e6fa..c57195f 100644
--- a/learning/k8s-intermediate/workload/pod-kuboard.md
+++ b/learning/k8s-intermediate/workload/pod-kuboard.md
@@ -7,6 +7,8 @@ meta:
 
 # 容器组_Kuboard
 
+<AdSenseTitle/>
+
 ## 通过 Kuboard 创建容器组
 
 由于在 Kubernetes 中，任何时候都是不推荐用户直接创建容器组，而是应该通过控制器创建容器组，Kuboard 管理工具并不提供直接创建容器组的界面，而是通过 **工作负载编辑器** 创建 Deployment、StatefulSet、DaemonSet 等方式来创建容器组。
diff --git a/learning/k8s-intermediate/workload/pod-lifecycle.md b/learning/k8s-intermediate/workload/pod-lifecycle.md
index 9595196..77246a0 100644
--- a/learning/k8s-intermediate/workload/pod-lifecycle.md
+++ b/learning/k8s-intermediate/workload/pod-lifecycle.md
@@ -11,6 +11,8 @@ meta:
 
 参考文档： Kubernetes 官网文档 [Pod Lifecycle](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/)
 
+<AdSenseTitle/>
+
 [[TOC]]
 
 ## Pod phase
diff --git a/learning/k8s-intermediate/workload/pod-privileged.md b/learning/k8s-intermediate/workload/pod-privileged.md
index 0879f0d..a78eb6c 100644
--- a/learning/k8s-intermediate/workload/pod-privileged.md
+++ b/learning/k8s-intermediate/workload/pod-privileged.md
@@ -7,6 +7,7 @@ meta:
 
 # 容器组_Privileged 模式
 
+<AdSenseTitle/>
 
 ## Privilged 模式运行容器
 
diff --git a/learning/k8s-intermediate/workload/pod.md b/learning/k8s-intermediate/workload/pod.md
index d9ce49c..4890534 100644
--- a/learning/k8s-intermediate/workload/pod.md
+++ b/learning/k8s-intermediate/workload/pod.md
@@ -11,6 +11,8 @@ meta:
 
 参考文档：Kubernetes 官方文档 [Pod Overview](https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/) [Pods](https://kubernetes.io/docs/concepts/workloads/pods/pod/)
 
+<AdSenseTitle/>
+
 术语中英文对照：
 
 | 英文全称  | 英文缩写  | 中文翻译 |
diff --git a/learning/k8s-intermediate/workload/wl-daemonset/alternative.md b/learning/k8s-intermediate/workload/wl-daemonset/alternative.md
index 2040211..d846e42 100644
--- a/learning/k8s-intermediate/workload/wl-daemonset/alternative.md
+++ b/learning/k8s-intermediate/workload/wl-daemonset/alternative.md
@@ -11,6 +11,8 @@ meta:
 
 > 参考文档： Kubernetes 官网文档 [Alternatives to DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#alternatives-to-daemonset)
 
+<AdSenseTitle/>
+
 DaemonSet 有如下替代选项可以选择
 
 ## Init Scripts
diff --git a/learning/k8s-intermediate/workload/wl-daemonset/communicate.md b/learning/k8s-intermediate/workload/wl-daemonset/communicate.md
index 51798dc..0f732d5 100644
--- a/learning/k8s-intermediate/workload/wl-daemonset/communicate.md
+++ b/learning/k8s-intermediate/workload/wl-daemonset/communicate.md
@@ -11,6 +11,8 @@ meta:
 
 > 参考文档 Kubernetes 官网文档 [Communicating with Daemon Pods](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#communicating-with-daemon-pods)
 
+<AdSenseTitle/>
+
 与 DaemonSet 容器组通信的模式有：
 
 * **Push：** DaemonSet 容器组用来向另一个服务推送信息，例如数据库的统计信息。这种情况下 DaemonSet 容器组没有客户端
diff --git a/learning/k8s-intermediate/workload/wl-daemonset/create.md b/learning/k8s-intermediate/workload/wl-daemonset/create.md
index bc58c86..28a42d3 100644
--- a/learning/k8s-intermediate/workload/wl-daemonset/create.md
+++ b/learning/k8s-intermediate/workload/wl-daemonset/create.md
@@ -9,6 +9,8 @@ meta:
 
 # 创建 DaemonSet
 
+<AdSenseTitle/>
+
 ## YAML 示例
 
 下面是 DaemonSet 的 YAML 文件示例 daemonset.yaml。该例子中的 DaemonSet 运行了一个 fluentd-elasticsearch 的 docker 镜像：
diff --git a/learning/k8s-intermediate/workload/wl-daemonset/index.md b/learning/k8s-intermediate/workload/wl-daemonset/index.md
index f60fab3..0b6a682 100644
--- a/learning/k8s-intermediate/workload/wl-daemonset/index.md
+++ b/learning/k8s-intermediate/workload/wl-daemonset/index.md
@@ -11,6 +11,7 @@ meta:
 
 > 参考文档： Kubernetes 官网文档 [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/)
 
+<AdSenseTitle/>
 
 DaemonSet 控制器确保所有（或一部分）的节点都运行了一个指定的 Pod 副本。
 * 每当向集群中添加一个节点时，指定的 Pod 副本也将添加到该节点上
diff --git a/learning/k8s-intermediate/workload/wl-daemonset/schedule.md b/learning/k8s-intermediate/workload/wl-daemonset/schedule.md
index c559918..bfa3f67 100644
--- a/learning/k8s-intermediate/workload/wl-daemonset/schedule.md
+++ b/learning/k8s-intermediate/workload/wl-daemonset/schedule.md
@@ -11,6 +11,8 @@ meta:
 
 > 参考文档 Kubernetes 官网文档 [How Daemon Pods are Scheduled](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#how-daemon-pods-are-scheduled)
 
+<AdSenseTitle/>
+
 ## 由 DaemonSet 控制器调度
 
 **v1.12以后默认禁用**
diff --git a/learning/k8s-intermediate/workload/wl-daemonset/update.md b/learning/k8s-intermediate/workload/wl-daemonset/update.md
index 50374c0..6e6b17e 100644
--- a/learning/k8s-intermediate/workload/wl-daemonset/update.md
+++ b/learning/k8s-intermediate/workload/wl-daemonset/update.md
@@ -11,6 +11,8 @@ meta:
 
 > 参考文档 Kubernetes 官网文档 [Updating a DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#updating-a-daemonset)
 
+<AdSenseTitle/>
+
 ## 更新信息
 
 * 在改变节点的标签时：
diff --git a/learning/k8s-intermediate/workload/wl-deployment/canary.md b/learning/k8s-intermediate/workload/wl-deployment/canary.md
index a6cf21b..d12de2b 100644
--- a/learning/k8s-intermediate/workload/wl-deployment/canary.md
+++ b/learning/k8s-intermediate/workload/wl-deployment/canary.md
@@ -9,6 +9,8 @@ meta:
 
 # 金丝雀发布
 
+<AdSenseTitle/>
+
 [返回 Deployment](./#deployment-概述)
 
 <el-tabs type="border-card">
diff --git a/learning/k8s-intermediate/workload/wl-deployment/cleanup.md b/learning/k8s-intermediate/workload/wl-deployment/cleanup.md
index 8445a2a..cb34922 100644
--- a/learning/k8s-intermediate/workload/wl-deployment/cleanup.md
+++ b/learning/k8s-intermediate/workload/wl-deployment/cleanup.md
@@ -9,6 +9,8 @@ meta:
 
 # 清理策略
 
+<AdSenseTitle/>
+
 [返回 Deployment](./#deployment-概述)
 
 通过 Deployment 中 `.spec.revisionHistoryLimit` 字段，可指定为该 Deployment 保留多少个旧的 ReplicaSet。超出该数字的将被在后台进行垃圾回收。该字段的默认值是 10。
diff --git a/learning/k8s-intermediate/workload/wl-deployment/create.md b/learning/k8s-intermediate/workload/wl-deployment/create.md
index 9e089be..0fe20f0 100644
--- a/learning/k8s-intermediate/workload/wl-deployment/create.md
+++ b/learning/k8s-intermediate/workload/wl-deployment/create.md
@@ -9,6 +9,8 @@ meta:
 
 # 创建 Deployment
 
+<AdSenseTitle/>
+
 [返回 Deployment](./#deployment-概述)
 
 本文描述了如何创建一个 Deployment，如何理解 Deployment 各个字段，以及如何查看 Deployment 的创建结果。
diff --git a/learning/k8s-intermediate/workload/wl-deployment/index.md b/learning/k8s-intermediate/workload/wl-deployment/index.md
index c3ab9ee..5143ed3 100644
--- a/learning/k8s-intermediate/workload/wl-deployment/index.md
+++ b/learning/k8s-intermediate/workload/wl-deployment/index.md
@@ -11,6 +11,8 @@ meta:
 
 参考文档： Kubernetes 官网 [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/)、 [ReplicaSet](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/)
 
+<AdSenseTitle/>
+
 术语表
 
 | 英文       | 英文简称   | 中文   |
diff --git a/learning/k8s-intermediate/workload/wl-deployment/pause.md b/learning/k8s-intermediate/workload/wl-deployment/pause.md
index 546dd9c..b0b7fd1 100644
--- a/learning/k8s-intermediate/workload/wl-deployment/pause.md
+++ b/learning/k8s-intermediate/workload/wl-deployment/pause.md
@@ -9,6 +9,8 @@ meta:
 
 # 暂停和继续 Deployment
 
+<AdSenseTitle/>
+
 [返回 Deployment](./#deployment-概述)
 
 您可以先暂停 Deployment，然后再触发一个或多个更新，最后再继续（resume）该 Deployment。这种做法使得您可以在暂停和继续中间对 Deployment 做多次更新，而无需触发不必要的滚动更新。
diff --git a/learning/k8s-intermediate/workload/wl-deployment/rollback.md b/learning/k8s-intermediate/workload/wl-deployment/rollback.md
index 236ae13..a25cab1 100644
--- a/learning/k8s-intermediate/workload/wl-deployment/rollback.md
+++ b/learning/k8s-intermediate/workload/wl-deployment/rollback.md
@@ -9,6 +9,8 @@ meta:
 
 # 回滚 Deployment
 
+<AdSenseTitle/>
+
 [返回 Deployment](./#deployment-概述)
 
 某些情况下，您可能想要回滚（rollback）Deployment，例如：Deployment 不稳定（可能是不断地崩溃）。默认情况下，kubernetes 将保存 Deployment 的所有更新（rollout）历史。您可以设定 revision history limit 来确定保存的历史版本数量。
diff --git a/learning/k8s-intermediate/workload/wl-deployment/scale.md b/learning/k8s-intermediate/workload/wl-deployment/scale.md
index 5c2f1b8..5c6a804 100644
--- a/learning/k8s-intermediate/workload/wl-deployment/scale.md
+++ b/learning/k8s-intermediate/workload/wl-deployment/scale.md
@@ -9,6 +9,8 @@ meta:
 
 # 伸缩 Deployment
 
+<AdSenseTitle/>
+
 [返回 Deployment](./#deployment-概述)
 
 伸缩（Scaling） Deployment，是指改变 Deployment 中 Pod 的副本数量，以应对实际业务流量的变化。
diff --git a/learning/k8s-intermediate/workload/wl-deployment/status.md b/learning/k8s-intermediate/workload/wl-deployment/status.md
index c66ba36..50d4364 100644
--- a/learning/k8s-intermediate/workload/wl-deployment/status.md
+++ b/learning/k8s-intermediate/workload/wl-deployment/status.md
@@ -9,6 +9,8 @@ meta:
 
 # 查看 Deployment 的状态
 
+<AdSenseTitle/>
+
 [返回 Deployment](./#deployment-概述)
 
 Deployment 的生命周期中，将会进入不同的状态，这些状态可能是：
diff --git a/learning/k8s-intermediate/workload/wl-deployment/update.md b/learning/k8s-intermediate/workload/wl-deployment/update.md
index 749e315..90e17fa 100644
--- a/learning/k8s-intermediate/workload/wl-deployment/update.md
+++ b/learning/k8s-intermediate/workload/wl-deployment/update.md
@@ -9,6 +9,8 @@ meta:
 
 # 更新 Deployment
 
+<AdSenseTitle/>
+
 [返回 Deployment](./#deployment-概述)
 
 ## 执行更新
diff --git a/learning/k8s-intermediate/workload/wl-statefulset/basics.md b/learning/k8s-intermediate/workload/wl-statefulset/basics.md
index b6d1efa..7576c6e 100644
--- a/learning/k8s-intermediate/workload/wl-statefulset/basics.md
+++ b/learning/k8s-intermediate/workload/wl-statefulset/basics.md
@@ -9,6 +9,8 @@ meta:
 
 # StatefulSet 的基本信息
 
+<AdSenseTitle/>
+
 [返回 StatefulSet](./)
 
 ## 创建 StatefulSet
diff --git a/learning/k8s-intermediate/workload/wl-statefulset/index.md b/learning/k8s-intermediate/workload/wl-statefulset/index.md
index f904f44..5ce665d 100644
--- a/learning/k8s-intermediate/workload/wl-statefulset/index.md
+++ b/learning/k8s-intermediate/workload/wl-statefulset/index.md
@@ -11,6 +11,8 @@ meta:
 
 > 参考文档： Kubernetes 官网文档 [StatefulSets](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/)
 
+<AdSenseTitle/>
+
 ## StatefulSet 概述
 
 StatefulSet 顾名思义，用于管理 Stateful（有状态）的应用程序。
diff --git a/learning/k8s-intermediate/workload/wl-statefulset/scaling.md b/learning/k8s-intermediate/workload/wl-statefulset/scaling.md
index 4a82627..c7bdbe7 100644
--- a/learning/k8s-intermediate/workload/wl-statefulset/scaling.md
+++ b/learning/k8s-intermediate/workload/wl-statefulset/scaling.md
@@ -9,6 +9,8 @@ meta:
 
 # StatefulSet 的部署和伸缩
 
+<AdSenseTitle/>
+
 [返回 StatefulSet](./)
 
 ## 部署和伸缩 StatefulSet 时的执行顺序
diff --git a/learning/k8s-intermediate/workload/wl-statefulset/update.md b/learning/k8s-intermediate/workload/wl-statefulset/update.md
index 774595d..327bda0 100644
--- a/learning/k8s-intermediate/workload/wl-statefulset/update.md
+++ b/learning/k8s-intermediate/workload/wl-statefulset/update.md
@@ -9,6 +9,8 @@ meta:
 
 # StatefulSet 的更新策略
 
+<AdSenseTitle/>
+
 [返回 StatefulSet](./)
 
 ## StatefulSet 的更新策略 <Badge text="Kuboard 暂不支持" type="warn"/>
diff --git a/learning/k8s-intermediate/workload/workload.md b/learning/k8s-intermediate/workload/workload.md
index bf8388a..3f22be0 100644
--- a/learning/k8s-intermediate/workload/workload.md
+++ b/learning/k8s-intermediate/workload/workload.md
@@ -9,6 +9,8 @@ meta:
 
 # 控制器_概述
 
+<AdSenseTitle/>
+
 ## 概述
 
 Pod（容器组）是 Kubernetes 中最小的调度单元，您可以通过 kubectl 直接创建一个 Pod。Pod 本身并不能自愈（self-healing）。如果一个 Pod 所在的 Node （节点）出现故障，或者调度程序自身出现故障，Pod 将被删除；同理，当因为节点资源不够或节点维护而驱逐 Pod 时，Pod 也将被删除。
diff --git a/learning/k8s-practice/micro-service/kuboard-view-of-k8s.md b/learning/k8s-practice/micro-service/kuboard-view-of-k8s.md
index 928b033..270b57a 100644
--- a/learning/k8s-practice/micro-service/kuboard-view-of-k8s.md
+++ b/learning/k8s-practice/micro-service/kuboard-view-of-k8s.md
@@ -9,6 +9,8 @@ meta:
 
 # 从微服务视角看Kubernetes
 
+<AdSenseTitle/>
+
 ## 微服务
 
 当我们谈论微服务的时候，总避免不了说 Spring Cloud / Dubbo，这些微服务架构的采用，确实达到了我们对他的期许：分布式、熔断/限流、高可用、可扩展、分离关注、链路追踪、小团队快速迭代。
diff --git a/learning/k8s-practice/ocp/api-gateway.md b/learning/k8s-practice/ocp/api-gateway.md
index 82e8172..c1d16dc 100644
--- a/learning/k8s-practice/ocp/api-gateway.md
+++ b/learning/k8s-practice/ocp/api-gateway.md
@@ -9,6 +9,8 @@ meta:
 
 # 在K8S上部署api-gateway
 
+<AdSenseTitle/>
+
 本文假设您已经完成了 [在Kubernetes 上部署 Spring Cloud - OCP](./) 系列教程的前面部分，并已经完成了 eureka-server、api-gateway-mysql、log-center-mysql、redis、auth-server、user-center 在 K8S 上的部署。
 
 ## 理解api-gateway
diff --git a/learning/k8s-practice/ocp/auth-server.md b/learning/k8s-practice/ocp/auth-server.md
index a2c05f0..2e48598 100644
--- a/learning/k8s-practice/ocp/auth-server.md
+++ b/learning/k8s-practice/ocp/auth-server.md
@@ -9,6 +9,8 @@ meta:
 
 # 在K8S上部署auth-server
 
+<AdSenseTitle/>
+
 本文假设您已经完成了 [在Kubernetes 上部署 Spring Cloud - OCP](./) 系列教程的前面部分，并已经完成了 eureka-server、auth-center-mysql、redis 在 K8S 上的部署。
 
 ## 理解auth-server
diff --git a/learning/k8s-practice/ocp/back-center.md b/learning/k8s-practice/ocp/back-center.md
index 6404c60..6dcc50d 100644
--- a/learning/k8s-practice/ocp/back-center.md
+++ b/learning/k8s-practice/ocp/back-center.md
@@ -9,6 +9,8 @@ meta:
 
 # 在K8S上部署back-center
 
+<AdSenseTitle/>
+
 本文假设您已经完成了 [在Kubernetes 上部署 Spring Cloud - OCP](./) 系列教程的前面部分，并已经完成了 eureka-server、user-center-mysql、log-center-mysql、redis、auth-server、user-center 在 K8S 上的部署。
 
 ## 理解back-center
diff --git a/learning/k8s-practice/ocp/build.md b/learning/k8s-practice/ocp/build.md
index ddd6fbf..3cb24af 100644
--- a/learning/k8s-practice/ocp/build.md
+++ b/learning/k8s-practice/ocp/build.md
@@ -9,6 +9,8 @@ meta:
 
 # 构建docker镜像并推送到仓库
 
+<AdSenseTitle/>
+
 本文假设您已经完成了 [准备OCP的构建环境和部署环境](./prepare.html)，在该文档的最后，我们将 Open Capacity Platform 的代码仓库克隆到了 master 节点的 /root/open-capacity-platform。
 
 ::: tip
diff --git a/learning/k8s-practice/ocp/eureka-server.md b/learning/k8s-practice/ocp/eureka-server.md
index 5dd8b0b..da4b3d2 100644
--- a/learning/k8s-practice/ocp/eureka-server.md
+++ b/learning/k8s-practice/ocp/eureka-server.md
@@ -9,6 +9,8 @@ meta:
 
 # 在K8S上部署eureka-server
 
+<AdSenseTitle/>
+
 本文假设您已经完成了 [在Kubernetes上部署SpringCloud-OCP](/learning/k8s-practice/ocp/) 教程的前序步骤：
 * [准备OCP的构建环境和部署环境](/learning/k8s-practice/ocp/prepare.html)
 
diff --git a/learning/k8s-practice/ocp/export.md b/learning/k8s-practice/ocp/export.md
index 31690cc..f8df0d3 100644
--- a/learning/k8s-practice/ocp/export.md
+++ b/learning/k8s-practice/ocp/export.md
@@ -10,6 +10,8 @@ meta:
 
 # 导出部署配置
 
+<AdSenseTitle/>
+
 通过本系列文章前面的部分，我们终于完整了 Spring Cloud OCP 的核心组件在 Kubernetes 上的部署。此时，Kuboard 的名称空间 `ocp` 界面的截图如下所示：
 
 ![Kubernetes教程_部署SpringCloud_OCP_导出部署配置_配置内容](./export.assets/image-20191001123231022.png)
diff --git a/learning/k8s-practice/ocp/import.md b/learning/k8s-practice/ocp/import.md
index 67bca73..125d558 100644
--- a/learning/k8s-practice/ocp/import.md
+++ b/learning/k8s-practice/ocp/import.md
@@ -10,6 +10,8 @@ meta:
 
 # 导入部署配置
 
+<AdSenseTitle/>
+
 <script>
 
 export default {
diff --git a/learning/k8s-practice/ocp/index.md b/learning/k8s-practice/ocp/index.md
index 865d6f3..79f28fa 100644
--- a/learning/k8s-practice/ocp/index.md
+++ b/learning/k8s-practice/ocp/index.md
@@ -9,6 +9,7 @@ meta:
 
 # 在Kubernetes上部署SpringCloud
 
+<AdSenseTitle/>
 
 ## 使用 Kuboard 在 K8S 上部署 OCP
 
diff --git a/learning/k8s-practice/ocp/mysql.md b/learning/k8s-practice/ocp/mysql.md
index dd24eb5..0f3b295 100644
--- a/learning/k8s-practice/ocp/mysql.md
+++ b/learning/k8s-practice/ocp/mysql.md
@@ -10,6 +10,8 @@ meta:
 
 # 在K8S上部署mysql
 
+<AdSenseTitle/>
+
 OCP 的 auth-server 和 user-center 都有自己的数据库，同时 auth-server、user-center 和 api-gateway 又都依赖于 redis 缓存服务 和 log-center 数据库。这使得我们的部署结构演变成下图所示：
 
 我们必须先完成 db-auth-center、db-user-center、db-log-center 和 redis 的部署，才能继续部署 auth-server 和 user-center。本文描述了如何部署 db-auth-center、db-user-center、db-log-center。
diff --git a/learning/k8s-practice/ocp/prepare.md b/learning/k8s-practice/ocp/prepare.md
index 91afa58..3a9dc0c 100644
--- a/learning/k8s-practice/ocp/prepare.md
+++ b/learning/k8s-practice/ocp/prepare.md
@@ -9,6 +9,8 @@ meta:
 
 # 准备OCP的构建环境和部署环境
 
+<AdSenseTitle/>
+
 ## 环境要求
 
 Open Capacity Platform 是基于 Java Spring Cloud 的微服务架构，为了将其部署到 Kubernetes 上，我们需要准备如下环境：
diff --git a/learning/k8s-practice/ocp/redis.md b/learning/k8s-practice/ocp/redis.md
index f7bac81..1417e8b 100644
--- a/learning/k8s-practice/ocp/redis.md
+++ b/learning/k8s-practice/ocp/redis.md
@@ -10,6 +10,8 @@ meta:
 
 # 在K8S上部署redis
 
+<AdSenseTitle/>
+
 如 [在K8S上部署mysql](./mysql.html) 所述，auth-server、user-center、api-gateway 都需要使用 redis 服务，本文描述如何使用 Kuboard 在 Kubernetes 上部署 redis。
 
 本文将使用 [redis官方镜像](https://hub.docker.com/_/redis) 进行部署。
diff --git a/learning/k8s-practice/ocp/review.md b/learning/k8s-practice/ocp/review.md
index 12771e3..fc7ae43 100644
--- a/learning/k8s-practice/ocp/review.md
+++ b/learning/k8s-practice/ocp/review.md
@@ -10,6 +10,8 @@ meta:
 
 # 重新审视配置信息
 
+<AdSenseTitle/>
+
 在本系列文章的前面部分，我们已经完成了在 Kubernetes 上部署 Spring Cloud OCP 的主要组件：eureka-server、auth-server、user-cetner、api-gateway、back-center。
 
 ## 提取相同的参数
diff --git a/learning/k8s-practice/ocp/sequence.md b/learning/k8s-practice/ocp/sequence.md
index 9c1ecd2..cc32e3e 100644
--- a/learning/k8s-practice/ocp/sequence.md
+++ b/learning/k8s-practice/ocp/sequence.md
@@ -9,6 +9,8 @@ meta:
 
 # 部署顺序
 
+<AdSenseTitle/>
+
 ## 部署顺序的确定
 
 本教程将在 KUbernet是上部署 Spring Cloud - Open Capacity Platform 微服务架构的如下模块：
diff --git a/learning/k8s-practice/ocp/user-center.md b/learning/k8s-practice/ocp/user-center.md
index 0a51c65..ac21b6a 100644
--- a/learning/k8s-practice/ocp/user-center.md
+++ b/learning/k8s-practice/ocp/user-center.md
@@ -9,6 +9,8 @@ meta:
 
 # 在K8S上部署user-center
 
+<AdSenseTitle/>
+
 本文假设您已经完成了 [在Kubernetes 上部署 Spring Cloud - OCP](./) 系列教程的前面部分，并已经完成了 eureka-server、user-center-mysql、log-center-mysql、redis 在 K8S 上的部署。
 
 ## 理解user-center
diff --git a/learning/k8s-practice/spring-cloud/README.md b/learning/k8s-practice/spring-cloud/README.md
index a14d998..2179757 100644
--- a/learning/k8s-practice/spring-cloud/README.md
+++ b/learning/k8s-practice/spring-cloud/README.md
@@ -9,6 +9,8 @@ meta:
 
 # Spring Cloud on Kubernetes
 
+<AdSenseTitle/>
+
 下图是作者在落地 Spring Cloud 微架构的过程中，设计了如下图所示的微服务参考架构，设计和研发 Kuboard 的初心便源于此图。历时两年时间，Kuboard终于发布，也标志着该参考架构的成熟可用。该参考架构主要包括四个重要组成部分：
 
 * 微服务运行时
diff --git a/learning/k8s-practice/spring-cloud/cloud-eureka.md b/learning/k8s-practice/spring-cloud/cloud-eureka.md
index 2f28808..c2f92d8 100644
--- a/learning/k8s-practice/spring-cloud/cloud-eureka.md
+++ b/learning/k8s-practice/spring-cloud/cloud-eureka.md
@@ -4,6 +4,8 @@ description: Kubernetes教程_使用Kuboard在Kubernetes上部署spring_cloud服
 
 # 部署cloud-eureka
 
+<AdSenseTitle/>
+
 本文所使用的代码请参考 [cloud-eureka](https://github.com/eip-work/kuboard-example/tree/master/cloud-eureka)
 
 ## 检查 cloud-eureka 项目的配置
diff --git a/learning/k8s-practice/spring-cloud/db-example.md b/learning/k8s-practice/spring-cloud/db-example.md
index bd9b3f4..7e0f8f9 100644
--- a/learning/k8s-practice/spring-cloud/db-example.md
+++ b/learning/k8s-practice/spring-cloud/db-example.md
@@ -4,6 +4,8 @@ description: 在Kubernetes上部署测试数据库mysql的详细介绍。
 
 # 部署db-example
 
+<AdSenseTitle/>
+
 本文所使用的代码请参考 [db-example](https://github.com/eip-work/kuboard-example/tree/master/db-example)
 
 ## 检查 db-example 项目的配置
diff --git a/overview/README.md b/overview/README.md
index fcd3b09..de27725 100644
--- a/overview/README.md
+++ b/overview/README.md
@@ -8,6 +8,8 @@ meta:
 
 # Kuboard简介
 
+<AdSenseTitle/>
+
 <div style="background-color: #0063dc;">
 <div style="max-width: 363px; margin: auto;">
   <img src="/images/logo-main.png" style="background-color: #0063dc; max-width: 100%; vertical-align: bottom;" alt="Kubernetes管理界面：Kuboard Logo"/>
diff --git a/overview/change-log.md b/overview/change-log.md
index 1940912..ab0ae4d 100644
--- a/overview/change-log.md
+++ b/overview/change-log.md
@@ -4,6 +4,8 @@ description: Kuboard更新日志的详细信息
 
 # 更新日志
 
+<AdSenseTitle/>
+
 ::: danger 页面已迁移
 本页面已迁移到 [Kuboard 更新日志](/support/change-log/v1.0.x.html)
 :::
diff --git a/overview/concepts.md b/overview/concepts.md
index e7cbeed..9fef228 100644
--- a/overview/concepts.md
+++ b/overview/concepts.md
@@ -8,6 +8,8 @@ meta:
 
 # 如何降低Kubernetes学习门槛
 
+<AdSenseTitle/>
+
 ## Kubernetes 学习门槛在哪儿
 
 学习 Kubernetes 之前，必须具备的知识储备：
diff --git a/overview/k8s-core-concepts.md b/overview/k8s-core-concepts.md
index b8c0ddc..cb7af38 100644
--- a/overview/k8s-core-concepts.md
+++ b/overview/k8s-core-concepts.md
@@ -4,6 +4,8 @@ description: Kubernetes教程_以gif动图的形式形象的描述Kubernetes核
 
 # 十分钟带你理解Kubernetes核心概念
 
+<AdSenseTitle/>
+
 > 转载信息：
 >
 > 译者：崔婧雯
diff --git a/overview/kuboard-vs-kubectl.md b/overview/kuboard-vs-kubectl.md
index a80407b..b224eaa 100644
--- a/overview/kuboard-vs-kubectl.md
+++ b/overview/kuboard-vs-kubectl.md
@@ -4,6 +4,8 @@ description: Kubernetes教程_为什么要使用kuboard_而不是直接使用kub
 
 # 为什么要使用Kuboard_而不是直接用kubectl
 
+<AdSenseTitle/>
+
 ## Kuboard v.s. kubectl
 
 Kuboard 有如下优势：
diff --git a/overview/quick-win.md b/overview/quick-win.md
index 1b9af37..f056a68 100644
--- a/overview/quick-win.md
+++ b/overview/quick-win.md
@@ -5,6 +5,8 @@ description: Kuboard提供Kubernetes图形化管理界面_Kubernetes最新版本
 
 # 在Kubernetes上快速落地微服务
 
+<AdSenseTitle/>
+
 ## Kubernetes 落地难
 
 **Kubernetes 是趋势**
diff --git a/overview/share-coder.md b/overview/share-coder.md
index f187fc1..3182c0a 100644
--- a/overview/share-coder.md
+++ b/overview/share-coder.md
@@ -1,6 +1,6 @@
 # Kuboard介绍
 
-
+<AdSenseTitle/>
 
 Kubernetes 容器编排已越来越被大家关注，然而学习 Kubernetes 的门槛却依然很高，主要体现在这几个方面：
 
diff --git a/overview/support.md b/overview/support.md
index c7ceb64..da647fc 100644
--- a/overview/support.md
+++ b/overview/support.md
@@ -4,6 +4,7 @@ description: Kubernetes教程_如何获得Kuboard相关的支持和帮助？
 
 # 支持
 
+<AdSenseTitle/>
 
 ## 提交 BUG
 
diff --git a/overview/why-kuboard.md b/overview/why-kuboard.md
index 41432fb..2edd387 100644
--- a/overview/why-kuboard.md
+++ b/overview/why-kuboard.md
@@ -8,6 +8,8 @@ meta:
 
 # 为什么选择Kuboard
 
+<AdSenseTitle/>
+
 Kubernetes 已然是当下容器编排领域事实上的标准，各大云服务商都急于推出 Kubernetes 服务，互联网公司也纷纷跟进，将自己的应用容器化，并使用 Kubernetes 编排。
 
 在 Kubernetes 图形化工具方面，我们已经获得了极大的可选择空间：
diff --git a/support/change-log/change-log-on-the-way.md b/support/change-log/change-log-on-the-way.md
index bd7c99a..87e96c7 100644
--- a/support/change-log/change-log-on-the-way.md
+++ b/support/change-log/change-log-on-the-way.md
@@ -11,12 +11,19 @@ Kuboard v1.0.x 的更新说明
 * kubernetes 1.16.1
 * HostAliases
 
+* 容器组列表，筛选结果为空时，提示筛选 “其他”
+* 存储类列表为空时，提示当前无内容，请创建
+
 * https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
 
+* https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/ha-topology/  专题：ETCD 集群是如何setup起来的
+
 * Service --> SessionAffinity
               --> clientIP.timeoutSeconds
 * Service --> .spec.clusterIP
 
+* PV 中支持 hostPath
+
 * 创建工作负载时，不追加前缀
 * 存储卷声明去掉分配模式的字段
 * 删除容器组时 - graceful period
diff --git a/support/change-log/v1.0.x.md b/support/change-log/v1.0.x.md
index d0774d4..b5ad19f 100644
--- a/support/change-log/v1.0.x.md
+++ b/support/change-log/v1.0.x.md
@@ -5,6 +5,8 @@ description: 本文描述了Kuboard_v1.0.x的版本变更说明
 
 # Kuboardv1.0.x
 
+<AdSenseTitle/>
+
 Kuboard v1.0.x 的更新说明
 
 ## v1.0.4-beta.2
diff --git a/support/index.md b/support/index.md
index fca4194..6dc69f3 100644
--- a/support/index.md
+++ b/support/index.md
@@ -5,11 +5,7 @@ description: Kubernetes教程_本文描述了如何获得Kuboard授权
 
 # Kuboard
 
-<div style="background-color: #0063dc;">
-  <div style="max-width: 363px; margin: auto;">
-    <img src="/images/logo-main.png" style="background-color: #0063dc; max-width: 100%;" alt="Kubernetes管理界面：Kuboard Logo"/>
-  </div>
-</div>
+<AdSenseTitle/>
 
 ## Kuboard 授权声明