| Laura Fitzgerald I got access to the comm1 cluster and I have updated the tagging in AWS to distinguish between the infra's and compute nodes. Just in case we decide to go down the route of downgrading the cluster.
|
oc get nodes -L hostnames |
NAME STATUS ROLES AGE VERSION HOSTNAMES |
ip-10-10-0-26.eu-west-1.compute.internal Ready <none> 98d v1.9.1+a0ce1bc657 |
ip-10-10-0-29.eu-west-1.compute.internal Ready compute 98d v1.9.1+a0ce1bc657 |
ip-10-10-0-33.eu-west-1.compute.internal Ready master 98d v1.9.1+a0ce1bc657 |
ip-10-10-0-38.eu-west-1.compute.internal Ready compute 98d v1.9.1+a0ce1bc657 |
ip-10-10-0-45.eu-west-1.compute.internal Ready compute 98d v1.9.1+a0ce1bc657 |
ip-10-10-0-51.eu-west-1.compute.internal Ready <none> 98d v1.9.1+a0ce1bc657 |
ip-10-10-0-53.eu-west-1.compute.internal Ready compute 98d v1.9.1+a0ce1bc657 |
ip-10-10-0-58.eu-west-1.compute.internal Ready master 98d v1.9.1+a0ce1bc657 |
ip-10-10-0-60.eu-west-1.compute.internal Ready master 98d v1.9.1+a0ce1bc657
|
[root@ip-10-10-0-33 ~]# oc get -o wide pods |
NAME READY STATUS RESTARTS AGE IP NODE |
docker-registry-1-h4zfs 1/1 Running 0 98d 10.128.0.3 ip-10-10-0-26.eu-west-1.compute.internal |
docker-registry-1-kctsx 1/1 Running 0 98d 10.128.2.3 ip-10-10-0-51.eu-west-1.compute.internal |
registry-console-1-6kk9f 1/1 Running 1 98d 10.129.0.22 ip-10-10-0-60.eu-west-1.compute.internal |
router-1-kz9vm 1/1 Running 0 98d 10.10.0.26 ip-10-10-0-26.eu-west-1.compute.internal |
router-1-xmddl 1/1 Running 0 98d 10.10.0.51 ip-10-10-0-51.eu-west-1.compute.internal |
|
|
