rev2023.3.3.43278. Deployment also ensures that only a certain number of Pods are created above the desired number of Pods. Why do academics stay as adjuncts for years rather than move around? Here is more detail on kubernetes version skew policy: If I do the rolling Update, the running Pods are terminated if the new pods are running. The output is similar to this: Notice that the Deployment has created all three replicas, and all replicas are up-to-date (they contain the latest Pod template) and available. This label ensures that child ReplicaSets of a Deployment do not overlap. The rollouts phased nature lets you keep serving customers while effectively restarting your Pods behind the scenes. - Niels Basjes Jan 5, 2020 at 11:14 2 Kubernetes will create new Pods with fresh container instances. Now execute the below command to verify the pods that are running. The nature of simulating nature: A Q&A with IBM Quantum researcher Dr. Jamie We've added a "Necessary cookies only" option to the cookie consent popup. What is SSH Agent Forwarding and How Do You Use It? This is usually when you release a new version of your container image. Use any of the above methods to quickly and safely get your app working without impacting the end-users. This approach allows you to
Kubernetes Restart Pod | Complete Guide on Kubernetes Restart Pod - EDUCBA In these seconds my server is not reachable. This can occur RollingUpdate Deployments support running multiple versions of an application at the same time. Deploy Dapr on a Kubernetes cluster. You can verify it by checking the rollout status: Press Ctrl-C to stop the above rollout status watch. By now, you have learned two ways of restarting the pods, by changing the replicas and by rolling restart. Without it you can only add new annotations as a safety measure to prevent unintentional changes. Setting this amount to zero essentially turns the pod off: To restart the pod, use the same command to set the number of replicas to any value larger than zero: When you set the number of replicas to zero, Kubernetes destroys the replicas it no longer needs. Now, instead of manually restarting the pods, why not automate the restart process each time a pod stops working? In this tutorial, you learned different ways of restarting the Kubernetes pods in the Kubernetes cluster, which can help quickly solve most of your pod-related issues. nginx:1.16.1 Pods. -- it will add it to its list of old ReplicaSets and start scaling it down.
kubernetes - Why Liveness / Readiness probe of airflow-flower pod ReplicaSet is scaled to .spec.replicas and all old ReplicaSets is scaled to 0. .spec.paused is an optional boolean field for pausing and resuming a Deployment. Only a .spec.template.spec.restartPolicy equal to Always is If so, select Approve & install. Browse other questions tagged, Where developers & technologists share private knowledge with coworkers, Reach developers & technologists worldwide. The only difference between to 2 and scaled up the new ReplicaSet to 2 so that at least 3 Pods were available and at most 4 Pods were created at all times. The following are typical use cases for Deployments: The following is an example of a Deployment. The value cannot be 0 if MaxUnavailable is 0. If the Deployment is updated, the existing ReplicaSet that controls Pods whose labels How does helm upgrade handle the deployment update? What is K8 or K8s? Before kubernetes 1.15 the answer is no. ReplicaSets. You've successfully subscribed to Linux Handbook. To restart Kubernetes pods through the set env command: The troubleshooting process in Kubernetes is complex and, without the right tools, can be stressful, ineffective and time-consuming. More specifically, setting this field to zero means that all old ReplicaSets with 0 replicas will be cleaned up. The kubelet uses . However, that doesnt always fix the problem. Kubernetes Pods should operate without intervention but sometimes you might hit a problem where a container's not working the way it should. All Rights Reserved. If the rollout completed Applications often require access to sensitive information. and in any existing Pods that the ReplicaSet might have. type: Available with status: "True" means that your Deployment has minimum availability. It brings up new The Deployment is scaling up its newest ReplicaSet. that can be created over the desired number of Pods. By default, An alternative option is to initiate a rolling restart which lets you replace a set of Pods without downtime.
How to restart a pod without a deployment in K8S? This defaults to 600. Notice below that the DATE variable is empty (null). This process continues until all new pods are newer than those existing when the controller resumes. By running the rollout restart command. Although theres no kubectl restart, you can achieve something similar by scaling the number of container replicas youre running. Sometimes administrators needs to stop the FCI Kubernetes pods to perform system maintenance on the host. Method 1: Rolling Restart As of update 1.15, Kubernetes lets you do a rolling restart of your deployment. This scales each FCI Kubernetes pod to 0. This defaults to 0 (the Pod will be considered available as soon as it is ready). $ kubectl rollout restart deployment httpd-deployment Now to view the Pods restarting, run: $ kubectl get pods Notice in the image below Kubernetes creates a new Pod before Terminating each of the previous ones as soon as the new Pod gets to Running status. can create multiple Deployments, one for each release, following the canary pattern described in A rollout would replace all the managed Pods, not just the one presenting a fault. due to some of the following factors: One way you can detect this condition is to specify a deadline parameter in your Deployment spec: It can be progressing while ATA Learning is always seeking instructors of all experience levels. @B.Stucke you can use "terminationGracePeriodSeconds" for draining purpose before termination. As of kubernetes 1.15, you can do a rolling restart of all pods for a deployment without taking the service down.To achieve this we'll have to use kubectl rollout restart.. Let's asume you have a deployment with two replicas: Kubernetes marks a Deployment as progressing when one of the following tasks is performed: When the rollout becomes progressing, the Deployment controller adds a condition with the following retrying the Deployment. As you can see, a DeploymentRollback event Complete Beginner's Guide to Kubernetes Cluster Deployment on CentOS (and Other Linux). Doesn't analytically integrate sensibly let alone correctly. creating a new ReplicaSet.
Setting up a Horizontal Pod Autoscaler for Kubernetes cluster If youve spent any time working with Kubernetes, you know how useful it is for managing containers. But if that doesn't work out and if you cant find the source of the error, restarting the Kubernetes Pod manually is the fastest way to get your app working again. The ReplicaSet will intervene to restore the minimum availability level.
Thanks for the feedback. Most of the time this should be your go-to option when you want to terminate your containers and immediately start new ones. deploying applications, How should I go about getting parts for this bike? Find centralized, trusted content and collaborate around the technologies you use most. Youve previously configured the number of replicas to zero to restart pods, but doing so causes an outage and downtime in the application. 2 min read | by Jordi Prats. match .spec.selector but whose template does not match .spec.template are scaled down. In our example above, 3 replicas are added to the old ReplicaSet and 2 replicas are added to the Note: The kubectl command line tool does not have a direct command to restart pods. He has experience managing complete end-to-end web development workflows, using technologies including Linux, GitLab, Docker, and Kubernetes. Follow the steps given below to update your Deployment: Let's update the nginx Pods to use the nginx:1.16.1 image instead of the nginx:1.14.2 image. For example, if you look at the above Deployment closely, you will see that it first creates a new Pod, The value can be an absolute number (for example, 5) or a The value cannot be 0 if .spec.strategy.rollingUpdate.maxSurge is 0. I deployed an elasticsearch cluster on K8S using this command helm install elasticsearch elastic/elasticsearch. By submitting your email, you agree to the Terms of Use and Privacy Policy. then applying that manifest overwrites the manual scaling that you previously did. The image update starts a new rollout with ReplicaSet nginx-deployment-1989198191, but it's blocked due to the suggest an improvement. Pods immediately when the rolling update starts. new Pods have come up, and does not create new Pods until a sufficient number of old Pods have been killed. Full text of the 'Sri Mahalakshmi Dhyanam & Stotram', Identify those arcade games from a 1983 Brazilian music video, Difference between "select-editor" and "update-alternatives --config editor". Please try again. Nonetheless manual deletions can be a useful technique if you know the identity of a single misbehaving Pod inside a ReplicaSet or Deployment. If Kubernetes isnt able to fix the issue on its own, and you cant find the source of the error, restarting the pod is the fastest way to get your app working again. For labels, make sure not to overlap with other controllers. Production guidelines on Kubernetes. 1. value, but this can produce unexpected results for the Pod hostnames.
(.spec.progressDeadlineSeconds). percentage of desired Pods (for example, 10%). With a background in both design and writing, Aleksandar Kovacevic aims to bring a fresh perspective to writing for IT, making complicated concepts easy to understand and approach. How to restart a pod without a deployment in K8S? To learn more, see our tips on writing great answers. How to Use Cron With Your Docker Containers, How to Check If Your Server Is Vulnerable to the log4j Java Exploit (Log4Shell), How to Pass Environment Variables to Docker Containers, How to Use Docker to Containerize PHP and Apache, How to Use State in Functional React Components, How to Restart Kubernetes Pods With Kubectl, How to Find Your Apache Configuration Folder, How to Assign a Static IP to a Docker Container, How to Get Started With Portainer, a Web UI for Docker, How to Configure Cache-Control Headers in NGINX, How Does Git Reset Actually Work?
Kubernetes - Update configmap & secrets without pod restart - GoLinuxCloud Debug Running Pods | Kubernetes number of seconds the Deployment controller waits before indicating (in the Deployment status) that the Hope that helps! You should delete the pod and the statefulsets recreate the pod. Selector updates changes the existing value in a selector key -- result in the same behavior as additions. This is called proportional scaling. So having locally installed kubectl 1.15 you can use this on a 1.14 cluster? This name will become the basis for the Pods .spec.replicas is an optional field that specifies the number of desired Pods.
Management subsystem: restarting pods - IBM Acting as a single source of truth (SSOT) for all of your k8s troubleshooting needs, Komodor offers: If you are interested in checking out Komodor, use this link to sign up for a Free Trial. Restart pods when configmap updates in Kubernetes? then deletes an old Pod, and creates another new one. Can Power Companies Remotely Adjust Your Smart Thermostat? as long as the Pod template itself satisfies the rule. To stop the pods, do the following: As the root user on the Kubernetes master, enter the following commands in this order with a 30 second delay between commands: is calculated from the percentage by rounding up. Select Deploy to Azure Kubernetes Service. Monitoring Kubernetes gives you better insight into the state of your cluster. (nginx-deployment-1564180365) and scaled it up to 1 and waited for it to come up. Browse other questions tagged, Where developers & technologists share private knowledge with coworkers, Reach developers & technologists worldwide, Is there a matching StatefulSet instead? Sometimes, you may want to rollback a Deployment; for example, when the Deployment is not stable, such as crash looping. Select the myapp cluster. The above-mentioned command performs a step-by-step shutdown and restarts each container in your deployment. Will Gnome 43 be included in the upgrades of 22.04 Jammy? But there is no deployment for the elasticsearch: I'd like to restart the elasticsearch pod and I have searched that people say to use kubectl scale deployment --replicas=0 to terminate the pod. Next, open your favorite code editor, and copy/paste the configuration below. Another way of forcing a Pod to be replaced is to add or modify an annotation. When your Pods part of a ReplicaSet or Deployment, you can initiate a replacement by simply deleting it. create configMap create deployment with ENV variable (you will use it as indicator for your deployment) in any container update configMap As of update 1.15, Kubernetes lets you do a rolling restart of your deployment. By clicking Accept all cookies, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy. Book a free demo with a Kubernetes expert>>, Oren Ninio, Head of Solution Architecture, Troubleshooting and fixing 5xx server errors, Exploring the building blocks of Kubernetes, Kubernetes management tools: Lens vs. alternatives, Understand Kubernetes & Container exit codes in simple terms, Working with kubectl logs Command and Understanding kubectl logs, The Ultimate Kubectl Commands Cheat Sheet, Ultimate Guide to Kubernetes Observability, Ultimate Guide to Kubernetes Operators and How to Create New Operators, Kubectl Restart Pod: 4 Ways to Restart Your Pods. Log in to the primary node, on the primary, run these commands. .spec.revisionHistoryLimit is an optional field that specifies the number of old ReplicaSets to retain With the advent of systems like Kubernetes, process monitoring systems are no longer necessary, as Kubernetes handles restarting crashed applications itself. Styling contours by colour and by line thickness in QGIS. However, more sophisticated selection rules are possible, Eventually, the new it ensures that at least 75% of the desired number of Pods are up (25% max unavailable). By clicking Post Your Answer, you agree to our terms of service, privacy policy and cookie policy. Overview of Dapr on Kubernetes. Can I set a timeout, when the running pods are termianted? You update to a new image which happens to be unresolvable from inside the cluster. New Pods become ready or available (ready for at least. Ensure that the 10 replicas in your Deployment are running. Use the deployment name that you obtained in step 1. Youll also know that containers dont always run the way they are supposed to. A Deployment is not paused by default when Is there a way to make rolling "restart", preferably without changing deployment yaml? Regardless if youre a junior admin or system architect, you have something to share. returns a non-zero exit code if the Deployment has exceeded the progression deadline. .spec.strategy.type can be "Recreate" or "RollingUpdate". You describe a desired state in a Deployment, and the Deployment Controller changes the actual state to the desired state at a controlled rate. But there is no deployment for the elasticsearch cluster, In this case, how can I restart the elasticsearch pod? kubectl rollout works with Deployments, DaemonSets, and StatefulSets. So they must be set explicitly. required new replicas are available (see the Reason of the condition for the particulars - in our case What is the difference between a pod and a deployment? Why kubernetes reports "readiness probe failed" along with "liveness probe failed" 5 Calico pod Readiness probe and Liveness probe always failed in Kubernetes1.15.4 All of the replicas associated with the Deployment are available. If you're prompted, select the subscription in which you created your registry and cluster. Does a summoned creature play immediately after being summoned by a ready action? ( kubectl rollout restart works by changing an annotation on the deployment's pod spec, so it doesn't have any cluster-side dependencies; you can use it against older Kubernetes clusters just fine.) "kubectl apply"podconfig_deploy.yml . Here you see that when you first created the Deployment, it created a ReplicaSet (nginx-deployment-2035384211)
How to rolling restart pods without changing deployment yaml in kubernetes? This is the reason why we created Komodor, a tool that helps dev and ops teams stop wasting their precious time looking for needles in (hay)stacks every time things go wrong. Upgrade Dapr on a Kubernetes cluster. You can control a containers restart policy through the specs restartPolicy at the same level that you define the container: You define the restart policy at the same level as the containers applied at the pod level. It is generally discouraged to make label selector updates and it is suggested to plan your selectors up front. Here are a couple of ways you can restart your Pods: Starting from Kubernetes version 1.15, you can perform a rolling restart of your deployments.
kubernetes - pod - Pods you want to run based on the CPU utilization of your existing Pods. How Intuit democratizes AI development across teams through reusability. If you have a specific, answerable question about how to use Kubernetes, ask it on Verify that all Management pods are ready by running the following command: kubectl -n namespace get po where namespace is the namespace where the Management subsystem is installed. attributes to the Deployment's .status.conditions: This condition can also fail early and is then set to status value of "False" due to reasons as ReplicaSetCreateError. The Deployment is now rolled back to a previous stable revision. The command instructs the controller to kill the pods one by one. Similarly, pods cannot survive evictions resulting from a lack of resources or to maintain the node. You will notice below that each pod runs and are back in business after restarting. .metadata.name field. kubectl get daemonsets -A. kubectl get rs -A | grep -v '0 0 0'. When the control plane creates new Pods for a Deployment, the .metadata.name of the All Rights Reserved. Follow the steps given below to create the above Deployment: Create the Deployment by running the following command: Run kubectl get deployments to check if the Deployment was created. .spec.selector is a required field that specifies a label selector By default, Kubernetes Documentation Tasks Monitoring, Logging, and Debugging Troubleshooting Applications Debug Running Pods Debug Running Pods This page explains how to debug Pods running (or crashing) on a Node. How to restart Pods in Kubernetes Method 1: Rollout Pod restarts Method 2. In API version apps/v1, .spec.selector and .metadata.labels do not default to .spec.template.metadata.labels if not set. controller will roll back a Deployment as soon as it observes such a condition. All existing Pods are killed before new ones are created when .spec.strategy.type==Recreate. There are many ways to restart pods in kubernetes with kubectl commands, but for a start, first, restart pods by changing the number of replicas in the deployment. To subscribe to this RSS feed, copy and paste this URL into your RSS reader. In my opinion, this is the best way to restart your pods as your application will not go down. Hope you like this Kubernetes tip. Thanks for contributing an answer to Stack Overflow! Now to see the change you can just enter the following command see the Events: In the events you can see: Container busybox definition changed, Why? .spec.progressDeadlineSeconds denotes the .spec.selector must match .spec.template.metadata.labels, or it will be rejected by the API. a Pod is considered ready, see Container Probes. The absolute number In kubernetes there is a rolling update (automatically without downtime) but there is not a rolling restart, at least i could not find. Method 1. kubectl rollout restart. fashion when .spec.strategy.type==RollingUpdate. This is technically a side-effect its better to use the scale or rollout commands which are more explicit and designed for this use case. If your Pod is not yet running, start with Debugging Pods. killing the 3 nginx:1.14.2 Pods that it had created, and starts creating Selector removals removes an existing key from the Deployment selector -- do not require any changes in the He is the founder of Heron Web, a UK-based digital agency providing bespoke software development services to SMEs. See the Kubernetes API conventions for more information on status conditions. Soft, Hard, and Mixed Resets Explained, How to Set Variables In Your GitLab CI Pipelines, How to Send a Message to Slack From a Bash Script, The New Outlook Is Opening Up to More People, Windows 11 Feature Updates Are Speeding Up, E-Win Champion Fabric Gaming Chair Review, Amazon Echo Dot With Clock (5th-gen) Review, Grelife 24in Oscillating Space Heater Review: Comfort and Functionality Combined, VCK Dual Filter Air Purifier Review: Affordable and Practical for Home or Office, LatticeWork Amber X Personal Cloud Storage Review: Backups Made Easy, Neat Bumblebee II Review: It's Good, It's Affordable, and It's Usually On Sale, How to Win $2000 By Learning to Code a Rocket League Bot, How to Watch UFC 285 Jones vs. Gane Live Online, How to Fix Your Connection Is Not Private Errors, 2023 LifeSavvy Media. []Kubernetes: Restart pods when config map values change 2021-09-08 17:16:34 2 74 kubernetes / configmap. .spec.progressDeadlineSeconds is an optional field that specifies the number of seconds you want Join 425,000 subscribers and get a daily digest of news, geek trivia, and our feature articles. Check your email for magic link to sign-in. and Pods which are created later. reason: NewReplicaSetAvailable means that the Deployment is complete). Minimum availability is dictated If you want to roll out releases to a subset of users or servers using the Deployment, you As a new addition to Kubernetes, this is the fastest restart method. The controller kills one pod at a time and relies on the ReplicaSet to scale up new Pods until all the Pods are newer than the restarted time. Change this value and apply the updated ReplicaSet manifest to your cluster to have Kubernetes reschedule your Pods to match the new replica count. the desired Pods. When you @Joey Yi Zhao thanks for the upvote, yes SAEED is correct, if you have a statefulset for that elasticsearch pod then killing the pod will eventually recreate it. The output is similar to: The created ReplicaSet ensures that there are three nginx Pods. type: Progressing with status: "True" means that your Deployment By default, it ensures that at most 125% of the desired number of Pods are up (25% max surge). Did any DOS compatibility layers exist for any UNIX-like systems before DOS started to become outmoded? Any leftovers are added to the Stack Overflow. Last modified February 18, 2023 at 7:06 PM PST: Installing Kubernetes with deployment tools, Customizing components with the kubeadm API, Creating Highly Available Clusters with kubeadm, Set up a High Availability etcd Cluster with kubeadm, Configuring each kubelet in your cluster using kubeadm, Communication between Nodes and the Control Plane, Guide for scheduling Windows containers in Kubernetes, Topology-aware traffic routing with topology keys, Resource Management for Pods and Containers, Organizing Cluster Access Using kubeconfig Files, Compute, Storage, and Networking Extensions, Changing the Container Runtime on a Node from Docker Engine to containerd, Migrate Docker Engine nodes from dockershim to cri-dockerd, Find Out What Container Runtime is Used on a Node, Troubleshooting CNI plugin-related errors, Check whether dockershim removal affects you, Migrating telemetry and security agents from dockershim, Configure Default Memory Requests and Limits for a Namespace, Configure Default CPU Requests and Limits for a Namespace, Configure Minimum and Maximum Memory Constraints for a Namespace, Configure Minimum and Maximum CPU Constraints for a Namespace, Configure Memory and CPU Quotas for a Namespace, Change the Reclaim Policy of a PersistentVolume, Configure a kubelet image credential provider, Control CPU Management Policies on the Node, Control Topology Management Policies on a node, Guaranteed Scheduling For Critical Add-On Pods, Migrate Replicated Control Plane To Use Cloud Controller Manager, Reconfigure a Node's Kubelet in a Live Cluster, Reserve Compute Resources for System Daemons, Running Kubernetes Node Components as a Non-root User, Using NodeLocal DNSCache in Kubernetes Clusters, Assign Memory Resources to Containers and Pods, Assign CPU Resources to Containers and Pods, Configure GMSA for Windows Pods and containers, Configure RunAsUserName for Windows pods and containers, Configure a Pod to Use a Volume for Storage, Configure a Pod to Use a PersistentVolume for Storage, Configure a Pod to Use a Projected Volume for Storage, Configure a Security Context for a Pod or Container, Configure Liveness, Readiness and Startup Probes, Attach Handlers to Container Lifecycle Events, Share Process Namespace between Containers in a Pod, Translate a Docker Compose File to Kubernetes Resources, Enforce Pod Security Standards by Configuring the Built-in Admission Controller, Enforce Pod Security Standards with Namespace Labels, Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller, Developing and debugging services locally using telepresence, Declarative Management of Kubernetes Objects Using Configuration Files, Declarative Management of Kubernetes Objects Using Kustomize, Managing Kubernetes Objects Using Imperative Commands, Imperative Management of Kubernetes Objects Using Configuration Files, Update API Objects in Place Using kubectl patch, Managing Secrets using Configuration File, Define a Command and Arguments for a Container, Define Environment Variables for a Container, Expose Pod Information to Containers Through Environment Variables, Expose Pod Information to Containers Through Files, Distribute Credentials Securely Using Secrets, Run a Stateless Application Using a Deployment, Run a Single-Instance Stateful Application, Specifying a Disruption Budget for your Application, Coarse Parallel Processing Using a Work Queue, Fine Parallel Processing Using a Work Queue, Indexed Job for Parallel Processing with Static Work Assignment, Handling retriable and non-retriable pod failures with Pod failure policy, Deploy and Access the Kubernetes Dashboard, Use Port Forwarding to Access Applications in a Cluster, Use a Service to Access an Application in a Cluster, Connect a Frontend to a Backend Using Services, List All Container Images Running in a Cluster, Set up Ingress on Minikube with the NGINX Ingress Controller, Communicate Between Containers in the Same Pod Using a Shared Volume, Extend the Kubernetes API with CustomResourceDefinitions, Use an HTTP Proxy to Access the Kubernetes API, Use a SOCKS5 Proxy to Access the Kubernetes API, Configure Certificate Rotation for the Kubelet, Adding entries to Pod /etc/hosts with HostAliases, Interactive Tutorial - Creating a Cluster, Interactive Tutorial - Exploring Your App, Externalizing config using MicroProfile, ConfigMaps and Secrets, Interactive Tutorial - Configuring a Java Microservice, Apply Pod Security Standards at the Cluster Level, Apply Pod Security Standards at the Namespace Level, Restrict a Container's Access to Resources with AppArmor, Restrict a Container's Syscalls with seccomp, Exposing an External IP Address to Access an Application in a Cluster, Example: Deploying PHP Guestbook application with Redis, Example: Deploying WordPress and MySQL with Persistent Volumes, Example: Deploying Cassandra with a StatefulSet, Running ZooKeeper, A Distributed System Coordinator, Mapping PodSecurityPolicies to Pod Security Standards, Well-Known Labels, Annotations and Taints, ValidatingAdmissionPolicyBindingList v1alpha1, Kubernetes Security and Disclosure Information, Articles on dockershim Removal and on Using CRI-compatible Runtimes, Event Rate Limit Configuration (v1alpha1), kube-apiserver Encryption Configuration (v1), kube-controller-manager Configuration (v1alpha1), Contributing to the Upstream Kubernetes Code, Generating Reference Documentation for the Kubernetes API, Generating Reference Documentation for kubectl Commands, Generating Reference Pages for Kubernetes Components and Tools, kubectl apply -f https://k8s.io/examples/controllers/nginx-deployment.yaml, kubectl rollout status deployment/nginx-deployment, NAME READY UP-TO-DATE AVAILABLE AGE, nginx-deployment 3/3 3 3 36s, kubectl rollout undo deployment/nginx-deployment, kubectl rollout undo deployment/nginx-deployment --to-revision, kubectl describe deployment nginx-deployment, kubectl scale deployment/nginx-deployment --replicas, kubectl autoscale deployment/nginx-deployment --min, kubectl rollout pause deployment/nginx-deployment, kubectl rollout resume deployment/nginx-deployment, kubectl patch deployment/nginx-deployment -p, '{"spec":{"progressDeadlineSeconds":600}}', Create a Deployment to rollout a ReplicaSet, Rollback to an earlier Deployment revision, Scale up the Deployment to facilitate more load, Rollover (aka multiple updates in-flight), Pausing and Resuming a rollout of a Deployment.