基于Kargo 快速部署多master 的 kubernetes 集群
1、初始化环境
1.1、环境：
| 节点 | IP | 角色 |
|---|
| node-1 | 10.6.0.52 | Master |
| node-2 | 10.6.0.53 | Master |
| node-3 | 10.6.0.55 | Node |
| node-4 | 10.6.0.56 | Node |
1.2、配置SSH Key 登陆
1
2
3
4
5
6
7
8
9
10
11
12
| # 确保本机也可以 ssh 连接，否则下面部署失败
ssh-keygen -t rsa -N ""
ssh-copy-id -i /root/.ssh/id_rsa.pub 10.6.0.52
ssh-copy-id -i /root/.ssh/id_rsa.pub 10.6.0.53
ssh-copy-id -i /root/.ssh/id_rsa.pub 10.6.0.55
ssh-copy-id -i /root/.ssh/id_rsa.pub 10.6.0.56
|
2、获取 Kargo
Kargo 官方github
https://github.com/kubernetes-incubator/kargo
2.1、安装基础软件
Kargo 是基于 ansible 统一部署，所以必须安装 ansible
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
| # 安装 centos 额外的yum源
yum install -y epel-release
# 安装 软件
yum install -y python-pip python34 python-netaddr python34-pip ansible
# 升级 Jinja2 否则报错 no test named 'equalto'
pip install --upgrade Jinja2
# k8s 1.5.4镜像, 可提前下载，安装docker 以后导入
# 百度网盘地址
http://pan.baidu.com/s/1jH5105S
# karogo 2.2.0 k8s 1.5.5镜像
http://pan.baidu.com/s/1pKCdOoV
|
2.2、获取源码
1
| git clone https://github.com/kubernetes-incubator/kargo
|
2.3、编辑配置文件
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
| cd kargo
vim inventory/group_vars/k8s-cluster.yml
# 配置文件如下:
# 其中{ { 与 } } 实际为 "{+{ }+}" 因为博客 jellky 的原因 他会解析"{+{ }+}" 并自动去掉，所以我在里面加了空格。
# 请自行使用 sed 替换
# 启动集群的基础系统
bootstrap_os: centos
# etcd 数据存放位置
etcd_data_dir: /var/lib/etcd
# 二进制文件将要安装的位置
bin_dir: /usr/local/bin
# kubernetes 配置文件存放目录以及命名空间
kube_config_dir: /etc/kubernetes
kube_script_dir: "{ { bin_dir } }/kubernetes-scripts"
kube_manifest_dir: "{ { kube_config_dir } }/manifests"
system_namespace: kube-system
# 日志存放位置
kube_log_dir: "/var/log/kubernetes"
# kubernetes 证书存放位置
kube_cert_dir: "{ { kube_config_dir } }/ssl"
# token存放位置
kube_token_dir: "{ { kube_config_dir } }/tokens"
# basic auth 认证文件存放位置
kube_users_dir: "{ { kube_config_dir } }/users"
# 关闭匿名授权
kube_api_anonymous_auth: false
## 使用的 kubernetes 版本
kube_version: v1.5.4
# 安装过程中缓存文件下载位置(最少 1G)
local_release_dir: "/tmp/releases"
# 重试次数，比如下载失败等情况
retry_stagger: 5
# 证书组
kube_cert_group: kube-cert
# 集群日志等级
kube_log_level: 2
# HTTP 下 api server 密码及用户
kube_api_pwd: "test123"
kube_users:
kube:
pass: "{ { kube_api_pwd } }"
role: admin
root:
pass: "{ { kube_api_pwd } }"
role: admin
# 网络 CNI 组件 (calico, weave or flannel)
kube_network_plugin: calico
# 服务地址分配
kube_service_addresses: 10.233.0.0/18
# pod 地址分配
kube_pods_subnet: 10.233.64.0/18
# 网络节点大小分配
kube_network_node_prefix: 24
# api server 监听地址及端口
kube_apiserver_ip: "{ { kube_service_addresses|ipaddr('net')|ipaddr(1)|ipaddr('address') } }"
kube_apiserver_port: 6443 # (https)
kube_apiserver_insecure_port: 8080 # (http)
# 默认 dns 后缀
cluster_name: cluster.local
# Subdomains of DNS domain to be resolved via /etc/resolv.conf for hostnet pods
ndots: 2
# DNS 组件 dnsmasq_kubedns/kubedns
dns_mode: dnsmasq_kubedns
# Can be docker_dns, host_resolvconf or none
resolvconf_mode: docker_dns
# 部署 netchecker 来检测 DNS 和 HTTP 状态
deploy_netchecker: true
# skydns service IP 配置
skydns_server: "{ { kube_service_addresses|ipaddr('net')|ipaddr(3)|ipaddr('address') } }"
dns_server: "{ { kube_service_addresses|ipaddr('net')|ipaddr(2)|ipaddr('address') } }"
dns_domain: "{ { cluster_name } }"
# docker 存储目录
docker_daemon_graph: "/var/lib/docker"
# docker 的额外配置参数，默认会在 /etc/systemd/system/docker.service.d/ 创建相关配置，如果节点已经安装了 docker，并且做了自己的配置，比如启用的 device mapper ，那么要删除/更改这里，防止冲突导致 docker 无法启动
docker_options: "--insecure-registry={ { kube_service_addresses } } --graph={ { docker_daemon_graph } } --iptables=false"
docker_bin_dir: "/usr/bin"
# 组件部署方式
# Settings for containerized control plane (etcd/kubelet/secrets)
etcd_deployment_type: docker
kubelet_deployment_type: docker
cert_management: script
vault_deployment_type: docker
# 这里修改为 读取本地的,否则会自动去下载
k8s_image_pull_policy: IfNotPresent
# Monitoring apps for k8s
efk_enabled: true
|
2.4、生成集群配置文件
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
| cd kargo
CONFIG_FILE=inventory/inventory.cfg python3 contrib/inventory_builder/inventory.py 10.6.0.52 10.6.0.53 10.6.0.55 10.6.0.56
# 输入如下：
DEBUG: Adding group all
DEBUG: Adding group kube-master
DEBUG: Adding group kube-node
DEBUG: Adding group etcd
DEBUG: Adding group k8s-cluster:children
DEBUG: Adding group calico-rr
DEBUG: adding host node1 to group all
DEBUG: adding host node2 to group all
DEBUG: adding host node3 to group all
DEBUG: adding host node4 to group all
DEBUG: adding host kube-node to group k8s-cluster:children
DEBUG: adding host kube-master to group k8s-cluster:children
DEBUG: adding host node1 to group etcd
DEBUG: adding host node2 to group etcd
DEBUG: adding host node3 to group etcd
DEBUG: adding host node1 to group kube-master
DEBUG: adding host node2 to group kube-master
DEBUG: adding host node1 to group kube-node
DEBUG: adding host node2 to group kube-node
DEBUG: adding host node3 to group kube-node
DEBUG: adding host node4 to group kube-node
# 生成的配置文件在当前目录，既 kargo/inventory 目录下 inventory.cfg
# 配置文件如下(默认配置双master，可自行修改)：
# SSH 非 22 端口 添加 ansible_port=xxx
[all]
node1 ansible_host=10.6.0.52 ansible_port=33 ip=10.6.0.52
node2 ansible_host=10.6.0.53 ansible_port=33 ip=10.6.0.53
node3 ansible_host=10.6.0.55 ansible_port=33 ip=10.6.0.55
node4 ansible_host=10.6.0.56 ansible_port=33 ip=10.6.0.56
[kube-master]
node1
node2
[kube-node]
node1
node2
node3
node4
[etcd]
node1
node2
node3
[k8s-cluster:children]
kube-node
kube-master
[calico-rr]
|
1
2
3
4
5
6
7
8
| # 这里修改一下 下载 镜像 的版本
# 我在使用的时候 官方已经更新到 1.5.4 了， kargo 里的还是 1.5.3 版本的
cd kargo
vi roles/download/defaults/main.yml
# 修改里面的download 版本
# 或者很快 kargo 已经更新 1.5.4版本
|
2.5、部署集群
1
2
3
4
| # 执行如下命令，请确保SSH KEY 登陆, 端口一致
ansible-playbook -i inventory/inventory.cfg cluster.yml -b -v --private-key=~/.ssh/id_rsa
|
2.6、测试
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
| # 两个 master 中使用 kubectl get nodes
[root@k8s-node-1 ~]# kubectl get nodes
NAME STATUS AGE
k8s-node-1 Ready 16m
k8s-node-2 Ready 20m
k8s-node-3 Ready 16m
k8s-node-4 Ready 16m
[root@k8s-node-2 ~]# kubectl get nodes
NAME STATUS AGE
k8s-node-1 Ready 11m
k8s-node-2 Ready 16m
k8s-node-3 Ready 11m
k8s-node-4 Ready 11m
[root@k8s-node-1 ~]# kubectl get pods --namespace=kube-system
NAME READY STATUS RESTARTS AGE
dnsmasq-411420702-z0gkx 1/1 Running 0 16m
dnsmasq-autoscaler-1155841093-1hxdl 1/1 Running 0 16m
elasticsearch-logging-v1-kgt1t 1/1 Running 0 15m
elasticsearch-logging-v1-vm4bd 1/1 Running 0 15m
fluentd-es-v1.22-6gql6 1/1 Running 0 15m
fluentd-es-v1.22-8zkjh 1/1 Running 0 15m
fluentd-es-v1.22-cjskv 1/1 Running 0 15m
fluentd-es-v1.22-j4857 1/1 Running 0 15m
kibana-logging-2924323056-x3vjk 1/1 Running 0 15m
kube-apiserver-k8s-node-1 1/1 Running 0 15m
kube-apiserver-k8s-node-2 1/1 Running 0 20m
kube-controller-manager-k8s-node-1 1/1 Running 0 16m
kube-controller-manager-k8s-node-2 1/1 Running 0 21m
kube-proxy-k8s-node-1 1/1 Running 0 16m
kube-proxy-k8s-node-2 1/1 Running 0 21m
kube-proxy-k8s-node-3 1/1 Running 0 16m
kube-proxy-k8s-node-4 1/1 Running 0 16m
kube-scheduler-k8s-node-1 1/1 Running 0 16m
kube-scheduler-k8s-node-2 1/1 Running 0 21m
kubedns-3830354952-pfl7n 3/3 Running 4 16m
kubedns-autoscaler-54374881-64x6d 1/1 Running 0 16m
nginx-proxy-k8s-node-3 1/1 Running 0 16m
nginx-proxy-k8s-node-4 1/1 Running 0 16m
[root@k8s-node-1 ~]# kubectl get pods
NAME READY STATUS RESTARTS AGE
netchecker-agent-3x3sj 1/1 Running 0 16m
netchecker-agent-ggxs2 1/1 Running 0 16m
netchecker-agent-hostnet-45k84 1/1 Running 0 16m
netchecker-agent-hostnet-kwvc8 1/1 Running 0 16m
netchecker-agent-hostnet-pwm77 1/1 Running 0 16m
netchecker-agent-hostnet-z4gmq 1/1 Running 0 16m
netchecker-agent-q3291 1/1 Running 0 16m
netchecker-agent-qtml6 1/1 Running 0 16m
netchecker-server 1/1 Running 0 16m
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
| # 配置一个 nginx deplyment 与 nginx service
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: nginx-dm
spec:
replicas: 2
template:
metadata:
labels:
name: nginx
spec:
containers:
- name: nginx
image: nginx:alpine
imagePullPolicy: IfNotPresent
ports:
- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
name: nginx-dm
spec:
ports:
- port: 80
targetPort: 80
protocol: TCP
selector:
name: nginx
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
| # 导入 yaml 文件
[root@k8s-node-1 ~]# kubectl apply -f nginx.yaml
deployment "nginx-dm" created
service "nginx-dm" created
[root@k8s-node-1 ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
nginx-dm-4194680597-0h071 1/1 Running 0 9m 10.233.75.8 k8s-node-4
nginx-dm-4194680597-dzcf3 1/1 Running 0 9m 10.233.76.124 k8s-node-3
[root@k8s-node-1 ~]# kubectl get svc -o wide
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
kubernetes 10.233.0.1 <none> 443/TCP 39m <none>
netchecker-service 10.233.0.126 <nodes> 8081:31081/TCP 33m app=netchecker-server
nginx-dm 10.233.56.138 <none> 80/TCP 10m name=nginx
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
| # 部署一个 curl 的 pods 用来测试 内部通信
apiVersion: v1
kind: Pod
metadata:
name: curl
spec:
containers:
- name: curl
image: radial/busyboxplus:curl
command:
- sh
- -c
- while true; do sleep 1; done
|
1
2
3
4
5
6
7
8
9
10
11
| # 导入 yaml 文件
[root@k8s-node-1 ~]# kubectl apply -f curl.yaml
pod "curl" created
[root@k8s-node-1 ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
curl 1/1 Running 0 2m 10.233.75.22 k8s-node-4
|
1
2
3
4
5
6
| # 测试 curl --> nginx-svc
[root@k8s-node-1 ~]# kubectl exec -it curl curl nginx-dm
Welcome to nginx!
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
| # 创建一个 zk 集群 zk-deplyment 和 service
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: zookeeper-1
spec:
replicas: 1
template:
metadata:
labels:
name: zookeeper-1
spec:
containers:
- name: zookeeper-1
image: jicki/zk:alpine
imagePullPolicy: IfNotPresent
env:
- name: NODE_ID
value: "1"
- name: NODES
value: "0.0.0.0,zookeeper-2,zookeeper-3"
ports:
- containerPort: 2181
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: zookeeper-2
spec:
replicas: 1
template:
metadata:
labels:
name: zookeeper-2
spec:
containers:
- name: zookeeper-2
image: jicki/zk:alpine
imagePullPolicy: IfNotPresent
env:
- name: NODE_ID
value: "2"
- name: NODES
value: "zookeeper-1,0.0.0.0,zookeeper-3"
ports:
- containerPort: 2181
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: zookeeper-3
spec:
replicas: 1
template:
metadata:
labels:
name: zookeeper-3
spec:
containers:
- name: zookeeper-3
image: jicki/zk:alpine
imagePullPolicy: IfNotPresent
env:
- name: NODE_ID
value: "3"
- name: NODES
value: "zookeeper-1,zookeeper-2,0.0.0.0"
ports:
- containerPort: 2181
---
apiVersion: v1
kind: Service
metadata:
name: zookeeper-1
labels:
name: zookeeper-1
spec:
ports:
- name: client
port: 2181
protocol: TCP
- name: followers
port: 2888
protocol: TCP
- name: election
port: 3888
protocol: TCP
selector:
name: zookeeper-1
---
apiVersion: v1
kind: Service
metadata:
name: zookeeper-2
labels:
name: zookeeper-2
spec:
ports:
- name: client
port: 2181
protocol: TCP
- name: followers
port: 2888
protocol: TCP
- name: election
port: 3888
protocol: TCP
selector:
name: zookeeper-2
---
apiVersion: v1
kind: Service
metadata:
name: zookeeper-3
labels:
name: zookeeper-3
spec:
ports:
- name: client
port: 2181
protocol: TCP
- name: followers
port: 2888
protocol: TCP
- name: election
port: 3888
protocol: TCP
selector:
name: zookeeper-3
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
| # 查看状态 pods 与 service
[root@k8s-node-1 ~]# kubectl get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE
zookeeper-1-3762028479-gd5rm 1/1 Running 0 1m 10.233.76.125 k8s-node-3
zookeeper-2-4266983361-cz80w 1/1 Running 0 1m 10.233.75.23 k8s-node-4
zookeeper-3-479264707-hlv3x 1/1 Running 0 1m 10.233.75.24 k8s-node-4
[root@k8s-node-1 ~]# kubectl get svc -o wide
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
zookeeper-1 10.233.25.46 <none> 2181/TCP,2888/TCP,3888/TCP 1m name=zookeeper-1
zookeeper-2 10.233.49.4 <none> 2181/TCP,2888/TCP,3888/TCP 1m name=zookeeper-2
zookeeper-3 10.233.50.206 <none> 2181/TCP,2888/TCP,3888/TCP 1m name=zookeeper-3
|
2.7、部署一个 Nginx Ingress
kubernetes 暴露服务的方式目前只有三种：LoadBlancer Service、NodePort Service、Ingress；
什么是 Ingress ? Ingress 就是利用 nginx haproxy 等负载均衡工具来暴露 kubernetes 服务。
1
2
| # 首先 部署一个 http-backend, 用于统一转发 没有的域名 到指定页面。
# 官方 nginx ingress 库 https://github.com/kubernetes/ingress/tree/master/examples/deployment/nginx
|
1
2
3
4
5
| # 下载 docker images
docker pull jicki/defaultbackend:1.0
docker tag jicki/defaultbackend:1.0 gcr.io/google_containers/defaultbackend:1.0
docker rmi jicki/defaultbackend:1.0
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
| # 下载官方的 nginx backend 文件
curl -O https://raw.githubusercontent.com/kubernetes/ingress/master/examples/deployment/nginx/default-backend.yaml
# 直接导入既可
[root@k8s-node-1 ~]# kubectl apply -f default-backend.yaml
deployment "default-http-backend" created
service "default-http-backend" created
# 查看 deployment 与 service
[root@k8s-node-1 ~]# kubectl get deployment --namespace=kube-system
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
default-http-backend 1 1 1 1 33m
[root@k8s-node-1 ~]# kubectl get svc --namespace=kube-system
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default-http-backend 10.233.20.232 <none> 80/TCP 33m
|
1
| # 部署 Ingress Controller 组件
|
1
2
3
4
5
6
| # 下载 docker 镜像
docker pull jicki/nginx-ingress-controller:0.9.0-beta.3
docker tag jicki/nginx-ingress-controller:0.9.0-beta.3 gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.3
docker rmi jicki/nginx-ingress-controller:0.9.0-beta.3
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
| # 下载 官方 nginx-ingress-controller 的yaml文件
curl -O https://raw.githubusercontent.com/kubernetes/ingress/master/examples/deployment/nginx/nginx-ingress-controller.yaml
# 编辑 yaml 文件，打开 hostNetwork: true , 将端口绑定到宿主机中
# 这里面deployment 默认只启动了一个pods, 这里可以修改 kind: Deployment 为 kind: DaemonSet 并注释掉 replicas
# 或者 修改 replicas: 1 为 N
vi nginx-ingress-controller.yaml
将 hostNetwork: true 前面的注释去掉
# 导入 yaml 文件
[root@k8s-node-1 ~]# kubectl apply -f nginx-ingress-controller.yaml
deployment "nginx-ingress-controller" created
# 查看 deployment 或者 daemonsets
[root@k8s-node-1 yaml]# kubectl get deployment --namespace=kube-system
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
nginx-ingress-controller 1 1 1 1 31s
[root@k8s-node-1 yaml]# kubectl get daemonsets --namespace=kube-system
NAME DESIRED CURRENT READY NODE-SELECTOR AGE
nginx-ingress-controller 4 4 4 <none> 1m
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
| # 最后开始 部署 Ingress
# 这里请先看看官方 ingress 的 yaml 写法
# https://kubernetes.io/docs/user-guide/ingress/
# 我们使用 之前创建的 nginx-dm service，我们来写一个 ingress
# 首先查看一下 svc
[root@k8s-node-1 yaml]# kubectl get svc
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes 10.233.0.1 <none> 443/TCP 1d
netchecker-service 10.233.0.126 <nodes> 8081:31081/TCP 1d
nginx-dm 10.233.56.138 <none> 80/TCP 1d
zookeeper-1 10.233.25.46 <none> 2181/TCP,2888/TCP,3888/TCP 1d
zookeeper-2 10.233.49.4 <none> 2181/TCP,2888/TCP,3888/TCP 1d
zookeeper-3 10.233.50.206 <none> 2181/TCP,2888/TCP,3888/TCP 1d
# 创建 yaml 文件， 这里特别注意，如果 svc 在 kube-system 下
# 必须在 metadata: 下面添加 namespace: kube-system 指定命名空间
vim nginx-ingress.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: nginx-ingress
spec:
rules:
- host: nginx.jicki.cn
http:
paths:
- backend:
serviceName: nginx-dm
servicePort: 80
# 导入 yaml 文件
[root@k8s-node-1 ~]# kubectl apply -f nginx-ingress.yaml
ingress "nginx-ingress" created
# 查看一下 创建的 ingress
[root@k8s-node-1 ~]# kubectl get ingresses
NAME HOSTS ADDRESS PORTS AGE
nginx-ingress nginx.jicki.cn 80 17s
# 这里显示 ADDRESS 为 空 实际上 所有 master 与 nodes 都绑定了
# 将域名解析到 任何一个 IP 上都可以。
# 下面访问 http://nginx.jicki.cn/
# 这里注意，Ingresses 只做简单的端口转发。
|
维护 FAQ
1
2
3
4
5
6
7
8
| # 卸载
cd kargo
ansible-playbook -i inventory/inventory.cfg reset.yml -b -v --private-key=~/.ssh/id_rsa
|
1
2
3
4
5
6
| # hostname 的问题
# 部署 kargo 必须配置 hostname 否则 多 master 会出现 无法创建 api 等 pods
# 如果 执行了 ansible-playbook 之前没改 hostname 必须删除 /tmp 下的 node[N]
# 否则更改 /etc/hosts 失败
|
