search

DataONEorg / k8s-cluster

Documentation on the DataONE Kubernetes cluster
Apache License 2.0
2 stars 1 forks source link

Expand K8s onto k8s-node-4, 5, and 6 #31

Closed nickatnceas closed 1 year ago

nickatnceas commented 2 years ago

Three VMs, k8s-node-4, k8s-node-5, and k8s-node-6 have been provisioned for K8s over in https://github.nceas.ucsb.edu/NCEAS/Computing/issues/98

The physical: virtual layout of these VMs is:

host-ucsb-6: k8s-node-1
host-ucsb-7: k8s-node-2
host-ucsb-8: k8s-node-3
host-ucsb-9: k8s-node-4
host-ucsb-10: k8s-node-5
host-ucsb-11: k8s-node-6
nickatnceas commented 1 year ago

link to #36

nickatnceas commented 1 year ago

Work for this ticket was also documented in https://github.nceas.ucsb.edu/NCEAS/Computing/issues/98

nickatnceas commented 1 year ago

I added k8s-node-4 to the production cluster and moved some pods onto it. The pods appear to be running properly on the new node. I re-read the notes in https://github.nceas.ucsb.edu/NCEAS/Computing/issues/98 and am not seeing the same issues.

metadig@docker-ucsb-4:~$ kubectl get pods -A -o wide | grep k8s-node-4
ceph-csi-cephfs   ceph-csi-cephfs-csi-cephfsplugin-slnlp         3/3     Running      14 (38m ago)     67m    128.111.85.209   k8s-node-4      <none>           <none>
ceph-csi-cephfs   ceph-csi-cephfs-provisioner-5f465c8b64-kj2qw   6/6     Running      0                13m    192.168.55.133   k8s-node-4      <none>           <none>
ceph-csi-rbd      ceph-csi-rbd-csi-cephrbdplugin-vqgtg           3/3     Running      14 (38m ago)     67m    128.111.85.209   k8s-node-4      <none>           <none>
ceph-csi-rbd      ceph-csi-rbd-provisioner-6945954b55-9s46w      7/7     Running      0                13m    192.168.55.132   k8s-node-4      <none>           <none>
cert-manager      cert-manager-6c576bddcf-8cbnj                  1/1     Running      0                13m    192.168.55.138   k8s-node-4      <none>           <none>
cert-manager      cert-manager-cainjector-669c966b86-j6krg       1/1     Running      0                13m    192.168.55.129   k8s-node-4      <none>           <none>
cert-manager      cert-manager-webhook-7ff944cc49-xshkv          1/1     Running      0                13m    192.168.55.137   k8s-node-4      <none>           <none>
ingress-nginx     ingress-nginx-controller-8b88b8bc8-mrmsw       1/1     Running      0                13m    192.168.55.140   k8s-node-4      <none>           <none>
kube-system       calico-node-wsh4l                              1/1     Running      3 (44m ago)      67m    128.111.85.209   k8s-node-4      <none>           <none>
kube-system       coredns-57d8848788-8rbbm                       1/1     Running      0                13m    192.168.55.130   k8s-node-4      <none>           <none>
kube-system       kube-proxy-hl888                               1/1     Running      4 (38m ago)      67m    128.111.85.209   k8s-node-4      <none>           <none>
metadig           metadig-postgres-656f5975d4-xc7cq              2/2     Running      0                13m    192.168.55.139   k8s-node-4      <none>           <none>
metadig           metadig-rabbitmq-0                             1/1     Running      0                11m    192.168.55.141   k8s-node-4      <none>           <none>
metadig           metadig-worker-6b9bdb9445-d8l4s                1/1     Running      0                13m    192.168.55.136   k8s-node-4      <none>           <none>
metadig           metadig-worker-6b9bdb9445-gckzt                1/1     Running      0                13m    192.168.55.135   k8s-node-4      <none>           <none>
metadig           metadig-worker-6b9bdb9445-l6v4z                1/1     Running      0                13m    192.168.55.134   k8s-node-4      <none>           <none>
purser            purser-76fbcfc9c-qkvc9                         1/1     Running      0                13m    192.168.55.131   k8s-node-4      <none>           <none>
nickatnceas commented 1 year ago

I added k8s-node-5 and k8s-node-6 as well. All three new nodes appear to be operating properly:

metadig@docker-ucsb-4:~$ kubectl get nodes
NAME            STATUS   ROLES                  AGE      VERSION
docker-ucsb-4   Ready    control-plane,master   2y266d   v1.23.4
docker-ucsb-5   Ready    <none>                 531d     v1.23.4
docker-ucsb-6   Ready    <none>                 2y265d   v1.23.4
docker-ucsb-7   Ready    <none>                 2y265d   v1.23.4
k8s-node-4      Ready    <none>                 4h43m    v1.23.4
k8s-node-5      Ready    <none>                 3h13m    v1.23.4
k8s-node-6      Ready    <none>                 3h10m    v1.23.4