9.2.3 Verifying the Scaling Up

1. Verify the new OUDSM pod oudsm-2 has started:

   kubectl get pod,service -o wide -n <namespace> 

   For example:

   kubectl get pods,service -n oudsmns
   

   The output will look similar to the following:

   NAME          READY   STATUS    RESTARTS   AGE   IP            NODE            NOMINATED NODE   READINESS GATES
   pod/oudsm-1   1/1     Running   0          88m   10.244.0.19   <worker-node>   <none>           <none>
   pod/oudsm-2   1/1     Running   0          15m   10.245.3.45   <worker-node>   <none>           <none>
   	
   NAME                TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE   SELECTOR
   service/oudsm-1     ClusterIP   10.96.108.200   <none>        7001/TCP,7002/TCP   88m   app.kubernetes.io/instance=oudsm,app.kubernetes.io/name=oudsm,oudsm/instance=oudsm-1
   service/oudsm-2     ClusterIP   10.96.31.201    <none>        7001/TCP,7002/TCP   15m   app.kubernetes.io/instance=oudsm,app.kubernetes.io/name=oudsm,oudsm/instance=oudsm-2
   service/oudsm-lbr   ClusterIP   10.96.41.201    <none>        7001/TCP,7002/TCP   73m   app.kubernetes.io/instance=oudsm,app.kubernetes.io/name=oudsm
   

   Note:

   It will take several minutes before all the services listed above show. While the oudsm-2 pod has a STATUS of 0/1 the pod is started but the OUDSM server associated with it is currently starting. While the pod is starting, you can check the startup status in the pod log, by running the following command:

   kubectl logs oudsm-2 -n oudsmns