Basic knowledge of Pod and ReplicaSet is suggested to follow this hands-on practice.Ĭreating a Deployment is the same as creating a ReplicaSet, but Deployment is the kind property’s value. Check KubeOne doc for a guide on getting a running Kubernetes cluster using KubeOne. You must have a running Kubernetes cluster with the kubectl command-line tool configured and connected to it to follow this exercise. We will create a Deployment that will roll out a ReplicaSet to bring up three instances of an nginx Pod. Also, using a declarative management style for Deployment allows it to bring the desired states of the defined application in a YAML file into reality. This means you can update or downgrade an application to the desired version without experiencing a user blackout as well as roll back to the previous version in case the new version is unstable or filled with bugs. It provides updates, control as well as rollback functionalities. What is a Deployment in Kubernetes?Ī Deployment is one of the Kubernetes objects that is used to manage Pods via ReplicaSets in a declarative way. Questions like why do we need Deployment, and the relationship between Deployment and ReplicaSet will be answered in this section.
You will learn how to use Deployment to create a Pod, upgrade or downgrade your application with zero downtime and other Deployment actions using hands-on practice in this part of the series. We will take a step further in this part by introducing you to Kubernetes Deployment. In the last part of this series, you learnt about ReplicaSet and its functionalities to make the management of Kubernetes applications easier.