Master Docker basics, Kubernetes architecture, and cluster management. Delve into creating Dockerfiles and setting up Kubernetes on Azure using Helm charts for efficient container orchestration.

final.tar.gz

APP_ID

PASSWORD

TENANT

RESOURCE_GROUP

CLUSTER_NAME

hello

With the huge shift in the technological world, from running servers on local premises to the cloud, the need for containerization has increased. Kubernetes is a powerful open-source platform to manage containers and their services. This course provides an understanding of Docker and Kubernetes.

You will start with the basics of Docker and an introduction to containers and images. Next, you'll learn to create Dockerfile for building images. Then, you’ll learn about Kubernetes, Kubernetes clusters, nodes, and their working. You will finish this course by setting up your own Kubernetes cluster on top of Azure and using the Helm chart to manage it.

In the 4 years (2015-2019), Kubernetes job searches grew by 2,125% and are continuing to grow. Therefore, understanding the basics of Kubernetes, its architecture, and its working would help you land roles like that of a DevOps engineer and a cloud architect.

Running Kubernetes Cluster using Azure Kubernetes Service

## Some commands related to deployments
The table below contains some of the useful commands for deployment. Try these commands out in the terminal below the table.

align-center

## Observations

 In the above terminal:
- `kubectl apply -f https://k8s.io/examples/controllers/nginx-deployment.yaml`: Creates deployment.
- `kubectl get deployments`: Gets list of deployments that include recently created `nginx-deployment`.
- `kubectl rollout pause deployment/nginx-deployment`: The deployment rollout gets paused.
- `kubectl get rs`: Here, no replica set appears because the rollout process has been paused.
- `kubectl rollout resume deployment/nginx-deployment`: Resumes the rollout process.
- `kubectl rollout status deployment/nginx-deployment`: Shows the rollout process status.
- `kubectl get rs`: A replica set gets listed as the rollout process is completed.
- `kubectl get pods`: We can see a total of three Pods in running or launching state, as specified in the deployment file.
- `kubectl describe deployments`: The deployment description shows the Nginx image of version 1.14.2.
- `kubectl set image deployment/nginx-deployment nginx=nginx:1.16.1`: Updates the image version from 1.14.2 to 1.16.1.
- `kubectl rollout status deployment/nginx-deployment`: Shows the rollout status of the deployment.
- `kubectl describe deployments`: As we can see, the deployment description now shows an Nginx image of version 1.16.1.
- `kubectl get pods`: On running this, we can see only three Pods will be in the running or about to run the state. Other old pods are getting terminated.
- `kubectl rollout undo deployment/nginx-deployment`: Rolls back to the previous version of deployment.
- `kubectl rollout status deployment/nginx-deployment`: Shows the rollback status.
- `kubectl describe deployment nginx-deployment`: We can see that the deployment description shows an Nginx image of version 1.14.2.
- `kubectl get pods`: Again, we can see only three Pods in the running or launching state. The old Pods are getting terminated.
- `kubectl scale deployment/nginx-deployment --replicas=10`: Increases the number of Pods.
- `kubectl get pods`: Earlier, there were three Pods in running state, which now gets increased to 10.
- `kubectl scale deployment/nginx-deployment --replicas=2`: Scales down the number of Pods to two.
- `kubectl get pods`: Earlier, there were 10 Pods in running state, which now gets reduced to two.
- `kubectl delete deployment nginx-deployment`: Deletes the deployment.
- `kubectl get pods`: Now, no pods are available. All Pods get deleted along with the deployment.
- `kubectl get rs`: No replica set is available because the replica set gets deleted along with the deployment.

# Some commands related to deployments
The table below contains some of the useful commands for deployment. Try these commands out in the terminal below the table.

# Observations

 In the above terminal:
- `kubectl apply -f https://k8s.io/examples/controllers/nginx-deployment.yaml`: Creates deployment.
- `kubectl get deployments`: Gets list of deployments that include recently created `nginx-deployment`.
- `kubectl rollout pause deployment/nginx-deployment`: The deployment rollout gets paused.
- `kubectl get rs`: Here, no replica set appears because the rollout process has been paused.
- `kubectl rollout resume deployment/nginx-deployment`: Resumes the rollout process.
- `kubectl rollout status deployment/nginx-deployment`: Shows the rollout process status.
- `kubectl get rs`: A replica set gets listed as the rollout process is completed.
- `kubectl get pods`: We can see a total of three Pods in running or launching state, as specified in the deployment file.
- `kubectl describe deployments`: The deployment description shows the Nginx image of version 1.14.2.
- `kubectl set image deployment/nginx-deployment nginx=nginx:1.16.1`: Updates the image version from 1.14.2 to 1.16.1.
- `kubectl rollout status deployment/nginx-deployment`: Shows the rollout status of the deployment.
- `kubectl describe deployments`: As we can see, the deployment description now shows an Nginx image of version 1.16.1.
- `kubectl get pods`: On running this, we can see only three Pods will be in the running or about to run the state. Other old pods are getting terminated.
- `kubectl rollout undo deployment/nginx-deployment`: Rolls back to the previous version of deployment.
- `kubectl rollout status deployment/nginx-deployment`: Shows the rollback status.
- `kubectl describe deployment nginx-deployment`: We can see that the deployment description shows an Nginx image of version 1.14.2.
- `kubectl get pods`: Again, we can see only three Pods in the running or launching state. The old Pods are getting terminated.
- `kubectl scale deployment/nginx-deployment --replicas=10`: Increases the number of Pods.
- `kubectl get pods`: Earlier, there were three Pods in running state, which now gets increased to 10.
- `kubectl scale deployment/nginx-deployment --replicas=2`: Scales down the number of Pods to two.
- `kubectl get pods`: Earlier, there were 10 Pods in running state, which now gets reduced to two.
- `kubectl delete deployment nginx-deployment`: Deletes the deployment.
- `kubectl get pods`: Now, no pods are available. All Pods get deleted along with the deployment.
- `kubectl get rs`: No replica set is available because the replica set gets deleted along with the deployment.

Try out some commands related to deployments like rollup, rollback, scale, and more.

Commands	Use
`kubectl rollout undo deployment/<depoyment_name>`	Rolls back to the previous version of specified deployment
`kubectl scale deployment/<deployment_name> --replicas=<number_of_pods>`	Scales the number of Pods in the specified deployment
`kubectl autoscale deployment/<depolyment_name> --min=10 --max=15 --cpu-percent=80`	Auto scales the number of Pods in the specified deployment as per need to a certain maximum and minimum
`kubectl rollout pause deployment/<depolyment_name>`	Pauses the rollout of deployment
`kubectl rollout resume deployment/<depolyment_name>`	Resumes the rollout of deployment

Introduction

Docker

Docker Assessment

Kubernetes

Kubernetes Assessment

Deploying a Web Application over Kubernetes

Azure Kubernetes Services

Deploy an Application on AKS

Assessment of Azure Kubernetes Service

Application Management using Helm

Create Multiple Deployments Using Helm

Appendix

Working with Deployments

Some commands related to deployments

Observations