

zhangguanzhang's Blog

手动修复v1.14-v1.15版本k8s的issue:76956

zhangguanzhang's Blog

手动修复v1.14-v1.15版本k8s的issue:76956

k8s golang

字数统计: 2.7k阅读时长: 15 min

 2019/10/21   Share

• 
• 
• 
• 
• 

由来

该issue见 https://github.com/kubernetes/kubernetes/issues/76956, apiserver和controller-manager每次start的时候会刷下面信息。不影响使用，但是有强迫症可以按照本文思路手动修改。当然本文也是自己编译k8s的教程

E0423 17:35:58.491576       1 prometheus.go:138] failed to register depth metric admission_quota_controller: duplicate metrics collector registration attempted
E0423 17:35:58.491625       1 prometheus.go:150] failed to register adds metric admission_quota_controller: duplicate metrics collector registration attempted
E0423 17:35:58.491901       1 prometheus.go:162] failed to register latency metric admission_quota_controller: duplicate metrics collector registration attempted
E0423 17:35:58.492191       1 prometheus.go:174] failed to register work_duration metric admission_quota_controller: duplicate metrics collector registration attempted
E0423 17:35:58.492367       1 prometheus.go:189] failed to register unfinished_work_seconds metric admission_quota_controller: duplicate metrics collector registration attempted
E0423 17:35:58.492507       1 prometheus.go:202] failed to register longest_running_processor_microseconds metric admission_quota_controller: duplicate metrics collector registration attempted

      从这个issue我们可以找到对应的修复pr https://github.com/kubernetes/kubernetes/pull/77553, 我们看到是metrics信息被注册了两次的错误输出。
      但是该pr只被merge到了v1.16以上 https://github.com/kubernetes/kubernetes/commit/f101466d2e4d96854c80f58203de2cc6b5aaeb6a#diff-60187c78fbca5a995fd7d2ac913eb6c8, 意味着1.14，1.15都存在这个。

master (#77553)  v1.17.0-alpha.2  v1.17.0-alpha.1 v1.17.0-alpha.0 v1.16.3-beta.0 v1.16.2 v1.16.2-beta.0 v1.16.1 v1.16.1-beta.0 v1.16.0 v1.16.0-rc.2 v1.16.0-rc.1 v1.16.0-beta.2 v1.16.0-beta.1 v1.16.0-beta.0 v1.16.0-alpha.3 v1.16.0-alpha.2

实战

下载源码

手动下载源码编译，这里我使用v1.15.5来做示范。我们使用容器编译，这里我使用4c8g的centos7.6+docker-ce-18.09。想办法把源码拉下来

git clone https://github.com/kubernetes/kubernetes -b v1.15.5
cd kubernetes
git checkout -b v1.15.5

编译前准备

因为我们拉取后修改了源码，编译出的version信息会是下面带-dirty

$ kube-controller-manager --version
Kubernetes v1.15.5-dirty

可以执行下面命令去掉-dirty,或者自己git add后commit也行

sed -ri 's#KUBE_GIT_TREE_STATE="dirty"#KUBE_GIT_TREE_STATE="clean"#g' hack/lib/version.sh

另外如果有需求也编译docker镜像的话可以先提前准备本地镜像，修改build/lib/release.sh，命令sed -ri 's#(build)\s+--pull#\1#' build/lib/release.sh

"${DOCKER[@]}" build --pull -q -t "${docker_image_tag}" "${docker_build_path}" >/dev/null
修改为下面
"${DOCKER[@]}" build -q -t "${docker_image_tag}" "${docker_build_path}" >/dev/null

因为我们使用docker镜像起容器编译，需要提前准备镜像，查看下版本，各个版本k8s的golang版本是不一样的，不要乱写

$ cat build/build-image/cross/VERSION
v1.12.10-1

拉取该镜像

curl -s https://zhangguanzhang.github.io/bash/pull.sh | bash -s k8s.gcr.io/kube-cross:v1.12.10-1

把merge打patch

merge的url为 https://github.com/kubernetes/kubernetes/commit/f101466d2e4d96854c80f58203de2cc6b5aaeb6a#diff-60187c78fbca5a995fd7d2ac913eb6c8
把url中#以及后面的改为.patch执行下面命令打patch

[root@k8s-m1 kubernetes]# wget https://github.com/kubernetes/kubernetes/commit/f101466d2e4d96854c80f58203de2cc6b5aaeb6a.patch
[root@k8s-m1 kubernetes]# patch -p1  < f101466d2e4d96854c80f58203de2cc6b5aaeb6a.patch 
patching file pkg/util/workqueue/prometheus/prometheus.go
patching file pkg/util/workqueue/prometheus/prometheus_test.go
patching file pkg/util/workqueue/prometheus/BUILD
patching file pkg/util/workqueue/prometheus/prometheus.go
patching file pkg/util/workqueue/prometheus/prometheus_test.go
patching file staging/src/k8s.io/client-go/util/workqueue/delaying_queue.go
Hunk #1 succeeded at 44 (offset 1 line).
Hunk #2 succeeded at 76 (offset 3 lines).
Hunk #3 succeeded at 152 (offset 6 lines).
patching file staging/src/k8s.io/client-go/util/workqueue/metrics.go
patching file staging/src/k8s.io/client-go/util/workqueue/metrics_test.go
patching file staging/src/k8s.io/client-go/util/workqueue/rate_limiting_queue_test.go

编译

为了和官方尽量保持一致，这里使用docker容器编译，先说下几个环境变量:
KUBE_BUILD_CONFORMANCE=n 和 KUBE_BUILD_HYPERKUBE=n 参数决定是否构建 hyperkube-amd64 和 conformance-amd64 镜像，默认是 y 构建，这里设置为n表示不构建
配置尽量两个cpu以上而不是1个cpu多核心，不然编译很容易高负载被系统kill了

[root@k8s-m1 kubernetes]# KUBE_BUILD_PLATFORMS=linux/amd64 KUBE_BUILD_CONFORMANCE=n KUBE_BUILD_HYPERKUBE=n make quick-release
+++ [1021 21:30:50] Verifying Prerequisites....
+++ [1021 21:30:51] Building Docker image kube-build:build-7db96ab759-5-v1.12.10-1
+++ [1021 21:30:54] Syncing sources to container
+++ [1021 21:30:58] Running build command...
+++ [1021 21:31:43] Building go targets for linux/amd64:
    cmd/kube-proxy
    cmd/kube-apiserver
    cmd/kube-controller-manager
    cmd/cloud-controller-manager
    cmd/kubelet
    cmd/kubeadm
    cmd/hyperkube
    cmd/kube-scheduler
    vendor/k8s.io/apiextensions-apiserver
    cluster/gce/gci/mounter
+++ [1021 21:34:05] Building go targets for linux/amd64:
    cmd/kube-proxy
    cmd/kubeadm
    cmd/kubelet
+++ [1021 21:34:49] Building go targets for linux/amd64:
    cmd/kubectl
+++ [1021 21:35:11] Building go targets for linux/amd64:
    cmd/gendocs
    cmd/genkubedocs
    cmd/genman
    cmd/genyaml
    cmd/genswaggertypedocs
    cmd/linkcheck
    vendor/github.com/onsi/ginkgo/ginkgo
    test/e2e/e2e.test
+++ [1021 21:37:01] Building go targets for linux/amd64:
    cmd/kubemark
    vendor/github.com/onsi/ginkgo/ginkgo
    test/e2e_node/e2e_node.test
+++ [1021 21:38:03] Syncing out of container
+++ [1021 21:38:33] Building tarball: manifests
+++ [1021 21:38:33] Building tarball: src
+++ [1021 21:38:33] Starting tarball: client linux-amd64
+++ [1021 21:38:33] Waiting on tarballs
+++ [1021 21:38:49] Building images: linux-amd64
+++ [1021 21:38:49] Building tarball: node linux-amd64
+++ [1021 21:38:49] Starting docker build for image: cloud-controller-manager-amd64
+++ [1021 21:38:49] Starting docker build for image: kube-apiserver-amd64
+++ [1021 21:38:49] Starting docker build for image: kube-controller-manager-amd64
+++ [1021 21:38:49] Starting docker build for image: kube-scheduler-amd64
+++ [1021 21:38:49] Starting docker build for image: kube-proxy-amd64
+++ [1021 21:38:49] Building conformance image for arch: amd64
+++ [1021 21:38:49] Building hyperkube image for arch: amd64
Sending build context to Docker daemon  52.65MB
Step 1/2 : FROM k8s.gcr.io/debian-base-amd64:v1.0.0
Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
!!! [1021 21:39:07] Call tree:
!!! [1021 21:39:07]  1: /root/kubernetes/build/lib/release.sh:231 kube::release::create_docker_images_for_server(...)
!!! [1021 21:39:07]  2: /root/kubernetes/build/lib/release.sh:237 kube::release::build_server_images(...)
!!! [1021 21:39:07]  3: /root/kubernetes/build/lib/release.sh:93 kube::release::package_server_tarballs(...)
!!! [1021 21:39:07]  4: build/release.sh:45 kube::release::package_tarballs(...)
Sending build context to Docker daemon  50.07MB
Step 1/2 : FROM k8s.gcr.io/debian-iptables-amd64:v11.0.2
Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
!!! [1021 21:39:08] Call tree:
!!! [1021 21:39:08]  1: /root/kubernetes/build/lib/release.sh:231 kube::release::create_docker_images_for_server(...)
!!! [1021 21:39:08]  2: /root/kubernetes/build/lib/release.sh:237 kube::release::build_server_images(...)
!!! [1021 21:39:08]  3: /root/kubernetes/build/lib/release.sh:93 kube::release::package_server_tarballs(...)
!!! [1021 21:39:08]  4: build/release.sh:45 kube::release::package_tarballs(...)
Sending build context to Docker daemon    156MB
Step 1/2 : FROM k8s.gcr.io/debian-base-amd64:v1.0.0
Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
!!! [1021 21:39:12] Call tree:
!!! [1021 21:39:12]  1: /root/kubernetes/build/lib/release.sh:231 kube::release::create_docker_images_for_server(...)
!!! [1021 21:39:12]  2: /root/kubernetes/build/lib/release.sh:237 kube::release::build_server_images(...)
!!! [1021 21:39:12]  3: /root/kubernetes/build/lib/release.sh:93 kube::release::package_server_tarballs(...)
!!! [1021 21:39:12]  4: build/release.sh:45 kube::release::package_tarballs(...)
Sending build context to Docker daemon  134.3MB
Step 1/2 : FROM k8s.gcr.io/debian-base-amd64:v1.0.0
Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
!!! [1021 21:39:13] Call tree:
!!! [1021 21:39:13]  1: /root/kubernetes/build/lib/release.sh:231 kube::release::create_docker_images_for_server(...)
!!! [1021 21:39:13]  2: /root/kubernetes/build/lib/release.sh:237 kube::release::build_server_images(...)
!!! [1021 21:39:13]  3: /root/kubernetes/build/lib/release.sh:93 kube::release::package_server_tarballs(...)
!!! [1021 21:39:13]  4: build/release.sh:45 kube::release::package_tarballs(...)
Sending build context to Docker daemon  205.2MB
Step 1/2 : FROM k8s.gcr.io/debian-base-amd64:v1.0.0
Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
!!! [1021 21:39:13] Call tree:
!!! [1021 21:39:13]  1: /root/kubernetes/build/lib/release.sh:231 kube::release::create_docker_images_for_server(...)
!!! [1021 21:39:13]  2: /root/kubernetes/build/lib/release.sh:237 kube::release::build_server_images(...)
!!! [1021 21:39:13]  3: /root/kubernetes/build/lib/release.sh:93 kube::release::package_server_tarballs(...)
!!! [1021 21:39:13]  4: build/release.sh:45 kube::release::package_tarballs(...)
Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
make[1]: *** [build] Error 1
!!! [1021 21:39:14] Call tree:
!!! [1021 21:39:14]  1: /root/kubernetes/build/lib/release.sh:420 kube::release::build_hyperkube_image(...)
!!! [1021 21:39:14]  2: /root/kubernetes/build/lib/release.sh:231 kube::release::create_docker_images_for_server(...)
!!! [1021 21:39:14]  3: /root/kubernetes/build/lib/release.sh:237 kube::release::build_server_images(...)
!!! [1021 21:39:14]  4: /root/kubernetes/build/lib/release.sh:93 kube::release::package_server_tarballs(...)
!!! [1021 21:39:14]  5: build/release.sh:45 kube::release::package_tarballs(...)
Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
make[1]: *** [build] Error 1
!!! [1021 21:39:14] Call tree:
!!! [1021 21:39:14]  1: /root/kubernetes/build/lib/release.sh:424 kube::release::build_conformance_image(...)
!!! [1021 21:39:14]  2: /root/kubernetes/build/lib/release.sh:231 kube::release::create_docker_images_for_server(...)
!!! [1021 21:39:14]  3: /root/kubernetes/build/lib/release.sh:237 kube::release::build_server_images(...)
!!! [1021 21:39:14]  4: /root/kubernetes/build/lib/release.sh:93 kube::release::package_server_tarballs(...)
!!! [1021 21:39:14]  5: build/release.sh:45 kube::release::package_tarballs(...)
!!! [1021 21:39:14] previous Docker build failed
!!! [1021 21:39:14] Call tree:
!!! [1021 21:39:14]  1: /root/kubernetes/build/lib/release.sh:231 kube::release::create_docker_images_for_server(...)
!!! [1021 21:39:14]  2: /root/kubernetes/build/lib/release.sh:237 kube::release::build_server_images(...)
!!! [1021 21:39:14]  3: /root/kubernetes/build/lib/release.sh:93 kube::release::package_server_tarballs(...)
!!! [1021 21:39:14]  4: build/release.sh:45 kube::release::package_tarballs(...)
!!! [1021 21:39:14] previous tarball phase failed
make: *** [quick-release] Error 1

查看结果

构建出错，不用管，出错是要构建k8s的docker镜像，二进制已经被构建出来的，我们可以查看_output/release-stage目录

[root@k8s-m1 kubernetes]# ll _output/release-stage/server/linux-amd64/kubernetes/server/bin/
total 828572
-rwxr-xr-x 2 root root 134324933 Oct 21 21:38 cloud-controller-manager
drwxr-xr-x 2 root root      4096 Oct 21 21:38 cloud-controller-manager.dockerbuild
-rwxr-xr-x 1 root root 250209280 Oct 21 21:38 hyperkube
-rwxr-xr-x 2 root root 205195189 Oct 21 21:38 kube-apiserver
drwxr-xr-x 2 root root      4096 Oct 21 21:38 kube-apiserver.dockerbuild
-rwxr-xr-x 2 root root 155984780 Oct 21 21:38 kube-controller-manager
drwxr-xr-x 2 root root      4096 Oct 21 21:38 kube-controller-manager.dockerbuild
-rwxr-xr-x 2 root root  50064955 Oct 21 21:38 kube-proxy
drwxr-xr-x 2 root root      4096 Oct 21 21:38 kube-proxy.dockerbuild
-rwxr-xr-x 2 root root  52643510 Oct 21 21:38 kube-scheduler
drwxr-xr-x 2 root root      4096 Oct 21 21:38 kube-scheduler.dockerbuild

替换后查看输出信息

cp _output/release-stage/server/linux-amd64/kubernetes/server/bin/kube-controller-manager /usr/local/bin/
cp: overwrite ‘/usr/local/bin/kube-controller-manager’? y
[root@k8s-m1 kubernetes]# systemctl status kube-controller-manager.service 
● kube-controller-manager.service - Kubernetes Controller Manager
   Loaded: loaded (/usr/lib/systemd/system/kube-controller-manager.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Mon 2019-10-21 20:47:21 CST; 55min ago
     Docs: https://github.com/kubernetes/kubernetes
  Process: 114302 ExecStart=/usr/local/bin/kube-controller-manager --allocate-node-cidrs=true --authentication-kubeconfig=/etc/kubernetes/controller-manager.kubeconfig --authorization-kubeconfig=/etc/kubernetes/controller-manager.kubeconfig --bind-address=0.0.0.0 --client-ca-file=/etc/kubernetes/pki/ca.crt --cluster-signing-cert-file=/etc/kubernetes/pki/ca.crt --cluster-signing-key-file=/etc/kubernetes/pki/ca.key --kubeconfig=/etc/kubernetes/controller-manager.kubeconfig --leader-elect=true --cluster-cidr=10.244.0.0/16 --service-cluster-ip-range=10.96.0.0/12 --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt --service-account-private-key-file=/etc/kubernetes/pki/sa.key --root-ca-file=/etc/kubernetes/pki/ca.crt --use-service-account-credentials=true --controllers=*,bootstrapsigner,tokencleaner --experimental-cluster-signing-duration=86700h --feature-gates=RotateKubeletClientCertificate=true --node-monitor-period=5s --node-monitor-grace-period=2m --pod-eviction-timeout=1m --logtostderr=false --log-dir=/var/log/kubernetes/kube-controller-manager --v=2 (code=killed, signal=TERM)
 Main PID: 114302 (code=killed, signal=TERM)

Oct 21 20:45:10 k8s-m1 systemd[1]: Started Kubernetes Controller Manager.
Oct 21 20:47:21 k8s-m1 systemd[1]: Stopping Kubernetes Controller Manager...
Oct 21 20:47:21 k8s-m1 systemd[1]: Stopped Kubernetes Controller Manager.
[root@k8s-m1 kubernetes]# systemctl start kube-controller-manager.service 
[root@k8s-m1 kubernetes]# systemctl status kube-controller-manager.service 
● kube-controller-manager.service - Kubernetes Controller Manager
   Loaded: loaded (/usr/lib/systemd/system/kube-controller-manager.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2019-10-21 21:43:25 CST; 1s ago
     Docs: https://github.com/kubernetes/kubernetes
 Main PID: 11996 (kube-controller)
    Tasks: 8
   Memory: 12.2M
   CGroup: /system.slice/kube-controller-manager.service
           └─11996 /usr/local/bin/kube-controller-manager --allocate-node-cidrs=true --authentication-kubeconfig=/etc/kubernetes/controller-manager.kubeconfig --authorization-kubeconfig=/etc/kubernetes/controller-manager.kubeconfig -...

Oct 21 21:43:25 k8s-m1 systemd[1]: Started Kubernetes Controller Manager.

已经没有相关错误了

参考

https://www.kubernetes.org.cn/5033.html
https://www.twblogs.net/a/5c76b632bd9eee33991811bf

原文作者：Zhangguanzhang

原文链接：http://zhangguanzhang.github.io/2019/10/21/k8s-v1.14-v1.15-fix-issue/

发表日期：十月 21日 2019, 9:36:53 晚上

更新日期：December 27th 2019, 10:44:43 am

版权声明：本文采用知识共享署名-非商业性使用 4.0 国际许可协议进行许可

• Next Post
  consul仅当服务发现在k8s无状态部署使用
• Previous Post
  /boot目录被清空下物理机无法开机的一次救援

Powered by Hexotheme Archer

PV: :)

CATALOG

1. 1. 由来
2. 2. 实战
   1. 2.1. 下载源码
   2. 2.2. 编译前准备
   3. 2.3. 把merge打patch
   4. 2.4. 编译
   5. 2.5. 查看结果
      1. 2.5.1. 替换后查看输出信息
3. 3. 参考



• Archive
• Tag
• Cate

Total : 78

2020

• 03/26一次deploy,rs,sts Mismatch 的处理
• 03/02centos6中毒重启后卡在启动页面
• 03/02记录一次request_module: runaway loop modeprobe binfmt-0000
• 02/27使用microsoft-graph的api对接onedrive
• 01/08docker-18.06.3-ce启动panic: invalid page type: 0: 0的解决处理

2019

• 12/05opensuse的一次救援
• 12/03从PTTYPE="dos"到TYPE="LVM2_member"的救援
• 11/24应大多数人要求写下kubeadm的基础使用
• 10/24consul仅当服务发现在k8s无状态部署使用
• 10/21手动修复v1.14-v1.15版本k8s的issue:76956
• 10/12/boot目录被清空下物理机无法开机的一次救援
• 10/11ansible数量限制上的幂等性
• 09/27高可用的SSL consul cluster实践
• 09/05修改源码更改prometheus的时区问题
• 08/24gobot控制esp8266
• 08/06ubuntu preseed无人应答安装
• 07/14golang headless browser包chromedp初探
• 07/08为什么我不用nodePort之偶然中奖几率
• 07/07golang的net/http包的客户端简单科普
• 06/26uefi模式下docker+交换机部署pxe批量安装
• 06/23拟定excel表格服务器自动按照表格配置信息和安装的实现过程
• 06/12SMASH CLP的一些笔记
• 06/02golang cobra的一些笔记
• 04/28闲谈线上俩k8s环境同等limits下pod启动时间不一样解决过程
• 03/22一次kube-controller-manager的bug导致的线上无法调度处理过程
• 03/15不走etcd v2 api下二进制跑flannel的总结
• 03/11k8s高可用涉及到ip填写的相关配置和一些坑
• 03/03二进制部署Kubernetes v1.13.12 HA可选
• 02/19docker部署jira(8.0.0)和confluence(6.14.1)
• 02/12通用的dashboard部署和tls，SSL相关部署
• 01/30fstab与systemd.mount自动挂载的一点研究和见解
• 01/22proxmox里使用cloud-init和一些笔记

2018

• 12/04prometheus的黑盒监控
• 11/24对于初入k8s和kubeadm的一些建议
• 11/06一次docker镜像的解耦--onlyoffice
• 11/05记录一次十字符病毒清理过程
• 10/12全手动部署prometheus-operator监控K8S集群以及一些坑
• 10/06IngressController使用和它的高可用落地
• 09/24跨VPC或者跨云供应商搭建K8S集群正确姿势
• 09/18二进制部署Kubernetes v1.11.x(1.12.x) HA可选
• 08/03Kubernetes v1.11.x HA全手动苦工安装教学
• 07/18基于openstack的ecs上使用VIP
• 07/08利用travis同步gcr.io镜像到dockerhub
• 06/25记录一次线上k8s节点故障
• 06/03kubernetes's Job总结和实战以及坑
• 06/02kubernetes的PodAffinity的不解
• 05/05[转载+修正]Kubernetes v1.10.x HA全手动苦工安装教学
• 04/29kubernetes的configMap文件挂载不同的路径且不覆盖目录的解决方法
• 02/05docker无法删除掉镜像的解决方法
• 01/20慎用docker的--rm选项!!!
• 01/10docker的一些概念

2017

• 12/24docker容器访问宿主机
• 12/23docker容器网络互联
• 06/26lua列出所有upsteam
• 06/03bash自定义补全
• 05/25shell脚本的选项和参数处理
• 05/12ssh互信
• 05/06shell利用快捷键提升命令输入和编辑
• 04/29个人zabbix安装和坑的解决
• 04/26正则零宽断言的一个注意点
• 04/25[转载]awk中RS,ORS,FS,OFS区别于联系
• 04/20记录LVM和raid的练习
• 04/17分享下自己做的外网控制硬件
• 04/15shell多进程并发执行
• 04/15shell的字符串截取
• 04/118266模块的烧写和sdk的坑
• 04/09安卓安装linux并且源码编译安装搭建lnmp的坑和总结
• 04/03centos配置bond
• 03/20vsftpd虚拟用户简单部署
• 03/15源码编译安装lnmp
• 02/26Altium Designer里走线开窗和挖除铺铜还有一些技巧
• 02/12微信公众号接入自己服务器
• 02/02lamp环境搭建总结
• 01/08微信公众号接入图灵机器人api

2016

• 11/13cad
• 10/30记录下自己制作的led-vu
• 10/29原生js左右分散对齐文字
• 10/28hello world

ipmi CLP diy k8s Mismatch 8266 总结 ingress Altium Designer ansible consul initrd grub raid Linux kernel prometheus exporter lnmp 安卓 cad centos6 boot golang chromedp cobra Dockerfile docker etcd keepavlied flannel cifs gobot esp8266 ftp hello world mqtt 原创 http kube-controller-manager jira confluence java springboot kubeadm ConfigMap PodAffinity nginx lamp microsoft graph onedrive nodeport operator preseed openstack cloud-init timezone js 左右分散对齐文字 shell bash dockerhub gcr.io linux ssh suse tftp 正则 微信 api awk zabbix



缺失模块。
1、请确保node版本大于6.2
2、在博客根目录（注意不是archer根目录）执行以下命令：
npm i hexo-generator-json-content --save
3、在根目录_config.yml里添加配置：

jsonContent:
  meta: false
  pages: false
  posts:
    title: true
    date: true
    path: true
    text: false
    raw: false
    content: false
    slug: false
    updated: false
    comments: false
    link: false
    permalink: false
    excerpt: false
    categories: true
    tags: true

ipmi 日志 kubernetes 日志/心得 日志/闲搞 ansible kubernetes/kubelet pxe Linux prometheus 日志/Auto-cad boot golang consul ansible/心得 docker kubernetes/docker 日志/容器 容器 pxe/raid Linux/boot Linux/centos6 boot/grub kubernetes/docker/panic pxe/raid/kickstart Linux/centos6/boot openstack fstab gobot vsftp 日志/闲聊 golang/http kubernetes/kube-controller-manager kubernetes/kubeadm kubernetes/k8s kubernetes/Job lua microsoft kubernetes/prometheus preseed proxmox microsoft/graph prometheus/golang 日志/总结 CI boot/grub/suse microsoft/graph/onedrive pxe/docker 日志/技巧 日志/LVM CI/travis 日志/运维 pxe/docker/kickstart 日志/LVM/raid

