Skip to main content

Kubernetes: 18. Rollout and Rollback

Deployment

  • When a deployment is created, it triggers a rollout
  • Rollout creates a new revision (version)
  • In the future when new deployment is created,  a new rollout is created
  • The new rollout creates one more "new" version
  • These versions help to keep track of the changes and rollback if necessary
Deployment Strategy
  • First strategy is delete and recreate strategy. 
  • Delete all the existing pods and deploy the new updated pods
  • But this comes with application downtime
  • Second strategy and default strategy is Rolling update strategy
  • Kubernetes deletes one pod at a time in the older version and in its place creates a one pod at a time in the newer version
Update Strategy
  • Updates can be many things like updating the labels, docker image, replicas etc
  • These are directly updated into the deployment file and the changes are applied
  • When the changes are applied using kubectl apply command, a new rollout and a new revision is created
  • Another way to update the image name is to use the kubectl set image command. This will update the image name in the deployment. [CHECK THIS]
  • Using kubectl describe deployment on the recreate and rollout upgrade strategy gives insight about the deployment strategy
  • For recreate we can see that kubernetes creates the new replicaset, sets the old replicaset to zero
  • For rollout upgrade we can see that kubernetes decrements one replica at a time in old replicaset and increments one replica at a time in the new replicaset
  • At the end of the rollout the first replicaset will have 0 pods and the new replicaset have the desired pods
  • Now when we undo a rollback of deployment kubernetes sets replicas to 0 in the new replicaset and the desired number in the older replica set
  • At the end of the undo rollout the first replicaset will have desired pods and the new replicaset have the 0 pods

kubectl create -f <deployment-file>.yaml
-> Create a new deployment

kubectl get -f <deployment-file>.yaml
-> Get the status of the deployment

kubectl apply -f <deployment-definition>.yaml
-> Apply the new changes in the deployment file

kubectl rollout status deployment/<deployment-name> -n <namespace>
-> Get the rollout status of the deployment

kubectl rollout history deployment/<deployment-name> -n <namespace>
-> Get the rollout history of the deployment

kubectl set image deployment/<deployment-name> <container-name>=<new-image> -n <namespace>
-> Update the image name in the deployment file

kubectl get replicaset -n <namespace>
-> Gets the replicaset for the old and new deployments

kubectl rollout undo deployment/<deployment-name> -n <namespace>
-> Rollback the latest deployment


Labels:

Comments

Post a Comment

Popular posts from this blog

Kubernetes: 6. Imperative Commands

Imperative commands are useful in quickly creating the resources on Kubernetes kubectl --dry-run -> When created with this option, Kubernetes just validates the definition and does not actually create the resource -o=yaml -> Gets the output in YAML format kubectl run nginx-pod --image=nginx:alpine  -> Create a pod with name nginx-pod and image nginx:alpine kubectl run httpd --image=httpd:alpine  -> By default, run implies run-a-pod kubectl run redis --image=redis:alpine --labels=tier=db  -> Create a pod with name redis and image redis:alpine and labels set to tier=db kubectl run custom-nginx --image=nginx --port=8080  -> Create a pod with name custom-nginx and image nginx to run on port 8080 kubectl expose pod redis --port=6379 --name=redis-service  -> Create a service with name redis-service to expose pod named redis on service-port 6379 kubectl create deployment webapp --image=kodekloud/webapp-color --replicas=3  -> Create a depl...
Post a Comment
Read more

Kubernetes: 21. Secrets

Passwords In the webapps we store the properties file for storing and retrieving the data required by application But we never store the application passwords, truststore, keystore passwords etc here We might store them in an encrypted format, but storing them as plain text is not the correct way In Kubernetes we store these sensitive information in Secrets https://medium.com/avmconsulting-blog/secrets-management-in-kubernetes-378cbf8171d0 Secrets Secrets are used to store the sensitive information They are similar to ConfigMaps, except that they are stored in hashed or encoded format Note that they are only encoded (using base64) but are not encrypted So secrets are a safe option to store sensitive information but infact they are not the safest option As such secret objects should be not checked into source code tools, its best to store them encrypted at REST in ETCD Again as in ConfigMaps, we have to create the secrets object first and then inject them into the pods There are 2 ways ...
Post a Comment
Read more

Kubernetes: 19. Configure Application

Configuring application consists of Configuring commands and arguments on applications Configuring environment variables Configuring secrets Docker Commands docker run ubuntu  -> Runs ubuntu container and exit, container CMD is set to [bash], so the container quitely exits docker run ubuntu echo "Hello World" -> Runs ubuntu container, prints "Hello World" exits quitely. To update the default settings, create your own image from the base image lets call this ubuntu-sleeper image FROM ubuntu CMD sleep 5 CMD can also be mentioned in the JSON format like CMD ["sleep", "5"] Note that with JSON format the first element should always be the command to execute,  for eg, it CANNOT be ["sleep 5"] Run build the new ubuntu-sleeper image and run the new image docker build -t ubuntu-sleeper .  -> Build the image docker run ubuntu-sleeper -> Run the new image So the new image will launch ubuntu container, sleep for 5 seconds and quitely ex...
Post a Comment
Read more