Enable Deployments by default

Author: janetkuo

api/swagger-spec/extensions_v1beta1.json

@@ -83,7 +83,6 @@ MASTER_RESERVED_IP="${MASTER_RESERVED_IP:-}"
 RUNTIME_CONFIG="${KUBE_RUNTIME_CONFIG:-}"
 
 # Enable various v1beta1 features
-ENABLE_DEPLOYMENTS="${KUBE_ENABLE_DEPLOYMENTS:-true}"
 ENABLE_DAEMONSETS="${KUBE_ENABLE_DAEMONSETS:-true}"
 
 # Optional: Cluster monitoring to setup as part of the cluster bring up:

cluster/aws/config-test.sh

@@ -422,15 +422,6 @@ function yaml-quote {
 
 # Builds the RUNTIME_CONFIG var from other feature enable options
 function build-runtime-config() {
-  if [[ "${ENABLE_DEPLOYMENTS}" == "true" ]]; then
-      if [[ -z "${RUNTIME_CONFIG}" ]]; then
-          RUNTIME_CONFIG="extensions/v1beta1/deployments=true"
-      else
-          if echo "${RUNTIME_CONFIG}" | grep -q -v "extensions/v1beta1/deployments=true"; then
-            RUNTIME_CONFIG="${RUNTIME_CONFIG},extensions/v1beta1/deployments=true"
-          fi
-      fi
-  fi
   if [[ "${ENABLE_DAEMONSETS}" == "true" ]]; then
       if [[ -z "${RUNTIME_CONFIG}" ]]; then
           RUNTIME_CONFIG="extensions/v1beta1/daemonsets=true"

cluster/common.sh

@@ -51,7 +51,6 @@ RUNTIME_CONFIG="${KUBE_RUNTIME_CONFIG:-}"
 TERMINATED_POD_GC_THRESHOLD=${TERMINATED_POD_GC_THRESHOLD:-100}
 
 # Optional: enable v1beta1 related features
-ENABLE_DEPLOYMENTS="${KUBE_ENABLE_DEPLOYMENTS:-true}"
 ENABLE_DAEMONSETS="${KUBE_ENABLE_DAEMONSETS:-true}"
 ENABLE_REPLICASETS="${KUBE_ENABLE_REPLICASETS:-true}"
 

cluster/gce/config-test.sh

@@ -42,7 +42,6 @@ RUNTIME_CONFIG="${KUBE_RUNTIME_CONFIG:-}"
 TERMINATED_POD_GC_THRESHOLD=${TERMINATED_POD_GC_THRESHOLD:-100}
 
 # Optional: enable v1beta1 related features
-ENABLE_DEPLOYMENTS="${KUBE_ENABLE_DEPLOYMENTS:-true}"
 ENABLE_DAEMONSETS="${KUBE_ENABLE_DAEMONSETS:-true}"
 
 TEST_CLUSTER_LOG_LEVEL="${TEST_CLUSTER_LOG_LEVEL:---v=2}"

cluster/kubemark/config-default.sh

@@ -113,10 +113,10 @@ create their own API groups](design/extending-api.md), and to avoid naming colli
 
 ## Enabling resources in the extensions group
 
-HorizontalPodAutoscalers, Jobs, Ingress and ReplicaSets are enabled by default.
+HorizontalPodAutoscalers, Jobs, Ingress, Deployments and ReplicaSets are enabled by default.
 Other extensions resources can be enabled by setting runtime-config on
-apiserver. runtime-config accepts comma separated values. For ex: to enable deployments and disable jobs, set
-`--runtime-config=extensions/v1beta1/deployments=true,extensions/v1beta1/jobs=false`
+apiserver. runtime-config accepts comma separated values. For ex: to disable deployments and jobs, set
+`--runtime-config=extensions/v1beta1/deployments=false,extensions/v1beta1/jobs=false`
 
 ## v1beta1, v1beta2, and v1beta3 are deprecated; please move to v1 ASAP
 

docs/api-reference/extensions/v1beta1/definitions.html

@@ -70,21 +70,6 @@ A typical use case is:
 * Create a Deployment to bring up a replication controller and pods.
 * Later, update that Deployment to recreate the pods (for example, to use a new image).
 
-## Enabling Deployments on a Kubernetes cluster
-
-Deployment objects are part of the [`extensions` API Group](../api.md#api-groups) and this feature
-is not enabled by default.
-Set `--runtime-config=extensions/v1beta1/deployments=true` on the API server to
-enable it.
-This can be achieved by exporting `KUBE_ENABLE_DEPLOYMENTS=true` before running the
-`kube-up.sh` script on GCE.
-
-Note that Deployment objects effectively have [API version
-`v1alpha1`](../api.md#api-versioning).
-Alpha objects may change or even be discontinued in future software releases.
-However, due to to a known issue, they will appear as API version `v1beta1` if
-enabled.
-
 ## Creating a Deployment
 
 Here is an example Deployment. It creates a replication controller to

docs/api-reference/extensions/v1beta1/operations.html

@@ -178,8 +178,6 @@ func Up() bool {
 		}
 	}
 
-	// Enable deployments for e2e tests.
-	os.Setenv("KUBE_ENABLE_DEPLOYMENTS", "true")
 	return finishRunning("up", exec.Command(path.Join(*root, "hack/e2e-internal/e2e-up.sh")))
 }