- [Instructor] Okay, welcome back. In this lecture, we'll now deploy the API into the cluster. In this lecture, we'll provision the following communities' resources, a deployment consisting of four pods using the Cloud Academy, API, Version 1 Docker Image, which will serve, TCP traffic on port 80/80. The deployment will be configured for rolling updates and have liveness and readiness probes configured. 

The MongoDB replica set connection string will be passed in as an environment variable, specified on the container itself. We'll also create a service, which will provide a stable, private VEP and provide internal wide balancing over the four API Pods. And finally, we will create an ingress, which will forward external TCP port 80 traffic to the API service backing, listening on port 80/80. Okay, let's start. Within the terminal, I'll first navigate into the Voteapp kubernetes project directory. 

We will use the tree command to examine the directory structure, like so. Next, I'll use the kubectl command to perform an audit deployment of the files stored within the API Directory. We can do this by simply running the following command. kubectl apply -f, and the folder name, in this case API. 

Okay, let's now take a look at the current state of the Pods. And, as you can see, the API-Pods have successfully been provisioned. We can then take a closer look at the status of the API-Pods by, examining the logs at the Pod level, by running the following commands. kubectl get pods -o wide. This will allow us to see the Pod name. We take the Pod name, and then we run the command, kubectl logs pod name. Here, we can see that the API-Pod has indeed successfully connected to our backing BongoDB replica set, that we set up in the previous lecture. 

We can now also test the API, by using the curl command, aimed directly at the actual API Pod. In this case, we're using the Pod's internal API address and using curl to connect to it on port 80/80. So this looks really good. Next, let's now query their registered services. 

Well run the command, kubectl get services. Here we can take the service API address that was generated for the API service and again use the curl command to navigate via the VIP that was registered for the API service, like so. In fact, we can run this command within a loop to have the service load balancing round robin our request across the backend API pods. 

Okay, the API configuration is now complete. We'll delay testing it externally for now, as the nginx ingress controller hasn't yet been deployed. Instead, we'll move on and deploy the front end into the cluster.