终于,coredns也处于活动状态,集群已完全启动!
[root@ip-172-31-13-9 ~]# kubectl get pod --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
default cirros-deployment-86885fbf85-pkzqz 1/1 Running 0 47m
default cirros-deployment-86885fbf85-w4w6h 1/1 Running 0 47m
kube-system config-zookeeper-l8m9l 1/1 Running 0 24m
kube-system config-zookeeper-lvtmq 1/1 Running 0 24m
kube-system config-zookeeper-mzlgm 1/1 Running 0 24m
kube-system contrail-agent-jc4x2 2/2 Running 0 24m
kube-system contrail-agent-psk2v 2/2 Running 0 24m
kube-system contrail-analytics-hsm7w 3/3 Running 0 24m
kube-system contrail-analytics-vgwcb 3/3 Running 0 24m
kube-system contrail-analytics-xbpwf 3/3 Running 0 24m
kube-system contrail-config-database-nodemgr-7xvnb 1/1 Running 0 24m
kube-system contrail-config-database-nodemgr-9bznv 1/1 Running 0 24m
kube-system contrail-config-database-nodemgr-lqtkq 1/1 Running 0 24m
kube-system contrail-configdb-4svwg 1/1 Running 0 24m
kube-system contrail-configdb-gdvmc 1/1 Running 0 24m
kube-system contrail-configdb-sll25 1/1 Running 0 24m
kube-system contrail-controller-config-gmkpr 5/5 Running 0 24m
kube-system contrail-controller-config-q6rvx 5/5 Running 0 24m
kube-system contrail-controller-config-zbpjm 5/5 Running 0 24m
kube-system contrail-controller-control-4m9fd 4/4 Running 0 24m
kube-system contrail-controller-control-9klxh 4/4 Running 0 24m
kube-system contrail-controller-control-wk6jp 4/4 Running 0 24m
kube-system contrail-controller-webui-268bc 2/2 Running 0 24m
kube-system contrail-controller-webui-57dbf 2/2 Running 0 24m
kube-system contrail-controller-webui-z6c68 2/2 Running 0 24m
kube-system contrail-kube-manager-6nh9d 1/1 Running 0 24m
kube-system contrail-kube-manager-stqf5 1/1 Running 0 24m
kube-system contrail-kube-manager-wqgl4 1/1 Running 0 24m
kube-system coredns-7f865bd4f9-g8j8f 1/1 Running 0 13s
kube-system coredns-7f865bd4f9-zftsc 1/1 Running 0 13s
kube-system etcd-ip-172-31-13-9.ap-northeast-1.compute.internal 1/1 Running 0 82m
kube-system etcd-ip-172-31-32-58.ap-northeast-1.compute.internal 1/1 Running 0 81m
kube-system etcd-ip-172-31-8-73.ap-northeast-1.compute.internal 1/1 Running 0 79m
kube-system kube-apiserver-ip-172-31-13-9.ap-northeast-1.compute.internal 1/1 Running 0 82m
kube-system kube-apiserver-ip-172-31-32-58.ap-northeast-1.compute.internal 1/1 Running 1 81m
kube-system kube-apiserver-ip-172-31-8-73.ap-northeast-1.compute.internal 1/1 Running 1 80m
kube-system kube-controller-manager-ip-172-31-13-9.ap-northeast-1.compute.internal 1/1 Running 1 83m
kube-system kube-controller-manager-ip-172-31-32-58.ap-northeast-1.compute.internal 1/1 Running 0 80m
kube-system kube-controller-manager-ip-172-31-8-73.ap-northeast-1.compute.internal 1/1 Running 0 80m
kube-system kube-proxy-6ls9w 1/1 Running 0 81m
kube-system kube-proxy-82jl8 1/1 Running 0 80m
kube-system kube-proxy-bjdj9 1/1 Running 0 81m
kube-system kube-proxy-nd7hq 1/1 Running 0 80m
kube-system kube-proxy-rb7nk 1/1 Running 0 83m
kube-system kube-scheduler-ip-172-31-13-9.ap-northeast-1.compute.internal 1/1 Running 1 83m
kube-system kube-scheduler-ip-172-31-32-58.ap-northeast-1.compute.internal 1/1 Running 0 80m
kube-system kube-scheduler-ip-172-31-8-73.ap-northeast-1.compute.internal 1/1 Running 0 80m
kube-system rabbitmq-b6rpx 1/1 Running 0 24m
kube-system rabbitmq-gn67t 1/1 Running 0 24m
kube-system rabbitmq-r8dvb 1/1 Running 0 24m
kube-system redis-5qvbv 1/1 Running 0 24m
kube-system redis-8mck5 1/1 Running 0 24m
kube-system redis-9d9dv 1/1 Running 0 24m
[root@ip-172-31-13-9 ~]#
[root@ip-172-31-13-9 ~]# kubectl get deployment -n kube-system
NAME READY UP-TO-DATE AVAILABLE AGE
coredns 2/2 2 2 98m
[root@ip-172-31-13-9 ~]#
[root@ip-172-31-13-9 ~]# ./contrail-introspect-cli/ist.py ctr route summary
+----------------------------------------------------+----------+-------+---------------+-----------------+------------------+
| name | prefixes | paths | primary_paths | secondary_paths | infeasible_paths |
+----------------------------------------------------+----------+-------+---------------+-----------------+------------------+
| default-domain:default- | 0 | 0 | 0 | 0 | 0 |
| project:__link_local__:__link_local__.inet.0 | | | | | |
| default-domain:default-project:dci- | 0 | 0 | 0 | 0 | 0 |
| network:__default__.inet.0 | | | | | |
| default-domain:default-project:dci-network:dci- | 3 | 8 | 0 | 8 | 0 |
| network.inet.0 | | | | | |
| default-domain:default-project:default-virtual- | 0 | 0 | 0 | 0 | 0 |
| network:default-virtual-network.inet.0 | | | | | |
| inet.0 | 0 | 0 | 0 | 0 | 0 |
| default-domain:default-project:ip-fabric:ip- | 5 | 12 | 2 | 10 | 0 |
| fabric.inet.0 | | | | | |
| default-domain:k8s-default:k8s-default-pod-network | 5 | 14 | 4 | 10 | 0 |
| :k8s-default-pod-network.inet.0 | | | | | |
| default-domain:k8s-default:k8s-default-service- | 5 | 12 | 2 | 10 | 0 |
| network:k8s-default-service-network.inet.0 | | | | | |
+----------------------------------------------------+----------+-------+---------------+-----------------+------------------+
[root@ip-172-31-13-9 ~]#
由于MP-BGP支持两个集群之间的缝合(stitching),因此这些集群很容易扩展到多集群环境。
我将在附录部分描述此设置的详细信息。
(编者按:下一篇文章,我们将介绍关于OpenStack和vCenter的HA安装,以及在新的安装中选择什么标签的问题。)
·END·
Tungsten Fabric入门宝典系列文章——
1. 首次启动和运行指南
3. 编排器集成
Tungsten Fabric 架构解析系列文章——
添加描述
本文系外文翻译,前往查看
如有侵权,请联系 cloudcommunity@tencent.com 删除。
本文系外文翻译,前往查看
如有侵权,请联系 cloudcommunity@tencent.com 删除。