k8s多集羣配置管理平臺
k8s多集羣配置管理平臺
臨時集羣特性
模擬生產環境css
總體環境說明
內網：10.17.1.44
[root@localhost account-server]# kubectl get nodes NAME STATUS ROLES AGE VERSION localhost Ready master 25h v1.17.5 [root@localhost account-server]# kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE cattle-system cattle-cluster-agent-689f8dcc64-7slpk 1/1 Running 0 78m cattle-system cattle-node-agent-7lndv 1/1 Running 0 78m ingress-nginx nginx-ingress-controller-74879f74c6-jdzx9 1/1 Running 0 24h kong ingress-kong-d7b5d68f4-j6tsx 2/2 Running 2 25h kube-system calico-kube-controllers-69cb4d4df7-447m5 1/1 Running 0 25h kube-system calico-node-7cb2w 1/1 Running 0 25h kube-system coredns-9d85f5447-x5l4c 1/1 Running 0 25h kube-system coredns-9d85f5447-zqgh7 1/1 Running 0 25h kube-system etcd-localhost 1/1 Running 0 25h kube-system kube-apiserver-localhost 1/1 Running 0 25h kube-system kube-controller-manager-localhost 1/1 Running 0 25h kube-system kube-proxy-gdtdt 1/1 Running 0 25h kube-system kube-scheduler-localhost 1/1 Running 0 25h kube-system metrics-server-6fcdc7bddc-ggsnm 1/1 Running 0 25h
myaliyun: 47.1x6.x9.1x6
rancher 部署於此節點node
[root@zisefeizhu ~]# docker run -d --restart=unless-stopped \
-p 80:80 -p 443:443 \
rancher/rancher:latest
[root@zisefeizhu ~]# free -h
total used free shared buff/cache available
Mem: 3.7G 1.1G 320M 640K 2.3G 2.3G
Swap: 0B 0B 0B
[root@zisefeizhu ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
87aeb7e4a262 rancher/rancher:latest "entrypoint.sh" 2 hours ago Up 2 hours 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp angry_visvesvaraya
臨時環境(模擬生產)：如上圖
[root@mobanji .kube]# kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE arms-prom arms-prometheus-ack-arms-prometheus-7b4d578f86-ff824 1/1 Running 0 9m26s arms-prom kube-state-metrics-864b9c5857-ljb6l 1/1 Running 0 9m42s arms-prom node-exporter-6ttg5 2/2 Running 0 9m42s arms-prom node-exporter-rz7rr 2/2 Running 0 9m42s arms-prom node-exporter-t45zj 2/2 Running 0 9m42s kube-system ack-node-problem-detector-daemonset-2r9bg 1/1 Running 0 9m14s kube-system ack-node-problem-detector-daemonset-mjk4k 1/1 Running 0 9m15s kube-system ack-node-problem-detector-daemonset-t94p4 1/1 Running 0 9m13s kube-system ack-node-problem-detector-eventer-6cb57ffb68-gl5n5 1/1 Running 0 9m44s kube-system alibaba-log-controller-795d7486f8-jrcv2 1/1 Running 2 9m45s kube-system alicloud-application-controller-bc84954fb-z5dq9 1/1 Running 0 9m45s kube-system alicloud-monitor-controller-7c8c5485f4-xdrdd 1/1 Running 0 9m45s kube-system aliyun-acr-credential-helper-59b59477df-p7vxc 1/1 Running 0 9m46s kube-system coredns-79989b94b6-47vll 1/1 Running 0 9m46s kube-system coredns-79989b94b6-dqpjm 1/1 Running 0 9m46s kube-system csi-plugin-2kjc9 9/9 Running 0 9m45s kube-system csi-plugin-5lt7b 9/9 Running 0 9m45s kube-system csi-plugin-px52m 9/9 Running 0 9m45s kube-system csi-provisioner-56d7fb44b6-6czqx 8/8 Running 0 9m45s kube-system csi-provisioner-56d7fb44b6-jqsrt 8/8 Running 1 9m45s kube-system kube-eventer-init-mv2vj 0/1 Completed 0 9m44s kube-system kube-flannel-ds-4xbhr 1/1 Running 0 9m46s kube-system kube-flannel-ds-mfg7m 1/1 Running 0 9m46s kube-system kube-flannel-ds-wnrp2 1/1 Running 0 9m46s kube-system kube-proxy-worker-44tkt 1/1 Running 0 9m45s kube-system kube-proxy-worker-nw2g6 1/1 Running 0 9m45s kube-system kube-proxy-worker-s78vl 1/1 Running 0 9m45s kube-system logtail-ds-67lkm 1/1 Running 0 9m45s kube-system logtail-ds-68fdz 1/1 Running 0 9m45s kube-system logtail-ds-bkntm 1/1 Running 0 9m45s kube-system metrics-server-f88f9b8d8-l9zl4 1/1 Running 0 9m46s kube-system nginx-ingress-controller-758cdc676c-k8ffj 1/1 Running 0 9m46s kube-system nginx-ingress-controller-758cdc676c-pxzxd 1/1 Running 0 9m46s
測試點
可行性驗證
在臨時環境上部署rancher 並同時管控臨時環境和內網環境
🆗！暫rancher管控兩個k8s集羣成功。說明rancher能夠管理多k8s集羣nginx
臨時環境
內網環境
可行性驗證到此完畢web
可預測性問題驗證
測試rancher web 和k8s本端是否能夠同時進行操做
k8s集羣本端正常。
rancher web 正常。docker
這說明 rancher web 能夠和k8s本端同時進行管控操做vim
刪除myaliyun的rancher而後再起一個rancher 看可否管控
[root@zisefeizhu ~]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 87aeb7e4a262 rancher/rancher:latest "entrypoint.sh" 2 hours ago Up 2 hours 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp angry_visvesvaraya [root@zisefeizhu ~]# docker container rm -f 87aeb7e4a262 87aeb7e4a262 觀察k8s集羣 [root@mobanji .kube]# kubectl get pods -A -w NAMESPACE NAME READY STATUS RESTARTS AGE arms-prom arms-prometheus-ack-arms-prometheus-7b4d578f86-ff824 1/1 Running 0 22m arms-prom kube-state-metrics-864b9c5857-ljb6l 1/1 Running 0 22m arms-prom node-exporter-6ttg5 2/2 Running 0 22m arms-prom node-exporter-rz7rr 2/2 Running 0 22m arms-prom node-exporter-t45zj 2/2 Running 0 22m cattle-system cattle-cluster-agent-7d99b645d9-s5gqh 1/1 Running 0 16m cattle-system cattle-node-agent-9s4tw 0/1 Pending 0 16m cattle-system cattle-node-agent-m8rhk 1/1 Running 0 17m cattle-system cattle-node-agent-nkl5m 1/1 Running 0 17m kube-system ack-node-problem-detector-daemonset-2r9bg 1/1 Running 0 22m kube-system ack-node-problem-detector-daemonset-mjk4k 1/1 Running 0 22m kube-system ack-node-problem-detector-daemonset-t94p4 1/1 Running 0 22m kube-system ack-node-problem-detector-eventer-6cb57ffb68-gl5n5 1/1 Running 0 22m kube-system alibaba-log-controller-795d7486f8-jrcv2 1/1 Running 2 22m kube-system alicloud-application-controller-bc84954fb-z5dq9 1/1 Running 0 22m kube-system alicloud-monitor-controller-7c8c5485f4-xdrdd 1/1 Running 0 22m kube-system aliyun-acr-credential-helper-59b59477df-p7vxc 1/1 Running 0 23m kube-system coredns-79989b94b6-47vll 1/1 Running 0 23m kube-system coredns-79989b94b6-dqpjm 1/1 Running 0 23m kube-system csi-plugin-2kjc9 9/9 Running 0 22m kube-system csi-plugin-5lt7b 9/9 Running 0 22m kube-system csi-plugin-px52m 9/9 Running 0 22m kube-system csi-provisioner-56d7fb44b6-6czqx 8/8 Running 0 22m kube-system csi-provisioner-56d7fb44b6-jqsrt 8/8 Running 1 22m kube-system kube-eventer-init-mv2vj 0/1 Completed 0 22m kube-system kube-flannel-ds-4xbhr 1/1 Running 0 23m kube-system kube-flannel-ds-mfg7m 1/1 Running 0 23m kube-system kube-flannel-ds-wnrp2 1/1 Running 0 23m kube-system kube-proxy-worker-44tkt 1/1 Running 0 22m kube-system kube-proxy-worker-nw2g6 1/1 Running 0 22m kube-system kube-proxy-worker-s78vl 1/1 Running 0 22m kube-system logtail-ds-67lkm 1/1 Running 0 22m kube-system logtail-ds-68fdz 1/1 Running 0 22m kube-system logtail-ds-bkntm 1/1 Running 0 22m kube-system metrics-server-f88f9b8d8-l9zl4 1/1 Running 0 23m kube-system nginx-ingress-controller-758cdc676c-k8ffj 1/1 Running 0 23m kube-system nginx-ingress-controller-758cdc676c-pxzxd 1/1 Running 0 23m 臨時環境和內網環境 k8s 集羣都沒發生改變
[root@zisefeizhu ~]# docker run -d --restart=unless-stopped \ > -p 80:80 -p 443:443 \ > rancher/rancher:latest bdc79c85e179ab9bb481a391029ac7e03a19252ede71860992971e90f6e871bd
rancher web k8s集羣丟失，再次添加api
[root@mobanji .kube]# curl --insecure -sfL https://47.1xx.x9.1x6/v3/import/tgnmhhj6n2s5tc4prw9ft4pnd87w6sfw54487lrj2k5rkd26zwg8.yaml | kubectl apply -f - clusterrole.rbac.authorization.k8s.io/proxy-clusterrole-kubeapiserver unchanged clusterrolebinding.rbac.authorization.k8s.io/proxy-role-binding-kubernetes-master unchanged namespace/cattle-system unchanged serviceaccount/cattle unchanged clusterrolebinding.rbac.authorization.k8s.io/cattle-admin-binding unchanged secret/cattle-credentials-e50bc99 created clusterrole.rbac.authorization.k8s.io/cattle-admin unchanged deployment.apps/cattle-cluster-agent configured daemonset.apps/cattle-node-agent configured
這證實rancher意外宕機對k8s集羣沒有影響app
可否兩個rancher同時管控
在內網環境部署rancherless
注：由於臨時環境沒法訪問內網，因此此問題只能在內網環境測試curl
目前內網環境正加入在臨時環境部署的rancher中，如今直接在內網環境的rancher中加入內網k8s
[root@localhost elfk]# curl --insecure -sfL https://10.17.1.44:1443/v3/import/867hj6vl9tfg7vqwc4xdnpck8f6pjw8hn4bjw9thksj5spbnwjprjh.yaml | kubectl apply -f - clusterrole.rbac.authorization.k8s.io/proxy-clusterrole-kubeapiserver unchanged clusterrolebinding.rbac.authorization.k8s.io/proxy-role-binding-kubernetes-master unchanged namespace/cattle-system unchanged serviceaccount/cattle unchanged clusterrolebinding.rbac.authorization.k8s.io/cattle-admin-binding unchanged secret/cattle-credentials-6375cce created clusterrole.rbac.authorization.k8s.io/cattle-admin unchanged deployment.apps/cattle-cluster-agent configured daemonset.apps/cattle-node-agent configured 內網環境的k8s端 管控正常 [root@localhost elfk]# kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE cattle-prometheus exporter-kube-state-cluster-monitoring-dcf459bb8-t8qnj 1/1 Running 0 98m cattle-prometheus exporter-node-cluster-monitoring-9kdvj 1/1 Running 0 98m cattle-prometheus grafana-cluster-monitoring-698d79ff64-tv8hx 2/2 Running 0 98m cattle-prometheus prometheus-cluster-monitoring-0 5/5 Running 1 95m cattle-prometheus prometheus-operator-monitoring-operator-5f5d4c5987-8fjtq 1/1 Running 0 98m cattle-system cattle-cluster-agent-56c4d48669-dpftm 1/1 Running 0 73s cattle-system cattle-node-agent-p8r5x 1/1 Running 0 69s ingress-nginx nginx-ingress-controller-74879f74c6-jdzx9 1/1 Running 0 25h kong ingress-kong-d7b5d68f4-j6tsx 2/2 Running 2 25h kube-system calico-kube-controllers-69cb4d4df7-447m5 1/1 Running 0 25h kube-system calico-node-7cb2w 1/1 Running 0 25h kube-system coredns-9d85f5447-x5l4c 1/1 Running 0 26h kube-system coredns-9d85f5447-zqgh7 1/1 Running 0 26h kube-system etcd-localhost 1/1 Running 0 26h kube-system kube-apiserver-localhost 1/1 Running 0 26h kube-system kube-controller-manager-localhost 1/1 Running 0 26h kube-system kube-proxy-gdtdt 1/1 Running 0 26h kube-system kube-scheduler-localhost 1/1 Running 0 26h kube-system metrics-server-6fcdc7bddc-ggsnm 1/1 Running 0 25h
臨時環境的rancher 失去對內網k8s的管控
內網環境的rancher接管對內網k8s的管控
此實驗在臨時環境同時跑兩個rancher（端口差異）驗證也是如此
使用rancher 的kubeconfig管控k8s集羣
[root@mobanji .kube]# vim config
apiVersion: v1
kind: Config
clusters:
- name: "linshi"
cluster:
server: "https://4xx.1xx.6x.1x6/k8s/clusters/c-tgrbh"
certificate-authority-data: "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJpVENDQ\
VM2Z0F3SUJBZ0lCQURBS0JnZ3Foa2pPUFFRREFqQTdNUnd3R2dZRFZRUUtFeE5rZVc1aGJXbGoKY\
kdsemRHVnVaWEl0YjNKbk1Sc3dHUVlEVlFRREV4SmtlVzVoYldsamJHbHpkR1Z1WlhJdFkyRXdIa\
GNOTWpBdwpOekUxTURrMU56VXlXaGNOTXpBd056RXpNRGsxTnpVeVdqQTdNUnd3R2dZRFZRUUtFe\
E5rZVc1aGJXbGpiR2x6CmRHVnVaWEl0YjNKbk1Sc3dHUVlEVlFRREV4SmtlVzVoYldsamJHbHpkR\
1Z1WlhJdFkyRXdXVEFUQmdjcWhrak8KUFFJQkJnZ3Foa2pPUFFNQkJ3TkNBQVIza3pSWnV4UDVia\
npjd0lGVkNTcHdHZFZ2d281M1Q5b1pwajBOczhuVApVemg1VVFUNHVPYzE4QytYZVUvZkdyM3QrV\
0Q4bU0vRDVaaHc3L0ZuTWw0b295TXdJVEFPQmdOVkhROEJBZjhFCkJBTUNBcVF3RHdZRFZSMFRBU\
UgvQkFVd0F3RUIvekFLQmdncWhrak9QUVFEQWdOSkFEQkdBaUVBd2JaRmRBbEkKSWVJNlBrODdsU\
kJTNVh3eDk3NHNGUHpIL3RCRTUxMnpSOVFDSVFEbWtDZWpoa1paZlhocG1LWHdCMjc2ek1Odwpzc\
zdYdFdRY25Hc1JKNjJpZkE9PQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0t"
users:
- name: "linshi"
user:
token: "kubeconfig-user-rjd7z:z4lw5wcchlmf5ncjcss7hw7rrspcrt8jxcv29xxmlrtmjchw6kp8fc"
contexts:
- name: "linshi"
context:
user: "linshi"
cluster: "linshi"
current-context: "linshi"
[root@mobanji .kube]# kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
arms-prom arms-prometheus-ack-arms-prometheus-7b4d578f86-ff824 1/1 Running 0 69m
arms-prom kube-state-metrics-864b9c5857-ljb6l 1/1 Running 0 70m
arms-prom node-exporter-6ttg5 2/2 Running 0 70m
arms-prom node-exporter-rz7rr 2/2 Running 0 70m
arms-prom node-exporter-t45zj 2/2 Running 0 70m
cattle-system cattle-cluster-agent-57c67fb54c-6pr9q 1/1 Running 0 22m
cattle-system cattle-node-agent-44d7g 1/1 Running 0 40m
cattle-system cattle-node-agent-f2b62 0/1 Pending 0 22m
cattle-system cattle-node-agent-qg86b 1/1 Running 0 40m
kube-system ack-node-problem-detector-daemonset-2r9bg 1/1 Running 0 69m
kube-system ack-node-problem-detector-daemonset-mjk4k 1/1 Running 0 69m
kube-system ack-node-problem-detector-daemonset-t94p4 1/1 Running 0 69m
kube-system ack-node-problem-detector-eventer-6cb57ffb68-gl5n5 1/1 Running 0 70m
kube-system alibaba-log-controller-795d7486f8-jrcv2 1/1 Running 2 70m
kube-system alicloud-application-controller-bc84954fb-z5dq9 1/1 Running 0 70m
kube-system alicloud-monitor-controller-7c8c5485f4-xdrdd 1/1 Running 0 70m
kube-system aliyun-acr-credential-helper-59b59477df-p7vxc 1/1 Running 0 70m
kube-system coredns-79989b94b6-47vll 1/1 Running 0 70m
kube-system coredns-79989b94b6-dqpjm 1/1 Running 0 70m
kube-system csi-plugin-2kjc9 9/9 Running 0 70m
kube-system csi-plugin-5lt7b 9/9 Running 0 70m
kube-system csi-plugin-px52m 9/9 Running 0 70m
kube-system csi-provisioner-56d7fb44b6-6czqx 8/8 Running 0 70m
kube-system csi-provisioner-56d7fb44b6-jqsrt 8/8 Running 1 70m
kube-system kube-eventer-init-mv2vj 0/1 Completed 0 70m
kube-system kube-flannel-ds-4xbhr 1/1 Running 0 70m
kube-system kube-flannel-ds-mfg7m 1/1 Running 0 70m
kube-system kube-flannel-ds-wnrp2 1/1 Running 0 70m
kube-system kube-proxy-worker-44tkt 1/1 Running 0 70m
kube-system kube-proxy-worker-nw2g6 1/1 Running 0 70m
kube-system kube-proxy-worker-s78vl 1/1 Running 0 70m
kube-system logtail-ds-67lkm 1/1 Running 0 70m
kube-system logtail-ds-68fdz 1/1 Running 0 70m
kube-system logtail-ds-bkntm 1/1 Running 0 70m
kube-system metrics-server-f88f9b8d8-l9zl4 1/1 Running 0 70m
kube-system nginx-ingress-controller-758cdc676c-k8ffj 1/1 Running 0 70m
kube-system nginx-ingress-controller-758cdc676c-pxzxd 1/1 Running 0 70m
這說明使用rancher的kubeconfig能夠給特定集羣進行管控
如今換回原來的看是否能夠管控
[root@mobanji .kube]# mv config.bak02 config mv：是否覆蓋"config"？ y [root@mobanji .kube]# kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE arms-prom arms-prometheus-ack-arms-prometheus-7b4d578f86-ff824 1/1 Running 0 71m arms-prom kube-state-metrics-864b9c5857-ljb6l 1/1 Running 0 71m arms-prom node-exporter-6ttg5 2/2 Running 0 71m arms-prom node-exporter-rz7rr 2/2 Running 0 71m arms-prom node-exporter-t45zj 2/2 Running 0 71m cattle-system cattle-cluster-agent-57c67fb54c-6pr9q 1/1 Running 0 24m cattle-system cattle-node-agent-44d7g 1/1 Running 0 41m cattle-system cattle-node-agent-f2b62 0/1 Pending 0 24m cattle-system cattle-node-agent-qg86b 1/1 Running 0 41m kube-system ack-node-problem-detector-daemonset-2r9bg 1/1 Running 0 71m kube-system ack-node-problem-detector-daemonset-mjk4k 1/1 Running 0 71m kube-system ack-node-problem-detector-daemonset-t94p4 1/1 Running 0 71m kube-system ack-node-problem-detector-eventer-6cb57ffb68-gl5n5 1/1 Running 0 71m kube-system alibaba-log-controller-795d7486f8-jrcv2 1/1 Running 2 71m kube-system alicloud-application-controller-bc84954fb-z5dq9 1/1 Running 0 71m kube-system alicloud-monitor-controller-7c8c5485f4-xdrdd 1/1 Running 0 71m kube-system aliyun-acr-credential-helper-59b59477df-p7vxc 1/1 Running 0 71m kube-system coredns-79989b94b6-47vll 1/1 Running 0 71m kube-system coredns-79989b94b6-dqpjm 1/1 Running 0 71m kube-system csi-plugin-2kjc9 9/9 Running 0 71m kube-system csi-plugin-5lt7b 9/9 Running 0 71m kube-system csi-plugin-px52m 9/9 Running 0 71m kube-system csi-provisioner-56d7fb44b6-6czqx 8/8 Running 0 71m kube-system csi-provisioner-56d7fb44b6-jqsrt 8/8 Running 1 71m kube-system kube-eventer-init-mv2vj 0/1 Completed 0 71m kube-system kube-flannel-ds-4xbhr 1/1 Running 0 71m kube-system kube-flannel-ds-mfg7m 1/1 Running 0 71m kube-system kube-flannel-ds-wnrp2 1/1 Running 0 71m kube-system kube-proxy-worker-44tkt 1/1 Running 0 71m kube-system kube-proxy-worker-nw2g6 1/1 Running 0 71m kube-system kube-proxy-worker-s78vl 1/1 Running 0 71m kube-system logtail-ds-67lkm 1/1 Running 0 71m kube-system logtail-ds-68fdz 1/1 Running 0 71m kube-system logtail-ds-bkntm 1/1 Running 0 71m kube-system metrics-server-f88f9b8d8-l9zl4 1/1 Running 0 71m kube-system nginx-ingress-controller-758cdc676c-k8ffj 1/1 Running 0 71m kube-system nginx-ingress-controller-758cdc676c-pxzxd 1/1 Running 0 71m
這證實rancher的kubeconfig並不影響k8s集羣自身的config
遇到的問題
臨時環境託管k8s沒法拉取鏡像
1.虛擬路由器
2.防火牆
臨時環境沒有公網ip 沒法部署rancher
綁定eip
部署rancher臨時環境k8s掛掉
在myaliyun部署rancher致使臨時環境k8s集羣的controller和scheduler掛掉
我觀察到一個現象：在aliyun的ecs上部署k8s 而後在用：docker run -d --restart=unless-stopped \
> -p 1880:80 -p 1443:443 \
> rancher/rancher:latest 起一個rancher 這會致使k8s集羣崩潰。以下所示：kube-system kube-controller-manager-zisefeizhu 0/1 Error 10 117s
kube-system kube-controller-manager-zisefeizhu 0/1 CrashLoopBackOff 10 118s
kube-system kube-scheduler-zisefeizhu 0/1 Error 9 3m59s
kube-system kube-scheduler-zisefeizhu 0/1 CrashLoopBackOff 9 4m3s
具體緣由是：rancher 在試圖控制個人k8s集羣的controller 和 scheduler
並且還有一個現像：docker 起的rancher 處於不斷重啓的過程
[rootazisefeizhu-J#docker ps |grep rancher
0.0.0.0:1
entrypoint.sh"
rancher/rancher:latest
3d9ff6e8388
880.2807P000
rootazisefeizhu-liadockorps
greprancher
0.0.0.0:1
e3d91f6e8388ncher/ranchert
Up75econds
minutes4go
entrypoint.sh
880-80/tcp0.0.0.0:1443-3443/tcp
cstaticnightingalo
這個現象在內網自建的k8s上沒有的 但在阿里雲的k8s上是出現的
資源不足致使競爭，並且涼掉
相關文章
- 1. 多k8s集羣管理
- 2. docker+k8s+rancher搭建集羣管理平臺
- 3. 集羣資源管理系統 yarn平臺的配置
- 4. Rancher管理k8s集羣
- 5. k8s之集羣管理
- 6. k8s集羣service管理
- 7. Wayne 配置 k8s 集羣
- 8. nginx配置管理平臺
- 9. KubeSphere®️ 容器集羣管理平臺
- 10. rancher2.X搭建k8s集羣平臺
- 更多相關文章...
- • Swarm 集羣管理 - Docker教程
- • ionic 平臺 - ionic 教程
- • ☆技術問答集錦（13）Java Instrument原理
- • IntelliJ IDEA 代碼格式化配置和快捷鍵
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
最新文章
歡迎關注本站公眾號,獲取更多信息
相關文章
- 1. 多k8s集羣管理
- 2. docker+k8s+rancher搭建集羣管理平臺
- 3. 集羣資源管理系統 yarn平臺的配置
- 4. Rancher管理k8s集羣
- 5. k8s之集羣管理
- 6. k8s集羣service管理
- 7. Wayne 配置 k8s 集羣
- 8. nginx配置管理平臺
- 9. KubeSphere®️ 容器集羣管理平臺
- 10. rancher2.X搭建k8s集羣平臺