Chapter 7. Use cases 187
Delete the pod that is running in the public cloud, as shown in Example 7-29.
Example 7-29   Deleting the Pod from the public cloud
[root@ip-10-0-2-217 ~]# oc delete pod appmongo-ibm-mongodb-dev
pod "appmongo-ibm-mongodb-dev" deleted
[root@ip-10-0-2-217 ~]# oc get pod appmongo-ibm-mongodb-dev
Error from server (NotFound): pods "appmongo-ibm-mongodb-dev" not found
root@ip-10-0-2-217 ~]# 
Bring the pod up on-premises, as shown in Example 7-30.
Example 7-30   Bring Pod up at the on-premises cloud
[root@dcocp01 ~]# oc apply -f mongo_pod.yaml
pod/appmongo-ibm-mongodb-dev created
[root@dcocp01 ~]# oc get pod appmongo-ibm-mongodb-dev
NAME                       READY     STATUS    RESTARTS   AGE
appmongo-ibm-mongodb-dev   1/1       Running   0          1m
Now, open the restaurant database at the on-premises cluster, and again on the Aggregation 
tab. Look for the entry that was inserted in the public cloud. You can see the match, as shown 
in Figure 7-13.
Figure 7-13   Matching document created at the public cloud on-premises