rename resize to scale

Author: andronat

contrib/completions/bash/kubectl

@@ -442,9 +442,9 @@ _kubectl_rolling-update()
     must_have_one_noun=()
 }
 
-_kubectl_resize()
+_kubectl_scale()
 {
-    last_command="kubectl_resize"
+    last_command="kubectl_scale"
     commands=()
 
     flags=()
@@ -897,7 +897,7 @@ _kubectl()
     commands+=("namespace")
     commands+=("logs")
     commands+=("rolling-update")
-    commands+=("resize")
+    commands+=("scale")
     commands+=("exec")
     commands+=("port-forward")
     commands+=("proxy")

docs/.files_generated

@@ -20,9 +20,9 @@ kubectl_logs.md
 kubectl_namespace.md
 kubectl_port-forward.md
 kubectl_proxy.md
-kubectl_resize.md
 kubectl_rolling-update.md
 kubectl_run.md
+kubectl_scale.md
 kubectl_stop.md
 kubectl_update.md
 kubectl_version.md

docs/api-conventions.md

@@ -189,7 +189,7 @@ These are verbs which change the fundamental type of data returned (watch return
 
 Two additional verbs `redirect` and `proxy` provide access to cluster resources as described in [accessing-the-cluster.md](accessing-the-cluster.md).
 
-When resources wish to expose alternative actions that are closely coupled to a single resource, they should do so using new sub-resources. An example is allowing automated processes to update the "status" field of a Pod. The `/pods` endpoint only allows updates to "metadata" and "spec", since those reflect end-user intent. An automated process should be able to modify status for users to see by sending an updated Pod kind to the server to the "/pods/<name>/status" endpoint - the alternate endpoint allows different rules to be applied to the update, and access to be appropriately restricted. Likewise, some actions like "stop" or "resize" are best represented as REST sub-resources that are POSTed to.  The POST action may require a simple kind to be provided if the action requires parameters, or function without a request body.
+When resources wish to expose alternative actions that are closely coupled to a single resource, they should do so using new sub-resources. An example is allowing automated processes to update the "status" field of a Pod. The `/pods` endpoint only allows updates to "metadata" and "spec", since those reflect end-user intent. An automated process should be able to modify status for users to see by sending an updated Pod kind to the server to the "/pods/<name>/status" endpoint - the alternate endpoint allows different rules to be applied to the update, and access to be appropriately restricted. Likewise, some actions like "stop" or "scale" are best represented as REST sub-resources that are POSTed to.  The POST action may require a simple kind to be provided if the action requires parameters, or function without a request body.
 
 TODO: more documentation of Watch
 

docs/devel/developer-guides/vagrant.md

@@ -243,10 +243,10 @@ myNginx   nginx              name=my-nginx   3
 
 We did not start any services, hence there are none listed. But we see three replicas displayed properly.
 Check the [guestbook](../../examples/guestbook/README.md) application to learn how to create a service.
-You can already play with resizing the replicas with:
+You can already play with scaling the replicas with:
 
 ```sh
-$ ./cluster/kubectl.sh resize rc my-nginx --replicas=2
+$ ./cluster/kubectl.sh scale rc my-nginx --replicas=2
 $ ./cluster/kubectl.sh get pods
 NAME                                   IMAGE(S)            HOST                    LABELS         STATUS
 7813c8bd-3ffe-11e4-9036-0800279696e1   nginx               10.245.2.2/10.245.2.2   name=myNginx   Running

docs/getting-started-guides/coreos/azure/README.md

@@ -88,17 +88,17 @@ redis-slave-controller-gziey   10.2.1.4       slave           brendanburns/redis
 
 ## Scaling
 
-Two single-core minions are certainly not enough for a production system of today, and, as you can see, there is one _unassigned_ pod. Let's resize the cluster by adding a couple of bigger nodes.
+Two single-core minions are certainly not enough for a production system of today, and, as you can see, there is one _unassigned_ pod. Let's scale the cluster by adding a couple of bigger nodes.
 
 You will need to open another terminal window on your machine and go to the same working directory (e.g. `~/Workspace/weave-demos/coreos-azure`).
 
 First, lets set the size of new VMs:
 ```
 export AZ_VM_SIZE=Large
 ```
-Now, run resize script with state file of the previous deployment and number of minions to add:
+Now, run scale script with state file of the previous deployment and number of minions to add:
 ```
-./resize-kubernetes-cluster.js ./output/kubernetes_1c1496016083b4_deployment.yml 2
+./scale-kubernetes-cluster.js ./output/kubernetes_1c1496016083b4_deployment.yml 2
 ...
 azure_wrapper/info: Saved SSH config, you can use it like so: `ssh -F  ./output/kubernetes_8f984af944f572_ssh_conf <hostname>`
 azure_wrapper/info: The hosts in this deployment are:
@@ -124,7 +124,7 @@ kube-03             environment=production   Ready
 kube-04             environment=production   Ready
 ```
 
-You can see that two more minions joined happily. Let's resize the number of Guestbook instances now.
+You can see that two more minions joined happily. Let's scale the number of Guestbook instances now.
 
 First, double-check how many replication controllers there are:
 
@@ -134,12 +134,12 @@ CONTROLLER               CONTAINER(S)  IMAGE(S)
 frontend-controller      php-redis     kubernetes/example-guestbook-php-redis   name=frontend    3
 redis-slave-controller   slave         brendanburns/redis-slave                 name=redisslave  2
 ```
-As there are 4 minions, let's resize proportionally:
+As there are 4 minions, let's scale proportionally:
 ```
-core@kube-00 ~ $ kubectl resize --replicas=4 rc redis-slave-controller
-resized
-core@kube-00 ~ $ kubectl resize --replicas=4 rc frontend-controller
-resized
+core@kube-00 ~ $ kubectl scale --replicas=4 rc redis-slave-controller
+scaled
+core@kube-00 ~ $ kubectl scale --replicas=4 rc frontend-controller
+scaled
 ```
 Check what you have now:
 ```
@@ -182,7 +182,7 @@ If you don't wish care about the Azure bill, you can tear down the cluster. It's
 ./destroy-cluster.js ./output/kubernetes_8f984af944f572_deployment.yml 
 ```
 
-> Note: make sure to use the _latest state file_, as after resizing there is a new one.
+> Note: make sure to use the _latest state file_, as after scaling there is a new one.
 
 By the way, with the scripts shown, you can deploy multiple clusters, if you like :)
 

docs/getting-started-guides/coreos/azure/resize-kubernetes-cluster.js renamed to docs/getting-started-guides/coreos/azure/scale-kubernetes-cluster.js

@@ -46,7 +46,7 @@ Note that you will need run this curl command on your boot2docker VM if you are
 Now try to scale up the nginx you created before:
 
 ```sh
-kubectl resize rc nginx --replicas=3
+kubectl scale rc nginx --replicas=3
 ```
 
 And list the pods

docs/getting-started-guides/docker-multinode/testing.md

@@ -219,10 +219,10 @@ myNginx   nginx              name=my-nginx   3
 
 We did not start any services, hence there are none listed. But we see three replicas displayed properly.
 Check the [guestbook](../../examples/guestbook/README.md) application to learn how to create a service.
-You can already play with resizing the replicas with:
+You can already play with scaling the replicas with:
 
 ```sh
-$ ./cluster/kubectl.sh resize rc my-nginx --replicas=2
+$ ./cluster/kubectl.sh scale rc my-nginx --replicas=2
 $ ./cluster/kubectl.sh get pods
 NAME                                   IMAGE(S)            HOST                    LABELS         STATUS
 7813c8bd-3ffe-11e4-9036-0800279696e1   nginx               10.245.2.2/10.245.2.2   name=myNginx   Running

docs/getting-started-guides/vagrant.md

@@ -58,9 +58,9 @@ kubectl
 * [kubectl namespace](kubectl_namespace.md)	 - SUPERCEDED: Set and view the current Kubernetes namespace
 * [kubectl port-forward](kubectl_port-forward.md)	 - Forward one or more local ports to a pod.
 * [kubectl proxy](kubectl_proxy.md)	 - Run a proxy to the Kubernetes API server
-* [kubectl resize](kubectl_resize.md)	 - Set a new size for a Replication Controller.
 * [kubectl rolling-update](kubectl_rolling-update.md)	 - Perform a rolling update of the given ReplicationController.
 * [kubectl run](kubectl_run.md)	 - Run a particular image on the cluster.
+* [kubectl scale](kubectl_scale.md)	 - Set a new size for a Replication Controller.
 * [kubectl stop](kubectl_stop.md)	 - Gracefully shut down a resource by id or filename.
 * [kubectl update](kubectl_update.md)	 - Update a resource by filename or stdin.
 * [kubectl version](kubectl_version.md)	 - Print the client and server version information.

docs/kubectl.md

@@ -1,4 +1,4 @@
-## kubectl resize
+## kubectl scale
 
 Set a new size for a Replication Controller.
 
@@ -7,32 +7,32 @@ Set a new size for a Replication Controller.
 
 Set a new size for a Replication Controller.
 
-Resize also allows users to specify one or more preconditions for the resize action.
+Scale also allows users to specify one or more preconditions for the scale action.
 If --current-replicas or --resource-version is specified, it is validated before the
-resize is attempted, and it is guaranteed that the precondition holds true when the
-resize is sent to the server.
+scale is attempted, and it is guaranteed that the precondition holds true when the
+scale is sent to the server.
 
 ```
-kubectl resize [--resource-version=version] [--current-replicas=count] --replicas=COUNT RESOURCE ID
+kubectl scale [--resource-version=version] [--current-replicas=count] --replicas=COUNT RESOURCE ID
 ```
 
 ### Examples
 
 ```
-// Resize replication controller named 'foo' to 3.
-$ kubectl resize --replicas=3 replicationcontrollers foo
+// Scale replication controller named 'foo' to 3.
+$ kubectl scale --replicas=3 replicationcontrollers foo
 
-// If the replication controller named foo's current size is 2, resize foo to 3.
-$ kubectl resize --current-replicas=2 --replicas=3 replicationcontrollers foo
+// If the replication controller named foo's current size is 2, scale foo to 3.
+$ kubectl scale --current-replicas=2 --replicas=3 replicationcontrollers foo
 ```
 
 ### Options
 
 ```
-      --current-replicas=-1: Precondition for current size. Requires that the current size of the replication controller match this value in order to resize.
-  -h, --help=false: help for resize
+      --current-replicas=-1: Precondition for current size. Requires that the current size of the replication controller match this value in order to scale.
+  -h, --help=false: help for scale
       --replicas=-1: The new desired number of replicas. Required.
-      --resource-version="": Precondition for resource version. Requires that the current resource version match this value in order to resize.
+      --resource-version="": Precondition for resource version. Requires that the current resource version match this value in order to scale.
 ```
 
 ### Options inherited from parent commands
@@ -69,4 +69,4 @@ $ kubectl resize --current-replicas=2 --replicas=3 replicationcontrollers foo
 
 ###### Auto generated by spf13/cobra at 2015-05-21 10:33:11.185268791 +0000 UTC
 
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/kubectl_resize.md?pixel)]()
+[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/kubectl_scale.md?pixel)]()

docs/kubectl_resize.md renamed to docs/kubectl_scale.md

@@ -8,7 +8,7 @@ Gracefully shut down a resource by id or filename.
 Gracefully shut down a resource by id or filename.
 
 Attempts to shut down and delete a resource that supports graceful termination.
-If the resource is resizable it will be resized to 0 before deletion.
+If the resource is scalable it will be scaled to 0 before deletion.
 
 ```
 kubectl stop (-f FILENAME | RESOURCE (ID | -l label | --all))

docs/kubectl_stop.md

@@ -19,9 +19,9 @@ kubectl-logs.1
 kubectl-namespace.1
 kubectl-port-forward.1
 kubectl-proxy.1
-kubectl-resize.1
 kubectl-rolling-update.1
 kubectl-run.1
+kubectl-scale.1
 kubectl-stop.1
 kubectl-update.1
 kubectl-version.1

docs/man/man1/.files_generated

@@ -3,41 +3,41 @@
 
 .SH NAME
 .PP
-kubectl resize \- Set a new size for a Replication Controller.
+kubectl scale \- Set a new size for a Replication Controller.
 
 
 .SH SYNOPSIS
 .PP
-\fBkubectl resize\fP [OPTIONS]
+\fBkubectl scale\fP [OPTIONS]
 
 
 .SH DESCRIPTION
 .PP
 Set a new size for a Replication Controller.
 
 .PP
-Resize also allows users to specify one or more preconditions for the resize action.
+Scale also allows users to specify one or more preconditions for the scale action.
 If \-\-current\-replicas or \-\-resource\-version is specified, it is validated before the
-resize is attempted, and it is guaranteed that the precondition holds true when the
-resize is sent to the server.
+scale is attempted, and it is guaranteed that the precondition holds true when the
+scale is sent to the server.
 
 
 .SH OPTIONS
 .PP
 \fB\-\-current\-replicas\fP=\-1
-    Precondition for current size. Requires that the current size of the replication controller match this value in order to resize.
+    Precondition for current size. Requires that the current size of the replication controller match this value in order to scale.
 
 .PP
 \fB\-h\fP, \fB\-\-help\fP=false
-    help for resize
+    help for scale
 
 .PP
 \fB\-\-replicas\fP=\-1
     The new desired number of replicas. Required.
 
 .PP
 \fB\-\-resource\-version\fP=""
-    Precondition for resource version. Requires that the current resource version match this value in order to resize.
+    Precondition for resource version. Requires that the current resource version match this value in order to scale.
 
 
 .SH OPTIONS INHERITED FROM PARENT COMMANDS
@@ -143,11 +143,11 @@ resize is sent to the server.
 .RS
 
 .nf
-// Resize replication controller named 'foo' to 3.
-$ kubectl resize \-\-replicas=3 replicationcontrollers foo
+// Scale replication controller named 'foo' to 3.
+$ kubectl scale \-\-replicas=3 replicationcontrollers foo
 
-// If the replication controller named foo's current size is 2, resize foo to 3.
-$ kubectl resize \-\-current\-replicas=2 \-\-replicas=3 replicationcontrollers foo
+// If the replication controller named foo's current size is 2, scale foo to 3.
+$ kubectl scale \-\-current\-replicas=2 \-\-replicas=3 replicationcontrollers foo
 
 .fi
 .RE

docs/man/man1/kubectl-resize.1 renamed to docs/man/man1/kubectl-scale.1

@@ -17,7 +17,7 @@ Gracefully shut down a resource by id or filename.
 
 .PP
 Attempts to shut down and delete a resource that supports graceful termination.
-If the resource is resizable it will be resized to 0 before deletion.
+If the resource is scalable it will be scaled to 0 before deletion.
 
 
 .SH OPTIONS

docs/man/man1/kubectl-stop.1

@@ -124,7 +124,7 @@ Find more information at
 
 .SH SEE ALSO
 .PP
-\fBkubectl\-get(1)\fP, \fBkubectl\-describe(1)\fP, \fBkubectl\-create(1)\fP, \fBkubectl\-update(1)\fP, \fBkubectl\-delete(1)\fP, \fBkubectl\-namespace(1)\fP, \fBkubectl\-logs(1)\fP, \fBkubectl\-rolling\-update(1)\fP, \fBkubectl\-resize(1)\fP, \fBkubectl\-exec(1)\fP, \fBkubectl\-port\-forward(1)\fP, \fBkubectl\-proxy(1)\fP, \fBkubectl\-run(1)\fP, \fBkubectl\-stop(1)\fP, \fBkubectl\-expose(1)\fP, \fBkubectl\-label(1)\fP, \fBkubectl\-config(1)\fP, \fBkubectl\-cluster\-info(1)\fP, \fBkubectl\-api\-versions(1)\fP, \fBkubectl\-version(1)\fP,
+\fBkubectl\-get(1)\fP, \fBkubectl\-describe(1)\fP, \fBkubectl\-create(1)\fP, \fBkubectl\-update(1)\fP, \fBkubectl\-delete(1)\fP, \fBkubectl\-namespace(1)\fP, \fBkubectl\-logs(1)\fP, \fBkubectl\-rolling\-update(1)\fP, \fBkubectl\-scale(1)\fP, \fBkubectl\-exec(1)\fP, \fBkubectl\-port\-forward(1)\fP, \fBkubectl\-proxy(1)\fP, \fBkubectl\-run(1)\fP, \fBkubectl\-stop(1)\fP, \fBkubectl\-expose(1)\fP, \fBkubectl\-label(1)\fP, \fBkubectl\-config(1)\fP, \fBkubectl\-cluster\-info(1)\fP, \fBkubectl\-api\-versions(1)\fP, \fBkubectl\-version(1)\fP,
 
 
 .SH HISTORY