Changes

Page history
Update Constructs authored by Irina Averin's avatar Irina Averin
Show whitespace changes
Inline Side-by-side
Kubernetes/Constructs.md
View page @ 44a82c5a
...@@ -101,7 +101,7 @@ kubectl get ingress ...@@ -101,7 +101,7 @@ kubectl get ingress
``` ```
If we want to view a particular Ingress If we want to view a particular Ingress
``` ```
kubectl get Ingress frontend-ingress kubectl get ingress frontend-ingress
``` ```
If you want to view a description of the Ingress If you want to view a description of the Ingress
``` ```
...@@ -113,7 +113,7 @@ A Job creates one or more Pods and ensures that a specified number of them succe ...@@ -113,7 +113,7 @@ A Job creates one or more Pods and ensures that a specified number of them succe
In our project, we found this useful for testing our controllers database connection. Rather than having a fully functional controller application, we built a test program that connected to our cluster, performed a simple selection and printed results. The test program was best suited as a job because we did not want the pod trying to select and print continuously, we just needed it to run once. In our project, we found this useful for testing our controllers database connection. Rather than having a fully functional controller application, we built a test program that connected to our cluster, performed a simple selection and printed results. The test program was best suited as a job because we did not want the pod trying to select and print continuously, we just needed it to run once.
Below is the YAML file, which we use to create a Job. As in the deployment we use the image from the GitLab pipeline and we have declared the Kubernetes secret. The main difference from a deployment is the `restartpolicy` being set to Never and a `backofflimit` is set to 0 to ensure the job runs once. We declare a command to execute a run of the program in *command: ["dotnet", "postgrestest.dll"]* so the program is triggered open creation like hitting the run button in IDE. Below is the YAML file, which we use to create a Job. As in the deployment we use the image from the GitLab pipeline and we have declared the Kubernetes secret. The main difference from a deployment is the `restartPolicy` being set to Never and a `backofflimit` is set to 0 to ensure the job runs once. We declare a command to execute a run of the program in *command: ["dotnet", "postgrestest.dll"]* so the program is triggered open creation like hitting the run button in IDE.
``` ```
...@@ -148,7 +148,7 @@ This returns all deployments however if we are just concerned with one deploymen ...@@ -148,7 +148,7 @@ This returns all deployments however if we are just concerned with one deploymen
``` ```
kubectl get job kubemoviejob kubectl get job kubemoviejob
``` ```
If we wanted to get more information on the jobs then we can use kubectl logs If we wanted to get more information on the jobs then we can use `kubectl logs`
``` ```
kubectl logs kubemoviejob kubectl logs kubemoviejob
``` ```
... ...
......