Running Our backend Deployment

With our Deployment manifest ready, let's deploy it onto our remote cluster. You should be familiar with the drill by now—simply run kubectl apply:

$ kubectl apply -f ./manifests/backend/deployment.yamldeployment.apps "backend" created

Check the status of the Deployment using kubectl get all:

$ kubectl get allNAME                           READY     STATUS    RESTARTS   AGEpod/backend-6d58f66658-6wx4f   1/1       Running   0          21spod/backend-6d58f66658-rzwnl   1/1       Running   0          21spod/backend-6d58f66658-wlsdz   1/1       Running   0          21spod/elasticsearch-0            1/1       Running   0          18hpod/elasticsearch-1            1/1       Running   0          20hpod/elasticsearch-2            1/1       Running   0          20hNAME                    TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)          service/elasticsearch   ClusterIP   None         <none>        9200/TCP,9300/TCPservice/kubernetes ClusterIP ...

Get Building Enterprise JavaScript Applications now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.