k8s多集群配置管理平台

临时集群特性



模拟生产环境

整体环境说明

内网：10.17.1.44

  1. [root@localhost account-server]# kubectl get nodes
  2. NAME        STATUS   ROLES    AGE   VERSION
  3. localhost   Ready    master   25h   v1.17.5
  4. [root@localhost account-server]# kubectl get pods -A
  5. NAMESPACE           NAME                                                       READY   STATUS    RESTARTS   AGE
  6. cattle-system       cattle-cluster-agent-689f8dcc64-7slpk                      1/1     Running   0          78m
  7. cattle-system       cattle-node-agent-7lndv                                    1/1     Running   0          78m
  8. ingress-nginx       nginx-ingress-controller-74879f74c6-jdzx9                  1/1     Running   0          24h
  9. kong                ingress-kong-d7b5d68f4-j6tsx                               2/2     Running   2          25h
  10. kube-system         calico-kube-controllers-69cb4d4df7-447m5                   1/1     Running   0          25h
  11. kube-system         calico-node-7cb2w                                          1/1     Running   0          25h
  12. kube-system         coredns-9d85f5447-x5l4c                                    1/1     Running   0          25h
  13. kube-system         coredns-9d85f5447-zqgh7                                    1/1     Running   0          25h
  14. kube-system         etcd-localhost                                             1/1     Running   0          25h
  15. kube-system         kube-apiserver-localhost                                   1/1     Running   0          25h
  16. kube-system         kube-controller-manager-localhost                          1/1     Running   0          25h
  17. kube-system         kube-proxy-gdtdt                                           1/1     Running   0          25h
  18. kube-system         kube-scheduler-localhost                                   1/1     Running   0          25h
  19. kube-system         metrics-server-6fcdc7bddc-ggsnm                            1/1     Running   0          25h

myaliyun: 47.1x6.x9.1x6

rancher 部署于此节点

  1. [root@zisefeizhu ~]# docker run -d --restart=unless-stopped \
  2.     -p 80:80 -p 443:443 \
  3.     rancher/rancher:latest
  4. [root@zisefeizhu ~]# free -h
  5.               total        used        free      shared  buff/cache   available
  6. Mem:           3.7G        1.1G        320M        640K        2.3G        2.3G
  7. Swap:            0B          0B          0B
  8. [root@zisefeizhu ~]# docker ps
  9. CONTAINER ID        IMAGE                    COMMAND             CREATED             STATUS              PORTS                                      NAMES
  10. 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

临时环境(模拟生产)：如上图

  1. [root@mobanji .kube]# kubectl get pods -A
  2. NAMESPACE       NAME                                                   READY   STATUS      RESTARTS   AGE
  3. arms-prom       arms-prometheus-ack-arms-prometheus-7b4d578f86-ff824   1/1     Running     0          9m26s
  4. arms-prom       kube-state-metrics-864b9c5857-ljb6l                    1/1     Running     0          9m42s
  5. arms-prom       node-exporter-6ttg5                                    2/2     Running     0          9m42s
  6. arms-prom       node-exporter-rz7rr                                    2/2     Running     0          9m42s
  7. arms-prom       node-exporter-t45zj                                    2/2     Running     0          9m42s
  8. kube-system     ack-node-problem-detector-daemonset-2r9bg              1/1     Running     0          9m14s
  9. kube-system     ack-node-problem-detector-daemonset-mjk4k              1/1     Running     0          9m15s
  10. kube-system     ack-node-problem-detector-daemonset-t94p4              1/1     Running     0          9m13s
  11. kube-system     ack-node-problem-detector-eventer-6cb57ffb68-gl5n5     1/1     Running     0          9m44s
  12. kube-system     alibaba-log-controller-795d7486f8-jrcv2                1/1     Running     2          9m45s
  13. kube-system     alicloud-application-controller-bc84954fb-z5dq9        1/1     Running     0          9m45s
  14. kube-system     alicloud-monitor-controller-7c8c5485f4-xdrdd           1/1     Running     0          9m45s
  15. kube-system     aliyun-acr-credential-helper-59b59477df-p7vxc          1/1     Running     0          9m46s
  16. kube-system     coredns-79989b94b6-47vll                               1/1     Running     0          9m46s
  17. kube-system     coredns-79989b94b6-dqpjm                               1/1     Running     0          9m46s
  18. kube-system     csi-plugin-2kjc9                                       9/9     Running     0          9m45s
  19. kube-system     csi-plugin-5lt7b                                       9/9     Running     0          9m45s
  20. kube-system     csi-plugin-px52m                                       9/9     Running     0          9m45s
  21. kube-system     csi-provisioner-56d7fb44b6-6czqx                       8/8     Running     0          9m45s
  22. kube-system     csi-provisioner-56d7fb44b6-jqsrt                       8/8     Running     1          9m45s
  23. kube-system     kube-eventer-init-mv2vj                                0/1     Completed   0          9m44s
  24. kube-system     kube-flannel-ds-4xbhr                                  1/1     Running     0          9m46s
  25. kube-system     kube-flannel-ds-mfg7m                                  1/1     Running     0          9m46s
  26. kube-system     kube-flannel-ds-wnrp2                                  1/1     Running     0          9m46s
  27. kube-system     kube-proxy-worker-44tkt                                1/1     Running     0          9m45s
  28. kube-system     kube-proxy-worker-nw2g6                                1/1     Running     0          9m45s
  29. kube-system     kube-proxy-worker-s78vl                                1/1     Running     0          9m45s
  30. kube-system     logtail-ds-67lkm                                       1/1     Running     0          9m45s
  31. kube-system     logtail-ds-68fdz                                       1/1     Running     0          9m45s
  32. kube-system     logtail-ds-bkntm                                       1/1     Running     0          9m45s
  33. kube-system     metrics-server-f88f9b8d8-l9zl4                         1/1     Running     0          9m46s
  34. kube-system     nginx-ingress-controller-758cdc676c-k8ffj              1/1     Running     0          9m46s
  35. kube-system     nginx-ingress-controller-758cdc676c-pxzxd              1/1     Running     0          9m46s

测试点

可行性验证

在临时环境上部署rancher 并同时管控临时环境和内网环境







！暂rancher管控两个k8s集群成功。说明rancher可以管理多k8s集群

临时环境



内网环境





可行性验证到此完毕

可预测性问题验证

测试rancher web 和k8s本端是否可以同时进行操作

k8s集群本端正常。



rancher web 正常。

这说明 rancher web 可以和k8s本端同时进行管控操作

删除myaliyun的rancher然后再起一个rancher 看能否管控

  1. [root@zisefeizhu ~]# docker ps
  2. CONTAINER ID        IMAGE                    COMMAND             CREATED             STATUS              PORTS                                      NAMES
  3. 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
  5. [root@zisefeizhu ~]# docker container rm -f 87aeb7e4a262
  6. 87aeb7e4a262
  8. 观察k8s集群
  9. [root@mobanji .kube]# kubectl get pods -A -w
  10. NAMESPACE       NAME                                                   READY   STATUS      RESTARTS   AGE
  11. arms-prom       arms-prometheus-ack-arms-prometheus-7b4d578f86-ff824   1/1     Running     0          22m
  12. arms-prom       kube-state-metrics-864b9c5857-ljb6l                    1/1     Running     0          22m
  13. arms-prom       node-exporter-6ttg5                                    2/2     Running     0          22m
  14. arms-prom       node-exporter-rz7rr                                    2/2     Running     0          22m
  15. arms-prom       node-exporter-t45zj                                    2/2     Running     0          22m
  16. cattle-system   cattle-cluster-agent-7d99b645d9-s5gqh                  1/1     Running     0          16m
  17. cattle-system   cattle-node-agent-9s4tw                                0/1     Pending     0          16m
  18. cattle-system   cattle-node-agent-m8rhk                                1/1     Running     0          17m
  19. cattle-system   cattle-node-agent-nkl5m                                1/1     Running     0          17m
  20. kube-system     ack-node-problem-detector-daemonset-2r9bg              1/1     Running     0          22m
  21. kube-system     ack-node-problem-detector-daemonset-mjk4k              1/1     Running     0          22m
  22. kube-system     ack-node-problem-detector-daemonset-t94p4              1/1     Running     0          22m
  23. kube-system     ack-node-problem-detector-eventer-6cb57ffb68-gl5n5     1/1     Running     0          22m
  24. kube-system     alibaba-log-controller-795d7486f8-jrcv2                1/1     Running     2          22m
  25. kube-system     alicloud-application-controller-bc84954fb-z5dq9        1/1     Running     0          22m
  26. kube-system     alicloud-monitor-controller-7c8c5485f4-xdrdd           1/1     Running     0          22m
  27. kube-system     aliyun-acr-credential-helper-59b59477df-p7vxc          1/1     Running     0          23m
  28. kube-system     coredns-79989b94b6-47vll                               1/1     Running     0          23m
  29. kube-system     coredns-79989b94b6-dqpjm                               1/1     Running     0          23m
  30. kube-system     csi-plugin-2kjc9                                       9/9     Running     0          22m
  31. kube-system     csi-plugin-5lt7b                                       9/9     Running     0          22m
  32. kube-system     csi-plugin-px52m                                       9/9     Running     0          22m
  33. kube-system     csi-provisioner-56d7fb44b6-6czqx                       8/8     Running     0          22m
  34. kube-system     csi-provisioner-56d7fb44b6-jqsrt                       8/8     Running     1          22m
  35. kube-system     kube-eventer-init-mv2vj                                0/1     Completed   0          22m
  36. kube-system     kube-flannel-ds-4xbhr                                  1/1     Running     0          23m
  37. kube-system     kube-flannel-ds-mfg7m                                  1/1     Running     0          23m
  38. kube-system     kube-flannel-ds-wnrp2                                  1/1     Running     0          23m
  39. kube-system     kube-proxy-worker-44tkt                                1/1     Running     0          22m
  40. kube-system     kube-proxy-worker-nw2g6                                1/1     Running     0          22m
  41. kube-system     kube-proxy-worker-s78vl                                1/1     Running     0          22m
  42. kube-system     logtail-ds-67lkm                                       1/1     Running     0          22m
  43. kube-system     logtail-ds-68fdz                                       1/1     Running     0          22m
  44. kube-system     logtail-ds-bkntm                                       1/1     Running     0          22m
  45. kube-system     metrics-server-f88f9b8d8-l9zl4                         1/1     Running     0          23m
  46. kube-system     nginx-ingress-controller-758cdc676c-k8ffj              1/1     Running     0          23m
  47. kube-system     nginx-ingress-controller-758cdc676c-pxzxd              1/1     Running     0          23m
  49. 临时环境和内网环境 k8s 集群都没发生改变

  1. [root@zisefeizhu ~]# docker run -d --restart=unless-stopped \
  2. >     -p 80:80 -p 443:443 \
  3. >     rancher/rancher:latest
  4. bdc79c85e179ab9bb481a391029ac7e03a19252ede71860992971e90f6e871bd



rancher web k8s集群丢失，再次添加

  1. [root@mobanji .kube]# curl --insecure -sfL https://47.1xx.x9.1x6/v3/import/tgnmhhj6n2s5tc4prw9ft4pnd87w6sfw54487lrj2k5rkd26zwg8.yaml | kubectl apply -f -
  2. clusterrole.rbac.authorization.k8s.io/proxy-clusterrole-kubeapiserver unchanged
  3. clusterrolebinding.rbac.authorization.k8s.io/proxy-role-binding-kubernetes-master unchanged
  4. namespace/cattle-system unchanged
  5. serviceaccount/cattle unchanged
  6. clusterrolebinding.rbac.authorization.k8s.io/cattle-admin-binding unchanged
  7. secret/cattle-credentials-e50bc99 created
  8. clusterrole.rbac.authorization.k8s.io/cattle-admin unchanged
  9. deployment.apps/cattle-cluster-agent configured
  10. daemonset.apps/cattle-node-agent configured



这证明rancher意外宕机对k8s集群没有影响

能否两个rancher同时管控

在内网环境部署rancher

注：因为临时环境无法访问内网，所以此问题只能在内网环境测试

目前内网环境正加入在临时环境部署的rancher中，现在直接在内网环境的rancher中加入内网k8s

  1. [root@localhost elfk]# curl --insecure -sfL https://10.17.1.44:1443/v3/import/867hj6vl9tfg7vqwc4xdnpck8f6pjw8hn4bjw9thksj5spbnwjprjh.yaml | kubectl apply -f -
  2. clusterrole.rbac.authorization.k8s.io/proxy-clusterrole-kubeapiserver unchanged
  3. clusterrolebinding.rbac.authorization.k8s.io/proxy-role-binding-kubernetes-master unchanged
  4. namespace/cattle-system unchanged
  5. serviceaccount/cattle unchanged
  6. clusterrolebinding.rbac.authorization.k8s.io/cattle-admin-binding unchanged
  7. secret/cattle-credentials-6375cce created
  8. clusterrole.rbac.authorization.k8s.io/cattle-admin unchanged
  9. deployment.apps/cattle-cluster-agent configured
  10. daemonset.apps/cattle-node-agent configured
  11. 内网环境的k8s端 管控正常
  12. [root@localhost elfk]# kubectl get pods -A
  13. NAMESPACE           NAME                                                       READY   STATUS    RESTARTS   AGE
  14. cattle-prometheus   exporter-kube-state-cluster-monitoring-dcf459bb8-t8qnj     1/1     Running   0          98m
  15. cattle-prometheus   exporter-node-cluster-monitoring-9kdvj                     1/1     Running   0          98m
  16. cattle-prometheus   grafana-cluster-monitoring-698d79ff64-tv8hx                2/2     Running   0          98m
  17. cattle-prometheus   prometheus-cluster-monitoring-0                            5/5     Running   1          95m
  18. cattle-prometheus   prometheus-operator-monitoring-operator-5f5d4c5987-8fjtq   1/1     Running   0          98m
  19. cattle-system       cattle-cluster-agent-56c4d48669-dpftm                      1/1     Running   0          73s
  20. cattle-system       cattle-node-agent-p8r5x                                    1/1     Running   0          69s
  21. ingress-nginx       nginx-ingress-controller-74879f74c6-jdzx9                  1/1     Running   0          25h
  22. kong                ingress-kong-d7b5d68f4-j6tsx                               2/2     Running   2          25h
  23. kube-system         calico-kube-controllers-69cb4d4df7-447m5                   1/1     Running   0          25h
  24. kube-system         calico-node-7cb2w                                          1/1     Running   0          25h
  25. kube-system         coredns-9d85f5447-x5l4c                                    1/1     Running   0          26h
  26. kube-system         coredns-9d85f5447-zqgh7                                    1/1     Running   0          26h
  27. kube-system         etcd-localhost                                             1/1     Running   0          26h
  28. kube-system         kube-apiserver-localhost                                   1/1     Running   0          26h
  29. kube-system         kube-controller-manager-localhost                          1/1     Running   0          26h
  30. kube-system         kube-proxy-gdtdt                                           1/1     Running   0          26h
  31. kube-system         kube-scheduler-localhost                                   1/1     Running   0          26h
  32. kube-system         metrics-server-6fcdc7bddc-ggsnm                            1/1     Running   0          25h

临时环境的rancher 失去对内网k8s的管控

内网环境的rancher接管对内网k8s的管控

此实验在临时环境同时跑两个rancher（端口差别）验证也是如此

使用rancher 的kubeconfig管控k8s集群

  1. [root@mobanji .kube]# vim config
  2. apiVersion: v1
  3. kind: Config
  4. clusters:
  5. - name: "linshi"
  6.   cluster:
  7.     server: "https://4xx.1xx.6x.1x6/k8s/clusters/c-tgrbh"
  8.     certificate-authority-data: "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJpVENDQ\
  9.       VM2Z0F3SUJBZ0lCQURBS0JnZ3Foa2pPUFFRREFqQTdNUnd3R2dZRFZRUUtFeE5rZVc1aGJXbGoKY\
  10.       kdsemRHVnVaWEl0YjNKbk1Sc3dHUVlEVlFRREV4SmtlVzVoYldsamJHbHpkR1Z1WlhJdFkyRXdIa\
  11.       GNOTWpBdwpOekUxTURrMU56VXlXaGNOTXpBd056RXpNRGsxTnpVeVdqQTdNUnd3R2dZRFZRUUtFe\
  12.       E5rZVc1aGJXbGpiR2x6CmRHVnVaWEl0YjNKbk1Sc3dHUVlEVlFRREV4SmtlVzVoYldsamJHbHpkR\
  13.       1Z1WlhJdFkyRXdXVEFUQmdjcWhrak8KUFFJQkJnZ3Foa2pPUFFNQkJ3TkNBQVIza3pSWnV4UDVia\
  14.       npjd0lGVkNTcHdHZFZ2d281M1Q5b1pwajBOczhuVApVemg1VVFUNHVPYzE4QytYZVUvZkdyM3QrV\
  15.       0Q4bU0vRDVaaHc3L0ZuTWw0b295TXdJVEFPQmdOVkhROEJBZjhFCkJBTUNBcVF3RHdZRFZSMFRBU\
  16.       UgvQkFVd0F3RUIvekFLQmdncWhrak9QUVFEQWdOSkFEQkdBaUVBd2JaRmRBbEkKSWVJNlBrODdsU\
  17.       kJTNVh3eDk3NHNGUHpIL3RCRTUxMnpSOVFDSVFEbWtDZWpoa1paZlhocG1LWHdCMjc2ek1Odwpzc\
  18.       zdYdFdRY25Hc1JKNjJpZkE9PQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0t"
  20. users:
  21. - name: "linshi"
  22.   user:
  23.     token: "kubeconfig-user-rjd7z:z4lw5wcchlmf5ncjcss7hw7rrspcrt8jxcv29xxmlrtmjchw6kp8fc"
  25. contexts:
  26. - name: "linshi"
  27.   context:
  28.     user: "linshi"
  29.     cluster: "linshi"
  31. current-context: "linshi"
  33. [root@mobanji .kube]# kubectl get pods -A
  34. NAMESPACE       NAME                                                   READY   STATUS      RESTARTS   AGE
  35. arms-prom       arms-prometheus-ack-arms-prometheus-7b4d578f86-ff824   1/1     Running     0          69m
  36. arms-prom       kube-state-metrics-864b9c5857-ljb6l                    1/1     Running     0          70m
  37. arms-prom       node-exporter-6ttg5                                    2/2     Running     0          70m
  38. arms-prom       node-exporter-rz7rr                                    2/2     Running     0          70m
  39. arms-prom       node-exporter-t45zj                                    2/2     Running     0          70m
  40. cattle-system   cattle-cluster-agent-57c67fb54c-6pr9q                  1/1     Running     0          22m
  41. cattle-system   cattle-node-agent-44d7g                                1/1     Running     0          40m
  42. cattle-system   cattle-node-agent-f2b62                                0/1     Pending     0          22m
  43. cattle-system   cattle-node-agent-qg86b                                1/1     Running     0          40m
  44. kube-system     ack-node-problem-detector-daemonset-2r9bg              1/1     Running     0          69m
  45. kube-system     ack-node-problem-detector-daemonset-mjk4k              1/1     Running     0          69m
  46. kube-system     ack-node-problem-detector-daemonset-t94p4              1/1     Running     0          69m
  47. kube-system     ack-node-problem-detector-eventer-6cb57ffb68-gl5n5     1/1     Running     0          70m
  48. kube-system     alibaba-log-controller-795d7486f8-jrcv2                1/1     Running     2          70m
  49. kube-system     alicloud-application-controller-bc84954fb-z5dq9        1/1     Running     0          70m
  50. kube-system     alicloud-monitor-controller-7c8c5485f4-xdrdd           1/1     Running     0          70m
  51. kube-system     aliyun-acr-credential-helper-59b59477df-p7vxc          1/1     Running     0          70m
  52. kube-system     coredns-79989b94b6-47vll                               1/1     Running     0          70m
  53. kube-system     coredns-79989b94b6-dqpjm                               1/1     Running     0          70m
  54. kube-system     csi-plugin-2kjc9                                       9/9     Running     0          70m
  55. kube-system     csi-plugin-5lt7b                                       9/9     Running     0          70m
  56. kube-system     csi-plugin-px52m                                       9/9     Running     0          70m
  57. kube-system     csi-provisioner-56d7fb44b6-6czqx                       8/8     Running     0          70m
  58. kube-system     csi-provisioner-56d7fb44b6-jqsrt                       8/8     Running     1          70m
  59. kube-system     kube-eventer-init-mv2vj                                0/1     Completed   0          70m
  60. kube-system     kube-flannel-ds-4xbhr                                  1/1     Running     0          70m
  61. kube-system     kube-flannel-ds-mfg7m                                  1/1     Running     0          70m
  62. kube-system     kube-flannel-ds-wnrp2                                  1/1     Running     0          70m
  63. kube-system     kube-proxy-worker-44tkt                                1/1     Running     0          70m
  64. kube-system     kube-proxy-worker-nw2g6                                1/1     Running     0          70m
  65. kube-system     kube-proxy-worker-s78vl                                1/1     Running     0          70m
  66. kube-system     logtail-ds-67lkm                                       1/1     Running     0          70m
  67. kube-system     logtail-ds-68fdz                                       1/1     Running     0          70m
  68. kube-system     logtail-ds-bkntm                                       1/1     Running     0          70m
  69. kube-system     metrics-server-f88f9b8d8-l9zl4                         1/1     Running     0          70m
  70. kube-system     nginx-ingress-controller-758cdc676c-k8ffj              1/1     Running     0          70m
  71. kube-system     nginx-ingress-controller-758cdc676c-pxzxd              1/1     Running     0          70m

这说明使用rancher的kubeconfig可以给特定集群进行管控

现在换回原来的看是否可以管控

  1. [root@mobanji .kube]# mv config.bak02 config
  2. mv：是否覆盖"config"？ y
  4. [root@mobanji .kube]# kubectl get pods -A
  5. NAMESPACE       NAME                                                   READY   STATUS      RESTARTS   AGE
  6. arms-prom       arms-prometheus-ack-arms-prometheus-7b4d578f86-ff824   1/1     Running     0          71m
  7. arms-prom       kube-state-metrics-864b9c5857-ljb6l                    1/1     Running     0          71m
  8. arms-prom       node-exporter-6ttg5                                    2/2     Running     0          71m
  9. arms-prom       node-exporter-rz7rr                                    2/2     Running     0          71m
  10. arms-prom       node-exporter-t45zj                                    2/2     Running     0          71m
  11. cattle-system   cattle-cluster-agent-57c67fb54c-6pr9q                  1/1     Running     0          24m
  12. cattle-system   cattle-node-agent-44d7g                                1/1     Running     0          41m
  13. cattle-system   cattle-node-agent-f2b62                                0/1     Pending     0          24m
  14. cattle-system   cattle-node-agent-qg86b                                1/1     Running     0          41m
  15. kube-system     ack-node-problem-detector-daemonset-2r9bg              1/1     Running     0          71m
  16. kube-system     ack-node-problem-detector-daemonset-mjk4k              1/1     Running     0          71m
  17. kube-system     ack-node-problem-detector-daemonset-t94p4              1/1     Running     0          71m
  18. kube-system     ack-node-problem-detector-eventer-6cb57ffb68-gl5n5     1/1     Running     0          71m
  19. kube-system     alibaba-log-controller-795d7486f8-jrcv2                1/1     Running     2          71m
  20. kube-system     alicloud-application-controller-bc84954fb-z5dq9        1/1     Running     0          71m
  21. kube-system     alicloud-monitor-controller-7c8c5485f4-xdrdd           1/1     Running     0          71m
  22. kube-system     aliyun-acr-credential-helper-59b59477df-p7vxc          1/1     Running     0          71m
  23. kube-system     coredns-79989b94b6-47vll                               1/1     Running     0          71m
  24. kube-system     coredns-79989b94b6-dqpjm                               1/1     Running     0          71m
  25. kube-system     csi-plugin-2kjc9                                       9/9     Running     0          71m
  26. kube-system     csi-plugin-5lt7b                                       9/9     Running     0          71m
  27. kube-system     csi-plugin-px52m                                       9/9     Running     0          71m
  28. kube-system     csi-provisioner-56d7fb44b6-6czqx                       8/8     Running     0          71m
  29. kube-system     csi-provisioner-56d7fb44b6-jqsrt                       8/8     Running     1          71m
  30. kube-system     kube-eventer-init-mv2vj                                0/1     Completed   0          71m
  31. kube-system     kube-flannel-ds-4xbhr                                  1/1     Running     0          71m
  32. kube-system     kube-flannel-ds-mfg7m                                  1/1     Running     0          71m
  33. kube-system     kube-flannel-ds-wnrp2                                  1/1     Running     0          71m
  34. kube-system     kube-proxy-worker-44tkt                                1/1     Running     0          71m
  35. kube-system     kube-proxy-worker-nw2g6                                1/1     Running     0          71m
  36. kube-system     kube-proxy-worker-s78vl                                1/1     Running     0          71m
  37. kube-system     logtail-ds-67lkm                                       1/1     Running     0          71m
  38. kube-system     logtail-ds-68fdz                                       1/1     Running     0          71m
  39. kube-system     logtail-ds-bkntm                                       1/1     Running     0          71m
  40. kube-system     metrics-server-f88f9b8d8-l9zl4                         1/1     Running     0          71m
  41. kube-system     nginx-ingress-controller-758cdc676c-k8ffj              1/1     Running     0          71m
  42. 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上是出现的

资源不足导致竞争，而且凉掉

k8s多集群配置管理平台的更多相关文章

  1. 基于k8s的集群稳定架构

    前言 我司的集群时刻处于崩溃的边缘,通过近三个月的掌握,发现我司的集群不稳定的原因有以下几点: 1.发版流程不稳定 2.缺少监控平台[最重要的原因] 3.缺少日志系统 4.极度缺少有关操作文档 5.请 ...

  2. 基于k8s的集群稳定架构-转载

    基于k8s的集群稳定架构-转载 前言 我司的集群时刻处于崩溃的边缘,通过近三个月的掌握,发现我司的集群不稳定的原因有以下几点: 1.发版流程不稳定 2.缺少监控平台[最重要的原因] 3.缺少日志系统 ...

  3. k8s docker集群搭建

    一.Kubernetes系列之介绍篇   •Kubernetes介绍 1.背景介绍 云计算飞速发展 - IaaS - PaaS - SaaS Docker技术突飞猛进 - 一次构建,到处运行 - 容器 ...

  4. Kubernetes(k8s) docker集群搭建

    原文地址:https://blog.csdn.net/real_myth/article/details/78719244 一.Kubernetes系列之介绍篇   •Kubernetes介绍 1.背 ...

  5. k8s极简史：K8s多集群技术发展的历史、现状与未来

    引子 随着云原生技术的普及,越来越多的企业使用Kubernetes来管理应用,并且集群规模也呈爆发式增长,企业也亟需应对随集群规模增长而带来的各种挑战.同时,为了更好地提供高可用.弹性伸缩的应用,企业 ...

  6. 基于 Clusternet 与 OCM 打造新一代开放的多集群管理平台

    背景 随着 5G.物联网设备的爆炸性增长以及智能终端不断增强的计算能力,带来了前所未有的数据量,传统的中心集中式计算捉襟见肘."新基建"战略的实施,工业互联网.车联网/自动驾驶.智 ...

  7. 这一篇 K8S(Kubernetes)集群部署 我觉得还可以！！！

    点赞再看,养成习惯,微信搜索[牧小农]关注我获取更多资讯,风里雨里,小农等你,很高兴能够成为你的朋友. 国内安装K8S的四种途径 Kubernetes 的安装其实并不复杂,因为Kubernetes 属 ...

  8. 腾讯发布 K8s 多集群管理开源项目 Clusternet

    11月4日,在腾讯数字生态大会上,腾讯宣布了云原生领域一项重磅开源进展-- K8s 多集群管理项目 Clusternet 正式开源. Clusternet 由腾讯联合多点生活.QQ音乐.富途证券.微众 ...

  9. 基于zookeeper+mesos+marathon的docker集群管理平台

    参考文档: mesos:http://mesos.apache.org/ mesosphere社区版:https://github.com/mesosphere/open-docs mesospher ...

随机推荐

  1. Web Performance API

    Web Performance API 性能监测/性能优化 https://developer.mozilla.org/en-US/docs/Web/API/Performance https://d ...

  2. Android Studio show whitespace & Android studio 设置注释缩进

    Android Studio show whitespace & Android studio 设置注释缩进 https://github.com/xgqfrms/flutter/issues ...

  3. 呼叫河马——搭建在NGK公链上的去中心化智能合约DAPP

    基于区块链技术发展的DAPP是一种分布式应用生态系统.目前最受DAPP欢迎的区块链有以太坊.EOS.波场等公链. 但由于当前 EOS资源模型的局限性,使得其使用成本较高.尽管 EOS的DPOS共识机制 ...

  4. 对DevOps的九大误解，是时候纠正了！

    DevOps是开发和运维的结合,有助于集成和自动化测试过程以及部署存储库,还提供了透明度以及灵活性.DevOps的目标如下: ●更快的上市时间(TTM). ●减少各种修复之间的前置时间.●提高部署频率 ...

  5. epoll使用

    epoll通过下面3个epoll系统调用为用户提供服务. (1)epoll_create系统调用 epoll_create在C库中的原型如下: int epoll_create(int size); ...

  6. Hbase ——Not only SQL

    HBase -- NoSQL_Not Only SQL NoSQL数据库: 不遵循传统的RDBMS模型 解决数据库的可伸缩性和可用性(多机器) 数据是非关系的(可切分),不使用sql语句 不针对原子性 ...

  7. JS判断对象是否包含某个属性

    1.使用hasOwnProperty()判断 hasOwnProperty方法的参数就是要判断的属性名称,当对象的属性存在时返回true,否则返回false. var obj = { name:'ja ...

  8. Svelte v2 已经过时了！

    带你走马观花,细看新版变化. 注意:原文发表于2018-04-18,随着框架不断演进,部分内容可能已不适用. 大约是一年之前,我们首次在 Svelte 的 issue 跟踪器上讨论过 v2 版本,现在 ...

  9. 大数据开发-Spark-Streaming处理数据到mysql

    前面一篇讲到streamin读取kafka数据加工处理后写到kafka数据,大数据开发-Spark-开发Streaming处理数据 && 写入Kafka是针对比如推荐领域,实时标签等场 ...

  10. wxWidgets源码分析(3) - 消息映射表

    目录 消息映射表 静态消息映射表 静态消息映射表处理过程 动态消息映射表 动态消息映射表处理过程 消息映射表 消息是GUI程序的核心,所有的操作行为均通过消息传递. 静态消息映射表 使用静态Event ...