Conclusion and Further Exploration of Kubernetes Deployments

](https://1.bp.blogspot.com/-3U1OTNqdz1s/Vv7Kfw4uGYI/AAAAAAAAChU/CgF6Mv5J6b8_lANXkpEIFytRGo9x0Bn_A/s1600/deployment-API-6.png) From the events section, you’ll find that the Deployment is managing another resource called [Replica Set](/docs/user-guide/replicasets/), each controls the number of replicas of a different pod template. The Deployment enables progressive rollout by scaling up and down Replica Sets of new and old pod templates. ### Conclusion Now, you’ve learned the basic use of Deployment objects: 1. Deploy an app with a Deployment, using kubectl run 2. Updating the app by updating the Deployment with kubectl edit 3. Rolling back to a previously deployed app with kubectl rollout undo But there’s so much more in Deployment that this article didn’t cover! To discover more, continue reading [Deployment’s introduction](/docs/user-guide/deployments/). **_Note:_** _In Kubernetes 1.2, Deployment (beta release) is now feature-complete and enabled by default. For those of you who have tried Deployment in Kubernetes 1.1, please **delete all Deployment 1.1 resources** (including the Replication Controllers and Pods they manage) before trying out Deployments in 1.2. This is necessary because we made some non-backward-compatible changes to the API._ If you’re interested in Kubernetes and configuration, you’ll want to participate in: - Our Configuration [slack channel](https://kubernetes.slack.com/messages/sig-configuration/) - Our [Kubernetes Configuration Special Interest Group](https://groups.google.com/forum/#!forum/kubernetes-sig-config) email list - The Configuration “Special Interest Group,” which meets weekly on Wednesdays at 10am (10h00) Pacific Time at [SIG-Config hangout](https://hangouts.google.com/hangouts/_/google.com/kube-sig-config) And of course for more information about the project in general, go to [www.kubernetes.io](http://www.kubernetes.io/). **1** “kubectl run” outputs the type and name of the resource(s) it creates. In 1.2, it now creates a deployment resource. You can use that in subsequent commands, such as "kubectl get deployment ", or "kubectl expose deployment ". If you want to write a script to do that automatically, in a forward-compatible manner, use "-o name" flag with "kubectl run", and it will generate short output "deployments/", which can also be used on subsequent command lines. The "--generator" flag can be used with "kubectl run" to generate other types of resources, for example, set it to "run/v1" to create a Replication Controller, which was the default in 1.1 and 1.0, and to "run-pod/v1" to create a Pod, such as for --restart=Never pods.

This section summarizes the basic usage of Deployment objects, including deploying an app, updating it, and rolling back to a previous version. It encourages readers to explore more advanced features in the Deployment's introduction documentation. A note advises users upgrading from Kubernetes 1.1 to delete old Deployment resources due to API changes. The section also invites readers to participate in Kubernetes configuration-related channels and groups.