diff --git a/index.html b/index.html index 5b276104f0bd223bb321348bb01f3384de9a9a71..1d379a236bea8e3c78450b59fe9ff30f5f923c8b 100644 --- a/index.html +++ b/index.html @@ -1853,18 +1853,15 @@ RU5ErkJggg==" /> - - + + - - - - - + + @@ -1875,6 +1872,9 @@ RU5ErkJggg==" /> + + + diff --git a/wechat/articles/2019/07/2019-07-29-leveraging-jenkins-on-kubernetes/index.html b/wechat/articles/2019/07/2019-07-29-leveraging-jenkins-on-kubernetes/index.html index e10bf2f1752396a2266cc0989610cec09d044e22..77dded95a7228496c795fe6efe4b62f49425fe16 100644 --- a/wechat/articles/2019/07/2019-07-29-leveraging-jenkins-on-kubernetes/index.html +++ b/wechat/articles/2019/07/2019-07-29-leveraging-jenkins-on-kubernetes/index.html @@ -389,10 +389,10 @@ var trackOutboundLink = function(id, url) {
集群集成进来之后,我们可以直接从 web 页面安装 helm(Kubernetes 包管理工具)。
- + - +现在我们可以通过命令行检查一下 tiller
守护进程(helm 的服务器端组件)是否运行。