diff --git a/_config.yml b/_config.yml
index 4acb94edca..acdccbee88 100644
--- a/_config.yml
+++ b/_config.yml
@@ -14,20 +14,10 @@ lsi: false
 defaults:
   -
     scope:
-      path: "v1.1"
+      path: "docs"
     values:
       version: "v1.1"
-      versionfilesafe: "v1_1"
       layout: docwithnav
       showedit: true
       githubbranch: "release-1.1"
-  -
-    scope:
-      path: "v1.2"
-    values:
-      version: "v1.2"
-      versionfilesafe: "v1_2"
-      layout: docwithnav
-      showedit: true
-      githubbranch: "release-1.2"
 permalink: pretty
diff --git a/_data/v1_1/globals.yml b/_data/globals.yml
similarity index 100%
rename from _data/v1_1/globals.yml
rename to _data/globals.yml
diff --git a/_data/v1_1/guides.yml b/_data/guides.yml
similarity index 54%
rename from _data/v1_1/guides.yml
rename to _data/guides.yml
index 8409e4e615..08c3470553 100644
--- a/_data/v1_1/guides.yml
+++ b/_data/guides.yml
@@ -2,178 +2,178 @@ bigheader: "Guides"
 abstract: "How to get started, and acheive tasks, using Kubernetes"
 toc:
 - title: Guides
-  path: /v1.1/
+  path: /docs/
 
 - title: Quickstarts
   section:
   - title: What is Kubernetes?
-    path: /v1.1/docs/whatisk8s/
+    path: /docs/whatisk8s/
   - title: TODO - 5-minute Quickstart
-    path: /v1.1/docs/hellonode/
+    path: /docs/hellonode/
   - title: Kubernetes 101
-    path: /v1.1/docs/user-guide/walkthrough/
+    path: /docs/user-guide/walkthrough/
   - title: Kubernetes 201
-    path: /v1.1/docs/user-guide/walkthrough/k8s201/
+    path: /docs/user-guide/walkthrough/k8s201/
 
 - title: Running Kubernetes
   section:
   - title: Picking the Right Solution
-    path: /v1.1/docs/getting-started-guides/
+    path: /docs/getting-started-guides/
   - title: Running Kubernetes on Your Local Machine
     section:
     - title: Running Kubernetes Locally via Docker
-      path: /v1.1/docs/getting-started-guides/docker/
+      path: /docs/getting-started-guides/docker/
     - title: Running Kubernetes Locally via Vagrant
-      path: /v1.1/docs/getting-started-guides/vagrant/
+      path: /docs/getting-started-guides/vagrant/
     - title: Running Kubernetes Locally with No VM
-      path: /v1.1/docs/getting-started-guides/locally/
+      path: /docs/getting-started-guides/locally/
   - title: Running Kubernetes on Turn-key Cloud Solutions
     section:
     - title: Running Kubernetes on Google Container Engine
       path: https://cloud.google.com/container-engine/docs/before-you-begin/
     - title: Running Kubernetes on Google Compute Engine
-      path: /v1.1/docs/getting-started-guides/gce/
+      path: /docs/getting-started-guides/gce/
     - title: Running Kubernetes on AWS EC2
-      path: /v1.1/docs/getting-started-guides/aws/
+      path: /docs/getting-started-guides/aws/
     - title: Running Kubernetes on Azure
-      path: /v1.1/docs/getting-started-guides/coreos/azure/
+      path: /docs/getting-started-guides/coreos/azure/
   - title: Running Kubernetes on Custom Solutions
     section:
     - title: Getting Started From Scratch
-      path: /v1.1/docs/getting-started-guides/scratch/
+      path: /docs/getting-started-guides/scratch/
     - title: Custom Cloud Solutions
       section:
       - title: AWS or GCE on CoreOS
-        path: /v1.1/docs/getting-started-guides/coreos/
+        path: /docs/getting-started-guides/coreos/
       - title: AWS or Joyent on Ubuntu
-        path: /v1.1/docs/getting-started-guides/juju/
+        path: /docs/getting-started-guides/juju/
       - title: Rackspace on CoreOS
-        path: /v1.1/docs/getting-started-guides/rackspace/
+        path: /docs/getting-started-guides/rackspace/
     - title: On-Premise VMs
       section:
       - title: Vagrant or VMware
-        path: /v1.1/docs/getting-started-guides/coreos/
+        path: /docs/getting-started-guides/coreos/
       - title: Cloudstack
-        path: /v1.1/docs/getting-started-guides/cloudstack/
+        path: /docs/getting-started-guides/cloudstack/
       - title: VMWare
-        path: /v1.1/docs/getting-started-guides/vsphere/
+        path: /docs/getting-started-guides/vsphere/
       - title: Juju
-        path: /v1.1/docs/getting-started-guides/juju/
+        path: /docs/getting-started-guides/juju/
       - title: libvirt on CoreOS
-        path: /v1.1/docs/getting-started-guides/libvirt-coreos/
+        path: /docs/getting-started-guides/libvirt-coreos/
       - title: oVirt
-        path: /v1.1/docs/getting-started-guides/ovirt/
+        path: /docs/getting-started-guides/ovirt/
       - title: libvirt or KVM
-        path: /v1.1/docs/getting-started-guides/fedora/flannel_multi_node_cluster/
+        path: /docs/getting-started-guides/fedora/flannel_multi_node_cluster/
     - title: Bare Metal
       section:
       - title: Offline
-        path: /v1.1/docs/getting-started-guides/coreos/bare_metal_offline/
+        path: /docs/getting-started-guides/coreos/bare_metal_offline/
       - title: Fedora via Ansible
-        path: /v1.1/docs/getting-started-guides/fedora/fedora_ansible_config/
+        path: /docs/getting-started-guides/fedora/fedora_ansible_config/
       - title: Fedora (Single Node)
-        path: /v1.1/docs/getting-started-guides/fedora/fedora_manual_config/
+        path: /docs/getting-started-guides/fedora/fedora_manual_config/
       - title: Fedora (Multi Node)
-        path: /v1.1/docs/getting-started-guides/fedora/flannel_multi_node_cluster/
+        path: /docs/getting-started-guides/fedora/flannel_multi_node_cluster/
       - title: Centos
-        path: /v1.1/docs/getting-started-guides/centos/centos_manual_config/
+        path: /docs/getting-started-guides/centos/centos_manual_config/
       - title: Ubuntu
-        path: /v1.1/docs/getting-started-guides/ubuntu/
+        path: /docs/getting-started-guides/ubuntu/
       - title: Docker (Multi Node)
-        path: /v1.1/docs/getting-started-guides/docker-multinode/
+        path: /docs/getting-started-guides/docker-multinode/
 
 - title: Administering Clusters
   section:
   - title: Kubernetes Cluster Admin Guide
-    path: /v1.1/docs/admin/
+    path: /docs/admin/
   - title: Using Multiple Clusters
-    path: /v1.1/docs/admin/multi-cluster/
+    path: /docs/admin/multi-cluster/
   - title: Using Large Clusters
-    path: /v1.1/docs/admin/cluster-large/
+    path: /docs/admin/cluster-large/
   - title: Building High-Availability Clusters
-    path: /v1.1/docs/admin/high-availability/
+    path: /docs/admin/high-availability/
   - title: Accessing Clusters
-    path: /v1.1/docs/user-guide/accessing-the-cluster/
+    path: /docs/user-guide/accessing-the-cluster/
   - title: Sharing a Cluster
-    path: /v1.1/docs/admin/namespaces/
+    path: /docs/admin/namespaces/
   - title: Changing Cluster Size
     path: https://github.com/kubernetes/kubernetes/wiki/User-FAQ#how-do-i-change-the-size-of-my-cluster/
   - title: Creating a Custom Cluster from Scratch
-    path: /v1.1/docs/getting-started-guides/scratch/
+    path: /docs/getting-started-guides/scratch/
   - title: Authenticating Across Clusters with kubeconfig
-    path: /v1.1/docs/user-guide/kubeconfig-file/
+    path: /docs/user-guide/kubeconfig-file/
  
 - title: Using Nodes, Pods, and Containers
   section:
   - title: Assigning Pods to Nodes
-    path: /v1.1/docs/user-guide/node-selection/
+    path: /docs/user-guide/node-selection/
   - title: Working with Containers
-    path: /v1.1/docs/user-guide/production-pods/
+    path: /docs/user-guide/production-pods/
   - title: Creating Pods with the Downward API
-    path: /v1.1/docs/user-guide/downward-api/
+    path: /docs/user-guide/downward-api/
   - title: Updating Live Pods
-    path: /v1.1/docs/user-guide/update-demo/
+    path: /docs/user-guide/update-demo/
   - title: Running Commands in a Container with kubectl exec
-    path: /v1.1/docs/user-guide/getting-into-containers/
+    path: /docs/user-guide/getting-into-containers/
 
 - title: Networking
   section:
   - title: Networking in Kubernetes
-    path: /v1.1/docs/admin/networking/
+    path: /docs/admin/networking/
   - title: Setting Up and Configuring DNS
     path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/cluster-dns
   - title: Connecting Applications
-    path: /v1.1/docs/user-guide/connecting-applications/
+    path: /docs/user-guide/connecting-applications/
   - title: Creating Servers with External IPs
     path: https://github.com/kubernetes/kubernetes/blob/release-1.1/examples/simple-nginx.md
   - title: Using DNS Pods and Services
-    path: /v1.1/docs/admin/dns/
+    path: /docs/admin/dns/
   - title: Connect with Proxies
-    path: /v1.1/docs/user-guide/connecting-to-applications-proxy/
+    path: /docs/user-guide/connecting-to-applications-proxy/
   - title: Connect with Port Forwarding
-    path: /v1.1/docs/user-guide/connecting-to-applications-port-forward/
+    path: /docs/user-guide/connecting-to-applications-port-forward/
  
 - title: Configuring Kubernetes
   section:
   - title: Using Configuration Files
-    path: /v1.1/docs/user-guide/simple-yaml/
+    path: /docs/user-guide/simple-yaml/
   - title: Configuring Containers
-    path: /v1.1/docs/user-guide/configuring-containers/
+    path: /docs/user-guide/configuring-containers/
   - title: Using Environment Variables
-    path: /v1.1/docs/user-guide/environment-guide/
+    path: /docs/user-guide/environment-guide/
   - title: Managing Compute Resources
-    path: /v1.1/docs/user-guide/compute-resources/
+    path: /docs/user-guide/compute-resources/
   - title: Applying Resource Quotas and Limits
-    path: /v1.1/docs/admin/resourcequota/
+    path: /docs/admin/resourcequota/
   - title: Setting Pod CPU and Memory Limits
-    path: /v1.1/docs/admin/limitrange/
+    path: /docs/admin/limitrange/
   - title: Configuring Garbage Collection
-    path: /v1.1/docs/admin/garbage-collection/
+    path: /docs/admin/garbage-collection/
   - title: Configuring Kubernetes with Salt
-    path: /v1.1/docs/admin/salt/
+    path: /docs/admin/salt/
   - title: Best Practices for Configuration
-    path: /v1.1/docs/user-guide/config-best-practices/
+    path: /docs/user-guide/config-best-practices/
 
 - title: Application Management and Deployment
   section:
   - title: "Managing Applications: Prerequisites"
-    path: /v1.1/docs/user-guide/prereqs/
+    path: /docs/user-guide/prereqs/
   - title: Managing Deployments
-    path: /v1.1/docs/user-guide/managing-deployments/
+    path: /docs/user-guide/managing-deployments/
   - title: Deploying Applications
-    path: /v1.1/docs/user-guide/deploying-applications/
+    path: /docs/user-guide/deploying-applications/
   - title: Launching, Exposing, and Killing Applications
-    path: /v1.1/docs/user-guide/quick-start/
+    path: /docs/user-guide/quick-start/
 
 - title: Testing and Monitoring
   section:
   - title: Simulating Large Test Loads
     path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/k8petstore
   - title: Checking Pod Health
-    path: /v1.1/docs/user-guide/liveness/
+    path: /docs/user-guide/liveness/
   - title: Using Explorer to Examine the Runtime Environment
     path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/explorer
   - title: Resource Usage Monitoring
-    path: /v1.1/docs/user-guide/monitoring/
+    path: /docs/user-guide/monitoring/
   - title: Logging
-    path: /v1.1/docs/user-guide/logging/
+    path: /docs/user-guide/logging/
diff --git a/_data/overrides.yml b/_data/overrides.yml
index a6de4e8739..cbb44bd518 100644
--- a/_data/overrides.yml
+++ b/_data/overrides.yml
@@ -1,15 +1,8 @@
 overrides:
-- path: v1.1/docs/api-reference
-- path: v1.1/docs/user-guide/kubectl
-- path: v1.1/docs/admin/kube-apiserver.md
-- path: v1.1/docs/admin/kube-controller-manager.md
-- path: v1.1/docs/admin/kube-proxy.md
-- path: v1.1/docs/admin/kube-scheduler.md
-- path: v1.1/docs/admin/kubelet.md
-- path: v1.2/docs/api-reference
-- path: v1.2/docs/user-guide/kubectl
-- path: v1.2/docs/admin/kube-apiserver.md
-- path: v1.2/docs/admin/kube-controller-manager.md
-- path: v1.2/docs/admin/kube-proxy.md
-- path: v1.2/docs/admin/kube-scheduler.md
-- path: v1.2/docs/admin/kubelet.md
\ No newline at end of file
+- path: docs/api-reference
+- path: docs/user-guide/kubectl
+- path: docs/admin/kube-apiserver.md
+- path: docs/admin/kube-controller-manager.md
+- path: docs/admin/kube-proxy.md
+- path: docs/admin/kube-scheduler.md
+- path: docs/admin/kubelet.md
\ No newline at end of file
diff --git a/_data/reference.yml b/_data/reference.yml
new file mode 100644
index 0000000000..0516f033a9
--- /dev/null
+++ b/_data/reference.yml
@@ -0,0 +1,184 @@
+bigheader: "Reference Documentation"
+abstract: "Design docs, concept definitions, and references for APIs and CLIs."
+toc:
+- title: Reference Documentation
+  path: /docs/reference/
+
+- title: Kubernetes API
+  section:
+  - title: Kubernetes API Overview
+    path: /docs/api/
+  - title: Kubernetes API Operations
+    path: /docs/api-reference/v1/operations/
+  - title: Kubernetes API Definitions
+    path: /docs/api-reference/v1/definitions/
+
+- title: Extensions API
+  section:
+  - title: Extensions API Operations
+    path: /docs/api-reference/extensions/v1beta1/operations/
+  - title: Extensions API Definitions
+    path: /docs/api-reference/extensions/v1beta1/definitions/
+
+- title: kubectl
+  section:
+  - title: kubectl Overview
+    path: /docs/user-guide/kubectl-overview/
+  - title: kubectl for Docker Users
+    path: /docs/user-guide/docker-cli-to-kubectl/
+  - title: kubectl Commands
+    section:
+    - title: kubectl
+      path: /docs/user-guide/kubectl/kubectl/
+    - title: kubectl annotate
+      path: /docs/user-guide/kubectl/kubectl_annotate/
+    - title: kubectl api-versions
+      path: /docs/user-guide/kubectl/kubectl_api-versions/
+    - title: kubectl apply
+      path: /docs/user-guide/kubectl/kubectl_apply/
+    - title: kubectl attach
+      path: /docs/user-guide/kubectl/kubectl_attach/
+    - title: kubectl autoscale
+      path: /docs/user-guide/kubectl/kubectl_autoscale/
+    - title: kubectl cluster-info
+      path: /docs/user-guide/kubectl/kubectl_cluster-info/
+    - title: kubectl config
+      path: /docs/user-guide/kubectl/kubectl_config/
+    - title: kubectl config set-cluster
+      path: /docs/user-guide/kubectl/kubectl_config_set-cluster/
+    - title: kubectl config set-context
+      path: /docs/user-guide/kubectl/kubectl_config_set-context/
+    - title: kubectl set-credentials
+      path: /docs/user-guide/kubectl/kubectl_config_set-credentials/
+    - title: kubectl config set
+      path: /docs/user-guide/kubectl/kubectl_config_set/
+    - title: kubectl config unset
+      path: /docs/user-guide/kubectl/kubectl_config_unset/
+    - title: kubectl config use-context
+      path: /docs/user-guide/kubectl/kubectl_config_use-context/
+    - title: kubectl config view
+      path: /docs/user-guide/kubectl/kubectl_config_view/
+    - title: kubectl create
+      path: /docs/user-guide/kubectl/kubectl_create/
+    - title: kubectl delete
+      path: /docs/user-guide/kubectl/kubectl_delete/
+    - title: kubectl describe
+      path: /docs/user-guide/kubectl/kubectl_describe/
+    - title: kubectl edit
+      path: /docs/user-guide/kubectl/kubectl_edit/
+    - title: kubectl exec
+      path: /docs/user-guide/kubectl/kubectl_exec/
+    - title: kubectl expose
+      path: /docs/user-guide/kubectl/kubectl_expose/
+    - title: kubectl get
+      path: /docs/user-guide/kubectl/kubectl_get/
+    - title: kubectl label
+      path: /docs/user-guide/kubectl/kubectl_label/
+    - title: kubectl logs
+      path: /docs/user-guide/kubectl/kubectl_logs/
+    - title: kubectl patch
+      path: /docs/user-guide/kubectl/kubectl_patch/
+    - title: kubectl port-forward
+      path: /docs/user-guide/kubectl/kubectl_port-forward/
+    - title: kubectl proxy
+      path: /docs/user-guide/kubectl/kubectl_proxy/
+    - title: kubectl replace
+      path: /docs/user-guide/kubectl/kubectl_replace/
+    - title: kubectl rolling-update
+      path: /docs/user-guide/kubectl/kubectl_rolling-update/
+    - title: kubectl run
+      path: /docs/user-guide/kubectl/kubectl_run/
+    - title: kubectl scale
+      path: /docs/user-guide/kubectl/kubectl_scale/
+    - title: kubectl stop
+      path: /docs/user-guide/kubectl/kubectl_stop/
+    - title: kubectl version
+      path: /docs/user-guide/kubectl/kubectl_version/
+
+- title: kube-apiserver
+  section:
+  - title: Overview
+    path: /docs/admin/kube-apiserver/
+  - title: Authorization Plugins
+    path: /docs/admin/authorization/
+  - title: Authentication
+    path: /docs/admin/authentication/
+  - title: Accessing the API
+    path: /docs/admin/accessing-the-api/
+  - title: Admission Controllers
+    path: /docs/admin/admission-controllers/
+  - title: Managing Service Accounts
+    path: /docs/admin/service-accounts-admin/
+
+- title: kub-scheduler
+  path: /docs/admin/kube-scheduler/
+
+- title: kubelet
+  path: /docs/admin/kubelet.md
+
+- title: kube-proxy
+  path: /docs/admin/kube-proxy/
+
+- title: JSONpath
+  path: /docs/user-guide/jsonpath/
+
+- title: etcd
+  path: /docs/admin/etcd/
+
+- title: Concept Definitions
+  section:
+  - title: Container Environment
+    path: /docs/user-guide/container-environment/
+  - title: Images
+    path: /docs/user-guide/images/
+  - title: Pods
+    path: /docs/user-guide/pods/
+  - title: Labels and Selectors
+    path: /docs/user-guide/labels/
+  - title: Replication Controller
+    path: /docs/user-guide/replication-controller/
+  - title: Services
+    path: /docs/user-guide/services/
+  - title: Volumes
+    path: /docs/user-guide/volumes/
+  - title: Persistent Volumes
+    path: /docs/user-guide/persistent-volumes/
+  - title: Secrets
+    path: /docs/user-guide/secrets/
+  - title: Names
+    path: /docs/user-guide/identifiers/
+  - title: Namespaces
+    path: /docs/user-guide/namespaces/
+  - title: Nodes
+    path: /docs/admin/node/
+  - title: Service Accounts
+    path: /docs/user-guide/service-accounts/
+  - title: Annotations
+    path: /docs/user-guide/annotations/
+  - title: Daemon Sets
+    path: /docs/admin/daemons/
+  - title: Deployments
+    path: /docs/user-guide/deployments/
+  - title: Ingress Resources
+    path: /docs/user-guide/ingress/
+  - title: Horizontal Pod Autoscaling
+    path: /docs/user-guide/horizontal-pod-autoscaler/
+  - title: Jobs
+    path: /docs/user-guide/jobs/
+  - title: Resource Quotas
+    path: /docs/admin/resource-quota/
+
+- title: Kubernetes Design Docs
+  section:
+  - title: Kubernetes Architecture
+    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/architecture.md
+  - title: Kubernetes Design Overview
+    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/
+  - title: Security in Kubernetes
+    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/security.md
+  - title: Kubernetes Identity and Access Management
+    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/access.md
+  - title: Security Contexts
+    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/security_context.md
+  - title: Kubernetes OpenVSwitch GRE/VxLAN networking
+    path: /docs/admin/ovs-networking/
\ No newline at end of file
diff --git a/_data/v1_2/samples.yml b/_data/samples.yml
similarity index 97%
rename from _data/v1_2/samples.yml
rename to _data/samples.yml
index 3ae4cf2f37..632d4039e4 100644
--- a/_data/v1_2/samples.yml
+++ b/_data/samples.yml
@@ -2,7 +2,7 @@ bigheader: "Samples"
 abstract: "A collection of example applications that show how to use Kubernetes."
 toc:
 - title: Samples
-  path: /v1.2/samples/
+  path: /docs/samples/
 
 - title: Clustered Application Samples
   section:
@@ -31,7 +31,7 @@ toc:
   - title: Ceph
     path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/rbd/
   - title: MEAN stack on Google Cloud Platform
-    path: /v1.2/docs/getting-started-guides/meanstack/
+    path: /docs/getting-started-guides/meanstack/
 
 - title: Persistent Volume Samples
   section:
diff --git a/_data/v1_1/support.yml b/_data/support.yml
similarity index 73%
rename from _data/v1_1/support.yml
rename to _data/support.yml
index 18445ec996..84bdc593f3 100644
--- a/_data/v1_1/support.yml
+++ b/_data/support.yml
@@ -2,16 +2,16 @@ bigheader: "Support"
 abstract: "Troubleshooting resources, frequently asked questions, and community support channels."
 toc:
 - title: Support
-  path: /v1.1/docs/troubleshooting/
+  path: /docs/troubleshooting/
 
 - title: Troubleshooting
   section:
   - title: Web Interface
-    path: /v1.1/docs/user-guide/ui/
+    path: /docs/user-guide/ui/
   - title: Troubleshooting Applications
-    path: /v1.1/docs/user-guide/application-troubleshooting/
+    path: /docs/user-guide/application-troubleshooting/
   - title: Troubleshooting Clusters
-    path: /v1.1/docs/admin/cluster-troubleshooting/
+    path: /docs/admin/cluster-troubleshooting/
 
 - title: Frequently Asked Questions
   section:
@@ -25,16 +25,16 @@ toc:
 - title: Other Resources
   section:
   - title: Known Issues
-    path: /v1.1/docs/user-guide/known-issues/
+    path: /docs/user-guide/known-issues/
   - title: Kubernetes Issue Tracker on GitHub
     path: https://github.com/kubernetes/kubernetes/issues/
   - title: Report a Security Vulnerability
-    path: /v1.1/docs/reporting-security-issues/
+    path: /docs/reporting-security-issues/
   - title: Release Notes
     path: https://github.com/kubernetes/kubernetes/releases/
   - title: Release Roadmap
-    path: /v1.1/docs/roadmap/
+    path: /docs/roadmap/
   - title: Contributing to Kubernetes Documentation
-    path: /v1.1/editdocs/
+    path: /docs/editdocs/
   - title: Sitemap for v1.1
-    path: /v1.1/pagelist/
+    path: /docs/pagelist/
diff --git a/_data/v1_1/reference.yml b/_data/v1_1/reference.yml
deleted file mode 100644
index d98defda46..0000000000
--- a/_data/v1_1/reference.yml
+++ /dev/null
@@ -1,184 +0,0 @@
-bigheader: "Reference Documentation"
-abstract: "Design docs, concept definitions, and references for APIs and CLIs."
-toc:
-- title: Reference Documentation
-  path: /v1.1/reference/
-
-- title: Kubernetes API
-  section:
-  - title: Kubernetes API Overview
-    path: /v1.1/docs/api/
-  - title: Kubernetes API Operations
-    path: http://kubernetes.io/v1.1/docs/api-reference/v1/operations.html
-  - title: Kubernetes API Definitions
-    path: http://kubernetes.io/v1.1/docs/api-reference/v1/definitions.html
-
-- title: Extensions API
-  section:
-  - title: Extensions API Operations
-    path: http://kubernetes.io/v1.1/docs/api-reference/extensions/v1beta1/operations.html
-  - title: Extensions API Definitions
-    path: http://kubernetes.io/v1.1/docs/api-reference/extensions/v1beta1/definitions.html
-
-- title: kubectl
-  section:
-  - title: kubectl Overview
-    path: /v1.1/docs/user-guide/kubectl-overview/
-  - title: kubectl for Docker Users
-    path: /v1.1/docs/user-guide/docker-cli-to-kubectl/
-  - title: kubectl Commands
-    section:
-    - title: kubectl
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl.md
-    - title: kubectl annotate
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_annotate.md
-    - title: kubectl api-versions
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_api-versions.md
-    - title: kubectl apply
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_apply.md
-    - title: kubectl attach
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_attach.md
-    - title: kubectl autoscale
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_autoscale.md
-    - title: kubectl cluster-info
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_cluster-info.md
-    - title: kubectl config
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config.md
-    - title: kubectl config set-cluster
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_set-cluster.md
-    - title: kubectl config set-context
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_set-context.md
-    - title: kubectl set-credentials
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_set-credentials.md
-    - title: kubectl config set
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_set.md
-    - title: kubectl config unset
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_unset.md
-    - title: kubectl config use-context
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_use-context.md
-    - title: kubectl config view
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_view.md
-    - title: kubectl create
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_create.md
-    - title: kubectl delete
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_delete.md
-    - title: kubectl describe
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_describe.md
-    - title: kubectl edit
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_edit.md
-    - title: kubectl exec
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_exec.md
-    - title: kubectl expose
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_expose.md
-    - title: kubectl get
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_get.md
-    - title: kubectl label
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_label.md
-    - title: kubectl logs
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_logs.md
-    - title: kubectl patch
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_patch.md
-    - title: kubectl port-forward
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_port-forward.md
-    - title: kubectl proxy
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_proxy.md
-    - title: kubectl replace
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_replace.md
-    - title: kubectl rolling-update
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_rolling-update.md
-    - title: kubectl run
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_run.md
-    - title: kubectl scale
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_scale.md
-    - title: kubectl stop
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_stop.md
-    - title: kubectl version
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_version.md
-
-- title: kube-apiserver
-  section:
-  - title: Overview
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/admin/kube-apiserver.md
-  - title: Authorization Plugins
-    path: /v1.1/docs/admin/authorization/
-  - title: Authentication
-    path: /v1.1/docs/admin/authentication/
-  - title: Accessing the API
-    path: /v1.1/docs/admin/accessing-the-api/
-  - title: Admission Controllers
-    path: /v1.1/docs/admin/admission-controllers/
-  - title: Managing Service Accounts
-    path: /v1.1/docs/admin/service-accounts-admin/
-
-- title: kub-scheduler
-  path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/admin/kube-scheduler.md
-
-- title: kubelet
-  path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/admin/kubelet.md
-
-- title: kube-proxy
-  path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/admin/kube-proxy.md
-
-- title: JSONpath
-  path: /v1.1/docs/user-guide/jsonpath/
-
-- title: etcd
-  path: /v1.1/docs/admin/etcd/
-
-- title: Concept Definitions
-  section:
-  - title: Container Environment
-    path: /v1.1/docs/user-guide/container-environment/
-  - title: Images
-    path: /v1.1/docs/user-guide/images/
-  - title: Pods
-    path: /v1.1/docs/user-guide/pods/
-  - title: Labels and Selectors
-    path: /v1.1/docs/user-guide/labels/
-  - title: Replication Controller
-    path: /v1.1/docs/user-guide/replication-controller/
-  - title: Services
-    path: /v1.1/docs/user-guide/services/
-  - title: Volumes
-    path: /v1.1/docs/user-guide/volumes/
-  - title: Persistent Volumes
-    path: /v1.1/docs/user-guide/persistent-volumes/
-  - title: Secrets
-    path: /v1.1/docs/user-guide/secrets/
-  - title: Names
-    path: /v1.1/docs/user-guide/identifiers/
-  - title: Namespaces
-    path: /v1.1/docs/user-guide/namespaces/
-  - title: Nodes
-    path: /v1.1/docs/admin/node/
-  - title: Service Accounts
-    path: /v1.1/docs/user-guide/service-accounts/
-  - title: Annotations
-    path: /v1.1/docs/user-guide/annotations/
-  - title: Daemon Sets
-    path: /v1.1/docs/admin/daemons/
-  - title: Deployments
-    path: /v1.1/docs/user-guide/deployments/
-  - title: Ingress Resources
-    path: /v1.1/docs/user-guide/ingress/
-  - title: Horizontal Pod Autoscaling
-    path: /v1.1/docs/user-guide/horizontal-pod-autoscaler/
-  - title: Jobs
-    path: /v1.1/docs/user-guide/jobs/
-  - title: Resource Quotas
-    path: /v1.1/docs/admin/resource-quota/
-
-- title: Kubernetes Design Docs
-  section:
-  - title: Kubernetes Architecture
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/architecture.md
-  - title: Kubernetes Design Overview
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/
-  - title: Security in Kubernetes
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/security.md
-  - title: Kubernetes Identity and Access Management
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/access.md
-  - title: Security Contexts
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/security_context.md
-  - title: Kubernetes OpenVSwitch GRE/VxLAN networking
-    path: /v1.1/docs/admin/ovs-networking/
\ No newline at end of file
diff --git a/_data/v1_1/samples.yml b/_data/v1_1/samples.yml
deleted file mode 100644
index fb7240d0ef..0000000000
--- a/_data/v1_1/samples.yml
+++ /dev/null
@@ -1,54 +0,0 @@
-bigheader: "Samples"
-abstract: "A collection of example applications that show how to use Kubernetes."
-toc:
-- title: Samples
-  path: /v1.1/samples/
-
-- title: Clustered Application Samples
-  section:
-  - title: Apache Cassandra Database
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/cassandra
-  - title: Apache Spark
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/spark
-  - title: Apache Storm
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/storm
-  - title: Distributed Task Queue
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/celery-rabbitmq
-  - title: Hazelcast
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/hazelcast
-  - title: Meteor Applications
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/meteor/
-  - title: Redis
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/redis/
-  - title: RethinkDB
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/rethinkdb/
-  - title: Elasticsearch/Kibana Logging Demonstration
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/logging-demo/
-  - title: Elasticsearch
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/elasticsearch/
-  - title: OpenShift Origin
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/openshift-origin/
-  - title: Ceph
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/rbd/
-  - title: MEAN stack on Google Cloud Platform
-    path: /v1.1/docs/getting-started-guides/meanstack/
-
-- title: Persistent Volume Samples
-  section:
-  - title: WordPress on a Kubernetes Persistent Volume
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/mysql-wordpress-pd/
-  - title: GlusterFS
-    path: /https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/glusterfs/
-  - title: iSCSI
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/iscsi/
-  - title: NFS
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/nfs/
-
-- title: Multi-tier Application Samples
-  section:
-  - title: Guestbook - Go Server
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/guestbook-go/
-  - title: GuestBook - PHP Server
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/guestbook/
-  - title: MySQL - Phabricator Server
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/phabricator/
diff --git a/_data/v1_2/globals.yml b/_data/v1_2/globals.yml
deleted file mode 100644
index fd3be92a16..0000000000
--- a/_data/v1_2/globals.yml
+++ /dev/null
@@ -1,5 +0,0 @@
-tocs:
-- guides
-- reference
-- samples
-- support
\ No newline at end of file
diff --git a/_data/v1_2/guides.yml b/_data/v1_2/guides.yml
deleted file mode 100644
index b36d4a5101..0000000000
--- a/_data/v1_2/guides.yml
+++ /dev/null
@@ -1,179 +0,0 @@
-bigheader: "Guides"
-abstract: "How to get started, and acheive tasks, using Kubernetes"
-toc:
-- title: Guides
-  path: /v1.2/
-
-- title: Quickstarts
-  section:
-  - title: What is Kubernetes?
-    path: /v1.2/docs/whatisk8s/
-  - title: TODO - 5-minute Quickstart
-    path: /v1.2/docs/hellonode/
-  - title: Kubernetes 101
-    path: /v1.2/docs/user-guide/walkthrough/
-  - title: Kubernetes 201
-    path: /v1.2/docs/user-guide/walkthrough/k8s201/
-
-- title: Running Kubernetes
-  section:
-  - title: Picking the Right Solution
-    path: /v1.2/docs/getting-started-guides/
-  - title: Running Kubernetes on Your Local Machine
-    section:
-    - title: Running Kubernetes Locally via Docker
-      path: /v1.2/docs/getting-started-guides/docker/
-    - title: Running Kubernetes Locally via Vagrant
-      path: /v1.2/docs/getting-started-guides/vagrant/
-    - title: Running Kubernetes Locally with No VM
-      path: /v1.2/docs/getting-started-guides/locally/
-  - title: Running Kubernetes on Turn-key Cloud Solutions
-    section:
-    - title: Running Kubernetes on Google Container Engine
-      path: https://cloud.google.com/container-engine/docs/before-you-begin/
-    - title: Running Kubernetes on Google Compute Engine
-      path: /v1.2/docs/getting-started-guides/gce/
-    - title: Running Kubernetes on AWS EC2
-      path: /v1.2/docs/getting-started-guides/aws/
-    - title: Running Kubernetes on Azure
-      path: /v1.2/docs/getting-started-guides/coreos/azure/
-  - title: Running Kubernetes on Custom Solutions
-    section:
-    - title: Getting Started From Scratch
-      path: /v1.2/docs/getting-started-guides/scratch/
-    - title: Custom Cloud Solutions
-      section:
-      - title: AWS or GCE on CoreOS
-        path: /v1.2/docs/getting-started-guides/coreos/
-      - title: AWS or Joyent on Ubuntu
-        path: /v1.2/docs/getting-started-guides/juju/
-      - title: Rackspace on CoreOS
-        path: /v1.2/docs/getting-started-guides/rackspace/
-    - title: On-Premise VMs
-      section:
-      - title: Vagrant or VMware
-        path: /v1.2/docs/getting-started-guides/coreos/
-      - title: Cloudstack
-        path: /v1.2/docs/getting-started-guides/cloudstack/
-      - title: VMWare
-        path: /v1.2/docs/getting-started-guides/vsphere/
-      - title: Juju
-        path: /v1.2/docs/getting-started-guides/juju/
-      - title: libvirt on CoreOS
-        path: /v1.2/docs/getting-started-guides/libvirt-coreos/
-      - title: oVirt
-        path: /v1.2/docs/getting-started-guides/ovirt/
-      - title: libvirt or KVM
-        path: /v1.2/docs/getting-started-guides/fedora/flannel_multi_node_cluster/
-    - title: Bare Metal
-      section:
-      - title: Offline
-        path: /v1.2/docs/getting-started-guides/coreos/bare_metal_offline/
-      - title: Fedora via Ansible
-        path: /v1.2/docs/getting-started-guides/fedora/fedora_ansible_config/
-      - title: Fedora (Single Node)
-        path: /v1.2/docs/getting-started-guides/fedora/fedora_manual_config/
-      - title: Fedora (Multi Node)
-        path: /v1.2/docs/getting-started-guides/fedora/flannel_multi_node_cluster/
-      - title: Centos
-        path: /v1.2/docs/getting-started-guides/centos/centos_manual_config/
-      - title: Ubuntu
-        path: /v1.2/docs/getting-started-guides/ubuntu/
-      - title: Docker (Multi Node)
-        path: /v1.2/docs/getting-started-guides/docker-multinode/
-
-- title: Administering Clusters
-  section:
-  - title: Kubernetes Cluster Admin Guide
-    path: /v1.2/docs/admin/
-  - title: Using Multiple Clusters
-    path: /v1.2/docs/admin/multi-cluster/
-  - title: Using Large Clusters
-    path: /v1.2/docs/admin/cluster-large/
-  - title: Building High-Availability Clusters
-    path: /v1.2/docs/admin/high-availability/
-  - title: Accessing Clusters
-    path: /v1.2/docs/user-guide/accessing-the-cluster/
-  - title: Sharing a Cluster
-    path: /v1.2/docs/admin/namespaces/
-  - title: Changing Cluster Size
-    path: https://github.com/kubernetes/kubernetes/wiki/User-FAQ#how-do-i-change-the-size-of-my-cluster/
-  - title: Creating a Custom Cluster from Scratch
-    path: /v1.2/docs/getting-started-guides/scratch/
-  - title: Authenticating Across Clusters with kubeconfig
-    path: /v1.2/docs/user-guide/kubeconfig-file/
- 
-- title: Using Nodes, Pods, and Containers
-  section:
-  - title: Assigning Pods to Nodes
-    path: /v1.2/docs/user-guide/node-selection/
-  - title: Working with Containers
-    path: /v1.2/docs/user-guide/production-pods/
-  - title: Creating Pods with the Downward API
-    path: /v1.2/docs/user-guide/downward-api/
-  - title: Updating Live Pods
-    path: /v1.2/docs/user-guide/update-demo/
-  - title: Running Commands in a Container with kubectl exec
-    path: /v1.2/docs/user-guide/getting-into-containers/
-
-- title: Networking
-  section:
-  - title: Networking in Kubernetes
-    path: /v1.2/docs/admin/networking/
-  - title: Setting Up and Configuring DNS
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/cluster-dns
-  - title: Connecting Applications
-    path: /v1.2/docs/user-guide/connecting-applications/
-  - title: Creating Servers with External IPs
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/examples/simple-nginx.md
-  - title: Using DNS Pods and Services
-    path: /v1.2/docs/admin/dns/
-  - title: Connect with Proxies
-    path: /v1.2/docs/user-guide/connecting-to-applications-proxy/
-  - title: Connect with Port Forwarding
-    path: /v1.2/docs/user-guide/connecting-to-applications-port-forward/
- 
-- title: Configuring Kubernetes
-  section:
-  - title: Using Configuration Files
-    path: /v1.2/docs/user-guide/simple-yaml/
-  - title: Configuring Containers
-    path: /v1.2/docs/user-guide/configuring-containers/
-  - title: Using Environment Variables
-    path: /v1.2/docs/user-guide/environment-guide/
-  - title: Managing Compute Resources
-    path: /v1.2/docs/user-guide/compute-resources/
-  - title: Applying Resource Quotas and Limits
-    path: /v1.2/docs/admin/resourcequota/
-  - title: Setting Pod CPU and Memory Limits
-    path: /v1.2/docs/admin/limitrange/
-  - title: Configuring Garbage Collection
-    path: /v1.2/docs/admin/garbage-collection/
-  - title: Configuring Kubernetes with Salt
-    path: /v1.2/docs/admin/salt/
-  - title: Best Practices for Configuration
-    path: /v1.2/docs/user-guide/config-best-practices/
-
-- title: Application Management and Deployment
-  section:
-  - title: "Managing Applications: Prerequisites"
-    path: /v1.2/docs/user-guide/prereqs/
-  - title: Managing Deployments
-    path: /v1.2/docs/user-guide/managing-deployments/
-  - title: Deploying Applications
-    path: /v1.2/docs/user-guide/deploying-applications/
-  - title: Launching, Exposing, and Killing Applications
-    path: /v1.2/docs/user-guide/quick-start/
-
-- title: Testing and Monitoring
-  section:
-  - title: Simulating Large Test Loads
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/k8petstore
-  - title: Checking Pod Health
-    path: /v1.2/docs/user-guide/liveness/
-  - title: Using Explorer to Examine the Runtime Environment
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.1/examples/explorer
-  - title: Resource Usage Monitoring
-    path: /v1.2/docs/user-guide/monitoring/
-  - title: Logging
-    path: /v1.2/docs/user-guide/logging/
diff --git a/_data/v1_2/reference.yml b/_data/v1_2/reference.yml
deleted file mode 100644
index c1062cd972..0000000000
--- a/_data/v1_2/reference.yml
+++ /dev/null
@@ -1,184 +0,0 @@
-bigheader: "Reference Documentation"
-abstract: "Design docs, concept definitions, and references for APIs and CLIs."
-toc:
-- title: Reference Documentation
-  path: /v1.2/reference/
-
-- title: Kubernetes API
-  section:
-  - title: Kubernetes API Overview
-    path: /v1.2/docs/api/
-  - title: Kubernetes API Operations
-    path: http://kubernetes.io/v1.2/docs/api-reference/v1/operations.html
-  - title: Kubernetes API Definitions
-    path: http://kubernetes.io/v1.2/docs/api-reference/v1/definitions.html
-
-- title: Extensions API
-  section:
-  - title: Extensions API Operations
-    path: http://kubernetes.io/v1.2/docs/api-reference/extensions/v1beta1/operations.html
-  - title: Extensions API Definitions
-    path: http://kubernetes.io/v1.2/docs/api-reference/extensions/v1beta1/definitions.html
-
-- title: kubectl
-  section:
-  - title: kubectl Overview
-    path: /v1.2/docs/user-guide/kubectl-overview/
-  - title: kubectl for Docker Users
-    path: /v1.2/docs/user-guide/docker-cli-to-kubectl/
-  - title: kubectl Commands
-    section:
-    - title: kubectl
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl.md
-    - title: kubectl annotate
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_annotate.md
-    - title: kubectl api-versions
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_api-versions.md
-    - title: kubectl apply
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_apply.md
-    - title: kubectl attach
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_attach.md
-    - title: kubectl autoscale
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_autoscale.md
-    - title: kubectl cluster-info
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_cluster-info.md
-    - title: kubectl config
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config.md
-    - title: kubectl config set-cluster
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_set-cluster.md
-    - title: kubectl config set-context
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_set-context.md
-    - title: kubectl set-credentials
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_set-credentials.md
-    - title: kubectl config set
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_set.md
-    - title: kubectl config unset
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_unset.md
-    - title: kubectl config use-context
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_use-context.md
-    - title: kubectl config view
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_config_view.md
-    - title: kubectl create
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_create.md
-    - title: kubectl delete
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_delete.md
-    - title: kubectl describe
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_describe.md
-    - title: kubectl edit
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_edit.md
-    - title: kubectl exec
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_exec.md
-    - title: kubectl expose
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_expose.md
-    - title: kubectl get
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_get.md
-    - title: kubectl label
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_label.md
-    - title: kubectl logs
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_logs.md
-    - title: kubectl patch
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_patch.md
-    - title: kubectl port-forward
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_port-forward.md
-    - title: kubectl proxy
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_proxy.md
-    - title: kubectl replace
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_replace.md
-    - title: kubectl rolling-update
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_rolling-update.md
-    - title: kubectl run
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_run.md
-    - title: kubectl scale
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_scale.md
-    - title: kubectl stop
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_stop.md
-    - title: kubectl version
-      path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_version.md
-
-- title: kube-apiserver
-  section:
-  - title: Overview
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/admin/kube-apiserver.md
-  - title: Authorization Plugins
-    path: /v1.2/docs/admin/authorization/
-  - title: Authentication
-    path: /v1.2/docs/admin/authentication/
-  - title: Accessing the API
-    path: /v1.2/docs/admin/accessing-the-api/
-  - title: Admission Controllers
-    path: /v1.2/docs/admin/admission-controllers/
-  - title: Managing Service Accounts
-    path: /v1.2/docs/admin/service-accounts-admin/
-
-- title: kub-scheduler
-  path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/admin/kube-scheduler.md
-
-- title: kubelet
-  path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/admin/kubelet.md
-
-- title: kube-proxy
-  path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/admin/kube-proxy.md
-
-- title: JSONpath
-  path: /v1.2/docs/user-guide/jsonpath/
-
-- title: etcd
-  path: /v1.2/docs/admin/etcd/
-
-- title: Concept Definitions
-  section:
-  - title: Container Environment
-    path: /v1.2/docs/user-guide/container-environment/
-  - title: Images
-    path: /v1.2/docs/user-guide/images/
-  - title: Pods
-    path: /v1.2/docs/user-guide/pods/
-  - title: Labels and Selectors
-    path: /v1.2/docs/user-guide/labels/
-  - title: Replication Controller
-    path: /v1.2/docs/user-guide/replication-controller/
-  - title: Services
-    path: /v1.2/docs/user-guide/services/
-  - title: Volumes
-    path: /v1.2/docs/user-guide/volumes/
-  - title: Persistent Volumes
-    path: /v1.2/docs/user-guide/persistent-volumes/
-  - title: Secrets
-    path: /v1.2/docs/user-guide/secrets/
-  - title: Names
-    path: /v1.2/docs/user-guide/identifiers/
-  - title: Namespaces
-    path: /v1.2/docs/user-guide/namespaces/
-  - title: Nodes
-    path: /v1.2/docs/admin/node/
-  - title: Service Accounts
-    path: /v1.2/docs/user-guide/service-accounts/
-  - title: Annotations
-    path: /v1.2/docs/user-guide/annotations/
-  - title: Daemon Sets
-    path: /v1.2/docs/admin/daemons/
-  - title: Deployments
-    path: /v1.2/docs/user-guide/deployments/
-  - title: Ingress Resources
-    path: /v1.2/docs/user-guide/ingress/
-  - title: Horizontal Pod Autoscaling
-    path: /v1.2/docs/user-guide/horizontal-pod-autoscaler/
-  - title: Jobs
-    path: /v1.2/docs/user-guide/jobs/
-  - title: Resource Quotas
-    path: /v1.2/docs/admin/resource-quota/
-
-- title: Kubernetes Design Docs
-  section:
-  - title: Kubernetes Architecture
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/architecture.md
-  - title: Kubernetes Design Overview
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/
-  - title: Security in Kubernetes
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/security.md
-  - title: Kubernetes Identity and Access Management
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/access.md
-  - title: Security Contexts
-    path: https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/design/security_context.md
-  - title: Kubernetes OpenVSwitch GRE/VxLAN networking
-    path: /v1.2/docs/admin/ovs-networking/
\ No newline at end of file
diff --git a/_data/v1_2/support.yml b/_data/v1_2/support.yml
deleted file mode 100644
index 4185295cc8..0000000000
--- a/_data/v1_2/support.yml
+++ /dev/null
@@ -1,40 +0,0 @@
-bigheader: "Support"
-abstract: "Troubleshooting resources, frequently asked questions, and community support channels."
-toc:
-- title: Support
-  path: /v1.2/docs/troubleshooting/
-
-- title: Troubleshooting
-  section:
-  - title: Web Interface
-    path: /v1.2/docs/user-guide/ui/
-  - title: Troubleshooting Applications
-    path: /v1.2/docs/user-guide/application-troubleshooting/
-  - title: Troubleshooting Clusters
-    path: /v1.2/docs/admin/cluster-troubleshooting/
-
-- title: Frequently Asked Questions
-  section:
-  - title: User FAQ
-    path: https://github.com/kubernetes/kubernetes/wiki/User-FAQ/
-  - title: Debugging FAQ
-    path: https://github.com/kubernetes/kubernetes/wiki/Debugging-FAQ/
-  - title: Services FAQ
-    path: https://github.com/kubernetes/kubernetes/wiki/Services-FAQ/
-
-- title: Other Resources
-  section:
-  - title: Known Issues
-    path: /v1.2/docs/user-guide/known-issues/
-  - title: Kubernetes Issue Tracker on GitHub
-    path: https://github.com/kubernetes/kubernetes/issues/
-  - title: Report a Security Vulnerability
-    path: /v1.2/docs/reporting-security-issues/
-  - title: Release Notes
-    path: https://github.com/kubernetes/kubernetes/releases/
-  - title: Release Roadmap
-    path: /v1.2/docs/roadmap/
-  - title: Contributing to Kubernetes Documentation
-    path: /v1.2/editdocs/
-  - title: Sitemap for v1.2
-    path: /v1.2/pagelist/
diff --git a/_layouts/docwithnav.html b/_layouts/docwithnav.html
index 2c4ffe9c45..c06e0a6942 100755
--- a/_layouts/docwithnav.html
+++ b/_layouts/docwithnav.html
@@ -1,6 +1,6 @@
 ---
 ---
-{% for thistoc in site.data[page.versionfilesafe].globals.tocs %}{% if foundTOC %}{% break %}{% else %}{% assign tree = site.data[page.versionfilesafe][thistoc].toc %}{% include tocsearch.html %}{% endif %}{% endfor %}
+{% for thistoc in site.data.globals.tocs %}{% if foundTOC %}{% break %}{% else %}{% assign tree = site.data[thistoc].toc %}{% include tocsearch.html %}{% endif %}{% endfor %}
 {% if page.title %}{% assign title=page.title %}{% endif %}
 <!Doctype html>
 <html id="docs">
@@ -69,14 +69,14 @@
 
 <!--  HERO  -->
 <section id="hero" class="light-text">
-	<h1>{{ site.data[page.versionfilesafe][foundTOC].bigheader }}</h1>
-	<h5>{{ site.data[page.versionfilesafe][foundTOC].abstract }}</h5>
+	<h1>{{ site.data[foundTOC].bigheader }}</h1>
+	<h5>{{ site.data[foundTOC].abstract }}</h5>
 	<div id="vendorStrip" class="light-text">
 		<ul>
-			<li><a href="/{{page.version}}/">GUIDES</a></li>
-			<li><a href="/{{page.version}}/reference">REFERENCE</a></li>
-			<li><a href="/{{page.version}}/samples">SAMPLES</a></li>
-			<li><a href="/{{page.version}}/docs/troubleshooting/">SUPPORT</a></li>
+			<li><a href="/docs/">GUIDES</a></li>
+			<li><a href="/docs/reference">REFERENCE</a></li>
+			<li><a href="/docs/samples">SAMPLES</a></li>
+			<li><a href="/docs/troubleshooting/">SUPPORT</a></li>
 		</ul>
 		<div class="dropdown">
 			<div class="readout"></div>
@@ -90,10 +90,10 @@
 <section id="encyclopedia">
 	<div id="docsToc">
         <div class="pi-accordion">
-        {% assign tree = site.data[page.versionfilesafe][foundTOC].toc %}{% include tree.html %}
+        {% assign tree = site.data[foundTOC].toc %}{% include tree.html %}
         </div> <!-- /pi-accordion -->
 	</div> <!-- /docsToc -->
-	<div id="docsContent"><a href="/{{ page.version }}/editdocs#{{ page.path }}" id="editPageButton">Edit This Page</a>
+	<div id="docsContent"><a href="/docs/editdocs#{{ page.path }}" id="editPageButton">Edit This Page</a>
     	<h1>{{ title }}</h1>
 		{{ content }}
         <p><a href=""><img src="https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/{{ page.path }}?pixel" alt="Analytics" /></a>
diff --git a/v1.1/docs/admin/accessing-the-api.md b/docs/admin/accessing-the-api.md
similarity index 90%
rename from v1.1/docs/admin/accessing-the-api.md
rename to docs/admin/accessing-the-api.md
index deaf67185b..18532f5155 100644
--- a/v1.1/docs/admin/accessing-the-api.md
+++ b/docs/admin/accessing-the-api.md
@@ -7,7 +7,7 @@ cluster administrators who want to customize their cluster
 or understand the details.
 
 Most questions about accessing the cluster are covered
-in [Accessing the cluster](/{{page.version}}/docs/user-guide/accessing-the-cluster).
+in [Accessing the cluster](/docs/user-guide/accessing-the-cluster).
 
 
 ## Ports and IPs Served On
@@ -27,10 +27,10 @@ By default the Kubernetes APIserver serves HTTP on 2 ports:
     - default is port 6443, change with `--secure-port` flag.
     - default IP is first non-localhost network interface, change with `--bind-address` flag.
     - serves HTTPS.  Set cert with `--tls-cert-file` and key with `--tls-private-key-file` flag.
-    - uses token-file or client-certificate based [authentication](/{{page.version}}/docs/admin/authentication).
-    - uses policy-based [authorization](/{{page.version}}/docs/admin/authorization).
+    - uses token-file or client-certificate based [authentication](/docs/admin/authentication).
+    - uses policy-based [authorization](/docs/admin/authorization).
   3. Removed: ReadOnly Port
-    - For security reasons, this had to be removed. Use the [service account](/{{page.version}}/docs/user-guide/service-accounts) feature instead.
+    - For security reasons, this had to be removed. Use the [service account](/docs/user-guide/service-accounts) feature instead.
 
 ## Proxies and Firewall rules
 
@@ -54,7 +54,7 @@ variety of uses cases:
       running on the `kubernetes-master` machine.  The proxy can use cert-based authentication
       or token-based authentication.
    2. Processes running in Containers on Kubernetes that need to read from
-      the apiserver.  Currently, these can use a [service account](/{{page.version}}/docs/user-guide/service-accounts).
+      the apiserver.  Currently, these can use a [service account](/docs/user-guide/service-accounts).
    3. Scheduler and Controller-manager processes, which need to do read-write
       API operations. Currently, these have to run on the same host as the
       apiserver and use the Localhost Port.  In the future, these will be
diff --git a/v1.2/docs/admin/admission-controllers.md b/docs/admin/admission-controllers.md
similarity index 92%
rename from v1.2/docs/admin/admission-controllers.md
rename to docs/admin/admission-controllers.md
index ae0330ccaf..7596b98fb2 100644
--- a/v1.2/docs/admin/admission-controllers.md
+++ b/docs/admin/admission-controllers.md
@@ -62,12 +62,12 @@ enabling this plug-in.
 
 ### ServiceAccount
 
-This plug-in implements automation for [serviceAccounts](/{{page.version}}/docs/user-guide/service-accounts).
+This plug-in implements automation for [serviceAccounts](/docs/user-guide/service-accounts).
 We strongly recommend using this plug-in if you intend to make use of Kubernetes `ServiceAccount` objects.
 
 ### SecurityContextDeny
 
-This plug-in will deny any pod with a [SecurityContext](/{{page.version}}/docs/user-guide/security-context) that defines options that were not available on the `Container`.
+This plug-in will deny any pod with a [SecurityContext](/docs/user-guide/security-context) that defines options that were not available on the `Container`.
 
 ### ResourceQuota
 
@@ -75,7 +75,7 @@ This plug-in will observe the incoming request and ensure that it does not viola
 enumerated in the `ResourceQuota` object in a `Namespace`.  If you are using `ResourceQuota`
 objects in your Kubernetes deployment, you MUST use this plug-in to enforce quota constraints.
 
-See the [resourceQuota design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_resource_quota.md) and the [example of Resource Quota](/{{page.version}}/docs/admin/resourcequota/) for more details.
+See the [resourceQuota design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_resource_quota.md) and the [example of Resource Quota](/docs/admin/resourcequota/) for more details.
 
 It is strongly encouraged that this plug-in is configured last in the sequence of admission control plug-ins.  This is
 so that quota is not prematurely incremented only for the request to be rejected later in admission control.
@@ -88,7 +88,7 @@ your Kubernetes deployment, you MUST use this plug-in to enforce those constrain
 be used to apply default resource requests to Pods that don't specify any; currently, the default LimitRanger
 applies a 0.1 CPU requirement to all Pods in the `default` namespace.
 
-See the [limitRange design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_limit_range.md) and the [example of Limit Range](/{{page.version}}/docs/admin/limitrange/) for more details.
+See the [limitRange design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_limit_range.md) and the [example of Limit Range](/docs/admin/limitrange/) for more details.
 
 ### InitialResources (experimental)
 
diff --git a/v1.1/docs/admin/authentication.md b/docs/admin/authentication.md
similarity index 100%
rename from v1.1/docs/admin/authentication.md
rename to docs/admin/authentication.md
diff --git a/v1.1/docs/admin/authorization.md b/docs/admin/authorization.md
similarity index 98%
rename from v1.1/docs/admin/authorization.md
rename to docs/admin/authorization.md
index 3f49467808..3c266085b1 100644
--- a/v1.1/docs/admin/authorization.md
+++ b/docs/admin/authorization.md
@@ -2,7 +2,7 @@
 ---
 
 In Kubernetes, authorization happens as a separate step from authentication.
-See the [authentication documentation](/{{page.version}}/docs/admin/authentication) for an
+See the [authentication documentation](/docs/admin/authentication) for an
 overview of authentication.
 
 Authorization applies to all HTTP accesses on the main (secure) apiserver port.
diff --git a/v1.2/docs/admin/cluster-components.md b/docs/admin/cluster-components.md
similarity index 77%
rename from v1.2/docs/admin/cluster-components.md
rename to docs/admin/cluster-components.md
index 0aae00ff96..6a8e42f84b 100644
--- a/v1.2/docs/admin/cluster-components.md
+++ b/docs/admin/cluster-components.md
@@ -15,7 +15,7 @@ unsatisfied).
 Master components could in theory be run on any node in the cluster. However,
 for simplicity, current set up scripts typically start all master components on
 the same VM, and does not run user containers on this VM. See
-[high-availability.md](/{{page.version}}/docs/admin/high-availability) for an example multi-master-VM setup.
+[high-availability.md](/docs/admin/high-availability) for an example multi-master-VM setup.
 
 Even in the future, when Kubernetes is fully self-hosting, it will probably be
 wise to only allow master components to schedule on a subset of nodes, to limit
@@ -24,19 +24,19 @@ node-compromising security exploit.
 
 ### kube-apiserver
 
-[kube-apiserver](/{{page.version}}/docs/admin/kube-apiserver) exposes the Kubernetes API; it is the front-end for the
+[kube-apiserver](/docs/admin/kube-apiserver) exposes the Kubernetes API; it is the front-end for the
 Kubernetes control plane. It is designed to scale horizontally (i.e., one scales
-it by running more of them-- [high-availability.md](/{{page.version}}/docs/admin/high-availability)).
+it by running more of them-- [high-availability.md](/docs/admin/high-availability)).
 
 ### etcd
 
-[etcd](/{{page.version}}/docs/admin/etcd) is used as Kubernetes' backing store. All cluster data is stored here.
+[etcd](/docs/admin/etcd) is used as Kubernetes' backing store. All cluster data is stored here.
 Proper administration of a Kubernetes cluster includes a backup plan for etcd's
 data.
 
 ### kube-controller-manager
 
-[kube-controller-manager](/{{page.version}}/docs/admin/kube-controller-manager) is a binary that runs controllers, which are the
+[kube-controller-manager](/docs/admin/kube-controller-manager) is a binary that runs controllers, which are the
 background threads that handle routine tasks in the cluster. Logically, each
 controller is a separate process, but to reduce the number of moving pieces in
 the system, they are all compiled into a single binary and run in a single
@@ -57,7 +57,7 @@ These controllers include:
 
 ### kube-scheduler
 
-[kube-scheduler](/{{page.version}}/docs/admin/kube-scheduler) watches newly created pods that have no node assigned, and
+[kube-scheduler](/docs/admin/kube-scheduler) watches newly created pods that have no node assigned, and
 selects a node for them to run on.
 
 ### addons
@@ -83,16 +83,16 @@ in their DNS searches.
 #### User interface
 
 The kube-ui provides a read-only overview of the cluster state.  Access
-[the UI using kubectl proxy](/{{page.version}}/docs/user-guide/connecting-to-applications-proxy/#connecting-to-the-kube-ui-service-from-your-local-workstation)
+[the UI using kubectl proxy](/docs/user-guide/connecting-to-applications-proxy/#connecting-to-the-kube-ui-service-from-your-local-workstation)
 
 #### Container Resource Monitoring
 
-[Container Resource Monitoring](/{{page.version}}/docs/user-guide/monitoring) records generic time-series metrics
+[Container Resource Monitoring](/docs/user-guide/monitoring) records generic time-series metrics
 about containers in a central database, and provides a UI for browsing that data.
 
 #### Cluster-level Logging
 
-[Container Logging](/{{page.version}}/docs/user-guide/monitoring.md) saves container logs
+[Container Logging](/docs/user-guide/monitoring.md) saves container logs
 to a central log store with search/browsing interface.  There are two
 implementations:
 
@@ -109,7 +109,7 @@ the Kubernetes runtime environment.
 
 ### kubelet
 
-[kubelet](/{{page.version}}/docs/admin/kubelet) is the primary node agent. It:
+[kubelet](/docs/admin/kubelet) is the primary node agent. It:
 * Watches for pods that have been assigned to its node (either by apiserver
   or via local configuration file) and:
  * Mounts the pod's required volumes
@@ -122,7 +122,7 @@ the Kubernetes runtime environment.
 
 ### kube-proxy
 
-[kube-proxy](/{{page.version}}/docs/admin/kube-proxy) enables the Kubernetes service abstraction by maintaining
+[kube-proxy](/docs/admin/kube-proxy) enables the Kubernetes service abstraction by maintaining
 network rules on the host and performing connection forwarding.
 
 ### docker
diff --git a/v1.2/docs/admin/cluster-large.md b/docs/admin/cluster-large.md
similarity index 97%
rename from v1.2/docs/admin/cluster-large.md
rename to docs/admin/cluster-large.md
index 6c3ade5a91..e1e02d14d6 100644
--- a/v1.2/docs/admin/cluster-large.md
+++ b/docs/admin/cluster-large.md
@@ -66,4 +66,4 @@ To avoid running into cluster addon resource issues, when creating a cluster wit
   * [FluentD with ElasticSearch Plugin](http://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/salt/fluentd-es/fluentd-es.yaml)
   * [FluentD with GCP Plugin](http://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/salt/fluentd-gcp/fluentd-gcp.yaml)
 
-For directions on how to detect if addon containers are hitting resource limits, see the [Troubleshooting section of Compute Resources](/{{page.version}}/docs/user-guide/compute-resources/#troubleshooting).
\ No newline at end of file
+For directions on how to detect if addon containers are hitting resource limits, see the [Troubleshooting section of Compute Resources](/docs/user-guide/compute-resources/#troubleshooting).
\ No newline at end of file
diff --git a/v1.2/docs/admin/cluster-management.md b/docs/admin/cluster-management.md
similarity index 97%
rename from v1.2/docs/admin/cluster-management.md
rename to docs/admin/cluster-management.md
index 8f76f2b16c..f2d340ec62 100644
--- a/v1.2/docs/admin/cluster-management.md
+++ b/docs/admin/cluster-management.md
@@ -8,7 +8,7 @@ running cluster.
 
 ## Creating and configuring a Cluster
 
-To install Kubernetes on a set of machines, consult one of the existing [Getting Started guides](/{{page.version}}/docs/getting-started-guides/) depending on your environment.
+To install Kubernetes on a set of machines, consult one of the existing [Getting Started guides](/docs/getting-started-guides/) depending on your environment.
 
 ## Upgrading a cluster
 
@@ -63,7 +63,7 @@ recommend testing the upgrade on an experimental cluster before performing the u
 
 ## Resizing a cluster
 
-If your cluster runs short on resources you can easily add more machines to it if your cluster is running in [Node self-registration mode](/{{page.version}}/docs/admin/node/#self-registration-of-nodes).
+If your cluster runs short on resources you can easily add more machines to it if your cluster is running in [Node self-registration mode](/docs/admin/node/#self-registration-of-nodes).
 If you're using GCE or GKE it's done by resizing Instance Group managing your Nodes. It can be accomplished by modifying number of instances on `Compute > Compute Engine > Instance groups > your group > Edit group` [Google Cloud Console page](https://console.developers.google.com) or using gcloud CLI:
 
 ```shell
@@ -145,7 +145,7 @@ kubectl replace nodes $NODENAME --patch='{"apiVersion": "v1", "spec": {"unschedu
 
 If you deleted the node's VM instance and created a new one, then a new schedulable node resource will
 be created automatically when you create a new VM instance (if you're using a cloud provider that supports
-node discovery; currently this is only Google Compute Engine, not including CoreOS on Google Compute Engine using kube-register). See [Node](/{{page.version}}/docs/admin/node) for more details.
+node discovery; currently this is only Google Compute Engine, not including CoreOS on Google Compute Engine using kube-register). See [Node](/docs/admin/node) for more details.
 
 ## Advanced Topics
 
diff --git a/v1.1/docs/admin/cluster-troubleshooting.md b/docs/admin/cluster-troubleshooting.md
similarity index 89%
rename from v1.1/docs/admin/cluster-troubleshooting.md
rename to docs/admin/cluster-troubleshooting.md
index cd1c95847f..22d461cd70 100644
--- a/v1.1/docs/admin/cluster-troubleshooting.md
+++ b/docs/admin/cluster-troubleshooting.md
@@ -3,8 +3,8 @@
 
 This doc is about cluster troubleshooting; we assume you have already ruled out your application as the root cause of the
 problem you are experiencing. See
-the [application troubleshooting guide](/{{page.version}}/docs/user-guide/application-troubleshooting) for tips on application debugging.
-You may also visit [troubleshooting document](/{{page.version}}/docs/troubleshooting/) for more information.
+the [application troubleshooting guide](/docs/user-guide/application-troubleshooting) for tips on application debugging.
+You may also visit [troubleshooting document](/docs/troubleshooting/) for more information.
 
 ## Listing your cluster
 
@@ -89,7 +89,7 @@ Mitigations:
 - Action use IaaS providers reliable storage (e.g GCE PD or AWS EBS volume) for VMs with apiserver+etcd
   - Mitigates: Apiserver backing storage lost
 
-- Action: Use (experimental) [high-availability](/{{page.version}}/docs/admin/high-availability) configuration
+- Action: Use (experimental) [high-availability](/docs/admin/high-availability) configuration
   - Mitigates: Master VM shutdown or master components (scheduler, API server, controller-managing) crashing
     - Will tolerate one or more simultaneous node or component failures
   - Mitigates: Apiserver backing storage (i.e., etcd's data directory) lost
@@ -108,5 +108,5 @@ Mitigations:
   - Mitigates: Node shutdown
   - Mitigates: Kubelet software fault
 
-- Action: [Multiple independent clusters](/{{page.version}}/docs/admin/multi-cluster) (and avoid making risky changes to all clusters at once)
+- Action: [Multiple independent clusters](/docs/admin/multi-cluster) (and avoid making risky changes to all clusters at once)
   - Mitigates: Everything listed above.
\ No newline at end of file
diff --git a/v1.1/docs/admin/daemon.yaml b/docs/admin/daemon.yaml
similarity index 100%
rename from v1.1/docs/admin/daemon.yaml
rename to docs/admin/daemon.yaml
diff --git a/v1.1/docs/admin/daemons.md b/docs/admin/daemons.md
similarity index 83%
rename from v1.1/docs/admin/daemons.md
rename to docs/admin/daemons.md
index 5645403d21..a8f3dfba5e 100644
--- a/v1.1/docs/admin/daemons.md
+++ b/docs/admin/daemons.md
@@ -26,30 +26,30 @@ but with different flags and/or different memory and cpu requests for different
 ### Required Fields
 
 As with all other Kubernetes config, a DaemonSet needs `apiVersion`, `kind`, and `metadata` fields.  For
-general information about working with config files, see [here](/{{page.version}}/docs/user-guide/simple-yaml),
-[here](/{{page.version}}/docs/user-guide/configuring-containers), and [here](/{{page.version}}/docs/user-guide/working-with-resources).
+general information about working with config files, see [here](/docs/user-guide/simple-yaml),
+[here](/docs/user-guide/configuring-containers), and [here](/docs/user-guide/working-with-resources).
 
-A DaemonSet also needs a [`.spec`](/{{page.version}}/docs/devel/api-conventions/#spec-and-status) section.
+A DaemonSet also needs a [`.spec`](/docs/devel/api-conventions/#spec-and-status) section.
 
 ### Pod Template
 
 The `.spec.template` is the only required field of the `.spec`.
 
-The `.spec.template` is a [pod template](/{{page.version}}/docs/user-guide/replication-controller/#pod-template).
-It has exactly the same schema as a [pod](/{{page.version}}/docs/user-guide/pods), except
+The `.spec.template` is a [pod template](/docs/user-guide/replication-controller/#pod-template).
+It has exactly the same schema as a [pod](/docs/user-guide/pods), except
 it is nested and does not have an `apiVersion` or `kind`.
 
 In addition to required fields for a pod, a pod template in a DaemonSet has to specify appropriate
 labels (see [pod selector](#pod-selector)).
 
-A pod template in a DaemonSet must have a [`RestartPolicy`](/{{page.version}}/docs/user-guide/pod-states)
+A pod template in a DaemonSet must have a [`RestartPolicy`](/docs/user-guide/pod-states)
  equal to `Always`, or be unspecified, which defaults to `Always`.
 
 ### Pod Selector
 
 The `.spec.selector` field is a pod selector.  It works the same as the `.spec.selector` of
-a [ReplicationController](/{{page.version}}/docs/user-guide/replication-controller) or
-[Job](/{{page.version}}/docs/user-guide/jobs).
+a [ReplicationController](/docs/user-guide/replication-controller) or
+[Job](/docs/user-guide/jobs).
 
 If the `.spec.selector` is specified, it must equal the `.spec.template.metadata.labels`.  If not
 specified, the are default to be equal.  Config with these unequal will be rejected by the API.
@@ -64,7 +64,7 @@ a node for testing.
 
 If you specify a `.spec.template.spec.nodeSelector`, then the DaemonSet controller will
 create pods on nodes which match that [node
-selector](/{{page.version}}/docs/user-guide/node-selection/).
+selector](/docs/user-guide/node-selection/).
 
 If you do not specify a `.spec.template.spec.nodeSelector`, then the DaemonSet controller will
 create pods on all nodes.
@@ -75,7 +75,7 @@ Normally, the machine that a pod runs on is selected by the Kubernetes scheduler
 created by the Daemon controller have the machine already selected (`.spec.nodeName` is specified
 when the pod is created, so it is ignored by the scheduler).  Therefore:
 
- - the [`unschedulable`](/{{page.version}}/docs/admin/node/#manual-node-administration) field of a node is not respected
+ - the [`unschedulable`](/docs/admin/node/#manual-node-administration) field of a node is not respected
    by the daemon set controller.
  - daemon set controller can make pods even when the scheduler has not been started, which can help cluster
    bootstrap.
@@ -88,7 +88,7 @@ Some possible patterns for communicating with pods in a DaemonSet are:
   as a stats database.  They do not have clients.
 - **NodeIP and Known Port**: Pods in the Daemon Set use a `hostPort`, so that the pods are reachable
   via the node IPs.  Clients knows the the list of nodes ips somehow, and know the port by convention.
-- **DNS**: Create a [headless service](/{{page.version}}/docs/user-guide/services/#headless-services) with the same pod selector,
+- **DNS**: Create a [headless service](/docs/user-guide/services/#headless-services) with the same pod selector,
   and then discover DaemonSets using the `endpoints` resource or retrieve multiple A records from
   DNS.
 - **Service**: Create a service with the same pod selector, and use the service to reach a
@@ -140,14 +140,14 @@ use a Daemon Set rather than creating individual pods.
 ### Static Pods
 
 It is possible to create pods by writing a file to a certain directory watched by Kubelet.  These
-are called [static pods](/{{page.version}}/docs/admin/static-pods).
+are called [static pods](/docs/admin/static-pods).
 Unlike DaemonSet, static pods cannot be managed with kubectl
 or other Kubernetes API clients.  Static pods do not depend on the apiserver, making them useful
 in cluster bootstrapping cases.  Also, static pods may be deprecated in the future.
 
 ### Replication Controller
 
-Daemon Set are similar to [Replication Controllers](/{{page.version}}/docs/user-guide/replication-controller) in that
+Daemon Set are similar to [Replication Controllers](/docs/user-guide/replication-controller) in that
 they both create pods, and those pods have processes which are not expected to terminate (e.g. web servers,
 storage servers).
 
@@ -158,12 +158,12 @@ all or certain hosts, and when it needs to start before other pods.
 
 ## Caveats
 
-DaemonSet objects are in the [`extensions` API Group](/{{page.version}}/docs/api/#api-groups).
+DaemonSet objects are in the [`extensions` API Group](/docs/api/#api-groups).
 DaemonSet is not enabled by default. Enable it by setting
 `--runtime-config=extensions/v1beta1/daemonsets=true` on the api server. This can be
 achieved by exporting ENABLE_DAEMONSETS=true before running kube-up.sh script
 on GCE.
 
-DaemonSet objects effectively have [API version `v1alpha1`](/{{page.version}}/docs/api/)#api-versioning).
+DaemonSet objects effectively have [API version `v1alpha1`](/docs/api/)#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.
\ No newline at end of file
diff --git a/v1.1/docs/admin/dns.md b/docs/admin/dns.md
similarity index 100%
rename from v1.1/docs/admin/dns.md
rename to docs/admin/dns.md
diff --git a/v1.1/docs/admin/etcd.md b/docs/admin/etcd.md
similarity index 88%
rename from v1.1/docs/admin/etcd.md
rename to docs/admin/etcd.md
index e3cb1aa980..2db4077729 100644
--- a/v1.1/docs/admin/etcd.md
+++ b/docs/admin/etcd.md
@@ -13,7 +13,7 @@ internet at large), because access to etcd is equivalent to root in your
 cluster.
 
 Data Reliability: for reasonable safety, either etcd needs to be run as a
-[cluster](/{{page.version}}/docs/admin/high-availability/#clustering-etcd) (multiple machines each running
+[cluster](/docs/admin/high-availability/#clustering-etcd) (multiple machines each running
 etcd) or etcd's data directory should be located on durable storage (e.g., GCE's
 persistent disk). In either case, if high availability is required--as it might
 be in a production cluster--the data directory ought to be [backed up
@@ -30,7 +30,7 @@ be run on master VMs. The default location that kubelet scans for manifests is
 ## Kubernetes's usage of etcd
 
 By default, Kubernetes objects are stored under the `/registry` key in etcd.
-This path can be prefixed by using the [kube-apiserver](/{{page.version}}/docs/admin/kube-apiserver) flag
+This path can be prefixed by using the [kube-apiserver](/docs/admin/kube-apiserver) flag
 `--etcd-prefix="/foo"`.
 
 `etcd` is the only place that Kubernetes keeps state.
diff --git a/v1.1/docs/admin/garbage-collection.md b/docs/admin/garbage-collection.md
similarity index 100%
rename from v1.1/docs/admin/garbage-collection.md
rename to docs/admin/garbage-collection.md
diff --git a/v1.1/docs/admin/high-availability.md b/docs/admin/high-availability.md
similarity index 90%
rename from v1.1/docs/admin/high-availability.md
rename to docs/admin/high-availability.md
index 0d28e3dad6..986aae6285 100644
--- a/v1.1/docs/admin/high-availability.md
+++ b/docs/admin/high-availability.md
@@ -3,7 +3,7 @@
 
 This document describes how to build a high-availability (HA) Kubernetes cluster.  This is a fairly advanced topic.
 Users who merely want to experiment with Kubernetes are encouraged to use configurations that are simpler to set up such as
-the simple [Docker based single node cluster instructions](/{{page.version}}/docs/getting-started-guides/docker),
+the simple [Docker based single node cluster instructions](/docs/getting-started-guides/docker),
 or try [Google Container Engine](https://cloud.google.com/container-engine/) for hosted Kubernetes.
 
 Also, at this time high availability support for Kubernetes is not continuously tested in our end-to-end (e2e) testing.  We will
@@ -53,11 +53,11 @@ choices. For example, on systemd-based systems (e.g. RHEL, CentOS), you can run
 If you are extending from a standard Kubernetes installation, the `kubelet` binary should already be present on your system.  You can run
 `which kubelet` to determine if the binary is in fact installed.  If it is not installed,
 you should install the [kubelet binary](https://storage.googleapis.com/kubernetes-release/release/v0.19.3/bin/linux/amd64/kubelet), the
-[kubelet init file](http://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/salt/kubelet/initd) and [high-availability/default-kubelet](/{{page.version}}/docs/admin/high-availability/default-kubelet)
+[kubelet init file](http://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/salt/kubelet/initd) and [high-availability/default-kubelet](/docs/admin/high-availability/default-kubelet)
 scripts.
 
-If you are using monit, you should also install the monit daemon (`apt-get install monit`) and the [high-availability/monit-kubelet](/{{page.version}}/docs/admin/high-availability/monit-kubelet) and
-[high-availability/monit-docker](/{{page.version}}/docs/admin/high-availability/monit-docker) configs.
+If you are using monit, you should also install the monit daemon (`apt-get install monit`) and the [high-availability/monit-kubelet](/docs/admin/high-availability/monit-kubelet) and
+[high-availability/monit-docker](/docs/admin/high-availability/monit-docker) configs.
 
 On systemd systems you `systemctl enable kubelet` and `systemctl enable docker`.
 
@@ -86,7 +86,7 @@ First, hit the etcd discovery service to create a new token:
 curl https://discovery.etcd.io/new?size=3
 ```
 
-On each node, copy the [etcd.yaml](/{{page.version}}/docs/admin/high-availability/etcd.yaml) file into `/etc/kubernetes/manifests/etcd.yaml`
+On each node, copy the [etcd.yaml](/docs/admin/high-availability/etcd.yaml) file into `/etc/kubernetes/manifests/etcd.yaml`
 
 The kubelet on each node actively monitors the contents of that directory, and it will create an instance of the `etcd`
 server from the definition of the pod specified in `etcd.yaml`.
@@ -156,7 +156,7 @@ The easiest way to create this directory, may be to copy it from the master node
 
 ### Starting the API Server
 
-Once these files exist, copy the [kube-apiserver.yaml](/{{page.version}}/docs/admin/high-availability/kube-apiserver.yaml) into `/etc/kubernetes/manifests/` on each master node.
+Once these files exist, copy the [kube-apiserver.yaml](/docs/admin/high-availability/kube-apiserver.yaml) into `/etc/kubernetes/manifests/` on each master node.
 
 The kubelet monitors this directory, and will automatically create an instance of the `kube-apiserver` container using the pod definition specified
 in the file.
@@ -197,11 +197,11 @@ touch /var/log/kube-controller-manager.log
 ```
 
 Next, set up the descriptions of the scheduler and controller manager pods on each node.
-by copying [kube-scheduler.yaml](/{{page.version}}/docs/admin/high-availability/kube-scheduler.yaml) and [kube-controller-manager.yaml](high-availability//{{page.version}}/docs/admin/kube-controller-manager.yaml) into the `/srv/kubernetes/` directory.
+by copying [kube-scheduler.yaml](/docs/admin/high-availability/kube-scheduler.yaml) and [kube-controller-manager.yaml](high-availability//{{page.version}}/docs/admin/kube-controller-manager.yaml) into the `/srv/kubernetes/` directory.
 
 ### Running the podmaster
 
-Now that the configuration files are in place, copy the [podmaster.yaml](/{{page.version}}/docs/admin/high-availability/podmaster.yaml) config file into `/etc/kubernetes/manifests/`
+Now that the configuration files are in place, copy the [podmaster.yaml](/docs/admin/high-availability/podmaster.yaml) config file into `/etc/kubernetes/manifests/`
 
 As before, the kubelet on the node monitors this directory, and will start an instance of the podmaster using the pod specification provided in `podmaster.yaml`.
 
diff --git a/v1.1/docs/admin/high-availability/default-kubelet b/docs/admin/high-availability/default-kubelet
similarity index 100%
rename from v1.1/docs/admin/high-availability/default-kubelet
rename to docs/admin/high-availability/default-kubelet
diff --git a/v1.1/docs/admin/high-availability/etcd.yaml b/docs/admin/high-availability/etcd.yaml
similarity index 100%
rename from v1.1/docs/admin/high-availability/etcd.yaml
rename to docs/admin/high-availability/etcd.yaml
diff --git a/v1.1/docs/admin/high-availability/kube-apiserver.yaml b/docs/admin/high-availability/kube-apiserver.yaml
similarity index 100%
rename from v1.1/docs/admin/high-availability/kube-apiserver.yaml
rename to docs/admin/high-availability/kube-apiserver.yaml
diff --git a/v1.1/docs/admin/high-availability/kube-controller-manager.yaml b/docs/admin/high-availability/kube-controller-manager.yaml
similarity index 100%
rename from v1.1/docs/admin/high-availability/kube-controller-manager.yaml
rename to docs/admin/high-availability/kube-controller-manager.yaml
diff --git a/v1.1/docs/admin/high-availability/kube-scheduler.yaml b/docs/admin/high-availability/kube-scheduler.yaml
similarity index 100%
rename from v1.1/docs/admin/high-availability/kube-scheduler.yaml
rename to docs/admin/high-availability/kube-scheduler.yaml
diff --git a/v1.1/docs/admin/high-availability/monit-docker b/docs/admin/high-availability/monit-docker
similarity index 100%
rename from v1.1/docs/admin/high-availability/monit-docker
rename to docs/admin/high-availability/monit-docker
diff --git a/v1.1/docs/admin/high-availability/monit-kubelet b/docs/admin/high-availability/monit-kubelet
similarity index 100%
rename from v1.1/docs/admin/high-availability/monit-kubelet
rename to docs/admin/high-availability/monit-kubelet
diff --git a/v1.1/docs/admin/high-availability/podmaster.yaml b/docs/admin/high-availability/podmaster.yaml
similarity index 100%
rename from v1.1/docs/admin/high-availability/podmaster.yaml
rename to docs/admin/high-availability/podmaster.yaml
diff --git a/v1.2/docs/admin/index.md b/docs/admin/index.md
similarity index 60%
rename from v1.2/docs/admin/index.md
rename to docs/admin/index.md
index b9d0f41a33..95a1aec99a 100644
--- a/v1.2/docs/admin/index.md
+++ b/docs/admin/index.md
@@ -2,7 +2,7 @@
 ---
 
 The cluster admin guide is for anyone creating or administering a Kubernetes cluster.
-It assumes some familiarity with concepts in the [User Guide](/{{page.version}}/docs/user-guide/).
+It assumes some familiarity with concepts in the [User Guide](/docs/user-guide/).
 
 * TOC
 {:toc}
@@ -10,7 +10,7 @@ It assumes some familiarity with concepts in the [User Guide](/{{page.version}}/
 ## Planning a cluster
 
 There are many different examples of how to setup a kubernetes cluster.  Many of them are listed in this
-[matrix](/{{page.version}}/docs/getting-started-guides/).  We call each of the combinations in this matrix a *distro*.
+[matrix](/docs/getting-started-guides/).  We call each of the combinations in this matrix a *distro*.
 
 Before choosing a particular guide, here are some things to consider:
 
@@ -27,52 +27,52 @@ Before choosing a particular guide, here are some things to consider:
  - Not all distros are maintained as actively.  Prefer ones which are listed as tested on a more recent version of
    Kubernetes.
  - If you are configuring kubernetes on-premises, you will need to consider what [networking
-   model](/{{page.version}}/docs/admin/networking) fits best.
- - If you are designing for very high-availability, you may want [clusters in multiple zones](/{{page.version}}/docs/admin/multi-cluster).
+   model](/docs/admin/networking) fits best.
+ - If you are designing for very high-availability, you may want [clusters in multiple zones](/docs/admin/multi-cluster).
  - You may want to familiarize yourself with the various
-   [components](/{{page.version}}/docs/admin/cluster-components) needed to run a cluster.
+   [components](/docs/admin/cluster-components) needed to run a cluster.
 
 ## Setting up a cluster
 
-Pick one of the Getting Started Guides from the [matrix](/{{page.version}}/docs/getting-started-guides/) and follow it.
+Pick one of the Getting Started Guides from the [matrix](/docs/getting-started-guides/) and follow it.
 If none of the Getting Started Guides fits, you may want to pull ideas from several of the guides.
 
-One option for custom networking is *OpenVSwitch GRE/VxLAN networking* ([ovs-networking.md](/{{page.version}}/docs/admin/ovs-networking)), which
+One option for custom networking is *OpenVSwitch GRE/VxLAN networking* ([ovs-networking.md](/docs/admin/ovs-networking)), which
 uses OpenVSwitch to set up networking between pods across
   Kubernetes nodes.
 
 If you are modifying an existing guide which uses Salt, this document explains [how Salt is used in the Kubernetes
-project](/{{page.version}}/docs/admin/salt).
+project](/docs/admin/salt).
 
 ## Managing a cluster, including upgrades
 
-[Managing a cluster](/{{page.version}}/docs/admin/cluster-management).
+[Managing a cluster](/docs/admin/cluster-management).
 
 ## Managing nodes
 
-[Managing nodes](/{{page.version}}/docs/admin/node).
+[Managing nodes](/docs/admin/node).
 
 ## Optional Cluster Services
 
-* **DNS Integration with SkyDNS** ([dns.md](/{{page.version}}/docs/admin/dns)):
+* **DNS Integration with SkyDNS** ([dns.md](/docs/admin/dns)):
   Resolving a DNS name directly to a Kubernetes service.
 
-* **Logging** with [Kibana](/{{page.version}}/docs/user-guide/logging)
+* **Logging** with [Kibana](/docs/user-guide/logging)
 
 ## Multi-tenant support
 
-* **Resource Quota** ([resource-quota.md](/{{page.version}}/docs/admin/resource-quota))
+* **Resource Quota** ([resource-quota.md](/docs/admin/resource-quota))
 
 ## Security
 
-* **Kubernetes Container Environment** ([docs/user-guide/container-environment.md](/{{page.version}}/docs/user-guide/container-environment)):
+* **Kubernetes Container Environment** ([docs/user-guide/container-environment.md](/docs/user-guide/container-environment)):
   Describes the environment for Kubelet managed containers on a Kubernetes
   node.
 
-* **Securing access to the API Server** [accessing the api](/{{page.version}}/docs/admin/accessing-the-api)
+* **Securing access to the API Server** [accessing the api](/docs/admin/accessing-the-api)
 
-* **Authentication**  [authentication](/{{page.version}}/docs/admin/authentication)
+* **Authentication**  [authentication](/docs/admin/authentication)
 
-* **Authorization** [authorization](/{{page.version}}/docs/admin/authorization)
+* **Authorization** [authorization](/docs/admin/authorization)
 
-* **Admission Controllers** [admission_controllers](/{{page.version}}/docs/admin/admission-controllers)
\ No newline at end of file
+* **Admission Controllers** [admission_controllers](/docs/admin/admission-controllers)
\ No newline at end of file
diff --git a/v1.1/docs/admin/kube-apiserver.md b/docs/admin/kube-apiserver.md
similarity index 100%
rename from v1.1/docs/admin/kube-apiserver.md
rename to docs/admin/kube-apiserver.md
diff --git a/v1.1/docs/admin/kube-controller-manager.md b/docs/admin/kube-controller-manager.md
similarity index 100%
rename from v1.1/docs/admin/kube-controller-manager.md
rename to docs/admin/kube-controller-manager.md
diff --git a/v1.1/docs/admin/kube-proxy.md b/docs/admin/kube-proxy.md
similarity index 100%
rename from v1.1/docs/admin/kube-proxy.md
rename to docs/admin/kube-proxy.md
diff --git a/v1.1/docs/admin/kube-scheduler.md b/docs/admin/kube-scheduler.md
similarity index 100%
rename from v1.1/docs/admin/kube-scheduler.md
rename to docs/admin/kube-scheduler.md
diff --git a/v1.1/docs/admin/kubelet.md b/docs/admin/kubelet.md
similarity index 100%
rename from v1.1/docs/admin/kubelet.md
rename to docs/admin/kubelet.md
diff --git a/v1.1/docs/admin/limitrange/index.md b/docs/admin/limitrange/index.md
similarity index 95%
rename from v1.1/docs/admin/limitrange/index.md
rename to docs/admin/limitrange/index.md
index 5475b8fc32..efa212d19a 100644
--- a/v1.1/docs/admin/limitrange/index.md
+++ b/docs/admin/limitrange/index.md
@@ -26,11 +26,11 @@ This example demonstrates how limits can be applied to a Kubernetes namespace to
 min/max resource limits per pod.  In addition, this example demonstrates how you can
 apply default resource limits to pods in the absence of an end-user specified value.
 
-See [LimitRange design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_limit_range.md) for more information. For a detailed description of the Kubernetes resource model, see [Resources](/{{page.version}}/docs/user-guide/compute-resources)
+See [LimitRange design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_limit_range.md) for more information. For a detailed description of the Kubernetes resource model, see [Resources](/docs/user-guide/compute-resources)
 
 ## Step 0: Prerequisites
 
-This example requires a running Kubernetes cluster.  See the [Getting Started guides](/{{page.version}}/docs/getting-started-guides/) for how to get started.
+This example requires a running Kubernetes cluster.  See the [Getting Started guides](/docs/getting-started-guides/) for how to get started.
 
 Change to the `<kubernetes>` directory if you're not already there.
 
diff --git a/v1.1/docs/admin/limitrange/invalid-pod.yaml b/docs/admin/limitrange/invalid-pod.yaml
similarity index 100%
rename from v1.1/docs/admin/limitrange/invalid-pod.yaml
rename to docs/admin/limitrange/invalid-pod.yaml
diff --git a/v1.1/docs/admin/limitrange/limits.yaml b/docs/admin/limitrange/limits.yaml
similarity index 100%
rename from v1.1/docs/admin/limitrange/limits.yaml
rename to docs/admin/limitrange/limits.yaml
diff --git a/v1.1/docs/admin/limitrange/namespace.yaml b/docs/admin/limitrange/namespace.yaml
similarity index 100%
rename from v1.1/docs/admin/limitrange/namespace.yaml
rename to docs/admin/limitrange/namespace.yaml
diff --git a/v1.1/docs/admin/limitrange/valid-pod.yaml b/docs/admin/limitrange/valid-pod.yaml
similarity index 100%
rename from v1.1/docs/admin/limitrange/valid-pod.yaml
rename to docs/admin/limitrange/valid-pod.yaml
diff --git a/v1.1/docs/admin/multi-cluster.md b/docs/admin/multi-cluster.md
similarity index 100%
rename from v1.1/docs/admin/multi-cluster.md
rename to docs/admin/multi-cluster.md
diff --git a/v1.2/docs/admin/namespaces.md b/docs/admin/namespaces.md
similarity index 90%
rename from v1.2/docs/admin/namespaces.md
rename to docs/admin/namespaces.md
index 0ea405250f..6a5265eadd 100644
--- a/v1.2/docs/admin/namespaces.md
+++ b/docs/admin/namespaces.md
@@ -37,7 +37,7 @@ The Namespace provides a unique scope for:
 
 ## Usage
 
-Look [here](/{{page.version}}/docs/admin/namespaces/) for an in depth example of namespaces.
+Look [here](/docs/admin/namespaces/) for an in depth example of namespaces.
 
 ### Viewing namespaces
 
@@ -115,8 +115,8 @@ $ kubectl create -f ./my-namespace.yaml
 
 ### Working in namespaces
 
-See [Setting the namespace for a request](/{{page.version}}/docs/user-guide/namespaces/#setting-the-namespace-for-a-request)
-and [Setting the namespace preference](/{{page.version}}/docs/user-guide/namespaces/#setting-the-namespace-preference).
+See [Setting the namespace for a request](/docs/user-guide/namespaces/#setting-the-namespace-for-a-request)
+and [Setting the namespace preference](/docs/user-guide/namespaces/#setting-the-namespace-preference).
 
 ### Deleting a namespace
 
@@ -132,7 +132,7 @@ This delete is asynchronous, so for a time you will see the namespace in the `Te
 
 ## Namespaces and DNS
 
-When you create a [Service](/{{page.version}}/docs/user-guide/services), it creates a corresponding [DNS entry](/{{page.version}}/docs/admin/dns).
+When you create a [Service](/docs/user-guide/services), it creates a corresponding [DNS entry](/docs/admin/dns).
 This entry is of the form `<service-name>.<namespace-name>.svc.cluster.local`, which means
 that if a container just uses `<service-name>` it will resolve to the service which
 is local to a namespace.  This is useful for using the same configuration across
diff --git a/v1.2/docs/admin/namespaces/index.md b/docs/admin/namespaces/index.md
similarity index 92%
rename from v1.2/docs/admin/namespaces/index.md
rename to docs/admin/namespaces/index.md
index 27b2631ecb..9a8e96c57b 100644
--- a/v1.2/docs/admin/namespaces/index.md
+++ b/docs/admin/namespaces/index.md
@@ -5,7 +5,7 @@ Kubernetes _namespaces_ help different projects, teams, or customers to share a
 
 It does this by providing the following:
 
-1. A scope for [Names](/{{page.version}}/docs/user-guide/identifiers).
+1. A scope for [Names](/docs/user-guide/identifiers).
 2. A mechanism to attach authorization and policy to a subsection of the cluster.
 
 Use of multiple namespaces is optional.
@@ -16,8 +16,8 @@ This example demonstrates how to use Kubernetes namespaces to subdivide your clu
 
 This example assumes the following:
 
-1. You have an [existing Kubernetes cluster](/{{page.version}}/docs/getting-started-guides/).
-2. You have a basic understanding of Kubernetes _[pods](/{{page.version}}/docs/user-guide/pods)_, _[services](/{{page.version}}/docs/user-guide/services)_, and _[replication controllers](/{{page.version}}/docs/user-guide/replication-controller)_.
+1. You have an [existing Kubernetes cluster](/docs/getting-started-guides/).
+2. You have a basic understanding of Kubernetes _[pods](/docs/user-guide/pods)_, _[services](/docs/user-guide/services)_, and _[replication controllers](/docs/user-guide/replication-controller)_.
 
 ### Step One: Understand the default namespace
 
@@ -49,7 +49,7 @@ One pattern this organization could follow is to partition the Kubernetes cluste
 
 Let's create two new namespaces to hold our work.
 
-Use the file [`namespace-dev.json`](/{{page.version}}/docs/admin/namespacesnamespace-dev.json) which describes a development namespace:
+Use the file [`namespace-dev.json`](/docs/admin/namespacesnamespace-dev.json) which describes a development namespace:
 
 <!-- BEGIN MUNGE: EXAMPLE namespace-dev.json -->
 
@@ -66,7 +66,7 @@ Use the file [`namespace-dev.json`](/{{page.version}}/docs/admin/namespacesnames
 }
 ```
 
-[Download example](/{{page.version}}/docs/admin/namespacesnamespace-dev.json)
+[Download example](/docs/admin/namespacesnamespace-dev.json)
 <!-- END MUNGE: EXAMPLE namespace-dev.json -->
 
 Create the development namespace using kubectl.
diff --git a/v1.1/docs/admin/namespaces/namespace-dev.json b/docs/admin/namespaces/namespace-dev.json
similarity index 100%
rename from v1.1/docs/admin/namespaces/namespace-dev.json
rename to docs/admin/namespaces/namespace-dev.json
diff --git a/v1.1/docs/admin/namespaces/namespace-prod.json b/docs/admin/namespaces/namespace-prod.json
similarity index 100%
rename from v1.1/docs/admin/namespaces/namespace-prod.json
rename to docs/admin/namespaces/namespace-prod.json
diff --git a/v1.1/docs/admin/networking.md b/docs/admin/networking.md
similarity index 96%
rename from v1.1/docs/admin/networking.md
rename to docs/admin/networking.md
index 9fd86e9c1e..d408c1e590 100644
--- a/v1.1/docs/admin/networking.md
+++ b/docs/admin/networking.md
@@ -5,10 +5,10 @@ Kubernetes approaches networking somewhat differently than Docker does by
 default.  There are 4 distinct networking problems to solve:
 
 1. Highly-coupled container-to-container communications: this is solved by
-   [pods](/{{page.version}}/docs/user-guide/pods) and `localhost` communications.
+   [pods](/docs/user-guide/pods) and `localhost` communications.
 2. Pod-to-Pod communications: this is the primary focus of this document.
-3. Pod-to-Service communications: this is covered by [services](/{{page.version}}/docs/user-guide/services).
-4. External-to-Service communications: this is covered by [services](/{{page.version}}/docs/user-guide/services).
+3. Pod-to-Service communications: this is covered by [services](/docs/user-guide/services).
+4. External-to-Service communications: this is covered by [services](/docs/user-guide/services).
 
 * TOC
 {:toc}
@@ -163,7 +163,7 @@ people have reported success with Flannel and Kubernetes.
 
 ### OpenVSwitch
 
-[OpenVSwitch](/{{page.version}}/docs/admin/ovs-networking) is a somewhat more mature but also
+[OpenVSwitch](/docs/admin/ovs-networking) is a somewhat more mature but also
 complicated way to build an overlay network.  This is endorsed by several of the
 "Big Shops" for networking.
 
diff --git a/v1.2/docs/admin/node.md b/docs/admin/node.md
similarity index 97%
rename from v1.2/docs/admin/node.md
rename to docs/admin/node.md
index 1844b2376f..2539e05450 100644
--- a/v1.2/docs/admin/node.md
+++ b/docs/admin/node.md
@@ -8,7 +8,7 @@
 
 `Node` is a worker machine in Kubernetes, previously known as `Minion`. Node
 may be a VM or physical machine, depending on the cluster. Each node has
-the services necessary to run [Pods](/{{page.version}}/docs/user-guide/pods) and is managed by the master
+the services necessary to run [Pods](/docs/user-guide/pods) and is managed by the master
 components. The services on a node include docker, kubelet and network proxy. See
 [The Kubernetes Node](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/architecture.md#the-kubernetes-node) section in the
 architecture design doc for more details.
@@ -82,7 +82,7 @@ The information is gathered by Kubelet from the node.
 
 ## Node Management
 
-Unlike [Pods](/{{page.version}}/docs/user-guide/pods) and [Services](/{{page.version}}/docs/user-guide/services), a Node is not inherently
+Unlike [Pods](/docs/user-guide/pods) and [Services](/docs/user-guide/services), a Node is not inherently
 created by Kubernetes: it is either taken from cloud providers like Google Compute Engine,
 or from your pool of physical or virtual machines. What this means is that when
 Kubernetes creates a node, it is really just creating an object that represents the node in its internal state.
diff --git a/v1.1/docs/admin/ovs-networking.md b/docs/admin/ovs-networking.md
similarity index 100%
rename from v1.1/docs/admin/ovs-networking.md
rename to docs/admin/ovs-networking.md
diff --git a/v1.1/docs/admin/resource-quota.md b/docs/admin/resource-quota.md
similarity index 90%
rename from v1.1/docs/admin/resource-quota.md
rename to docs/admin/resource-quota.md
index 494f014987..03679248fe 100755
--- a/v1.1/docs/admin/resource-quota.md
+++ b/docs/admin/resource-quota.md
@@ -18,7 +18,7 @@ work like this:
   their resource requests defaulted to match their defined limits. The user is only charged for the
   resources they request in the Resource Quota versus their limits because the request is the minimum
   amount of resource guaranteed by the cluster during scheduling. For more information on over commit,
-  see [compute-resources](/{{page.version}}/docs/user-guide/compute-resources).
+  see [compute-resources](/docs/user-guide/compute-resources).
 - If creating a pod would cause the namespace to exceed any of the limits specified in the
   the Resource Quota for that namespace, then the request will fail with HTTP status
   code `403 FORBIDDEN`.
@@ -26,7 +26,7 @@ work like this:
   of the resources for which quota is enabled, then the POST of the pod will fail with HTTP
   status code `403 FORBIDDEN`.  Hint: Use the LimitRange admission controller to force default
   values of *limits* (then resource *requests* would be equal to *limits* by default, see
-  [admission controller](/{{page.version}}/docs/admin/admission-controllers)) before the quota is checked to avoid this problem.
+  [admission controller](/docs/admin/admission-controllers)) before the quota is checked to avoid this problem.
 
 Examples of policies that could be created using namespaces and quotas are:
 
@@ -52,7 +52,7 @@ Resource Quota is enforced in a particular namespace when there is a
 
 ## Compute Resource Quota
 
-The total sum of [compute resources](/{{page.version}}/docs/user-guide/compute-resources) requested by pods
+The total sum of [compute resources](/docs/user-guide/compute-resources) requested by pods
 in a namespace can be limited.  The following compute resource types are supported:
 
 | ResourceName | Description |
@@ -73,9 +73,9 @@ are supported:
 | pods | Total number of pods  |
 | services | Total number of services |
 | replicationcontrollers | Total number of replication controllers |
-| resourcequotas | Total number of [resource quotas](/{{page.version}}/docs/admin/admission-controllers/#resourcequota) |
+| resourcequotas | Total number of [resource quotas](/docs/admin/admission-controllers/#resourcequota) |
 | secrets | Total number of secrets |
-| persistentvolumeclaims | Total number of [persistent volume claims](/{{page.version}}/docs/user-guide/persistent-volumes/#persistentvolumeclaims) |
+| persistentvolumeclaims | Total number of [persistent volume claims](/docs/user-guide/persistent-volumes/#persistentvolumeclaims) |
 
 For example, `pods` quota counts and enforces a maximum on the number of `pods`
 created in a single namespace.
@@ -147,7 +147,7 @@ restrictions around nodes: pods from several namespaces may run on the same node
 
 ## Example
 
-See a [detailed example for how to use resource quota](/{{page.version}}/docs/admin/resourcequota/).
+See a [detailed example for how to use resource quota](/docs/admin/resourcequota/).
 
 ## Read More
 
diff --git a/v1.1/docs/admin/resourcequota/index.md b/docs/admin/resourcequota/index.md
similarity index 95%
rename from v1.1/docs/admin/resourcequota/index.md
rename to docs/admin/resourcequota/index.md
index 9011d51d37..dab2e6ca64 100644
--- a/v1.1/docs/admin/resourcequota/index.md
+++ b/docs/admin/resourcequota/index.md
@@ -1,8 +1,8 @@
 ---
 ---
 
-This example demonstrates how [resource quota](/{{page.version}}/docs/admin/admission-controllers/#resourcequota) and
-[limitsranger](/{{page.version}}/docs/admin/admission-controllers/#limitranger) can be applied to a Kubernetes namespace.
+This example demonstrates how [resource quota](/docs/admin/admission-controllers/#resourcequota) and
+[limitsranger](/docs/admin/admission-controllers/#limitranger) can be applied to a Kubernetes namespace.
 See [ResourceQuota design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_resource_quota.md) for more information.
 
 This example assumes you have a functional Kubernetes setup.
diff --git a/v1.1/docs/admin/resourcequota/limits.yaml b/docs/admin/resourcequota/limits.yaml
similarity index 100%
rename from v1.1/docs/admin/resourcequota/limits.yaml
rename to docs/admin/resourcequota/limits.yaml
diff --git a/v1.1/docs/admin/resourcequota/namespace.yaml b/docs/admin/resourcequota/namespace.yaml
similarity index 100%
rename from v1.1/docs/admin/resourcequota/namespace.yaml
rename to docs/admin/resourcequota/namespace.yaml
diff --git a/v1.1/docs/admin/resourcequota/quota.yaml b/docs/admin/resourcequota/quota.yaml
similarity index 100%
rename from v1.1/docs/admin/resourcequota/quota.yaml
rename to docs/admin/resourcequota/quota.yaml
diff --git a/v1.1/docs/admin/salt.md b/docs/admin/salt.md
similarity index 100%
rename from v1.1/docs/admin/salt.md
rename to docs/admin/salt.md
diff --git a/v1.2/docs/admin/service-accounts-admin.md b/docs/admin/service-accounts-admin.md
similarity index 94%
rename from v1.2/docs/admin/service-accounts-admin.md
rename to docs/admin/service-accounts-admin.md
index d68383e640..d58922dc07 100644
--- a/v1.2/docs/admin/service-accounts-admin.md
+++ b/docs/admin/service-accounts-admin.md
@@ -2,7 +2,7 @@
 ---
 
 *This is a Cluster Administrator guide to service accounts.  It assumes knowledge of
-the [User Guide to Service Accounts](/{{page.version}}/docs/user-guide/service-accounts).*
+the [User Guide to Service Accounts](/docs/user-guide/service-accounts).*
 
 *Support for authorization and user accounts is planned but incomplete.  Sometimes
 incomplete features are referred to in order to better describe service accounts.*
@@ -38,7 +38,7 @@ Three separate components cooperate to implement the automation around service a
 ### Service Account Admission Controller
 
 The modification of pods is implemented via a plugin
-called an [Admission Controller](/{{page.version}}/docs/admin/admission-controllers). It is part of the apiserver.
+called an [Admission Controller](/docs/admin/admission-controllers). It is part of the apiserver.
 It acts synchronously to modify pods as they are created or updated. When this plugin is active
 (and it is by default on most distributions), then it does the following when a pod is created or modified:
 
diff --git a/v1.1/docs/admin/static-pods.md b/docs/admin/static-pods.md
similarity index 96%
rename from v1.1/docs/admin/static-pods.md
rename to docs/admin/static-pods.md
index 1f53fcfa8c..b322f23fc6 100644
--- a/v1.1/docs/admin/static-pods.md
+++ b/docs/admin/static-pods.md
@@ -85,7 +85,7 @@ static-web-my-minion1   172.17.0.3                              my-minion1/192.1
 
 Labels from the static pod are propagated into the mirror-pod and can be used as usual for filtering.
 
-Notice we cannot delete the pod with the API server (e.g. via [`kubectl`](/{{page.version}}/docs/user-guide/kubectl/kubectl) command), kubelet simply won't remove it.
+Notice we cannot delete the pod with the API server (e.g. via [`kubectl`](/docs/user-guide/kubectl/kubectl) command), kubelet simply won't remove it.
 
 ```shell
 [joe@my-master ~] $ kubectl delete pod static-web-my-minion1
diff --git a/v1.1/docs/api-reference/extensions/v1beta1/definitions.md b/docs/api-reference/extensions/v1beta1/definitions.md
similarity index 100%
rename from v1.1/docs/api-reference/extensions/v1beta1/definitions.md
rename to docs/api-reference/extensions/v1beta1/definitions.md
diff --git a/v1.1/docs/api-reference/extensions/v1beta1/operations.md b/docs/api-reference/extensions/v1beta1/operations.md
similarity index 100%
rename from v1.1/docs/api-reference/extensions/v1beta1/operations.md
rename to docs/api-reference/extensions/v1beta1/operations.md
diff --git a/v1.1/docs/api-reference/v1/definitions.md b/docs/api-reference/v1/definitions.md
similarity index 100%
rename from v1.1/docs/api-reference/v1/definitions.md
rename to docs/api-reference/v1/definitions.md
diff --git a/v1.1/docs/api-reference/v1/operations.md b/docs/api-reference/v1/operations.md
similarity index 100%
rename from v1.1/docs/api-reference/v1/operations.md
rename to docs/api-reference/v1/operations.md
diff --git a/v1.1/docs/api.md b/docs/api.md
similarity index 86%
rename from v1.1/docs/api.md
rename to docs/api.md
index 720817c275..f5bd67a745 100644
--- a/v1.1/docs/api.md
+++ b/docs/api.md
@@ -1,15 +1,15 @@
 ---
 ---
 
-Primary system and API concepts are documented in the [User guide](/{{page.version}}/docs/user-guide/).
+Primary system and API concepts are documented in the [User guide](/docs/user-guide/).
 
-Overall API conventions are described in the [API conventions doc](/{{page.version}}/docs/devel/api-conventions).
+Overall API conventions are described in the [API conventions doc](/docs/devel/api-conventions).
 
 Complete API details are documented via [Swagger](http://swagger.io/). The Kubernetes apiserver (aka "master") exports an API that can be used to retrieve the [Swagger spec](https://github.com/swagger-api/swagger-spec/tree/master/schemas/v1.2) for the Kubernetes API, by default at `/swaggerapi`, and a UI you can use to browse the API documentation at `/swagger-ui`. We also periodically update a [statically generated UI](http://kubernetes.io/third_party/swagger-ui/).
 
-Remote access to the API is discussed in the [access doc](/{{page.version}}/docs/admin/accessing-the-api).
+Remote access to the API is discussed in the [access doc](/docs/admin/accessing-the-api).
 
-The Kubernetes API also serves as the foundation for the declarative configuration schema for the system. The [Kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) command-line tool can be used to create, update, delete, and get API objects.
+The Kubernetes API also serves as the foundation for the declarative configuration schema for the system. The [Kubectl](/docs/user-guide/kubectl/kubectl) command-line tool can be used to create, update, delete, and get API objects.
 
 Kubernetes also stores its serialized state (currently in [etcd](https://coreos.com/docs/distributed-configuration/getting-started-with-etcd/)) in terms of the API resources.
 
@@ -19,7 +19,7 @@ Kubernetes itself is decomposed into multiple components, which interact through
 
 In our experience, any system that is successful needs to grow and change as new use cases emerge or existing ones change. Therefore, we expect the Kubernetes API to continuously change and grow. However, we intend to not break compatibility with existing clients, for an extended period of time. In general, new API resources and new resource fields can be expected to be added frequently. Elimination of resources or fields will require following a deprecation process. The precise deprecation policy for eliminating features is TBD, but once we reach our 1.0 milestone, there will be a specific policy.
 
-What constitutes a compatible change and how to change the API are detailed by the [API change document](/{{page.version}}/docs/devel/api_changes).
+What constitutes a compatible change and how to change the API are detailed by the [API change document](/docs/devel/api_changes).
 
 ## API versioning
 
@@ -35,7 +35,7 @@ software versioning.
 
 
 Different API versions imply different levels of stability and support.  The criteria for each level are described
-in more detail in the [API Changes documentation](/{{page.version}}/docs/devel/api_changes/#alpha-beta-and-stable-versions).  They are summarized here:
+in more detail in the [API Changes documentation](/docs/devel/api_changes/#alpha-beta-and-stable-versions).  They are summarized here:
 
 - Alpha level:
   - The version names contain `alpha` (e.g. `v1alpha1`).
@@ -88,17 +88,17 @@ As of June 4, 2015, the Kubernetes v1 API has been enabled by default. The v1bet
 
 ### v1 conversion tips (from v1beta3)
 
-We're working to convert all documentation and examples to v1. A simple [API conversion tool](/{{page.version}}/docs/admin/cluster-management/#switching-your-config-files-to-a-new-api-version) has been written to simplify the translation process. Use `kubectl create --validate` in order to validate your json or yaml against our Swagger spec.
+We're working to convert all documentation and examples to v1. A simple [API conversion tool](/docs/admin/cluster-management/#switching-your-config-files-to-a-new-api-version) has been written to simplify the translation process. Use `kubectl create --validate` in order to validate your json or yaml against our Swagger spec.
 
 Changes to services are the most significant difference between v1beta3 and v1.
 
 * The `service.spec.portalIP` property is renamed to `service.spec.clusterIP`.
 * The `service.spec.createExternalLoadBalancer` property is removed. Specify `service.spec.type: "LoadBalancer"` to create an external load balancer instead.
-* The `service.spec.publicIPs` property is deprecated and now called `service.spec.deprecatedPublicIPs`. This property will be removed entirely when v1beta3 is removed. The vast majority of users of this field were using it to expose services on ports on the node. Those users should specify `service.spec.type: "NodePort"` instead. Read [External Services](/{{page.version}}/docs/user-guide/services/#external-services) for more info. If this is not sufficient for your use case, please file an issue or contact @thockin.
+* The `service.spec.publicIPs` property is deprecated and now called `service.spec.deprecatedPublicIPs`. This property will be removed entirely when v1beta3 is removed. The vast majority of users of this field were using it to expose services on ports on the node. Those users should specify `service.spec.type: "NodePort"` instead. Read [External Services](/docs/user-guide/services/#external-services) for more info. If this is not sufficient for your use case, please file an issue or contact @thockin.
 
 Some other difference between v1beta3 and v1:
 
-* The `pod.spec.containers[*].privileged` and `pod.spec.containers[*].capabilities` properties are now nested under the `pod.spec.containers[*].securityContext` property. See [Security Contexts](/{{page.version}}/docs/user-guide/security-context).
+* The `pod.spec.containers[*].privileged` and `pod.spec.containers[*].capabilities` properties are now nested under the `pod.spec.containers[*].securityContext` property. See [Security Contexts](/docs/user-guide/security-context).
 * The `pod.spec.host` property is renamed to `pod.spec.nodeName`.
 * The `endpoints.subsets[*].addresses.IP` property is renamed to `endpoints.subsets[*].addresses.ip`.
 * The `pod.status.containerStatuses[*].state.termination` and `pod.status.containerStatuses[*].lastState.termination` properties are renamed to `pod.status.containerStatuses[*].state.terminated` and `pod.status.containerStatuses[*].lastState.terminated` respectively.
@@ -119,11 +119,8 @@ Some important differences between v1beta1/2 and v1beta3:
 * The `labels` query parameter has been renamed to `labelSelector`.
 * The `fields` query parameter has been renamed to `fieldSelector`.
 * The container `entrypoint` has been renamed to `command`, and `command` has been renamed to `args`.
-* Container, volume, and node resources are expressed as nested maps (e.g., `resources{cpu:1}`) rather than as individual fields, and resource values support [scaling suffixes](/{{page.version}}/docs/user-guide/compute-resources/#specifying-resource-quantities) rather than fixed scales (e.g., milli-cores).
+* Container, volume, and node resources are expressed as nested maps (e.g., `resources{cpu:1}`) rather than as individual fields, and resource values support [scaling suffixes](/docs/user-guide/compute-resources/#specifying-resource-quantities) rather than fixed scales (e.g., milli-cores).
 * Restart policy is represented simply as a string (e.g., `"Always"`) rather than as a nested map (`always{}`).
 * Pull policies changed from `PullAlways`, `PullNever`, and `PullIfNotPresent` to `Always`, `Never`, and `IfNotPresent`.
 * The volume `source` is inlined into `volume` rather than nested.
-* Host volumes have been changed from `hostDir` to `hostPath` to better reflect that they can be files or directories.
-
-
-
+* Host volumes have been changed from `hostDir` to `hostPath` to better reflect that they can be files or directories.
\ No newline at end of file
diff --git a/v1.1/docs/devel/api-conventions.md b/docs/devel/api-conventions.md
similarity index 94%
rename from v1.1/docs/devel/api-conventions.md
rename to docs/devel/api-conventions.md
index 806a4fac07..5ae751ad2c 100644
--- a/v1.1/docs/devel/api-conventions.md
+++ b/docs/devel/api-conventions.md
@@ -5,12 +5,12 @@ Updated: 9/20/2015
 
 *This document is oriented at users who want a deeper understanding of the Kubernetes
 API structure, and developers wanting to extend the Kubernetes API.  An introduction to
-using resources with kubectl can be found in [Working with resources](/{{page.version}}/docs/user-guide/working-with-resources).*
+using resources with kubectl can be found in [Working with resources](/docs/user-guide/working-with-resources).*
 
 * TOC
 {:toc}
 
-The conventions of the [Kubernetes API](/{{page.version}}/docs/api/) (and related APIs in the ecosystem) are intended to ease client development and ensure that configuration mechanisms can be implemented that work across a diverse set of use cases consistently.
+The conventions of the [Kubernetes API](/docs/api/) (and related APIs in the ecosystem) are intended to ease client development and ensure that configuration mechanisms can be implemented that work across a diverse set of use cases consistently.
 
 The general style of the Kubernetes API is RESTful - clients create, update, delete, or retrieve a description of an object via the standard HTTP verbs (POST, PUT, DELETE, and GET) - and those APIs preferentially accept and return JSON. Kubernetes also exposes additional endpoints for non-standard verbs and allows alternative content types. All of the JSON accepted and returned by the server has a schema, identified by the "kind" and "apiVersion" fields. Where relevant HTTP header fields exist, they should mirror the content of JSON fields, but the information should not be represented only in the HTTP header.
 
@@ -44,7 +44,7 @@ Kinds are grouped into three categories:
 
    Most objects defined in the system should have an endpoint that returns the full set of resources, as well as zero or more endpoints that return subsets of the full list. Some objects may be singletons (the current user, the system defaults) and may not have lists.
 
-   In addition, all lists that return objects with labels should support label filtering (see [docs/user-guide/labels.md](/{{page.version}}/docs/user-guide/labels), and most lists should support filtering by fields.
+   In addition, all lists that return objects with labels should support label filtering (see [docs/user-guide/labels.md](/docs/user-guide/labels), and most lists should support filtering by fields.
 
    Examples: PodLists, ServiceLists, NodeLists
 
@@ -62,7 +62,7 @@ Kinds are grouped into three categories:
    * `/status`: Used to write just the status portion of a resource. For example, 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/&lt;name&gt;/status" endpoint - the alternate endpoint allows different rules to be applied to the update, and access to be appropriately restricted.
    * `/scale`: Used to read and write the count of a resource in a manner that is independent of the specific resource schema.
 
-   Two additional subresources, `proxy` and `portforward`, provide access to cluster resources as described in [docs/user-guide/accessing-the-cluster.md](/{{page.version}}/docs/user-guide/accessing-the-cluster).
+   Two additional subresources, `proxy` and `portforward`, provide access to cluster resources as described in [docs/user-guide/accessing-the-cluster.md](/docs/user-guide/accessing-the-cluster).
 
 The standard REST verbs (defined below) MUST return singular JSON objects. Some API endpoints may deviate from the strict REST pattern and return resources that are not singular JSON objects, such as streams of JSON objects or unstructured text log data.
 
@@ -83,9 +83,9 @@ These fields are required for proper decoding of the object. They may be populat
 
 Every object kind MUST have the following metadata in a nested object field called "metadata":
 
-* namespace: a namespace is a DNS compatible subdomain that objects are subdivided into. The default namespace is 'default'.  See [docs/user-guide/namespaces.md](/{{page.version}}/docs/user-guide/namespaces) for more.
-* name: a string that uniquely identifies this object within the current namespace (see [docs/user-guide/identifiers.md](/{{page.version}}/docs/user-guide/identifiers)). This value is used in the path when retrieving an individual object.
-* uid: a unique in time and space value (typically an RFC 4122 generated identifier, see [docs/user-guide/identifiers.md](/{{page.version}}/docs/user-guide/identifiers)) used to distinguish between objects with the same name that have been deleted and recreated
+* namespace: a namespace is a DNS compatible subdomain that objects are subdivided into. The default namespace is 'default'.  See [docs/user-guide/namespaces.md](/docs/user-guide/namespaces) for more.
+* name: a string that uniquely identifies this object within the current namespace (see [docs/user-guide/identifiers.md](/docs/user-guide/identifiers)). This value is used in the path when retrieving an individual object.
+* uid: a unique in time and space value (typically an RFC 4122 generated identifier, see [docs/user-guide/identifiers.md](/docs/user-guide/identifiers)) used to distinguish between objects with the same name that have been deleted and recreated
 
 Every object SHOULD have the following metadata in a nested object field called "metadata":
 
@@ -93,8 +93,8 @@ Every object SHOULD have the following metadata in a nested object field called
 * generation: a sequence number representing a specific generation of the desired state. Set by the system and monotonically increasing, per-resource. May be compared, such as for RAW and WAW consistency.
 * creationTimestamp: a string representing an RFC 3339 date of the date and time an object was created
 * deletionTimestamp: a string representing an RFC 3339 date of the date and time after which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource will be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field. Once set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time.
-* labels: a map of string keys and values that can be used to organize and categorize objects (see [docs/user-guide/labels.md](/{{page.version}}/docs/user-guide/labels))
-* annotations: a map of string keys and values that can be used by external tooling to store and retrieve arbitrary metadata about this object (see [docs/user-guide/annotations.md](/{{page.version}}/docs/user-guide/annotations))
+* labels: a map of string keys and values that can be used to organize and categorize objects (see [docs/user-guide/labels.md](/docs/user-guide/labels))
+* annotations: a map of string keys and values that can be used by external tooling to store and retrieve arbitrary metadata about this object (see [docs/user-guide/annotations.md](/docs/user-guide/annotations))
 
 Labels are intended for organizational purposes by end users (select the pods that match this label query). Annotations enable third-party automation and tooling to decorate objects with additional metadata for their own use.
 
@@ -139,7 +139,7 @@ In general, condition values may change back and forth, but some condition trans
 
 A typical oscillating condition type is `Ready`, which indicates the object was believed to be fully operational at the time it was last probed. A possible monotonic condition could be `Succeeded`. A `False` status for `Succeeded` would imply failure. An object that was still active would not have a `Succeeded` condition, or its status would be `Unknown`.
 
-Some resources in the v1 API contain fields called **`phase`**, and associated `message`, `reason`, and other status fields. The pattern of using `phase` is deprecated. Newer API types should use conditions instead. Phase was essentially a state-machine enumeration field, that contradicted [system-design principles](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/principles.md#control-logic) and hampered evolution, since [adding new enum values breaks backward compatibility](/{{page.version}}/docs/devel/api_changes). Rather than encouraging clients to infer implicit properties from phases, we intend to explicitly expose the conditions that clients need to monitor. Conditions also have the benefit that it is possible to create some conditions with uniform meaning across all resource types, while still exposing others that are unique to specific resource types. See [#7856](http://issues.k8s.io/7856) for more details and discussion.
+Some resources in the v1 API contain fields called **`phase`**, and associated `message`, `reason`, and other status fields. The pattern of using `phase` is deprecated. Newer API types should use conditions instead. Phase was essentially a state-machine enumeration field, that contradicted [system-design principles](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/principles.md#control-logic) and hampered evolution, since [adding new enum values breaks backward compatibility](/docs/devel/api_changes). Rather than encouraging clients to infer implicit properties from phases, we intend to explicitly expose the conditions that clients need to monitor. Conditions also have the benefit that it is possible to create some conditions with uniform meaning across all resource types, while still exposing others that are unique to specific resource types. See [#7856](http://issues.k8s.io/7856) for more details and discussion.
 
 In condition types, and everywhere else they appear in the API, **`Reason`** is intended to be a one-word, CamelCase representation of the category of cause of the current status, and **`Message`** is intended to be a human-readable phrase or sentence, which may contain specific details of the individual occurrence. `Reason` is intended to be used in concise output, such as one-line `kubectl get` output, and in summarizing occurrences of causes, whereas `Message` is intended to be presented to users in detailed status explanations, such as `kubectl describe` output.
 
@@ -151,7 +151,7 @@ Some resources report the `observedGeneration`, which is the `generation` most r
 
 #### References to related objects
 
-References to loosely coupled sets of objects, such as [pods](/{{page.version}}/docs/user-guide/pods) overseen by a [replication controller](/{{page.version}}/docs/user-guide/replication-controller), are usually best referred to using a [label selector](/{{page.version}}/docs/user-guide/labels). In order to ensure that GETs of individual objects remain bounded in time and space, these sets may be queried via separate API queries, but will not be expanded in the referring object's status.
+References to loosely coupled sets of objects, such as [pods](/docs/user-guide/pods) overseen by a [replication controller](/docs/user-guide/replication-controller), are usually best referred to using a [label selector](/docs/user-guide/labels). In order to ensure that GETs of individual objects remain bounded in time and space, these sets may be queried via separate API queries, but will not be expanded in the referring object's status.
 
 References to specific objects, especially specific resource versions and/or specific fields of those objects, are specified using the `ObjectReference` type (or other types representing strict subsets of it). Unlike partial URLs, the ObjectReference type facilitates flexible defaulting of fields from the referring object or other contextual information.
 
@@ -298,7 +298,7 @@ labels:
 
 ## Idempotency
 
-All compatible Kubernetes APIs MUST support "name idempotency" and respond with an HTTP status code 409 when a request is made to POST an object that has the same name as an existing object in the system. See [docs/user-guide/identifiers.md](/{{page.version}}/docs/user-guide/identifiers) for details.
+All compatible Kubernetes APIs MUST support "name idempotency" and respond with an HTTP status code 409 when a request is made to POST an object that has the same name as an existing object in the system. See [docs/user-guide/identifiers.md](/docs/user-guide/identifiers) for details.
 
 Names generated by the system may be requested using `metadata.generateName`. GenerateName indicates that the name should be made unique by the server prior to persisting it. A non-empty value for the field indicates the name will be made unique (and the name returned to the client will be different than the name passed). The value of this field will be combined with a unique suffix on the server if the Name field has not been provided. The provided value must be valid within the rules for Name, and may be truncated by the length of the suffix required to make the value unique on the server. If this field is specified, and Name is not present, the server will NOT return a 409 if the generated name exists - instead, it will either return 201 Created or 504 with Reason `ServerTimeout` indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header).
 
@@ -637,7 +637,7 @@ However, we should support conveniences for common cases by default. For example
 
 If the user wants to apply additional labels to the pods that it doesn't select upon, such as to facilitate adoption of pods or in the expectation that some label values will change, they can set the selector to a subset of the pod labels. Similarly, the RC's labels could be initialized to a subset of the pod template's labels, or could include additional/different labels.
 
-For disciplined users managing resources within their own namespaces, it's not that hard to consistently apply schemas that ensure uniqueness. One just needs to ensure that at least one value of some label key in common differs compared to all other comparable resources. We could/should provide a verification tool to check that. However, development of conventions similar to the examples in [Labels](/{{page.version}}/docs/user-guide/labels) make uniqueness straightforward. Furthermore, relatively narrowly used namespaces (e.g., per environment, per application) can be used to reduce the set of resources that could potentially cause overlap.
+For disciplined users managing resources within their own namespaces, it's not that hard to consistently apply schemas that ensure uniqueness. One just needs to ensure that at least one value of some label key in common differs compared to all other comparable resources. We could/should provide a verification tool to check that. However, development of conventions similar to the examples in [Labels](/docs/user-guide/labels) make uniqueness straightforward. Furthermore, relatively narrowly used namespaces (e.g., per environment, per application) can be used to reduce the set of resources that could potentially cause overlap.
 
 In cases where users could be running misc. examples with inconsistent schemas, or where tooling or components need to programmatically generate new objects to be selected, there needs to be a straightforward way to generate unique label sets. A simple way to ensure uniqueness of the set is to ensure uniqueness of a single label value, such as by using a resource name, uid, resource hash, or generation number.
 
diff --git a/v1.1/docs/devel/api_changes.md b/docs/devel/api_changes.md
similarity index 98%
rename from v1.1/docs/devel/api_changes.md
rename to docs/devel/api_changes.md
index 907c6d04fc..16da5a8ebd 100644
--- a/v1.1/docs/devel/api_changes.md
+++ b/docs/devel/api_changes.md
@@ -3,7 +3,7 @@
 
 Before attempting a change to the API, you should familiarize yourself
 with a number of existing API types and with the [API
-conventions](/{{page.version}}/docs/devel/api-conventions).  If creating a new API
+conventions](/docs/devel/api-conventions).  If creating a new API
 type/resource, we also recommend that you first send a PR containing
 just a proposal for the new API types, and that you initially target
 the extensions API (pkg/apis/extensions).
@@ -182,7 +182,7 @@ pass (e.g., `heightInInches` from `height`, and vice versa), which runs just pri
 to conversion. That works fine when the user creates a resource from a hand-written
 configuration -- clients can write either field and read either field, but what about
 creation or update from the output of GET, or update via PATCH (see
-[In-place updates](/{{page.version}}/docs/user-guide/managing-deployments/#in-place-updates-of-resources))?
+[In-place updates](/docs/user-guide/managing-deployments/#in-place-updates-of-resources))?
 In this case, the two fields will conflict, because only one field would be updated
 in the case of an old client that was only aware of the old field (e.g., `height`).
 
@@ -252,7 +252,7 @@ Compatibility for experimental or alpha APIs is not strictly required, but
 breaking compatibility should not be done lightly, as it disrupts all users of the
 feature. Experimental APIs may be removed. Alpha and beta API versions may be deprecated
 and eventually removed wholesale, as described in the [versioning document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/versioning.md).
-Document incompatible changes across API versions under the [conversion tips](/{{page.version}}/docs/api/).
+Document incompatible changes across API versions under the [conversion tips](/docs/api/).
 
 If your change is going to be backward incompatible or might be a breaking change for API
 consumers, please send an announcement to `kubernetes-dev@googlegroups.com` before
@@ -494,7 +494,7 @@ doing!
 
 ## Write end-to-end tests
 
-Check out the [E2E docs](/{{page.version}}/docs/devel/e2e-tests) for detailed information about how to write end-to-end
+Check out the [E2E docs](/docs/devel/e2e-tests) for detailed information about how to write end-to-end
 tests for your feature.
 
 ## Examples and docs
@@ -564,7 +564,7 @@ New feature development proceeds through a series of stages of increasing maturi
     upgrade may require downtime for anything relying on the new feature, and may require
     manual conversion of objects to the new version; when manual conversion is necessary, the
     project will provide documentation on the process (for an example, see [v1 conversion
-    tips](/{{page.version}}/docs/api/))
+    tips](/docs/api/))
   - Cluster Reliability: since the feature has e2e tests, enabling the feature via a flag should not
     create new bugs in unrelated features;  because the feature is new, it may have minor bugs
   - Support: the project commits to complete the feature, in some form, in a subsequent Stable
diff --git a/v1.1/docs/devel/automation.md b/docs/devel/automation.md
similarity index 100%
rename from v1.1/docs/devel/automation.md
rename to docs/devel/automation.md
diff --git a/v1.1/docs/devel/cherry-picks.md b/docs/devel/cherry-picks.md
similarity index 100%
rename from v1.1/docs/devel/cherry-picks.md
rename to docs/devel/cherry-picks.md
diff --git a/v1.1/docs/devel/cli-roadmap.md b/docs/devel/cli-roadmap.md
similarity index 100%
rename from v1.1/docs/devel/cli-roadmap.md
rename to docs/devel/cli-roadmap.md
diff --git a/v1.1/docs/devel/client-libraries.md b/docs/devel/client-libraries.md
similarity index 100%
rename from v1.1/docs/devel/client-libraries.md
rename to docs/devel/client-libraries.md
diff --git a/v1.2/docs/devel/coding-conventions.md b/docs/devel/coding-conventions.md
similarity index 89%
rename from v1.2/docs/devel/coding-conventions.md
rename to docs/devel/coding-conventions.md
index 31e8762a60..1d5f87ef3f 100644
--- a/v1.2/docs/devel/coding-conventions.md
+++ b/docs/devel/coding-conventions.md
@@ -6,7 +6,7 @@
     - https://google-styleguide.googlecode.com/svn/trunk/shell.xml
     - Ensure that build, release, test, and cluster-management scripts run on OS X
   - Go
-    - Ensure your code passes the [presubmit checks](/{{page.version}}/docs/devel/development/#hooks)
+    - Ensure your code passes the [presubmit checks](/docs/devel/development/#hooks)
     - [Go Code Review Comments](https://github.com/golang/go/wiki/CodeReviewComments)
     - [Effective Go](https://golang.org/doc/effective_go)
     - Comment your code.
@@ -23,10 +23,10 @@
         - Importers can use a different name if they need to disambiguate.
       - Locks should be called `lock` and should never be embedded (always `lock sync.Mutex`). When multiple locks are present, give each lock a distinct name following Go conventions - `stateLock`, `mapLock` etc.
     - API conventions
-      - [API changes](/{{page.version}}/docs/devel/api_changes)
-      - [API conventions](/{{page.version}}/docs/devel/api-conventions)
-    - [Kubectl conventions](/{{page.version}}/docs/devel/kubectl-conventions)
-    - [Logging conventions](/{{page.version}}/docs/devel/logging)
+      - [API changes](/docs/devel/api_changes)
+      - [API conventions](/docs/devel/api-conventions)
+    - [Kubectl conventions](/docs/devel/kubectl-conventions)
+    - [Logging conventions](/docs/devel/logging)
 
 Testing conventions
 
@@ -45,7 +45,7 @@ Directory and file conventions
     - Package directories should generally avoid using separators as much as possible (when packages are multiple words, they usually should be in nested subdirectories).
   - Document directories and filenames should use dashes rather than underscores
   - Contrived examples that illustrate system features belong in /docs/user-guide or /docs/admin, depending on whether it is a feature primarily intended for users that deploy applications or cluster administrators, respectively. Actual application examples belong in /examples.
-    - Examples should also illustrate [best practices for using the system](/{{page.version}}/docs/user-guide/config-best-practices)
+    - Examples should also illustrate [best practices for using the system](/docs/user-guide/config-best-practices)
   - Third-party code
     - Third-party Go code is managed using Godeps
     - Other third-party code belongs in /third_party
diff --git a/v1.1/docs/devel/collab.md b/docs/devel/collab.md
similarity index 100%
rename from v1.1/docs/devel/collab.md
rename to docs/devel/collab.md
diff --git a/v1.2/docs/devel/developer-guides/vagrant.md b/docs/devel/developer-guides/vagrant.md
similarity index 99%
rename from v1.2/docs/devel/developer-guides/vagrant.md
rename to docs/devel/developer-guides/vagrant.md
index a338bf2ac4..2ad83e9214 100644
--- a/v1.2/docs/devel/developer-guides/vagrant.md
+++ b/docs/devel/developer-guides/vagrant.md
@@ -11,7 +11,7 @@ Running kubernetes with Vagrant (and VirtualBox) is an easy way to run/test/deve
    2. [VMWare Fusion](https://www.vmware.com/products/fusion/) version 5 or greater as well as the appropriate [Vagrant VMWare Fusion provider](https://www.vagrantup.com/vmware)
    3. [VMWare Workstation](https://www.vmware.com/products/workstation/) version 9 or greater as well as the [Vagrant VMWare Workstation provider](https://www.vagrantup.com/vmware)
    4. [Parallels Desktop](https://www.parallels.com/products/desktop/) version 9 or greater as well as the [Vagrant Parallels provider](https://parallels.github.io/vagrant-parallels/)
-3. Get or build a [binary release](/{{page.version}}/docs/getting-started-guides/binary_release)
+3. Get or build a [binary release](/docs/getting-started-guides/binary_release)
 
 ### Setup
 
diff --git a/v1.1/docs/devel/development.md b/docs/devel/development.md
similarity index 96%
rename from v1.1/docs/devel/development.md
rename to docs/devel/development.md
index aa9dd687fa..881ae4351a 100644
--- a/v1.1/docs/devel/development.md
+++ b/docs/devel/development.md
@@ -66,7 +66,7 @@ git push -f origin myfeature
 
 1. Visit https://github.com/$YOUR_GITHUB_USERNAME/kubernetes
 2. Click the "Compare and pull request" button next to your "myfeature" branch.
-3. Check out the pull request [process](/{{page.version}}/docs/devel/pull-requests) for more details
+3. Check out the pull request [process](/docs/devel/pull-requests) for more details
 
 ### When to retain commits and when to squash
 
@@ -80,7 +80,7 @@ fixups (e.g. automated doc formatting), use one or more commits for the
 changes to tooling and a final commit to apply the fixup en masse.  This makes
 reviews much easier.
 
-See [Faster Reviews](/{{page.version}}/docs/devel/faster_reviews) for more details.
+See [Faster Reviews](/docs/devel/faster_reviews) for more details.
 
 ## godep and dependency management
 
@@ -297,8 +297,8 @@ go run hack/e2e.go -v -ctl='delete pod foobar'
 ## Conformance testing
 
 End-to-end testing, as described above, is for [development
-distributions](/{{page.version}}/docs/devel/writing-a-getting-started-guide).  A conformance test is used on
-a [versioned distro](/{{page.version}}/docs/devel/writing-a-getting-started-guide).
+distributions](/docs/devel/writing-a-getting-started-guide).  A conformance test is used on
+a [versioned distro](/docs/devel/writing-a-getting-started-guide).
 
 The conformance test runs a subset of the e2e-tests against a manually-created cluster.  It does not
 require support for up/push/down and other operations.  To run a conformance test, you need to know the
@@ -308,7 +308,7 @@ See [conformance-test.sh](http://releases.k8s.io/{{page.githubbranch}}/hack/conf
 
 ## Testing out flaky tests
 
-[Instructions here](/{{page.version}}/docs/devel/flaky-tests)
+[Instructions here](/docs/devel/flaky-tests)
 
 ## Regenerating the CLI documentation
 
diff --git a/v1.1/docs/devel/e2e-tests.md b/docs/devel/e2e-tests.md
similarity index 100%
rename from v1.1/docs/devel/e2e-tests.md
rename to docs/devel/e2e-tests.md
diff --git a/v1.2/docs/devel/faster_reviews.md b/docs/devel/faster_reviews.md
similarity index 97%
rename from v1.2/docs/devel/faster_reviews.md
rename to docs/devel/faster_reviews.md
index 8545d609d7..26d3b9dc81 100644
--- a/v1.2/docs/devel/faster_reviews.md
+++ b/docs/devel/faster_reviews.md
@@ -23,10 +23,10 @@ Let's talk about how to avoid this.
 
 ## 0. Familiarize yourself with project conventions
 
-* [Development guide](/{{page.version}}/docs/devel/development)
-* [Coding conventions](/{{page.version}}/docs/devel/coding-conventions)
-* [API conventions](/{{page.version}}/docs/devel/api-conventions)
-* [Kubectl conventions](/{{page.version}}/docs/devel/kubectl-conventions)
+* [Development guide](/docs/devel/development)
+* [Coding conventions](/docs/devel/coding-conventions)
+* [API conventions](/docs/devel/api-conventions)
+* [Kubectl conventions](/docs/devel/kubectl-conventions)
 
 ## 1. Don't build a cathedral in one PR
 
diff --git a/v1.1/docs/devel/flaky-tests.md b/docs/devel/flaky-tests.md
similarity index 100%
rename from v1.1/docs/devel/flaky-tests.md
rename to docs/devel/flaky-tests.md
diff --git a/v1.1/docs/devel/getting-builds.md b/docs/devel/getting-builds.md
similarity index 100%
rename from v1.1/docs/devel/getting-builds.md
rename to docs/devel/getting-builds.md
diff --git a/docs/devel/index.md b/docs/devel/index.md
new file mode 100644
index 0000000000..81f3017ac8
--- /dev/null
+++ b/docs/devel/index.md
@@ -0,0 +1,78 @@
+---
+---
+
+The developer guide is for anyone wanting to either write code which directly accesses the
+Kubernetes API, or to contribute directly to the Kubernetes project.
+It assumes some familiarity with concepts in the [User Guide](/docs/user-guide/) and the [Cluster Admin
+Guide](/docs/admin/).
+
+
+## The process of developing and contributing code to the Kubernetes project
+
+* **On Collaborative Development** ([collab.md](/docs/devel/collab)): Info on pull requests and code reviews.
+
+* **GitHub Issues** ([issues.md](/docs/devel/issues)): How incoming issues are reviewed and prioritized.
+
+* **Pull Request Process** ([pull-requests.md](/docs/devel/pull-requests)): When and why pull requests are closed.
+
+* **Faster PR reviews** ([faster_reviews.md](/docs/devel/faster_reviews)): How to get faster PR reviews.
+
+* **Getting Recent Builds** ([getting-builds.md](/docs/devel/getting-builds)): How to get recent builds including the latest builds that pass CI.
+
+* **Automated Tools** ([automation.md](/docs/devel/automation)): Descriptions of the automation that is running on our github repository.
+
+
+## Setting up your dev environment, coding, and debugging
+
+* **Development Guide** ([development.md](/docs/devel/development)): Setting up your development environment.
+
+* **Hunting flaky tests** ([flaky-tests.md](/docs/devel/flaky-tests)): We have a goal of 99.9% flake free tests.
+  Here's how to run your tests many times.
+
+* **Logging Conventions** ([logging.md](/docs/devel/logging)]: Glog levels.
+
+* **Profiling Kubernetes** ([profiling.md](/docs/devel/profiling)): How to plug in go pprof profiler to Kubernetes.
+
+* **Instrumenting Kubernetes with a new metric**
+  ([instrumentation.md](/docs/devel/instrumentation)): How to add a new metrics to the
+  Kubernetes code base.
+
+* **Coding Conventions** ([coding-conventions.md](/docs/devel/coding-conventions)):
+  Coding style advice for contributors.
+
+
+## Developing against the Kubernetes API
+
+* API objects are explained at [http://kubernetes.io/third_party/swagger-ui/](http://kubernetes.io/third_party/swagger-ui/).
+
+* **Annotations** ([docs/user-guide/annotations.md](/docs/user-guide/annotations)): are for attaching arbitrary non-identifying metadata to objects.
+  Programs that automate Kubernetes objects may use annotations to store small amounts of their state.
+
+* **API Conventions** ([api-conventions.md](/docs/devel/api-conventions)):
+  Defining the verbs and resources used in the Kubernetes API.
+
+* **API Client Libraries** ([client-libraries.md](/docs/devel/client-libraries)):
+  A list of existing client libraries, both supported and user-contributed.
+
+
+## Writing plugins
+
+* **Authentication Plugins** ([docs/admin/authentication.md](/docs/admin/authentication)):
+  The current and planned states of authentication tokens.
+
+* **Authorization Plugins** ([docs/admin/authorization.md](/docs/admin/authorization)):
+  Authorization applies to all HTTP requests on the main apiserver port.
+  This doc explains the available authorization implementations.
+
+* **Admission Control Plugins** ([admission_control](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control.md))
+
+
+## Building releases
+
+* **Making release notes** ([making-release-notes.md](/docs/devel/making-release-notes)): Generating release nodes for a new release.
+
+* **Releasing Kubernetes** ([releasing.md](/docs/devel/releasing)): How to create a Kubernetes release (as in version)
+  and how the version information gets embedded into the built binaries.
+
+
+
diff --git a/v1.1/docs/devel/instrumentation.md b/docs/devel/instrumentation.md
similarity index 100%
rename from v1.1/docs/devel/instrumentation.md
rename to docs/devel/instrumentation.md
diff --git a/v1.1/docs/devel/issues.md b/docs/devel/issues.md
similarity index 100%
rename from v1.1/docs/devel/issues.md
rename to docs/devel/issues.md
diff --git a/v1.1/docs/devel/kubectl-conventions.md b/docs/devel/kubectl-conventions.md
similarity index 100%
rename from v1.1/docs/devel/kubectl-conventions.md
rename to docs/devel/kubectl-conventions.md
diff --git a/v1.1/docs/devel/logging.md b/docs/devel/logging.md
similarity index 100%
rename from v1.1/docs/devel/logging.md
rename to docs/devel/logging.md
diff --git a/v1.1/docs/devel/making-release-notes.md b/docs/devel/making-release-notes.md
similarity index 100%
rename from v1.1/docs/devel/making-release-notes.md
rename to docs/devel/making-release-notes.md
diff --git a/v1.1/docs/devel/profiling.md b/docs/devel/profiling.md
similarity index 100%
rename from v1.1/docs/devel/profiling.md
rename to docs/devel/profiling.md
diff --git a/v1.2/docs/devel/pull-requests.md b/docs/devel/pull-requests.md
similarity index 96%
rename from v1.2/docs/devel/pull-requests.md
rename to docs/devel/pull-requests.md
index 9615079d13..fc7053f60f 100644
--- a/v1.2/docs/devel/pull-requests.md
+++ b/docs/devel/pull-requests.md
@@ -30,7 +30,7 @@ Additionally, for infrequent or new contributors, we require the on call to appl
 ## Automation
 
 We use a variety of automation to manage pull requests.  This automation is described in detail
-[elsewhere.](/{{page.version}}/docs/devel/automation)
+[elsewhere.](/docs/devel/automation)
 
 
 
diff --git a/v1.2/docs/devel/releasing.md b/docs/devel/releasing.md
similarity index 98%
rename from v1.2/docs/devel/releasing.md
rename to docs/devel/releasing.md
index f527616ec7..35a63e5474 100644
--- a/v1.2/docs/devel/releasing.md
+++ b/docs/devel/releasing.md
@@ -87,7 +87,7 @@ In your git repo (you still have `${VER}` set from above right?):
 
 #### Writing Release Notes
 
-[This helpful guide](/{{page.version}}/docs/devel/making-release-notes) describes how to write release
+[This helpful guide](/docs/devel/making-release-notes) describes how to write release
 notes for a major/minor release. In the release template on GitHub, leave the
 last PR number that the tool finds for the `.0` release, so the next releaser
 doesn't have to hunt.
@@ -99,7 +99,7 @@ doesn't have to hunt.
 We cut `vX.Y.Z` releases from the `release-vX.Y` branch after all cherry picks
 to the branch have been resolved. You should ensure all outstanding cherry picks
 have been reviewed and merged and the branch validated on Jenkins (validation
-TBD). See the [Cherry Picks](/{{page.version}}/docs/devel/cherry-picks) for more information on how to
+TBD). See the [Cherry Picks](/docs/devel/cherry-picks) for more information on how to
 manage cherry picks prior to cutting the release.
 
 #### Tagging and Merging
diff --git a/v1.1/docs/devel/scheduler.md b/docs/devel/scheduler.md
similarity index 100%
rename from v1.1/docs/devel/scheduler.md
rename to docs/devel/scheduler.md
diff --git a/v1.2/docs/devel/scheduler_algorithm.md b/docs/devel/scheduler_algorithm.md
similarity index 89%
rename from v1.2/docs/devel/scheduler_algorithm.md
rename to docs/devel/scheduler_algorithm.md
index d1207f98e3..8360092d4e 100755
--- a/v1.2/docs/devel/scheduler_algorithm.md
+++ b/docs/devel/scheduler_algorithm.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-For each unscheduled Pod, the Kubernetes scheduler tries to find a node across the cluster according to a set of rules. A general introduction to the Kubernetes scheduler can be found at [scheduler.md](/{{page.version}}/docs/devel/scheduler). In this document, the algorithm of how to select a node for the Pod is explained. There are two steps before a destination node of a Pod is chosen. The first step is filtering all the nodes and the second is ranking the remaining nodes to find a best fit for the Pod.
+For each unscheduled Pod, the Kubernetes scheduler tries to find a node across the cluster according to a set of rules. A general introduction to the Kubernetes scheduler can be found at [scheduler.md](/docs/devel/scheduler). In this document, the algorithm of how to select a node for the Pod is explained. There are two steps before a destination node of a Pod is chosen. The first step is filtering all the nodes and the second is ranking the remaining nodes to find a best fit for the Pod.
 
 ## Filtering the nodes
 
@@ -11,7 +11,7 @@ The purpose of filtering the nodes is to filter out the nodes that do not meet c
 - `PodFitsResources`: Check if the free resource (CPU and Memory) meets the requirement of the Pod. The free resource is measured by the capacity minus the sum of requests of all Pods on the node. To learn more about the resource QoS in Kubernetes, please check [QoS proposal](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/proposals/resource-qos.md).
 - `PodFitsHostPorts`: Check if any HostPort required by the Pod is already occupied on the node.
 - `PodFitsHost`: Filter out all nodes except the one specified in the PodSpec's NodeName field.
-- `PodSelectorMatches`: Check if the labels of the node match the labels specified in the Pod's `nodeSelector` field ([Here](/{{page.version}}/docs/user-guide/node-selection/) is an example of how to use `nodeSelector` field).
+- `PodSelectorMatches`: Check if the labels of the node match the labels specified in the Pod's `nodeSelector` field ([Here](/docs/user-guide/node-selection/) is an example of how to use `nodeSelector` field).
 - `CheckNodeLabelPresence`: Check if all the specified labels exist on a node or not, regardless of the value.
 
 The details of the above predicates can be found in [plugin/pkg/scheduler/algorithm/predicates/predicates.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithm/predicates/predicates.go). All predicates mentioned above can be used in combination to perform a sophisticated filtering policy. Kubernetes uses some, but not all, of these predicates by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go).
@@ -32,7 +32,7 @@ Currently, Kubernetes scheduler provides some practical priority functions, incl
 - `CalculateSpreadPriority`: Spread Pods by minimizing the number of Pods belonging to the same service on the same node.
 - `CalculateAntiAffinityPriority`: Spread Pods by minimizing the number of Pods belonging to the same service on nodes with the same value for a particular label.
 
-The details of the above priority functions can be found in [plugin/pkg/scheduler/algorithm/priorities](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithm/priorities/). Kubernetes uses some, but not all, of these priority functions by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go). Similar as predicates, you can combine the above priority functions and assign weight factors (positive number) to them as you want (check [scheduler.md](/{{page.version}}/docs/devel/scheduler) for how to customize).
+The details of the above priority functions can be found in [plugin/pkg/scheduler/algorithm/priorities](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithm/priorities/). Kubernetes uses some, but not all, of these priority functions by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go). Similar as predicates, you can combine the above priority functions and assign weight factors (positive number) to them as you want (check [scheduler.md](/docs/devel/scheduler) for how to customize).
 
 
 
diff --git a/v1.1/docs/devel/writing-a-getting-started-guide.md b/docs/devel/writing-a-getting-started-guide.md
similarity index 92%
rename from v1.1/docs/devel/writing-a-getting-started-guide.md
rename to docs/devel/writing-a-getting-started-guide.md
index 65e615eb9a..4741bbf7d3 100644
--- a/v1.1/docs/devel/writing-a-getting-started-guide.md
+++ b/docs/devel/writing-a-getting-started-guide.md
@@ -12,7 +12,7 @@ A guide refers to scripts, Configuration Management files, and/or binary assets
 the combination of all these things needed to run on a particular type of infrastructure a
 **distro**.
 
-[The Matrix](/{{page.version}}/docs/getting-started-guides/) lists the distros.  If there is already a guide
+[The Matrix](/docs/getting-started-guides/) lists the distros.  If there is already a guide
 which is similar to the one you have planned, consider improving that one.
 
 
@@ -35,9 +35,9 @@ These guidelines say *what* to do.  See the Rationale section for *why*.
    search for uses of flags by guides.
  - We may ask that you host binary assets or large amounts of code in our `contrib` directory or on your
    own repo.
- - Add or update a row in [The Matrix](/{{page.version}}/docs/getting-started-guides/).
+ - Add or update a row in [The Matrix](/docs/getting-started-guides/).
  - State the binary version of Kubernetes that you tested clearly in your Guide doc.
- - Setup a cluster and run the [conformance test](/{{page.version}}/docs/devel/development/#conformance-testing) against it, and report the
+ - Setup a cluster and run the [conformance test](/docs/devel/development/#conformance-testing) against it, and report the
    results in your PR.
  - Versioned distros should typically not modify or add code in `cluster/`.  That is just scripts for developer
    distros.
@@ -46,7 +46,7 @@ These guidelines say *what* to do.  See the Rationale section for *why*.
 
 If you have a cluster partially working, but doing all the above steps seems like too much work,
 we still want to hear from you.  We suggest you write a blog post or a Gist, and we will link to it on our wiki page.
-Just file an issue or chat us on [Slack](/{{page.version}}/docs/troubleshooting/#slack) and one of the committers will link to it from the wiki.
+Just file an issue or chat us on [Slack](/docs/troubleshooting/#slack) and one of the committers will link to it from the wiki.
 
 ## Development Distro Guidelines
 
diff --git a/v1.1/editdocs.md b/docs/editdocs.md
similarity index 100%
rename from v1.1/editdocs.md
rename to docs/editdocs.md
diff --git a/v1.2/docs/getting-started-guides/aws.md b/docs/getting-started-guides/aws.md
similarity index 85%
rename from v1.2/docs/getting-started-guides/aws.md
rename to docs/getting-started-guides/aws.md
index 9f0429f438..fe055ed1a1 100644
--- a/v1.2/docs/getting-started-guides/aws.md
+++ b/docs/getting-started-guides/aws.md
@@ -56,7 +56,7 @@ NOTE: If using an existing keypair named "kubernetes" then you must set the `AWS
 
 ### Alternatives
 
-A contributed [example](/{{page.version}}/docs/getting-started-guides/coreos/coreos_multinode_cluster) allows you to setup a Kubernetes cluster based on [CoreOS](http://www.coreos.com), using
+A contributed [example](/docs/getting-started-guides/coreos/coreos_multinode_cluster) allows you to setup a Kubernetes cluster based on [CoreOS](http://www.coreos.com), using
 EC2 with user data (cloud-config).
 
 ## Getting started with your cluster
@@ -75,14 +75,14 @@ export PATH=<path/to/kubernetes-directory>/platforms/darwin/amd64:$PATH
 export PATH=<path/to/kubernetes-directory>/platforms/linux/amd64:$PATH
 ```
 
-An up-to-date documentation page for this tool is available here: [kubectl manual](/{{page.version}}/docs/user-guide/kubectl/kubectl)
+An up-to-date documentation page for this tool is available here: [kubectl manual](/docs/user-guide/kubectl/kubectl)
 
 By default, `kubectl` will use the `kubeconfig` file generated during the cluster startup for authenticating against the API.
-For more information, please read [kubeconfig files](/{{page.version}}/docs/user-guide/kubeconfig-file)
+For more information, please read [kubeconfig files](/docs/user-guide/kubeconfig-file)
 
 ### Examples
 
-See [a simple nginx example](/{{page.version}}/docs/user-guide/simple-nginx) to try out your new cluster.
+See [a simple nginx example](/docs/user-guide/simple-nginx) to try out your new cluster.
 
 The "Guestbook" application is another popular example to get started with Kubernetes: [guestbook example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/)
 
@@ -99,5 +99,5 @@ cluster/kube-down.sh
 
 ## Further reading
 
-Please see the [Kubernetes docs](/{{page.version}}/docs/) for more details on administering
+Please see the [Kubernetes docs](/docs/) for more details on administering
 and using a Kubernetes cluster.
\ No newline at end of file
diff --git a/docs/getting-started-guides/azure.md b/docs/getting-started-guides/azure.md
new file mode 100644
index 0000000000..b45e438ca7
--- /dev/null
+++ b/docs/getting-started-guides/azure.md
@@ -0,0 +1,10 @@
+---
+---
+
+
+## Getting started on Microsoft Azure
+
+Checkout the [coreos azure getting started guide](/docs/getting-started-guides/coreos/azure/)
+
+
+
diff --git a/v1.1/docs/getting-started-guides/binary_release.md b/docs/getting-started-guides/binary_release.md
similarity index 100%
rename from v1.1/docs/getting-started-guides/binary_release.md
rename to docs/getting-started-guides/binary_release.md
diff --git a/v1.1/docs/getting-started-guides/centos/centos_manual_config.md b/docs/getting-started-guides/centos/centos_manual_config.md
similarity index 91%
rename from v1.1/docs/getting-started-guides/centos/centos_manual_config.md
rename to docs/getting-started-guides/centos/centos_manual_config.md
index 9c7b2638ab..be5892f5a0 100644
--- a/v1.1/docs/getting-started-guides/centos/centos_manual_config.md
+++ b/docs/getting-started-guides/centos/centos_manual_config.md
@@ -12,7 +12,7 @@ You need two machines with CentOS installed on them.
 
 This is a getting started guide for CentOS.  It is a manual configuration so you understand all the underlying packages / services / ports, etc...
 
-This guide will only get ONE node working.  Multiple nodes requires a functional [networking configuration](/{{page.version}}/docs/admin/networking) done outside of kubernetes.  Although the additional Kubernetes configuration requirements should be obvious.
+This guide will only get ONE node working.  Multiple nodes requires a functional [networking configuration](/docs/admin/networking) done outside of kubernetes.  Although the additional Kubernetes configuration requirements should be obvious.
 
 The Kubernetes package provides a few services: kube-apiserver, kube-scheduler, kube-controller-manager, kubelet, kube-proxy.  These services are managed by systemd and the configuration resides in a central location: /etc/kubernetes. We will break the services up between the hosts.  The first host, centos-master, will be the Kubernetes master.  This host will run the kube-apiserver, kube-controller-manager, and kube-scheduler.  In addition, the master will also run _etcd_.  The remaining host, centos-minion will be the node and run kubelet, proxy, cadvisor and docker.
 
@@ -168,4 +168,4 @@ centos-minion          <none>            Ready
 
 **The cluster should be running! Launch a test pod.**
 
-You should have a functional cluster, check out [101](/{{page.version}}/docs/user-guide/walkthrough/)!
\ No newline at end of file
+You should have a functional cluster, check out [101](/docs/user-guide/walkthrough/)!
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/cloudstack.md b/docs/getting-started-guides/cloudstack.md
similarity index 96%
rename from v1.1/docs/getting-started-guides/cloudstack.md
rename to docs/getting-started-guides/cloudstack.md
index b70bd0f850..5e1b9af4c0 100644
--- a/v1.1/docs/getting-started-guides/cloudstack.md
+++ b/docs/getting-started-guides/cloudstack.md
@@ -6,7 +6,7 @@ CloudStack is a software to build public and private clouds based on hardware vi
 [CoreOS](http://coreos.com) templates for CloudStack are built [nightly](http://stable.release.core-os.net/amd64-usr/current/). CloudStack operators need to [register](http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/templates) this template in their cloud before proceeding with these Kubernetes deployment instructions.
 
 This guide uses an [Ansible playbook](https://github.com/runseb/ansible-kubernetes).
-This is a completely automated, a single playbook deploys Kubernetes based on the coreOS [instructions](/{{page.version}}/docs/getting-started-guides/coreos/coreos_multinode_cluster).
+This is a completely automated, a single playbook deploys Kubernetes based on the coreOS [instructions](/docs/getting-started-guides/coreos/coreos_multinode_cluster).
 
 
 This [Ansible](http://ansibleworks.com) playbook deploys Kubernetes on a CloudStack based Cloud using CoreOS images. The playbook, creates an ssh key pair, creates a security group and associated rules and finally starts coreOS instances configured via cloud-init.
diff --git a/v1.1/docs/getting-started-guides/coreos.md b/docs/getting-started-guides/coreos.md
similarity index 93%
rename from v1.1/docs/getting-started-guides/coreos.md
rename to docs/getting-started-guides/coreos.md
index 82cba8d24b..0f3136a85b 100644
--- a/v1.1/docs/getting-started-guides/coreos.md
+++ b/docs/getting-started-guides/coreos.md
@@ -30,7 +30,7 @@ A generic guide to setting up an HA cluster on any cloud or bare metal, with ful
 
 These guides are maintained by community members, cover specific platforms and use cases, and experiment with different ways of configuring Kubernetes on CoreOS.
 
-[**Multi-node Cluster**](/{{page.version}}/docs/getting-started-guides/coreos/coreos_multinode_cluster)
+[**Multi-node Cluster**](/docs/getting-started-guides/coreos/coreos_multinode_cluster)
 
 Set up a single master, multi-worker cluster on your choice of platform: AWS, GCE, or VMware Fusion.
 
@@ -60,7 +60,7 @@ Guide to running a single master, multi-worker cluster controlled by an OS X men
 
 <hr/>
 
-[**Resizable multi-node cluster on Azure with Weave**](/{{page.version}}/docs/getting-started-guides/coreos/azure/)
+[**Resizable multi-node cluster on Azure with Weave**](/docs/getting-started-guides/coreos/azure/)
 
 Guide to running an HA etcd cluster with a single master on Azure. Uses the Azure node.js CLI to resize the cluster.
 
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/.gitignore b/docs/getting-started-guides/coreos/azure/.gitignore
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/.gitignore
rename to docs/getting-started-guides/coreos/azure/.gitignore
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/addons/skydns-rc.yaml b/docs/getting-started-guides/coreos/azure/addons/skydns-rc.yaml
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/addons/skydns-rc.yaml
rename to docs/getting-started-guides/coreos/azure/addons/skydns-rc.yaml
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/addons/skydns-svc.yaml b/docs/getting-started-guides/coreos/azure/addons/skydns-svc.yaml
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/addons/skydns-svc.yaml
rename to docs/getting-started-guides/coreos/azure/addons/skydns-svc.yaml
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/azure-login.js b/docs/getting-started-guides/coreos/azure/azure-login.js
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/azure-login.js
rename to docs/getting-started-guides/coreos/azure/azure-login.js
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-etcd-node-template.yml b/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-etcd-node-template.yml
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-etcd-node-template.yml
rename to docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-etcd-node-template.yml
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml b/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml
rename to docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/create-kubernetes-cluster.js b/docs/getting-started-guides/coreos/azure/create-kubernetes-cluster.js
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/create-kubernetes-cluster.js
rename to docs/getting-started-guides/coreos/azure/create-kubernetes-cluster.js
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/destroy-cluster.js b/docs/getting-started-guides/coreos/azure/destroy-cluster.js
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/destroy-cluster.js
rename to docs/getting-started-guides/coreos/azure/destroy-cluster.js
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/expose_guestbook_app_port.sh b/docs/getting-started-guides/coreos/azure/expose_guestbook_app_port.sh
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/expose_guestbook_app_port.sh
rename to docs/getting-started-guides/coreos/azure/expose_guestbook_app_port.sh
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/index.md b/docs/getting-started-guides/coreos/azure/index.md
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/index.md
rename to docs/getting-started-guides/coreos/azure/index.md
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/lib/azure_wrapper.js b/docs/getting-started-guides/coreos/azure/lib/azure_wrapper.js
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/lib/azure_wrapper.js
rename to docs/getting-started-guides/coreos/azure/lib/azure_wrapper.js
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/lib/cloud_config.js b/docs/getting-started-guides/coreos/azure/lib/cloud_config.js
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/lib/cloud_config.js
rename to docs/getting-started-guides/coreos/azure/lib/cloud_config.js
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/lib/deployment_logic/kubernetes.js b/docs/getting-started-guides/coreos/azure/lib/deployment_logic/kubernetes.js
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/lib/deployment_logic/kubernetes.js
rename to docs/getting-started-guides/coreos/azure/lib/deployment_logic/kubernetes.js
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/lib/util.js b/docs/getting-started-guides/coreos/azure/lib/util.js
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/lib/util.js
rename to docs/getting-started-guides/coreos/azure/lib/util.js
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/package.json b/docs/getting-started-guides/coreos/azure/package.json
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/package.json
rename to docs/getting-started-guides/coreos/azure/package.json
diff --git a/v1.1/docs/getting-started-guides/coreos/azure/scale-kubernetes-cluster.js b/docs/getting-started-guides/coreos/azure/scale-kubernetes-cluster.js
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/azure/scale-kubernetes-cluster.js
rename to docs/getting-started-guides/coreos/azure/scale-kubernetes-cluster.js
diff --git a/v1.1/docs/getting-started-guides/coreos/bare_metal_calico.md b/docs/getting-started-guides/coreos/bare_metal_calico.md
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/bare_metal_calico.md
rename to docs/getting-started-guides/coreos/bare_metal_calico.md
diff --git a/v1.2/docs/getting-started-guides/coreos/bare_metal_offline.md b/docs/getting-started-guides/coreos/bare_metal_offline.md
similarity index 98%
rename from v1.2/docs/getting-started-guides/coreos/bare_metal_offline.md
rename to docs/getting-started-guides/coreos/bare_metal_offline.md
index b74b83cb07..f80f90412c 100644
--- a/v1.2/docs/getting-started-guides/coreos/bare_metal_offline.md
+++ b/docs/getting-started-guides/coreos/bare_metal_offline.md
@@ -228,7 +228,7 @@ Now for the good stuff!
 
 The following config files are tailored for the OFFLINE version of a Kubernetes deployment.
 
-These are based on the work found here: [master.yml](/{{page.version}}/docs/getting-started-guides/coreos/cloud-configs/master.yaml), [node.yml](/{{page.version}}/docs/getting-started-guides/coreos/cloud-configs/node.yaml)
+These are based on the work found here: [master.yml](/docs/getting-started-guides/coreos/cloud-configs/master.yaml), [node.yml](/docs/getting-started-guides/coreos/cloud-configs/node.yaml)
 
 To make the setup work, you need to replace a few placeholders:
 
@@ -646,7 +646,7 @@ Reboot these servers to get the images PXEd and ready for running containers!
 
 Now that the CoreOS with Kubernetes installed is up and running lets spin up some Kubernetes pods to demonstrate the system.
 
-See [a simple nginx example](/{{page.version}}/docs/user-guide/simple-nginx) to try out your new cluster.
+See [a simple nginx example](/docs/user-guide/simple-nginx) to try out your new cluster.
 
 For more complete applications, please look in the [examples directory](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/).
 
diff --git a/v1.1/docs/getting-started-guides/coreos/cloud-configs/master.yaml b/docs/getting-started-guides/coreos/cloud-configs/master.yaml
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/cloud-configs/master.yaml
rename to docs/getting-started-guides/coreos/cloud-configs/master.yaml
diff --git a/v1.1/docs/getting-started-guides/coreos/cloud-configs/node.yaml b/docs/getting-started-guides/coreos/cloud-configs/node.yaml
similarity index 100%
rename from v1.1/docs/getting-started-guides/coreos/cloud-configs/node.yaml
rename to docs/getting-started-guides/coreos/cloud-configs/node.yaml
diff --git a/v1.2/docs/getting-started-guides/coreos/coreos_multinode_cluster.md b/docs/getting-started-guides/coreos/coreos_multinode_cluster.md
similarity index 95%
rename from v1.2/docs/getting-started-guides/coreos/coreos_multinode_cluster.md
rename to docs/getting-started-guides/coreos/coreos_multinode_cluster.md
index b86f435e6b..e08345123a 100644
--- a/v1.2/docs/getting-started-guides/coreos/coreos_multinode_cluster.md
+++ b/docs/getting-started-guides/coreos/coreos_multinode_cluster.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-Use the [master.yaml](/{{page.version}}/docs/getting-started-guides/coreos/cloud-configs/master.yaml) and [node.yaml](/{{page.version}}/docs/getting-started-guides/coreos/cloud-configs/node.yaml) cloud-configs to provision a multi-node Kubernetes cluster.
+Use the [master.yaml](/docs/getting-started-guides/coreos/cloud-configs/master.yaml) and [node.yaml](/docs/getting-started-guides/coreos/cloud-configs/node.yaml) cloud-configs to provision a multi-node Kubernetes cluster.
 
 > **Attention**: This requires at least CoreOS version **[695.0.0][coreos695]**, which includes `etcd2`.
 
diff --git a/v1.1/docs/getting-started-guides/dcos.md b/docs/getting-started-guides/dcos.md
similarity index 97%
rename from v1.1/docs/getting-started-guides/dcos.md
rename to docs/getting-started-guides/dcos.md
index bc2f3441a8..efc64002b7 100644
--- a/v1.1/docs/getting-started-guides/dcos.md
+++ b/docs/getting-started-guides/dcos.md
@@ -105,7 +105,7 @@ $ dcos kubectl get pods --namespace=kube-system
 Names and ages may vary.
 
 
-Now that Kubernetes is installed on DCOS, you may wish to explore the [Kubernetes Examples](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/) or the [Kubernetes User Guide](/{{page.version}}/docs/user-guide/).
+Now that Kubernetes is installed on DCOS, you may wish to explore the [Kubernetes Examples](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/) or the [Kubernetes User Guide](/docs/user-guide/).
 
 
 ## Uninstall
diff --git a/v1.2/docs/getting-started-guides/docker-multinode.md b/docs/getting-started-guides/docker-multinode.md
similarity index 71%
rename from v1.2/docs/getting-started-guides/docker-multinode.md
rename to docs/getting-started-guides/docker-multinode.md
index d2c55f81e0..d42e1d5970 100644
--- a/v1.2/docs/getting-started-guides/docker-multinode.md
+++ b/docs/getting-started-guides/docker-multinode.md
@@ -10,7 +10,7 @@ Here's a diagram of what the final result will look like:
 ![Kubernetes Single Node on Docker](/images/docs/k8s-docker.png)
 
 _Note_:
-These instructions are somewhat significantly more advanced than the [single node](/{{page.version}}/docs/getting-started-guides/docker) instructions.  If you are
+These instructions are somewhat significantly more advanced than the [single node](/docs/getting-started-guides/docker) instructions.  If you are
 interested in just starting to explore Kubernetes, we recommend that you start there.
 
 _Note_:
@@ -46,7 +46,7 @@ Otherwise, we'll use latest `hyperkube` image as default k8s version.
 
 The first step in the process is to initialize the master node.
 
-Clone the Kubernetes repo, and run [master.sh](/{{page.version}}/docs/getting-started-guides/docker-multinode/master.sh) on the master machine with root:
+Clone the Kubernetes repo, and run [master.sh](/docs/getting-started-guides/docker-multinode/master.sh) on the master machine with root:
 
 ```shell
 cd kubernetes/docs/getting-started-guides/docker-multinode/
@@ -55,13 +55,13 @@ cd kubernetes/docs/getting-started-guides/docker-multinode/
 `Master done!`
 ```
 
-See [here](/{{page.version}}/docs/getting-started-guides/docker-multinode/master) for detailed instructions explanation.
+See [here](/docs/getting-started-guides/docker-multinode/master) for detailed instructions explanation.
 
 ## Adding a worker node
 
 Once your master is up and running you can add one or more workers on different machines.
 
-Clone the Kubernetes repo, and run [worker.sh](/{{page.version}}/docs/getting-started-guides/docker-multinode/worker.sh) on the worker machine with root:
+Clone the Kubernetes repo, and run [worker.sh](/docs/getting-started-guides/docker-multinode/worker.sh) on the worker machine with root:
 
 ```shell
 export MASTER_IP=<your_master_ip (e.g. 1.2.3.4)>
@@ -71,14 +71,14 @@ cd kubernetes/docs/getting-started-guides/docker-multinode/
 `Worker done!`
 ````
 
-See [here](/{{page.version}}/docs/getting-started-guides/docker-multinode/worker) for detailed instructions explanation.
+See [here](/docs/getting-started-guides/docker-multinode/worker) for detailed instructions explanation.
 
 ## Deploy a DNS
 
-See [here](/{{page.version}}/docs/getting-started-guides/docker-multinode/deployDNS) for instructions.
+See [here](/docs/getting-started-guides/docker-multinode/deployDNS) for instructions.
 
 ## Testing your cluster
 
-Once your cluster has been created you can [test it out](/{{page.version}}/docs/getting-started-guides/docker-multinode/testing)
+Once your cluster has been created you can [test it out](/docs/getting-started-guides/docker-multinode/testing)
 
 For more complete applications, please look in the [examples directory](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/)
diff --git a/v1.2/docs/getting-started-guides/docker-multinode/deployDNS.md b/docs/getting-started-guides/docker-multinode/deployDNS.md
similarity index 86%
rename from v1.2/docs/getting-started-guides/docker-multinode/deployDNS.md
rename to docs/getting-started-guides/docker-multinode/deployDNS.md
index 896df170f7..9bd738ea13 100644
--- a/v1.2/docs/getting-started-guides/docker-multinode/deployDNS.md
+++ b/docs/getting-started-guides/docker-multinode/deployDNS.md
@@ -5,9 +5,9 @@
 
 First of all, download the template dns rc and svc file from
 
-[skydns-rc template](/{{page.version}}/docs/getting-started-guides/docker-multinode/skydns-rc.yaml.in)
+[skydns-rc template](/docs/getting-started-guides/docker-multinode/skydns-rc.yaml.in)
 
-[skydns-svc template](/{{page.version}}/docs/getting-started-guides/docker-multinode/skydns-svc.yaml.in)
+[skydns-svc template](/docs/getting-started-guides/docker-multinode/skydns-svc.yaml.in)
 
 ### Set env
 
diff --git a/v1.1/docs/getting-started-guides/docker-multinode/master.md b/docs/getting-started-guides/docker-multinode/master.md
similarity index 95%
rename from v1.1/docs/getting-started-guides/docker-multinode/master.md
rename to docs/getting-started-guides/docker-multinode/master.md
index c62fb2bc2b..5867a0de01 100644
--- a/v1.1/docs/getting-started-guides/docker-multinode/master.md
+++ b/docs/getting-started-guides/docker-multinode/master.md
@@ -171,9 +171,9 @@ NAME        LABELS                             STATUS
 ```
 
 If the status of the node is `NotReady` or `Unknown` please check that all of the containers you created are successfully running.
-If all else fails, ask questions on [Slack](/{{page.version}}/docs/troubleshooting/#slack).
+If all else fails, ask questions on [Slack](/docs/troubleshooting/#slack).
 
 
 ### Next steps
 
-Move on to [adding one or more workers](/{{page.version}}/docs/getting-started-guides/docker-multinode/worker) or [deploy a dns](/{{page.version}}/docs/getting-started-guides/docker-multinode/deployDNS)
\ No newline at end of file
+Move on to [adding one or more workers](/docs/getting-started-guides/docker-multinode/worker) or [deploy a dns](/docs/getting-started-guides/docker-multinode/deployDNS)
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/docker-multinode/master.sh b/docs/getting-started-guides/docker-multinode/master.sh
similarity index 100%
rename from v1.1/docs/getting-started-guides/docker-multinode/master.sh
rename to docs/getting-started-guides/docker-multinode/master.sh
diff --git a/v1.1/docs/getting-started-guides/docker-multinode/skydns-rc.yaml.in b/docs/getting-started-guides/docker-multinode/skydns-rc.yaml.in
similarity index 100%
rename from v1.1/docs/getting-started-guides/docker-multinode/skydns-rc.yaml.in
rename to docs/getting-started-guides/docker-multinode/skydns-rc.yaml.in
diff --git a/v1.1/docs/getting-started-guides/docker-multinode/skydns-svc.yaml.in b/docs/getting-started-guides/docker-multinode/skydns-svc.yaml.in
similarity index 100%
rename from v1.1/docs/getting-started-guides/docker-multinode/skydns-svc.yaml.in
rename to docs/getting-started-guides/docker-multinode/skydns-svc.yaml.in
diff --git a/v1.1/docs/getting-started-guides/docker-multinode/testing.md b/docs/getting-started-guides/docker-multinode/testing.md
similarity index 94%
rename from v1.1/docs/getting-started-guides/docker-multinode/testing.md
rename to docs/getting-started-guides/docker-multinode/testing.md
index 0dc593d6a0..708ecea7a5 100644
--- a/v1.1/docs/getting-started-guides/docker-multinode/testing.md
+++ b/docs/getting-started-guides/docker-multinode/testing.md
@@ -15,7 +15,7 @@ NAME           LABELS                                 STATUS
 127.0.0.1      kubernetes.io/hostname=127.0.0.1       Ready
 ```
 
-If the status of any node is `Unknown` or `NotReady` your cluster is broken, double check that all containers are running properly, and if all else fails, contact us on [Slack](/{{page.version}}/docs/troubleshooting/#slack).
+If the status of any node is `Unknown` or `NotReady` your cluster is broken, double check that all containers are running properly, and if all else fails, contact us on [Slack](/docs/troubleshooting/#slack).
 
 ### Run an application
 
diff --git a/v1.2/docs/getting-started-guides/docker-multinode/worker.md b/docs/getting-started-guides/docker-multinode/worker.md
similarity index 94%
rename from v1.2/docs/getting-started-guides/docker-multinode/worker.md
rename to docs/getting-started-guides/docker-multinode/worker.md
index be2d42acee..4a0acd58f6 100644
--- a/v1.2/docs/getting-started-guides/docker-multinode/worker.md
+++ b/docs/getting-started-guides/docker-multinode/worker.md
@@ -3,7 +3,7 @@
 
 These instructions are very similar to the master set-up above, but they are duplicated for clarity.
 You need to repeat these instructions for each node you want to join the cluster.
-We will assume that the IP address of this node is `${NODE_IP}` and you have the IP address of the master in `${MASTER_IP}` that you created in the [master instructions](/{{page.version}}/docs/getting-started-guides/docker-multinode/master).
+We will assume that the IP address of this node is `${NODE_IP}` and you have the IP address of the master in `${MASTER_IP}` that you created in the [master instructions](/docs/getting-started-guides/docker-multinode/master).
 
 For each worker node, there are three steps:
 
@@ -136,4 +136,4 @@ sudo docker run -d --net=host --privileged gcr.io/google_containers/hyperkube:v1
 
 ### Next steps
 
-Move on to [testing your cluster](/{{page.version}}/docs/getting-started-guides/docker-multinode/testing) or add another node](#).
\ No newline at end of file
+Move on to [testing your cluster](/docs/getting-started-guides/docker-multinode/testing) or add another node](#).
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/docker-multinode/worker.sh b/docs/getting-started-guides/docker-multinode/worker.sh
similarity index 100%
rename from v1.1/docs/getting-started-guides/docker-multinode/worker.sh
rename to docs/getting-started-guides/docker-multinode/worker.sh
diff --git a/v1.1/docs/getting-started-guides/docker.md b/docs/getting-started-guides/docker.md
similarity index 93%
rename from v1.1/docs/getting-started-guides/docker.md
rename to docs/getting-started-guides/docker.md
index 948edafd9d..42468a3dfc 100644
--- a/v1.1/docs/getting-started-guides/docker.md
+++ b/docs/getting-started-guides/docker.md
@@ -65,7 +65,7 @@ docker run \
     /hyperkube kubelet --containerized --hostname-override="127.0.0.1" --address="0.0.0.0" --api-servers=http://localhost:8080 --config=/etc/kubernetes/manifests
 ```
 
-This actually runs the kubelet, which in turn runs a [pod](/{{page.version}}/docs/user-guide/pods) that contains the other master components.
+This actually runs the kubelet, which in turn runs a [pod](/docs/user-guide/pods) that contains the other master components.
 
 ### Step Three: Run the service proxy
 
diff --git a/v1.1/docs/getting-started-guides/fedora/fedora-calico.md b/docs/getting-started-guides/fedora/fedora-calico.md
similarity index 100%
rename from v1.1/docs/getting-started-guides/fedora/fedora-calico.md
rename to docs/getting-started-guides/fedora/fedora-calico.md
diff --git a/v1.1/docs/getting-started-guides/fedora/fedora_ansible_config.md b/docs/getting-started-guides/fedora/fedora_ansible_config.md
similarity index 100%
rename from v1.1/docs/getting-started-guides/fedora/fedora_ansible_config.md
rename to docs/getting-started-guides/fedora/fedora_ansible_config.md
diff --git a/v1.2/docs/getting-started-guides/fedora/fedora_manual_config.md b/docs/getting-started-guides/fedora/fedora_manual_config.md
similarity index 95%
rename from v1.2/docs/getting-started-guides/fedora/fedora_manual_config.md
rename to docs/getting-started-guides/fedora/fedora_manual_config.md
index c865d8a1b2..9b638163a6 100644
--- a/v1.2/docs/getting-started-guides/fedora/fedora_manual_config.md
+++ b/docs/getting-started-guides/fedora/fedora_manual_config.md
@@ -12,7 +12,7 @@
 
 This is a getting started guide for [Fedora](http://fedoraproject.org).  It is a manual configuration so you understand all the underlying packages / services / ports, etc...
 
-This guide will only get ONE node (previously minion) working.  Multiple nodes require a functional [networking configuration](/{{page.version}}/docs/admin/networking)
+This guide will only get ONE node (previously minion) working.  Multiple nodes require a functional [networking configuration](/docs/admin/networking)
 done outside of Kubernetes.  Although the additional Kubernetes configuration requirements should be obvious.
 
 The Kubernetes package provides a few services: kube-apiserver, kube-scheduler, kube-controller-manager, kubelet, kube-proxy.  These
@@ -212,4 +212,4 @@ kubectl delete -f ./node.json
 
 **The cluster should be running! Launch a test pod.**
 
-You should have a functional cluster, check out [101](/{{page.version}}/docs/user-guide/walkthrough/)!
+You should have a functional cluster, check out [101](/docs/user-guide/walkthrough/)!
diff --git a/v1.1/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md b/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md
similarity index 87%
rename from v1.1/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md
rename to docs/getting-started-guides/fedora/flannel_multi_node_cluster.md
index e816b545c3..d10eb42fb6 100644
--- a/v1.1/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md
+++ b/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-This document describes how to deploy Kubernetes on multiple hosts to set up a multi-node cluster and networking with flannel. Follow fedora [getting started guide](/{{page.version}}/docs/getting-started-guides/fedora/fedora_manual_config) to setup 1 master (fed-master) and 2 or more nodes. Make sure that all nodes have different names (fed-node1, fed-node2 and so on) and labels (fed-node1-label, fed-node2-label, and so on) to avoid any conflict. Also make sure that the Kubernetes master host is running etcd, kube-controller-manager, kube-scheduler, and kube-apiserver services, and the nodes are running docker, kube-proxy and kubelet services. Now install flannel on Kubernetes nodes. flannel on each node configures an overlay network that docker uses. flannel runs on each node to setup a unique class-C container network.
+This document describes how to deploy Kubernetes on multiple hosts to set up a multi-node cluster and networking with flannel. Follow fedora [getting started guide](/docs/getting-started-guides/fedora/fedora_manual_config) to setup 1 master (fed-master) and 2 or more nodes. Make sure that all nodes have different names (fed-node1, fed-node2 and so on) and labels (fed-node1-label, fed-node2-label, and so on) to avoid any conflict. Also make sure that the Kubernetes master host is running etcd, kube-controller-manager, kube-scheduler, and kube-apiserver services, and the nodes are running docker, kube-proxy and kubelet services. Now install flannel on Kubernetes nodes. flannel on each node configures an overlay network that docker uses. flannel runs on each node to setup a unique class-C container network.
 
 * TOC
 {:toc}
diff --git a/v1.1/docs/getting-started-guides/gce.md b/docs/getting-started-guides/gce.md
similarity index 90%
rename from v1.1/docs/getting-started-guides/gce.md
rename to docs/getting-started-guides/gce.md
index 09786b54dc..d987ee66ff 100644
--- a/v1.1/docs/getting-started-guides/gce.md
+++ b/docs/getting-started-guides/gce.md
@@ -40,7 +40,7 @@ wget -q -O - https://get.k8s.io | bash
 
 Once this command completes, you will have a master VM and four worker VMs, running as a Kubernetes cluster.
 
-By default, some containers will already be running on your cluster. Containers like `kibana` and `elasticsearch` provide [logging](/{{page.version}}/docs/getting-started-guides/logging), while `heapster` provides [monitoring](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/README.md) services.
+By default, some containers will already be running on your cluster. Containers like `kibana` and `elasticsearch` provide [logging](/docs/getting-started-guides/logging), while `heapster` provides [monitoring](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/README.md) services.
 
 The script run by the commands above creates a cluster with the name/prefix "kubernetes". It defines one specific cluster config, so you can't run it more than once.
 
@@ -53,8 +53,8 @@ cluster/kube-up.sh
 
 If you want more than one cluster running in your project, want to use a different name, or want a different number of worker nodes, see the `<kubernetes>/cluster/gce/config-default.sh` file for more fine-grained configuration before you start up your cluster.
 
-If you run into trouble, please see the section on [troubleshooting](/{{page.version}}/docs/getting-started-guides/gce/#troubleshooting), post to the
-[google-containers group](https://groups.google.com/forum/#!forum/google-containers), or come ask questions on [Slack](/{{page.version}}/docs/troubleshooting/#slack).
+If you run into trouble, please see the section on [troubleshooting](/docs/getting-started-guides/gce/#troubleshooting), post to the
+[google-containers group](https://groups.google.com/forum/#!forum/google-containers), or come ask questions on [Slack](/docs/troubleshooting/#slack).
 
 The next few steps will show you:
 
@@ -68,7 +68,7 @@ The next few steps will show you:
 The cluster startup script will leave you with a running cluster and a `kubernetes` directory on your workstation.
 The next step is to make sure the `kubectl` tool is in your path.
 
-The [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) tool controls the Kubernetes cluster manager.  It lets you inspect your cluster resources, create, delete, and update components, and much more.
+The [kubectl](/docs/user-guide/kubectl/kubectl) tool controls the Kubernetes cluster manager.  It lets you inspect your cluster resources, create, delete, and update components, and much more.
 You will use it to look at your new cluster and bring up example apps.
 
 Add the appropriate binary folder to your `PATH` to access kubectl:
@@ -113,7 +113,7 @@ Once `kubectl` is in your path, you can use it to look at your cluster. E.g., ru
 $ kubectl get --all-namespaces services
 ```
 
-should show a set of [services](/{{page.version}}/docs/user-guide/services) that look something like this:
+should show a set of [services](/docs/user-guide/services) that look something like this:
 
 ```shell
 NAMESPACE     NAME                  CLUSTER_IP       EXTERNAL_IP       PORT(S)       SELECTOR               AGE
@@ -123,7 +123,7 @@ kube-system   kube-ui               10.0.0.3         <none>            80/TCP
 ...
 ```
 
-Similarly, you can take a look at the set of [pods](/{{page.version}}/docs/user-guide/pods) that were created during cluster startup.
+Similarly, you can take a look at the set of [pods](/docs/user-guide/pods) that were created during cluster startup.
 You can do this via the
 
 ```shell
@@ -150,7 +150,7 @@ Some of the pods may take a few seconds to start up (during this time they'll sh
 
 #### Run some examples
 
-Then, see [a simple nginx example](/{{page.version}}/docs/user-guide/simple-nginx) to try out your new cluster.
+Then, see [a simple nginx example](/docs/user-guide/simple-nginx) to try out your new cluster.
 
 For more complete applications, please look in the [examples directory](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/).  The [guestbook example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/) is a good "getting started" walkthrough.
 
diff --git a/docs/getting-started-guides/index.md b/docs/getting-started-guides/index.md
new file mode 100644
index 0000000000..09afc7fe9b
--- /dev/null
+++ b/docs/getting-started-guides/index.md
@@ -0,0 +1,177 @@
+---
+---
+
+Kubernetes can run on a range of platforms, from your laptop, to VMs on a cloud provider, to rack of
+bare metal servers.  The effort required to set up a cluster varies from running a single command to
+crafting your own customized cluster.  We'll guide you in picking a solution that fits for your needs.
+
+If you just want to "kick the tires" on Kubernetes, we recommend the [local Docker-based](/docs/getting-started-guides/docker) solution.
+
+The local Docker-based solution is one of several [Local cluster](#local-machine-solutions) solutions
+that are quick to set up, but are limited to running on one machine.
+
+When you are ready to scale up to more machines and higher availability, a [Hosted](#hosted-solutions)
+solution is the easiest to create and maintain.
+
+[Turn-key cloud solutions](#turn-key-cloud-solutions) require only a few commands to create
+and cover a wider range of cloud providers.
+
+[Custom solutions](#custom-solutions) require more effort to setup but cover and even
+they vary from step-by-step instructions to general advice for setting up
+a Kubernetes cluster from scratch.
+
+* TOC
+{:toc}
+
+### Local-machine Solutions
+
+Local-machine solutions create a single cluster with one or more Kubernetes nodes on a single
+physical machine.  Setup is completely automated and doesn't require a cloud provider account.
+But their size and availability is limited to that of a single machine.
+
+The local-machine solutions are:
+
+- [Local Docker-based](/docs/getting-started-guides/docker) (recommended starting point)
+- [Vagrant](/docs/getting-started-guides/vagrant) (works on any platform with Vagrant: Linux, MacOS, or Windows.)
+- [No-VM local cluster](/docs/getting-started-guides/locally) (Linux only)
+
+
+### Hosted Solutions
+
+[Google Container Engine](https://cloud.google.com/container-engine) offers managed Kubernetes
+clusters.
+
+### Turn-key Cloud Solutions
+
+These solutions allow you to create Kubernetes clusters on a range of Cloud IaaS providers with only a
+few commands, and have active community support.
+
+- [GCE](/docs/getting-started-guides/gce)
+- [AWS](/docs/getting-started-guides/aws)
+- [Azure](/docs/getting-started-guides/coreos/azure/)
+
+### Custom Solutions
+
+Kubernetes can run on a wide range of Cloud providers and bare-metal environments, and with many
+base operating systems.
+
+If you can find a guide below that matches your needs, use it.  It may be a little out of date, but
+it will be easier than starting from scratch.  If you do want to start from scratch because you
+have special requirements or just because you want to understand what is underneath a Kubernetes
+cluster, try the [Getting Started from Scratch](/docs/getting-started-guides/scratch) guide.
+
+If you are interested in supporting Kubernetes on a new platform, check out our [advice for
+writing a new solution](/docs/devel/writing-a-getting-started-guide).
+
+#### Cloud
+
+These solutions are combinations of cloud provider and OS not covered by the above solutions.
+
+- [AWS + coreos](/docs/getting-started-guides/coreos)
+- [GCE + CoreOS](/docs/getting-started-guides/coreos)
+- [AWS + Ubuntu](/docs/getting-started-guides/juju)
+- [Joyent + Ubuntu](/docs/getting-started-guides/juju)
+- [Rackspace + CoreOS](/docs/getting-started-guides/rackspace)
+
+#### On-Premises VMs
+
+- [Vagrant](/docs/getting-started-guides/coreos) (uses CoreOS and flannel)
+- [CloudStack](/docs/getting-started-guides/cloudstack) (uses Ansible, CoreOS and flannel)
+- [Vmware](/docs/getting-started-guides/vsphere)  (uses Debian)
+- [juju.md](/docs/getting-started-guides/juju) (uses Juju, Ubuntu and flannel)
+- [Vmware](/docs/getting-started-guides/coreos)  (uses CoreOS and flannel)
+- [libvirt-coreos.md](/docs/getting-started-guides/libvirt-coreos)  (uses CoreOS)
+- [oVirt](/docs/getting-started-guides/ovirt)
+- [libvirt](/docs/getting-started-guides/fedora/flannel_multi_node_cluster) (uses Fedora and flannel)
+- [KVM](/docs/getting-started-guides/fedora/flannel_multi_node_cluster)  (uses Fedora and flannel)
+
+#### Bare Metal
+
+- [Offline](/docs/getting-started-guides/coreos/bare_metal_offline) (no internet required.  Uses CoreOS and Flannel)
+- [fedora/fedora_ansible_config.md](/docs/getting-started-guides/fedora/fedora_ansible_config)
+- [Fedora single node](/docs/getting-started-guides/fedora/fedora_manual_config)
+- [Fedora multi node](/docs/getting-started-guides/fedora/flannel_multi_node_cluster)
+- [Centos](/docs/getting-started-guides/centos/centos_manual_config)
+- [Ubuntu](/docs/getting-started-guides/ubuntu)
+- [Docker Multi Node](/docs/getting-started-guides/docker-multinode)
+
+#### Integrations
+
+These solutions provide integration with 3rd party schedulers, resource managers, and/or lower level platforms.
+
+- [Kubernetes on Mesos](/docs/getting-started-guides/mesos)
+  - Instructions specify GCE, but are generic enough to be adapted to most existing Mesos clusters
+- [Kubernetes on DCOS](/docs/getting-started-guides/dcos)
+  - Community Edition DCOS uses AWS
+  - Enterprise Edition DCOS supports cloud hosting, on-premise VMs, and bare metal
+
+## Table of Solutions
+
+Here are all the solutions mentioned above in table form.
+
+IaaS Provider        | Config. Mgmt | OS     | Networking  | Docs                                              | Conforms | Support Level
+-------------------- | ------------ | ------ | ----------  | ---------------------------------------------     | ---------| ----------------------------
+GKE                  |              |        | GCE         | [docs](https://cloud.google.com/container-engine) | ['œ“][3]   | Commercial
+Vagrant              | Saltstack    | Fedora | flannel     | [docs](/docs/getting-started-guides/vagrant)                                | ['œ“][2]   | Project
+GCE                  | Saltstack    | Debian | GCE         | [docs](/docs/getting-started-guides/gce)                                    | ['œ“][1]   | Project
+Azure                | CoreOS       | CoreOS | Weave       | [docs](/docs/getting-started-guides/coreos/azure/)                    |          | Community ([@errordeveloper](https://github.com/errordeveloper), [@squillace](https://github.com/squillace), [@chanezon](https://github.com/chanezon), [@crossorigin](https://github.com/crossorigin))
+Docker Single Node   | custom       | N/A    | local       | [docs](/docs/getting-started-guides/docker)                                 |          | Project ([@brendandburns](https://github.com/brendandburns))
+Docker Multi Node    | Flannel      | N/A    | local       | [docs](/docs/getting-started-guides/docker-multinode)                       |          | Project ([@brendandburns](https://github.com/brendandburns))
+Bare-metal           | Ansible      | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/fedora_ansible_config)           |          | Project
+Digital Ocean        | custom       | Fedora | Calico      | [docs](/docs/getting-started-guides/fedora/fedora-calico)                   |          | Community (@djosborne)
+Bare-metal           | custom       | Fedora | _none_      | [docs](/docs/getting-started-guides/fedora/fedora_manual_config)            |          | Project
+Bare-metal           | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
+libvirt              | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
+KVM                  | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
+Mesos/Docker         | custom       | Ubuntu | Docker      | [docs](/docs/getting-started-guides/mesos-docker)                           |          | Community ([Kubernetes-Mesos Authors](https://github.com/mesosphere/kubernetes-mesos/blob/master/AUTHORS.md))
+Mesos/GCE            |              |        |             | [docs](/docs/getting-started-guides/mesos)                                  |          | Community ([Kubernetes-Mesos Authors](https://github.com/mesosphere/kubernetes-mesos/blob/master/AUTHORS.md))
+DCOS                 | Marathon   | CoreOS/Alpine | custom | [docs](/docs/getting-started-guides/dcos)                                   |          | Community ([Kubernetes-Mesos Authors](https://github.com/mesosphere/kubernetes-mesos/blob/master/AUTHORS.md))
+AWS                  | CoreOS       | CoreOS | flannel     | [docs](/docs/getting-started-guides/coreos)                                 |          | Community
+GCE                  | CoreOS       | CoreOS | flannel     | [docs](/docs/getting-started-guides/coreos)                                 |          | Community ([@pires](https://github.com/pires))
+Vagrant              | CoreOS       | CoreOS | flannel     | [docs](/docs/getting-started-guides/coreos)                                 |          | Community ([@pires](https://github.com/pires), [@AntonioMeireles](https://github.com/AntonioMeireles))
+Bare-metal (Offline) | CoreOS       | CoreOS | flannel     | [docs](/docs/getting-started-guides/coreos/bare_metal_offline)              |          | Community ([@jeffbean](https://github.com/jeffbean))
+Bare-metal           | CoreOS       | CoreOS | Calico      | [docs](/docs/getting-started-guides/coreos/bare_metal_calico)               |          | Community ([@caseydavenport](https://github.com/caseydavenport))
+CloudStack           | Ansible      | CoreOS | flannel     | [docs](/docs/getting-started-guides/cloudstack)                             |          | Community ([@runseb](https://github.com/runseb))
+Vmware               |              | Debian | OVS         | [docs](/docs/getting-started-guides/vsphere)                                |          | Community ([@pietern](https://github.com/pietern))
+Bare-metal           | custom       | CentOS | _none_      | [docs](/docs/getting-started-guides/centos/centos_manual_config)            |          | Community ([@coolsvap](https://github.com/coolsvap))
+AWS                  | Juju         | Ubuntu | flannel     | [docs](/docs/getting-started-guides/juju)                                   |          | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) )
+OpenStack/HPCloud    | Juju         | Ubuntu | flannel     | [docs](/docs/getting-started-guides/juju)                                   |          | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) )
+Joyent               | Juju         | Ubuntu | flannel     | [docs](/docs/getting-started-guides/juju)                                   |          | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) )
+AWS                  | Saltstack    | Ubuntu | OVS         | [docs](/docs/getting-started-guides/aws)                                    |          | Community ([@justinsb](https://github.com/justinsb))
+Bare-metal           | custom       | Ubuntu | Calico      | [docs](/docs/getting-started-guides/ubuntu-calico)                          |          | Community ([@djosborne](https://github.com/djosborne))
+Bare-metal           | custom       | Ubuntu | flannel     | [docs](/docs/getting-started-guides/ubuntu)                                 |          | Community ([@resouer](https://github.com/resouer), [@WIZARD-CXY](https://github.com/WIZARD-CXY))
+Local                |              |        | _none_      | [docs](/docs/getting-started-guides/locally)                                |          | Community ([@preillyme](https://github.com/preillyme))
+libvirt/KVM          | CoreOS       | CoreOS | libvirt/KVM | [docs](/docs/getting-started-guides/libvirt-coreos)                         |          | Community ([@lhuard1A](https://github.com/lhuard1A))
+oVirt                |              |        |             | [docs](/docs/getting-started-guides/ovirt)                                  |          | Community ([@simon3z](https://github.com/simon3z))
+Rackspace            | CoreOS       | CoreOS | flannel     | [docs](/docs/getting-started-guides/rackspace)                              |          | Community ([@doublerr](https://github.com/doublerr))
+any                  | any          | any    | any         | [docs](/docs/getting-started-guides/scratch)                                |          | Community ([@erictune](https://github.com/erictune))
+
+
+*Note*: The above table is ordered by version test/used in notes followed by support level.
+
+Definition of columns:
+
+- **IaaS Provider** is who/what provides the virtual or physical machines (nodes) that Kubernetes runs on.
+- **OS** is the base operating system of the nodes.
+- **Config. Mgmt** is the configuration management system that helps install and maintain Kubernetes software on the
+  nodes.
+- **Networking** is what implements the [networking model](/docs/admin/networking).  Those with networking type
+  _none_ may not support more than one node, or may support multiple VM nodes only in the same physical node.
+- **Conformance** indicates whether a cluster created with this configuration has passed the project's conformance
+  tests for supporting the API and base features of Kubernetes v1.0.0.
+- Support Levels
+  - **Project**:  Kubernetes Committers regularly use this configuration, so it usually works with the latest release
+    of Kubernetes.
+  - **Commercial**: A commercial offering with its own support arrangements.
+  - **Community**: Actively supported by community contributions. May not work with more recent releases of Kubernetes.
+  - **Inactive**: No active maintainer.  Not recommended for first-time Kubernetes users, and may be deleted soon.
+- **Notes** is relevant information such as the version of Kubernetes used.
+
+
+<!-- reference style links below here -->
+<!-- GCE conformance test result -->
+[1]: https://gist.github.com/erictune/4cabc010906afbcc5061
+<!-- Vagrant conformance test result -->
+[2]: https://gist.github.com/derekwaynecarr/505e56036cdf010bf6b6
+<!-- GKE conformance test result -->
+[3]: https://gist.github.com/erictune/2f39b22f72565365e59b
diff --git a/v1.1/docs/getting-started-guides/juju.md b/docs/getting-started-guides/juju.md
similarity index 100%
rename from v1.1/docs/getting-started-guides/juju.md
rename to docs/getting-started-guides/juju.md
diff --git a/v1.1/docs/getting-started-guides/libvirt-coreos.md b/docs/getting-started-guides/libvirt-coreos.md
similarity index 100%
rename from v1.1/docs/getting-started-guides/libvirt-coreos.md
rename to docs/getting-started-guides/libvirt-coreos.md
diff --git a/v1.2/docs/getting-started-guides/locally.md b/docs/getting-started-guides/locally.md
similarity index 89%
rename from v1.2/docs/getting-started-guides/locally.md
rename to docs/getting-started-guides/locally.md
index 83dcc2981c..4a75240207 100644
--- a/v1.2/docs/getting-started-guides/locally.md
+++ b/docs/getting-started-guides/locally.md
@@ -8,7 +8,7 @@
 
 #### Linux
 
-Not running Linux? Consider running Linux in a local virtual machine with [Vagrant](/{{page.version}}/docs/getting-started-guides/vagrant), or on a cloud provider like [Google Compute Engine](/{{page.version}}/docs/getting-started-guides/gce)
+Not running Linux? Consider running Linux in a local virtual machine with [Vagrant](/docs/getting-started-guides/vagrant), or on a cloud provider like [Google Compute Engine](/docs/getting-started-guides/gce)
 
 #### Docker
 
@@ -69,8 +69,8 @@ cluster/kubectl.sh get replicationcontrollers
 
 ### Running a user defined pod
 
-Note the difference between a [container](/{{page.version}}/docs/user-guide/containers)
-and a [pod](/{{page.version}}/docs/user-guide/pods). Since you only asked for the former, Kubernetes will create a wrapper pod for you.
+Note the difference between a [container](/docs/user-guide/containers)
+and a [pod](/docs/user-guide/pods). Since you only asked for the former, Kubernetes will create a wrapper pod for you.
 However you cannot view the nginx start page on localhost. To verify that nginx is running you need to run `curl` within the docker container (try `docker exec`).
 
 You can control the specifications of a pod via a user defined manifest, and reach nginx through your browser on the port specified therein:
diff --git a/v1.1/docs/getting-started-guides/logging-elasticsearch.md b/docs/getting-started-guides/logging-elasticsearch.md
similarity index 99%
rename from v1.1/docs/getting-started-guides/logging-elasticsearch.md
rename to docs/getting-started-guides/logging-elasticsearch.md
index 80af1d2975..9fe352eb47 100644
--- a/v1.1/docs/getting-started-guides/logging-elasticsearch.md
+++ b/docs/getting-started-guides/logging-elasticsearch.md
@@ -2,7 +2,7 @@
 ---
 
 On the Google Compute Engine (GCE) platform the default cluster level logging support targets
-[Google Cloud Logging](https://cloud.google.com/logging/docs/) as described at the [Logging](/{{page.version}}/docs/getting-started-guides/logging) getting
+[Google Cloud Logging](https://cloud.google.com/logging/docs/) as described at the [Logging](/docs/getting-started-guides/logging) getting
 started page. Here we describe how to set up a cluster to ingest logs into Elasticsearch and view them using Kibana as an
 alternative to Google Cloud Logging.
 
diff --git a/v1.1/docs/getting-started-guides/logging.md b/docs/getting-started-guides/logging.md
similarity index 98%
rename from v1.1/docs/getting-started-guides/logging.md
rename to docs/getting-started-guides/logging.md
index ecebe877ac..b6f20bccef 100644
--- a/v1.1/docs/getting-started-guides/logging.md
+++ b/docs/getting-started-guides/logging.md
@@ -22,7 +22,7 @@ Here is the same information in a picture which shows how the pods might be plac
 ![Cluster](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/blog-logging/diagrams/cloud-logging.png)
 
 This diagram shows four nodes created on a Google Compute Engine cluster with the name of each VM node on a purple background. The internal and public IPs of each node are shown on gray boxes and the pods running in each node are shown in green boxes. Each pod box shows the name of the pod and the namespace it runs in, the IP address of the pod and the images which are run as part of the pod's execution. Here we see that every node is running a fluentd-cloud-logging pod which is collecting the log output of the containers running on the same node and sending them to Google Cloud Logging. A pod which provides the
-[cluster DNS service](/{{page.version}}/docs/admin/dns) runs on one of the nodes and a pod which provides monitoring support runs on another node.
+[cluster DNS service](/docs/admin/dns) runs on one of the nodes and a pod which provides monitoring support runs on another node.
 
 To help explain how cluster level logging works let's start off with a synthetic log generator pod specification [counter-pod.yaml](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/blog-logging/counter-pod.yaml):
 
diff --git a/v1.1/docs/getting-started-guides/meanstack.md b/docs/getting-started-guides/meanstack.md
similarity index 100%
rename from v1.1/docs/getting-started-guides/meanstack.md
rename to docs/getting-started-guides/meanstack.md
diff --git a/v1.2/docs/getting-started-guides/mesos-docker.md b/docs/getting-started-guides/mesos-docker.md
similarity index 99%
rename from v1.2/docs/getting-started-guides/mesos-docker.md
rename to docs/getting-started-guides/mesos-docker.md
index 37f2fab172..5578025751 100644
--- a/v1.2/docs/getting-started-guides/mesos-docker.md
+++ b/docs/getting-started-guides/mesos-docker.md
@@ -182,7 +182,7 @@ host machine (mac).
 1. Explore examples
 
     To learn more about Pods, Volumes, Labels, Services, and Replication Controllers, start with the
-    [Kubernetes Walkthrough](/{{page.version}}/docs/user-guide/walkthrough/).
+    [Kubernetes Walkthrough](/docs/user-guide/walkthrough/).
 
     To skip to a more advanced example, see the [Guestbook Example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/)
 
diff --git a/v1.1/docs/getting-started-guides/mesos.md b/docs/getting-started-guides/mesos.md
similarity index 100%
rename from v1.1/docs/getting-started-guides/mesos.md
rename to docs/getting-started-guides/mesos.md
diff --git a/v1.1/docs/getting-started-guides/ovirt.md b/docs/getting-started-guides/ovirt.md
similarity index 100%
rename from v1.1/docs/getting-started-guides/ovirt.md
rename to docs/getting-started-guides/ovirt.md
diff --git a/v1.1/docs/getting-started-guides/rackspace.md b/docs/getting-started-guides/rackspace.md
similarity index 100%
rename from v1.1/docs/getting-started-guides/rackspace.md
rename to docs/getting-started-guides/rackspace.md
diff --git a/v1.2/docs/getting-started-guides/rkt/index.md b/docs/getting-started-guides/rkt/index.md
similarity index 95%
rename from v1.2/docs/getting-started-guides/rkt/index.md
rename to docs/getting-started-guides/rkt/index.md
index 909176322c..21cac24c71 100644
--- a/v1.2/docs/getting-started-guides/rkt/index.md
+++ b/docs/getting-started-guides/rkt/index.md
@@ -92,7 +92,7 @@ scripts. The master node is always Ubuntu.
 
 ### Getting started with your cluster
 
-See [a simple nginx example](/{{page.version}}/docs/user-guide/simple-nginx) to try out your new cluster.
+See [a simple nginx example](/docs/user-guide/simple-nginx) to try out your new cluster.
 
 For more complete applications, please look in the [examples directory](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/).
 
@@ -135,4 +135,4 @@ where `$UUID` is the rkt pod's UUID, which you can find via `rkt list --full`, a
 
 ##### Check Kubernetes events, logs.
 
-Besides above tricks, Kubernetes also provides us handy tools for debugging the pods. More information can be found [here](/{{page.version}}/docs/user-guide/application-troubleshooting)
\ No newline at end of file
+Besides above tricks, Kubernetes also provides us handy tools for debugging the pods. More information can be found [here](/docs/user-guide/application-troubleshooting)
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/scratch.md b/docs/getting-started-guides/scratch.md
similarity index 91%
rename from v1.2/docs/getting-started-guides/scratch.md
rename to docs/getting-started-guides/scratch.md
index d1045187cc..02b3f51c11 100644
--- a/v1.2/docs/getting-started-guides/scratch.md
+++ b/docs/getting-started-guides/scratch.md
@@ -3,7 +3,7 @@
 
 This guide is for people who want to craft a custom Kubernetes cluster.  If you
 can find an existing Getting Started Guide that meets your needs on [this
-list](/{{page.version}}/docs/getting-started-guides/README/), then we recommend using it, as you will be able to benefit
+list](/docs/getting-started-guides/README/), then we recommend using it, as you will be able to benefit
 from the experience of others.  However, if you have specific IaaS, networking,
 configuration management, or operating system requirements not met by any of
 those guides, then this guide will provide an outline of the steps you need to
@@ -22,10 +22,10 @@ steps that existing cluster setup scripts are making.
 
   1. You should be familiar with using Kubernetes already.  We suggest you set
     up a temporary cluster by following one of the other Getting Started Guides.
-    This will help you become familiar with the CLI ([kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl)) and concepts ([pods](/{{page.version}}/docs/user-guide/pods), [services](/{{page.version}}/docs/user-guide/services), etc.) first.
+    This will help you become familiar with the CLI ([kubectl](/docs/user-guide/kubectl/kubectl)) and concepts ([pods](/docs/user-guide/pods), [services](/docs/user-guide/services), etc.) first.
   1. You should have `kubectl` installed on your desktop.  This will happen as a side
     effect of completing one of the other Getting Started Guides.  If not, follow the instructions
-    [here](/{{page.version}}/docs/user-guide/prereqs).
+    [here](/docs/user-guide/prereqs).
 
 ### Cloud Provider
 
@@ -52,7 +52,7 @@ on how flags are set on various components.
 
 ### Network
 
-Kubernetes has a distinctive [networking model](/{{page.version}}/docs/admin/networking).
+Kubernetes has a distinctive [networking model](/docs/admin/networking).
 
 Kubernetes allocates an IP address to each pod.  When creating a cluster, you
 need to allocate a block of IPs for Kubernetes to use as Pod IPs.  The simplest
@@ -63,7 +63,7 @@ accomplished in two ways:
 
 - Configure network to route Pod IPs
   - Harder to setup from scratch.
-  - Google Compute Engine ([GCE](/{{page.version}}/docs/getting-started-guides/gce)) and [AWS](/{{page.version}}/docs/getting-started-guides/aws) guides use this approach.
+  - Google Compute Engine ([GCE](/docs/getting-started-guides/gce)) and [AWS](/docs/getting-started-guides/aws) guides use this approach.
   - Need to make the Pod IPs routable by programming routers, switches, etc.
   - Can be configured external to Kubernetes, or can implement in the "Routes" interface of a Cloud Provider module.
   - Generally highest performance.
@@ -96,7 +96,7 @@ You need to select an address range for the Pod IPs.
     using `10.10.0.0/24` through `10.10.255.0/24`, respectively.
   - Need to make these routable or connect with overlay.
 
-Kubernetes also allocates an IP to each [service](/{{page.version}}/docs/user-guide/services).  However,
+Kubernetes also allocates an IP to each [service](/docs/user-guide/services).  However,
 service IPs do not necessarily need to be routable.  The kube-proxy takes care
 of translating Service IPs to Pod IPs before traffic leaves the node.  You do
 need to Allocate a block of IPs for services.  Call this
@@ -140,7 +140,7 @@ You will need binaries for:
 
 A Kubernetes binary release includes all the Kubernetes binaries as well as the supported release of etcd.
 You can use a Kubernetes binary release (recommended) or build your Kubernetes binaries following the instructions in the
-[Developer Documentation](/{{page.version}}/docs/devel/).  Only using a binary release is covered in this guide.
+[Developer Documentation](/docs/devel/).  Only using a binary release is covered in this guide.
 
 Download the [latest binary release](https://github.com/kubernetes/kubernetes/releases/latest) and unzip it.
 Then locate `./kubernetes/server/kubernetes-server-linux-amd64.tar.gz` and unzip *that*.
@@ -238,10 +238,10 @@ The admin user (and any users) need:
 
 Your tokens and passwords need to be stored in a file for the apiserver
 to read.  This guide uses `/var/lib/kube-apiserver/known_tokens.csv`.
-The format for this file is described in the [authentication documentation](/{{page.version}}/docs/admin/authentication).
+The format for this file is described in the [authentication documentation](/docs/admin/authentication).
 
 For distributing credentials to clients, the convention in Kubernetes is to put the credentials
-into a [kubeconfig file](/{{page.version}}/docs/user-guide/kubeconfig-file).
+into a [kubeconfig file](/docs/user-guide/kubeconfig-file).
 
 The kubeconfig file for the administrator can be created as follows:
 
@@ -383,7 +383,7 @@ Arguments to consider:
   - `--docker-root=`
   - `--root-dir=`
   - `--configure-cbr0=` (described above)
-  - `--register-node` (described in [Node](/{{page.version}}/docs/admin/node) documentation.)
+  - `--register-node` (described in [Node](/docs/admin/node) documentation.)
 
 ### kube-proxy
 
@@ -405,7 +405,7 @@ Each node needs to be allocated its own CIDR range for pod networking.
 Call this `NODE_X_POD_CIDR`.
 
 A bridge called `cbr0` needs to be created on each node.  The bridge is explained
-further in the [networking documentation](/{{page.version}}/docs/admin/networking).  The bridge itself
+further in the [networking documentation](/docs/admin/networking).  The bridge itself
 needs an address from `$NODE_X_POD_CIDR` - by convention the first IP.  Call
 this `NODE_X_BRIDGE_ADDR`.  For example, if `NODE_X_POD_CIDR` is `10.0.0.0/16`,
 then `NODE_X_BRIDGE_ADDR` is `10.0.0.1/16`.  NOTE: this retains the `/16` suffix
@@ -460,7 +460,7 @@ traffic to the internet, but have no problem with them inside your GCE Project.
 
 The previous steps all involved "conventional" system administration techniques for setting up
 machines.  You may want to use a Configuration Management system to automate the node configuration
-process.  There are examples of [Saltstack](/{{page.version}}/docs/admin/salt), Ansible, Juju, and CoreOS Cloud Config in the
+process.  There are examples of [Saltstack](/docs/admin/salt), Ansible, Juju, and CoreOS Cloud Config in the
 various Getting Started Guides.
 
 ## Bootstrapping the Cluster
@@ -483,7 +483,7 @@ You will need to run one or more instances of etcd.
     - Log can be written to non-durable storage because storage is replicated.
     - run a single apiserver which connects to one of the etc nodes.
 
-See [cluster-troubleshooting](/{{page.version}}/docs/admin/cluster-troubleshooting) for more discussion on factors affecting cluster
+See [cluster-troubleshooting](/docs/admin/cluster-troubleshooting) for more discussion on factors affecting cluster
 availability.
 
 To run an etcd instance:
@@ -591,7 +591,7 @@ Here are some apiserver flags you may need to set:
 - `--tls-cert-file=/srv/kubernetes/server.cert`
 - `--tls-private-key-file=/srv/kubernetes/server.key`
 - `--admission-control=$RECOMMENDED_LIST`
-  - See [admission controllers](/{{page.version}}/docs/admin/admission-controllers) for recommended arguments.
+  - See [admission controllers](/docs/admin/admission-controllers) for recommended arguments.
 - `--allow-privileged=true`, only if you trust your cluster user to run pods as root.
 
 If you are following the firewall-only security approach, then use these arguments:
@@ -752,7 +752,7 @@ Flags to consider using with controller manager:
  - `--allocate-node-cidrs=`
    - *TODO*: explain when you want controller to do this and when you want to do it another way.
  - `--cloud-provider=` and `--cloud-config` as described in apiserver section.
- - `--service-account-private-key-file=/srv/kubernetes/server.key`, used by the [service account](/{{page.version}}/docs/user-guide/service-accounts) feature.
+ - `--service-account-private-key-file=/srv/kubernetes/server.key`, used by the [service account](/docs/user-guide/service-accounts) feature.
  - `--master=127.0.0.1:8080`
 
 #### Starting and Verifying Apiserver, Scheduler, and Controller Manager
@@ -806,12 +806,12 @@ Otherwise, you will need to manually create node objects.
 
 ### Inspect pods and services
 
-Try to run through the "Inspect your cluster" section in one of the other Getting Started Guides, such as [GCE](/{{page.version}}/docs/getting-started-guides/gce/#inspect-your-cluster).
+Try to run through the "Inspect your cluster" section in one of the other Getting Started Guides, such as [GCE](/docs/getting-started-guides/gce/#inspect-your-cluster).
 You should see some services.  You should also see "mirror pods" for the apiserver, scheduler and controller-manager, plus any add-ons you started.
 
 ### Try Examples
 
-At this point you should be able to run through one of the basic examples, such as the [nginx example](/{{page.version}}/examples/simple-nginx).
+At this point you should be able to run through one of the basic examples, such as the [nginx example](/examples/simple-nginx).
 
 ### Running the Conformance Test
 
@@ -824,5 +824,5 @@ pinging or SSH-ing from one node to another.
 
 ### Getting Help
 
-If you run into trouble, please see the section on [troubleshooting](/{{page.version}}/docs/getting-started-guides/gce#troubleshooting), post to the
-[google-containers group](https://groups.google.com/forum/#!forum/google-containers), or come ask questions on [Slack](/{{page.version}}/docs/troubleshooting#slack).
\ No newline at end of file
+If you run into trouble, please see the section on [troubleshooting](/docs/getting-started-guides/gce#troubleshooting), post to the
+[google-containers group](https://groups.google.com/forum/#!forum/google-containers), or come ask questions on [Slack](/docs/troubleshooting#slack).
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/ubuntu-calico.md b/docs/getting-started-guides/ubuntu-calico.md
similarity index 98%
rename from v1.1/docs/getting-started-guides/ubuntu-calico.md
rename to docs/getting-started-guides/ubuntu-calico.md
index e71c0c8982..ef4b96ba73 100644
--- a/v1.1/docs/getting-started-guides/ubuntu-calico.md
+++ b/docs/getting-started-guides/ubuntu-calico.md
@@ -250,7 +250,7 @@ With this sample configuration, because the containers have private `192.168.0.0
 
 ### NAT on the nodes
 
-The simplest method for enabling connectivity from containers to the internet is to use an iptables masquerade rule. This is the standard mechanism [recommended](/{{page.version}}/docs/admin/networking/#google-compute-engine-gce) in the Kubernetes GCE environment.
+The simplest method for enabling connectivity from containers to the internet is to use an iptables masquerade rule. This is the standard mechanism [recommended](/docs/admin/networking/#google-compute-engine-gce) in the Kubernetes GCE environment.
 
 We need to NAT traffic that has a destination outside of the cluster. Internal traffic includes the master/nodes, and the container IP pools. A suitable masquerade chain would follow the pattern below, replacing the following variables:
 
diff --git a/v1.1/docs/getting-started-guides/ubuntu.md b/docs/getting-started-guides/ubuntu.md
similarity index 98%
rename from v1.1/docs/getting-started-guides/ubuntu.md
rename to docs/getting-started-guides/ubuntu.md
index a8de4a3a28..bd6a06b903 100644
--- a/v1.1/docs/getting-started-guides/ubuntu.md
+++ b/docs/getting-started-guides/ubuntu.md
@@ -258,4 +258,4 @@ Some examples are as follows:
 
 The script will not delete any resources of your cluster, it just replaces the binaries.
 You can use `kubectl` command to check if the newly upgraded k8s is working correctly.
-For example, use `$ kubectl get nodes` to see if all of your nodes are ready.Or refer to [test-it-out](/{{page.version}}/docs/getting-started-guides/ubuntu/#test-it-out)
\ No newline at end of file
+For example, use `$ kubectl get nodes` to see if all of your nodes are ready.Or refer to [test-it-out](/docs/getting-started-guides/ubuntu/#test-it-out)
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/vagrant.md b/docs/getting-started-guides/vagrant.md
similarity index 97%
rename from v1.1/docs/getting-started-guides/vagrant.md
rename to docs/getting-started-guides/vagrant.md
index 9bea0df0a1..37c06bcbbc 100644
--- a/v1.1/docs/getting-started-guides/vagrant.md
+++ b/docs/getting-started-guides/vagrant.md
@@ -293,7 +293,7 @@ If this is your first time creating the cluster, the kubelet on each node schedu
 
 #### I want to make changes to Kubernetes code!
 
-To set up a vagrant cluster for hacking, follow the [vagrant developer guide](/{{page.version}}/docs/devel/developer-guides/vagrant).
+To set up a vagrant cluster for hacking, follow the [vagrant developer guide](/docs/devel/developer-guides/vagrant).
 
 #### I have brought Vagrant up but the nodes cannot validate!
 
diff --git a/v1.1/docs/getting-started-guides/vsphere.md b/docs/getting-started-guides/vsphere.md
similarity index 93%
rename from v1.1/docs/getting-started-guides/vsphere.md
rename to docs/getting-started-guides/vsphere.md
index e41175bcac..da3eb4b0b4 100644
--- a/v1.1/docs/getting-started-guides/vsphere.md
+++ b/docs/getting-started-guides/vsphere.md
@@ -27,7 +27,7 @@ export GOPATH=$HOME/src/go
 go get github.com/vmware/govmomi/govc
 ```
 
-5. Get or build a [binary release](/{{page.version}}/docs/getting-started-guides/binary_release)
+5. Get or build a [binary release](/docs/getting-started-guides/binary_release)
 
 ### Setup
 
diff --git a/v1.1/index.md b/docs/index.md
similarity index 100%
rename from v1.1/index.md
rename to docs/index.md
diff --git a/v1.2/pagelist.md b/docs/pagelist.md
similarity index 73%
rename from v1.2/pagelist.md
rename to docs/pagelist.md
index 431f35c628..dcfebf90fb 100644
--- a/v1.2/pagelist.md
+++ b/docs/pagelist.md
@@ -17,6 +17,6 @@ The following is a list of all pages for {{ page.version }}. We also have a [`si
     {% endif %}
     {% endif %}
   {% endfor %}
-* {% if pageTOC %}**[{{ pageTOC | capitalize }}](/{{page.version}}/{%if pageTOC != "guides"%}{{pageTOC}}/{%endif%})**: {% endif %}[{% if page.title %}{{page.title}}{% else %}{{ page.url }}{% endif %}]({{ page.url }})
+* {% if pageTOC %}**[{{ pageTOC | capitalize }}](/{%if pageTOC != "guides"%}{{pageTOC}}/{%endif%})**: {% endif %}[{% if page.title %}{{page.title}}{% else %}{{ page.url }}{% endif %}]({{ page.url }})
   {% endif %}
 {% endfor %}
\ No newline at end of file
diff --git a/v1.1/reference.md b/docs/reference.md
similarity index 100%
rename from v1.1/reference.md
rename to docs/reference.md
diff --git a/v1.1/docs/reporting-security-issues.md b/docs/reporting-security-issues.md
similarity index 100%
rename from v1.1/docs/reporting-security-issues.md
rename to docs/reporting-security-issues.md
diff --git a/v1.1/docs/roadmap.md b/docs/roadmap.md
similarity index 100%
rename from v1.1/docs/roadmap.md
rename to docs/roadmap.md
diff --git a/v1.1/samples.md b/docs/samples.md
similarity index 100%
rename from v1.1/samples.md
rename to docs/samples.md
diff --git a/search.md b/docs/search.md
similarity index 100%
rename from search.md
rename to docs/search.md
diff --git a/v1.1/docs/troubleshooting.md b/docs/troubleshooting.md
similarity index 81%
rename from v1.1/docs/troubleshooting.md
rename to docs/troubleshooting.md
index fd79413735..bf0c90e007 100644
--- a/v1.1/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -5,10 +5,10 @@
 
 Sometimes things go wrong.  This guide is aimed at making them right.  It has two sections:
 
-   * [Troubleshooting your application](/{{page.version}}/docs/user-guide/application-troubleshooting) - Useful for users who are deploying code into Kubernetes and wondering why it is not working.
-   * [Troubleshooting your cluster](/{{page.version}}/docs/admin/cluster-troubleshooting) - Useful for cluster administrators and people whose Kubernetes cluster is unhappy.
+   * [Troubleshooting your application](/docs/user-guide/application-troubleshooting) - Useful for users who are deploying code into Kubernetes and wondering why it is not working.
+   * [Troubleshooting your cluster](/docs/admin/cluster-troubleshooting) - Useful for cluster administrators and people whose Kubernetes cluster is unhappy.
 
-You should also check the [known issues](/{{page.version}}/docs/user-guide/known-issues) for the release you're using.
+You should also check the [known issues](/docs/user-guide/known-issues) for the release you're using.
 
 # Getting help
 
@@ -16,7 +16,7 @@ If your problem isn't answered by any of the guides above, there are variety of
 
 ## Questions
 
-If you aren't familiar with it, many of your questions may be answered by the [user guide](/{{page.version}}/docs/user-guide/).
+If you aren't familiar with it, many of your questions may be answered by the [user guide](/docs/user-guide/).
 
 We also have a number of FAQ pages:
 
diff --git a/v1.2/docs/user-guide/accessing-the-cluster.md b/docs/user-guide/accessing-the-cluster.md
similarity index 89%
rename from v1.2/docs/user-guide/accessing-the-cluster.md
rename to docs/user-guide/accessing-the-cluster.md
index eecfaeae6c..190ada577d 100644
--- a/v1.2/docs/user-guide/accessing-the-cluster.md
+++ b/docs/user-guide/accessing-the-cluster.md
@@ -13,7 +13,7 @@ Kubernetes CLI, `kubectl`.
 
 To access a cluster, you need to know the location of the cluster and have credentials
 to access it.  Typically, this is automatically set-up when you work through
-though a [Getting started guide](/{{page.version}}/docs/getting-started-guides/),
+though a [Getting started guide](/docs/getting-started-guides/),
 or someone else setup the cluster and provided you with credentials and a location.
 
 Check the location and credentials that kubectl knows about with this command:
@@ -23,7 +23,7 @@ $ kubectl config view
 ```
 
 Many of the [examples](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/) provide an introduction to using
-kubectl and complete documentation is found in the [kubectl manual](/{{page.version}}/docs/user-guide/kubectl/kubectl).
+kubectl and complete documentation is found in the [kubectl manual](/docs/user-guide/kubectl/kubectl).
 
 ### Directly accessing the REST API
 
@@ -52,7 +52,7 @@ Run it like this:
 $ kubectl proxy --port=8080 &
 ```
 
-See [kubectl proxy](/{{page.version}}/docs/user-guide/kubectl/kubectl_proxy) for more details.
+See [kubectl proxy](/docs/user-guide/kubectl/kubectl_proxy) for more details.
 
 Then you can explore the API with curl, wget, or a browser, like so:
 
@@ -90,16 +90,16 @@ certificate.
 
 On some clusters, the apiserver does not require authentication; it may serve
 on localhost, or be protected by a firewall.  There is not a standard
-for this.  [Configuring Access to the API](/{{page.version}}/docs/admin/accessing-the-api)
+for this.  [Configuring Access to the API](/docs/admin/accessing-the-api)
 describes how a cluster admin can configure this.  Such approaches may conflict
 with future high-availability support.
 
 ### Programmatic access to the API
 
-There are [client libraries](/{{page.version}}/docs/devel/client-libraries) for accessing the API
+There are [client libraries](/docs/devel/client-libraries) for accessing the API
 from several languages.  The Kubernetes project-supported
 [Go](http://releases.k8s.io/{{page.githubbranch}}/pkg/client/)
-client library can use the same [kubeconfig file](/{{page.version}}/docs/user-guide/kubeconfig-file)
+client library can use the same [kubeconfig file](/docs/user-guide/kubeconfig-file)
 as the kubectl CLI does to locate and authenticate to the apiserver.
 
 See documentation for other libraries for how they authenticate.
@@ -114,7 +114,7 @@ the `kubernetes` DNS name, which resolves to a Service IP which in turn
 will be routed to an apiserver.
 
 The recommended way to authenticate to the apiserver is with a
-[service account](/{{page.version}}/docs/user-guide/service-accounts) credential.  By kube-system, a pod
+[service account](/docs/user-guide/service-accounts) credential.  By kube-system, a pod
 is associated with a service account, and a credential (token) for that
 service account is placed into the filesystem tree of each container in that pod,
 at `/var/run/secrets/kubernetes.io/serviceaccount/token`.
@@ -136,7 +136,7 @@ In each case, the credentials of the pod are used to communicate securely with t
 
 The previous section was about connecting the Kubernetes API server.  This section is about
 connecting to other services running on Kubernetes cluster.  In Kubernetes, the
-[nodes](/{{page.version}}/docs/admin/node), [pods](/{{page.version}}/docs/user-guide/pods) and [services](/{{page.version}}/docs/user-guide/services) all have
+[nodes](/docs/admin/node), [pods](/docs/user-guide/pods) and [services](/docs/user-guide/services) all have
 their own IPs.  In many cases, the node IPs, pod IPs, and some service IPs on a cluster will not be
 routable, so they will not be reachable from a machine outside the cluster,
 such as your desktop machine.
@@ -147,8 +147,8 @@ You have several options for connecting to nodes, pods and services from outside
 
   - Access services through public IPs.
     - Use a service with type `NodePort` or `LoadBalancer` to make the service reachable outside
-      the cluster.  See the [services](/{{page.version}}/docs/user-guide/services) and
-      [kubectl expose](/{{page.version}}/docs/user-guide/kubectl/kubectl_expose) documentation.
+      the cluster.  See the [services](/docs/user-guide/services) and
+      [kubectl expose](/docs/user-guide/kubectl/kubectl_expose) documentation.
     - Depending on your cluster environment, this may just expose the service to your corporate network,
       or it may expose it to the internet.  Think about whether the service being exposed is secure.
       Does it do its own authentication?
@@ -164,7 +164,7 @@ You have several options for connecting to nodes, pods and services from outside
     - Only works for HTTP/HTTPS.
     - Described [here](#discovering-builtin-services).
   - Access from a node or pod in the cluster.
-    - Run a pod, and then connect to a shell in it using [kubectl exec](/{{page.version}}/docs/user-guide/kubectl/kubectl_exec).
+    - Run a pod, and then connect to a shell in it using [kubectl exec](/docs/user-guide/kubectl/kubectl_exec).
       Connect to other nodes, pods, and services from that shell.
     - Some clusters may allow you to ssh to a node in the cluster.  From there you may be able to
       access cluster services.  This is a non-standard method, and will work on some clusters but
@@ -251,7 +251,7 @@ There are several different proxies you may encounter when using Kubernetes:
     - proxy to target may use HTTP or HTTPS as chosen by proxy using available information
     - can be used to reach a Node, Pod, or Service
     - does load balancing when used to reach a Service
-  1. The [kube proxy](/{{page.version}}/docs/user-guide/services/#ips-and-vips):
+  1. The [kube proxy](/docs/user-guide/services/#ips-and-vips):
     - runs on each node
     - proxies UDP and TCP
     - does not understand HTTP
diff --git a/v1.2/docs/user-guide/annotations.md b/docs/user-guide/annotations.md
similarity index 94%
rename from v1.2/docs/user-guide/annotations.md
rename to docs/user-guide/annotations.md
index ff2965cbe5..9a28452929 100644
--- a/v1.2/docs/user-guide/annotations.md
+++ b/docs/user-guide/annotations.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-We have [labels](/{{page.version}}/docs/user-guide/labels) for identifying metadata.
+We have [labels](/docs/user-guide/labels) for identifying metadata.
 
 It is also useful to be able to attach arbitrary non-identifying metadata, for retrieval by API clients such as tools, libraries, etc. This information may be large, may be structured or unstructured, may include characters not permitted by labels, etc. Such information would not be used for object selection and therefore doesn't belong in labels.
 
diff --git a/v1.1/docs/user-guide/application-troubleshooting.md b/docs/user-guide/application-troubleshooting.md
similarity index 92%
rename from v1.1/docs/user-guide/application-troubleshooting.md
rename to docs/user-guide/application-troubleshooting.md
index 9f3ea06aaf..a82cf67b60 100644
--- a/v1.1/docs/user-guide/application-troubleshooting.md
+++ b/docs/user-guide/application-troubleshooting.md
@@ -3,7 +3,7 @@
 
 This guide is to help users debug applications that are deployed into Kubernetes and not behaving correctly.
 This is *not* a guide for people who want to debug their cluster.  For that you should check out
-[this guide](/{{page.version}}/docs/admin/cluster-troubleshooting)
+[this guide](/docs/admin/cluster-troubleshooting)
 
 * TOC
 {:toc}
@@ -41,7 +41,7 @@ there are insufficient resources of one type or another that prevent scheduling.
 your pod.  Reasons include:
 
 * **You don't have enough resources**:  You may have exhausted the supply of CPU or Memory in your cluster, in this case
-you need to delete Pods, adjust resource requests, or add new nodes to your cluster. See [Compute Resources document](/{{page.version}}/docs/user-guide/compute-resources/#my-pods-are-pending-with-event-message-failedscheduling) for more information.
+you need to delete Pods, adjust resource requests, or add new nodes to your cluster. See [Compute Resources document](/docs/user-guide/compute-resources/#my-pods-are-pending-with-event-message-failedscheduling) for more information.
 
 * **You are using `hostPort`**:  When you bind a Pod to a `hostPort` there are a limited number of places that pod can be
 scheduled.  In most cases, `hostPort` is unnecessary, try using a Service object to expose your Pod.  If you do require
@@ -186,6 +186,6 @@ check:
 
 #### More information
 
-If none of the above solves your problem, follow the instructions in [Debugging Service document](/{{page.version}}/docs/user-guide/debugging-services) to make sure that your `Service` is running, has `Endpoints`, and your `Pods` are actually serving; you have DNS working, iptables rules installed, and kube-proxy does not seem to be misbehaving.
+If none of the above solves your problem, follow the instructions in [Debugging Service document](/docs/user-guide/debugging-services) to make sure that your `Service` is running, has `Endpoints`, and your `Pods` are actually serving; you have DNS working, iptables rules installed, and kube-proxy does not seem to be misbehaving.
 
-You may also visit [troubleshooting document](/{{page.version}}/docs/troubleshooting/) for more information.
\ No newline at end of file
+You may also visit [troubleshooting document](/docs/troubleshooting/) for more information.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/compute-resources.md b/docs/user-guide/compute-resources.md
similarity index 95%
rename from v1.1/docs/user-guide/compute-resources.md
rename to docs/user-guide/compute-resources.md
index 533edd866f..f962a35ac8 100644
--- a/v1.1/docs/user-guide/compute-resources.md
+++ b/docs/user-guide/compute-resources.md
@@ -4,7 +4,7 @@
 * TOC
 {:toc}
 
-When specifying a [pod](/{{page.version}}/docs/user-guide/pods), you can optionally specify how much CPU and memory (RAM) each
+When specifying a [pod](/docs/user-guide/pods), you can optionally specify how much CPU and memory (RAM) each
 container needs.  When containers have their resource requests specified, the scheduler is
 able to make better decisions about which nodes to place pods on; and when containers have their
 limits specified, contention for resources on a node can be handled in a specified manner. For
@@ -16,8 +16,8 @@ in units of cores.  Memory is specified in units of bytes.
 
 CPU and RAM are collectively referred to as *compute resources*, or just *resources*.  Compute
 resources are measureable quantities which can be requested, allocated, and consumed.  They are
-distinct from [API resources](/{{page.version}}/docs/user-guide/working-with-resources).  API resources, such as pods and
-[services](/{{page.version}}/docs/user-guide/services) are objects that can be written to and retrieved from the Kubernetes API
+distinct from [API resources](/docs/user-guide/working-with-resources).  API resources, such as pods and
+[services](/docs/user-guide/services) are objects that can be written to and retrieved from the Kubernetes API
 server.
 
 ## Resource Requests and Limits of Pod and Container
@@ -171,7 +171,7 @@ Here you can see from the `Allocated resources` section that that a pod which as
 
 Looking at the `Pods` section, you can see which pods are taking up space on the node.
 
-The [resource quota](/{{page.version}}/docs/admin/resource-quota) feature can be configured
+The [resource quota](/docs/admin/resource-quota) feature can be configured
 to limit the total amount of resources that can be consumed.  If used in conjunction
 with namespaces, it can prevent one team from hogging all the resources.
 
@@ -234,7 +234,7 @@ We can see that this container was terminated because `reason:OOM Killed`, where
 
 The current system only allows resource quantities to be specified on a container.
 It is planned to improve accounting for resources which are shared by all containers in a pod,
-such as [EmptyDir volumes](/{{page.version}}/docs/user-guide/volumes/#emptydir).
+such as [EmptyDir volumes](/docs/user-guide/volumes/#emptydir).
 
 The current system only supports container requests and limits for CPU and Memory.
 It is planned to add new resource types, including a node disk space
diff --git a/v1.2/docs/user-guide/config-best-practices.md b/docs/user-guide/config-best-practices.md
similarity index 77%
rename from v1.2/docs/user-guide/config-best-practices.md
rename to docs/user-guide/config-best-practices.md
index 2f2ebcdc6a..b3f36056a0 100644
--- a/v1.2/docs/user-guide/config-best-practices.md
+++ b/docs/user-guide/config-best-practices.md
@@ -9,16 +9,16 @@ This document is meant to highlight and consolidate in one place configuration b
 1. Group related objects together in a single file. This is often better than separate files.
 1. Use `kubectl create -f <directory>` where possible. This looks for config objects in all `.yaml`, `.yml`, and `.json` files in `<directory>` and passes them to create.
 1. Create a service before corresponding replication controllers so that the scheduler can spread the pods comprising the service. You can also create the replication controller without specifying replicas, create the service, then scale up the replication controller, which may work better in an example using progressive disclosure and may have benefits in real scenarios also, such as ensuring one replica works before creating lots of them)
-1. Don't use `hostPort` unless absolutely necessary (e.g., for a node daemon) as it will prevent certain scheduling configurations due to port conflicts. Use the apiserver proxying or port forwarding for debug/admin access, or a service for external service access. If you need to expose a pod's port on the host machine, consider using a [NodePort](/{{page.version}}/docs/user-guide/services/#type--loadbalancer) service before resorting to `hostPort`. If you only need access to the port for debugging purposes, you can also use the [kubectl proxy and apiserver proxy](/{{page.version}}/docs/user-guide/connecting-to-applications-proxy) or [kubectl port-forward](/{{page.version}}/docs/user-guide/connecting-to-applications-port-forward).
+1. Don't use `hostPort` unless absolutely necessary (e.g., for a node daemon) as it will prevent certain scheduling configurations due to port conflicts. Use the apiserver proxying or port forwarding for debug/admin access, or a service for external service access. If you need to expose a pod's port on the host machine, consider using a [NodePort](/docs/user-guide/services/#type--loadbalancer) service before resorting to `hostPort`. If you only need access to the port for debugging purposes, you can also use the [kubectl proxy and apiserver proxy](/docs/user-guide/connecting-to-applications-proxy) or [kubectl port-forward](/docs/user-guide/connecting-to-applications-port-forward).
 1. Don't use `hostNetwork` for the same reasons as `hostPort`.
 1. Don't specify default values unnecessarily, to simplify and minimize configs. For example, omit the selector and labels in ReplicationController if you want them to be the same as the labels in its podTemplate, since those fields are populated from the podTemplate labels by default.
 1. Instead of attaching one label to a set of pods to represent a service (e.g., `service: myservice`) and another to represent the replication controller managing the pods (e.g., `controller: mycontroller`), attach labels that identify semantic attributes of your application or deployment and select the appropriate subsets in your service and replication controller, such as `{ app: myapp, tier: frontend, deployment: v3 }`. A service can be made to span multiple deployments, such as across rolling updates, by simply omitting release-specific labels from its selector, rather than updating a service's selector to match the replication controller's selector fully.
-1. Use kubectl bulk operations (via files and/or labels) for get and delete. See [label selectors](/{{page.version}}/docs/user-guide/labels/#label-selectors) and [using labels effectively](/{{page.version}}/docs/user-guide/managing-deployments/#using-labels-effectively).
-1. Use kubectl run and expose to quickly create and expose single container replication controllers. See the [quick start guide](/{{page.version}}/docs/user-guide/quick-start) for an example.
-1. Use headless services for easy service discovery when you don't need kube-proxy load balancing. See [headless services](/{{page.version}}/docs/user-guide/services/#headless-services).
+1. Use kubectl bulk operations (via files and/or labels) for get and delete. See [label selectors](/docs/user-guide/labels/#label-selectors) and [using labels effectively](/docs/user-guide/managing-deployments/#using-labels-effectively).
+1. Use kubectl run and expose to quickly create and expose single container replication controllers. See the [quick start guide](/docs/user-guide/quick-start) for an example.
+1. Use headless services for easy service discovery when you don't need kube-proxy load balancing. See [headless services](/docs/user-guide/services/#headless-services).
 1. Use kubectl delete rather than stop. Delete has a superset of the functionality of stop and stop is deprecated.
 1. If there is a viable alternative to naked pods (i.e. pods not bound to a controller), go with the alternative. Controllers are almost always preferable to creating pods (except for some `restartPolicy: Never` scenarios). A minimal Job is coming. See [#1624](http://issue.k8s.io/1624). Naked pods will not be rescheduled in the event of node failure.
-1. Put a version number or hash as a suffix to the name and in a label on a replication controller to facilitate rolling update, as we do for [--image](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update). This is necessary because rolling-update actually creates a new controller as opposed to modifying the existing controller. This does not play well with version agnostic controller names.
+1. Put a version number or hash as a suffix to the name and in a label on a replication controller to facilitate rolling update, as we do for [--image](/docs/user-guide/kubectl/kubectl_rolling-update). This is necessary because rolling-update actually creates a new controller as opposed to modifying the existing controller. This does not play well with version agnostic controller names.
 1. Put an object description in an annotation to allow better introspection.
 
 
diff --git a/v1.2/docs/user-guide/configuring-containers.md b/docs/user-guide/configuring-containers.md
similarity index 85%
rename from v1.2/docs/user-guide/configuring-containers.md
rename to docs/user-guide/configuring-containers.md
index 5704cb0e17..14314ec0ec 100644
--- a/v1.2/docs/user-guide/configuring-containers.md
+++ b/docs/user-guide/configuring-containers.md
@@ -6,13 +6,13 @@
 
 ## Configuration in Kubernetes
 
-In addition to the imperative-style commands, such as `kubectl run` and `kubectl expose`, described [elsewhere](/{{page.version}}/docs/user-guide/quick-start), Kubernetes supports declarative configuration. Often times, configuration files are preferable to imperative commands, since they can be checked into version control and changes to the files can be code reviewed, which is especially important for more complex configurations, producing a more robust, reliable and archival system.
+In addition to the imperative-style commands, such as `kubectl run` and `kubectl expose`, described [elsewhere](/docs/user-guide/quick-start), Kubernetes supports declarative configuration. Often times, configuration files are preferable to imperative commands, since they can be checked into version control and changes to the files can be code reviewed, which is especially important for more complex configurations, producing a more robust, reliable and archival system.
 
 In the declarative style, all configuration is stored in YAML or JSON configuration files using Kubernetes's API resource schemas as the configuration schemas. `kubectl` can create, update, delete, and get API resources. The `apiVersion` (currently 'v1'?), resource `kind`, and resource `name` are used by `kubectl` to construct the appropriate API path to invoke for the specified operation.
 
 ## Launching a container using a configuration file
 
-Kubernetes executes containers in [*Pods*](/{{page.version}}/docs/user-guide/pods). A pod containing a simple Hello World container can be specified in YAML as follows:
+Kubernetes executes containers in [*Pods*](/docs/user-guide/pods). A pod containing a simple Hello World container can be specified in YAML as follows:
 
 ```yaml
 apiVersion: v1
@@ -31,7 +31,7 @@ The value of `metadata.name`, `hello-world`, will be the name of the pod resourc
 
 `restartPolicy: Never` indicates that we just want to run the container once and then terminate the pod.
 
-The [`command`](/{{page.version}}/docs/user-guide/containers/#containers-and-commands) overrides the Docker container's `Entrypoint`. Command arguments (corresponding to Docker's `Cmd`) may be specified using `args`, as follows:
+The [`command`](/docs/user-guide/containers/#containers-and-commands) overrides the Docker container's `Entrypoint`. Command arguments (corresponding to Docker's `Cmd`) may be specified using `args`, as follows:
 
 ```yaml
 command: ["/bin/echo"]
@@ -160,4 +160,4 @@ On the other hand, containers and their logs are eventually deleted automaticall
 
 ## What's next?
 
-[Learn about deploying continuously running applications.](/{{page.version}}/docs/user-guide/deploying-applications)
+[Learn about deploying continuously running applications.](/docs/user-guide/deploying-applications)
diff --git a/v1.1/docs/user-guide/connecting-applications.md b/docs/user-guide/connecting-applications.md
similarity index 97%
rename from v1.1/docs/user-guide/connecting-applications.md
rename to docs/user-guide/connecting-applications.md
index 0788094ec3..9d00a4b32d 100644
--- a/v1.1/docs/user-guide/connecting-applications.md
+++ b/docs/user-guide/connecting-applications.md
@@ -57,7 +57,7 @@ $ kubectl get pods -l app=nginx -o json | grep podIP
 
 You should be able to ssh into any node in your cluster and curl both IPs. Note that the containers are *not* using port 80 on the node, nor are there any special NAT rules to route traffic to the pod. This means you can run multiple nginx pods on the same node all using the same containerPort and access them from any other pod or node in your cluster using IP. Like Docker, ports can still be published to the host node's interface(s), but the need for this is radically diminished because of the networking model.
 
-You can read more about [how we achieve this](/{{page.version}}/docs/admin/networking/#how-to-achieve-this) if you're curious.
+You can read more about [how we achieve this](/docs/admin/networking/#how-to-achieve-this) if you're curious.
 
 ## Creating a Service
 
@@ -113,7 +113,7 @@ NAME         ENDPOINTS
 nginxsvc     10.245.0.14:80,10.245.0.15:80
 ```
 
-You should now be able to curl the nginx Service on `10.0.116.146:80` from any node in your cluster. Note that the Service IP is completely virtual, it never hits the wire, if you're curious about how this works you can read more about the [service proxy](/{{page.version}}/docs/user-guide/services/#virtual-ips-and-service-proxies).
+You should now be able to curl the nginx Service on `10.0.116.146:80` from any node in your cluster. Note that the Service IP is completely virtual, it never hits the wire, if you're curious about how this works you can read more about the [service proxy](/docs/user-guide/services/#virtual-ips-and-service-proxies).
 
 ## Accessing the Service
 
@@ -196,7 +196,7 @@ Till now we have only accessed the nginx server from within the cluster. Before
 
 * Self signed certificates for https (unless you already have an identity certificate)
 * An nginx server configured to use the certificates
-* A [secret](/{{page.version}}/docs/user-guide/secrets) that makes the certificates accessible to pods
+* A [secret](/docs/user-guide/secrets) that makes the certificates accessible to pods
 
 You can acquire all these from the [nginx https example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/https-nginx/), in short:
 
@@ -383,4 +383,4 @@ cluster/private cloud network.
 
 ## What's next?
 
-[Learn about more Kubernetes features that will help you run containers reliably in production.](/{{page.version}}/docs/user-guide/production-pods)
+[Learn about more Kubernetes features that will help you run containers reliably in production.](/docs/user-guide/production-pods)
diff --git a/v1.1/docs/user-guide/connecting-to-applications-port-forward.md b/docs/user-guide/connecting-to-applications-port-forward.md
similarity index 69%
rename from v1.1/docs/user-guide/connecting-to-applications-port-forward.md
rename to docs/user-guide/connecting-to-applications-port-forward.md
index c74dfaa0c5..0cf9add25a 100644
--- a/v1.1/docs/user-guide/connecting-to-applications-port-forward.md
+++ b/docs/user-guide/connecting-to-applications-port-forward.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-kubectl port-forward forwards connections to a local port to a port on a pod. Its man page is available [here](/{{page.version}}/docs/user-guide/kubectl/kubectl_port-forward). Compared to [kubectl proxy](/{{page.version}}/docs/user-guide/accessing-the-cluster/#using-kubectl-proxy), `kubectl port-forward` is more generic as it can forward TCP traffic while `kubectl proxy` can only forward HTTP traffic. This guide demonstrates how to use `kubectl port-forward` to connect to a Redis database, which may be useful for database debugging.
+kubectl port-forward forwards connections to a local port to a port on a pod. Its man page is available [here](/docs/user-guide/kubectl/kubectl_port-forward). Compared to [kubectl proxy](/docs/user-guide/accessing-the-cluster/#using-kubectl-proxy), `kubectl port-forward` is more generic as it can forward TCP traffic while `kubectl proxy` can only forward HTTP traffic. This guide demonstrates how to use `kubectl port-forward` to connect to a Redis database, which may be useful for database debugging.
 
 ## Creating a Redis master
 
diff --git a/v1.2/docs/user-guide/connecting-to-applications-proxy.md b/docs/user-guide/connecting-to-applications-proxy.md
similarity index 66%
rename from v1.2/docs/user-guide/connecting-to-applications-proxy.md
rename to docs/user-guide/connecting-to-applications-proxy.md
index 26ab41e361..76ccf1a569 100644
--- a/v1.2/docs/user-guide/connecting-to-applications-proxy.md
+++ b/docs/user-guide/connecting-to-applications-proxy.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-You have seen the [basics](/{{page.version}}/docs/user-guide/accessing-the-cluster) about `kubectl proxy` and `apiserver proxy`. This guide shows how to use them together to access a service([kube-ui](/{{page.version}}/docs/user-guide/ui)) running on the Kubernetes cluster from your workstation.
+You have seen the [basics](/docs/user-guide/accessing-the-cluster) about `kubectl proxy` and `apiserver proxy`. This guide shows how to use them together to access a service([kube-ui](/docs/user-guide/ui)) running on the Kubernetes cluster from your workstation.
 
 
 ## Getting the apiserver proxy URL of kube-ui
@@ -13,7 +13,7 @@ $ kubectl cluster-info | grep "KubeUI"
 KubeUI is running at https://173.255.119.104/api/v1/proxy/namespaces/kube-system/services/kube-ui
 ```
 
-if this command does not find the URL, try the steps [here](/{{page.version}}/docs/user-guide/ui/#accessing-the-ui).
+if this command does not find the URL, try the steps [here](/docs/user-guide/ui/#accessing-the-ui).
 
 
 ## Connecting to the kube-ui service from your local workstation
diff --git a/v1.2/docs/user-guide/container-environment.md b/docs/user-guide/container-environment.md
similarity index 91%
rename from v1.2/docs/user-guide/container-environment.md
rename to docs/user-guide/container-environment.md
index b816cd3442..35fcac136f 100644
--- a/v1.2/docs/user-guide/container-environment.md
+++ b/docs/user-guide/container-environment.md
@@ -6,7 +6,7 @@ This document describes the environment for Kubelet managed containers on a Kube
 This cluster information makes it possible to build applications that are *cluster aware*.
 Additionally, the Kubernetes container environment defines a series of hooks that are surfaced to optional hook handlers defined as part of individual containers.  Container hooks are somewhat analogous to operating system signals in a traditional process model.   However these hooks are designed to make it easier to build reliable, scalable cloud applications in the Kubernetes cluster.  Containers that participate in this cluster lifecycle become *cluster native*.
 
-Another important part of the container environment is the file system that is available to the container.  In Kubernetes, the filesystem is a combination of an [image](/{{page.version}}/docs/user-guide/images) and one or more [volumes](/{{page.version}}/docs/user-guide/volumes).
+Another important part of the container environment is the file system that is available to the container.  In Kubernetes, the filesystem is a combination of an [image](/docs/user-guide/images) and one or more [volumes](/docs/user-guide/volumes).
 
 The following sections describe both the cluster information provided to containers, as well as the hooks and life-cycle that allows containers to interact with the management system.
 
@@ -21,7 +21,7 @@ There are two types of information that are available within the container envir
 
 Currently, the Pod name for the pod in which the container is running is set as the hostname of the container, and is accessible through all calls to access the hostname within the container (e.g. the hostname command, or the [gethostname][1] function call in libc), but this is planned to change in the future and should not be used.
 
-The Pod name and namespace are also available as environment variables via the [downward API](/{{page.version}}/docs/user-guide/downward-api).  Additionally, user-defined environment variables from the pod definition, are also available to the container, as are any environment variables specified statically in the Docker image.
+The Pod name and namespace are also available as environment variables via the [downward API](/docs/user-guide/downward-api).  Additionally, user-defined environment variables from the pod definition, are also available to the container, as are any environment variables specified statically in the Docker image.
 
 In the future, we anticipate expanding this information with richer information about the container.  Examples include available memory, number of restarts, and in general any state that you could get from the call to GET /pods on the API server.
 
@@ -52,7 +52,7 @@ This hook is sent immediately after a container is created.  It notifies the co
 
 *PreStop*
 
-This hook is called immediately before a container is terminated. No parameters are passed to the handler. This event handler is blocking, and must complete before the call to delete the container is sent to the Docker daemon.  The SIGTERM notification sent by Docker is also still sent. A more complete description of termination behavior can be found in [Termination of Pods](/{{page.version}}/docs/user-guide/pods/#termination-of-pods).
+This hook is called immediately before a container is terminated. No parameters are passed to the handler. This event handler is blocking, and must complete before the call to delete the container is sent to the Docker daemon.  The SIGTERM notification sent by Docker is also still sent. A more complete description of termination behavior can be found in [Termination of Pods](/docs/user-guide/pods/#termination-of-pods).
 
 ### Hook Handler Execution
 
diff --git a/v1.1/docs/user-guide/containers.md b/docs/user-guide/containers.md
similarity index 100%
rename from v1.1/docs/user-guide/containers.md
rename to docs/user-guide/containers.md
diff --git a/v1.1/docs/user-guide/debugging-services.md b/docs/user-guide/debugging-services.md
similarity index 99%
rename from v1.1/docs/user-guide/debugging-services.md
rename to docs/user-guide/debugging-services.md
index b0aea4739b..d9cea7e5b9 100644
--- a/v1.1/docs/user-guide/debugging-services.md
+++ b/docs/user-guide/debugging-services.md
@@ -494,10 +494,10 @@ misbehaving.  And yet your `Service` is not working.  You should probably let
 us know, so we can help investigate!
 
 Contact us on
-[Slack](/{{page.version}}/docs/troubleshooting/#slack) or
+[Slack](/docs/troubleshooting/#slack) or
 [email](https://groups.google.com/forum/#!forum/google-containers) or
 [GitHub](https://github.com/kubernetes/kubernetes).
 
 ## More information
 
-Visit [troubleshooting document](/{{page.version}}/docs/troubleshooting/) for more information.
\ No newline at end of file
+Visit [troubleshooting document](/docs/troubleshooting/) for more information.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/deploying-applications.md b/docs/user-guide/deploying-applications.md
similarity index 77%
rename from v1.1/docs/user-guide/deploying-applications.md
rename to docs/user-guide/deploying-applications.md
index 6bd8c1cb93..d573c7d3a5 100644
--- a/v1.1/docs/user-guide/deploying-applications.md
+++ b/docs/user-guide/deploying-applications.md
@@ -1,18 +1,18 @@
 ---
 ---
 
-You previously read about how to quickly deploy a simple replicated application using [`kubectl run`](/{{page.version}}/docs/user-guide/quick-start) and how to configure and launch single-run containers using pods ([Configuring containers](/{{page.version}}/docs/user-guide/configuring-containers)). Here you'll use the configuration-based approach to deploy a continuously running, replicated application.
+You previously read about how to quickly deploy a simple replicated application using [`kubectl run`](/docs/user-guide/quick-start) and how to configure and launch single-run containers using pods ([Configuring containers](/docs/user-guide/configuring-containers)). Here you'll use the configuration-based approach to deploy a continuously running, replicated application.
 
 * TOC
 {:toc}
 
 ## Launching a set of replicas using a configuration file
 
-Kubernetes creates and manages sets of replicated containers (actually, replicated [Pods](/{{page.version}}/docs/user-guide/pods)) using [*Replication Controllers*](/{{page.version}}/docs/user-guide/replication-controller).
+Kubernetes creates and manages sets of replicated containers (actually, replicated [Pods](/docs/user-guide/pods)) using [*Replication Controllers*](/docs/user-guide/replication-controller).
 
 A replication controller simply ensures that a specified number of pod "replicas" are running at any one time. If there are too many, it will kill some. If there are too few, it will start more. It's analogous to Google Compute Engine's [Instance Group Manager](https://cloud.google.com/compute/docs/instance-groups/manager/) or AWS's [Auto-scaling Group](http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/AutoScalingGroup) (with no scaling policies).
 
-The replication controller created to run nginx by `kubectl run` in the [Quick start](/{{page.version}}/docs/user-guide/quick-start) could be specified using YAML as follows:
+The replication controller created to run nginx by `kubectl run` in the [Quick start](/docs/user-guide/quick-start) could be specified using YAML as follows:
 
 ```yaml
 apiVersion: v1
@@ -70,7 +70,7 @@ my-nginx-buaiq   1/1       Running   0          51s
 
 ## Deleting replication controllers
 
-When you want to kill your application, delete your replication controller, as in the [Quick start](/{{page.version}}/docs/user-guide/quick-start):
+When you want to kill your application, delete your replication controller, as in the [Quick start](/docs/user-guide/quick-start):
 
 ```shell
 $ kubectl delete rc my-nginx
@@ -83,7 +83,7 @@ If you try to delete the pods before deleting the replication controller, it wil
 
 ## Labels
 
-Kubernetes uses user-defined key-value attributes called [*labels*](/{{page.version}}/docs/user-guide/labels) to categorize and identify sets of resources, such as pods and replication controllers. The example above specified a single label in the pod template, with key `app` and value `nginx`. All pods created carry that label, which can be viewed using `-L`:
+Kubernetes uses user-defined key-value attributes called [*labels*](/docs/user-guide/labels) to categorize and identify sets of resources, such as pods and replication controllers. The example above specified a single label in the pod template, with key `app` and value `nginx`. All pods created carry that label, which can be viewed using `-L`:
 
 ```shell
 $ kubectl get pods -L app
@@ -100,7 +100,7 @@ CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR    REPLICAS   APP
 my-nginx     nginx          nginx      app=nginx   2          nginx
 ```
 
-More importantly, the pod template's labels are used to create a [`selector`](/{{page.version}}/docs/user-guide/labels/#label-selectors) that will match pods carrying those labels. You can see this field by requesting it using the [Go template output format of `kubectl get`](/{{page.version}}/docs/user-guide/kubectl/kubectl_get):
+More importantly, the pod template's labels are used to create a [`selector`](/docs/user-guide/labels/#label-selectors) that will match pods carrying those labels. You can see this field by requesting it using the [Go template output format of `kubectl get`](/docs/user-guide/kubectl/kubectl_get):
 
 ```shell
 $ kubectl get rc my-nginx -o template --template="{{.spec.selector}}"
@@ -111,4 +111,4 @@ You could also specify the `selector` explicitly, such as if you wanted to speci
 
 ## What's next?
 
-[Learn about exposing applications to users and clients, and connecting tiers of your application together.](/{{page.version}}/docs/user-guide/connecting-applications)
\ No newline at end of file
+[Learn about exposing applications to users and clients, and connecting tiers of your application together.](/docs/user-guide/connecting-applications)
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/deployments.md b/docs/user-guide/deployments.md
similarity index 92%
rename from v1.2/docs/user-guide/deployments.md
rename to docs/user-guide/deployments.md
index 014ff690a4..9d24c5c31c 100644
--- a/v1.2/docs/user-guide/deployments.md
+++ b/docs/user-guide/deployments.md
@@ -19,14 +19,14 @@ A typical use case is:
 
 ## Enabling Deployments on kubernetes cluster
 
-Deployments is part of the [`extensions` API Group](/{{page.version}}/docs/api/#api-groups) and is not enabled by default.
+Deployments is part of the [`extensions` API Group](/docs/api/#api-groups) and is not enabled by default.
 Set `--runtime-config=extensions/v1beta1/deployments=true` on API server to
 enable it.
 This can be achieved by exporting `ENABLE_DEPLOYMENTS=true` before running
 `kube-up.sh` script on GCE.
 
 Note that Deployment objects effectively have [API version
-`v1alpha1`](/{{page.version}}/docs/api/)#api-versioning).
+`v1alpha1`](/docs/api/)#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.
@@ -57,7 +57,7 @@ spec:
         - containerPort: 80
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/nginx-deployment.yaml)
+[Download example](/docs/user-guide/nginx-deployment.yaml)
 <!-- END MUNGE: EXAMPLE nginx-deployment.yaml -->
 
 Run the example by downloading the example file and then running this command:
@@ -135,7 +135,7 @@ spec:
         - containerPort: 80
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/new-nginx-deployment.yaml)
+[Download example](/docs/user-guide/new-nginx-deployment.yaml)
 <!-- END MUNGE: EXAMPLE new-nginx-deployment.yaml -->
 
 
@@ -250,16 +250,16 @@ before changing course.
 
 As with all other Kubernetes configs, a Deployment needs `apiVersion`, `kind`, and
 `metadata` fields.  For general information about working with config files,
-see [here](/{{page.version}}/docs/user-guide/deploying-applications), [here](/{{page.version}}/docs/user-guide/configuring-containers), and [here](/{{page.version}}/docs/user-guide/working-with-resources).
+see [here](/docs/user-guide/deploying-applications), [here](/docs/user-guide/configuring-containers), and [here](/docs/user-guide/working-with-resources).
 
-A Deployment also needs a [`.spec` section](/{{page.version}}/docs/devel/api-conventions/#spec-and-status).
+A Deployment also needs a [`.spec` section](/docs/devel/api-conventions/#spec-and-status).
 
 ### Pod Template
 
 The `.spec.template` is the only required field of the `.spec`.
 
-The `.spec.template` is a [pod template](/{{page.version}}/docs/user-guide/replication-controller/#pod-template).  It has exactly
-the same schema as a [pod](/{{page.version}}/docs/user-guide/pods), except it is nested and does not have an
+The `.spec.template` is a [pod template](/docs/user-guide/replication-controller/#pod-template).  It has exactly
+the same schema as a [pod](/docs/user-guide/pods), except it is nested and does not have an
 `apiVersion` or `kind`.
 
 ### Replicas
@@ -347,5 +347,5 @@ Note: This is not implemented yet.
 
 ### kubectl rolling update
 
-[Kubectl rolling update](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update) also updates pods and replication controllers in a similar fashion.
+[Kubectl rolling update](/docs/user-guide/kubectl/kubectl_rolling-update) also updates pods and replication controllers in a similar fashion.
 But deployments is declarative and is server side.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/docker-cli-to-kubectl.md b/docs/user-guide/docker-cli-to-kubectl.md
similarity index 86%
rename from v1.1/docs/user-guide/docker-cli-to-kubectl.md
rename to docs/user-guide/docker-cli-to-kubectl.md
index 71e31f6087..10bc548a4d 100644
--- a/v1.1/docs/user-guide/docker-cli-to-kubectl.md
+++ b/docs/user-guide/docker-cli-to-kubectl.md
@@ -8,7 +8,7 @@ In this doc, we introduce the Kubernetes command line for interacting with the a
 
 #### docker run
 
-How do I run an nginx container and expose it to the world? Checkout [kubectl run](/{{page.version}}/docs/user-guide/kubectl/kubectl_run).
+How do I run an nginx container and expose it to the world? Checkout [kubectl run](/docs/user-guide/kubectl/kubectl_run).
 
 With docker:
 
@@ -30,7 +30,7 @@ replicationcontroller "nginx-app" created
 $ kubectl expose rc nginx-app --port=80 --name=nginx-http
 ```
 
-With kubectl, we create a [replication controller](/{{page.version}}/docs/user-guide/replication-controller) which will make sure that N pods are running nginx (where N is the number of replicas stated in the spec, which defaults to 1). We also create a [service](/{{page.version}}/docs/user-guide/services) with a selector that matches the replication controller's selector. See the [Quick start](/{{page.version}}/docs/user-guide/quick-start) for more information.
+With kubectl, we create a [replication controller](/docs/user-guide/replication-controller) which will make sure that N pods are running nginx (where N is the number of replicas stated in the spec, which defaults to 1). We also create a [service](/docs/user-guide/services) with a selector that matches the replication controller's selector. See the [Quick start](/docs/user-guide/quick-start) for more information.
 
 By default images are run in the background, similar to `docker run -d ...`, if you want to run things in the foreground, use:
 
@@ -45,7 +45,7 @@ To destroy the replication controller (and it's pods)  you need to run `kubectl
 
 #### docker ps
 
-How do I list what is currently running? Checkout [kubectl get](/{{page.version}}/docs/user-guide/kubectl/kubectl_get).
+How do I list what is currently running? Checkout [kubectl get](/docs/user-guide/kubectl/kubectl_get).
 
 With docker:
 
@@ -65,7 +65,7 @@ nginx-app-5jyvm   1/1       Running   0          1h
 
 #### docker attach
 
-How do I attach to a process that is already running in a container?  Checkout [kubectl attach](/{{page.version}}/docs/user-guide/kubectl/kubectl_attach)
+How do I attach to a process that is already running in a container?  Checkout [kubectl attach](/docs/user-guide/kubectl/kubectl_attach)
 
 With docker:
 
@@ -89,7 +89,7 @@ $ kubectl attach -it nginx-app-5jyvm
 
 #### docker exec
 
-How do I execute a command in a container? Checkout [kubectl exec](/{{page.version}}/docs/user-guide/kubectl/kubectl_exec).
+How do I execute a command in a container? Checkout [kubectl exec](/docs/user-guide/kubectl/kubectl_exec).
 
 With docker:
 
@@ -128,11 +128,11 @@ $ kubectl exec -ti nginx-app-5jyvm -- /bin/sh
 # exit
 ```
 
-For more information see [Getting into containers](/{{page.version}}/docs/user-guide/getting-into-containers).
+For more information see [Getting into containers](/docs/user-guide/getting-into-containers).
 
 #### docker logs
 
-How do I follow stdout/stderr of a running process? Checkout [kubectl logs](/{{page.version}}/docs/user-guide/kubectl/kubectl_logs).
+How do I follow stdout/stderr of a running process? Checkout [kubectl logs](/docs/user-guide/kubectl/kubectl_logs).
 
 
 With docker:
@@ -159,11 +159,11 @@ $ kubectl logs --previous nginx-app-zibvs
 10.240.63.110 - - [14/Jul/2015:01:09:02 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.26.0" "-"
 ```
 
-See [Logging](/{{page.version}}/docs/user-guide/logging) for more information.
+See [Logging](/docs/user-guide/logging) for more information.
 
 #### docker stop and docker rm
 
-How do I stop and delete a running process? Checkout [kubectl delete](/{{page.version}}/docs/user-guide/kubectl/kubectl_delete).
+How do I stop and delete a running process? Checkout [kubectl delete](/docs/user-guide/kubectl/kubectl_delete).
 
 With docker
 
@@ -197,11 +197,11 @@ Notice that we don't delete the pod directly. With kubectl we want to delete the
 
 #### docker login
 
-There is no direct analog of `docker login` in kubectl. If you are interested in using Kubernetes with a private registry, see [Using a Private Registry](/{{page.version}}/docs/user-guide/images/#using-a-private-registry).
+There is no direct analog of `docker login` in kubectl. If you are interested in using Kubernetes with a private registry, see [Using a Private Registry](/docs/user-guide/images/#using-a-private-registry).
 
 #### docker version
 
-How do I get the version of my client and server? Checkout [kubectl version](/{{page.version}}/docs/user-guide/kubectl/kubectl_version).
+How do I get the version of my client and server? Checkout [kubectl version](/docs/user-guide/kubectl/kubectl_version).
 
 With docker:
 
@@ -229,7 +229,7 @@ Server Version: version.Info{Major:"0", Minor:"21+", GitVersion:"v0.21.1-411-g32
 
 #### docker info
 
-How do I get miscellaneous info about my environment and configuration? Checkout [kubectl cluster-info](/{{page.version}}/docs/user-guide/kubectl/kubectl_cluster-info).
+How do I get miscellaneous info about my environment and configuration? Checkout [kubectl cluster-info](/docs/user-guide/kubectl/kubectl_cluster-info).
 
 With docker:
 
diff --git a/v1.1/docs/user-guide/downward-api.md b/docs/user-guide/downward-api.md
similarity index 90%
rename from v1.1/docs/user-guide/downward-api.md
rename to docs/user-guide/downward-api.md
index e9e4a320eb..24d34a01e6 100644
--- a/v1.1/docs/user-guide/downward-api.md
+++ b/docs/user-guide/downward-api.md
@@ -76,7 +76,7 @@ spec:
   restartPolicy: Never
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/downward-api/dapi-pod.yaml)
+[Download example](/docs/user-guide/downward-api/dapi-pod.yaml)
 <!-- END MUNGE: EXAMPLE downward-api/dapi-pod.yaml -->
 
 
@@ -86,7 +86,7 @@ Using a similar syntax it's possible to expose pod information to containers usi
 Downward API are dumped to a mounted volume. This is achieved using a `downwardAPI`
 volume type and the different items represent the files to be created. `fieldPath` references the field to be exposed.
 
-Downward API volume permits to store more complex data like [`metadata.labels`](/{{page.version}}/docs/user-guide/labels) and [`metadata.annotations`](/{{page.version}}/docs/user-guide/annotations). Currently key/value pair set fields are saved using `key="value"` format:
+Downward API volume permits to store more complex data like [`metadata.labels`](/docs/user-guide/labels) and [`metadata.annotations`](/docs/user-guide/annotations). Currently key/value pair set fields are saved using `key="value"` format:
 
 ```conf
 key1="value1"
@@ -145,10 +145,10 @@ spec:
               fieldPath: metadata.annotations
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/downward-api/volume/dapi-volume.yaml)
+[Download example](/docs/user-guide/downward-api/volume/dapi-volume.yaml)
 <!-- END MUNGE: EXAMPLE downward-api/volume/dapi-volume.yaml -->
 
 Some more thorough examples:
 
-   * [environment variables](/{{page.version}}/docs/user-guide/environment-guide/)
-   * [downward API](/{{page.version}}/docs/user-guide/downward-api/)
\ No newline at end of file
+   * [environment variables](/docs/user-guide/environment-guide/)
+   * [downward API](/docs/user-guide/downward-api/)
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/downward-api/dapi-pod.yaml b/docs/user-guide/downward-api/dapi-pod.yaml
similarity index 100%
rename from v1.1/docs/user-guide/downward-api/dapi-pod.yaml
rename to docs/user-guide/downward-api/dapi-pod.yaml
diff --git a/v1.2/docs/user-guide/downward-api/index.md b/docs/user-guide/downward-api/index.md
similarity index 75%
rename from v1.2/docs/user-guide/downward-api/index.md
rename to docs/user-guide/downward-api/index.md
index 222bf0acaf..2bb36e7743 100644
--- a/v1.2/docs/user-guide/downward-api/index.md
+++ b/docs/user-guide/downward-api/index.md
@@ -2,20 +2,20 @@
 ---
 
 Following this example, you will create a pod with a container that consumes the pod's name and
-namespace using the [downward API](/{{page.version}}/docs/user-guide/downward-api/).
+namespace using the [downward API](/docs/user-guide/downward-api/).
 
 ## Step Zero: Prerequisites
 
 This example assumes you have a Kubernetes cluster installed and running, and that you have
 installed the `kubectl` command line tool somewhere in your path. Please see the [getting
-started](/{{page.version}}/docs/getting-started-guides/) for installation instructions for your platform.
+started](/docs/getting-started-guides/) for installation instructions for your platform.
 
 ## Step One: Create the pod
 
 Containers consume the downward API using environment variables.  The downward API allows
 containers to be injected with the name and namespace of the pod the container is in.
 
-Use the [`dapi-pod.yaml`](/{{page.version}}/docs/user-guide/downward-api/dapi-pod.yaml) file to create a Pod with a container that consumes the
+Use the [`dapi-pod.yaml`](/docs/user-guide/downward-api/dapi-pod.yaml) file to create a Pod with a container that consumes the
 downward API.
 
 ```shell
diff --git a/v1.1/docs/user-guide/downward-api/volume/dapi-volume.yaml b/docs/user-guide/downward-api/volume/dapi-volume.yaml
similarity index 100%
rename from v1.1/docs/user-guide/downward-api/volume/dapi-volume.yaml
rename to docs/user-guide/downward-api/volume/dapi-volume.yaml
diff --git a/v1.1/docs/user-guide/downward-api/volume/index.md b/docs/user-guide/downward-api/volume/index.md
similarity index 93%
rename from v1.1/docs/user-guide/downward-api/volume/index.md
rename to docs/user-guide/downward-api/volume/index.md
index 1894903d94..bef993725b 100644
--- a/v1.1/docs/user-guide/downward-api/volume/index.md
+++ b/docs/user-guide/downward-api/volume/index.md
@@ -2,7 +2,7 @@
 ---
 
 Following this example, you will create a pod with a downward API volume.
-A downward API volume is a k8s volume plugin with the ability to save some pod information in a plain text file. The pod information can be  for example some [metadata](/{{page.version}}/docs/devel/api-conventions/#metadata).
+A downward API volume is a k8s volume plugin with the ability to save some pod information in a plain text file. The pod information can be  for example some [metadata](/docs/devel/api-conventions/#metadata).
 
 Supported metadata fields:
 
@@ -14,7 +14,7 @@ Supported metadata fields:
 ### Step Zero: Prerequisites
 
 This example assumes you have a Kubernetes cluster installed and running, and the `kubectl`
-command line tool somewhere in your path. Please see the [gettingstarted](/{{page.version}}/docs/getting-started-guides/) for installation instructions for your platform.
+command line tool somewhere in your path. Please see the [gettingstarted](/docs/getting-started-guides/) for installation instructions for your platform.
 
 ### Step One: Create the pod
 
diff --git a/v1.1/docs/user-guide/environment-guide/backend-rc.yaml b/docs/user-guide/environment-guide/backend-rc.yaml
similarity index 100%
rename from v1.1/docs/user-guide/environment-guide/backend-rc.yaml
rename to docs/user-guide/environment-guide/backend-rc.yaml
diff --git a/v1.1/docs/user-guide/environment-guide/backend-srv.yaml b/docs/user-guide/environment-guide/backend-srv.yaml
similarity index 100%
rename from v1.1/docs/user-guide/environment-guide/backend-srv.yaml
rename to docs/user-guide/environment-guide/backend-srv.yaml
diff --git a/v1.1/docs/user-guide/environment-guide/containers/backend/Dockerfile b/docs/user-guide/environment-guide/containers/backend/Dockerfile
similarity index 100%
rename from v1.1/docs/user-guide/environment-guide/containers/backend/Dockerfile
rename to docs/user-guide/environment-guide/containers/backend/Dockerfile
diff --git a/v1.1/docs/user-guide/environment-guide/containers/backend/backend.go b/docs/user-guide/environment-guide/containers/backend/backend.go
similarity index 100%
rename from v1.1/docs/user-guide/environment-guide/containers/backend/backend.go
rename to docs/user-guide/environment-guide/containers/backend/backend.go
diff --git a/v1.1/docs/user-guide/environment-guide/containers/index.md b/docs/user-guide/environment-guide/containers/index.md
similarity index 100%
rename from v1.1/docs/user-guide/environment-guide/containers/index.md
rename to docs/user-guide/environment-guide/containers/index.md
diff --git a/v1.1/docs/user-guide/environment-guide/containers/show/Dockerfile b/docs/user-guide/environment-guide/containers/show/Dockerfile
similarity index 100%
rename from v1.1/docs/user-guide/environment-guide/containers/show/Dockerfile
rename to docs/user-guide/environment-guide/containers/show/Dockerfile
diff --git a/v1.1/docs/user-guide/environment-guide/containers/show/show.go b/docs/user-guide/environment-guide/containers/show/show.go
similarity index 100%
rename from v1.1/docs/user-guide/environment-guide/containers/show/show.go
rename to docs/user-guide/environment-guide/containers/show/show.go
diff --git a/v1.2/docs/user-guide/environment-guide/index.md b/docs/user-guide/environment-guide/index.md
similarity index 84%
rename from v1.2/docs/user-guide/environment-guide/index.md
rename to docs/user-guide/environment-guide/index.md
index 43d1b38acd..ee96df9e04 100644
--- a/v1.2/docs/user-guide/environment-guide/index.md
+++ b/docs/user-guide/environment-guide/index.md
@@ -8,7 +8,7 @@ environment information about itself, and a backend pod that it has
 accessed through the service. The goal is to illuminate the
 environment metadata available to running containers inside the
 Kubernetes cluster. The documentation for the Kubernetes environment
-is [here](/{{page.version}}/docs/user-guide/container-environment).
+is [here](/docs/user-guide/container-environment).
 
 ![Diagram](/images/docs/diagram.png)
 
@@ -17,13 +17,13 @@ is [here](/{{page.version}}/docs/user-guide/container-environment).
 This example assumes that you have a Kubernetes cluster installed and
 running, and that you have installed the `kubectl` command line tool
 somewhere in your path.  Please see the [getting
-started](/{{page.version}}/docs/getting-started-guides/) for installation instructions
+started](/docs/getting-started-guides/) for installation instructions
 for your platform.
 
 ## Optional: Build your own containers
 
 The code for the containers is under
-[containers/](/{{page.version}}/docs/user-guide/environment-guide/containers/)
+[containers/](/docs/user-guide/environment-guide/containers/)
 
 ## Get everything running
 
@@ -70,9 +70,9 @@ Backend Namespace: default
 
 First the frontend pod's information is printed. The pod name and
 [namespace](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/namespaces.md) are retrieved from the
-[Downward API](/{{page.version}}/docs/user-guide/downward-api). Next, `USER_VAR` is the name of
+[Downward API](/docs/user-guide/downward-api). Next, `USER_VAR` is the name of
 an environment variable set in the [pod
-definition](/{{page.version}}/docs/user-guide/environment-guide/show-rc.yaml). Then, the dynamic Kubernetes environment
+definition](/docs/user-guide/environment-guide/show-rc.yaml). Then, the dynamic Kubernetes environment
 variables are scanned and printed. These are used to find the backend
 service, named `backend-srv`. Finally, the frontend pod queries the
 backend service and prints the information returned. Again the backend
diff --git a/v1.1/docs/user-guide/environment-guide/show-rc.yaml b/docs/user-guide/environment-guide/show-rc.yaml
similarity index 100%
rename from v1.1/docs/user-guide/environment-guide/show-rc.yaml
rename to docs/user-guide/environment-guide/show-rc.yaml
diff --git a/v1.1/docs/user-guide/environment-guide/show-srv.yaml b/docs/user-guide/environment-guide/show-srv.yaml
similarity index 100%
rename from v1.1/docs/user-guide/environment-guide/show-srv.yaml
rename to docs/user-guide/environment-guide/show-srv.yaml
diff --git a/v1.1/docs/user-guide/getting-into-containers.md b/docs/user-guide/getting-into-containers.md
similarity index 87%
rename from v1.1/docs/user-guide/getting-into-containers.md
rename to docs/user-guide/getting-into-containers.md
index 03b0109a2c..94e25f580c 100644
--- a/v1.1/docs/user-guide/getting-into-containers.md
+++ b/docs/user-guide/getting-into-containers.md
@@ -5,7 +5,7 @@ Developers can use `kubectl exec` to run commands in a container. This guide dem
 
 ## Using kubectl exec to check the environment variables of a container
 
-Kubernetes exposes [services](/{{page.version}}/docs/user-guide/services/#environment-variables) through environment variables. It is convenient to check these environment variables using `kubectl exec`.
+Kubernetes exposes [services](/docs/user-guide/services/#environment-variables) through environment variables. It is convenient to check these environment variables using `kubectl exec`.
 
 We first create a pod and a service,
 
diff --git a/v1.1/docs/user-guide/horizontal-pod-autoscaler.md b/docs/user-guide/horizontal-pod-autoscaler.md
similarity index 90%
rename from v1.1/docs/user-guide/horizontal-pod-autoscaler.md
rename to docs/user-guide/horizontal-pod-autoscaler.md
index 1ad4cc651a..0a1fbca549 100644
--- a/v1.1/docs/user-guide/horizontal-pod-autoscaler.md
+++ b/docs/user-guide/horizontal-pod-autoscaler.md
@@ -7,7 +7,7 @@ This document describes the current state of Horizontal Pod Autoscaler in Kubern
 
 Horizontal pod autoscaling allows the number of pods in a replication controller or deployment
 to scale automatically based on observed CPU utilization.
-It is a [beta](/{{page.version}}/docs/api/)#api-versioning) feature in Kubernetes 1.1.
+It is a [beta](/docs/api/)#api-versioning) feature in Kubernetes 1.1.
 
 The autoscaler is implemented as a Kubernetes API resource and a controller.
 The resource describes behavior of the controller.
@@ -40,7 +40,7 @@ More details on scale sub-resource can be found [here](https://github.com/kubern
 
 ## API Object
 
-Horizontal pod autoscaler is a top-level resource in the Kubernetes REST API (currently in [beta](/{{page.version}}/docs/api/)#api-versioning)).
+Horizontal pod autoscaler is a top-level resource in the Kubernetes REST API (currently in [beta](/docs/api/)#api-versioning)).
 More details about the API object can be found at
 [HorizontalPodAutoscaler Object](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/horizontal-pod-autoscaler.md#horizontalpodautoscaler-object).
 
@@ -55,7 +55,7 @@ In addition, there is a special `kubectl autoscale` command that allows for easy
 For instance, executing `kubectl autoscale rc foo --min=2 --max=5 --cpu-percent=80`
 will create an autoscaler for replication controller *foo*, with target CPU utilization set to `80%`
 and the number of replicas between 2 and 5.
-The detailed documentation of `kubectl autoscale` can be found [here](/{{page.version}}/docs/user-guide/kubectl/kubectl_autoscale).
+The detailed documentation of `kubectl autoscale` can be found [here](/docs/user-guide/kubectl/kubectl_autoscale).
 
 
 ## Autoscaling during rolling update
@@ -74,5 +74,5 @@ the horizontal pod autoscaler will not be bound to the new replication controlle
 ## Further reading
 
 * Design documentation: [Horizontal Pod Autoscaling](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/horizontal-pod-autoscaler.md).
-* Manual of autoscale command in kubectl: [kubectl autoscale](/{{page.version}}/docs/user-guide/kubectl/kubectl_autoscale).
-* Usage example of [Horizontal Pod Autoscaler](/{{page.version}}/docs/user-guide/horizontal-pod-autoscaling/).
\ No newline at end of file
+* Manual of autoscale command in kubectl: [kubectl autoscale](/docs/user-guide/kubectl/kubectl_autoscale).
+* Usage example of [Horizontal Pod Autoscaler](/docs/user-guide/horizontal-pod-autoscaling/).
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml b/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml
similarity index 100%
rename from v1.1/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml
rename to docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml
diff --git a/v1.1/docs/user-guide/horizontal-pod-autoscaling/image/Dockerfile b/docs/user-guide/horizontal-pod-autoscaling/image/Dockerfile
similarity index 100%
rename from v1.1/docs/user-guide/horizontal-pod-autoscaling/image/Dockerfile
rename to docs/user-guide/horizontal-pod-autoscaling/image/Dockerfile
diff --git a/v1.1/docs/user-guide/horizontal-pod-autoscaling/image/index.php b/docs/user-guide/horizontal-pod-autoscaling/image/index.php
similarity index 100%
rename from v1.1/docs/user-guide/horizontal-pod-autoscaling/image/index.php
rename to docs/user-guide/horizontal-pod-autoscaling/image/index.php
diff --git a/v1.2/docs/user-guide/horizontal-pod-autoscaling/index.md b/docs/user-guide/horizontal-pod-autoscaling/index.md
similarity index 91%
rename from v1.2/docs/user-guide/horizontal-pod-autoscaling/index.md
rename to docs/user-guide/horizontal-pod-autoscaling/index.md
index 25747788de..074304194b 100644
--- a/v1.2/docs/user-guide/horizontal-pod-autoscaling/index.md
+++ b/docs/user-guide/horizontal-pod-autoscaling/index.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-Horizontal pod autoscaling is a [beta](/{{page.version}}/docs/api/#api-versioning) feature in Kubernetes 1.1.
+Horizontal pod autoscaling is a [beta](/docs/api/#api-versioning) feature in Kubernetes 1.1.
 It allows the number of pods in a replication controller or deployment to scale automatically based on observed CPU usage.
 In the future also other metrics will be supported.
 
@@ -12,7 +12,7 @@ In this document we explain how this feature works by walking you through an exa
 This example requires a running Kubernetes cluster and kubectl in the version at least 1.1.
 [Heapster](https://github.com/kubernetes/heapster) monitoring needs to be deployed in the cluster
 as horizontal pod autoscaler uses it to collect metrics
-(if you followed [getting started on GCE guide](/{{page.version}}/docs/getting-started-guides/gce),
+(if you followed [getting started on GCE guide](/docs/getting-started-guides/gce),
 heapster monitoring will be turned-on by default).
 
 
@@ -20,7 +20,7 @@ heapster monitoring will be turned-on by default).
 
 To demonstrate horizontal pod autoscaler we will use a custom docker image based on php-apache server.
 The image can be found [here](https://releases.k8s.io/{{page.githubbranch}}/docs/user-guide/horizontal-pod-autoscaling/image).
-It defines [index.php](/{{page.version}}/docs/user-guide/horizontal-pod-autoscaling/image/index.php) page which performs some CPU intensive computations.
+It defines [index.php](/docs/user-guide/horizontal-pod-autoscaling/image/index.php) page which performs some CPU intensive computations.
 
 First, we will start a replication controller running the image and expose it as an external service:
 
@@ -69,7 +69,7 @@ OK!
 ## Step Two: Create horizontal pod autoscaler
 
 Now that the server is running, we will create a horizontal pod autoscaler for it.
-To create it, we will use the [hpa-php-apache.yaml](/{{page.version}}/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml) file, which looks like this:
+To create it, we will use the [hpa-php-apache.yaml](/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml) file, which looks like this:
 
 ```yaml
 apiVersion: extensions/v1beta1
@@ -103,7 +103,7 @@ horizontalpodautoscaler "php-apache" created
 ```
 
 Alternatively, we can create the autoscaler using [kubectl autoscale](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/user-guide/kubectl/kubectl_autoscale.md).
-The following command will create the equivalent autoscaler as defined in the [hpa-php-apache.yaml](/{{page.version}}/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml) file:
+The following command will create the equivalent autoscaler as defined in the [hpa-php-apache.yaml](/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml) file:
 
 ```shell
 $ kubectl autoscale rc php-apache --cpu-percent=50 --min=1 --max=10
diff --git a/v1.1/docs/user-guide/identifiers.md b/docs/user-guide/identifiers.md
similarity index 90%
rename from v1.1/docs/user-guide/identifiers.md
rename to docs/user-guide/identifiers.md
index 44d820c6ab..b5fd025e29 100644
--- a/v1.1/docs/user-guide/identifiers.md
+++ b/docs/user-guide/identifiers.md
@@ -3,7 +3,7 @@
 
 All objects in the Kubernetes REST API are unambiguously identified by a Name and a UID.
 
-For non-unique user-provided attributes, Kubernetes provides [labels](/{{page.version}}/docs/user-guide/labels) and [annotations](/{{page.version}}/docs/user-guide/annotations).
+For non-unique user-provided attributes, Kubernetes provides [labels](/docs/user-guide/labels) and [annotations](/docs/user-guide/annotations).
 
 ## Names
 
diff --git a/v1.1/docs/user-guide/images.md b/docs/user-guide/images.md
similarity index 98%
rename from v1.1/docs/user-guide/images.md
rename to docs/user-guide/images.md
index 05020328f1..48832d4f84 100644
--- a/v1.1/docs/user-guide/images.md
+++ b/docs/user-guide/images.md
@@ -146,7 +146,7 @@ where node creation is automated.
 Kubernetes supports specifying registry keys on a pod.
 
 First, create a `.dockercfg`, such as running `docker login <registry.domain>`.
-Then put the resulting `.dockercfg` file into a [secret resource](/{{page.version}}/docs/user-guide/secrets).  For example:
+Then put the resulting `.dockercfg` file into a [secret resource](/docs/user-guide/secrets).  For example:
 
 ```shell
 $ docker login
@@ -201,7 +201,7 @@ spec:
 
 This needs to be done for each pod that is using a private registry.
 However, setting of this field can be automated by setting the imagePullSecrets
-in a [serviceAccount](/{{page.version}}/docs/user-guide/service-accounts) resource.
+in a [serviceAccount](/docs/user-guide/service-accounts) resource.
 
 Currently, all pods will potentially have read access to any images which were
 pulled using imagePullSecrets.  That is, imagePullSecrets does *NOT* protect your
diff --git a/docs/user-guide/index.md b/docs/user-guide/index.md
new file mode 100644
index 0000000000..9dbabb5667
--- /dev/null
+++ b/docs/user-guide/index.md
@@ -0,0 +1,90 @@
+---
+---
+
+* TOC
+{:toc}
+
+The user guide is intended for anyone who wants to run programs and services on an existing Kubernetes cluster.  Setup and administration of a Kubernetes cluster is described in the [Cluster Admin Guide](/docs/admin/). The [Developer Guide](/docs/devel/) is for anyone wanting to either write code which directly accesses the Kubernetes API, or to contribute directly to the Kubernetes project.
+
+Please ensure you have completed the [prerequisites for running examples from the user guide](/docs/user-guide/prereqs).
+
+## Quick walkthrough
+
+1. [Kubernetes 101](/docs/user-guide/walkthrough/)
+1. [Kubernetes 201](/docs/user-guide/walkthrough/k8s201)
+
+## Thorough walkthrough
+
+If you don't have much familiarity with Kubernetes, we recommend you read the following sections in order:
+
+1. [Quick start: launch and expose an application](/docs/user-guide/quick-start)
+1. [Configuring and launching containers: configuring common container parameters](/docs/user-guide/configuring-containers)
+1. [Deploying continuously running applications](/docs/user-guide/deploying-applications)
+1. [Connecting applications: exposing applications to clients and users](/docs/user-guide/connecting-applications)
+1. [Working with containers in production](/docs/user-guide/production-pods)
+1. [Managing deployments](/docs/user-guide/managing-deployments)
+1. [Application introspection and debugging](/docs/user-guide/introspection-and-debugging)
+    1. [Using the Kubernetes web user interface](/docs/user-guide/ui)
+    1. [Logging](/docs/user-guide/logging)
+    1. [Monitoring](/docs/user-guide/monitoring)
+    1. [Getting into containers via `exec`](/docs/user-guide/getting-into-containers)
+    1. [Connecting to containers via proxies](/docs/user-guide/connecting-to-applications-proxy)
+    1. [Connecting to containers via port forwarding](/docs/user-guide/connecting-to-applications-port-forward)
+
+## Concept guide
+
+[**Overview**](/docs/user-guide/overview)
+: A brief overview of Kubernetes concepts.
+
+[**Cluster**](/docs/admin/)
+: A cluster is a set of physical or virtual machines and other infrastructure resources used by Kubernetes to run your applications.
+
+[**Node**](/docs/admin/node)
+: A node is a physical or virtual machine running Kubernetes, onto which pods can be scheduled.
+
+[**Pod**](/docs/user-guide/pods)
+: A pod is a co-located group of containers and volumes.
+
+[**Label**](/docs/user-guide/labels)
+: A label is a key/value pair that is attached to a resource, such as a pod, to convey a user-defined identifying attribute. Labels can be used to organize and to select subsets of resources.
+
+[**Selector**](/docs/user-guide/labels/#label-selectors)
+: A selector is an expression that matches labels in order to identify related resources, such as which pods are targeted by a load-balanced service.
+
+[**Replication Controller**](/docs/user-guide/replication-controller)
+: A replication controller ensures that a specified number of pod replicas are running at any one time. It both allows for easy scaling of replicated systems and handles re-creation of a pod when the machine it is on reboots or otherwise fails.
+
+[**Service**](/docs/user-guide/services)
+: A service defines a set of pods and a means by which to access them, such as single stable IP address and corresponding DNS name.
+
+[**Volume**](/docs/user-guide/volumes)
+: A volume is a directory, possibly with some data in it, which is accessible to a Container as part of its filesystem.  Kubernetes volumes build upon [Docker Volumes](https://docs.docker.com/userguide/dockervolumes/), adding provisioning of the volume directory and/or device.
+
+[**Secret**](/docs/user-guide/secrets)
+: A secret stores sensitive data, such as authentication tokens, which can be made available to containers upon request.
+
+[**Name**](/docs/user-guide/identifiers)
+: A user- or client-provided name for a resource.
+
+[**Namespace**](/docs/user-guide/namespaces)
+: A namespace is like a prefix to the name of a resource. Namespaces help different projects, teams, or customers to share a cluster, such as by preventing name collisions between unrelated teams.
+
+[**Annotation**](/docs/user-guide/annotations)
+: A key/value pair that can hold larger (compared to a label), and possibly not human-readable, data, intended to store non-identifying auxiliary data, especially data manipulated by tools and system extensions.  Efficient filtering by annotation values is not supported.
+
+## Further reading
+
+* API resources
+  * [Working with resources](/docs/user-guide/working-with-resources)
+
+* Pods and containers
+  * [Pod lifecycle and restart policies](/docs/user-guide/pod-states)
+  * [Lifecycle hooks](/docs/user-guide/container-environment)
+  * [Compute resources, such as cpu and memory](/docs/user-guide/compute-resources)
+  * [Specifying commands and requesting capabilities](/docs/user-guide/containers)
+  * [Downward API: accessing system configuration from a pod](/docs/user-guide/downward-api)
+  * [Images and registries](/docs/user-guide/images)
+  * [Migrating from docker-cli to kubectl](/docs/user-guide/docker-cli-to-kubectl)
+  * [Tips and tricks when working with config](/docs/user-guide/config-best-practices)
+  * [Assign pods to selected nodes](/docs/user-guide/node-selection/)
+  * [Perform a rolling update on a running group of pods](/docs/user-guide/update-demo/)
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/ingress.md b/docs/user-guide/ingress.md
similarity index 93%
rename from v1.1/docs/user-guide/ingress.md
rename to docs/user-guide/ingress.md
index b84db5c494..cc47e0c6fb 100644
--- a/v1.1/docs/user-guide/ingress.md
+++ b/docs/user-guide/ingress.md
@@ -67,13 +67,13 @@ rules:
 
 *POSTing this to the API server will have no effect if you have not configured an [Ingress controller](#ingress-controllers).*
 
-__Lines 1-4__: As with all other Kubernetes config, an Ingress needs `apiVersion`, `kind`, and `metadata` fields.  For general information about working with config files, see [here](/{{page.version}}/docs/user-guide/simple-yaml), [here](/{{page.version}}/docs/user-guide/configuring-containers), and [here](/{{page.version}}/docs/user-guide/working-with-resources).
+__Lines 1-4__: As with all other Kubernetes config, an Ingress needs `apiVersion`, `kind`, and `metadata` fields.  For general information about working with config files, see [here](/docs/user-guide/simple-yaml), [here](/docs/user-guide/configuring-containers), and [here](/docs/user-guide/working-with-resources).
 
-__Lines 5-7__: Ingress [spec](/{{page.version}}/docs/devel/api-conventions/#spec-and-status) has all the information needed to configure a loadbalancer or proxy server. Most importantly, it contains a list of rules matched against all incoming requests. Currently the Ingress resource only supports http rules.
+__Lines 5-7__: Ingress [spec](/docs/devel/api-conventions/#spec-and-status) has all the information needed to configure a loadbalancer or proxy server. Most importantly, it contains a list of rules matched against all incoming requests. Currently the Ingress resource only supports http rules.
 
 __Lines 8-9__: Each http rule contains the following information: A host (eg: foo.bar.com, defaults to * in this example), a list of paths (eg: /testpath) each of which has an associated backend (test:80). Both the host and path must match the content of an incoming request before the loadbalancer directs traffic to the backend.
 
-__Lines 10-12__: A backend is a service:port combination as described in the [services doc](/{{page.version}}/docs/user-guide/services). Ingress traffic is typically sent directly to the endpoints matching a backend.
+__Lines 10-12__: A backend is a service:port combination as described in the [services doc](/docs/user-guide/services). Ingress traffic is typically sent directly to the endpoints matching a backend.
 
 __Global Parameters__: For the sake of simplicity the example Ingress has no global parameters, see the [api-reference](https://releases.k8s.io/{{page.githubbranch}}/pkg/apis/extensions/v1beta1/types.go) for a full definition of the resource. One can specify a global default backend in the absence of which requests that don't match a path in the spec are sent to the default backend of the Ingress controller. Though the Ingress resource doesn't support HTTPS yet, security configs would also be global.
 
@@ -100,7 +100,7 @@ spec:
     servicePort: 80
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/ingress.yaml)
+[Download example](/docs/user-guide/ingress.yaml)
 <!-- END MUNGE: EXAMPLE ingress.yaml -->
 
 If you create it using `kubectl -f` you should see:
diff --git a/v1.1/docs/user-guide/ingress.yaml b/docs/user-guide/ingress.yaml
similarity index 100%
rename from v1.1/docs/user-guide/ingress.yaml
rename to docs/user-guide/ingress.yaml
diff --git a/v1.1/docs/user-guide/introspection-and-debugging.md b/docs/user-guide/introspection-and-debugging.md
similarity index 96%
rename from v1.1/docs/user-guide/introspection-and-debugging.md
rename to docs/user-guide/introspection-and-debugging.md
index 3933342eaf..2bcbb00b51 100644
--- a/v1.1/docs/user-guide/introspection-and-debugging.md
+++ b/docs/user-guide/introspection-and-debugging.md
@@ -308,9 +308,9 @@ status:
 
 Learn about additional debugging tools, including:
 
-* [Logging](/{{page.version}}/docs/user-guide/logging)
-* [Monitoring](/{{page.version}}/docs/user-guide/monitoring)
-* [Getting into containers via `exec`](/{{page.version}}/docs/user-guide/getting-into-containers)
-* [Connecting to containers via proxies](/{{page.version}}/docs/user-guide/connecting-to-applications-proxy)
-* [Connecting to containers via port forwarding](/{{page.version}}/docs/user-guide/connecting-to-applications-port-forward)
+* [Logging](/docs/user-guide/logging)
+* [Monitoring](/docs/user-guide/monitoring)
+* [Getting into containers via `exec`](/docs/user-guide/getting-into-containers)
+* [Connecting to containers via proxies](/docs/user-guide/connecting-to-applications-proxy)
+* [Connecting to containers via port forwarding](/docs/user-guide/connecting-to-applications-port-forward)
 
diff --git a/v1.1/docs/user-guide/job.yaml b/docs/user-guide/job.yaml
similarity index 100%
rename from v1.1/docs/user-guide/job.yaml
rename to docs/user-guide/job.yaml
diff --git a/v1.1/docs/user-guide/jobs.md b/docs/user-guide/jobs.md
similarity index 87%
rename from v1.1/docs/user-guide/jobs.md
rename to docs/user-guide/jobs.md
index 5363e492d4..bad1e8dd3c 100644
--- a/v1.1/docs/user-guide/jobs.md
+++ b/docs/user-guide/jobs.md
@@ -42,7 +42,7 @@ spec:
       restartPolicy: Never
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/job.yaml)
+[Download example](/docs/user-guide/job.yaml)
 <!-- END MUNGE: EXAMPLE job.yaml -->
 
 Run the example job by downloading the example file and then running this command:
@@ -93,23 +93,23 @@ $ kubectl logs pi-aiw0a
 ## Writing a Job Spec
 
 As with all other Kubernetes config, a Job needs `apiVersion`, `kind`, and `metadata` fields.  For
-general information about working with config files, see [here](/{{page.version}}/docs/user-guide/simple-yaml),
-[here](/{{page.version}}/docs/user-guide/configuring-containers), and [here](working-with-resources).
+general information about working with config files, see [here](/docs/user-guide/simple-yaml),
+[here](/docs/user-guide/configuring-containers), and [here](working-with-resources).
 
-A Job also needs a [`.spec` section](/{{page.version}}/docs/devel/api-conventions/#spec-and-status).
+A Job also needs a [`.spec` section](/docs/devel/api-conventions/#spec-and-status).
 
 ### Pod Template
 
 The `.spec.template` is the only required field of the `.spec`.
 
-The `.spec.template` is a [pod template](/{{page.version}}/docs/user-guide/replication-controller/#pod-template).  It has exactly
-the same schema as a [pod](/{{page.version}}/docs/user-guide/pods), except it is nested and does not have an `apiVersion` or
+The `.spec.template` is a [pod template](/docs/user-guide/replication-controller/#pod-template).  It has exactly
+the same schema as a [pod](/docs/user-guide/pods), except it is nested and does not have an `apiVersion` or
 `kind`.
 
 In addition to required fields for a Pod, a pod template in a job must specify appropriate
 lables (see [pod selector](#pod-selector) and an appropriate restart policy.
 
-Only a [`RestartPolicy`](/{{page.version}}/docs/user-guide/pod-states) equal to `Never` or `OnFailure` are allowed.
+Only a [`RestartPolicy`](/docs/user-guide/pod-states) equal to `Never` or `OnFailure` are allowed.
 
 ### Pod Selector
 
@@ -117,7 +117,7 @@ The `.spec.selector` field is a label query over a set of pods.
 
 The `spec.selector` is an object consisting of two fields:
 
-* `matchLabels` - works the same as the `.spec.selector` of a [ReplicationController](/{{page.version}}/docs/user-guide/replication-controller)
+* `matchLabels` - works the same as the `.spec.selector` of a [ReplicationController](/docs/user-guide/replication-controller)
 * `matchExpressions` - allows to build more sophisticated selectors by specyfing key,
   list of values and an operator that relates the key and values.
 
@@ -135,7 +135,7 @@ think that those pods were created by it.  Kubernetes will not stop you from doi
 By default, a Job is complete when one Pod runs to successful completion.  You can also specify that
 this needs to happen multiple times by specifying `.spec.completions` with a value greater than 1.
 When multiple completions are requested, each Pod created by the Job controller has an identical
-[`spec`](/{{page.version}}/docs/devel/api-conventions/#spec-and-status).  In particular, all pods will have
+[`spec`](/docs/devel/api-conventions/#spec-and-status).  In particular, all pods will have
 the same command line and the same image, the same volumes, and mostly the same environment
 variables.  It is up to the user to arrange for the pods to do work on different things.  For
 example, the pods might all access a shared work queue service to acquire work units.
@@ -161,7 +161,7 @@ a non-zero exit code, or the Container was killed for exceeding a memory limit,
 happens, and the `.spec.template.containers[].restartPolicy = "OnFailure"`, then the Pod stays
 on the node, but the Container is re-run.  Therefore, your program needs to handle the the case when it is
 restarted locally, or else specify `.spec.template.containers[].restartPolicy = "Never"`.
-See [pods-states](/{{page.version}}/docs/user-guide/pod-states) for more information on `restartPolicy`.
+See [pods-states](/docs/user-guide/pod-states) for more information on `restartPolicy`.
 
 An entire Pod can also fail, for a number of reasons, such as when the pod is kicked off the node
 (node is upgraded, rebooted, delelted, etc.), or if a container of the Pod fails and the
@@ -188,19 +188,19 @@ requires only a single pod.
 
 ### Replication Controller
 
-Jobs are complementary to [Replication Controllers](/{{page.version}}/docs/user-guide/replication-controller).
+Jobs are complementary to [Replication Controllers](/docs/user-guide/replication-controller).
 A Replication Controller manages pods which are not expected to terminate (e.g. web servers), and a Job
 manages pods that are expected to terminate (e.g. batch jobs).
 
-As discussed in [life of a pod](/{{page.version}}/docs/user-guide/pod-states), `Job` is *only* appropriate for pods with
+As discussed in [life of a pod](/docs/user-guide/pod-states), `Job` is *only* appropriate for pods with
 `RestartPolicy` equal to `OnFailure` or `Never`.  (Note: If `RestartPolicy` is not set, the default
 value is `Always`.)
 
 ## Caveats
 
-Job objects are in the [`extensions` API Group](/{{page.version}}/docs/api/#api-groups).
+Job objects are in the [`extensions` API Group](/docs/api/#api-groups).
 
-Job objects have [API version `v1beta1`](/{{page.version}}/docs/api/)#api-versioning).  Beta objects may
+Job objects have [API version `v1beta1`](/docs/api/)#api-versioning).  Beta objects may
 undergo changes to their schema and/or semantics in future software releases, but
 similar functionality will be supported.
 
diff --git a/v1.1/docs/user-guide/jsonpath.md b/docs/user-guide/jsonpath.md
similarity index 100%
rename from v1.1/docs/user-guide/jsonpath.md
rename to docs/user-guide/jsonpath.md
diff --git a/v1.1/docs/user-guide/known-issues.md b/docs/user-guide/known-issues.md
similarity index 100%
rename from v1.1/docs/user-guide/known-issues.md
rename to docs/user-guide/known-issues.md
diff --git a/v1.2/docs/user-guide/kubeconfig-file.md b/docs/user-guide/kubeconfig-file.md
similarity index 97%
rename from v1.2/docs/user-guide/kubeconfig-file.md
rename to docs/user-guide/kubeconfig-file.md
index 18441725f0..9e2df71e67 100644
--- a/v1.2/docs/user-guide/kubeconfig-file.md
+++ b/docs/user-guide/kubeconfig-file.md
@@ -122,7 +122,7 @@ The rules for loading and merging the kubeconfig files are straightforward, but
 ## Manipulation of kubeconfig via `kubectl config <subcommand>`
 
 In order to more easily manipulate kubeconfig files, there are a series of subcommands to `kubectl config` to help.
-See [kubectl/kubectl_config.md](/{{page.version}}/docs/user-guide/kubectl/kubectl_config) for help.
+See [kubectl/kubectl_config.md](/docs/user-guide/kubectl/kubectl_config) for help.
 
 ### Example
 
diff --git a/v1.2/docs/user-guide/kubectl-overview.md b/docs/user-guide/kubectl-overview.md
similarity index 93%
rename from v1.2/docs/user-guide/kubectl-overview.md
rename to docs/user-guide/kubectl-overview.md
index 9e0d94562a..9435504461 100644
--- a/v1.2/docs/user-guide/kubectl-overview.md
+++ b/docs/user-guide/kubectl-overview.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-Use this overview of the `kubectl` command line interface to help you start running commands against Kubernetes clusters. This overview quickly covers `kubectl` syntax, describes the command operations, and provides common examples. For details about each command, including all the supported flags and subcommands, see the [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) reference documentation.
+Use this overview of the `kubectl` command line interface to help you start running commands against Kubernetes clusters. This overview quickly covers `kubectl` syntax, describes the command operations, and provides common examples. For details about each command, including all the supported flags and subcommands, see the [kubectl](/docs/user-guide/kubectl/kubectl) reference documentation.
 
 TODO: Auto-generate this file to ensure it's always in sync with any `kubectl` changes, see [#14177](http://pr.k8s.io/14177).
 
@@ -34,7 +34,7 @@ When performing an operation on multiple resources, you can specify each resourc
         * To specify multiple resource types individually: `TYPE1/name1 TYPE1/name2 TYPE2/name3 TYPE<#>/name<#>`<br/>
         Example: `$ kubectl get pod/example-pod1 replicationcontroller/example-rc1`
    * To specify resources with one or more files: `-f file1 -f file2 -f file<#>`
-	 [Use YAML rather than JSON](/{{page.version}}/docs/user-guide/config-best-practices) since YAML tends to be more user-friendly, especially for configuration files.<br/>
+	 [Use YAML rather than JSON](/docs/user-guide/config-best-practices) since YAML tends to be more user-friendly, especially for configuration files.<br/>
      Example: `$ kubectl get pod -f ./pod.yaml`
 * `flags`: Specifies optional flags. For example, you can use the `-s` or `--server` flags to specify the address and port of the Kubernetes API server.
 
@@ -74,7 +74,7 @@ Operation       | Syntax	|       Description
 `stop`		| `kubectl stop` | Deprecated: Instead, see `kubectl delete`.
 `version`		| `kubectl version [--client] [flags]` | Display the Kubernetes version running on the client and server.
 
-Remember: For more about command operations, see the [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) reference documentation.
+Remember: For more about command operations, see the [kubectl](/docs/user-guide/kubectl/kubectl) reference documentation.
 
 ## Resource types
 
@@ -101,7 +101,7 @@ Resource type	| Abbreviated alias
 
 ## Output options
 
-Use the following sections for information about how you can format or sort the output of certain commands. For details about which commands support the various output options, see the [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) reference documentation.
+Use the following sections for information about how you can format or sort the output of certain commands. For details about which commands support the various output options, see the [kubectl](/docs/user-guide/kubectl/kubectl) reference documentation.
 
 ### Formatting output
 
@@ -120,8 +120,8 @@ Output format | Description
 `-o=custom-columns=<spec>` | Print a table using a comma separated list of [custom columns](#custom-columns).
 `-o=custom-columns-file=<filename>` | Print a table using the [custom columns](#custom-columns) template in the `<filename>` file.
 `-o=json`     | Output a JSON formatted API object.
-`-o=jsonpath=<template>` | Print the fields defined in a [jsonpath](/{{page.version}}/docs/user-guide/jsonpath) expression.
-`-o=jsonpath-file=<filename>` | Print the fields defined by the [jsonpath](/{{page.version}}/docs/user-guide/jsonpath) expression in the `<filename>` file.
+`-o=jsonpath=<template>` | Print the fields defined in a [jsonpath](/docs/user-guide/jsonpath) expression.
+`-o=jsonpath-file=<filename>` | Print the fields defined by the [jsonpath](/docs/user-guide/jsonpath) expression in the `<filename>` file.
 `-o=name`     | Print only the resource name and nothing else.
 `-o=wide`     | Output in the plain-text format with any additional information. For pods, the node name is included.
 `-o=yaml`     | Output a YAML formatted API object.
@@ -132,7 +132,7 @@ In this example, the following command outputs the details for a single pod as a
 
 `$ kubectl get pod web-pod-13je7 -o=yaml`
 
-Remember: See the [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) reference documentation for details about which output format is supported by each command.
+Remember: See the [kubectl](/docs/user-guide/kubectl/kubectl) reference documentation for details about which output format is supported by each command.
 
 #### Custom columns
 
@@ -167,7 +167,7 @@ submit-queue   610995
 
 ### Sorting list objects
 
-To output objects to a sorted list in your terminal window, you can add the `--sort-by` flag to a supported `kubectl` command. Sort your objects by specifying any numeric or string field with the `--sort-by` flag. To specify a field, use a [jsonpath](/{{page.version}}/docs/user-guide/jsonpath) expression.
+To output objects to a sorted list in your terminal window, you can add the `--sort-by` flag to a supported `kubectl` command. Sort your objects by specifying any numeric or string field with the `--sort-by` flag. To specify a field, use a [jsonpath](/docs/user-guide/jsonpath) expression.
 
 #### Syntax
 
@@ -267,4 +267,4 @@ $ kubectl logs -f <pod-name>
 
 ## Next steps
 
-Start using the [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) commands.
\ No newline at end of file
+Start using the [kubectl](/docs/user-guide/kubectl/kubectl) commands.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/kubectl/.files_generated b/docs/user-guide/kubectl/.files_generated
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/.files_generated
rename to docs/user-guide/kubectl/.files_generated
diff --git a/v1.1/docs/user-guide/kubectl/kubectl.md b/docs/user-guide/kubectl/kubectl.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl.md
rename to docs/user-guide/kubectl/kubectl.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_annotate.md b/docs/user-guide/kubectl/kubectl_annotate.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_annotate.md
rename to docs/user-guide/kubectl/kubectl_annotate.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_api-versions.md b/docs/user-guide/kubectl/kubectl_api-versions.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_api-versions.md
rename to docs/user-guide/kubectl/kubectl_api-versions.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_apply.md b/docs/user-guide/kubectl/kubectl_apply.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_apply.md
rename to docs/user-guide/kubectl/kubectl_apply.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_attach.md b/docs/user-guide/kubectl/kubectl_attach.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_attach.md
rename to docs/user-guide/kubectl/kubectl_attach.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_autoscale.md b/docs/user-guide/kubectl/kubectl_autoscale.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_autoscale.md
rename to docs/user-guide/kubectl/kubectl_autoscale.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_cluster-info.md b/docs/user-guide/kubectl/kubectl_cluster-info.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_cluster-info.md
rename to docs/user-guide/kubectl/kubectl_cluster-info.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_config.md b/docs/user-guide/kubectl/kubectl_config.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_config.md
rename to docs/user-guide/kubectl/kubectl_config.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_config_set-cluster.md b/docs/user-guide/kubectl/kubectl_config_set-cluster.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_config_set-cluster.md
rename to docs/user-guide/kubectl/kubectl_config_set-cluster.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_config_set-context.md b/docs/user-guide/kubectl/kubectl_config_set-context.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_config_set-context.md
rename to docs/user-guide/kubectl/kubectl_config_set-context.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_config_set-credentials.md b/docs/user-guide/kubectl/kubectl_config_set-credentials.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_config_set-credentials.md
rename to docs/user-guide/kubectl/kubectl_config_set-credentials.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_config_set.md b/docs/user-guide/kubectl/kubectl_config_set.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_config_set.md
rename to docs/user-guide/kubectl/kubectl_config_set.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_config_unset.md b/docs/user-guide/kubectl/kubectl_config_unset.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_config_unset.md
rename to docs/user-guide/kubectl/kubectl_config_unset.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_config_use-context.md b/docs/user-guide/kubectl/kubectl_config_use-context.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_config_use-context.md
rename to docs/user-guide/kubectl/kubectl_config_use-context.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_config_view.md b/docs/user-guide/kubectl/kubectl_config_view.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_config_view.md
rename to docs/user-guide/kubectl/kubectl_config_view.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_create.md b/docs/user-guide/kubectl/kubectl_create.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_create.md
rename to docs/user-guide/kubectl/kubectl_create.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_delete.md b/docs/user-guide/kubectl/kubectl_delete.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_delete.md
rename to docs/user-guide/kubectl/kubectl_delete.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_describe.md b/docs/user-guide/kubectl/kubectl_describe.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_describe.md
rename to docs/user-guide/kubectl/kubectl_describe.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_edit.md b/docs/user-guide/kubectl/kubectl_edit.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_edit.md
rename to docs/user-guide/kubectl/kubectl_edit.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_exec.md b/docs/user-guide/kubectl/kubectl_exec.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_exec.md
rename to docs/user-guide/kubectl/kubectl_exec.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_expose.md b/docs/user-guide/kubectl/kubectl_expose.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_expose.md
rename to docs/user-guide/kubectl/kubectl_expose.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_get.md b/docs/user-guide/kubectl/kubectl_get.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_get.md
rename to docs/user-guide/kubectl/kubectl_get.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_label.md b/docs/user-guide/kubectl/kubectl_label.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_label.md
rename to docs/user-guide/kubectl/kubectl_label.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_logs.md b/docs/user-guide/kubectl/kubectl_logs.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_logs.md
rename to docs/user-guide/kubectl/kubectl_logs.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_namespace.md b/docs/user-guide/kubectl/kubectl_namespace.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_namespace.md
rename to docs/user-guide/kubectl/kubectl_namespace.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_patch.md b/docs/user-guide/kubectl/kubectl_patch.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_patch.md
rename to docs/user-guide/kubectl/kubectl_patch.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_port-forward.md b/docs/user-guide/kubectl/kubectl_port-forward.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_port-forward.md
rename to docs/user-guide/kubectl/kubectl_port-forward.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_proxy.md b/docs/user-guide/kubectl/kubectl_proxy.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_proxy.md
rename to docs/user-guide/kubectl/kubectl_proxy.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_replace.md b/docs/user-guide/kubectl/kubectl_replace.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_replace.md
rename to docs/user-guide/kubectl/kubectl_replace.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_rolling-update.md b/docs/user-guide/kubectl/kubectl_rolling-update.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_rolling-update.md
rename to docs/user-guide/kubectl/kubectl_rolling-update.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_run.md b/docs/user-guide/kubectl/kubectl_run.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_run.md
rename to docs/user-guide/kubectl/kubectl_run.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_scale.md b/docs/user-guide/kubectl/kubectl_scale.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_scale.md
rename to docs/user-guide/kubectl/kubectl_scale.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_stop.md b/docs/user-guide/kubectl/kubectl_stop.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_stop.md
rename to docs/user-guide/kubectl/kubectl_stop.md
diff --git a/v1.1/docs/user-guide/kubectl/kubectl_version.md b/docs/user-guide/kubectl/kubectl_version.md
similarity index 100%
rename from v1.1/docs/user-guide/kubectl/kubectl_version.md
rename to docs/user-guide/kubectl/kubectl_version.md
diff --git a/v1.2/docs/user-guide/labels.md b/docs/user-guide/labels.md
similarity index 92%
rename from v1.2/docs/user-guide/labels.md
rename to docs/user-guide/labels.md
index 31eddd0216..7d58fe6e7e 100644
--- a/v1.2/docs/user-guide/labels.md
+++ b/docs/user-guide/labels.md
@@ -13,7 +13,7 @@ Each object can have a set of key/value labels defined.  Each Key must be unique
 }
 ```
 
-We'll eventually index and reverse-index labels for efficient queries and watches, use them to sort and group in UIs and CLIs, etc. We don't want to pollute labels with non-identifying, especially large and/or structured, data. Non-identifying information should be recorded using [annotations](/{{page.version}}/docs/user-guide/annotations).
+We'll eventually index and reverse-index labels for efficient queries and watches, use them to sort and group in UIs and CLIs, etc. We don't want to pollute labels with non-identifying, especially large and/or structured, data. Non-identifying information should be recorded using [annotations](/docs/user-guide/annotations).
 
 * TOC
 {:toc}
@@ -43,7 +43,7 @@ Valid label values must be 63 characters or less and must be empty or begin and
 
 ## Label selectors
 
-Unlike [names and UIDs](/{{page.version}}/docs/user-guide/identifiers), labels do not provide uniqueness. In general, we expect many objects to carry the same label(s).
+Unlike [names and UIDs](/docs/user-guide/identifiers), labels do not provide uniqueness. In general, we expect many objects to carry the same label(s).
 
 Via a _label selector_, the client/user can identify a set of objects. The label selector is the core grouping primitive in Kubernetes.
 
@@ -125,7 +125,7 @@ $ kubectl get pods -l 'environment,environment notin (frontend)'
 
 ### Set references in API objects
 
-Some Kubernetes objects, such as [`service`s](/{{page.version}}/docs/user-guide/services) and [`replicationcontroller`s](/{{page.version}}/docs/user-guide/replication-controller), also use label selectors to specify sets of other resources, such as [pods](/{{page.version}}/docs/user-guide/pods).
+Some Kubernetes objects, such as [`service`s](/docs/user-guide/services) and [`replicationcontroller`s](/docs/user-guide/replication-controller), also use label selectors to specify sets of other resources, such as [pods](/docs/user-guide/pods).
 
 #### Service and ReplicationController
 
@@ -149,7 +149,7 @@ this selector (respectively in `json` or `yaml` format) is equivalent to `compon
 
 #### Job and other new resources
 
-Newer resources, such as [job](/{{page.version}}/docs/user-guide/jobs), support _set-based_ requirements as well.
+Newer resources, such as [job](/docs/user-guide/jobs), support _set-based_ requirements as well.
 
 ```yaml
 selector:
diff --git a/v1.1/docs/user-guide/liveness/exec-liveness.yaml b/docs/user-guide/liveness/exec-liveness.yaml
similarity index 100%
rename from v1.1/docs/user-guide/liveness/exec-liveness.yaml
rename to docs/user-guide/liveness/exec-liveness.yaml
diff --git a/v1.1/docs/user-guide/liveness/http-liveness.yaml b/docs/user-guide/liveness/http-liveness.yaml
similarity index 100%
rename from v1.1/docs/user-guide/liveness/http-liveness.yaml
rename to docs/user-guide/liveness/http-liveness.yaml
diff --git a/v1.1/docs/user-guide/liveness/image/Dockerfile b/docs/user-guide/liveness/image/Dockerfile
similarity index 100%
rename from v1.1/docs/user-guide/liveness/image/Dockerfile
rename to docs/user-guide/liveness/image/Dockerfile
diff --git a/v1.1/docs/user-guide/liveness/image/Makefile b/docs/user-guide/liveness/image/Makefile
similarity index 100%
rename from v1.1/docs/user-guide/liveness/image/Makefile
rename to docs/user-guide/liveness/image/Makefile
diff --git a/v1.1/docs/user-guide/liveness/image/server.go b/docs/user-guide/liveness/image/server.go
similarity index 100%
rename from v1.1/docs/user-guide/liveness/image/server.go
rename to docs/user-guide/liveness/image/server.go
diff --git a/v1.1/docs/user-guide/liveness/index.md b/docs/user-guide/liveness/index.md
similarity index 85%
rename from v1.1/docs/user-guide/liveness/index.md
rename to docs/user-guide/liveness/index.md
index 3f5c99eac4..6bc0af3d93 100644
--- a/v1.1/docs/user-guide/liveness/index.md
+++ b/docs/user-guide/liveness/index.md
@@ -1,9 +1,9 @@
 ---
 ---
 
-This example shows two types of pod [health checks](/{{page.version}}/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks): HTTP checks and container execution checks.
+This example shows two types of pod [health checks](/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks): HTTP checks and container execution checks.
 
-The [exec-liveness.yaml](/{{page.version}}/docs/user-guide/liveness/exec-liveness.yaml) demonstrates the container execution check.
+The [exec-liveness.yaml](/docs/user-guide/liveness/exec-liveness.yaml) demonstrates the container execution check.
 
 ```yaml
 livenessProbe:
@@ -26,7 +26,7 @@ echo ok > /tmp/health; sleep 10; rm -rf /tmp/health; sleep 600
 so when Kubelet executes the health check 15 seconds (defined by initialDelaySeconds) after the container started, the check would fail.
 
 
-The [http-liveness.yaml](/{{page.version}}/docs/user-guide/liveness/http-liveness.yaml) demonstrates the HTTP check.
+The [http-liveness.yaml](/docs/user-guide/liveness/http-liveness.yaml) demonstrates the HTTP check.
 
 ```yaml
 livenessProbe:
@@ -39,7 +39,7 @@ livenessProbe:
 
 The Kubelet sends an HTTP request to the specified path and port to perform the health check. If you take a look at image/server.go, you will see the server starts to respond with an error code 500 after 10 seconds, so the check fails. The Kubelet sends the probe to the container's ip address by default which could be specified with `host` as part of httpGet probe. If the container listens on `127.0.0.1`, `host` should be specified as `127.0.0.1`. In general, if the container listens on its ip address or on all interfaces (0.0.0.0), there is no need to specify the `host` as part of the httpGet probe.
 
-This [guide](/{{page.version}}/docs/user-guide/k8s201/#health-checking) has more information on health checks.
+This [guide](/docs/user-guide/k8s201/#health-checking) has more information on health checks.
 
 ## Get your hands dirty
 
diff --git a/v1.1/docs/user-guide/logging-demo/Makefile b/docs/user-guide/logging-demo/Makefile
similarity index 100%
rename from v1.1/docs/user-guide/logging-demo/Makefile
rename to docs/user-guide/logging-demo/Makefile
diff --git a/docs/user-guide/logging-demo/index.md b/docs/user-guide/logging-demo/index.md
new file mode 100644
index 0000000000..8927213857
--- /dev/null
+++ b/docs/user-guide/logging-demo/index.md
@@ -0,0 +1,18 @@
+---
+---
+
+This directory contains two [pod](/docs/user-guide/pods) specifications which can be used as synthetic
+logging sources. The pod specification in [synthetic_0_25lps.yaml](/docs/user-guide/logging-demo/synthetic_0_25lps.yaml)
+describes a pod that just emits a log message once every 4 seconds. The pod specification in
+[synthetic_10lps.yaml](/docs/user-guide/logging-demo/synthetic_10lps.yaml)
+describes a pod that just emits 10 log lines per second.
+
+See [logging document](/docs/user-guide/logging/) for more details about logging. To observe the ingested log lines when using Google Cloud Logging please see the getting
+started instructions
+at [Cluster Level Logging to Google Cloud Logging](/docs/getting-started-guides/logging).
+To observe the ingested log lines when using Elasticsearch and Kibana please see the getting
+started instructions
+at [Cluster Level Logging with Elasticsearch and Kibana](/docs/getting-started-guides/logging-elasticsearch).
+
+
+
diff --git a/v1.1/docs/user-guide/logging-demo/synthetic_0_25lps.yaml b/docs/user-guide/logging-demo/synthetic_0_25lps.yaml
similarity index 100%
rename from v1.1/docs/user-guide/logging-demo/synthetic_0_25lps.yaml
rename to docs/user-guide/logging-demo/synthetic_0_25lps.yaml
diff --git a/v1.1/docs/user-guide/logging-demo/synthetic_10lps.yaml b/docs/user-guide/logging-demo/synthetic_10lps.yaml
similarity index 100%
rename from v1.1/docs/user-guide/logging-demo/synthetic_10lps.yaml
rename to docs/user-guide/logging-demo/synthetic_10lps.yaml
diff --git a/v1.2/docs/user-guide/logging.md b/docs/user-guide/logging.md
similarity index 91%
rename from v1.2/docs/user-guide/logging.md
rename to docs/user-guide/logging.md
index fb0a62a633..16085393af 100644
--- a/v1.2/docs/user-guide/logging.md
+++ b/docs/user-guide/logging.md
@@ -5,13 +5,13 @@ This page is designed to help you use logs to troubleshoot issues with your Kube
 
 ## Logging by Kubernetes Components
 
-Kubernetes components, such as kubelet and apiserver, use the [glog](https://godoc.org/github.com/golang/glog) logging library.  Developer conventions for logging severity are described in [docs/devel/logging.md](/{{page.version}}/docs/devel/logging).
+Kubernetes components, such as kubelet and apiserver, use the [glog](https://godoc.org/github.com/golang/glog) logging library.  Developer conventions for logging severity are described in [docs/devel/logging.md](/docs/devel/logging).
 
 ## Examining the logs of running containers
 
 The logs of a running container may be fetched using the command `kubectl logs`. For example, given
 this pod specification [counter-pod.yaml](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/blog-logging/counter-pod.yaml), which has a container which writes out some text to standard
-output every second. (You can find different pod specifications [here](/{{page.version}}/docs/user-guide/logging-demo/).)
+output every second. (You can find different pod specifications [here](/docs/user-guide/logging-demo/).)
 
 <!-- BEGIN MUNGE: EXAMPLE ../../examples/blog-logging/counter-pod.yaml -->
 
@@ -74,13 +74,13 @@ $ kubectl logs kube-dns-v3-7r1l9 etcd
 
 ## Cluster level logging to Google Cloud Logging
 
-The getting started guide [Cluster Level Logging to Google Cloud Logging](/{{page.version}}/docs/getting-started-guides/logging)
+The getting started guide [Cluster Level Logging to Google Cloud Logging](/docs/getting-started-guides/logging)
 explains how container logs are ingested into [Google Cloud Logging](https://cloud.google.com/logging/docs/)
 and shows how to query the ingested logs.
 
 ## Cluster level logging with Elasticsearch and Kibana
 
-The getting started guide [Cluster Level Logging with Elasticsearch and Kibana](/{{page.version}}/docs/getting-started-guides/logging-elasticsearch)
+The getting started guide [Cluster Level Logging with Elasticsearch and Kibana](/docs/getting-started-guides/logging-elasticsearch)
 describes how to ingest cluster level logs into Elasticsearch and view them using Kibana.
 
 ## Ingesting Application Log Files
diff --git a/v1.1/docs/user-guide/managing-deployments.md b/docs/user-guide/managing-deployments.md
similarity index 93%
rename from v1.1/docs/user-guide/managing-deployments.md
rename to docs/user-guide/managing-deployments.md
index d0f56ac419..27c8a63379 100644
--- a/v1.1/docs/user-guide/managing-deployments.md
+++ b/docs/user-guide/managing-deployments.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-You've deployed your application and exposed it via a service. Now what? Kubernetes provides a number of tools to help you manage your application deployment, including scaling and updating. Among the features we'll discuss in more depth are [configuration files](/{{page.version}}/docs/user-guide/configuring-containers/#configuration-in-kubernetes) and [labels](/{{page.version}}/docs/user-guide/deploying-applications/#labels).
+You've deployed your application and exposed it via a service. Now what? Kubernetes provides a number of tools to help you manage your application deployment, including scaling and updating. Among the features we'll discuss in more depth are [configuration files](/docs/user-guide/configuring-containers/#configuration-in-kubernetes) and [labels](/docs/user-guide/deploying-applications/#labels).
 
 * TOC
 {:toc}
@@ -233,7 +233,7 @@ my-nginx-o0ef1   1/1       Running   0          1h
 
 At some point, you'll eventually need to update your deployed application, typically by specifying a new image or image tag, as in the canary deployment scenario above. `kubectl` supports several update operations, each of which is applicable to different scenarios.
 
-To update a service without an outage, `kubectl` supports what is called ['rolling update'?](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update), which updates one pod at a time, rather than taking down the entire service at the same time. See the [rolling update design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/simple-rolling-update.md) and the [example of rolling update](/{{page.version}}/docs/user-guide/update-demo/) for more information.
+To update a service without an outage, `kubectl` supports what is called ['rolling update'?](/docs/user-guide/kubectl/kubectl_rolling-update), which updates one pod at a time, rather than taking down the entire service at the same time. See the [rolling update design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/simple-rolling-update.md) and the [example of rolling update](/docs/user-guide/update-demo/) for more information.
 
 Let's say you were running version 1.7.9 of nginx:
 
@@ -361,11 +361,11 @@ Update succeeded. Deleting my-nginx
 my-nginx-v4
 ```
 
-You can also run the [update demo](/{{page.version}}/docs/user-guide/update-demo/) to see a visual representation of the rolling update process.
+You can also run the [update demo](/docs/user-guide/update-demo/) to see a visual representation of the rolling update process.
 
 ## In-place updates of resources
 
-Sometimes it's necessary to make narrow, non-disruptive updates to resources you've created. For instance, you might want to add an [annotation](/{{page.version}}/docs/user-guide/annotations) with a description of your object. That's easiest to do with `kubectl patch`:
+Sometimes it's necessary to make narrow, non-disruptive updates to resources you've created. For instance, you might want to add an [annotation](/docs/user-guide/annotations) with a description of your object. That's easiest to do with `kubectl patch`:
 
 ```shell
 $ kubectl patch rc my-nginx-v4 -p '{"metadata": {"annotations": {"description": "my frontend running nginx"}}}' 
@@ -405,5 +405,5 @@ replicationcontrollers/my-nginx-v4
 
 ## What's next?
 
-- [Learn about how to use `kubectl` for application introspection and debugging.](/{{page.version}}/docs/user-guide/introspection-and-debugging)
-- [Tips and tricks when working with config](/{{page.version}}/docs/user-guide/config-best-practices
+- [Learn about how to use `kubectl` for application introspection and debugging.](/docs/user-guide/introspection-and-debugging)
+- [Tips and tricks when working with config](/docs/user-guide/config-best-practices
diff --git a/v1.1/docs/user-guide/monitoring.md b/docs/user-guide/monitoring.md
similarity index 89%
rename from v1.1/docs/user-guide/monitoring.md
rename to docs/user-guide/monitoring.md
index d47a3be2bb..aefd685339 100644
--- a/v1.1/docs/user-guide/monitoring.md
+++ b/docs/user-guide/monitoring.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-Understanding how an application behaves when deployed is crucial to scaling the application and providing a reliable service. In a Kubernetes cluster, application performance can be examined at many different levels: containers, [pods](/{{page.version}}/docs/user-guide/pods), [services](/{{page.version}}/docs/user-guide/services), and whole clusters. As part of Kubernetes we want to provide users with detailed resource usage information about their running applications at all these levels. This will give users deep insights into how their applications are performing and where possible application bottlenecks may be found. In comes [Heapster](https://github.com/GoogleCloudPlatform/heapster), a project meant to provide a base monitoring platform on Kubernetes.
+Understanding how an application behaves when deployed is crucial to scaling the application and providing a reliable service. In a Kubernetes cluster, application performance can be examined at many different levels: containers, [pods](/docs/user-guide/pods), [services](/docs/user-guide/services), and whole clusters. As part of Kubernetes we want to provide users with detailed resource usage information about their running applications at all these levels. This will give users deep insights into how their applications are performing and where possible application bottlenecks may be found. In comes [Heapster](https://github.com/GoogleCloudPlatform/heapster), a project meant to provide a base monitoring platform on Kubernetes.
 
 ### Overview
 
@@ -53,7 +53,7 @@ Here is a snapshot of the a Google Cloud Monitoring dashboard showing cluster-wi
 
 ## Try it out!
 
-Now that you've learned a bit about Heapster, feel free to try it out on your own clusters! The [Heapster repository](https://github.com/kubernetes/heapster) is available on GitHub. It contains detailed instructions to setup Heapster and its storage backends. Heapster runs by default on most Kubernetes clusters, so you may already have it! Feedback is always welcome. Please let us know if you run into any issues via the troubleshooting [channels](/{{page.version}}/docs/troubleshooting/).
+Now that you've learned a bit about Heapster, feel free to try it out on your own clusters! The [Heapster repository](https://github.com/kubernetes/heapster) is available on GitHub. It contains detailed instructions to setup Heapster and its storage backends. Heapster runs by default on most Kubernetes clusters, so you may already have it! Feedback is always welcome. Please let us know if you run into any issues via the troubleshooting [channels](/docs/troubleshooting/).
 
 ***
 *Authors: Vishnu Kannan and Victor Marmol, Google Software Engineers.*
diff --git a/v1.1/docs/user-guide/multi-pod.yaml b/docs/user-guide/multi-pod.yaml
similarity index 100%
rename from v1.1/docs/user-guide/multi-pod.yaml
rename to docs/user-guide/multi-pod.yaml
diff --git a/v1.2/docs/user-guide/namespaces.md b/docs/user-guide/namespaces.md
similarity index 87%
rename from v1.2/docs/user-guide/namespaces.md
rename to docs/user-guide/namespaces.md
index b473e21b32..29a9c13f45 100644
--- a/v1.2/docs/user-guide/namespaces.md
+++ b/docs/user-guide/namespaces.md
@@ -13,19 +13,19 @@ need the features they provide.
 
 Namespaces provide a scope for names.  Names of resources need to be unique within a namespace, but not across namespaces.
 
-Namespaces are a way to divide cluster resources between multiple uses (via [resource quota](/{{page.version}}/docs/admin/resource-quota)).
+Namespaces are a way to divide cluster resources between multiple uses (via [resource quota](/docs/admin/resource-quota)).
 
 In future versions of Kubernetes, objects in the same namespace will have the same
 access control policies by default.
 
 It is not necessary to use multiple namespaces just to separate slightly different
-resources, such as different versions of the same software: use [labels](/{{page.version}}/docs/user-guide/labels) to distinguish
+resources, such as different versions of the same software: use [labels](/docs/user-guide/labels) to distinguish
 resources within the same namespace.
 
 ## Working with Namespaces
 
 Creation and deletion of namespaces is described in the [Admin Guide documentation
-for namespaces](/{{page.version}}/docs/admin/namespaces)
+for namespaces](/docs/admin/namespaces)
 
 ### Viewing namespaces
 
@@ -73,7 +73,7 @@ $ kubectl config set-context $(CONTEXT) --namespace=<insert-namespace-name-here>
 
 ## Namespaces and DNS
 
-When you create a [Service](/{{page.version}}/docs/user-guide/services), it creates a corresponding [DNS entry](/{{page.version}}/docs/admin/dns).
+When you create a [Service](/docs/user-guide/services), it creates a corresponding [DNS entry](/docs/admin/dns).
 This entry is of the form `<service-name>.<namespace-name>.svc.cluster.local`, which means
 that if a container just uses `<service-name>` it will resolve to the service which
 is local to a namespace.  This is useful for using the same configuration across
@@ -84,6 +84,6 @@ across namespaces, you need to use the fully qualified domain name (FQDN).
 
 Most kubernetes resources (e.g. pods, services, replication controllers, and others) are
 in a some namespace.  However namespace resources are not themselves in a namespace.
-And, low-level resources, such as [nodes](/{{page.version}}/docs/admin/node) and
+And, low-level resources, such as [nodes](/docs/admin/node) and
 persistentVolumes, are not in any namespace. Events are an exception: they may or may not
 have a namespace, depending on the object the event is about.
diff --git a/v1.1/docs/user-guide/new-nginx-deployment.yaml b/docs/user-guide/new-nginx-deployment.yaml
similarity index 100%
rename from v1.1/docs/user-guide/new-nginx-deployment.yaml
rename to docs/user-guide/new-nginx-deployment.yaml
diff --git a/v1.1/docs/user-guide/nginx-deployment.yaml b/docs/user-guide/nginx-deployment.yaml
similarity index 100%
rename from v1.1/docs/user-guide/nginx-deployment.yaml
rename to docs/user-guide/nginx-deployment.yaml
diff --git a/v1.1/docs/user-guide/node-selection/index.md b/docs/user-guide/node-selection/index.md
similarity index 85%
rename from v1.1/docs/user-guide/node-selection/index.md
rename to docs/user-guide/node-selection/index.md
index f3ee5dd838..5a7a5f3b98 100644
--- a/v1.1/docs/user-guide/node-selection/index.md
+++ b/docs/user-guide/node-selection/index.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-This example shows how to assign a [pod](/{{page.version}}/docs/user-guide/pods/) to a specific [node](/{{page.version}}/docs/admin/node/) or to one of a set of nodes using node labels and the nodeSelector field in a pod specification. Generally this is unnecessary, as the scheduler will take care of things for you, but you may want to do so in certain circumstances like to ensure that your pod ends up on a machine with an SSD attached to it.
+This example shows how to assign a [pod](/docs/user-guide/pods/) to a specific [node](/docs/admin/node/) or to one of a set of nodes using node labels and the nodeSelector field in a pod specification. Generally this is unnecessary, as the scheduler will take care of things for you, but you may want to do so in certain circumstances like to ensure that your pod ends up on a machine with an SSD attached to it.
 
 ### Step Zero: Prerequisites
 
diff --git a/v1.1/docs/user-guide/node-selection/pod.yaml b/docs/user-guide/node-selection/pod.yaml
similarity index 100%
rename from v1.1/docs/user-guide/node-selection/pod.yaml
rename to docs/user-guide/node-selection/pod.yaml
diff --git a/docs/user-guide/overview.md b/docs/user-guide/overview.md
new file mode 100644
index 0000000000..79a824f6b9
--- /dev/null
+++ b/docs/user-guide/overview.md
@@ -0,0 +1,25 @@
+---
+---
+
+Kubernetes is an open-source system for managing containerized applications across multiple hosts in a cluster. Kubernetes is intended to make deploying containerized/microservice-based applications easy but powerful.
+
+Kubernetes provides mechanisms for application deployment, scheduling, updating, maintenance, and scaling. A key feature of Kubernetes is that it actively manages the containers to ensure that the state of the cluster continually matches the user's intentions. An operations user should be able to launch a micro-service, letting the scheduler find the right placement. We also want to improve the tools and experience for how users can roll-out applications through patterns like canary deployments.
+
+Kubernetes supports [Docker](http://www.docker.io) and [Rocket](https://coreos.com/blog/rocket/) containers, and other container image formats and container runtimes will be supported in the future.
+
+While Kubernetes currently focuses on continuously-running stateless (e.g. web server or in-memory object cache) and "cloud native" stateful applications (e.g. NoSQL datastores), in the near future it will support all the other workload types commonly found in production cluster environments, such as batch, stream processing, and traditional databases.
+
+In Kubernetes, all containers run inside [pods](/docs/user-guide/pods). A pod can host a single container, or multiple cooperating containers; in the latter case, the containers in the pod are guaranteed to be co-located on the same machine and can share resources. A pod can also contain zero or more [volumes](/docs/user-guide/volumes), which are directories that are private to a container or shared across containers in a pod. For each pod the user creates, the system finds a machine that is healthy and that has sufficient available capacity, and starts up the corresponding container(s) there. If a container fails it can be automatically restarted by Kubernetes' node agent, called the Kubelet. But if the pod or its machine fails, it is not automatically moved or restarted unless the user also defines a [replication controller](/docs/user-guide/replication-controller), which we discuss next.
+
+Users can create and manage pods themselves, but Kubernetes drastically simplifies system management by allowing users to delegate two common pod-related activities: deploying multiple pod replicas based on the same pod configuration, and creating replacement pods when a pod or its machine fails. The Kubernetes API object that manages these behaviors is called a [replication controller](/docs/user-guide/replication-controller). It defines a pod in terms of a template, that the system then instantiates as some number of pods (specified by the user). The replicated set of pods might constitute an entire application, a micro-service, or one layer in a multi-tier application. Once the pods are created, the system continually monitors their health and that of the machines they are running on; if a pod fails due to a software problem or machine failure, the replication controller automatically creates a new pod on a healthy machine, to maintain the set of pods at the desired replication level. Multiple pods from the same or different applications can share the same machine. Note that a replication controller is needed even in the case of a single non-replicated pod if the user wants it to be re-created when it or its machine fails.
+
+Frequently it is useful to refer to a set of pods, for example to limit the set of pods on which a mutating operation should be performed, or that should be queried for status. As a general mechanism, users can attach to most Kubernetes API objects arbitrary key-value pairs called [labels](/docs/user-guide/labels), and then use a set of label selectors (key-value queries over labels) to constrain the target of API operations. Each resource also has a map of string keys and values that can be used by external tooling to store and retrieve arbitrary metadata about this object, called [annotations](/docs/user-guide/annotations).
+
+Kubernetes supports a unique [networking model](/docs/admin/networking). Kubernetes encourages a flat address space and does not dynamically allocate ports, instead allowing users to select whichever ports are convenient for them. To achieve this, it allocates an IP address for each pod.
+
+Modern Internet applications are commonly built by layering micro-services, for example a set of web front-ends talking to a distributed in-memory key-value store talking to a replicated storage service. To facilitate this architecture, Kubernetes offers the [service](/docs/user-guide/services) abstraction, which provides a stable IP address and [DNS name](/docs/admin/dns) that corresponds to a dynamic set of pods such as the set of pods constituting a micro-service. The set is defined using a label selector and thus can refer to any set of pods. When a container running in a Kubernetes pod connects to this address, the connection is forwarded by a local agent (called the kube proxy) running on the source machine, to one of the corresponding back-end containers. The exact back-end is chosen using a round-robin policy to balance load. The kube proxy takes care of tracking the dynamic set of back-ends as pods are replaced by new pods on new hosts, so that the service IP address (and DNS name) never changes.
+
+Every resource in Kubernetes, such as a pod, is identified by a URI and has a UID. Important components of the URI are the kind of object (e.g. pod), the object's name, and the object's [namespace](/docs/user-guide/namespaces). For a certain object kind, every name is unique within its namespace. In contexts where an object name is provided without a namespace, it is assumed to be in the default namespace. UID is unique across time and space.
+
+
+
diff --git a/v1.2/docs/user-guide/persistent-volumes.md b/docs/user-guide/persistent-volumes.md
similarity index 97%
rename from v1.2/docs/user-guide/persistent-volumes.md
rename to docs/user-guide/persistent-volumes.md
index 73c75ee105..ec0bc1b981 100644
--- a/v1.2/docs/user-guide/persistent-volumes.md
+++ b/docs/user-guide/persistent-volumes.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-This document describes the current state of `PersistentVolumes` in Kubernetes.  Familiarity with [volumes](/{{page.version}}/docs/user-guide/volumes) is suggested.
+This document describes the current state of `PersistentVolumes` in Kubernetes.  Familiarity with [volumes](/docs/user-guide/volumes) is suggested.
 
 * TOC
 {:toc}
@@ -14,7 +14,7 @@ A `PersistentVolume` (PV) is a piece of networked storage in the cluster that ha
 
 A `PersistentVolumeClaim` (PVC) is a request for storage by a user.  It is similar to a pod.  Pods consume node resources and PVCs consume PV resources.  Pods can request specific levels of resources (CPU and Memory).  Claims can request specific size and access modes (e.g, can be mounted once read/write or many times read-only).
 
-Please see the [detailed walkthrough with working examples](/{{page.version}}/docs/user-guide/persistent-volumes/).
+Please see the [detailed walkthrough with working examples](/docs/user-guide/persistent-volumes/).
 
 
 ## Lifecycle of a volume and claim
diff --git a/v1.1/docs/user-guide/persistent-volumes/claims/claim-01.yaml b/docs/user-guide/persistent-volumes/claims/claim-01.yaml
similarity index 100%
rename from v1.1/docs/user-guide/persistent-volumes/claims/claim-01.yaml
rename to docs/user-guide/persistent-volumes/claims/claim-01.yaml
diff --git a/v1.1/docs/user-guide/persistent-volumes/claims/claim-02.yaml b/docs/user-guide/persistent-volumes/claims/claim-02.yaml
similarity index 100%
rename from v1.1/docs/user-guide/persistent-volumes/claims/claim-02.yaml
rename to docs/user-guide/persistent-volumes/claims/claim-02.yaml
diff --git a/v1.1/docs/user-guide/persistent-volumes/claims/claim-03.json b/docs/user-guide/persistent-volumes/claims/claim-03.json
similarity index 100%
rename from v1.1/docs/user-guide/persistent-volumes/claims/claim-03.json
rename to docs/user-guide/persistent-volumes/claims/claim-03.json
diff --git a/v1.1/docs/user-guide/persistent-volumes/index.md b/docs/user-guide/persistent-volumes/index.md
similarity index 95%
rename from v1.1/docs/user-guide/persistent-volumes/index.md
rename to docs/user-guide/persistent-volumes/index.md
index ee996b58de..ab3076bf77 100644
--- a/v1.1/docs/user-guide/persistent-volumes/index.md
+++ b/docs/user-guide/persistent-volumes/index.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-The purpose of this guide is to help you become familiar with [Kubernetes Persistent Volumes](/{{page.version}}/docs/user-guide/persistent-volumes/).  By the end of the guide, we'll have
+The purpose of this guide is to help you become familiar with [Kubernetes Persistent Volumes](/docs/user-guide/persistent-volumes/).  By the end of the guide, we'll have
 nginx serving content from your persistent volume.
 
 This guide assumes knowledge of Kubernetes fundamentals and that you have a cluster up and running.
@@ -88,6 +88,6 @@ $ curl 10.0.0.241:3000
 I love Kubernetes storage!
 ```
 
-Hopefully this simple guide is enough to get you started with PersistentVolumes.  If you have any questions, join the team on [Slack](/{{page.version}}/docs/troubleshooting/#slack) and ask!
+Hopefully this simple guide is enough to get you started with PersistentVolumes.  If you have any questions, join the team on [Slack](/docs/troubleshooting/#slack) and ask!
 
 Enjoy!
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/persistent-volumes/simpletest/namespace.json b/docs/user-guide/persistent-volumes/simpletest/namespace.json
similarity index 100%
rename from v1.1/docs/user-guide/persistent-volumes/simpletest/namespace.json
rename to docs/user-guide/persistent-volumes/simpletest/namespace.json
diff --git a/v1.1/docs/user-guide/persistent-volumes/simpletest/pod.yaml b/docs/user-guide/persistent-volumes/simpletest/pod.yaml
similarity index 100%
rename from v1.1/docs/user-guide/persistent-volumes/simpletest/pod.yaml
rename to docs/user-guide/persistent-volumes/simpletest/pod.yaml
diff --git a/v1.1/docs/user-guide/persistent-volumes/simpletest/service.json b/docs/user-guide/persistent-volumes/simpletest/service.json
similarity index 100%
rename from v1.1/docs/user-guide/persistent-volumes/simpletest/service.json
rename to docs/user-guide/persistent-volumes/simpletest/service.json
diff --git a/v1.1/docs/user-guide/persistent-volumes/volumes/gce.yaml b/docs/user-guide/persistent-volumes/volumes/gce.yaml
similarity index 100%
rename from v1.1/docs/user-guide/persistent-volumes/volumes/gce.yaml
rename to docs/user-guide/persistent-volumes/volumes/gce.yaml
diff --git a/v1.1/docs/user-guide/persistent-volumes/volumes/local-01.yaml b/docs/user-guide/persistent-volumes/volumes/local-01.yaml
similarity index 100%
rename from v1.1/docs/user-guide/persistent-volumes/volumes/local-01.yaml
rename to docs/user-guide/persistent-volumes/volumes/local-01.yaml
diff --git a/v1.1/docs/user-guide/persistent-volumes/volumes/local-02.yaml b/docs/user-guide/persistent-volumes/volumes/local-02.yaml
similarity index 100%
rename from v1.1/docs/user-guide/persistent-volumes/volumes/local-02.yaml
rename to docs/user-guide/persistent-volumes/volumes/local-02.yaml
diff --git a/v1.1/docs/user-guide/persistent-volumes/volumes/nfs.yaml b/docs/user-guide/persistent-volumes/volumes/nfs.yaml
similarity index 100%
rename from v1.1/docs/user-guide/persistent-volumes/volumes/nfs.yaml
rename to docs/user-guide/persistent-volumes/volumes/nfs.yaml
diff --git a/v1.1/docs/user-guide/pod-states.md b/docs/user-guide/pod-states.md
similarity index 86%
rename from v1.1/docs/user-guide/pod-states.md
rename to docs/user-guide/pod-states.md
index 83e9bb8466..86fd49c29b 100644
--- a/v1.1/docs/user-guide/pod-states.md
+++ b/docs/user-guide/pod-states.md
@@ -7,7 +7,7 @@ This document covers the lifecycle of a pod.  It is not an exhaustive document,
 
 ## Pod Phase
 
-As consistent with the overall [API convention](/{{page.version}}/docs/devel/api-conventions/#typical-status-properties), phase is a simple, high-level summary of the phase of the lifecycle of a pod. It is not intended to be a comprehensive rollup of observations of container-level or even pod-level conditions or other state, nor is it intended to be a comprehensive state machine.
+As consistent with the overall [API convention](/docs/devel/api-conventions/#typical-status-properties), phase is a simple, high-level summary of the phase of the lifecycle of a pod. It is not intended to be a comprehensive rollup of observations of container-level or even pod-level conditions or other state, nor is it intended to be a comprehensive state machine.
 
 The number and meanings of `PodPhase` values are tightly guarded.  Other than what is documented here, nothing should be assumed about pods with a given `PodPhase`.
 
@@ -46,18 +46,18 @@ More detailed information about the current (and previous) container statuses ca
 
 ## RestartPolicy
 
-The possible values for RestartPolicy are `Always`, `OnFailure`, or `Never`. If RestartPolicy is not set, the default value is `Always`. RestartPolicy applies to all containers in the pod. RestartPolicy only refers to restarts of the containers by the Kubelet on the same node. Failed containers that are restarted by Kubelet, are restarted with an exponential back-off delay, the delay is in multiples of sync-frequency 0, 1x, 2x, 4x, 8x ... capped at 5 minutes and is reset after 10 minutes of successful execution. As discussed in the [pods document](/{{page.version}}/docs/user-guide/pods/#durability-of-pods-or-lack-thereof), once bound to a node, a pod will never be rebound to another node. This means that some kind of controller is necessary in order for a pod to survive node failure, even if just a single pod at a time is desired.
+The possible values for RestartPolicy are `Always`, `OnFailure`, or `Never`. If RestartPolicy is not set, the default value is `Always`. RestartPolicy applies to all containers in the pod. RestartPolicy only refers to restarts of the containers by the Kubelet on the same node. Failed containers that are restarted by Kubelet, are restarted with an exponential back-off delay, the delay is in multiples of sync-frequency 0, 1x, 2x, 4x, 8x ... capped at 5 minutes and is reset after 10 minutes of successful execution. As discussed in the [pods document](/docs/user-guide/pods/#durability-of-pods-or-lack-thereof), once bound to a node, a pod will never be rebound to another node. This means that some kind of controller is necessary in order for a pod to survive node failure, even if just a single pod at a time is desired.
 
 Three types of controllers are currently available:
 
-- Use a [`Job`](/{{page.version}}/docs/user-guide/jobs) for pods which are expected to terminate (e.g. batch computations).
-- Use a [`ReplicationController`](/{{page.version}}/docs/user-guide/replication-controller) for pods which are not expected to
+- Use a [`Job`](/docs/user-guide/jobs) for pods which are expected to terminate (e.g. batch computations).
+- Use a [`ReplicationController`](/docs/user-guide/replication-controller) for pods which are not expected to
 
   terminate, and where (e.g. web servers).
-- Use a [`DaemonSet`](/{{page.version}}/docs/admin/daemons): Use for pods which need to run 1 per machine because they provide a
+- Use a [`DaemonSet`](/docs/admin/daemons): Use for pods which need to run 1 per machine because they provide a
   machine-specific system service.
 If you are unsure whether to use ReplicationController or Daemon, then see [Daemon Set versus
-Replication Controller](/{{page.version}}/docs/admin/daemons/#daemon-set-versus-replication-controller).
+Replication Controller](/docs/admin/daemons/#daemon-set-versus-replication-controller).
 
 `ReplicationController` is *only* appropriate for pods with `RestartPolicy = Always`.
 `Job` is *only* appropriate for pods with `RestartPolicy` equal to `OnFailure` or `Never`.
diff --git a/v1.1/docs/user-guide/pod.yaml b/docs/user-guide/pod.yaml
similarity index 100%
rename from v1.1/docs/user-guide/pod.yaml
rename to docs/user-guide/pod.yaml
diff --git a/v1.1/docs/user-guide/pods.md b/docs/user-guide/pods.md
similarity index 89%
rename from v1.1/docs/user-guide/pods.md
rename to docs/user-guide/pods.md
index eb018929f3..7544dddf19 100644
--- a/v1.1/docs/user-guide/pods.md
+++ b/docs/user-guide/pods.md
@@ -19,9 +19,9 @@ The context of the pod can be defined as the conjunction of several Linux namesp
 
 Applications within a pod also have access to shared volumes, which are defined at the pod level and made available in each application's filesystem. Additionally, a pod may define top-level cgroup isolations which form an outer bound to any individual isolation applied to constituent applications.
 
-In terms of [Docker](https://www.docker.com/) constructs, a pod consists of a colocated group of Docker containers with shared [volumes](/{{page.version}}/docs/user-guide/volumes). PID namespace sharing is not yet implemented with Docker.
+In terms of [Docker](https://www.docker.com/) constructs, a pod consists of a colocated group of Docker containers with shared [volumes](/docs/user-guide/volumes). PID namespace sharing is not yet implemented with Docker.
 
-Like individual application containers, pods are considered to be relatively ephemeral rather than durable entities. As discussed in [life of a pod](/{{page.version}}/docs/user-guide/pod-states), pods are scheduled to nodes and remain there until termination (according to restart policy) or deletion. When a node dies, the pods scheduled to that node are deleted. Specific pods are never rescheduled to new nodes; instead, they must be replaced (see [/{{page.version}}/docs/user-guide/replication controller](/{{page.version}}/docs/user-guide/replication-controller) for more details). (In the future, a higher-level API may support pod migration.)
+Like individual application containers, pods are considered to be relatively ephemeral rather than durable entities. As discussed in [life of a pod](/docs/user-guide/pod-states), pods are scheduled to nodes and remain there until termination (according to restart policy) or deletion. When a node dies, the pods scheduled to that node are deleted. Specific pods are never rescheduled to new nodes; instead, they must be replaced (see [/{{page.version}}/docs/user-guide/replication controller](/docs/user-guide/replication-controller) for more details). (In the future, a higher-level API may support pod migration.)
 
 ## Motivation for pods
 
@@ -29,7 +29,7 @@ Like individual application containers, pods are considered to be relatively eph
 
 Pods facilitate data sharing and communication among their constituents.
 
-The applications in the pod all use the same network namespace/IP and port space, and can find and communicate with each other using localhost. Each pod has an IP address in a flat shared networking namespace that has full communication with other physical computers and containers across the network. The hostname is set to the pod's Name for the application containers within the pod. [More details on networking](/{{page.version}}/docs/admin/networking).
+The applications in the pod all use the same network namespace/IP and port space, and can find and communicate with each other using localhost. Each pod has an IP address in a flat shared networking namespace that has full communication with other physical computers and containers across the network. The hostname is set to the pod's Name for the application containers within the pod. [More details on networking](/docs/admin/networking).
 
 In addition to defining the application containers that run in the pod, the pod specifies a set of shared storage volumes. Volumes enable data to survive container restarts and to be shared among the applications within the pod.
 
@@ -68,7 +68,7 @@ That approach would provide co-location, but would not provide most of the benef
 
 Pods aren't intended to be treated as durable [pets](https://blog.engineyard.com/2014/pets-vs-cattle). They won't survive scheduling failures, node failures, or other evictions, such as due to lack of resources, or in the case of node maintenance.
 
-In general, users shouldn't need to create pods directly. They should almost always use controllers (e.g., [replication controller](/{{page.version}}/docs/user-guide/replication-controller)), even for singletons.  Controllers provide self-healing with a cluster scope, as well as replication and rollout management.
+In general, users shouldn't need to create pods directly. They should almost always use controllers (e.g., [replication controller](/docs/user-guide/replication-controller)), even for singletons.  Controllers provide self-healing with a cluster scope, as well as replication and rollout management.
 
 The use of collective APIs as the primary user-facing primitive is relatively common among cluster scheduling systems, including [Borg](https://research.google.com/pubs/pub43438), [Marathon](https://mesosphere.github.io/marathon/docs/rest-api), [Aurora](http://aurora.apache.org/documentation/latest/configuration-reference/#job-schema), and [Tupperware](http://www.slideshare.net/Docker/aravindnarayanan-facebook140613153626phpapp02-37588997).
 
@@ -93,7 +93,7 @@ An example flow:
 2. The Pod in the API server is updated with the time beyond which the Pod is considered "dead" along with the grace period.
 3. Pod shows up as "Terminating" when listed in client commands
 4. (simultaneous with 3) When the Kubelet sees that a Pod has been marked as terminating because the time in 2 has been set, it begins the pod shutdown process.
-  1. If the pod has defined a [preStop hook](/{{page.version}}/docs/user-guide/container-environment/#hook-details), it is invoked inside of the pod. If the `preStop` hook is still running after the grace period expires, step 2 is then invoked with a small (2 second) extended grace period.
+  1. If the pod has defined a [preStop hook](/docs/user-guide/container-environment/#hook-details), it is invoked inside of the pod. If the `preStop` hook is still running after the grace period expires, step 2 is then invoked with a small (2 second) extended grace period.
   2. The processes in the Pod are sent the TERM signal.
 5. (simultaneous with 3), Pod is removed from endpoints list for service, and are no longer considered part of the set of running pods for replication controllers. Pods that shutdown slowly can continue to serve traffic as load balancers (like the service proxy) remove them from their rotations.
 6. When the grace period expires, any processes still running in the Pod are killed with SIGKILL.
diff --git a/v1.1/docs/user-guide/prereqs.md b/docs/user-guide/prereqs.md
similarity index 66%
rename from v1.1/docs/user-guide/prereqs.md
rename to docs/user-guide/prereqs.md
index 45ced79a73..a75b685b73 100644
--- a/v1.1/docs/user-guide/prereqs.md
+++ b/docs/user-guide/prereqs.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-To deploy and manage applications on Kubernetes, you'll use the Kubernetes command-line tool, [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl). It lets you inspect your cluster resources, create, delete, and update components, and much more. You will use it to look at your new cluster and bring up example apps.
+To deploy and manage applications on Kubernetes, you'll use the Kubernetes command-line tool, [kubectl](/docs/user-guide/kubectl/kubectl). It lets you inspect your cluster resources, create, delete, and update components, and much more. You will use it to look at your new cluster and bring up example apps.
 
 ## Installing kubectl
 
@@ -38,7 +38,7 @@ export PATH=<path/to/kubernetes-directory>/platforms/linux/amd64:$PATH
 
 ## Configuring kubectl
 
-In order for kubectl to find and access the Kubernetes cluster, it needs a [kubeconfig file](/{{page.version}}/docs/user-guide/kubeconfig-file), which is created automatically when creating a cluster using kube-up.sh (see the [getting started guides](/{{page.version}}/docs/getting-started-guides/) for more about creating clusters). If you need access to a cluster you didn't create, see the [Sharing Cluster Access document](/{{page.version}}/docs/user-guide/sharing-clusters).
+In order for kubectl to find and access the Kubernetes cluster, it needs a [kubeconfig file](/docs/user-guide/kubeconfig-file), which is created automatically when creating a cluster using kube-up.sh (see the [getting started guides](/docs/getting-started-guides/) for more about creating clusters). If you need access to a cluster you didn't create, see the [Sharing Cluster Access document](/docs/user-guide/sharing-clusters).
 By default, kubectl configuration lives at `~/.kube/config`.
 
 #### Making sure you're ready
@@ -53,4 +53,4 @@ If you see a url response, you are ready to go.
 
 ## What's next?
 
-[Learn how to launch and expose your application.](/{{page.version}}/docs/user-guide/quick-start)
\ No newline at end of file
+[Learn how to launch and expose your application.](/docs/user-guide/quick-start)
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/production-pods.md b/docs/user-guide/production-pods.md
similarity index 74%
rename from v1.1/docs/user-guide/production-pods.md
rename to docs/user-guide/production-pods.md
index 8be9ee4328..99234499ee 100644
--- a/v1.1/docs/user-guide/production-pods.md
+++ b/docs/user-guide/production-pods.md
@@ -1,14 +1,14 @@
 ---
 ---
 
-You've seen [how to configure and deploy pods and containers](/{{page.version}}/docs/user-guide/configuring-containers), using some of the most common configuration parameters. This section dives into additional features that are especially useful for running applications in production.
+You've seen [how to configure and deploy pods and containers](/docs/user-guide/configuring-containers), using some of the most common configuration parameters. This section dives into additional features that are especially useful for running applications in production.
 
 * TOC
 {:toc}
 
 ## Persistent storage
 
-The container file system only lives as long as the container does, so when a container crashes and restarts, changes to the filesystem will be lost and the container will restart from a clean slate. To access more-persistent storage, outside the container file system, you need a [*volume*](/{{page.version}}/docs/user-guide/volumes). This is especially important to stateful applications, such as key-value stores and databases.
+The container file system only lives as long as the container does, so when a container crashes and restarts, changes to the filesystem will be lost and the container will restart from a clean slate. To access more-persistent storage, outside the container file system, you need a [*volume*](/docs/user-guide/volumes). This is especially important to stateful applications, such as key-value stores and databases.
 
 For example, [Redis](http://redis.io/) is a key-value cache and store, which we use in the [guestbook](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/) and other examples. We can add a volume to it to store persistent data as follows:
 
@@ -39,15 +39,15 @@ spec:
           name: data   # must match the name of the volume, above
 ```
 
-`emptyDir` volumes live for the lifespan of the [pod](/{{page.version}}/docs/user-guide/pods), which is longer than the lifespan of any one container, so if the container fails and is restarted, our storage will live on.
+`emptyDir` volumes live for the lifespan of the [pod](/docs/user-guide/pods), which is longer than the lifespan of any one container, so if the container fails and is restarted, our storage will live on.
 
-In addition to the local disk storage provided by `emptyDir`, Kubernetes supports many different network-attached storage solutions, including PD on GCE and EBS on EC2, which are preferred for critical data, and will handle details such as mounting and unmounting the devices on the nodes. See [the volumes doc](/{{page.version}}/docs/user-guide/volumes) for more details.
+In addition to the local disk storage provided by `emptyDir`, Kubernetes supports many different network-attached storage solutions, including PD on GCE and EBS on EC2, which are preferred for critical data, and will handle details such as mounting and unmounting the devices on the nodes. See [the volumes doc](/docs/user-guide/volumes) for more details.
 
 ## Distributing credentials
 
 Many applications need credentials, such as passwords, OAuth tokens, and TLS keys, to authenticate with other applications, databases, and services. Storing these credentials in container images or environment variables is less than ideal, since the credentials can then be copied by anyone with access to the image, pod/container specification, host file system, or host Docker daemon.
 
-Kubernetes provides a mechanism, called [*secrets*](/{{page.version}}/docs/user-guide/secrets), that facilitates delivery of sensitive credentials to applications. A `Secret` is a simple resource containing a map of data. For instance, a simple secret with a username and password might look as follows:
+Kubernetes provides a mechanism, called [*secrets*](/docs/user-guide/secrets), that facilitates delivery of sensitive credentials to applications. A `Secret` is a simple resource containing a map of data. For instance, a simple secret with a username and password might look as follows:
 
 ```yaml
 apiVersion: v1
@@ -104,14 +104,14 @@ spec:
           name: supersecret
 ```
 
-For more details, see the [secrets document](/{{page.version}}/docs/user-guide/secrets), [example](/{{page.version}}/docs/user-guide/secrets/) and [design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/secrets.md).
+For more details, see the [secrets document](/docs/user-guide/secrets), [example](/docs/user-guide/secrets/) and [design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/secrets.md).
 
 ## Authenticating with a private image registry
 
-Secrets can also be used to pass [image registry credentials](/{{page.version}}/docs/user-guide/images/#using-a-private-registry).
+Secrets can also be used to pass [image registry credentials](/docs/user-guide/images/#using-a-private-registry).
 
 First, create a `.dockercfg` file, such as running `docker login <registry.domain>`.
-Then put the resulting `.dockercfg` file into a [secret resource](/{{page.version}}/docs/user-guide/secrets).  For example:
+Then put the resulting `.dockercfg` file into a [secret resource](/docs/user-guide/secrets).  For example:
 
 ```shell
 $ docker login
@@ -159,7 +159,7 @@ spec:
 
 ## Helper containers
 
-[Pods](/{{page.version}}/docs/user-guide/pods) support running multiple containers co-located together. They can be used to host vertically integrated application stacks, but their primary motivation is to support auxiliary helper programs that assist the primary application. Typical examples are data pullers, data pushers, and proxies.
+[Pods](/docs/user-guide/pods) support running multiple containers co-located together. They can be used to host vertically integrated application stacks, but their primary motivation is to support auxiliary helper programs that assist the primary application. Typical examples are data pullers, data pushers, and proxies.
 
 Such containers typically need to communicate with one another, often through the file system. This can be achieved by mounting the same volume into both containers. An example of this pattern would be a web server with a [program that polls a git repository](http://releases.k8s.io/{{page.githubbranch}}/contrib/git-sync/) for new updates:
 
@@ -200,9 +200,9 @@ More examples can be found in our [blog article](http://blog.kubernetes.io/2015/
 
 ## Resource management
 
-Kubernetes's scheduler will place applications only where they have adequate CPU and memory, but it can only do so if it knows how much [resources they require](/{{page.version}}/docs/user-guide/compute-resources). The consequence of specifying too little CPU is that the containers could be starved of CPU if too many other containers were scheduled onto the same node. Similarly, containers could die unpredictably due to running out of memory if no memory were requested, which can be especially likely for large-memory applications.
+Kubernetes's scheduler will place applications only where they have adequate CPU and memory, but it can only do so if it knows how much [resources they require](/docs/user-guide/compute-resources). The consequence of specifying too little CPU is that the containers could be starved of CPU if too many other containers were scheduled onto the same node. Similarly, containers could die unpredictably due to running out of memory if no memory were requested, which can be especially likely for large-memory applications.
 
-If no resource requirements are specified, a nominal amount of resources is assumed. (This default is applied via a [LimitRange](/{{page.version}}/docs/admin/limitrange/) for the default [Namespace](/{{page.version}}/docs/user-guide/namespaces). It can be viewed with `kubectl describe limitrange limits`.) You may explicitly specify the amount of resources required as follows:
+If no resource requirements are specified, a nominal amount of resources is assumed. (This default is applied via a [LimitRange](/docs/admin/limitrange/) for the default [Namespace](/docs/user-guide/namespaces). It can be viewed with `kubectl describe limitrange limits`.) You may explicitly specify the amount of resources required as follows:
 
 ```yaml
 apiVersion: v1
@@ -236,11 +236,11 @@ spec:
 
 The container will die due to OOM (out of memory) if it exceeds its specified limit, so specifying a value a little higher than expected generally improves reliability. By specifying request, pod is guaranteed to be able to use that much of resource when needed. See [Resource QoS](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/proposals/resource-qos.md) for the difference between resource limits and requests.
 
-If you're not sure how much resources to request, you can first launch the application without specifying resources, and use [resource usage monitoring](/{{page.version}}/docs/user-guide/monitoring) to determine appropriate values.
+If you're not sure how much resources to request, you can first launch the application without specifying resources, and use [resource usage monitoring](/docs/user-guide/monitoring) to determine appropriate values.
 
 ## Liveness and readiness probes (aka health checks)
 
-Many applications running for long periods of time eventually transition to broken states, and cannot recover except by restarting them. Kubernetes provides [*liveness probes*](/{{page.version}}/docs/user-guide/pod-states/#container-probes) to detect and remedy such situations.
+Many applications running for long periods of time eventually transition to broken states, and cannot recover except by restarting them. Kubernetes provides [*liveness probes*](/docs/user-guide/pod-states/#container-probes) to detect and remedy such situations.
 
 A common way to probe an application is using HTTP, which can be specified as follows:
 
@@ -270,16 +270,16 @@ spec:
           timeoutSeconds: 1
 ```
 
-Other times, applications are only temporarily unable to serve, and will recover on their own. Typically in such cases you'd prefer not to kill the application, but don't want to send it requests, either, since the application won't respond correctly or at all. A common such scenario is loading large data or configuration files during application startup. Kubernetes provides *readiness probes* to detect and mitigate such situations. Readiness probes are configured similarly to liveness probes, just using the `readinessProbe` field. A pod with containers reporting that they are not ready will not receive traffic through Kubernetes [services](/{{page.version}}/docs/user-guide/connecting-applications).
+Other times, applications are only temporarily unable to serve, and will recover on their own. Typically in such cases you'd prefer not to kill the application, but don't want to send it requests, either, since the application won't respond correctly or at all. A common such scenario is loading large data or configuration files during application startup. Kubernetes provides *readiness probes* to detect and mitigate such situations. Readiness probes are configured similarly to liveness probes, just using the `readinessProbe` field. A pod with containers reporting that they are not ready will not receive traffic through Kubernetes [services](/docs/user-guide/connecting-applications).
 
-For more details (e.g., how to specify command-based probes), see the [example in the walkthrough](/{{page.version}}/docs/user-guide/walkthrough/k8s201/#health-checking), the [standalone example](/{{page.version}}/docs/user-guide/liveness/), and the [documentation](/{{page.version}}/docs/user-guide/pod-states/#container-probes).
+For more details (e.g., how to specify command-based probes), see the [example in the walkthrough](/docs/user-guide/walkthrough/k8s201/#health-checking), the [standalone example](/docs/user-guide/liveness/), and the [documentation](/docs/user-guide/pod-states/#container-probes).
 
 ## Lifecycle hooks and termination notice
 
 Of course, nodes and applications may fail at any time, but many applications benefit from clean shutdown, such as to complete in-flight requests, when the termination of the application is deliberate. To support such cases, Kubernetes supports two kinds of notifications:
 
 * Kubernetes will send SIGTERM to applications, which can be handled in order to effect graceful termination. SIGKILL is sent a configurable number of seconds later if the application does not terminate sooner (defaults to 30 seconds, controlled by `spec.terminationGracePeriodSeconds`).
-* Kubernetes supports the (optional) specification of a [*pre-stop lifecycle hook*](/{{page.version}}/docs/user-guide/container-environment/#container-hooks), which will execute prior to sending SIGTERM.
+* Kubernetes supports the (optional) specification of a [*pre-stop lifecycle hook*](/docs/user-guide/container-environment/#container-hooks), which will execute prior to sending SIGTERM.
 
 The specification of a pre-stop hook is similar to that of probes, but without the timing-related parameters. For example:
 
@@ -309,7 +309,7 @@ spec:
 
 ## Termination message
 
-In order to achieve a reasonably high level of availability, especially for actively developed applications, it's important to debug failures quickly. Kubernetes can speed debugging by surfacing causes of fatal errors in a way that can be display using [`kubectl`](/{{page.version}}/docs/user-guide/kubectl/kubectl) or the [UI](/{{page.version}}/docs/user-guide/ui), in addition to general [log collection](/{{page.version}}/docs/user-guide/logging). It is possible to specify a `terminationMessagePath` where a container will write its 'death rattle'?, such as assertion failure messages, stack traces, exceptions, and so on. The default path is `/dev/termination-log`.
+In order to achieve a reasonably high level of availability, especially for actively developed applications, it's important to debug failures quickly. Kubernetes can speed debugging by surfacing causes of fatal errors in a way that can be display using [`kubectl`](/docs/user-guide/kubectl/kubectl) or the [UI](/docs/user-guide/ui), in addition to general [log collection](/docs/user-guide/logging). It is possible to specify a `terminationMessagePath` where a container will write its 'death rattle'?, such as assertion failure messages, stack traces, exceptions, and so on. The default path is `/dev/termination-log`.
 
 Here is a toy example:
 
@@ -340,4 +340,4 @@ $ kubectl get pods/pod-w-message -o go-template="{{range .status.containerStatus
 
 ## What's next?
 
-[Learn more about managing deployments.](/{{page.version}}/docs/user-guide/managing-deployments)
+[Learn more about managing deployments.](/docs/user-guide/managing-deployments)
diff --git a/v1.2/docs/user-guide/quick-start.md b/docs/user-guide/quick-start.md
similarity index 83%
rename from v1.2/docs/user-guide/quick-start.md
rename to docs/user-guide/quick-start.md
index fd0c12a35d..3ce7f31110 100644
--- a/v1.2/docs/user-guide/quick-start.md
+++ b/docs/user-guide/quick-start.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-This guide will help you get oriented to Kubernetes and running your first containers on the cluster. If you are already familiar with the docker-cli, you can also checkout the docker-cli to kubectl migration guide [here](/{{page.version}}/docs/user-guide/docker-cli-to-kubectl).
+This guide will help you get oriented to Kubernetes and running your first containers on the cluster. If you are already familiar with the docker-cli, you can also checkout the docker-cli to kubectl migration guide [here](/docs/user-guide/docker-cli-to-kubectl).
 
 * TOC
 {:toc}
@@ -10,7 +10,7 @@ This guide will help you get oriented to Kubernetes and running your first conta
 
 Once your application is packaged into a container and pushed to an image registry, you're ready to deploy it to Kubernetes.
 
-For example, [nginx](http://wiki.nginx.org/Main) is a popular HTTP server, with a [pre-built container on Docker hub](https://registry.hub.docker.com/_/nginx/). The [`kubectl run`](/{{page.version}}/docs/user-guide/kubectl/kubectl_run) command below will create two nginx replicas, listening on port 80.
+For example, [nginx](http://wiki.nginx.org/Main) is a popular HTTP server, with a [pre-built container on Docker hub](https://registry.hub.docker.com/_/nginx/). The [`kubectl run`](/docs/user-guide/kubectl/kubectl_run) command below will create two nginx replicas, listening on port 80.
 
 ```shell
 $ kubectl run my-nginx --image=nginx --replicas=2 --port=80
@@ -48,7 +48,7 @@ my-nginx     10.179.240.1     25.1.2.3          80/TCP                 run=nginx
 
 You may need to wait for a minute or two for the external ip address to be provisioned.
 
-In order to access your nginx landing page, you also have to make sure that traffic from external IPs is allowed. Do this by opening a [firewall to allow traffic on port 80](/{{page.version}}/docs/user-guide/services-firewalls).
+In order to access your nginx landing page, you also have to make sure that traffic from external IPs is allowed. Do this by opening a [firewall to allow traffic on port 80](/docs/user-guide/services-firewalls).
 
 ## Killing the application
 
@@ -63,4 +63,4 @@ services/my-nginx
 
 ## What's next?
 
-[Learn about how to configure common container parameters, such as commands and environment variables.](/{{page.version}}/docs/user-guide/configuring-containers)
\ No newline at end of file
+[Learn about how to configure common container parameters, such as commands and environment variables.](/docs/user-guide/configuring-containers)
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/replication-controller.md b/docs/user-guide/replication-controller.md
similarity index 86%
rename from v1.2/docs/user-guide/replication-controller.md
rename to docs/user-guide/replication-controller.md
index 9e4c053b9a..722e0a2d58 100644
--- a/v1.2/docs/user-guide/replication-controller.md
+++ b/docs/user-guide/replication-controller.md
@@ -8,7 +8,7 @@
 
 A _replication controller_ ensures that a specified number of pod "replicas" are running at any one time.  If there are too many, it will kill some.  If there are too few, it will start more. Unlike in the case where a user directly created pods, a replication controller replaces pods that are deleted or terminated for any reason, such as in the case of node failure or disruptive node maintenance, such as a kernel upgrade. For this reason, we recommend that you use a replication controller even if your application requires only a single pod. Think of it similarly to a process supervisor, only it supervises multiple pods across multiple nodes instead of individual processes on a single node.  A replication controller delegates local container restarts to some agent on the node (e.g., Kubelet or Docker).
 
-As discussed in [life of a pod](/{{page.version}}/docs/user-guide/pod-states), `ReplicationController` is *only* appropriate for pods with `RestartPolicy = Always`. (Note: If `RestartPolicy` is not set, the default value is `Always`.)  `ReplicationController` should refuse to instantiate any pod that has a different restart policy. As discussed in [issue #503](http://issue.k8s.io/503#issuecomment-50169443), we expect other types of controllers to be added to Kubernetes to handle other types of workloads, such as build/test and batch workloads, in the future.
+As discussed in [life of a pod](/docs/user-guide/pod-states), `ReplicationController` is *only* appropriate for pods with `RestartPolicy = Always`. (Note: If `RestartPolicy` is not set, the default value is `Always`.)  `ReplicationController` should refuse to instantiate any pod that has a different restart policy. As discussed in [issue #503](http://issue.k8s.io/503#issuecomment-50169443), we expect other types of controllers to be added to Kubernetes to handle other types of workloads, such as build/test and batch workloads, in the future.
 
 A replication controller will never terminate on its own, but it isn't expected to be as long-lived as services. Services may be composed of pods controlled by multiple replication controllers, and it is expected that many replication controllers may be created and destroyed over the lifetime of a service (for instance, to perform an update of pods that run the service). Both services themselves and their clients should remain oblivious to the replication controllers that maintain the pods of the services.
 
@@ -24,7 +24,7 @@ Pods created by a replication controller are intended to be fungible and semanti
 
 ### Labels
 
-The population of pods that a replication controller is monitoring is defined with a [label selector](/{{page.version}}/docs/user-guide/labels/#label-selectors), which creates a loosely coupled relationship between the controller and the pods controlled, in contrast to pods, which are more tightly coupled to their definition. We deliberately chose not to represent the set of pods controlled using a fixed-length array of pod specifications, because our experience is that approach increases complexity of management operations, for both clients and the system.
+The population of pods that a replication controller is monitoring is defined with a [label selector](/docs/user-guide/labels/#label-selectors), which creates a loosely coupled relationship between the controller and the pods controlled, in contrast to pods, which are more tightly coupled to their definition. We deliberately chose not to represent the set of pods controlled using a fixed-length array of pod specifications, because our experience is that approach increases complexity of management operations, for both clients and the system.
 
 The replication controller should verify that the pods created from the specified template have labels that match its label selector. Though it isn't verified yet, you should also ensure that only one replication controller controls any given pod, by ensuring that the label selectors of replication controllers do not target overlapping sets. If you do end up with multiple controllers that have overlapping selectors, you will have to manage the deletion yourself with --cascade=false until there are no controllers with an overlapping superset of selectors.
 
@@ -32,7 +32,7 @@ Note that replication controllers may themselves have labels and would generally
 
 Pods may be removed from a replication controller's target set by changing their labels. This technique may be used to remove pods from service for debugging, data recovery, etc. Pods that are removed in this way will be replaced automatically (assuming that the number of replicas is not also changed).
 
-Similarly, deleting a replication controller using the API does not affect the pods it created. Its `replicas` field must first be set to `0` in order to delete the pods controlled. (Note that the client tool, `kubectl`, provides a single operation, [delete](/{{page.version}}/docs/user-guide/kubectl/kubectl_delete) to delete both the replication controller and the pods it controls. If you want to leave the pods running when deleting a replication controller, specify `--cascade=false`. However, there is no such operation in the API at the moment)
+Similarly, deleting a replication controller using the API does not affect the pods it created. Its `replicas` field must first be set to `0` in order to delete the pods controlled. (Note that the client tool, `kubectl`, provides a single operation, [delete](/docs/user-guide/kubectl/kubectl_delete) to delete both the replication controller and the pods it controls. If you want to leave the pods running when deleting a replication controller, specify `--cascade=false`. However, there is no such operation in the API at the moment)
 
 ## Responsibilities of the replication controller
 
@@ -63,7 +63,7 @@ Ideally, the rolling update controller would take application readiness into acc
 The two replication controllers would need to create pods with at least one differentiating label, such as the image tag of the primary container of the pod, since it is typically image updates that motivate rolling updates.
 
 Rolling update is implemented in the client tool
-[kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update)
+[kubectl](/docs/user-guide/kubectl/kubectl_rolling-update)
 
 ### Multiple release tracks
 
diff --git a/v1.1/docs/user-guide/replication.yaml b/docs/user-guide/replication.yaml
similarity index 100%
rename from v1.1/docs/user-guide/replication.yaml
rename to docs/user-guide/replication.yaml
diff --git a/docs/user-guide/resourcequota/index.md b/docs/user-guide/resourcequota/index.md
new file mode 100644
index 0000000000..07f6f3ea8e
--- /dev/null
+++ b/docs/user-guide/resourcequota/index.md
@@ -0,0 +1,6 @@
+---
+---
+
+This page has been moved to [here](/docs/admin/resourcequota/)
+
+
diff --git a/v1.2/docs/user-guide/secrets.md b/docs/user-guide/secrets.md
similarity index 95%
rename from v1.2/docs/user-guide/secrets.md
rename to docs/user-guide/secrets.md
index fa6de0b769..cf2eab61aa 100644
--- a/v1.2/docs/user-guide/secrets.md
+++ b/docs/user-guide/secrets.md
@@ -19,7 +19,7 @@ more control over how it is used, and reduces the risk of accidental exposure.
 Users can create secrets, and the system also creates some secrets.
 
 To use a secret, a pod needs to reference the secret.
-A secret can be used with a pod in two ways: either as files in a [volume](/{{page.version}}/docs/user-guide/volumes) mounted on one or more of
+A secret can be used with a pod in two ways: either as files in a [volume](/docs/user-guide/volumes) mounted on one or more of
 its containers, or used by kubelet when pulling images for the pod.
 
 ### Service Accounts Automatically Create and Attach Secrets with API Credentials
@@ -32,7 +32,7 @@ The automatic creation and use of API credentials can be disabled or overridden
 if desired.  However, if all you need to do is securely access the apiserver,
 this is the recommended workflow.
 
-See the [Service Account](/{{page.version}}/docs/user-guide/service-accounts) documentation for more
+See the [Service Account](/docs/user-guide/service-accounts) documentation for more
 information on how Service Accounts work.
 
 ### Creating a Secret Manually
@@ -56,7 +56,7 @@ allowed.  The values are arbitrary data, encoded using base64. The values of
 username and password in the example above, before base64 encoding,
 are `value-1` and `value-2`, respectively, with carriage return and newline characters at the end.
 
-Create the secret using [`kubectl create`](/{{page.version}}/docs/user-guide/kubectl/kubectl_create).
+Create the secret using [`kubectl create`](/docs/user-guide/kubectl/kubectl_create).
 
 Once the secret is created, you can need to modify your pod to specify
 that it should use the secret.
@@ -101,11 +101,11 @@ own `volumeMounts` block, but only one `spec.volumes` is needed per secret.
 You can package many files into one secret, or use many secrets,
 whichever is convenient.
 
-See another example of creating a secret and a pod that consumes that secret in a volume [here](/{{page.version}}/docs/user-guide/secrets/).
+See another example of creating a secret and a pod that consumes that secret in a volume [here](/docs/user-guide/secrets/).
 
 ### Manually specifying an imagePullSecret
 
-Use of imagePullSecrets is described in the [images documentation](/{{page.version}}/docs/user-guide/images/#specifying-imagepullsecrets-on-a-pod)
+Use of imagePullSecrets is described in the [images documentation](/docs/user-guide/images/#specifying-imagepullsecrets-on-a-pod)
 
 ### Arranging for imagePullSecrets to be Automatically Attached
 
@@ -113,7 +113,7 @@ You can manually create an imagePullSecret, and reference it from
 a serviceAccount.  Any pods created with that serviceAccount
 or that default to use that serviceAccount, will get have the imagePullSecret of the
 field set to that of the service account.
-See [here](/{{page.version}}/docs/user-guide/service-accounts/#adding-imagepullsecrets-to-a-service-account)
+See [here](/docs/user-guide/service-accounts/#adding-imagepullsecrets-to-a-service-account)
  for a detailed explanation of that process.
 
 
@@ -187,9 +187,9 @@ change, even if the secret resource is modified.  To change the secret used,
 the original pod must be deleted, and a new pod (perhaps with an identical
 `PodSpec`) must be created.  Therefore, updating a secret follows the same
 workflow as deploying a new container image.  The `kubectl rolling-update`
-command can be used ([man page](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update)).
+command can be used ([man page](/docs/user-guide/kubectl/kubectl_rolling-update)).
 
-The [`resourceVersion`](/{{page.version}}/docs/devel/api-conventions/#concurrency-control-and-consistency)
+The [`resourceVersion`](/docs/devel/api-conventions/#concurrency-control-and-consistency)
 of the secret is not specified when it is referenced.
 Therefore, if a secret is updated at about the same time as pods are starting,
 then it is not defined which version of the secret will be used for the pod. It
diff --git a/v1.1/docs/user-guide/secrets/index.md b/docs/user-guide/secrets/index.md
similarity index 62%
rename from v1.1/docs/user-guide/secrets/index.md
rename to docs/user-guide/secrets/index.md
index aa4b229dfd..3f17f1aa20 100644
--- a/v1.1/docs/user-guide/secrets/index.md
+++ b/docs/user-guide/secrets/index.md
@@ -1,19 +1,19 @@
 ---
 ---
 
-Following this example, you will create a secret and a [pod](/{{page.version}}/docs/user-guide/pods/) that consumes that secret in a [volume](/{{page.version}}/docs/user-guide/volumes/). See [Secrets design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/secrets.md) for more information.
+Following this example, you will create a secret and a [pod](/docs/user-guide/pods/) that consumes that secret in a [volume](/docs/user-guide/volumes/). See [Secrets design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/secrets.md) for more information.
 
 ## Step Zero: Prerequisites
 
 This example assumes you have a Kubernetes cluster installed and running, and that you have
 installed the `kubectl` command line tool somewhere in your path. Please see the [getting
-started](/{{page.version}}/docs/getting-started-guides/) for installation instructions for your platform.
+started](/docs/getting-started-guides/) for installation instructions for your platform.
 
 ## Step One: Create the secret
 
 A secret contains a set of named byte arrays.
 
-Use the [`examples/secrets/secret.yaml`](/{{page.version}}/docs/user-guide/secrets/secret.yaml) file to create a secret:
+Use the [`examples/secrets/secret.yaml`](/docs/user-guide/secrets/secret.yaml) file to create a secret:
 
 ```shell
 $ kubectl create -f docs/user-guide/secrets/secret.yaml
@@ -44,7 +44,7 @@ data-2: 11 bytes
 Pods consume secrets in volumes.  Now that you have created a secret, you can create a pod that
 consumes it.
 
-Use the [`examples/secrets/secret-pod.yaml`](/{{page.version}}/docs/user-guide/secrets/secret-pod.yaml) file to create a Pod that consumes the secret.
+Use the [`examples/secrets/secret-pod.yaml`](/docs/user-guide/secrets/secret-pod.yaml) file to create a Pod that consumes the secret.
 
 ```shell
 $ kubectl create -f docs/user-guide/secrets/secret-pod.yaml
diff --git a/v1.1/docs/user-guide/secrets/secret-pod.yaml b/docs/user-guide/secrets/secret-pod.yaml
similarity index 100%
rename from v1.1/docs/user-guide/secrets/secret-pod.yaml
rename to docs/user-guide/secrets/secret-pod.yaml
diff --git a/v1.1/docs/user-guide/secrets/secret.yaml b/docs/user-guide/secrets/secret.yaml
similarity index 100%
rename from v1.1/docs/user-guide/secrets/secret.yaml
rename to docs/user-guide/secrets/secret.yaml
diff --git a/v1.1/docs/user-guide/security-context.md b/docs/user-guide/security-context.md
similarity index 100%
rename from v1.1/docs/user-guide/security-context.md
rename to docs/user-guide/security-context.md
diff --git a/v1.2/docs/user-guide/service-accounts.md b/docs/user-guide/service-accounts.md
similarity index 94%
rename from v1.2/docs/user-guide/service-accounts.md
rename to docs/user-guide/service-accounts.md
index b36355bcda..be38e8c377 100644
--- a/v1.2/docs/user-guide/service-accounts.md
+++ b/docs/user-guide/service-accounts.md
@@ -4,7 +4,7 @@
 A service account provides an identity for processes that run in a Pod.
 
 *This is a user introduction to Service Accounts.  See also the
-[Cluster Admin Guide to Service Accounts](/{{page.version}}/docs/admin/service-accounts-admin).*
+[Cluster Admin Guide to Service Accounts](/docs/admin/service-accounts-admin).*
 
 *Note: This document describes how service accounts behave in a cluster set up
 as recommended by the Kubernetes project.  Your cluster administrator may have
@@ -27,7 +27,7 @@ pods/podname -o yaml`), you can see the `spec.serviceAccount` field has been
 [automatically set](working-with-resources/#resources-are-automatically-modified).
 
 You can access the API using a proxy or with a client library, as described in
-[Accessing the Cluster](/{{page.version}}/docs/user-guide/accessing-the-cluster/#accessing-the-api-from-a-pod).
+[Accessing the Cluster](/docs/user-guide/accessing-the-cluster/#accessing-the-api-from-a-pod).
 
 ## Using Multiple Service Accounts.
 
@@ -130,7 +130,7 @@ token:
 
 ## Adding ImagePullSecrets to a service account
 
-First, create an imagePullSecret, as described [here](/{{page.version}}/docs/user-guide/images/#specifying-imagepullsecrets-on-a-pod)
+First, create an imagePullSecret, as described [here](/docs/user-guide/images/#specifying-imagepullsecrets-on-a-pod)
 Next, verify it has been created.  For example:
 
 ```shell
diff --git a/v1.1/docs/user-guide/services-firewalls.md b/docs/user-guide/services-firewalls.md
similarity index 100%
rename from v1.1/docs/user-guide/services-firewalls.md
rename to docs/user-guide/services-firewalls.md
diff --git a/v1.2/docs/user-guide/services.md b/docs/user-guide/services.md
similarity index 97%
rename from v1.2/docs/user-guide/services.md
rename to docs/user-guide/services.md
index abf509ae74..372f2a5a7f 100644
--- a/v1.2/docs/user-guide/services.md
+++ b/docs/user-guide/services.md
@@ -1,10 +1,10 @@
 ---
 ---
 
-Kubernetes [`Pods`](/{{page.version}}/docs/user-guide/pods) are mortal. They are born and they die, and they
-are not resurrected.  [`ReplicationControllers`](/{{page.version}}/docs/user-guide/replication-controller) in
+Kubernetes [`Pods`](/docs/user-guide/pods) are mortal. They are born and they die, and they
+are not resurrected.  [`ReplicationControllers`](/docs/user-guide/replication-controller) in
 particular create and destroy `Pods` dynamically (e.g. when scaling up or down
-or when doing [rolling updates](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update)).  While each `Pod` gets its own IP address, even
+or when doing [rolling updates](/docs/user-guide/kubectl/kubectl_rolling-update)).  While each `Pod` gets its own IP address, even
 those IP addresses cannot be relied upon to be stable over time. This leads to
 a problem: if some set of `Pods` (let's call them backends) provides
 functionality to other `Pods` (let's call them frontends) inside the Kubernetes
@@ -16,7 +16,7 @@ Enter `Services`.
 A Kubernetes `Service` is an abstraction which defines a logical set of `Pods`
 and a policy by which to access them - sometimes called a micro-service.  The
 set of `Pods` targeted by a `Service` is (usually) determined by a [`Label
-Selector`](/{{page.version}}/docs/user-guide/labels/#label-selectors) (see below for why you might want a
+Selector`](/docs/user-guide/labels/#label-selectors) (see below for why you might want a
 `Service` without a selector).
 
 As an example, consider an image-processing backend which is running with 3
@@ -89,7 +89,7 @@ abstract other kinds of backends.  For example:
   * You want to have an external database cluster in production, but in test
     you use your own databases.
   * You want to point your service to a service in another
-    [`Namespace`](/{{page.version}}/docs/user-guide/namespaces) or on another cluster.
+    [`Namespace`](/docs/user-guide/namespaces) or on another cluster.
   * You are migrating your workload to Kubernetes and some of your backends run
     outside of Kubernetes.
 
@@ -528,4 +528,4 @@ of which `Pods` they are actually accessing.
 
 Service is a top-level resource in the kubernetes REST API. More details about the
 API object can be found at: [Service API
-object](/{{page.version}}/docs/api-reference/v1/definitions/#_v1_service).
\ No newline at end of file
+object](/docs/api-reference/v1/definitions/#_v1_service).
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/sharing-clusters.md b/docs/user-guide/sharing-clusters.md
similarity index 91%
rename from v1.1/docs/user-guide/sharing-clusters.md
rename to docs/user-guide/sharing-clusters.md
index 01d96b063e..9db2460ed2 100644
--- a/v1.1/docs/user-guide/sharing-clusters.md
+++ b/docs/user-guide/sharing-clusters.md
@@ -2,7 +2,7 @@
 ---
 
 Client access to a running Kubernetes cluster can be shared by copying
-the `kubectl` client config bundle ([kubeconfig](/{{page.version}}/docs/user-guide/kubeconfig-file)).
+the `kubectl` client config bundle ([kubeconfig](/docs/user-guide/kubeconfig-file)).
 This config bundle lives in `$HOME/.kube/config`, and is generated
 by `cluster/kube-up.sh`. Sample steps for sharing `kubeconfig` below.
 
@@ -89,7 +89,7 @@ $ export KUBECONFIG=/path/to/standalone/.kube/config
 kube master at cluster turnup. They can be found on the master under
 `/srv/kubernetes`. Bearer token/basic auth are also generated on the kube master.
 
-For more details on `kubeconfig` see [kubeconfig-file.md](/{{page.version}}/docs/user-guide/kubeconfig-file),
+For more details on `kubeconfig` see [kubeconfig-file.md](/docs/user-guide/kubeconfig-file),
 and/or run `kubectl config -h`.
 
 ## Merging `kubeconfig` Example
@@ -116,4 +116,4 @@ $ scp host2:/path/to/home2/.kube/config /path/to/other/.kube/config
 $ export $KUBECONFIG=/path/to/other/.kube/config
 ```
 
-Detailed examples and explanation of `kubeconfig` loading/merging rules can be found in [kubeconfig-file](/{{page.version}}/docs/user-guide/kubeconfig-file).
\ No newline at end of file
+Detailed examples and explanation of `kubeconfig` loading/merging rules can be found in [kubeconfig-file](/docs/user-guide/kubeconfig-file).
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/simple-nginx.md b/docs/user-guide/simple-nginx.md
similarity index 71%
rename from v1.1/docs/user-guide/simple-nginx.md
rename to docs/user-guide/simple-nginx.md
index 225b056429..56cde57aa5 100644
--- a/v1.1/docs/user-guide/simple-nginx.md
+++ b/docs/user-guide/simple-nginx.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-Ok, you've run one of the [getting started guides](/{{page.version}}/docs/getting-started-guides/) and you have
+Ok, you've run one of the [getting started guides](/docs/getting-started-guides/) and you have
 successfully turned up a Kubernetes cluster.  Now what?  This guide will help you get oriented
 to Kubernetes and running your first containers on the cluster.
 
@@ -9,7 +9,7 @@ to Kubernetes and running your first containers on the cluster.
 
 From this point onwards, it is assumed that `kubectl` is on your path from one of the getting started guides.
 
-The [`kubectl run`](/{{page.version}}/docs/user-guide/kubectl/kubectl_run) line below will create two [nginx](https://registry.hub.docker.com/_/nginx/) [pods](/{{page.version}}/docs/user-guide/pods) listening on port 80. It will also create a [replication controller](/{{page.version}}/docs/user-guide/replication-controller) named `my-nginx` to ensure that there are always two pods running.
+The [`kubectl run`](/docs/user-guide/kubectl/kubectl_run) line below will create two [nginx](https://registry.hub.docker.com/_/nginx/) [pods](/docs/user-guide/pods) listening on port 80. It will also create a [replication controller](/docs/user-guide/replication-controller) named `my-nginx` to ensure that there are always two pods running.
 
 ```shell
 kubectl run my-nginx --image=nginx --replicas=2 --port=80
@@ -35,7 +35,7 @@ kubectl stop rc my-nginx
 
 ### Exposing your pods to the internet.
 
-On some platforms (for example Google Compute Engine) the kubectl command can integrate with your cloud provider to add a [public IP address](/{{page.version}}/docs/user-guide/services/#external-services) for the pods,
+On some platforms (for example Google Compute Engine) the kubectl command can integrate with your cloud provider to add a [public IP address](/docs/user-guide/services/#external-services) for the pods,
 to do this run:
 
 ```shell
@@ -52,5 +52,5 @@ In order to access your nginx landing page, you also have to make sure that traf
 
 ### Next: Configuration files
 
-Most people will eventually want to use declarative configuration files for creating/modifying their applications.  A [simplified introduction](/{{page.version}}/docs/user-guide/simple-yaml)
+Most people will eventually want to use declarative configuration files for creating/modifying their applications.  A [simplified introduction](/docs/user-guide/simple-yaml)
 is given in a different document.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/simple-yaml.md b/docs/user-guide/simple-yaml.md
similarity index 87%
rename from v1.1/docs/user-guide/simple-yaml.md
rename to docs/user-guide/simple-yaml.md
index 165e7464b3..c5454ffaf4 100644
--- a/v1.1/docs/user-guide/simple-yaml.md
+++ b/docs/user-guide/simple-yaml.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-In addition to the imperative style commands described [elsewhere](/{{page.version}}/docs/user-guide/simple-nginx), Kubernetes
+In addition to the imperative style commands described [elsewhere](/docs/user-guide/simple-nginx), Kubernetes
 supports declarative YAML or JSON configuration files.  Often times config files are preferable
 to imperative commands, since they can be checked into version control and changes to the files
 can be code reviewed, producing a more robust, reliable and archival system.
@@ -32,7 +32,7 @@ spec:
     - containerPort: 80
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/pod.yaml)
+[Download example](/docs/user-guide/pod.yaml)
 <!-- END MUNGE: EXAMPLE pod.yaml -->
 
 You can see your cluster's pods:
@@ -49,7 +49,7 @@ $ kubectl delete pods nginx
 
 ### Running a replicated set of containers from a configuration file
 
-To run replicated containers, you need a [Replication Controller](/{{page.version}}/docs/user-guide/replication-controller).
+To run replicated containers, you need a [Replication Controller](/docs/user-guide/replication-controller).
 A replication controller is responsible for ensuring that a specific number of pods exist in the
 cluster.
 
@@ -84,7 +84,7 @@ spec:
         - containerPort: 80
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/replication.yaml)
+[Download example](/docs/user-guide/replication.yaml)
 <!-- END MUNGE: EXAMPLE replication.yaml -->
 
 To delete the replication controller (and the pods it created):
diff --git a/v1.1/docs/user-guide/ui.md b/docs/user-guide/ui.md
similarity index 100%
rename from v1.1/docs/user-guide/ui.md
rename to docs/user-guide/ui.md
diff --git a/v1.1/docs/user-guide/update-demo/build-images.sh b/docs/user-guide/update-demo/build-images.sh
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/build-images.sh
rename to docs/user-guide/update-demo/build-images.sh
diff --git a/v1.1/docs/user-guide/update-demo/images/kitten/Dockerfile b/docs/user-guide/update-demo/images/kitten/Dockerfile
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/images/kitten/Dockerfile
rename to docs/user-guide/update-demo/images/kitten/Dockerfile
diff --git a/v1.1/docs/user-guide/update-demo/images/kitten/html/data.json b/docs/user-guide/update-demo/images/kitten/html/data.json
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/images/kitten/html/data.json
rename to docs/user-guide/update-demo/images/kitten/html/data.json
diff --git a/v1.1/docs/user-guide/update-demo/images/kitten/html/kitten.jpg b/docs/user-guide/update-demo/images/kitten/html/kitten.jpg
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/images/kitten/html/kitten.jpg
rename to docs/user-guide/update-demo/images/kitten/html/kitten.jpg
diff --git a/v1.1/docs/user-guide/update-demo/images/nautilus/Dockerfile b/docs/user-guide/update-demo/images/nautilus/Dockerfile
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/images/nautilus/Dockerfile
rename to docs/user-guide/update-demo/images/nautilus/Dockerfile
diff --git a/v1.1/docs/user-guide/update-demo/images/nautilus/html/data.json b/docs/user-guide/update-demo/images/nautilus/html/data.json
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/images/nautilus/html/data.json
rename to docs/user-guide/update-demo/images/nautilus/html/data.json
diff --git a/v1.1/docs/user-guide/update-demo/images/nautilus/html/nautilus.jpg b/docs/user-guide/update-demo/images/nautilus/html/nautilus.jpg
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/images/nautilus/html/nautilus.jpg
rename to docs/user-guide/update-demo/images/nautilus/html/nautilus.jpg
diff --git a/v1.2/docs/user-guide/update-demo/index.md b/docs/user-guide/update-demo/index.md
similarity index 82%
rename from v1.2/docs/user-guide/update-demo/index.md
rename to docs/user-guide/update-demo/index.md
index 8879699f9f..cb84919a46 100644
--- a/v1.2/docs/user-guide/update-demo/index.md
+++ b/docs/user-guide/update-demo/index.md
@@ -19,11 +19,11 @@ limitations under the License.
 
 -->
 
-This example demonstrates the usage of Kubernetes to perform a [rolling update](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/user-guide/kubectl/kubectl_rolling-update.md) on a running group of [pods](/{{page.version}}/docs/user-guide/pods). See [here](/{{page.version}}/docs/user-guide/managing-deployments/#updating-your-application-without-a-service-outage) to understand why you need a rolling update. Also check [rolling update design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/simple-rolling-update.md) for more information.
+This example demonstrates the usage of Kubernetes to perform a [rolling update](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/user-guide/kubectl/kubectl_rolling-update.md) on a running group of [pods](/docs/user-guide/pods). See [here](/docs/user-guide/managing-deployments/#updating-your-application-without-a-service-outage) to understand why you need a rolling update. Also check [rolling update design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/simple-rolling-update.md) for more information.
 
 ### Step Zero: Prerequisites
 
-This example assumes that you have forked the repository and [turned up a Kubernetes cluster](/{{page.version}}/docs/getting-started-guides/):
+This example assumes that you have forked the repository and [turned up a Kubernetes cluster](/docs/getting-started-guides/):
 
 ```shell
 $ cd kubernetes
@@ -35,7 +35,7 @@ $ ./cluster/kube-up.sh
 You can use bash job control to run this in the background (note that you must use the default port -- 8001 -- for the following demonstration to work properly).
 This can sometimes spew to the output so you could also run it in a different terminal. You have to run `kubectl proxy` in the root of the
 Kubernetes repository. Otherwise you will get "404 page not found" errors as the paths will not match. You can find more information about `kubectl proxy`
-[here](/{{page.version}}/docs/user-guide/kubectl/kubectl_proxy).
+[here](/docs/user-guide/kubectl/kubectl_proxy).
 
 ```shell
 $ kubectl proxy --www=docs/user-guide/update-demo/local/ &
@@ -46,7 +46,7 @@ Now visit the the [demo website](http://localhost:8001/static).  You won't see a
 
 ### Step Two: Run the replication controller
 
-Now we will turn up two replicas of an [image](/{{page.version}}/docs/user-guide/images/).  They all serve on internal port 80.
+Now we will turn up two replicas of an [image](/docs/user-guide/images/).  They all serve on internal port 80.
 
 ```shell
 $ kubectl create -f docs/user-guide/update-demo/nautilus-rc.yaml
@@ -74,7 +74,7 @@ $ kubectl rolling-update update-demo-nautilus --update-period=10s -f docs/user-g
 
 The rolling-update command in kubectl will do 2 things:
 
-1. Create a new [replication controller](/{{page.version}}/docs/user-guide/replication-controller) with a pod template that uses the new image (`gcr.io/google_containers/update-demo:kitten`)
+1. Create a new [replication controller](/docs/user-guide/replication-controller) with a pod template that uses the new image (`gcr.io/google_containers/update-demo:kitten`)
 2. Scale the old and new replication controllers until the new controller replaces the old. This will kill the current pods one at a time, spinning up new ones to replace them.
 
 Watch the [demo website](http://localhost:8001/static/index), it will update one pod every 10 seconds until all of the pods have the new image.
diff --git a/v1.1/docs/user-guide/update-demo/kitten-rc.yaml b/docs/user-guide/update-demo/kitten-rc.yaml
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/kitten-rc.yaml
rename to docs/user-guide/update-demo/kitten-rc.yaml
diff --git a/v1.1/docs/user-guide/update-demo/local/LICENSE.angular b/docs/user-guide/update-demo/local/LICENSE.angular
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/local/LICENSE.angular
rename to docs/user-guide/update-demo/local/LICENSE.angular
diff --git a/v1.1/docs/user-guide/update-demo/local/angular.min.js b/docs/user-guide/update-demo/local/angular.min.js
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/local/angular.min.js
rename to docs/user-guide/update-demo/local/angular.min.js
diff --git a/v1.1/docs/user-guide/update-demo/local/angular.min.js.map b/docs/user-guide/update-demo/local/angular.min.js.map
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/local/angular.min.js.map
rename to docs/user-guide/update-demo/local/angular.min.js.map
diff --git a/v1.1/docs/user-guide/update-demo/local/index.html b/docs/user-guide/update-demo/local/index.html
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/local/index.html
rename to docs/user-guide/update-demo/local/index.html
diff --git a/v1.1/docs/user-guide/update-demo/local/script.js b/docs/user-guide/update-demo/local/script.js
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/local/script.js
rename to docs/user-guide/update-demo/local/script.js
diff --git a/v1.1/docs/user-guide/update-demo/local/style.css b/docs/user-guide/update-demo/local/style.css
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/local/style.css
rename to docs/user-guide/update-demo/local/style.css
diff --git a/v1.1/docs/user-guide/update-demo/nautilus-rc.yaml b/docs/user-guide/update-demo/nautilus-rc.yaml
similarity index 100%
rename from v1.1/docs/user-guide/update-demo/nautilus-rc.yaml
rename to docs/user-guide/update-demo/nautilus-rc.yaml
diff --git a/v1.1/docs/user-guide/volumes.md b/docs/user-guide/volumes.md
similarity index 95%
rename from v1.1/docs/user-guide/volumes.md
rename to docs/user-guide/volumes.md
index fe55dd38e2..d9afd2011a 100644
--- a/v1.1/docs/user-guide/volumes.md
+++ b/docs/user-guide/volumes.md
@@ -8,7 +8,7 @@ container starts with a clean slate.  Second, when running containers together
 in a `Pod` it is often necessary to share files between those containers.  The
 Kubernetes `Volume` abstraction solves both of these problems.
 
-Familiarity with [pods](/{{page.version}}/docs/user-guide/pods) is suggested.
+Familiarity with [pods](/docs/user-guide/pods) is suggested.
 
 * TOC
 {:toc}
@@ -345,16 +345,16 @@ non-volatile storage.
 __Important: You must create a secret in the Kubernetes API before you can use
 it__
 
-Secrets are described in more detail [here](/{{page.version}}/docs/user-guide/secrets).
+Secrets are described in more detail [here](/docs/user-guide/secrets).
 
 ### persistentVolumeClaim
 
 A `persistentVolumeClaim` volume is used to mount a
-[PersistentVolume](/{{page.version}}/docs/user-guide/persistent-volumes) into a pod.  PersistentVolumes are a
+[PersistentVolume](/docs/user-guide/persistent-volumes) into a pod.  PersistentVolumes are a
 way for users to "claim" durable storage (such as a GCE PersistentDisk or an
 iSCSI volume) without knowing the details of the particular cloud environment.
 
-See the [PersistentVolumes example](/{{page.version}}/docs/user-guide/persistent-volumes/) for more
+See the [PersistentVolumes example](/docs/user-guide/persistent-volumes/) for more
 details.
 
 ### downwardAPI
@@ -362,7 +362,7 @@ details.
 A `downwardAPI` volume is used to make downward API data available to applications.
 It mounts a directory and writes the requested data in plain text files.
 
-See the [`downwardAPI` volume example](/{{page.version}}/docs/user-guide/downward-api/volume/)  for more details.
+See the [`downwardAPI` volume example](/docs/user-guide/downward-api/volume/)  for more details.
 
 ## Resources
 
@@ -373,6 +373,6 @@ medium of the filesystem holding the kubelet root dir (typically
 pods.
 
 In the future, we expect that `emptyDir` and `hostPath` volumes will be able to
-request a certain amount of space using a [resource](/{{page.version}}/docs/user-guide/compute-resources)
+request a certain amount of space using a [resource](/docs/user-guide/compute-resources)
 specification, and to select the type of media to use, for clusters that have
 several media types.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/walkthrough/index.md b/docs/user-guide/walkthrough/index.md
similarity index 86%
rename from v1.1/docs/user-guide/walkthrough/index.md
rename to docs/user-guide/walkthrough/index.md
index 88d9417418..959d4e3d25 100644
--- a/v1.1/docs/user-guide/walkthrough/index.md
+++ b/docs/user-guide/walkthrough/index.md
@@ -11,17 +11,17 @@ In order for the kubectl usage examples to work, make sure you have an examples
 
 ## Kubectl CLI
 
-The easiest way to interact with Kubernetes is via the [kubectl](/{{page.version}}/docs/user-guide/kubectl-overview/) command-line interface.
+The easiest way to interact with Kubernetes is via the [kubectl](/docs/user-guide/kubectl-overview/) command-line interface.
 
-For more info about kubectl, including its usage, commands, and parameters, see the [kubectl CLI reference](/{{page.version}}/docs/user-guide/kubectl-overview/).
+For more info about kubectl, including its usage, commands, and parameters, see the [kubectl CLI reference](/docs/user-guide/kubectl-overview/).
 
-If you haven't installed and configured kubectl, finish the [prerequisites](/{{page.version}}/docs/user-guide/prereqs/) before continuing.
+If you haven't installed and configured kubectl, finish the [prerequisites](/docs/user-guide/prereqs/) before continuing.
 
 ## Pods
 
 In Kubernetes, a group of one or more containers is called a _pod_. Containers in a pod are deployed together, and are started, stopped, and replicated as a group.
 
-See [pods](/{{page.version}}/docs/user-guide/pods/) for more details.
+See [pods](/docs/user-guide/pods/) for more details.
 
 
 #### Pod Definition
@@ -48,7 +48,7 @@ See the [design document](https://github.com/kubernetes/kubernetes/blob/{{page.g
 
 #### Pod Management
 
-Create a pod containing an nginx server ([pod-nginx.yaml](/{{page.version}}/docs/user-guide/walkthrough/pod-nginx.yaml)):
+Create a pod containing an nginx server ([pod-nginx.yaml](/docs/user-guide/walkthrough/pod-nginx.yaml)):
 
 ```shell
 $ kubectl create -f docs/user-guide/walkthrough/pod-nginx.yaml
@@ -60,7 +60,7 @@ List all pods:
 $ kubectl get pods
 ```
 
-On most providers, the pod IPs are not externally accessible. The easiest way to test that the pod is working is to create a busybox pod and exec commands on it remotely. See the [command execution documentation](/{{page.version}}/docs/user-guide/getting-into-containers/) for details.
+On most providers, the pod IPs are not externally accessible. The easiest way to test that the pod is working is to create a busybox pod and exec commands on it remotely. See the [command execution documentation](/docs/user-guide/getting-into-containers/) for details.
 
 Provided the pod IP is accessible, you should be able to access its http endpoint with curl on port 80:
 
@@ -100,7 +100,7 @@ volumeMounts:
       mountPath: /data/redis
 ```
 
-Example Redis pod definition with a persistent storage volume ([pod-redis.yaml](/{{page.version}}/docs/user-guide/walkthrough/pod-redis.yaml)):
+Example Redis pod definition with a persistent storage volume ([pod-redis.yaml](/docs/user-guide/walkthrough/pod-redis.yaml)):
 
 <!-- BEGIN MUNGE: EXAMPLE pod-redis.yaml -->
 
@@ -121,7 +121,7 @@ spec:
     emptyDir: {}
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/walkthrough/pod-redis.yaml)
+[Download example](/docs/user-guide/walkthrough/pod-redis.yaml)
 <!-- END MUNGE: EXAMPLE pod-redis.yaml -->
 
 Notes:
@@ -134,7 +134,7 @@ Notes:
 - **EmptyDir**: Creates a new directory that will persist across container failures and restarts.
 - **HostPath**: Mounts an existing directory on the node's file system (e.g. `/var/logs`).
 
-See [volumes](/{{page.version}}/docs/user-guide/volumes) for more details.
+See [volumes](/docs/user-guide/volumes) for more details.
 
 
 #### Multiple Containers
@@ -178,5 +178,5 @@ Finally, we have also introduced an environment variable to the `git-monitor` co
 
 ## What's Next?
 
-Continue on to [Kubernetes 201](/{{page.version}}/docs/user-guide/walkthrough/k8s201) or
+Continue on to [Kubernetes 201](/docs/user-guide/walkthrough/k8s201) or
 for a complete application see the [guestbook example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/)
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/walkthrough/k8s201.md b/docs/user-guide/walkthrough/k8s201.md
similarity index 82%
rename from v1.2/docs/user-guide/walkthrough/k8s201.md
rename to docs/user-guide/walkthrough/k8s201.md
index d9db253863..b7e028f6e6 100644
--- a/v1.2/docs/user-guide/walkthrough/k8s201.md
+++ b/docs/user-guide/walkthrough/k8s201.md
@@ -2,7 +2,7 @@
 ---
 
 
-If you went through [Kubernetes 101](/{{page.version}}/docs/user-guide/walkthrough/), you learned about kubectl, pods, volumes, and multiple containers.
+If you went through [Kubernetes 101](/docs/user-guide/walkthrough/), you learned about kubectl, pods, volumes, and multiple containers.
 For Kubernetes 201, we will pick up where 101 left off and cover some slightly more advanced topics in Kubernetes, related to application productionization, deployment and
 scaling.
 
@@ -22,7 +22,7 @@ labels:
     app: nginx
 ```
 
-For example, here is the nginx pod definition with labels ([pod-nginx-with-label.yaml](/{{page.version}}/docs/user-guide/walkthrough/pod-nginx-with-label.yaml)):
+For example, here is the nginx pod definition with labels ([pod-nginx-with-label.yaml](/docs/user-guide/walkthrough/pod-nginx-with-label.yaml)):
 
 <!-- BEGIN MUNGE: EXAMPLE pod-nginx-with-label.yaml -->
 
@@ -41,10 +41,10 @@ spec:
     - containerPort: 80
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/walkthrough/pod-nginx-with-label.yaml)
+[Download example](/docs/user-guide/walkthrough/pod-nginx-with-label.yaml)
 <!-- END MUNGE: EXAMPLE pod-nginx-with-label.yaml -->
 
-Create the labeled pod ([pod-nginx-with-label.yaml](/{{page.version}}/docs/user-guide/walkthrough/pod-nginx-with-label.yaml)):
+Create the labeled pod ([pod-nginx-with-label.yaml](/docs/user-guide/walkthrough/pod-nginx-with-label.yaml)):
 
 ```shell
 $ kubectl create -f docs/user-guide/walkthrough/pod-nginx-with-label.yaml
@@ -56,7 +56,7 @@ List all pods with the label `app=nginx`:
 $ kubectl get pods -l app=nginx
 ```
 
-For more information, see [Labels](/{{page.version}}/docs/user-guide/labels).
+For more information, see [Labels](/docs/user-guide/labels).
 They are a core concept used by two additional Kubernetes building blocks: Replication Controllers and Services.
 
 
@@ -66,7 +66,7 @@ OK, now you know how to make awesome, multi-container, labeled pods and you want
 
 Replication controllers are the objects to answer these questions.  A replication controller combines a template for pod creation (a "cookie-cutter" if you will) and a number of desired replicas, into a single Kubernetes object.  The replication controller also contains a label selector that identifies the set of objects managed by the replication controller.  The replication controller constantly measures the size of this set relative to the desired size, and takes action by creating or deleting pods.
 
-For example, here is a replication controller that instantiates two nginx pods ([replication-controller.yaml](/{{page.version}}/docs/user-guide/walkthrough/replication-controller.yaml)):
+For example, here is a replication controller that instantiates two nginx pods ([replication-controller.yaml](/docs/user-guide/walkthrough/replication-controller.yaml)):
 
 <!-- BEGIN MUNGE: EXAMPLE replication-controller.yaml -->
 
@@ -97,12 +97,12 @@ spec:
         - containerPort: 80
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/walkthrough/replication-controller.yaml)
+[Download example](/docs/user-guide/walkthrough/replication-controller.yaml)
 <!-- END MUNGE: EXAMPLE replication-controller.yaml -->
 
 #### Replication Controller Management
 
-Create an nginx replication controller ([replication-controller.yaml](/{{page.version}}/docs/user-guide/walkthrough/replication-controller.yaml)):
+Create an nginx replication controller ([replication-controller.yaml](/docs/user-guide/walkthrough/replication-controller.yaml)):
 
 ```shell
 $ kubectl create -f docs/user-guide/walkthrough/replication-controller.yaml
@@ -120,14 +120,14 @@ Delete the replication controller by name:
 $ kubectl delete rc nginx-controller
 ```
 
-For more information, see [Replication Controllers](/{{page.version}}/docs/user-guide/replication-controller).
+For more information, see [Replication Controllers](/docs/user-guide/replication-controller).
 
 
 ## Services
 
 Once you have a replicated set of pods, you need an abstraction that enables connectivity between the layers of your application.  For example, if you have a replication controller managing your backend jobs, you don't want to have to reconfigure your front-ends whenever you re-scale your backends.  Likewise, if the pods in your backends are scheduled (or rescheduled) onto different machines, you can't be required to re-configure your front-ends.  In Kubernetes, the service abstraction achieves these goals.  A service provides a way to refer to a set of pods (selected by labels) with a single static IP address. It may also provide load balancing, if supported by the provider.
 
-For example, here is a service that balances across the pods created in the previous nginx replication controller example ([service.yaml](/{{page.version}}/docs/user-guide/walkthrough/service.yaml)):
+For example, here is a service that balances across the pods created in the previous nginx replication controller example ([service.yaml](/docs/user-guide/walkthrough/service.yaml)):
 
 <!-- BEGIN MUNGE: EXAMPLE service.yaml -->
 
@@ -150,12 +150,12 @@ spec:
     app: nginx
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/walkthrough/service.yaml)
+[Download example](/docs/user-guide/walkthrough/service.yaml)
 <!-- END MUNGE: EXAMPLE service.yaml -->
 
 #### Service Management
 
-Create an nginx service ([service.yaml](/{{page.version}}/docs/user-guide/walkthrough/service.yaml)):
+Create an nginx service ([service.yaml](/docs/user-guide/walkthrough/service.yaml)):
 
 ```shell
 $ kubectl create -f docs/user-guide/walkthrough/service.yaml
@@ -167,7 +167,7 @@ List all services:
 $ kubectl get services
 ```
 
-On most providers, the service IPs are not externally accessible. The easiest way to test that the service is working is to create a busybox pod and exec commands on it remotely. See the [command execution documentation](/{{page.version}}/docs/user-guide/kubectl-overview/) for details.
+On most providers, the service IPs are not externally accessible. The easiest way to test that the service is working is to create a busybox pod and exec commands on it remotely. See the [command execution documentation](/docs/user-guide/kubectl-overview/) for details.
 
 Provided the service IP is accessible, you should be able to access its http endpoint with curl on port 80:
 
@@ -185,7 +185,7 @@ $ kubectl delete service nginx-service
 
 When created, each service is assigned a unique IP address.  This address is tied to the lifespan of the Service, and will not change while the Service is alive.  Pods can be configured to talk to the service, and know that communication to the service will be automatically load-balanced out to some pod that is a member of the set identified by the label selector in the Service.
 
-For more information, see [Services](/{{page.version}}/docs/user-guide/services/).
+For more information, see [Services](/docs/user-guide/services/).
 
 
 ## Health Checking
@@ -231,15 +231,15 @@ Kubelet to ensure that your application is operating correctly for a definition
 
 Currently, there are three types of application health checks that you can choose from:
 
-   * HTTP Health Checks - The Kubelet will call a web hook.  If it returns between 200 and 399, it is considered success, failure otherwise. See health check examples [here](/{{page.version}}/docs/user-guide/liveness/).
-   * Container Exec - The Kubelet will execute a command inside your container.  If it exits with status 0 it will be considered a success. See health check examples [here](/{{page.version}}/docs/user-guide/liveness/).
+   * HTTP Health Checks - The Kubelet will call a web hook.  If it returns between 200 and 399, it is considered success, failure otherwise. See health check examples [here](/docs/user-guide/liveness/).
+   * Container Exec - The Kubelet will execute a command inside your container.  If it exits with status 0 it will be considered a success. See health check examples [here](/docs/user-guide/liveness/).
    * TCP Socket - The Kubelet will attempt to open a socket to your container.  If it can establish a connection, the container is considered healthy, if it can't it is considered a failure.
 
 In all cases, if the Kubelet discovers a failure the container is restarted.
 
 The container health checks are configured in the `livenessProbe` section of your container config. There you can also specify an `initialDelaySeconds` that is a grace period from when the container is started to when health checks are performed, to enable your container to perform any necessary initialization.
 
-Here is an example config for a pod with an HTTP health check ([pod-with-http-healthcheck.yaml](/{{page.version}}/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml)):
+Here is an example config for a pod with an HTTP health check ([pod-with-http-healthcheck.yaml](/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml)):
 
 <!-- BEGIN MUNGE: EXAMPLE pod-with-http-healthcheck.yaml -->
 
@@ -266,10 +266,10 @@ spec:
     - containerPort: 80
 ```
 
-[Download example](/{{page.version}}/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml)
+[Download example](/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml)
 <!-- END MUNGE: EXAMPLE pod-with-http-healthcheck.yaml -->
 
-For more information about health checking, see [Container Probes](/{{page.version}}/docs/user-guide/pod-states/#container-probes).
+For more information about health checking, see [Container Probes](/docs/user-guide/pod-states/#container-probes).
 
 
 ## What's Next?
diff --git a/v1.1/docs/user-guide/walkthrough/pod-nginx-with-label.yaml b/docs/user-guide/walkthrough/pod-nginx-with-label.yaml
similarity index 100%
rename from v1.1/docs/user-guide/walkthrough/pod-nginx-with-label.yaml
rename to docs/user-guide/walkthrough/pod-nginx-with-label.yaml
diff --git a/v1.1/docs/user-guide/walkthrough/pod-nginx.yaml b/docs/user-guide/walkthrough/pod-nginx.yaml
similarity index 100%
rename from v1.1/docs/user-guide/walkthrough/pod-nginx.yaml
rename to docs/user-guide/walkthrough/pod-nginx.yaml
diff --git a/v1.1/docs/user-guide/walkthrough/pod-redis.yaml b/docs/user-guide/walkthrough/pod-redis.yaml
similarity index 100%
rename from v1.1/docs/user-guide/walkthrough/pod-redis.yaml
rename to docs/user-guide/walkthrough/pod-redis.yaml
diff --git a/v1.1/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml b/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml
similarity index 100%
rename from v1.1/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml
rename to docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml
diff --git a/v1.1/docs/user-guide/walkthrough/podtemplate.json b/docs/user-guide/walkthrough/podtemplate.json
similarity index 100%
rename from v1.1/docs/user-guide/walkthrough/podtemplate.json
rename to docs/user-guide/walkthrough/podtemplate.json
diff --git a/v1.1/docs/user-guide/walkthrough/replication-controller.yaml b/docs/user-guide/walkthrough/replication-controller.yaml
similarity index 100%
rename from v1.1/docs/user-guide/walkthrough/replication-controller.yaml
rename to docs/user-guide/walkthrough/replication-controller.yaml
diff --git a/v1.1/docs/user-guide/walkthrough/service.yaml b/docs/user-guide/walkthrough/service.yaml
similarity index 100%
rename from v1.1/docs/user-guide/walkthrough/service.yaml
rename to docs/user-guide/walkthrough/service.yaml
diff --git a/v1.1/docs/user-guide/working-with-resources.md b/docs/user-guide/working-with-resources.md
similarity index 77%
rename from v1.1/docs/user-guide/working-with-resources.md
rename to docs/user-guide/working-with-resources.md
index bcd1ae2f7d..73d622a9c6 100644
--- a/v1.1/docs/user-guide/working-with-resources.md
+++ b/docs/user-guide/working-with-resources.md
@@ -5,8 +5,8 @@
 and who want to learn more about using kubectl to manage resources such
 as pods and services.  Users who want to access the REST API directly,
 and developers who want to extend the Kubernetes API should
-refer to the [api conventions](/{{page.version}}/docs/devel/api-conventions) and
-the [api document](/{{page.version}}/docs/api/).*
+refer to the [api conventions](/docs/devel/api-conventions) and
+the [api document](/docs/api/).*
 
 ## Resources are Automatically Modified
 
@@ -41,9 +41,9 @@ If you `diff -u /tmp/original.yaml /tmp/current.yaml`, you can see the fields ad
 The system adds fields in several ways:
 
   - Some fields are added synchronously with creation of the resource and some are set asynchronously.
-    - For example: `metadata.uid` is set synchronously.  (Read more about [metadata](/{{page.version}}/docs/devel/api-conventions/#metadata)).
-    - For example, `status.hostIP` is set only after the pod has been scheduled.  This often happens fast, but you may notice pods which do not have this set yet.  This is called Late Initialization.  (Read mode about [status](/{{page.version}}/docs/devel/api-conventions/#spec-and-status) and [late initialization](/{{page.version}}/docs/devel/api-conventions/#late-initialization) ).
-  - Some fields are set to default values.  Some defaults vary by cluster and some are fixed for the API at a certain version.  (Read more about [defaulting](/{{page.version}}/docs/devel/api-conventions/#defaulting)).
+    - For example: `metadata.uid` is set synchronously.  (Read more about [metadata](/docs/devel/api-conventions/#metadata)).
+    - For example, `status.hostIP` is set only after the pod has been scheduled.  This often happens fast, but you may notice pods which do not have this set yet.  This is called Late Initialization.  (Read mode about [status](/docs/devel/api-conventions/#spec-and-status) and [late initialization](/docs/devel/api-conventions/#late-initialization) ).
+  - Some fields are set to default values.  Some defaults vary by cluster and some are fixed for the API at a certain version.  (Read more about [defaulting](/docs/devel/api-conventions/#defaulting)).
     - For example, `spec.containers[0].imagePullPolicy` always defaults to `IfNotPresent` in api v1.
     - For example, `spec.containers[0].resources.limits.cpu` may be defaulted to  `100m` on some clusters, to some other value on others, and not defaulted at all on others.
     
@@ -51,4 +51,4 @@ The API will generally not modify fields that you have set; it just sets ones wh
 
 ## <a name="finding_schema_docs"></a>Finding Documentation on Resource Fields
 
-You can browse auto-generated API documentation at the [project website](/{{page.version}}/docs/api/) or on [github](https://releases.k8s.io/{{page.githubbranch}}/docs/api-reference).
\ No newline at end of file
+You can browse auto-generated API documentation at the [project website](/docs/api/) or on [github](https://releases.k8s.io/{{page.githubbranch}}/docs/api-reference).
\ No newline at end of file
diff --git a/v1.1/docs/whatisk8s.md b/docs/whatisk8s.md
similarity index 78%
rename from v1.1/docs/whatisk8s.md
rename to docs/whatisk8s.md
index 17cc03fefc..cb3b6f7cbc 100644
--- a/v1.1/docs/whatisk8s.md
+++ b/docs/whatisk8s.md
@@ -55,24 +55,24 @@ It can also do much more than that.
 
 Kubernetes satisfies a number of common needs of applications running in production, such as:
 
-* [co-locating helper processes](/{{page.version}}/docs/user-guide/pods),
-* [mounting storage systems](/{{page.version}}/docs/user-guide/volumes),
-* [distributing secrets](/{{page.version}}/docs/user-guide/secrets),
-* [application health checking](/{{page.version}}/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks),
-* [replicating application instances](/{{page.version}}/docs/user-guide/replication-controller),
-* [horizontal auto-scaling](/{{page.version}}/docs/user-guide/horizontal-pod-autoscaler),
-* [load balancing](/{{page.version}}/docs/user-guide/services),
-* [rolling updates](/{{page.version}}/docs/user-guide/update-demo/), and
-* [resource monitoring](/{{page.version}}/docs/user-guide/monitoring).
+* [co-locating helper processes](/docs/user-guide/pods/),
+* [mounting storage systems](/docs/user-guide/volumes/),
+* [distributing secrets](/docs/user-guide/secrets/),
+* [application health checking](/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks),
+* [replicating application instances](/docs/user-guide/replication-controller/),
+* [horizontal auto-scaling](/docs/user-guide/horizontal-pod-autoscaler/),
+* [load balancing](/docs/user-guide/services/),
+* [rolling updates](/docs/user-guide/update-demo/), and
+* [resource monitoring](/docs/user-guide/monitoring/).
 
 
 ## Why and how is Kubernetes a platform?
 
 Even though Kubernetes provides a lot of functionality, there are always new scenarios that would benefit from new features. Ad hoc orchestration that is acceptable initially often requires robust automation at scale. Application-specific workflows can be streamlined to accelerate developer velocity. This is why Kubernetes was also designed to serve as a platform for building an ecosystem of components and tools to make it easier to deploy, scale, and manage applications.
 
-[Labels](/{{page.version}}/docs/user-guide/labels) empower users to organize their resources however they please. [Annotations](/{{page.version}}/docs/user-guide/annotations) enable users to decorate resources with custom information to facilitate their workflows and provide an easy way for management tools to checkpoint state.
+[Labels](/docs/user-guide/labels/) empower users to organize their resources however they please. [Annotations](/docs/user-guide/annotations/) enable users to decorate resources with custom information to facilitate their workflows and provide an easy way for management tools to checkpoint state.
 
-Additionally, the [Kubernetes control plane](/{{page.version}}/docs/admin/cluster-components) is built upon the same [APIs](/{{page.version}}/docs/api/) that are available to developers and users. Users can write their own controllers, [schedulers](/{{page.version}}/docs/devel/scheduler), etc., if they choose, with [their own APIs](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/extending-api.md) that can be targeted by a general-purpose [command-line tool](/{{page.version}}/docs/user-guide/kubectl-overview).
+Additionally, the [Kubernetes control plane](/docs/admin/cluster-components) is built upon the same [APIs](/docs/api/) that are available to developers and users. Users can write their own controllers, [schedulers](/docs/devel/scheduler), etc., if they choose, with [their own APIs](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/extending-api.md) that can be targeted by a general-purpose [command-line tool](/docs/user-guide/kubectl-overview/).
 
 This [design](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/principles.md) has enabled a number of other systems to build atop Kubernetes.
 
diff --git a/v1.1/docs/admin/admission-controllers.md b/v1.1/docs/admin/admission-controllers.md
deleted file mode 100644
index ae0330ccaf..0000000000
--- a/v1.1/docs/admin/admission-controllers.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## What are they?
-
-An admission control plug-in is a piece of code that intercepts requests to the Kubernetes
-API server prior to persistence of the object, but after the request is authenticated
-and authorized.  The plug-in code is in the API server process
-and must be compiled into the binary in order to be used at this time.
-
-Each admission control plug-in is run in sequence before a request is accepted into the cluster.  If
-any of the plug-ins in the sequence reject the request, the entire request is rejected immediately
-and an error is returned to the end-user.
-
-Admission control plug-ins may mutate the incoming object in some cases to apply system configured
-defaults.  In addition, admission control plug-ins may mutate related resources as part of request
-processing to do things like increment quota usage.
-
-## Why do I need them?
-
-Many advanced features in Kubernetes require an admission control plug-in to be enabled in order
-to properly support the feature.  As a result, a Kubernetes API server that is not properly
-configured with the right set of admission control plug-ins is an incomplete server and will not
-support all the features you expect.
-
-## How do I turn on an admission control plug-in?
-
-The Kubernetes API server supports a flag, `admission-control` that takes a comma-delimited,
-ordered list of admission control choices to invoke prior to modifying objects in the cluster.
-
-## What does each plug-in do?
-
-### AlwaysAdmit
-
-Use this plugin by itself to pass-through all requests.
-
-### AlwaysDeny
-
-Rejects all requests.  Used for testing.
-
-### DenyExecOnPrivileged (deprecated)
-
-This plug-in will intercept all requests to exec a command in a pod if that pod has a privileged container.
-
-If your cluster supports privileged containers, and you want to restrict the ability of end-users to exec
-commands in those containers, we strongly encourage enabling this plug-in.
-
-This functionality has been merged into [DenyEscalatingExec](#denyescalatingexec).
-
-### DenyEscalatingExec
-
-This plug-in will deny exec and attach commands to pods that run with escalated privileges that
-allow host access.  This includes pods that run as privileged, have access to the host IPC namespace, and
-have access to the host PID namespace.
-
-If your cluster supports containers that run with escalated privileges, and you want to
-restrict the ability of end-users to exec commands in those containers, we strongly encourage
-enabling this plug-in.
-
-### ServiceAccount
-
-This plug-in implements automation for [serviceAccounts](/{{page.version}}/docs/user-guide/service-accounts).
-We strongly recommend using this plug-in if you intend to make use of Kubernetes `ServiceAccount` objects.
-
-### SecurityContextDeny
-
-This plug-in will deny any pod with a [SecurityContext](/{{page.version}}/docs/user-guide/security-context) that defines options that were not available on the `Container`.
-
-### ResourceQuota
-
-This plug-in will observe the incoming request and ensure that it does not violate any of the constraints
-enumerated in the `ResourceQuota` object in a `Namespace`.  If you are using `ResourceQuota`
-objects in your Kubernetes deployment, you MUST use this plug-in to enforce quota constraints.
-
-See the [resourceQuota design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_resource_quota.md) and the [example of Resource Quota](/{{page.version}}/docs/admin/resourcequota/) for more details.
-
-It is strongly encouraged that this plug-in is configured last in the sequence of admission control plug-ins.  This is
-so that quota is not prematurely incremented only for the request to be rejected later in admission control.
-
-### LimitRanger
-
-This plug-in will observe the incoming request and ensure that it does not violate any of the constraints
-enumerated in the `LimitRange` object in a `Namespace`.  If you are using `LimitRange` objects in
-your Kubernetes deployment, you MUST use this plug-in to enforce those constraints. LimitRanger can also
-be used to apply default resource requests to Pods that don't specify any; currently, the default LimitRanger
-applies a 0.1 CPU requirement to all Pods in the `default` namespace.
-
-See the [limitRange design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_limit_range.md) and the [example of Limit Range](/{{page.version}}/docs/admin/limitrange/) for more details.
-
-### InitialResources (experimental)
-
-This plug-in observes pod creation requests. If a container omits compute resource requests and limits,
-then the plug-in auto-populates a compute resource request based on historical usage of containers running the same image.
-If there is not enough data to make a decision the Request is left unchanged.
-When the plug-in sets a compute resource request, it annotates the pod with information on what compute resources it auto-populated.
-
-See the [InitialResouces proposal](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/proposals/initial-resources.md) for more details.
-
-### NamespaceExists (deprecated)
-
-This plug-in will observe all incoming requests that attempt to create a resource in a Kubernetes `Namespace`
-and reject the request if the `Namespace` was not previously created.  We strongly recommend running
-this plug-in to ensure integrity of your data.
-
-The functionality of this admission controller has been merged into `NamespaceLifecycle`
-
-### NamespaceAutoProvision (deprecated)
-
-This plug-in will observe all incoming requests that attempt to create a resource in a Kubernetes `Namespace`
-and create a new `Namespace` if one did not already exist previously.
-
-We strongly recommend `NamespaceLifecycle` over `NamespaceAutoProvision`.
-
-### NamespaceLifecycle
-
-This plug-in enforces that a `Namespace` that is undergoing termination cannot have new objects created in it,
-and ensures that requests in a non-existant `Namespace` are rejected.
-
-A `Namespace` deletion kicks off a sequence of operations that remove all objects (pods, services, etc.) in that
-namespace.  In order to enforce integrity of that process, we strongly recommend running this plug-in.
-
-## Is there a recommended set of plug-ins to use?
-
-Yes.
-
-For Kubernetes 1.0, we strongly recommend running the following set of admission control plug-ins (order matters):
-
-```shell
---admission-control=NamespaceLifecycle,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota
-```
diff --git a/v1.1/docs/admin/cluster-components.md b/v1.1/docs/admin/cluster-components.md
deleted file mode 100644
index 0aae00ff96..0000000000
--- a/v1.1/docs/admin/cluster-components.md
+++ /dev/null
@@ -1,142 +0,0 @@
----
----
-
-This document outlines the various binary components that need to run to
-deliver a functioning Kubernetes cluster.
-
-## Master Components
-
-Master components are those that provide the cluster's control plane. For
-example, master components are responsible for making global decisions about the
-cluster (e.g., scheduling), and detecting and responding to cluster events
-(e.g., starting up a new pod when a replication controller's 'replicas' field is
-unsatisfied).
-
-Master components could in theory be run on any node in the cluster. However,
-for simplicity, current set up scripts typically start all master components on
-the same VM, and does not run user containers on this VM. See
-[high-availability.md](/{{page.version}}/docs/admin/high-availability) for an example multi-master-VM setup.
-
-Even in the future, when Kubernetes is fully self-hosting, it will probably be
-wise to only allow master components to schedule on a subset of nodes, to limit
-co-running with user-run pods, reducing the possible scope of a
-node-compromising security exploit.
-
-### kube-apiserver
-
-[kube-apiserver](/{{page.version}}/docs/admin/kube-apiserver) exposes the Kubernetes API; it is the front-end for the
-Kubernetes control plane. It is designed to scale horizontally (i.e., one scales
-it by running more of them-- [high-availability.md](/{{page.version}}/docs/admin/high-availability)).
-
-### etcd
-
-[etcd](/{{page.version}}/docs/admin/etcd) is used as Kubernetes' backing store. All cluster data is stored here.
-Proper administration of a Kubernetes cluster includes a backup plan for etcd's
-data.
-
-### kube-controller-manager
-
-[kube-controller-manager](/{{page.version}}/docs/admin/kube-controller-manager) is a binary that runs controllers, which are the
-background threads that handle routine tasks in the cluster. Logically, each
-controller is a separate process, but to reduce the number of moving pieces in
-the system, they are all compiled into a single binary and run in a single
-process.
-
-These controllers include:
-
-* Node Controller
- * Responsible for noticing & responding when nodes go down.
-* Replication Controller
- * Responsible for maintaining the correct number of pods for every replication
-   controller object in the system.
-* Endpoints Controller
- * Populates the Endpoints object (i.e., join Services & Pods).
-* Service Account & Token Controllers
- * Create default accounts and API access tokens for new namespaces.
-* ... and others.
-
-### kube-scheduler
-
-[kube-scheduler](/{{page.version}}/docs/admin/kube-scheduler) watches newly created pods that have no node assigned, and
-selects a node for them to run on.
-
-### addons
-
-Addons are pods and services that implement cluster features. They don't run on
-the master VM, but currently the default setup scripts that make the API calls
-to create these pods and services does run on the master VM. See:
-[kube-master-addons](http://releases.k8s.io/HEAD/cluster/saltbase/salt/kube-master-addons/kube-master-addons.sh)
-
-Addon objects are created in the "kube-system" namespace.
-
-#### DNS
-
-While the other addons are not strictly required, all Kubernetes
-clusters should have [cluster DNS](dns.md), as many examples rely on it.
-
-Cluster DNS is a DNS server, in addition to the other DNS server(s) in your
-environment, which serves DNS records for Kubernetes services.
-
-Containers started by Kubernetes automatically include this DNS server
-in their DNS searches.
-
-#### User interface
-
-The kube-ui provides a read-only overview of the cluster state.  Access
-[the UI using kubectl proxy](/{{page.version}}/docs/user-guide/connecting-to-applications-proxy/#connecting-to-the-kube-ui-service-from-your-local-workstation)
-
-#### Container Resource Monitoring
-
-[Container Resource Monitoring](/{{page.version}}/docs/user-guide/monitoring) records generic time-series metrics
-about containers in a central database, and provides a UI for browsing that data.
-
-#### Cluster-level Logging
-
-[Container Logging](/{{page.version}}/docs/user-guide/monitoring.md) saves container logs
-to a central log store with search/browsing interface.  There are two
-implementations:
-
-* [Cluster-level logging to Google Cloud Logging](
-docs/user-guide/logging/#cluster-level-logging-to-google-cloud-logging)
-
-* [Cluster-level Logging with Elasticsearch and Kibana](
-docs/user-guide/logging/#cluster-level-logging-with-elasticsearch-and-kibana)
-
-## Node components
-
-Node components run on every node, maintaining running pods and providing them
-the Kubernetes runtime environment.
-
-### kubelet
-
-[kubelet](/{{page.version}}/docs/admin/kubelet) is the primary node agent. It:
-* Watches for pods that have been assigned to its node (either by apiserver
-  or via local configuration file) and:
- * Mounts the pod's required volumes
- * Downloads the pod's secrets
- * Run the pod's containers via docker (or, experimentally, rkt).
- * Periodically executes any requested container liveness probes.
- * Reports the status of the pod back to the rest of the system, by creating a
-   "mirror pod" if necessary.
-* Reports the status of the node back to the rest of the system.
-
-### kube-proxy
-
-[kube-proxy](/{{page.version}}/docs/admin/kube-proxy) enables the Kubernetes service abstraction by maintaining
-network rules on the host and performing connection forwarding.
-
-### docker
-
-`docker` is of course used for actually running containers.
-
-### rkt
-
-`rkt` is supported experimentally as an alternative to docker.
-
-### supervisord
-
-`supervisord` is a lightweight process babysitting system for keeping kubelet and docker
-running.
-
-
-
diff --git a/v1.1/docs/admin/cluster-large.md b/v1.1/docs/admin/cluster-large.md
deleted file mode 100644
index 6c3ade5a91..0000000000
--- a/v1.1/docs/admin/cluster-large.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
----
-
-
-## Support
-
-At v1.0, Kubernetes supports clusters up to 100 nodes with 30 pods per node and 1-2 containers per pod.
-
-* TOC
-{:toc}
-
-## Setup
-
-A cluster is a set of nodes (physical or virtual machines) running Kubernetes agents, managed by a "master" (the cluster-level control plane).
-
-Normally the number of nodes in a cluster is controlled by the the value `NUM_MINIONS` in the platform-specific `config-default.sh` file (for example, see [GCE's `config-default.sh`](http://releases.k8s.io/{{page.githubbranch}}/cluster/gce/config-default.sh)).
-
-Simply changing that value to something very large, however, may cause the setup script to fail for many cloud providers. A GCE deployment, for example, will run in to quota issues and fail to bring the cluster up.
-
-When setting up a large Kubernetes cluster, the following issues must be considered.
-
-### Quota Issues
-
-To avoid running into cloud provider quota issues, when creating a cluster with many nodes, consider:
-
-* Increase the quota for things like CPU, IPs, etc.
-  * In [GCE, for example,](https://cloud.google.com/compute/docs/resource-quotas) you'll want to increase the quota for:
-    * CPUs
-    * VM instances
-    * Total persistent disk reserved
-    * In-use IP addresses
-    * Firewall Rules
-    * Forwarding rules
-    * Routes
-    * Target pools
-* Gating the setup script so that it brings up new node VMs in smaller batches with waits in between, because some cloud providers rate limit the creation of VMs.
-
-### Addon Resources
-
-To prevent memory leaks or other resource issues in [cluster addons](https://releases.k8s.io/{{page.githubbranch}}/cluster/addons) from consuming all the resources available on a node, Kubernetes sets resource limits on addon containers to limit the CPU and Memory resources they can consume (See PR [#10653](http://pr.k8s.io/10653/files) and [#10778](http://pr.k8s.io/10778/files)).
-
-For example:
-
-```yaml
-containers:
-  - image: gcr.io/google_containers/heapster:v0.15.0
-    name: heapster
-    resources:
-      limits:
-        cpu: 100m
-        memory: 200Mi
-```
-
-These limits, however, are based on data collected from addons running on 4-node clusters (see [#10335](http://issue.k8s.io/10335#issuecomment-117861225)). The addons consume a lot more resources when running on large deployment clusters (see [#5880](http://issue.k8s.io/5880#issuecomment-113984085)). So, if a large cluster is deployed without adjusting these values, the addons may continuously get killed because they keep hitting the limits.
-
-To avoid running into cluster addon resource issues, when creating a cluster with many nodes, consider the following:
-
-- Scale memory and CPU limits for each of the following addons, if used, along with the size of cluster (there is one replica of each handling the entire cluster so memory and CPU usage tends to grow proportionally with size/load on cluster):
-  - Heapster ([GCM/GCL backed](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/google/heapster-controller.yaml), [InfluxDB backed](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/influxdb/heapster-controller.yaml), [InfluxDB/GCL backed](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/googleinfluxdb/heapster-controller-combined.yaml), [standalone](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/standalone/heapster-controller.yaml))
-  * [InfluxDB and Grafana](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/influxdb/influxdb-grafana-controller.yaml)
-  * [skydns, kube2sky, and dns etcd](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/skydns-rc.yaml.in)
-  * [Kibana](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/fluentd-elasticsearch/kibana-controller.yaml)
-* Scale number of replicas for the following addons, if used, along with the size of cluster (there are multiple replicas of each so increasing replicas should help handle increased load, but, since load per replica also increases slightly, also consider increasing CPU/memory limits):
-  * [elasticsearch](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/fluentd-elasticsearch/es-controller.yaml)
-* Increase memory and CPU limits slightly for each of the following addons, if used, along with the size of cluster (there is one replica per node but CPU/memory usage increases slightly along with cluster load/size as well):
-  * [FluentD with ElasticSearch Plugin](http://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/salt/fluentd-es/fluentd-es.yaml)
-  * [FluentD with GCP Plugin](http://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/salt/fluentd-gcp/fluentd-gcp.yaml)
-
-For directions on how to detect if addon containers are hitting resource limits, see the [Troubleshooting section of Compute Resources](/{{page.version}}/docs/user-guide/compute-resources/#troubleshooting).
\ No newline at end of file
diff --git a/v1.1/docs/admin/cluster-management.md b/v1.1/docs/admin/cluster-management.md
deleted file mode 100644
index 8f76f2b16c..0000000000
--- a/v1.1/docs/admin/cluster-management.md
+++ /dev/null
@@ -1,187 +0,0 @@
----
----
-
-This document describes several topics related to the lifecycle of a cluster: creating a new cluster,
-upgrading your cluster's
-master and worker nodes, performing node maintenance (e.g. kernel upgrades), and upgrading the Kubernetes API version of a
-running cluster.
-
-## Creating and configuring a Cluster
-
-To install Kubernetes on a set of machines, consult one of the existing [Getting Started guides](/{{page.version}}/docs/getting-started-guides/) depending on your environment.
-
-## Upgrading a cluster
-
-The current state of cluster upgrades is provider dependent.
-
-### Master Upgrades
-
-Both Google Container Engine (GKE) and
-Compute Engine Open Source (GCE-OSS) support node upgrades via a [Managed Instance Group](https://cloud.google.com/compute/docs/instance-groups/).
-Managed Instance Group upgrades sequentially delete and recreate each virtual machine, while maintaining the same
-Persistent Disk (PD) to ensure that data is retained across the upgrade.
-
-In contrast, the `kube-push.sh` process used on [other platforms](#other-platforms) attempts to upgrade the binaries in
-places, without recreating the virtual machines.
-
-### Node Upgrades
-
-Node upgrades for GKE and GCE-OSS again use a Managed Instance Group, each node is sequentially destroyed and then recreated with new software.  Any Pods that are running
-on that node need to be controlled by a Replication Controller, or manually re-created after the roll out.
-
-For other platforms, `kube-push.sh` is again used, performing an in-place binary upgrade on existing machines.
-
-### Upgrading Google Container Engine (GKE)
-
-Google Container Engine automatically updates master components (e.g. `kube-apiserver`, `kube-scheduler`) to the latest
-version. It also handles upgrading the operating system and other components that the master runs on.
-
-The node upgrade process is user-initiated and is described in the [GKE documentation.](https://cloud.google.com/container-engine/docs/clusters/upgrade)
-
-### Upgrading open source Google Compute Engine clusters
-
-Upgrades on open source Google Compute Engine (GCE) clusters are controlled by the `cluster/gce/upgrade.sh` script.
-
-Get its usage by running `cluster/gce/upgrade.sh -h`.
-
-For example, to upgrade just your master to a specific version (v1.0.2):
-
-```shell
-cluster/gce/upgrade.sh -M v1.0.2
-```
-
-Alternatively, to upgrade your entire cluster to the latest stable release:
-
-```shell
-cluster/gce/upgrade.sh release/stable
-```
-
-### Other platforms
-
-The `cluster/kube-push.sh` script will do a rudimentary update.  This process is still quite experimental, we
-recommend testing the upgrade on an experimental cluster before performing the update on a production cluster.
-
-## Resizing a cluster
-
-If your cluster runs short on resources you can easily add more machines to it if your cluster is running in [Node self-registration mode](/{{page.version}}/docs/admin/node/#self-registration-of-nodes).
-If you're using GCE or GKE it's done by resizing Instance Group managing your Nodes. It can be accomplished by modifying number of instances on `Compute > Compute Engine > Instance groups > your group > Edit group` [Google Cloud Console page](https://console.developers.google.com) or using gcloud CLI:
-
-```shell
-gcloud compute instance-groups managed --zone compute-zone resize my-cluster-minon-group --new-size 42
-```
-
-Instance Group will take care of putting appropriate image on new machines and start them, while Kubelet will register its Node with API server to make it available for scheduling. If you scale the instance group down, system will randomly choose Nodes to kill.
-
-In other environments you may need to configure the machine yourself and tell the Kubelet on which machine API server is running.
-
-
-### Horizontal auto-scaling of nodes (GCE)
-
-If you are using GCE, you can configure your cluster so that the number of nodes will be automatically scaled based on their CPU and memory utilization.
-Before setting up the cluster by `kube-up.sh`, you can set `KUBE_ENABLE_NODE_AUTOSCALE`
-environment variable to `true`
-and export it.
-The script will create an autoscaler for the instance group managing your nodes.
-
-The autoscaler will try to maintain the average CPU and memory utilization of nodes within the cluster close to the target value.
-The target value can be configured by `KUBE_TARGET_NODE_UTILIZATION`
-environment variable (default: 0.7) for `kube-up.sh` when creating the cluster.
-The node utilization is the total node's CPU/memory usage (OS + k8s + user load) divided by the node's capacity.
-If the desired numbers of nodes in the cluster resulting from CPU utilization and memory utilization are different,
-the autoscaler will choose the bigger number.
-The number of nodes in the cluster set by the autoscaler will be limited from `KUBE_AUTOSCALER_MIN_NODES`
-(default: 1)
-to `KUBE_AUTOSCALER_MAX_NODES`
-(default: the initial number of nodes in the cluster).
-
-The autoscaler is implemented as a Compute Engine Autoscaler.
-The initial values of the autoscaler parameters set by `kube-up.sh` and some more advanced options can be tweaked on
-`Compute > Compute Engine > Instance groups > your group > Edit group`[Google Cloud Console page](https://console.developers.google.com)
-or using gcloud CLI:
-
-```shell
-gcloud preview autoscaler --zone compute-zone <command>
-```
-
-Note that autoscaling will work properly only if node metrics are accessible in Google Cloud Monitoring. To make the metrics accessible, you need to create your cluster with `KUBE_ENABLE_CLUSTER_MONITORING` equal to `google` or `googleinfluxdb` (`googleinfluxdb` is the default value).
-
-## Maintenance on a Node
-
-If you need to reboot a node (such as for a kernel upgrade, libc upgrade, hardware repair, etc.), and the downtime is
-brief, then when the Kubelet restarts, it will attempt to restart the pods scheduled to it.  If the reboot takes longer,
-then the node controller will terminate the pods that are bound to the unavailable node.  If there is a corresponding
-replication controller, then a new copy of the pod will be started on a different node.  So, in the case where all
-pods are replicated, upgrades can be done without special coordination, assuming that not all nodes will go down at the same time.
-
-If you want more control over the upgrading process, you may use the following workflow:
-
-Mark the node to be rebooted as unschedulable:
-
-```shell
-kubectl replace nodes $NODENAME --patch='{"apiVersion": "v1", "spec": {"unschedulable": true}}'
-```
-
-This keeps new pods from landing on the node while you are trying to get them off.
-
-Get the pods off the machine, via any of the following strategies:
-   * Wait for finite-duration pods to complete.
-   * Delete pods with:
-
-```shell
-kubectl delete pods $PODNAME
-```
-
-For pods with a replication controller, the pod will eventually be replaced by a new pod which will be scheduled to a new node. Additionally, if the pod is part of a service, then clients will automatically be redirected to the new pod.
-
-For pods with no replication controller, you need to bring up a new copy of the pod, and assuming it is not part of a service, redirect clients to it.
-
-Perform maintenance work on the node.
-
-Make the node schedulable again:
-
-```shell
-kubectl replace nodes $NODENAME --patch='{"apiVersion": "v1", "spec": {"unschedulable": false}}'
-```
-
-If you deleted the node's VM instance and created a new one, then a new schedulable node resource will
-be created automatically when you create a new VM instance (if you're using a cloud provider that supports
-node discovery; currently this is only Google Compute Engine, not including CoreOS on Google Compute Engine using kube-register). See [Node](/{{page.version}}/docs/admin/node) for more details.
-
-## Advanced Topics
-
-### Upgrading to a different API version
-
-When a new API version is released, you may need to upgrade a cluster to support the new API version (e.g. switching from 'v1' to 'v2' when 'v2' is launched)
-
-This is an infrequent event, but it requires careful management. There is a sequence of steps to upgrade to a new API version.
-
-   1. Turn on the new api version.
-   1. Upgrade the cluster's storage to use the new version.
-   1. Upgrade all config files. Identify users of the old API version endpoints.
-   1. Update existing objects in the storage to new version by running `cluster/update-storage-objects.sh`.
-   1. Turn off the old API version.
-
-### Turn on or off an API version for your cluster
-
-Specific API versions can be turned on or off by passing --runtime-config=api/<version> flag while bringing up the API server. For example: to turn off v1 API, pass `--runtime-config=api/v1=false`.
-runtime-config also supports 2 special keys: api/all and api/legacy to control all and legacy APIs respectively.
-For example, for turning off all api versions except v1, pass `--runtime-config=api/all=false,api/v1=true`.
-For the purposes of these flags, _legacy_ APIs are those APIs which have been explicitly deprecated (e.g. `v1beta3`).
-
-### Switching your cluster's storage API version
-
-The objects that are stored to disk for a cluster's internal representation of the Kubernetes resources active in the cluster are written using a particular version of the API.
-When the supported API changes, these objects may need to be rewritten in the newer API.  Failure to do this will eventually result in resources that are no longer decodable or usable
-by the kubernetes API server.
-
-`KUBE_API_VERSIONS` environment variable for the `kube-apiserver` binary which controls the API versions that are supported in the cluster. The first version in the list is used as the cluster's storage version. Hence, to set a specific version as the storage version, bring it to the front of list of versions in the value of `KUBE_API_VERSIONS`.  You need to restart the `kube-apiserver` binary
-for changes to this variable to take effect.
-
-### Switching your config files to a new API version
-
-You can use the `kube-version-change` utility to convert config files between different API versions.
-
-```shell
-$ hack/build-go.sh cmd/kube-version-change
-$ _output/local/go/bin/kube-version-change -i myPod.v1beta3.yaml -o myPod.v1.yaml
-```
diff --git a/v1.1/docs/admin/index.md b/v1.1/docs/admin/index.md
deleted file mode 100644
index b9d0f41a33..0000000000
--- a/v1.1/docs/admin/index.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
----
-
-The cluster admin guide is for anyone creating or administering a Kubernetes cluster.
-It assumes some familiarity with concepts in the [User Guide](/{{page.version}}/docs/user-guide/).
-
-* TOC
-{:toc}
-
-## Planning a cluster
-
-There are many different examples of how to setup a kubernetes cluster.  Many of them are listed in this
-[matrix](/{{page.version}}/docs/getting-started-guides/).  We call each of the combinations in this matrix a *distro*.
-
-Before choosing a particular guide, here are some things to consider:
-
- - Are you just looking to try out Kubernetes on your laptop, or build a high-availability many-node cluster? Both
-   models are supported, but some distros are better for one case or the other.
- - Will you be using a hosted Kubernetes cluster, such as [GKE](https://cloud.google.com/container-engine), or setting
-   one up yourself?
- - Will your cluster be on-premises, or in the cloud (IaaS)?  Kubernetes does not directly support hybrid clusters.  We
-   recommend setting up multiple clusters rather than spanning distant locations.
- - Will you be running Kubernetes on "bare metal" or virtual machines?  Kubernetes supports both, via different distros.
- - Do you just want to run a cluster, or do you expect to do active development of kubernetes project code?  If the
-   latter, it is better to pick a distro actively used by other developers.  Some distros only use binary releases, but
-   offer is a greater variety of choices.
- - Not all distros are maintained as actively.  Prefer ones which are listed as tested on a more recent version of
-   Kubernetes.
- - If you are configuring kubernetes on-premises, you will need to consider what [networking
-   model](/{{page.version}}/docs/admin/networking) fits best.
- - If you are designing for very high-availability, you may want [clusters in multiple zones](/{{page.version}}/docs/admin/multi-cluster).
- - You may want to familiarize yourself with the various
-   [components](/{{page.version}}/docs/admin/cluster-components) needed to run a cluster.
-
-## Setting up a cluster
-
-Pick one of the Getting Started Guides from the [matrix](/{{page.version}}/docs/getting-started-guides/) and follow it.
-If none of the Getting Started Guides fits, you may want to pull ideas from several of the guides.
-
-One option for custom networking is *OpenVSwitch GRE/VxLAN networking* ([ovs-networking.md](/{{page.version}}/docs/admin/ovs-networking)), which
-uses OpenVSwitch to set up networking between pods across
-  Kubernetes nodes.
-
-If you are modifying an existing guide which uses Salt, this document explains [how Salt is used in the Kubernetes
-project](/{{page.version}}/docs/admin/salt).
-
-## Managing a cluster, including upgrades
-
-[Managing a cluster](/{{page.version}}/docs/admin/cluster-management).
-
-## Managing nodes
-
-[Managing nodes](/{{page.version}}/docs/admin/node).
-
-## Optional Cluster Services
-
-* **DNS Integration with SkyDNS** ([dns.md](/{{page.version}}/docs/admin/dns)):
-  Resolving a DNS name directly to a Kubernetes service.
-
-* **Logging** with [Kibana](/{{page.version}}/docs/user-guide/logging)
-
-## Multi-tenant support
-
-* **Resource Quota** ([resource-quota.md](/{{page.version}}/docs/admin/resource-quota))
-
-## Security
-
-* **Kubernetes Container Environment** ([docs/user-guide/container-environment.md](/{{page.version}}/docs/user-guide/container-environment)):
-  Describes the environment for Kubelet managed containers on a Kubernetes
-  node.
-
-* **Securing access to the API Server** [accessing the api](/{{page.version}}/docs/admin/accessing-the-api)
-
-* **Authentication**  [authentication](/{{page.version}}/docs/admin/authentication)
-
-* **Authorization** [authorization](/{{page.version}}/docs/admin/authorization)
-
-* **Admission Controllers** [admission_controllers](/{{page.version}}/docs/admin/admission-controllers)
\ No newline at end of file
diff --git a/v1.1/docs/admin/namespaces.md b/v1.1/docs/admin/namespaces.md
deleted file mode 100644
index 0ea405250f..0000000000
--- a/v1.1/docs/admin/namespaces.md
+++ /dev/null
@@ -1,145 +0,0 @@
----
----
-
-A Namespace is a mechanism to partition resources created by users into
-a logically named group.
-
-## Motivation
-
-A single cluster should be able to satisfy the needs of multiple users or groups of users (henceforth a 'user community').
-
-Each user community wants to be able to work in isolation from other communities.
-
-Each user community has its own:
-
-1. resources (pods, services, replication controllers, etc.)
-2. policies (who can or cannot perform actions in their community)
-3. constraints (this community is allowed this much quota, etc.)
-
-A cluster operator may create a Namespace for each unique user community.
-
-The Namespace provides a unique scope for:
-
-1. named resources (to avoid basic naming collisions)
-2. delegated management authority to trusted users
-3. ability to limit community resource consumption
-
-## Use cases
-
-1.  As a cluster operator, I want to support multiple user communities on a single cluster.
-2.  As a cluster operator, I want to delegate authority to partitions of the cluster to trusted users
-    in those communities.
-3.  As a cluster operator, I want to limit the amount of resources each community can consume in order
-    to limit the impact to other communities using the cluster.
-4.  As a cluster user, I want to interact with resources that are pertinent to my user community in
-    isolation of what other user communities are doing on the cluster.
-
-
-## Usage
-
-Look [here](/{{page.version}}/docs/admin/namespaces/) for an in depth example of namespaces.
-
-### Viewing namespaces
-
-You can list the current namespaces in a cluster using:
-
-```shell
-$ kubectl get namespaces
-NAME          LABELS    STATUS
-default       <none>    Active
-kube-system   <none>    Active
-```
-
-Kubernetes starts with two initial namespaces:
-   * `default` The default namespace for objects with no other namespace
-   * `kube-system` The namespace for objects created by the Kubernetes system
-
-You can also get the summary of a specific namespace using:
-
-```shell
-$ kubectl get namespaces <name>
-```
-
-Or you can get detailed information with:
-
-```shell
-$ kubectl describe namespaces <name>
-Name:	   default
-Labels:	   <none>
-Status:	   Active
-
-No resource quota.
-
-Resource Limits
- Type		Resource	Min	Max	Default
- ----				--------	---	---	---
- Container			cpu			-	-	100m
-```
-
-Note that these details show both resource quota (if present) as well as resource limit ranges.
-
-Resource quota tracks aggregate usage of resources in the *Namespace* and allows cluster operators
-to define *Hard* resource usage limits that a *Namespace* may consume.
-
-A limit range defines min/max constraints on the amount of resources a single entity can consume in
-a *Namespace*.
-
-See [Admission control: Limit Range](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_limit_range.md)
-
-A namespace can be in one of two phases:
-   * `Active` the namespace is in use
-   * `Terminating` the namespace is being deleted, and can not be used for new objects
-
-See the [design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/namespaces.md#phases) for more details.
-
-### Creating a new namespace
-
-To create a new namespace, first create a new YAML file called `my-namespace.yaml` with the contents:
-
-```yaml
-apiVersion: v1
-kind: Namespace
-metadata:
-  name: <insert-namespace-name-here>
-```
-
-Note that the name of your namespace must be a DNS compatible label.
-
-More information on the `finalizers` field can be found in the namespace [design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/namespaces.md#finalizers).
-
-Then run:
-
-```shell
-$ kubectl create -f ./my-namespace.yaml
-```
-
-### Working in namespaces
-
-See [Setting the namespace for a request](/{{page.version}}/docs/user-guide/namespaces/#setting-the-namespace-for-a-request)
-and [Setting the namespace preference](/{{page.version}}/docs/user-guide/namespaces/#setting-the-namespace-preference).
-
-### Deleting a namespace
-
-You can delete a namespace with
-
-```shell
-$ kubectl delete namespaces <insert-some-namespace-name>
-```
-
-**WARNING, this deletes _everything_ under the namespace!**
-
-This delete is asynchronous, so for a time you will see the namespace in the `Terminating` state.
-
-## Namespaces and DNS
-
-When you create a [Service](/{{page.version}}/docs/user-guide/services), it creates a corresponding [DNS entry](/{{page.version}}/docs/admin/dns).
-This entry is of the form `<service-name>.<namespace-name>.svc.cluster.local`, which means
-that if a container just uses `<service-name>` it will resolve to the service which
-is local to a namespace.  This is useful for using the same configuration across
-multiple namespaces such as Development, Staging and Production.  If you want to reach
-across namespaces, you need to use the fully qualified domain name (FQDN).
-
-## Design
-
-Details of the design of namespaces in Kubernetes, including a [detailed example](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/namespaces.md#example-openshift-origin-managing-a-kubernetes-namespace)
-can be found in the [namespaces design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/namespaces.md)
\ No newline at end of file
diff --git a/v1.1/docs/admin/namespaces/index.md b/v1.1/docs/admin/namespaces/index.md
deleted file mode 100644
index 27b2631ecb..0000000000
--- a/v1.1/docs/admin/namespaces/index.md
+++ /dev/null
@@ -1,250 +0,0 @@
----
----
-
-Kubernetes _namespaces_ help different projects, teams, or customers to share a Kubernetes cluster.
-
-It does this by providing the following:
-
-1. A scope for [Names](/{{page.version}}/docs/user-guide/identifiers).
-2. A mechanism to attach authorization and policy to a subsection of the cluster.
-
-Use of multiple namespaces is optional.
-
-This example demonstrates how to use Kubernetes namespaces to subdivide your cluster.
-
-### Step Zero: Prerequisites
-
-This example assumes the following:
-
-1. You have an [existing Kubernetes cluster](/{{page.version}}/docs/getting-started-guides/).
-2. You have a basic understanding of Kubernetes _[pods](/{{page.version}}/docs/user-guide/pods)_, _[services](/{{page.version}}/docs/user-guide/services)_, and _[replication controllers](/{{page.version}}/docs/user-guide/replication-controller)_.
-
-### Step One: Understand the default namespace
-
-By default, a Kubernetes cluster will instantiate a default namespace when provisioning the cluster to hold the default set of pods,
-services, and replication controllers used by the cluster.
-
-Assuming you have a fresh cluster, you can introspect the available namespace's by doing the following:
-
-```shell
-$ kubectl get namespaces
-NAME                LABELS
-default             <none>
-```
-
-### Step Two: Create new namespaces
-
-For this exercise, we will create two additional Kubernetes namespaces to hold our content.
-
-Let's imagine a scenario where an organization is using a shared Kubernetes cluster for development and production use cases.
-
-The development team would like to maintain a space in the cluster where they can get a view on the list of pods, services, and replication controllers
-they use to build and run their application.  In this space, Kubernetes resources come and go, and the restrictions on who can or cannot modify resources
-are relaxed to enable agile development.
-
-The operations team would like to maintain a space in the cluster where they can enforce strict procedures on who can or cannot manipulate the set of
-pods, services, and replication controllers that run the production site.
-
-One pattern this organization could follow is to partition the Kubernetes cluster into two namespaces: development and production.
-
-Let's create two new namespaces to hold our work.
-
-Use the file [`namespace-dev.json`](/{{page.version}}/docs/admin/namespacesnamespace-dev.json) which describes a development namespace:
-
-<!-- BEGIN MUNGE: EXAMPLE namespace-dev.json -->
-
-```json
-{
-  "kind": "Namespace",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "development",
-    "labels": {
-      "name": "development"
-    }
-  }
-}
-```
-
-[Download example](/{{page.version}}/docs/admin/namespacesnamespace-dev.json)
-<!-- END MUNGE: EXAMPLE namespace-dev.json -->
-
-Create the development namespace using kubectl.
-
-```shell
-$ kubectl create -f docs/admin/namespaces/namespace-dev.json
-```
-
-And then lets create the production namespace using kubectl.
-
-```shell
-$ kubectl create -f docs/admin/namespaces/namespace-prod.json
-```
-
-To be sure things are right, let's list all of the namespaces in our cluster.
-
-```shell
-$ kubectl get namespaces
-NAME          LABELS             STATUS
-default       <none>             Active
-development   name=development   Active
-production    name=production    Active
-```
-
-### Step Three: Create pods in each namespace
-
-A Kubernetes namespace provides the scope for pods, services, and replication controllers in the cluster.
-
-Users interacting with one namespace do not see the content in another namespace.
-
-To demonstrate this, let's spin up a simple replication controller and pod in the development namespace.
-
-We first check what is the current context:
-
-```yaml
-apiVersion: v1
-clusters:
-- cluster:
-    certificate-authority-data: REDACTED
-    server: https://130.211.122.180
-  name: lithe-cocoa-92103_kubernetes
-contexts:
-- context:
-    cluster: lithe-cocoa-92103_kubernetes
-    user: lithe-cocoa-92103_kubernetes
-  name: lithe-cocoa-92103_kubernetes
-current-context: lithe-cocoa-92103_kubernetes
-kind: Config
-preferences: {}
-users:
-- name: lithe-cocoa-92103_kubernetes
-  user:
-    client-certificate-data: REDACTED
-    client-key-data: REDACTED
-    token: 65rZW78y8HbwXXtSXuUw9DbP4FLjHi4b
-- name: lithe-cocoa-92103_kubernetes-basic-auth
-  user:
-    password: h5M0FtUUIflBSdI7
-    username: admin
-```
-
-The next step is to define a context for the kubectl client to work in each namespace. The value of "cluster" and "user" fields are copied from the current context.
-
-```shell
-$ kubectl config set-context dev --namespace=development --cluster=lithe-cocoa-92103_kubernetes --user=lithe-cocoa-92103_kubernetes
-$ kubectl config set-context prod --namespace=production --cluster=lithe-cocoa-92103_kubernetes --user=lithe-cocoa-92103_kubernetes
-```
-
-The above commands provided two request contexts you can alternate against depending on what namespace you
-wish to work against.
-
-Let's switch to operate in the development namespace.
-
-```shell
-$ kubectl config use-context dev
-```
-
-You can verify your current context by doing the following:
-
-```shell
-$ kubectl config view
-```
-
-```yaml
-apiVersion: v1
-clusters:
-- cluster:
-    certificate-authority-data: REDACTED
-    server: https://130.211.122.180
-  name: lithe-cocoa-92103_kubernetes
-contexts:
-- context:
-    cluster: lithe-cocoa-92103_kubernetes
-    namespace: development
-    user: lithe-cocoa-92103_kubernetes
-  name: dev
-- context:
-    cluster: lithe-cocoa-92103_kubernetes
-    user: lithe-cocoa-92103_kubernetes
-  name: lithe-cocoa-92103_kubernetes
-- context:
-    cluster: lithe-cocoa-92103_kubernetes
-    namespace: production
-    user: lithe-cocoa-92103_kubernetes
-  name: prod
-current-context: dev
-kind: Config
-preferences: {}
-users:
-- name: lithe-cocoa-92103_kubernetes
-  user:
-    client-certificate-data: REDACTED
-    client-key-data: REDACTED
-    token: 65rZW78y8HbwXXtSXuUw9DbP4FLjHi4b
-- name: lithe-cocoa-92103_kubernetes-basic-auth
-  user:
-    password: h5M0FtUUIflBSdI7
-    username: admin
-```
-
-At this point, all requests we make to the Kubernetes cluster from the command line are scoped to the development namespace.
-
-Let's create some content.
-
-```shell
-$ kubectl run snowflake --image=kubernetes/serve_hostname --replicas=2
-```
-
-We have just created a replication controller whose replica size is 2 that is running the pod called snowflake with a basic container that just serves the hostname.
-
-```shell
-$ kubectl get rc
-CONTROLLER   CONTAINER(S)   IMAGE(S)                    SELECTOR        REPLICAS
-snowflake    snowflake      kubernetes/serve_hostname   run=snowflake   2
-
-$ kubectl get pods
-NAME              READY     STATUS    RESTARTS   AGE
-snowflake-8w0qn   1/1       Running   0          22s
-snowflake-jrpzb   1/1       Running   0          22s
-```
-
-And this is great, developers are able to do what they want, and they do not have to worry about affecting content in the production namespace.
-
-Let's switch to the production namespace and show how resources in one namespace are hidden from the other.
-
-```shell
-$ kubectl config use-context prod
-```
-
-The production namespace should be empty.
-
-```shell
-$ kubectl get rc
-CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR   REPLICAS
-
-$ kubectl get pods
-NAME      READY     STATUS    RESTARTS   AGE
-```
-
-Production likes to run cattle, so let's create some cattle pods.
-
-```shell
-$ kubectl run cattle --image=kubernetes/serve_hostname --replicas=5
-
-$ kubectl get rc
-CONTROLLER   CONTAINER(S)   IMAGE(S)                    SELECTOR     REPLICAS
-cattle       cattle         kubernetes/serve_hostname   run=cattle   5
-
-$ kubectl get pods
-NAME           READY     STATUS    RESTARTS   AGE
-cattle-97rva   1/1       Running   0          12s
-cattle-i9ojn   1/1       Running   0          12s
-cattle-qj3yv   1/1       Running   0          12s
-cattle-yc7vn   1/1       Running   0          12s
-cattle-zz7ea   1/1       Running   0          12s
-```
-
-At this point, it should be clear that the resources users create in one namespace are hidden from the other namespace.
-
-As the policy support in Kubernetes evolves, we will extend this scenario to show how you can provide different
-authorization rules for each namespace.
\ No newline at end of file
diff --git a/v1.1/docs/admin/node.md b/v1.1/docs/admin/node.md
deleted file mode 100644
index 1844b2376f..0000000000
--- a/v1.1/docs/admin/node.md
+++ /dev/null
@@ -1,212 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## What is a node?
-
-`Node` is a worker machine in Kubernetes, previously known as `Minion`. Node
-may be a VM or physical machine, depending on the cluster. Each node has
-the services necessary to run [Pods](/{{page.version}}/docs/user-guide/pods) and is managed by the master
-components. The services on a node include docker, kubelet and network proxy. See
-[The Kubernetes Node](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/architecture.md#the-kubernetes-node) section in the
-architecture design doc for more details.
-
-## Node Status
-
-Node status describes current status of a node. For now, there are the following
-pieces of information:
-
-### Node Addresses
-
-The usage of these fields varies depending on your cloud provider or bare metal configuration.
-
-* HostName: Generally not used
-
-* ExternalIP: Generally the IP address of the node that is externally routable (available from outside the cluster)
-
-* InternalIP: Generally the IP address of the node that is routable only within the cluster
-
-
-### Node Phase
-
-Node Phase is the current lifecycle phase of node, one of `Pending`,
-`Running` and `Terminated`.
-
-* Pending: New nodes are created in this state. A node stays in this state until it is configured.
-
-* Running: Node has been configured and the Kubernetes components are running
-
-* Terminated: Node has been removed from the cluster. It will not receive any scheduling requests,
-and any running pods will be removed from the node.
-
-Node with `Running` phase is necessary but not sufficient requirement for
-scheduling Pods. For a node to be considered a scheduling candidate, it
-must have appropriate conditions, see below.
-
-### Node Condition
-
-Node Condition describes the conditions of `Running` nodes. Currently the only
-node condition is Ready. The Status of this condition can be True, False, or
-Unknown. True means the Kubelet is healthy and ready to accept pods.
-False means the Kubelet is not healthy and is not accepting pods. Unknown
-means the Node Controller, which manages node lifecycle and is responsible for
-setting the Status of the condition, has not heard from the
-node recently (currently 40 seconds).
-Node condition is represented as a json object. For example,
-the following conditions mean the node is in sane state:
-
-```json
-"conditions": [
-  {
-    "kind": "Ready",
-    "status": "True",
-    },
-]
-```
-
-If the Status of the Ready condition
-is Unknown or False for more than five minutes, then all of the Pods on the node are terminated by the Node Controller.
-
-### Node Capacity
-
-Describes the resources available on the node: CPUs, memory and the maximum
-number of pods that can be scheduled onto the node.
-
-### Node Info
-
-General information about the node, for instance kernel version, Kubernetes version
-(kubelet version, kube-proxy version), docker version (if used), OS name.
-The information is gathered by Kubelet from the node.
-
-## Node Management
-
-Unlike [Pods](/{{page.version}}/docs/user-guide/pods) and [Services](/{{page.version}}/docs/user-guide/services), a Node is not inherently
-created by Kubernetes: it is either taken from cloud providers like Google Compute Engine,
-or from your pool of physical or virtual machines. What this means is that when
-Kubernetes creates a node, it is really just creating an object that represents the node in its internal state.
-After creation, Kubernetes will check whether the node is valid or not.
-For example, if you try to create a node from the following content:
-
-```json
-{
-  "kind": "Node",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "10.240.79.157",
-    "labels": {
-      "name": "my-first-k8s-node"
-    }
-  }
-}
-```
-
-Kubernetes will create a Node object internally (the representation), and
-validate the node by health checking based on the `metadata.name` field: we
-assume `metadata.name` can be resolved. If the node is valid, i.e. all necessary
-services are running, it is eligible to run a Pod; otherwise, it will be
-ignored for any cluster activity, until it becomes valid. Note that Kubernetes
-will keep the object for the invalid node unless it is explicitly deleted by the client, and it will keep
-checking to see if it becomes valid.
-
-Currently, there are three components that interact with the Kubernetes node interface: Node Controller, Kubelet, and kubectl.
-
-### Node Controller
-
-Node controller is a component in Kubernetes master which manages Node
-objects. It performs two major functions: cluster-wide node synchronization
-and single node life-cycle management.
-
-Node controller has a sync loop that creates/deletes Nodes from Kubernetes
-based on all matching VM instances listed from the cloud provider. The sync period
-can be controlled via flag `--node-sync-period`. If a new VM instance
-gets created, Node Controller creates a representation for it. If an existing
-instance gets deleted, Node Controller deletes the representation. Note however,
-that Node Controller is unable to provision the node for you, i.e. it won't install
-any binary; therefore, to
-join a node to a Kubernetes cluster, you as an admin need to make sure proper services are
-running in the node. In the future, we plan to automatically provision some node
-services.
-
-### Self-Registration of Nodes
-
-When kubelet flag `--register-node` is true (the default), the kubelet will attempt to
-register itself with the API server.  This is the preferred pattern, used by most distros.
-
-For self-registration, the kubelet is started with the following options:
-
-  - `--api-servers=` tells the kubelet the location of the apiserver.
-  - `--kubeconfig` tells kubelet where to find credentials to authenticate itself to the apiserver.
-  - `--cloud-provider=` tells the kubelet how to talk to a cloud provider to read metadata about itself.
-  - `--register-node` tells the kubelet to create its own node resource.
-
-Currently, any kubelet is authorized to create/modify any node resource, but in practice it only creates/modifies
-its own.  (In the future, we plan to limit authorization to only allow a kubelet to modify its own Node resource.)
-
-#### Manual Node Administration
-
-A cluster administrator can create and modify Node objects.
-
-If the administrator wishes to create node objects manually, set kubelet flag
-`--register-node=false`.
-
-The administrator can modify Node resources (regardless of the setting of `--register-node`).
-Modifications include setting labels on the Node, and marking it unschedulable.
-
-Labels on nodes can be used in conjunction with node selectors on pods to control scheduling,
-e.g. to constrain a Pod to only be eligible to run on a subset of the nodes.
-
-Making a node unscheduleable will prevent new pods from being scheduled to that
-node, but will not affect any existing pods on the node.  This is useful as a
-preparatory step before a node reboot, etc.  For example, to mark a node
-unschedulable, run this command:
-
-```shell
-kubectl replace nodes 10.1.2.3 --patch='{"apiVersion": "v1", "unschedulable": true}'
-```
-
-Note that pods which are created by a daemonSet controller bypass the Kubernetes scheduler,
-and do not respect the unschedulable attribute on a node.   The assumption is that daemons belong on
-the machine even if it is being drained of applications in preparation for a reboot.
-
-### Node capacity
-
-The capacity of the node (number of cpus and amount of memory) is part of the node resource.
-Normally, nodes register themselves and report their capacity when creating the node resource.  If
-you are doing [manual node administration](#manual-node-administration), then you need to set node
-capacity when adding a node.
-
-The Kubernetes scheduler ensures that there are enough resources for all the pods on a node.  It
-checks that the sum of the limits of containers on the node is no greater than the node capacity.  It
-includes all containers started by kubelet, but not containers started directly by docker, nor
-processes not in containers.
-
-If you want to explicitly reserve resources for non-Pod processes, you can create a placeholder
-pod.  Use the following template:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: resource-reserver
-spec:
-  containers:
-  - name: sleep-forever
-    image: gcr.io/google_containers/pause:0.8.0
-    resources:
-      limits:
-        cpu: 100m
-        memory: 100Mi
-```
-
-Set the `cpu` and `memory` values to the amount of resources you want to reserve.
-Place the file in the manifest directory (`--config=DIR` flag of kubelet).  Do this
-on each kubelet where you want to reserve resources.
-
-
-## API Object
-
-Node is a top-level resource in the kubernetes REST API. More details about the
-API object can be found at: [Node API
-object](http://kubernetes.io/v1.1/docs/api-reference/v1/definitions/#_v1_node).
diff --git a/v1.1/docs/admin/service-accounts-admin.md b/v1.1/docs/admin/service-accounts-admin.md
deleted file mode 100644
index d68383e640..0000000000
--- a/v1.1/docs/admin/service-accounts-admin.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
----
-
-*This is a Cluster Administrator guide to service accounts.  It assumes knowledge of
-the [User Guide to Service Accounts](/{{page.version}}/docs/user-guide/service-accounts).*
-
-*Support for authorization and user accounts is planned but incomplete.  Sometimes
-incomplete features are referred to in order to better describe service accounts.*
-
-## User accounts vs service accounts
-
-Kubernetes distinguished between the concept of a user account and a service accounts
-for a number of reasons:
-
-  - User accounts are for humans.  Service accounts are for processes, which
-    run in pods.
-  - User accounts are intended to be global. Names must be unique across all
-    namespaces of a cluster, future user resource will not be namespaced).
-    Service accounts are namespaced.
-  - Typically, a cluster's User accounts might be synced from a corporate
-    database, where new user account creation requires special privileges and
-    is tied to complex business  processes.  Service account creation is intended
-    to be more lightweight, allowing cluster users to create service accounts for
-    specific tasks (i.e. principle of least privilege).
-  - Auditing considerations for humans and service accounts may differ.
-  - A config bundle for a complex system may include definition of various service
-    accounts for components of that system.  Because service accounts can be created
-    ad-hoc and have namespaced names, such config is portable.
-
-## Service account automation
-
-Three separate components cooperate to implement the automation around service accounts:
-
-  - A Service account admission controller
-  - A Token controller
-  - A Service account controller
-
-### Service Account Admission Controller
-
-The modification of pods is implemented via a plugin
-called an [Admission Controller](/{{page.version}}/docs/admin/admission-controllers). It is part of the apiserver.
-It acts synchronously to modify pods as they are created or updated. When this plugin is active
-(and it is by default on most distributions), then it does the following when a pod is created or modified:
-
-  1. If the pod does not have a `ServiceAccount` set, it sets the `ServiceAccount` to `default`.
-  2. It ensures that the `ServiceAccount` referenced by the pod exists, and otherwise rejects it.
-  4. If the pod does not contain any `ImagePullSecrets`, then `ImagePullSecrets` of the
-`ServiceAccount` are added to the pod.
-  5. It adds a `volume` to the pod which contains a token for API access.
-  6. It adds a `volumeSource` to each container of the pod mounted at `/var/run/secrets/kubernetes.io/serviceaccount`.
-
-### Token Controller
-
-TokenController runs as part of controller-manager. It acts asynchronously. It:
-
-- observes serviceAccount creation and creates a corresponding Secret to allow API access.
-- observes serviceAccount deletion and deletes all corresponding ServiceAccountToken Secrets
-- observes secret addition, and ensures the referenced ServiceAccount exists, and adds a token to the secret if needed
-- observes secret deletion and removes a reference from the corresponding ServiceAccount if needed
-
-#### To create additional API tokens
-
-A controller loop ensures a secret with an API token exists for each service
-account. To create additional API tokens for a service account, create a secret
-of type `ServiceAccountToken` with an annotation referencing the service
-account, and the controller will update it with a generated token:
-
-```json
-secret.json:
-{
-    "kind": "Secret",
-    "apiVersion": "v1",
-    "metadata": {
-        "name": "mysecretname",
-        "annotations": {
-            "kubernetes.io/service-account.name": "myserviceaccount"
-        }
-    },
-    "type": "kubernetes.io/service-account-token"
-}
-```
-
-```shell
-kubectl create -f ./secret.json
-kubectl describe secret mysecretname
-```
-
-#### To delete/invalidate a service account token
-
-```shell
-kubectl delete secret mysecretname
-```
-
-### Service Account Controller
-
-Service Account Controller manages ServiceAccount inside namespaces, and ensures
-a ServiceAccount named "default" exists in every active namespace.
\ No newline at end of file
diff --git a/v1.1/docs/devel/coding-conventions.md b/v1.1/docs/devel/coding-conventions.md
deleted file mode 100644
index 31e8762a60..0000000000
--- a/v1.1/docs/devel/coding-conventions.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
----
-
-
-  - Bash
-    - https://google-styleguide.googlecode.com/svn/trunk/shell.xml
-    - Ensure that build, release, test, and cluster-management scripts run on OS X
-  - Go
-    - Ensure your code passes the [presubmit checks](/{{page.version}}/docs/devel/development/#hooks)
-    - [Go Code Review Comments](https://github.com/golang/go/wiki/CodeReviewComments)
-    - [Effective Go](https://golang.org/doc/effective_go)
-    - Comment your code.
-      - [Go's commenting conventions](http://blog.golang.org/godoc-documenting-go-code)
-      - If reviewers ask questions about why the code is the way it is, that's a sign that comments might be helpful.
-    - Command-line flags should use dashes, not underscores
-    - Naming
-      - Please consider package name when selecting an interface name, and avoid redundancy.
-        - e.g.: `storage.Interface` is better than `storage.StorageInterface`.
-      - Do not use uppercase characters, underscores, or dashes in package names.
-      - Please consider parent directory name when choosing a package name.
-        - so pkg/controllers/autoscaler/foo.go should say `package autoscaler` not `package autoscalercontroller`.
-        - Unless there's a good reason, the `package foo` line should match the name of the directory in which the .go file exists.
-        - Importers can use a different name if they need to disambiguate.
-      - Locks should be called `lock` and should never be embedded (always `lock sync.Mutex`). When multiple locks are present, give each lock a distinct name following Go conventions - `stateLock`, `mapLock` etc.
-    - API conventions
-      - [API changes](/{{page.version}}/docs/devel/api_changes)
-      - [API conventions](/{{page.version}}/docs/devel/api-conventions)
-    - [Kubectl conventions](/{{page.version}}/docs/devel/kubectl-conventions)
-    - [Logging conventions](/{{page.version}}/docs/devel/logging)
-
-Testing conventions
-
-  - All new packages and most new significant functionality must come with unit tests
-  - Table-driven tests are preferred for testing multiple scenarios/inputs; for example, see [TestNamespaceAuthorization](https://releases.k8s.io/{{page.githubbranch}}/test/integration/auth_test.go)
-  - Significant features should come with integration (test/integration) and/or end-to-end (test/e2e) tests
-    - Including new kubectl commands and major features of existing commands
-  - Unit tests must pass on OS X and Windows platforms - if you use Linux specific features, your test case must either be skipped on windows or compiled out (skipped is better when running Linux specific commands, compiled out is required when your code does not compile on Windows).
-
-Directory and file conventions
-
-  - Avoid package sprawl. Find an appropriate subdirectory for new packages. (See [#4851](http://issues.k8s.io/4851) for discussion.)
-    - Libraries with no more appropriate home belong in new package subdirectories of pkg/util
-  - Avoid general utility packages. Packages called "util" are suspect. Instead, derive a name that describes your desired function. For example, the utility functions dealing with waiting for operations are in the "wait" package and include functionality like Poll. So the full name is wait.Poll
-  - Go source files and directories use underscores, not dashes
-    - Package directories should generally avoid using separators as much as possible (when packages are multiple words, they usually should be in nested subdirectories).
-  - Document directories and filenames should use dashes rather than underscores
-  - Contrived examples that illustrate system features belong in /docs/user-guide or /docs/admin, depending on whether it is a feature primarily intended for users that deploy applications or cluster administrators, respectively. Actual application examples belong in /examples.
-    - Examples should also illustrate [best practices for using the system](/{{page.version}}/docs/user-guide/config-best-practices)
-  - Third-party code
-    - Third-party Go code is managed using Godeps
-    - Other third-party code belongs in /third_party
-    - Third-party code must include licenses
-    - This includes modified third-party code and excerpts, as well
-
-Coding advice
-
-  - Go
-    - [Go landmines](https://gist.github.com/lavalamp/4bd23295a9f32706a48f)
diff --git a/v1.1/docs/devel/developer-guides/vagrant.md b/v1.1/docs/devel/developer-guides/vagrant.md
deleted file mode 100644
index a338bf2ac4..0000000000
--- a/v1.1/docs/devel/developer-guides/vagrant.md
+++ /dev/null
@@ -1,345 +0,0 @@
----
----
-
-Running kubernetes with Vagrant (and VirtualBox) is an easy way to run/test/develop on your local machine (Linux, Mac OS X).
-
-### Prerequisites
-
-1. Install latest version >= 1.6.2 of vagrant from http://www.vagrantup.com/downloads.html
-2. Install one of:
-   1. The latest version of Virtual Box from https://www.virtualbox.org/wiki/Downloads
-   2. [VMWare Fusion](https://www.vmware.com/products/fusion/) version 5 or greater as well as the appropriate [Vagrant VMWare Fusion provider](https://www.vagrantup.com/vmware)
-   3. [VMWare Workstation](https://www.vmware.com/products/workstation/) version 9 or greater as well as the [Vagrant VMWare Workstation provider](https://www.vagrantup.com/vmware)
-   4. [Parallels Desktop](https://www.parallels.com/products/desktop/) version 9 or greater as well as the [Vagrant Parallels provider](https://parallels.github.io/vagrant-parallels/)
-3. Get or build a [binary release](/{{page.version}}/docs/getting-started-guides/binary_release)
-
-### Setup
-
-By default, the Vagrant setup will create a single master VM (called kubernetes-master) and one node (called kubernetes-minion-1). Each VM will take 1 GB, so make sure you have at least 2GB to 4GB of free memory (plus appropriate free disk space). To start your local cluster, open a shell and run:
-
-```shell
-cd kubernetes
-
-export KUBERNETES_PROVIDER=vagrant
-./cluster/kube-up.sh
-```
-
-The `KUBERNETES_PROVIDER` environment variable tells all of the various cluster management scripts which variant to use.  If you forget to set this, the assumption is you are running on Google Compute Engine.
-
-If you installed more than one Vagrant provider, Kubernetes will usually pick the appropriate one. However, you can override which one Kubernetes will use by setting the [`VAGRANT_DEFAULT_PROVIDER`](https://docs.vagrantup.com/v2/providers/default) environment variable:
-
-```shell
-export VAGRANT_DEFAULT_PROVIDER=parallels
-export KUBERNETES_PROVIDER=vagrant
-./cluster/kube-up.sh
-```
-
-Vagrant will provision each machine in the cluster with all the necessary components to run Kubernetes.  The initial setup can take a few minutes to complete on each machine.
-
-By default, each VM in the cluster is running Fedora, and all of the Kubernetes services are installed into systemd.
-
-To access the master or any node:
-
-```shell
-vagrant ssh master
-vagrant ssh minion-1
-```
-
-If you are running more than one nodes, you can access the others by:
-
-```shell
-vagrant ssh minion-2
-vagrant ssh minion-3
-```
-
-To view the service status and/or logs on the kubernetes-master:
-
-```shell
-$ vagrant ssh master
-[vagrant@kubernetes-master ~] $ sudo systemctl status kube-apiserver
-[vagrant@kubernetes-master ~] $ sudo journalctl -r -u kube-apiserver
-
-[vagrant@kubernetes-master ~] $ sudo systemctl status kube-controller-manager
-[vagrant@kubernetes-master ~] $ sudo journalctl -r -u kube-controller-manager
-
-[vagrant@kubernetes-master ~] $ sudo systemctl status etcd
-[vagrant@kubernetes-master ~] $ sudo systemctl status nginx
-```
-
-To view the services on any of the nodes:
-
-```shell
-$ vagrant ssh minion-1
-[vagrant@kubernetes-minion-1] $ sudo systemctl status docker
-[vagrant@kubernetes-minion-1] $ sudo journalctl -r -u docker
-[vagrant@kubernetes-minion-1] $ sudo systemctl status kubelet
-[vagrant@kubernetes-minion-1] $ sudo journalctl -r -u kubelet
-```
-
-### Interacting with your Kubernetes cluster with Vagrant.
-
-With your Kubernetes cluster up, you can manage the nodes in your cluster with the regular Vagrant commands.
-
-To push updates to new Kubernetes code after making source changes:
-
-```shell
-./cluster/kube-push.sh
-```
-
-To stop and then restart the cluster:
-
-```shell
-vagrant halt
-./cluster/kube-up.sh
-```
-
-To destroy the cluster:
-
-```shell
-vagrant destroy
-```
-
-Once your Vagrant machines are up and provisioned, the first thing to do is to check that you can use the `kubectl.sh` script.
-
-You may need to build the binaries first, you can do this with `make`
-
-```shell
-$ ./cluster/kubectl.sh get nodes
-
-NAME                     LABELS                                          STATUS
-kubernetes-minion-0whl   kubernetes.io/hostname=kubernetes-minion-0whl   Ready
-kubernetes-minion-4jdf   kubernetes.io/hostname=kubernetes-minion-4jdf   Ready
-kubernetes-minion-epbe   kubernetes.io/hostname=kubernetes-minion-epbe   Ready
-```
-
-### Interacting with your Kubernetes cluster with the `kube-*` scripts.
-
-Alternatively to using the vagrant commands, you can also use the `cluster/kube-*.sh` scripts to interact with the vagrant based provider just like any other hosting platform for kubernetes.
-
-All of these commands assume you have set `KUBERNETES_PROVIDER` appropriately:
-
-```shell
-export KUBERNETES_PROVIDER=vagrant
-```
-
-Bring up a vagrant cluster
-
-```shell
-./cluster/kube-up.sh
-```
-
-Destroy the vagrant cluster
-
-```shell
-./cluster/kube-down.sh
-```
-
-Update the vagrant cluster after you make changes (only works when building your own releases locally):
-
-```shell
-./cluster/kube-push.sh
-```
-
-Interact with the cluster
-
-```shell
-./cluster/kubectl.sh
-```
-
-### Authenticating with your master
-
-When using the vagrant provider in Kubernetes, the `cluster/kubectl.sh` script will cache your credentials in a `~/.kubernetes_vagrant_auth` file so you will not be prompted for them in the future.
-
-```shell
-$ cat ~/.kubernetes_vagrant_auth
-{ "User": "vagrant",
-  "Password": "vagrant"
-  "CAFile": "/home/k8s_user/.kubernetes.vagrant.ca.crt",
-  "CertFile": "/home/k8s_user/.kubecfg.vagrant.crt",
-  "KeyFile": "/home/k8s_user/.kubecfg.vagrant.key"
-}
-```
-
-You should now be set to use the `cluster/kubectl.sh` script. For example try to list the nodes that you have started with:
-
-```shell
-./cluster/kubectl.sh get nodes
-```
-
-### Running containers
-
-Your cluster is running, you can list the nodes in your cluster:
-
-```shell
-$ ./cluster/kubectl.sh get nodes
-
-NAME                     LABELS                                          STATUS
-kubernetes-minion-0whl   kubernetes.io/hostname=kubernetes-minion-0whl   Ready
-kubernetes-minion-4jdf   kubernetes.io/hostname=kubernetes-minion-4jdf   Ready
-kubernetes-minion-epbe   kubernetes.io/hostname=kubernetes-minion-epbe   Ready
-```
-
-Now start running some containers!
-
-You can now use any of the cluster/kube-*.sh commands to interact with your VM machines.
-Before starting a container there will be no pods, services and replication controllers.
-
-```shell
-$ cluster/kubectl.sh get pods
-NAME  READY   STATUS    RESTARTS    AGE
-
-$ cluster/kubectl.sh get services
-NAME  LABELS   SELECTOR    IP(S)    PORT(S)
-
-$ cluster/kubectl.sh get rc
-CONTROLLER  CONTAINER(S)   IMAGE(S)    SELECTOR    REPLICAS
-```
-
-Start a container running nginx with a replication controller and three replicas
-
-```shell
-$ cluster/kubectl.sh run my-nginx --image=nginx --replicas=3 --port=80
-CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR       REPLICAS
-my-nginx     my-nginx       nginx      run=my-nginx   3
-```
-
-When listing the pods, you will see that three containers have been started and are in Waiting state:
-
-```shell
-$ cluster/kubectl.sh get pods
-NAME              READY     STATUS    RESTARTS   AGE
-my-nginx-389da    1/1       Waiting   0          33s
-my-nginx-kqdjk    1/1       Waiting   0          33s
-my-nginx-nyj3x    1/1       Waiting   0          33s
-```
-
-You need to wait for the provisioning to complete, you can monitor the minions by doing:
-
-```shell
-$ sudo salt '*minion-1' cmd.run 'docker images'
-kubernetes-minion-1:
-    REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
-    <none>              <none>              96864a7d2df3        26 hours ago        204.4 MB
-    kubernetes/pause    latest              6c4579af347b        8 weeks ago         239.8 kB
-```
-
-Once the docker image for nginx has been downloaded, the container will start and you can list it:
-
-```shell
-$ sudo salt '*minion-1' cmd.run 'docker ps'
-kubernetes-minion-1:
-    CONTAINER ID        IMAGE                     COMMAND                CREATED             STATUS              PORTS                    NAMES
-    dbe79bf6e25b        nginx:latest              "nginx"                21 seconds ago      Up 19 seconds                                k8s--mynginx.8c5b8a3a--7813c8bd_-_3ffe_-_11e4_-_9036_-_0800279696e1.etcd--7813c8bd_-_3ffe_-_11e4_-_9036_-_0800279696e1--fcfa837f
-    fa0e29c94501        kubernetes/pause:latest   "/pause"               8 minutes ago       Up 8 minutes        0.0.0.0:8080->80/tcp     k8s--net.a90e7ce4--7813c8bd_-_3ffe_-_11e4_-_9036_-_0800279696e1.etcd--7813c8bd_-_3ffe_-_11e4_-_9036_-_0800279696e1--baf5b21b
-```
-
-Going back to listing the pods, services and replicationcontrollers, you now have:
-
-```shell
-$ cluster/kubectl.sh get pods
-NAME              READY     STATUS    RESTARTS   AGE
-my-nginx-389da    1/1       Running   0          33s
-my-nginx-kqdjk    1/1       Running   0          33s
-my-nginx-nyj3x    1/1       Running   0          33s
-
-$ cluster/kubectl.sh get services
-NAME   LABELS   SELECTOR   IP(S)   PORT(S)
-
-$ cluster/kubectl.sh get rc
-NAME        IMAGE(S)          SELECTOR       REPLICAS
-my-nginx    nginx             run=my-nginx   3
-```
-
-We did not start any services, hence there are none listed. But we see three replicas displayed properly.
-Check the [guestbook](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/) application to learn how to create a service.
-You can already play with scaling the replicas with:
-
-```shell
-$ ./cluster/kubectl.sh scale rc my-nginx --replicas=2
-$ ./cluster/kubectl.sh get pods
-NAME              READY     STATUS    RESTARTS   AGE
-my-nginx-kqdjk    1/1       Running   0          13m
-my-nginx-nyj3x    1/1       Running   0          13m
-```
-
-Congratulations!
-
-### Testing
-
-The following will run all of the end-to-end testing scenarios assuming you set your environment in `cluster/kube-env.sh`:
-
-```shell
-NUM_MINIONS=3 hack/e2e-test.sh
-```
-
-### Troubleshooting
-
-#### I keep downloading the same (large) box all the time!
-
-By default the Vagrantfile will download the box from S3. You can change this (and cache the box locally) by providing a name and an alternate URL when calling `kube-up.sh`
-
-```shell
-export KUBERNETES_BOX_NAME=choose_your_own_name_for_your_kuber_box
-export KUBERNETES_BOX_URL=path_of_your_kuber_box
-export KUBERNETES_PROVIDER=vagrant
-./cluster/kube-up.sh
-```
-
-#### I just created the cluster, but I am getting authorization errors!
-
-You probably have an incorrect ~/.kubernetes_vagrant_auth file for the cluster you are attempting to contact.
-
-```shell
-rm ~/.kubernetes_vagrant_auth
-```
-
-After using kubectl.sh make sure that the correct credentials are set:
-
-```shell
-$ cat ~/.kubernetes_vagrant_auth
-{
-  "User": "vagrant",
-  "Password": "vagrant"
-}
-```
-
-#### I just created the cluster, but I do not see my container running!
-
-If this is your first time creating the cluster, the kubelet on each node schedules a number of docker pull requests to fetch prerequisite images.  This can take some time and as a result may delay your initial pod getting provisioned.
-
-#### I changed Kubernetes code, but it's not running!
-
-Are you sure there was no build error?  After running `$ vagrant provision`, scroll up and ensure that each Salt state was completed successfully on each box in the cluster.
-It's very likely you see a build error due to an error in your source files!
-
-#### I have brought Vagrant up but the nodes won't validate!
-
-Are you sure you built a release first? Did you install `net-tools`? For more clues, login to one of the nodes (`vagrant ssh minion-1`) and inspect the salt minion log (`sudo cat /var/log/salt/minion`).
-
-#### I want to change the number of nodes!
-
-You can control the number of nodes that are instantiated via the environment variable `NUM_MINIONS` on your host machine.  If you plan to work with replicas, we strongly encourage you to work with enough nodes to satisfy your largest intended replica size.  If you do not plan to work with replicas, you can save some system resources by running with a single node. You do this, by setting `NUM_MINIONS` to 1 like so:
-
-```shell
-export NUM_MINIONS=1
-```
-
-#### I want my VMs to have more memory!
-
-You can control the memory allotted to virtual machines with the `KUBERNETES_MEMORY` environment variable.
-Just set it to the number of megabytes you would like the machines to have. For example:
-
-```shell
-export KUBERNETES_MEMORY=2048
-```
-
-If you need more granular control, you can set the amount of memory for the master and nodes independently. For example:
-
-```shell
-export KUBERNETES_MASTER_MEMORY=1536
-export KUBERNETES_MINION_MEMORY=2048
-
-```
-#### I ran vagrant suspend and nothing works!
-
-`vagrant suspend` seems to mess up the network.  It's not supported at this time.
\ No newline at end of file
diff --git a/v1.1/docs/devel/faster_reviews.md b/v1.1/docs/devel/faster_reviews.md
deleted file mode 100644
index 8545d609d7..0000000000
--- a/v1.1/docs/devel/faster_reviews.md
+++ /dev/null
@@ -1,202 +0,0 @@
----
----
-
-Most of what is written here is not at all specific to Kubernetes, but it bears
-being written down in the hope that it will occasionally remind people of "best
-practices" around code reviews.
-
-You've just had a brilliant idea on how to make Kubernetes better.  Let's call
-that idea "FeatureX".  Feature X is not even that complicated.  You have a
-pretty good idea of how to implement it.  You jump in and implement it, fixing a
-bunch of stuff along the way.  You send your PR - this is awesome!  And it sits.
-And sits.  A week goes by and nobody reviews it.  Finally someone offers a few
-comments, which you fix up and wait for more review.  And you wait.  Another
-week or two goes by.  This is horrible.
-
-What went wrong?  One particular problem that comes up frequently is this - your
-PR is too big to review.  You've touched 39 files and have 8657 insertions.
-When your would-be reviewers pull up the diffs they run away - this PR is going
-to take 4 hours to review and they don't have 4 hours right now.  They'll get to it
-later, just as soon as they have more free time (ha!).
-
-Let's talk about how to avoid this.
-
-## 0. Familiarize yourself with project conventions
-
-* [Development guide](/{{page.version}}/docs/devel/development)
-* [Coding conventions](/{{page.version}}/docs/devel/coding-conventions)
-* [API conventions](/{{page.version}}/docs/devel/api-conventions)
-* [Kubectl conventions](/{{page.version}}/docs/devel/kubectl-conventions)
-
-## 1. Don't build a cathedral in one PR
-
-Are you sure FeatureX is something the Kubernetes team wants or will accept, or
-that it is implemented to fit with other changes in flight?  Are you willing to
-bet a few days or weeks of work on it?  If you have any doubt at all about the
-usefulness of your feature or the design - make a proposal doc (in docs/proposals;
-for example [the QoS proposal](http://prs.k8s.io/11713)) or a sketch PR (e.g., just
-the API or Go interface) or both.  Write or code up just enough to express the idea
-and the design and why you made those choices, then get feedback on this. Be clear
-about what type of feedback you are asking for. Now, if we ask you to change a
-bunch of facets of the design, you won't have to re-write it all.
-
-## 2. Smaller diffs are exponentially better
-
-Small PRs get reviewed faster and are more likely to be correct than big ones.
-Let's face it - attention wanes over time.  If your PR takes 60 minutes to
-review, I almost guarantee that the reviewer's eye for details is not as keen in
-the last 30 minutes as it was in the first.  This leads to multiple rounds of
-review when one might have sufficed.  In some cases the review is delayed in its
-entirety by the need for a large contiguous block of time to sit and read your
-code.
-
-Whenever possible, break up your PRs into multiple commits.  Making a series of
-discrete commits is a powerful way to express the evolution of an idea or the
-different ideas that make up a single feature.  There's a balance to be struck,
-obviously.  If your commits are too small they become more cumbersome to deal
-with.  Strive to group logically distinct ideas into commits.
-
-For example, if you found that FeatureX needed some "prefactoring" to fit in,
-make a commit that JUST does that prefactoring.  Then make a new commit for
-FeatureX.  Don't lump unrelated things together just because you didn't think
-about prefactoring.  If you need to, fork a new branch, do the prefactoring
-there and send a PR for that.  If you can explain why you are doing seemingly
-no-op work ("it makes the FeatureX change easier, I promise") we'll probably be
-OK with it.
-
-Obviously, a PR with 25 commits is still very cumbersome to review, so use
-common sense.
-
-## 3. Multiple small PRs are often better than multiple commits
-
-If you can extract whole ideas from your PR and send those as PRs of their own,
-you can avoid the painful problem of continually rebasing.  Kubernetes is a
-fast-moving codebase - lock in your changes ASAP, and make merges be someone
-else's problem.
-
-Obviously, we want every PR to be useful on its own, so you'll have to use
-common sense in deciding what can be a PR vs what should be a commit in a larger
-PR.  Rule of thumb - if this commit or set of commits is directly related to
-FeatureX and nothing else, it should probably be part of the FeatureX PR.  If
-you can plausibly imagine someone finding value in this commit outside of
-FeatureX, try it as a PR.
-
-Don't worry about flooding us with PRs.  We'd rather have 100 small, obvious PRs
-than 10 unreviewable monoliths.
-
-## 4. Don't rename, reformat, comment, etc in the same PR
-
-Often, as you are implementing FeatureX, you find things that are just wrong.
-Bad comments, poorly named functions, bad structure, weak type-safety.  You
-should absolutely fix those things (or at least file issues, please) - but not
-in this PR.  See the above points - break unrelated changes out into different
-PRs or commits.  Otherwise your diff will have WAY too many changes, and your
-reviewer won't see the forest because of all the trees.
-
-## 5. Comments matter
-
-Read up on GoDoc - follow those general rules.  If you're writing code and you
-think there is any possible chance that someone might not understand why you did
-something (or that you won't remember what you yourself did), comment it.  If
-you think there's something pretty obvious that we could follow up on, add a
-TODO.  Many code-review comments are about this exact issue.
-
-## 5. Tests are almost always required
-
-Nothing is more frustrating than doing a review, only to find that the tests are
-inadequate or even entirely absent.  Very few PRs can touch code and NOT touch
-tests.  If you don't know how to test FeatureX - ask!  We'll be happy to help
-you design things for easy testing or to suggest appropriate test cases.
-
-## 6. Look for opportunities to generify
-
-If you find yourself writing something that touches a lot of modules, think hard
-about the dependencies you are introducing between packages.  Can some of what
-you're doing be made more generic and moved up and out of the FeatureX package?
-Do you need to use a function or type from an otherwise unrelated package?  If
-so, promote!  We have places specifically for hosting more generic code.
-
-Likewise if FeatureX is similar in form to FeatureW which was checked in last
-month and it happens to exactly duplicate some tricky stuff from FeatureW,
-consider prefactoring core logic out and using it in both FeatureW and FeatureX.
-But do that in a different commit or PR, please.
-
-## 7. Fix feedback in a new commit
-
-Your reviewer has finally sent you some feedback on FeatureX.  You make a bunch
-of changes and ... what?  You could patch those into your commits with git
-"squash" or "fixup" logic.  But that makes your changes hard to verify.  Unless
-your whole PR is pretty trivial, you should instead put your fixups into a new
-commit and re-push.  Your reviewer can then look at that commit on its own - so
-much faster to review than starting over.
-
-We might still ask you to clean up your commits at the very end, for the sake
-of a more readable history, but don't do this until asked, typically at the point
-where the PR would otherwise be tagged LGTM.
-
-General squashing guidelines:
-
-* Sausage => squash
-
-  When there are several commits to fix bugs in the original commit(s), address reviewer feedback, etc. Really we only want to see the end state and commit message for the whole PR.
-
-* Layers => don't squash
-
-  When there are independent changes layered upon each other to achieve a single goal. For instance, writing a code munger could be one commit, applying it could be another, and adding a precommit check could be a third. One could argue they should be separate PRs, but there's really no way to test/review the munger without seeing it applied, and there needs to be a precommit check to ensure the munged output doesn't immediately get out of date.
-
-A commit, as much as possible, should be a single logical change. Each commit should always have a good title line (<70 characters) and include an additional description paragraph describing in more detail the change intended. Do not link pull requests by `#` in a commit description, because GitHub creates lots of spam. Instead, reference other PRs via the PR your commit is in.
-
-## 8. KISS, YAGNI, MVP, etc
-
-Sometimes we need to remind each other of core tenets of software design - Keep
-It Simple, You Aren't Gonna Need It, Minimum Viable Product, and so on.  Adding
-features "because we might need it later" is antithetical to software that
-ships.  Add the things you need NOW and (ideally) leave room for things you
-might need later - but don't implement them now.
-
-## 9. Push back
-
-We understand that it is hard to imagine, but sometimes we make mistakes.  It's
-OK to push back on changes requested during a review.  If you have a good reason
-for doing something a certain way, you are absolutely allowed to debate the
-merits of a requested change.  You might be overruled, but you might also
-prevail.  We're mostly pretty reasonable people.  Mostly.
-
-## 10. I'm still getting stalled - help?!
-
-So, you've done all that and you still aren't getting any PR love?  Here's some
-things you can do that might help kick a stalled process along:
-
-   * Make sure that your PR has an assigned reviewer (assignee in GitHub).  If
-     this is not the case, reply to the PR comment stream asking for one to be
-     assigned.
-
-   * Ping the assignee (@username) on the PR comment stream asking for an
-     estimate of when they can get to it.
-
-   * Ping the assignee by email (many of us have email addresses that are well
-     published or are the same as our GitHub handle @google.com or @redhat.com).
-
-   * Ping the [team](https://github.com/orgs/kubernetes/teams) (via @team-name)
-     that works in the area you're submitting code.
-
-If you think you have fixed all the issues in a round of review, and you haven't
-heard back, you should ping the reviewer (assignee) on the comment stream with a
-"please take another look" (PTAL) or similar comment indicating you are done and
-you think it is ready for re-review.  In fact, this is probably a good habit for
-all PRs.
-
-One phenomenon of open-source projects (where anyone can comment on any issue)
-is the dog-pile - your PR gets so many comments from so many people it becomes
-hard to follow.  In this situation you can ask the primary reviewer
-(assignee) whether they want you to fork a new PR to clear out all the comments.
-Remember: you don't HAVE to fix every issue raised by every person who feels
-like commenting, but you should at least answer reasonable comments with an
-explanation.
-
-## Final: Use common sense
-
-Obviously, none of these points are hard rules.  There is no document that can
-take the place of common sense and good taste.  Use your best judgment, but put
-a bit of thought into how your work can be made easier to review.  If you do
-these things your PRs will flow much more easily.
\ No newline at end of file
diff --git a/v1.1/docs/devel/index.md b/v1.1/docs/devel/index.md
deleted file mode 100644
index 54f8ec5f99..0000000000
--- a/v1.1/docs/devel/index.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
----
-
-The developer guide is for anyone wanting to either write code which directly accesses the
-Kubernetes API, or to contribute directly to the Kubernetes project.
-It assumes some familiarity with concepts in the [User Guide](/{{page.version}}/docs/user-guide/) and the [Cluster Admin
-Guide](/{{page.version}}/docs/admin/).
-
-
-## The process of developing and contributing code to the Kubernetes project
-
-* **On Collaborative Development** ([collab.md](/{{page.version}}/docs/devel/collab)): Info on pull requests and code reviews.
-
-* **GitHub Issues** ([issues.md](/{{page.version}}/docs/devel/issues)): How incoming issues are reviewed and prioritized.
-
-* **Pull Request Process** ([pull-requests.md](/{{page.version}}/docs/devel/pull-requests)): When and why pull requests are closed.
-
-* **Faster PR reviews** ([faster_reviews.md](/{{page.version}}/docs/devel/faster_reviews)): How to get faster PR reviews.
-
-* **Getting Recent Builds** ([getting-builds.md](/{{page.version}}/docs/devel/getting-builds)): How to get recent builds including the latest builds that pass CI.
-
-* **Automated Tools** ([automation.md](/{{page.version}}/docs/devel/automation)): Descriptions of the automation that is running on our github repository.
-
-
-## Setting up your dev environment, coding, and debugging
-
-* **Development Guide** ([development.md](/{{page.version}}/docs/devel/development)): Setting up your development environment.
-
-* **Hunting flaky tests** ([flaky-tests.md](/{{page.version}}/docs/devel/flaky-tests)): We have a goal of 99.9% flake free tests.
-  Here's how to run your tests many times.
-
-* **Logging Conventions** ([logging.md](/{{page.version}}/docs/devel/logging)]: Glog levels.
-
-* **Profiling Kubernetes** ([profiling.md](/{{page.version}}/docs/devel/profiling)): How to plug in go pprof profiler to Kubernetes.
-
-* **Instrumenting Kubernetes with a new metric**
-  ([instrumentation.md](/{{page.version}}/docs/devel/instrumentation)): How to add a new metrics to the
-  Kubernetes code base.
-
-* **Coding Conventions** ([coding-conventions.md](/{{page.version}}/docs/devel/coding-conventions)):
-  Coding style advice for contributors.
-
-
-## Developing against the Kubernetes API
-
-* API objects are explained at [http://kubernetes.io/third_party/swagger-ui/](http://kubernetes.io/third_party/swagger-ui/).
-
-* **Annotations** ([docs/user-guide/annotations.md](/{{page.version}}/docs/user-guide/annotations)): are for attaching arbitrary non-identifying metadata to objects.
-  Programs that automate Kubernetes objects may use annotations to store small amounts of their state.
-
-* **API Conventions** ([api-conventions.md](/{{page.version}}/docs/devel/api-conventions)):
-  Defining the verbs and resources used in the Kubernetes API.
-
-* **API Client Libraries** ([client-libraries.md](/{{page.version}}/docs/devel/client-libraries)):
-  A list of existing client libraries, both supported and user-contributed.
-
-
-## Writing plugins
-
-* **Authentication Plugins** ([docs/admin/authentication.md](/{{page.version}}/docs/admin/authentication)):
-  The current and planned states of authentication tokens.
-
-* **Authorization Plugins** ([docs/admin/authorization.md](/{{page.version}}/docs/admin/authorization)):
-  Authorization applies to all HTTP requests on the main apiserver port.
-  This doc explains the available authorization implementations.
-
-* **Admission Control Plugins** ([admission_control](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control.md))
-
-
-## Building releases
-
-* **Making release notes** ([making-release-notes.md](/{{page.version}}/docs/devel/making-release-notes)): Generating release nodes for a new release.
-
-* **Releasing Kubernetes** ([releasing.md](/{{page.version}}/docs/devel/releasing)): How to create a Kubernetes release (as in version)
-  and how the version information gets embedded into the built binaries.
-
-
-
diff --git a/v1.1/docs/devel/pull-requests.md b/v1.1/docs/devel/pull-requests.md
deleted file mode 100644
index 9615079d13..0000000000
--- a/v1.1/docs/devel/pull-requests.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
----
-
-An overview of how we will manage old or out-of-date pull requests.
-
-## Process
-
-We will close any pull requests older than two weeks.
-
-Exceptions can be made for PRs that have active review comments, or that are awaiting other dependent PRs.  Closed pull requests are easy to recreate, and little work is lost by closing a pull request that subsequently needs to be reopened.
-
-We want to limit the total number of PRs in flight to:
-* Maintain a clean project
-* Remove old PRs that would be difficult to rebase as the underlying code has changed over time
-* Encourage code velocity
-
-## Life of a Pull Request
-
-Unless in the last few weeks of a milestone when we need to reduce churn and stabilize, we aim to be always accepting pull requests.
-
-Either the [on call](https://github.com/kubernetes/kubernetes/wiki/Kubernetes-on-call-rotation) manually or the [submit queue](https://github.com/kubernetes/contrib/tree/master/submit-queue) automatically will manage merging PRs.
-
-There are several requirements for the submit queue to work:
-* Author must have signed CLA ("cla: yes" label added to PR)
-* No changes can be made since last lgtm label was applied
-* k8s-bot must have reported the GCE E2E build and test steps passed (Travis, Shippable and Jenkins build)
-
-Additionally, for infrequent or new contributors, we require the on call to apply the "ok-to-merge" label manually.  This is gated by the [whitelist](https://github.com/kubernetes/contrib/tree/master/submit-queue/whitelist.txt).
-
-## Automation
-
-We use a variety of automation to manage pull requests.  This automation is described in detail
-[elsewhere.](/{{page.version}}/docs/devel/automation)
-
-
-
diff --git a/v1.1/docs/devel/releasing.md b/v1.1/docs/devel/releasing.md
deleted file mode 100644
index f527616ec7..0000000000
--- a/v1.1/docs/devel/releasing.md
+++ /dev/null
@@ -1,309 +0,0 @@
----
----
-
-This document explains how to cut a release, and the theory behind it. If you
-just want to cut a release and move on with your life, you can stop reading
-after the first section.
-
-## How to cut a Kubernetes release
-
-Regardless of whether you are cutting a major or minor version, cutting a
-release breaks down into four pieces:
-
-1. Selecting release components.
-1. Tagging and merging the release in Git.
-1. Building and pushing the binaries.
-1. Writing release notes.
-
-You should progress in this strict order.
-
-### Building a New Major/Minor Version (`vX.Y.0`)
-
-#### Selecting Release Components
-
-When cutting a major/minor release, your first job is to find the branch
-point. We cut `vX.Y.0` releases directly from `master`, which is also the
-branch that we have most continuous validation on. Go first to [the main GCE
-Jenkins end-to-end job](http://go/k8s-test/job/kubernetes-e2e-gce) and next to [the
-Critical Builds page](http://go/k8s-test/view/Critical%20Builds) and hopefully find a
-recent Git hash that looks stable across at least `kubernetes-e2e-gce` and
-`kubernetes-e2e-gke-ci`. First glance through builds and look for nice solid
-rows of green builds, and then check temporally with the other Critical Builds
-to make sure they're solid around then as well. Once you find some greens, you
-can find the Git hash for a build by looking at the "Console Log", then look for
-`githash=`. You should see a line line:
-
-```shell
-+ githash=v0.20.2-322-g974377b
-```
-
-Because Jenkins builds frequently, if you're looking between jobs
-(e.g. `kubernetes-e2e-gke-ci` and `kubernetes-e2e-gce`), there may be no single
-`githash` that's been run on both jobs. In that case, take the a green
-`kubernetes-e2e-gce` build (but please check that it corresponds to a temporally
-similar build that's green on `kubernetes-e2e-gke-ci`). Lastly, if you're having
-trouble understanding why the GKE continuous integration clusters are failing
-and you're trying to cut a release, don't hesitate to contact the GKE
-oncall.
-
-Before proceeding to the next step:
-
-```shell
-export BRANCHPOINT=v0.20.2-322-g974377b
-```
-
-Where `v0.20.2-322-g974377b` is the git hash you decided on. This will become
-our (retroactive) branch point.
-
-#### Branching, Tagging and Merging
-
-Do the following:
-
-1. `export VER=x.y` (e.g. `0.20` for v0.20)
-1. cd to the base of the repo
-1. `git fetch upstream && git checkout -b release-${VER} ${BRANCHPOINT}` (you did set `${BRANCHPOINT}`, right?)
-1. Make sure you don't have any files you care about littering your repo (they
-   better be checked in or outside the repo, or the next step will delete them).
-1. `make clean && git reset --hard HEAD && git clean -xdf`
-1. `make` (TBD: you really shouldn't have to do this, but the swagger output step requires it right now)
-1. `./build/mark-new-version.sh v${VER}.0` to mark the new release and get further
-   instructions. This creates a series of commits on the branch you're working
-   on (`release-${VER}`), including forking our documentation for the release,
-   the release version commit (which is then tagged), and the post-release
-   version commit.
-1. Follow the instructions given to you by that script. They are canon for the
-   remainder of the Git process. If you don't understand something in that
-   process, please ask!
-
-**TODO**: how to fix tags, etc., if you have to shift the release branchpoint.
-
-#### Building and Pushing Binaries
-
-In your git repo (you still have `${VER}` set from above right?):
-
-1. `git checkout upstream/master && build/build-official-release.sh v${VER}.0` (the `build-official-release.sh` script is version agnostic, so it's best to run it off `master` directly).
-1. Follow the instructions given to you by that script.
-1. At this point, you've done all the Git bits, you've got all the binary bits pushed, and you've got the template for the release started on GitHub.
-
-#### Writing Release Notes
-
-[This helpful guide](/{{page.version}}/docs/devel/making-release-notes) describes how to write release
-notes for a major/minor release. In the release template on GitHub, leave the
-last PR number that the tool finds for the `.0` release, so the next releaser
-doesn't have to hunt.
-
-### Building a New Patch Release (`vX.Y.Z` for `Z > 0`)
-
-#### Selecting Release Components
-
-We cut `vX.Y.Z` releases from the `release-vX.Y` branch after all cherry picks
-to the branch have been resolved. You should ensure all outstanding cherry picks
-have been reviewed and merged and the branch validated on Jenkins (validation
-TBD). See the [Cherry Picks](/{{page.version}}/docs/devel/cherry-picks) for more information on how to
-manage cherry picks prior to cutting the release.
-
-#### Tagging and Merging
-
-1. `export VER=x.y` (e.g. `0.20` for v0.20)
-1. `export PATCH=Z` where `Z` is the patch level of `vX.Y.Z`
-1. cd to the base of the repo
-1. `git fetch upstream && git checkout -b upstream/release-${VER} release-${VER}`
-1. Make sure you don't have any files you care about littering your repo (they
-   better be checked in or outside the repo, or the next step will delete them).
-1. `make clean && git reset --hard HEAD && git clean -xdf`
-1. `make` (TBD: you really shouldn't have to do this, but the swagger output step requires it right now)
-1. `./build/mark-new-version.sh v${VER}.${PATCH}` to mark the new release and get further
-   instructions. This creates a series of commits on the branch you're working
-   on (`release-${VER}`), including forking our documentation for the release,
-   the release version commit (which is then tagged), and the post-release
-   version commit.
-1. Follow the instructions given to you by that script. They are canon for the
-   remainder of the Git process. If you don't understand something in that
-   process, please ask! When proposing PRs, you can pre-fill the body with
-   `hack/cherry_pick_list.sh upstream/release-${VER}` to inform people of what
-   is already on the branch.
-
-**TODO**: how to fix tags, etc., if the release is changed.
-
-#### Building and Pushing Binaries
-
-In your git repo (you still have `${VER}` and `${PATCH}` set from above right?):
-
-1. `git checkout upstream/master && build/build-official-release.sh
-   v${VER}.${PATCH}` (the `build-official-release.sh` script is version
-   agnostic, so it's best to run it off `master` directly).
-1. Follow the instructions given to you by that script. At this point, you've
-   done all the Git bits, you've got all the binary bits pushed, and you've got
-   the template for the release started on GitHub.
-
-#### Writing Release Notes
-
-Run `hack/cherry_pick_list.sh ${VER}.${PATCH}~1` to get the release notes for
-the patch release you just created. Feel free to prune anything internal, like
-you would for a major release, but typically for patch releases we tend to
-include everything in the release notes.
-
-## Origin of the Sources
-
-Kubernetes may be built from either a git tree (using `hack/build-go.sh`) or
-from a tarball (using either `hack/build-go.sh` or `go install`) or directly by
-the Go native build system (using `go get`).
-
-When building from git, we want to be able to insert specific information about
-the build tree at build time. In particular, we want to use the output of `git
-describe` to generate the version of Kubernetes and the status of the build
-tree (add a `-dirty` prefix if the tree was modified.)
-
-When building from a tarball or using the Go build system, we will not have
-access to the information about the git tree, but we still want to be able to
-tell whether this build corresponds to an exact release (e.g. v0.3) or is
-between releases (e.g. at some point in development between v0.3 and v0.4).
-
-## Version Number Format
-
-In order to account for these use cases, there are some specific formats that
-may end up representing the Kubernetes version. Here are a few examples:
-
-- **v0.5**: This is official version 0.5 and this version will only be used
-  when building from a clean git tree at the v0.5 git tag, or from a tree
-  extracted from the tarball corresponding to that specific release.
-- **v0.5-15-g0123abcd4567**: This is the `git describe` output and it indicates
-  that we are 15 commits past the v0.5 release and that the SHA1 of the commit
-  where the binaries were built was `0123abcd4567`. It is only possible to have
-  this level of detail in the version information when building from git, not
-  when building from a tarball.
-- **v0.5-15-g0123abcd4567-dirty** or **v0.5-dirty**: The extra `-dirty` prefix
-  means that the tree had local modifications or untracked files at the time of
-  the build, so there's no guarantee that the source code matches exactly the
-  state of the tree at the `0123abcd4567` commit or at the `v0.5` git tag
-  (resp.)
-- **v0.5-dev**: This means we are building from a tarball or using `go get` or,
-  if we have a git tree, we are using `go install` directly, so it is not
-  possible to inject the git version into the build information. Additionally,
-  this is not an official release, so the `-dev` prefix indicates that the
-  version we are building is after `v0.5` but before `v0.6`. (There is actually
-  an exception where a commit with `v0.5-dev` is not present on `v0.6`, see
-  later for details.)
-
-## Injecting Version into Binaries
-
-In order to cover the different build cases, we start by providing information
-that can be used when using only Go build tools or when we do not have the git
-version information available.
-
-To be able to provide a meaningful version in those cases, we set the contents
-of variables in a Go source file that will be used when no overrides are
-present.
-
-We are using `pkg/version/base.go` as the source of versioning in absence of
-information from git. Here is a sample of that file's contents:
-
-```go
-var (
-    gitVersion   string = "v0.4-dev"  // version from git, output of $(git describe)
-    gitCommit    string = ""          // sha1 from git, output of $(git rev-parse HEAD)
-)
-```
-
-This means a build with `go install` or `go get` or a build from a tarball will
-yield binaries that will identify themselves as `v0.4-dev` and will not be able
-to provide you with a SHA1.
-
-To add the extra versioning information when building from git, the
-`hack/build-go.sh` script will gather that information (using `git describe` and
-`git rev-parse`) and then create a `-ldflags` string to pass to `go install` and
-tell the Go linker to override the contents of those variables at build time. It
-can, for instance, tell it to override `gitVersion` and set it to
-`v0.4-13-g4567bcdef6789-dirty` and set `gitCommit` to `4567bcdef6789...` which
-is the complete SHA1 of the (dirty) tree used at build time.
-
-## Handling Official Versions
-
-Handling official versions from git is easy, as long as there is an annotated
-git tag pointing to a specific version then `git describe` will return that tag
-exactly which will match the idea of an official version (e.g. `v0.5`).
-
-Handling it on tarballs is a bit harder since the exact version string must be
-present in `pkg/version/base.go` for it to get embedded into the binaries. But
-simply creating a commit with `v0.5` on its own would mean that the commits
-coming after it would also get the `v0.5` version when built from tarball or `go
-get` while in fact they do not match `v0.5` (the one that was tagged) exactly.
-
-To handle that case, creating a new release should involve creating two adjacent
-commits where the first of them will set the version to `v0.5` and the second
-will set it to `v0.5-dev`. In that case, even in the presence of merges, there
-will be a single commit where the exact `v0.5` version will be used and all
-others around it will either have `v0.4-dev` or `v0.5-dev`.
-
-The diagram below illustrates it.
-
-![Diagram of git commits involved in the release](/images/docs/releasing.svg)
-
-After working on `v0.4-dev` and merging PR 99 we decide it is time to release
-`v0.5`. So we start a new branch, create one commit to update
-`pkg/version/base.go` to include `gitVersion = "v0.5"` and `git commit` it.
-
-We test it and make sure everything is working as expected.
-
-Before sending a PR for it, we create a second commit on that same branch,
-updating `pkg/version/base.go` to include `gitVersion = "v0.5-dev"`. That will
-ensure that further builds (from tarball or `go install`) on that tree will
-always include the `-dev` prefix and will not have a `v0.5` version (since they
-do not match the official `v0.5` exactly.)
-
-We then send PR 100 with both commits in it.
-
-Once the PR is accepted, we can use `git tag -a` to create an annotated tag
-*pointing to the one commit* that has `v0.5` in `pkg/version/base.go` and push
-it to GitHub. (Unfortunately GitHub tags/releases are not annotated tags, so
-this needs to be done from a git client and pushed to GitHub using SSH or
-HTTPS.)
-
-## Parallel Commits
-
-While we are working on releasing `v0.5`, other development takes place and
-other PRs get merged. For instance, in the example above, PRs 101 and 102 get
-merged to the master branch before the versioning PR gets merged.
-
-This is not a problem, it is only slightly inaccurate that checking out the tree
-at commit `012abc` or commit `345cde` or at the commit of the merges of PR 101
-or 102 will yield a version of `v0.4-dev` *but* those commits are not present in
-`v0.5`.
-
-In that sense, there is a small window in which commits will get a
-`v0.4-dev` or `v0.4-N-gXXX` label and while they're indeed later than `v0.4`
-but they are not really before `v0.5` in that `v0.5` does not contain those
-commits.
-
-Unfortunately, there is not much we can do about it. On the other hand, other
-projects seem to live with that and it does not really become a large problem.
-
-As an example, Docker commit a327d9b91edf has a `v1.1.1-N-gXXX` label but it is
-not present in Docker `v1.2.0`:
-
-```shell
-$ git describe a327d9b91edf
-v1.1.1-822-ga327d9b91edf
-
-$ git log --oneline v1.2.0..a327d9b91edf
-a327d9b91edf Fix data space reporting from Kb/Mb to KB/MB
-
-(Non-empty output here means the commit is not present on v1.2.0.)
-```
-
-## Release Notes
-
-No official release should be made final without properly matching release notes.
-
-There should be made available, per release, a small summary, preamble, of the
-major changes, both in terms of feature improvements/bug fixes and notes about
-functional feature changes (if any) regarding the previous released version so
-that the BOM regarding updating to it gets as obvious and trouble free as possible.
-
-After this summary, preamble, all the relevant PRs/issues that got in that
-version should be listed and linked together with a small summary understandable
-by plain mortals (in a perfect world PR/issue's title would be enough but often
-it is just too cryptic/geeky/domain-specific that it isn't).
-
-
-
diff --git a/v1.1/docs/devel/scheduler_algorithm.md b/v1.1/docs/devel/scheduler_algorithm.md
deleted file mode 100755
index d1207f98e3..0000000000
--- a/v1.1/docs/devel/scheduler_algorithm.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
----
-
-For each unscheduled Pod, the Kubernetes scheduler tries to find a node across the cluster according to a set of rules. A general introduction to the Kubernetes scheduler can be found at [scheduler.md](/{{page.version}}/docs/devel/scheduler). In this document, the algorithm of how to select a node for the Pod is explained. There are two steps before a destination node of a Pod is chosen. The first step is filtering all the nodes and the second is ranking the remaining nodes to find a best fit for the Pod.
-
-## Filtering the nodes
-
-The purpose of filtering the nodes is to filter out the nodes that do not meet certain requirements of the Pod. For example, if the free resource on a node (measured by the capacity minus the sum of the resource requests of all the Pods that already run on the node) is less than the Pod's required resource, the node should not be considered in the ranking phase so it is filtered out. Currently, there are several "predicates" implementing different filtering policies, including:
-
-- `NoDiskConflict`: Evaluate if a pod can fit due to the volumes it requests, and those that are already mounted.
-- `PodFitsResources`: Check if the free resource (CPU and Memory) meets the requirement of the Pod. The free resource is measured by the capacity minus the sum of requests of all Pods on the node. To learn more about the resource QoS in Kubernetes, please check [QoS proposal](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/proposals/resource-qos.md).
-- `PodFitsHostPorts`: Check if any HostPort required by the Pod is already occupied on the node.
-- `PodFitsHost`: Filter out all nodes except the one specified in the PodSpec's NodeName field.
-- `PodSelectorMatches`: Check if the labels of the node match the labels specified in the Pod's `nodeSelector` field ([Here](/{{page.version}}/docs/user-guide/node-selection/) is an example of how to use `nodeSelector` field).
-- `CheckNodeLabelPresence`: Check if all the specified labels exist on a node or not, regardless of the value.
-
-The details of the above predicates can be found in [plugin/pkg/scheduler/algorithm/predicates/predicates.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithm/predicates/predicates.go). All predicates mentioned above can be used in combination to perform a sophisticated filtering policy. Kubernetes uses some, but not all, of these predicates by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go).
-
-## Ranking the nodes
-
-The filtered nodes are considered suitable to host the Pod, and it is often that there are more than one nodes remaining. Kubernetes prioritizes the remaining nodes to find the "best" one for the Pod. The prioritization is performed by a set of priority functions. For each remaining node, a priority function gives a score which scales from 0-10 with 10 representing for "most preferred" and 0 for "least preferred". Each priority function is weighted by a positive number and the final score of each node is calculated by adding up all the weighted scores. For example, suppose there are two priority functions, `priorityFunc1` and `priorityFunc2` with weighting factors `weight1` and `weight2` respectively, the final score of some NodeA is:
-
-    finalScoreNodeA = (weight1 * priorityFunc1) + (weight2 * priorityFunc2)
-
-After the scores of all nodes are calculated, the node with highest score is chosen as the host of the Pod. If there are more than one nodes with equal highest scores, a random one among them is chosen.
-
-Currently, Kubernetes scheduler provides some practical priority functions, including:
-
-- `LeastRequestedPriority`: The node is prioritized based on the fraction of the node that would be free if the new Pod were scheduled onto the node. (In other words, (capacity - sum of requests of all Pods already on the node - request of Pod that is being scheduled) / capacity). CPU and memory are equally weighted. The node with the highest free fraction is the most preferred. Note that this priority function has the effect of spreading Pods across the nodes with respect to resource consumption.
-- `CalculateNodeLabelPriority`: Prefer nodes that have the specified label.
-- `BalancedResourceAllocation`: This priority function tries to put the Pod on a node such that the CPU and Memory utilization rate is balanced after the Pod is deployed.
-- `CalculateSpreadPriority`: Spread Pods by minimizing the number of Pods belonging to the same service on the same node.
-- `CalculateAntiAffinityPriority`: Spread Pods by minimizing the number of Pods belonging to the same service on nodes with the same value for a particular label.
-
-The details of the above priority functions can be found in [plugin/pkg/scheduler/algorithm/priorities](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithm/priorities/). Kubernetes uses some, but not all, of these priority functions by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go). Similar as predicates, you can combine the above priority functions and assign weight factors (positive number) to them as you want (check [scheduler.md](/{{page.version}}/docs/devel/scheduler) for how to customize).
-
-
-
diff --git a/v1.1/docs/getting-started-guides/aws.md b/v1.1/docs/getting-started-guides/aws.md
deleted file mode 100644
index 9f0429f438..0000000000
--- a/v1.1/docs/getting-started-guides/aws.md
+++ /dev/null
@@ -1,103 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-1. You need an AWS account. Visit [http://aws.amazon.com](http://aws.amazon.com) to get started
-2. Install and configure [AWS Command Line Interface](http://aws.amazon.com/cli)
-3. You need an AWS [instance profile and role](http://docs.aws.amazon.com/IAM/latest/UserGuide/instance-profiles) with EC2 full access.
-
-NOTE: This script use the 'default' AWS profile by default.
-You may explicitly set AWS profile to use using the `AWS_DEFAULT_PROFILE` environment variable:
-
-```shell
-export AWS_DEFAULT_PROFILE=myawsprofile
-```
-
-## Cluster turnup
-
-### Supported procedure: `get-kube`
-
-```shell
-#Using wget
-export KUBERNETES_PROVIDER=aws; wget -q -O - https://get.k8s.io | bash
-#Using cURL
-export KUBERNETES_PROVIDER=aws; curl -sS https://get.k8s.io | bash
-```
-
-NOTE: This script calls [cluster/kube-up.sh](http://releases.k8s.io/{{page.githubbranch}}/cluster/kube-up.sh)
-which in turn calls [cluster/aws/util.sh](http://releases.k8s.io/{{page.githubbranch}}/cluster/aws/util.sh)
-using [cluster/aws/config-default.sh](http://releases.k8s.io/{{page.githubbranch}}/cluster/aws/config-default.sh).
-
-This process takes about 5 to 10 minutes. Once the cluster is up, the IP addresses of your master and node(s) will be printed,
-as well as information about the default services running in the cluster (monitoring, logging, dns). User credentials and security
-tokens are written in `~/.kube/config`, they will be necessary to use the CLI or the HTTP Basic Auth.
-
-By default, the script will provision a new VPC and a 4 node k8s cluster in us-west-2a (Oregon) with `t2.micro` instances running on Ubuntu.
-You can override the variables defined in [config-default.sh](http://releases.k8s.io/{{page.githubbranch}}/cluster/aws/config-default.sh) to change this behavior as follows:
-
-```shell
-export KUBE_AWS_ZONE=eu-west-1c
-export NUM_MINIONS=2
-export MINION_SIZE=m3.medium
-export AWS_S3_REGION=eu-west-1
-export AWS_S3_BUCKET=mycompany-kubernetes-artifacts
-export INSTANCE_PREFIX=k8s
-...
-```
-
-It will also try to create or reuse a keypair called "kubernetes", and IAM profiles called "kubernetes-master" and "kubernetes-minion".
-If these already exist, make sure you want them to be used here.
-
-NOTE: If using an existing keypair named "kubernetes" then you must set the `AWS_SSH_KEY` key to point to your private key.
-
-### Alternatives
-
-A contributed [example](/{{page.version}}/docs/getting-started-guides/coreos/coreos_multinode_cluster) allows you to setup a Kubernetes cluster based on [CoreOS](http://www.coreos.com), using
-EC2 with user data (cloud-config).
-
-## Getting started with your cluster
-
-### Command line administration tool: `kubectl`
-
-The cluster startup script will leave you with a `kubernetes` directory on your workstation.
-Alternately, you can download the latest Kubernetes release from [this page](https://github.com/kubernetes/kubernetes/releases).
-
-Next, add the appropriate binary folder to your `PATH` to access kubectl:
-
-```shell
-# OS X
-export PATH=<path/to/kubernetes-directory>/platforms/darwin/amd64:$PATH
-# Linux
-export PATH=<path/to/kubernetes-directory>/platforms/linux/amd64:$PATH
-```
-
-An up-to-date documentation page for this tool is available here: [kubectl manual](/{{page.version}}/docs/user-guide/kubectl/kubectl)
-
-By default, `kubectl` will use the `kubeconfig` file generated during the cluster startup for authenticating against the API.
-For more information, please read [kubeconfig files](/{{page.version}}/docs/user-guide/kubeconfig-file)
-
-### Examples
-
-See [a simple nginx example](/{{page.version}}/docs/user-guide/simple-nginx) to try out your new cluster.
-
-The "Guestbook" application is another popular example to get started with Kubernetes: [guestbook example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/)
-
-For more complete applications, please look in the [examples directory](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/)
-
-## Tearing down the cluster
-
-Make sure the environment variables you used to provision your cluster are still exported, then call the following script inside the
-`kubernetes` directory:
-
-```shell
-cluster/kube-down.sh
-```
-
-## Further reading
-
-Please see the [Kubernetes docs](/{{page.version}}/docs/) for more details on administering
-and using a Kubernetes cluster.
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/azure.md b/v1.1/docs/getting-started-guides/azure.md
deleted file mode 100644
index a1d446aef1..0000000000
--- a/v1.1/docs/getting-started-guides/azure.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
----
-
-
-## Getting started on Microsoft Azure
-
-Checkout the [coreos azure getting started guide](/{{page.version}}/docs/getting-started-guides/coreos/azure/)
-
-
-
diff --git a/v1.1/docs/getting-started-guides/coreos/bare_metal_offline.md b/v1.1/docs/getting-started-guides/coreos/bare_metal_offline.md
deleted file mode 100644
index b74b83cb07..0000000000
--- a/v1.1/docs/getting-started-guides/coreos/bare_metal_offline.md
+++ /dev/null
@@ -1,694 +0,0 @@
----
----
-
-Deploy a CoreOS running Kubernetes environment. This particular guild is made to help those in an OFFLINE system, 
-whether for testing a POC before the real deal, or you are restricted to be totally offline for your applications.
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-1. Installed *CentOS 6* for PXE server
-2. At least two bare metal nodes to work with
-
-## High Level Design
-
-1. Manage the tftp directory
-  * /tftpboot/(coreos)(centos)(RHEL)
-  * /tftpboot/pxelinux.0/(MAC) -> linked to Linux image config file
-2. Update per install the link for pxelinux
-3. Update the DHCP config to reflect the host needing deployment
-4. Setup nodes to deploy CoreOS creating a etcd cluster.
-5. Have no access to the public [etcd discovery tool](https://discovery.etcd.io/).
-6. Installing the CoreOS slaves to become Kubernetes nodes.
-
-## This Guides variables
-
-| Node Description              | MAC               | IP          |
-| :---------------------------- | :---------------: | :---------: |
-| CoreOS/etcd/Kubernetes Master | d0:00:67:13:0d:00 | 10.20.30.40 |
-| CoreOS Slave 1                | d0:00:67:13:0d:01 | 10.20.30.41 |
-| CoreOS Slave 2                | d0:00:67:13:0d:02 | 10.20.30.42 |
-
-## Setup PXELINUX CentOS
-
-To setup CentOS PXELINUX environment there is a complete [guide here](http://docs.fedoraproject.org/en-US/Fedora/7/html/Installation_Guide/ap-pxe-server). This section is the abbreviated version.
-
-1. Install packages needed on CentOS
-
-```shell
-sudo yum install tftp-server dhcp syslinux
-```
-
-2. `vi /etc/xinetd.d/tftp` to enable tftp service and change disable to 'no'
-
-```conf
-disable = no
-```
-
-3. Copy over the syslinux images we will need.
-
-```shell
-su -
-mkdir -p /tftpboot
-cd /tftpboot
-cp /usr/share/syslinux/pxelinux.0 /tftpboot
-cp /usr/share/syslinux/menu.c32 /tftpboot
-cp /usr/share/syslinux/memdisk /tftpboot
-cp /usr/share/syslinux/mboot.c32 /tftpboot
-cp /usr/share/syslinux/chain.c32 /tftpboot
-
-/sbin/service dhcpd start
-/sbin/service xinetd start
-/sbin/chkconfig tftp on
-```
-
-4. Setup default boot menu
-
-```shell
-mkdir /tftpboot/pxelinux.cfg
-touch /tftpboot/pxelinux.cfg/default
-```
-
-5. Edit the menu `vi /tftpboot/pxelinux.cfg/default`
-
-```conf
-default menu.c32
-prompt 0
-timeout 15
-ONTIMEOUT local
-display boot.msg
-
-MENU TITLE Main Menu
-
-LABEL local
-        MENU LABEL Boot local hard drive
-        LOCALBOOT 0
-```
-
-Now you should have a working PXELINUX setup to image CoreOS nodes. You can verify the services by using VirtualBox locally or with bare metal servers.
-
-## Adding CoreOS to PXE
-
-This section describes how to setup the CoreOS images to live alongside a pre-existing PXELINUX environment.
-
-1. Find or create the TFTP root directory that everything will be based off of.
-    * For this document we will assume `/tftpboot/` is our root directory.
-2. Once we know and have our tftp root directory we will create a new directory structure for our CoreOS images.
-3. Download the CoreOS PXE files provided by the CoreOS team.
-
-```shell
-MY_TFTPROOT_DIR=/tftpboot
-mkdir -p $MY_TFTPROOT_DIR/images/coreos/
-cd $MY_TFTPROOT_DIR/images/coreos/
-wget http://stable.release.core-os.net/amd64-usr/current/coreos_production_pxe.vmlinuz
-wget http://stable.release.core-os.net/amd64-usr/current/coreos_production_pxe.vmlinuz.sig
-wget http://stable.release.core-os.net/amd64-usr/current/coreos_production_pxe_image.cpio.gz
-wget http://stable.release.core-os.net/amd64-usr/current/coreos_production_pxe_image.cpio.gz.sig
-gpg --verify coreos_production_pxe.vmlinuz.sig
-gpg --verify coreos_production_pxe_image.cpio.gz.sig
-```
-
-4. Edit the menu `vi /tftpboot/pxelinux.cfg/default` again
-
-```conf
-default menu.c32
-prompt 0
-timeout 300
-ONTIMEOUT local
-display boot.msg
-
-MENU TITLE Main Menu
-
-LABEL local
-        MENU LABEL Boot local hard drive
-        LOCALBOOT 0
-
-MENU BEGIN CoreOS Menu
-
-    LABEL coreos-master
-        MENU LABEL CoreOS Master
-        KERNEL images/coreos/coreos_production_pxe.vmlinuz
-        APPEND initrd=images/coreos/coreos_production_pxe_image.cpio.gz cloud-config-url=http://<xxx.xxx.xxx.xxx>/pxe-cloud-config-single-master.yml
-
-    LABEL coreos-slave
-        MENU LABEL CoreOS Slave
-        KERNEL images/coreos/coreos_production_pxe.vmlinuz
-        APPEND initrd=images/coreos/coreos_production_pxe_image.cpio.gz cloud-config-url=http://<xxx.xxx.xxx.xxx>/pxe-cloud-config-slave.yml
-MENU END
-```
-
-This configuration file will now boot from local drive but have the option to PXE image CoreOS.
-
-## DHCP configuration
-
-This section covers configuring the DHCP server to hand out our new images. In this case we are assuming that there are other servers that will boot alongside other images.
-
-1. Add the `filename` to the _host_ or _subnet_ sections.
-
-```conf
-filename "/tftpboot/pxelinux.0";
-```
-
-2. At this point we want to make pxelinux configuration files that will be the templates for the different CoreOS deployments.
-
-```conf
-subnet 10.20.30.0 netmask 255.255.255.0 {
-        next-server 10.20.30.242;
-        option broadcast-address 10.20.30.255;
-        filename "<other default image>";
-
-        ...
-        # http://www.syslinux.org/wiki/index.php/PXELINUX
-        host core_os_master {
-                hardware ethernet d0:00:67:13:0d:00;
-                option routers 10.20.30.1;
-                fixed-address 10.20.30.40;
-                option domain-name-servers 10.20.30.242;
-                filename "/pxelinux.0";
-        }
-        host core_os_slave {
-                hardware ethernet d0:00:67:13:0d:01;
-                option routers 10.20.30.1;
-                fixed-address 10.20.30.41;
-                option domain-name-servers 10.20.30.242;
-                filename "/pxelinux.0";
-        }
-        host core_os_slave2 {
-                hardware ethernet d0:00:67:13:0d:02;
-                option routers 10.20.30.1;
-                fixed-address 10.20.30.42;
-                option domain-name-servers 10.20.30.242;
-                filename "/pxelinux.0";
-        }
-        ...
-}
-```
-
-We will be specifying the node configuration later in the guide.
-
-## Kubernetes
-
-To deploy our configuration we need to create an `etcd` master. To do so we want to pxe CoreOS with a specific cloud-config.yml. There are two options we have here.
-1. Is to template the cloud config file and programmatically create new static configs for different cluster setups.
-2. Have a service discovery protocol running in our stack to do auto discovery.
-
-This demo we just make a static single `etcd` server to host our Kubernetes and `etcd` master servers.
-
-Since we are OFFLINE here most of the helping processes in CoreOS and Kubernetes are then limited. To do our setup we will then have to download and serve up our binaries for Kubernetes in our local environment.
-
-An easy solution is to host a small web server on the DHCP/TFTP host for all our binaries to make them available to the local CoreOS PXE machines.
-
-To get this up and running we are going to setup a simple `apache` server to serve our binaries needed to bootstrap Kubernetes.
-
-This is on the PXE server from the previous section:
-
-```shell
-rm /etc/httpd/conf.d/welcome.conf
-cd /var/www/html/
-wget -O kube-register  https://github.com/kelseyhightower/kube-register/releases/download/v0.0.2/kube-register-0.0.2-linux-amd64
-wget -O setup-network-environment https://github.com/kelseyhightower/setup-network-environment/releases/download/v1.0.0/setup-network-environment
-wget https://storage.googleapis.com/kubernetes-release/release/v0.15.0/bin/linux/amd64/kubernetes --no-check-certificate
-wget https://storage.googleapis.com/kubernetes-release/release/v0.15.0/bin/linux/amd64/kube-apiserver --no-check-certificate
-wget https://storage.googleapis.com/kubernetes-release/release/v0.15.0/bin/linux/amd64/kube-controller-manager --no-check-certificate
-wget https://storage.googleapis.com/kubernetes-release/release/v0.15.0/bin/linux/amd64/kube-scheduler --no-check-certificate
-wget https://storage.googleapis.com/kubernetes-release/release/v0.15.0/bin/linux/amd64/kubectl --no-check-certificate
-wget https://storage.googleapis.com/kubernetes-release/release/v0.15.0/bin/linux/amd64/kubecfg --no-check-certificate
-wget https://storage.googleapis.com/kubernetes-release/release/v0.15.0/bin/linux/amd64/kubelet --no-check-certificate
-wget https://storage.googleapis.com/kubernetes-release/release/v0.15.0/bin/linux/amd64/kube-proxy --no-check-certificate
-wget -O flanneld https://storage.googleapis.com/k8s/flanneld --no-check-certificate
-```
-
-This sets up our binaries we need to run Kubernetes. This would need to be enhanced to download from the Internet for updates in the future.
-
-Now for the good stuff!
-
-## Cloud Configs
-
-The following config files are tailored for the OFFLINE version of a Kubernetes deployment.
-
-These are based on the work found here: [master.yml](/{{page.version}}/docs/getting-started-guides/coreos/cloud-configs/master.yaml), [node.yml](/{{page.version}}/docs/getting-started-guides/coreos/cloud-configs/node.yaml)
-
-To make the setup work, you need to replace a few placeholders:
-
- - Replace `<PXE_SERVER_IP>` with your PXE server ip address (e.g. 10.20.30.242)
- - Replace `<MASTER_SERVER_IP>` with the Kubernetes master ip address (e.g. 10.20.30.40)
- - If you run a private docker registry, replace `rdocker.example.com` with your docker registry dns name.
- - If you use a proxy, replace `rproxy.example.com` with your proxy server (and port)
- - Add your own SSH public key(s) to the cloud config at the end
-
-### master.yml
-
-On the PXE server make and fill in the variables `vi /var/www/html/coreos/pxe-cloud-config-master.yml`.
-
-```yaml
-#cloud-config
----
-write_files:
-  - path: /opt/bin/waiter.sh
-    owner: root
-    content: |
-      #! /usr/bin/bash
-      until curl http://127.0.0.1:4001/v2/machines; do sleep 2; done
-  - path: /opt/bin/kubernetes-download.sh
-    owner: root
-    permissions: 0755
-    content: |
-      #! /usr/bin/bash
-      /usr/bin/wget -N -P "/opt/bin" "http://<PXE_SERVER_IP>/kubectl"
-      /usr/bin/wget -N -P "/opt/bin" "http://<PXE_SERVER_IP>/kubernetes"
-      /usr/bin/wget -N -P "/opt/bin" "http://<PXE_SERVER_IP>/kubecfg"
-      chmod +x /opt/bin/*
-  - path: /etc/profile.d/opt-path.sh
-    owner: root
-    permissions: 0755
-    content: |
-      #! /usr/bin/bash
-      PATH=$PATH/opt/bin
-coreos:
-  units:
-    - name: 10-eno1.network
-      runtime: true
-      content: |
-        [Match]
-        Name=eno1
-        [Network]
-        DHCP=yes
-    - name: 20-nodhcp.network
-      runtime: true
-      content: |
-        [Match]
-        Name=en*
-        [Network]
-        DHCP=none
-    - name: get-kube-tools.service
-      runtime: true
-      command: start
-      content: |
-        [Service]
-        ExecStartPre=-/usr/bin/mkdir -p /opt/bin
-        ExecStart=/opt/bin/kubernetes-download.sh
-        RemainAfterExit=yes
-        Type=oneshot
-    - name: setup-network-environment.service
-      command: start
-      content: |
-        [Unit]
-        Description=Setup Network Environment
-        Documentation=https://github.com/kelseyhightower/setup-network-environment
-        Requires=network-online.target
-        After=network-online.target
-        [Service]
-        ExecStartPre=-/usr/bin/mkdir -p /opt/bin
-        ExecStartPre=/usr/bin/wget -N -P /opt/bin http://<PXE_SERVER_IP>/setup-network-environment
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/setup-network-environment
-        ExecStart=/opt/bin/setup-network-environment
-        RemainAfterExit=yes
-        Type=oneshot
-    - name: etcd.service
-      command: start
-      content: |
-        [Unit]
-        Description=etcd
-        Requires=setup-network-environment.service
-        After=setup-network-environment.service
-        [Service]
-        EnvironmentFile=/etc/network-environment
-        User=etcd
-        PermissionsStartOnly=true
-        ExecStart=/usr/bin/etcd \
-        --name ${DEFAULT_IPV4} \
-        --addr ${DEFAULT_IPV4}:4001 \
-        --bind-addr 0.0.0.0 \
-        --cluster-active-size 1 \
-        --data-dir /var/lib/etcd \
-        --http-read-timeout 86400 \
-        --peer-addr ${DEFAULT_IPV4}:7001 \
-        --snapshot true
-        Restart=always
-        RestartSec=10s
-    - name: fleet.socket
-      command: start
-      content: |
-        [Socket]
-        ListenStream=/var/run/fleet.sock
-    - name: fleet.service
-      command: start
-      content: |
-        [Unit]
-        Description=fleet daemon
-        Wants=etcd.service
-        After=etcd.service
-        Wants=fleet.socket
-        After=fleet.socket
-        [Service]
-        Environment="FLEET_ETCD_SERVERS=http://127.0.0.1:4001"
-        Environment="FLEET_METADATA=role=master"
-        ExecStart=/usr/bin/fleetd
-        Restart=always
-        RestartSec=10s
-    - name: etcd-waiter.service
-      command: start
-      content: |
-        [Unit]
-        Description=etcd waiter
-        Wants=network-online.target
-        Wants=etcd.service
-        After=etcd.service
-        After=network-online.target
-        Before=flannel.service
-        Before=setup-network-environment.service
-        [Service]
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/waiter.sh
-        ExecStart=/usr/bin/bash /opt/bin/waiter.sh
-        RemainAfterExit=true
-        Type=oneshot
-    - name: flannel.service
-      command: start
-      content: |
-        [Unit]
-        Wants=etcd-waiter.service
-        After=etcd-waiter.service
-        Requires=etcd.service
-        After=etcd.service
-        After=network-online.target
-        Wants=network-online.target
-        Description=flannel is an etcd backed overlay network for containers
-        [Service]
-        Type=notify
-        ExecStartPre=-/usr/bin/mkdir -p /opt/bin
-        ExecStartPre=/usr/bin/wget -N -P /opt/bin http://<PXE_SERVER_IP>/flanneld
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/flanneld
-        ExecStartPre=-/usr/bin/etcdctl mk /coreos.com/network/config '{"Network":"10.100.0.0/16", "Backend": {"Type": "vxlan"}}'
-        ExecStart=/opt/bin/flanneld
-    - name: kube-apiserver.service
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes API Server
-        Documentation=https://github.com/kubernetes/kubernetes
-        Requires=etcd.service
-        After=etcd.service
-        [Service]
-        ExecStartPre=-/usr/bin/mkdir -p /opt/bin
-        ExecStartPre=/usr/bin/wget -N -P /opt/bin http://<PXE_SERVER_IP>/kube-apiserver
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/kube-apiserver
-        ExecStart=/opt/bin/kube-apiserver \
-        --address=0.0.0.0 \
-        --port=8080 \
-        --service-cluster-ip-range=10.100.0.0/16 \
-        --etcd-servers=http://127.0.0.1:4001 \
-        --logtostderr=true
-        Restart=always
-        RestartSec=10
-    - name: kube-controller-manager.service
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes Controller Manager
-        Documentation=https://github.com/kubernetes/kubernetes
-        Requires=kube-apiserver.service
-        After=kube-apiserver.service
-        [Service]
-        ExecStartPre=/usr/bin/wget -N -P /opt/bin http://<PXE_SERVER_IP>/kube-controller-manager
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/kube-controller-manager
-        ExecStart=/opt/bin/kube-controller-manager \
-        --master=127.0.0.1:8080 \
-        --logtostderr=true
-        Restart=always
-        RestartSec=10
-    - name: kube-scheduler.service
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes Scheduler
-        Documentation=https://github.com/kubernetes/kubernetes
-        Requires=kube-apiserver.service
-        After=kube-apiserver.service
-        [Service]
-        ExecStartPre=/usr/bin/wget -N -P /opt/bin http://<PXE_SERVER_IP>/kube-scheduler
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/kube-scheduler
-        ExecStart=/opt/bin/kube-scheduler --master=127.0.0.1:8080
-        Restart=always
-        RestartSec=10
-    - name: kube-register.service
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes Registration Service
-        Documentation=https://github.com/kelseyhightower/kube-register
-        Requires=kube-apiserver.service
-        After=kube-apiserver.service
-        Requires=fleet.service
-        After=fleet.service
-        [Service]
-        ExecStartPre=/usr/bin/wget -N -P /opt/bin http://<PXE_SERVER_IP>/kube-register
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/kube-register
-        ExecStart=/opt/bin/kube-register \
-        --metadata=role=node \
-        --fleet-endpoint=unix:///var/run/fleet.sock \
-        --healthz-port=10248 \
-        --api-endpoint=http://127.0.0.1:8080
-        Restart=always
-        RestartSec=10
-  update:
-    group: stable
-    reboot-strategy: off
-ssh_authorized_keys:
-  - ssh-rsa AAAAB3NzaC1yc2EAAAAD...
-```
-
-### node.yml
-
-On the PXE server make and fill in the variables `vi /var/www/html/coreos/pxe-cloud-config-slave.yml`.
-
-```yaml
-#cloud-config
----
-write_files:
-  - path: /etc/default/docker
-    content: |
-      DOCKER_EXTRA_OPTS='--insecure-registry="rdocker.example.com:5000"'
-coreos:
-  units:
-    - name: 10-eno1.network
-      runtime: true
-      content: |
-        [Match]
-        Name=eno1
-        [Network]
-        DHCP=yes
-    - name: 20-nodhcp.network
-      runtime: true
-      content: |
-        [Match]
-        Name=en*
-        [Network]
-        DHCP=none
-    - name: etcd.service
-      mask: true
-    - name: docker.service
-      drop-ins:
-        - name: 50-insecure-registry.conf
-          content: |
-            [Service]
-            Environment="HTTP_PROXY=http://rproxy.example.com:3128/" "NO_PROXY=localhost,127.0.0.0/8,rdocker.example.com"
-    - name: fleet.service
-      command: start
-      content: |
-        [Unit]
-        Description=fleet daemon
-        Wants=fleet.socket
-        After=fleet.socket
-        [Service]
-        Environment="FLEET_ETCD_SERVERS=http://<MASTER_SERVER_IP>:4001"
-        Environment="FLEET_METADATA=role=node"
-        ExecStart=/usr/bin/fleetd
-        Restart=always
-        RestartSec=10s
-    - name: flannel.service
-      command: start
-      content: |
-        [Unit]
-        After=network-online.target
-        Wants=network-online.target
-        Description=flannel is an etcd backed overlay network for containers
-        [Service]
-        Type=notify
-        ExecStartPre=-/usr/bin/mkdir -p /opt/bin
-        ExecStartPre=/usr/bin/wget -N -P /opt/bin http://<PXE_SERVER_IP>/flanneld
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/flanneld
-        ExecStart=/opt/bin/flanneld -etcd-endpoints http://<MASTER_SERVER_IP>:4001
-    - name: docker.service
-      command: start
-      content: |
-        [Unit]
-        After=flannel.service
-        Wants=flannel.service
-        Description=Docker Application Container Engine
-        Documentation=http://docs.docker.io
-        [Service]
-        EnvironmentFile=-/etc/default/docker
-        EnvironmentFile=/run/flannel/subnet.env
-        ExecStartPre=/bin/mount --make-rprivate /
-        ExecStart=/usr/bin/docker -d --bip=${FLANNEL_SUBNET} --mtu=${FLANNEL_MTU} -s=overlay -H fd:// ${DOCKER_EXTRA_OPTS}
-        [Install]
-        WantedBy=multi-user.target
-    - name: setup-network-environment.service
-      command: start
-      content: |
-        [Unit]
-        Description=Setup Network Environment
-        Documentation=https://github.com/kelseyhightower/setup-network-environment
-        Requires=network-online.target
-        After=network-online.target
-        [Service]
-        ExecStartPre=-/usr/bin/mkdir -p /opt/bin
-        ExecStartPre=/usr/bin/wget -N -P /opt/bin http://<PXE_SERVER_IP>/setup-network-environment
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/setup-network-environment
-        ExecStart=/opt/bin/setup-network-environment
-        RemainAfterExit=yes
-        Type=oneshot
-    - name: kube-proxy.service
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes Proxy
-        Documentation=https://github.com/kubernetes/kubernetes
-        Requires=setup-network-environment.service
-        After=setup-network-environment.service
-        [Service]
-        ExecStartPre=/usr/bin/wget -N -P /opt/bin http://<PXE_SERVER_IP>/kube-proxy
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/kube-proxy
-        ExecStart=/opt/bin/kube-proxy \
-        --etcd-servers=http://<MASTER_SERVER_IP>:4001 \
-        --logtostderr=true
-        Restart=always
-        RestartSec=10
-    - name: kube-kubelet.service
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes Kubelet
-        Documentation=https://github.com/kubernetes/kubernetes
-        Requires=setup-network-environment.service
-        After=setup-network-environment.service
-        [Service]
-        EnvironmentFile=/etc/network-environment
-        ExecStartPre=/usr/bin/wget -N -P /opt/bin http://<PXE_SERVER_IP>/kubelet
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/kubelet
-        ExecStart=/opt/bin/kubelet \
-        --address=0.0.0.0 \
-        --port=10250 \
-        --hostname-override=${DEFAULT_IPV4} \
-        --api-servers=<MASTER_SERVER_IP>:8080 \
-        --healthz-bind-address=0.0.0.0 \
-        --healthz-port=10248 \
-        --logtostderr=true
-        Restart=always
-        RestartSec=10
-  update:
-    group: stable
-    reboot-strategy: off
-ssh_authorized_keys:
-  - ssh-rsa AAAAB3NzaC1yc2EAAAAD...
-```
-
-## New pxelinux.cfg file
-
-Create a pxelinux target file for a _slave_ node: `vi /tftpboot/pxelinux.cfg/coreos-node-slave`
-
-```conf
-default coreos
-prompt 1
-timeout 15
-
-display boot.msg
-
-label coreos
-    menu default
-    kernel images/coreos/coreos_production_pxe.vmlinuz
-    append initrd=images/coreos/coreos_production_pxe_image.cpio.gz cloud-config-url=http://<pxe-host-ip>/coreos/pxe-cloud-config-slave.yml console=tty0 console=ttyS0 coreos.autologin=tty1 coreos.autologin=ttyS0
-```
-
-And one for the _master_ node: `vi /tftpboot/pxelinux.cfg/coreos-node-master`
-
-```conf
-default coreos
-prompt 1
-timeout 15
-
-display boot.msg
-
-label coreos
-    menu default
-    kernel images/coreos/coreos_production_pxe.vmlinuz
-    append initrd=images/coreos/coreos_production_pxe_image.cpio.gz cloud-config-url=http://<pxe-host-ip>/coreos/pxe-cloud-config-master.yml console=tty0 console=ttyS0 coreos.autologin=tty1 coreos.autologin=ttyS0
-```
-
-## Specify the pxelinux targets
-
-Now that we have our new targets setup for master and slave we want to configure the specific hosts to those targets. We will do this by using the pxelinux mechanism of setting a specific MAC addresses to a specific pxelinux.cfg file.
-
-Refer to the MAC address table in the beginning of this guide. Documentation for more details can be found [here](http://www.syslinux.org/wiki/index.php/PXELINUX).
-
-```shell
-cd /tftpboot/pxelinux.cfg
-ln -s coreos-node-master 01-d0-00-67-13-0d-00
-ln -s coreos-node-slave 01-d0-00-67-13-0d-01
-ln -s coreos-node-slave 01-d0-00-67-13-0d-02
-```
-
-Reboot these servers to get the images PXEd and ready for running containers!
-
-## Creating test pod
-
-Now that the CoreOS with Kubernetes installed is up and running lets spin up some Kubernetes pods to demonstrate the system.
-
-See [a simple nginx example](/{{page.version}}/docs/user-guide/simple-nginx) to try out your new cluster.
-
-For more complete applications, please look in the [examples directory](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/).
-
-## Helping commands for debugging
-
-List all keys in etcd:
-
-```shell
-etcdctl ls --recursive
-```
-
-List fleet machines
-
-```shell
-fleetctl list-machines
-```
-
-Check system status of services on master:
-
-```shell
-systemctl status kube-apiserver
-systemctl status kube-controller-manager
-systemctl status kube-scheduler
-systemctl status kube-register
-```
-
-Check system status of services on a node:
-
-```shell
-systemctl status kube-kubelet
-systemctl status docker.service
-```
-
-List Kubernetes
-
-```shell
-kubectl get pods
-kubectl get nodes
-```
-
-Kill all pods:
-
-```shell
-for i in `kubectl get pods | awk '{print $1}'`; do kubectl stop pod $i; done
-```
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/coreos/coreos_multinode_cluster.md b/v1.1/docs/getting-started-guides/coreos/coreos_multinode_cluster.md
deleted file mode 100644
index b86f435e6b..0000000000
--- a/v1.1/docs/getting-started-guides/coreos/coreos_multinode_cluster.md
+++ /dev/null
@@ -1,199 +0,0 @@
----
----
-
-Use the [master.yaml](/{{page.version}}/docs/getting-started-guides/coreos/cloud-configs/master.yaml) and [node.yaml](/{{page.version}}/docs/getting-started-guides/coreos/cloud-configs/node.yaml) cloud-configs to provision a multi-node Kubernetes cluster.
-
-> **Attention**: This requires at least CoreOS version **[695.0.0][coreos695]**, which includes `etcd2`.
-
-[coreos695]: https://coreos.com/releases/#695.0.0
-
-* TOC
-{:toc}
-
-### AWS
-
-*Attention:* Replace `<ami_image_id>` below for a [suitable version of CoreOS image for AWS](https://coreos.com/docs/running-coreos/cloud-providers/ec2/).
-
-#### Provision the Master
-
-```shell
-aws ec2 create-security-group --group-name kubernetes --description "Kubernetes Security Group"
-aws ec2 authorize-security-group-ingress --group-name kubernetes --protocol tcp --port 22 --cidr 0.0.0.0/0
-aws ec2 authorize-security-group-ingress --group-name kubernetes --protocol tcp --port 80 --cidr 0.0.0.0/0
-aws ec2 authorize-security-group-ingress --group-name kubernetes --source-security-group-name kubernetes
-```
-
-```shell
-aws ec2 run-instances \
---image-id <ami_image_id> \
---key-name <keypair> \
---region us-west-2 \
---security-groups kubernetes \
---instance-type m3.medium \
---user-data file://master.yaml
-```
-
-#### Capture the private IP address
-
-```shell
-aws ec2 describe-instances --instance-id <master-instance-id>
-```
-
-#### Edit node.yaml
-
-Edit `node.yaml` and replace all instances of `<master-private-ip>` with the private IP address of the master node.
-
-#### Provision worker nodes
-
-```shell
-aws ec2 run-instances \
---count 1 \
---image-id <ami_image_id> \
---key-name <keypair> \
---region us-west-2 \
---security-groups kubernetes \
---instance-type m3.medium \
---user-data file://node.yaml
-```
-
-### Google Compute Engine (GCE)
-
-*Attention:* Replace `<gce_image_id>` below for a [suitable version of CoreOS image for Google Compute Engine](https://coreos.com/docs/running-coreos/cloud-providers/google-compute-engine/).
-
-#### Provision the Master
-
-```shell
-gcloud compute instances create master \
---image-project coreos-cloud \
---image <gce_image_id> \
---boot-disk-size 200GB \
---machine-type n1-standard-1 \
---zone us-central1-a \
---metadata-from-file user-data=master.yaml
-```
-
-#### Capture the private IP address
-
-```shell
-gcloud compute instances list
-```
-
-#### Edit node.yaml
-
-Edit `node.yaml` and replace all instances of `<master-private-ip>` with the private IP address of the master node.
-
-#### Provision worker nodes
-
-```shell
-gcloud compute instances create node1 \
---image-project coreos-cloud \
---image <gce_image_id> \
---boot-disk-size 200GB \
---machine-type n1-standard-1 \
---zone us-central1-a \
---metadata-from-file user-data=node.yaml
-```
-
-#### Establish network connectivity
-
-Next, setup an ssh tunnel to the master so you can run kubectl from your local host.
-In one terminal, run `gcloud compute ssh master --ssh-flag="-L 8080:127.0.0.1:8080"` and in a second
-run `gcloud compute ssh master --ssh-flag="-R 8080:127.0.0.1:8080"`.
-
-### OpenStack
-
-These instructions are for running on the command line.  Most of this you can also do through the Horizon dashboard.
-These instructions were tested on the Ice House release on a Metacloud distribution of OpenStack but should be similar if not the same across other versions/distributions of OpenStack.
-
-#### Make sure you can connect with OpenStack
-
-Make sure the environment variables are set for OpenStack such as:
-
-```shell
-OS_TENANT_ID
-OS_PASSWORD
-OS_AUTH_URL
-OS_USERNAME
-OS_TENANT_NAME
-```
-
-Test this works with something like:
-
-```shell
-nova list
-```
-
-#### Get a Suitable CoreOS Image
-
-You'll need a [suitable version of CoreOS image for OpenStack](https://coreos.com/os/docs/latest/booting-on-openstack)
-Once you download that, upload it to glance.  An example is shown below:
-
-```shell
-glance image-create --name CoreOS723 \
---container-format bare --disk-format qcow2 \
---file coreos_production_openstack_image.img \
---is-public True
-```
-
-#### Create security group
-
-```shell
-nova secgroup-create kubernetes "Kubernetes Security Group"
-nova secgroup-add-rule kubernetes tcp 22 22   0.0.0.0/0
-nova secgroup-add-rule kubernetes tcp 80 80   0.0.0.0/0
-```
-
-#### Provision the Master
-
-```shell
-nova boot \
---image <image_name> \
---key-name <my_key> \
---flavor <flavor id> \
---security-group kubernetes \
---user-data files/master.yaml \
-kube-master
-```
-
-`<image_name>` is the CoreOS image name. In our example we can use the image we created in the previous step and put in 'CoreOS723'
-
-`<my_key>` is the keypair name that you already generated to access the instance.
-
-`<flavor_id>` is the flavor ID you use to size the instance.  Run `nova flavor-list`
-to get the IDs.  3 on the system this was tested with gives the m1.large size.
-
-The important part is to ensure you have the files/master.yml as this is what will do all the post boot configuration. This path is relevant so we are assuming in this example that you are running the nova command in a directory where there is a subdirectory called files that has the master.yml file in it.  Absolute paths also work.
-
-Next, assign it a public IP address:
-
-```shell
-nova floating-ip-list
-```
-
-Get an IP address that's free and run:
-
-```shell
-nova floating-ip-associate kube-master <ip address>
-```
-
-...where `<ip address>` is the IP address that was available from the `nova floating-ip-list`
-command.
-
-#### Provision Worker Nodes
-
-Edit `node.yaml`
-and replace all instances of ```<master-private-ip>```
-with the private IP address of the master node.  You can get this by running ```nova show kube-master```
-assuming you named your instance kube master.  This is not the floating IP address you just assigned it.
-
-```shell
-nova boot \
---image <image_name> \
---key-name <my_key> \
---flavor <flavor id> \
---security-group kubernetes \
---user-data files/node.yaml \
-minion01
-```
-
-This is basically the same as the master nodes but with the node.yaml post-boot script instead of the master.
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/docker-multinode.md b/v1.1/docs/getting-started-guides/docker-multinode.md
deleted file mode 100644
index d2c55f81e0..0000000000
--- a/v1.1/docs/getting-started-guides/docker-multinode.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
----
-
-This guide will set up a 2-node Kubernetes cluster, consisting of a _master_ node which hosts the API server and orchestrates work
-and a _worker_ node which receives work from the master.  You can repeat the process of adding worker nodes an arbitrary number of
-times to create larger clusters.
-
-Here's a diagram of what the final result will look like:
-
-![Kubernetes Single Node on Docker](/images/docs/k8s-docker.png)
-
-_Note_:
-These instructions are somewhat significantly more advanced than the [single node](/{{page.version}}/docs/getting-started-guides/docker) instructions.  If you are
-interested in just starting to explore Kubernetes, we recommend that you start there.
-
-_Note_:
-There is a [bug](https://github.com/docker/docker/issues/14106) in Docker 1.7.0 that prevents this from working correctly.
-Please install Docker 1.6.2 or Docker 1.7.1.
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-You need a machine with docker of right version installed.
-
-### Bootstrap Docker
-
-This guide also uses a pattern of running two instances of the Docker daemon
-   1) A _bootstrap_ Docker instance which is used to start system daemons like `flanneld` and `etcd`
-   2) A _main_ Docker instance which is used for the Kubernetes infrastructure and user's scheduled containers
-
-This pattern is necessary because the `flannel` daemon is responsible for setting up and managing the network that interconnects
-all of the Docker containers created by Kubernetes.  To achieve this, it must run outside of the _main_ Docker daemon.  However,
-it is still useful to use containers for deployment and management, so we create a simpler _bootstrap_ daemon to achieve this.
-
-You can specify k8s version on very node before install:
-
-```shell
-export K8S_VERSION=<your_k8s_version (e.g. 1.0.3)>
-```
-
-Otherwise, we'll use latest `hyperkube` image as default k8s version.
-
-## Master Node
-
-The first step in the process is to initialize the master node.
-
-Clone the Kubernetes repo, and run [master.sh](/{{page.version}}/docs/getting-started-guides/docker-multinode/master.sh) on the master machine with root:
-
-```shell
-cd kubernetes/docs/getting-started-guides/docker-multinode/
-./master.sh
-...
-`Master done!`
-```
-
-See [here](/{{page.version}}/docs/getting-started-guides/docker-multinode/master) for detailed instructions explanation.
-
-## Adding a worker node
-
-Once your master is up and running you can add one or more workers on different machines.
-
-Clone the Kubernetes repo, and run [worker.sh](/{{page.version}}/docs/getting-started-guides/docker-multinode/worker.sh) on the worker machine with root:
-
-```shell
-export MASTER_IP=<your_master_ip (e.g. 1.2.3.4)>
-cd kubernetes/docs/getting-started-guides/docker-multinode/
-./worker.sh
-...
-`Worker done!`
-````
-
-See [here](/{{page.version}}/docs/getting-started-guides/docker-multinode/worker) for detailed instructions explanation.
-
-## Deploy a DNS
-
-See [here](/{{page.version}}/docs/getting-started-guides/docker-multinode/deployDNS) for instructions.
-
-## Testing your cluster
-
-Once your cluster has been created you can [test it out](/{{page.version}}/docs/getting-started-guides/docker-multinode/testing)
-
-For more complete applications, please look in the [examples directory](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/)
diff --git a/v1.1/docs/getting-started-guides/docker-multinode/deployDNS.md b/v1.1/docs/getting-started-guides/docker-multinode/deployDNS.md
deleted file mode 100644
index 896df170f7..0000000000
--- a/v1.1/docs/getting-started-guides/docker-multinode/deployDNS.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
----
-
-### Get the template file
-
-First of all, download the template dns rc and svc file from
-
-[skydns-rc template](/{{page.version}}/docs/getting-started-guides/docker-multinode/skydns-rc.yaml.in)
-
-[skydns-svc template](/{{page.version}}/docs/getting-started-guides/docker-multinode/skydns-svc.yaml.in)
-
-### Set env
-
-Then you need to set `DNS_REPLICAS` , `DNS_DOMAIN` , `DNS_SERVER_IP` , `KUBE_SERVER` ENV.
-
-```shell
-$ export DNS_REPLICAS=1
-
-$ export DNS_DOMAIN=cluster.local # specify in startup parameter `--cluster-domain` for containerized kubelet 
-
-$ export DNS_SERVER_IP=10.0.0.10  # specify in startup parameter `--cluster-dns` for containerized kubelet 
-
-$ export KUBE_SERVER=10.10.103.250 # your master server ip, you may change it
-```
-
-### Replace the corresponding value in the template.
-
-```shell
-$ sed -e "s/{{ pillar\['dns_replicas'\] }}/${DNS_REPLICAS}/g;s/{{ pillar\['dns_domain'\] }}/${DNS_DOMAIN}/g;s/{kube_server_url}/${KUBE_SERVER}/g;" skydns-rc.yaml.in > ./skydns-rc.yaml
-
-$ sed -e "s/{{ pillar\['dns_server'\] }}/${DNS_SERVER_IP}/g" skydns-svc.yaml.in > ./skydns-svc.yaml
-```
-
-### Use `kubectl` to create skydns rc and service
-
-
-```shell
-$ kubectl -s "$KUBE_SERVER:8080" --namespace=kube-system create -f ./skydns-rc.yaml
-
-$ kubectl -s "$KUBE_SERVER:8080" --namespace=kube-system create -f ./skydns-svc.yaml
-```
-
-### Test if DNS works
-
-Follow [this link](https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns#how-do-i-test-if-it-is-working) to check it out.
-
-
-
-
-
-
diff --git a/v1.1/docs/getting-started-guides/docker-multinode/worker.md b/v1.1/docs/getting-started-guides/docker-multinode/worker.md
deleted file mode 100644
index be2d42acee..0000000000
--- a/v1.1/docs/getting-started-guides/docker-multinode/worker.md
+++ /dev/null
@@ -1,139 +0,0 @@
----
----
-
-These instructions are very similar to the master set-up above, but they are duplicated for clarity.
-You need to repeat these instructions for each node you want to join the cluster.
-We will assume that the IP address of this node is `${NODE_IP}` and you have the IP address of the master in `${MASTER_IP}` that you created in the [master instructions](/{{page.version}}/docs/getting-started-guides/docker-multinode/master).
-
-For each worker node, there are three steps:
-
-* [Set up `flanneld` on the worker node](#set-up-flanneld-on-the-worker-node)
-* [Start Kubernetes on the worker node](#start-kubernetes-on-the-worker-node)
-* [Add the worker to the cluster](#add-the-node-to-the-cluster)
-
-### Set up Flanneld on the worker node
-
-As before, the Flannel daemon is going to provide network connectivity.
-
-_Note_:
-There is a [bug](https://github.com/docker/docker/issues/14106) in Docker 1.7.0 that prevents this from working correctly.
-Please install Docker 1.6.2 or wait for Docker 1.7.1.
-
-
-#### Set up a bootstrap docker
-
-As previously, we need a second instance of the Docker daemon running to bootstrap the flannel networking.
-
-Run:
-
-```shell
-sudo sh -c 'docker -d -H unix:///var/run/docker-bootstrap.sock -p /var/run/docker-bootstrap.pid --iptables=false --ip-masq=false --bridge=none --graph=/var/lib/docker-bootstrap 2> /var/log/docker-bootstrap.log 1> /dev/null &'
-```
-
-_Important Note_:
-If you are running this on a long running system, rather than experimenting, you should run the bootstrap Docker instance under something like SysV init, upstart or systemd so that it is restarted
-across reboots and failures.
-
-#### Bring down Docker
-
-To re-configure Docker to use flannel, we need to take docker down, run flannel and then restart Docker.
-
-Turning down Docker is system dependent, it may be:
-
-```shell
-sudo /etc/init.d/docker stop
-```
-
-or
-
-```shell
-sudo systemctl stop docker
-```
-
-or it may be something else.
-
-#### Run flannel
-
-Now run flanneld itself, this call is slightly different from the above, since we point it at the etcd instance on the master.
-
-```shell
-sudo docker -H unix:///var/run/docker-bootstrap.sock run -d --net=host --privileged -v /dev/net:/dev/net quay.io/coreos/flannel:0.5.0 /opt/bin/flanneld --etcd-endpoints=http://${MASTER_IP}:4001
-```
-
-The previous command should have printed a really long hash, copy this hash.
-
-Now get the subnet settings from flannel:
-
-```shell
-sudo docker -H unix:///var/run/docker-bootstrap.sock exec <really-long-hash-from-above-here> cat /run/flannel/subnet.env
-```
-
-#### Edit the docker configuration
-
-You now need to edit the docker configuration to activate new flags.  Again, this is system specific.
-
-This may be in `/etc/default/docker` or `/etc/systemd/service/docker.service` or it may be elsewhere.
-
-Regardless, you need to add the following to the docker command line:
-
-```shell
---bip=${FLANNEL_SUBNET} --mtu=${FLANNEL_MTU}
-```
-
-#### Remove the existing Docker bridge
-
-Docker creates a bridge named `docker0` by default.  You need to remove this:
-
-```shell
-sudo /sbin/ifconfig docker0 down
-sudo brctl delbr docker0
-```
-
-You may need to install the `bridge-utils` package for the `brctl` binary.
-
-#### Restart Docker
-
-Again this is system dependent, it may be:
-
-```shell
-sudo /etc/init.d/docker start
-```
-
-it may be:
-
-```shell
-systemctl start docker
-```
-
-### Start Kubernetes on the worker node
-
-#### Run the kubelet
-
-Again this is similar to the above, but the `--api-servers` now points to the master we set up in the beginning.
-
-```shell
-sudo docker run \
-    --volume=/:/rootfs:ro \
-    --volume=/sys:/sys:ro \
-    --volume=/dev:/dev \
-    --volume=/var/lib/docker/:/var/lib/docker:rw \
-    --volume=/var/lib/kubelet/:/var/lib/kubelet:rw \
-    --volume=/var/run:/var/run:rw \
-    --net=host \
-    --privileged=true \
-    --pid=host \ 
-    -d \
-    gcr.io/google_containers/hyperkube:v1.0.1 /hyperkube kubelet --api-servers=http://${MASTER_IP}:8080 --v=2 --address=0.0.0.0 --enable-server --hostname-override=$(hostname -i) --cluster-dns=10.0.0.10 --cluster-domain=cluster.local
-```
-
-#### Run the service proxy
-
-The service proxy provides load-balancing between groups of containers defined by Kubernetes `Services`
-
-```shell
-sudo docker run -d --net=host --privileged gcr.io/google_containers/hyperkube:v1.0.1 /hyperkube proxy --master=http://${MASTER_IP}:8080 --v=2
-```
-
-### Next steps
-
-Move on to [testing your cluster](/{{page.version}}/docs/getting-started-guides/docker-multinode/testing) or add another node](#).
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/fedora/fedora_manual_config.md b/v1.1/docs/getting-started-guides/fedora/fedora_manual_config.md
deleted file mode 100644
index c865d8a1b2..0000000000
--- a/v1.1/docs/getting-started-guides/fedora/fedora_manual_config.md
+++ /dev/null
@@ -1,215 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-1. You need 2 or more machines with Fedora installed.
-
-## Instructions
-
-This is a getting started guide for [Fedora](http://fedoraproject.org).  It is a manual configuration so you understand all the underlying packages / services / ports, etc...
-
-This guide will only get ONE node (previously minion) working.  Multiple nodes require a functional [networking configuration](/{{page.version}}/docs/admin/networking)
-done outside of Kubernetes.  Although the additional Kubernetes configuration requirements should be obvious.
-
-The Kubernetes package provides a few services: kube-apiserver, kube-scheduler, kube-controller-manager, kubelet, kube-proxy.  These
-services are managed by systemd and the configuration resides in a central location: /etc/kubernetes.  We will break the services up
-between the hosts.  The first host, fed-master, will be the Kubernetes master.  This host will run the kube-apiserver, kube-controller-manager,
-and kube-scheduler.  In addition, the master will also run _etcd_ (not needed if _etcd_ runs on a different host but this guide assumes
-that _etcd_ and Kubernetes master run on the same host).  The remaining host, fed-node will be the node and run kubelet, proxy and docker.
-
-**System Information:**
-
-Hosts:
-
-```conf
-fed-master = 192.168.121.9
-fed-node = 192.168.121.65
-```
-
-**Prepare the hosts:**
-
-* Install Kubernetes on all hosts - fed-{master,node}.  This will also pull in docker. Also install etcd on fed-master. 
-  This guide has been tested with kubernetes-0.18 and beyond.
-* The [--enablerepo=updates-testing](https://fedoraproject.org/wiki/QA:Updates_Testing) directive in the yum 
-  command below will ensure that the most recent Kubernetes version that is scheduled for pre-release will
-  be installed. This should be a more recent version than the Fedora "stable" release for Kubernetes that you
-  would get without adding the directive.
-* If you want the very latest Kubernetes release [you can download and yum install the RPM directly from
-  Fedora Koji](http://koji.fedoraproject.org/koji/packageinfo?packageID=19202) instead of using the yum
-  install command below.
-
-```shell
-yum -y install --enablerepo=updates-testing kubernetes
-```
-
-* Install etcd and iptables
-
-```shell
-yum -y install etcd iptables
-```
-
-* Add master and node to /etc/hosts on all machines (not needed if hostnames already in DNS). Make sure that communication works between fed-master and fed-node by using a utility such as ping.
-
-```shell
-echo "192.168.121.9	fed-master
-192.168.121.65	fed-node" >> /etc/hosts
-```
-
-* Edit /etc/kubernetes/config which will be the same on all hosts (master and node) to contain:
-
-```shell
-# Comma separated list of nodes in the etcd cluster
-KUBE_MASTER="--master=http://fed-master:8080"
-
-# logging to stderr means we get it in the systemd journal
-KUBE_LOGTOSTDERR="--logtostderr=true"
-
-# journal message level, 0 is debug
-KUBE_LOG_LEVEL="--v=0"
-
-# Should this cluster be allowed to run privileged docker containers
-KUBE_ALLOW_PRIV="--allow-privileged=false"
-```
-
-* Disable the firewall on both the master and node, as docker does not play well with other firewall rule managers.  Please note that iptables-services does not exist on default fedora server install.
-
-```shell
-systemctl disable iptables-services firewalld
-systemctl stop iptables-services firewalld
-```
-
-**Configure the Kubernetes services on the master.**
-
-* Edit /etc/kubernetes/apiserver to appear as such.  The service-cluster-ip-range IP addresses must be an unused block of addresses, not used anywhere else. 
-They do not need to be routed or assigned to anything.
-
-```shell
-# The address on the local server to listen to.
-KUBE_API_ADDRESS="--address=0.0.0.0"
-
-# Comma separated list of nodes in the etcd cluster
-KUBE_ETCD_SERVERS="--etcd-servers=http://127.0.0.1:4001"
-
-# Address range to use for services
-KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"
-
-# Add your own!
-KUBE_API_ARGS=""
-```
-
-* Edit /etc/etcd/etcd.conf,let the etcd to listen all the ip instead of 127.0.0.1, if not, you will get the error like "connection refused". Note that Fedora 22 uses etcd 2.0, One of the changes in etcd 2.0 is that now uses port 2379 and 2380 (as opposed to etcd 0.46 which userd 4001 and 7001).
-
-```shell
-ETCD_LISTEN_CLIENT_URLS="http://0.0.0.0:4001"
-```
-
-* Create /var/run/kubernetes on master:
-
-```shell
-mkdir /var/run/kubernetes
-chown kube:kube /var/run/kubernetes
-chmod 750 /var/run/kubernetes
-```
-
-* Start the appropriate services on master:
-
-```shell
-for SERVICES in etcd kube-apiserver kube-controller-manager kube-scheduler; do
-	systemctl restart $SERVICES
-	systemctl enable $SERVICES
-	systemctl status $SERVICES
-done
-```
-
-* Addition of nodes:
-
-* Create following node.json file on Kubernetes master node:
-
-```json
-{
-    "apiVersion": "v1",
-    "kind": "Node",
-    "metadata": {
-        "name": "fed-node",
-        "labels":{ "name": "fed-node-label"}
-    },
-    "spec": {
-        "externalID": "fed-node"
-    }
-}
-```
-
-Now create a node object internally in your Kubernetes cluster by running:
-
-```shell
-$ kubectl create -f ./node.json
-
-$ kubectl get nodes
-NAME                LABELS              STATUS
-fed-node           name=fed-node-label     Unknown
-```
-
-Please note that in the above, it only creates a representation for the node
-_fed-node_ internally. It does not provision the actual _fed-node_. Also, it
-is assumed that _fed-node_ (as specified in `name`) can be resolved and is
-reachable from Kubernetes master node. This guide will discuss how to provision
-a Kubernetes node (fed-node) below.
-
-**Configure the Kubernetes services on the node.**
-
-***We need to configure the kubelet on the node.***
-
-* Edit /etc/kubernetes/kubelet to appear as such:
-
-```shell
-###
-# Kubernetes kubelet (node) config
-
-# The address for the info server to serve on (set to 0.0.0.0 or "" for all interfaces)
-KUBELET_ADDRESS="--address=0.0.0.0"
-
-# You may leave this blank to use the actual hostname
-KUBELET_HOSTNAME="--hostname-override=fed-node"
-
-# location of the api-server
-KUBELET_API_SERVER="--api-servers=http://fed-master:8080"
-
-# Add your own!
-#KUBELET_ARGS=""
-```
-
-* Start the appropriate services on the node (fed-node).
-
-```shell
-for SERVICES in kube-proxy kubelet docker; do 
-    systemctl restart $SERVICES
-    systemctl enable $SERVICES
-    systemctl status $SERVICES 
-done
-```
-
-* Check to make sure now the cluster can see the fed-node on fed-master, and its status changes to _Ready_.
-
-```shell
-kubectl get nodes
-NAME                LABELS              STATUS
-fed-node          name=fed-node-label     Ready
-```
-
-* Deletion of nodes:
-
-To delete _fed-node_ from your Kubernetes cluster, one should run the following on fed-master (Please do not do it, it is just for information):
-
-```shell
-kubectl delete -f ./node.json
-```
-
-*You should be finished!*
-
-**The cluster should be running! Launch a test pod.**
-
-You should have a functional cluster, check out [101](/{{page.version}}/docs/user-guide/walkthrough/)!
diff --git a/v1.1/docs/getting-started-guides/index.md b/v1.1/docs/getting-started-guides/index.md
deleted file mode 100644
index 9218b643b7..0000000000
--- a/v1.1/docs/getting-started-guides/index.md
+++ /dev/null
@@ -1,177 +0,0 @@
----
----
-
-Kubernetes can run on a range of platforms, from your laptop, to VMs on a cloud provider, to rack of
-bare metal servers.  The effort required to set up a cluster varies from running a single command to
-crafting your own customized cluster.  We'll guide you in picking a solution that fits for your needs.
-
-If you just want to "kick the tires" on Kubernetes, we recommend the [local Docker-based](/{{page.version}}/docs/getting-started-guides/docker) solution.
-
-The local Docker-based solution is one of several [Local cluster](#local-machine-solutions) solutions
-that are quick to set up, but are limited to running on one machine.
-
-When you are ready to scale up to more machines and higher availability, a [Hosted](#hosted-solutions)
-solution is the easiest to create and maintain.
-
-[Turn-key cloud solutions](#turn-key-cloud-solutions) require only a few commands to create
-and cover a wider range of cloud providers.
-
-[Custom solutions](#custom-solutions) require more effort to setup but cover and even
-they vary from step-by-step instructions to general advice for setting up
-a Kubernetes cluster from scratch.
-
-* TOC
-{:toc}
-
-### Local-machine Solutions
-
-Local-machine solutions create a single cluster with one or more Kubernetes nodes on a single
-physical machine.  Setup is completely automated and doesn't require a cloud provider account.
-But their size and availability is limited to that of a single machine.
-
-The local-machine solutions are:
-
-- [Local Docker-based](/{{page.version}}/docs/getting-started-guides/docker) (recommended starting point)
-- [Vagrant](/{{page.version}}/docs/getting-started-guides/vagrant) (works on any platform with Vagrant: Linux, MacOS, or Windows.)
-- [No-VM local cluster](/{{page.version}}/docs/getting-started-guides/locally) (Linux only)
-
-
-### Hosted Solutions
-
-[Google Container Engine](https://cloud.google.com/container-engine) offers managed Kubernetes
-clusters.
-
-### Turn-key Cloud Solutions
-
-These solutions allow you to create Kubernetes clusters on a range of Cloud IaaS providers with only a
-few commands, and have active community support.
-
-- [GCE](/{{page.version}}/docs/getting-started-guides/gce)
-- [AWS](/{{page.version}}/docs/getting-started-guides/aws)
-- [Azure](/{{page.version}}/docs/getting-started-guides/coreos/azure/)
-
-### Custom Solutions
-
-Kubernetes can run on a wide range of Cloud providers and bare-metal environments, and with many
-base operating systems.
-
-If you can find a guide below that matches your needs, use it.  It may be a little out of date, but
-it will be easier than starting from scratch.  If you do want to start from scratch because you
-have special requirements or just because you want to understand what is underneath a Kubernetes
-cluster, try the [Getting Started from Scratch](/{{page.version}}/docs/getting-started-guides/scratch) guide.
-
-If you are interested in supporting Kubernetes on a new platform, check out our [advice for
-writing a new solution](/{{page.version}}/docs/devel/writing-a-getting-started-guide).
-
-#### Cloud
-
-These solutions are combinations of cloud provider and OS not covered by the above solutions.
-
-- [AWS + coreos](/{{page.version}}/docs/getting-started-guides/coreos)
-- [GCE + CoreOS](/{{page.version}}/docs/getting-started-guides/coreos)
-- [AWS + Ubuntu](/{{page.version}}/docs/getting-started-guides/juju)
-- [Joyent + Ubuntu](/{{page.version}}/docs/getting-started-guides/juju)
-- [Rackspace + CoreOS](/{{page.version}}/docs/getting-started-guides/rackspace)
-
-#### On-Premises VMs
-
-- [Vagrant](/{{page.version}}/docs/getting-started-guides/coreos) (uses CoreOS and flannel)
-- [CloudStack](/{{page.version}}/docs/getting-started-guides/cloudstack) (uses Ansible, CoreOS and flannel)
-- [Vmware](/{{page.version}}/docs/getting-started-guides/vsphere)  (uses Debian)
-- [juju.md](/{{page.version}}/docs/getting-started-guides/juju) (uses Juju, Ubuntu and flannel)
-- [Vmware](/{{page.version}}/docs/getting-started-guides/coreos)  (uses CoreOS and flannel)
-- [libvirt-coreos.md](/{{page.version}}/docs/getting-started-guides/libvirt-coreos)  (uses CoreOS)
-- [oVirt](/{{page.version}}/docs/getting-started-guides/ovirt)
-- [libvirt](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster) (uses Fedora and flannel)
-- [KVM](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster)  (uses Fedora and flannel)
-
-#### Bare Metal
-
-- [Offline](/{{page.version}}/docs/getting-started-guides/coreos/bare_metal_offline) (no internet required.  Uses CoreOS and Flannel)
-- [fedora/fedora_ansible_config.md](/{{page.version}}/docs/getting-started-guides/fedora/fedora_ansible_config)
-- [Fedora single node](/{{page.version}}/docs/getting-started-guides/fedora/fedora_manual_config)
-- [Fedora multi node](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster)
-- [Centos](/{{page.version}}/docs/getting-started-guides/centos/centos_manual_config)
-- [Ubuntu](/{{page.version}}/docs/getting-started-guides/ubuntu)
-- [Docker Multi Node](/{{page.version}}/docs/getting-started-guides/docker-multinode)
-
-#### Integrations
-
-These solutions provide integration with 3rd party schedulers, resource managers, and/or lower level platforms.
-
-- [Kubernetes on Mesos](/{{page.version}}/docs/getting-started-guides/mesos)
-  - Instructions specify GCE, but are generic enough to be adapted to most existing Mesos clusters
-- [Kubernetes on DCOS](/{{page.version}}/docs/getting-started-guides/dcos)
-  - Community Edition DCOS uses AWS
-  - Enterprise Edition DCOS supports cloud hosting, on-premise VMs, and bare metal
-
-## Table of Solutions
-
-Here are all the solutions mentioned above in table form.
-
-IaaS Provider        | Config. Mgmt | OS     | Networking  | Docs                                              | Conforms | Support Level
--------------------- | ------------ | ------ | ----------  | ---------------------------------------------     | ---------| ----------------------------
-GKE                  |              |        | GCE         | [docs](https://cloud.google.com/container-engine) | ['œ“][3]   | Commercial
-Vagrant              | Saltstack    | Fedora | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/vagrant)                                | ['œ“][2]   | Project
-GCE                  | Saltstack    | Debian | GCE         | [docs](/{{page.version}}/docs/getting-started-guides/gce)                                    | ['œ“][1]   | Project
-Azure                | CoreOS       | CoreOS | Weave       | [docs](/{{page.version}}/docs/getting-started-guides/coreos/azure/)                    |          | Community ([@errordeveloper](https://github.com/errordeveloper), [@squillace](https://github.com/squillace), [@chanezon](https://github.com/chanezon), [@crossorigin](https://github.com/crossorigin))
-Docker Single Node   | custom       | N/A    | local       | [docs](/{{page.version}}/docs/getting-started-guides/docker)                                 |          | Project ([@brendandburns](https://github.com/brendandburns))
-Docker Multi Node    | Flannel      | N/A    | local       | [docs](/{{page.version}}/docs/getting-started-guides/docker-multinode)                       |          | Project ([@brendandburns](https://github.com/brendandburns))
-Bare-metal           | Ansible      | Fedora | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/fedora/fedora_ansible_config)           |          | Project
-Digital Ocean        | custom       | Fedora | Calico      | [docs](/{{page.version}}/docs/getting-started-guides/fedora/fedora-calico)                   |          | Community (@djosborne)
-Bare-metal           | custom       | Fedora | _none_      | [docs](/{{page.version}}/docs/getting-started-guides/fedora/fedora_manual_config)            |          | Project
-Bare-metal           | custom       | Fedora | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
-libvirt              | custom       | Fedora | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
-KVM                  | custom       | Fedora | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
-Mesos/Docker         | custom       | Ubuntu | Docker      | [docs](/{{page.version}}/docs/getting-started-guides/mesos-docker)                           |          | Community ([Kubernetes-Mesos Authors](https://github.com/mesosphere/kubernetes-mesos/blob/master/AUTHORS.md))
-Mesos/GCE            |              |        |             | [docs](/{{page.version}}/docs/getting-started-guides/mesos)                                  |          | Community ([Kubernetes-Mesos Authors](https://github.com/mesosphere/kubernetes-mesos/blob/master/AUTHORS.md))
-DCOS                 | Marathon   | CoreOS/Alpine | custom | [docs](/{{page.version}}/docs/getting-started-guides/dcos)                                   |          | Community ([Kubernetes-Mesos Authors](https://github.com/mesosphere/kubernetes-mesos/blob/master/AUTHORS.md))
-AWS                  | CoreOS       | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/coreos)                                 |          | Community
-GCE                  | CoreOS       | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/coreos)                                 |          | Community ([@pires](https://github.com/pires))
-Vagrant              | CoreOS       | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/coreos)                                 |          | Community ([@pires](https://github.com/pires), [@AntonioMeireles](https://github.com/AntonioMeireles))
-Bare-metal (Offline) | CoreOS       | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/coreos/bare_metal_offline)              |          | Community ([@jeffbean](https://github.com/jeffbean))
-Bare-metal           | CoreOS       | CoreOS | Calico      | [docs](/{{page.version}}/docs/getting-started-guides/coreos/bare_metal_calico)               |          | Community ([@caseydavenport](https://github.com/caseydavenport))
-CloudStack           | Ansible      | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/cloudstack)                             |          | Community ([@runseb](https://github.com/runseb))
-Vmware               |              | Debian | OVS         | [docs](/{{page.version}}/docs/getting-started-guides/vsphere)                                |          | Community ([@pietern](https://github.com/pietern))
-Bare-metal           | custom       | CentOS | _none_      | [docs](/{{page.version}}/docs/getting-started-guides/centos/centos_manual_config)            |          | Community ([@coolsvap](https://github.com/coolsvap))
-AWS                  | Juju         | Ubuntu | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/juju)                                   |          | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) )
-OpenStack/HPCloud    | Juju         | Ubuntu | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/juju)                                   |          | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) )
-Joyent               | Juju         | Ubuntu | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/juju)                                   |          | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) )
-AWS                  | Saltstack    | Ubuntu | OVS         | [docs](/{{page.version}}/docs/getting-started-guides/aws)                                    |          | Community ([@justinsb](https://github.com/justinsb))
-Bare-metal           | custom       | Ubuntu | Calico      | [docs](/{{page.version}}/docs/getting-started-guides/ubuntu-calico)                          |          | Community ([@djosborne](https://github.com/djosborne))
-Bare-metal           | custom       | Ubuntu | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/ubuntu)                                 |          | Community ([@resouer](https://github.com/resouer), [@WIZARD-CXY](https://github.com/WIZARD-CXY))
-Local                |              |        | _none_      | [docs](/{{page.version}}/docs/getting-started-guides/locally)                                |          | Community ([@preillyme](https://github.com/preillyme))
-libvirt/KVM          | CoreOS       | CoreOS | libvirt/KVM | [docs](/{{page.version}}/docs/getting-started-guides/libvirt-coreos)                         |          | Community ([@lhuard1A](https://github.com/lhuard1A))
-oVirt                |              |        |             | [docs](/{{page.version}}/docs/getting-started-guides/ovirt)                                  |          | Community ([@simon3z](https://github.com/simon3z))
-Rackspace            | CoreOS       | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/rackspace)                              |          | Community ([@doublerr](https://github.com/doublerr))
-any                  | any          | any    | any         | [docs](/{{page.version}}/docs/getting-started-guides/scratch)                                |          | Community ([@erictune](https://github.com/erictune))
-
-
-*Note*: The above table is ordered by version test/used in notes followed by support level.
-
-Definition of columns:
-
-- **IaaS Provider** is who/what provides the virtual or physical machines (nodes) that Kubernetes runs on.
-- **OS** is the base operating system of the nodes.
-- **Config. Mgmt** is the configuration management system that helps install and maintain Kubernetes software on the
-  nodes.
-- **Networking** is what implements the [networking model](/{{page.version}}/docs/admin/networking).  Those with networking type
-  _none_ may not support more than one node, or may support multiple VM nodes only in the same physical node.
-- **Conformance** indicates whether a cluster created with this configuration has passed the project's conformance
-  tests for supporting the API and base features of Kubernetes v1.0.0.
-- Support Levels
-  - **Project**:  Kubernetes Committers regularly use this configuration, so it usually works with the latest release
-    of Kubernetes.
-  - **Commercial**: A commercial offering with its own support arrangements.
-  - **Community**: Actively supported by community contributions. May not work with more recent releases of Kubernetes.
-  - **Inactive**: No active maintainer.  Not recommended for first-time Kubernetes users, and may be deleted soon.
-- **Notes** is relevant information such as the version of Kubernetes used.
-
-
-<!-- reference style links below here -->
-<!-- GCE conformance test result -->
-[1]: https://gist.github.com/erictune/4cabc010906afbcc5061
-<!-- Vagrant conformance test result -->
-[2]: https://gist.github.com/derekwaynecarr/505e56036cdf010bf6b6
-<!-- GKE conformance test result -->
-[3]: https://gist.github.com/erictune/2f39b22f72565365e59b
diff --git a/v1.1/docs/getting-started-guides/locally.md b/v1.1/docs/getting-started-guides/locally.md
deleted file mode 100644
index 83dcc2981c..0000000000
--- a/v1.1/docs/getting-started-guides/locally.md
+++ /dev/null
@@ -1,116 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-### Requirements
-
-#### Linux
-
-Not running Linux? Consider running Linux in a local virtual machine with [Vagrant](/{{page.version}}/docs/getting-started-guides/vagrant), or on a cloud provider like [Google Compute Engine](/{{page.version}}/docs/getting-started-guides/gce)
-
-#### Docker
-
-At least [Docker](https://docs.docker.com/installation/#installation)
-1.3+. Ensure the Docker daemon is running and can be contacted (try `docker
-ps`).  Some of the Kubernetes components need to run as root, which normally
-works fine with docker.
-
-#### etcd
-
-You need an [etcd](https://github.com/coreos/etcd/releases) in your path, please make sure it is installed and in your ``$PATH``.
-
-#### go
-
-You need [go](https://golang.org/doc/install) at least 1.3+ in your path, please make sure it is installed and in your ``$PATH``.
-
-### Starting the cluster
-
-In a separate tab of your terminal, run the following (since one needs sudo access to start/stop Kubernetes daemons, it is easier to run the entire script as root):
-
-```shell
-cd kubernetes
-hack/local-up-cluster.sh
-```
-
-This will build and start a lightweight local cluster, consisting of a master
-and a single node. Type Control-C to shut it down.
-
-You can use the cluster/kubectl.sh script to interact with the local cluster. hack/local-up-cluster.sh will
-print the commands to run to point kubectl at the local cluster.
-
-
-### Running a container
-
-Your cluster is running, and you want to start running containers!
-
-You can now use any of the cluster/kubectl.sh commands to interact with your local setup.
-
-```shell
-cluster/kubectl.sh get pods
-cluster/kubectl.sh get services
-cluster/kubectl.sh get replicationcontrollers
-cluster/kubectl.sh run my-nginx --image=nginx --replicas=2 --port=80
-
-## begin wait for provision to complete, you can monitor the docker pull by opening a new terminal
-  sudo docker images
-  ## you should see it pulling the nginx image, once the above command returns it
-  sudo docker ps
-  ## you should see your container running!
-  exit
-## end wait
-
-## introspect Kubernetes!
-cluster/kubectl.sh get pods
-cluster/kubectl.sh get services
-cluster/kubectl.sh get replicationcontrollers
-```
-
-### Running a user defined pod
-
-Note the difference between a [container](/{{page.version}}/docs/user-guide/containers)
-and a [pod](/{{page.version}}/docs/user-guide/pods). Since you only asked for the former, Kubernetes will create a wrapper pod for you.
-However you cannot view the nginx start page on localhost. To verify that nginx is running you need to run `curl` within the docker container (try `docker exec`).
-
-You can control the specifications of a pod via a user defined manifest, and reach nginx through your browser on the port specified therein:
-
-```shell
-cluster/kubectl.sh create -f docs/user-guide/pod.yaml
-```
-
-Congratulations!
-
-### Troubleshooting
-
-#### I cannot reach service IPs on the network.
-
-Some firewall software that uses iptables may not interact well with
-kubernetes.  If you have trouble around networking, try disabling any
-firewall or other iptables-using systems, first.  Also, you can check
-if SELinux is blocking anything by running a command such as `journalctl --since yesterday | grep avc`.
-
-By default the IP range for service cluster IPs is 10.0.*.* - depending on your
-docker installation, this may conflict with IPs for containers.  If you find
-containers running with IPs in this range, edit hack/local-cluster-up.sh and
-change the service-cluster-ip-range flag to something else.
-
-#### I cannot create a replication controller with replica size greater than 1!  What gives?
-
-You are running a single node setup.  This has the limitation of only supporting a single replica of a given pod.  If you are interested in running with larger replica sizes, we encourage you to try the local vagrant setup or one of the cloud providers.
-
-#### I changed Kubernetes code, how do I run it?
-
-```shell
-cd kubernetes
-hack/build-go.sh
-hack/local-up-cluster.sh
-```
-
-#### kubectl claims to start a container but `get pods` and `docker ps` don't show it.
-
-One or more of the KUbernetes daemons might've crashed. Tail the logs of each in /tmp.
-
-#### The pods fail to connect to the services by host names
-
-The local-up-cluster.sh script doesn't start a DNS service. Similar situation can be found [here](http://issue.k8s.io/6667). You can start a manually. Related documents can be found [here](https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns#how-do-i-configure-it)
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/mesos-docker.md b/v1.1/docs/getting-started-guides/mesos-docker.md
deleted file mode 100644
index 37f2fab172..0000000000
--- a/v1.1/docs/getting-started-guides/mesos-docker.md
+++ /dev/null
@@ -1,262 +0,0 @@
----
----
-
-
-The mesos/docker provider uses docker-compose to launch Kubernetes as a Mesos framework, running in docker with its
-dependencies (etcd & mesos).
-
-* TOC
-{:toc}
-
-## Cluster Goals
-
-- kubernetes development
-- pod/service development
-- demoing
-- fast deployment
-- minimal hardware requirements
-- minimal configuration
-- entry point for exploration
-- simplified networking
-- fast end-to-end tests
-- local deployment
-
-Non-Goals:
-
-- high availability
-- fault tolerance
-- remote deployment
-- production usage
-- monitoring
-- long running
-- state persistence across restarts
-
-## Cluster Topology
-
-The cluster consists of several docker containers linked together by docker-managed hostnames:
-
-| Component                     | Hostname                    | Description                                                                             |
-|-------------------------------|-----------------------------|-----------------------------------------------------------------------------------------|
-| docker-grand-ambassador       |                             | Proxy to allow circular hostname linking in docker                                      |
-| etcd                          | etcd                        | Key/Value store used by Mesos                                                           |
-| Mesos Master                  | mesosmaster1                | REST endpoint for interacting with Mesos                                                |
-| Mesos Slave (x2)              | mesosslave1, mesosslave2    | Mesos agents that offer resources and run framework executors (e.g. Kubernetes Kublets) |
-| Kubernetes API Server         | apiserver                   | REST endpoint for interacting with Kubernetes                                           |
-| Kubernetes Controller Manager | controller                  |                                                            |
-| Kubernetes Scheduler          | scheduler                   | Schedules container deployment by accepting Mesos offers                                |
-
-## Prerequisites
-
-Required:
-
-- [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - version control system
-- [Docker CLI](https://docs.docker.com/) - container management command line client
-- [Docker Engine](https://docs.docker.com/) - container management daemon
-  - On Mac, use [Boot2Docker](http://boot2docker.io/) or [Docker Machine](https://docs.docker.com/machine/install-machine/)
-- [Docker Compose](https://docs.docker.com/compose/install/) - multi-container application orchestration
-
-Optional:
-
-- [Virtual Box](https://www.virtualbox.org/wiki/Downloads) - x86 hardware virtualizer
-  - Required by Boot2Docker and Docker Machine
-- [Golang](https://golang.org/doc/install) - Go programming language
-  - Required to build Kubernetes locally
-- [Make](https://en.wikipedia.org/wiki/Make_(software))  - Utility for building executables from source
-  - Required to build Kubernetes locally with make
-
-### Install on Mac (Homebrew)
-
-It's possible to install all of the above via [Homebrew](http://brew.sh/) on a Mac.
-
-Some steps print instructions for configuring or launching. Make sure each is properly set up before continuing to the next step.
-
-    brew install git
-    brew install caskroom/cask/brew-cask
-    brew cask install virtualbox
-    brew install docker
-    brew install boot2docker
-    boot2docker init
-    boot2docker up
-    brew install docker-compose
-
-### Install on Linux
-
-Most of the above are available via apt and yum, but depending on your distribution, you may have to install via other
-means to get the latest versions.
-
-It is recommended to use Ubuntu, simply because it best supports AUFS, used by docker to mount volumes. Alternate file
-systems may not fully support docker-in-docker.
-
-In order to build Kubernetes, the current user must be in a docker group with sudo privileges.
-See the docker docs for [instructions](https://docs.docker.com/installation/ubuntulinux/#create-a-docker-group).
-
-
-### Boot2Docker Config (Mac)
-
-If on a mac using boot2docker, the following steps will make the docker IPs (in the virtualbox VM) reachable from the
-host machine (mac).
-
-1. Set the VM's host-only network to "promiscuous mode":
-
-	  boot2docker stop
-      VBoxManage modifyvm boot2docker-vm --nicpromisc2 allow-all
-      boot2docker start
-
-    This allows the VM to accept packets that were sent to a different IP.
-
-    Since the host-only network routes traffic between VMs and the host, other VMs will also be able to access the docker
-    IPs, if they have the following route.
-
-1. Route traffic to docker through the boot2docker IP:
-
-      sudo route -n add -net 172.17.0.0 $(boot2docker ip)
-
-    Since the boot2docker IP can change when the VM is restarted, this route may need to be updated over time.
-    To delete the route later: `sudo route delete 172.17.0.0`
-
-
-## Walkthrough
-
-1. Checkout source
-
-      git clone https://github.com/kubernetes/kubernetes
-      cd kubernetes
-
-    By default, that will get you the bleeding edge of master branch.
-    You may want a [release branch](https://github.com/kubernetes/kubernetes/releases) instead,
-    if you have trouble with master.
-
-1. Build binaries
-
-    You'll need to build kubectl (CLI) for your local architecture and operating system and the rest of the server binaries for linux/amd64.
-
-    Building a new release covers both cases:
-
-      KUBERNETES_CONTRIB=mesos build/release.sh
-
-    For developers, it may be faster to [build locally](#build-locally).
-
-1. [Optional] Build docker images
-
-    The following docker images are built as part of `./cluster/kube-up.sh`, but it may make sense to build them manually the first time because it may take a while.
-
-    1. Test image includes all the dependencies required for running e2e tests.
-
-          ./cluster/mesos/docker/test/build.sh
-
-        In the future, this image may be available to download. It doesn't contain anything specific to the current release, except its build dependencies.
-
-    1. Kubernetes-Mesos image includes the compiled linux binaries.
-
-          ./cluster/mesos/docker/km/build.sh
-
-        This image needs to be built every time you recompile the server binaries.
-
-1. [Optional] Configure Mesos resources
-
-    By default, the mesos-slaves are configured to offer a fixed amount of resources (cpus, memory, disk, ports).
-    If you want to customize these values, update the `MESOS_RESOURCES` environment variables in `./cluster/mesos/docker/docker-compose.yml`.
-    If you delete the `MESOS_RESOURCES` environment variables, the resource amounts will be auto-detected based on the host resources, which will over-provision by > 2x.
-
-    If the configured resources are not available on the host, you may want to increase the resources available to Docker Engine.
-    You may have to increase you VM disk, memory, or cpu allocation in VirtualBox,
-    [Docker Machine](https://docs.docker.com/machine/#oracle-virtualbox), or
-    [Boot2Docker](https://ryanfb.github.io/etc/2015/01/28/increasing_boot2docker_allocations_on_os_x).
-
-1. Configure provider
-
-      export KUBERNETES_PROVIDER=mesos/docker
-
-    This tells cluster scripts to use the code within `cluster/mesos/docker`.
-
-1. Create cluster
-
-      ./cluster/kube-up.sh
-
-    If you manually built all the above docker images, you can skip that step during kube-up:
-
-      MESOS_DOCKER_SKIP_BUILD=true ./cluster/kube-up.sh
-
-    After deploying the cluster, `~/.kube/config` will be created or updated to configure kubectl to target the new cluster.
-
-1. Explore examples
-
-    To learn more about Pods, Volumes, Labels, Services, and Replication Controllers, start with the
-    [Kubernetes Walkthrough](/{{page.version}}/docs/user-guide/walkthrough/).
-
-    To skip to a more advanced example, see the [Guestbook Example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/)
-
-1. Destroy cluster
-
-      ./cluster/kube-down.sh
-
-## Addons
-
-The `kube-up` for the mesos/docker provider will automatically deploy KubeDNS and KubeUI addons as pods/services.
-
-Check their status with:
-
-    ./cluster/kubectl.sh get pods --namespace=kube-system
-
-### KubeUI
-
-The web-based Kubernetes UI is accessible in a browser through the API Server proxy: `https://<apiserver>:6443/ui/`.
-
-By default, basic-auth is configured with user `admin` and password `admin`.
-
-The IP of the API Server can be found using `./cluster/kubectl.sh cluster-info`.
-
-
-## End To End Testing
-
-Warning: e2e tests can take a long time to run. You may not want to run them immediately if you're just getting started.
-
-While your cluster is up, you can run the end-to-end tests:
-
-    ./cluster/test-e2e.sh
-
-Notable parameters:
-- Increase the logging verbosity: `-v=2`
-- Run only a subset of the tests (regex matching): `-ginkgo.focus=<pattern>`
-
-To build, deploy, test, and destroy, all in one command (plus unit & integration tests):
-
-    make test_e2e
-
-## Kubernetes CLI
-
-When compiling from source, it's simplest to use the `./cluster/kubectl.sh` script, which detects your platform &
-architecture and proxies commands to the appropriate `kubectl` binary.
-
-    `./cluster/kubectl.sh get pods`
-
-
-## Helpful scripts
-
-Kill all docker containers
-  
-    docker ps -q -a | xargs docker rm -f
-
-Clean up unused docker volumes
-  
-    docker run -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/docker:/var/lib/docker --rm martin/docker-cleanup-volumes
-
-## Build Locally
-
-The steps above tell you how to build in a container, for minimal local dependencies. But if you have Go and Make installed you can build locally much faster:
-
-    KUBERNETES_CONTRIB=mesos make
-
-However, if you're not on linux, you'll still need to compile the linux/amd64 server binaries:
-
-    KUBERNETES_CONTRIB=mesos build/run.sh hack/build-go.sh
-
-The above two steps should be significantly faster than cross-compiling a whole new release for every supported platform (which is what `./build/release.sh` does).
-
-Breakdown:
-
-- `KUBERNETES_CONTRIB=mesos` - enables building of the contrib/mesos binaries
-- `hack/build-go.sh` - builds the Go binaries for the current architecture (linux/amd64 when in a docker container)
-- `make` - delegates to `hack/build-go.sh`
-- `build/run.sh` - executes a command in the build container
-- `build/release.sh` - cross compiles Kubernetes for all supported architectures and operating systems (slow)
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/rkt/index.md b/v1.1/docs/getting-started-guides/rkt/index.md
deleted file mode 100644
index 909176322c..0000000000
--- a/v1.1/docs/getting-started-guides/rkt/index.md
+++ /dev/null
@@ -1,138 +0,0 @@
----
----
-
-This document describes how to run Kubernetes using [rkt](https://github.com/coreos/rkt) as a container runtime.
-We still have [a bunch of work](http://issue.k8s.io/8262) to do to make the experience with rkt wonderful, please stay tuned!
-
-### **Prerequisite**
-
-- [systemd](http://www.freedesktop.org/wiki/Software/systemd/) should be installed on the machine and should be enabled. The minimum version required at this moment (2015/09/01) is 219
-  *(Note that systemd is not required by rkt itself, we are using it here to monitor and manage the pods launched by kubelet.)*
-
-- Install the latest rkt release according to the instructions [here](https://github.com/coreos/rkt).
-  The minimum version required for now is [v0.8.0](https://github.com/coreos/rkt/releases/tag/v0.8.0).
-
-- Note that for rkt version later than v0.7.0, `metadata service` is not required for running pods in private networks. So now rkt pods will not register the metadata service be default.
-
-### Local cluster
-
-To use rkt as the container runtime, we need to supply `--container-runtime=rkt` and `--rkt-path=$PATH_TO_RKT_BINARY` to kubelet. Additionally we can provide `--rkt-stage1-image` flag
-as well to select which [stage1 image](https://github.com/coreos/rkt/blob/master/Documentation/running-lkvm-stage1.md) we want to use.
-
-If you are using the [hack/local-up-cluster.sh](https://releases.k8s.io/{{page.githubbranch}}/hack/local-up-cluster.sh) script to launch the local cluster, then you can edit the environment variable `CONTAINER_RUNTIME`, `RKT_PATH` and `RKT_STAGE1_IMAGE` to
-set these flags:
-
-```shell
-$ export CONTAINER_RUNTIME=rkt
-$ export RKT_PATH=$PATH_TO_RKT_BINARY
-$ export RKT_STAGE1_IMAGE=PATH=$PATH_TO_STAGE1_IMAGE
-```
-
-Then we can launch the local cluster using the script:
-
-```shell
-$ hack/local-up-cluster.sh
-```
-
-### CoreOS cluster on Google Compute Engine (GCE)
-
-To use rkt as the container runtime for your CoreOS cluster on GCE, you need to specify the OS distribution, project, image:
-
-```shell
-$ export KUBE_OS_DISTRIBUTION=coreos
-$ export KUBE_GCE_MINION_IMAGE=<image_id>
-$ export KUBE_GCE_MINION_PROJECT=coreos-cloud
-$ export KUBE_CONTAINER_RUNTIME=rkt
-```
-
-You can optionally choose the version of rkt used by setting `KUBE_RKT_VERSION`:
-
-```shell
-$ export KUBE_RKT_VERSION=0.8.0
-```
-
-Then you can launch the cluster by:
-
-```shell
-$ kube-up.sh
-```
-
-Note that we are still working on making all containerized the master components run smoothly in rkt. Before that we are not able to run the master node with rkt yet.
-
-### CoreOS cluster on AWS
-
-To use rkt as the container runtime for your CoreOS cluster on AWS, you need to specify the provider and OS distribution:
-
-```shell
-$ export KUBERNETES_PROVIDER=aws
-$ export KUBE_OS_DISTRIBUTION=coreos
-$ export KUBE_CONTAINER_RUNTIME=rkt
-```
-
-You can optionally choose the version of rkt used by setting `KUBE_RKT_VERSION`:
-
-```shell
-$ export KUBE_RKT_VERSION=0.8.0
-```
-
-You can optionally choose the CoreOS channel  by setting `COREOS_CHANNEL`:
-
-```shell
-$ export COREOS_CHANNEL=stable
-```
-
-Then you can launch the cluster by:
-
-```shell
-$ kube-up.sh
-```
-
-Note: CoreOS is not supported as the master using the automated launch
-scripts. The master node is always Ubuntu.
-
-### Getting started with your cluster
-
-See [a simple nginx example](/{{page.version}}/docs/user-guide/simple-nginx) to try out your new cluster.
-
-For more complete applications, please look in the [examples directory](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/).
-
-
-### Debugging
-
-Here are severals tips for you when you run into any issues.
-
-##### Check logs
-
-By default, the log verbose level is 2. In order to see more logs related to rkt, we can set the verbose level to 4.
-For local cluster, we can set the environment variable: `LOG_LEVEL=4`.
-If the cluster is using salt, we can edit the [logging.sls](https://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/pillar/logging.sls) in the saltbase.
-
-##### Check rkt pod status
-
-To check the pods' status, we can use rkt command, such as `rkt list`, `rkt status`, `rkt image list`, etc.
-More information about rkt command line can be found [here](https://github.com/coreos/rkt/blob/master/Documentation/commands.md)
-
-##### Check journal logs
-
-As we use systemd to launch rkt pods(by creating service files which will run `rkt run-prepared`, we can check the pods' log
-using `journalctl`:
-
-- Check the running state of the systemd service:
-
-```shell
-$ sudo journalctl -u $SERVICE_FILE
-```
-
-where `$SERVICE_FILE` is the name of the service file created for the pod, you can find it in the kubelet logs.
-
-##### Check the log of the container in the pod:
-
-```shell
-$ sudo journalctl -M rkt-$UUID -u $CONTAINER_NAME
-```
-
-where `$UUID` is the rkt pod's UUID, which you can find via `rkt list --full`, and `$CONTAINER_NAME` is the container's name.
-
-##### Check Kubernetes events, logs.
-
-Besides above tricks, Kubernetes also provides us handy tools for debugging the pods. More information can be found [here](/{{page.version}}/docs/user-guide/application-troubleshooting)
\ No newline at end of file
diff --git a/v1.1/docs/getting-started-guides/scratch.md b/v1.1/docs/getting-started-guides/scratch.md
deleted file mode 100644
index d1045187cc..0000000000
--- a/v1.1/docs/getting-started-guides/scratch.md
+++ /dev/null
@@ -1,828 +0,0 @@
----
----
-
-This guide is for people who want to craft a custom Kubernetes cluster.  If you
-can find an existing Getting Started Guide that meets your needs on [this
-list](/{{page.version}}/docs/getting-started-guides/README/), then we recommend using it, as you will be able to benefit
-from the experience of others.  However, if you have specific IaaS, networking,
-configuration management, or operating system requirements not met by any of
-those guides, then this guide will provide an outline of the steps you need to
-take.  Note that it requires considerably more effort than using one of the
-pre-defined guides.
-
-This guide is also useful for those wanting to understand at a high level some of the
-steps that existing cluster setup scripts are making.
-
-* TOC
-{:toc}
-
-## Designing and Preparing
-
-### Learning
-
-  1. You should be familiar with using Kubernetes already.  We suggest you set
-    up a temporary cluster by following one of the other Getting Started Guides.
-    This will help you become familiar with the CLI ([kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl)) and concepts ([pods](/{{page.version}}/docs/user-guide/pods), [services](/{{page.version}}/docs/user-guide/services), etc.) first.
-  1. You should have `kubectl` installed on your desktop.  This will happen as a side
-    effect of completing one of the other Getting Started Guides.  If not, follow the instructions
-    [here](/{{page.version}}/docs/user-guide/prereqs).
-
-### Cloud Provider
-
-Kubernetes has the concept of a Cloud Provider, which is a module which provides
-an interface for managing TCP Load Balancers, Nodes (Instances) and Networking Routes.
-The interface is defined in `pkg/cloudprovider/cloud.go`.  It is possible to
-create a custom cluster without implementing a cloud provider (for example if using
-bare-metal), and not all parts of the interface need to be implemented, depending
-on how flags are set on various components.
-
-### Nodes
-
-- You can use virtual or physical machines.
-- While you can build a cluster with 1 machine, in order to run all the examples and tests you
-  need at least 4 nodes.
-- Many Getting-started-guides make a distinction between the master node and regular nodes.  This
-  is not strictly necessary.
-- Nodes will need to run some version of Linux with the x86_64 architecture.  It may be possible
-  to run on other OSes and Architectures, but this guide does not try to assist with that.
-- Apiserver and etcd together are fine on a machine with 1 core and 1GB RAM for clusters with 10s of nodes.
-  Larger or more active clusters may benefit from more cores.
-- Other nodes can have any reasonable amount of memory and any number of cores.  They need not
-  have identical configurations.
-
-### Network
-
-Kubernetes has a distinctive [networking model](/{{page.version}}/docs/admin/networking).
-
-Kubernetes allocates an IP address to each pod.  When creating a cluster, you
-need to allocate a block of IPs for Kubernetes to use as Pod IPs.  The simplest
-approach is to allocate a different block of IPs to each node in the cluster as
-the node is added.  A process in one pod should be able to communicate with
-another pod using the IP of the second pod.  This connectivity can be
-accomplished in two ways:
-
-- Configure network to route Pod IPs
-  - Harder to setup from scratch.
-  - Google Compute Engine ([GCE](/{{page.version}}/docs/getting-started-guides/gce)) and [AWS](/{{page.version}}/docs/getting-started-guides/aws) guides use this approach.
-  - Need to make the Pod IPs routable by programming routers, switches, etc.
-  - Can be configured external to Kubernetes, or can implement in the "Routes" interface of a Cloud Provider module.
-  - Generally highest performance.
-- Create an Overlay network
-  - Easier to setup
-  - Traffic is encapsulated, so per-pod IPs are routable.
-  - Examples:
-    - [Flannel](https://github.com/coreos/flannel)
-    - [Weave](http://weave.works/)
-    - [Open vSwitch (OVS)](http://openvswitch.org/)
-  - Does not require "Routes" portion of Cloud Provider module.
-  - Reduced performance (exactly how much depends on your solution).
-
-You need to select an address range for the Pod IPs.
-
-- Various approaches:
-  - GCE: each project has its own `10.0.0.0/8`.  Carve off a `/16` for each
-    Kubernetes cluster from that space, which leaves room for several clusters.
-    Each node gets a further subdivision of this space.
-  - AWS: use one VPC for whole organization, carve off a chunk for each
-    cluster, or use different VPC for different clusters.
-  - IPv6 is not supported yet.
-- Allocate one CIDR subnet for each node's PodIPs, or a single large CIDR
-  from which smaller CIDRs are automatically allocated to each node (if nodes
-  are dynamically added).
-  - You need max-pods-per-node * max-number-of-nodes IPs in total. A `/24` per
-    node supports 254 pods per machine and is a common choice.  If IPs are
-    scarce, a `/26` (62 pods per machine) or even a `/27` (30 pods) may be sufficient.
-  - e.g. use `10.10.0.0/16` as the range for the cluster, with up to 256 nodes
-    using `10.10.0.0/24` through `10.10.255.0/24`, respectively.
-  - Need to make these routable or connect with overlay.
-
-Kubernetes also allocates an IP to each [service](/{{page.version}}/docs/user-guide/services).  However,
-service IPs do not necessarily need to be routable.  The kube-proxy takes care
-of translating Service IPs to Pod IPs before traffic leaves the node.  You do
-need to Allocate a block of IPs for services.  Call this
-`SERVICE_CLUSTER_IP_RANGE`.  For example, you could set
-`SERVICE_CLUSTER_IP_RANGE="10.0.0.0/16"`, allowing 65534 distinct services to
-be active at once.  Note that you can grow the end of this range, but you
-cannot move it without disrupting the services and pods that already use it.
-
-Also, you need to pick a static IP for master node.
-- Call this `MASTER_IP`.
-- Open any firewalls to allow access to the apiserver ports 80 and/or 443.
-- Enable ipv4 forwarding sysctl, `net.ipv4.ip_forward = 1`
-
-### Cluster Naming
-
-You should pick a name for your cluster.  Pick a short name for each cluster
-which is unique from future cluster names. This will be used in several ways:
-
-  - by kubectl to distinguish between various clusters you have access to.  You will probably want a
-    second one sometime later, such as for testing new Kubernetes releases, running in a different
-region of the world, etc.
-  - Kubernetes clusters can create cloud provider resources (e.g. AWS ELBs) and different clusters
-    need to distinguish which resources each created.  Call this `CLUSTERNAME`.
-
-### Software Binaries
-
-You will need binaries for:
-
-  - etcd
-  - A container runner, one of:
-    - docker
-    - rkt
-  - Kubernetes
-    - kubelet
-    - kube-proxy
-    - kube-apiserver
-    - kube-controller-manager
-    - kube-scheduler
-
-#### Downloading and Extracting Kubernetes Binaries
-
-A Kubernetes binary release includes all the Kubernetes binaries as well as the supported release of etcd.
-You can use a Kubernetes binary release (recommended) or build your Kubernetes binaries following the instructions in the
-[Developer Documentation](/{{page.version}}/docs/devel/).  Only using a binary release is covered in this guide.
-
-Download the [latest binary release](https://github.com/kubernetes/kubernetes/releases/latest) and unzip it.
-Then locate `./kubernetes/server/kubernetes-server-linux-amd64.tar.gz` and unzip *that*.
-Then, within the second set of unzipped files, locate `./kubernetes/server/bin`, which contains
-all the necessary binaries.
-
-#### Selecting Images
-
-You will run docker, kubelet, and kube-proxy outside of a container, the same way you would run any system daemon, so
-you just need the bare binaries.  For etcd, kube-apiserver, kube-controller-manager, and kube-scheduler,
-we recommend that you run these as containers, so you need an image to be built.
-
-You have several choices for Kubernetes images:
-
-- Use images hosted on Google Container Registry (GCR):
-  - e.g `gcr.io/google_containers/hyperkube:$TAG`, where `TAG` is the latest
-    release tag, which can be found on the [latest releases page](https://github.com/kubernetes/kubernetes/releases/latest).
-  - Ensure $TAG is the same tag as the release tag you are using for kubelet and kube-proxy.
-  - The [hyperkube](https://releases.k8s.io/{{page.githubbranch}}/cmd/hyperkube) binary is an all in one binary
-    - `hyperkube kubelet ...` runs the kublet, `hyperkube apiserver ...` runs an apiserver, etc.
-- Build your own images.
-  - Useful if you are using a private registry.
-  - The release contains files such as `./kubernetes/server/bin/kube-apiserver.tar` which
-    can be converted into docker images using a command like
-    `docker load -i kube-apiserver.tar`
-  - You can verify if the image is loaded successfully with the right repository and tag using
-    command like `docker images`
-
-For etcd, you can:
-
-- Use images hosted on Google Container Registry (GCR), such as `gcr.io/google_containers/etcd:2.0.12`
-- Use images hosted on [Docker Hub](https://hub.docker.com/search/?q=etcd) or [Quay.io](https://quay.io/repository/coreos/etcd), such as `quay.io/coreos/etcd:v2.2.0`
-- Use etcd binary included in your OS distro.
-- Build your own image
-  - You can do: `cd kubernetes/cluster/images/etcd; make`
-
-We recommend that you use the etcd version which is provided in the Kubernetes binary distribution.   The Kubernetes binaries in the release
-were tested extensively with this version of etcd and not with any other version.
-The recommended version number can also be found as the value of `ETCD_VERSION` in `kubernetes/cluster/images/etcd/Makefile`.
-
-The remainder of the document assumes that the image identifiers have been chosen and stored in corresponding env vars.  Examples (replace with latest tags and appropriate registry):
-
-  - `HYPERKUBE_IMAGE==gcr.io/google_containers/hyperkube:$TAG`
-  - `ETCD_IMAGE=gcr.io/google_containers/etcd:$ETCD_VERSION`
-
-### Security Models
-
-There are two main options for security:
-
-- Access the apiserver using HTTP.
-  - Use a firewall for security.
-  - This is easier to setup.
-- Access the apiserver using HTTPS
-  - Use https with certs, and credentials for user.
-  - This is the recommended approach.
-  - Configuring certs can be tricky.
-
-If following the HTTPS approach, you will need to prepare certs and credentials.
-
-#### Preparing Certs
-
-You need to prepare several certs:
-
-- The master needs a cert to act as an HTTPS server.
-- The kubelets optionally need certs to identify themselves as clients of the master, and when
-  serving its own API over HTTPS.
-
-Unless you plan to have a real CA generate your certs, you will need to generate a root cert and use that to sign the master, kubelet, and kubectl certs:
-
-- See function `create-certs` in `cluster/gce/util.sh`
-- See also `cluster/saltbase/salt/generate-cert/make-ca-cert.sh` and
-  `cluster/saltbase/salt/generate-cert/make-cert.sh`
-
-You will end up with the following files (we will use these variables later on):
-
-- `CA_CERT`
-  - put in on node where apiserver runs, in e.g. `/srv/kubernetes/ca.crt`.
-- `MASTER_CERT`
-  - signed by CA_CERT
-  - put in on node where apiserver runs, in e.g. `/srv/kubernetes/server.crt`
-- `MASTER_KEY `
-  - put in on node where apiserver runs, in e.g. `/srv/kubernetes/server.key`
-- `KUBELET_CERT`
-  - optional
-- `KUBELET_KEY`
-  - optional
-
-#### Preparing Credentials
-
-The admin user (and any users) need:
-
-  - a token or a password to identify them.
-  - tokens are just long alphanumeric strings, e.g. 32 chars.  See
-    - `TOKEN=$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64 | tr -d "=+/" | dd bs=32 count=1 2>/dev/null)`
-
-Your tokens and passwords need to be stored in a file for the apiserver
-to read.  This guide uses `/var/lib/kube-apiserver/known_tokens.csv`.
-The format for this file is described in the [authentication documentation](/{{page.version}}/docs/admin/authentication).
-
-For distributing credentials to clients, the convention in Kubernetes is to put the credentials
-into a [kubeconfig file](/{{page.version}}/docs/user-guide/kubeconfig-file).
-
-The kubeconfig file for the administrator can be created as follows:
-
- - If you have already used Kubernetes with a non-custom cluster (for example, used a Getting Started
-   Guide), you will already have a `$HOME/.kube/config` file.
- - You need to add certs, keys, and the master IP to the kubeconfig file:
-    - If using the firewall-only security option, set the apiserver this way:
-      - `kubectl config set-cluster $CLUSTER_NAME --server=http://$MASTER_IP --insecure-skip-tls-verify=true`
-    - Otherwise, do this to set the apiserver ip, client certs, and user credentials.
-      - `kubectl config set-cluster $CLUSTER_NAME --certificate-authority=$CA_CERT --embed-certs=true --server=https://$MASTER_IP`
-      - `kubectl config set-credentials $USER --client-certificate=$CLI_CERT --client-key=$CLI_KEY --embed-certs=true --token=$TOKEN`
-    - Set your cluster as the default cluster to use:
-      - `kubectl config set-context $CONTEXT_NAME --cluster=$CLUSTER_NAME --user=$USER`
-      - `kubectl config use-context $CONTEXT_NAME`
-
-Next, make a kubeconfig file for the kubelets and kube-proxy.  There are a couple of options for how
-many distinct files to make:
-
-  1. Use the same credential as the admin
-    - This is simplest to setup.
-  1. One token and kubeconfig file for all kubelets, one for all kube-proxy, one for admin.
-    - This mirrors what is done on GCE today
-  1. Different credentials for every kubelet, etc.
-    - We are working on this but all the pieces are not ready yet.
-
-You can make the files by copying the `$HOME/.kube/config`, by following the code
-in `cluster/gce/configure-vm.sh` or by using the following template:
-
-```yaml
-apiVersion: v1
-kind: Config
-users:
-- name: kubelet
-  user:
-    token: ${KUBELET_TOKEN}
-clusters:
-- name: local
-  cluster:
-    certificate-authority-data: ${CA_CERT_BASE64_ENCODED}
-contexts:
-- context:
-    cluster: local
-    user: kubelet
-  name: service-account-context
-current-context: service-account-context
-```
-
-Put the kubeconfig(s) on every node.  The examples later in this
-guide assume that there are kubeconfigs in `/var/lib/kube-proxy/kubeconfig` and
-`/var/lib/kubelet/kubeconfig`.
-
-## Configuring and Installing Base Software on Nodes
-
-This section discusses how to configure machines to be Kubernetes nodes.
-
-You should run three daemons on every node:
-
-  - docker or rkt
-  - kubelet
-  - kube-proxy
-
-You will also need to do assorted other configuration on top of a
-base OS install.
-
-Tip: One possible starting point is to setup a cluster using an existing Getting
-Started Guide.   After getting a cluster running, you can then copy the init.d scripts or systemd unit files from that
-cluster, and then modify them for use on your custom cluster.
-
-### Docker
-
-The minimum required Docker version will vary as the kubelet version changes.  The newest stable release is a good choice.  Kubelet will log a warning and refuse to start pods if the version is too old, so pick a version and try it.
-
-If you previously had Docker installed on a node without setting Kubernetes-specific
-options, you may have a Docker-created bridge and iptables rules.  You may want to remove these
-as follows before proceeding to configure Docker for Kubernetes.
-
-```shell
-iptables -t nat -F
-ifconfig docker0 down
-brctl delbr docker0
-```
-
-The way you configure docker will depend in whether you have chosen the routable-vip or overlay-network approaches for your network.
-Some suggested docker options:
-
-  - create your own bridge for the per-node CIDR ranges, call it cbr0, and set `--bridge=cbr0` option on docker.
-  - set `--iptables=false` so docker will not manipulate iptables for host-ports (too coarse on older docker versions, may be fixed in newer versions)
-so that kube-proxy can manage iptables instead of docker.
-  - `--ip-masq=false`
-    - if you have setup PodIPs to be routable, then you want this false, otherwise, docker will
-      rewrite the PodIP source-address to a NodeIP.
-    - some environments (e.g. GCE) still need you to masquerade out-bound traffic when it leaves the cloud environment. This is very environment specific.
-    - if you are using an overlay network, consult those instructions.
-  - `--mtu=`
-    - may be required when using Flannel, because of the extra packet size due to udp encapsulation
-  - `--insecure-registry $CLUSTER_SUBNET`
-    - to connect to a private registry, if you set one up, without using SSL.
-
-You may want to increase the number of open files for docker:
-
-   - `DOCKER_NOFILE=1000000`
-
-Where this config goes depends on your node OS.  For example, GCE's Debian-based distro uses `/etc/default/docker`.
-
-Ensure docker is working correctly on your system before proceeding with the rest of the
-installation, by following examples given in the Docker documentation.
-
-### rkt
-
-[rkt](https://github.com/coreos/rkt) is an alternative to Docker.  You only need to install one of Docker or rkt.
-The minimum version required is [v0.5.6](https://github.com/coreos/rkt/releases/tag/v0.5.6).
-
-[systemd](http://www.freedesktop.org/wiki/Software/systemd/) is required on your node to run rkt.  The
-minimum version required to match rkt v0.5.6 is
-[systemd 215](http://lists.freedesktop.org/archives/systemd-devel/2014-July/020903).
-
-[rkt metadata service](https://github.com/coreos/rkt/blob/master/Documentation/networking.md) is also required
-for rkt networking support.  You can start rkt metadata service by using command like
-`sudo systemd-run rkt metadata-service`
-
-Then you need to configure your kubelet with flag:
-
-  - `--container-runtime=rkt`
-
-### kubelet
-
-All nodes should run kubelet.  See [Selecting Binaries](#selecting-binaries).
-
-Arguments to consider:
-
-  - If following the HTTPS security approach:
-    - `--api-servers=https://$MASTER_IP`
-    - `--kubeconfig=/var/lib/kubelet/kubeconfig`
-  - Otherwise, if taking the firewall-based security approach
-    - `--api-servers=http://$MASTER_IP`
-  - `--config=/etc/kubernetes/manifests`
-  - `--cluster-dns=` to the address of the DNS server you will setup (see [Starting Addons](#starting-addons).)
-  - `--cluster-domain=` to the dns domain prefix to use for cluster DNS addresses.
-  - `--docker-root=`
-  - `--root-dir=`
-  - `--configure-cbr0=` (described above)
-  - `--register-node` (described in [Node](/{{page.version}}/docs/admin/node) documentation.)
-
-### kube-proxy
-
-All nodes should run kube-proxy.  (Running kube-proxy on a "master" node is not
-strictly required, but being consistent is easier.)   Obtain a binary as described for
-kubelet.
-
-Arguments to consider:
-
-  - If following the HTTPS security approach:
-    - `--api-servers=https://$MASTER_IP`
-    - `--kubeconfig=/var/lib/kube-proxy/kubeconfig`
-  - Otherwise, if taking the firewall-based security approach
-    - `--api-servers=http://$MASTER_IP`
-
-### Networking
-
-Each node needs to be allocated its own CIDR range for pod networking.
-Call this `NODE_X_POD_CIDR`.
-
-A bridge called `cbr0` needs to be created on each node.  The bridge is explained
-further in the [networking documentation](/{{page.version}}/docs/admin/networking).  The bridge itself
-needs an address from `$NODE_X_POD_CIDR` - by convention the first IP.  Call
-this `NODE_X_BRIDGE_ADDR`.  For example, if `NODE_X_POD_CIDR` is `10.0.0.0/16`,
-then `NODE_X_BRIDGE_ADDR` is `10.0.0.1/16`.  NOTE: this retains the `/16` suffix
-because of how this is used later.
-
-Recommended, automatic approach:
-
-  1. Set `--configure-cbr0=true` option in kubelet init script and restart kubelet service.  Kubelet will configure cbr0 automatically.
-     It will wait to do this until the node controller has set Node.Spec.PodCIDR.  Since you have not setup apiserver and node controller
-     yet, the bridge will not be setup immediately.
-
-Alternate, manual approach:
-
-  1. Set `--configure-cbr0=false` on kubelet and restart.
-  1. Create a bridge
-  - e.g. `brctl addbr cbr0`.
-  1. Set appropriate MTU
-  - `ip link set dev cbr0 mtu 1460` (NOTE: the actual value of MTU will depend on your network environment)
-  1. Add the clusters network to the bridge (docker will go on other side of bridge).
-  - e.g. `ip addr add $NODE_X_BRIDGE_ADDR dev eth0`
-  1. Turn it on
-  - e.g. `ip link set dev cbr0 up`
-
-If you have turned off Docker's IP masquerading to allow pods to talk to each
-other, then you may need to do masquerading just for destination IPs outside
-the cluster network.  For example:
-
-```shell
-iptables -w -t nat -A POSTROUTING -o eth0 -j MASQUERADE \! -d ${CLUSTER_SUBNET}
-```
-
-This will rewrite the source address from
-the PodIP to the Node IP for traffic bound outside the cluster, and kernel
-[connection tracking](http://www.iptables.info/en/connection-state)
-will ensure that responses destined to the node still reach
-the pod.
-
-NOTE: This is environment specific.  Some environments will not need
-any masquerading at all.  Others, such as GCE, will not allow pod IPs to send
-traffic to the internet, but have no problem with them inside your GCE Project.
-
-### Other
-
-- Enable auto-upgrades for your OS package manager, if desired.
-- Configure log rotation for all node components (e.g. using [logrotate](http://linux.die.net/man/8/logrotate)).
-- Setup liveness-monitoring (e.g. using [supervisord](http://supervisord.org/)).
-- Setup volume plugin support (optional)
-  - Install any client binaries for optional volume types, such as `glusterfs-client` for GlusterFS
-    volumes.
-
-### Using Configuration Management
-
-The previous steps all involved "conventional" system administration techniques for setting up
-machines.  You may want to use a Configuration Management system to automate the node configuration
-process.  There are examples of [Saltstack](/{{page.version}}/docs/admin/salt), Ansible, Juju, and CoreOS Cloud Config in the
-various Getting Started Guides.
-
-## Bootstrapping the Cluster
-
-While the basic node services (kubelet, kube-proxy, docker) are typically started and managed using
-traditional system administration/automation approaches, the remaining *master* components of Kubernetes are
-all configured and managed *by Kubernetes*:
-
-  - their options are specified in a Pod spec (yaml or json) rather than an /etc/init.d file or
-    systemd unit.
-  - they are kept running by Kubernetes rather than by init.
-
-### etcd
-
-You will need to run one or more instances of etcd.
-
-  - Recommended approach: run one etcd instance, with its log written to a directory backed
-    by durable storage (RAID, GCE PD)
-  - Alternative: run 3 or 5 etcd instances.
-    - Log can be written to non-durable storage because storage is replicated.
-    - run a single apiserver which connects to one of the etc nodes.
-
-See [cluster-troubleshooting](/{{page.version}}/docs/admin/cluster-troubleshooting) for more discussion on factors affecting cluster
-availability.
-
-To run an etcd instance:
-
-1. copy `cluster/saltbase/salt/etcd/etcd.manifest`
-1. make any modifications needed
-1. start the pod by putting it into the kubelet manifest directory
-
-### Apiserver, Controller Manager, and Scheduler
-
-The apiserver, controller manager, and scheduler will each run as a pod on the master node.
-
-For each of these components, the steps to start them running are similar:
-
-1. Start with a provided template for a pod.
-1. Set the `HYPERKUBE_IMAGE` to the values chosen in [Selecting Images](#selecting-images).
-1. Determine which flags are needed for your cluster, using the advice below each template.
-1. Set the flags to be individual strings in the command array (e.g. $ARGN below)
-1. Start the pod by putting the completed template into the kubelet manifest directory.
-1. Verify that the pod is started.
-
-#### Apiserver pod template
-
-```json
-{
-  "kind": "Pod",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "kube-apiserver"
-  },
-  "spec": {
-    "hostNetwork": true,
-    "containers": [
-      {
-        "name": "kube-apiserver",
-        "image": "${HYPERKUBE_IMAGE}",
-        "command": [
-          "/hyperkube",
-          "apiserver",
-          "$ARG1",
-          "$ARG2",
-          ...
-          "$ARGN"
-        ],
-        "ports": [
-          {
-            "name": "https",
-            "hostPort": 443,
-            "containerPort": 443
-          },
-          {
-            "name": "local",
-            "hostPort": 8080,
-            "containerPort": 8080
-          }
-        ],
-        "volumeMounts": [
-          {
-            "name": "srvkube",
-            "mountPath": "/srv/kubernetes",
-            "readOnly": true
-          },
-          {
-            "name": "etcssl",
-            "mountPath": "/etc/ssl",
-            "readOnly": true
-          }
-        ],
-        "livenessProbe": {
-          "httpGet": {
-            "path": "/healthz",
-            "port": 8080
-          },
-          "initialDelaySeconds": 15,
-          "timeoutSeconds": 15
-        }
-      }
-    ],
-    "volumes": [
-      {
-        "name": "srvkube",
-        "hostPath": {
-          "path": "/srv/kubernetes"
-        }
-      },
-      {
-        "name": "etcssl",
-        "hostPath": {
-          "path": "/etc/ssl"
-        }
-      }
-    ]
-  }
-}
-```
-
-Here are some apiserver flags you may need to set:
-
-- `--cloud-provider=` see [cloud providers](#cloud-providers)
-- `--cloud-config=` see [cloud providers](#cloud-providers)
-- `--address=${MASTER_IP}` *or* `--bind-address=127.0.0.1` and `--address=127.0.0.1` if you want to run a proxy on the master node.
-- `--cluster-name=$CLUSTER_NAME`
-- `--service-cluster-ip-range=$SERVICE_CLUSTER_IP_RANGE`
-- `--etcd-servers=http://127.0.0.1:4001`
-- `--tls-cert-file=/srv/kubernetes/server.cert`
-- `--tls-private-key-file=/srv/kubernetes/server.key`
-- `--admission-control=$RECOMMENDED_LIST`
-  - See [admission controllers](/{{page.version}}/docs/admin/admission-controllers) for recommended arguments.
-- `--allow-privileged=true`, only if you trust your cluster user to run pods as root.
-
-If you are following the firewall-only security approach, then use these arguments:
-
-- `--token-auth-file=/dev/null`
-- `--insecure-bind-address=$MASTER_IP`
-- `--advertise-address=$MASTER_IP`
-
-If you are using the HTTPS approach, then set:
-- `--client-ca-file=/srv/kubernetes/ca.crt`
-- `--token-auth-file=/srv/kubernetes/known_tokens.csv`
-- `--basic-auth-file=/srv/kubernetes/basic_auth.csv`
-
-This pod mounts several node file system directories using the  `hostPath` volumes.  Their purposes are:
-
-- The `/etc/ssl` mount allows the apiserver to find the SSL root certs so it can
-  authenticate external services, such as a cloud provider.
-  - This is not required if you do not use a cloud provider (e.g. bare-metal).
-- The `/srv/kubernetes` mount allows the apiserver to read certs and credentials stored on the
-  node disk.  These could instead be stored on a persistent disk, such as a GCE PD, or baked into the image.
-- Optionally, you may want to mount `/var/log` as well and redirect output there (not shown in template).
-  - Do this if you prefer your logs to be accessible from the root filesystem with tools like journalctl.
-
-*TODO* document proxy-ssh setup.
-
-##### Cloud Providers
-
-Apiserver supports several cloud providers.
-
-- options for `--cloud-provider` flag are `aws`, `gce`, `mesos`, `openshift`, `ovirt`, `rackspace`, `vagrant`, or unset.
-- unset used for e.g. bare metal setups.
-- support for new IaaS is added by contributing code [here](https://releases.k8s.io/{{page.githubbranch}}/pkg/cloudprovider/providers)
-
-Some cloud providers require a config file. If so, you need to put config file into apiserver image or mount through hostPath.
-
-- `--cloud-config=` set if cloud provider requires a config file.
-- Used by `aws`, `gce`, `mesos`, `openshift`, `ovirt` and `rackspace`.
-- You must put config file into apiserver image or mount through hostPath.
-- Cloud config file syntax is [Gcfg](https://code.google.com/p/gcfg/).
-- AWS format defined by type [AWSCloudConfig](https://releases.k8s.io/{{page.githubbranch}}/pkg/cloudprovider/providers/aws/aws.go)
-- There is a similar type in the corresponding file for other cloud providers.
-- GCE example: search for `gce.conf` in [this file](https://releases.k8s.io/{{page.githubbranch}}/cluster/gce/configure-vm.sh)
-
-#### Scheduler pod template
-
-Complete this template for the scheduler pod:
-
-```json
-{
-  "kind": "Pod",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "kube-scheduler"
-  },
-  "spec": {
-    "hostNetwork": true,
-    "containers": [
-      {
-        "name": "kube-scheduler",
-        "image": "$HYBERKUBE_IMAGE",
-        "command": [
-          "/hyperkube",
-          "scheduler",
-          "--master=127.0.0.1:8080",
-          "$SCHEDULER_FLAG1",
-          ...
-          "$SCHEDULER_FLAGN"
-        ],
-        "livenessProbe": {
-          "httpGet": {
-            "host" : "127.0.0.1",
-            "path": "/healthz",
-            "port": 10251
-          },
-          "initialDelaySeconds": 15,
-          "timeoutSeconds": 15
-        }
-      }
-    ]
-  }
-}
-```
-
-Typically, no additional flags are required for the scheduler.
-
-Optionally, you may want to mount `/var/log` as well and redirect output there.
-
-#### Controller Manager Template
-
-Template for controller manager pod:
-
-```json
-{
-  "kind": "Pod",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "kube-controller-manager"
-  },
-  "spec": {
-    "hostNetwork": true,
-    "containers": [
-      {
-        "name": "kube-controller-manager",
-        "image": "$HYPERKUBE_IMAGE",
-        "command": [
-          "/hyperkube",
-          "controller-manager",
-          "$CNTRLMNGR_FLAG1",
-          ...
-          "$CNTRLMNGR_FLAGN"
-        ],
-        "volumeMounts": [
-          {
-            "name": "srvkube",
-            "mountPath": "/srv/kubernetes",
-            "readOnly": true
-          },
-          {
-            "name": "etcssl",
-            "mountPath": "/etc/ssl",
-            "readOnly": true
-          }
-        ],
-        "livenessProbe": {
-          "httpGet": {
-            "host": "127.0.0.1",
-            "path": "/healthz",
-            "port": 10252
-          },
-          "initialDelaySeconds": 15,
-          "timeoutSeconds": 15
-        }
-      }
-    ],
-    "volumes": [
-      {
-        "name": "srvkube",
-        "hostPath": {
-          "path": "/srv/kubernetes"
-        }
-      },
-      {
-        "name": "etcssl",
-        "hostPath": {
-          "path": "/etc/ssl"
-        }
-      }
-    ]
-  }
-}
-```
-
-Flags to consider using with controller manager:
-
- - `--cluster-name=$CLUSTER_NAME`
- - `--cluster-cidr=`
-   - *TODO*: explain this flag.
- - `--allocate-node-cidrs=`
-   - *TODO*: explain when you want controller to do this and when you want to do it another way.
- - `--cloud-provider=` and `--cloud-config` as described in apiserver section.
- - `--service-account-private-key-file=/srv/kubernetes/server.key`, used by the [service account](/{{page.version}}/docs/user-guide/service-accounts) feature.
- - `--master=127.0.0.1:8080`
-
-#### Starting and Verifying Apiserver, Scheduler, and Controller Manager
-
-Place each completed pod template into the kubelet config dir
-(whatever `--config=` argument of kubelet is set to, typically
-`/etc/kubernetes/manifests`).  The order does not matter: scheduler and
-controller manager will retry reaching the apiserver until it is up.
-
-Use `ps` or `docker ps` to verify that each process has started.  For example, verify that kubelet has started a container for the apiserver like this:
-
-```shell
-$ sudo docker ps | grep apiserver:
-5783290746d5        gcr.io/google_containers/kube-apiserver:e36bf367342b5a80d7467fd7611ad873            "/bin/sh -c '/usr/lo'"    10 seconds ago      Up 9 seconds                              k8s_kube-apiserver.feb145e7_kube-apiserver-kubernetes-master_default_eaebc600cf80dae59902b44225f2fc0a_225a4695
-```
-
-Then try to connect to the apiserver:
-
-```shell
-$ echo $(curl -s http://localhost:8080/healthz)
-ok
-$ curl -s http://localhost:8080/api
-{
-  "versions": [
-    "v1"
-  ]
-}
-```
-
-If you have selected the `--register-node=true` option for kubelets, they will now begin self-registering with the apiserver.
-You should soon be able to see all your nodes by running the `kubectl get nodes` command.
-Otherwise, you will need to manually create node objects.
-
-### Logging
-
-**TODO** talk about starting Logging.
-
-### Monitoring
-
-**TODO** talk about starting Monitoring.
-
-### DNS
-
-**TODO** talk about starting DNS.
-
-## Troubleshooting
-
-### Running validate-cluster
-
-**TODO** explain how to use `cluster/validate-cluster.sh`
-
-### Inspect pods and services
-
-Try to run through the "Inspect your cluster" section in one of the other Getting Started Guides, such as [GCE](/{{page.version}}/docs/getting-started-guides/gce/#inspect-your-cluster).
-You should see some services.  You should also see "mirror pods" for the apiserver, scheduler and controller-manager, plus any add-ons you started.
-
-### Try Examples
-
-At this point you should be able to run through one of the basic examples, such as the [nginx example](/{{page.version}}/examples/simple-nginx).
-
-### Running the Conformance Test
-
-You may want to try to run the [Conformance test](http://releases.k8s.io/{{page.githubbranch}}/hack/conformance-test.sh).  Any failures may give a hint as to areas that need more attention.
-
-### Networking
-
-The nodes must be able to connect to each other using their private IP. Verify this by
-pinging or SSH-ing from one node to another.
-
-### Getting Help
-
-If you run into trouble, please see the section on [troubleshooting](/{{page.version}}/docs/getting-started-guides/gce#troubleshooting), post to the
-[google-containers group](https://groups.google.com/forum/#!forum/google-containers), or come ask questions on [Slack](/{{page.version}}/docs/troubleshooting#slack).
\ No newline at end of file
diff --git a/v1.1/docs/index.md b/v1.1/docs/index.md
deleted file mode 100644
index dd7900d609..0000000000
--- a/v1.1/docs/index.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
----
-
-* The [User's guide](/{{page.version}}/docs/user-guide/) is for anyone who wants to run programs and
-  services on an existing Kubernetes cluster.
-
-* The [Cluster Admin's guide](/{{page.version}}/docs/admin/) is for anyone setting up
-  a Kubernetes cluster or administering it.
-
-* The [Developer guide](/{{page.version}}/docs/devel/) is for anyone wanting to write
-  programs that access the Kubernetes API, write plugins or extensions, or
-  modify the core code of Kubernetes.
-
-* The [Kubectl Command Line Interface](/{{page.version}}/docs/user-guide/kubectl/kubectl) is a detailed reference on
-  the `kubectl` CLI.
-
-* The [API object documentation](http://kubernetes.io/third_party/swagger-ui/)
-  is a detailed description of all fields found in core API objects.
-
-* An overview of the [Design of Kubernetes](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/)
-
-* There are example files and walkthroughs in the [examples](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples)
-  folder.
-
-* If something went wrong, see the [troubleshooting](/{{page.version}}/docs/troubleshooting) document for how to debug.
-You should also check the [known issues](/{{page.version}}/docs/user-guide/known-issues) for the release you're using.
-
-* To report a security issue, see [Reporting a Security Issue](/{{page.version}}/docs/reporting-security-issues).
-
-
-
diff --git a/v1.1/docs/user-guide/accessing-the-cluster.md b/v1.1/docs/user-guide/accessing-the-cluster.md
deleted file mode 100644
index eecfaeae6c..0000000000
--- a/v1.1/docs/user-guide/accessing-the-cluster.md
+++ /dev/null
@@ -1,271 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## Accessing the cluster API
-
-### Accessing for the first time with kubectl
-
-When accessing the Kubernetes API for the first time, we suggest using the
-Kubernetes CLI, `kubectl`.
-
-To access a cluster, you need to know the location of the cluster and have credentials
-to access it.  Typically, this is automatically set-up when you work through
-though a [Getting started guide](/{{page.version}}/docs/getting-started-guides/),
-or someone else setup the cluster and provided you with credentials and a location.
-
-Check the location and credentials that kubectl knows about with this command:
-
-```shell
-$ kubectl config view
-```
-
-Many of the [examples](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/) provide an introduction to using
-kubectl and complete documentation is found in the [kubectl manual](/{{page.version}}/docs/user-guide/kubectl/kubectl).
-
-### Directly accessing the REST API
-
-Kubectl handles locating and authenticating to the apiserver.
-If you want to directly access the REST API with an http client like
-curl or wget, or a browser, there are several ways to locate and authenticate:
-
-  - Run kubectl in proxy mode.
-    - Recommended approach.
-    - Uses stored apiserver location.
-    - Verifies identity of apiserver using self-signed cert.  No MITM possible.
-    - Authenticates to apiserver.
-    - In future, may do intelligent client-side load-balancing and failover.
-  - Provide the location and credentials directly to the http client.
-    - Alternate approach.
-    - Works with some types of client code that are confused by using a proxy.
-    - Need to import a root cert into your browser to protect against MITM.
-
-#### Using kubectl proxy
-
-The following command runs kubectl in a mode where it acts as a reverse proxy.  It handles
-locating the apiserver and authenticating.
-Run it like this:
-
-```shell
-$ kubectl proxy --port=8080 &
-```
-
-See [kubectl proxy](/{{page.version}}/docs/user-guide/kubectl/kubectl_proxy) for more details.
-
-Then you can explore the API with curl, wget, or a browser, like so:
-
-```shell
-$ curl http://localhost:8080/api/
-{
-  "versions": [
-    "v1"
-  ]
-}
-```
-
-#### Without kubectl proxy
-
-It is also possible to avoid using kubectl proxy by passing an authentication token
-directly to the apiserver, like this:
-
-```shell
-$ APISERVER=$(kubectl config view | grep server | cut -f 2- -d ":" | tr -d " ")
-$ TOKEN=$(kubectl config view | grep token | cut -f 2 -d ":" | tr -d " ")
-$ curl $APISERVER/api --header "Authorization: Bearer $TOKEN" --insecure
-{
-  "versions": [
-    "v1"
-  ]
-}
-```
-
-The above example uses the `--insecure` flag.  This leaves it subject to MITM
-attacks.  When kubectl accesses the cluster it uses a stored root certificate
-and client certificates to access the server.  (These are installed in the
-`~/.kube` directory).  Since cluster certificates are typically self-signed, it
-make take special configuration to get your http client to use root
-certificate.
-
-On some clusters, the apiserver does not require authentication; it may serve
-on localhost, or be protected by a firewall.  There is not a standard
-for this.  [Configuring Access to the API](/{{page.version}}/docs/admin/accessing-the-api)
-describes how a cluster admin can configure this.  Such approaches may conflict
-with future high-availability support.
-
-### Programmatic access to the API
-
-There are [client libraries](/{{page.version}}/docs/devel/client-libraries) for accessing the API
-from several languages.  The Kubernetes project-supported
-[Go](http://releases.k8s.io/{{page.githubbranch}}/pkg/client/)
-client library can use the same [kubeconfig file](/{{page.version}}/docs/user-guide/kubeconfig-file)
-as the kubectl CLI does to locate and authenticate to the apiserver.
-
-See documentation for other libraries for how they authenticate.
-
-### Accessing the API from a Pod
-
-When accessing the API from a pod, locating and authenticating
-to the api server are somewhat different.
-
-The recommended way to locate the apiserver within the pod is with
-the `kubernetes` DNS name, which resolves to a Service IP which in turn
-will be routed to an apiserver.
-
-The recommended way to authenticate to the apiserver is with a
-[service account](/{{page.version}}/docs/user-guide/service-accounts) credential.  By kube-system, a pod
-is associated with a service account, and a credential (token) for that
-service account is placed into the filesystem tree of each container in that pod,
-at `/var/run/secrets/kubernetes.io/serviceaccount/token`.
-
-From within a pod the recommended ways to connect to API are:
-
-  - run a kubectl proxy as one of the containers in the pod, or as a background
-    process within a container.  This proxies the
-    Kubernetes API to the localhost interface of the pod, so that other processes
-    in any container of the pod can access it.  See this [example of using kubectl proxy
-    in a pod](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/kubectl-container/).
-  - use the Go client library, and create a client using the `client.NewInCluster()` factory.
-    This handles locating and authenticating to the apiserver.
-
-In each case, the credentials of the pod are used to communicate securely with the apiserver.
-
-
-## Accessing services running on the cluster
-
-The previous section was about connecting the Kubernetes API server.  This section is about
-connecting to other services running on Kubernetes cluster.  In Kubernetes, the
-[nodes](/{{page.version}}/docs/admin/node), [pods](/{{page.version}}/docs/user-guide/pods) and [services](/{{page.version}}/docs/user-guide/services) all have
-their own IPs.  In many cases, the node IPs, pod IPs, and some service IPs on a cluster will not be
-routable, so they will not be reachable from a machine outside the cluster,
-such as your desktop machine.
-
-### Ways to connect
-
-You have several options for connecting to nodes, pods and services from outside the cluster:
-
-  - Access services through public IPs.
-    - Use a service with type `NodePort` or `LoadBalancer` to make the service reachable outside
-      the cluster.  See the [services](/{{page.version}}/docs/user-guide/services) and
-      [kubectl expose](/{{page.version}}/docs/user-guide/kubectl/kubectl_expose) documentation.
-    - Depending on your cluster environment, this may just expose the service to your corporate network,
-      or it may expose it to the internet.  Think about whether the service being exposed is secure.
-      Does it do its own authentication?
-    - Place pods behind services.  To access one specific pod from a set of replicas, such as for debugging,
-      place a unique label on the pod it and create a new service which selects this label.
-    - In most cases, it should not be necessary for application developer to directly access
-      nodes via their nodeIPs.
-  - Access services, nodes, or pods using the Proxy Verb.
-    - Does apiserver authentication and authorization prior to accessing the remote service.
-      Use this if the services are not secure enough to expose to the internet, or to gain
-      access to ports on the node IP, or for debugging.
-    - Proxies may cause problems for some web applications.
-    - Only works for HTTP/HTTPS.
-    - Described [here](#discovering-builtin-services).
-  - Access from a node or pod in the cluster.
-    - Run a pod, and then connect to a shell in it using [kubectl exec](/{{page.version}}/docs/user-guide/kubectl/kubectl_exec).
-      Connect to other nodes, pods, and services from that shell.
-    - Some clusters may allow you to ssh to a node in the cluster.  From there you may be able to
-      access cluster services.  This is a non-standard method, and will work on some clusters but
-      not others.  Browsers and other tools may or may not be installed.  Cluster DNS may not work.
-
-### Discovering builtin services
-
-Typically, there are several services which are started on a cluster by kube-system. Get a list of these
-with the `kubectl cluster-info` command:
-
-```shell
-$ kubectl cluster-info
-
-  Kubernetes master is running at https://104.197.5.247
-  elasticsearch-logging is running at https://104.197.5.247/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging
-  kibana-logging is running at https://104.197.5.247/api/v1/proxy/namespaces/kube-system/services/kibana-logging
-  kube-dns is running at https://104.197.5.247/api/v1/proxy/namespaces/kube-system/services/kube-dns
-  grafana is running at https://104.197.5.247/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
-  heapster is running at https://104.197.5.247/api/v1/proxy/namespaces/kube-system/services/monitoring-heapster
-```
-
-This shows the proxy-verb URL for accessing each service.
-For example, this cluster has cluster-level logging enabled (using Elasticsearch), which can be reached
-at `https://104.197.5.247/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging/` if suitable credentials are passed, or through a kubectl proxy at, for example:
-`http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging/`.
-(See [above](#accessing-the-cluster-api) for how to pass credentials or use kubectl proxy.)
-
-#### Manually constructing apiserver proxy URLs
-
-As mentioned above, you use the `kubectl cluster-info` command to retrieve the service's proxy URL. To create proxy URLs that include service endpoints, suffixes, and parameters, you simply append to the service's proxy URL:
-`http://`*`kubernetes_master_address`*`/`*`service_path`*`/`*`service_name`*`/`*`service_endpoint-suffix-parameter`*
-<!--- TODO: update this part of doc because it doesn't seem to be valid. What
-about namespaces? 'proxy' verb? -->
-
-##### Examples
-
- * To access the Elasticsearch service endpoint `_search?q=user:kimchy`, you would use:   `http://104.197.5.247/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy`
- * To access the Elasticsearch cluster health information `_cluster/health?pretty=true`, you would use:   `https://104.197.5.247/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging/_cluster/health?pretty=true`
-
-```json
-{
-	 "cluster_name" : "kubernetes_logging",
-	 "status" : "yellow",
-	 "timed_out" : false,
-	 "number_of_nodes" : 1,
-	 "number_of_data_nodes" : 1,
-	 "active_primary_shards" : 5,
-	 "active_shards" : 5,
-	 "relocating_shards" : 0,
-	 "initializing_shards" : 0,
-	 "unassigned_shards" : 5
-  }
-```
-
-#### Using web browsers to access services running on the cluster
-
-You may be able to put an apiserver proxy url into the address bar of a browser. However:
-
-  - Web browsers cannot usually pass tokens, so you may need to use basic (password) auth.  Apiserver can be configured to accept basic auth,
-    but your cluster may not be configured to accept basic auth.
-  - Some web apps may not work, particularly those with client side javascript that construct urls in a
-    way that is unaware of the proxy path prefix.
-
-## Requesting redirects
-
-The redirect capabilities have been deprecated and removed.  Please use a proxy (see below) instead.
-
-## So Many Proxies
-
-There are several different proxies you may encounter when using Kubernetes:
-
-  1. The [kubectl proxy](#directly-accessing-the-rest-api):
-    - runs on a user's desktop or in a pod
-    - proxies from a localhost address to the Kubernetes apiserver
-    - client to proxy uses HTTP
-    - proxy to apiserver uses HTTPS
-    - locates apiserver
-    - adds authentication headers
-  1. The [apiserver proxy](#discovering-builtin-services):
-    - is a bastion built into the apiserver
-    - connects a user outside of the cluster to cluster IPs which otherwise might not be reachable
-    - runs in the apiserver processes
-    - client to proxy uses HTTPS (or http if apiserver so configured)
-    - proxy to target may use HTTP or HTTPS as chosen by proxy using available information
-    - can be used to reach a Node, Pod, or Service
-    - does load balancing when used to reach a Service
-  1. The [kube proxy](/{{page.version}}/docs/user-guide/services/#ips-and-vips):
-    - runs on each node
-    - proxies UDP and TCP
-    - does not understand HTTP
-    - provides load balancing
-    - is just used to reach services
-  1. A Proxy/Load-balancer in front of apiserver(s):
-    - existence and implementation varies from cluster to cluster (e.g. nginx)
-    - sits between all clients and one or more apiservers
-    - acts as load balancer if there are several apiservers.
-  1. Cloud Load Balancers on external services:
-    - are provided by some cloud providers (e.g. AWS ELB, Google Cloud Load Balancer)
-    - are created automatically when the Kubernetes service has type `LoadBalancer`
-    - use UDP/TCP only
-    - implementation varies by cloud provider.
-
-Kubernetes users will typically not need to worry about anything other than the first two types.  The cluster admin
-will typically ensure that the latter types are setup correctly.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/annotations.md b/v1.1/docs/user-guide/annotations.md
deleted file mode 100644
index ff2965cbe5..0000000000
--- a/v1.1/docs/user-guide/annotations.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
----
-
-We have [labels](/{{page.version}}/docs/user-guide/labels) for identifying metadata.
-
-It is also useful to be able to attach arbitrary non-identifying metadata, for retrieval by API clients such as tools, libraries, etc. This information may be large, may be structured or unstructured, may include characters not permitted by labels, etc. Such information would not be used for object selection and therefore doesn't belong in labels.
-
-Like labels, annotations are key-value maps.
-
-```json
-"annotations": {
-  "key1" : "value1",
-  "key2" : "value2"
-}
-```
-
-Possible information that could be recorded in annotations:
-
-* fields managed by a declarative configuration layer, to distinguish them from client- and/or server-set default values and other auto-generated fields, fields set by auto-sizing/auto-scaling systems, etc., in order to facilitate merging
-* build/release/image information (timestamps, release ids, git branch, PR numbers, image hashes, registry address, etc.)
-* pointers to logging/monitoring/analytics/audit repos
-* client library/tool information (e.g. for debugging purposes -- name, version, build info)
-* other user and/or tool/system provenance info, such as URLs of related objects from other ecosystem components
-* lightweight rollout tool metadata (config and/or checkpoints)
-* phone/pager number(s) of person(s) responsible, or directory entry where that info could be found, such as a team website
-
-Yes, this information could be stored in an external database or directory, but that would make it much harder to produce shared client libraries and tools for deployment, management, introspection, etc.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/config-best-practices.md b/v1.1/docs/user-guide/config-best-practices.md
deleted file mode 100644
index 2f2ebcdc6a..0000000000
--- a/v1.1/docs/user-guide/config-best-practices.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
----
-
-This document is meant to highlight and consolidate in one place configuration best practices that are introduced throughout the user-guide and getting-started documentation and examples. This is a living document so if you think of something that is not on this list but might be useful to others, please don't hesitate to file an issue or submit a PR.
-
-1. When writing configuration, use the latest stable API version (currently v1).
-1. Configuration should be stored in version control before being pushed to the cluster. This allows configuration to be quickly rolled back if needed and will aid with cluster re-creation and restoration if the worst were to happen.
-1. Use YAML rather than JSON. They can be used interchangeably in almost all scenarios but YAML tends to be more user-friendly for config.
-1. Group related objects together in a single file. This is often better than separate files.
-1. Use `kubectl create -f <directory>` where possible. This looks for config objects in all `.yaml`, `.yml`, and `.json` files in `<directory>` and passes them to create.
-1. Create a service before corresponding replication controllers so that the scheduler can spread the pods comprising the service. You can also create the replication controller without specifying replicas, create the service, then scale up the replication controller, which may work better in an example using progressive disclosure and may have benefits in real scenarios also, such as ensuring one replica works before creating lots of them)
-1. Don't use `hostPort` unless absolutely necessary (e.g., for a node daemon) as it will prevent certain scheduling configurations due to port conflicts. Use the apiserver proxying or port forwarding for debug/admin access, or a service for external service access. If you need to expose a pod's port on the host machine, consider using a [NodePort](/{{page.version}}/docs/user-guide/services/#type--loadbalancer) service before resorting to `hostPort`. If you only need access to the port for debugging purposes, you can also use the [kubectl proxy and apiserver proxy](/{{page.version}}/docs/user-guide/connecting-to-applications-proxy) or [kubectl port-forward](/{{page.version}}/docs/user-guide/connecting-to-applications-port-forward).
-1. Don't use `hostNetwork` for the same reasons as `hostPort`.
-1. Don't specify default values unnecessarily, to simplify and minimize configs. For example, omit the selector and labels in ReplicationController if you want them to be the same as the labels in its podTemplate, since those fields are populated from the podTemplate labels by default.
-1. Instead of attaching one label to a set of pods to represent a service (e.g., `service: myservice`) and another to represent the replication controller managing the pods (e.g., `controller: mycontroller`), attach labels that identify semantic attributes of your application or deployment and select the appropriate subsets in your service and replication controller, such as `{ app: myapp, tier: frontend, deployment: v3 }`. A service can be made to span multiple deployments, such as across rolling updates, by simply omitting release-specific labels from its selector, rather than updating a service's selector to match the replication controller's selector fully.
-1. Use kubectl bulk operations (via files and/or labels) for get and delete. See [label selectors](/{{page.version}}/docs/user-guide/labels/#label-selectors) and [using labels effectively](/{{page.version}}/docs/user-guide/managing-deployments/#using-labels-effectively).
-1. Use kubectl run and expose to quickly create and expose single container replication controllers. See the [quick start guide](/{{page.version}}/docs/user-guide/quick-start) for an example.
-1. Use headless services for easy service discovery when you don't need kube-proxy load balancing. See [headless services](/{{page.version}}/docs/user-guide/services/#headless-services).
-1. Use kubectl delete rather than stop. Delete has a superset of the functionality of stop and stop is deprecated.
-1. If there is a viable alternative to naked pods (i.e. pods not bound to a controller), go with the alternative. Controllers are almost always preferable to creating pods (except for some `restartPolicy: Never` scenarios). A minimal Job is coming. See [#1624](http://issue.k8s.io/1624). Naked pods will not be rescheduled in the event of node failure.
-1. Put a version number or hash as a suffix to the name and in a label on a replication controller to facilitate rolling update, as we do for [--image](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update). This is necessary because rolling-update actually creates a new controller as opposed to modifying the existing controller. This does not play well with version agnostic controller names.
-1. Put an object description in an annotation to allow better introspection.
-
-
-
diff --git a/v1.1/docs/user-guide/configuring-containers.md b/v1.1/docs/user-guide/configuring-containers.md
deleted file mode 100644
index 5704cb0e17..0000000000
--- a/v1.1/docs/user-guide/configuring-containers.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## Configuration in Kubernetes
-
-In addition to the imperative-style commands, such as `kubectl run` and `kubectl expose`, described [elsewhere](/{{page.version}}/docs/user-guide/quick-start), Kubernetes supports declarative configuration. Often times, configuration files are preferable to imperative commands, since they can be checked into version control and changes to the files can be code reviewed, which is especially important for more complex configurations, producing a more robust, reliable and archival system.
-
-In the declarative style, all configuration is stored in YAML or JSON configuration files using Kubernetes's API resource schemas as the configuration schemas. `kubectl` can create, update, delete, and get API resources. The `apiVersion` (currently 'v1'?), resource `kind`, and resource `name` are used by `kubectl` to construct the appropriate API path to invoke for the specified operation.
-
-## Launching a container using a configuration file
-
-Kubernetes executes containers in [*Pods*](/{{page.version}}/docs/user-guide/pods). A pod containing a simple Hello World container can be specified in YAML as follows:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: hello-world
-spec:  # specification of the pod's contents
-  restartPolicy: Never
-  containers:
-  - name: hello
-    image: "ubuntu:14.04"
-    command: ["/bin/echo","hello'?,'?world"]
-```
-
-The value of `metadata.name`, `hello-world`, will be the name of the pod resource created, and must be unique within the cluster, whereas `containers[0].name` is just a nickname for the container within that pod. `image` is the name of the Docker image, which Kubernetes expects to be able to pull from a registry, the [Docker Hub](https://registry.hub.docker.com/) by default.
-
-`restartPolicy: Never` indicates that we just want to run the container once and then terminate the pod.
-
-The [`command`](/{{page.version}}/docs/user-guide/containers/#containers-and-commands) overrides the Docker container's `Entrypoint`. Command arguments (corresponding to Docker's `Cmd`) may be specified using `args`, as follows:
-
-```yaml
-command: ["/bin/echo"]
-    args: ["hello","world"]
-```
-
-This pod can be created using the `create` command:
-
-```shell
-$ kubectl create -f ./hello-world.yaml
-pods/hello-world
-```
-
-`kubectl` prints the resource type and name of the resource created when successful.
-
-## Validating configuration
-
-If you're not sure you specified the resource correctly, you can ask `kubectl` to validate it for you:
-
-```shell
-$ kubectl create -f ./hello-world.yaml --validate
-```
-
-Let's say you specified `entrypoint` instead of `command`. You'd see output as follows:
-
-```shell
-I0709 06:33:05.600829   14160 schema.go:126] unknown field: entrypoint
-I0709 06:33:05.600988   14160 schema.go:129] this may be a false alarm, see http://issue.k8s.io/6842 pods/hello-world
-```
-
-`kubectl create --validate` currently warns about problems it detects, but creates the resource anyway, unless a required field is absent or a field value is invalid. Unknown API fields are ignored, so be careful. This pod was created, but with no `command`, which is an optional field, since the image may specify an `Entrypoint`.
-View the [Pod API
-object](http://kubernetes.io/v1.1/docs/api-reference/v1/definitions/#_v1_pod)
-to see the list of valid fields.
-
-## Environment variables and variable expansion
-
-Kubernetes [does not automatically run commands in a shell](https://github.com/kubernetes/kubernetes/wiki/User-FAQ#use-of-environment-variables-on-the-command-line) (not all images contain shells). If you would like to run your command in a shell, such as to expand environment variables (specified using `env`), you could do the following:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: hello-world
-spec:  # specification of the pod's contents
-  restartPolicy: Never
-  containers:
-  - name: hello
-    image: "ubuntu:14.04"
-    env:
-    - name: MESSAGE
-      value: "hello world"
-    command: ["/bin/sh","-c"]
-    args: ["/bin/echo \"${MESSAGE}\""]
-```
-
-However, a shell isn't necessary just to expand environment variables. Kubernetes will do it for you if you use [`$(ENVVAR)` syntax](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/expansion):
-
-```yaml
-command: ["/bin/echo"]
-    args: ["$(MESSAGE)"]
-```
-
-## Viewing pod status
-
-You can see the pod you created (actually all of your cluster's pods) using the `get` command.
-
-If you're quick, it will look as follows:
-
-```shell
-$ kubectl get pods
-NAME          READY     STATUS    RESTARTS   AGE
-hello-world   0/1       Pending   0          0s
-```
-
-Initially, a newly created pod is unscheduled -- no node has been selected to run it. Scheduling happens after creation, but is fast, so you normally shouldn't see pods in an unscheduled state unless there's a problem.
-
-After the pod has been scheduled, the image may need to be pulled to the node on which it was scheduled, if it hadn't been pulled already. After a few seconds, you should see the container running:
-
-```shell
-$ kubectl get pods
-NAME          READY     STATUS    RESTARTS   AGE
-hello-world   1/1       Running   0          5s
-```
-
-The `READY` column shows how many containers in the pod are running.
-
-Almost immediately after it starts running, this command will terminate. `kubectl` shows that the container is no longer running and displays the exit status:
-
-```shell
-$ kubectl get pods
-NAME          READY     STATUS       RESTARTS   AGE
-hello-world   0/1       ExitCode:0   0          15s
-```
-
-## Viewing pod output
-
-You probably want to see the output of the command you ran. As with [`docker logs`](https://docs.docker.com/userguide/usingdocker/), `kubectl logs` will show you the output:
-
-```shell
-$ kubectl logs hello-world
-hello world
-```
-
-## Deleting pods
-
-When you're done looking at the output, you should delete the pod:
-
-```shell
-$ kubectl delete pod hello-world
-pods/hello-world
-```
-
-As with `create`, `kubectl` prints the resource type and name of the resource deleted when successful.
-
-You can also use the resource/name format to specify the pod:
-
-```shell
-$ kubectl delete pods/hello-world
-pods/hello-world
-```
-
-Terminated pods aren't currently automatically deleted, so that you can observe their final status, so be sure to clean up your dead pods.
-
-On the other hand, containers and their logs are eventually deleted automatically in order to free up disk space on the nodes.
-
-## What's next?
-
-[Learn about deploying continuously running applications.](/{{page.version}}/docs/user-guide/deploying-applications)
diff --git a/v1.1/docs/user-guide/connecting-to-applications-proxy.md b/v1.1/docs/user-guide/connecting-to-applications-proxy.md
deleted file mode 100644
index 26ab41e361..0000000000
--- a/v1.1/docs/user-guide/connecting-to-applications-proxy.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
----
-
-You have seen the [basics](/{{page.version}}/docs/user-guide/accessing-the-cluster) about `kubectl proxy` and `apiserver proxy`. This guide shows how to use them together to access a service([kube-ui](/{{page.version}}/docs/user-guide/ui)) running on the Kubernetes cluster from your workstation.
-
-
-## Getting the apiserver proxy URL of kube-ui
-
-kube-ui is deployed as a cluster add-on. To find its apiserver proxy URL,
-
-```shell
-$ kubectl cluster-info | grep "KubeUI"
-KubeUI is running at https://173.255.119.104/api/v1/proxy/namespaces/kube-system/services/kube-ui
-```
-
-if this command does not find the URL, try the steps [here](/{{page.version}}/docs/user-guide/ui/#accessing-the-ui).
-
-
-## Connecting to the kube-ui service from your local workstation
-
-The above proxy URL is an access to the kube-ui service provided by the apiserver. To access it, you still need to authenticate to the apiserver. `kubectl proxy` can handle the authentication.
-
-```shell
-$ kubectl proxy --port=8001
-Starting to serve on localhost:8001
-```
-
-Now you can access the kube-ui service on your local workstation at [http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kube-ui](http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kube-ui)
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/container-environment.md b/v1.1/docs/user-guide/container-environment.md
deleted file mode 100644
index b816cd3442..0000000000
--- a/v1.1/docs/user-guide/container-environment.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
----
-
-This document describes the environment for Kubelet managed containers on a Kubernetes node (kNode).  In contrast to the Kubernetes cluster API, which provides an API for creating and managing containers, the Kubernetes container environment provides the container access to information about what else is going on in the cluster.
-
-This cluster information makes it possible to build applications that are *cluster aware*.
-Additionally, the Kubernetes container environment defines a series of hooks that are surfaced to optional hook handlers defined as part of individual containers.  Container hooks are somewhat analogous to operating system signals in a traditional process model.   However these hooks are designed to make it easier to build reliable, scalable cloud applications in the Kubernetes cluster.  Containers that participate in this cluster lifecycle become *cluster native*.
-
-Another important part of the container environment is the file system that is available to the container.  In Kubernetes, the filesystem is a combination of an [image](/{{page.version}}/docs/user-guide/images) and one or more [volumes](/{{page.version}}/docs/user-guide/volumes).
-
-The following sections describe both the cluster information provided to containers, as well as the hooks and life-cycle that allows containers to interact with the management system.
-
-* TOC
-{:toc}
-
-## Cluster Information
-
-There are two types of information that are available within the container environment.  There is information about the container itself, and there is information about other objects in the system.
-
-### Container Information
-
-Currently, the Pod name for the pod in which the container is running is set as the hostname of the container, and is accessible through all calls to access the hostname within the container (e.g. the hostname command, or the [gethostname][1] function call in libc), but this is planned to change in the future and should not be used.
-
-The Pod name and namespace are also available as environment variables via the [downward API](/{{page.version}}/docs/user-guide/downward-api).  Additionally, user-defined environment variables from the pod definition, are also available to the container, as are any environment variables specified statically in the Docker image.
-
-In the future, we anticipate expanding this information with richer information about the container.  Examples include available memory, number of restarts, and in general any state that you could get from the call to GET /pods on the API server.
-
-### Cluster Information
-
-Currently the list of all services that are running at the time when the container was created via the Kubernetes Cluster API are available to the container as environment variables.  The set of environment variables matches the syntax of Docker links.
-
-For a service named **foo** that maps to a container port named **bar**, the following variables are defined:
-
-```shell
-FOO_SERVICE_HOST=<the host the service is running on>
-FOO_SERVICE_PORT=<the port the service is running on>
-```
-
-Services have dedicated IP address, and are also surfaced to the container via DNS (If [DNS addon](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/) is enabled).  Of course DNS is still not an enumerable protocol, so we will continue to provide environment variables so that containers can do discovery.
-
-## Container Hooks
-
-Container hooks provide information to the container about events in its management lifecycle.  For example, immediately after a container is started, it receives a *PostStart* hook.  These hooks are broadcast *into* the container with information about the life-cycle of the container.  They are different from the events provided by Docker and other systems which are *output* from the container.  Output events provide a log of what has already happened.  Input hooks provide real-time notification about things that are happening, but no historical log.
-
-### Hook Details
-
-There are currently two container hooks that are surfaced to containers:
-
-*PostStart*
-
-This hook is sent immediately after a container is created.  It notifies the container that it has been created.  No parameters are passed to the handler.
-
-*PreStop*
-
-This hook is called immediately before a container is terminated. No parameters are passed to the handler. This event handler is blocking, and must complete before the call to delete the container is sent to the Docker daemon.  The SIGTERM notification sent by Docker is also still sent. A more complete description of termination behavior can be found in [Termination of Pods](/{{page.version}}/docs/user-guide/pods/#termination-of-pods).
-
-### Hook Handler Execution
-
-When a management hook occurs, the management system calls into any registered hook handlers in the container for that hook.  These hook handler calls are synchronous in the context of the pod containing the container. Typically we expect that users will make their hook handlers as lightweight as possible, but there are cases where long running commands make sense (e.g. saving state prior to container stop).
-
-### Hook delivery guarantees
-
-Hook delivery is intended to be "at least once", which means that a hook may be called multiple times for any given event (e.g. "start" or "stop") and it is up to the hook implementer to be able to handle this
-correctly.
-
-We expect double delivery to be rare, but in some cases if the Kubelet restarts in the middle of sending a hook, the hook may be resent after the Kubelet comes back up.
-
-Likewise, we only make a single delivery attempt.  If (for example) an http hook receiver is down, and unable to take traffic, we do not make any attempts to resend.
-
-Currently, there are (hopefully rare) scenarios where PostStart hooks may not be delivered.
-
-### Hook Handler Implementations
-
-Hook handlers are the way that hooks are surfaced to containers.  Containers can select the type of hook handler they would like to implement.  Kubernetes currently supports two different hook handler types:
-
-   * Exec - Executes a specific command (e.g. pre-stop.sh) inside the cgroups and namespaces of the container.  Resources consumed by the command are counted against the container.
-
-   * HTTP - Executes an HTTP request against a specific endpoint on the container.
-
-[1]: http://man7.org/linux/man-pages/man2/gethostname.2.html
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/deployments.md b/v1.1/docs/user-guide/deployments.md
deleted file mode 100644
index 014ff690a4..0000000000
--- a/v1.1/docs/user-guide/deployments.md
+++ /dev/null
@@ -1,351 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## What is a _Deployment_?
-
-A _Deployment_ provides declarative update for Pods and ReplicationControllers.
-Users describe the desired state in deployment object and deployment
-controller changes the actual state to that at a controlled rate.
-Users can define deployments to create new resources, or replace existing ones
-by new ones.
-
-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 ex: to use a new image).
-
-## Enabling Deployments on kubernetes cluster
-
-Deployments is part of the [`extensions` API Group](/{{page.version}}/docs/api/#api-groups) and is not enabled by default.
-Set `--runtime-config=extensions/v1beta1/deployments=true` on API server to
-enable it.
-This can be achieved by exporting `ENABLE_DEPLOYMENTS=true` before running
-`kube-up.sh` script on GCE.
-
-Note that Deployment objects effectively have [API version
-`v1alpha1`](/{{page.version}}/docs/api/)#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
-bring up 3 nginx pods.
-
-<!-- BEGIN MUNGE: EXAMPLE nginx-deployment.yaml -->
-
-```yaml
-apiVersion: extensions/v1beta1
-kind: Deployment
-metadata:
-  name: nginx-deployment
-spec:
-  replicas: 3
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx:1.7.9
-        ports:
-        - containerPort: 80
-```
-
-[Download example](/{{page.version}}/docs/user-guide/nginx-deployment.yaml)
-<!-- END MUNGE: EXAMPLE nginx-deployment.yaml -->
-
-Run the example by downloading the example file and then running this command:
-
-```shell
-$ kubectl create -f docs/user-guide/nginx-deployment.yaml
-deployment "nginx-deployment" created
-```
-
-Running a get immediately will give:
-
-```shell
-$ kubectl get deployments
-NAME               UPDATEDREPLICAS   AGE
-nginx-deployment   0/3               8s
-```
-
-This indicates that deployment is trying to update 3 replicas. It has not
-updated any one of those yet.
-
-Running a get again after a minute, will give:
-
-```shell
-$ kubectl get deployments
-NAME               UPDATEDREPLICAS   AGE
-nginx-deployment   3/3               1m
-```
-
-This indicates that deployent has created all the 3 replicas.
-Running ```kubectl get rc```
-and ```kubectl get pods```
-will show the replication controller (RC) and pods created.
-
-```shell
-$ kubectl get rc
-CONTROLLER                      CONTAINER(S)   IMAGE(S)      SELECTOR                                                        REPLICAS   AGE
-REPLICAS   AGE
-deploymentrc-1975012602         nginx          nginx:1.7.9   deployment.kubernetes.io/podTemplateHash=1975012602,app=nginx   3          2m
-```
-
-```shell
-$ kubectl get pods
-NAME                            READY          STATUS        RESTARTS       AGE
-deploymentrc-1975012602-4f2tb   1/1            Running       0              1m
-deploymentrc-1975012602-j975u   1/1            Running       0              1m
-deploymentrc-1975012602-uashb   1/1            Running       0              1m
-```
-
-The created RC will ensure that there are 3 nginx pods at all time.
-
-## Updating a Deployment
-
-Lets say, now we want to update the nginx pods to start using nginx:1.9.1 image
-instead of nginx:1.7.9.
-For this, we update our deployment to be as follows:
-
-<!-- BEGIN MUNGE: EXAMPLE new-nginx-deployment.yaml -->
-
-```yaml
-apiVersion: extensions/v1beta1
-kind: Deployment
-metadata:
-  name: nginx-deployment
-spec:
-  replicas: 3
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx:1.9.1
-        ports:
-        - containerPort: 80
-```
-
-[Download example](/{{page.version}}/docs/user-guide/new-nginx-deployment.yaml)
-<!-- END MUNGE: EXAMPLE new-nginx-deployment.yaml -->
-
-
-```shell
-$ kubectl apply -f docs/user-guide/new-nginx-deployment.yaml
-deployment "nginx-deployment" configured
-```
-
-Running a get immediately will still give:
-
-```shell
-$ kubectl get deployments
-NAME               UPDATEDREPLICAS   AGE
-nginx-deployment   3/3               8s
-```
-
-This indicates that deployment status has not been updated yet (it is still
-showing old status).
-Running a get again after a minute, will give:
-
-```shell
-$ kubectl get deployments
-NAME               UPDATEDREPLICAS   AGE
-nginx-deployment   1/3               1m
-```
-
-This indicates that deployment has updated one of the three pods that it needs
-to update.
-Eventually, it will get around to updating all the pods.
-
-```shell
-$ kubectl get deployments
-NAME               UPDATEDREPLICAS   AGE
-nginx-deployment   3/3               3m
-```
-
-We can run `kubectl get rc`
-to see that deployment updated the pods by creating a new RC
-which it scaled up to 3 and scaled down the old RC to 0.
-
-```shell
-kubectl get rc
-CONTROLLER                CONTAINER(S)   IMAGE(S)      SELECTOR                                                         REPLICAS   AGE
-deploymentrc-1562004724   nginx          nginx:1.9.1   deployment.kubernetes.io/podTemplateHash=1562004724,app=nginx   3          5m
-deploymentrc-1975012602   nginx          nginx:1.7.9   deployment.kubernetes.io/podTemplateHash=1975012602,app=nginx   0          7m
-```
-
-Running get pods, will only show the new pods.
-
-```shell
-kubectl get pods
-NAME                            READY     STATUS    RESTARTS   AGE
-deploymentrc-1562004724-0tgk5   1/1       Running   0          9m
-deploymentrc-1562004724-1rkfl   1/1       Running   0          8m
-deploymentrc-1562004724-6v702   1/1       Running   0          8m
-```
-
-Next time we want to update pods, we can just update the deployment again.
-
-Deployment ensures that not all pods are down while they are being updated. By
-default, it ensures that minimum of 1 less than the desired number of pods are
-up. For example, if you look at the above deployment closely, you will see that
-it first created a new pod, then deleted some old pods and created new ones. It
-does not kill old pods until a sufficient number of new pods have come up.
-
-```shell
-$ kubectl describe deployments
-Name:                           nginx-deployment
-Namespace:                      default
-CreationTimestamp:              Thu, 22 Oct 2015 17:58:49 -0700
-Labels:                         app=nginx-deployment
-Selector:                       app=nginx
-Replicas:                       3 updated / 3 total
-StrategyType:                   RollingUpdate
-RollingUpdateStrategy:          1 max unavailable, 1 max surge, 0 min ready seconds
-OldReplicationControllers:      deploymentrc-1562004724 (3/3 replicas created)
-NewReplicationController:       <none>
-Events:
-  FirstSeen     LastSeen        Count   From                            SubobjectPath   Reason          Message
-  '��'��'��'��'��'��'��'��'��     '��'��'��'��'��'��'��'��        '��'��'��'��'��   '��'��'��'��                            '��'��'��'��'��'��'��'��'��'��'��'��'��   '��'��'��'��'��'��          '��'��'��'��'��'��'��
-  10m           10m             1       {deployment-controller }                        ScalingRC       Scaled up rc deploymentrc-1975012602 to 3
-  2m            2m              1       {deployment-controller }                        ScalingRC       Scaled up rc deploymentrc-1562004724 to 1
-  2m            2m              1       {deployment-controller }                        ScalingRC       Scaled down rc deploymentrc-1975012602 to 1
-  1m            1m              1       {deployment-controller }                        ScalingRC       Scaled up rc deploymentrc-1562004724 to 3
-  1m            1m              1       {deployment-controller }                        ScalingRC       Scaled down rc deploymentrc-1975012602 to 0
-```
-
-Here we see that when we first created the deployment, it created an RC and scaled it up to 3 replicas directly.
-When we updated the deployment, it created a new RC and scaled it up to 1 and then scaled down the old RC by 1, so that at least 2 pods were available at all times.
-It then scaled up the new RC to 3 and when those pods were ready, it scaled down the old RC to 0.
-
-### Multiple Updates
-
-Each time a new deployment object is observed, a replication controller is
-created to bring up the desired pods if there is no existing RC doing so.
-Existing RCs controlling pods whose labels match `.spec.selector` but the
-template does not match `.spec.template` are scaled down.
-Eventually, the new RC will be scaled to `.spec.replicas` and all old RCs will
-be scaled to 0.
-If the user updates the deployment while an existing deployment was in progress,
-deployment will create a new RC as per the update and start scaling that up and
-will roll the RC that it was scaling up before in its list of old RCs and will
-start scaling it down.
-For example: If user creates a deployment to create 5 replicas of nginx:1.7.9.
-But then updates the deployment to create 5 replicas of nging:1.9.1, when only 3
-replicas of nginx:1.7.9 had been created, then deployment will immediately start
-killing the 3 nginx:1.7.9 pods that it had created and will start creating
-nginx:1.9.1 pods. It will not wait for 5 replicas of nginx:1.7.9 to be created
-before changing course.
-
-## Writing a Deployment Spec
-
-As with all other Kubernetes configs, a Deployment needs `apiVersion`, `kind`, and
-`metadata` fields.  For general information about working with config files,
-see [here](/{{page.version}}/docs/user-guide/deploying-applications), [here](/{{page.version}}/docs/user-guide/configuring-containers), and [here](/{{page.version}}/docs/user-guide/working-with-resources).
-
-A Deployment also needs a [`.spec` section](/{{page.version}}/docs/devel/api-conventions/#spec-and-status).
-
-### Pod Template
-
-The `.spec.template` is the only required field of the `.spec`.
-
-The `.spec.template` is a [pod template](/{{page.version}}/docs/user-guide/replication-controller/#pod-template).  It has exactly
-the same schema as a [pod](/{{page.version}}/docs/user-guide/pods), except it is nested and does not have an
-`apiVersion` or `kind`.
-
-### Replicas
-
-`.spec.replicas` is an optional field that specifies the number of desired pods. Defaults
-to 1.
-
-### Selector
-
-`.spec.selector` is an optional field that specifies label selectors for pods
-targeted by this deployment. Deployment kills some of these pods, if their
-template is different than `.spec.template` or if the total number of such pods
-exceeds `.spec.replicas`. It will bring up new pods with `.spec.template` if
-number of pods are less than the desired number.
-
-### Unique Label Key
-
-`.spec.uniqueLabelKey` is an optional field specifying key of the selector that
-is added to existing RCs (and label key that is added to its pods) to prevent
-the existing RCs to select new pods (and old pods being selected by new RC).
-Users can set this to an empty string to indicate that the system should
-not add any selector and label. If unspecified, system uses
-"deployment.kubernetes.io/podTemplateHash".
-Value of this key is hash of `.spec.template`.
-No label is added if this is set to empty string.
-
-### Strategy
-
-`.spec.strategy` specifies the strategy to replace old pods by new ones.
-`.spec.strategy.type` can be "Recreate" or "RollingUpdate". "RollingUpdate" is
-the default value.
-
-#### Recreate Deployment
-
-All existing pods are killed before new ones are created when
-`.spec.strategy.type==Recreate`.
-Note: This is not implemented yet.
-
-#### Rolling Update Deployment
-
-Deployment updates pods in a [rolling update][update-demo/] fashion
-when `.spec.strategy.type==RollingUpdate`.
-Users can specify `maxUnavailable`, `maxSurge` and `minReadySeconds` to control
-the rolling update process.
-
-##### Max Unavailable
-
-`.spec.strategy.rollingUpdate.maxUnavailable` is an optional field that specifies the
-maximum number of pods that can be unavailable during the update process.
-Value can be an absolute number (ex: 5) or a percentage of desired pods (ex:
-10%).
-Absolute number is calculated from percentage by rounding up.
-This can not be 0 if `.spec.strategy.rollingUpdate.maxSurge` is 0.
-By default, a fixed value of 1 is used.
-Example: when this is set to 30%, the old RC can be scaled down to
-70% of desired pods immediately when the rolling update starts. Once new pods are
-ready, old RC can be scaled down further, followed by scaling up the new RC,
-ensuring that the total number of pods available at all times during the
-update is at least 70% of desired pods.
-
-##### Max Surge
-
-`.spec.strategy.rollingUpdate.maxSurge` is an optional field that specifies the
-maximum number of pods that can be created above the desired number of pods.
-Value can be an absolute number (ex: 5) or a percentage of desired pods (ex:
-10%).
-This can not be 0 if MaxUnavailable is 0.
-Absolute number is calculated from percentage by rounding up.
-By default, a value of 1 is used.
-Example: when this is set to 30%, the new RC can be scaled up immediately when
-the rolling update starts, such that the total number of old and new pods do not exceed
-130% of desired pods. Once old pods have been killed,
-new RC can be scaled up further, ensuring that total number of pods running
-at any time during the update is atmost 130% of desired pods.
-
-##### Min Ready Seconds
-
-`.spec.strategy.rollingUpdate.minReadySeconds` is an optional field that specifies the
-minimum number of seconds for which a newly created pod should be ready
-without any of its container crashing, for it to be considered available.
-Defaults to 0 (pod will be considered available as soon as it is ready).
-Note: This is not implemented yet.
-
-## Alternative to Deployments
-
-### kubectl rolling update
-
-[Kubectl rolling update](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update) also updates pods and replication controllers in a similar fashion.
-But deployments is declarative and is server side.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/downward-api/index.md b/v1.1/docs/user-guide/downward-api/index.md
deleted file mode 100644
index 222bf0acaf..0000000000
--- a/v1.1/docs/user-guide/downward-api/index.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
----
-
-Following this example, you will create a pod with a container that consumes the pod's name and
-namespace using the [downward API](/{{page.version}}/docs/user-guide/downward-api/).
-
-## Step Zero: Prerequisites
-
-This example assumes you have a Kubernetes cluster installed and running, and that you have
-installed the `kubectl` command line tool somewhere in your path. Please see the [getting
-started](/{{page.version}}/docs/getting-started-guides/) for installation instructions for your platform.
-
-## Step One: Create the pod
-
-Containers consume the downward API using environment variables.  The downward API allows
-containers to be injected with the name and namespace of the pod the container is in.
-
-Use the [`dapi-pod.yaml`](/{{page.version}}/docs/user-guide/downward-api/dapi-pod.yaml) file to create a Pod with a container that consumes the
-downward API.
-
-```shell
-$ kubectl create -f docs/user-guide/downward-api/dapi-pod.yaml
-```
-
-### Examine the logs
-
-This pod runs the `env` command in a container that consumes the downward API.  You can grep
-through the pod logs to see that the pod was injected with the correct values:
-
-```shell
-$ kubectl logs dapi-test-pod | grep POD_
-2015-04-30T20:22:18.568024817Z MY_POD_NAME=dapi-test-pod
-2015-04-30T20:22:18.568087688Z MY_POD_NAMESPACE=default
-2015-04-30T20:22:18.568092435Z MY_POD_IP=10.0.1.6
-```
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/environment-guide/index.md b/v1.1/docs/user-guide/environment-guide/index.md
deleted file mode 100644
index 43d1b38acd..0000000000
--- a/v1.1/docs/user-guide/environment-guide/index.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
----
-
-This example demonstrates running pods, replication controllers, and
-services. It shows two types of pods: frontend and backend, with
-services on top of both. Accessing the frontend pod will return
-environment information about itself, and a backend pod that it has
-accessed through the service. The goal is to illuminate the
-environment metadata available to running containers inside the
-Kubernetes cluster. The documentation for the Kubernetes environment
-is [here](/{{page.version}}/docs/user-guide/container-environment).
-
-![Diagram](/images/docs/diagram.png)
-
-## Prerequisites
-
-This example assumes that you have a Kubernetes cluster installed and
-running, and that you have installed the `kubectl` command line tool
-somewhere in your path.  Please see the [getting
-started](/{{page.version}}/docs/getting-started-guides/) for installation instructions
-for your platform.
-
-## Optional: Build your own containers
-
-The code for the containers is under
-[containers/](/{{page.version}}/docs/user-guide/environment-guide/containers/)
-
-## Get everything running
-
-```shell
-kubectl create -f ./backend-rc.yaml
-kubectl create -f ./backend-srv.yaml
-kubectl create -f ./show-rc.yaml
-kubectl create -f ./show-srv.yaml
-```
-
-## Query the service
-
-Use `kubectl describe service show-srv` to determine the public IP of
-your service.
-
-> Note: If your platform does not support external load balancers,
-> you'll need to open the proper port and direct traffic to the
-> internal IP shown for the frontend service with the above command
-
-Run `curl <public ip>:80` to query the service. You should get
-something like this back:
-
-```shell
-Pod Name: show-rc-xxu6i
-Pod Namespace: default
-USER_VAR: important information
-
-Kubernetes environment variables
-BACKEND_SRV_SERVICE_HOST = 10.147.252.185
-BACKEND_SRV_SERVICE_PORT = 5000
-KUBERNETES_RO_SERVICE_HOST = 10.147.240.1
-KUBERNETES_RO_SERVICE_PORT = 80
-KUBERNETES_SERVICE_HOST = 10.147.240.2
-KUBERNETES_SERVICE_PORT = 443
-KUBE_DNS_SERVICE_HOST = 10.147.240.10
-KUBE_DNS_SERVICE_PORT = 53
-
-Found backend ip: 10.147.252.185 port: 5000
-Response from backend
-Backend Container
-Backend Pod Name: backend-rc-6qiya
-Backend Namespace: default
-```
-
-First the frontend pod's information is printed. The pod name and
-[namespace](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/namespaces.md) are retrieved from the
-[Downward API](/{{page.version}}/docs/user-guide/downward-api). Next, `USER_VAR` is the name of
-an environment variable set in the [pod
-definition](/{{page.version}}/docs/user-guide/environment-guide/show-rc.yaml). Then, the dynamic Kubernetes environment
-variables are scanned and printed. These are used to find the backend
-service, named `backend-srv`. Finally, the frontend pod queries the
-backend service and prints the information returned. Again the backend
-pod returns its own pod name and namespace.
-
-Try running the `curl` command a few times, and notice what
-changes. Ex: `watch -n 1 curl -s <ip>` Firstly, the frontend service
-is directing your request to different frontend pods each time. The
-frontend pods are always contacting the backend through the backend
-service. This results in a different backend pod servicing each
-request as well.
-
-## Cleanup
-
-```shell
-kubectl delete rc,service -l type=show-type
-kubectl delete rc,service -l type=backend-type
-```
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/horizontal-pod-autoscaling/index.md b/v1.1/docs/user-guide/horizontal-pod-autoscaling/index.md
deleted file mode 100644
index 25747788de..0000000000
--- a/v1.1/docs/user-guide/horizontal-pod-autoscaling/index.md
+++ /dev/null
@@ -1,184 +0,0 @@
----
----
-
-Horizontal pod autoscaling is a [beta](/{{page.version}}/docs/api/#api-versioning) feature in Kubernetes 1.1.
-It allows the number of pods in a replication controller or deployment to scale automatically based on observed CPU usage.
-In the future also other metrics will be supported.
-
-In this document we explain how this feature works by walking you through an example of enabling horizontal pod autoscaling with the php-apache server.
-
-## Prerequisites
-
-This example requires a running Kubernetes cluster and kubectl in the version at least 1.1.
-[Heapster](https://github.com/kubernetes/heapster) monitoring needs to be deployed in the cluster
-as horizontal pod autoscaler uses it to collect metrics
-(if you followed [getting started on GCE guide](/{{page.version}}/docs/getting-started-guides/gce),
-heapster monitoring will be turned-on by default).
-
-
-## Step One: Run & expose php-apache server
-
-To demonstrate horizontal pod autoscaler we will use a custom docker image based on php-apache server.
-The image can be found [here](https://releases.k8s.io/{{page.githubbranch}}/docs/user-guide/horizontal-pod-autoscaling/image).
-It defines [index.php](/{{page.version}}/docs/user-guide/horizontal-pod-autoscaling/image/index.php) page which performs some CPU intensive computations.
-
-First, we will start a replication controller running the image and expose it as an external service:
-
-<a name="kubectl-run"></a>
-
-```shell
-$ kubectl run php-apache --image=gcr.io/google_containers/hpa-example --requests=cpu=200m
-replicationcontroller "php-apache" created
-
-$ kubectl expose rc php-apache --port=80 --type=LoadBalancer
-service "php-apache" exposed
-```
-
-Now, we will wait some time and verify that both the replication controller and the service were correctly created and are running. We will also determine the IP address of the service:
-
-```shell
-$ kubectl get pods
-NAME               READY     STATUS    RESTARTS   AGE
-php-apache-wa3t1   1/1       Running   0          12m
-
-$ kubectl describe services php-apache | grep "LoadBalancer Ingress"
-LoadBalancer Ingress:	146.148.24.244
-```
-
-We may now check that php-apache server works correctly by calling `curl` with the service's IP:
-
-```shell
-$ curl http://146.148.24.244
-OK!
-```
-
-Please notice that when exposing the service we assumed that our cluster runs on a provider which supports load balancers (e.g.: on GCE).
-If load balancers are not supported (e.g.: on Vagrant), we can expose php-apache service as ``ClusterIP`` and connect to it using the proxy on the master:
-
-```shell
-$ kubectl expose rc php-apache --port=80 --type=ClusterIP
-service "php-apache" exposed
-
-$ kubectl cluster-info | grep master
-Kubernetes master is running at https://146.148.6.215
-
-$ curl -k -u <admin>:<password> https://146.148.6.215/api/v1/proxy/namespaces/default/services/php-apache/
-OK!
-```
-
-## Step Two: Create horizontal pod autoscaler
-
-Now that the server is running, we will create a horizontal pod autoscaler for it.
-To create it, we will use the [hpa-php-apache.yaml](/{{page.version}}/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml) file, which looks like this:
-
-```yaml
-apiVersion: extensions/v1beta1
-kind: HorizontalPodAutoscaler
-metadata:
-  name: php-apache
-  namespace: default
-spec:
-  scaleRef:
-    kind: ReplicationController
-    name: php-apache
-    namespace: default
-  minReplicas: 1
-  maxReplicas: 10
-  cpuUtilization:
-    targetPercentage: 50
-```
-
-This defines a horizontal pod autoscaler that maintains between 1 and 10 replicas of the Pods
-controlled by the php-apache replication controller we created in the first step of these instructions.
-Roughly speaking, the horizontal autoscaler will increase and decrease the number of replicas
-(via the replication controller) so as to maintain an average CPU utilization across all Pods of 50%
-(since each pod requests 200 milli-cores by [kubectl run](#kubectl-run), this means average CPU utilization of 100 milli-cores).
-See [here](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/horizontal-pod-autoscaler.md#autoscaling-algorithm) for more details on the algorithm.
-
-We will create the autoscaler by executing the following command:
-
-```shell
-$ kubectl create -f docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml
-horizontalpodautoscaler "php-apache" created
-```
-
-Alternatively, we can create the autoscaler using [kubectl autoscale](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/user-guide/kubectl/kubectl_autoscale.md).
-The following command will create the equivalent autoscaler as defined in the [hpa-php-apache.yaml](/{{page.version}}/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml) file:
-
-```shell
-$ kubectl autoscale rc php-apache --cpu-percent=50 --min=1 --max=10
-replicationcontroller "php-apache" autoscaled
-```
-
-We may check the current status of autoscaler by running:
-
-```shell
-$ kubectl get hpa
-NAME         REFERENCE                                   TARGET    CURRENT   MINPODS   MAXPODS   AGE
-php-apache   ReplicationController/default/php-apache/   50%       0%        1         10        27s
-```
-
-Please note that the current CPU consumption is 0% as we are not sending any requests to the server
-(the ``CURRENT`` column shows the average across all the pods controlled by the corresponding replication controller).
-
-## Step Three: Increase load
-
-Now, we will see how the autoscaler reacts on the increased load of the server.
-We will start an infinite loop of queries to our server (please run it in a different terminal):
-
-```shell
-$ while true; do curl http://146.148.6.244; done
-```
-
-We may examine, how CPU load was increased (the results should be visible after about 3-4 minutes) by executing:
-
-```shell
-$ kubectl get hpa
-NAME         REFERENCE                                   TARGET    CURRENT   MINPODS   MAXPODS   AGE
-php-apache   ReplicationController/default/php-apache/   50%       305%      1         10        4m
-```
-
-In the case presented here, it bumped CPU consumption to 305% of the request.
-As a result, the replication controller was resized to 7 replicas:
-
-```shell
-$ kubectl get rc
-CONTROLLER   CONTAINER(S)   IMAGE(S)                               SELECTOR         REPLICAS   AGE
-php-apache   php-apache     gcr.io/google_containers/hpa-example   run=php-apache   7          18m
-```
-
-Now, we may increase the load even more by running yet another infinite loop of queries (in yet another terminal):
-
-```shell
-$ while true; do curl http://146.148.6.244; done
-```
-
-In the case presented here, it increased the number of serving pods to 10:
-
-```shell
-$ kubectl get hpa
-NAME         REFERENCE                                   TARGET    CURRENT   MINPODS   MAXPODS   AGE
-php-apache   ReplicationController/default/php-apache/   50%       65%       1         10        14m
-
-$ kubectl get rc
-CONTROLLER   CONTAINER(S)   IMAGE(S)                               SELECTOR         REPLICAS   AGE
-php-apache   php-apache     gcr.io/google_containers/hpa-example   run=php-apache   10         24m
-```
-
-## Step Four: Stop load
-
-We will finish our example by stopping the user load.
-
-We will terminate both infinite ``while`` loops sending requests to the server and verify the result state:
-
-```shell
-$ kubectl get hpa
-NAME         REFERENCE                                   TARGET    CURRENT   MINPODS   MAXPODS   AGE
-php-apache   ReplicationController/default/php-apache/   50%       0%        1         10        21m
-
-$ kubectl get rc
-CONTROLLER   CONTAINER(S)   IMAGE(S)                               SELECTOR         REPLICAS   AGE
-php-apache   php-apache     gcr.io/google_containers/hpa-example   run=php-apache   1          31m
-```
-
-As we see, in the presented case CPU utilization dropped to 0, and the number of replicas dropped to 1.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/index.md b/v1.1/docs/user-guide/index.md
deleted file mode 100644
index 6447b85d81..0000000000
--- a/v1.1/docs/user-guide/index.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-The user guide is intended for anyone who wants to run programs and services on an existing Kubernetes cluster.  Setup and administration of a Kubernetes cluster is described in the [Cluster Admin Guide](/{{page.version}}/docs/admin/). The [Developer Guide](/{{page.version}}/docs/devel/) is for anyone wanting to either write code which directly accesses the Kubernetes API, or to contribute directly to the Kubernetes project.
-
-Please ensure you have completed the [prerequisites for running examples from the user guide](/{{page.version}}/docs/user-guide/prereqs).
-
-## Quick walkthrough
-
-1. [Kubernetes 101](/{{page.version}}/docs/user-guide/walkthrough/)
-1. [Kubernetes 201](/{{page.version}}/docs/user-guide/walkthrough/k8s201)
-
-## Thorough walkthrough
-
-If you don't have much familiarity with Kubernetes, we recommend you read the following sections in order:
-
-1. [Quick start: launch and expose an application](/{{page.version}}/docs/user-guide/quick-start)
-1. [Configuring and launching containers: configuring common container parameters](/{{page.version}}/docs/user-guide/configuring-containers)
-1. [Deploying continuously running applications](/{{page.version}}/docs/user-guide/deploying-applications)
-1. [Connecting applications: exposing applications to clients and users](/{{page.version}}/docs/user-guide/connecting-applications)
-1. [Working with containers in production](/{{page.version}}/docs/user-guide/production-pods)
-1. [Managing deployments](/{{page.version}}/docs/user-guide/managing-deployments)
-1. [Application introspection and debugging](/{{page.version}}/docs/user-guide/introspection-and-debugging)
-    1. [Using the Kubernetes web user interface](/{{page.version}}/docs/user-guide/ui)
-    1. [Logging](/{{page.version}}/docs/user-guide/logging)
-    1. [Monitoring](/{{page.version}}/docs/user-guide/monitoring)
-    1. [Getting into containers via `exec`](/{{page.version}}/docs/user-guide/getting-into-containers)
-    1. [Connecting to containers via proxies](/{{page.version}}/docs/user-guide/connecting-to-applications-proxy)
-    1. [Connecting to containers via port forwarding](/{{page.version}}/docs/user-guide/connecting-to-applications-port-forward)
-
-## Concept guide
-
-[**Overview**](/{{page.version}}/docs/user-guide/overview)
-: A brief overview of Kubernetes concepts.
-
-[**Cluster**](/{{page.version}}/docs/admin/)
-: A cluster is a set of physical or virtual machines and other infrastructure resources used by Kubernetes to run your applications.
-
-[**Node**](/{{page.version}}/docs/admin/node)
-: A node is a physical or virtual machine running Kubernetes, onto which pods can be scheduled.
-
-[**Pod**](/{{page.version}}/docs/user-guide/pods)
-: A pod is a co-located group of containers and volumes.
-
-[**Label**](/{{page.version}}/docs/user-guide/labels)
-: A label is a key/value pair that is attached to a resource, such as a pod, to convey a user-defined identifying attribute. Labels can be used to organize and to select subsets of resources.
-
-[**Selector**](/{{page.version}}/docs/user-guide/labels/#label-selectors)
-: A selector is an expression that matches labels in order to identify related resources, such as which pods are targeted by a load-balanced service.
-
-[**Replication Controller**](/{{page.version}}/docs/user-guide/replication-controller)
-: A replication controller ensures that a specified number of pod replicas are running at any one time. It both allows for easy scaling of replicated systems and handles re-creation of a pod when the machine it is on reboots or otherwise fails.
-
-[**Service**](/{{page.version}}/docs/user-guide/services)
-: A service defines a set of pods and a means by which to access them, such as single stable IP address and corresponding DNS name.
-
-[**Volume**](/{{page.version}}/docs/user-guide/volumes)
-: A volume is a directory, possibly with some data in it, which is accessible to a Container as part of its filesystem.  Kubernetes volumes build upon [Docker Volumes](https://docs.docker.com/userguide/dockervolumes/), adding provisioning of the volume directory and/or device.
-
-[**Secret**](/{{page.version}}/docs/user-guide/secrets)
-: A secret stores sensitive data, such as authentication tokens, which can be made available to containers upon request.
-
-[**Name**](/{{page.version}}/docs/user-guide/identifiers)
-: A user- or client-provided name for a resource.
-
-[**Namespace**](/{{page.version}}/docs/user-guide/namespaces)
-: A namespace is like a prefix to the name of a resource. Namespaces help different projects, teams, or customers to share a cluster, such as by preventing name collisions between unrelated teams.
-
-[**Annotation**](/{{page.version}}/docs/user-guide/annotations)
-: A key/value pair that can hold larger (compared to a label), and possibly not human-readable, data, intended to store non-identifying auxiliary data, especially data manipulated by tools and system extensions.  Efficient filtering by annotation values is not supported.
-
-## Further reading
-
-* API resources
-  * [Working with resources](/{{page.version}}/docs/user-guide/working-with-resources)
-
-* Pods and containers
-  * [Pod lifecycle and restart policies](/{{page.version}}/docs/user-guide/pod-states)
-  * [Lifecycle hooks](/{{page.version}}/docs/user-guide/container-environment)
-  * [Compute resources, such as cpu and memory](/{{page.version}}/docs/user-guide/compute-resources)
-  * [Specifying commands and requesting capabilities](/{{page.version}}/docs/user-guide/containers)
-  * [Downward API: accessing system configuration from a pod](/{{page.version}}/docs/user-guide/downward-api)
-  * [Images and registries](/{{page.version}}/docs/user-guide/images)
-  * [Migrating from docker-cli to kubectl](/{{page.version}}/docs/user-guide/docker-cli-to-kubectl)
-  * [Tips and tricks when working with config](/{{page.version}}/docs/user-guide/config-best-practices)
-  * [Assign pods to selected nodes](/{{page.version}}/docs/user-guide/node-selection/)
-  * [Perform a rolling update on a running group of pods](/{{page.version}}/docs/user-guide/update-demo/)
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/kubeconfig-file.md b/v1.1/docs/user-guide/kubeconfig-file.md
deleted file mode 100644
index 18441725f0..0000000000
--- a/v1.1/docs/user-guide/kubeconfig-file.md
+++ /dev/null
@@ -1,208 +0,0 @@
----
----
-
-Authentication in kubernetes can differ for different individuals.
-
-- A running kubelet might have one way of authenticating (i.e. certificates).
-- Users might have a different way of authenticating (i.e. tokens).
-- Administrators might have a list of certificates which they provide individual users.
-- There may be multiple clusters, and we may want to define them all in one place - giving users the ability to use their own certificates and reusing the same global configuration.
-
-So in order to easily switch between multiple clusters, for multiple users, a kubeconfig file was defined.
-
-This file contains a series of authentication mechanisms and cluster connection information associated with nicknames.  It also introduces the concept of a tuple of authentication information (user) and cluster connection information called a context that is also associated with a nickname.
-
-Multiple kubeconfig files are allowed.  At runtime they are loaded and merged together along with override options specified from the command line (see rules below).
-
-## Related discussion
-
-http://issue.k8s.io/1755
-
-## Example kubeconfig file
-
-The below file contains a `current-context` which will be used by default by clients which are using the file to connect to a cluster.  Thus, this kubeconfig file has more information in it then we will necessarily have to use in a given session.  You can see it defines many clusters, and users associated with those clusters.  The context itself is associated with both a cluster AND a user.
-
-```yaml
-current-context: federal-context
-apiVersion: v1
-clusters:
-- cluster:
-    api-version: v1
-    server: http://cow.org:8080
-  name: cow-cluster
-- cluster:
-    certificate-authority: path/to/my/cafile
-    server: https://horse.org:4443
-  name: horse-cluster
-- cluster:
-    insecure-skip-tls-verify: true
-    server: https://pig.org:443
-  name: pig-cluster
-contexts:
-- context:
-    cluster: horse-cluster
-    namespace: chisel-ns
-    user: green-user
-  name: federal-context
-- context:
-    cluster: pig-cluster
-    namespace: saw-ns
-    user: black-user
-  name: queen-anne-context
-kind: Config
-preferences:
-  colors: true
-users:
-- name: blue-user
-  user:
-    token: blue-token
-- name: green-user
-  user:
-    client-certificate: path/to/my/client/cert
-    client-key: path/to/my/client/key
-```
-
-### Building your own kubeconfig file
-
-NOTE, that if you are deploying k8s via kube-up.sh, you do not need to create your own kubeconfig files, the script will do it for you.
-
-In any case, you can easily use this file as a template to create your own kubeconfig files.
-
-So, lets do a quick walk through the basics of the above file so you can easily modify it as needed...
-
-The above file would likely correspond to an api-server which was launched using the `--token-auth-file=tokens.csv` option, where the tokens.csv file looked something like this:
-
-```conf
-blue-user,blue-user,1
-mister-red,mister-red,2
-```
-
-Also, since we have other users who validate using **other** mechanisms, the api-server would have probably been launched with other authentication options (there are many such options, make sure you understand which ones YOU care about before crafting a kubeconfig file, as nobody needs to implement all the different permutations of possible authentication schemes).
-
-- Since the user for the current context is "green-user", any client of the api-server using this kubeconfig file would naturally be able to log in succesfully, because we are providigin the green-user's client credentials.
-- Similarly, we can operate as the "blue-user" if we choose to change the value of current-context.
-
-In the above scenario, green-user would have to log in by providing certificates, whereas blue-user would just provide the token.  All this information would be handled for us by the
-
-## Loading and merging rules
-
-The rules for loading and merging the kubeconfig files are straightforward, but there are a lot of them.  The final config is built in this order:
-  1.  Get the kubeconfig  from disk.  This is done with the following hierarchy and merge rules:
-
-
-      If the CommandLineLocation (the value of the `kubeconfig` command line option) is set, use this file only.  No merging.  Only one instance of this flag is allowed.
-
-
-      Else, if EnvVarLocation (the value of $KUBECONFIG) is available, use it as a list of files that should be merged.
-      Merge files together based on the following rules.
-      Empty filenames are ignored.  Files with non-deserializable content produced errors.
-      The first file to set a particular value or map key wins and the value or map key is never changed.
-      This means that the first file to set CurrentContext will have its context preserved.  It also means that if two files specify a "red-user", only values from the first file's red-user are used.  Even non-conflicting entries from the second file's "red-user" are discarded.
-
-
-      Otherwise, use HomeDirectoryLocation (~/.kube/config) with no merging.
-  1.  Determine the context to use based on the first hit in this chain
-      1.  command line argument - the value of the `context` command line option
-      1.  current-context from the merged kubeconfig file
-      1.  Empty is allowed at this stage
-  1.  Determine the cluster info and user to use.  At this point, we may or may not have a context.  They are built based on the first hit in this chain.  (run it twice, once for user, once for cluster)
-      1.  command line argument - `user` for user name and `cluster` for cluster name
-      1.  If context is present, then use the context's value
-      1.  Empty is allowed
-  1.  Determine the actual cluster info to use.  At this point, we may or may not have a cluster info.  Build each piece of the cluster info based on the chain (first hit wins):
-      1.  command line arguments - `server`, `api-version`, `certificate-authority`, and `insecure-skip-tls-verify`
-      1.  If cluster info is present and a value for the attribute is present, use it.
-      1.  If you don't have a server location, error.
-  1.  Determine the actual user info to use. User is built using the same rules as cluster info, EXCEPT that you can only have one authentication technique per user.
-      1. Load precedence is 1) command line flag, 2) user fields from kubeconfig
-      1. The command line flags are: `client-certificate`, `client-key`, `username`, `password`, and `token`.
-      1. If there are two conflicting techniques, fail.
-  1.  For any information still missing, use default values and potentially prompt for authentication information
-
-## Manipulation of kubeconfig via `kubectl config <subcommand>`
-
-In order to more easily manipulate kubeconfig files, there are a series of subcommands to `kubectl config` to help.
-See [kubectl/kubectl_config.md](/{{page.version}}/docs/user-guide/kubectl/kubectl_config) for help.
-
-### Example
-
-```shell
-$ kubectl config set-credentials myself --username=admin --password=secret
-$ kubectl config set-cluster local-server --server=http://localhost:8080
-$ kubectl config set-context default-context --cluster=local-server --user=myself
-$ kubectl config use-context default-context
-$ kubectl config set contexts.default-context.namespace the-right-prefix
-$ kubectl config view
-```
-
-produces this output
-
-```yaml
-apiVersion: v1
-clusters:
-- cluster:
-    server: http://localhost:8080
-  name: local-server
-contexts:
-- context:
-    cluster: local-server
-    namespace: the-right-prefix
-    user: myself
-  name: default-context
-current-context: default-context
-kind: Config
-preferences: {}
-users:
-- name: myself
-  user:
-    password: secret
-    username: admin
-```
-
-and a kubeconfig file that looks like this
-
-```yaml
-apiVersion: v1
-clusters:
-- cluster:
-    server: http://localhost:8080
-  name: local-server
-contexts:
-- context:
-    cluster: local-server
-    namespace: the-right-prefix
-    user: myself
-  name: default-context
-current-context: default-context
-kind: Config
-preferences: {}
-users:
-- name: myself
-  user:
-    password: secret
-    username: admin
-```
-
-#### Commands for the example file
-
-```shell
-$ kubectl config set preferences.colors true
-$ kubectl config set-cluster cow-cluster --server=http://cow.org:8080 --api-version=v1
-$ kubectl config set-cluster horse-cluster --server=https://horse.org:4443 --certificate-authority=path/to/my/cafile
-$ kubectl config set-cluster pig-cluster --server=https://pig.org:443 --insecure-skip-tls-verify=true
-$ kubectl config set-credentials blue-user --token=blue-token
-$ kubectl config set-credentials green-user --client-certificate=path/to/my/client/cert --client-key=path/to/my/client/key
-$ kubectl config set-context queen-anne-context --cluster=pig-cluster --user=black-user --namespace=saw-ns
-$ kubectl config set-context federal-context --cluster=horse-cluster --user=green-user --namespace=chisel-ns
-$ kubectl config use-context federal-context
-```
-
-### Final notes for tying it all together
-
-So, tying this all together, a quick start to creating your own kubeconfig file:
-
-- Take a good look and understand how you're api-server is being launched: You need to know YOUR security requirements and policies before you can design a kubeconfig file for convenient authentication.
-
-- Replace the snippet above with information for your cluster's api-server endpoint.
-
-- Make sure your api-server is launched in such a way that at least one user (i.e. green-user) credentials are provided to it.  You will of course have to look at api-server documentation in order to determine the current state-of-the-art in terms of providing authentication details.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/kubectl-overview.md b/v1.1/docs/user-guide/kubectl-overview.md
deleted file mode 100644
index 9e0d94562a..0000000000
--- a/v1.1/docs/user-guide/kubectl-overview.md
+++ /dev/null
@@ -1,270 +0,0 @@
----
----
-
-Use this overview of the `kubectl` command line interface to help you start running commands against Kubernetes clusters. This overview quickly covers `kubectl` syntax, describes the command operations, and provides common examples. For details about each command, including all the supported flags and subcommands, see the [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) reference documentation.
-
-TODO: Auto-generate this file to ensure it's always in sync with any `kubectl` changes, see [#14177](http://pr.k8s.io/14177).
-
-## Syntax
-
-Use the following syntax to run `kubectl` commands from your terminal window:
-
-```shell
-kubectl [command] [TYPE] [NAME] [flags]
-```
-
-where `command`, `TYPE`, `NAME`, and `flags` are:
-
-* `command`: Specifies the operation that you want to perform on one or more resources, for example `create`, `get`, `describe`, `delete`.
-* `TYPE`: Specifies the [resource type](#resource-types). Resource types are case-sensitive and you can specify the singular, plural, or abbreviated forms. For example, the following commands produce the same output:
-
-```shell
-$ kubectl get pod pod1
-$ kubectl get pods pod1
-$ kubectl get po pod1
-```
-
-* `NAME`: Specifies the name of the resource. Names are case-sensitive. If the name is omitted, details for all resources are displayed, for example `$ kubectl get pods`.
-
-When performing an operation on multiple resources, you can specify each resource by type and name or specify one or more files:
-
-* To specify resources by type and name:
-	    * To group resources if they are all the same type: `TYPE1 name1 name2 name<#>`<br/>
-        Example: `$ kubectl get pod example-pod1 example-pod2`
-        * To specify multiple resource types individually: `TYPE1/name1 TYPE1/name2 TYPE2/name3 TYPE<#>/name<#>`<br/>
-        Example: `$ kubectl get pod/example-pod1 replicationcontroller/example-rc1`
-   * To specify resources with one or more files: `-f file1 -f file2 -f file<#>`
-	 [Use YAML rather than JSON](/{{page.version}}/docs/user-guide/config-best-practices) since YAML tends to be more user-friendly, especially for configuration files.<br/>
-     Example: `$ kubectl get pod -f ./pod.yaml`
-* `flags`: Specifies optional flags. For example, you can use the `-s` or `--server` flags to specify the address and port of the Kubernetes API server.
-
-**Important**: Flags that you specify from the command line override default values and any corresponding environment variables.
-
-If you need help, just run `kubectl help` from the terminal window.
-
-## Operations
-
-The following table includes short descriptions and the general syntax for all of the `kubectl` operations:
-
-Operation       | Syntax	|       Description
--------------------- | -------------------- | --------------------
-`annotate`	| `kubectl annotate (-f FILENAME | TYPE NAME | TYPE/NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--overwrite] [--all] [--resource-version=version] [flags]` | Add or update the annotations of one or more resources.
-`api-versions`	| `kubectl api-versions [flags]` | List the API versions that are available.
-`apply`			| `kubectl apply -f FILENAME [flags]`| Apply a configuration change to a resource from a file or stdin.
-`attach`		| `kubectl attach POD -c CONTAINER [-i] [-t] [flags]` | Attach to a running container either to view the output stream or interact with the container (stdin).
-`autoscale`	| `autoscale (-f FILENAME | TYPE NAME | TYPE/NAME) [--min=MINPODS] --max=MAXPODS [--cpu-percent=CPU] [flags]` | Automatically scale the set of pods that are managed by a replication controller.
-`cluster-info`	| `kubectl cluster-info [flags]` | Display endpoint information about the master and services in the cluster.
-`config`		| `kubectl config SUBCOMMAND [flags]` | Modifies kubeconfig files. See the individual subcommands for details.
-`create`		| `kubectl create -f FILENAME [flags]` | Create one or more resources from a file or stdin.
-`delete`		| `kubectl delete (-f FILENAME | TYPE [NAME | /NAME | -l label | --all]) [flags]` | Delete resources either from a file, stdin, or specifying label selectors, names, resource selectors, or resources.
-`describe`	| `kubectl describe (-f FILENAME | TYPE [NAME_PREFIX | /NAME | -l label]) [flags]` | Display the detailed state of one or more resources.
-`edit`		| `kubectl edit (-f FILENAME | TYPE NAME | TYPE/NAME) [flags]` | Edit and update the definition of one or more resources on the server by using the default editor.
-`exec`		| `kubectl exec POD [-c CONTAINER] [-i] [-t] [flags] [-- COMMAND [args...]]` | Execute a command against a container in a pod.
-`expose`		| `kubectl expose (-f FILENAME | TYPE NAME | TYPE/NAME) [--port=port] [--protocol=TCP|UDP] [--target-port=number-or-name] [--name=name] [----external-ip=external-ip-of-service] [--type=type] [flags]` | Expose a replication controller, service, or pod as a new Kubernetes service.
-`get`		| `kubectl get (-f FILENAME | TYPE [NAME | /NAME | -l label]) [--watch] [--sort-by=FIELD] [[-o | --output]=OUTPUT_FORMAT] [flags]` | List one or more resources.
-`label`		| `kubectl label (-f FILENAME | TYPE NAME | TYPE/NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--overwrite] [--all] [--resource-version=version] [flags]` | Add or update the labels of one or more resources.
-`logs`		| `kubectl logs POD [-c CONTAINER] [--follow] [flags]` | Print the logs for a container in a pod.
-`patch`		| `kubectl patch (-f FILENAME | TYPE NAME | TYPE/NAME) --patch PATCH [flags]` | Update one or more fields of a resource by using the strategic merge patch process.
-`port-forward`	| `kubectl port-forward POD [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags]` | Forward one or more local ports to a pod.
-`proxy`		| `kubectl proxy [--port=PORT] [--www=static-dir] [--www-prefix=prefix] [--api-prefix=prefix] [flags]` | Run a proxy to the Kubernetes API server.
-`replace`		| `kubectl replace -f FILENAME` | Replace a resource from a file or stdin.
-`rolling-update`	| `kubectl rolling-update OLD_CONTROLLER_NAME ([NEW_CONTROLLER_NAME] --image=NEW_CONTAINER_IMAGE | -f NEW_CONTROLLER_SPEC) [flags]` | Perform a rolling update by gradually replacing the specified replication controller and its pods.
-`run`		| `kubectl run NAME --image=image [--env="key=value"] [--port=port] [--replicas=replicas] [--dry-run=bool] [--overrides=inline-json] [flags]` | Run a specified image on the cluster.
-`scale`		| `kubectl scale (-f FILENAME | TYPE NAME | TYPE/NAME) --replicas=COUNT [--resource-version=version] [--current-replicas=count] [flags]` | Update the size of the specified replication controller.
-`stop`		| `kubectl stop` | Deprecated: Instead, see `kubectl delete`.
-`version`		| `kubectl version [--client] [flags]` | Display the Kubernetes version running on the client and server.
-
-Remember: For more about command operations, see the [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) reference documentation.
-
-## Resource types
-
-The following table includes a list of all the supported resource types and their abbreviated aliases:
-
-Resource type	| Abbreviated alias
--------------------- | --------------------
-`componentstatuses`	|	`cs`
-`events`	|	`ev`
-`endpoints`	|	`ep`
-`horizontalpodautoscalers`	|	`hpa`
-`limitranges`	|	`limits`
-`nodes`	|	`no`
-`namespaces`	|	`ns`
-`pods`	|	`po`
-`persistentvolumes`	|	`pv`
-`persistentvolumeclaims`	|	`pvc`
-`resourcequotas`	|	`quota`
-`replicationcontrollers`	|	`rc`
-`secrets`	|
-`serviceaccounts`	|
-`services`	|	`svc`
-`ingress`		|	`ing`
-
-## Output options
-
-Use the following sections for information about how you can format or sort the output of certain commands. For details about which commands support the various output options, see the [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) reference documentation.
-
-### Formatting output
-
-The default output format for all `kubectl` commands is the human readable plain-text format. To output details to your terminal window in a specific format, you can add either the `-o` or `-output` flags to a supported `kubectl` command.
-
-#### Syntax
-
-```shell
-kubectl [command] [TYPE] [NAME] -o=<output_format>
-```
-
-Depending on the `kubectl` operation, the following output formats are supported:
-
-Output format | Description
---------------| -----------
-`-o=custom-columns=<spec>` | Print a table using a comma separated list of [custom columns](#custom-columns).
-`-o=custom-columns-file=<filename>` | Print a table using the [custom columns](#custom-columns) template in the `<filename>` file.
-`-o=json`     | Output a JSON formatted API object.
-`-o=jsonpath=<template>` | Print the fields defined in a [jsonpath](/{{page.version}}/docs/user-guide/jsonpath) expression.
-`-o=jsonpath-file=<filename>` | Print the fields defined by the [jsonpath](/{{page.version}}/docs/user-guide/jsonpath) expression in the `<filename>` file.
-`-o=name`     | Print only the resource name and nothing else.
-`-o=wide`     | Output in the plain-text format with any additional information. For pods, the node name is included.
-`-o=yaml`     | Output a YAML formatted API object.
-
-##### Example
-
-In this example, the following command outputs the details for a single pod as a YAML formatted object:
-
-`$ kubectl get pod web-pod-13je7 -o=yaml`
-
-Remember: See the [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) reference documentation for details about which output format is supported by each command.
-
-#### Custom columns
-
-To define custom columns and output only the details that you want into a table, you can use the `custom-columns` option. You can choose to define the custom columns inline or use a template file: `-o=custom-columns=<spec>` or `-o=custom-columns-file=<filename>`.
-
-##### Examples
-
-Inline:
-
-```shell
-$ kubectl get pods <pod-name> -o=custom-columns=NAME:.metadata.name,RSRC:.metadata.resourceVersion
-```
-
-Template file:
-
-```shell
-$ kubectl get pods <pod-name> -o=custom-columns-file=template.txt
-```
-
-where the `template.txt` file contains:
-
-```
-NAME                    RSRC
-      metadata.name           metadata.resourceVersion
-```
-The result of running either command is:
-
-```shell
-NAME           RSRC
-submit-queue   610995
-```
-
-### Sorting list objects
-
-To output objects to a sorted list in your terminal window, you can add the `--sort-by` flag to a supported `kubectl` command. Sort your objects by specifying any numeric or string field with the `--sort-by` flag. To specify a field, use a [jsonpath](/{{page.version}}/docs/user-guide/jsonpath) expression.
-
-#### Syntax
-
-```shell
-kubectl [command] [TYPE] [NAME] --sort-by=<jsonpath_exp>
-```
-
-##### Example
-
-To print a list of pods sorted by name, you run:
-
-`$ kubectl get pods --sort-by=.metadata.name`
-
-## Examples: Common operations
-
-Use the following set of examples to help you familiarize yourself with running the commonly used `kubectl` operations:
-
-`kubectl create` - Create a resource from a file or stdin.
-
-```shell
-// Create a service using the definition in example-service.yaml.
-$ kubectl create -f example-service.yaml
-
-// Create a replication controller using the definition in example-controller.yaml.
-$ kubectl create -f example-controller.yaml
-
-// Create the objects that are defined in any .yaml, .yml, or .json file within the <directory> directory.
-$ kubectl create -f <directory>
-```
-
-`kubectl get` - List one or more resources.
-
-```shell
-// List all pods in plain-text output format.
-$ kubectl get pods
-
-// List all pods in plain-text output format and includes additional information (such as node name).
-$ kubectl get pods -o wide
-
-// List the replication controller with the specified name in plain-text output format. Tip: You can shorten and replace the 'replicationcontroller' resource type with the alias 'rc'.
-$ kubectl get replicationcontroller <rc-name>
-
-// List all replication controllers and services together in plain-text output format.
-$ kubectl get rc,services
-```
-
-`kubectl describe` - Display detailed state of one or more resources.
-
-```shell
-// Display the details of the node with name <node-name>.
-$ kubectl describe nodes <node-name>
-
-// Display the details of the pod with name <pod-name>.
-$ kubectl describe pods/<pod-name>
-
-// Display the details of all the pods that are managed by the replication controller named <rc-name>.
-// Remember: Any pods that are created by the replication controller get prefixed with the name of the replication controller.
-$ kubectl describe pods <rc-name>
-```
-
-`kubectl delete` - Delete resources either from a file, stdin, or specifying label selectors, names, resource selectors, or resources.
-
-```shell
-// Delete a pod using the type and name specified in the pod.yaml file.
-$ kubectl delete -f pod.yaml
-
-// Delete all the pods and services that have the label name=<label-name>.
-$ kubectl delete pods,services -l name=<label-name>
-
-// Delete all pods.
-$ kubectl delete pods --all
-```
-
-`kubectl exec` - Execute a command against a container in a pod.
-
-```shell
-// Get output from running 'date' from pod <pod-name>. By default, output is from the first container.
-$ kubectl exec <pod-name> date
-
-// Get output from running 'date' in container <container-name> of pod <pod-name>.
-$ kubectl exec <pod-name> -c <container-name> date
-
-// Get an interactive TTY and run /bin/bash from pod <pod-name>. By default, output is from the first container.
-$ kubectl exec -ti <pod-name> /bin/bash
-```
-
-`kubectl logs` - Print the logs for a container in a pod.
-
-```shell
-// Return a snapshot of the logs from pod <pod-name>.
-$ kubectl logs <pod-name>
-
-// Start streaming the logs from pod <pod-name>. This is similiar to the 'tail -f' Linux command.
-$ kubectl logs -f <pod-name>
-```
-
-
-## Next steps
-
-Start using the [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) commands.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/labels.md b/v1.1/docs/user-guide/labels.md
deleted file mode 100644
index 31eddd0216..0000000000
--- a/v1.1/docs/user-guide/labels.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
----
-
-_Labels_ are key/value pairs that are attached to objects, such as pods.
-Labels are intended to be used to specify identifying attributes of objects that are meaningful and relevant to users, but which do not directly imply semantics to the core system.
-Labels can be used to organize and to select subsets of objects.  Labels can be attached to objects at creation time and subsequently added and modified at any time.
-Each object can have a set of key/value labels defined.  Each Key must be unique for a given object.
-
-```json
-"labels": {
-  "key1" : "value1",
-  "key2" : "value2"
-}
-```
-
-We'll eventually index and reverse-index labels for efficient queries and watches, use them to sort and group in UIs and CLIs, etc. We don't want to pollute labels with non-identifying, especially large and/or structured, data. Non-identifying information should be recorded using [annotations](/{{page.version}}/docs/user-guide/annotations).
-
-* TOC
-{:toc}
-
-## Motivation
-
-Labels enable users to map their own organizational structures onto system objects in a loosely coupled fashion, without requiring clients to store these mappings.
-
-Service deployments and batch processing pipelines are often multi-dimensional entities (e.g., multiple partitions or deployments, multiple release tracks, multiple tiers, multiple micro-services per tier). Management often requires cross-cutting operations, which breaks encapsulation of strictly hierarchical representations, especially rigid hierarchies determined by the infrastructure rather than by users.
-
-Example labels:
-
-   * `"release" : "stable"`, `"release" : "canary"`
-   * `"environment" : "dev"`, `"environment" : "qa"`, `"environment" : "production"`
-   * `"tier" : "frontend"`, `"tier" : "backend"`, `"tier" : "cache"`
-   * `"partition" : "customerA"`, `"partition" : "customerB"`
-   * `"track" : "daily"`, `"track" : "weekly"`
-
-These are just examples; you are free to develop your own conventions.
-
-## Syntax and character set
-
-_Labels_ are key value pairs. Valid label keys have two segments: an optional prefix and name, separated by a slash (`/`).  The name segment is required and must be 63 characters or less, beginning and ending with an alphanumeric character (`[a-z0-9A-Z]`) with dashes (`-`), underscores (`_`), dots (`.`), and alphanumerics between.  The prefix is optional.  If specified, the prefix must be a DNS subdomain: a series of DNS labels separated by dots (`.`), not longer than 253 characters in total, followed by a slash (`/`).
-If the prefix is omitted, the label key is presumed to be private to the user. Automated system components (e.g. `kube-scheduler`, `kube-controller-manager`, `kube-apiserver`, `kubectl`, or other third-party automation) which add labels to end-user objects must specify a prefix.  The `kubernetes.io/` prefix is reserved for Kubernetes core components.
-
-Valid label values must be 63 characters or less and must be empty or begin and end with an alphanumeric character (`[a-z0-9A-Z]`) with dashes (`-`), underscores (`_`), dots (`.`), and alphanumerics between.
-
-## Label selectors
-
-Unlike [names and UIDs](/{{page.version}}/docs/user-guide/identifiers), labels do not provide uniqueness. In general, we expect many objects to carry the same label(s).
-
-Via a _label selector_, the client/user can identify a set of objects. The label selector is the core grouping primitive in Kubernetes.
-
-The API currently supports two types of selectors: _equality-based_ and _set-based_.
-A label selector can be made of multiple _requirements_ which are comma-separated. In the case of multiple requirements, all must be satisfied so the comma separator acts as an _AND_ logical operator.
-
-An empty label selector (that is, one with zero requirements) selects every object in the collection.
-
-A null label selector (which is only possible for optional selector fields) selects no objects.
-
-### _Equality-based_ requirement
-
-_Equality-_ or _inequality-based_ requirements allow filtering by label keys and values. Matching objects must satisfy all of the specified label constraints, though they may have additional labels as well.
-Three kinds of operators are admitted `=`,`==`,`!=`. The first two represent _equality_ (and are simply synonyms), while the latter represents _inequality_. For example:
-
-```
-environment = production
-tier != frontend
-```
-
-The former selects all resources with key equal to `environment` and value equal to `production`.
-The latter selects all resources with key equal to `tier` and value distinct from `frontend`, and all resources with no labels with the `tier` key.
-One could filter for resources in `production` excluding `frontend` using the comma operator: `environment=production,tier!=frontend`
-
-
-### _Set-based_ requirement
-
-_Set-based_ label requirements allow filtering keys according to a set of values. Three kinds of operators are supported: `in`,`notin` and exists (only the key identifier). For example:
-
-```
-environment in (production, qa)
-tier notin (frontend, backend)
-partition
-!partition
-```
-
-The first example selects all resources with key equal to `environment` and value equal to `production` or `qa`.
-The second example selects all resources with key equal to `tier` and values other than `frontend` and `backend`, and all resources with no labels with the `tier` key.
-The third example selects all resources including a label with key `partition`; no values are checked.
-The fourth example selects all resources without a label with key `partition`; no values are checked.
-Similarly the comma separator acts as an _AND_ operator. So filtering resources with a `partition` key (no matter the value) and with `environment` different than  `qa` can be achieved using `partition,environment notin (qa)`.
-The _set-based_ label selector is a general form of equality since `environment=production` is equivalent to `environment in (production)`; similarly for `!=` and `notin`.
-
-_Set-based_ requirements can be mixed with _equality-based_ requirements. For example: `partition in (customerA, customerB),environment!=qa`.
-
-
-## API
-
-### LIST and WATCH filtering
-
-LIST and WATCH operations may specify label selectors to filter the sets of objects returned using a query parameter. Both requirements are permitted:
-
-    * _equality-based_ requirements: `?labelSelector=environment%3Dproduction,tier%3Dfrontend`
-    * _set-based_ requirements: `?labelSelector=environment+in+%28production%2Cqa%29%2Ctier+in+%28frontend%29`
-
-Both label selector styles can be used to list or watch resources via a REST client. For example targetting `apiserver` with `kubectl` and using _equality-based_ one may write:
-
-```shell
-$ kubectl get pods -l environment=production,tier=frontend
-```
-
-or using _set-based_ requirements:
-
-```shell
-$ kubectl get pods -l 'environment in (production),tier in (frontend)'
-```
-
-As already mentioned _set-based_ requirements are more expressive.  For instance, they can implement the _OR_ operator on values:
-
-```shell
-$ kubectl get pods -l 'environment in (production, qa)'
-```
-
-or restricting negative matching via _exists_ operator:
-
-```shell
-$ kubectl get pods -l 'environment,environment notin (frontend)'
-```
-
-### Set references in API objects
-
-Some Kubernetes objects, such as [`service`s](/{{page.version}}/docs/user-guide/services) and [`replicationcontroller`s](/{{page.version}}/docs/user-guide/replication-controller), also use label selectors to specify sets of other resources, such as [pods](/{{page.version}}/docs/user-guide/pods).
-
-#### Service and ReplicationController
-
-The set of pods that a `service` targets is defined with a label selector. Similarly, the population of pods that a `replicationcontroller` should manage is also defined with a label selector.
-
-Labels selectors for both objects are defined in `json` or `yaml` files using maps, and only _equality-based_ requirement selectors are supported:
-
-```json
-"selector": {
-    "component" : "redis",
-}
-```
-or
-
-```yaml
-selector:
-    component: redis
-```
-
-this selector (respectively in `json` or `yaml` format) is equivalent to `component=redis` or `component in (redis)`.
-
-#### Job and other new resources
-
-Newer resources, such as [job](/{{page.version}}/docs/user-guide/jobs), support _set-based_ requirements as well.
-
-```yaml
-selector:
-  matchLabels:
-    component: redis
-  matchExpressions:
-    - {key: tier, operator: In, values: [cache]}
-    - {key: environment, operator: NotIn, values: [dev]}
-```
-
-`matchLabels` is a map of `{key,value}` pairs. A single `{key,value}` in the `matchLabels` map is equivalent to an element of `matchExpressions`, whose `key` field is "key", the `operator` is "In", and the `values` array contains only "value". `matchExpressions` is a list of pod selector requirements. Valid operators include In, NotIn, Exists, and DoesNotExist. The values set must be non-empty in the case of In and NotIn. All of the requirements, from both `matchLabels` and `matchExpressions` are ANDed together -- they must all be satisfied in order to match.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/logging-demo/index.md b/v1.1/docs/user-guide/logging-demo/index.md
deleted file mode 100644
index 32460c5608..0000000000
--- a/v1.1/docs/user-guide/logging-demo/index.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
----
-
-This directory contains two [pod](/{{page.version}}/docs/user-guide/pods) specifications which can be used as synthetic
-logging sources. The pod specification in [synthetic_0_25lps.yaml](/{{page.version}}/docs/user-guide/logging-demo/synthetic_0_25lps.yaml)
-describes a pod that just emits a log message once every 4 seconds. The pod specification in
-[synthetic_10lps.yaml](/{{page.version}}/docs/user-guide/logging-demo/synthetic_10lps.yaml)
-describes a pod that just emits 10 log lines per second.
-
-See [logging document](/{{page.version}}/docs/user-guide/logging/) for more details about logging. To observe the ingested log lines when using Google Cloud Logging please see the getting
-started instructions
-at [Cluster Level Logging to Google Cloud Logging](/{{page.version}}/docs/getting-started-guides/logging).
-To observe the ingested log lines when using Elasticsearch and Kibana please see the getting
-started instructions
-at [Cluster Level Logging with Elasticsearch and Kibana](/{{page.version}}/docs/getting-started-guides/logging-elasticsearch).
-
-
-
diff --git a/v1.1/docs/user-guide/logging.md b/v1.1/docs/user-guide/logging.md
deleted file mode 100644
index fb0a62a633..0000000000
--- a/v1.1/docs/user-guide/logging.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
----
-
-This page is designed to help you use logs to troubleshoot issues with your Kubernetes solution.
-
-## Logging by Kubernetes Components
-
-Kubernetes components, such as kubelet and apiserver, use the [glog](https://godoc.org/github.com/golang/glog) logging library.  Developer conventions for logging severity are described in [docs/devel/logging.md](/{{page.version}}/docs/devel/logging).
-
-## Examining the logs of running containers
-
-The logs of a running container may be fetched using the command `kubectl logs`. For example, given
-this pod specification [counter-pod.yaml](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/blog-logging/counter-pod.yaml), which has a container which writes out some text to standard
-output every second. (You can find different pod specifications [here](/{{page.version}}/docs/user-guide/logging-demo/).)
-
-<!-- BEGIN MUNGE: EXAMPLE ../../examples/blog-logging/counter-pod.yaml -->
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: counter
-spec:
-  containers:
-  - name: count
-    image: ubuntu:14.04
-    args: [bash, -c, 
-           'for ((i = 0; ; i++)); do echo "$i: $(date)"; sleep 1; done']
-```
-
-[Download example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/blog-logging/counter-pod.yaml)
-<!-- END MUNGE: EXAMPLE ../../examples/blog-logging/counter-pod.yaml -->
-
-we can run the pod:
-
-```shell
-$ kubectl create -f ./counter-pod.yaml
-pods/counter
-```
-
-and then fetch the logs:
-
-```shell
-$ kubectl logs counter
-0: Tue Jun  2 21:37:31 UTC 2015
-1: Tue Jun  2 21:37:32 UTC 2015
-2: Tue Jun  2 21:37:33 UTC 2015
-3: Tue Jun  2 21:37:34 UTC 2015
-4: Tue Jun  2 21:37:35 UTC 2015
-5: Tue Jun  2 21:37:36 UTC 2015
-...
-```
-
-If a pod has more than one container then you need to specify which container's log files should
-be fetched e.g.
-
-```shell
-$ kubectl logs kube-dns-v3-7r1l9 etcd
-2015/06/23 00:43:10 etcdserver: start to snapshot (applied: 30003, lastsnap: 20002)
-2015/06/23 00:43:10 etcdserver: compacted log at index 30003
-2015/06/23 00:43:10 etcdserver: saved snapshot at index 30003
-2015/06/23 02:05:42 etcdserver: start to snapshot (applied: 40004, lastsnap: 30003)
-2015/06/23 02:05:42 etcdserver: compacted log at index 40004
-2015/06/23 02:05:42 etcdserver: saved snapshot at index 40004
-2015/06/23 03:28:31 etcdserver: start to snapshot (applied: 50005, lastsnap: 40004)
-2015/06/23 03:28:31 etcdserver: compacted log at index 50005
-2015/06/23 03:28:31 etcdserver: saved snapshot at index 50005
-2015/06/23 03:28:56 filePurge: successfully removed file default.etcd/member/wal/0000000000000000-0000000000000000.wal
-2015/06/23 04:51:03 etcdserver: start to snapshot (applied: 60006, lastsnap: 50005)
-2015/06/23 04:51:03 etcdserver: compacted log at index 60006
-2015/06/23 04:51:03 etcdserver: saved snapshot at index 60006
-...
-```
-
-## Cluster level logging to Google Cloud Logging
-
-The getting started guide [Cluster Level Logging to Google Cloud Logging](/{{page.version}}/docs/getting-started-guides/logging)
-explains how container logs are ingested into [Google Cloud Logging](https://cloud.google.com/logging/docs/)
-and shows how to query the ingested logs.
-
-## Cluster level logging with Elasticsearch and Kibana
-
-The getting started guide [Cluster Level Logging with Elasticsearch and Kibana](/{{page.version}}/docs/getting-started-guides/logging-elasticsearch)
-describes how to ingest cluster level logs into Elasticsearch and view them using Kibana.
-
-## Ingesting Application Log Files
-
-Cluster level logging only collects the standard output and standard error output of the applications
-running in containers. The guide [Collecting log files within containers with Fluentd](http://releases.k8s.io/{{page.githubbranch}}/contrib/logging/fluentd-sidecar-gcp/README.md) explains how the log files of applications can also be ingested into Google Cloud logging.
-
-## Known issues
-
-Kubernetes does log rotation for Kubernetes components and docker containers. The command `kubectl logs` currently only read the latest logs, not all historical ones.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/namespaces.md b/v1.1/docs/user-guide/namespaces.md
deleted file mode 100644
index b473e21b32..0000000000
--- a/v1.1/docs/user-guide/namespaces.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
----
-
-Kubernetes supports multiple virtual clusters backed by the same physical cluster.
-These virtual clusters are called namespaces.
-
-## When to Use Multiple Namespaces
-
-Namespaces are intended for use in environments with many users spread across multiple
-teams, or projects.  For clusters with a few to tens of users, you should not
-need to create or think about namespaces at all.  Start using namespaces when you
-need the features they provide.
-
-Namespaces provide a scope for names.  Names of resources need to be unique within a namespace, but not across namespaces.
-
-Namespaces are a way to divide cluster resources between multiple uses (via [resource quota](/{{page.version}}/docs/admin/resource-quota)).
-
-In future versions of Kubernetes, objects in the same namespace will have the same
-access control policies by default.
-
-It is not necessary to use multiple namespaces just to separate slightly different
-resources, such as different versions of the same software: use [labels](/{{page.version}}/docs/user-guide/labels) to distinguish
-resources within the same namespace.
-
-## Working with Namespaces
-
-Creation and deletion of namespaces is described in the [Admin Guide documentation
-for namespaces](/{{page.version}}/docs/admin/namespaces)
-
-### Viewing namespaces
-
-You can list the current namespaces in a cluster using:
-
-```shell
-$ kubectl get namespaces
-NAME          LABELS    STATUS
-default       <none>    Active
-kube-system   <none>    Active
-```
-
-Kubernetes starts with two initial namespaces:
-
-   * `default` The default namespace for objects with no other namespace
-   * `kube-system` The namespace for objects created by the Kubernetes system
-
-### Setting the namespace for a request
-
-To temporarily set the namespace for a request, use the `--namespace` flag.
-
-For example:
-
-```shell
-$ kubectl --namespace=<insert-namespace-name-here> run nginx --image=nginx
-$ kubectl --namespace=<insert-namespace-name-here> get pods
-```
-
-### Setting the namespace preference
-
-You can permanently save the namespace for all subsequent kubectl commands in that
-context.
-
-First get your current context:
-
-```shell
-$ export CONTEXT=$(kubectl config view | grep current-context | awk '{print $2}')
-```
-
-Then update the default namespace:
-
-```shell
-$ kubectl config set-context $(CONTEXT) --namespace=<insert-namespace-name-here>
-```
-
-## Namespaces and DNS
-
-When you create a [Service](/{{page.version}}/docs/user-guide/services), it creates a corresponding [DNS entry](/{{page.version}}/docs/admin/dns).
-This entry is of the form `<service-name>.<namespace-name>.svc.cluster.local`, which means
-that if a container just uses `<service-name>` it will resolve to the service which
-is local to a namespace.  This is useful for using the same configuration across
-multiple namespaces such as Development, Staging and Production.  If you want to reach
-across namespaces, you need to use the fully qualified domain name (FQDN).
-
-## Not All Objects are in a Namespace
-
-Most kubernetes resources (e.g. pods, services, replication controllers, and others) are
-in a some namespace.  However namespace resources are not themselves in a namespace.
-And, low-level resources, such as [nodes](/{{page.version}}/docs/admin/node) and
-persistentVolumes, are not in any namespace. Events are an exception: they may or may not
-have a namespace, depending on the object the event is about.
diff --git a/v1.1/docs/user-guide/overview.md b/v1.1/docs/user-guide/overview.md
deleted file mode 100644
index 74594d02b0..0000000000
--- a/v1.1/docs/user-guide/overview.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
----
-
-Kubernetes is an open-source system for managing containerized applications across multiple hosts in a cluster. Kubernetes is intended to make deploying containerized/microservice-based applications easy but powerful.
-
-Kubernetes provides mechanisms for application deployment, scheduling, updating, maintenance, and scaling. A key feature of Kubernetes is that it actively manages the containers to ensure that the state of the cluster continually matches the user's intentions. An operations user should be able to launch a micro-service, letting the scheduler find the right placement. We also want to improve the tools and experience for how users can roll-out applications through patterns like canary deployments.
-
-Kubernetes supports [Docker](http://www.docker.io) and [Rocket](https://coreos.com/blog/rocket/) containers, and other container image formats and container runtimes will be supported in the future.
-
-While Kubernetes currently focuses on continuously-running stateless (e.g. web server or in-memory object cache) and "cloud native" stateful applications (e.g. NoSQL datastores), in the near future it will support all the other workload types commonly found in production cluster environments, such as batch, stream processing, and traditional databases.
-
-In Kubernetes, all containers run inside [pods](/{{page.version}}/docs/user-guide/pods). A pod can host a single container, or multiple cooperating containers; in the latter case, the containers in the pod are guaranteed to be co-located on the same machine and can share resources. A pod can also contain zero or more [volumes](/{{page.version}}/docs/user-guide/volumes), which are directories that are private to a container or shared across containers in a pod. For each pod the user creates, the system finds a machine that is healthy and that has sufficient available capacity, and starts up the corresponding container(s) there. If a container fails it can be automatically restarted by Kubernetes' node agent, called the Kubelet. But if the pod or its machine fails, it is not automatically moved or restarted unless the user also defines a [replication controller](/{{page.version}}/docs/user-guide/replication-controller), which we discuss next.
-
-Users can create and manage pods themselves, but Kubernetes drastically simplifies system management by allowing users to delegate two common pod-related activities: deploying multiple pod replicas based on the same pod configuration, and creating replacement pods when a pod or its machine fails. The Kubernetes API object that manages these behaviors is called a [replication controller](/{{page.version}}/docs/user-guide/replication-controller). It defines a pod in terms of a template, that the system then instantiates as some number of pods (specified by the user). The replicated set of pods might constitute an entire application, a micro-service, or one layer in a multi-tier application. Once the pods are created, the system continually monitors their health and that of the machines they are running on; if a pod fails due to a software problem or machine failure, the replication controller automatically creates a new pod on a healthy machine, to maintain the set of pods at the desired replication level. Multiple pods from the same or different applications can share the same machine. Note that a replication controller is needed even in the case of a single non-replicated pod if the user wants it to be re-created when it or its machine fails.
-
-Frequently it is useful to refer to a set of pods, for example to limit the set of pods on which a mutating operation should be performed, or that should be queried for status. As a general mechanism, users can attach to most Kubernetes API objects arbitrary key-value pairs called [labels](/{{page.version}}/docs/user-guide/labels), and then use a set of label selectors (key-value queries over labels) to constrain the target of API operations. Each resource also has a map of string keys and values that can be used by external tooling to store and retrieve arbitrary metadata about this object, called [annotations](/{{page.version}}/docs/user-guide/annotations).
-
-Kubernetes supports a unique [networking model](/{{page.version}}/docs/admin/networking). Kubernetes encourages a flat address space and does not dynamically allocate ports, instead allowing users to select whichever ports are convenient for them. To achieve this, it allocates an IP address for each pod.
-
-Modern Internet applications are commonly built by layering micro-services, for example a set of web front-ends talking to a distributed in-memory key-value store talking to a replicated storage service. To facilitate this architecture, Kubernetes offers the [service](/{{page.version}}/docs/user-guide/services) abstraction, which provides a stable IP address and [DNS name](/{{page.version}}/docs/admin/dns) that corresponds to a dynamic set of pods such as the set of pods constituting a micro-service. The set is defined using a label selector and thus can refer to any set of pods. When a container running in a Kubernetes pod connects to this address, the connection is forwarded by a local agent (called the kube proxy) running on the source machine, to one of the corresponding back-end containers. The exact back-end is chosen using a round-robin policy to balance load. The kube proxy takes care of tracking the dynamic set of back-ends as pods are replaced by new pods on new hosts, so that the service IP address (and DNS name) never changes.
-
-Every resource in Kubernetes, such as a pod, is identified by a URI and has a UID. Important components of the URI are the kind of object (e.g. pod), the object's name, and the object's [namespace](/{{page.version}}/docs/user-guide/namespaces). For a certain object kind, every name is unique within its namespace. In contexts where an object name is provided without a namespace, it is assumed to be in the default namespace. UID is unique across time and space.
-
-
-
diff --git a/v1.1/docs/user-guide/persistent-volumes.md b/v1.1/docs/user-guide/persistent-volumes.md
deleted file mode 100644
index 73c75ee105..0000000000
--- a/v1.1/docs/user-guide/persistent-volumes.md
+++ /dev/null
@@ -1,171 +0,0 @@
----
----
-
-This document describes the current state of `PersistentVolumes` in Kubernetes.  Familiarity with [volumes](/{{page.version}}/docs/user-guide/volumes) is suggested.
-
-* TOC
-{:toc}
-
-## Introduction
-
-Managing storage is a distinct problem from managing compute. The `PersistentVolume` subsystem provides an API for users and administrators that abstracts details of how storage is provided from how it is consumed.  To do this we introduce two new API resources:  `PersistentVolume` and `PersistentVolumeClaim`.
-
-A `PersistentVolume` (PV) is a piece of networked storage in the cluster that has been provisioned by an administrator.  It is a resource in the cluster just like a node is a cluster resource.   PVs are volume plugins like Volumes, but have a lifecycle independent of any individual pod that uses the PV.  This API object captures the details of the implementation of the storage, be that NFS, iSCSI, or a cloud-provider-specific storage system.
-
-A `PersistentVolumeClaim` (PVC) is a request for storage by a user.  It is similar to a pod.  Pods consume node resources and PVCs consume PV resources.  Pods can request specific levels of resources (CPU and Memory).  Claims can request specific size and access modes (e.g, can be mounted once read/write or many times read-only).
-
-Please see the [detailed walkthrough with working examples](/{{page.version}}/docs/user-guide/persistent-volumes/).
-
-
-## Lifecycle of a volume and claim
-
-PVs are resources in the cluster.  PVCs are requests for those resources and also act as claim checks to the resource.  The interaction between PVs and PVCs follows this lifecycle:
-
-### Provisioning
-
-A cluster administrator will create a number of PVs. They carry the details of the real storage which is available for use by cluster users.  They exist in the Kubernetes API and are available for consumption.
-
-### Binding
-
-A user creates a `PersistentVolumeClaim` with a specific amount of storage requested and with certain access modes.  A control loop in the master watches for new PVCs, finds a matching PV (if possible), and binds them together.  The user will always get at least what they asked for, but the volume may be in excess of what was requested.
-
-Claims will remain unbound indefinitely if a matching volume does not exist.  Claims will be bound as matching volumes become available.  For example, a cluster provisioned with many 50Gi PVs would not match a PVC requesting 100Gi.  The PVC can be bound when a 100Gi PV is added to the cluster.
-
-### Using
-
-Pods use claims as volumes. The cluster inspects the claim to find the bound volume and mounts that volume for a pod.  For volumes which support multiple access modes, the user specifies which mode desired when using their claim as a volume in a pod.
-
-Once a user has a claim and that claim is bound, the bound PV belongs to the user for as long as they need it. Users schedule Pods and access their claimed PVs by including a persistentVolumeClaim in their Pod's volumes block. [See below for syntax details](#claims-as-volumes).
-
-### Releasing
-
-When a user is done with their volume, they can delete the PVC objects from the API which allows reclamation of the resource.  The volume is considered "released" when the claim is deleted, but it is not yet available for another claim.  The previous claimant's data remains on the volume which must be handled according to policy.
-
-### Reclaiming
-
-The reclaim policy for a `PersistentVolume` tells the cluster what to do with the volume after it has been released.  Currently, volumes can either be Retained or Recycled.  Retention allows for manual reclamation of the resource.  For those volume plugins that support it, recycling performs a basic scrub (`rm -rf /thevolume/*`) on the volume and makes it available again for a new claim.
-
-## Types of Persistent Volumes
-
-`PersistentVolume` types are implemented as plugins.  Kubernetes currently supports the following plugins:
-
-* GCEPersistentDisk
-* AWSElasticBlockStore
-* NFS
-* iSCSI
-* RBD (Ceph Block Device)
-* Glusterfs
-* HostPath (single node testing only -- local storage is not supported in any way and WILL NOT WORK in a multi-node cluster)
-
-
-## Persistent Volumes
-
-Each PV contains a spec and status, which is the specification and status of the volume.
-
-```yaml
-apiVersion: v1
-  kind: PersistentVolume
-  metadata:
-    name: pv0003
-  spec:
-    capacity:
-      storage: 5Gi
-    accessModes:
-      - ReadWriteOnce
-    persistentVolumeReclaimPolicy: Recycle
-    nfs:
-      path: /tmp
-      server: 172.17.0.2
-```
-
-### Capacity
-
-Generally, a PV will have a specific storage capacity.  This is set using the PV's `capacity` attribute.  See the Kubernetes [Resource Model](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/resources.md) to understand the units expected by `capacity`.
-
-Currently, storage size is the only resource that can be set or requested.  Future attributes may include IOPS, throughput, etc.
-
-### Access Modes
-
-A `PersistentVolume` can be mounted on a host in any way supported by the resource provider.  Providers will have different capabilities and each PV's access modes are set to the specific modes supported by that particular volume.  For example, NFS can support multiple read/write clients, but a specific NFS PV might be exported on the server as read-only.  Each PV gets its own set of access modes describing that specific PV's capabilities.
-
-The access modes are:
-
-* ReadWriteOnce -- the volume can be mounted as read-write by a single node
-* ReadOnlyMany -- the volume can be mounted read-only by many nodes
-* ReadWriteMany -- the volume can be mounted as read-write by many nodes
-
-In the CLI, the access modes are abbreviated to:
-
-* RWO - ReadWriteOnce
-* ROX - ReadOnlyMany
-* RWX - ReadWriteMany
-
-> __Important!__ A volume can only be mounted using one access mode at a time, even if it supports many.  For example, a GCEPersistentDisk can be mounted as ReadWriteOnce by a single node or ReadOnlyMany by many nodes, but not at the same time.
-
-
-### Recycling Policy
-
-Current recycling policies are:
-
-* Retain -- manual reclamation
-* Recycle -- basic scrub ("rm -rf /thevolume/*")
-
-Currently, NFS and HostPath support recycling.
-
-### Phase
-
-A volume will be in one of the following phases:
-
-* Available -- a free resource that is not yet bound to a claim
-* Bound -- the volume is bound to a claim
-* Released -- the claim has been deleted, but the resource is not yet reclaimed by the cluster
-* Failed -- the volume has failed its automatic reclamation
-
-The CLI will show the name of the PVC bound to the PV.
-
-## PersistentVolumeClaims
-
-Each PVC contains a spec and status, which is the specification and status of the claim.
-
-```yaml
-kind: PersistentVolumeClaim
-apiVersion: v1
-metadata:
-  name: myclaim
-spec:
-  accessModes:
-    - ReadWriteOnce
-  resources:
-    requests:
-      storage: 8Gi
-```
-
-### Access Modes
-
-Claims use the same conventions as volumes when requesting storage with specific access modes.
-
-### Resources
-
-Claims, like pods, can request specific quantities of a resource.  In this case, the request is for storage.  The same [resource model](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/resources.md) applies to both volumes and claims.
-
-## Claims As Volumes
-
-Pods access storage by using the claim as a volume.  Claims must exist in the same namespace as the pod using the claim.  The cluster finds the claim in the pod's namespace and uses it to get the `PersistentVolume` backing the claim.  The volume is then mounted to the host and into the pod.
-
-```yaml
-kind: Pod
-apiVersion: v1
-metadata:
-  name: mypod
-spec:
-  containers:
-    - name: myfrontend
-      image: dockerfile/nginx
-      volumeMounts:
-      - mountPath: "/var/www/html"
-        name: mypd
-  volumes:
-    - name: mypd
-      persistentVolumeClaim:
-        claimName: myclaim
-```
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/quick-start.md b/v1.1/docs/user-guide/quick-start.md
deleted file mode 100644
index fd0c12a35d..0000000000
--- a/v1.1/docs/user-guide/quick-start.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
----
-
-This guide will help you get oriented to Kubernetes and running your first containers on the cluster. If you are already familiar with the docker-cli, you can also checkout the docker-cli to kubectl migration guide [here](/{{page.version}}/docs/user-guide/docker-cli-to-kubectl).
-
-* TOC
-{:toc}
-
-## Launching a simple application
-
-Once your application is packaged into a container and pushed to an image registry, you're ready to deploy it to Kubernetes.
-
-For example, [nginx](http://wiki.nginx.org/Main) is a popular HTTP server, with a [pre-built container on Docker hub](https://registry.hub.docker.com/_/nginx/). The [`kubectl run`](/{{page.version}}/docs/user-guide/kubectl/kubectl_run) command below will create two nginx replicas, listening on port 80.
-
-```shell
-$ kubectl run my-nginx --image=nginx --replicas=2 --port=80
-CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR       REPLICAS
-my-nginx     my-nginx       nginx      run=my-nginx   2
-```
-
-You can see that they are running by:
-
-```shell
-$ kubectl get po
-NAME             READY     STATUS    RESTARTS   AGE
-my-nginx-l8n3i   1/1       Running   0          29m
-my-nginx-q7jo3   1/1       Running   0          29m
-```
-
-Kubernetes will ensure that your application keeps running, by automatically restarting containers that fail, spreading containers across nodes, and recreating containers on new nodes when nodes fail.
-
-## Exposing your application to the Internet
-
-Through integration with some cloud providers (for example Google Compute Engine and AWS EC2), Kubernetes enables you to request that it provision a public IP address for your application. To do this run:
-
-```shell
-$ kubectl expose rc my-nginx --port=80 --type=LoadBalancer
-service "my-nginx" exposed
-```
-
-To find the public IP address assigned to your application, execute:
-
-```shell
-$ kubectl get svc my-nginx
-NAME         CLUSTER_IP       EXTERNAL_IP       PORT(S)                SELECTOR     AGE
-my-nginx     10.179.240.1     25.1.2.3          80/TCP                 run=nginx    8d
-```
-
-You may need to wait for a minute or two for the external ip address to be provisioned.
-
-In order to access your nginx landing page, you also have to make sure that traffic from external IPs is allowed. Do this by opening a [firewall to allow traffic on port 80](/{{page.version}}/docs/user-guide/services-firewalls).
-
-## Killing the application
-
-To kill the application and delete its containers and public IP address, do:
-
-```shell
-$ kubectl delete rc my-nginx
-replicationcontrollers/my-nginx
-$ kubectl delete svc my-nginx
-services/my-nginx
-```
-
-## What's next?
-
-[Learn about how to configure common container parameters, such as commands and environment variables.](/{{page.version}}/docs/user-guide/configuring-containers)
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/replication-controller.md b/v1.1/docs/user-guide/replication-controller.md
deleted file mode 100644
index 9e4c053b9a..0000000000
--- a/v1.1/docs/user-guide/replication-controller.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## What is a _replication controller_?
-
-A _replication controller_ ensures that a specified number of pod "replicas" are running at any one time.  If there are too many, it will kill some.  If there are too few, it will start more. Unlike in the case where a user directly created pods, a replication controller replaces pods that are deleted or terminated for any reason, such as in the case of node failure or disruptive node maintenance, such as a kernel upgrade. For this reason, we recommend that you use a replication controller even if your application requires only a single pod. Think of it similarly to a process supervisor, only it supervises multiple pods across multiple nodes instead of individual processes on a single node.  A replication controller delegates local container restarts to some agent on the node (e.g., Kubelet or Docker).
-
-As discussed in [life of a pod](/{{page.version}}/docs/user-guide/pod-states), `ReplicationController` is *only* appropriate for pods with `RestartPolicy = Always`. (Note: If `RestartPolicy` is not set, the default value is `Always`.)  `ReplicationController` should refuse to instantiate any pod that has a different restart policy. As discussed in [issue #503](http://issue.k8s.io/503#issuecomment-50169443), we expect other types of controllers to be added to Kubernetes to handle other types of workloads, such as build/test and batch workloads, in the future.
-
-A replication controller will never terminate on its own, but it isn't expected to be as long-lived as services. Services may be composed of pods controlled by multiple replication controllers, and it is expected that many replication controllers may be created and destroyed over the lifetime of a service (for instance, to perform an update of pods that run the service). Both services themselves and their clients should remain oblivious to the replication controllers that maintain the pods of the services.
-
-## How does a replication controller work?
-
-### Pod template
-
-A replication controller creates new pods from a template, which is currently inline in the `ReplicationController` object, but which we plan to extract into its own resource [#170](http://issue.k8s.io/170).
-
-Rather than specifying the current desired state of all replicas, pod templates are like cookie cutters. Once a cookie has been cut, the cookie has no relationship to the cutter. There is no quantum entanglement. Subsequent changes to the template or even switching to a new template has no direct effect on the pods already created. Similarly, pods created by a replication controller may subsequently be updated directly. This is in deliberate contrast to pods, which do specify the current desired state of all containers belonging to the pod. This approach radically simplifies system semantics and increases the flexibility of the primitive, as demonstrated by the use cases explained below.
-
-Pods created by a replication controller are intended to be fungible and semantically identical, though their configurations may become heterogeneous over time. This is an obvious fit for replicated stateless servers, but replication controllers can also be used to maintain availability of master-elected, sharded, and worker-pool applications. Such applications should use dynamic work assignment mechanisms, such as the [etcd lock module](https://coreos.com/docs/distributed-configuration/etcd-modules/) or [RabbitMQ work queues](https://www.rabbitmq.com/tutorials/tutorial-two-python), as opposed to static/one-time customization of the configuration of each pod, which is considered an anti-pattern. Any pod customization performed, such as vertical auto-sizing of resources (e.g., cpu or memory), should be performed by another online controller process, not unlike the replication controller itself.
-
-### Labels
-
-The population of pods that a replication controller is monitoring is defined with a [label selector](/{{page.version}}/docs/user-guide/labels/#label-selectors), which creates a loosely coupled relationship between the controller and the pods controlled, in contrast to pods, which are more tightly coupled to their definition. We deliberately chose not to represent the set of pods controlled using a fixed-length array of pod specifications, because our experience is that approach increases complexity of management operations, for both clients and the system.
-
-The replication controller should verify that the pods created from the specified template have labels that match its label selector. Though it isn't verified yet, you should also ensure that only one replication controller controls any given pod, by ensuring that the label selectors of replication controllers do not target overlapping sets. If you do end up with multiple controllers that have overlapping selectors, you will have to manage the deletion yourself with --cascade=false until there are no controllers with an overlapping superset of selectors.
-
-Note that replication controllers may themselves have labels and would generally carry the labels their corresponding pods have in common, but these labels do not affect the behavior of the replication controllers.
-
-Pods may be removed from a replication controller's target set by changing their labels. This technique may be used to remove pods from service for debugging, data recovery, etc. Pods that are removed in this way will be replaced automatically (assuming that the number of replicas is not also changed).
-
-Similarly, deleting a replication controller using the API does not affect the pods it created. Its `replicas` field must first be set to `0` in order to delete the pods controlled. (Note that the client tool, `kubectl`, provides a single operation, [delete](/{{page.version}}/docs/user-guide/kubectl/kubectl_delete) to delete both the replication controller and the pods it controls. If you want to leave the pods running when deleting a replication controller, specify `--cascade=false`. However, there is no such operation in the API at the moment)
-
-## Responsibilities of the replication controller
-
-The replication controller simply ensures that the desired number of pods matches its label selector and are operational. Currently, only terminated pods are excluded from its count. In the future, [readiness](http://issue.k8s.io/620) and other information available from the system may be taken into account, we may add more controls over the replacement policy, and we plan to emit events that could be used by external clients to implement arbitrarily sophisticated replacement and/or scale-down policies.
-
-The replication controller is forever constrained to this narrow responsibility. It itself will not perform readiness nor liveness probes. Rather than performing auto-scaling, it is intended to be controlled by an external auto-scaler (as discussed in [#492](http://issue.k8s.io/492)), which would change its `replicas` field. We will not add scheduling policies (e.g., [spreading](http://issue.k8s.io/367#issuecomment-48428019)) to the replication controller. Nor should it verify that the pods controlled match the currently specified template, as that would obstruct auto-sizing and other automated processes. Similarly, completion deadlines, ordering dependencies, configuration expansion, and other features belong elsewhere. We even plan to factor out the mechanism for bulk pod creation ([#170](http://issue.k8s.io/170)).
-
-The replication controller is intended to be a composable building-block primitive. We expect higher-level APIs and/or tools to be built on top of it and other complementary primitives for user convenience in the future. The "macro" operations currently supported by kubectl (run, stop, scale, rolling-update) are proof-of-concept examples of this. For instance, we could imagine something like [Spinnaker] (http://spinnaker.io/) managing replication controllers, auto-scalers, services, scheduling policies, canaries, etc.
-
-## Common usage patterns
-
-### Rescheduling
-
-As mentioned above, whether you have 1 pod you want to keep running, or 1000, a replication controller will ensure that the specified number of pods exists, even in the event of node failure or pod termination (e.g., due to an action by another control agent).
-
-### Scaling
-
-The replication controller makes it easy to scale the number of replicas up or down, either manually or by an auto-scaling control agent, by simply updating the `replicas` field.
-
-### Rolling updates
-
-The replication controller is designed to facilitate rolling updates to a service by replacing pods one-by-one.
-
-As explained in [#1353](http://issue.k8s.io/1353), the recommended approach is to create a new replication controller with 1 replica, scale the new (+1) and old (-1) controllers one by one, and then delete the old controller after it reaches 0 replicas. This predictably updates the set of pods regardless of unexpected failures.
-
-Ideally, the rolling update controller would take application readiness into account, and would ensure that a sufficient number of pods were productively serving at any given time.
-
-The two replication controllers would need to create pods with at least one differentiating label, such as the image tag of the primary container of the pod, since it is typically image updates that motivate rolling updates.
-
-Rolling update is implemented in the client tool
-[kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update)
-
-### Multiple release tracks
-
-In addition to running multiple releases of an application while a rolling update is in progress, it's common to run multiple releases for an extended period of time, or even continuously, using multiple release tracks. The tracks would be differentiated by labels.
-
-For instance, a service might target all pods with `tier in (frontend), environment in (prod)`.  Now say you have 10 replicated pods that make up this tier.  But you want to be able to 'canary' a new version of this component.  You could set up a replication controller with `replicas` set to 9 for the bulk of the replicas, with labels `tier=frontend, environment=prod, track=stable`, and another replication controller with `replicas` set to 1 for the canary, with labels `tier=frontend, environment=prod, track=canary`.  Now the service is covering both the canary and non-canary pods.  But you can mess with the replication controllers separately to test things out, monitor the results, etc.
-
-## API Object
-
-Replication controller is a top-level resource in the kubernetes REST API. More details about the
-API object can be found at: [ReplicationController API
-object](http://kubernetes.io/v1.1/docs/api-reference/v1/definitions/#_v1_replicationcontroller).
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/resourcequota/index.md b/v1.1/docs/user-guide/resourcequota/index.md
deleted file mode 100644
index e2de1b99b0..0000000000
--- a/v1.1/docs/user-guide/resourcequota/index.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
----
-
-This page has been moved to [here](/{{page.version}}/docs/admin/resourcequota/)
-
-
diff --git a/v1.1/docs/user-guide/secrets.md b/v1.1/docs/user-guide/secrets.md
deleted file mode 100644
index fa6de0b769..0000000000
--- a/v1.1/docs/user-guide/secrets.md
+++ /dev/null
@@ -1,491 +0,0 @@
----
----
-
-Objects of type `secret` are intended to hold sensitive information, such as
-passwords, OAuth tokens, and ssh keys.  Putting this information in a `secret`
-is safer and more flexible than putting it verbatim in a `pod` definition or in
-a docker image. See [Secrets design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/secrets.md) for more information.
-
-* TOC
-{:toc}
-
-## Overview of Secrets
-
-A Secret is an object that contains a small amount of sensitive data such as
-a password, a token, or a key.  Such information might otherwise be put in a
-Pod specification or in an image; putting it in a Secret object allows for
-more control over how it is used, and reduces the risk of accidental exposure.
-
-Users can create secrets, and the system also creates some secrets.
-
-To use a secret, a pod needs to reference the secret.
-A secret can be used with a pod in two ways: either as files in a [volume](/{{page.version}}/docs/user-guide/volumes) mounted on one or more of
-its containers, or used by kubelet when pulling images for the pod.
-
-### Service Accounts Automatically Create and Attach Secrets with API Credentials
-
-Kubernetes automatically creates secrets which contain credentials for
-accessing the API and it automatically modifies your pods to use this type of
-secret.
-
-The automatic creation and use of API credentials can be disabled or overridden
-if desired.  However, if all you need to do is securely access the apiserver,
-this is the recommended workflow.
-
-See the [Service Account](/{{page.version}}/docs/user-guide/service-accounts) documentation for more
-information on how Service Accounts work.
-
-### Creating a Secret Manually
-
-This is an example of a simple secret, in yaml format:
-
-```yaml
-apiVersion: v1
-kind: Secret
-metadata:
-  name: mysecret
-type: Opaque
-data:
-  password: dmFsdWUtMg0K
-  username: dmFsdWUtMQ0K
-```
-
-The data field is a map.  Its keys must match
-[`DNS_SUBDOMAIN`](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/identifiers.md), except that leading dots are also
-allowed.  The values are arbitrary data, encoded using base64. The values of
-username and password in the example above, before base64 encoding,
-are `value-1` and `value-2`, respectively, with carriage return and newline characters at the end.
-
-Create the secret using [`kubectl create`](/{{page.version}}/docs/user-guide/kubectl/kubectl_create).
-
-Once the secret is created, you can need to modify your pod to specify
-that it should use the secret.
-
-### Manually specifying a Secret to be Mounted on a Pod
-
-This is an example of a pod that mounts a secret in a volume:
-
-```json
-{
- "apiVersion": "v1",
- "kind": "Pod",
-  "metadata": {
-    "name": "mypod",
-    "namespace": "myns"
-  },
-  "spec": {
-    "containers": [{
-      "name": "mypod",
-      "image": "redis",
-      "volumeMounts": [{
-        "name": "foo",
-        "mountPath": "/etc/foo",
-        "readOnly": true
-      }]
-    }],
-    "volumes": [{
-      "name": "foo",
-      "secret": {
-        "secretName": "mysecret"
-      }
-    }]
-  }
-}
-```
-
-Each secret you want to use needs its own `spec.volumes`.
-
-If there are multiple containers in the pod, then each container needs its
-own `volumeMounts` block, but only one `spec.volumes` is needed per secret.
-
-You can package many files into one secret, or use many secrets,
-whichever is convenient.
-
-See another example of creating a secret and a pod that consumes that secret in a volume [here](/{{page.version}}/docs/user-guide/secrets/).
-
-### Manually specifying an imagePullSecret
-
-Use of imagePullSecrets is described in the [images documentation](/{{page.version}}/docs/user-guide/images/#specifying-imagepullsecrets-on-a-pod)
-
-### Arranging for imagePullSecrets to be Automatically Attached
-
-You can manually create an imagePullSecret, and reference it from
-a serviceAccount.  Any pods created with that serviceAccount
-or that default to use that serviceAccount, will get have the imagePullSecret of the
-field set to that of the service account.
-See [here](/{{page.version}}/docs/user-guide/service-accounts/#adding-imagepullsecrets-to-a-service-account)
- for a detailed explanation of that process.
-
-
-### Automatic Mounting of Manually Created Secrets
-
-We plan to extend the service account behavior so that manually created
-secrets (e.g. one containing a token for accessing a github account)
-can be automatically attached to pods based on their service account.
-*This is not implemented yet.  See [issue 9902](http://issue.k8s.io/9902).*
-
-## Details
-
-### Restrictions
-
-Secret volume sources are validated to ensure that the specified object
-reference actually points to an object of type `Secret`.  Therefore, a secret
-needs to be created before any pods that depend on it.
-
-Secret API objects reside in a namespace.   They can only be referenced by pods
-in that same namespace.
-
-Individual secrets are limited to 1MB in size.  This is to discourage creation
-of very large secrets which would exhaust apiserver and kubelet memory.
-However, creation of many smaller secrets could also exhaust memory.  More
-comprehensive limits on memory usage due to secrets is a planned feature.
-
-Kubelet only supports use of secrets for Pods it gets from the API server.
-This includes any pods created using kubectl, or indirectly via a replication
-controller.  It does not include pods created via the kubelets
-`--manifest-url` flag, its `--config` flag, or its REST API (these are
-not common ways to create pods.)
-
-### Consuming Secret Values
-
-Inside the container that mounts a secret volume, the secret keys appear as
-files and the secret values are base-64 decoded and stored inside these files.
-This is the result of commands
-executed inside the container from the example above:
-
-```shell
-$ ls /etc/foo/
-username
-password
-$ cat /etc/foo/username
-value-1
-$ cat /etc/foo/password
-value-2
-```
-
-The program in a container is responsible for reading the secret(s) from the
-files.  Currently, if a program expects a secret to be stored in an environment
-variable, then the user needs to modify the image to populate the environment
-variable from the file as an step before running the main program.  Future
-versions of Kubernetes are expected to provide more automation for populating
-environment variables from files.
-
-
-### Secret and Pod Lifetime interaction
-
-When a pod is created via the API, there is no check whether a referenced
-secret exists.  Once a pod is scheduled, the kubelet will try to fetch the
-secret value.  If the secret cannot be fetched because it does not exist or
-because of a temporary lack of connection to the API server, kubelet will
-periodically retry.  It will report an event about the pod explaining the
-reason it is not started yet.  Once the a secret is fetched, the kubelet will
-create and mount a volume containing it.  None of the pod's containers will
-start until all the pod's volumes are mounted.
-
-Once the kubelet has started a pod's containers, its secret volumes will not
-change, even if the secret resource is modified.  To change the secret used,
-the original pod must be deleted, and a new pod (perhaps with an identical
-`PodSpec`) must be created.  Therefore, updating a secret follows the same
-workflow as deploying a new container image.  The `kubectl rolling-update`
-command can be used ([man page](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update)).
-
-The [`resourceVersion`](/{{page.version}}/docs/devel/api-conventions/#concurrency-control-and-consistency)
-of the secret is not specified when it is referenced.
-Therefore, if a secret is updated at about the same time as pods are starting,
-then it is not defined which version of the secret will be used for the pod. It
-is not possible currently to check what resource version of a secret object was
-used when a pod was created.  It is planned that pods will report this
-information, so that a replication controller restarts ones using an old
-`resourceVersion`.  In the interim, if this is a concern, it is recommended to not
-update the data of existing secrets, but to create new ones with distinct names.
-
-## Use cases
-
-### Use-Case: Pod with ssh keys
-
-To create a pod that uses an ssh key stored as a secret, we first need to create a secret:
-
-```json
-{
-  "kind": "Secret",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "ssh-key-secret"
-  },
-  "data": {
-    "id-rsa": "dmFsdWUtMg0KDQo=",
-    "id-rsa.pub": "dmFsdWUtMQ0K"
-  }
-}
-```
-
-**Note:** The serialized JSON and YAML values of secret data are encoded as
-base64 strings.  Newlines are not valid within these strings and must be
-omitted.
-
-Now we can create a pod which references the secret with the ssh key and
-consumes it in a volume:
-
-```json
-{
-  "kind": "Pod",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "secret-test-pod",
-    "labels": {
-      "name": "secret-test"
-    }
-  },
-  "spec": {
-    "volumes": [
-      {
-        "name": "secret-volume",
-        "secret": {
-          "secretName": "ssh-key-secret"
-        }
-      }
-    ],
-    "containers": [
-      {
-        "name": "ssh-test-container",
-        "image": "mySshImage",
-        "volumeMounts": [
-          {
-            "name": "secret-volume",
-            "readOnly": true,
-            "mountPath": "/etc/secret-volume"
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-When the container's command runs, the pieces of the key will be available in:
-
-```shell
-/etc/secret-volume/id-rsa.pub
-/etc/secret-volume/id-rsa
-```
-
-The container is then free to use the secret data to establish an ssh connection.
-
-### Use-Case: Pods with prod / test credentials
-
-This example illustrates a pod which consumes a secret containing prod
-credentials and another pod which consumes a secret with test environment
-credentials.
-
-The secrets:
-
-```json
-{
-  "apiVersion": "v1",
-  "kind": "List",
-  "items":
-  [{
-    "kind": "Secret",
-    "apiVersion": "v1",
-    "metadata": {
-      "name": "prod-db-secret"
-    },
-    "data": {
-      "password": "dmFsdWUtMg0KDQo=",
-      "username": "dmFsdWUtMQ0K"
-    }
-  },
-  {
-    "kind": "Secret",
-    "apiVersion": "v1",
-    "metadata": {
-      "name": "test-db-secret"
-    },
-    "data": {
-      "password": "dmFsdWUtMg0KDQo=",
-      "username": "dmFsdWUtMQ0K"
-    }
-  }]
-}
-```
-
-The pods:
-
-```json
-{
-  "apiVersion": "v1",
-  "kind": "List",
-  "items":
-  [{
-    "kind": "Pod",
-    "apiVersion": "v1",
-    "metadata": {
-      "name": "prod-db-client-pod",
-      "labels": {
-        "name": "prod-db-client"
-      }
-    },
-    "spec": {
-      "volumes": [
-        {
-          "name": "secret-volume",
-          "secret": {
-            "secretName": "prod-db-secret"
-          }
-        }
-      ],
-      "containers": [
-        {
-          "name": "db-client-container",
-          "image": "myClientImage",
-          "volumeMounts": [
-            {
-              "name": "secret-volume",
-              "readOnly": true,
-              "mountPath": "/etc/secret-volume"
-            }
-          ]
-        }
-      ]
-    }
-  },
-  {
-    "kind": "Pod",
-    "apiVersion": "v1",
-    "metadata": {
-      "name": "test-db-client-pod",
-      "labels": {
-        "name": "test-db-client"
-      }
-    },
-    "spec": {
-      "volumes": [
-        {
-          "name": "secret-volume",
-          "secret": {
-            "secretName": "test-db-secret"
-          }
-        }
-      ],
-      "containers": [
-        {
-          "name": "db-client-container",
-          "image": "myClientImage",
-          "volumeMounts": [
-            {
-              "name": "secret-volume",
-              "readOnly": true,
-              "mountPath": "/etc/secret-volume"
-            }
-          ]
-        }
-      ]
-    }
-  }]
-}
-```
-
-Both containers will have the following files present on their filesystems:
-
-```shell
-/etc/secret-volume/username
-/etc/secret-volume/password
-```
-
-Note how the specs for the two pods differ only in one field;  this facilitates
-creating pods with different capabilities from a common pod config template.
-
-You could further simplify the base pod specification by using two Service Accounts:
-one called, say, `prod-user` with the `prod-db-secret`, and one called, say,
-`test-user` with the `test-db-secret`.  Then, the pod spec can be shortened to, for example:
-
-```json
-{
-"kind": "Pod",
-"apiVersion": "v1",
-"metadata": {
-  "name": "prod-db-client-pod",
-  "labels": {
-    "name": "prod-db-client"
-  }
-},
-"spec": {
-  "serviceAccount": "prod-db-client",
-  "containers": [
-    {
-      "name": "db-client-container",
-      "image": "myClientImage",
-    }
-  ]
-}
-```
-
-### Use-case: Secret visible to one container in a pod
-
-<a name="use-case-two-containers"></a>
-
-Consider a program that needs to handle HTTP requests, do some complex business
-logic, and then sign some messages with an HMAC.  Because it has complex
-application logic, there might be an unnoticed remote file reading exploit in
-the server, which could expose the private key to an attacker.
-
-This could be divided into two processes in two containers: a frontend container
-which handles user interaction and business logic, but which cannot see the
-private key; and a signer container that can see the private key, and responds
-to simple signing requests from the frontend (e.g. over localhost networking).
-
-With this partitioned approach, an attacker now has to trick the application
-server into doing something rather arbitrary, which may be harder than getting
-it to read a file.
-
-<!-- TODO: explain how to do this while still using automation. -->
-
-## Security Properties
-
-### Protections
-
-Because `secret` objects can be created independently of the `pods` that use
-them, there is less risk of the secret being exposed during the workflow of
-creating, viewing, and editing pods.  The system can also take additional
-precautions with `secret` objects, such as avoiding writing them to disk where
-possible.
-
-A secret is only sent to a node if a pod on that node requires it.  It is not
-written to disk.  It is stored in a tmpfs.  It is deleted once the pod that
-depends on it is deleted.
-
-On most Kubernetes-project-maintained distributions, communication between user
-to the apiserver, and from apiserver to the kubelets, is protected by SSL/TLS.
-Secrets are protected when transmitted over these channels.
-
-Secret data on nodes is stored in tmpfs volumes and thus does not come to rest
-on the node.
-
-There may be secrets for several pods on the same node.  However, only the
-secrets that a pod requests are potentially visible within its containers.
-Therefore, one Pod does not have access to the secrets of another pod.
-
-There may be several containers in a pod.  However, each container in a pod has
-to request the secret volume in its `volumeMounts` for it to be visible within
-the container.  This can be used to construct useful [security partitions at the
-Pod level](#use-case-two-containers).
-
-### Risks
-
- - In the API server secret data is stored as plaintext in etcd; therefore:
-   - Administrators should limit access to etcd to admin users
-   - Secret data in the API server is at rest on the disk that etcd uses; admins may want to wipe/shred disks
-     used by etcd when no longer in use
- - Applications still need to protect the value of secret after reading it from the volume,
-   such as not accidentally logging it or transmitting it to an untrusted party.
- - A user who can create a pod that uses a secret can also see the value of that secret.  Even
-   if apiserver policy does not allow that user to read the secret object, the user could
-   run a pod which exposes the secret.
- - If multiple replicas of etcd are run, then the secrets will be shared between them.
-   By default, etcd does not secure peer-to-peer communication with SSL/TLS, though this can be configured.
- - It is not possible currently to control which users of a Kubernetes cluster can
-   access a secret.  Support for this is planned.
- - Currently, anyone with root on any node can read any secret from the apiserver,
-   by impersonating the kubelet.  It is a planned feature to only send secrets to
-   nodes that actually require them, to restrict the impact of a root exploit on a
-   single node.
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/service-accounts.md b/v1.1/docs/user-guide/service-accounts.md
deleted file mode 100644
index b36355bcda..0000000000
--- a/v1.1/docs/user-guide/service-accounts.md
+++ /dev/null
@@ -1,192 +0,0 @@
----
----
-
-A service account provides an identity for processes that run in a Pod.
-
-*This is a user introduction to Service Accounts.  See also the
-[Cluster Admin Guide to Service Accounts](/{{page.version}}/docs/admin/service-accounts-admin).*
-
-*Note: This document describes how service accounts behave in a cluster set up
-as recommended by the Kubernetes project.  Your cluster administrator may have
-customized the behavior in your cluster, in which case this documentation may
-not apply.*
-
-When you (a human) access the cluster (e.g. using `kubectl`), you are
-authenticated by the apiserver as a particular User Account (currently this is
-usually `admin`, unless your cluster administrator has customized your
-cluster).  Processes in containers inside pods can also contact the apiserver.
-When they do, they are authenticated as a particular Service Account (e.g.
-`default`).
-
-## Using the Default Service Account to access the API server.
-
-When you create a pod, you do not need to specify a service account.  It is
-automatically assigned the `default` service account of the same namespace.  If
-you get the raw json or yaml for a pod you have created (e.g. `kubectl get
-pods/podname -o yaml`), you can see the `spec.serviceAccount` field has been
-[automatically set](working-with-resources/#resources-are-automatically-modified).
-
-You can access the API using a proxy or with a client library, as described in
-[Accessing the Cluster](/{{page.version}}/docs/user-guide/accessing-the-cluster/#accessing-the-api-from-a-pod).
-
-## Using Multiple Service Accounts.
-
-Every namespace has a default service account resource called `default`.
-You can list this and any other serviceAccount resources in the namespace with this command:
-
-```shell
-$ kubectl get serviceAccounts
-NAME      SECRETS
-default   1
-```
-
-You can create additional serviceAccounts like this:
-
-```shell
-$ cat > /tmp/serviceaccount.yaml <<EOF
-apiVersion: v1
-kind: ServiceAccount
-metadata:
-  name: build-robot
-EOF
-$ kubectl create -f /tmp/serviceaccount.yaml
-serviceaccounts/build-robot
-```
-
-If you get a complete dump of the service account object, like this:
-
-```shell
-$ kubectl get serviceaccounts/build-robot -o yaml
-apiVersion: v1
-kind: ServiceAccount
-metadata:
-  creationTimestamp: 2015-06-16T00:12:59Z
-  name: build-robot
-  namespace: default
-  resourceVersion: "272500"
-  selfLink: /api/v1/namespaces/default/serviceaccounts/build-robot
-  uid: 721ab723-13bc-11e5-aec2-42010af0021e
-secrets:
-- name: build-robot-token-bvbk5
-```
-
-then you will see that a token has automatically been created and is referenced by the service account.
-
-In the future, you will be able to configure different access policies for each service account.
-
-To use a non-default service account, simply set the `spec.serviceAccount`
-field of a pod to the name of the service account you wish to use.
-
-The service account has to exist at the time the pod is created, or it will be rejected.
-
-You cannot update the service account of an already created pod.
-
-You can clean up the service account from this example like this:
-
-```shell
-$ kubectl delete serviceaccount/build-robot
-```
-
-<!-- TODO: describe how to create a pod with no Service Account. -->
-Note that if a pod does not have a `ServiceAccount` set, the `ServiceAccount` will be set to `default`.
-
-## Manually create a service account API token.
-
-Suppose we have an existing service account named "build-robot" as mentioned above, and we create
-a new secret manually.
-
-```shell
-$ cat > /tmp/build-robot-secret.yaml <<EOF
-apiVersion: v1
-kind: Secret
-metadata:
-  name: build-robot-secret
-  annotations: 
-    kubernetes.io/service-account.name: build-robot
-type: kubernetes.io/service-account-token
-EOF
-$ kubectl create -f /tmp/build-robot-secret.yaml
-secrets/build-robot-secret
-```
-
-Now you can confirm that the newly built secret is populated with an API token for the "build-robot" service account.
-
-```shell
-$ kubectl describe secrets/build-robot-secret 
-Name:   build-robot-secret
-Namespace:  default
-Labels:   <none>
-Annotations:  kubernetes.io/service-account.name=build-robot,kubernetes.io/service-account.uid=870ef2a5-35cf-11e5-8d06-005056b45392
-
-Type: kubernetes.io/service-account-token
-
-Data
-====
-ca.crt: 1220 bytes
-token:  
-```
-
-> Note that the content of `token` is elided here.
-
-## Adding ImagePullSecrets to a service account
-
-First, create an imagePullSecret, as described [here](/{{page.version}}/docs/user-guide/images/#specifying-imagepullsecrets-on-a-pod)
-Next, verify it has been created.  For example:
-
-```shell
-$ kubectl get secrets myregistrykey
-NAME             TYPE                      DATA
-myregistrykey    kubernetes.io/dockercfg   1
-```
-
-Next, read/modify/write the service account for the namespace to use this secret as an imagePullSecret
-
-```shell
-$ kubectl get serviceaccounts default -o yaml > ./sa.yaml
-$ cat sa.yaml
-apiVersion: v1
-kind: ServiceAccount
-metadata:
-  creationTimestamp: 2015-08-07T22:02:39Z
-  name: default
-  namespace: default
-  resourceVersion: "243024"
-  selfLink: /api/v1/namespaces/default/serviceaccounts/default
-  uid: 052fb0f4-3d50-11e5-b066-42010af0d7b6
-secrets:
-- name: default-token-uudge
-$ vi sa.yaml
-[editor session not shown]
-[delete line with key "resourceVersion"]
-[add lines with "imagePullSecret:"]
-$ cat sa.yaml
-apiVersion: v1
-kind: ServiceAccount
-metadata:
-  creationTimestamp: 2015-08-07T22:02:39Z
-  name: default
-  namespace: default
-  selfLink: /api/v1/namespaces/default/serviceaccounts/default
-  uid: 052fb0f4-3d50-11e5-b066-42010af0d7b6
-secrets:
-- name: default-token-uudge
-imagePullSecrets:
-- name: myregistrykey
-$ kubectl replace serviceaccount default -f ./sa.yaml
-serviceaccounts/default
-```
-
-Now, any new pods created in the current namespace will have this added to their spec:
-
-```yaml
-spec:
-  imagePullSecrets:
-  - name: myregistrykey
-```
-
-## Adding Secrets to a service account.
-
-TODO: Test and explain how to use additional non-K8s secrets with an existing service account.
-
-TODO explain:
-  - The token goes to: "/var/run/secrets/kubernetes.io/serviceaccount/$WHATFILENAME"
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/services.md b/v1.1/docs/user-guide/services.md
deleted file mode 100644
index abf509ae74..0000000000
--- a/v1.1/docs/user-guide/services.md
+++ /dev/null
@@ -1,531 +0,0 @@
----
----
-
-Kubernetes [`Pods`](/{{page.version}}/docs/user-guide/pods) are mortal. They are born and they die, and they
-are not resurrected.  [`ReplicationControllers`](/{{page.version}}/docs/user-guide/replication-controller) in
-particular create and destroy `Pods` dynamically (e.g. when scaling up or down
-or when doing [rolling updates](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update)).  While each `Pod` gets its own IP address, even
-those IP addresses cannot be relied upon to be stable over time. This leads to
-a problem: if some set of `Pods` (let's call them backends) provides
-functionality to other `Pods` (let's call them frontends) inside the Kubernetes
-cluster, how do those frontends find out and keep track of which backends are
-in that set?
-
-Enter `Services`.
-
-A Kubernetes `Service` is an abstraction which defines a logical set of `Pods`
-and a policy by which to access them - sometimes called a micro-service.  The
-set of `Pods` targeted by a `Service` is (usually) determined by a [`Label
-Selector`](/{{page.version}}/docs/user-guide/labels/#label-selectors) (see below for why you might want a
-`Service` without a selector).
-
-As an example, consider an image-processing backend which is running with 3
-replicas.  Those replicas are fungible - frontends do not care which backend
-they use.  While the actual `Pods` that compose the backend set may change, the
-frontend clients should not need to be aware of that or keep track of the list
-of backends themselves.  The `Service` abstraction enables this decoupling.
-
-For Kubernetes-native applications, Kubernetes offers a simple `Endpoints` API
-that is updated whenever the set of `Pods` in a `Service` changes.  For
-non-native applications, Kubernetes offers a virtual-IP-based bridge to Services
-which redirects to the backend `Pods`.
-
-* TOC
-{:toc}
-
-## Defining a service
-
-A `Service` in Kubernetes is a REST object, similar to a `Pod`.  Like all of the
-REST objects, a `Service` definition can be POSTed to the apiserver to create a
-new instance.  For example, suppose you have a set of `Pods` that each expose
-port 9376 and carry a label `"app=MyApp"`.
-
-```json
-{
-    "kind": "Service",
-    "apiVersion": "v1",
-    "metadata": {
-        "name": "my-service"
-    },
-    "spec": {
-        "selector": {
-            "app": "MyApp"
-        },
-        "ports": [
-            {
-                "protocol": "TCP",
-                "port": 80,
-                "targetPort": 9376
-            }
-        ]
-    }
-}
-```
-
-This specification will create a new `Service` object named "my-service" which
-targets TCP port 9376 on any `Pod` with the `"app=MyApp"` label.  This `Service`
-will also be assigned an IP address (sometimes called the "cluster IP"), which
-is used by the service proxies (see below).  The `Service`'s selector will be
-evaluated continuously and the results will be POSTed to an `Endpoints` object
-also named "my-service".
-
-Note that a `Service` can map an incoming port to any `targetPort`.  By default
-the `targetPort` will be set to the same value as the `port` field.  Perhaps
-more interesting is that `targetPort` can be a string, referring to the name of
-a port in the backend `Pods`.  The actual port number assigned to that name can
-be different in each backend `Pod`. This offers a lot of flexibility for
-deploying and evolving your `Services`.  For example, you can change the port
-number that pods expose in the next version of your backend software, without
-breaking clients.
-
-Kubernetes `Services` support `TCP` and `UDP` for protocols.  The default
-is `TCP`.
-
-### Services without selectors
-
-Services generally abstract access to Kubernetes `Pods`, but they can also
-abstract other kinds of backends.  For example:
-
-  * You want to have an external database cluster in production, but in test
-    you use your own databases.
-  * You want to point your service to a service in another
-    [`Namespace`](/{{page.version}}/docs/user-guide/namespaces) or on another cluster.
-  * You are migrating your workload to Kubernetes and some of your backends run
-    outside of Kubernetes.
-
-In any of these scenarios you can define a service without a selector:
-
-```json
-{
-    "kind": "Service",
-    "apiVersion": "v1",
-    "metadata": {
-        "name": "my-service"
-    },
-    "spec": {
-        "ports": [
-            {
-                "protocol": "TCP",
-                "port": 80,
-                "targetPort": 9376
-            }
-        ]
-    }
-}
-```
-
-Because this has no selector, the corresponding `Endpoints` object will not be
-created. You can manually map the service to your own specific endpoints:
-
-```json
-{
-    "kind": "Endpoints",
-    "apiVersion": "v1",
-    "metadata": {
-        "name": "my-service"
-    },
-    "subsets": [
-        {
-            "addresses": [
-                { "IP": "1.2.3.4" }
-            ],
-            "ports": [
-                { "port": 80 }
-            ]
-        }
-    ]
-}
-```
-
-NOTE: Endpoint IPs may not be loopback (127.0.0.0/8), link-local
-(169.254.0.0/16), or link-local multicast ((224.0.0.0/24).
-
-Accessing a `Service` without a selector works the same as if it had selector.
-The traffic will be routed to endpoints defined by the user (`1.2.3.4:80` in
-this example).
-
-## Virtual IPs and service proxies
-
-Every node in a Kubernetes cluster runs a `kube-proxy`.  This application
-watches the Kubernetes master for the addition and removal of `Service`
-and `Endpoints` objects. For each `Service` it opens a port (randomly chosen)
-on the local node.  Any connections made to that port will be proxied to one of
-the corresponding backend `Pods`.  Which backend to use is decided based on the
-`SessionAffinity` of the `Service`.  Lastly, it installs iptables rules which
-capture traffic to the `Service`'s cluster IP (which is virtual) and `Port` and
-redirects that traffic to the previously described port.
-
-The net result is that any traffic bound for the `Service` is proxied to an
-appropriate backend without the clients knowing anything about Kubernetes or
-`Services` or `Pods`.
-
-![Services overview diagram](/images/docs/services-overview.svg)
-
-By default, the choice of backend is round robin.  Client-IP based session affinity
-can be selected by setting `service.spec.sessionAffinity` to `"ClientIP"` (the
-default is `"None"`).
-
-As of Kubernetes 1.0, `Services` are a "layer 3" (TCP/UDP over IP) construct.  We do not
-yet have a concept of "layer 7" (HTTP) services.
-
-## Multi-Port Services
-
-Many `Services` need to expose more than one port.  For this case, Kubernetes
-supports multiple port definitions on a `Service` object.  When using multiple
-ports you must give all of your ports names, so that endpoints can be
-disambiguated.  For example:
-
-```json
-{
-    "kind": "Service",
-    "apiVersion": "v1",
-    "metadata": {
-        "name": "my-service"
-    },
-    "spec": {
-        "selector": {
-            "app": "MyApp"
-        },
-        "ports": [
-            {
-                "name": "http",
-                "protocol": "TCP",
-                "port": 80,
-                "targetPort": 9376
-            },
-            {
-                "name": "https",
-                "protocol": "TCP",
-                "port": 443,
-                "targetPort": 9377
-            }
-        ]
-    }
-}
-```
-
-## Choosing your own IP address
-
-You can specify your own cluster IP address as part of a `Service` creation
-request.  To do this, set the `spec.clusterIP` field. For example, if you
-already have an existing DNS entry that you wish to replace, or legacy systems
-that are configured for a specific IP address and difficult to re-configure.
-The IP address that a user chooses must be a valid IP address and within the
-`service-cluster-ip-range` CIDR range that is specified by flag to the API
-server.  If the IP address value is invalid, the apiserver returns a 422 HTTP
-status code to indicate that the value is invalid.
-
-### Why not use round-robin DNS?
-
-A question that pops up every now and then is why we do all this stuff with
-virtual IPs rather than just use standard round-robin DNS.  There are a few
-reasons:
-
-   * There is a long history of DNS libraries not respecting DNS TTLs and
-     caching the results of name lookups.
-   * Many apps do DNS lookups once and cache the results.
-   * Even if apps and libraries did proper re-resolution, the load of every
-     client re-resolving DNS over and over would be difficult to manage.
-
-We try to discourage users from doing things that hurt themselves.  That said,
-if enough people ask for this, we may implement it as an alternative.
-
-## Discovering services
-
-Kubernetes supports 2 primary modes of finding a `Service` - environment
-variables and DNS.
-
-### Environment variables
-
-When a `Pod` is run on a `Node`, the kubelet adds a set of environment variables
-for each active `Service`.  It supports both [Docker links
-compatible](https://docs.docker.com/userguide/dockerlinks/) variables (see
-[makeLinkVariables](http://releases.k8s.io/{{page.githubbranch}}/pkg/kubelet/envvars/envvars.go#L49))
-and simpler `{SVCNAME}_SERVICE_HOST` and `{SVCNAME}_SERVICE_PORT` variables,
-where the Service name is upper-cased and dashes are converted to underscores.
-
-For example, the Service `"redis-master"` which exposes TCP port 6379 and has been
-allocated cluster IP address 10.0.0.11 produces the following environment
-variables:
-
-```shell
-REDIS_MASTER_SERVICE_HOST=10.0.0.11
-REDIS_MASTER_SERVICE_PORT=6379
-REDIS_MASTER_PORT=tcp://10.0.0.11:6379
-REDIS_MASTER_PORT_6379_TCP=tcp://10.0.0.11:6379
-REDIS_MASTER_PORT_6379_TCP_PROTO=tcp
-REDIS_MASTER_PORT_6379_TCP_PORT=6379
-REDIS_MASTER_PORT_6379_TCP_ADDR=10.0.0.11
-```
-
-*This does imply an ordering requirement* - any `Service` that a `Pod` wants to
-access must be created before the `Pod` itself, or else the environment
-variables will not be populated.  DNS does not have this restriction.
-
-### DNS
-
-An optional (though strongly recommended) [cluster
-add-on](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/README.md) is a DNS server.  The
-DNS server watches the Kubernetes API for new `Services` and creates a set of
-DNS records for each.  If DNS has been enabled throughout the cluster then all
-`Pods` should be able to do name resolution of `Services` automatically.
-
-For example, if you have a `Service` called `"my-service"` in Kubernetes
-`Namespace` `"my-ns"` a DNS record for `"my-service.my-ns"` is created.  `Pods`
-which exist in the `"my-ns"` `Namespace` should be able to find it by simply doing
-a name lookup for `"my-service"`.  `Pods` which exist in other `Namespaces` must
-qualify the name as `"my-service.my-ns"`.  The result of these name lookups is the
-cluster IP.
-
-Kubernetes also supports DNS SRV (service) records for named ports.  If the
-`"my-service.my-ns"` `Service` has a port named `"http"` with protocol `TCP`, you
-can do a DNS SRV query for `"_http._tcp.my-service.my-ns"` to discover the port
-number for `"http"`.
-
-## Headless services
-
-Sometimes you don't need or want load-balancing and a single service IP.  In
-this case, you can create "headless" services by specifying `"None"` for the
-cluster IP (`spec.clusterIP`).
-
-For such `Services`, a cluster IP is not allocated. DNS is configured to return
-multiple A records (addresses) for the `Service` name, which point directly to
-the `Pods` backing the `Service`.  Additionally, the kube proxy does not handle
-these services and there is no load balancing or proxying done by the platform
-for them.  The endpoints controller will still create `Endpoints` records in
-the API.
-
-This option allows developers to reduce coupling to the Kubernetes system, if
-they desire, but leaves them freedom to do discovery in their own way.
-Applications can still use a self-registration pattern and adapters for other
-discovery systems could easily be built upon this API.
-
-## Publishing services - service types
-
-For some parts of your application (e.g. frontends) you may want to expose a
-Service onto an external (outside of your cluster, maybe public internet) IP
-address, other services should be visible only from inside of the cluster.
-
-
-Kubernetes `ServiceTypes` allow you to specify what kind of service you want.
-The default and base type is `ClusterIP`, which exposes a service to connection
-from inside the cluster. `NodePort` and `LoadBalancer` are two types that expose
-services to external traffic.
-
-Valid values for the `ServiceType` field are:
-
-   * `ClusterIP`: use a cluster-internal IP only - this is the default and is
-     discussed above. Choosing this value means that you want this service to be
-     reachable only from inside of the cluster.
-   * `NodePort`: on top of having a cluster-internal IP, expose the service on a
-     port on each node of the cluster (the same port on each node). You'll be able
-     to contact the service on any `<NodeIP>:NodePort` address.
-   * `LoadBalancer`: on top of having a cluster-internal IP and exposing service
-     on a NodePort also, ask the cloud provider for a load balancer
-     which forwards to the `Service` exposed as a `<NodeIP>:NodePort`
-     for each Node.
-
-Note that while `NodePort`s can be TCP or UDP, `LoadBalancer`s only support TCP
-as of Kubernetes 1.0.
-
-### Type NodePort
-
-If you set the `type` field to `"NodePort"`, the Kubernetes master will
-allocate a port from a flag-configured range (default: 30000-32767), and each
-Node will proxy that port (the same port number on every Node) into your `Service`.
-That port will be reported in your `Service`'s `spec.ports[*].nodePort` field.
-
-If you want a specific port number, you can specify a value in the `nodePort`
-field, and the system will allocate you that port or else the API transaction
-will fail (i.e. you need to take care about possible port collisions yourself).
-The value you specify must be in the configured range for node ports.
-
-This gives developers the freedom to set up their own load balancers, to
-configure cloud environments that are not fully supported by Kubernetes, or
-even to just expose one or more nodes' IPs directly.
-
-Note that this Service will be visible as both `<NodeIP>:spec.ports[*].nodePort`
-and `spec.clusterIp:spec.ports[*].port`.
-
-### Type LoadBalancer
-
-On cloud providers which support external load balancers, setting the `type`
-field to `"LoadBalancer"` will provision a load balancer for your `Service`.
-The actual creation of the load balancer happens asynchronously, and
-information about the provisioned balancer will be published in the `Service`'s
-`status.loadBalancer` field.  For example:
-
-```json
-{
-    "kind": "Service",
-    "apiVersion": "v1",
-    "metadata": {
-        "name": "my-service"
-    },
-    "spec": {
-        "selector": {
-            "app": "MyApp"
-        },
-        "ports": [
-            {
-                "protocol": "TCP",
-                "port": 80,
-                "targetPort": 9376,
-                "nodePort": 30061
-            }
-        ],
-        "clusterIP": "10.0.171.239",
-        "loadBalancerIP": "78.11.24.19",
-        "type": "LoadBalancer"
-    },
-    "status": {
-        "loadBalancer": {
-            "ingress": [
-                {
-                    "ip": "146.148.47.155"
-                }
-            ]
-        }
-    }
-}
-```
-
-Traffic from the external load balancer will be directed at the backend `Pods`,
-though exactly how that works depends on the cloud provider. Some cloud providers allow
-the `loadBalancerIP` to be specified. In those cases, the load-balancer will be created
-with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not specified,
-an ephemeral IP will be assigned to the loadBalancer. If the `loadBalancerIP` is specified, but the
-cloud provider does not support the feature, the field will be ignored.
-
-### External IPs
-
-If there are external IPs that route to one or more cluster nodes, Kubernetes services can be exposed on those
-`externalIPs`. Traffic that ingresses into the cluster with the external IP (as destination IP), on the service port,
-will be routed to one of the service endpoints. `externalIPs` are not managed by Kubernetes and are the responsibility
-of the cluster administrator.
-
-In the ServiceSpec, `externalIPs` can be specified along with any of the `ServiceTypes`.
-In the example below, my-service can be accessed by clients on 80.11.12.10:80 (externalIP:port)
-
-```json
-{
-    "kind": "Service",
-    "apiVersion": "v1",
-    "metadata": {
-        "name": "my-service"
-    },
-    "spec": {
-        "selector": {
-            "app": "MyApp"
-        },
-        "ports": [
-            {
-                "name": "http",
-                "protocol": "TCP",
-                "port": 80,
-                "targetPort": 9376
-            }
-        ],
-        "externalIPs" : [
-            "80.11.12.10"
-        ]
-    }
-}
-```
-
-## Shortcomings
-
-We expect that using iptables and userspace proxies for VIPs will work at
-small to medium scale, but may not scale to very large clusters with thousands
-of Services.  See [the original design proposal for
-portals](http://issue.k8s.io/1107) for more
-details.
-
-Using the kube-proxy obscures the source-IP of a packet accessing a `Service`.
-This makes some kinds of firewalling impossible.
-
-LoadBalancers only support TCP, not UDP.
-
-The `Type` field is designed as nested functionality - each level adds to the
-previous.  This is not strictly required on all cloud providers (e.g. Google Compute Engine does
-not need to allocate a `NodePort` to make `LoadBalancer` work, but AWS does)
-but the current API requires it.
-
-## Future work
-
-In the future we envision that the proxy policy can become more nuanced than
-simple round robin balancing, for example master-elected or sharded.  We also
-envision that some `Services` will have "real" load balancers, in which case the
-VIP will simply transport the packets there.
-
-There's a
-[proposal](http://issue.k8s.io/3760) to
-eliminate userspace proxying in favor of doing it all in iptables.  This should
-perform better and fix the source-IP obfuscation, though is less flexible than
-arbitrary userspace code.
-
-We intend to have first-class support for L7 (HTTP) `Services`.
-
-We intend to have more flexible ingress modes for `Services` which encompass
-the current `ClusterIP`, `NodePort`, and `LoadBalancer` modes and more.
-
-## The gory details of virtual IPs
-
-The previous information should be sufficient for many people who just want to
-use `Services`.  However, there is a lot going on behind the scenes that may be
-worth understanding.
-
-### Avoiding collisions
-
-One of the primary philosophies of Kubernetes is that users should not be
-exposed to situations that could cause their actions to fail through no fault
-of their own.  In this situation, we are looking at network ports - users
-should not have to choose a port number if that choice might collide with
-another user.  That is an isolation failure.
-
-In order to allow users to choose a port number for their `Services`, we must
-ensure that no two `Services` can collide.  We do that by allocating each
-`Service` its own IP address.
-
-To ensure each service receives a unique IP, an internal allocator atomically
-updates a global allocation map in etcd prior to each service. The map object
-must exist in the registry for services to get IPs, otherwise creations will
-fail with a message indicating an IP could not be allocated. A background
-controller is responsible for creating that map (to migrate from older versions
-of Kubernetes that used in memory locking) as well as checking for invalid
-assignments due to administrator intervention and cleaning up any IPs
-that were allocated but which no service currently uses.
-
-### IPs and VIPs
-
-Unlike `Pod` IP addresses, which actually route to a fixed destination,
-`Service` IPs are not actually answered by a single host.  Instead, we use
-`iptables` (packet processing logic in Linux) to define virtual IP addresses
-which are transparently redirected as needed.  When clients connect to the
-VIP, their traffic is automatically transported to an appropriate endpoint.
-The environment variables and DNS for `Services` are actually populated in
-terms of the `Service`'s VIP and port.
-
-As an example, consider the image processing application described above.
-When the backend `Service` is created, the Kubernetes master assigns a virtual
-IP address, for example 10.0.0.1.  Assuming the `Service` port is 1234, the
-`Service` is observed by all of the `kube-proxy` instances in the cluster.
-When a proxy sees a new `Service`, it opens a new random port, establishes an
-iptables redirect from the VIP to this new port, and starts accepting
-connections on it.
-
-When a client connects to the VIP the iptables rule kicks in, and redirects
-the packets to the `Service proxy`'s own port.  The `Service proxy` chooses a
-backend, and starts proxying traffic from the client to the backend.
-
-This means that `Service` owners can choose any port they want without risk of
-collision.  Clients can simply connect to an IP and port, without being aware
-of which `Pods` they are actually accessing.
-
-![Services detailed diagram](/images/docs/services-detail.svg)
-
-## API Object
-
-Service is a top-level resource in the kubernetes REST API. More details about the
-API object can be found at: [Service API
-object](/{{page.version}}/docs/api-reference/v1/definitions/#_v1_service).
\ No newline at end of file
diff --git a/v1.1/docs/user-guide/update-demo/index.md b/v1.1/docs/user-guide/update-demo/index.md
deleted file mode 100644
index 8879699f9f..0000000000
--- a/v1.1/docs/user-guide/update-demo/index.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
----
-
-
-<!--
-Copyright 2014 Google Inc. All rights reserved.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-
--->
-
-This example demonstrates the usage of Kubernetes to perform a [rolling update](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/user-guide/kubectl/kubectl_rolling-update.md) on a running group of [pods](/{{page.version}}/docs/user-guide/pods). See [here](/{{page.version}}/docs/user-guide/managing-deployments/#updating-your-application-without-a-service-outage) to understand why you need a rolling update. Also check [rolling update design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/simple-rolling-update.md) for more information.
-
-### Step Zero: Prerequisites
-
-This example assumes that you have forked the repository and [turned up a Kubernetes cluster](/{{page.version}}/docs/getting-started-guides/):
-
-```shell
-$ cd kubernetes
-$ ./cluster/kube-up.sh
-```
-
-### Step One: Turn up the UX for the demo
-
-You can use bash job control to run this in the background (note that you must use the default port -- 8001 -- for the following demonstration to work properly).
-This can sometimes spew to the output so you could also run it in a different terminal. You have to run `kubectl proxy` in the root of the
-Kubernetes repository. Otherwise you will get "404 page not found" errors as the paths will not match. You can find more information about `kubectl proxy`
-[here](/{{page.version}}/docs/user-guide/kubectl/kubectl_proxy).
-
-```shell
-$ kubectl proxy --www=docs/user-guide/update-demo/local/ &
-I0218 15:18:31.623279   67480 proxy.go:36] Starting to serve on localhost:8001
-```
-
-Now visit the the [demo website](http://localhost:8001/static).  You won't see anything much quite yet.
-
-### Step Two: Run the replication controller
-
-Now we will turn up two replicas of an [image](/{{page.version}}/docs/user-guide/images/).  They all serve on internal port 80.
-
-```shell
-$ kubectl create -f docs/user-guide/update-demo/nautilus-rc.yaml
-```
-
-After pulling the image from the Docker Hub to your worker nodes (which may take a minute or so) you'll see a couple of squares in the UI detailing the pods that are running along with the image that they are serving up.  A cute little nautilus.
-
-### Step Three: Try scaling the replication controller
-
-Now we will increase the number of replicas from two to four:
-
-```shell
-$ kubectl scale rc update-demo-nautilus --replicas=4
-```
-
-If you go back to the [demo website](http://localhost:8001/static/index) you should eventually see four boxes, one for each pod.
-
-### Step Four: Update the docker image
-
-We will now update the docker image to serve a different image by doing a rolling update to a new Docker image.
-
-```shell
-$ kubectl rolling-update update-demo-nautilus --update-period=10s -f docs/user-guide/update-demo/kitten-rc.yaml
-```
-
-The rolling-update command in kubectl will do 2 things:
-
-1. Create a new [replication controller](/{{page.version}}/docs/user-guide/replication-controller) with a pod template that uses the new image (`gcr.io/google_containers/update-demo:kitten`)
-2. Scale the old and new replication controllers until the new controller replaces the old. This will kill the current pods one at a time, spinning up new ones to replace them.
-
-Watch the [demo website](http://localhost:8001/static/index), it will update one pod every 10 seconds until all of the pods have the new image.
-Note that the new replication controller definition does not include the replica count, so the current replica count of the old replication controller is preserved.
-But if the replica count had been specified, the final replica count of the new replication controller will be equal this number.
-
-### Step Five: Bring down the pods
-
-```shell
-$ kubectl delete rc update-demo-kitten
-```
-
-This first stops the replication controller by turning the target number of replicas to 0 and then deletes the controller.
-
-### Step Six: Cleanup
-
-To turn down a Kubernetes cluster:
-
-```shell
-$ ./cluster/kube-down.sh
-```
-
-Kill the proxy running in the background:
-After you are done running this demo make sure to kill it:
-
-```shell
-$ jobs
-[1]+  Running                 ./kubectl proxy --www=local/ &
-$ kill %1
-[1]+  Terminated: 15          ./kubectl proxy --www=local/
-```
-
-### Updating the Docker images
-
-If you want to build your own docker images, you can set `$DOCKER_HUB_USER` to your Docker user id and run the included shell script. It can take a few minutes to download/upload stuff.
-
-```shell
-$ export DOCKER_HUB_USER=my-docker-id
-$ ./docs/user-guide/update-demo/build-images.sh
-```
-
-To use your custom docker image in the above examples, you will need to change the image name in `docs/user-guide/update-demo/nautilus-rc.yaml` and `docs/user-guide/update-demo/kitten-rc.yaml`.
-
-### Image Copyright
-
-Note that the images included here are public domain.
-
-* [kitten](http://commons.wikimedia.org/wiki/File:Kitten-stare.jpg)
-* [nautilus](http://commons.wikimedia.org/wiki/File:Nautilus_pompilius.jpg)
diff --git a/v1.1/docs/user-guide/walkthrough/k8s201.md b/v1.1/docs/user-guide/walkthrough/k8s201.md
deleted file mode 100644
index d9db253863..0000000000
--- a/v1.1/docs/user-guide/walkthrough/k8s201.md
+++ /dev/null
@@ -1,277 +0,0 @@
----
----
-
-
-If you went through [Kubernetes 101](/{{page.version}}/docs/user-guide/walkthrough/), you learned about kubectl, pods, volumes, and multiple containers.
-For Kubernetes 201, we will pick up where 101 left off and cover some slightly more advanced topics in Kubernetes, related to application productionization, deployment and
-scaling.
-
-In order for the kubectl usage examples to work, make sure you have an examples directory locally, either from [a release](https://github.com/kubernetes/kubernetes/releases) or [the source](https://github.com/kubernetes/kubernetes).
-
-* TOC
-{:toc}
-
-## Labels
-
-Having already learned about Pods and how to create them, you may be struck by an urge to create many, many pods.  Please do!  But eventually you will need a system to organize these pods into groups.  The system for achieving this in Kubernetes is Labels.  Labels are key-value pairs that are attached to each object in Kubernetes.  Label selectors can be passed along with a RESTful `list` request to the apiserver to retrieve a list of objects which match that label selector.
-
-To add a label, add a labels section under metadata in the pod definition:
-
-```yaml
-labels:
-    app: nginx
-```
-
-For example, here is the nginx pod definition with labels ([pod-nginx-with-label.yaml](/{{page.version}}/docs/user-guide/walkthrough/pod-nginx-with-label.yaml)):
-
-<!-- BEGIN MUNGE: EXAMPLE pod-nginx-with-label.yaml -->
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-  labels:
-    app: nginx
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    ports:
-    - containerPort: 80
-```
-
-[Download example](/{{page.version}}/docs/user-guide/walkthrough/pod-nginx-with-label.yaml)
-<!-- END MUNGE: EXAMPLE pod-nginx-with-label.yaml -->
-
-Create the labeled pod ([pod-nginx-with-label.yaml](/{{page.version}}/docs/user-guide/walkthrough/pod-nginx-with-label.yaml)):
-
-```shell
-$ kubectl create -f docs/user-guide/walkthrough/pod-nginx-with-label.yaml
-```
-
-List all pods with the label `app=nginx`:
-
-```shell
-$ kubectl get pods -l app=nginx
-```
-
-For more information, see [Labels](/{{page.version}}/docs/user-guide/labels).
-They are a core concept used by two additional Kubernetes building blocks: Replication Controllers and Services.
-
-
-## Replication Controllers
-
-OK, now you know how to make awesome, multi-container, labeled pods and you want to use them to build an application, you might be tempted to just start building a whole bunch of individual pods, but if you do that, a whole host of operational concerns pop up.  For example: how will you scale the number of pods up or down and how will you ensure that all pods are homogenous?
-
-Replication controllers are the objects to answer these questions.  A replication controller combines a template for pod creation (a "cookie-cutter" if you will) and a number of desired replicas, into a single Kubernetes object.  The replication controller also contains a label selector that identifies the set of objects managed by the replication controller.  The replication controller constantly measures the size of this set relative to the desired size, and takes action by creating or deleting pods.
-
-For example, here is a replication controller that instantiates two nginx pods ([replication-controller.yaml](/{{page.version}}/docs/user-guide/walkthrough/replication-controller.yaml)):
-
-<!-- BEGIN MUNGE: EXAMPLE replication-controller.yaml -->
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: nginx-controller
-spec:
-  replicas: 2
-  # selector identifies the set of Pods that this
-  # replication controller is responsible for managing
-  selector:
-    app: nginx
-  # podTemplate defines the 'cookie cutter' used for creating
-  # new pods when necessary
-  template:
-    metadata:
-      labels:
-        # Important: these labels need to match the selector above
-        # The api server enforces this constraint.
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        ports:
-        - containerPort: 80
-```
-
-[Download example](/{{page.version}}/docs/user-guide/walkthrough/replication-controller.yaml)
-<!-- END MUNGE: EXAMPLE replication-controller.yaml -->
-
-#### Replication Controller Management
-
-Create an nginx replication controller ([replication-controller.yaml](/{{page.version}}/docs/user-guide/walkthrough/replication-controller.yaml)):
-
-```shell
-$ kubectl create -f docs/user-guide/walkthrough/replication-controller.yaml
-```
-
-List all replication controllers:
-
-```shell
-$ kubectl get rc
-```
-
-Delete the replication controller by name:
-
-```shell
-$ kubectl delete rc nginx-controller
-```
-
-For more information, see [Replication Controllers](/{{page.version}}/docs/user-guide/replication-controller).
-
-
-## Services
-
-Once you have a replicated set of pods, you need an abstraction that enables connectivity between the layers of your application.  For example, if you have a replication controller managing your backend jobs, you don't want to have to reconfigure your front-ends whenever you re-scale your backends.  Likewise, if the pods in your backends are scheduled (or rescheduled) onto different machines, you can't be required to re-configure your front-ends.  In Kubernetes, the service abstraction achieves these goals.  A service provides a way to refer to a set of pods (selected by labels) with a single static IP address. It may also provide load balancing, if supported by the provider.
-
-For example, here is a service that balances across the pods created in the previous nginx replication controller example ([service.yaml](/{{page.version}}/docs/user-guide/walkthrough/service.yaml)):
-
-<!-- BEGIN MUNGE: EXAMPLE service.yaml -->
-
-```yaml
-apiVersion: v1
-kind: Service
-metadata:
-  name: nginx-service
-spec:
-  ports:
-  - port: 8000 # the port that this service should serve on
-    # the container on each pod to connect to, can be a name
-    # (e.g. 'www') or a number (e.g. 80)
-    targetPort: 80
-    protocol: TCP
-  # just like the selector in the replication controller,
-  # but this time it identifies the set of pods to load balance
-  # traffic to.
-  selector:
-    app: nginx
-```
-
-[Download example](/{{page.version}}/docs/user-guide/walkthrough/service.yaml)
-<!-- END MUNGE: EXAMPLE service.yaml -->
-
-#### Service Management
-
-Create an nginx service ([service.yaml](/{{page.version}}/docs/user-guide/walkthrough/service.yaml)):
-
-```shell
-$ kubectl create -f docs/user-guide/walkthrough/service.yaml
-```
-
-List all services:
-
-```shell
-$ kubectl get services
-```
-
-On most providers, the service IPs are not externally accessible. The easiest way to test that the service is working is to create a busybox pod and exec commands on it remotely. See the [command execution documentation](/{{page.version}}/docs/user-guide/kubectl-overview/) for details.
-
-Provided the service IP is accessible, you should be able to access its http endpoint with curl on port 80:
-
-```shell
-$ export SERVICE_IP=$(kubectl get service nginx-service -o go-template={{.spec.clusterIP}})
-$ export SERVICE_PORT=$(kubectl get service nginx-service -o go-template'={{(index .spec.ports 0).port}}')
-$ curl http://${SERVICE_IP}:${SERVICE_PORT}
-```
-
-To delete the service by name:
-
-```shell
-$ kubectl delete service nginx-service
-```
-
-When created, each service is assigned a unique IP address.  This address is tied to the lifespan of the Service, and will not change while the Service is alive.  Pods can be configured to talk to the service, and know that communication to the service will be automatically load-balanced out to some pod that is a member of the set identified by the label selector in the Service.
-
-For more information, see [Services](/{{page.version}}/docs/user-guide/services/).
-
-
-## Health Checking
-
-When I write code it never crashes, right?  Sadly the [Kubernetes issues list](https://github.com/kubernetes/kubernetes/issues) indicates otherwise...
-
-Rather than trying to write bug-free code, a better approach is to use a management system to perform periodic health checking
-and repair of your application.  That way a system outside of your application itself is responsible for monitoring the
-application and taking action to fix it.  It's important that the system be outside of the application, since if
-your application fails and the health checking agent is part of your application, it may fail as well and you'll never know.
-In Kubernetes, the health check monitor is the Kubelet agent.
-
-#### Process Health Checking
-
-The simplest form of health-checking is just process level health checking.  The Kubelet constantly asks the Docker daemon
-if the container process is still running, and if not, the container process is restarted.  In all of the Kubernetes examples
-you have run so far, this health checking was actually already enabled.  It's on for every single container that runs in
-Kubernetes.
-
-#### Application Health Checking
-
-However, in many cases this low-level health checking is insufficient.  Consider, for example, the following code:
-
-```go
-lockOne := sync.Mutex{}
-lockTwo := sync.Mutex{}
-
-go func() {
-  lockOne.Lock();
-  lockTwo.Lock();
-  ...
-}()
-
-lockTwo.Lock();
-lockOne.Lock();
-```
-
-This is a classic example of a problem in computer science known as ["Deadlock"](https://en.wikipedia.org/wiki/Deadlock). From Docker's perspective your application is
-still operating and the process is still running, but from your application's perspective your code is locked up and will never respond correctly.
-
-To address this problem, Kubernetes supports user implemented application health-checks.  These checks are performed by the
-Kubelet to ensure that your application is operating correctly for a definition of "correctly" that _you_ provide.
-
-Currently, there are three types of application health checks that you can choose from:
-
-   * HTTP Health Checks - The Kubelet will call a web hook.  If it returns between 200 and 399, it is considered success, failure otherwise. See health check examples [here](/{{page.version}}/docs/user-guide/liveness/).
-   * Container Exec - The Kubelet will execute a command inside your container.  If it exits with status 0 it will be considered a success. See health check examples [here](/{{page.version}}/docs/user-guide/liveness/).
-   * TCP Socket - The Kubelet will attempt to open a socket to your container.  If it can establish a connection, the container is considered healthy, if it can't it is considered a failure.
-
-In all cases, if the Kubelet discovers a failure the container is restarted.
-
-The container health checks are configured in the `livenessProbe` section of your container config. There you can also specify an `initialDelaySeconds` that is a grace period from when the container is started to when health checks are performed, to enable your container to perform any necessary initialization.
-
-Here is an example config for a pod with an HTTP health check ([pod-with-http-healthcheck.yaml](/{{page.version}}/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml)):
-
-<!-- BEGIN MUNGE: EXAMPLE pod-with-http-healthcheck.yaml -->
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: pod-with-healthcheck
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    # defines the health checking
-    livenessProbe:
-      # an http probe
-      httpGet:
-        path: /_status/healthz
-        port: 80
-      # length of time to wait for a pod to initialize
-      # after pod startup, before applying health checking
-      initialDelaySeconds: 30
-      timeoutSeconds: 1
-    ports:
-    - containerPort: 80
-```
-
-[Download example](/{{page.version}}/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml)
-<!-- END MUNGE: EXAMPLE pod-with-http-healthcheck.yaml -->
-
-For more information about health checking, see [Container Probes](/{{page.version}}/docs/user-guide/pod-states/#container-probes).
-
-
-## What's Next?
-
-For a complete application see the [guestbook example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/).
\ No newline at end of file
diff --git a/v1.1/pagelist.md b/v1.1/pagelist.md
deleted file mode 100644
index 431f35c628..0000000000
--- a/v1.1/pagelist.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
----
-The following is a list of all pages for {{ page.version }}. We also have a [`sitemap.xml`](/sitemap.xml) file.
-
-{% for page in site.pages %}
-  {% if page.url contains page.version %}
-  {% assign foundTOC=false %}
-  {% assign pageTOC=false %}
-  {% for thistoc in site.data[page.versionfilesafe].globals.tocs %}
-    {% if foundTOC %}
-    {% break %}
-    {% else %}
-    {% assign tree = site.data[page.versionfilesafe][thistoc].toc %}
-    {% include tocsearch.html %}
-    {% if foundTOC %}
-      {% assign pageTOC = thistoc %}
-    {% endif %}
-    {% endif %}
-  {% endfor %}
-* {% if pageTOC %}**[{{ pageTOC | capitalize }}](/{{page.version}}/{%if pageTOC != "guides"%}{{pageTOC}}/{%endif%})**: {% endif %}[{% if page.title %}{{page.title}}{% else %}{{ page.url }}{% endif %}]({{ page.url }})
-  {% endif %}
-{% endfor %}
\ No newline at end of file
diff --git a/v1.2/docs/admin/accessing-the-api.md b/v1.2/docs/admin/accessing-the-api.md
deleted file mode 100644
index deaf67185b..0000000000
--- a/v1.2/docs/admin/accessing-the-api.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
----
-
-This document describes what ports the Kubernetes apiserver
-may serve on and how to reach them.  The audience is
-cluster administrators who want to customize their cluster
-or understand the details.
-
-Most questions about accessing the cluster are covered
-in [Accessing the cluster](/{{page.version}}/docs/user-guide/accessing-the-cluster).
-
-
-## Ports and IPs Served On
-
-The Kubernetes API is served by the Kubernetes apiserver process.  Typically,
-there is one of these running on a single kubernetes-master node.
-
-By default the Kubernetes APIserver serves HTTP on 2 ports:
-
-  1. Localhost Port
-    - serves HTTP
-    - default is port 8080, change with `--insecure-port` flag.
-    - defaults IP is localhost, change with `--insecure-bind-address` flag.
-    - no authentication or authorization checks in HTTP
-    - protected by need to have host access
-  2. Secure Port
-    - default is port 6443, change with `--secure-port` flag.
-    - default IP is first non-localhost network interface, change with `--bind-address` flag.
-    - serves HTTPS.  Set cert with `--tls-cert-file` and key with `--tls-private-key-file` flag.
-    - uses token-file or client-certificate based [authentication](/{{page.version}}/docs/admin/authentication).
-    - uses policy-based [authorization](/{{page.version}}/docs/admin/authorization).
-  3. Removed: ReadOnly Port
-    - For security reasons, this had to be removed. Use the [service account](/{{page.version}}/docs/user-guide/service-accounts) feature instead.
-
-## Proxies and Firewall rules
-
-Additionally, in some configurations there is a proxy (nginx) running
-on the same machine as the apiserver process.  The proxy serves HTTPS protected
-by Basic Auth on port 443, and proxies to the apiserver on localhost:8080. In
-these configurations the secure port is typically set to 6443.
-
-A firewall rule is typically configured to allow external HTTPS access to port 443.
-
-The above are defaults and reflect how Kubernetes is deployed to Google Compute Engine using
-kube-up.sh.  Other cloud providers may vary.
-
-## Use Cases vs IP:Ports
-
-There are three differently configured serving ports because there are a
-variety of uses cases:
-
-   1. Clients outside of a Kubernetes cluster, such as human running `kubectl`
-      on desktop machine.  Currently, accesses the Localhost Port via a proxy (nginx)
-      running on the `kubernetes-master` machine.  The proxy can use cert-based authentication
-      or token-based authentication.
-   2. Processes running in Containers on Kubernetes that need to read from
-      the apiserver.  Currently, these can use a [service account](/{{page.version}}/docs/user-guide/service-accounts).
-   3. Scheduler and Controller-manager processes, which need to do read-write
-      API operations. Currently, these have to run on the same host as the
-      apiserver and use the Localhost Port.  In the future, these will be
-      switched to using service accounts to avoid the need to be co-located.
-   4. Kubelets, which need to do read-write API operations and are necessarily
-      on different machines than the apiserver.  Kubelet uses the Secure Port
-      to get their pods, to find the services that a pod can see, and to
-      write events.  Credentials are distributed to kubelets at cluster
-      setup time. Kubelet and kube-proxy can use cert-based authentication or token-based
-      authentication.
-
-## Expected changes
-
-   - Policy will limit the actions kubelets can do via the authed port.
-   - Scheduler and Controller-manager will use the Secure Port too.  They
-     will then be able to run on different machines than the apiserver.
-
-
diff --git a/v1.2/docs/admin/authentication.md b/v1.2/docs/admin/authentication.md
deleted file mode 100644
index 60b5923101..0000000000
--- a/v1.2/docs/admin/authentication.md
+++ /dev/null
@@ -1,128 +0,0 @@
----
----
-
-Kubernetes uses client certificates, tokens, or http basic auth to authenticate users for API calls.
-
-**Client certificate authentication** is enabled by passing the `--client-ca-file=SOMEFILE`
-option to apiserver. The referenced file must contain one or more certificates authorities
-to use to validate client certificates presented to the apiserver. If a client certificate
-is presented and verified, the common name of the subject is used as the user name for the
-request.
-
-**Token File** is enabled by passing the `--token-auth-file=SOMEFILE` option
-to apiserver.  Currently, tokens last indefinitely, and the token list cannot
-be changed without restarting apiserver.
-
-The token file format is implemented in `plugin/pkg/auth/authenticator/token/tokenfile/...`
-and is a csv file with 3 columns: token, user name, user uid.
-
-When using token authentication from an http client the apiserver expects an `Authorization`
-header with a value of `Bearer SOMETOKEN`.
-
-**OpenID Connect ID Token** is enabled by passing the following options to the apiserver:
-- `--oidc-issuer-url` (required) tells the apiserver where to connect to the OpenID provider. Only HTTPS scheme will be accepted.
-- `--oidc-client-id` (required) is used by apiserver to verify the audience of the token.
-A valid [ID token](http://openid.net/specs/openid-connect-core-1_0/#IDToken) MUST have this
-client-id in its `aud` claims.
-- `--oidc-ca-file` (optional) is used by apiserver to establish and verify the secure connection
-to the OpenID provider.
-- `--oidc-username-claim` (optional, experimental) specifies which OpenID claim to use as the user name. By default, `sub`
-will be used, which should be unique and immutable under the issuer's domain. Cluster administrator can
-choose other claims such as `email` to use as the user name, but the uniqueness and immutability is not guaranteed.
-
-Please note that this flag is still experimental until we settle more on how to handle the mapping of the OpenID user to the Kubernetes user. Thus further changes are possible.
-
-Currently, the ID token will be obtained by some third-party app. This means the app and apiserver
-MUST share the `--oidc-client-id`.
-
-Like **Token File**, when using token authentication from an http client the apiserver expects
-an `Authorization` header with a value of `Bearer SOMETOKEN`.
-
-**Basic authentication** is enabled by passing the `--basic-auth-file=SOMEFILE`
-option to apiserver. Currently, the basic auth credentials last indefinitely,
-and the password cannot be changed without restarting apiserver. Note that basic
-authentication is currently supported for convenience while we finish making the
-more secure modes described above easier to use.
-
-The basic auth file format is implemented in `plugin/pkg/auth/authenticator/password/passwordfile/...`
-and is a csv file with 3 columns: password, user name, user id.
-
-When using basic authentication from an http client, the apiserver expects an `Authorization` header
-with a value of `Basic BASE64ENCODED(USER:PASSWORD)`.
-
-**Keystone authentication** is enabled by passing the `--experimental-keystone-url=<AuthURL>`
-option to the apiserver during startup. The plugin is implemented in
-`plugin/pkg/auth/authenticator/request/keystone/keystone.go`.
-For details on how to use keystone to manage projects and users, refer to the
-[Keystone documentation](http://docs.openstack.org/developer/keystone/). Please note that
-this plugin is still experimental which means it is subject to changes.
-Please refer to the [discussion](https://github.com/kubernetes/kubernetes/pull/11798#issuecomment-129655212)
-and the [blueprint](https://github.com/kubernetes/kubernetes/issues/11626) for more details
-
-## Plugin Development
-
-We plan for the Kubernetes API server to issue tokens
-after the user has been (re)authenticated by a *bedrock* authentication
-provider external to Kubernetes.  We plan to make it easy to develop modules
-that interface between Kubernetes and a bedrock authentication provider (e.g.
-github.com, google.com, enterprise directory, kerberos, etc.)
-
-## APPENDIX
-
-### Creating Certificates
-
-When using client certificate authentication, you can generate certificates manually or
-using an existing deployment script.
-
-**Deployment script** is implemented at
-`cluster/saltbase/salt/generate-cert/make-ca-cert.sh`.
-Execute this script with two parameters. First is the IP address of apiserver, the second is
-a list of subject alternate names in the form `IP:<ip-address> or DNS:<dns-name>`.
-The script will generate three files:ca.crt, server.crt and server.key.
-Finally, add these parameters
-`--client-ca-file=/srv/kubernetes/ca.crt`
-`--tls-cert-file=/srv/kubernetes/server.cert`
-`--tls-private-key-file=/srv/kubernetes/server.key`
-into apiserver start parameters.
-
-**easyrsa** can be used to manually generate certificates for your cluster.
-
-1.  Download, unpack, and initialize the patched version of easyrsa3.
-
-          curl -L -O https://storage.googleapis.com/kubernetes-release/easy-rsa/easy-rsa.tar.gz
-          tar xzf easy-rsa.tar.gz
-          cd easy-rsa-master/easyrsa3
-          ./easyrsa init-pki
-1.  Generate a CA. (`--batch` set automatic mode. `--req-cn` default CN to use.)
-
-          ./easyrsa --batch "--req-cn=${MASTER_IP}@`date +%s`" build-ca nopass
-1.  Generate server certificate and key.
-    (build-server-full [filename]: Generate a keypair and sign locally for a client or server)
-
-          ./easyrsa --subject-alt-name="IP:${MASTER_IP}" build-server-full kubernetes-master nopass
-1.  Copy `pki/ca.crt`  `pki/issued/kubernetes-master.crt`
-    `pki/private/kubernetes-master.key` to your directory.
-1.  Remember fill the parameters
-    `--client-ca-file=/yourdirectory/ca.crt`
-    `--tls-cert-file=/yourdirectory/server.cert`
-    `--tls-private-key-file=/yourdirectory/server.key`
-    and add these into apiserver start parameters.
-
-**openssl** can also be use to manually generate certificates for your cluster.
-
-1.  Generate a ca.key with 2048bit
-    `openssl genrsa -out ca.key 2048`
-1.  According to the ca.key generate a ca.crt.  (-days set the certificate effective time).
-    `openssl req -x509 -new -nodes -key ca.key -subj "/CN=${MASTER_IP}" -days 10000 -out ca.crt`
-1.  Generate a server.key with 2048bit
-    `openssl genrsa -out server.key 2048`
-1.  According to the server.key generate a server.csr.
-    `openssl req -new -key server.key -subj "/CN=${MASTER_IP}" -out server.csr`
-1.  According to the ca.key, ca.crt and server.csr generate the server.crt.
-    `openssl x509 -req -in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out server.crt
-    -days 10000`
-1.  View the certificate.
-    `openssl x509  -noout -text -in ./server.crt`
-    Finally, do not forget fill the same parameters and add parameters into apiserver start parameters.
-
-
diff --git a/v1.2/docs/admin/authorization.md b/v1.2/docs/admin/authorization.md
deleted file mode 100644
index 3f49467808..0000000000
--- a/v1.2/docs/admin/authorization.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
----
-
-In Kubernetes, authorization happens as a separate step from authentication.
-See the [authentication documentation](/{{page.version}}/docs/admin/authentication) for an
-overview of authentication.
-
-Authorization applies to all HTTP accesses on the main (secure) apiserver port.
-
-The authorization check for any request compares attributes of the context of
-the request, (such as user, resource, and namespace) with access
-policies.  An API call must be allowed by some policy in order to proceed.
-
-The following implementations are available, and are selected by flag:
-
-  - `--authorization-mode=AlwaysDeny`
-  - `--authorization-mode=AlwaysAllow`
-  - `--authorization-mode=ABAC`
-
-`AlwaysDeny` blocks all requests (used in tests).
-`AlwaysAllow` allows all requests; use if you don't need authorization.
-`ABAC` allows for user-configured authorization policy.  ABAC stands for Attribute-Based Access Control.
-
-## ABAC Mode
-
-### Request Attributes
-
-A request has 5 attributes that can be considered for authorization:
-
-  - user (the user-string which a user was authenticated as).
-  - group (the list of group names the authenticated user is a member of).
-  - whether the request is readonly (GETs are readonly).
-  - what resource is being accessed.
-    - applies only to the API endpoints, such as
-        `/api/v1/namespaces/default/pods`.  For miscellaneous endpoints, like `/version`, the
-        resource is the empty string.
-  - the namespace of the object being access, or the empty string if the
-        endpoint does not support namespaced objects.
-
-We anticipate adding more attributes to allow finer grained access control and
-to assist in policy management.
-
-### Policy File Format
-
-For mode `ABAC`, also specify `--authorization-policy-file=SOME_FILENAME`.
-
-The file format is [one JSON object per line](http://jsonlines.org/).  There should be no enclosing list or map, just
-one map per line.
-
-Each line is a "policy object".  A policy object is a map with the following properties:
-
-  - `user`, type string; the user-string from `--token-auth-file`. If you specify `user`, it must match the username of the authenticated user.
-  - `group`, type string; if you specify `group`, it must match one of the groups of the authenticated user.
-  - `readonly`, type boolean, when true, means that the policy only applies to GET
-      operations.
-  - `resource`, type string; a resource from an URL, such as `pods`.
-  - `namespace`, type string; a namespace string.
-
-An unset property is the same as a property set to the zero value for its type (e.g. empty string, 0, false).
-However, unset should be preferred for readability.
-
-In the future, policies may be expressed in a JSON format, and managed via a REST
-interface.
-
-### Authorization Algorithm
-
-A request has attributes which correspond to the properties of a policy object.
-
-When a request is received, the attributes are determined.  Unknown attributes
-are set to the zero value of its type (e.g. empty string, 0, false).
-
-An unset property will match any value of the corresponding
-attribute.  An unset attribute will match any value of the corresponding property.
-
-The tuple of attributes is checked for a match against every policy in the policy file.
-If at least one line matches the request attributes, then the request is authorized (but may fail later validation).
-
-To permit any user to do something, write a policy with the user property unset.
-To permit an action Policy with an unset namespace applies regardless of namespace.
-
-### Examples
-
- 1. Alice can do anything: `{"user":"alice"}`
- 2. Kubelet can read any pods: `{"user":"kubelet", "resource": "pods", "readonly": true}`
- 3. Kubelet can read and write events: `{"user":"kubelet", "resource": "events"}`
- 4. Bob can just read pods in namespace "projectCaribou": `{"user":"bob", "resource": "pods", "readonly": true, "namespace": "projectCaribou"}`
-
-[Complete file example](http://releases.k8s.io/{{page.githubbranch}}/pkg/auth/authorizer/abac/example_policy_file.jsonl)
-
-### A quick note on service accounts
-
-A service account automatically generates a user. The user's name is generated according to the naming convention:
-
-```shell
-system:serviceaccount:<namespace>:<serviceaccountname>
-```
-Creating a new namespace also causes a new service account to be created, of this form:*
-
-```shell
-system:serviceaccount:<namespace>:default
-```
-
-For example, if you wanted to grant the default service account in the kube-system full privilege to the API, you would add this line to your policy file:
-
-```json
-{"user":"system:serviceaccount:kube-system:default"}
-```
-
-The apiserver will need to be restarted to pickup the new policy lines.
-
-## Plugin Development
-
-Other implementations can be developed fairly easily.
-The APIserver calls the Authorizer interface:
-
-```go
-type Authorizer interface {
-  Authorize(a Attributes) error
-}
-```
-
-to determine whether or not to allow each API action.
-
-An authorization plugin is a module that implements this interface.
-Authorization plugin code goes in `pkg/auth/authorizer/$MODULENAME`.
-
-An authorization module can be completely implemented in go, or can call out
-to a remote authorization service.  Authorization modules can implement
-their own caching to reduce the cost of repeated authorization calls with the
-same or similar arguments.  Developers should then consider the interaction between
-caching and revocation of permissions.
\ No newline at end of file
diff --git a/v1.2/docs/admin/cluster-troubleshooting.md b/v1.2/docs/admin/cluster-troubleshooting.md
deleted file mode 100644
index cd1c95847f..0000000000
--- a/v1.2/docs/admin/cluster-troubleshooting.md
+++ /dev/null
@@ -1,112 +0,0 @@
----
----
-
-This doc is about cluster troubleshooting; we assume you have already ruled out your application as the root cause of the
-problem you are experiencing. See
-the [application troubleshooting guide](/{{page.version}}/docs/user-guide/application-troubleshooting) for tips on application debugging.
-You may also visit [troubleshooting document](/{{page.version}}/docs/troubleshooting/) for more information.
-
-## Listing your cluster
-
-The first thing to debug in your cluster is if your nodes are all registered correctly.
-
-Run
-
-```shell
-kubectl get nodes
-```
-
-And verify that all of the nodes you expect to see are present and that they are all in the `Ready` state.
-
-## Looking at logs
-
-For now, digging deeper into the cluster requires logging into the relevant machines.  Here are the locations
-of the relevant log files.  (note that on systemd-based systems, you may need to use `journalctl` instead)
-
-### Master
-
-   * /var/log/kube-apiserver.log - API Server, responsible for serving the API
-   * /var/log/kube-scheduler.log - Scheduler, responsible for making scheduling decisions
-   * /var/log/kube-controller-manager.log - Controller that manages replication controllers
-
-### Worker Nodes
-
-   * /var/log/kubelet.log - Kubelet, responsible for running containers on the node
-   * /var/log/kube-proxy.log - Kube Proxy, responsible for service load balancing
-
-## A general overview of cluster failure modes
-
-This is an incomplete list of things that could go wrong, and how to adjust your cluster setup to mitigate the problems.
-
-Root causes:
-
-  - VM(s) shutdown
-  - Network partition within cluster, or between cluster and users
-  - Crashes in Kubernetes software
-  - Data loss or unavailability of persistent storage (e.g. GCE PD or AWS EBS volume)
-  - Operator error, e.g. misconfigured Kubernetes software or application software
-
-Specific scenarios:
-
-  - Apiserver VM shutdown or apiserver crashing
-    - Results
-      - unable to stop, update, or start new pods, services, replication controller
-      - existing pods and services should continue to work normally, unless they depend on the Kubernetes API
-  - Apiserver backing storage lost
-    - Results
-      - apiserver should fail to come up
-      - kubelets will not be able to reach it but will continue to run the same pods and provide the same service proxying
-      - manual recovery or recreation of apiserver state necessary before apiserver is restarted
-  - Supporting services (node controller, replication controller manager, scheduler, etc) VM shutdown or crashes
-    - currently those are colocated with the apiserver, and their unavailability has similar consequences as apiserver
-    - in future, these will be replicated as well and may not be co-located
-    - they do not have their own persistent state
-  - Individual node (VM or physical machine) shuts down
-    - Results
-      - pods on that Node stop running
-  - Network partition
-    - Results
-      - partition A thinks the nodes in partition B are down; partition B thinks the apiserver is down. (Assuming the master VM ends up in partition A.)
-  - Kubelet software fault
-    - Results
-      - crashing kubelet cannot start new pods on the node
-      - kubelet might delete the pods or not
-      - node marked unhealthy
-      - replication controllers start new pods elsewhere
-  - Cluster operator error
-    - Results
-      - loss of pods, services, etc
-      - lost of apiserver backing store
-      - users unable to read API
-      - etc.
-
-Mitigations:
-
-- Action: Use IaaS provider's automatic VM restarting feature for IaaS VMs
-  - Mitigates: Apiserver VM shutdown or apiserver crashing
-  - Mitigates: Supporting services VM shutdown or crashes
-
-- Action use IaaS providers reliable storage (e.g GCE PD or AWS EBS volume) for VMs with apiserver+etcd
-  - Mitigates: Apiserver backing storage lost
-
-- Action: Use (experimental) [high-availability](/{{page.version}}/docs/admin/high-availability) configuration
-  - Mitigates: Master VM shutdown or master components (scheduler, API server, controller-managing) crashing
-    - Will tolerate one or more simultaneous node or component failures
-  - Mitigates: Apiserver backing storage (i.e., etcd's data directory) lost
-    - Assuming you used clustered etcd.
-
-- Action: Snapshot apiserver PDs/EBS-volumes periodically
-  - Mitigates: Apiserver backing storage lost
-  - Mitigates: Some cases of operator error
-  - Mitigates: Some cases of Kubernetes software fault
-
-- Action: use replication controller and services in front of pods
-  - Mitigates: Node shutdown
-  - Mitigates: Kubelet software fault
-
-- Action: applications (containers) designed to tolerate unexpected restarts
-  - Mitigates: Node shutdown
-  - Mitigates: Kubelet software fault
-
-- Action: [Multiple independent clusters](/{{page.version}}/docs/admin/multi-cluster) (and avoid making risky changes to all clusters at once)
-  - Mitigates: Everything listed above.
\ No newline at end of file
diff --git a/v1.2/docs/admin/daemon.yaml b/v1.2/docs/admin/daemon.yaml
deleted file mode 100644
index c5cd14a592..0000000000
--- a/v1.2/docs/admin/daemon.yaml
+++ /dev/null
@@ -1,18 +0,0 @@
-apiVersion: extensions/v1beta1 
-kind: DaemonSet
-metadata:
-  name: prometheus-node-exporter
-spec:
-  template:
-    metadata:
-      name: prometheus-node-exporter
-      labels:
-        daemon: prom-node-exp
-    spec:
-      containers:
-      - name: c
-        image: prom/prometheus
-        ports:
-        - containerPort: 9090
-          hostPort: 9090
-          name: serverport
diff --git a/v1.2/docs/admin/daemons.md b/v1.2/docs/admin/daemons.md
deleted file mode 100644
index 5645403d21..0000000000
--- a/v1.2/docs/admin/daemons.md
+++ /dev/null
@@ -1,169 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## What is a _Daemon Set_?
-
-A _Daemon Set_ ensures that all (or some) nodes run a copy of a pod.  As nodes are added to the
-cluster, pods are added to them.  As nodes are removed from the cluster, those pods are garbage
-collected.  Deleting a Daemon Set will clean up the pods it created.
-
-Some typical uses of a Daemon Set are:
-
-- running a cluster storage daemon, such as `glusterd`, `ceph`, on each node.
-- running a logs collection daemon on every node, such as `fluentd` or `logstash`.
-- running a node monitoring daemon on every node, such as [Prometheus Node Exporter](
-  https://github.com/prometheus/node_exporter), `collectd`, New Relic agent, or Ganglia `gmond`.
-
-In a simple case, one Daemon Set, covering all nodes, would be used for each type of daemon.
-A more complex setup might use multiple DaemonSets would be used for a single type of daemon,
-but with different flags and/or different memory and cpu requests for different hardware types.
-
-## Writing a DaemonSet Spec
-
-### Required Fields
-
-As with all other Kubernetes config, a DaemonSet needs `apiVersion`, `kind`, and `metadata` fields.  For
-general information about working with config files, see [here](/{{page.version}}/docs/user-guide/simple-yaml),
-[here](/{{page.version}}/docs/user-guide/configuring-containers), and [here](/{{page.version}}/docs/user-guide/working-with-resources).
-
-A DaemonSet also needs a [`.spec`](/{{page.version}}/docs/devel/api-conventions/#spec-and-status) section.
-
-### Pod Template
-
-The `.spec.template` is the only required field of the `.spec`.
-
-The `.spec.template` is a [pod template](/{{page.version}}/docs/user-guide/replication-controller/#pod-template).
-It has exactly the same schema as a [pod](/{{page.version}}/docs/user-guide/pods), except
-it is nested and does not have an `apiVersion` or `kind`.
-
-In addition to required fields for a pod, a pod template in a DaemonSet has to specify appropriate
-labels (see [pod selector](#pod-selector)).
-
-A pod template in a DaemonSet must have a [`RestartPolicy`](/{{page.version}}/docs/user-guide/pod-states)
- equal to `Always`, or be unspecified, which defaults to `Always`.
-
-### Pod Selector
-
-The `.spec.selector` field is a pod selector.  It works the same as the `.spec.selector` of
-a [ReplicationController](/{{page.version}}/docs/user-guide/replication-controller) or
-[Job](/{{page.version}}/docs/user-guide/jobs).
-
-If the `.spec.selector` is specified, it must equal the `.spec.template.metadata.labels`.  If not
-specified, the are default to be equal.  Config with these unequal will be rejected by the API.
-
-Also you should not normally create any pods whose labels match this selector, either directly, via
-another DaemonSet, or via other controller such as ReplicationController.  Otherwise, the DaemonSet
-controller will think that those pods were created by it.  Kubernetes will not stop you from doing
-this.  Once case where you might want to do this is manually create a pod with a different value on
-a node for testing.
-
-### Running Pods on Only Some Nodes
-
-If you specify a `.spec.template.spec.nodeSelector`, then the DaemonSet controller will
-create pods on nodes which match that [node
-selector](/{{page.version}}/docs/user-guide/node-selection/).
-
-If you do not specify a `.spec.template.spec.nodeSelector`, then the DaemonSet controller will
-create pods on all nodes.
-
-## How Daemon Pods are Scheduled
-
-Normally, the machine that a pod runs on is selected by the Kubernetes scheduler.  However, pods
-created by the Daemon controller have the machine already selected (`.spec.nodeName` is specified
-when the pod is created, so it is ignored by the scheduler).  Therefore:
-
- - the [`unschedulable`](/{{page.version}}/docs/admin/node/#manual-node-administration) field of a node is not respected
-   by the daemon set controller.
- - daemon set controller can make pods even when the scheduler has not been started, which can help cluster
-   bootstrap.
-
-## Communicating with DaemonSet Pods
-
-Some possible patterns for communicating with pods in a DaemonSet are:
-
-- **Push**: Pods in the Daemon Set are configured to send updates to another service, such
-  as a stats database.  They do not have clients.
-- **NodeIP and Known Port**: Pods in the Daemon Set use a `hostPort`, so that the pods are reachable
-  via the node IPs.  Clients knows the the list of nodes ips somehow, and know the port by convention.
-- **DNS**: Create a [headless service](/{{page.version}}/docs/user-guide/services/#headless-services) with the same pod selector,
-  and then discover DaemonSets using the `endpoints` resource or retrieve multiple A records from
-  DNS.
-- **Service**: Create a service with the same pod selector, and use the service to reach a
-  daemon on a random node. (No way to reach specific node.)
-
-## Updating a DaemonSet
-
-If node labels are changed, the DaemonSet will promptly add pods to newly matching nodes and delete
-pods from newly not-matching nodes.
-
-You can modify the pods that a DaemonSet creates.  However, pods do not allow all
-fields to be updated.  Also, the DeamonSet controller will use the original template the next
-time a node (even with the same name) is created.
-
-
-You can delete a DeamonSet.  If you specify `--cascade=false` with `kubectl`, then the pods
-will be left on the nodes.  You can then create a new DaemonSet with a different template.
-the new DaemonSet with the different template will recognize all the existing pods as having
-matching labels.  It will not modify or delete them despite a mismatch in the pod template.
-You will need to force new pod creation by deleting the pod or deleting the node.
-
-You cannot update a DaemonSet.
-
-Support for updating DaemonSets and controlled updating of nodes is planned.
-
-## Alternatives to Daemon Set
-
-### Init Scripts
-
-It is certainly possible to run daemon processes by directly starting them on a node (e.g using
-`init`, `upstartd`, or `systemd`).  This is perfectly fine.  However, there are several advantages to
-running such processes via a DaemonSet:
-
-- Ability to monitor and manage logs for daemons in the same way as applications.
-- Same config language and tools (e.g. pod templates, `kubectl`) for daemons and applications.
-- Future versions of Kubernetes will likely support integration between DaemonSet-created
-  pods and node upgrade workflows.
-- Running daemons in containers with resource limits increases isolation between daemons from app
-  containers.  However, this can also be accomplished by running the daemons in a container but not in a pod
-  (e.g. start directly via Docker).
-
-### Bare Pods
-
-It is possible to create pods directly which specify a particular node to run on.  However,
-a Daemon Set replaces pods that are deleted or terminated for any reason, such as in the case of
-node failure or disruptive node maintenance, such as a kernel upgrade. For this reason, you should
-use a Daemon Set rather than creating individual pods.
-
-### Static Pods
-
-It is possible to create pods by writing a file to a certain directory watched by Kubelet.  These
-are called [static pods](/{{page.version}}/docs/admin/static-pods).
-Unlike DaemonSet, static pods cannot be managed with kubectl
-or other Kubernetes API clients.  Static pods do not depend on the apiserver, making them useful
-in cluster bootstrapping cases.  Also, static pods may be deprecated in the future.
-
-### Replication Controller
-
-Daemon Set are similar to [Replication Controllers](/{{page.version}}/docs/user-guide/replication-controller) in that
-they both create pods, and those pods have processes which are not expected to terminate (e.g. web servers,
-storage servers).
-
-Use a replication controller for stateless services, like frontends, where scaling up and down the
-number of replicas and rolling out updates are more important than controlling exactly which host
-the pod runs on.  Use a Daemon Controller when it is important that a copy of a pod always run on
-all or certain hosts, and when it needs to start before other pods.
-
-## Caveats
-
-DaemonSet objects are in the [`extensions` API Group](/{{page.version}}/docs/api/#api-groups).
-DaemonSet is not enabled by default. Enable it by setting
-`--runtime-config=extensions/v1beta1/daemonsets=true` on the api server. This can be
-achieved by exporting ENABLE_DAEMONSETS=true before running kube-up.sh script
-on GCE.
-
-DaemonSet objects effectively have [API version `v1alpha1`](/{{page.version}}/docs/api/)#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.
\ No newline at end of file
diff --git a/v1.2/docs/admin/dns.md b/v1.2/docs/admin/dns.md
deleted file mode 100644
index 714c8bcf8b..0000000000
--- a/v1.2/docs/admin/dns.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
----
-
-As of Kubernetes 0.8, DNS is offered as a [cluster add-on](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/README.md).
-If enabled, a DNS Pod and Service will be scheduled on the cluster, and the kubelets will be
-configured to tell individual containers to use the DNS Service's IP to resolve DNS names.
-
-Every Service defined in the cluster (including the DNS server itself) will be
-assigned a DNS name.  By default, a client Pod's DNS search list will
-include the Pod's own namespace and the cluster's default domain.  This is best
-illustrated by example:
-
-Assume a Service named `foo` in the Kubernetes namespace `bar`.  A Pod running
-in namespace `bar` can look up this service by simply doing a DNS query for
-`foo`.  A Pod running in namespace `quux` can look up this service by doing a
-DNS query for `foo.bar`.
-
-The cluster DNS server ([SkyDNS](https://github.com/skynetservices/skydns))
-supports forward lookups (A records) and service lookups (SRV records).
-
-## How it Works
-
-The running DNS pod holds 3 containers - skydns, etcd (a private instance which skydns uses),
-and a Kubernetes-to-skydns bridge called kube2sky.  The kube2sky process
-watches the Kubernetes master for changes in Services, and then writes the
-information to etcd, which skydns reads.  This etcd instance is not linked to
-any other etcd clusters that might exist, including the Kubernetes master.
-
-## Issues
-
-The skydns service is reachable directly from Kubernetes nodes (outside
-of any container) and DNS resolution works if the skydns service is targeted
-explicitly. However, nodes are not configured to use the cluster DNS service or
-to search the cluster's DNS domain by default.  This may be resolved at a later
-time.
-
-## For more information
-
-See [the docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/README.md).
\ No newline at end of file
diff --git a/v1.2/docs/admin/etcd.md b/v1.2/docs/admin/etcd.md
deleted file mode 100644
index e3cb1aa980..0000000000
--- a/v1.2/docs/admin/etcd.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
----
-
-[etcd](https://coreos.com/etcd/docs/2.0.12/) is a highly-available key value
-store which Kubernetes uses for persistent storage of all of its REST API
-objects.
-
-## Configuration: high-level goals
-
-Access Control: give *only* kube-apiserver read/write access to etcd. You do not
-want apiserver's etcd exposed to every node in your cluster (or worse, to the
-internet at large), because access to etcd is equivalent to root in your
-cluster.
-
-Data Reliability: for reasonable safety, either etcd needs to be run as a
-[cluster](/{{page.version}}/docs/admin/high-availability/#clustering-etcd) (multiple machines each running
-etcd) or etcd's data directory should be located on durable storage (e.g., GCE's
-persistent disk). In either case, if high availability is required--as it might
-be in a production cluster--the data directory ought to be [backed up
-periodically](https://coreos.com/etcd/docs/2.0.12/admin_guide/#disaster-recovery),
-to reduce downtime in case of corruption.
-
-## Default configuration
-
-The default setup scripts use kubelet's file-based static pods feature to run etcd in a
-[pod](http://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/salt/etcd/etcd.manifest). This manifest should only
-be run on master VMs. The default location that kubelet scans for manifests is
-`/etc/kubernetes/manifests/`.
-
-## Kubernetes's usage of etcd
-
-By default, Kubernetes objects are stored under the `/registry` key in etcd.
-This path can be prefixed by using the [kube-apiserver](/{{page.version}}/docs/admin/kube-apiserver) flag
-`--etcd-prefix="/foo"`.
-
-`etcd` is the only place that Kubernetes keeps state.
-
-## Troubleshooting
-
-To test whether `etcd` is running correctly, you can try writing a value to a
-test key. On your master VM (or somewhere with firewalls configured such that
-you can talk to your cluster's etcd), try:
-
-```shell
-curl -fs -X PUT "http://${host}:${port}/v2/keys/_test"
-```
diff --git a/v1.2/docs/admin/garbage-collection.md b/v1.2/docs/admin/garbage-collection.md
deleted file mode 100644
index 15b1232ae0..0000000000
--- a/v1.2/docs/admin/garbage-collection.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
----
-
-Garbage collection is managed by kubelet automatically, mainly including unreferenced
-images and dead containers. kubelet applies container garbage collection every minute
-and image garbage collection every 5 minutes.
-Note that we don't recommend external garbage collection tool generally, since it could
-break the behavior of kubelet potentially if it attempts to remove all of the containers
-which acts as the tombstone kubelet relies on. Yet those garbage collector aims to deal
-with the docker leaking issues would be appreciated.
-
-### Image Collection
-
-kubernetes manages lifecycle of all images through imageManager, with the cooperation
-of cadvisor.
-The policy for garbage collecting images we apply takes two factors into consideration,
-`HighThresholdPercent` and `LowThresholdPercent`. Disk usage above the the high threshold
-will trigger garbage collection, which attempts to delete unused images until the low
-threshold is met. Least recently used images are deleted first.
-
-### Container Collection
-
-The policy for garbage collecting containers we apply takes on three variables, which can
-be user-defined. `MinAge` is the minimum age at which a container can be garbage collected,
-zero for no limit. `MaxPerPodContainer` is the max number of dead containers any single
-pod (UID, container name) pair is allowed to have, less than zero for no limit.
-`MaxContainers` is the max number of total dead containers, less than zero for no limit as well.
-
-kubelet sorts out containers which are unidentified or stay out of bounds set by previous
-mentioned three flags. Gernerally the oldest containers are removed first. Since we take both
-`MaxPerPodContainer` and `MaxContainers` into consideration, it could happen when they
-have conflict -- retaining the max number of containers per pod goes out of range set by max
-number of global dead containers. In this case, we would sacrifice the `MaxPerPodContainer`
-a little bit. For the worst case, we first downgrade it to 1 container per pod, and then
-evict the oldest containers for the greater good.
-
-When kubelet removes the dead containers, all the files inside the container will be cleaned up as well.
-Note that we will skip the containers that are not managed by kubelet.
-
-### User Configuration
-
-Users are free to set their own value to address image garbage collection.
-
-1. `image-gc-high-threshold`, the percent of disk usage which triggers image garbage collection.
-Default is 90%.
-2. `image-gc-low-threshold`, the percent of disk usage to which image garbage collection attempts
-to free. Default is 80%.
-
-We also allow users to customize garbage collection policy, basically via following three flags.
-
-1. `minimum-container-ttl-duration`, minimum age for a finished container before it is
-garbage collected. Default is 1 minute.
-2. `maximum-dead-containers-per-container`, maximum number of old instances to retain
-per container. Default is 2.
-3. `maximum-dead-containers`, maximum number of old instances of containers to retain globally.
-Default is 100.
-
-Note that we highly recommend a large enough value for `maximum-dead-containers-per-container`
-to allow at least 2 dead containers retaining per expected container when you customize the flag
-configuration. A loose value for `maximum-dead-containers` also assumes importance for a similar reason.
-See [this issue](https://github.com/kubernetes/kubernetes/issues/13287) for more details.
diff --git a/v1.2/docs/admin/high-availability.md b/v1.2/docs/admin/high-availability.md
deleted file mode 100644
index 0d28e3dad6..0000000000
--- a/v1.2/docs/admin/high-availability.md
+++ /dev/null
@@ -1,227 +0,0 @@
----
----
-
-This document describes how to build a high-availability (HA) Kubernetes cluster.  This is a fairly advanced topic.
-Users who merely want to experiment with Kubernetes are encouraged to use configurations that are simpler to set up such as
-the simple [Docker based single node cluster instructions](/{{page.version}}/docs/getting-started-guides/docker),
-or try [Google Container Engine](https://cloud.google.com/container-engine/) for hosted Kubernetes.
-
-Also, at this time high availability support for Kubernetes is not continuously tested in our end-to-end (e2e) testing.  We will
-be working to add this continuous testing, but for now the single-node master installations are more heavily tested.
-
-* TOC
-{:toc}
-
-## Overview
-
-Setting up a truly reliable, highly available distributed system requires a number of steps, it is akin to
-wearing underwear, pants, a belt, suspenders, another pair of underwear, and another pair of pants.  We go into each
-of these steps in detail, but a summary is given here to help guide and orient the user.
-
-The steps involved are as follows:
-
-   * [Creating the reliable constituent nodes that collectively form our HA master implementation.](#reliable-nodes)
-   * [Setting up a redundant, reliable storage layer with clustered etcd.](#establishing-a-redundant-reliable-data-storage-layer)
-   * [Starting replicated, load balanced Kubernetes API servers](#replicated-api-servers)
-   * [Setting up master-elected Kubernetes scheduler and controller-manager daemons](#master-elected-components)
-
-Here's what the system should look like when it's finished:
-![High availability Kubernetes diagram](/images/docs/ha.svg)
-
-Ready? Let's get started.
-
-## Initial set-up
-
-The remainder of this guide assumes that you are setting up a 3-node clustered master, where each machine is running some flavor of Linux.
-Examples in the guide are given for Debian distributions, but they should be easily adaptable to other distributions.
-Likewise, this set up should work whether you are running in a public or private cloud provider, or if you are running
-on bare metal.
-
-The easiest way to implement an HA Kubernetes cluster is to start with an existing single-master cluster.  The
-instructions at [https://get.k8s.io](https://get.k8s.io)
-describe easy installation for single-master clusters on a variety of platforms.
-
-## Reliable nodes
-
-On each master node, we are going to run a number of processes that implement the Kubernetes API.  The first step in making these reliable is
-to make sure that each automatically restarts when it fails.  To achieve this, we need to install a process watcher.  We choose to use
-the `kubelet` that we run on each of the worker nodes.  This is convenient, since we can use containers to distribute our binaries, we can
-establish resource limits, and introspect the resource usage of each daemon.  Of course, we also need something to monitor the kubelet
-itself (insert who watches the watcher jokes here).  For Debian systems, we choose monit, but there are a number of alternate
-choices. For example, on systemd-based systems (e.g. RHEL, CentOS), you can run 'systemctl enable kubelet'.
-
-If you are extending from a standard Kubernetes installation, the `kubelet` binary should already be present on your system.  You can run
-`which kubelet` to determine if the binary is in fact installed.  If it is not installed,
-you should install the [kubelet binary](https://storage.googleapis.com/kubernetes-release/release/v0.19.3/bin/linux/amd64/kubelet), the
-[kubelet init file](http://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/salt/kubelet/initd) and [high-availability/default-kubelet](/{{page.version}}/docs/admin/high-availability/default-kubelet)
-scripts.
-
-If you are using monit, you should also install the monit daemon (`apt-get install monit`) and the [high-availability/monit-kubelet](/{{page.version}}/docs/admin/high-availability/monit-kubelet) and
-[high-availability/monit-docker](/{{page.version}}/docs/admin/high-availability/monit-docker) configs.
-
-On systemd systems you `systemctl enable kubelet` and `systemctl enable docker`.
-
-
-## Establishing a redundant, reliable data storage layer
-
-The central foundation of a highly available solution is a redundant, reliable storage layer.  The number one rule of high-availability is
-to protect the data.  Whatever else happens, whatever catches on fire, if you have the data, you can rebuild.  If you lose the data, you're
-done.
-
-Clustered etcd already replicates your storage to all master instances in your cluster.  This means that to lose data, all three nodes would need
-to have their physical (or virtual) disks fail at the same time.  The probability that this occurs is relatively low, so for many people
-running a replicated etcd cluster is likely reliable enough.  You can add additional reliability by increasing the
-size of the cluster from three to five nodes.  If that is still insufficient, you can add
-[even more redundancy to your storage layer](#even-more-reliable-storage).
-
-### Clustering etcd
-
-The full details of clustering etcd are beyond the scope of this document, lots of details are given on the
-[etcd clustering page](https://github.com/coreos/etcd/blob/master/Documentation/clustering.md).  This example walks through
-a simple cluster set up, using etcd's built in discovery to build our cluster.
-
-First, hit the etcd discovery service to create a new token:
-
-```shell
-curl https://discovery.etcd.io/new?size=3
-```
-
-On each node, copy the [etcd.yaml](/{{page.version}}/docs/admin/high-availability/etcd.yaml) file into `/etc/kubernetes/manifests/etcd.yaml`
-
-The kubelet on each node actively monitors the contents of that directory, and it will create an instance of the `etcd`
-server from the definition of the pod specified in `etcd.yaml`.
-
-Note that in `etcd.yaml` you should substitute the token URL you got above for `${DISCOVERY_TOKEN}` on all three machines,
-and you should substitute a different name (e.g. `node-1`) for ${NODE_NAME} and the correct IP address
-for `${NODE_IP}` on each machine.
-
-
-#### Validating your cluster
-
-Once you copy this into all three nodes, you should have a clustered etcd set up.  You can validate with
-
-```shell
-etcdctl member list
-```
-
-and
-
-```shell
-etcdctl cluster-health
-```
-
-You can also validate that this is working with `etcdctl set foo bar` on one node, and `etcd get foo`
-on a different node.
-
-### Even more reliable storage
-
-Of course, if you are interested in increased data reliability, there are further options which makes the place where etcd
-installs it's data even more reliable than regular disks (belts *and* suspenders, ftw!).
-
-If you use a cloud provider, then they usually provide this
-for you, for example [Persistent Disk](https://cloud.google.com/compute/docs/disks/persistent-disks) on the Google Cloud Platform.  These
-are block-device persistent storage that can be mounted onto your virtual machine. Other cloud providers provide similar solutions.
-
-If you are running on physical machines, you can also use network attached redundant storage using an iSCSI or NFS interface.
-Alternatively, you can run a clustered file system like Gluster or Ceph.  Finally, you can also run a RAID array on each physical machine.
-
-Regardless of how you choose to implement it, if you chose to use one of these options, you should make sure that your storage is mounted
-to each machine.  If your storage is shared between the three masters in your cluster, you should create a different directory on the storage
-for each node.  Throughout these instructions, we assume that this storage is mounted to your machine in `/var/etcd/data`
-
-
-## Replicated API Servers
-
-Once you have replicated etcd set up correctly, we will also install the apiserver using the kubelet.
-
-### Installing configuration files
-
-First you need to create the initial log file, so that Docker mounts a file instead of a directory:
-
-```shell
-touch /var/log/kube-apiserver.log
-```
-
-Next, you need to create a `/srv/kubernetes/` directory on each node.  This directory includes:
-
-   * basic_auth.csv  - basic auth user and password
-   * ca.crt - Certificate Authority cert
-   * known_tokens.csv - tokens that entities (e.g. the kubelet) can use to talk to the apiserver
-   * kubecfg.crt - Client certificate, public key
-   * kubecfg.key - Client certificate, private key
-   * server.cert - Server certificate, public key
-   * server.key - Server certificate, private key
-
-The easiest way to create this directory, may be to copy it from the master node of a working cluster, or you can manually generate these files yourself.
-
-### Starting the API Server
-
-Once these files exist, copy the [kube-apiserver.yaml](/{{page.version}}/docs/admin/high-availability/kube-apiserver.yaml) into `/etc/kubernetes/manifests/` on each master node.
-
-The kubelet monitors this directory, and will automatically create an instance of the `kube-apiserver` container using the pod definition specified
-in the file.
-
-### Load balancing
-
-At this point, you should have 3 apiservers all working correctly.  If you set up a network load balancer, you should
-be able to access your cluster via that load balancer, and see traffic balancing between the apiserver instances.  Setting
-up a load balancer will depend on the specifics of your platform, for example instructions for the Google Cloud
-Platform can be found [here](https://cloud.google.com/compute/docs/load-balancing/)
-
-Note, if you are using authentication, you may need to regenerate your certificate to include the IP address of the balancer,
-in addition to the IP addresses of the individual nodes.
-
-For pods that you deploy into the cluster, the `kubernetes` service/dns name should provide a load balanced endpoint for the master automatically.
-
-For external users of the API (e.g. the `kubectl` command line interface, continuous build pipelines, or other clients) you will want to configure
-them to talk to the external load balancer's IP address.
-
-## Master elected components
-
-So far we have set up state storage, and we have set up the API server, but we haven't run anything that actually modifies
-cluster state, such as the controller manager and scheduler.  To achieve this reliably, we only want to have one actor modifying state at a time, but we want replicated
-instances of these actors, in case a machine dies.  To achieve this, we are going to use a lease-lock in etcd to perform
-master election.  On each of the three apiserver nodes, we run a small utility application named `podmaster`. It's job is to implement a master
-election protocol using etcd "compare and swap". If the apiserver node wins the election, it starts the master component it is managing (e.g. the scheduler), if it
-loses the election, it ensures that any master components running on the node (e.g. the scheduler) are stopped.
-
-In the future, we expect to more tightly integrate this lease-locking into the scheduler and controller-manager binaries directly, as described in the [high availability design proposal](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/proposals/high-availability.md)
-
-### Installing configuration files
-
-First, create empty log files on each node, so that Docker will mount the files not make new directories:
-
-```shell
-touch /var/log/kube-scheduler.log
-touch /var/log/kube-controller-manager.log
-```
-
-Next, set up the descriptions of the scheduler and controller manager pods on each node.
-by copying [kube-scheduler.yaml](/{{page.version}}/docs/admin/high-availability/kube-scheduler.yaml) and [kube-controller-manager.yaml](high-availability//{{page.version}}/docs/admin/kube-controller-manager.yaml) into the `/srv/kubernetes/` directory.
-
-### Running the podmaster
-
-Now that the configuration files are in place, copy the [podmaster.yaml](/{{page.version}}/docs/admin/high-availability/podmaster.yaml) config file into `/etc/kubernetes/manifests/`
-
-As before, the kubelet on the node monitors this directory, and will start an instance of the podmaster using the pod specification provided in `podmaster.yaml`.
-
-Now you will have one instance of the scheduler process running on a single master node, and likewise one
-controller-manager process running on a single (possibly different) master node.  If either of these processes fail,
-the kubelet will restart them.  If any of these nodes fail, the process will move to a different instance of a master
-node.
-
-## Conclusion
-
-At this point, you are done (yeah!) with the master components, but you still need to add worker nodes (boo!).
-
-If you have an existing cluster, this is as simple as reconfiguring your kubelets to talk to the load-balanced endpoint, and
-restarting the kubelets on each node.
-
-If you are turning up a fresh cluster, you will need to install the kubelet and kube-proxy on each worker node, and
-set the `--apiserver` flag to your replicated endpoint.
-
-## Vagrant up!
-
-We indeed have an initial proof of concept tester for this, which is available [here](https://releases.k8s.io/{{page.githubbranch}}/examples/high-availability).
-
-It implements the major concepts (with a few minor reductions for simplicity), of the podmaster HA implementation alongside a quick smoke test using k8petstore.
diff --git a/v1.2/docs/admin/high-availability/default-kubelet b/v1.2/docs/admin/high-availability/default-kubelet
deleted file mode 100644
index 41ee530151..0000000000
--- a/v1.2/docs/admin/high-availability/default-kubelet
+++ /dev/null
@@ -1,8 +0,0 @@
-# This should be the IP address of the load balancer for all masters
-MASTER_IP=<insert-ip-here>
-# This should be the internal service IP address reserved for DNS
-DNS_IP=<insert-dns-ip-here>
-
-DAEMON_ARGS="$DAEMON_ARGS --api-servers=https://${MASTER_IP} --enable-debugging-handlers=true  --cloud-provider=
-gce --config=/etc/kubernetes/manifests --allow-privileged=False --v=2 --cluster-dns=${DNS_IP} --cluster-domain=c
-luster.local   --configure-cbr0=true --cgroup-root=/ --system-container=/system "
diff --git a/v1.2/docs/admin/high-availability/etcd.yaml b/v1.2/docs/admin/high-availability/etcd.yaml
deleted file mode 100644
index fc9fe67e75..0000000000
--- a/v1.2/docs/admin/high-availability/etcd.yaml
+++ /dev/null
@@ -1,87 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: etcd-server
-spec:
-  hostNetwork: true
-  containers:
-  - image: gcr.io/google_containers/etcd:2.0.9
-    name: etcd-container
-    command:
-    - /usr/local/bin/etcd
-    - --name
-    - ${NODE_NAME}
-    - --initial-advertise-peer-urls
-    - http://${NODE_IP}:2380
-    - --listen-peer-urls
-    - http://${NODE_IP}:2380
-    - --advertise-client-urls
-    - http://${NODE_IP}:4001
-    - --listen-client-urls
-    - http://127.0.0.1:4001
-    - --data-dir
-    - /var/etcd/data
-    - --discovery
-    - ${DISCOVERY_TOKEN}
-    ports:
-    - containerPort: 2380
-      hostPort: 2380
-      name: serverport
-    - containerPort: 4001
-      hostPort: 4001
-      name: clientport
-    volumeMounts:
-    - mountPath: /var/etcd
-      name: varetcd
-    - mountPath: /etc/ssl
-      name: etcssl
-      readOnly: true
-    - mountPath: /usr/share/ssl
-      name: usrsharessl
-      readOnly: true
-    - mountPath: /var/ssl
-      name: varssl
-      readOnly: true
-    - mountPath: /usr/ssl
-      name: usrssl
-      readOnly: true
-    - mountPath: /usr/lib/ssl
-      name: usrlibssl
-      readOnly: true
-    - mountPath: /usr/local/openssl
-      name: usrlocalopenssl
-      readOnly: true
-    - mountPath: /etc/openssl
-      name: etcopenssl
-      readOnly: true
-    - mountPath: /etc/pki/tls
-      name: etcpkitls
-      readOnly: true
-  volumes:
-  - hostPath:
-      path: /var/etcd/data
-    name: varetcd
-  - hostPath:
-      path: /etc/ssl
-    name: etcssl
-  - hostPath:
-      path: /usr/share/ssl
-    name: usrsharessl
-  - hostPath:
-      path: /var/ssl
-    name: varssl
-  - hostPath:
-      path: /usr/ssl
-    name: usrssl
-  - hostPath:
-      path: /usr/lib/ssl
-    name: usrlibssl
-  - hostPath:
-      path: /usr/local/openssl
-    name: usrlocalopenssl
-  - hostPath:
-      path: /etc/openssl
-    name: etcopenssl
-  - hostPath:
-      path: /etc/pki/tls
-    name: etcpkitls
diff --git a/v1.2/docs/admin/high-availability/kube-apiserver.yaml b/v1.2/docs/admin/high-availability/kube-apiserver.yaml
deleted file mode 100644
index 33d5cff5cd..0000000000
--- a/v1.2/docs/admin/high-availability/kube-apiserver.yaml
+++ /dev/null
@@ -1,90 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: kube-apiserver
-spec:
-  hostNetwork: true
-  containers:
-  - name: kube-apiserver
-    image: gcr.io/google_containers/kube-apiserver:9680e782e08a1a1c94c656190011bd02
-    command:
-    - /bin/sh
-    - -c
-    - /usr/local/bin/kube-apiserver --address=127.0.0.1 --etcd-servers=http://127.0.0.1:4001
-      --cloud-provider=gce   --admission-control=NamespaceLifecycle,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota
-      --service-cluster-ip-range=10.0.0.0/16 --client-ca-file=/srv/kubernetes/ca.crt
-      --basic-auth-file=/srv/kubernetes/basic_auth.csv --cluster-name=e2e-test-bburns
-      --tls-cert-file=/srv/kubernetes/server.cert --tls-private-key-file=/srv/kubernetes/server.key
-      --secure-port=443 --token-auth-file=/srv/kubernetes/known_tokens.csv  --v=2
-      --allow-privileged=False 1>>/var/log/kube-apiserver.log 2>&1
-    ports:
-    - containerPort: 443
-      hostPort: 443
-      name: https
-    - containerPort: 7080
-      hostPort: 7080
-      name: http
-    - containerPort: 8080
-      hostPort: 8080
-      name: local
-    volumeMounts:
-    - mountPath: /srv/kubernetes
-      name: srvkube
-      readOnly: true
-    - mountPath: /var/log/kube-apiserver.log
-      name: logfile
-    - mountPath: /etc/ssl
-      name: etcssl
-      readOnly: true
-    - mountPath: /usr/share/ssl
-      name: usrsharessl
-      readOnly: true
-    - mountPath: /var/ssl
-      name: varssl
-      readOnly: true
-    - mountPath: /usr/ssl
-      name: usrssl
-      readOnly: true
-    - mountPath: /usr/lib/ssl
-      name: usrlibssl
-      readOnly: true
-    - mountPath: /usr/local/openssl
-      name: usrlocalopenssl
-      readOnly: true
-    - mountPath: /etc/openssl
-      name: etcopenssl
-      readOnly: true
-    - mountPath: /etc/pki/tls
-      name: etcpkitls
-      readOnly: true
-  volumes:
-  - hostPath:
-      path: /srv/kubernetes
-    name: srvkube
-  - hostPath:
-      path: /var/log/kube-apiserver.log
-    name: logfile
-  - hostPath:
-      path: /etc/ssl
-    name: etcssl
-  - hostPath:
-      path: /usr/share/ssl
-    name: usrsharessl
-  - hostPath:
-      path: /var/ssl
-    name: varssl
-  - hostPath:
-      path: /usr/ssl
-    name: usrssl
-  - hostPath:
-      path: /usr/lib/ssl
-    name: usrlibssl
-  - hostPath:
-      path: /usr/local/openssl
-    name: usrlocalopenssl
-  - hostPath:
-      path: /etc/openssl
-    name: etcopenssl
-  - hostPath:
-      path: /etc/pki/tls
-    name: etcpkitls
diff --git a/v1.2/docs/admin/high-availability/kube-controller-manager.yaml b/v1.2/docs/admin/high-availability/kube-controller-manager.yaml
deleted file mode 100644
index 736181fc7c..0000000000
--- a/v1.2/docs/admin/high-availability/kube-controller-manager.yaml
+++ /dev/null
@@ -1,82 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: kube-controller-manager
-spec:
-  containers:
-  - command:
-    - /bin/sh
-    - -c
-    - /usr/local/bin/kube-controller-manager --master=127.0.0.1:8080 --cluster-name=e2e-test-bburns
-      --cluster-cidr=10.245.0.0/16 --allocate-node-cidrs=true --cloud-provider=gce  --service-account-private-key-file=/srv/kubernetes/server.key
-      --v=2 1>>/var/log/kube-controller-manager.log 2>&1
-    image: gcr.io/google_containers/kube-controller-manager:fda24638d51a48baa13c35337fcd4793
-    livenessProbe:
-      httpGet:
-        path: /healthz
-        port: 10252
-      initialDelaySeconds: 15
-      timeoutSeconds: 1
-    name: kube-controller-manager
-    volumeMounts:
-    - mountPath: /srv/kubernetes
-      name: srvkube
-      readOnly: true
-    - mountPath: /var/log/kube-controller-manager.log
-      name: logfile
-    - mountPath: /etc/ssl
-      name: etcssl
-      readOnly: true
-    - mountPath: /usr/share/ssl
-      name: usrsharessl
-      readOnly: true
-    - mountPath: /var/ssl
-      name: varssl
-      readOnly: true
-    - mountPath: /usr/ssl
-      name: usrssl
-      readOnly: true
-    - mountPath: /usr/lib/ssl
-      name: usrlibssl
-      readOnly: true
-    - mountPath: /usr/local/openssl
-      name: usrlocalopenssl
-      readOnly: true
-    - mountPath: /etc/openssl
-      name: etcopenssl
-      readOnly: true
-    - mountPath: /etc/pki/tls
-      name: etcpkitls
-      readOnly: true
-  hostNetwork: true
-  volumes:
-  - hostPath:
-      path: /srv/kubernetes
-    name: srvkube
-  - hostPath:
-      path: /var/log/kube-controller-manager.log
-    name: logfile
-  - hostPath:
-      path: /etc/ssl
-    name: etcssl
-  - hostPath:
-      path: /usr/share/ssl
-    name: usrsharessl
-  - hostPath:
-      path: /var/ssl
-    name: varssl
-  - hostPath:
-      path: /usr/ssl
-    name: usrssl
-  - hostPath:
-      path: /usr/lib/ssl
-    name: usrlibssl
-  - hostPath:
-      path: /usr/local/openssl
-    name: usrlocalopenssl
-  - hostPath:
-      path: /etc/openssl
-    name: etcopenssl
-  - hostPath:
-      path: /etc/pki/tls
-    name: etcpkitls
diff --git a/v1.2/docs/admin/high-availability/kube-scheduler.yaml b/v1.2/docs/admin/high-availability/kube-scheduler.yaml
deleted file mode 100644
index 1b23ee1bb8..0000000000
--- a/v1.2/docs/admin/high-availability/kube-scheduler.yaml
+++ /dev/null
@@ -1,30 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: kube-scheduler
-spec:
-  hostNetwork: true
-  containers:
-  - name: kube-scheduler
-    image: gcr.io/google_containers/kube-scheduler:34d0b8f8b31e27937327961528739bc9
-    command:
-    - /bin/sh
-    - -c
-    - /usr/local/bin/kube-scheduler --master=127.0.0.1:8080 --v=2 1>>/var/log/kube-scheduler.log
-      2>&1
-    livenessProbe:
-      httpGet:
-        path: /healthz
-        port: 10251
-      initialDelaySeconds: 15
-      timeoutSeconds: 1
-    volumeMounts:
-    - mountPath: /var/log/kube-scheduler.log
-      name: logfile
-    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
-      name: default-token-s8ejd
-      readOnly: true
-  volumes:
-  - hostPath:
-      path: /var/log/kube-scheduler.log
-    name: logfile
diff --git a/v1.2/docs/admin/high-availability/monit-docker b/v1.2/docs/admin/high-availability/monit-docker
deleted file mode 100644
index 8c2753a430..0000000000
--- a/v1.2/docs/admin/high-availability/monit-docker
+++ /dev/null
@@ -1,9 +0,0 @@
-check process docker with pidfile /var/run/docker.pid
-group docker
-start program = "/etc/init.d/docker start"
-stop program = "/etc/init.d/docker stop"
-if does not exist then restart
-if failed
-  unixsocket /var/run/docker.sock
-  protocol HTTP request "/version"
-then restart
\ No newline at end of file
diff --git a/v1.2/docs/admin/high-availability/monit-kubelet b/v1.2/docs/admin/high-availability/monit-kubelet
deleted file mode 100644
index eb3211b06a..0000000000
--- a/v1.2/docs/admin/high-availability/monit-kubelet
+++ /dev/null
@@ -1,11 +0,0 @@
-check process kubelet with pidfile /var/run/kubelet.pid
-group kubelet
-start program = "/etc/init.d/kubelet start"
-stop program = "/etc/init.d/kubelet stop"
-if does not exist then restart
-if failed
-  host 127.0.0.1
-  port 10255
-  protocol HTTP
-  request "/healthz"
-then restart
diff --git a/v1.2/docs/admin/high-availability/podmaster.yaml b/v1.2/docs/admin/high-availability/podmaster.yaml
deleted file mode 100644
index d634225b93..0000000000
--- a/v1.2/docs/admin/high-availability/podmaster.yaml
+++ /dev/null
@@ -1,43 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: scheduler-master
-spec:
-  hostNetwork: true
-  containers:
-  - name: scheduler-elector
-    image: gcr.io/google_containers/podmaster:1.1
-    command:
-    - /podmaster
-    - --etcd-servers=http://127.0.0.1:4001
-    - --key=scheduler
-    - --source-file=/kubernetes/kube-scheduler.manifest
-    - --dest-file=/manifests/kube-scheduler.manifest
-    volumeMounts:
-    - mountPath: /kubernetes
-      name: k8s
-      readOnly: true
-    - mountPath: /manifests
-      name: manifests
-  - name: controller-manager-elector
-    image: gcr.io/google_containers/podmaster:1.1
-    command:
-    - /podmaster
-    - --etcd-servers=http://127.0.0.1:4001
-    - --key=controller
-    - --source-file=/kubernetes/kube-controller-manager.manifest
-    - --dest-file=/manifests/kube-controller-manager.manifest
-    terminationMessagePath: /dev/termination-log
-    volumeMounts:
-    - mountPath: /kubernetes
-      name: k8s
-      readOnly: true
-    - mountPath: /manifests
-      name: manifests
-  volumes:
-  - hostPath:
-      path: /srv/kubernetes
-    name: k8s
-  - hostPath:
-      path: /etc/kubernetes/manifests
-    name: manifests
diff --git a/v1.2/docs/admin/limitrange/index.md b/v1.2/docs/admin/limitrange/index.md
deleted file mode 100644
index 5475b8fc32..0000000000
--- a/v1.2/docs/admin/limitrange/index.md
+++ /dev/null
@@ -1,194 +0,0 @@
----
----
-
-By default, pods run with unbounded CPU and memory limits.  This means that any pod in the
-system will be able to consume as much CPU and memory on the node that executes the pod.
-
-Users may want to impose restrictions on the amount of resource a single pod in the system may consume
-for a variety of reasons.
-
-For example:
-
-1. Each node in the cluster has 2GB of memory.  The cluster operator does not want to accept pods
-that require more than 2GB of memory since no node in the cluster can support the requirement.  To prevent a
-pod from being permanently unscheduled to a node, the operator instead chooses to reject pods that exceed 2GB
-of memory as part of admission control.
-2. A cluster is shared by two communities in an organization that runs production and development workloads
-respectively.  Production workloads may consume up to 8GB of memory, but development workloads may consume up
-to 512MB of memory.  The cluster operator creates a separate namespace for each workload, and applies limits to
-each namespace.
-3. Users may create a pod which consumes resources just below the capacity of a machine.  The left over space
-may be too small to be useful, but big enough for the waste to be costly over the entire cluster.  As a result,
-the cluster operator may want to set limits that a pod must consume at least 20% of the memory and cpu of their
-average node size in order to provide for more uniform scheduling and to limit waste.
-
-This example demonstrates how limits can be applied to a Kubernetes namespace to control
-min/max resource limits per pod.  In addition, this example demonstrates how you can
-apply default resource limits to pods in the absence of an end-user specified value.
-
-See [LimitRange design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_limit_range.md) for more information. For a detailed description of the Kubernetes resource model, see [Resources](/{{page.version}}/docs/user-guide/compute-resources)
-
-## Step 0: Prerequisites
-
-This example requires a running Kubernetes cluster.  See the [Getting Started guides](/{{page.version}}/docs/getting-started-guides/) for how to get started.
-
-Change to the `<kubernetes>` directory if you're not already there.
-
-## Step 1: Create a namespace
-
-This example will work in a custom namespace to demonstrate the concepts involved.
-
-Let's create a new namespace called limit-example:
-
-```shell
-$ kubectl create -f docs/admin/limitrange/namespace.yaml
-namespace "limit-example" created
-$ kubectl get namespaces
-NAME            LABELS    STATUS    AGE
-default         <none>    Active    5m
-limit-example   <none>    Active    53s
-```
-
-## Step 2: Apply a limit to the namespace
-
-Let's create a simple limit in our namespace.
-
-```shell
-$ kubectl create -f docs/admin/limitrange/limits.yaml --namespace=limit-example
-limitrange "mylimits" created
-```
-
-Let's describe the limits that we have imposed in our namespace.
-
-```shell
-$ kubectl describe limits mylimits --namespace=limit-example
-Name:   mylimits
-Namespace:  limit-example
-Type        Resource      Min      Max      Request      Limit      Limit/Request
-----        --------      ---      ---      -------      -----      -------------
-Pod         cpu           200m     2        -            -          -
-Pod         memory        6Mi      1Gi      -            -          -
-Container   cpu           100m     2        200m         300m       -
-Container   memory        3Mi      1Gi      100Mi        200Mi      -
-```
-
-In this scenario, we have said the following:
-
-1. If a max constraint is specified for a resource (2 CPU and 1Gi memory in this case), then a limit
-must be specified for that resource across all containers. Failure to specify a limit will result in
-a validation error when attempting to create the pod. Note that a default value of limit is set by
-*default* in file `limits.yaml` (300m CPU and 200Mi memory).
-2. If a min constraint is specified for a resource (100m CPU and 3Mi memory in this case), then a
-request must be specified for that resource across all containers. Failure to specify a request will
-result in a validation error when attempting to create the pod. Note that a default value of request is
-set by *defaultRequest* in file `limits.yaml` (200m CPU and 100Mi memory).
-3. For any pod, the sum of all containers memory requests must be >= 6Mi and the sum of all containers
-memory limits must be <= 1Gi; the sum of all containers CPU requests must be >= 200m and the sum of all
-containers CPU limits must be <= 2.
-
-## Step 3: Enforcing limits at point of creation
-
-The limits enumerated in a namespace are only enforced when a pod is created or updated in
-the cluster.  If you change the limits to a different value range, it does not affect pods that
-were previously created in a namespace.
-
-If a resource (cpu or memory) is being restricted by a limit, the user will get an error at time
-of creation explaining why.
-
-Let's first spin up a replication controller that creates a single container pod to demonstrate
-how default values are applied to each pod.
-
-```shell
-$ kubectl run nginx --image=nginx --replicas=1 --namespace=limit-example
-replicationcontroller "nginx" created
-$ kubectl get pods --namespace=limit-example
-NAME          READY     STATUS    RESTARTS   AGE
-nginx-aq0mf   1/1       Running   0          35s
-$ kubectl get pods nginx-aq0mf --namespace=limit-example -o yaml | grep resources -C 8
-```
-
-```yaml
-resourceVersion: "127"
-  selfLink: /api/v1/namespaces/limit-example/pods/nginx-aq0mf
-  uid: 51be42a7-7156-11e5-9921-286ed488f785
-spec:
-  containers:
-  - image: nginx
-    imagePullPolicy: IfNotPresent
-    name: nginx
-    resources:
-      limits:
-        cpu: 300m
-        memory: 200Mi
-      requests:
-        cpu: 200m
-        memory: 100Mi
-    terminationMessagePath: /dev/termination-log
-    volumeMounts:
-```
-
-Note that our nginx container has picked up the namespace default cpu and memory resource *limits* and *requests*.
-
-Let's create a pod that exceeds our allowed limits by having it have a container that requests 3 cpu cores.
-
-```shell
-$ kubectl create -f docs/admin/limitrange/invalid-pod.yaml --namespace=limit-example
-Error from server: error when creating "docs/admin/limitrange/invalid-pod.yaml": Pod "invalid-pod" is forbidden: [Maximum cpu usage per Pod is 2, but limit is 3., Maximum cpu usage per Container is 2, but limit is 3.]
-```
-
-Let's create a pod that falls within the allowed limit boundaries.
-
-```shell
-$ kubectl create -f docs/admin/limitrange/valid-pod.yaml --namespace=limit-example
-pod "valid-pod" created
-$ kubectl get pods valid-pod --namespace=limit-example -o yaml | grep -C 6 resources
-```
-
-```yaml
-uid: 162a12aa-7157-11e5-9921-286ed488f785
-spec:
-  containers:
-  - image: gcr.io/google_containers/serve_hostname
-    imagePullPolicy: IfNotPresent
-    name: kubernetes-serve-hostname
-    resources:
-      limits:
-        cpu: "1"
-        memory: 512Mi
-      requests:
-        cpu: "1"
-        memory: 512Mi
-```
-
-Note that this pod specifies explicit resource *limits* and *requests* so it did not pick up the namespace
-default values.
-
-Note: The *limits* for CPU resource are not enforced in the default Kubernetes setup on the physical node
-that runs the container unless the administrator deploys the kubelet with the folllowing flag:
-
-```shell
-$ kubelet --help
-Usage of kubelet
-....
-  --cpu-cfs-quota[=false]: Enable CPU CFS quota enforcement for containers that specify CPU limits
-$ kubelet --cpu-cfs-quota=true ...
-```
-
-## Step 4: Cleanup
-
-To remove the resources used by this example, you can just delete the limit-example namespace.
-
-```shell
-$ kubectl delete namespace limit-example
-namespace "limit-example" deleted
-$ kubectl get namespaces
-NAME      LABELS    STATUS    AGE
-default   <none>    Active    20m
-```
-
-## Summary
-
-Cluster operators that want to restrict the amount of resources a single container or pod may consume
-are able to define allowable ranges per Kubernetes namespace.  In the absence of any explicit assignments,
-the Kubernetes system is able to apply default resource *limits* and *requests* if desired in order to
-constrain the amount of resource a pod consumes on a node.
\ No newline at end of file
diff --git a/v1.2/docs/admin/limitrange/invalid-pod.yaml b/v1.2/docs/admin/limitrange/invalid-pod.yaml
deleted file mode 100644
index b63f25deba..0000000000
--- a/v1.2/docs/admin/limitrange/invalid-pod.yaml
+++ /dev/null
@@ -1,12 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: invalid-pod
-spec:
-  containers:
-  - name: kubernetes-serve-hostname
-    image: gcr.io/google_containers/serve_hostname
-    resources:
-      limits:
-        cpu: "3"
-        memory: 100Mi
diff --git a/v1.2/docs/admin/limitrange/limits.yaml b/v1.2/docs/admin/limitrange/limits.yaml
deleted file mode 100644
index 5de4841705..0000000000
--- a/v1.2/docs/admin/limitrange/limits.yaml
+++ /dev/null
@@ -1,26 +0,0 @@
-apiVersion: v1
-kind: LimitRange
-metadata:
-  name: mylimits
-spec:
-  limits:
-  - max:
-      cpu: "2"
-      memory: 1Gi
-    min:
-      cpu: 200m
-      memory: 6Mi
-    type: Pod
-  - default:
-      cpu: 300m
-      memory: 200Mi
-    defaultRequest:
-      cpu: 200m
-      memory: 100Mi
-    max:
-      cpu: "2"
-      memory: 1Gi
-    min:
-      cpu: 100m
-      memory: 3Mi
-    type: Container
diff --git a/v1.2/docs/admin/limitrange/namespace.yaml b/v1.2/docs/admin/limitrange/namespace.yaml
deleted file mode 100644
index 200a894b0b..0000000000
--- a/v1.2/docs/admin/limitrange/namespace.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-apiVersion: v1
-kind: Namespace
-metadata:
-  name: limit-example
diff --git a/v1.2/docs/admin/limitrange/valid-pod.yaml b/v1.2/docs/admin/limitrange/valid-pod.yaml
deleted file mode 100644
index c1ec54183b..0000000000
--- a/v1.2/docs/admin/limitrange/valid-pod.yaml
+++ /dev/null
@@ -1,14 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: valid-pod
-  labels:
-    name: valid-pod
-spec:
-  containers:
-  - name: kubernetes-serve-hostname
-    image: gcr.io/google_containers/serve_hostname
-    resources:
-      limits:
-        cpu: "1"
-        memory: 512Mi
diff --git a/v1.2/docs/admin/multi-cluster.md b/v1.2/docs/admin/multi-cluster.md
deleted file mode 100644
index caeb8fbfb8..0000000000
--- a/v1.2/docs/admin/multi-cluster.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
----
-
-You may want to set up multiple Kubernetes clusters, both to
-have clusters in different regions to be nearer to your users, and to tolerate failures and/or invasive maintenance.
-This document describes some of the issues to consider when making a decision about doing so.
-
-Note that at present,
-Kubernetes does not offer a mechanism to aggregate multiple clusters into a single virtual cluster. However,
-we [plan to do this in the future](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/proposals/federation.md).
-
-## Scope of a single cluster
-
-On IaaS providers such as Google Compute Engine or Amazon Web Services, a VM exists in a
-[zone](https://cloud.google.com/compute/docs/zones) or [availability
-zone](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones).
-
-We suggest that all the VMs in a Kubernetes cluster should be in the same availability zone, because:
-
-  - compared to having a single global Kubernetes cluster, there are fewer single-points of failure
-  - compared to a cluster that spans availability zones, it is easier to reason about the availability properties of a
-    single-zone cluster.
-  - when the Kubernetes developers are designing the system (e.g. making assumptions about latency, bandwidth, or
-    correlated failures) they are assuming all the machines are in a single data center, or otherwise closely connected.
-
-It is okay to have multiple clusters per availability zone, though on balance we think fewer is better.
-Reasons to prefer fewer clusters are:
-
-  - improved bin packing of Pods in some cases with more nodes in one cluster (less resource fragmentation)
-  - reduced operational overhead (though the advantage is diminished as ops tooling and processes matures)
-  - reduced costs for per-cluster fixed resource costs, e.g. apiserver VMs (but small as a percentage
-    of overall cluster cost for medium to large clusters).
-
-Reasons to have multiple clusters include:
-
-  - strict security policies requiring isolation of one class of work from another (but, see Partitioning Clusters
-    below).
-  - test clusters to canary new Kubernetes releases or other cluster software.
-
-## Selecting the right number of clusters
-
-The selection of the number of Kubernetes clusters may be a relatively static choice, only revisited occasionally.
-By contrast, the number of nodes in a cluster and the number of pods in a service may be change frequently according to
-load and growth.
-
-To pick the number of clusters, first, decide which regions you need to be in to have adequate latency to all your end users, for services that will run
-on Kubernetes (if you use a Content Distribution Network, the latency requirements for the CDN-hosted content need not
-be considered).  Legal issues might influence this as well. For example, a company with a global customer base might decide to have clusters in US, EU, AP, and SA regions.
-Call the number of regions to be in `R`.
-
-Second, decide how many clusters should be able to be unavailable at the same time, while still being available.  Call
-the number that can be unavailable `U`.  If you are not sure, then 1 is a fine choice.
-
-If it is allowable for load-balancing to direct traffic to any region in the event of a cluster failure, then
-you need `R + U` clusters.  If it is not (e.g you want to ensure low latency for all users in the event of a
-cluster failure), then you need to have `R * U` clusters (`U` in each of `R` regions).  In any case, try to put each cluster in a different zone.
-
-Finally, if any of your clusters would need more than the maximum recommended number of nodes for a Kubernetes cluster, then
-you may need even more clusters.  Kubernetes v1.0 currently supports clusters up to 100 nodes in size, but we are targeting
-1000-node clusters by early 2016.
-
-## Working with multiple clusters
-
-When you have multiple clusters, you would typically create services with the same config in each cluster and put each of those
-service instances behind a load balancer (AWS Elastic Load Balancer, GCE Forwarding Rule or HTTP Load Balancer) spanning all of them, so that
-failures of a single cluster are not visible to end users.
\ No newline at end of file
diff --git a/v1.2/docs/admin/namespaces/namespace-dev.json b/v1.2/docs/admin/namespaces/namespace-dev.json
deleted file mode 100644
index b2b43b0b73..0000000000
--- a/v1.2/docs/admin/namespaces/namespace-dev.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
-  "kind": "Namespace",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "development",
-    "labels": {
-      "name": "development"
-    }
-  }
-}
diff --git a/v1.2/docs/admin/namespaces/namespace-prod.json b/v1.2/docs/admin/namespaces/namespace-prod.json
deleted file mode 100644
index d4503f1ac1..0000000000
--- a/v1.2/docs/admin/namespaces/namespace-prod.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
-  "kind": "Namespace",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "production",
-    "labels": {
-      "name": "production"
-    }
-  }
-}
diff --git a/v1.2/docs/admin/networking.md b/v1.2/docs/admin/networking.md
deleted file mode 100644
index 9fd86e9c1e..0000000000
--- a/v1.2/docs/admin/networking.md
+++ /dev/null
@@ -1,184 +0,0 @@
----
----
-
-Kubernetes approaches networking somewhat differently than Docker does by
-default.  There are 4 distinct networking problems to solve:
-
-1. Highly-coupled container-to-container communications: this is solved by
-   [pods](/{{page.version}}/docs/user-guide/pods) and `localhost` communications.
-2. Pod-to-Pod communications: this is the primary focus of this document.
-3. Pod-to-Service communications: this is covered by [services](/{{page.version}}/docs/user-guide/services).
-4. External-to-Service communications: this is covered by [services](/{{page.version}}/docs/user-guide/services).
-
-* TOC
-{:toc}
-
-
-## Summary
-
-Kubernetes assumes that pods can communicate with other pods, regardless of
-which host they land on.  We give every pod its own IP address so you do not
-need to explicitly create links between pods and you almost never need to deal
-with mapping container ports to host ports.  This creates a clean,
-backwards-compatible model where pods can be treated much like VMs or physical
-hosts from the perspectives of port allocation, naming, service discovery, load
-balancing, application configuration, and migration.
-
-To achieve this we must impose some requirements on how you set up your cluster
-networking.
-
-## Docker model
-
-Before discussing the Kubernetes approach to networking, it is worthwhile to
-review the "normal" way that networking works with Docker.  By default, Docker
-uses host-private networking.  It creates a virtual bridge, called `docker0` by
-default, and allocates a subnet from one of the private address blocks defined
-in [RFC1918](https://tools.ietf.org/html/rfc1918) for that bridge.  For each
-container that Docker creates, it allocates a virtual ethernet device (called
-`veth`) which is attached to the bridge. The veth is mapped to appear as `eth0`
-in the container, using Linux namespaces.  The in-container `eth0` interface is
-given an IP address from the bridge's address range.
-
-The result is that Docker containers can talk to other containers only if they
-are on the same machine (and thus the same virtual bridge).  Containers on
-different machines can not reach each other - in fact they may end up with the
-exact same network ranges and IP addresses.
-
-In order for Docker containers to communicate across nodes, they must be
-allocated ports on the machine's own IP address, which are then forwarded or
-proxied to the containers.  This obviously means that containers must either
-coordinate which ports they use very carefully or else be allocated ports
-dynamically.
-
-## Kubernetes model
-
-Coordinating ports across multiple developers is very difficult to do at
-scale and exposes users to cluster-level issues outside of their control.
-Dynamic port allocation brings a lot of complications to the system - every
-application has to take ports as flags, the API servers have to know how to
-insert dynamic port numbers into configuration blocks, services have to know
-how to find each other, etc.  Rather than deal with this, Kubernetes takes a
-different approach.
-
-Kubernetes imposes the following fundamental requirements on any networking
-implementation (barring any intentional network segmentation policies):
-
-   * all containers can communicate with all other containers without NAT
-   * all nodes can communicate with all containers (and vice-versa) without NAT
-   * the IP that a container sees itself as is the same IP that others see it as
-
-What this means in practice is that you can not just take two computers
-running Docker and expect Kubernetes to work.  You must ensure that the
-fundamental requirements are met.
-
-This model is not only less complex overall, but it is principally compatible
-with the desire for Kubernetes to enable low-friction porting of apps from VMs
-to containers.  If your job previously ran in a VM, your VM had an IP and could
-talk to other VMs in your project.  This is the same basic model.
-
-Until now this document has talked about containers.  In reality, Kubernetes
-applies IP addresses at the `Pod` scope - containers within a `Pod` share their
-network namespaces - including their IP address.  This means that containers
-within a `Pod` can all reach each other's ports on `localhost`.  This does imply
-that containers within a `Pod` must coordinate port usage, but this is no
-different than processes in a VM.  We call this the "IP-per-pod" model.  This
-is implemented in Docker as a "pod container" which holds the network namespace
-open while "app containers" (the things the user specified) join that namespace
-with Docker's `--net=container:<id>` function.
-
-As with Docker, it is possible to request host ports, but this is reduced to a
-very niche operation.  In this case a port will be allocated on the host `Node`
-and traffic will be forwarded to the `Pod`.  The `Pod` itself is blind to the
-existence or non-existence of host ports.
-
-## How to achieve this
-
-There are a number of ways that this network model can be implemented.  This
-document is not an exhaustive study of the various methods, but hopefully serves
-as an introduction to various technologies and serves as a jumping-off point.
-If some techniques become vastly preferable to others, we might detail them more
-here.
-
-### Google Compute Engine (GCE)
-
-For the Google Compute Engine cluster configuration scripts, we use [advanced
-routing](https://developers.google.com/compute/docs/networking#routing) to
-assign each VM a subnet (default is `/24` - 254 IPs).  Any traffic bound for that
-subnet will be routed directly to the VM by the GCE network fabric.  This is in
-addition to the "main" IP address assigned to the VM, which is NAT'ed for
-outbound internet access.  A linux bridge (called `cbr0`) is configured to exist
-on that subnet, and is passed to docker's `--bridge` flag.
-
-We start Docker with:
-
-```shell
-DOCKER_OPTS="--bridge=cbr0 --iptables=false --ip-masq=false"
-```
-
-This bridge is created by Kubelet (controlled by the `--configure-cbr0=true`
-flag) according to the `Node`'s `spec.podCIDR`.
-
-Docker will now allocate IPs from the `cbr-cidr` block.  Containers can reach
-each other and `Nodes` over the `cbr0` bridge.  Those IPs are all routable
-within the GCE project network.
-
-GCE itself does not know anything about these IPs, though, so it will not NAT
-them for outbound internet traffic.  To achieve that we use an iptables rule to
-masquerade (aka SNAT - to make it seem as if packets came from the `Node`
-itself) traffic that is bound for IPs outside the GCE project network
-(10.0.0.0/8).
-
-```shell
-iptables -t nat -A POSTROUTING ! -d 10.0.0.0/8 -o eth0 -j MASQUERADE
-```
-
-Lastly we enable IP forwarding in the kernel (so the kernel will process
-packets for bridged containers):
-
-```shell
-sysctl net.ipv4.ip_forward=1
-```
-
-The result of all this is that all `Pods` can reach each other and can egress
-traffic to the internet.
-
-### L2 networks and linux bridging
-
-If you have a "dumb" L2 network, such as a simple switch in a "bare-metal"
-environment, you should be able to do something similar to the above GCE setup.
-Note that these instructions have only been tried very casually - it seems to
-work, but has not been thoroughly tested.  If you use this technique and
-perfect the process, please let us know.
-
-Follow the "With Linux Bridge devices" section of [this very nice
-tutorial](http://blog.oddbit.com/2014/08/11/four-ways-to-connect-a-docker/) from
-Lars Kellogg-Stedman.
-
-### Flannel
-
-[Flannel](https://github.com/coreos/flannel#flannel) is a very simple overlay
-network that satisfies the Kubernetes requirements.  It installs in minutes and
-should get you up and running if the above techniques are not working.  Many
-people have reported success with Flannel and Kubernetes.
-
-### OpenVSwitch
-
-[OpenVSwitch](/{{page.version}}/docs/admin/ovs-networking) is a somewhat more mature but also
-complicated way to build an overlay network.  This is endorsed by several of the
-"Big Shops" for networking.
-
-### Weave
-
-[Weave](https://github.com/zettio/weave) is yet another way to build an overlay
-network, primarily aiming at Docker integration.
-
-### Calico
-
-[Calico](https://github.com/Metaswitch/calico) uses BGP to enable real container
-IPs.
-
-## Other reading
-
-The early design of the networking model and its rationale, and some future
-plans are described in more detail in the [networking design
-document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/networking.md).
\ No newline at end of file
diff --git a/v1.2/docs/admin/ovs-networking.md b/v1.2/docs/admin/ovs-networking.md
deleted file mode 100644
index f5a279339a..0000000000
--- a/v1.2/docs/admin/ovs-networking.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
----
-
-This document describes how OpenVSwitch is used to setup networking between pods across nodes.
-The tunnel type could be GRE or VxLAN. VxLAN is preferable when large scale isolation needs to be performed within the network.
-
-![OVS Networking](/images/docs/ovs-networking.png)
-
-The vagrant setup in Kubernetes does the following:
-
-The docker bridge is replaced with a brctl generated linux bridge (kbr0) with a 256 address space subnet. Basically, a node gets 10.244.x.0/24 subnet and docker is configured to use that bridge instead of the default docker0 bridge.
-
-Also, an OVS bridge is created(obr0) and added as a port to the kbr0 bridge. All OVS bridges across all nodes are linked with GRE tunnels. So, each node has an outgoing GRE tunnel to all other nodes. It does not need to be a complete mesh really, just meshier the better. STP (spanning tree) mode is enabled in the bridges to prevent loops.
-
-Routing rules enable any 10.244.0.0/16 target to become reachable via the OVS bridge connected with the tunnels.
-
-
-
diff --git a/v1.2/docs/admin/resource-quota.md b/v1.2/docs/admin/resource-quota.md
deleted file mode 100755
index 494f014987..0000000000
--- a/v1.2/docs/admin/resource-quota.md
+++ /dev/null
@@ -1,154 +0,0 @@
----
----
-
-When several users or teams share a cluster with a fixed number of nodes,
-there is a concern that one team could use more than its fair share of resources.
-
-Resource quotas are a tool for administrators to address this concern. Resource quotas
-work like this:
-
-- Different teams work in different namespaces.  Currently this is voluntary, but
-  support for making this mandatory via ACLs is planned.
-- The administrator creates a Resource Quota for each namespace.
-- Users put compute resource requests on their pods. The sum of all resource requests across
-  all pods in the same namespace must not exceed any hard resource limit in any Resource Quota
-  document for the namespace. Note that we used to verify Resource Quota by taking the sum of
-  resource limits of the pods, but this was altered to use resource requests. Backwards compatibility
-  for those pods previously created is preserved because pods that only specify a resource limit have
-  their resource requests defaulted to match their defined limits. The user is only charged for the
-  resources they request in the Resource Quota versus their limits because the request is the minimum
-  amount of resource guaranteed by the cluster during scheduling. For more information on over commit,
-  see [compute-resources](/{{page.version}}/docs/user-guide/compute-resources).
-- If creating a pod would cause the namespace to exceed any of the limits specified in the
-  the Resource Quota for that namespace, then the request will fail with HTTP status
-  code `403 FORBIDDEN`.
-- If quota is enabled in a namespace and the user does not specify *requests* on the pod for each
-  of the resources for which quota is enabled, then the POST of the pod will fail with HTTP
-  status code `403 FORBIDDEN`.  Hint: Use the LimitRange admission controller to force default
-  values of *limits* (then resource *requests* would be equal to *limits* by default, see
-  [admission controller](/{{page.version}}/docs/admin/admission-controllers)) before the quota is checked to avoid this problem.
-
-Examples of policies that could be created using namespaces and quotas are:
-
-- In a cluster with a capacity of 32 GiB RAM, and 16 cores, let team A use 20 Gib and 10 cores,
-  let B use 10GiB and 4 cores, and hold 2GiB and 2 cores in reserve for future allocation.
-- Limit the "testing" namespace to using 1 core and 1GiB RAM.  Let the "production" namespace
-  use any amount.
-
-In the case where the total capacity of the cluster is less than the sum of the quotas of the namespaces,
-there may be contention for resources.  This is handled on a first-come-first-served basis.
-
-Neither contention nor changes to quota will affect already-running pods.
-
-## Enabling Resource Quota
-
-Resource Quota support is enabled by default for many Kubernetes distributions.  It is
-enabled when the apiserver `--admission-control=` flag has `ResourceQuota` as
-one of its arguments.
-
-Resource Quota is enforced in a particular namespace when there is a
-`ResourceQuota` object in that namespace.  There should be at most one
-`ResourceQuota` object in a namespace.
-
-## Compute Resource Quota
-
-The total sum of [compute resources](/{{page.version}}/docs/user-guide/compute-resources) requested by pods
-in a namespace can be limited.  The following compute resource types are supported:
-
-| ResourceName | Description |
-| ------------ | ----------- |
-| cpu | Total cpu requests of containers |
-| memory | Total memory requests of containers
-
-For example, `cpu` quota sums up the `resources.requests.cpu` fields of every
-container of every pod in the namespace, and enforces a maximum on that sum.
-
-## Object Count Quota
-
-The number of objects of a given type can be restricted.  The following types
-are supported:
-
-| ResourceName | Description |
-| ------------ | ----------- |
-| pods | Total number of pods  |
-| services | Total number of services |
-| replicationcontrollers | Total number of replication controllers |
-| resourcequotas | Total number of [resource quotas](/{{page.version}}/docs/admin/admission-controllers/#resourcequota) |
-| secrets | Total number of secrets |
-| persistentvolumeclaims | Total number of [persistent volume claims](/{{page.version}}/docs/user-guide/persistent-volumes/#persistentvolumeclaims) |
-
-For example, `pods` quota counts and enforces a maximum on the number of `pods`
-created in a single namespace.
-
-You might want to set a pods quota on a namespace
-to avoid the case where a user creates many small pods and exhausts the cluster's
-supply of Pod IPs.
-
-## Viewing and Setting Quotas
-
-Kubectl supports creating, updating, and viewing quotas:
-
-```shell
-$ kubectl namespace myspace
-$ cat <<EOF > quota.json
-{
-  "apiVersion": "v1",
-  "kind": "ResourceQuota",
-  "metadata": {
-    "name": "quota",
-  },
-  "spec": {
-    "hard": {
-      "memory": "1Gi",
-      "cpu": "20",
-      "pods": "10",
-      "services": "5",
-      "replicationcontrollers":"20",
-      "resourcequotas":"1",
-    },
-  }
-}
-EOF
-$ kubectl create -f ./quota.json
-$ kubectl get quota
-NAME
-quota
-$ kubectl describe quota quota
-Name:                   quota
-Resource                Used    Hard
---------                ----    ----
-cpu                     0m      20
-memory                  0       1Gi
-pods                    5       10
-replicationcontrollers  5       20
-resourcequotas          1       1
-services                3       5
-```
-
-## Quota and Cluster Capacity
-
-Resource Quota objects are independent of the Cluster Capacity. They are
-expressed in absolute units.  So, if you add nodes to your cluster, this does *not*
-automatically give each namespace the ability to consume more resources.
-
-Sometimes more complex policies may be desired, such as:
-
-  - proportionally divide total cluster resources among several teams.
-  - allow each tenant to grow resource usage as needed, but have a generous
-    limit to prevent accidental resource exhaustion.
-  - detect demand from one namespace, add nodes, and increase quota.
-
-Such policies could be implemented using ResourceQuota as a building-block, by
-writing a 'controller' which watches the quota usage and adjusts the quota
-hard limits of each namespace according to other signals.
-
-Note that resource quota divides up aggregate cluster resources, but it creates no
-restrictions around nodes: pods from several namespaces may run on the same node.
-
-## Example
-
-See a [detailed example for how to use resource quota](/{{page.version}}/docs/admin/resourcequota/).
-
-## Read More
-
-See [ResourceQuota design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_resource_quota.md) for more information.
\ No newline at end of file
diff --git a/v1.2/docs/admin/resourcequota/index.md b/v1.2/docs/admin/resourcequota/index.md
deleted file mode 100644
index 9011d51d37..0000000000
--- a/v1.2/docs/admin/resourcequota/index.md
+++ /dev/null
@@ -1,156 +0,0 @@
----
----
-
-This example demonstrates how [resource quota](/{{page.version}}/docs/admin/admission-controllers/#resourcequota) and
-[limitsranger](/{{page.version}}/docs/admin/admission-controllers/#limitranger) can be applied to a Kubernetes namespace.
-See [ResourceQuota design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control_resource_quota.md) for more information.
-
-This example assumes you have a functional Kubernetes setup.
-
-## Step 1: Create a namespace
-
-This example will work in a custom namespace to demonstrate the concepts involved.
-
-Let's create a new namespace called quota-example:
-
-```shell
-$ kubectl create -f docs/admin/resourcequota/namespace.yaml
-namespace "quota-example" created
-$ kubectl get namespaces
-NAME            LABELS    STATUS    AGE
-default         <none>    Active    2m
-quota-example   <none>    Active    39s
-```
-
-## Step 2: Apply a quota to the namespace
-
-By default, a pod will run with unbounded CPU and memory requests/limits.  This means that any pod in the
-system will be able to consume as much CPU and memory on the node that executes the pod.
-
-Users may want to restrict how much of the cluster resources a given namespace may consume
-across all of its pods in order to manage cluster usage.  To do this, a user applies a quota to
-a namespace.  A quota lets the user set hard limits on the total amount of node resources (cpu, memory)
-and API resources (pods, services, etc.) that a namespace may consume. In term of resources, Kubernetes
-checks the total resource *requests*, not resource *limits* of all containers/pods in the namespace.
-
-Let's create a simple quota in our namespace:
-
-```shell
-$ kubectl create -f docs/admin/resourcequota/quota.yaml --namespace=quota-example
-resourcequota "quota" created
-```
-
-Once your quota is applied to a namespace, the system will restrict any creation of content
-in the namespace until the quota usage has been calculated.  This should happen quickly.
-
-You can describe your current quota usage to see what resources are being consumed in your
-namespace.
-
-```shell
-$ kubectl describe quota quota --namespace=quota-example
-Name:			quota
-Namespace:		quota-example
-Resource		Used	Hard
---------		----	----
-cpu			0	20
-memory			0	1Gi
-persistentvolumeclaims	0	10
-pods			0	10
-replicationcontrollers	0	20
-resourcequotas		1	1
-secrets			1	10
-services		0	5
-```
-
-## Step 3: Applying default resource requests and limits
-
-Pod authors rarely specify resource requests and limits for their pods.
-
-Since we applied a quota to our project, let's see what happens when an end-user creates a pod that has unbounded
-cpu and memory by creating an nginx container.
-
-To demonstrate, lets create a replication controller that runs nginx:
-
-```shell
-$ kubectl run nginx --image=nginx --replicas=1 --namespace=quota-example
-replicationcontroller "nginx" created
-```
-
-Now let's look at the pods that were created.
-
-```shell
-$ kubectl get pods --namespace=quota-example
-NAME      READY     STATUS    RESTARTS   AGE
-```
-
-What happened?  I have no pods!  Let's describe the replication controller to get a view of what is happening.
-
-```shell
-kubectl describe rc nginx --namespace=quota-example
-Name:		nginx
-Namespace:	quota-example
-Image(s):	nginx
-Selector:	run=nginx
-Labels:		run=nginx
-Replicas:	0 current / 1 desired
-Pods Status:	0 Running / 0 Waiting / 0 Succeeded / 0 Failed
-No volumes.
-Events:
-  FirstSeen	LastSeen	Count	From				SubobjectPath	Reason		Message
-  42s		11s		3	{replication-controller }			FailedCreate	Error creating: Pod "nginx-" is forbidden: Must make a non-zero request for memory since it is tracked by quota.
-```
-
-The Kubernetes API server is rejecting the replication controllers requests to create a pod because our pods
-do not specify any memory usage *request*.
-
-So let's set some default values for the amount of cpu and memory a pod can consume:
-
-```shell
-$ kubectl create -f docs/admin/resourcequota/limits.yaml --namespace=quota-example
-limitrange "limits" created
-$ kubectl describe limits limits --namespace=quota-example
-Name:		limits
-Namespace:	quota-example
-Type		Resource	Min	Max	Request	Limit	Limit/Request
-----		--------	---	---	-------	-----	-------------
-Container	memory		-	-	256Mi	512Mi	-
-Container	cpu		-	-	100m	200m	-
-```
-
-Now any time a pod is created in this namespace, if it has not specified any resource request/limit, the default
-amount of cpu and memory per container will be applied, and the request will be used as part of admission control.
-
-Now that we have applied default resource *request* for our namespace, our replication controller should be able to
-create its pods.
-
-```shell
-$ kubectl get pods --namespace=quota-example
-NAME          READY     STATUS    RESTARTS   AGE
-nginx-fca65   1/1       Running   0          1m
-```
-
-And if we print out our quota usage in the namespace:
-
-```shell
-$ kubectl describe quota quota --namespace=quota-example
-Name:			quota
-Namespace:		quota-example
-Resource		Used	Hard
---------		----	----
-cpu			100m	20
-memory			256Mi	1Gi
-persistentvolumeclaims	0	10
-pods			1	10
-replicationcontrollers	1	20
-resourcequotas		1	1
-secrets			1	10
-services		0	5
-```
-
-You can now see the pod that was created is consuming explicit amounts of resources (specified by resource *request*), and the usage is being tracked by the Kubernetes system properly.
-
-## Summary
-
-Actions that consume node resources for cpu and memory can be subject to hard quota limits defined by the namespace quota. The resource consumption is measured by resource *request* in pod specification.
-
-Any action that consumes those resources can be tweaked, or can pick up namespace level defaults to meet your end goal.
\ No newline at end of file
diff --git a/v1.2/docs/admin/resourcequota/limits.yaml b/v1.2/docs/admin/resourcequota/limits.yaml
deleted file mode 100755
index 84b50b4e2a..0000000000
--- a/v1.2/docs/admin/resourcequota/limits.yaml
+++ /dev/null
@@ -1,13 +0,0 @@
-apiVersion: v1
-kind: LimitRange
-metadata:
-  name: limits
-spec:
-  limits:
-  - default:
-      cpu: 200m
-      memory: 512Mi
-    defaultRequest:
-      cpu: 100m
-      memory: 256Mi
-    type: Container
diff --git a/v1.2/docs/admin/resourcequota/namespace.yaml b/v1.2/docs/admin/resourcequota/namespace.yaml
deleted file mode 100644
index 2da842033b..0000000000
--- a/v1.2/docs/admin/resourcequota/namespace.yaml
+++ /dev/null
@@ -1,4 +0,0 @@
-apiVersion: v1
-kind: Namespace
-metadata:
-  name: quota-example
diff --git a/v1.2/docs/admin/resourcequota/quota.yaml b/v1.2/docs/admin/resourcequota/quota.yaml
deleted file mode 100644
index 6885efc6d1..0000000000
--- a/v1.2/docs/admin/resourcequota/quota.yaml
+++ /dev/null
@@ -1,14 +0,0 @@
-apiVersion: v1
-kind: ResourceQuota
-metadata:
-  name: quota
-spec:
-  hard:
-    cpu: "20"
-    memory: 1Gi
-    persistentvolumeclaims: "10"
-    pods: "10"
-    replicationcontrollers: "20"
-    resourcequotas: "1"
-    secrets: "10"
-    services: "5"
diff --git a/v1.2/docs/admin/salt.md b/v1.2/docs/admin/salt.md
deleted file mode 100644
index 25967ccf84..0000000000
--- a/v1.2/docs/admin/salt.md
+++ /dev/null
@@ -1,102 +0,0 @@
----
----
-
-The Kubernetes cluster can be configured using Salt.
-
-The Salt scripts are shared across multiple hosting providers, so it's important to understand some background information prior to making a modification to ensure your changes do not break hosting Kubernetes across multiple environments.  Depending on where you host your Kubernetes cluster, you may be using different operating systems and different networking configurations.  As a result, it's important to understand some background information before making Salt changes in order to minimize introducing failures for other hosting providers.
-
-## Salt cluster setup
-
-The **salt-master** service runs on the kubernetes-master [(except on the default GCE setup)](#standalone-salt-configuration-on-gce).
-
-The **salt-minion** service runs on the kubernetes-master and each kubernetes-node in the cluster.
-
-Each salt-minion service is configured to interact with the **salt-master** service hosted on the kubernetes-master via the **master.conf** file [(except on GCE)](#standalone-salt-configuration-on-gce).
-
-```shell
-[root@kubernetes-master] $ cat /etc/salt/minion.d/master.conf
-master: kubernetes-master
-```
-
-The salt-master is contacted by each salt-minion and depending upon the machine information presented, the salt-master will provision the machine as either a kubernetes-master or kubernetes-node with all the required capabilities needed to run Kubernetes.
-
-If you are running the Vagrant based environment, the **salt-api** service is running on the kubernetes-master.  It is configured to enable the vagrant user to introspect the salt cluster in order to find out about machines in the Vagrant environment via a REST API.
-
-## Standalone Salt Configuration on GCE
-
-On GCE, the master and nodes are all configured as [standalone minions](http://docs.saltstack.com/en/latest/topics/tutorials/standalone_minion). The configuration for each VM is derived from the VM's [instance metadata](https://cloud.google.com/compute/docs/metadata) and then stored in Salt grains (`/etc/salt/minion.d/grains.conf`) and pillars (`/srv/salt-overlay/pillar/cluster-params.sls`) that local Salt uses to enforce state.
-
-All remaining sections that refer to master/minion setups should be ignored for GCE. One fallout of the GCE setup is that the Salt mine doesn't exist - there is no sharing of configuration amongst nodes.
-
-## Salt security
-
-*(Not applicable on default GCE setup.)*
-
-Security is not enabled on the salt-master, and the salt-master is configured to auto-accept incoming requests from minions.  It is not recommended to use this security configuration in production environments without deeper study.  (In some environments this isn't as bad as it might sound if the salt master port isn't externally accessible and you trust everyone on your network.)
-
-```shell
-[root@kubernetes-master] $ cat /etc/salt/master.d/auto-accept.conf
-open_mode: True
-auto_accept: True
-```
-
-## Salt minion configuration
-
-Each minion in the salt cluster has an associated configuration that instructs the salt-master how to provision the required resources on the machine.
-
-An example file is presented below using the Vagrant based environment.
-
-```shell
-[root@kubernetes-master] $ cat /etc/salt/minion.d/grains.conf
-grains:
-  etcd_servers: $MASTER_IP
-  cloud_provider: vagrant
-  roles:
-    - kubernetes-master
-```
-
-Each hosting environment has a slightly different grains.conf file that is used to build conditional logic where required in the Salt files.
-
-The following enumerates the set of defined key/value pairs that are supported today.  If you add new ones, please make sure to update this list.
-
-Key | Value
-------------- | -------------
-`api_servers` | (Optional) The IP address / host name where a kubelet can get read-only access to kube-apiserver
-`cbr-cidr` | (Optional) The minion IP address range used for the docker container bridge.
-`cloud` | (Optional) Which IaaS platform is used to host Kubernetes, *gce*, *azure*, *aws*, *vagrant*
-`etcd_servers` | (Optional) Comma-delimited list of IP addresses the kube-apiserver and kubelet use to reach etcd.  Uses the IP of the first machine in the kubernetes_master role, or 127.0.0.1 on GCE.
-`hostnamef` | (Optional) The full host name of the machine, i.e. uname -n
-`node_ip` | (Optional) The IP address to use to address this node
-`hostname_override` | (Optional) Mapped to the kubelet hostname-override
-`network_mode` | (Optional) Networking model to use among nodes: *openvswitch*
-`networkInterfaceName` | (Optional) Networking interface to use to bind addresses, default value *eth0*
-`publicAddressOverride` | (Optional) The IP address the kube-apiserver should use to bind against for external read-only access
-`roles` | (Required) 1. `kubernetes-master` means this machine is the master in the Kubernetes cluster.  2. `kubernetes-pool` means this machine is a kubernetes-node.  Depending on the role, the Salt scripts will provision different resources on the machine.
-
-These keys may be leveraged by the Salt sls files to branch behavior.
-
-In addition, a cluster may be running a Debian based operating system or Red Hat based operating system (Centos, Fedora, RHEL, etc.).  As a result, it's important to sometimes distinguish behavior based on operating system using if branches like the following.
-
-```liquid
-{% raw %}
-{% if grains['os_family'] == 'RedHat' %}
-// something specific to a RedHat environment (Centos, Fedora, RHEL) where you may use yum, systemd, etc.
-{% else %}
-// something specific to Debian environment (apt-get, initd)
-{% endif %}
-{% endraw %}
-```
-
-## Best Practices
-
-1.  When configuring default arguments for processes, it's best to avoid the use of EnvironmentFiles (Systemd in Red Hat environments) or init.d files (Debian distributions) to hold default values that should be common across operating system environments.  This helps keep our Salt template files easy to understand for editors who may not be familiar with the particulars of each distribution.
-
-## Future enhancements (Networking)
-
-Per pod IP configuration is provider-specific, so when making networking changes, it's important to sandbox these as all providers may not use the same mechanisms (iptables, openvswitch, etc.)
-
-We should define a grains.conf key that captures more specifically what network configuration environment is being used to avoid future confusion across providers.
-
-## Further reading
-
-The [cluster/saltbase](http://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/) tree has more details on the current SaltStack configuration.
\ No newline at end of file
diff --git a/v1.2/docs/admin/static-pods.md b/v1.2/docs/admin/static-pods.md
deleted file mode 100644
index 1f53fcfa8c..0000000000
--- a/v1.2/docs/admin/static-pods.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
----
-
-
-**Static pods are to be deprecated and can be removed in any future Kubernetes release!**
-
-*Static pod* are managed directly by kubelet daemon on a specific node, without API server observing it. It does not have associated any replication controller, kubelet daemon itself watches it and restarts it when it crashes. There is no health check though. Static pods are always bound to one kubelet daemon and always run on the same node with it.
-
-Kubelet automatically creates so-called *mirror pod* on Kubernetes API server for each static pod, so the pods are visible there, but they cannot be controlled from the API server.
-
-## Static pod creation
-
-Static pod can be created in two ways: either by using configuration file(s) or by HTTP.
-
-### Configuration files
-
-The configuration files are just standard pod definition in json or yaml format in specific directory. Use `kubelet --config=<the directory>` to start kubelet daemon, which periodically scans the directory and creates/deletes static pods as yaml/json files appear/disappear there.
-
-For example, this is how to start a simple web server as a static pod:
-
-1. Choose a node where we want to run the static pod. In this example, it's `my-minion1`.
-
-```shell
-[joe@host ~] $ ssh my-minion1
-```
-
-2. Choose a directory, say `/etc/kubelet.d` and place a web server pod definition there, e.g. `/etc/kubernetes.d/static-web.yaml`:
-
-```shell
-[root@my-minion1 ~] $ mkdir /etc/kubernetes.d/
-    [root@my-minion1 ~] $ cat <<EOF >/etc/kubernetes.d/static-web.yaml
-    apiVersion: v1
-    kind: Pod
-    metadata:
-      name: static-web
-      labels:
-        role: myrole
-    spec:
-      containers:
-        - name: web
-          image: nginx
-          ports:
-            - name: web
-              containerPort: 80
-              protocol: tcp
-    EOF
-```
-
-2. Configure your kubelet daemon on the node to use this directory by running it with `--config=/etc/kubelet.d/` argument.  On Fedora Fedora 21 with Kubernetes 0.17 edit `/etc/kubernetes/kubelet` to include this line:
-
-    ```
-KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --config=/etc/kubelet.d/"

-    ```
-Instructions for other distributions or Kubernetes installations may vary.
-
-3. Restart kubelet. On Fedora 21, this is:
-
-```shell
-[root@my-minion1 ~] $ systemctl restart kubelet
-```
-
-## Pods created via HTTP
-
-Kubelet periodically downloads a file specified by `--manifest-url=<URL>` argument and interprets it as a json/yaml file with a pod definition. It works the same as `--config=<directory>`, i.e. it's reloaded every now and then and changes are applied to running static pods (see below).
-
-## Behavior of static pods
-
-When kubelet starts, it automatically starts all pods defined in directory specified in `--config=` or `--manifest-url=` arguments, i.e. our static-web.  (It may take some time to pull nginx image, be patient'|):
-
-```shell
-[joe@my-minion1 ~] $ docker ps
-CONTAINER ID IMAGE         COMMAND  CREATED        STATUS              NAMES
-f6d05272b57e nginx:latest  "nginx"  8 minutes ago  Up 8 minutes        k8s_web.6f802af4_static-web-fk-minion1_default_67e24ed9466ba55986d120c867395f3c_378e5f3c
-```
-
-If we look at our Kubernetes API server (running on host `my-master`), we see that a new mirror-pod was created there too:
-
-```shell
-[joe@host ~] $ ssh my-master
-[joe@my-master ~] $ kubectl get pods
-POD                     IP           CONTAINER(S)   IMAGE(S)    HOST                        LABELS       STATUS    CREATED         MESSAGE
-static-web-my-minion1   172.17.0.3                              my-minion1/192.168.100.71   role=myrole  Running   11 minutes
-                                     web            nginx                                                Running   11 minutes
-```
-
-Labels from the static pod are propagated into the mirror-pod and can be used as usual for filtering.
-
-Notice we cannot delete the pod with the API server (e.g. via [`kubectl`](/{{page.version}}/docs/user-guide/kubectl/kubectl) command), kubelet simply won't remove it.
-
-```shell
-[joe@my-master ~] $ kubectl delete pod static-web-my-minion1
-pods/static-web-my-minion1
-[joe@my-master ~] $ kubectl get pods
-POD                     IP           CONTAINER(S)   IMAGE(S)    HOST                        ...
-static-web-my-minion1   172.17.0.3                              my-minion1/192.168.100.71   ...
-```
-
-Back to our `my-minion1` host, we can try to stop the container manually and see, that kubelet automatically restarts it in a while:
-
-```shell
-[joe@host ~] $ ssh my-minion1
-[joe@my-minion1 ~] $ docker stop f6d05272b57e
-[joe@my-minion1 ~] $ sleep 20
-[joe@my-minion1 ~] $ docker ps
-CONTAINER ID        IMAGE         COMMAND                CREATED       ...
-5b920cbaf8b1        nginx:latest  "nginx -g 'daemon of   2 seconds ago ...
-```
-
-## Dynamic addition and removal of static pods
-
-Running kubelet periodically scans the configured directory (`/etc/kubelet.d` in our example) for changes and adds/removes pods as files appear/disappear in this directory.
-
-```shell
-[joe@my-minion1 ~] $ mv /etc/kubernetes.d/static-web.yaml /tmp
-[joe@my-minion1 ~] $ sleep 20
-[joe@my-minion1 ~] $ docker ps
-// no nginx container is running
-[joe@my-minion1 ~] $ mv /tmp/static-web.yaml  /etc/kubernetes.d/
-[joe@my-minion1 ~] $ sleep 20
-[joe@my-minion1 ~] $ docker ps
-CONTAINER ID        IMAGE         COMMAND                CREATED           ...
-e7a62e3427f1        nginx:latest  "nginx -g 'daemon of   27 seconds ago
-```
\ No newline at end of file
diff --git a/v1.2/docs/api.md b/v1.2/docs/api.md
deleted file mode 100644
index 720817c275..0000000000
--- a/v1.2/docs/api.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
----
-
-Primary system and API concepts are documented in the [User guide](/{{page.version}}/docs/user-guide/).
-
-Overall API conventions are described in the [API conventions doc](/{{page.version}}/docs/devel/api-conventions).
-
-Complete API details are documented via [Swagger](http://swagger.io/). The Kubernetes apiserver (aka "master") exports an API that can be used to retrieve the [Swagger spec](https://github.com/swagger-api/swagger-spec/tree/master/schemas/v1.2) for the Kubernetes API, by default at `/swaggerapi`, and a UI you can use to browse the API documentation at `/swagger-ui`. We also periodically update a [statically generated UI](http://kubernetes.io/third_party/swagger-ui/).
-
-Remote access to the API is discussed in the [access doc](/{{page.version}}/docs/admin/accessing-the-api).
-
-The Kubernetes API also serves as the foundation for the declarative configuration schema for the system. The [Kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) command-line tool can be used to create, update, delete, and get API objects.
-
-Kubernetes also stores its serialized state (currently in [etcd](https://coreos.com/docs/distributed-configuration/getting-started-with-etcd/)) in terms of the API resources.
-
-Kubernetes itself is decomposed into multiple components, which interact through its API.
-
-## API changes
-
-In our experience, any system that is successful needs to grow and change as new use cases emerge or existing ones change. Therefore, we expect the Kubernetes API to continuously change and grow. However, we intend to not break compatibility with existing clients, for an extended period of time. In general, new API resources and new resource fields can be expected to be added frequently. Elimination of resources or fields will require following a deprecation process. The precise deprecation policy for eliminating features is TBD, but once we reach our 1.0 milestone, there will be a specific policy.
-
-What constitutes a compatible change and how to change the API are detailed by the [API change document](/{{page.version}}/docs/devel/api_changes).
-
-## API versioning
-
-To make it easier to eliminate fields or restructure resource representations, Kubernetes supports
-multiple API versions, each at a different API path, such as `/api/v1` or
-`/apis/extensions/v1beta1`.
-
-We chose to version at the API level rather than at the resource or field level to ensure that the API presents a clear, consistent view of system resources and behavior, and to enable controlling access to end-of-lifed and/or experimental APIs.
-
-Note that API versioning and Software versioning are only indirectly related.  The [API and release
-versioning proposal](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/versioning.md) describes the relationship between API versioning and
-software versioning.
-
-
-Different API versions imply different levels of stability and support.  The criteria for each level are described
-in more detail in the [API Changes documentation](/{{page.version}}/docs/devel/api_changes/#alpha-beta-and-stable-versions).  They are summarized here:
-
-- Alpha level:
-  - The version names contain `alpha` (e.g. `v1alpha1`).
-  - May be buggy.  Enabling the feature may expose bugs.  Disabled by default.
-  - Support for feature may be dropped at any time without notice.
-  - The API may change in incompatible ways in a later software release without notice.
-  - Recommended for use only in short-lived testing clusters, due to increased risk of bugs and lack of long-term support.
-- Beta level:
-  - The version names contain `beta` (e.g. `v2beta3`).
-  - Code is well tested.  Enabling the feature is considered safe.  Enabled by default.
-  - Support for the overall feature will not be dropped, though details may change.
-  - The schema and/or semantics of objects may change in incompatible ways in a subsequent beta or stable release.  When this happens,
-    we will provide instructions for migrating to the next version.  This may require deleting, editing, and re-creating
-    API objects.  The editing process may require some thought.   This may require downtime for appplications that rely on the feature.
-  - Recommended for only non-business-critical uses because of potential for incompatible changes in subsequent releases.  If you have
-    multiple clusters which can be upgraded independently, you may be able to relax this restriction.
-  - **Please do try our beta features and give feedback on them!  Once they exit beta, it may not be practical for us to make more changes.**
-- Stable level:
-  - The version name is `vX` where `X` is an integer.
-  - Stable versions of features will appear in released software for many subsequent versions.
-
-## API groups
-
-To make it easier to extend the Kubernetes API, we are in the process of implementing [*API
-groups*](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/proposals/api-group.md).  These are simply different interfaces to read and/or modify the
-same underlying resources.  The API group is specified in a REST path and in the `apiVersion` field
-of a serialized object.
-
-Currently there are two API groups in use:
-
-1. the "core" group, which is at REST path `/api/v1` and is not specified as part of the `apiVersion` field, e.g.
-   `apiVersion: v1`.
-1. the "extensions" group, which is at REST path `/apis/extensions/$VERSION`, and which uses
-  `apiVersion: extensions/$VERSION` (e.g. currently `apiVersion: extensions/v1beta1`).
-
-In the future we expect that there will be more API groups, all at REST path `/apis/$API_GROUP` and
-using `apiVersion: $API_GROUP/$VERSION`.  We expect that there will be a way for (third parties to
-create their own API groups](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/extending-api.md), and to avoid naming collisions.
-
-## Enabling resources in the extensions group
-
-Jobs, Ingress and HorizontalPodAutoscalers 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`
-
-## v1beta1, v1beta2, and v1beta3 are deprecated; please move to v1 ASAP
-
-As of June 4, 2015, the Kubernetes v1 API has been enabled by default. The v1beta1 and v1beta2 APIs were deleted on June 1, 2015. v1beta3 is planned to be deleted on July 6, 2015.
-
-### v1 conversion tips (from v1beta3)
-
-We're working to convert all documentation and examples to v1. A simple [API conversion tool](/{{page.version}}/docs/admin/cluster-management/#switching-your-config-files-to-a-new-api-version) has been written to simplify the translation process. Use `kubectl create --validate` in order to validate your json or yaml against our Swagger spec.
-
-Changes to services are the most significant difference between v1beta3 and v1.
-
-* The `service.spec.portalIP` property is renamed to `service.spec.clusterIP`.
-* The `service.spec.createExternalLoadBalancer` property is removed. Specify `service.spec.type: "LoadBalancer"` to create an external load balancer instead.
-* The `service.spec.publicIPs` property is deprecated and now called `service.spec.deprecatedPublicIPs`. This property will be removed entirely when v1beta3 is removed. The vast majority of users of this field were using it to expose services on ports on the node. Those users should specify `service.spec.type: "NodePort"` instead. Read [External Services](/{{page.version}}/docs/user-guide/services/#external-services) for more info. If this is not sufficient for your use case, please file an issue or contact @thockin.
-
-Some other difference between v1beta3 and v1:
-
-* The `pod.spec.containers[*].privileged` and `pod.spec.containers[*].capabilities` properties are now nested under the `pod.spec.containers[*].securityContext` property. See [Security Contexts](/{{page.version}}/docs/user-guide/security-context).
-* The `pod.spec.host` property is renamed to `pod.spec.nodeName`.
-* The `endpoints.subsets[*].addresses.IP` property is renamed to `endpoints.subsets[*].addresses.ip`.
-* The `pod.status.containerStatuses[*].state.termination` and `pod.status.containerStatuses[*].lastState.termination` properties are renamed to `pod.status.containerStatuses[*].state.terminated` and `pod.status.containerStatuses[*].lastState.terminated` respectively.
-* The `pod.status.Condition` property is renamed to `pod.status.conditions`.
-* The `status.details.id` property is renamed to `status.details.name`.
-
-### v1beta3 conversion tips (from v1beta1/2)
-
-Some important differences between v1beta1/2 and v1beta3:
-
-* The resource `id` is now called `name`.
-* `name`, `labels`, `annotations`, and other metadata are now nested in a map called `metadata`
-* `desiredState` is now called `spec`, and `currentState` is now called `status`
-* `/minions` has been moved to `/nodes`, and the resource has kind `Node`
-* The namespace is required (for all namespaced resources) and has moved from a URL parameter to the path: `/api/v1beta3/namespaces/{namespace}/{resource_collection}/{resource_name}`. If you were not using a namespace before, use `default` here.
-* The names of all resource collections are now lower cased - instead of `replicationControllers`, use `replicationcontrollers`.
-* To watch for changes to a resource, open an HTTP or Websocket connection to the collection query and provide the `?watch=true` query parameter along with the desired `resourceVersion` parameter to watch from.
-* The `labels` query parameter has been renamed to `labelSelector`.
-* The `fields` query parameter has been renamed to `fieldSelector`.
-* The container `entrypoint` has been renamed to `command`, and `command` has been renamed to `args`.
-* Container, volume, and node resources are expressed as nested maps (e.g., `resources{cpu:1}`) rather than as individual fields, and resource values support [scaling suffixes](/{{page.version}}/docs/user-guide/compute-resources/#specifying-resource-quantities) rather than fixed scales (e.g., milli-cores).
-* Restart policy is represented simply as a string (e.g., `"Always"`) rather than as a nested map (`always{}`).
-* Pull policies changed from `PullAlways`, `PullNever`, and `PullIfNotPresent` to `Always`, `Never`, and `IfNotPresent`.
-* The volume `source` is inlined into `volume` rather than nested.
-* Host volumes have been changed from `hostDir` to `hostPath` to better reflect that they can be files or directories.
-
-
-
diff --git a/v1.2/docs/devel/api-conventions.md b/v1.2/docs/devel/api-conventions.md
deleted file mode 100644
index 806a4fac07..0000000000
--- a/v1.2/docs/devel/api-conventions.md
+++ /dev/null
@@ -1,659 +0,0 @@
----
----
-
-Updated: 9/20/2015
-
-*This document is oriented at users who want a deeper understanding of the Kubernetes
-API structure, and developers wanting to extend the Kubernetes API.  An introduction to
-using resources with kubectl can be found in [Working with resources](/{{page.version}}/docs/user-guide/working-with-resources).*
-
-* TOC
-{:toc}
-
-The conventions of the [Kubernetes API](/{{page.version}}/docs/api/) (and related APIs in the ecosystem) are intended to ease client development and ensure that configuration mechanisms can be implemented that work across a diverse set of use cases consistently.
-
-The general style of the Kubernetes API is RESTful - clients create, update, delete, or retrieve a description of an object via the standard HTTP verbs (POST, PUT, DELETE, and GET) - and those APIs preferentially accept and return JSON. Kubernetes also exposes additional endpoints for non-standard verbs and allows alternative content types. All of the JSON accepted and returned by the server has a schema, identified by the "kind" and "apiVersion" fields. Where relevant HTTP header fields exist, they should mirror the content of JSON fields, but the information should not be represented only in the HTTP header.
-
-The following terms are defined:
-
-* **Kind** the name of a particular object schema (e.g. the "Cat" and "Dog" kinds would have different attributes and properties)
-* **Resource** a representation of a system entity, sent or retrieved as JSON via HTTP to the server. Resources are exposed via:
-  * Collections - a list of resources of the same type, which may be queryable
-  * Elements - an individual resource, addressable via a URL
-
-Each resource typically accepts and returns data of a single kind.  A kind may be accepted or returned by multiple resources that reflect specific use cases. For instance, the kind "Pod" is exposed as a "pods" resource that allows end users to create, update, and delete pods, while a separate "pod status" resource (that acts on "Pod" kind) allows automated processes to update a subset of the fields in that resource.
-
-Resource collections should be all lowercase and plural, whereas kinds are CamelCase and singular.
-
-
-## Types (Kinds)
-
-Kinds are grouped into three categories:
-
-1. **Objects** represent a persistent entity in the system.
-
-   Creating an API object is a record of intent - once created, the system will work to ensure that resource exists. All API objects have common metadata.
-
-   An object may have multiple resources that clients can use to perform specific actions that create, update, delete, or get.
-
-   Examples: `Pod`, `ReplicationController`, `Service`, `Namespace`, `Node`.
-
-2. **Lists** are collections of **resources** of one (usually) or more (occasionally) kinds.
-
-   Lists have a limited set of common metadata. All lists use the "items" field to contain the array of objects they return.
-
-   Most objects defined in the system should have an endpoint that returns the full set of resources, as well as zero or more endpoints that return subsets of the full list. Some objects may be singletons (the current user, the system defaults) and may not have lists.
-
-   In addition, all lists that return objects with labels should support label filtering (see [docs/user-guide/labels.md](/{{page.version}}/docs/user-guide/labels), and most lists should support filtering by fields.
-
-   Examples: PodLists, ServiceLists, NodeLists
-
-   TODO: Describe field filtering below or in a separate doc.
-
-3. **Simple** kinds are used for specific actions on objects and for non-persistent entities.
-
-   Given their limited scope, they have the same set of limited common metadata as lists.
-
-   For instance, the "Status" kind is returned when errors occur and is not persisted in the system.
-
-   Many simple resources are "subresources", which are rooted at API paths of specific resources. When resources wish to expose alternative actions or views that are closely coupled to a single resource, they should do so using new sub-resources. Common subresources include:
-
-   * `/binding`: Used to bind a resource representing a user request (e.g., Pod, PersistentVolumeClaim) to a cluster infrastructure resource (e.g., Node, PersistentVolume).
-   * `/status`: Used to write just the status portion of a resource. For example, 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/&lt;name&gt;/status" endpoint - the alternate endpoint allows different rules to be applied to the update, and access to be appropriately restricted.
-   * `/scale`: Used to read and write the count of a resource in a manner that is independent of the specific resource schema.
-
-   Two additional subresources, `proxy` and `portforward`, provide access to cluster resources as described in [docs/user-guide/accessing-the-cluster.md](/{{page.version}}/docs/user-guide/accessing-the-cluster).
-
-The standard REST verbs (defined below) MUST return singular JSON objects. Some API endpoints may deviate from the strict REST pattern and return resources that are not singular JSON objects, such as streams of JSON objects or unstructured text log data.
-
-The term "kind" is reserved for these "top-level" API types. The term "type" should be used for distinguishing sub-categories within objects or subobjects.
-
-### Resources
-
-All JSON objects returned by an API MUST have the following fields:
-
-* kind: a string that identifies the schema this object should have
-* apiVersion: a string that identifies the version of the schema the object should have
-
-These fields are required for proper decoding of the object. They may be populated by the server by default from the specified URL path, but the client likely needs to know the values in order to construct the URL path.
-
-### Objects
-
-#### Metadata
-
-Every object kind MUST have the following metadata in a nested object field called "metadata":
-
-* namespace: a namespace is a DNS compatible subdomain that objects are subdivided into. The default namespace is 'default'.  See [docs/user-guide/namespaces.md](/{{page.version}}/docs/user-guide/namespaces) for more.
-* name: a string that uniquely identifies this object within the current namespace (see [docs/user-guide/identifiers.md](/{{page.version}}/docs/user-guide/identifiers)). This value is used in the path when retrieving an individual object.
-* uid: a unique in time and space value (typically an RFC 4122 generated identifier, see [docs/user-guide/identifiers.md](/{{page.version}}/docs/user-guide/identifiers)) used to distinguish between objects with the same name that have been deleted and recreated
-
-Every object SHOULD have the following metadata in a nested object field called "metadata":
-
-* resourceVersion: a string that identifies the internal version of this object that can be used by clients to determine when objects have changed. This value MUST be treated as opaque by clients and passed unmodified back to the server. Clients should not assume that the resource version has meaning across namespaces, different kinds of resources, or different servers. (see [concurrency control](#concurrency-control-and-consistency), below, for more details)
-* generation: a sequence number representing a specific generation of the desired state. Set by the system and monotonically increasing, per-resource. May be compared, such as for RAW and WAW consistency.
-* creationTimestamp: a string representing an RFC 3339 date of the date and time an object was created
-* deletionTimestamp: a string representing an RFC 3339 date of the date and time after which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource will be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field. Once set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time.
-* labels: a map of string keys and values that can be used to organize and categorize objects (see [docs/user-guide/labels.md](/{{page.version}}/docs/user-guide/labels))
-* annotations: a map of string keys and values that can be used by external tooling to store and retrieve arbitrary metadata about this object (see [docs/user-guide/annotations.md](/{{page.version}}/docs/user-guide/annotations))
-
-Labels are intended for organizational purposes by end users (select the pods that match this label query). Annotations enable third-party automation and tooling to decorate objects with additional metadata for their own use.
-
-#### Spec and Status
-
-By convention, the Kubernetes API makes a distinction between the specification of the desired state of an object (a nested object field called "spec") and the status of the object at the current time (a nested object field called "status"). The specification is a complete description of the desired state, including configuration settings provided by the user, [default values](#defaulting) expanded by the system, and properties initialized or otherwise changed after creation by other ecosystem components (e.g., schedulers, auto-scalers), and is persisted in stable storage with the API object. If the specification is deleted, the object will be purged from the system. The status summarizes the current state of the object in the system, and is usually persisted with the object by an automated processes but may be generated on the fly. At some cost and perhaps some temporary degradation in behavior, the status could be reconstructed by observation if it were lost.
-
-When a new version of an object is POSTed or PUT, the "spec" is updated and available immediately. Over time the system will work to bring the "status" into line with the "spec". The system will drive toward the most recent "spec" regardless of previous versions of that stanza. In other words, if a value is changed from 2 to 5 in one PUT and then back down to 3 in another PUT the system is not required to 'touch base' at 5 before changing the "status" to 3. In other words, the system's behavior is *level-based* rather than *edge-based*. This enables robust behavior in the presence of missed intermediate state changes.
-
-The Kubernetes API also serves as the foundation for the declarative configuration schema for the system. In order to facilitate level-based operation and expression of declarative configuration, fields in the specification should have declarative rather than imperative names and semantics -- they represent the desired state, not actions intended to yield the desired state.
-
-The PUT and POST verbs on objects will ignore the "status" values. A `/status` subresource is provided to enable system components to update statuses of resources they manage.
-
-Otherwise, PUT expects the whole object to be specified. Therefore, if a field is omitted it is assumed that the client wants to clear that field's value. The PUT verb does not accept partial updates. Modification of just part of an object may be achieved by GETting the resource, modifying part of the spec, labels, or annotations, and then PUTting it back. See [concurrency control](#concurrency-control-and-consistency), below, regarding read-modify-write consistency when using this pattern. Some objects may expose alternative resource representations that allow mutation of the status, or performing custom actions on the object.
-
-All objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a "spec" and a "status".  Objects whose state cannot vary from the user's desired intent MAY have only "spec", and MAY rename "spec" to a more appropriate name.
-
-Objects that contain both spec and status should not contain additional top-level fields other than the standard metadata fields.
-
-##### Typical status properties
-
-**Conditions** represent the latest available observations of an object's current state. Objects may report multiple conditions, and new types of conditions may be added in the future. Therefore, conditions are represented using a list/slice, where all have similar structure.
-
-The `FooCondition` type for some resource type `Foo` may include a subset of the following fields, but must contain at least `type` and `status` fields:
-
-```go
-Type               FooConditionType  `json:"type" description:"type of Foo condition"`
-	Status             ConditionStatus   `json:"status" description:"status of the condition, one of True, False, Unknown"`
-	LastHeartbeatTime  unversioned.Time         `json:"lastHeartbeatTime,omitempty" description:"last time we got an update on a given condition"`
-	LastTransitionTime unversioned.Time         `json:"lastTransitionTime,omitempty" description:"last time the condition transit from one status to another"`
-	Reason             string            `json:"reason,omitempty" description:"one-word CamelCase reason for the condition's last transition"`
-	Message            string            `json:"message,omitempty" description:"human-readable message indicating details about last transition"`
-```
-
-Additional fields may be added in the future.
-
-Conditions should be added to explicitly convey properties that users and components care about rather than requiring those properties to be inferred from other observations.
-
-Condition status values may be `True`, `False`, or `Unknown`. The absence of a condition should be interpreted the same as `Unknown`.
-
-In general, condition values may change back and forth, but some condition transitions may be monotonic, depending on the resource and condition type. However, conditions are observations and not, themselves, state machines, nor do we define comprehensive state machines for objects, nor behaviors associated with state transitions. The system is level-based rather than edge-triggered, and should assume an Open World.
-
-A typical oscillating condition type is `Ready`, which indicates the object was believed to be fully operational at the time it was last probed. A possible monotonic condition could be `Succeeded`. A `False` status for `Succeeded` would imply failure. An object that was still active would not have a `Succeeded` condition, or its status would be `Unknown`.
-
-Some resources in the v1 API contain fields called **`phase`**, and associated `message`, `reason`, and other status fields. The pattern of using `phase` is deprecated. Newer API types should use conditions instead. Phase was essentially a state-machine enumeration field, that contradicted [system-design principles](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/principles.md#control-logic) and hampered evolution, since [adding new enum values breaks backward compatibility](/{{page.version}}/docs/devel/api_changes). Rather than encouraging clients to infer implicit properties from phases, we intend to explicitly expose the conditions that clients need to monitor. Conditions also have the benefit that it is possible to create some conditions with uniform meaning across all resource types, while still exposing others that are unique to specific resource types. See [#7856](http://issues.k8s.io/7856) for more details and discussion.
-
-In condition types, and everywhere else they appear in the API, **`Reason`** is intended to be a one-word, CamelCase representation of the category of cause of the current status, and **`Message`** is intended to be a human-readable phrase or sentence, which may contain specific details of the individual occurrence. `Reason` is intended to be used in concise output, such as one-line `kubectl get` output, and in summarizing occurrences of causes, whereas `Message` is intended to be presented to users in detailed status explanations, such as `kubectl describe` output.
-
-Historical information status (e.g., last transition time, failure counts) is only provided with reasonable effort, and is not guaranteed to not be lost.
-
-Status information that may be large (especially proportional in size to collections of other resources, such as lists of references to other objects -- see below) and/or rapidly changing, such as [resource usage](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/resources.md#usage-data), should be put into separate objects, with possibly a reference from the original object. This helps to ensure that GETs and watch remain reasonably efficient for the majority of clients, which may not need that data.
-
-Some resources report the `observedGeneration`, which is the `generation` most recently observed by the component responsible for acting upon changes to the desired state of the resource. This can be used, for instance, to ensure that the reported status reflects the most recent desired status.
-
-#### References to related objects
-
-References to loosely coupled sets of objects, such as [pods](/{{page.version}}/docs/user-guide/pods) overseen by a [replication controller](/{{page.version}}/docs/user-guide/replication-controller), are usually best referred to using a [label selector](/{{page.version}}/docs/user-guide/labels). In order to ensure that GETs of individual objects remain bounded in time and space, these sets may be queried via separate API queries, but will not be expanded in the referring object's status.
-
-References to specific objects, especially specific resource versions and/or specific fields of those objects, are specified using the `ObjectReference` type (or other types representing strict subsets of it). Unlike partial URLs, the ObjectReference type facilitates flexible defaulting of fields from the referring object or other contextual information.
-
-References in the status of the referee to the referrer may be permitted, when the references are one-to-one and do not need to be frequently updated, particularly in an edge-based manner.
-
-#### Lists of named subobjects preferred over maps
-
-Discussed in [#2004](http://issue.k8s.io/2004) and elsewhere. There are no maps of subobjects in any API objects. Instead, the convention is to use a list of subobjects containing name fields.
-
-For example:
-
-```yaml
-ports:
-  - name: www
-    containerPort: 80
-```
-
-vs.
-
-```yaml
-ports:
-  www:
-    containerPort: 80
-```
-
-This rule maintains the invariant that all JSON/YAML keys are fields in API objects. The only exceptions are pure maps in the API (currently, labels, selectors, annotations, data), as opposed to sets of subobjects.
-
-#### Constants
-
-Some fields will have a list of allowed values (enumerations). These values will be strings, and they will be in CamelCase, with an initial uppercase letter. Examples: "ClusterFirst", "Pending", "ClientIP".
-
-### Lists and Simple kinds
-
-Every list or simple kind SHOULD have the following metadata in a nested object field called "metadata":
-
-* resourceVersion: a string that identifies the common version of the objects returned by in a list. This value MUST be treated as opaque by clients and passed unmodified back to the server. A resource version is only valid within a single namespace on a single kind of resource.
-
-Every simple kind returned by the server, and any simple kind sent to the server that must support idempotency or optimistic concurrency should return this value.Since simple resources are often used as input alternate actions that modify objects, the resource version of the simple resource should correspond to the resource version of the object.
-
-
-## Differing Representations
-
-An API may represent a single entity in different ways for different clients, or transform an object after certain transitions in the system occur. In these cases, one request object may have two representations available as different resources, or different kinds.
-
-An example is a Service, which represents the intent of the user to group a set of pods with common behavior on common ports. When Kubernetes detects a pod matches the service selector, the IP address and port of the pod are added to an Endpoints resource for that Service. The Endpoints resource exists only if the Service exists, but exposes only the IPs and ports of the selected pods.  The full service is represented by two distinct resources - under the original Service resource the user created, as well as in the Endpoints resource.
-
-As another example, a "pod status" resource may accept a PUT with the "pod" kind, with different rules about what fields may be changed.
-
-Future versions of Kubernetes may allow alternative encodings of objects beyond JSON.
-
-
-## Verbs on Resources
-
-API resources should use the traditional REST pattern:
-
-* GET /&lt;resourceNamePlural&gt; - Retrieve a list of type &lt;resourceName&gt;, e.g. GET /pods returns a list of Pods.
-* POST /&lt;resourceNamePlural&gt; - Create a new resource from the JSON object provided by the client.
-* GET /&lt;resourceNamePlural&gt;/&lt;name&gt; - Retrieves a single resource with the given name, e.g. GET /pods/first returns a Pod named 'first'. Should be constant time, and the resource should be bounded in size.
-* DELETE /&lt;resourceNamePlural&gt;/&lt;name&gt;  - Delete the single resource with the given name. DeleteOptions may specify gracePeriodSeconds, the optional duration in seconds before the object should be deleted. Individual kinds may declare fields which provide a default grace period, and different kinds may have differing kind-wide default grace periods. A user provided grace period overrides a default grace period, including the zero grace period ("now").
-* PUT /&lt;resourceNamePlural&gt;/&lt;name&gt; - Update or create the resource with the given name with the JSON object provided by the client.
-* PATCH /&lt;resourceNamePlural&gt;/&lt;name&gt; - Selectively modify the specified fields of the resource. See more information [below](#patch).
-* GET /&lt;resourceNamePlural&gt;&amp;watch=true - Receive a stream of JSON objects corresponding to changes made to any resource of the given kind over time.
-
-### PATCH operations
-
-The API supports three different PATCH operations, determined by their corresponding Content-Type header:
-
-* JSON Patch, `Content-Type: application/json-patch+json`
- * As defined in [RFC6902](https://tools.ietf.org/html/rfc6902), a JSON Patch is a sequence of operations that are executed on the resource, e.g. `{"op": "add", "path": "/a/b/c", "value": [ "foo", "bar" ]}`. For more details on how to use JSON Patch, see the RFC.
-* Merge Patch, `Content-Type: application/merge-patch+json`
- * As defined in [RFC7386](https://tools.ietf.org/html/rfc7386), a Merge Patch is essentially a partial representation of the resource. The submitted JSON is "merged" with the current resource to create a new one, then the new one is saved. For more details on how to use Merge Patch, see the RFC.
-* Strategic Merge Patch, `Content-Type: application/strategic-merge-patch+json`
- * Strategic Merge Patch is a custom implementation of Merge Patch. For a detailed explanation of how it works and why it needed to be introduced, see below.
-
-#### Strategic Merge Patch
-
-In the standard JSON merge patch, JSON objects are always merged but lists are always replaced. Often that isn't what we want. Let's say we start with the following Pod:
-
-```yaml
-spec:
-  containers:
-    - name: nginx
-      image: nginx-1.0
-```
-
-...and we POST that to the server (as JSON). Then let's say we want to *add* a container to this Pod.
-
-```yaml
-PATCH /api/v1/namespaces/default/pods/pod-name
-spec:
-  containers:
-    - name: log-tailer
-      image: log-tailer-1.0
-```
-
-If we were to use standard Merge Patch, the entire container list would be replaced with the single log-tailer container. However, our intent is for the container lists to merge together based on the `name` field.
-
-To solve this problem, Strategic Merge Patch uses metadata attached to the API objects to determine what lists should be merged and which ones should not. Currently the metadata is available as struct tags on the API objects themselves, but will become available to clients as Swagger annotations in the future. In the above example, the `patchStrategy` metadata for the `containers` field would be `merge` and the `patchMergeKey` would be `name`.
-
-Note: If the patch results in merging two lists of scalars, the scalars are first deduplicated and then merged.
-
-Strategic Merge Patch also supports special operations as listed below.
-
-### List Operations
-
-To override the container list to be strictly replaced, regardless of the default:
-
-```yaml
-containers:
-  - name: nginx
-    image: nginx-1.0
-  - $patch: replace   # any further $patch operations nested in this list will be ignored
-```
-
-To delete an element of a list that should be merged:
-
-```yaml
-containers:
-  - name: nginx
-    image: nginx-1.0
-  - $patch: delete
-    name: log-tailer  # merge key and value goes here
-```
-
-### Map Operations
-
-To indicate that a map should not be merged and instead should be taken literally:
-
-```yaml
-$patch: replace  # recursive and applies to all fields of the map it's in
-containers:
-- name: nginx
-  image: nginx-1.0
-```
-
-To delete a field of a map:
-
-```yaml
-name: nginx
-image: nginx-1.0
-labels:
-  live: null  # set the value of the map key to null
-```
-
-## Idempotency
-
-All compatible Kubernetes APIs MUST support "name idempotency" and respond with an HTTP status code 409 when a request is made to POST an object that has the same name as an existing object in the system. See [docs/user-guide/identifiers.md](/{{page.version}}/docs/user-guide/identifiers) for details.
-
-Names generated by the system may be requested using `metadata.generateName`. GenerateName indicates that the name should be made unique by the server prior to persisting it. A non-empty value for the field indicates the name will be made unique (and the name returned to the client will be different than the name passed). The value of this field will be combined with a unique suffix on the server if the Name field has not been provided. The provided value must be valid within the rules for Name, and may be truncated by the length of the suffix required to make the value unique on the server. If this field is specified, and Name is not present, the server will NOT return a 409 if the generated name exists - instead, it will either return 201 Created or 504 with Reason `ServerTimeout` indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header).
-
-## Defaulting
-
-Default resource values are API version-specific, and they are applied during
-the conversion from API-versioned declarative configuration to internal objects
-representing the desired state (`Spec`) of the resource. Subsequent GETs of the
-resource will include the default values explicitly.
-
-Incorporating the default values into the `Spec` ensures that `Spec` depicts the
-full desired state so that it is easier for the system to determine how to
-achieve the state, and for the user to know what to anticipate.
-
-API version-specific default values are set by the API server.
-
-## Late Initialization
-
-Late initialization is when resource fields are set by a system controller
-after an object is created/updated.
-
-For example, the scheduler sets the `pod.spec.nodeName` field after the pod is created.
-
-Late-initializers should only make the following types of modifications:
-
- - Setting previously unset fields
- - Adding keys to maps
- - Adding values to arrays which have mergeable semantics (`patchStrategy:"merge"` attribute in
-  the type definition).
-
-These conventions:
-
- 1. allow a user (with sufficient privilege) to override any system-default behaviors by setting
-    the fields that would otherwise have been defaulted.
- 1. enables updates from users to be merged with changes made during late initialization, using
-    strategic merge patch, as opposed to clobbering the change.
- 1. allow the component which does the late-initialization to use strategic merge patch, which
-    facilitates composition and concurrency of such components.
-
-Although the apiserver Admission Control stage acts prior to object creation,
-Admission Control plugins should follow the Late Initialization conventions
-too, to allow their implementation to be later moved to a 'controller', or to client libraries.
-
-## Concurrency Control and Consistency
-
-Kubernetes leverages the concept of *resource versions* to achieve optimistic concurrency. All Kubernetes resources have a "resourceVersion" field as part of their metadata. This resourceVersion is a string that identifies the internal version of an object that can be used by clients to determine when objects have changed. When a record is about to be updated, it's version is checked against a pre-saved value, and if it doesn't match, the update fails with a StatusConflict (HTTP status code 409).
-
-The resourceVersion is changed by the server every time an object is modified. If resourceVersion is included with the PUT operation the system will verify that there have not been other successful mutations to the resource during a read/modify/write cycle, by verifying that the current value of resourceVersion matches the specified value.
-
-The resourceVersion is currently backed by [etcd's modifiedIndex](https://coreos.com/docs/distributed-configuration/etcd-api/). However, it's important to note that the application should *not* rely on the implementation details of the versioning system maintained by Kubernetes. We may change the implementation of resourceVersion in the future, such as to change it to a timestamp or per-object counter.
-
-The only way for a client to know the expected value of resourceVersion is to have received it from the server in response to a prior operation, typically a GET. This value MUST be treated as opaque by clients and passed unmodified back to the server. Clients should not assume that the resource version has meaning across namespaces, different kinds of resources, or different servers. Currently, the value of resourceVersion is set to match etcd's sequencer. You could think of it as a logical clock the API server can use to order requests. However, we expect the implementation of resourceVersion to change in the future, such as in the case we shard the state by kind and/or namespace, or port to another storage system.
-
-In the case of a conflict, the correct client action at this point is to GET the resource again, apply the changes afresh, and try submitting again. This mechanism can be used to prevent races like the following:
-
-```shell
-Client #1                                  Client #2
-GET Foo                                    GET Foo
-Set Foo.Bar = "one"                        Set Foo.Baz = "two"
-PUT Foo                                    PUT Foo
-```
-
-When these sequences occur in parallel, either the change to Foo.Bar or the change to Foo.Baz can be lost.
-
-On the other hand, when specifying the resourceVersion, one of the PUTs will fail, since whichever write succeeds changes the resourceVersion for Foo.
-
-resourceVersion may be used as a precondition for other operations (e.g., GET, DELETE) in the future, such as for read-after-write consistency in the presence of caching.
-
-"Watch" operations specify resourceVersion using a query parameter. It is used to specify the point at which to begin watching the specified resources. This may be used to ensure that no mutations are missed between a GET of a resource (or list of resources) and a subsequent Watch, even if the current version of the resource is more recent. This is currently the main reason that list operations (GET on a collection) return resourceVersion.
-
-
-## Serialization Format
-
-APIs may return alternative representations of any resource in response to an Accept header or under alternative endpoints, but the default serialization for input and output of API responses MUST be JSON.
-
-All dates should be serialized as RFC3339 strings.
-
-## Units
-
-Units must either be explicit in the field name (e.g., `timeoutSeconds`), or must be specified as part of the value (e.g., `resource.Quantity`). Which approach is preferred is TBD, though currently we use the `fooSeconds` convention for durations.
-
-
-## Selecting Fields
-
-Some APIs may need to identify which field in a JSON object is invalid, or to reference a value to extract from a separate resource. The current recommendation is to use standard JavaScript syntax for accessing that field, assuming the JSON object was transformed into a JavaScript object, without the leading dot, such as `metadata.name`.
-
-Examples:
-
-* Find the field "current" in the object "state" in the second item in the array "fields": `fields[1].state.current`
-
-## Object references
-
-Object references should either be called `fooName` if referring to an object of kind `Foo` by just the name (within the current namespace, if a namespaced resource), or should be called `fooRef`, and should contain a subset of the fields of the `ObjectReference` type.
-
-
-TODO: Plugins, extensions, nested kinds, headers
-
-
-## HTTP Status codes
-
-The server will respond with HTTP status codes that match the HTTP spec. See the section below for a breakdown of the types of status codes the server will send.
-
-The following HTTP status codes may be returned by the API.
-
-#### Success codes
-
-* `200 StatusOK`
-  * Indicates that the request completed successfully.
-* `201 StatusCreated`
-  * Indicates that the request to create kind completed successfully.
-* `204 StatusNoContent`
-  * Indicates that the request completed successfully, and the response contains no body.
-  * Returned in response to HTTP OPTIONS requests.
-
-#### Error codes
-
-* `307 StatusTemporaryRedirect`
-  * Indicates that the address for the requested resource has changed.
-  * Suggested client recovery behavior
-    * Follow the redirect.
-* `400 StatusBadRequest`
-  * Indicates the requested is invalid.
-  * Suggested client recovery behavior:
-    * Do not retry. Fix the request.
-* `401 StatusUnauthorized`
-  * Indicates that the server can be reached and understood the request, but refuses to take any further action, because the client must provide authorization. If the client has provided authorization, the server is indicating the provided authorization is unsuitable or invalid.
-  * Suggested client recovery behavior
-    * If the user has not supplied authorization information, prompt them for the appropriate credentials
-    * If the user has supplied authorization information, inform them their credentials were rejected and optionally prompt them again.
-* `403 StatusForbidden`
-  * Indicates that the server can be reached and understood the request, but refuses to take any further action, because it is configured to deny access for some reason to the requested resource by the client.
-  * Suggested client recovery behavior
-    * Do not retry. Fix the request.
-* `404 StatusNotFound`
-  * Indicates that the requested resource does not exist.
-  * Suggested client recovery behavior
-    * Do not retry. Fix the request.
-* `405 StatusMethodNotAllowed`
-  * Indicates that the action the client attempted to perform on the resource was not supported by the code.
-  * Suggested client recovery behavior
-    * Do not retry. Fix the request.
-* `409 StatusConflict`
-  * Indicates that either the resource the client attempted to create already exists or the requested update operation cannot be completed due to a conflict.
-  * Suggested client recovery behavior
-  * * If creating a new resource
-  *   * Either change the identifier and try again, or GET and compare the fields in the pre-existing object and issue a PUT/update to modify the existing object.
-  * * If updating an existing resource:
-      * See `Conflict` from the `status` response section below on how to retrieve more information about the nature of the conflict.
-      * GET and compare the fields in the pre-existing object, merge changes (if still valid according to preconditions), and retry with the updated request (including `ResourceVersion`).
-* `422 StatusUnprocessableEntity`
-  * Indicates that the requested create or update operation cannot be completed due to invalid data provided as part of the request.
-  * Suggested client recovery behavior
-    * Do not retry. Fix the request.
-* `429 StatusTooManyRequests`
-  * Indicates that the either the client rate limit has been exceeded or the server has received more requests then it can process.
-  * Suggested client recovery behavior:
-    * Read the `Retry-After` HTTP header from the response, and wait at least that long before retrying.
-* `500 StatusInternalServerError`
-  * Indicates that the server can be reached and understood the request, but either an unexpected internal error occurred and the outcome of the call is unknown, or the server cannot complete the action in a reasonable time (this maybe due to temporary server load or a transient communication issue with another server).
-  * Suggested client recovery behavior:
-    * Retry with exponential backoff.
-* `503 StatusServiceUnavailable`
-  * Indicates that required service is unavailable.
-  * Suggested client recovery behavior:
-    * Retry with exponential backoff.
-* `504 StatusServerTimeout`
-  * Indicates that the request could not be completed within the given time. Clients can get this response ONLY when they specified a timeout param in the request.
-  * Suggested client recovery behavior:
-    * Increase the value of the timeout param and retry with exponential backoff
-
-## Response Status Kind
-
-Kubernetes will always return the `Status` kind from any API endpoint when an error occurs.
-Clients SHOULD handle these types of objects when appropriate.
-
-A `Status` kind will be returned by the API in two cases:
-
-  1. When an operation is not successful (i.e. when the server would return a non 2xx HTTP status code).
-  2. When a HTTP `DELETE` call is successful.
-
-The status object is encoded as JSON and provided as the body of the response.  The status object contains fields for humans and machine consumers of the API to get more detailed information for the cause of the failure. The information in the status object supplements, but does not override, the HTTP status code's meaning. When fields in the status object have the same meaning as generally defined HTTP headers and that header is returned with the response, the header should be considered as having higher priority.
-
-**Example:**
-
-```shell
-$ curl -v -k -H "Authorization: Bearer WhCDvq4VPpYhrcfmF6ei7V9qlbqTubUc" https://10.240.122.184:443/api/v1/namespaces/default/pods/grafana
-
-> GET /api/v1/namespaces/default/pods/grafana HTTP/1.1
-> User-Agent: curl/7.26.0
-> Host: 10.240.122.184
-> Accept: */*
-> Authorization: Bearer WhCDvq4VPpYhrcfmF6ei7V9qlbqTubUc
-> 
-
-< HTTP/1.1 404 Not Found
-< Content-Type: application/json
-< Date: Wed, 20 May 2015 18:10:42 GMT
-< Content-Length: 232
-< 
-{
-  "kind": "Status",
-  "apiVersion": "v1",
-  "metadata": {},
-  "status": "Failure",
-  "message": "pods \"grafana\" not found",
-  "reason": "NotFound",
-  "details": {
-    "name": "grafana",
-    "kind": "pods"
-  },
-  "code": 404
-}
-```
-
-`status` field contains one of two possible values:
-* `Success`
-* `Failure`
-
-`message` may contain human-readable description of the error
-
-`reason` may contain a machine-readable, one-word, CamelCase description of why this operation is in the `Failure` status. If this value is empty there is no information available. The `reason` clarifies an HTTP status code but does not override it.
-
-`details` may contain extended data associated with the reason. Each reason may define its own extended details. This field is optional and the data returned is not guaranteed to conform to any schema except that defined by the reason type.
-
-Possible values for the `reason` and `details` fields:
-
-* `BadRequest`
-  * Indicates that the request itself was invalid, because the request doesn't make any sense, for example deleting a read-only object.
-  * This is different than `status reason` `Invalid` above which indicates that the API call could possibly succeed, but the data was invalid.
-  * API calls that return BadRequest can never succeed.
-  * Http status code: `400 StatusBadRequest`
-* `Unauthorized`
-  * Indicates that the server can be reached and understood the request, but refuses to take any further action without the client providing appropriate authorization. If the client has provided authorization, this error indicates the provided credentials are insufficient or invalid.
-  * Details (optional):
-    * `kind string`
-      * The kind attribute of the unauthorized resource (on some operations may differ from the requested resource).
-    * `name string`
-      * The identifier of the unauthorized resource.
-   * HTTP status code: `401 StatusUnauthorized`
-* `Forbidden`
-  * Indicates that the server can be reached and understood the request, but refuses to take any further action, because it is configured to deny access for some reason to the requested resource by the client.
-  * Details (optional):
-    * `kind string`
-      * The kind attribute of the forbidden resource (on some operations may differ from the requested resource).
-    * `name string`
-      * The identifier of the forbidden resource.
-	 * HTTP status code: `403 StatusForbidden`
-* `NotFound`
-  * Indicates that one or more resources required for this operation could not be found.
-  * Details (optional):
-    * `kind string`
-      * The kind attribute of the missing resource (on some operations may differ from the requested resource).
-    * `name string`
-      * The identifier of the missing resource.
-  * HTTP status code: `404 StatusNotFound`
-* `AlreadyExists`
-  * Indicates that the resource you are creating already exists.
-  * Details (optional):
-    * `kind string`
-      * The kind attribute of the conflicting resource.
-    * `name string`
-      * The identifier of the conflicting resource.
-  * HTTP status code: `409 StatusConflict`
-* `Conflict`
-  * Indicates that the requested update operation cannot be completed due to a conflict. The client may need to alter the request. Each resource may define custom details that indicate the nature of the conflict.
-  * HTTP status code: `409 StatusConflict`
-* `Invalid`
-  * Indicates that the requested create or update operation cannot be completed due to invalid data provided as part of the request.
-  * Details (optional):
-    * `kind string`
-      * the kind attribute of the invalid resource
-    * `name string`
-      * the identifier of the invalid resource
-    * `causes`
-      * One or more `StatusCause` entries indicating the data in the provided resource that was invalid. The `reason`, `message`, and `field` attributes will be set.
-  * HTTP status code: `422 StatusUnprocessableEntity`
-* `Timeout`
-  * Indicates that the request could not be completed within the given time. Clients may receive this response if the server has decided to rate limit the client, or if the server is overloaded and cannot process the request at this time.
-  * Http status code: `429 TooManyRequests`
-  * The server should set the `Retry-After` HTTP header and return `retryAfterSeconds` in the details field of the object. A value of `0` is the default.
-* `ServerTimeout`
-  * Indicates that the server can be reached and understood the request, but cannot complete the action in a reasonable time. This maybe due to temporary server load or a transient communication issue with another server.
-    * Details (optional):
-      * `kind string`
-        * The kind attribute of the resource being acted on.
-      * `name string`
-        * The operation that is being attempted.
-  * The server should set the `Retry-After` HTTP header and return `retryAfterSeconds` in the details field of the object. A value of `0` is the default.
-  * Http status code: `504 StatusServerTimeout`
-* `MethodNotAllowed`
-  * Indicates that the action the client attempted to perform on the resource was not supported by the code.
-  * For instance, attempting to delete a resource that can only be created.
-  * API calls that return MethodNotAllowed can never succeed.
-  * Http status code: `405 StatusMethodNotAllowed`
-* `InternalError`
-  * Indicates that an internal error occurred, it is unexpected and the outcome of the call is unknown.
-  * Details (optional):
-    * `causes`
-      * The original error.
-  * Http status code: `500 StatusInternalServerError`
-
-`code` may contain the suggested HTTP return code for this status.
-
-
-## Events
-
-Events are complementary to status information, since they can provide some historical information about status and occurrences in addition to current or previous status. Generate events for situations users or administrators should be alerted about.
-
-Choose a unique, specific, short, CamelCase reason for each event category. For example, `FreeDiskSpaceInvalid` is a good event reason because it is likely to refer to just one situation, but `Started` is not a good reason because it doesn't sufficiently indicate what started, even when combined with other event fields.
-
-`Error creating foo` or `Error creating foo %s` would be appropriate for an event message, with the latter being preferable, since it is more informational.
-
-Accumulate repeated events in the client, especially for frequent events, to reduce data volume, load on the system, and noise exposed to users.
-
-## Naming conventions
-
-* Go field names must be CamelCase. JSON field names must be camelCase. Other than capitalization of the initial letter, the two should almost always match. No underscores nor dashes in either.
-* Field and resource names should be declarative, not imperative (DoSomething, SomethingDoer, DoneBy, DoneAt).
-* `Minion` has been deprecated in favor of `Node`. Use `Node` where referring to the node resource in the context of the cluster. Use `Host` where referring to properties of the individual physical/virtual system, such as `hostname`, `hostPath`, `hostNetwork`, etc.
-* `FooController` is a deprecated kind naming convention. Name the kind after the thing being controlled instead (e.g., `Job` rather than `JobController`).
-* The name of a field that specifies the time at which `something` occurs should be called `somethingTime`. Do not use `stamp` (e.g., `creationTimestamp`).
-* We use the `fooSeconds` convention for durations, as discussed in the [units subsection](#units).
-  * `fooPeriodSeconds` is preferred for periodic intervals and other waiting periods (e.g., over `fooIntervalSeconds`).
-  * `fooTimeoutSeconds` is preferred for inactivity/unresponsiveness deadlines.
-  * `fooDeadlineSeconds` is preferred for activity completion deadlines.
-* Do not use abbreviations in the API, except where they are extremely commonly used, such as "id", "args", or "stdin".
-* Acronyms should similarly only be used when extremely commonly known. All letters in the acronym should have the same case, using the appropriate case for the situation. For example, at the beginning of a field name, the acronym should be all lowercase, such as "httpGet". Where used as a constant, all letters should be uppercase, such as "TCP" or "UDP".
-* The name of a field referring to another resource of kind `Foo` by name should be called `fooName`. The name of a field referring to another resource of kind `Foo` by ObjectReference (or subset thereof) should be called `fooRef`.
-* More generally, include the units and/or type in the field name if they could be ambiguous and they are not specified by the value or value type.
-
-## Label, selector, and annotation conventions
-
-Labels are the domain of users. They are intended to facilitate organization and management of API resources using attributes that are meaningful to users, as opposed to meaningful to the system. Think of them as user-created mp3 or email inbox labels, as opposed to the directory structure used by a program to store its data. The former is enables the user to apply an arbitrary ontology, whereas the latter is implementation-centric and inflexible. Users will use labels to select resources to operate on, display label values in CLI/UI columns, etc. Users should always retain full power and flexibility over the label schemas they apply to labels in their namespaces.
-
-However, we should support conveniences for common cases by default. For example, what we now do in ReplicationController is automatically set the RC's selector and labels to the labels in the pod template by default, if they are not already set. That ensures that the selector will match the template, and that the RC can be managed using the same labels as the pods it creates. Note that once we generalize selectors, it won't necessarily be possible to unambiguously generate labels that match an arbitrary selector.
-
-If the user wants to apply additional labels to the pods that it doesn't select upon, such as to facilitate adoption of pods or in the expectation that some label values will change, they can set the selector to a subset of the pod labels. Similarly, the RC's labels could be initialized to a subset of the pod template's labels, or could include additional/different labels.
-
-For disciplined users managing resources within their own namespaces, it's not that hard to consistently apply schemas that ensure uniqueness. One just needs to ensure that at least one value of some label key in common differs compared to all other comparable resources. We could/should provide a verification tool to check that. However, development of conventions similar to the examples in [Labels](/{{page.version}}/docs/user-guide/labels) make uniqueness straightforward. Furthermore, relatively narrowly used namespaces (e.g., per environment, per application) can be used to reduce the set of resources that could potentially cause overlap.
-
-In cases where users could be running misc. examples with inconsistent schemas, or where tooling or components need to programmatically generate new objects to be selected, there needs to be a straightforward way to generate unique label sets. A simple way to ensure uniqueness of the set is to ensure uniqueness of a single label value, such as by using a resource name, uid, resource hash, or generation number.
-
-Problems with uids and hashes, however, include that they have no semantic meaning to the user, are not memorable nor readily recognizable, and are not predictable. Lack of predictability obstructs use cases such as creation of a replication controller from a pod, such as people want to do when exploring the system, bootstrapping a self-hosted cluster, or deletion and re-creation of a new RC that adopts the pods of the previous one, such as to rename it. Generation numbers are more predictable and much clearer, assuming there is a logical sequence. Fortunately, for deployments that's the case. For jobs, use of creation timestamps is common internally. Users should always be able to turn off auto-generation, in order to permit some of the scenarios described above. Note that auto-generated labels will also become one more field that needs to be stripped out when cloning a resource, within a namespace, in a new namespace, in a new cluster, etc., and will need to be ignored around when updating a resource via patch or read-modify-write sequence.
-
-Inclusion of a system prefix in a label key is fairly hostile to UX. A prefix is only necessary in the case that the user cannot choose the label key, in order to avoid collisions with user-defined labels. However, I firmly believe that the user should always be allowed to select the label keys to use on their resources, so it should always be possible to override default label keys.
-
-Therefore, resources supporting auto-generation of unique labels should have a `uniqueLabelKey` field, so that the user could specify the key if they wanted to, but if unspecified, it could be set by default, such as to the resource type, like job, deployment, or replicationController. The value would need to be at least spatially unique, and perhaps temporally unique in the case of job.
-
-Annotations have very different intended usage from labels. We expect them to be primarily generated and consumed by tooling and system extensions. I'm inclined to generalize annotations to permit them to directly store arbitrary json. Rigid names and name prefixes make sense, since they are analogous to API fields.
-
-In fact, in-development API fields, including those used to represent fields of newer alpha/beta API versions in the older stable storage version, may be represented as annotations with the form `something.alpha.kubernetes.io/name` or `something.beta.kubernetes.io/name` (depending on our confidence in it).  For example `net.alpha.kubernetes.io/policy` might represent an experimental network policy field.
-
-Other advice regarding use of labels, annotations, and other generic map keys by Kubernetes components and tools:
-
-  - Key names should be all lowercase, with words separated by dashes, such as `desired-replicas`
-  - Prefix the key with `kubernetes.io/` or `foo.kubernetes.io/`, preferably the latter if the label/annotation is specific to `foo`
-    - For instance, prefer `service-account.kubernetes.io/name` over `kubernetes.io/service-account.name`
-  - Use annotations to store API extensions that the controller responsible for the resource doesn't need to know about, experimental fields that aren't intended to be generally used API fields, etc. Beware that annotations aren't automatically handled by the API conversion machinery.
\ No newline at end of file
diff --git a/v1.2/docs/devel/api_changes.md b/v1.2/docs/devel/api_changes.md
deleted file mode 100644
index 907c6d04fc..0000000000
--- a/v1.2/docs/devel/api_changes.md
+++ /dev/null
@@ -1,586 +0,0 @@
----
----
-
-Before attempting a change to the API, you should familiarize yourself
-with a number of existing API types and with the [API
-conventions](/{{page.version}}/docs/devel/api-conventions).  If creating a new API
-type/resource, we also recommend that you first send a PR containing
-just a proposal for the new API types, and that you initially target
-the extensions API (pkg/apis/extensions).
-
-The Kubernetes API has two major components - the internal structures and
-the versioned APIs.  The versioned APIs are intended to be stable, while the
-internal structures are implemented to best reflect the needs of the Kubernetes
-code itself.
-
-What this means for API changes is that you have to be somewhat thoughtful in
-how you approach changes, and that you have to touch a number of pieces to make
-a complete change.  This document aims to guide you through the process, though
-not all API changes will need all of these steps.
-
-## Operational overview
-
-It is important to have a high level understanding of the API system used in
-Kubernetes in order to navigate the rest of this document.
-
-As mentioned above, the internal representation of an API object is decoupled
-from any one API version.  This provides a lot of freedom to evolve the code,
-but it requires robust infrastructure to convert between representations.  There
-are multiple steps in processing an API operation - even something as simple as
-a GET involves a great deal of machinery.
-
-The conversion process is logically a "star" with the internal form at the
-center. Every versioned API can be converted to the internal form (and
-vice-versa), but versioned APIs do not convert to other versioned APIs directly.
-This sounds like a heavy process, but in reality we do not intend to keep more
-than a small number of versions alive at once.  While all of the Kubernetes code
-operates on the internal structures, they are always converted to a versioned
-form before being written to storage (disk or etcd) or being sent over a wire.
-Clients should consume and operate on the versioned APIs exclusively.
-
-To demonstrate the general process, here is a (hypothetical) example:
-
-   1. A user POSTs a `Pod` object to `/api/v7beta1/...`
-   2. The JSON is unmarshalled into a `v7beta1.Pod` structure
-   3. Default values are applied to the `v7beta1.Pod`
-   4. The `v7beta1.Pod` is converted to an `api.Pod` structure
-   5. The `api.Pod` is validated, and any errors are returned to the user
-   6. The `api.Pod` is converted to a `v6.Pod` (because v6 is the latest stable
-      version)
-   7. The `v6.Pod` is marshalled into JSON and written to etcd
-
-Now that we have the `Pod` object stored, a user can GET that object in any
-supported api version.  For example:
-
-   1. A user GETs the `Pod` from `/api/v5/...`
-   2. The JSON is read from etcd and unmarshalled into a `v6.Pod` structure
-   3. Default values are applied to the `v6.Pod`
-   4. The `v6.Pod` is converted to an `api.Pod` structure
-   5. The `api.Pod` is converted to a `v5.Pod` structure
-   6. The `v5.Pod` is marshalled into JSON and sent to the user
-
-The implication of this process is that API changes must be done carefully and
-backward-compatibly.
-
-## On compatibility
-
-Before talking about how to make API changes, it is worthwhile to clarify what
-we mean by API compatibility.  An API change is considered backward-compatible
-if it:
-
-   * adds new functionality that is not required for correct behavior (e.g.,
-     does not add a new required field)
-   * does not change existing semantics, including:
-     * default values and behavior
-     * interpretation of existing API types, fields, and values
-     * which fields are required and which are not
-
-Put another way:
-
-1. Any API call (e.g. a structure POSTed to a REST endpoint) that worked before
-   your change must work the same after your change.
-2. Any API call that uses your change must not cause problems (e.g. crash or
-   degrade behavior) when issued against servers that do not include your change.
-3. It must be possible to round-trip your change (convert to different API
-   versions and back) with no loss of information.
-4. Existing clients need not be aware of your change in order for them to continue
-   to function as they did previously, even when your change is utilized
-
-If your change does not meet these criteria, it is not considered strictly
-compatible.
-
-Let's consider some examples.  In a hypothetical API (assume we're at version
-v6), the `Frobber` struct looks something like this:
-
-```go
-// API v6.
-type Frobber struct {
-	Height int    `json:"height"`
-	Param  string `json:"param"`
-}
-```
-
-You want to add a new `Width` field.  It is generally safe to add new fields
-without changing the API version, so you can simply change it to:
-
-```go
-// Still API v6.
-type Frobber struct {
-	Height int    `json:"height"`
-	Width  int    `json:"width"`
-	Param  string `json:"param"`
-}
-```
-
-The onus is on you to define a sane default value for `Width` such that rule #1
-above is true - API calls and stored objects that used to work must continue to
-work.
-
-For your next change you want to allow multiple `Param` values.  You can not
-simply change `Param string` to `Params []string` (without creating a whole new
-API version) - that fails rules #1 and #2.  You can instead do something like:
-
-```go
-// Still API v6, but kind of clumsy.
-type Frobber struct {
-	Height int           `json:"height"`
-	Width  int           `json:"width"`
-	Param  string        `json:"param"`  // the first param
-	ExtraParams []string `json:"params"` // additional params
-}
-```
-
-Now you can satisfy the rules: API calls that provide the old style `Param`
-will still work, while servers that don't understand `ExtraParams` can ignore
-it.  This is somewhat unsatisfying as an API, but it is strictly compatible.
-
-Part of the reason for versioning APIs and for using internal structs that are
-distinct from any one version is to handle growth like this.  The internal
-representation can be implemented as:
-
-```go
-// Internal, soon to be v7beta1.
-type Frobber struct {
-	Height int
-	Width  int
-	Params []string
-}
-```
-
-The code that converts to/from versioned APIs can decode this into the somewhat
-uglier (but compatible!) structures.  Eventually, a new API version, let's call
-it v7beta1, will be forked and it can use the clean internal structure.
-
-We've seen how to satisfy rules #1 and #2.  Rule #3 means that you can not
-extend one versioned API without also extending the others.  For example, an
-API call might POST an object in API v7beta1 format, which uses the cleaner
-`Params` field, but the API server might store that object in trusty old v6
-form (since v7beta1 is "beta").  When the user reads the object back in the
-v7beta1 API it would be unacceptable to have lost all but `Params[0]`.  This
-means that, even though it is ugly, a compatible change must be made to the v6
-API.
-
-However, this is very challenging to do correctly. It often requires
-multiple representations of the same information in the same API resource, which
-need to be kept in sync in the event that either is changed. For example,
-let's say you decide to rename a field within the same API version. In this case,
-you add units to `height` and `width`. You implement this by adding duplicate
-fields:
-
-```go
-type Frobber struct {
-	Height         *int          `json:"height"`
-	Width          *int          `json:"width"`
-	HeightInInches *int          `json:"heightInInches"`
-	WidthInInches  *int          `json:"widthInInches"`
-}
-```
-
-You convert all of the fields to pointers in order to distinguish between unset and
-set to 0, and then set each corresponding field from the other in the defaulting
-pass (e.g., `heightInInches` from `height`, and vice versa), which runs just prior
-to conversion. That works fine when the user creates a resource from a hand-written
-configuration -- clients can write either field and read either field, but what about
-creation or update from the output of GET, or update via PATCH (see
-[In-place updates](/{{page.version}}/docs/user-guide/managing-deployments/#in-place-updates-of-resources))?
-In this case, the two fields will conflict, because only one field would be updated
-in the case of an old client that was only aware of the old field (e.g., `height`).
-
-Say the client creates:
-
-```json
-{
-  "height": 10,
-  "width": 5
-}
-```
-
-and GETs:
-
-```json
-{
-  "height": 10,
-  "heightInInches": 10,
-  "width": 5,
-  "widthInInches": 5
-}
-```
-
-then PUTs back:
-
-```json
-{
-  "height": 13,
-  "heightInInches": 10,
-  "width": 5,
-  "widthInInches": 5
-}
-```
-
-The update should not fail, because it would have worked before `heightInInches` was added.
-
-Therefore, when there are duplicate fields, the old field MUST take precedence
-over the new, and the new field should be set to match by the server upon write.
-A new client would be aware of the old field as well as the new, and so can ensure
-that the old field is either unset or is set consistently with the new field. However,
-older clients would be unaware of the new field. Please avoid introducing duplicate
-fields due to the complexity they incur in the API.
-
-A new representation, even in a new API version, that is more expressive than an old one
-breaks backward compatibility, since clients that only understood the old representation
-would not be aware of the new representation nor its semantics. Examples of
-proposals that have run into this challenge include [generalized label
-selectors](http://issues.k8s.io/341) and [pod-level security
-context](http://prs.k8s.io/12823).
-
-As another interesting example, enumerated values cause similar challenges.
-Adding a new value to an enumerated set is *not* a compatible change.  Clients
-which assume they know how to handle all possible values of a given field will
-not be able to handle the new values.  However, removing value from an
-enumerated set *can* be a compatible change, if handled properly (treat the
-removed value as deprecated but allowed). This is actually a special case of
-a new representation, discussed above.
-
-## Incompatible API changes
-
-There are times when this might be OK, but mostly we want changes that
-meet this definition.  If you think you need to break compatibility,
-you should talk to the Kubernetes team first.
-
-Breaking compatibility of a beta or stable API version, such as v1, is unacceptable.
-Compatibility for experimental or alpha APIs is not strictly required, but
-breaking compatibility should not be done lightly, as it disrupts all users of the
-feature. Experimental APIs may be removed. Alpha and beta API versions may be deprecated
-and eventually removed wholesale, as described in the [versioning document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/versioning.md).
-Document incompatible changes across API versions under the [conversion tips](/{{page.version}}/docs/api/).
-
-If your change is going to be backward incompatible or might be a breaking change for API
-consumers, please send an announcement to `kubernetes-dev@googlegroups.com` before
-the change gets in. If you are unsure, ask. Also make sure that the change gets documented in
-the release notes for the next release by labeling the PR with the "release-note" github label.
-
-If you found that your change accidentally broke clients, it should be reverted.
-
-In short, the expected API evolution is as follows:
-
-* `extensions/v1alpha1` ->
-* `newapigroup/v1alpha1` -> ... -> `newapigroup/v1alphaN` ->
-* `newapigroup/v1beta1` -> ... -> `newapigroup/v1betaN` ->
-* `newapigroup/v1` ->
-* `newapigroup/v2alpha1` -> ...
-
-While in extensions we have no obligation to move forward with the API at all and may delete or break it at any time.
-
-While in alpha we expect to move forward with it, but may break it.
-
-Once in beta we will preserve forward compatibility, but may introduce new versions and delete old ones.
-
-v1 must be backward-compatible for an extended length of time.
-
-## Changing versioned APIs
-
-For most changes, you will probably find it easiest to change the versioned
-APIs first.  This forces you to think about how to make your change in a
-compatible way.  Rather than doing each step in every version, it's usually
-easier to do each versioned API one at a time, or to do all of one version
-before starting "all the rest".
-
-### Edit types.go
-
-The struct definitions for each API are in `pkg/api/<version>/types.go`.  Edit
-those files to reflect the change you want to make.  Note that all types and non-inline
-fields in versioned APIs must be preceded by descriptive comments - these are used to generate
-documentation.
-
-Optional fields should have the `,omitempty` json tag; fields are interpreted as being
-required otherwise.
-
-### Edit defaults.go
-
-If your change includes new fields for which you will need default values, you
-need to add cases to `pkg/api/<version>/defaults.go`.  Of course, since you
-have added code, you have to add a test: `pkg/api/<version>/defaults_test.go`.
-
-Do use pointers to scalars when you need to distinguish between an unset value
-and an automatic zero value.  For example,
-`PodSpec.TerminationGracePeriodSeconds` is defined as `*int64` the go type
-definition.  A zero value means 0 seconds, and a nil value asks the system to
-pick a default.
-
-Don't forget to run the tests!
-
-### Edit conversion.go
-
-Given that you have not yet changed the internal structs, this might feel
-premature, and that's because it is.  You don't yet have anything to convert to
-or from.  We will revisit this in the "internal" section.  If you're doing this
-all in a different order (i.e. you started with the internal structs), then you
-should jump to that topic below.  In the very rare case that you are making an
-incompatible change you might or might not want to do this now, but you will
-have to do more later.  The files you want are
-`pkg/api/<version>/conversion.go` and `pkg/api/<version>/conversion_test.go`.
-
-Note that the conversion machinery doesn't generically handle conversion of values,
-such as various kinds of field references and API constants. [The client
-library](https://releases.k8s.io/{{page.githubbranch}}/pkg/client/unversioned/request.go) has custom conversion code for
-field references. You also need to add a call to api.Scheme.AddFieldLabelConversionFunc
-with a mapping function that understands supported translations.
-
-## Changing the internal structures
-
-Now it is time to change the internal structs so your versioned changes can be
-used.
-
-### Edit types.go
-
-Similar to the versioned APIs, the definitions for the internal structs are in
-`pkg/api/types.go`.  Edit those files to reflect the change you want to make.
-Keep in mind that the internal structs must be able to express *all* of the
-versioned APIs.
-
-## Edit validation.go
-
-Most changes made to the internal structs need some form of input validation.
-Validation is currently done on internal objects in
-`pkg/api/validation/validation.go`.  This validation is the one of the first
-opportunities we have to make a great user experience - good error messages and
-thorough validation help ensure that users are giving you what you expect and,
-when they don't, that they know why and how to fix it.  Think hard about the
-contents of `string` fields, the bounds of `int` fields and the
-requiredness/optionalness of fields.
-
-Of course, code needs tests - `pkg/api/validation/validation_test.go`.
-
-## Edit version conversions
-
-At this point you have both the versioned API changes and the internal
-structure changes done.  If there are any notable differences - field names,
-types, structural change in particular - you must add some logic to convert
-versioned APIs to and from the internal representation.  If you see errors from
-the `serialization_test`, it may indicate the need for explicit conversions.
-
-Performance of conversions very heavily influence performance of apiserver.
-Thus, we are auto-generating conversion functions that are much more efficient
-than the generic ones (which are based on reflections and thus are highly
-inefficient).
-
-The conversion code resides with each versioned API. There are two files:
-
-   - `pkg/api/<version>/conversion.go` containing manually written conversion
-     functions
-   - `pkg/api/<version>/conversion_generated.go` containing auto-generated
-     conversion functions
-   - `pkg/apis/extensions/<version>/conversion.go` containing manually written
-     conversion functions
-   - `pkg/apis/extensions/<version>/conversion_generated.go` containing
-     auto-generated conversion functions
-
-Since auto-generated conversion functions are using manually written ones,
-those manually written should be named with a defined convention, i.e. a function
-converting type X in pkg a to type Y in pkg b, should be named:
-`convert_a_X_To_b_Y`.
-
-Also note that you can (and for efficiency reasons should) use auto-generated
-conversion functions when writing your conversion functions.
-
-Once all the necessary manually written conversions are added, you need to
-regenerate auto-generated ones. To regenerate them, run:
-
-```shell
-hack/update-generated-conversions.sh
-
-```
-If running the above script is impossible due to compile errors, the easiest
-workaround is to comment out the code causing errors and let the script to
-regenerate it. If the auto-generated conversion methods are not used by the
-manually-written ones, it's fine to just remove the whole file and let the
-generator to create it from scratch.
-
-Unsurprisingly, adding manually written conversion also requires you to add tests to
-`pkg/api/<version>/conversion_test.go`.
-
-## Edit deep copy files
-
-At this point you have both the versioned API changes and the internal
-structure changes done.  You now need to generate code to handle deep copy
-of your versioned api objects.
-
-The deep copy code resides with each versioned API:
-
-   - `pkg/api/<version>/deep_copy_generated.go` containing auto-generated copy functions
-   - `pkg/apis/extensions/<version>/deep_copy_generated.go` containing auto-generated copy functions
-
-To regenerate them, run:
-
-```shell
-hack/update-generated-deep-copies.sh
-```
-
-## Edit json (un)marshaling code
-
-We are auto-generating code for marshaling and unmarshaling json representation
-of api objects - this is to improve the overall system performance.
-
-The auto-generated code resides with each versioned API:
-
-   - `pkg/api/<version>/types.generated.go`
-   - `pkg/apis/extensions/<version>/types.generated.go`
-
-To regenerate them, run:
-
-```shell
-hack/update-codecgen.sh
-```
-
-## Making a new API Group
-
-This section is under construction, as we make the tooling completely generic.
-
-At the moment, you'll have to make a new directory under pkg/apis/; copy the
-directory structure from pkg/apis/extensions. Add the new group/version to all
-of the hack/{verify,update}-generated-{deep-copy,conversions,swagger}.sh files
-in the appropriate places--it should just require adding your new group/version
-to a bash array. You will also need to make sure your new types are imported by
-the generation commands (cmd/gendeepcopy/ & cmd/genconversion). These
-instructions may not be complete and will be updated as we gain experience.
-
-Adding API groups outside of the pkg/apis/ directory is not currently supported,
-but is clearly desirable. The deep copy & conversion generators need to work by
-parsing go files instead of by reflection; then they will be easy to point at
-arbitrary directories: see issue [#13775](http://issue.k8s.io/13775).
-
-## Update the fuzzer
-
-Part of our testing regimen for APIs is to "fuzz" (fill with random values) API
-objects and then convert them to and from the different API versions.  This is
-a great way of exposing places where you lost information or made bad
-assumptions.  If you have added any fields which need very careful formatting
-(the test does not run validation) or if you have made assumptions such as
-"this slice will always have at least 1 element", you may get an error or even
-a panic from the `serialization_test`.  If so, look at the diff it produces (or
-the backtrace in case of a panic) and figure out what you forgot.  Encode that
-into the fuzzer's custom fuzz functions.  Hint: if you added defaults for a field,
-that field will need to have a custom fuzz function that ensures that the field is
-fuzzed to a non-empty value.
-
-The fuzzer can be found in `pkg/api/testing/fuzzer.go`.
-
-## Update the semantic comparisons
-
-VERY VERY rarely is this needed, but when it hits, it hurts.  In some rare
-cases we end up with objects (e.g. resource quantities) that have morally
-equivalent values with different bitwise representations (e.g. value 10 with a
-base-2 formatter is the same as value 0 with a base-10 formatter).  The only way
-Go knows how to do deep-equality is through field-by-field bitwise comparisons.
-This is a problem for us.
-
-The first thing you should do is try not to do that.  If you really can't avoid
-this, I'd like to introduce you to our semantic DeepEqual routine.  It supports
-custom overrides for specific types - you can find that in `pkg/api/helpers.go`.
-
-There's one other time when you might have to touch this: unexported fields.
-You see, while Go's `reflect` package is allowed to touch unexported fields, us
-mere mortals are not - this includes semantic DeepEqual.  Fortunately, most of
-our API objects are "dumb structs" all the way down - all fields are exported
-(start with a capital letter) and there are no unexported fields.  But sometimes
-you want to include an object in our API that does have unexported fields
-somewhere in it (for example, `time.Time` has unexported fields).  If this hits
-you, you may have to touch the semantic DeepEqual customization functions.
-
-## Implement your change
-
-Now you have the API all changed - go implement whatever it is that you're
-doing!
-
-## Write end-to-end tests
-
-Check out the [E2E docs](/{{page.version}}/docs/devel/e2e-tests) for detailed information about how to write end-to-end
-tests for your feature.
-
-## Examples and docs
-
-At last, your change is done, all unit tests pass, e2e passes, you're done,
-right?  Actually, no.  You just changed the API.  If you are touching an
-existing facet of the API, you have to try *really* hard to make sure that
-*all* the examples and docs are updated.  There's no easy way to do this, due
-in part to JSON and YAML silently dropping unknown fields.  You're clever -
-you'll figure it out.  Put `grep` or `ack` to good use.
-
-If you added functionality, you should consider documenting it and/or writing
-an example to illustrate your change.
-
-Make sure you update the swagger API spec by running:
-
-```shell
-hack/update-swagger-spec.sh
-```
-
-The API spec changes should be in a commit separate from your other changes.
-
-## Adding new REST objects
-
-TODO(smarterclayton): write this.
-
-## Alpha, Beta, and Stable Versions
-
-New feature development proceeds through a series of stages of increasing maturity:
-
-- Development level
-  - Object Versioning: no convention
-  - Availability: not commited to main kubernetes repo, and thus not available in offical releases
-  - Audience: other developers closely collaborating on a feature or proof-of-concept
-  - Upgradeability, Reliability, Completeness, and Support: no requirements or guarantees
-- Alpha level
-  - Object Versioning: API version name contains `alpha` (e.g. `v1alpha1`)
-  - Availability: committed to main kubernetes repo;  appears in an official release; feature is
-    disabled by default, but may be enabled by flag
-  - Audience: developers and expert users interested in giving early feedback on features
-  - Completeness: some API operations, CLI commands, or UI support may not be implemented;  the API
-    need not have had an *API review* (an intensive and targeted review of the API, on top of a normal
-    code review)
-  - Upgradeability: the object schema and semantics may change in a later software release, without
-    any provision for preserving objects in an existing cluster;
-    removing the upgradability concern allows developers to make rapid progress; in particular,
-    API versions can increment faster than the minor release cadence and the developer need not
-    maintain multiple versions; developers should still increment the API version when object schema
-    or semantics change in an [incompatible way](#on-compatibility)
-  - Cluster Reliability: because the feature is relatively new, and may lack complete end-to-end
-    tests, enabling the feature via a flag might expose bugs with destabilize the cluster (e.g. a
-    bug in a control loop might rapidly create excessive numbers of object, exhausting API storage).
-  - Support: there is *no commitment* from the project to complete the feature; the feature may be
-    dropped entirely in a later software release
-  - Recommended Use Cases: only in short-lived testing clusters, due to complexity of upgradeability
-    and lack of long-term support and lack of upgradability.
-- Beta level:
-  - Object Versioning: API version name contains `beta` (e.g. `v2beta3`)
-  - Availability: in official Kubernetes releases, and enabled by default
-  - Audience: users interested in providing feedback on features
-  - Completeness: all API operations, CLI commands, and UI support should be implemented; end-to-end
-    tests complete; the API has had a thorough API review and is thought to be complete, though use
-    during beta may frequently turn up API issues not thought of during review
-  - Upgradeability: the object schema and semantics may change in a later software release; when
-    this happens, an upgrade path will be documentedr; in some cases, objects will be automatically
-    converted to the new version; in other cases, a manual upgrade may be necessary;  a manual
-    upgrade may require downtime for anything relying on the new feature, and may require
-    manual conversion of objects to the new version; when manual conversion is necessary, the
-    project will provide documentation on the process (for an example, see [v1 conversion
-    tips](/{{page.version}}/docs/api/))
-  - Cluster Reliability: since the feature has e2e tests, enabling the feature via a flag should not
-    create new bugs in unrelated features;  because the feature is new, it may have minor bugs
-  - Support: the project commits to complete the feature, in some form, in a subsequent Stable
-    version;  typically this will happen within 3 months, but sometimes longer;  releases should
-    simultaneously support two consecutive versions (e.g. `v1beta1` and `v1beta2`; or `v1beta2` and
-    `v1`) for at least one minor release cycle (typically 3 months) so that users have enough time
-    to upgrade and migrate objects
-  - Recommended Use Cases: in short-lived testing clusters; in production clusters as part of a
-    short-lived evaluation of the feature in order to provide feedback
-- Stable level:
-  - Object Versioning: API version `vX` where `X` is an integer (e.g. `v1`)
-  - Availability: in official Kubernetes releases, and enabled by default
-  - Audience: all users
-  - Completeness: same as beta
-  - Upgradeability: only [strictly compatible](#on-compatibility) changes allowed in subsequent
-    software releases
-  - Cluster Reliability: high
-  - Support: API version will continue to be present for many subsequent software releases;
-  - Recommended Use Cases: any
\ No newline at end of file
diff --git a/v1.2/docs/devel/automation.md b/v1.2/docs/devel/automation.md
deleted file mode 100644
index 09a485b6f9..0000000000
--- a/v1.2/docs/devel/automation.md
+++ /dev/null
@@ -1,103 +0,0 @@
----
----
-
-Kubernetes uses a variety of automated tools in an attempt to relieve developers of repeptitive, low
-brain power work.  This document attempts to describe these processes.
-
-
-## Submit Queue
-
-In an effort to:
-
-   * reduce load on core developers
-   * maintain e2e stability
-   * load test githubs label feature
-
-We have added an automated [submit-queue](https://github.com/kubernetes/contrib/tree/master/submit-queue)
-for kubernetes.
-
-The submit-queue does the following:
-
-```go
-for _, pr := range readyToMergePRs() {
-    if testsAreStable() {
-        mergePR(pr)
-    }
-}
-```
-
-The status of the submit-queue is [online.](http://submit-queue.k8s.io/)
-
-### Ready to merge status
-
-A PR is considered "ready for merging" if it matches the following:
-
-   * it has the `lgtm` label, and that `lgtm` is newer than the latest commit
-   * it has passed the cla pre-submit and has the `cla:yes` label
-   * it has passed the travis and shippable pre-submit tests
-   * one (or all) of
-      * its author is in kubernetes/contrib/submit-queue/whitelist.txt
-      * its author is in contributors.txt via the github API.
-      * the PR has the `ok-to-merge` label
-   * One (or both of)
-      * it has passed the Jenkins e2e test
-      * it has the `e2e-not-required` label
-
-Note that the combined whitelist/committer list is available at [submit-queue.k8s.io](http://submit-queue.k8s.io)
-
-### Merge process
-
-Merges _only_ occur when the `critical builds` (Jenkins e2e for gce, gke, scalability, upgrade) are passing.
-We're open to including more builds here, let us know...
-
-Merges are serialized, so only a single PR is merged at a time, to ensure against races.
-
-If the PR has the `e2e-not-required` label, it is simply merged.
-If the PR does not have this label, e2e tests are re-run, if these new tests pass, the PR is merged.
-
-If e2e flakes or is currently buggy, the PR will not be merged, but it will be re-run on the following
-pass.
-
-## Github Munger
-
-We also run a [github "munger"](https://github.com/kubernetes/contrib/tree/master/mungegithub)
-
-This runs repeatedly over github pulls and issues and runs modular "mungers" similar to "mungedocs"
-
-Currently this runs:
-
-   * blunderbuss - Tries to automatically find an owner for a PR without an owner, uses mapping file here:
-        https://github.com/kubernetes/contrib/blob/master/mungegithub/blunderbuss.yml
-   * needs-rebase - Adds `needs-rebase` to PRs that aren't currently mergeable, and removes it from those that are.
-   * size - Adds `size/xs` - `size/xxl` labels to PRs
-   * ok-to-test - Adds the `ok-to-test` message to PRs that have an `lgtm` but the e2e-builder would otherwise not test due to whitelist
-   * ping-ci - Attempts to ping the ci systems (Travis/Shippable) if they are missing from a PR.
-   * lgtm-after-commit - Removes the `lgtm` label from PRs where there are commits that are newer than the `lgtm` label
-
-In the works:
-   * issue-detector - machine learning for determining if an issue that has been filed is a `support` issue, `bug` or `feature`
-
-Please feel free to unleash your creativity on this tool, send us new mungers that you think will help support the Kubernetes development process.
-
-## PR builder
-
-We also run a robotic PR builder that attempts to run e2e tests for each PR.
-
-Before a PR from an unknown user is run, the PR builder bot (`k8s-bot`) asks to a message from a
-contributor that a PR is "ok to test", the contributor replies with that message.  Contributors can also
-add users to the whitelist by replying with the message "add to whitelist" ("please" is optional, but
-remember to treat your robots with kindness...)
-
-If a PR is approved for testing, and tests either haven't run, or need to be re-run, you can ask the
-PR builder to re-run the tests.  To do this, reply to the PR with a message that begins with `@k8s-bot test this`, this should trigger a re-build/re-test.
-
-
-## FAQ:
-
-#### How can I ask my PR to be tested again for Jenkins failures?
-
-Right now you have to ask a contributor (this may be you!) to re-run the test with "@k8s-bot test this"
-
-### How can I kick Shippable to re-test on a failure?
-
-Right now the easiest way is to close and then immediately re-open the PR.
\ No newline at end of file
diff --git a/v1.2/docs/devel/cherry-picks.md b/v1.2/docs/devel/cherry-picks.md
deleted file mode 100644
index aff93a082c..0000000000
--- a/v1.2/docs/devel/cherry-picks.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
----
-
-This document explains cherry picks are managed on release branches within the
-Kubernetes projects.
-
-## Propose a Cherry Pick
-
-Any contributor can propose a cherry pick of any pull request, like so:
-
-```shell
-hack/cherry_pick_pull.sh upstream/release-3.14 98765
-```
-
-This will walk you through the steps to propose an automated cherry pick of pull
- #98765 for remote branch `upstream/release-3.14`.
-
-## Cherry Pick Review
-
-Cherry pick pull requests are reviewed differently than normal pull requests. In
-particular, they may be self-merged by the release branch owner without fanfare,
-in the case the release branch owner knows the cherry pick was already
-requested - this should not be the norm, but it may happen.
-
-[Contributor License Agreements](http://releases.k8s.io/{{page.githubbranch}}/CONTRIBUTING.md) is considered implicit
-for all code within cherry-pick pull requests, ***unless there is a large
-conflict***.
-
-## Searching for Cherry Picks
-
-Now that we've structured cherry picks as PRs, searching for all cherry-picks
-against a release is a GitHub query: For example,
-[this query is all of the v0.21.x cherry-picks](https://github.com/kubernetes/kubernetes/pulls?utf8=%E2%9C%93&q=is%3Apr+%22automated+cherry+pick%22+base%3Arelease-0.21)
\ No newline at end of file
diff --git a/v1.2/docs/devel/cli-roadmap.md b/v1.2/docs/devel/cli-roadmap.md
deleted file mode 100644
index 9eb5389e45..0000000000
--- a/v1.2/docs/devel/cli-roadmap.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
----
-
-See github issues with the following labels:
-* [area/app-config-deployment](https://github.com/kubernetes/kubernetes/labels/area/app-config-deployment)
-* [component/kubectl](https://github.com/kubernetes/kubernetes/labels/component/kubectl)
-* [component/clientlib](https://github.com/kubernetes/kubernetes/labels/component/clientlib)
-
-
-
diff --git a/v1.2/docs/devel/client-libraries.md b/v1.2/docs/devel/client-libraries.md
deleted file mode 100644
index 4503e90933..0000000000
--- a/v1.2/docs/devel/client-libraries.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
----
-
-### Supported
-
-   * [Go](http://releases.k8s.io/{{page.githubbranch}}/pkg/client/)
-
-### User Contributed
-
-*Note: Libraries provided by outside parties are supported by their authors, not the core Kubernetes team*
-
-   * [Java (OSGi)](https://bitbucket.org/amdatulabs/amdatu-kubernetes)
-   * [Java (Fabric8, OSGi)](https://github.com/fabric8io/kubernetes-client)
-   * [Ruby](https://github.com/Ch00k/kuber)
-   * [Ruby](https://github.com/abonas/kubeclient)
-   * [PHP](https://github.com/devstub/kubernetes-api-php-client)
-   * [PHP](https://github.com/maclof/kubernetes-client)
-   * [Node.js](https://github.com/tenxcloud/node-kubernetes-client)
-   * [Perl](https://metacpan.org/pod/Net::Kubernetes)
-
-
-
diff --git a/v1.2/docs/devel/collab.md b/v1.2/docs/devel/collab.md
deleted file mode 100644
index 8ff16d5b64..0000000000
--- a/v1.2/docs/devel/collab.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
----
-
-Kubernetes is open source, but many of the people working on it do so as their day job.  In order to avoid forcing people to be "at work" effectively 24/7, we want to establish some semi-formal protocols around development.  Hopefully these rules make things go more smoothly.  If you find that this is not the case, please complain loudly.
-
-## Patches welcome
-
-First and foremost: as a potential contributor, your changes and ideas are welcome at any hour of the day or night, weekdays, weekends, and holidays.  Please do not ever hesitate to ask a question or send a PR.
-
-## Code reviews
-
-All changes must be code reviewed.  For non-maintainers this is obvious, since you can't commit anyway.  But even for maintainers, we want all changes to get at least one review, preferably (for non-trivial changes obligatorily) from someone who knows the areas the change touches.  For non-trivial changes we may want two reviewers.  The primary reviewer will make this decision and nominate a second reviewer, if needed.  Except for trivial changes, PRs should not be committed until relevant parties (e.g. owners of the subsystem affected by the PR) have had a reasonable chance to look at PR in their local business hours.
-
-Most PRs will find reviewers organically.  If a maintainer intends to be the primary reviewer of a PR they should set themselves as the assignee on GitHub and say so in a reply to the PR.  Only the primary reviewer of a change should actually do the merge, except in rare cases (e.g. they are unavailable in a reasonable timeframe).
-
-If a PR has gone 2 work days without an owner emerging, please poke the PR thread and ask for a reviewer to be assigned.
-
-Except for rare cases, such as trivial changes (e.g. typos, comments) or emergencies (e.g. broken builds), maintainers should not merge their own changes.
-
-Expect reviewers to request that you avoid [common go style mistakes](https://github.com/golang/go/wiki/CodeReviewComments) in your PRs.
-
-## Assigned reviews
-
-Maintainers can assign reviews to other maintainers, when appropriate. The assignee becomes the shepherd for that PR and is responsible for merging the PR once they are satisfied with it or else closing it.  The assignee might request reviews from non-maintainers.
-
-## Merge hours
-
-Maintainers will do merges of appropriately reviewed-and-approved changes during their local "business hours" (typically 7:00 am Monday to 5:00 pm (17:00h) Friday).  PRs that arrive over the weekend or on holidays will only be merged if there is a very good reason for it and if the code review requirements have been met.  Concretely this means that nobody should merge changes immediately before going to bed for the night.
-
-There may be discussion an even approvals granted outside of the above hours, but merges will generally be deferred.
-
-If a PR is considered complex or controversial, the merge of that PR should be delayed to give all interested parties in all timezones the opportunity to provide feedback.  Concretely, this means that such PRs should be held for 24
-hours before merging.  Of course "complex" and "controversial" are left to the judgment of the people involved, but we trust that part of being a committer is the judgment required to evaluate such things honestly, and not be
-motivated by your desire (or your cube-mate's desire) to get their code merged.  Also see "Holds" below, any reviewer can issue a "hold" to indicate that the PR is in fact complicated or complex and deserves further review.
-
-PRs that are incorrectly judged to be merge-able, may be reverted and subject to re-review, if subsequent reviewers believe that they in fact are controversial or complex.
-
-
-## Holds
-
-Any maintainer or core contributor who wants to review a PR but does not have time immediately may put a hold on a PR simply by saying so on the PR discussion and offering an ETA measured in single-digit days at most.  Any PR that has a hold shall not be merged until the person who requested the hold acks the review, withdraws their hold, or is overruled by a preponderance of maintainers.
\ No newline at end of file
diff --git a/v1.2/docs/devel/development.md b/v1.2/docs/devel/development.md
deleted file mode 100644
index aa9dd687fa..0000000000
--- a/v1.2/docs/devel/development.md
+++ /dev/null
@@ -1,317 +0,0 @@
----
----
-
-# Releases and Official Builds
-
-Official releases are built in Docker containers.  Details are [here](http://releases.k8s.io/{{page.githubbranch}}/build/README.md).  You can do simple builds and development with just a local Docker installation.  If want to build go locally outside of docker, please continue below.
-
-## Go development environment
-
-Kubernetes is written in [Go](http://golang.org) programming language. If you haven't set up Go development environment, please follow [this instruction](http://golang.org/doc/code) to install go tool and set up GOPATH. Ensure your version of Go is at least 1.3.
-
-## Git Setup
-
-Below, we outline one of the more common git workflows that core developers use. Other git workflows are also valid.
-
-### Visual overview
-
-![Git workflow](/images/docs/git_workflow.png)
-
-### Fork the main repository
-
-1. Go to https://github.com/kubernetes/kubernetes
-2. Click the "Fork" button (at the top right)
-
-### Clone your fork
-
-The commands below require that you have $GOPATH set ([$GOPATH docs](https://golang.org/doc/code/#GOPATH)). We highly recommend you put Kubernetes' code into your GOPATH. Note: the commands below will not work if there is more than one directory in your `$GOPATH`.
-
-```shell
-mkdir -p $GOPATH/src/k8s.io
-cd $GOPATH/src/k8s.io
-# Replace "$YOUR_GITHUB_USERNAME" below with your github username
-git clone https://github.com/$YOUR_GITHUB_USERNAME/kubernetes.git
-cd kubernetes
-git remote add upstream 'https://github.com/kubernetes/kubernetes.git'
-```
-
-### Create a branch and make changes
-
-```shell
-git checkout -b myfeature
-# Make your code changes
-```
-
-### Keeping your development fork in sync
-
-```shell
-git fetch upstream
-git rebase upstream/master
-```
-
-Note: If you have write access to the main repository at github.com/kubernetes/kubernetes, you should modify your git configuration so that you can't accidentally push to upstream:
-
-```shell
-git remote set-url --push upstream no_push
-```
-
-### Committing changes to your fork
-
-```shell
-git commit
-git push -f origin myfeature
-```
-
-### Creating a pull request
-
-1. Visit https://github.com/$YOUR_GITHUB_USERNAME/kubernetes
-2. Click the "Compare and pull request" button next to your "myfeature" branch.
-3. Check out the pull request [process](/{{page.version}}/docs/devel/pull-requests) for more details
-
-### When to retain commits and when to squash
-
-Upon merge, all git commits should represent meaningful milestones or units of
-work.  Use commits to add clarity to the development and review process.
-
-Before merging a PR, squash any "fix review feedback", "typo", and "rebased"
-sorts of commits.  It is not imperative that every commit in a PR compile and
-pass tests independently, but it is worth striving for.  For mass automated
-fixups (e.g. automated doc formatting), use one or more commits for the
-changes to tooling and a final commit to apply the fixup en masse.  This makes
-reviews much easier.
-
-See [Faster Reviews](/{{page.version}}/docs/devel/faster_reviews) for more details.
-
-## godep and dependency management
-
-Kubernetes uses [godep](https://github.com/tools/godep) to manage dependencies. It is not strictly required for building Kubernetes but it is required when managing dependencies under the Godeps/ tree, and is required by a number of the build and test scripts. Please make sure that ``godep`` is installed and in your ``$PATH``.
-
-### Installing godep
-
-There are many ways to build and host go binaries. Here is an easy way to get utilities like `godep` installed:
-
-1) Ensure that [mercurial](http://mercurial.selenic.com/wiki/Download) is installed on your system. (some of godep's dependencies use the mercurial
-source control system).  Use `apt-get install mercurial` or `yum install mercurial` on Linux, or [brew.sh](http://brew.sh) on OS X, or download
-directly from mercurial.
-
-2) Create a new GOPATH for your tools and install godep:
-
-```shell
-export GOPATH=$HOME/go-tools
-mkdir -p $GOPATH
-go get github.com/tools/godep
-```
-
-3) Add $GOPATH/bin to your path. Typically you'd add this to your ~/.profile:
-
-```shell
-export GOPATH=$HOME/go-tools
-export PATH=$PATH:$GOPATH/bin
-```
-
-### Using godep
-
-Here's a quick walkthrough of one way to use godeps to add or update a Kubernetes dependency into Godeps/_workspace. For more details, please see the instructions in [godep's documentation](https://github.com/tools/godep).
-
-1) Devote a directory to this endeavor:
-
-_Devoting a separate directory is not required, but it is helpful to separate dependency updates from other changes._
-
-```shell
-export KPATH=$HOME/code/kubernetes
-mkdir -p $KPATH/src/k8s.io/kubernetes
-cd $KPATH/src/k8s.io/kubernetes
-git clone https://path/to/your/fork .
-# Or copy your existing local repo here. IMPORTANT: making a symlink doesn't work.
-```
-
-2) Set up your GOPATH.
-
-```shell
-# Option A: this will let your builds see packages that exist elsewhere on your system.
-export GOPATH=$KPATH:$GOPATH
-# Option B: This will *not* let your local builds see packages that exist elsewhere on your system.
-export GOPATH=$KPATH
-# Option B is recommended if you're going to mess with the dependencies.
-```
-
-3) Populate your new GOPATH.
-
-```shell
-cd $KPATH/src/k8s.io/kubernetes
-godep restore
-```
-
-4) Next, you can either add a new dependency or update an existing one.
-
-```shell
-# To add a new dependency, do:
-cd $KPATH/src/k8s.io/kubernetes
-go get path/to/dependency
-# Change code in Kubernetes to use the dependency.
-godep save ./...
-# To update an existing dependency, do:
-cd $KPATH/src/k8s.io/kubernetes
-go get -u path/to/dependency
-# Change code in Kubernetes accordingly if necessary.
-godep update path/to/dependency/...
-```
-
-_If `go get -u path/to/dependency` fails with compilation errors, instead try `go get -d -u path/to/dependency`
-to fetch the dependencies without compiling them.  This can happen when updating the cadvisor dependency._
-
-
-5) Before sending your PR, it's a good idea to sanity check that your Godeps.json file is ok by running hack/verify-godeps.sh
-
-_If hack/verify-godeps.sh fails after a `godep update`, it is possible that a transitive dependency was added or removed but not
-updated by godeps.  It then may be necessary to perform a `godep save ./...` to pick up the transitive dependency changes._
-
-It is sometimes expedient to manually fix the /Godeps/godeps.json file to minimize the changes.
-
-Please send dependency updates in separate commits within your PR, for easier reviewing.
-
-## Hooks
-
-Before committing any changes, please link/copy these hooks into your .git
-directory. This will keep you from accidentally committing non-gofmt'd go code.
-
-```shell
-cd kubernetes/.git/hooks/
-ln -s ../../hooks/pre-commit .
-```
-
-## Unit tests
-
-```shell
-cd kubernetes
-hack/test-go.sh
-```
-
-Alternatively, you could also run:
-
-```shell
-cd kubernetes
-godep go test ./...
-```
-
-If you only want to run unit tests in one package, you could run ``godep go test`` under the package directory. For example, the following commands will run all unit tests in package kubelet:
-
-```shell
-$ cd kubernetes # step into the kubernetes directory.
-$ cd pkg/kubelet
-$ godep go test
-# some output from unit tests
-PASS
-ok      k8s.io/kubernetes/pkg/kubelet   0.317s
-```
-
-## Coverage
-
-Currently, collecting coverage is only supported for the Go unit tests.
-
-To run all unit tests and generate an HTML coverage report, run the following:
-
-```shell
-cd kubernetes
-KUBE_COVER=y hack/test-go.sh
-```
-
-At the end of the run, an the HTML report will be generated with the path printed to stdout.
-
-To run tests and collect coverage in only one package, pass its relative path under the `kubernetes` directory as an argument, for example:
-
-```shell
-cd kubernetes
-KUBE_COVER=y hack/test-go.sh pkg/kubectl
-```
-
-Multiple arguments can be passed, in which case the coverage results will be combined for all tests run.
-
-Coverage results for the project can also be viewed on [Coveralls](https://coveralls.io/r/kubernetes/kubernetes), and are continuously updated as commits are merged. Additionally, all pull requests which spawn a Travis build will report unit test coverage results to Coveralls. Coverage reports from before the Kubernetes Github organization was created can be found [here](https://coveralls.io/r/GoogleCloudPlatform/kubernetes).
-
-## Integration tests
-
-You need an [etcd](https://github.com/coreos/etcd/releases/tag/v2.0.0) in your path, please make sure it is installed and in your ``$PATH``.
-
-```shell
-cd kubernetes
-hack/test-integration.sh
-```
-
-## End-to-End tests
-
-You can run an end-to-end test which will bring up a master and two nodes, perform some tests, and then tear everything down. Make sure you have followed the getting started steps for your chosen cloud platform (which might involve changing the `KUBERNETES_PROVIDER` environment variable to something other than "gce".
-
-```shell
-cd kubernetes
-hack/e2e-test.sh
-```
-
-Pressing control-C should result in an orderly shutdown but if something goes wrong and you still have some VMs running you can force a cleanup with this command:
-
-```shell
-go run hack/e2e.go --down
-```
-
-### Flag options
-
-See the flag definitions in `hack/e2e.go` for more options, such as reusing an existing cluster, here is an overview:
-
-```shell
-# Build binaries for testing
-go run hack/e2e.go --build
-# Create a fresh cluster.  Deletes a cluster first, if it exists
-go run hack/e2e.go --up
-# Create a fresh cluster at a specific release version.
-go run hack/e2e.go --up --version=0.7.0
-# Test if a cluster is up.
-go run hack/e2e.go --isup
-# Push code to an existing cluster
-go run hack/e2e.go --push
-# Push to an existing cluster, or bring up a cluster if it's down.
-go run hack/e2e.go --pushup
-# Run all tests
-go run hack/e2e.go --test
-# Run tests matching the regex "Pods.*env"
-go run hack/e2e.go -v -test --test_args="--ginkgo.focus=Pods.*env"
-# Alternately, if you have the e2e cluster up and no desire to see the event stream, you can run ginkgo-e2e.sh directly:
-hack/ginkgo-e2e.sh --ginkgo.focus=Pods.*env
-```
-
-### Combining flags
-
-```shell
-# Flags can be combined, and their actions will take place in this order:
-# -build, -push|-up|-pushup, -test|-tests=..., -down
-# e.g.:
-go run hack/e2e.go -build -pushup -test -down
-# -v (verbose) can be added if you want streaming output instead of only
-# seeing the output of failed commands.
-# -ctl can be used to quickly call kubectl against your e2e cluster. Useful for
-# cleaning up after a failed test or viewing logs. Use -v to avoid suppressing
-# kubectl output.
-go run hack/e2e.go -v -ctl='get events'
-go run hack/e2e.go -v -ctl='delete pod foobar'
-```
-
-## Conformance testing
-
-End-to-end testing, as described above, is for [development
-distributions](/{{page.version}}/docs/devel/writing-a-getting-started-guide).  A conformance test is used on
-a [versioned distro](/{{page.version}}/docs/devel/writing-a-getting-started-guide).
-
-The conformance test runs a subset of the e2e-tests against a manually-created cluster.  It does not
-require support for up/push/down and other operations.  To run a conformance test, you need to know the
-IP of the master for your cluster and the authorization arguments to use.  The conformance test is
-intended to run against a cluster at a specific binary release of Kubernetes.
-See [conformance-test.sh](http://releases.k8s.io/{{page.githubbranch}}/hack/conformance-test.sh).
-
-## Testing out flaky tests
-
-[Instructions here](/{{page.version}}/docs/devel/flaky-tests)
-
-## Regenerating the CLI documentation
-
-```shell
-hack/update-generated-docs.sh
-```
\ No newline at end of file
diff --git a/v1.2/docs/devel/e2e-tests.md b/v1.2/docs/devel/e2e-tests.md
deleted file mode 100644
index 09537e9273..0000000000
--- a/v1.2/docs/devel/e2e-tests.md
+++ /dev/null
@@ -1,112 +0,0 @@
----
----
-
-The end-2-end tests for kubernetes provide a mechanism to test behavior of the system, and to ensure end user operations match developer specifications.  In distributed systems it is not uncommon that a minor change may pass all unit tests, but cause unforseen changes at the system level.  Thus, the primary objectives of the end-2-end tests are to ensure a consistent and reliable behavior of the kubernetes code base, and to catch bugs early.
-
-The end-2-end tests in kubernetes are built atop of [ginkgo] (http://onsi.github.io/ginkgo/) and [gomega] (http://onsi.github.io/gomega/).  There are a host of features that this BDD testing framework provides, and it is recommended that the developer read the documentation prior to diving into the tests.
-
-The purpose of *this* document is to serve as a primer for developers who are looking to execute, or add tests, using a local development environment.
-
-## Building and Running the Tests
-
-**NOTE:** The tests have an array of options.  For simplicity, the examples will focus on leveraging the tests on a local cluster using `sudo ./hack/local-up-cluster.sh`
-
-### Building the Tests
-
-The tests are built into a single binary which can be run against any deployed kubernetes system.  To build the tests, navigate to your source directory and execute:
-
-`$ make all`
-
-The output for the end-2-end tests will be a single binary called `e2e.test` under the default output directory, which is typically `_output/local/bin/linux/amd64/`.  Within the repository there are scripts that are provided under the `./hack` directory that are helpful for automation, but may not apply for a local development purposes.  Instead, we recommend familiarizing yourself with the executable options.  To obtain the full list of options, run the following:
-
-`$ ./e2e.test --help`
-
-### Running the Tests
-
-For the purposes of brevity, we will look at a subset of the options, which are listed below:
-
-```shell
--ginkgo.dryRun=false: If set, ginkgo will walk the test hierarchy without actually running anything.  Best paired with -v.
--ginkgo.failFast=false: If set, ginkgo will stop running a test suite after a failure occurs.
--ginkgo.failOnPending=false: If set, ginkgo will mark the test suite as failed if any specs are pending.
--ginkgo.focus="": If set, ginkgo will only run specs that match this regular expression.
--ginkgo.skip="": If set, ginkgo will only run specs that do not match this regular expression.
--ginkgo.trace=false: If set, default reporter prints out the full stack trace when a failure occurs
--ginkgo.v=false: If set, default reporter print out all specs as they begin.
--host="": The host, or api-server, to connect to
--kubeconfig="": Path to kubeconfig containing embedded authinfo.
--prom-push-gateway="": The URL to prometheus gateway, so that metrics can be pushed during e2es and scraped by prometheus. Typically something like 127.0.0.1:9091.
--provider="": The name of the Kubernetes provider (gce, gke, local, vagrant, etc.)
--repo-root="../../": Root directory of kubernetes repository, for finding test files.
-```
-
-Prior to running the tests, it is recommended that you first create a simple auth file in your home directory, e.g. `$HOME/.kubernetes_auth` , with the following:
-
-```json
-{
-  "User": "root",
-  "Password": ""
-}
-```
-
-Next, you will need a cluster that you can test against.  As mentioned earlier, you will want to execute `sudo ./hack/local-up-cluster.sh`.  To get a sense of what tests exist, you may want to run:
-
-```shell
-e2e.test --host="127.0.0.1:8080" --provider="local" --ginkgo.v=true -ginkgo.dryRun=true --kubeconfig="$HOME/.kubernetes_auth" --repo-root="$KUBERNETES_SRC_PATH"
-```
-
-If you wish to execute a specific set of tests you can use the `-ginkgo.focus=` regex, e.g.:
-
-```shell
-e2e.test ... --ginkgo.focus="DNS|(?i)nodeport(?-i)|kubectl guestbook"
-```
-
-Conversely, if you wish to exclude a set of tests, you can run:
-
-```shell
-e2e.test ... --ginkgo.skip="Density|Scale"
-```
-
-As mentioned earlier there are a host of other options that are available, but are left to the developer
-
-**NOTE:** If you are running tests on a local cluster repeatedly, you may need to periodically perform some manual cleanup.
-- `rm -rf /var/run/kubernetes`, clear kube generated credentials, sometimes stale permissions can cause problems.
-- `sudo iptables -F`, clear ip tables rules left by the kube-proxy.
-
-## Adding a New Test
-
-As mentioned above, prior to adding a new test, it is a good idea to perform a `-ginkgo.dryRun=true` on the system, in order to see if a behavior is already being tested, or to determine if it may be possible to augment an existing set of tests for a specific use case.
-
-If a behavior does not currently have coverage and a developer wishes to add a new e2e test, navigate to the ./test/e2e directory and create a new test using the existing suite as a guide.
-
-**TODO:** Create a self-documented example which has been disabled, but can be copied to create new tests and outlines the capabilities and libraries used.
-
-## Performance Evaluation
-
-Another benefit of the end-2-end tests is the ability to create reproducible loads on the system, which can then be used to determine the responsiveness, or analyze other characteristics of the system.  For example, the density tests load the system to 30,50,100 pods per/node and measures the different characteristics of the system, such as throughput, api-latency, etc.
-
-For a good overview of how we analyze performance data, please read the following [post](http://blog.kubernetes.io/2015/09/kubernetes-performance-measurements-and)
-
-For developers who are interested in doing their own performance analysis, we recommend setting up [prometheus](http://prometheus.io/) for data collection, and using [promdash](http://prometheus.io/docs/visualization/promdash/) to visualize the data.  There also exists the option of pushing your own metrics in from the tests using a [prom-push-gateway](http://prometheus.io/docs/instrumenting/pushing/).  Containers for all of these components can be found [here](https://hub.docker.com/u/prom/).
-
-For more accurate measurements, you may wish to set up prometheus external to kubernetes in an environment where it can access the major system components (api-server, controller-manager, scheduler).  This is especially useful when attempting to gather metrics in a load-balanced api-server environment, because all api-servers can be analyzed independently as well as collectively. On startup, configuration file is passed to prometheus that specifies the endpoints that prometheus will scrape, as well as the sampling interval.
-
-**prometheus.conf**
-
-```conf
-job: {
-      name: "kubernetes"
-      scrape_interval: "1s"
-      target_group: {
-		# apiserver(s)
-		target: "http://localhost:8080/metrics"
-		# scheduler 
-		target: "http://localhost:10251/metrics"
-		# controller-manager
-		target: "http://localhost:10252/metrics"
-      }
-```
-
-Once prometheus is scraping the kubernetes endpoints, that data can then be plotted using promdash, and alerts can be created against the assortment of metrics that kubernetes provides.
-
-**HAPPY TESTING!**
diff --git a/v1.2/docs/devel/flaky-tests.md b/v1.2/docs/devel/flaky-tests.md
deleted file mode 100644
index dc5d4973e4..0000000000
--- a/v1.2/docs/devel/flaky-tests.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
----
-
-Sometimes unit tests are flaky.  This means that due to (usually) race conditions, they will occasionally fail, even though most of the time they pass.
-
-We have a goal of 99.9% flake free tests.  This means that there is only one flake in one thousand runs of a test.
-
-Running a test 1000 times on your own machine can be tedious and time consuming.  Fortunately, there is a better way to achieve this using Kubernetes.
-
-_Note: these instructions are mildly hacky for now, as we get run once semantics and logging they will get better_
-
-There is a testing image `brendanburns/flake` up on the docker hub.  We will use this image to test our fix.
-
-Create a replication controller with the following config:
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: flakecontroller
-spec:
-  replicas: 24
-  template:
-    metadata:
-      labels:
-        name: flake
-    spec:
-      containers:
-      - name: flake
-        image: brendanburns/flake
-        env:
-        - name: TEST_PACKAGE
-          value: pkg/tools
-        - name: REPO_SPEC
-          value: https://github.com/kubernetes/kubernetes
-```
-
-Note that we omit the labels and the selector fields of the replication controller, because they will be populated from the labels field of the pod template by default.
-
-```shell
-kubectl create -f ./controller.yaml
-```
-
-This will spin up 24 instances of the test.  They will run to completion, then exit, and the kubelet will restart them, accumulating more and more runs of the test.
-You can examine the recent runs of the test by calling `docker ps -a` and looking for tasks that exited with non-zero exit codes. Unfortunately, docker ps -a only keeps around the exit status of the last 15-20 containers with the same image, so you have to check them frequently.
-You can use this script to automate checking for failures, assuming your cluster is running on GCE and has four nodes:
-
-```shell
-echo "" > output.txt
-for i in {1..4}; do
-  echo "Checking kubernetes-minion-${i}"
-  echo "kubernetes-minion-${i}:" >> output.txt
-  gcloud compute ssh "kubernetes-minion-${i}" --command="sudo docker ps -a" >> output.txt
-done
-grep "Exited ([^0])" output.txt
-```
-
-Eventually you will have sufficient runs for your purposes. At that point you can stop and delete the replication controller by running:
-
-```shell
-kubectl stop replicationcontroller flakecontroller
-```
-
-If you do a final check for flakes with `docker ps -a`, ignore tasks that exited -1, since that's what happens when you stop the replication controller.
-
-Happy flake hunting!
\ No newline at end of file
diff --git a/v1.2/docs/devel/getting-builds.md b/v1.2/docs/devel/getting-builds.md
deleted file mode 100644
index e0d950b14c..0000000000
--- a/v1.2/docs/devel/getting-builds.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
----
-
-You can use [hack/get-build.sh](http://releases.k8s.io/{{page.githubbranch}}/hack/get-build.sh) to or use as a reference on how to get the most recent builds with curl. With `get-build.sh` you can grab the most recent stable build, the most recent release candidate, or the most recent build to pass our ci and gce e2e tests (essentially a nightly build).
-
-Run `./hack/get-build.sh -h` for its usage.
-
-For example, to get a build at a specific version (v1.0.2):
-
-```shell
-./hack/get-build.sh v1.0.2
-```
-
-Alternatively, to get the latest stable release:
-
-```shell
-./hack/get-build.sh release/stable
-```
-
-Finally, you can just print the latest or stable version:
-
-```shell
-./hack/get-build.sh -v ci/latest
-```
-
-You can also use the gsutil tool to explore the Google Cloud Storage release buckets. Here are some examples:
-
-```shell
-gsutil cat gs://kubernetes-release/ci/latest.txt          # output the latest ci version number
-gsutil cat gs://kubernetes-release/ci/latest-green.txt    # output the latest ci version number that passed gce e2e
-gsutil ls gs://kubernetes-release/ci/v0.20.0-29-g29a55cc/ # list the contents of a ci release
-gsutil ls gs://kubernetes-release/release                 # list all official releases and rcs
-```
diff --git a/v1.2/docs/devel/index.md b/v1.2/docs/devel/index.md
deleted file mode 100644
index 54f8ec5f99..0000000000
--- a/v1.2/docs/devel/index.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
----
-
-The developer guide is for anyone wanting to either write code which directly accesses the
-Kubernetes API, or to contribute directly to the Kubernetes project.
-It assumes some familiarity with concepts in the [User Guide](/{{page.version}}/docs/user-guide/) and the [Cluster Admin
-Guide](/{{page.version}}/docs/admin/).
-
-
-## The process of developing and contributing code to the Kubernetes project
-
-* **On Collaborative Development** ([collab.md](/{{page.version}}/docs/devel/collab)): Info on pull requests and code reviews.
-
-* **GitHub Issues** ([issues.md](/{{page.version}}/docs/devel/issues)): How incoming issues are reviewed and prioritized.
-
-* **Pull Request Process** ([pull-requests.md](/{{page.version}}/docs/devel/pull-requests)): When and why pull requests are closed.
-
-* **Faster PR reviews** ([faster_reviews.md](/{{page.version}}/docs/devel/faster_reviews)): How to get faster PR reviews.
-
-* **Getting Recent Builds** ([getting-builds.md](/{{page.version}}/docs/devel/getting-builds)): How to get recent builds including the latest builds that pass CI.
-
-* **Automated Tools** ([automation.md](/{{page.version}}/docs/devel/automation)): Descriptions of the automation that is running on our github repository.
-
-
-## Setting up your dev environment, coding, and debugging
-
-* **Development Guide** ([development.md](/{{page.version}}/docs/devel/development)): Setting up your development environment.
-
-* **Hunting flaky tests** ([flaky-tests.md](/{{page.version}}/docs/devel/flaky-tests)): We have a goal of 99.9% flake free tests.
-  Here's how to run your tests many times.
-
-* **Logging Conventions** ([logging.md](/{{page.version}}/docs/devel/logging)]: Glog levels.
-
-* **Profiling Kubernetes** ([profiling.md](/{{page.version}}/docs/devel/profiling)): How to plug in go pprof profiler to Kubernetes.
-
-* **Instrumenting Kubernetes with a new metric**
-  ([instrumentation.md](/{{page.version}}/docs/devel/instrumentation)): How to add a new metrics to the
-  Kubernetes code base.
-
-* **Coding Conventions** ([coding-conventions.md](/{{page.version}}/docs/devel/coding-conventions)):
-  Coding style advice for contributors.
-
-
-## Developing against the Kubernetes API
-
-* API objects are explained at [http://kubernetes.io/third_party/swagger-ui/](http://kubernetes.io/third_party/swagger-ui/).
-
-* **Annotations** ([docs/user-guide/annotations.md](/{{page.version}}/docs/user-guide/annotations)): are for attaching arbitrary non-identifying metadata to objects.
-  Programs that automate Kubernetes objects may use annotations to store small amounts of their state.
-
-* **API Conventions** ([api-conventions.md](/{{page.version}}/docs/devel/api-conventions)):
-  Defining the verbs and resources used in the Kubernetes API.
-
-* **API Client Libraries** ([client-libraries.md](/{{page.version}}/docs/devel/client-libraries)):
-  A list of existing client libraries, both supported and user-contributed.
-
-
-## Writing plugins
-
-* **Authentication Plugins** ([docs/admin/authentication.md](/{{page.version}}/docs/admin/authentication)):
-  The current and planned states of authentication tokens.
-
-* **Authorization Plugins** ([docs/admin/authorization.md](/{{page.version}}/docs/admin/authorization)):
-  Authorization applies to all HTTP requests on the main apiserver port.
-  This doc explains the available authorization implementations.
-
-* **Admission Control Plugins** ([admission_control](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/admission_control.md))
-
-
-## Building releases
-
-* **Making release notes** ([making-release-notes.md](/{{page.version}}/docs/devel/making-release-notes)): Generating release nodes for a new release.
-
-* **Releasing Kubernetes** ([releasing.md](/{{page.version}}/docs/devel/releasing)): How to create a Kubernetes release (as in version)
-  and how the version information gets embedded into the built binaries.
-
-
-
diff --git a/v1.2/docs/devel/instrumentation.md b/v1.2/docs/devel/instrumentation.md
deleted file mode 100644
index 95d3e3e4ae..0000000000
--- a/v1.2/docs/devel/instrumentation.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
----
-
-The following is a step-by-step guide for adding a new metric to the Kubernetes code base.
-
-We use the Prometheus monitoring system's golang client library for instrumenting our code. Once you've picked out a file that you want to add a metric to, you should:
-
-1. Import "github.com/prometheus/client_golang/prometheus".
-
-2. Create a top-level var to define the metric. For this, you have to:
-  1. Pick the type of metric. Use a Gauge for things you want to set to a particular value, a Counter for things you want to increment, or a Histogram or Summary for histograms/distributions of values (typically for latency). Histograms are better if you're going to aggregate the values across jobs, while summaries are better if you just want the job to give you a useful summary of the values.
-  2. Give the metric a name and description.
-  3. Pick whether you want to distinguish different categories of things using labels on the metric. If so, add "Vec" to the name of the type of metric you want and add a slice of the label names to the definition.
-
-   https://github.com/kubernetes/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/apiserver/apiserver.go#L53
-   https://github.com/kubernetes/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/kubelet/metrics/metrics.go#L31
-
-3. Register the metric so that prometheus will know to export it.
-
-   https://github.com/kubernetes/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/kubelet/metrics/metrics.go#L74
-   https://github.com/kubernetes/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/apiserver/apiserver.go#L78
-
-4. Use the metric by calling the appropriate method for your metric type (Set, Inc/Add, or Observe, respectively for Gauge, Counter, or Histogram/Summary), first calling WithLabelValues if your metric has any labels
-
-   https://github.com/kubernetes/kubernetes/blob/3ce7fe8310ff081dbbd3d95490193e1d5250d2c9/pkg/kubelet/kubelet.go#L1384
-   https://github.com/kubernetes/kubernetes/blob/cd3299307d44665564e1a5c77d0daa0286603ff5/pkg/apiserver/apiserver.go#L87
-
-
-These are the metric type definitions if you're curious to learn about them or need more information:
-https://github.com/prometheus/client_golang/blob/master/prometheus/gauge.go
-https://github.com/prometheus/client_golang/blob/master/prometheus/counter.go
-https://github.com/prometheus/client_golang/blob/master/prometheus/histogram.go
-https://github.com/prometheus/client_golang/blob/master/prometheus/summary.go
-
-
-
diff --git a/v1.2/docs/devel/issues.md b/v1.2/docs/devel/issues.md
deleted file mode 100644
index 588641a845..0000000000
--- a/v1.2/docs/devel/issues.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
----
-
-A list quick overview of how we will review and prioritize incoming issues at https://github.com/kubernetes/kubernetes/issues
-
-## Priorities
-
-We will use GitHub issue labels for prioritization.  The absence of a priority label means the bug has not been reviewed and prioritized yet.
-
-## Definitions
-
-* P0 - something broken for users, build broken, or critical security issue.  Someone must drop everything and work on it.
-* P1 - must fix for earliest possible binary release (every two weeks)
-* P2 - should be fixed in next major release version
-* P3 - default priority for lower importance bugs that we still want to track and plan to fix at some point
-* design - priority/design is for issues that are used to track design discussions
-* support - priority/support is used for issues tracking user support requests
-* untriaged - anything without a priority/X label will be considered untriaged
\ No newline at end of file
diff --git a/v1.2/docs/devel/kubectl-conventions.md b/v1.2/docs/devel/kubectl-conventions.md
deleted file mode 100644
index 6e961e62e6..0000000000
--- a/v1.2/docs/devel/kubectl-conventions.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
----
-
-Updated: 8/27/2015
-
-* TOC
-{:toc}
-
-
-## Principles
-
-* Strive for consistency across commands
-* Explicit should always override implicit
-  * Environment variables should override default values
-  * Command-line flags should override default values and environment variables
-    * --namespace should also override the value specified in a specified resource
-
-## Command conventions
-
-* Command names are all lowercase, and hyphenated if multiple words.
-* kubectl VERB NOUNs for commands that apply to multiple resource types
-* NOUNs may be specified as TYPE name1 name2 ... or TYPE/name1 TYPE/name2; TYPE is omitted when only a single type is expected
-* Resource types are all lowercase, with no hyphens; both singular and plural forms are accepted
-* NOUNs may also be specified by one or more file arguments: -f file1 -f file2 ...
-* Resource types may have 2- or 3-letter aliases.
-* Business logic should be decoupled from the command framework, so that it can be reused independently of kubectl, cobra, etc.
-  * Ideally, commonly needed functionality would be implemented server-side in order to avoid problems typical of "fat" clients and to make it readily available to non-Go clients
-* Commands that generate resources, such as `run` or `expose`, should obey the following conventions:
-  * Flags should be converted to a parameter Go map or json map prior to invoking the generator
-  * The generator must be versioned so that users depending on a specific behavior may pin to that version, via `--generator=`
-  * Generation should be decoupled from creation
-  * `--dry-run` should output the resource that would be created, without creating it
-* A command group (e.g., `kubectl config`) may be used to group related non-standard commands, such as custom generators, mutations, and computations
-
-## Flag conventions
-
-* Flags are all lowercase, with words separated by hyphens
-* Flag names and single-character aliases should have the same meaning across all commands
-* Command-line flags corresponding to API fields should accept API enums exactly (e.g., --restart=Always)
-* Do not reuse flags for different semantic purposes, and do not use different flag names for the same semantic purpose -- grep for `"Flags()"` before adding a new flag
-* Use short flags sparingly, only for the most frequently used options, prefer lowercase over uppercase for the most common cases, try to stick to well known conventions for UNIX commands and/or Docker, where they exist, and update this list when adding new short flags
-  * `-f`: Resource file
-    * also used for `--follow` in `logs`, but should be deprecated in favor of `-F`
-  * `-l`: Label selector
-    * also used for `--labels` in `expose`, but should be deprecated
-  * `-L`: Label columns
-  * `-c`: Container
-    * also used for `--client` in `version`, but should be deprecated
-  * `-i`: Attach stdin
-  * `-t`: Allocate TTY
-    * also used for `--template`, but deprecated
-  * `-w`: Watch (currently also used for `--www` in `proxy`, but should be deprecated)
-  * `-p`: Previous
-    * also used for `--pod` in `exec`, but deprecated
-    * also used for `--patch` in `patch`, but should be deprecated
-    * also used for `--port` in `proxy`, but should be deprecated
-  * `-P`: Static file prefix in `proxy`, but should be deprecated
-  * `-r`: Replicas
-  * `-u`: Unix socket
-  * `-v`: Verbose logging level
-* `--dry-run`: Don't modify the live state; simulate the mutation and display the output
-* `--local`: Don't contact the server; just do local read, transformation, generation, etc. and display the output
-* `--output-version=...`: Convert the output to a different API group/version
-* `--validate`: Validate the resource schema
-
-## Output conventions
-
-* By default, output is intended for humans rather than programs
-  * However, affordances are made for simple parsing of `get` output
-* Only errors should be directed to stderr
-* `get` commands should output one row per resource, and one resource per row
-  * Column titles and values should not contain spaces in order to facilitate commands that break lines into fields: cut, awk, etc.
-  * By default, `get` output should fit within about 80 columns
-    * Eventually we could perhaps auto-detect width
-    * `-o wide` may be used to display additional columns
-  * The first column should be the resource name, titled `NAME` (may change this to an abbreviation of resource type)
-  * NAMESPACE should be displayed as the first column when --all-namespaces is specified
-  * The last default column should be time since creation, titled `AGE`
-  * `-Lkey` should append a column containing the value of label with key `key`, with `<none>` if not present
-  * json, yaml, Go template, and jsonpath template formats should be supported and encouraged for subsequent processing
-    * Users should use --api-version or --output-version to ensure the output uses the version they expect
-* `describe` commands may output on multiple lines and may include information from related resources, such as events. Describe should add additional information from related resources that a normal user may need to know - if a user would always run "describe resource1" and the immediately want to run a "get type2" or "describe resource2", consider including that info. Examples, persistent volume claims for pods that reference claims, events for most resources, nodes and the pods scheduled on them. When fetching related resources, a targeted field selector should be used in favor of client side filtering of related resources.
-* Mutations should output TYPE/name verbed by default, where TYPE is singular; `-o name` may be used to just display TYPE/name, which may be used to specify resources in other commands
-
-## Documentation conventions
-
-* Commands are documented using Cobra; docs are then auto-generated by `hack/update-generated-docs.sh`.
-  * Use should contain a short usage string for the most common use case(s), not an exhaustive specification
-  * Short should contain a one-line explanation of what the command does
-  * Long may contain multiple lines, including additional information about input, output, commonly used flags, etc.
-  * Example should contain examples
-    * Start commands with `$`
-    * A comment should precede each example command, and should begin with `#`
-* Use "FILENAME" for filenames
-* Use "TYPE" for the particular flavor of resource type accepted by kubectl, rather than "RESOURCE" or "KIND"
-* Use "NAME" for resource names
-
-
diff --git a/v1.2/docs/devel/logging.md b/v1.2/docs/devel/logging.md
deleted file mode 100644
index 355fa3f4e9..0000000000
--- a/v1.2/docs/devel/logging.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
----
-
-The following conventions for the glog levels to use.  [glog](http://godoc.org/github.com/golang/glog) is globally preferred to [log](http://golang.org/pkg/log/) for better runtime control.
-
-* glog.Errorf() - Always an error
-* glog.Warningf() - Something unexpected, but probably not an error
-* glog.Infof() has multiple levels:
-  * glog.V(0) - Generally useful for this to ALWAYS be visible to an operator
-    * Programmer errors
-    * Logging extra info about a panic
-    * CLI argument handling
-  * glog.V(1) - A reasonable default log level if you don't want verbosity.
-    * Information about config (listening on X, watching Y)
-    * Errors that repeat frequently that relate to conditions that can be corrected (pod detected as unhealthy)
-  * glog.V(2) - Useful steady state information about the service and important log messages that may correlate to significant changes in the system.  This is the recommended default log level for most systems.
-    * Logging HTTP requests and their exit code
-    * System state changing (killing pod)
-    * Controller state change events (starting pods)
-    * Scheduler log messages
-  * glog.V(3) - Extended information about changes
-    * More info about system state changes
-  * glog.V(4) - Debug level verbosity (for now)
-    * Logging in particularly thorny parts of code where you may want to come back later and check it
-
-As per the comments, the practical default level is V(2).  Developers and QE environments may wish to run at V(3) or V(4). If you wish to change the log level, you can pass in `-v=X` where X is the desired maximum level to log.
-
-
-
diff --git a/v1.2/docs/devel/making-release-notes.md b/v1.2/docs/devel/making-release-notes.md
deleted file mode 100644
index 79d4efc2ed..0000000000
--- a/v1.2/docs/devel/making-release-notes.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
----
-
-This documents the process for making release notes for a release.
-
-### 1) Note the PR number of the previous release
-
-Find the most-recent PR that was merged with the previous .0 release.  Remember this as $LASTPR.
-_TODO_: Figure out a way to record this somewhere to save the next release engineer time.
-
-Find the most-recent PR that was merged with the current .0 release.  Remember this as $CURRENTPR.
-
-### 2) Run the release-notes tool
-
-```shell
-${KUBERNETES_ROOT}/build/make-release-notes.sh $LASTPR $CURRENTPR
-```
-
-### 3) Trim the release notes
-
-This generates a list of the entire set of PRs merged since the last minor
-release.  It is likely long and many PRs aren't worth mentioning.  If any of the
-PRs were cherrypicked into patches on the last minor release, you should exclude
-them from the current release's notes.
-
-Open up `candidate-notes.md` in your favorite editor.
-
-Remove, regroup, organize to your hearts content.
-
-
-### 4) Update CHANGELOG.md
-
-With the final markdown all set, cut and paste it to the top of `CHANGELOG.md`
-
-### 5) Update the Release page
-
-   * Switch to the [releases](https://github.com/kubernetes/kubernetes/releases) page.
-   * Open up the release you are working on.
-   * Cut and paste the final markdown from above into the release notes
-   * Press Save.
-
-
-
diff --git a/v1.2/docs/devel/profiling.md b/v1.2/docs/devel/profiling.md
deleted file mode 100644
index 7d54cce111..0000000000
--- a/v1.2/docs/devel/profiling.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
----
-
-This document explain how to plug in profiler and how to profile Kubernetes services.
-
-## Profiling library
-
-Go comes with inbuilt 'net/http/pprof' profiling library and profiling web service. The way service works is binding debug/pprof/ subtree on a running webserver to the profiler. Reading from subpages of debug/pprof returns pprof-formatted profiles of the running binary. The output can be processed offline by the tool of choice, or used as an input to handy 'go tool pprof', which can graphically represent the result.
-
-## Adding profiling to services to APIserver.
-
-TL;DR: Add lines:
-
-```go
-m.mux.HandleFunc("/debug/pprof/", pprof.Index)
-m.mux.HandleFunc("/debug/pprof/profile", pprof.Profile)
-m.mux.HandleFunc("/debug/pprof/symbol", pprof.Symbol)
-```
-
-to the init(c *Config) method in 'pkg/master/master.go' and import 'net/http/pprof' package.
-
-In most use cases to use profiler service it's enough to do 'import _ net/http/pprof', which automatically registers a handler in the default http.Server. Slight inconvenience is that APIserver uses default server for intra-cluster communication, so plugging profiler to it is not really useful. In 'pkg/master/server/server.go' more servers are created and started as separate goroutines. The one that is usually serving external traffic is secureServer. The handler for this traffic is defined in 'pkg/master/master.go' and stored in Handler variable. It is created from HTTP multiplexer, so the only thing that needs to be done is adding profiler handler functions to this multiplexer. This is exactly what lines after TL;DR do.
-
-## Connecting to the profiler
-
-Even when running profiler I found not really straightforward to use 'go tool pprof' with it. The problem is that at least for dev purposes certificates generated for APIserver are not signed by anyone trusted and because secureServer serves only secure traffic it isn't straightforward to connect to the service. The best workaround I found is by creating an ssh tunnel from the kubernetes_master open unsecured port to some external server, and use this server as a proxy. To save everyone looking for correct ssh flags, it is done by running:
-
-```shell
-ssh kubernetes_master -L<local_port>:localhost:8080
-```
-
-or analogous one for you Cloud provider. Afterwards you can e.g. run
-
-```shell
-go tool pprof http://localhost:<local_port>/debug/pprof/profile
-```
-
-to get 30 sec. CPU profile.
-
-## Contention profiling
-
-To enable contention profiling you need to add line `rt.SetBlockProfileRate(1)` in addition to `m.mux.HandleFunc(...)` added before (`rt` stands for `runtime` in `master.go`). This enables 'debug/pprof/block' subpage, which can be used as an input to `go tool pprof`.
-
-
-
diff --git a/v1.2/docs/devel/scheduler.md b/v1.2/docs/devel/scheduler.md
deleted file mode 100755
index 6856e9f140..0000000000
--- a/v1.2/docs/devel/scheduler.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
----
-
-The Kubernetes scheduler runs as a process alongside the other master
-components such as the API server. Its interface to the API server is to watch
-for Pods with an empty PodSpec.NodeName, and for each Pod, it posts a Binding
-indicating where the Pod should be scheduled.
-
-## The scheduling process
-
-The scheduler tries to find a node for each Pod, one at a time, as it notices
-these Pods via watch. There are three steps. First it applies a set of "predicates" that filter out
-inappropriate nodes. For example, if the PodSpec specifies resource requests, then the scheduler
-will filter out nodes that don't have at least that much resources available (computed
-as the capacity of the node minus the sum of the resource requests of the containers that
-are already running on the node). Second, it applies a set of "priority functions"
-that rank the nodes that weren't filtered out by the predicate check. For example,
-it tries to spread Pods across nodes while at the same time favoring the least-loaded
-nodes (where "load" here is sum of the resource requests of the containers running on the node,
-divided by the node's capacity).
-Finally, the node with the highest priority is chosen
-(or, if there are multiple such nodes, then one of them is chosen at random). The code
-for this main scheduling loop is in the function `Schedule()` in
-[plugin/pkg/scheduler/generic_scheduler.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/generic_scheduler.go)
-
-## Scheduler extensibility
-
-The scheduler is extensible: the cluster administrator can choose which of the pre-defined
-scheduling policies to apply, and can add new ones. The built-in predicates and priorities are
-defined in [plugin/pkg/scheduler/algorithm/predicates/predicates.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithm/predicates/predicates.go) and
-[plugin/pkg/scheduler/algorithm/priorities/priorities.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithm/priorities/priorities.go), respectively.
-The policies that are applied when scheduling can be chosen in one of two ways. Normally,
-the policies used are selected by the functions `defaultPredicates()` and `defaultPriorities()` in
-[plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go).
-However, the choice of policies
-can be overridden by passing the command-line flag `--policy-config-file` to the scheduler, pointing to a JSON
-file specifying which scheduling policies to use. See
-[examples/scheduler-policy-config.json](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/scheduler-policy-config.json) for an example
-config file. (Note that the config file format is versioned; the API is defined in
-[plugin/pkg/scheduler/api](http://releases.k8s.io/{{page.githubbranch}}/plugin/pkg/scheduler/api/)).
-Thus to add a new scheduling policy, you should modify predicates.go or priorities.go,
-and either register the policy in `defaultPredicates()` or `defaultPriorities()`, or use a policy config file.
-
-## Exploring the code
-
-If you want to get a global picture of how the scheduler works, you can start in
-[plugin/cmd/kube-scheduler/app/server.go](http://releases.k8s.io/{{page.githubbranch}}/plugin/cmd/kube-scheduler/app/server.go)
-
-
-
diff --git a/v1.2/docs/devel/writing-a-getting-started-guide.md b/v1.2/docs/devel/writing-a-getting-started-guide.md
deleted file mode 100644
index 65e615eb9a..0000000000
--- a/v1.2/docs/devel/writing-a-getting-started-guide.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
----
-
-This page gives some advice for anyone planning to write or update a Getting Started Guide for Kubernetes.
-It also gives some guidelines which reviewers should follow when reviewing a pull request for a
-guide.
-
-A Getting Started Guide is instructions on how to create a Kubernetes cluster on top of a particular
-type(s) of infrastructure.  Infrastructure includes: the IaaS provider for VMs;
-the node OS; inter-node networking; and node Configuration Management system.
-A guide refers to scripts, Configuration Management files, and/or binary assets such as RPMs.  We call
-the combination of all these things needed to run on a particular type of infrastructure a
-**distro**.
-
-[The Matrix](/{{page.version}}/docs/getting-started-guides/) lists the distros.  If there is already a guide
-which is similar to the one you have planned, consider improving that one.
-
-
-Distros fall into two categories:
-
-  - **versioned distros** are tested to work with a particular binary release of Kubernetes.  These
-    come in a wide variety, reflecting a wide range of ideas and preferences in how to run a cluster.
-  - **development distros** are tested work with the latest Kubernetes source code.  But, there are
-    relatively few of these and the bar is much higher for creating one.  They must support
-    fully automated cluster creation, deletion, and upgrade.
-
-There are different guidelines for each.
-
-## Versioned Distro Guidelines
-
-These guidelines say *what* to do.  See the Rationale section for *why*.
-
- - Send us a PR.
- - Put the instructions in `docs/getting-started-guides/...`. Scripts go there too.  This helps devs easily
-   search for uses of flags by guides.
- - We may ask that you host binary assets or large amounts of code in our `contrib` directory or on your
-   own repo.
- - Add or update a row in [The Matrix](/{{page.version}}/docs/getting-started-guides/).
- - State the binary version of Kubernetes that you tested clearly in your Guide doc.
- - Setup a cluster and run the [conformance test](/{{page.version}}/docs/devel/development/#conformance-testing) against it, and report the
-   results in your PR.
- - Versioned distros should typically not modify or add code in `cluster/`.  That is just scripts for developer
-   distros.
- - When a new major or minor release of Kubernetes comes out, we may also release a new
-   conformance test, and require a new conformance test run to earn a conformance checkmark.
-
-If you have a cluster partially working, but doing all the above steps seems like too much work,
-we still want to hear from you.  We suggest you write a blog post or a Gist, and we will link to it on our wiki page.
-Just file an issue or chat us on [Slack](/{{page.version}}/docs/troubleshooting/#slack) and one of the committers will link to it from the wiki.
-
-## Development Distro Guidelines
-
-These guidelines say *what* to do.  See the Rationale section for *why*.
-
-  - the main reason to add a new development distro is to support a new IaaS provider (VM and
-    network management).  This means implementing a new `pkg/cloudprovider/providers/$IAAS_NAME`.
-  - Development distros should use Saltstack for Configuration Management.
-  - development distros need to support automated cluster creation, deletion, upgrading, etc.
-    This mean writing scripts in `cluster/$IAAS_NAME`.
-  - all commits to the tip of this repo need to not break any of the development distros
-    - the author of the change is responsible for making changes necessary on all the cloud-providers if the
-      change affects any of them, and reverting the change if it breaks any of the CIs.
-  - a development distro needs to have an organization which owns it.  This organization needs to:
-    - Setting up and maintaining Continuous Integration that runs e2e frequently (multiple times per day) against the
-      Distro at head,  and which notifies all devs of breakage.
-    - being reasonably available for questions and assisting with
-      refactoring and feature additions that affect code for their IaaS.
-
-## Rationale
-
- - We want people to create Kubernetes clusters with whatever IaaS, Node OS,
-   configuration management tools, and so on, which they are familiar with.  The
-   guidelines for **versioned distros** are designed for flexibility.
- - We want developers to be able to work without understanding all the permutations of
-   IaaS, NodeOS, and configuration management.  The guidelines for **developer distros** are designed
-   for consistency.
- - We want users to have a uniform experience with Kubernetes whenever they follow instructions anywhere
-   in our Github repository.  So, we ask that versioned distros pass a **conformance test** to make sure
-   really work.
- - We want to **limit the number of development distros** for several reasons.  Developers should
-   only have to change a limited number of places to add a new feature.  Also, since we will
-   gate commits on passing CI for all distros, and since end-to-end tests are typically somewhat
-   flaky, it would be highly likely for there to be false positives and CI backlogs with many CI pipelines.
- - We do not require versioned distros to do **CI** for several reasons.  It is a steep
-   learning curve to understand our automated testing scripts.  And it is considerable effort
-   to fully automate setup and teardown of a cluster, which is needed for CI.  And, not everyone
-   has the time and money to run CI.  We do not want to
-   discourage people from writing and sharing guides because of this.
- - Versioned distro authors are free to run their own CI and let us know if there is breakage, but we
-   will not include them as commit hooks -- there cannot be so many commit checks that it is impossible
-   to pass them all.
- - We prefer a single Configuration Management tool for development distros.  If there were more
-   than one, the core developers would have to learn multiple tools and update config in multiple
-   places.  **Saltstack** happens to be the one we picked when we started the project.  We
-   welcome versioned distros that use any tool; there are already examples of
-   CoreOS Fleet, Ansible, and others.
- - You can still run code from head or your own branch
-   if you use another Configuration Management tool -- you just have to do some manual steps
-   during testing and deployment.
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/azure.md b/v1.2/docs/getting-started-guides/azure.md
deleted file mode 100644
index a1d446aef1..0000000000
--- a/v1.2/docs/getting-started-guides/azure.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
----
-
-
-## Getting started on Microsoft Azure
-
-Checkout the [coreos azure getting started guide](/{{page.version}}/docs/getting-started-guides/coreos/azure/)
-
-
-
diff --git a/v1.2/docs/getting-started-guides/binary_release.md b/v1.2/docs/getting-started-guides/binary_release.md
deleted file mode 100644
index 11eb0bb83c..0000000000
--- a/v1.2/docs/getting-started-guides/binary_release.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
----
-
-You can either build a release from sources or download a pre-built release.  If you do not plan on developing Kubernetes itself, we suggest a pre-built release.
-
-### Prebuilt Binary Release
-
-The list of binary releases is available for download from the [GitHub Kubernetes repo release page](https://github.com/kubernetes/kubernetes/releases).
-
-Download the latest release and unpack this tar file on Linux or OS X, cd to the created `kubernetes/` directory, and then follow the getting started guide for your cloud.
-
-### Building from source
-
-Get the Kubernetes source.  If you are simply building a release from source there is no need to set up a full golang environment as all building happens in a Docker container.
-
-Building a release is simple.
-
-```shell
-git clone https://github.com/kubernetes/kubernetes.git
-cd kubernetes
-make release
-```
-
-For more details on the release process see the [`build/` directory](http://releases.k8s.io/{{page.githubbranch}}/build/)
-
-
-
diff --git a/v1.2/docs/getting-started-guides/centos/centos_manual_config.md b/v1.2/docs/getting-started-guides/centos/centos_manual_config.md
deleted file mode 100644
index 9c7b2638ab..0000000000
--- a/v1.2/docs/getting-started-guides/centos/centos_manual_config.md
+++ /dev/null
@@ -1,171 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-You need two machines with CentOS installed on them.
-
-## Starting a cluster
-
-This is a getting started guide for CentOS.  It is a manual configuration so you understand all the underlying packages / services / ports, etc...
-
-This guide will only get ONE node working.  Multiple nodes requires a functional [networking configuration](/{{page.version}}/docs/admin/networking) done outside of kubernetes.  Although the additional Kubernetes configuration requirements should be obvious.
-
-The Kubernetes package provides a few services: kube-apiserver, kube-scheduler, kube-controller-manager, kubelet, kube-proxy.  These services are managed by systemd and the configuration resides in a central location: /etc/kubernetes. We will break the services up between the hosts.  The first host, centos-master, will be the Kubernetes master.  This host will run the kube-apiserver, kube-controller-manager, and kube-scheduler.  In addition, the master will also run _etcd_.  The remaining host, centos-minion will be the node and run kubelet, proxy, cadvisor and docker.
-
-**System Information:**
-
-Hosts:
-
-```conf
-centos-master = 192.168.121.9
-centos-minion = 192.168.121.65
-```
-
-**Prepare the hosts:**
-
-* Create virt7-testing repo on all hosts - centos-{master,minion} with following information.
-
-```conf
-[virt7-testing]
-name=virt7-testing
-baseurl=http://cbs.centos.org/repos/virt7-testing/x86_64/os/
-gpgcheck=0
-```
-
-* Install Kubernetes on all hosts - centos-{master,minion}.  This will also pull in etcd, docker, and cadvisor.
-
-```shell
-yum -y install --enablerepo=virt7-testing kubernetes
-```
-
-* Note * Using etcd-0.4.6-7 (This is temporary update in documentation)
-
-If you do not get etcd-0.4.6-7 installed with virt7-testing repo,
-
-In the current virt7-testing repo, the etcd package is updated which causes service failure. To avoid this,
-
-```shell
-yum erase etcd
-```
-
-It will uninstall the current available etcd package
-
-```shell
-yum install http://cbs.centos.org/kojifiles/packages/etcd/0.4.6/7.el7.centos/x86_64/etcd-0.4.6-7.el7.centos.x86_64.rpm
-yum -y install --enablerepo=virt7-testing kubernetes
-```
-
-* Add master and node to /etc/hosts on all machines (not needed if hostnames already in DNS)
-
-```shell
-echo "192.168.121.9	centos-master
-192.168.121.65	centos-minion" >> /etc/hosts
-```
-
-* Edit `/etc/kubernetes/config` which will be the same on all hosts to contain:
-
-```shell
-# Comma separated list of nodes in the etcd cluster
-KUBE_ETCD_SERVERS="--etcd-servers=http://centos-master:4001"
-
-# logging to stderr means we get it in the systemd journal
-KUBE_LOGTOSTDERR="--logtostderr=true"
-
-# journal message level, 0 is debug
-KUBE_LOG_LEVEL="--v=0"
-
-# Should this cluster be allowed to run privileged docker containers
-KUBE_ALLOW_PRIV="--allow-privileged=false"
-```
-
-* Disable the firewall on both the master and node, as docker does not play well with other firewall rule managers
-
-```shell
-systemctl disable iptables-services firewalld
-systemctl stop iptables-services firewalld
-```
-
-**Configure the Kubernetes services on the master.**
-
-* Edit /etc/kubernetes/apiserver to appear as such:
-
-```shell
-# The address on the local server to listen to.
-KUBE_API_ADDRESS="--address=0.0.0.0"
-
-# The port on the local server to listen on.
-KUBE_API_PORT="--port=8080"
-
-# How the replication controller and scheduler find the kube-apiserver
-KUBE_MASTER="--master=http://centos-master:8080"
-
-# Port kubelets listen on
-KUBELET_PORT="--kubelet-port=10250"
-
-# Address range to use for services
-KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"
-
-# Add your own!
-KUBE_API_ARGS=""
-```
-
-* Start the appropriate services on master:
-
-```shell
-for SERVICES in etcd kube-apiserver kube-controller-manager kube-scheduler; do 
-	systemctl restart $SERVICES
-	systemctl enable $SERVICES
-	systemctl status $SERVICES 
-done
-```
-
-**Configure the Kubernetes services on the node.**
-
-***We need to configure the kubelet and start the kubelet and proxy***
-
-* Edit `/etc/kubernetes/kubelet` to appear as such:
-
-```shell
-# The address for the info server to serve on
-KUBELET_ADDRESS="--address=0.0.0.0"
-
-# The port for the info server to serve on
-KUBELET_PORT="--port=10250"
-
-# You may leave this blank to use the actual hostname
-KUBELET_HOSTNAME="--hostname-override=centos-minion"
-
-# Location of the api-server
-KUBELET_API_SERVER="--api-servers=http://centos-master:8080"
-
-# Add your own!
-KUBELET_ARGS=""
-```
-
-* Start the appropriate services on node (centos-minion).
-
-```shell
-for SERVICES in kube-proxy kubelet docker; do 
-    systemctl restart $SERVICES
-    systemctl enable $SERVICES
-    systemctl status $SERVICES 
-done
-```
-
-*You should be finished!*
-
-* Check to make sure the cluster can see the node (on centos-master)
-
-```shell
-$ kubectl get nodes
-NAME                   LABELS            STATUS
-centos-minion          <none>            Ready
-```
-
-**The cluster should be running! Launch a test pod.**
-
-You should have a functional cluster, check out [101](/{{page.version}}/docs/user-guide/walkthrough/)!
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/cloudstack.md b/v1.2/docs/getting-started-guides/cloudstack.md
deleted file mode 100644
index b70bd0f850..0000000000
--- a/v1.2/docs/getting-started-guides/cloudstack.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
----
-
-CloudStack is a software to build public and private clouds based on hardware virtualization principles (traditional IaaS). To deploy Kubernetes on CloudStack there are several possibilities depending on the Cloud being used and what images are made available. [Exoscale](http://exoscale.ch) for instance makes a [CoreOS](http://coreos.com) template available, therefore instructions to deploy Kubernetes on coreOS can be used. CloudStack also has a vagrant plugin available, hence Vagrant could be used to deploy Kubernetes either using the existing shell provisioner or using new Salt based recipes.
-
-[CoreOS](http://coreos.com) templates for CloudStack are built [nightly](http://stable.release.core-os.net/amd64-usr/current/). CloudStack operators need to [register](http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/templates) this template in their cloud before proceeding with these Kubernetes deployment instructions.
-
-This guide uses an [Ansible playbook](https://github.com/runseb/ansible-kubernetes).
-This is a completely automated, a single playbook deploys Kubernetes based on the coreOS [instructions](/{{page.version}}/docs/getting-started-guides/coreos/coreos_multinode_cluster).
-
-
-This [Ansible](http://ansibleworks.com) playbook deploys Kubernetes on a CloudStack based Cloud using CoreOS images. The playbook, creates an ssh key pair, creates a security group and associated rules and finally starts coreOS instances configured via cloud-init.
-
-
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-    $ sudo apt-get install -y python-pip
-    $ sudo pip install ansible
-    $ sudo pip install cs
-
-[_cs_](https://github.com/exoscale/cs) is a python module for the CloudStack API.
-
-Set your CloudStack endpoint, API keys and HTTP method used.
-
-You can define them as environment variables: `CLOUDSTACK_ENDPOINT`, `CLOUDSTACK_KEY`, `CLOUDSTACK_SECRET` and `CLOUDSTACK_METHOD`.
-
-Or create a `~/.cloudstack.ini` file:
-
-    [cloudstack]
-    endpoint = <your cloudstack api endpoint>
-    key = <your api access key>
-    secret = <your api secret key>
-    method = post
-
-We need to use the http POST method to pass the _large_ userdata to the coreOS instances.
-
-### Clone the playbook
-
-    $ git clone --recursive https://github.com/runseb/ansible-kubernetes.git
-    $ cd ansible-kubernetes
-
-The [ansible-cloudstack](https://github.com/resmo/ansible-cloudstack) module is setup in this repository as a submodule, hence the `--recursive`.
-
-### Create a Kubernetes cluster
-
-You simply need to run the playbook.
-
-    $ ansible-playbook k8s.yml
-
-Some variables can be edited in the `k8s.yml` file.
-
-    vars:
-      ssh_key: k8s
-      k8s_num_nodes: 2
-      k8s_security_group_name: k8s
-      k8s_node_prefix: k8s2
-      k8s_template: Linux CoreOS alpha 435 64-bit 10GB Disk
-      k8s_instance_type: Tiny
-
-This will start a Kubernetes master node and a number of compute nodes (by default 2).
-The `instance_type` and `template` by default are specific to [exoscale](http://exoscale.ch), edit them to specify your CloudStack cloud specific template and instance type (i.e service offering).
-
-Check the tasks and templates in `roles/k8s` if you want to modify anything.
-
-Once the playbook as finished, it will print out the IP of the Kubernetes master:
-
-    TASK: [k8s | debug msg='k8s master IP is {{ k8s_master.default_ip }}'] ********
-
-SSH to it using the key that was created and using the _core_ user and you can list the machines in your cluster:
-
-    $ ssh -i ~/.ssh/id_rsa_k8s core@<master IP>
-    $ fleetctl list-machines
-    MACHINE		IP		       METADATA
-    a017c422...	<node #1 IP>   role=node
-    ad13bf84...	<master IP>	   role=master
-    e9af8293...	<node #2 IP>   role=node
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/coreos.md b/v1.2/docs/getting-started-guides/coreos.md
deleted file mode 100644
index 82cba8d24b..0000000000
--- a/v1.2/docs/getting-started-guides/coreos.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-There are multiple guides on running Kubernetes with [CoreOS](https://coreos.com/kubernetes/docs/latest/):
-
-### Official CoreOS Guides
-
-These guides are maintained by CoreOS and deploy Kubernetes the "CoreOS Way" with full TLS, the DNS add-on, and more. These guides pass Kubernetes conformance testing and we encourage you to [test this yourself](https://coreos.com/kubernetes/docs/latest/conformance-tests).
-
-[**Vagrant Multi-Node**](https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant)
-
-Guide to setting up a multi-node cluster on Vagrant. The deployer can independently configure the number of etcd nodes, master nodes, and worker nodes to bring up a fully HA control plane.
-
-<hr/>
-
-[**Vagrant Single-Node**](https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant-single)
-
-The quickest way to set up a Kubernetes development environment locally. As easy as `git clone`, `vagrant up` and configuring `kubectl`.
-
-<hr/>
-
-[**Full Step by Step Guide**](https://coreos.com/kubernetes/docs/latest/getting-started)
-
-A generic guide to setting up an HA cluster on any cloud or bare metal, with full TLS. Repeat the master or worker steps to configure more machines of that role.
-
-### Community Guides
-
-These guides are maintained by community members, cover specific platforms and use cases, and experiment with different ways of configuring Kubernetes on CoreOS.
-
-[**Multi-node Cluster**](/{{page.version}}/docs/getting-started-guides/coreos/coreos_multinode_cluster)
-
-Set up a single master, multi-worker cluster on your choice of platform: AWS, GCE, or VMware Fusion.
-
-<hr/>
-
-[**Easy Multi-node Cluster on Google Compute Engine**](https://github.com/rimusz/coreos-multi-node-k8s-gce/blob/master/README.md)
-
-Scripted installation of a single master, multi-worker cluster on GCE. Kubernetes components are managed by [fleet](https://github.com/coreos/fleet).
-
-<hr/>
-
-[**Multi-node cluster using cloud-config and Weave on Vagrant**](https://github.com/errordeveloper/weave-demos/blob/master/poseidon/README.md)
-
-Configure a Vagrant-based cluster of 3 machines with networking provided by Weave.
-
-<hr/>
-
-[**Multi-node cluster using cloud-config and Vagrant**](https://github.com/pires/kubernetes-vagrant-coreos-cluster/blob/master/README.md)
-
-Configure a single master, multi-worker cluster locally, running on your choice of hypervisor: VirtualBox, Parallels, or VMware
-
-<hr/>
-
-[**Multi-node cluster with Vagrant and fleet units using a small OS X App**](https://github.com/rimusz/coreos-osx-gui-kubernetes-cluster/blob/master/README.md)
-
-Guide to running a single master, multi-worker cluster controlled by an OS X menubar application. Uses Vagrant under the hood.
-
-<hr/>
-
-[**Resizable multi-node cluster on Azure with Weave**](/{{page.version}}/docs/getting-started-guides/coreos/azure/)
-
-Guide to running an HA etcd cluster with a single master on Azure. Uses the Azure node.js CLI to resize the cluster.
-
-<hr/>
-
-[**Multi-node cluster using cloud-config, CoreOS and VMware ESXi**](https://github.com/xavierbaude/VMware-coreos-multi-nodes-Kubernetes)
-
-Configure a single master, single worker cluster on VMware ESXi.
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/.gitignore b/v1.2/docs/getting-started-guides/coreos/azure/.gitignore
deleted file mode 100644
index c2658d7d1b..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/.gitignore
+++ /dev/null
@@ -1 +0,0 @@
-node_modules/
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/addons/skydns-rc.yaml b/v1.2/docs/getting-started-guides/coreos/azure/addons/skydns-rc.yaml
deleted file mode 100644
index 00a20f3b4a..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/addons/skydns-rc.yaml
+++ /dev/null
@@ -1,92 +0,0 @@
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: kube-dns-v8
-  namespace: kube-system
-  labels:
-    k8s-app: kube-dns
-    version: v8
-    kubernetes.io/cluster-service: "true"
-spec:
-  replicas: 3
-  selector:
-    k8s-app: kube-dns
-    version: v8
-  template:
-    metadata:
-      labels:
-        k8s-app: kube-dns
-        version: v8
-        kubernetes.io/cluster-service: "true"
-    spec:
-      containers:
-      - name: etcd
-        image: gcr.io/google_containers/etcd:2.0.9
-        resources:
-          limits:
-            cpu: 100m
-            memory: 50Mi
-        command:
-        - /usr/local/bin/etcd
-        - -data-dir
-        - /var/etcd/data
-        - -listen-client-urls
-        - http://127.0.0.1:2379,http://127.0.0.1:4001
-        - -advertise-client-urls
-        - http://127.0.0.1:2379,http://127.0.0.1:4001
-        - -initial-cluster-token
-        - skydns-etcd
-        volumeMounts:
-        - name: etcd-storage
-          mountPath: /var/etcd/data
-      - name: kube2sky
-        image: gcr.io/google_containers/kube2sky:1.11
-        resources:
-          limits:
-            cpu: 100m
-            memory: 50Mi
-        args:
-        # command = "/kube2sky"
-        - -domain=kube.local
-        - -kube_master_url=http://kube-00:8080
-      - name: skydns
-        image: gcr.io/google_containers/skydns:2015-03-11-001
-        resources:
-          limits:
-            cpu: 100m
-            memory: 50Mi
-        args:
-        # command = "/skydns"
-        - -machines=http://localhost:4001
-        - -addr=0.0.0.0:53
-        - -domain=kube.local
-        ports:
-        - containerPort: 53
-          name: dns
-          protocol: UDP
-        - containerPort: 53
-          name: dns-tcp
-          protocol: TCP
-        livenessProbe:
-          httpGet:
-            path: /healthz
-            port: 8080
-            scheme: HTTP
-          initialDelaySeconds: 30
-          timeoutSeconds: 5
-      - name: healthz
-        image: gcr.io/google_containers/exechealthz:1.0
-        resources:
-          limits:
-            cpu: 10m
-            memory: 20Mi
-        args:
-        - -cmd=nslookup kubernetes.default.svc.kube.local localhost >/dev/null
-        - -port=8080
-        ports:
-        - containerPort: 8080
-          protocol: TCP
-      volumes:
-      - name: etcd-storage
-        emptyDir: {}
-      dnsPolicy: Default  # Don't use cluster DNS.
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/addons/skydns-svc.yaml b/v1.2/docs/getting-started-guides/coreos/azure/addons/skydns-svc.yaml
deleted file mode 100644
index a0e979c266..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/addons/skydns-svc.yaml
+++ /dev/null
@@ -1,20 +0,0 @@
-apiVersion: v1
-kind: Service
-metadata:
-  name: kube-dns
-  namespace: kube-system
-  labels:
-    k8s-app: kube-dns
-    kubernetes.io/cluster-service: "true"
-    kubernetes.io/name: "KubeDNS"
-spec:
-  selector:
-    k8s-app: kube-dns
-  clusterIP: 10.1.0.3
-  ports:
-  - name: dns
-    port: 53
-    protocol: UDP
-  - name: dns-tcp
-    port: 53
-    protocol: TCP
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/azure-login.js b/v1.2/docs/getting-started-guides/coreos/azure/azure-login.js
deleted file mode 100755
index 624916b2b5..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/azure-login.js
+++ /dev/null
@@ -1,3 +0,0 @@
-#!/usr/bin/env node
-
-require('child_process').fork('node_modules/azure-cli/bin/azure', ['login'].concat(process.argv));
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-etcd-node-template.yml b/v1.2/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-etcd-node-template.yml
deleted file mode 100644
index 4cbb480e53..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-etcd-node-template.yml
+++ /dev/null
@@ -1,19 +0,0 @@
-## This file is used as input to deployment script, which amends it as needed.
-## More specifically, we need to add peer hosts for each but the elected peer.
-
-coreos:
-  units:
-    - name: etcd2.service
-      enable: true
-      command: start
-  etcd2:
-    name: '%H'
-    initial-cluster-token: 'etcd-cluster'
-    initial-advertise-peer-urls: 'http://%H:2380'
-    listen-peer-urls: 'http://%H:2380'
-    listen-client-urls: 'http://0.0.0.0:2379,http://0.0.0.0:4001'
-    advertise-client-urls: 'http://%H:2379,http://%H:4001'
-    initial-cluster-state: 'new'
-  update:
-    group: stable
-    reboot-strategy: off
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml b/v1.2/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml
deleted file mode 100644
index 340c804139..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml
+++ /dev/null
@@ -1,339 +0,0 @@
-## This file is used as input to deployment script, which amends it as needed.
-## More specifically, we need to add environment files for as many nodes as we
-## are going to deploy.
-
-write_files:
-  - path: /opt/bin/curl-retry.sh
-    permissions: '0755'
-    owner: root
-    content: |
-      #!/bin/sh -x
-      until curl $@
-      do sleep 1
-      done
-
-coreos:
-  update:
-    group: stable
-    reboot-strategy: off
-  units:
-    - name: systemd-networkd-wait-online.service
-      drop-ins:
-        - name: 50-check-github-is-reachable.conf
-          content: |
-            [Service]
-            ExecStart=/bin/sh -x -c \
-              'until curl --silent --fail https://status.github.com/api/status.json | grep -q \"good\"; do sleep 2; done'
-
-    - name: docker.service
-      drop-ins:
-        - name: 50-weave-kubernetes.conf
-          content: |
-            [Service]
-            Environment=DOCKER_OPTS='--bridge="weave" -r="false"'
-
-    - name: weave-network.target
-      enable: true
-      content: |
-        [Unit]
-        Description=Weave Network Setup Complete
-        Documentation=man:systemd.special(7)
-        RefuseManualStart=no
-        After=network-online.target
-        [Install]
-        WantedBy=multi-user.target
-        WantedBy=kubernetes-master.target
-        WantedBy=kubernetes-node.target
-
-    - name: kubernetes-master.target
-      enable: true
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes Cluster Master
-        Documentation=http://kubernetes.io/
-        RefuseManualStart=no
-        After=weave-network.target
-        Requires=weave-network.target
-        ConditionHost=kube-00
-        Wants=kube-apiserver.service
-        Wants=kube-scheduler.service
-        Wants=kube-controller-manager.service
-        Wants=kube-proxy.service
-        [Install]
-        WantedBy=multi-user.target
-
-    - name: kubernetes-node.target
-      enable: true
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes Cluster Node
-        Documentation=http://kubernetes.io/
-        RefuseManualStart=no
-        After=weave-network.target
-        Requires=weave-network.target
-        ConditionHost=!kube-00
-        Wants=kube-proxy.service
-        Wants=kubelet.service
-        [Install]
-        WantedBy=multi-user.target
-
-    - name: 10-weave.network
-      runtime: false
-      content: |
-        [Match]
-        Type=bridge
-        Name=weave*
-        [Network]
-
-    - name: install-weave.service
-      enable: true
-      content: |
-        [Unit]
-        After=network-online.target
-        Before=weave.service
-        Before=weave-helper.service
-        Before=docker.service
-        Description=Install Weave
-        Documentation=http://docs.weave.works/
-        Requires=network-online.target
-        [Service]
-        Type=oneshot
-        RemainAfterExit=yes
-        ExecStartPre=/bin/mkdir -p /opt/bin/
-        ExecStartPre=/opt/bin/curl-retry.sh \
-          --silent \
-          --location \
-          https://github.com/weaveworks/weave/releases/download/latest_release/weave \
-          --output /opt/bin/weave
-        ExecStartPre=/opt/bin/curl-retry.sh \
-          --silent \
-          --location \
-          https://raw.github.com/errordeveloper/weave-demos/master/poseidon/weave-helper \
-          --output /opt/bin/weave-helper
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/weave
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/weave-helper
-        ExecStart=/bin/echo Weave Installed
-        [Install]
-        WantedBy=weave-network.target
-        WantedBy=weave.service
-
-    - name: weave-helper.service
-      enable: true
-      content: |
-        [Unit]
-        After=install-weave.service
-        After=docker.service
-        Description=Weave Network Router
-        Documentation=http://docs.weave.works/
-        Requires=docker.service
-        Requires=install-weave.service
-        [Service]
-        ExecStart=/opt/bin/weave-helper
-        Restart=always
-        [Install]
-        WantedBy=weave-network.target
-
-    - name: weave.service
-      enable: true
-      content: |
-        [Unit]
-        After=install-weave.service
-        After=docker.service
-        Description=Weave Network Router
-        Documentation=http://docs.weave.works/
-        Requires=docker.service
-        Requires=install-weave.service
-        [Service]
-        TimeoutStartSec=0
-        EnvironmentFile=/etc/weave.%H.env
-        ExecStartPre=/opt/bin/weave setup
-        ExecStartPre=/opt/bin/weave launch $WEAVE_PEERS
-        ExecStart=/usr/bin/docker attach weave
-        Restart=on-failure
-        Restart=always
-        ExecStop=/opt/bin/weave stop
-        [Install]
-        WantedBy=weave-network.target
-
-    - name: weave-create-bridge.service
-      enable: true
-      content: |
-        [Unit]
-        After=network.target
-        After=install-weave.service
-        Before=weave.service
-        Before=docker.service
-        Requires=network.target
-        Requires=install-weave.service
-        [Service]
-        Type=oneshot
-        EnvironmentFile=/etc/weave.%H.env
-        ExecStart=/opt/bin/weave --local create-bridge
-        ExecStart=/usr/bin/ip addr add dev weave $BRIDGE_ADDRESS_CIDR
-        ExecStart=/usr/bin/ip route add $BREAKOUT_ROUTE dev weave scope link
-        ExecStart=/usr/bin/ip route add 224.0.0.0/4 dev weave
-        [Install]
-        WantedBy=multi-user.target
-        WantedBy=weave-network.target
-
-    - name: install-kubernetes.service
-      enable: true
-      content: |
-        [Unit]
-        After=network-online.target
-        Before=kube-apiserver.service
-        Before=kube-controller-manager.service
-        Before=kubelet.service
-        Before=kube-proxy.service
-        Description=Download Kubernetes Binaries
-        Documentation=http://kubernetes.io/
-        Requires=network-online.target
-        [Service]
-        Environment=KUBE_RELEASE_TARBALL=https://github.com/GoogleCloudPlatform/kubernetes/releases/download/v1.0.1/kubernetes.tar.gz
-        ExecStartPre=/bin/mkdir -p /opt/
-        ExecStart=/opt/bin/curl-retry.sh --silent --location $KUBE_RELEASE_TARBALL --output /tmp/kubernetes.tgz
-        ExecStart=/bin/tar xzvf /tmp/kubernetes.tgz -C /tmp/
-        ExecStart=/bin/tar xzvf /tmp/kubernetes/server/kubernetes-server-linux-amd64.tar.gz -C /opt
-        ExecStartPost=/bin/chmod o+rx -R /opt/kubernetes
-        ExecStartPost=/bin/ln -s /opt/kubernetes/server/bin/kubectl /opt/bin/
-        ExecStartPost=/bin/mv /tmp/kubernetes/examples/guestbook /home/core/guestbook-example
-        ExecStartPost=/bin/chown core. -R /home/core/guestbook-example
-        ExecStartPost=/bin/rm -rf /tmp/kubernetes
-        ExecStartPost=/bin/sed 's/# type: LoadBalancer/type: NodePort/' -i /home/core/guestbook-example/frontend-service.yaml
-        RemainAfterExit=yes
-        Type=oneshot
-        [Install]
-        WantedBy=kubernetes-master.target
-        WantedBy=kubernetes-node.target
-
-    - name: kube-apiserver.service
-      enable: true
-      content: |
-        [Unit]
-        After=install-kubernetes.service
-        Before=kube-controller-manager.service
-        Before=kube-scheduler.service
-        ConditionFileIsExecutable=/opt/kubernetes/server/bin/kube-apiserver
-        Description=Kubernetes API Server
-        Documentation=http://kubernetes.io/
-        Wants=install-kubernetes.service
-        ConditionHost=kube-00
-        [Service]
-        ExecStart=/opt/kubernetes/server/bin/kube-apiserver \
-            --address=0.0.0.0 \
-            --port=8080 \
-            $ETCD_SERVERS \
-            --service-cluster-ip-range=10.1.0.0/16 \
-            --logtostderr=true --v=3
-        Restart=always
-        RestartSec=10
-        [Install]
-        WantedBy=kubernetes-master.target
-
-    - name: kube-scheduler.service
-      enable: true
-      content: |
-        [Unit]
-        After=kube-apiserver.service
-        After=install-kubernetes.service
-        ConditionFileIsExecutable=/opt/kubernetes/server/bin/kube-scheduler
-        Description=Kubernetes Scheduler
-        Documentation=http://kubernetes.io/
-        Wants=kube-apiserver.service
-        ConditionHost=kube-00
-        [Service]
-        ExecStart=/opt/kubernetes/server/bin/kube-scheduler \
-            --logtostderr=true \
-            --master=127.0.0.1:8080
-        Restart=always
-        RestartSec=10
-        [Install]
-        WantedBy=kubernetes-master.target
-
-    - name: kube-controller-manager.service
-      enable: true
-      content: |
-        [Unit]
-        After=install-kubernetes.service
-        After=kube-apiserver.service
-        ConditionFileIsExecutable=/opt/kubernetes/server/bin/kube-controller-manager
-        Description=Kubernetes Controller Manager
-        Documentation=http://kubernetes.io/
-        Wants=kube-apiserver.service
-        Wants=install-kubernetes.service
-        ConditionHost=kube-00
-        [Service]
-        ExecStart=/opt/kubernetes/server/bin/kube-controller-manager \
-            --master=127.0.0.1:8080 \
-            --logtostderr=true
-        Restart=always
-        RestartSec=10
-        [Install]
-        WantedBy=kubernetes-master.target
-
-    - name: kubelet.service
-      enable: true
-      content: |
-        [Unit]
-        After=install-kubernetes.service
-        ConditionFileIsExecutable=/opt/kubernetes/server/bin/kubelet
-        Description=Kubernetes Kubelet
-        Documentation=http://kubernetes.io/
-        Wants=install-kubernetes.service
-        ConditionHost=!kube-00
-        [Service]
-        ExecStartPre=/bin/mkdir -p /etc/kubernetes/manifests/
-        ExecStart=/opt/kubernetes/server/bin/kubelet \
-            --address=0.0.0.0 \
-            --port=10250 \
-            --hostname-override=%H \
-            --api-servers=http://kube-00:8080 \
-            --logtostderr=true \
-            --cluster-dns=10.1.0.3 \
-            --cluster-domain=kube.local \
-            --config=/etc/kubernetes/manifests/
-        Restart=always
-        RestartSec=10
-        [Install]
-        WantedBy=kubernetes-node.target
-
-    - name: kube-proxy.service
-      enable: true
-      content: |
-        [Unit]
-        After=install-kubernetes.service
-        ConditionFileIsExecutable=/opt/kubernetes/server/bin/kube-proxy
-        Description=Kubernetes Proxy
-        Documentation=http://kubernetes.io/
-        Wants=install-kubernetes.service
-        [Service]
-        ExecStart=/opt/kubernetes/server/bin/kube-proxy \
-             --master=http://kube-00:8080 \
-             --logtostderr=true
-        Restart=always
-        RestartSec=10
-        [Install]
-        WantedBy=kubernetes-master.target
-        WantedBy=kubernetes-node.target
-
-    - name: kube-create-addons.service
-      enable: true
-      content: |
-        [Unit]
-        After=install-kubernetes.service
-        ConditionFileIsExecutable=/opt/kubernetes/server/bin/kubectl
-        ConditionPathIsDirectory=/etc/kubernetes/addons/
-        ConditionHost=kube-00
-        Description=Kubernetes Addons
-        Documentation=http://kubernetes.io/
-        Wants=install-kubernetes.service
-        Wants=kube-apiserver.service
-        [Service]
-        Type=oneshot
-        RemainAfterExit=no
-        ExecStart=/opt/kubernetes/server/bin/kubectl create -f /etc/kubernetes/addons/
-        SuccessExitStatus=1
-        [Install]
-        WantedBy=kubernetes-master.target
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/create-kubernetes-cluster.js b/v1.2/docs/getting-started-guides/coreos/azure/create-kubernetes-cluster.js
deleted file mode 100755
index 70248c596c..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/create-kubernetes-cluster.js
+++ /dev/null
@@ -1,15 +0,0 @@
-#!/usr/bin/env node
-
-var azure = require('./lib/azure_wrapper.js');
-var kube = require('./lib/deployment_logic/kubernetes.js');
-
-azure.create_config('kube', { 'etcd': 3, 'kube': 3 });
-
-azure.run_task_queue([
-  azure.queue_default_network(),
-  azure.queue_storage_if_needed(),
-  azure.queue_machines('etcd', 'stable',
-    kube.create_etcd_cloud_config),
-  azure.queue_machines('kube', 'stable',
-    kube.create_node_cloud_config),
-]);
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/destroy-cluster.js b/v1.2/docs/getting-started-guides/coreos/azure/destroy-cluster.js
deleted file mode 100755
index ce441e538a..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/destroy-cluster.js
+++ /dev/null
@@ -1,7 +0,0 @@
-#!/usr/bin/env node
-
-var azure = require('./lib/azure_wrapper.js');
-
-azure.destroy_cluster(process.argv[2]);
-
-console.log('The cluster had been destroyed, you can delete the state file now.');
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/expose_guestbook_app_port.sh b/v1.2/docs/getting-started-guides/coreos/azure/expose_guestbook_app_port.sh
deleted file mode 100755
index 65dfaf5d3a..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/expose_guestbook_app_port.sh
+++ /dev/null
@@ -1,29 +0,0 @@
-#!/bin/bash
-
-# Copyright 2014 The Kubernetes Authors All rights reserved.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-set -e
-
-[ ! -z $1 ] || (echo Usage: $0 ssh_conf; exit 1)
-
-fe_port=$(ssh -F $1 kube-00 \
-  "/opt/bin/kubectl get -o template --template='{{(index .spec.ports 0).nodePort}}' services frontend -L name=frontend" \
-)
-
-echo "Guestbook app is on port $fe_port, will map it to port 80 on kube-00"
-
-./node_modules/.bin/azure vm endpoint create kube-00 80 $fe_port
-
-./node_modules/.bin/azure vm endpoint show kube-00 tcp-80-${fe_port}
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/index.md b/v1.2/docs/getting-started-guides/coreos/azure/index.md
deleted file mode 100644
index 1750a9f5d2..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/index.md
+++ /dev/null
@@ -1,227 +0,0 @@
----
----
-
-In this guide I will demonstrate how to deploy a Kubernetes cluster to Azure cloud. You will be using CoreOS with  [Weave](http://weave.works), 
-which implements simple and secure networking, in a transparent, yet robust way. The purpose of this guide is to provide an out-of-the-box
-implementation that can ultimately be taken into production with little change. It will demonstrate how to provision a dedicated Kubernetes
-master and etcd nodes, and show how to scale the cluster with ease.
-
-* TOC
-{:toc}
-
-### Prerequisites
-
-1. You need an Azure account.
-
-## Let's go!
-
-To get started, you need to checkout the code:
-
-```shell
-git clone https://github.com/kubernetes/kubernetes
-cd kubernetes/docs/getting-started-guides/coreos/azure/
-```
-
-You will need to have [Node.js installed](http://nodejs.org/download/) on you machine. If you have previously used Azure CLI, you should have it already.
-
-First, you need to install some of the dependencies with
-
-```shell
-npm install
-```
-
-Now, all you need to do is:
-
-```shell
-./azure-login.js -u <your_username>
-./create-kubernetes-cluster.js
-```
-
-This script will provision a cluster suitable for production use, where there is a ring of 3 dedicated etcd nodes: 1 kubernetes master and 2 kubernetes nodes. 
-The `kube-00` VM will be the master, your work loads are only to be deployed on the nodes, `kube-01` and `kube-02`. Initially, all VMs are single-core, to 
-ensure a user of the free tier can reproduce it without paying extra. I will show how to add more bigger VMs later.
-
-![VMs in Azure](/images/docs/initial_cluster.png)
-
-Once the creation of Azure VMs has finished, you should see the following:
-
-```shell
-...
-azure_wrapper/info: Saved SSH config, you can use it like so: `ssh -F  ./output/kube_1c1496016083b4_ssh_conf <hostname>`
-azure_wrapper/info: The hosts in this deployment are:
- [ 'etcd-00', 'etcd-01', 'etcd-02', 'kube-00', 'kube-01', 'kube-02' ]
-azure_wrapper/info: Saved state into `./output/kube_1c1496016083b4_deployment.yml`
-```
-
-Let's login to the master node like so:
-
-```shell
-ssh -F  ./output/kube_1c1496016083b4_ssh_conf kube-00
-```
-
-> Note: config file name will be different, make sure to use the one you see.
-
-Check there are 2 nodes in the cluster:
-
-```shell
-core@kube-00 ~ $ kubectl get nodes
-NAME      LABELS                           STATUS
-kube-01   kubernetes.io/hostname=kube-01   Ready
-kube-02   kubernetes.io/hostname=kube-02   Ready
-```
-
-## Deploying the workload
-
-Let's follow the Guestbook example now:
-
-```shell
-kubectl create -f ~/guestbook-example
-```
-
-You need to wait for the pods to get deployed, run the following and wait for `STATUS` to change from `Pending` to `Running`.
-
-```shell
-kubectl get pods --watch
-```
-
-> Note: the most time it will spend downloading Docker container images on each of the nodes.
-
-Eventually you should see:
-
-```shell
-NAME                READY     STATUS    RESTARTS   AGE
-frontend-0a9xi      1/1       Running   0          4m
-frontend-4wahe      1/1       Running   0          4m
-frontend-6l36j      1/1       Running   0          4m
-redis-master-talmr  1/1       Running   0          4m
-redis-slave-12zfd   1/1       Running   0          4m
-redis-slave-3nbce   1/1       Running   0          4m
-```
-
-## Scaling
-
-Two single-core nodes are certainly not enough for a production system of today. 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/kubernetes/docs/getting-started-guides/coreos/azure/`).
-
-First, lets set the size of new VMs:
-
-```shell
-export AZ_VM_SIZE=Large
-```
-
-Now, run scale script with state file of the previous deployment and number of nodes to add:
-
-```shell
-core@kube-00 ~ $ ./scale-kubernetes-cluster.js ./output/kube_1c1496016083b4_deployment.yml 2
-...
-azure_wrapper/info: Saved SSH config, you can use it like so: `ssh -F  ./output/kube_8f984af944f572_ssh_conf <hostname>`
-azure_wrapper/info: The hosts in this deployment are:
- [ 'etcd-00',
-  'etcd-01',
-  'etcd-02',
-  'kube-00',
-  'kube-01',
-  'kube-02',
-  'kube-03',
-  'kube-04' ]
-azure_wrapper/info: Saved state into `./output/kube_8f984af944f572_deployment.yml`
-```
-
-> Note: this step has created new files in `./output`.
-
-Back on `kube-00`:
-
-```shell
-core@kube-00 ~ $ kubectl get nodes
-NAME      LABELS                           STATUS
-kube-01   kubernetes.io/hostname=kube-01   Ready
-kube-02   kubernetes.io/hostname=kube-02   Ready
-kube-03   kubernetes.io/hostname=kube-03   Ready
-kube-04   kubernetes.io/hostname=kube-04   Ready
-```
-
-You can see that two more nodes joined happily. Let's scale the number of Guestbook instances now.
-
-First, double-check how many replication controllers there are:
-
-```shell
-core@kube-00 ~ $ kubectl get rc
-ONTROLLER     CONTAINER(S)   IMAGE(S)                                    SELECTOR            REPLICAS
-frontend       php-redis      kubernetes/example-guestbook-php-redis:v2   name=frontend       3
-redis-master   master         redis                                       name=redis-master   1
-redis-slave    worker         kubernetes/redis-slave:v2                   name=redis-slave    2
-```
-
-As there are 4 nodes, let's scale proportionally:
-
-```shell
-core@kube-00 ~ $ kubectl scale --replicas=4 rc redis-slave
->>>>>>> coreos/azure: Updates for 1.0
-scaled
-core@kube-00 ~ $ kubectl scale --replicas=4 rc frontend
-scaled
-```
-
-Check what you have now:
-
-```shell
-core@kube-00 ~ $ kubectl get rc
-CONTROLLER     CONTAINER(S)   IMAGE(S)                                    SELECTOR            REPLICAS
-frontend       php-redis      kubernetes/example-guestbook-php-redis:v2   name=frontend       4
-redis-master   master         redis                                       name=redis-master   1
-redis-slave    worker         kubernetes/redis-slave:v2                   name=redis-slave    4
-```
-
-You now will have more instances of front-end Guestbook apps and Redis slaves; and, if you look up all pods labeled `name=frontend`, you should see one running on each node.
-
-```shell
-core@kube-00 ~/guestbook-example $ kubectl get pods -l name=frontend
-NAME             READY     STATUS    RESTARTS   AGE
-frontend-0a9xi   1/1       Running   0          22m
-frontend-4wahe   1/1       Running   0          22m
-frontend-6l36j   1/1       Running   0          22m
-frontend-z9oxo   1/1       Running   0          41s
-```
-
-## Exposing the app to the outside world
-
-There is no native Azure load-balancer support in Kubernetes 1.0, however here is how you can expose the Guestbook app to the Internet.
-
-```shell
-./expose_guestbook_app_port.sh ./output/kube_1c1496016083b4_ssh_conf
-Guestbook app is on port 31605, will map it to port 80 on kube-00
-info:    Executing command vm endpoint create
-+ Getting virtual machines
-+ Reading network configuration
-+ Updating network configuration
-info:    vm endpoint create command OK
-info:    Executing command vm endpoint show
-+ Getting virtual machines
-data:      Name                          : tcp-80-31605
-data:      Local port                    : 31605
-data:      Protcol                       : tcp
-data:      Virtual IP Address            : 137.117.156.164
-data:      Direct server return          : Disabled
-info:    vm endpoint show command OK
-```
-
-You then should be able to access it from anywhere via the Azure virtual IP for `kube-00` displayed above, i.e. `http://137.117.156.164/` in my case.
-
-## Next steps
-
-You now have a full-blow cluster running in Azure, congrats!
-
-You should probably try deploy other [example apps](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/) or write your own ;)
-
-## Tear down...
-
-If you don't wish care about the Azure bill, you can tear down the cluster. It's easy to redeploy it, as you can see.
-
-```shell
-./destroy-cluster.js ./output/kube_8f984af944f572_deployment.yml
-```
-
-> 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 :)
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/lib/azure_wrapper.js b/v1.2/docs/getting-started-guides/coreos/azure/lib/azure_wrapper.js
deleted file mode 100644
index d389efbea2..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/lib/azure_wrapper.js
+++ /dev/null
@@ -1,271 +0,0 @@
-var _ = require('underscore');
-
-var fs = require('fs');
-var cp = require('child_process');
-
-var yaml = require('js-yaml');
-
-var openssl = require('openssl-wrapper');
-
-var clr = require('colors');
-var inspect = require('util').inspect;
-
-var util = require('./util.js');
-
-var coreos_image_ids = {
-  'stable': '2b171e93f07c4903bcad35bda10acf22__CoreOS-Stable-717.3.0',
-  'beta': '2b171e93f07c4903bcad35bda10acf22__CoreOS-Beta-723.3.0', // untested
-  'alpha': '2b171e93f07c4903bcad35bda10acf22__CoreOS-Alpha-745.1.0' // untested
-};
-
-var conf = {};
-
-var hosts = {
-  collection: [],
-  ssh_port_counter: 2200,
-};
-
-var task_queue = [];
-
-exports.run_task_queue = function (dummy) {
-  var tasks = {
-    todo: task_queue,
-    done: [],
-  };
-
-  var pop_task = function() {
-    console.log(clr.yellow('azure_wrapper/task:'), clr.grey(inspect(tasks)));
-    var ret = {};
-    ret.current = tasks.todo.shift();
-    ret.remaining = tasks.todo.length;
-    return ret;
-  };
-
-  (function iter (task) {
-    if (task.current === undefined) {
-      if (conf.destroying === undefined) {
-        create_ssh_conf();
-        save_state();
-      }
-      return;
-    } else {
-      if (task.current.length !== 0) {
-        console.log(clr.yellow('azure_wrapper/exec:'), clr.blue(inspect(task.current)));
-        cp.fork('node_modules/azure-cli/bin/azure', task.current)
-          .on('exit', function (code, signal) {
-            tasks.done.push({
-              code: code,
-              signal: signal,
-              what: task.current.join(' '),
-              remaining: task.remaining,
-            });
-            if (code !== 0 && conf.destroying === undefined) {
-              console.log(clr.red('azure_wrapper/fail: Exiting due to an error.'));
-              save_state();
-              console.log(clr.cyan('azure_wrapper/info: You probably want to destroy and re-run.'));
-              process.abort();
-            } else {
-              iter(pop_task());
-            }
-        });
-      } else {
-        iter(pop_task());
-      }
-    }
-  })(pop_task());
-};
-
-var save_state = function () {
-  var file_name = util.join_output_file_path(conf.name, 'deployment.yml');
-  try {
-    conf.hosts = hosts.collection;
-    fs.writeFileSync(file_name, yaml.safeDump(conf));
-    console.log(clr.yellow('azure_wrapper/info: Saved state into `%s`'), file_name);
-  } catch (e) {
-    console.log(clr.red(e));
-  }
-};
-
-var load_state = function (file_name) {
-  try {
-    conf = yaml.safeLoad(fs.readFileSync(file_name, 'utf8'));
-    console.log(clr.yellow('azure_wrapper/info: Loaded state from `%s`'), file_name);
-    return conf;
-  } catch (e) {
-    console.log(clr.red(e));
-  }
-};
-
-var create_ssh_key = function (prefix) {
-  var opts = {
-    x509: true,
-    nodes: true,
-    newkey: 'rsa:2048',
-    subj: '/O=Weaveworks, Inc./L=London/C=GB/CN=weave.works',
-    keyout: util.join_output_file_path(prefix, 'ssh.key'),
-    out: util.join_output_file_path(prefix, 'ssh.pem'),
-  };
-  openssl.exec('req', opts, function (err, buffer) {
-    if (err) console.log(clr.red(err));
-    fs.chmod(opts.keyout, '0600', function (err) {
-      if (err) console.log(clr.red(err));
-    });
-  });
-  return {
-    key: opts.keyout,
-    pem: opts.out,
-  }
-}
-
-var create_ssh_conf = function () {
-  var file_name = util.join_output_file_path(conf.name, 'ssh_conf');
-  var ssh_conf_head = [
-    "Host *",
-    "\tHostname " + conf.resources['service'] + ".cloudapp.net",
-    "\tUser core",
-    "\tCompression yes",
-    "\tLogLevel FATAL",
-    "\tStrictHostKeyChecking no",
-    "\tUserKnownHostsFile /dev/null",
-    "\tIdentitiesOnly yes",
-    "\tIdentityFile " + conf.resources['ssh_key']['key'],
-    "\n",
-  ];
-
-  fs.writeFileSync(file_name, ssh_conf_head.concat(_.map(hosts.collection, function (host) {
-    return _.template("Host <%= name %>\n\tPort <%= port %>\n")(host);
-  })).join('\n'));
-  console.log(clr.yellow('azure_wrapper/info:'), clr.green('Saved SSH config, you can use it like so: `ssh -F ', file_name, '<hostname>`'));
-  console.log(clr.yellow('azure_wrapper/info:'), clr.green('The hosts in this deployment are:\n'), _.map(hosts.collection, function (host) { return host.name; }));
-};
-
-var get_location = function () {
-  if (process.env['AZ_AFFINITY']) {
-    return '--affinity-group=' + process.env['AZ_AFFINITY'];
-  } else if (process.env['AZ_LOCATION']) {
-    return '--location=' + process.env['AZ_LOCATION'];
-  } else {
-    return '--location=West Europe';
-  }
-}
-var get_vm_size = function () {
-  if (process.env['AZ_VM_SIZE']) {
-    return '--vm-size=' + process.env['AZ_VM_SIZE'];
-  } else {
-    return '--vm-size=Small';
-  }
-}
-
-exports.queue_default_network = function () {
-  task_queue.push([
-    'network', 'vnet', 'create',
-    get_location(),
-    '--address-space=172.16.0.0',
-    conf.resources['vnet'],
-  ]);
-}
-
-exports.queue_storage_if_needed = function() {
-  if (!process.env['AZURE_STORAGE_ACCOUNT']) {
-    conf.resources['storage_account'] = util.rand_suffix;
-    task_queue.push([
-      'storage', 'account', 'create',
-      '--type=LRS',
-      get_location(),
-      conf.resources['storage_account'],
-    ]);
-    process.env['AZURE_STORAGE_ACCOUNT'] = conf.resources['storage_account'];
-  } else {
-    // Preserve it for resizing, so we don't create a new one by accedent,
-    // when the environment variable is unset
-    conf.resources['storage_account'] = process.env['AZURE_STORAGE_ACCOUNT'];
-  }
-};
-
-exports.queue_machines = function (name_prefix, coreos_update_channel, cloud_config_creator) {
-  var x = conf.nodes[name_prefix];
-  var vm_create_base_args = [
-    'vm', 'create',
-    get_location(),
-    get_vm_size(),
-    '--connect=' + conf.resources['service'],
-    '--virtual-network-name=' + conf.resources['vnet'],
-    '--no-ssh-password',
-    '--ssh-cert=' + conf.resources['ssh_key']['pem'],
-  ];
-
-  var cloud_config = cloud_config_creator(x, conf);
-
-  var next_host = function (n) {
-    hosts.ssh_port_counter += 1;
-    var host = { name: util.hostname(n, name_prefix), port: hosts.ssh_port_counter };
-    if (cloud_config instanceof Array) {
-      host.cloud_config_file = cloud_config[n];
-    } else {
-      host.cloud_config_file = cloud_config;
-    }
-    hosts.collection.push(host);
-    return _.map([
-        "--vm-name=<%= name %>",
-        "--ssh=<%= port %>",
-        "--custom-data=<%= cloud_config_file %>",
-    ], function (arg) { return _.template(arg)(host); });
-  };
-
-  task_queue = task_queue.concat(_(x).times(function (n) {
-    if (conf.resizing && n < conf.old_size) {
-      return [];
-    } else {
-      return vm_create_base_args.concat(next_host(n), [
-        coreos_image_ids[coreos_update_channel], 'core',
-      ]);
-    }
-  }));
-};
-
-exports.create_config = function (name, nodes) {
-  conf = {
-    name: name,
-    nodes: nodes,
-    weave_salt: util.rand_string(),
-    resources: {
-      vnet: [name, 'internal-vnet', util.rand_suffix].join('-'),
-      service: [name, util.rand_suffix].join('-'),
-      ssh_key: create_ssh_key(name),
-    }
-  };
-
-};
-
-exports.destroy_cluster = function (state_file) {
-  load_state(state_file);
-  if (conf.hosts === undefined) {
-    console.log(clr.red('azure_wrapper/fail: Nothing to delete.'));
-    process.abort();
-  }
-
-  conf.destroying = true;
-  task_queue = _.map(conf.hosts, function (host) {
-    return ['vm', 'delete', '--quiet', '--blob-delete', host.name];
-  });
-
-  task_queue.push(['network', 'vnet', 'delete', '--quiet', conf.resources['vnet']]);
-  task_queue.push(['storage', 'account', 'delete', '--quiet', conf.resources['storage_account']]);
-
-  exports.run_task_queue();
-};
-
-exports.load_state_for_resizing = function (state_file, node_type, new_nodes) {
-  load_state(state_file);
-  if (conf.hosts === undefined) {
-    console.log(clr.red('azure_wrapper/fail: Nothing to look at.'));
-    process.abort();
-  }
-  conf.resizing = true;
-  conf.old_size = conf.nodes[node_type];
-  conf.old_state_file = state_file;
-  conf.nodes[node_type] += new_nodes;
-  hosts.collection = conf.hosts;
-  hosts.ssh_port_counter += conf.hosts.length;
-  process.env['AZURE_STORAGE_ACCOUNT'] = conf.resources['storage_account'];
-}
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/lib/cloud_config.js b/v1.2/docs/getting-started-guides/coreos/azure/lib/cloud_config.js
deleted file mode 100644
index d08b3f06ae..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/lib/cloud_config.js
+++ /dev/null
@@ -1,58 +0,0 @@
-var _ = require('underscore');
-var fs = require('fs');
-var yaml = require('js-yaml');
-var colors = require('colors/safe');
-
-var write_cloud_config_from_object = function (data, output_file) {
-  try {
-    fs.writeFileSync(output_file, [
-      '#cloud-config',
-      yaml.safeDump(data),
-    ].join("\n"));
-    return output_file;
-  } catch (e) {
-    console.log(colors.red(e));
-  }
-};
-
-exports.generate_environment_file_entry_from_object = function (hostname, environ) {
-  var data = {
-    hostname: hostname,
-    environ_array: _.map(environ, function (value, key) {
-      return [key.toUpperCase(), JSON.stringify(value.toString())].join('=');
-    }),
-  };
-
-  return {
-    permissions: '0600',
-    owner: 'root',
-    content: _.template("<%= environ_array.join('\\n') %>\n")(data),
-    path: _.template("/etc/weave.<%= hostname %>.env")(data),
-  };
-};
-
-exports.process_template = function (input_file, output_file, processor) {
-  var data = {};
-  try {
-    data = yaml.safeLoad(fs.readFileSync(input_file, 'utf8'));
-  } catch (e) {
-    console.log(colors.red(e));
-  }
-  return write_cloud_config_from_object(processor(_.clone(data)), output_file);
-};
-
-exports.write_files_from = function (local_dir, remote_dir) {
-  try {
-    return _.map(fs.readdirSync(local_dir), function (fn) {
-      return {
-        path: [remote_dir, fn].join('/'),
-        owner: 'root',
-        permissions: '0640',
-        encoding: 'base64',
-        content: fs.readFileSync([local_dir, fn].join('/')).toString('base64'),
-      };
-    });
-  } catch (e) {
-    console.log(colors.red(e));
-  }
-};
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/lib/deployment_logic/kubernetes.js b/v1.2/docs/getting-started-guides/coreos/azure/lib/deployment_logic/kubernetes.js
deleted file mode 100644
index 2002b43a53..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/lib/deployment_logic/kubernetes.js
+++ /dev/null
@@ -1,77 +0,0 @@
-var _ = require('underscore');
-_.mixin(require('underscore.string').exports());
-
-var util = require('../util.js');
-var cloud_config = require('../cloud_config.js');
-
-
-etcd_initial_cluster_conf_self = function (conf) {
-  var port = '2380';
-
-  var data = {
-    nodes: _(conf.nodes.etcd).times(function (n) {
-      var host = util.hostname(n, 'etcd');
-      return [host, [host, port].join(':')].join('=http://');
-    }),
-  };
-
-  return {
-    'name': 'etcd2.service',
-    'drop-ins': [{
-      'name': '50-etcd-initial-cluster.conf',
-      'content': _.template("[Service]\nEnvironment=ETCD_INITIAL_CLUSTER=<%= nodes.join(',') %>\n")(data),
-    }],
-  };
-};
-
-etcd_initial_cluster_conf_kube = function (conf) {
-  var port = '4001';
-
-  var data = {
-    nodes: _(conf.nodes.etcd).times(function (n) {
-      var host = util.hostname(n, 'etcd');
-      return 'http://' + [host, port].join(':');
-    }),
-  };
-
-  return {
-    'name': 'kube-apiserver.service',
-    'drop-ins': [{
-      'name': '50-etcd-initial-cluster.conf',
-      'content': _.template("[Service]\nEnvironment=ETCD_SERVERS=--etcd-servers=<%= nodes.join(',') %>\n")(data),
-    }],
-  };
-};
-
-exports.create_etcd_cloud_config = function (node_count, conf) {
-  var input_file = './cloud_config_templates/kubernetes-cluster-etcd-node-template.yml';
-  var output_file = util.join_output_file_path('kubernetes-cluster-etcd-nodes', 'generated.yml');
-
-  return cloud_config.process_template(input_file, output_file, function(data) {
-    data.coreos.units.push(etcd_initial_cluster_conf_self(conf));
-    return data;
-  });
-};
-
-exports.create_node_cloud_config = function (node_count, conf) {
-  var elected_node = 0;
-
-  var input_file = './cloud_config_templates/kubernetes-cluster-main-nodes-template.yml';
-  var output_file = util.join_output_file_path('kubernetes-cluster-main-nodes', 'generated.yml');
-
-  var make_node_config = function (n) {
-    return cloud_config.generate_environment_file_entry_from_object(util.hostname(n, 'kube'), {
-      weave_password: conf.weave_salt,
-      weave_peers: n === elected_node ? "" : util.hostname(elected_node, 'kube'),
-      breakout_route: util.ipv4([10, 2, 0, 0], 16),
-      bridge_address_cidr: util.ipv4([10, 2, n, 1], 24),
-    });
-  };
-
-  var write_files_extra = cloud_config.write_files_from('addons', '/etc/kubernetes/addons');
-  return cloud_config.process_template(input_file, output_file, function(data) {
-    data.write_files = data.write_files.concat(_(node_count).times(make_node_config), write_files_extra);
-    data.coreos.units.push(etcd_initial_cluster_conf_kube(conf));
-    return data;
-  });
-};
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/lib/util.js b/v1.2/docs/getting-started-guides/coreos/azure/lib/util.js
deleted file mode 100644
index 2c88b8cff3..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/lib/util.js
+++ /dev/null
@@ -1,33 +0,0 @@
-var _ = require('underscore');
-_.mixin(require('underscore.string').exports());
-
-exports.ipv4 = function (ocets, prefix) {
-  return {
-    ocets: ocets,
-    prefix: prefix,
-    toString: function () {
-      return [ocets.join('.'), prefix].join('/');
-    }
-  }
-};
-
-exports.hostname = function hostname (n, prefix) {
-  return _.template("<%= pre %>-<%= seq %>")({
-    pre: prefix || 'core',
-    seq: _.pad(n, 2, '0'),
-  });
-};
-
-exports.rand_string = function () {
-  var crypto = require('crypto');
-  var shasum = crypto.createHash('sha256');
-  shasum.update(crypto.randomBytes(256));
-  return shasum.digest('hex');
-};
-
-
-exports.rand_suffix = exports.rand_string().substring(50);
-
-exports.join_output_file_path = function(prefix, suffix) {
-  return './output/' + [prefix, exports.rand_suffix, suffix].join('_');
-};
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/package.json b/v1.2/docs/getting-started-guides/coreos/azure/package.json
deleted file mode 100644
index 3269b418e0..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/package.json
+++ /dev/null
@@ -1,19 +0,0 @@
-{
-  "name": "coreos-azure-weave",
-  "version": "1.0.0",
-  "description": "Small utility to bring up a woven CoreOS cluster",
-  "main": "index.js",
-  "scripts": {
-    "test": "echo \"Error: no test specified\" && exit 1"
-  },
-  "author": "Ilya Dmitrichenko <errordeveloper@gmail.com>",
-  "license": "Apache 2.0",
-  "dependencies": {
-    "azure-cli": "^0.9.5",
-    "colors": "^1.0.3",
-    "js-yaml": "^3.2.5",
-    "openssl-wrapper": "^0.2.1",
-    "underscore": "^1.7.0",
-    "underscore.string": "^3.0.2"
-  }
-}
diff --git a/v1.2/docs/getting-started-guides/coreos/azure/scale-kubernetes-cluster.js b/v1.2/docs/getting-started-guides/coreos/azure/scale-kubernetes-cluster.js
deleted file mode 100755
index f606898874..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/azure/scale-kubernetes-cluster.js
+++ /dev/null
@@ -1,10 +0,0 @@
-#!/usr/bin/env node
-
-var azure = require('./lib/azure_wrapper.js');
-var kube = require('./lib/deployment_logic/kubernetes.js');
-
-azure.load_state_for_resizing(process.argv[2], 'kube', parseInt(process.argv[3] || 1));
-
-azure.run_task_queue([
-  azure.queue_machines('kube', 'stable', kube.create_node_cloud_config),
-]);
diff --git a/v1.2/docs/getting-started-guides/coreos/bare_metal_calico.md b/v1.2/docs/getting-started-guides/coreos/bare_metal_calico.md
deleted file mode 100644
index eb8e9b642a..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/bare_metal_calico.md
+++ /dev/null
@@ -1,120 +0,0 @@
----
----
-
-This guide explains how to deploy a bare-metal Kubernetes cluster on CoreOS using [Calico networking](http://www.projectcalico.org).
-
-Specifically, this guide will have you do the following:
-
-- Deploy a Kubernetes master node on CoreOS using cloud-config
-- Deploy two Kubernetes compute nodes with Calico Networking using cloud-config
-
-## Prerequisites
-
-1. At least three bare-metal machines (or VMs) to work with. This guide will configure them as follows
-  - 1 Kubernetes Master
-  - 2 Kubernetes Nodes
-2. Your nodes should have IP connectivity.
-
-## Cloud-config
-
-This guide will use [cloud-config](https://coreos.com/docs/cluster-management/setup/cloudinit-cloud-config/) to configure each of the nodes in our Kubernetes cluster.
-
-For ease of distribution, the cloud-config files required for this demonstration can be found on [GitHub](https://github.com/projectcalico/calico-kubernetes-coreos-demo).
-
-This repo includes two cloud config files:
-
-- `master-config.yaml`: Cloud-config for the Kubernetes master
-- `node-config.yaml`: Cloud-config for each Kubernetes compute host
-
-In the next few steps you will be asked to configure these files and host them on an HTTP server where your cluster can access them.
-
-## Building Kubernetes
-
-To get the Kubernetes source, clone the GitHub repo, and build the binaries.
-
-```shell
-git clone https://github.com/kubernetes/kubernetes.git
-cd kubernetes
-./build/release.sh 
-```
-
-Once the binaries are built, host the entire `<kubernetes>/_output/dockerized/bin/<OS>/<ARCHITECTURE>/` folder on an accessible HTTP server so they can be accessed by the cloud-config.  You'll point your cloud-config files at this HTTP server later.
-
-## Download CoreOS
-
-Let's download the CoreOS bootable ISO.  We'll use this image to boot and install CoreOS on each server.
-
-```shell
-wget http://stable.release.core-os.net/amd64-usr/current/coreos_production_iso_image.iso
-```
-
-You can also download the ISO from the [CoreOS website](https://coreos.com/docs/running-coreos/platforms/iso/).
-
-## Configure the Kubernetes Master
-
-Once you've downloaded the image, use it to boot your Kubernetes Master server.  Once booted, you should be automatically logged in as the `core` user.
-
-Let's get the master-config.yaml and fill in the necessary variables.  Run the following commands on your HTTP server to get the cloud-config files.
-
-```shell
-git clone https://github.com/Metaswitch/calico-kubernetes-demo.git
-cd calico-kubernetes-demo/coreos
-```
-
-You'll need to replace the following variables in the `master-config.yaml` file to match your deployment.
-
-- `<SSH_PUBLIC_KEY>`: The public key you will use for SSH access to this server.
-- `<KUBERNETES_LOC>`: The address used to get the kubernetes binaries over HTTP.
-
-> **Note:** The config will prepend `"http://"` and append `"/(kubernetes | kubectl | ...)"` to your `KUBERNETES_LOC` variable:, format accordingly
-
-Host the modified `master-config.yaml` file and pull it on to your Kubernetes Master server.
-
-The CoreOS bootable ISO comes with a tool called `coreos-install` which will allow us to install CoreOS to disk and configure the install using cloud-config.  The following command will download and install stable CoreOS, using the master-config.yaml file for configuration.
-
-```shell
-sudo coreos-install -d /dev/sda -C stable -c master-config.yaml
-```
-
-Once complete, eject the bootable ISO and restart the server.  When it comes back up, you should have SSH access as the `core` user using the public key provided in the master-config.yaml file.
-
-## Configure the compute hosts
-
->The following steps will set up a Kubernetes node for use as a compute host.  This demo uses two compute hosts, so you should run the following steps on each.
-
-First, boot up your node using the bootable ISO we downloaded earlier.  You should be automatically logged in as the `core` user.
-
-Let's modify the `node-config.yaml` cloud-config file on your HTTP server.  Make a copy for this node, and fill in the necessary variables.
-
-You'll need to replace the following variables in the `node-config.yaml` file to match your deployment.
-
-- `<HOSTNAME>`: Hostname for this node (e.g. kube-node1, kube-node2)
-- `<SSH_PUBLIC_KEY>`: The public key you will use for SSH access to this server.
-- `<KUBERNETES_MASTER>`: The IPv4 address of the Kubernetes master.
-- `<KUBERNETES_LOC>`: The address to use in order to get the kubernetes binaries over HTTP.
-- `<DOCKER_BRIDGE_IP>`: The IP and subnet to use for pods on this node.  By default, this should fall within the 192.168.0.0/16 subnet.
-
-> Note: The DOCKER_BRIDGE_IP is the range used by this Kubernetes node to assign IP addresses to pods on this node.  This subnet must not overlap with the subnets assigned to the other Kubernetes nodes in your cluster.  Calico expects each DOCKER_BRIDGE_IP subnet to fall within 192.168.0.0/16 by default (e.g. 192.168.1.1/24 for node 1), but if you'd like to use pod IPs within a different subnet, simply run `calicoctl pool add <your_subnet>` and select DOCKER_BRIDGE_IP accordingly.
-
-Host the modified `node-config.yaml` file and pull it on to your Kubernetes node.
-
-```shell
-wget http://<http_server_ip>/node-config.yaml
-```
-
-Install and configure CoreOS on the node using the following command.
-
-```shell
-sudo coreos-install -d /dev/sda -C stable -c node-config.yaml
-```
-
-Once complete, restart the server.  When it comes back up, you should have SSH access as the `core` user using the public key provided in the `node-config.yaml` file.  It will take some time for the node to be fully configured.  Once fully configured, you can check that the node is running with the following command on the Kubernetes master.
-
-```shell
-/home/core/kubectl get nodes
-```
-
-## Testing the Cluster
-
-You should now have a functional bare-metal Kubernetes cluster with one master and two compute hosts.
-Try running the [guestbook demo](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/) to test out your new cluster!
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/coreos/cloud-configs/master.yaml b/v1.2/docs/getting-started-guides/coreos/cloud-configs/master.yaml
deleted file mode 100644
index c3b703d1d7..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/cloud-configs/master.yaml
+++ /dev/null
@@ -1,140 +0,0 @@
-#cloud-config
-
----
-write-files:
-  - path: /etc/conf.d/nfs
-    permissions: '0644'
-    content: |
-      OPTS_RPC_MOUNTD=""
-  - path: /opt/bin/wupiao
-    permissions: '0755'
-    content: |
-      #!/bin/bash
-      # [w]ait [u]ntil [p]ort [i]s [a]ctually [o]pen
-      [ -n "$1" ] && \
-        until curl -o /dev/null -sIf http://${1}; do \
-          sleep 1 && echo .;
-        done;
-      exit $?
-
-hostname: master
-coreos:
-  etcd2:
-    name: master
-    listen-client-urls: http://0.0.0.0:2379,http://0.0.0.0:4001
-    advertise-client-urls: http://$private_ipv4:2379,http://$private_ipv4:4001
-    initial-cluster-token: k8s_etcd
-    listen-peer-urls: http://$private_ipv4:2380,http://$private_ipv4:7001
-    initial-advertise-peer-urls: http://$private_ipv4:2380
-    initial-cluster: master=http://$private_ipv4:2380
-    initial-cluster-state: new
-  fleet:
-    metadata: "role=master"
-  units:
-    - name: generate-serviceaccount-key.service
-      command: start
-      content: |
-        [Unit]
-        Description=Generate service-account key file
-
-        [Service]
-        ExecStartPre=-/usr/bin/mkdir -p /opt/bin
-        ExecStart=/bin/openssl genrsa -out /opt/bin/kube-serviceaccount.key 2048 2>/dev/null
-        RemainAfterExit=yes
-        Type=oneshot
-    - name: setup-network-environment.service
-      command: start
-      content: |
-        [Unit]
-        Description=Setup Network Environment
-        Documentation=https://github.com/kelseyhightower/setup-network-environment
-        Requires=network-online.target
-        After=network-online.target
-
-        [Service]
-        ExecStartPre=-/usr/bin/mkdir -p /opt/bin
-        ExecStartPre=/usr/bin/curl -L -o /opt/bin/setup-network-environment -z /opt/bin/setup-network-environment https://github.com/kelseyhightower/setup-network-environment/releases/download/v1.0.0/setup-network-environment
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/setup-network-environment
-        ExecStart=/opt/bin/setup-network-environment
-        RemainAfterExit=yes
-        Type=oneshot
-    - name: fleet.service
-      command: start
-    - name: flanneld.service
-      command: start
-      drop-ins:
-        - name: 50-network-config.conf
-          content: |
-            [Unit]
-            Requires=etcd2.service
-            [Service]
-            ExecStartPre=/usr/bin/etcdctl set /coreos.com/network/config '{"Network":"10.244.0.0/16", "Backend": {"Type": "vxlan"}}'
-    - name: docker.service
-      command: start
-    - name: kube-apiserver.service
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes API Server
-        Documentation=https://github.com/GoogleCloudPlatform/kubernetes
-        Requires=setup-network-environment.service etcd2.service generate-serviceaccount-key.service
-        After=setup-network-environment.service etcd2.service generate-serviceaccount-key.service
-
-        [Service]
-        EnvironmentFile=/etc/network-environment
-        ExecStartPre=-/usr/bin/mkdir -p /opt/bin
-        ExecStartPre=/usr/bin/curl -L -o /opt/bin/kube-apiserver -z /opt/bin/kube-apiserver https://storage.googleapis.com/kubernetes-release/release/v1.0.3/bin/linux/amd64/kube-apiserver
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/kube-apiserver
-        ExecStartPre=/opt/bin/wupiao 127.0.0.1:2379/v2/machines
-        ExecStart=/opt/bin/kube-apiserver \
-        --service-account-key-file=/opt/bin/kube-serviceaccount.key \
-        --service-account-lookup=false \
-        --admission-control=NamespaceLifecycle,NamespaceAutoProvision,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota \
-        --runtime-config=api/v1 \
-        --allow-privileged=true \
-        --insecure-bind-address=0.0.0.0 \
-        --insecure-port=8080 \
-        --kubelet-https=true \
-        --secure-port=6443 \
-        --service-cluster-ip-range=10.100.0.0/16 \
-        --etcd-servers=http://127.0.0.1:2379 \
-        --public-address-override=${DEFAULT_IPV4} \
-        --logtostderr=true
-        Restart=always
-        RestartSec=10
-    - name: kube-controller-manager.service
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes Controller Manager
-        Documentation=https://github.com/GoogleCloudPlatform/kubernetes
-        Requires=kube-apiserver.service
-        After=kube-apiserver.service
-
-        [Service]
-        ExecStartPre=/usr/bin/curl -L -o /opt/bin/kube-controller-manager -z /opt/bin/kube-controller-manager https://storage.googleapis.com/kubernetes-release/release/v1.0.3/bin/linux/amd64/kube-controller-manager
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/kube-controller-manager
-        ExecStart=/opt/bin/kube-controller-manager \
-        --service-account-private-key-file=/opt/bin/kube-serviceaccount.key \
-        --master=127.0.0.1:8080 \
-        --logtostderr=true
-        Restart=always
-        RestartSec=10
-    - name: kube-scheduler.service
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes Scheduler
-        Documentation=https://github.com/GoogleCloudPlatform/kubernetes
-        Requires=kube-apiserver.service
-        After=kube-apiserver.service
-
-        [Service]
-        ExecStartPre=/usr/bin/curl -L -o /opt/bin/kube-scheduler -z /opt/bin/kube-scheduler https://storage.googleapis.com/kubernetes-release/release/v1.0.3/bin/linux/amd64/kube-scheduler
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/kube-scheduler
-        ExecStart=/opt/bin/kube-scheduler --master=127.0.0.1:8080
-        Restart=always
-        RestartSec=10
-  update:
-    group: alpha
-    reboot-strategy: off
diff --git a/v1.2/docs/getting-started-guides/coreos/cloud-configs/node.yaml b/v1.2/docs/getting-started-guides/coreos/cloud-configs/node.yaml
deleted file mode 100644
index b9a4cafcd9..0000000000
--- a/v1.2/docs/getting-started-guides/coreos/cloud-configs/node.yaml
+++ /dev/null
@@ -1,98 +0,0 @@
-#cloud-config
-write-files:
-  - path: /opt/bin/wupiao
-    permissions: '0755'
-    content: |
-      #!/bin/bash
-      # [w]ait [u]ntil [p]ort [i]s [a]ctually [o]pen
-      [ -n "$1" ] && [ -n "$2" ] && while ! curl --output /dev/null \
-        --silent --head --fail \
-        http://${1}:${2}; do sleep 1 && echo -n .; done;
-      exit $?
-coreos:
-  etcd2:
-    listen-client-urls: http://0.0.0.0:2379,http://0.0.0.0:4001
-    advertise-client-urls: http://0.0.0.0:2379,http://0.0.0.0:4001
-    initial-cluster: master=http://<master-private-ip>:2380
-    proxy: on
-  fleet:
-    metadata: "role=node"
-  units:
-    - name: fleet.service
-      command: start
-    - name: flanneld.service
-      command: start
-      drop-ins:
-        - name: 50-network-config.conf
-          content: |
-            [Unit]
-            Requires=etcd2.service
-            [Service]
-            ExecStartPre=/usr/bin/etcdctl set /coreos.com/network/config '{"Network":"10.244.0.0/16", "Backend": {"Type": "vxlan"}}'
-    - name: docker.service
-      command: start
-    - name: setup-network-environment.service
-      command: start
-      content: |
-        [Unit]
-        Description=Setup Network Environment
-        Documentation=https://github.com/kelseyhightower/setup-network-environment
-        Requires=network-online.target
-        After=network-online.target
-
-        [Service]
-        ExecStartPre=-/usr/bin/mkdir -p /opt/bin
-        ExecStartPre=/usr/bin/curl -L -o /opt/bin/setup-network-environment -z /opt/bin/setup-network-environment https://github.com/kelseyhightower/setup-network-environment/releases/download/v1.0.0/setup-network-environment
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/setup-network-environment
-        ExecStart=/opt/bin/setup-network-environment
-        RemainAfterExit=yes
-        Type=oneshot
-    - name: kube-proxy.service
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes Proxy
-        Documentation=https://github.com/GoogleCloudPlatform/kubernetes
-        Requires=setup-network-environment.service
-        After=setup-network-environment.service
-
-        [Service]
-        ExecStartPre=/usr/bin/curl -L -o /opt/bin/kube-proxy -z /opt/bin/kube-proxy https://storage.googleapis.com/kubernetes-release/release/v1.0.3/bin/linux/amd64/kube-proxy
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/kube-proxy
-        # wait for kubernetes master to be up and ready
-        ExecStartPre=/opt/bin/wupiao <master-private-ip> 8080
-        ExecStart=/opt/bin/kube-proxy \
-        --master=<master-private-ip>:8080 \
-        --logtostderr=true
-        Restart=always
-        RestartSec=10
-    - name: kube-kubelet.service
-      command: start
-      content: |
-        [Unit]
-        Description=Kubernetes Kubelet
-        Documentation=https://github.com/GoogleCloudPlatform/kubernetes
-        Requires=setup-network-environment.service
-        After=setup-network-environment.service
-
-        [Service]
-        EnvironmentFile=/etc/network-environment
-        ExecStartPre=/usr/bin/curl -L -o /opt/bin/kubelet -z /opt/bin/kubelet https://storage.googleapis.com/kubernetes-release/release/v1.0.3/bin/linux/amd64/kubelet
-        ExecStartPre=/usr/bin/chmod +x /opt/bin/kubelet
-        # wait for kubernetes master to be up and ready
-        ExecStartPre=/opt/bin/wupiao <master-private-ip> 8080
-        ExecStart=/opt/bin/kubelet \
-        --address=0.0.0.0 \
-        --port=10250 \
-        --hostname-override=${DEFAULT_IPV4} \
-        --api-servers=<master-private-ip>:8080 \
-        --allow-privileged=true \
-        --logtostderr=true \
-        --cadvisor-port=4194 \
-        --healthz-bind-address=0.0.0.0 \
-        --healthz-port=10248
-        Restart=always
-        RestartSec=10
-  update:
-    group: alpha
-    reboot-strategy: off
diff --git a/v1.2/docs/getting-started-guides/dcos.md b/v1.2/docs/getting-started-guides/dcos.md
deleted file mode 100644
index bc2f3441a8..0000000000
--- a/v1.2/docs/getting-started-guides/dcos.md
+++ /dev/null
@@ -1,130 +0,0 @@
----
----
-
-This guide will walk you through installing [Kubernetes-Mesos](https://github.com/mesosphere/kubernetes-mesos) on [Datacenter Operating System (DCOS)](https://mesosphere.com/product/) with the [DCOS CLI](https://github.com/mesosphere/dcos-cli) and operating Kubernetes with the [DCOS Kubectl plugin](https://github.com/mesosphere/dcos-kubectl).
-
-* TOC
-{:toc}
-
-
-## About Kubernetes on DCOS
-
-DCOS is system software that manages computer cluster hardware and software resources and provides common services for distributed applications. Among other services, it provides [Apache Mesos](http://mesos.apache.org/) as its cluster kernel and [Marathon](https://mesosphere.github.io/marathon/) as its init system. With DCOS CLI, Mesos frameworks like [Kubernetes-Mesos](https://github.com/mesosphere/kubernetes-mesos) can be installed with a single command.
-
-Another feature of the DCOS CLI is that it allows plugins like the [DCOS Kubectl plugin](https://github.com/mesosphere/dcos-kubectl). This allows for easy access to a version-compatible Kubectl without having to manually download or install.
-
-Further information about the benefits of installing Kubernetes on DCOS can be found in the [Kubernetes-Mesos documentation](https://releases.k8s.io/{{page.githubbranch}}/contrib/mesos/README.md).
-
-For more details about the Kubernetes DCOS packaging, see the [Kubernetes-Mesos project](https://github.com/mesosphere/kubernetes-mesos).
-
-Since Kubernetes-Mesos is still alpha, it is a good idea to familiarize yourself with the [current known issues](https://releases.k8s.io/{{page.githubbranch}}/contrib/mesos/docs/issues.md) which may limit or modify the behavior of Kubernetes on DCOS.
-
-If you have problems completing the steps below, please [file an issue against the kubernetes-mesos project](https://github.com/mesosphere/kubernetes-mesos/issues).
-
-
-## Resources
-
-Explore the following resources for more information about Kubernetes, Kubernetes on Mesos/DCOS, and DCOS itself.
-
-- [DCOS Documentation](https://docs.mesosphere.com/)
-- [Managing DCOS Services](https://docs.mesosphere.com/services/kubernetes/)
-- [Kubernetes Examples](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/)
-- [Kubernetes on Mesos Documentation](https://releases.k8s.io/{{page.githubbranch}}/contrib/mesos/README.md)
-- [Kubernetes on Mesos Release Notes](https://github.com/mesosphere/kubernetes-mesos/releases)
-- [Kubernetes on DCOS Package Source](https://github.com/mesosphere/kubernetes-mesos)
-
-
-## Prerequisites
-
-- A running [DCOS cluster](https://mesosphere.com/product/)
-  - [DCOS Community Edition](https://docs.mesosphere.com/install/) is currently available on [AWS](https://mesosphere.com/amazon/).
-  - [DCOS Enterprise Edition](https://mesosphere.com/product/) can be deployed on virtual or bare metal machines. Contact sales@mesosphere.com for more info and to set up an engagement.
-- [DCOS CLI](https://docs.mesosphere.com/install/cli/) installed locally
-
-
-## Install
-
-1. Configure and validate the [Mesosphere Multiverse](https://github.com/mesosphere/multiverse) as a package source repository
-
-    ```shell
-$ dcos config prepend package.sources https://github.com/mesosphere/multiverse/archive/version-1.x.zip
-    $ dcos package update --validate
-    ```    
-2. Install etcd
-
-    By default, the Kubernetes DCOS package starts a single-node etcd. In order to avoid state loss in the event of Kubernetes component container failure, install an HA [etcd-mesos](https://github.com/mesosphere/etcd-mesos) cluster on DCOS.
-
-    ```shell
-$ dcos package install etcd
-    ```    
-3. Verify that etcd is installed and healthy
-
-    The etcd cluster takes a short while to deploy. Verify that `/etcd` is healthy before going on to the next step.
-
-    ```shell
-$ dcos marathon app list
-    ID           MEM  CPUS  TASKS  HEALTH  DEPLOYMENT  CONTAINER  CMD
-    /etcd        128  0.2    1/1    1/1       ---        DOCKER   None
-    ```    
-4. Create Kubernetes installation configuration
-
-    Configure Kubernetes to use the HA etcd installed on DCOS.
-
-    ```shell
-$ cat >/tmp/options.json <<EOF
-    {
-      "kubernetes": {
-        "etcd-mesos-framework-name": "etcd"
-      }
-    }
-    EOF
-    ```    
-5. Install Kubernetes
-
-    ```shell
-$ dcos package install --options=/tmp/options.json kubernetes
-    ```    
-6. Verify that Kubernetes is installed and healthy
-
-    The Kubernetes cluster takes a short while to deploy. Verify that `/kubernetes` is healthy before going on to the next step.
-
-    ```shell
-$ dcos marathon app list
-    ID           MEM  CPUS  TASKS  HEALTH  DEPLOYMENT  CONTAINER  CMD
-    /etcd        128  0.2    1/1    1/1       ---        DOCKER   None
-    /kubernetes  768   1     1/1    1/1       ---        DOCKER   None
-    ```    
-7. Verify that Kube-DNS & Kube-UI are deployed, running, and ready
-
-    ```shell
-$ dcos kubectl get pods --namespace=kube-system
-    NAME                READY     STATUS    RESTARTS   AGE
-    kube-dns-v8-tjxk9   4/4       Running   0          1m
-    kube-ui-v2-tjq7b    1/1       Running   0          1m
-    ```    
-Names and ages may vary.
-
-
-Now that Kubernetes is installed on DCOS, you may wish to explore the [Kubernetes Examples](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/) or the [Kubernetes User Guide](/{{page.version}}/docs/user-guide/).
-
-
-## Uninstall
-
-1. Stop and delete all replication controllers and pods in each namespace:
-
-    Before uninstalling Kubernetes, destroy all the pods and replication controllers. The uninstall process will try to do this itself, but by default it times out quickly and may leave your cluster in a dirty state.
-
-    ```shell
-$ dcos kubectl delete rc,pods --all --namespace=default
-    $ dcos kubectl delete rc,pods --all --namespace=kube-system
-    ```    
-2. Validate that all pods have been deleted
-
-    ```shell
-$ dcos kubectl get pods --all-namespaces
-    ```    
-3. Uninstall Kubernetes
-
-    ```shell
-$ dcos package uninstall kubernetes
-    ```
diff --git a/v1.2/docs/getting-started-guides/docker-multinode/master.md b/v1.2/docs/getting-started-guides/docker-multinode/master.md
deleted file mode 100644
index c62fb2bc2b..0000000000
--- a/v1.2/docs/getting-started-guides/docker-multinode/master.md
+++ /dev/null
@@ -1,179 +0,0 @@
----
----
-
-We'll begin by setting up the master node.  For the purposes of illustration, we'll assume that the IP of this machine is `${MASTER_IP}`
-
-There are two main phases to installing the master:
-   * [Setting up `flanneld` and `etcd`](#setting-up-flanneld-and-etcd)
-   * [Starting the Kubernetes master components](#starting-the-kubernetes-master)
-
-
-## Setting up flanneld and etcd
-
-_Note_:
-There is a [bug](https://github.com/docker/docker/issues/14106) in Docker 1.7.0 that prevents this from working correctly.
-Please install Docker 1.6.2 or Docker 1.7.1.
-
-### Setup Docker-Bootstrap
-
-We're going to use `flannel` to set up networking between Docker daemons.  Flannel itself (and etcd on which it relies) will run inside of
-Docker containers themselves.  To achieve this, we need a separate "bootstrap" instance of the Docker daemon.  This daemon will be started with
-`--iptables=false` so that it can only run containers with `--net=host`.  That's sufficient to bootstrap our system.
-
-Run:
-
-```shell
-sudo sh -c 'docker -d -H unix:///var/run/docker-bootstrap.sock -p /var/run/docker-bootstrap.pid --iptables=false --ip-masq=false --bridge=none --graph=/var/lib/docker-bootstrap 2> /var/log/docker-bootstrap.log 1> /dev/null &'
-```
-
-_Important Note_:
-If you are running this on a long running system, rather than experimenting, you should run the bootstrap Docker instance under something like SysV init, upstart or systemd so that it is restarted
-across reboots and failures.
-
-
-### Startup etcd for flannel and the API server to use
-
-Run:
-
-```shell
-sudo docker -H unix:///var/run/docker-bootstrap.sock run --net=host -d gcr.io/google_containers/etcd:2.0.12 /usr/local/bin/etcd --addr=127.0.0.1:4001 --bind-addr=0.0.0.0:4001 --data-dir=/var/etcd/data
-```
-
-Next, you need to set a CIDR range for flannel.  This CIDR should be chosen to be non-overlapping with any existing network you are using:
-
-```shell
-sudo docker -H unix:///var/run/docker-bootstrap.sock run --net=host gcr.io/google_containers/etcd:2.0.12 etcdctl set /coreos.com/network/config '{ "Network": "10.1.0.0/16" }'
-```
-
-### Set up Flannel on the master node
-
-Flannel is a network abstraction layer build by CoreOS, we will use it to provide simplified networking between our Pods of containers.
-
-Flannel re-configures the bridge that Docker uses for networking.  As a result we need to stop Docker, reconfigure its networking, and then restart Docker.
-
-#### Bring down Docker
-
-To re-configure Docker to use flannel, we need to take docker down, run flannel and then restart Docker.
-
-Turning down Docker is system dependent, it may be:
-
-```shell
-sudo /etc/init.d/docker stop
-```
-
-or
-
-```shell
-sudo systemctl stop docker
-```
-
-or it may be something else.
-
-#### Run flannel
-
-Now run flanneld itself:
-
-```shell
-sudo docker -H unix:///var/run/docker-bootstrap.sock run -d --net=host --privileged -v /dev/net:/dev/net quay.io/coreos/flannel:0.5.0
-```
-
-The previous command should have printed a really long hash, copy this hash.
-
-Now get the subnet settings from flannel:
-
-```shell
-sudo docker -H unix:///var/run/docker-bootstrap.sock exec <really-long-hash-from-above-here> cat /run/flannel/subnet.env
-```
-
-#### Edit the docker configuration
-
-You now need to edit the docker configuration to activate new flags.  Again, this is system specific.
-
-This may be in `/etc/default/docker` or `/etc/systemd/service/docker.service` or it may be elsewhere.
-
-Regardless, you need to add the following to the docker command line:
-
-```shell
---bip=${FLANNEL_SUBNET} --mtu=${FLANNEL_MTU}
-```
-
-#### Remove the existing Docker bridge
-
-Docker creates a bridge named `docker0` by default.  You need to remove this:
-
-```shell
-sudo /sbin/ifconfig docker0 down
-sudo brctl delbr docker0
-```
-
-You may need to install the `bridge-utils` package for the `brctl` binary.
-
-#### Restart Docker
-
-Again this is system dependent, it may be:
-
-```shell
-sudo /etc/init.d/docker start
-```
-
-it may be:
-
-```shell
-systemctl start docker
-```
-
-## Starting the Kubernetes Master
-
-Ok, now that your networking is set up, you can startup Kubernetes, this is the same as the single-node case, we will use the "main" instance of the Docker daemon for the Kubernetes components.
-
-```shell
-sudo docker run \
-    --volume=/:/rootfs:ro \
-    --volume=/sys:/sys:ro \
-    --volume=/dev:/dev \
-    --volume=/var/lib/docker/:/var/lib/docker:rw \
-    --volume=/var/lib/kubelet/:/var/lib/kubelet:rw \
-    --volume=/var/run:/var/run:rw \
-    --net=host \
-    --privileged=true \
-    --pid=host \ 
-    -d \
-    gcr.io/google_containers/hyperkube:v1.0.1 /hyperkube kubelet --api-servers=http://localhost:8080 --v=2 --address=0.0.0.0 --enable-server --hostname-override=127.0.0.1 --config=/etc/kubernetes/manifests-multi --cluster-dns=10.0.0.10 --cluster-domain=cluster.local
-```
-
-> Note that `--cluster-dns` and `--cluster-domain` is used to deploy dns, feel free to discard them if dns is not needed.
-
-### Also run the service proxy
-
-```shell
-sudo docker run -d --net=host --privileged gcr.io/google_containers/hyperkube:v1.0.1 /hyperkube proxy --master=http://127.0.0.1:8080 --v=2
-```
-
-### Test it out
-
-At this point, you should have a functioning 1-node cluster.  Let's test it out!
-
-Download the kubectl binary and make it available by editing your PATH ENV.
-([OS X](http://storage.googleapis.com/kubernetes-release/release/v1.0.1/bin/darwin/amd64/kubectl))
-([linux](http://storage.googleapis.com/kubernetes-release/release/v1.0.1/bin/linux/amd64/kubectl))
-
-List the nodes
-
-```shell
-kubectl get nodes
-```
-
-This should print:
-
-```shell
-NAME        LABELS                             STATUS
-127.0.0.1   kubernetes.io/hostname=127.0.0.1   Ready
-```
-
-If the status of the node is `NotReady` or `Unknown` please check that all of the containers you created are successfully running.
-If all else fails, ask questions on [Slack](/{{page.version}}/docs/troubleshooting/#slack).
-
-
-### Next steps
-
-Move on to [adding one or more workers](/{{page.version}}/docs/getting-started-guides/docker-multinode/worker) or [deploy a dns](/{{page.version}}/docs/getting-started-guides/docker-multinode/deployDNS)
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/docker-multinode/master.sh b/v1.2/docs/getting-started-guides/docker-multinode/master.sh
deleted file mode 100755
index 0a247804ec..0000000000
--- a/v1.2/docs/getting-started-guides/docker-multinode/master.sh
+++ /dev/null
@@ -1,176 +0,0 @@
-#!/bin/bash
-
-# Copyright 2015 The Kubernetes Authors All rights reserved.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# A scripts to install k8s worker node.
-# Author @wizard_cxy @reouser
-
-set -e
-
-# Make sure docker daemon is running
-if ( ! ps -ef | grep "/usr/bin/docker" | grep -v 'grep' &> /dev/null ); then
-    echo "Docker is not running on this machine!"
-    exit 1
-fi
-
-# Make sure k8s version env is properly set
-if [ -z ${K8S_VERSION} ]; then
-    K8S_VERSION="1.0.3"
-    echo "K8S_VERSION is not set, using default: ${K8S_VERSION}"
-else
-    echo "k8s version is set to: ${K8S_VERSION}"
-fi
-
-
-# Run as root
-if [ "$(id -u)" != "0" ]; then
-    echo >&2 "Please run as root"
-    exit 1
-fi
-
-# Check if a command is valid
-command_exists() {
-    command -v "$@" > /dev/null 2>&1
-}
-
-lsb_dist=""
-
-# Detect the OS distro, we support ubuntu, debian, mint, centos, fedora dist
-detect_lsb() {
-    case "$(uname -m)" in
-    *64)
-        ;;
-    *)
-        echo "Error: We currently only support 64-bit platforms."       
-        exit 1
-        ;;
-    esac
-
-    if command_exists lsb_release; then
-        lsb_dist="$(lsb_release -si)"
-    fi
-    if [ -z ${lsb_dist} ] && [ -r /etc/lsb-release ]; then
-        lsb_dist="$(. /etc/lsb-release && echo "$DISTRIB_ID")"
-    fi
-    if [ -z ${lsb_dist} ] && [ -r /etc/debian_version ]; then
-        lsb_dist='debian'
-    fi
-    if [ -z ${lsb_dist} ] && [ -r /etc/fedora-release ]; then
-        lsb_dist='fedora'
-    fi
-    if [ -z ${lsb_dist} ] && [ -r /etc/os-release ]; then
-        lsb_dist="$(. /etc/os-release && echo "$ID")"
-    fi
-
-    lsb_dist="$(echo ${lsb_dist} | tr '[:upper:]' '[:lower:]')"
-}
-
-
-# Start the bootstrap daemon
-bootstrap_daemon() {
-    sudo -b docker -d -H unix:///var/run/docker-bootstrap.sock -p /var/run/docker-bootstrap.pid --iptables=false --ip-masq=false --bridge=none --graph=/var/lib/docker-bootstrap 2> /var/log/docker-bootstrap.log 1> /dev/null
-    
-    sleep 5
-}
-
-# Start k8s components in containers
-DOCKER_CONF=""
-
-start_k8s(){
-    # Start etcd 
-    docker -H unix:///var/run/docker-bootstrap.sock run --restart=always --net=host -d gcr.io/google_containers/etcd:2.0.12 /usr/local/bin/etcd --addr=127.0.0.1:4001 --bind-addr=0.0.0.0:4001 --data-dir=/var/etcd/data
-
-    sleep 5
-    # Set flannel net config
-    docker -H unix:///var/run/docker-bootstrap.sock run --net=host gcr.io/google_containers/etcd:2.0.12 etcdctl set /coreos.com/network/config '{ "Network": "10.1.0.0/16", "Backend": {"Type": "vxlan"}}'
-
-    # iface may change to a private network interface, eth0 is for default
-    flannelCID=$(docker -H unix:///var/run/docker-bootstrap.sock run --restart=always -d --net=host --privileged -v /dev/net:/dev/net quay.io/coreos/flannel:0.5.0 /opt/bin/flanneld -iface="eth0")
-
-    sleep 8
-
-    # Copy flannel env out and source it on the host
-    docker -H unix:///var/run/docker-bootstrap.sock cp ${flannelCID}:/run/flannel/subnet.env .
-    source subnet.env
-
-    # Configure docker net settings, then restart it
-    case "$lsb_dist" in
-        fedora|centos|amzn)
-            DOCKER_CONF="/etc/sysconfig/docker"
-        ;;
-        ubuntu|debian|linuxmint)
-            DOCKER_CONF="/etc/default/docker"
-        ;;
-    esac
-
-    # Append the docker opts
-    echo "DOCKER_OPTS=\"\$DOCKER_OPTS --mtu=${FLANNEL_MTU} --bip=${FLANNEL_SUBNET}\"" | sudo tee -a ${DOCKER_CONF}
-
-
-    # sleep a little bit
-    ifconfig docker0 down
-
-    case "$lsb_dist" in
-        fedora|centos|amzn)
-            yum install bridge-utils && brctl delbr docker0 && systemctl restart docker
-        ;;
-        ubuntu|debian|linuxmint)
-            apt-get install bridge-utils && brctl delbr docker0 && service docker restart
-        ;;
-    esac
-
-    # sleep a little bit
-    sleep 5
-
-    # Start kubelet & proxy, then start master components as pods
-    docker run \
-        --net=host \
-        --pid=host \
-        --privileged \
-        --restart=always \
-        -d \
-        -v /sys:/sys:ro \
-        -v /var/run:/var/run:rw \
-        -v /:/rootfs:ro \
-        -v /dev:/dev \
-        -v /var/lib/docker/:/var/lib/docker:ro \
-        -v /var/lib/kubelet/:/var/lib/kubelet:rw \
-        gcr.io/google_containers/hyperkube:v${K8S_VERSION} \
-        /hyperkube kubelet \
-        --api-servers=http://localhost:8080 \
-        --v=2 --address=0.0.0.0 --enable-server \
-        --hostname-override=127.0.0.1 \
-        --config=/etc/kubernetes/manifests-multi \
-        --cluster-dns=10.0.0.10 \
-        --cluster-domain=cluster.local
-    
-    docker run \
-        -d \
-        --net=host \
-        --privileged \
-        gcr.io/google_containers/hyperkube:v${K8S_VERSION} \
-        /hyperkube proxy --master=http://127.0.0.1:8080 --v=2   
-}
-
-echo "Detecting your OS distro ..."
-detect_lsb
-
-echo "Starting bootstrap docker ..."
-bootstrap_daemon
-
-echo "Starting k8s ..."
-start_k8s
-
-echo "Master done!"
diff --git a/v1.2/docs/getting-started-guides/docker-multinode/skydns-rc.yaml.in b/v1.2/docs/getting-started-guides/docker-multinode/skydns-rc.yaml.in
deleted file mode 100644
index 845af9bf94..0000000000
--- a/v1.2/docs/getting-started-guides/docker-multinode/skydns-rc.yaml.in
+++ /dev/null
@@ -1,92 +0,0 @@
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: kube-dns-v8
-  namespace: kube-system
-  labels:
-    k8s-app: kube-dns
-    version: v8
-    kubernetes.io/cluster-service: "true"
-spec:
-  replicas: {{ pillar['dns_replicas'] }}
-  selector:
-    k8s-app: kube-dns
-    version: v8
-  template:
-    metadata:
-      labels:
-        k8s-app: kube-dns
-        version: v8
-        kubernetes.io/cluster-service: "true"
-    spec:
-      containers:
-      - name: etcd
-        image: gcr.io/google_containers/etcd:2.0.9
-        resources:
-          limits:
-            cpu: 100m
-            memory: 50Mi
-        command:
-        - /usr/local/bin/etcd
-        - -data-dir
-        - /var/etcd/data
-        - -listen-client-urls
-        - http://127.0.0.1:2379,http://127.0.0.1:4001
-        - -advertise-client-urls
-        - http://127.0.0.1:2379,http://127.0.0.1:4001
-        - -initial-cluster-token
-        - skydns-etcd
-        volumeMounts:
-        - name: etcd-storage
-          mountPath: /var/etcd/data
-      - name: kube2sky
-        image: gcr.io/google_containers/kube2sky:1.11
-        resources:
-          limits:
-            cpu: 100m
-            memory: 50Mi
-        args:
-        # command = "/kube2sky"
-        - -domain={{ pillar['dns_domain'] }}
-        - -kube_master_url=http://{kube_server_url}:8080
-      - name: skydns
-        image: gcr.io/google_containers/skydns:2015-03-11-001
-        resources:
-          limits:
-            cpu: 100m
-            memory: 50Mi
-        args:
-        # command = "/skydns"
-        - -machines=http://localhost:4001
-        - -addr=0.0.0.0:53
-        - -domain={{ pillar['dns_domain'] }}.
-        ports:
-        - containerPort: 53
-          name: dns
-          protocol: UDP
-        - containerPort: 53
-          name: dns-tcp
-          protocol: TCP
-        livenessProbe:
-          httpGet:
-            path: /healthz
-            port: 8080
-            scheme: HTTP
-          initialDelaySeconds: 30
-          timeoutSeconds: 5
-      - name: healthz
-        image: gcr.io/google_containers/exechealthz:1.0
-        resources:
-          limits:
-            cpu: 10m
-            memory: 20Mi
-        args:
-        - -cmd=nslookup kubernetes.default.svc.{{ pillar['dns_domain'] }} localhost >/dev/null
-        - -port=8080
-        ports:
-        - containerPort: 8080
-          protocol: TCP
-      volumes:
-      - name: etcd-storage
-        emptyDir: {}
-      dnsPolicy: Default  # Don't use cluster DNS.
diff --git a/v1.2/docs/getting-started-guides/docker-multinode/skydns-svc.yaml.in b/v1.2/docs/getting-started-guides/docker-multinode/skydns-svc.yaml.in
deleted file mode 100644
index 242c8871ee..0000000000
--- a/v1.2/docs/getting-started-guides/docker-multinode/skydns-svc.yaml.in
+++ /dev/null
@@ -1,20 +0,0 @@
-apiVersion: v1
-kind: Service
-metadata:
-  name: kube-dns
-  namespace: kube-system
-  labels:
-    k8s-app: kube-dns
-    kubernetes.io/cluster-service: "true"
-    kubernetes.io/name: "KubeDNS"
-spec:
-  selector:
-    k8s-app: kube-dns
-  clusterIP:  {{ pillar['dns_server'] }}
-  ports:
-  - name: dns
-    port: 53
-    protocol: UDP
-  - name: dns-tcp
-    port: 53
-    protocol: TCP
diff --git a/v1.2/docs/getting-started-guides/docker-multinode/testing.md b/v1.2/docs/getting-started-guides/docker-multinode/testing.md
deleted file mode 100644
index 0dc593d6a0..0000000000
--- a/v1.2/docs/getting-started-guides/docker-multinode/testing.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
----
-
-To validate that your node(s) have been added, run:
-
-```shell
-kubectl get nodes
-```
-
-That should show something like:
-
-```shell
-NAME           LABELS                                 STATUS
-10.240.99.26   kubernetes.io/hostname=10.240.99.26    Ready
-127.0.0.1      kubernetes.io/hostname=127.0.0.1       Ready
-```
-
-If the status of any node is `Unknown` or `NotReady` your cluster is broken, double check that all containers are running properly, and if all else fails, contact us on [Slack](/{{page.version}}/docs/troubleshooting/#slack).
-
-### Run an application
-
-```shell
-kubectl -s http://localhost:8080 run nginx --image=nginx --port=80
-```
-
-now run `docker ps` you should see nginx running.  You may need to wait a few minutes for the image to get pulled.
-
-### Expose it as a service
-
-```shell
-kubectl expose rc nginx --port=80
-```
-
-Run the following command to obtain the IP of this service we just created. There are two IPs, the first one is internal (`CLUSTER_IP`), and the second one is the external load-balanced IP.
-
-```shell
-kubectl get svc nginx
-```
-
-Alternatively, you can obtain only the first IP (CLUSTER_IP) by running:
-
-```shell
-{% raw %}kubectl get svc nginx --template={{.spec.clusterIP}}{% endraw %}
-```
-
-Hit the webserver with the first IP (CLUSTER_IP):
-
-```shell
-curl <insert-cluster-ip-here>
-```
-
-Note that you will need run this curl command on your boot2docker VM if you are running on OS X.
-
-### Scaling
-
-Now try to scale up the nginx you created before:
-
-```shell
-kubectl scale rc nginx --replicas=3
-```
-
-And list the pods
-
-```shell
-kubectl get pods
-```
-
-You should see pods landing on the newly added machine.
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/docker-multinode/worker.sh b/v1.2/docs/getting-started-guides/docker-multinode/worker.sh
deleted file mode 100755
index dda80b553c..0000000000
--- a/v1.2/docs/getting-started-guides/docker-multinode/worker.sh
+++ /dev/null
@@ -1,174 +0,0 @@
-#!/bin/bash
-
-# Copyright 2015 The Kubernetes Authors All rights reserved.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# A scripts to install k8s worker node.
-# Author @wizard_cxy @reouser
-
-set -e
-
-# Make sure docker daemon is running
-if ( ! ps -ef | grep "/usr/bin/docker" | grep -v 'grep' &> /dev/null  ); then
-    echo "Docker is not running on this machine!"
-    exit 1
-fi
-
-# Make sure k8s version env is properly set
-if [ -z ${K8S_VERSION} ]; then
-    K8S_VERSION="1.0.3"
-    echo "K8S_VERSION is not set, using default: ${K8S_VERSION}"
-else
-    echo "k8s version is set to: ${K8S_VERSION}"
-fi
-
-
-
-# Run as root
-if [ "$(id -u)" != "0" ]; then
-    echo >&2 "Please run as root"
-    exit 1
-fi
-
-# Make sure master ip is properly set
-if [ -z ${MASTER_IP} ]; then
-    echo "Please export MASTER_IP in your env"
-    exit 1
-else
-    echo "k8s master is set to: ${MASTER_IP}"
-fi
-
-# Check if a command is valid
-command_exists() {
-    command -v "$@" > /dev/null 2>&1
-}
-
-lsb_dist=""
-
-# Detect the OS distro, we support ubuntu, debian, mint, centos, fedora dist
-detect_lsb() {
-    case "$(uname -m)" in
-    *64)
-        ;;
-    *)
-	echo "Error: We currently only support 64-bit platforms."	    
-	exit 1
-	;;
-    esac
-
-    if command_exists lsb_release; then
-        lsb_dist="$(lsb_release -si)"
-    fi
-    if [ -z ${lsb_dist} ] && [ -r /etc/lsb-release ]; then
-        lsb_dist="$(. /etc/lsb-release && echo "$DISTRIB_ID")"
-    fi
-    if [ -z ${lsb_dist} ] && [ -r /etc/debian_version ]; then
-        lsb_dist='debian'
-    fi
-    if [ -z ${lsb_dist} ] && [ -r /etc/fedora-release ]; then
-        lsb_dist='fedora'
-    fi
-    if [ -z ${lsb_dist} ] && [ -r /etc/os-release ]; then
-        lsb_dist="$(. /etc/os-release && echo "$ID")"
-    fi
-
-    lsb_dist="$(echo ${lsb_dist} | tr '[:upper:]' '[:lower:]')"
-}
-
-
-# Start the bootstrap daemon
-bootstrap_daemon() {
-    sudo -b docker -d -H unix:///var/run/docker-bootstrap.sock -p /var/run/docker-bootstrap.pid --iptables=false --ip-masq=false --bridge=none --graph=/var/lib/docker-bootstrap 2> /var/log/docker-bootstrap.log 1> /dev/null
-
-    sleep 5
-}
-
-DOCKER_CONF=""
-
-# Start k8s components in containers
-start_k8s() {
-    # Start flannel
-    flannelCID=$(sudo docker -H unix:///var/run/docker-bootstrap.sock run -d --restart=always --net=host --privileged -v /dev/net:/dev/net quay.io/coreos/flannel:0.5.0 /opt/bin/flanneld --etcd-endpoints=http://${MASTER_IP}:4001 -iface="eth0")
-
-    sleep 8
-
-    # Copy flannel env out and source it on the host
-    sudo docker -H unix:///var/run/docker-bootstrap.sock cp ${flannelCID}:/run/flannel/subnet.env .
-    source subnet.env
-
-    # Configure docker net settings, then restart it
-    case "$lsb_dist" in
-        fedora|centos|amzn)
-            DOCKER_CONF="/etc/sysconfig/docker"
-        ;;
-        ubuntu|debian|linuxmint)
-            DOCKER_CONF="/etc/default/docker"
-        ;;
-    esac
-
-    echo "DOCKER_OPTS=\"\$DOCKER_OPTS --mtu=${FLANNEL_MTU} --bip=${FLANNEL_SUBNET}\"" | sudo tee -a ${DOCKER_CONF}
-
-    ifconfig docker0 down
-
-    case "$lsb_dist" in
-        fedora|centos)
-            yum install bridge-utils && brctl delbr docker0 && systemctl restart docker
-        ;;
-        ubuntu|debian|linuxmint)
-            apt-get install bridge-utils && brctl delbr docker0 && service docker restart
-        ;;
-    esac
-
-    # sleep a little bit
-    sleep 5
-    
-    # Start kubelet & proxy in container
-    docker run \
-        --net=host \
-        --pid=host \
-        --privileged \
-        --restart=always \
-        -d \
-        -v /sys:/sys:ro \
-        -v /var/run:/var/run:rw  \
-        -v /dev:/dev \
-        -v /var/lib/docker/:/var/lib/docker:ro \
-        -v /var/lib/kubelet/:/var/lib/kubelet:rw \
-        gcr.io/google_containers/hyperkube:v${K8S_VERSION} \
-        /hyperkube kubelet --api-servers=http://${MASTER_IP}:8080 \
-        --v=2 --address=0.0.0.0 --enable-server \
-        --hostname-override=$(hostname -i) \
-        --cluster-dns=10.0.0.10 \
-        --cluster-domain=cluster.local
-    
-    docker run \
-        -d \
-        --net=host \
-        --privileged \
-        --restart=always \
-        gcr.io/google_containers/hyperkube:v${K8S_VERSION} \
-        /hyperkube proxy --master=http://${MASTER_IP}:8080 \
-        --v=2
-}
-
-echo "Detecting your OS distro ..."
-detect_lsb
-
-echo "Starting bootstrap docker ..."
-bootstrap_daemon
-
-echo "Starting k8s ..."
-start_k8s
-
-echo "Worker done!"
diff --git a/v1.2/docs/getting-started-guides/docker.md b/v1.2/docs/getting-started-guides/docker.md
deleted file mode 100644
index 948edafd9d..0000000000
--- a/v1.2/docs/getting-started-guides/docker.md
+++ /dev/null
@@ -1,144 +0,0 @@
----
----
-
-The following instructions show you how to set up a simple, single node Kubernetes cluster using Docker.
-
-Here's a diagram of what the final result will look like:
-
-![Kubernetes Single Node on Docker](/images/docs/k8s-singlenode-docker.png)
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-1. You need to have docker installed on one machine.
-2. Your kernel should support memory and swap accounting. Ensure that the
-following configs are turned on in your linux kernel:
-
-```shell
-CONFIG_RESOURCE_COUNTERS=y
-CONFIG_MEMCG=y
-CONFIG_MEMCG_SWAP=y
-CONFIG_MEMCG_SWAP_ENABLED=y
-CONFIG_MEMCG_KMEM=y
-```
-
-3. Enable the memory and swap accounting in the kernel, at boot, as command line
-parameters as follows:
-
-```shell
-GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1"
-```
-
-NOTE: The above is specifically for GRUB2.
-    You can check the command line parameters passed to your kernel by looking at the
-    output of /proc/cmdline:
-
-```shell
-$cat /proc/cmdline
-    BOOT_IMAGE=/boot/vmlinuz-3.18.4-aufs root=/dev/sda5 ro cgroup_enable=memory
-    swapaccount=1
-```
-
-### Step One: Run etcd
-
-```shell
-docker run --net=host -d gcr.io/google_containers/etcd:2.0.12 /usr/local/bin/etcd --addr=127.0.0.1:4001 --bind-addr=0.0.0.0:4001 --data-dir=/var/etcd/data
-```
-
-### Step Two: Run the master
-
-```shell
-docker run \
-    --volume=/:/rootfs:ro \
-    --volume=/sys:/sys:ro \
-    --volume=/dev:/dev \
-    --volume=/var/lib/docker/:/var/lib/docker:ro \
-    --volume=/var/lib/kubelet/:/var/lib/kubelet:rw \
-    --volume=/var/run:/var/run:rw \
-    --net=host \
-    --pid=host \
-    --privileged=true \
-    -d \
-    gcr.io/google_containers/hyperkube:v1.0.1 \
-    /hyperkube kubelet --containerized --hostname-override="127.0.0.1" --address="0.0.0.0" --api-servers=http://localhost:8080 --config=/etc/kubernetes/manifests
-```
-
-This actually runs the kubelet, which in turn runs a [pod](/{{page.version}}/docs/user-guide/pods) that contains the other master components.
-
-### Step Three: Run the service proxy
-
-```shell
-docker run -d --net=host --privileged gcr.io/google_containers/hyperkube:v1.0.1 /hyperkube proxy --master=http://127.0.0.1:8080 --v=2
-```
-
-### Test it out
-
-At this point you should have a running Kubernetes cluster.  You can test this by downloading the kubectl
-binary
-([OS X](https://storage.googleapis.com/kubernetes-release/release/v1.0.1/bin/darwin/amd64/kubectl))
-([linux](https://storage.googleapis.com/kubernetes-release/release/v1.0.1/bin/linux/amd64/kubectl))
-
-*Note:*
-On OS/X you will need to set up port forwarding via ssh:
-
-```shell
-boot2docker ssh -L8080:localhost:8080
-```
-
-List the nodes in your cluster by running:
-
-```shell
-kubectl get nodes
-```
-
-This should print:
-
-```shell
-NAME        LABELS    STATUS
-127.0.0.1   <none>    Ready
-```
-
-If you are running different Kubernetes clusters, you may need to specify `-s http://localhost:8080` to select the local cluster.
-
-### Run an application
-
-```shell
-kubectl -s http://localhost:8080 run nginx --image=nginx --port=80
-```
-
-Now run `docker ps` you should see nginx running.  You may need to wait a few minutes for the image to get pulled.
-
-### Expose it as a service
-
-```shell
-kubectl expose rc nginx --port=80
-```
-
-Run the following command to obtain the IP of this service we just created. There are two IPs, the first one is internal (CLUSTER_IP), and the second one is the external load-balanced IP.
-
-```shell
-kubectl get svc nginx
-```
-
-Alternatively, you can obtain only the first IP (CLUSTER_IP) by running:
-
-```shell
-kubectl get svc nginx --template={{.spec.clusterIP}}
-```
-
-Hit the webserver with the first IP (CLUSTER_IP):
-
-```shell
-curl <insert-cluster-ip-here>
-```
-
-Note that you will need run this curl command on your boot2docker VM if you are running on OS X.
-
-### A note on turning down your cluster
-
-Many of these containers run under the management of the `kubelet` binary, which attempts to keep containers running, even if they fail.  So, in order to turn down
-the cluster, you need to first kill the kubelet container, and then any other containers.
-
-You may use `docker kill $(docker ps -aq)`, note this removes _all_ containers running under Docker, so use with caution.
diff --git a/v1.2/docs/getting-started-guides/fedora/fedora-calico.md b/v1.2/docs/getting-started-guides/fedora/fedora-calico.md
deleted file mode 100644
index a73b7e23bc..0000000000
--- a/v1.2/docs/getting-started-guides/fedora/fedora-calico.md
+++ /dev/null
@@ -1,310 +0,0 @@
----
----
-
-This guide will walk you through the process of getting a Kubernetes Fedora cluster running on Digital Ocean with networking powered by Calico networking.
-It will cover the installation and configuration of the following systemd processes on the following hosts:
-
-Kubernetes Master:
-
-- `kube-apiserver`
-- `kube-controller-manager`
-- `kube-scheduler`
-- `etcd`
-- `docker`
-- `calico-node`
-
-Kubernetes Node:
-
-- `kubelet`
-- `kube-proxy`
-- `docker`
-- `calico-node`
-
-For this demo, we will be setting up one Master and one Node with the following information:
-
-|  Hostname   |     IP      |
-|-------------|-------------|
-| kube-master |10.134.251.56|
-| kube-node-1 |10.134.251.55|
-
-This guide is scalable to multiple nodes provided you [configure interface-cbr0 with its own subnet on each Node](#configure-the-virtual-interface---cbr0)
-and [add an entry to /etc/hosts for each host](#setup-communication-between-hosts).
-
-Ensure you substitute the IP Addresses and Hostnames used in this guide with ones in your own setup.
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-You need two or more Fedora 22 droplets on Digital Ocean with [Private Networking](https://www.digitalocean.com/community/tutorials/how-to-set-up-and-use-digitalocean-private-networking) enabled.
-
-## Setup Communication Between Hosts
-
-Digital Ocean private networking configures a private network on eth1 for each host.  To simplify communication between the hosts, we will add an entry to /etc/hosts
-so that all hosts in the cluster can hostname-resolve one another to this interface.  **It is important that the hostname resolves to this interface instead of eth0, as
-all Kubernetes and Calico services will be running on it.**
-
-```shell
-echo "10.134.251.56 kube-master" >> /etc/hosts
-echo "10.134.251.55 kube-node-1" >> /etc/hosts
-```
-
-> Make sure that communication works between kube-master and each kube-node by using a utility such as ping.
-
-## Setup Master
-
-### Install etcd
-
-* Both Calico and Kubernetes use etcd as their datastore. We will run etcd on Master and point all Kubernetes and Calico services at it.
-
-```shell
-yum -y install etcd
-```
-
-* Edit `/etc/etcd/etcd.conf`
-
-```conf
-ETCD_LISTEN_CLIENT_URLS="http://kube-master:4001"
-
-ETCD_ADVERTISE_CLIENT_URLS="http://kube-master:4001"
-```
-
-### Install Kubernetes
-
-* Run the following command on Master to install the latest Kubernetes (as well as docker):
-
-```shell
-yum -y install kubernetes
-```
-
-* Edit `/etc/kubernetes/config `
-
-```conf
-# How the controller-manager, scheduler, and proxy find the apiserver
-KUBE_MASTER="--master=http://kube-master:8080"
-```
-
-* Edit `/etc/kubernetes/apiserver`
-
-```conf
-# The address on the local server to listen to.
-KUBE_API_ADDRESS="--insecure-bind-address=0.0.0.0"
-
-KUBE_ETCD_SERVERS="--etcd-servers=http://kube-master:4001"
-
-# Remove ServiceAccount from this line to run without API Tokens
-KUBE_ADMISSION_CONTROL="--admission-control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ResourceQuota"
-```
-
-* Create /var/run/kubernetes on master:
-
-```shell
-mkdir /var/run/kubernetes
-chown kube:kube /var/run/kubernetes
-chmod 750 /var/run/kubernetes
-```
-
-* Start the appropriate services on master:
-
-```shell
-for SERVICE in etcd kube-apiserver kube-controller-manager kube-scheduler; do
-    systemctl restart $SERVICE
-    systemctl enable $SERVICE
-    systemctl status $SERVICE
-done
-```
-
-### Install Calico
-
-Next, we'll launch Calico on Master to allow communication between Pods and any services running on the Master.
-* Install calicoctl, the calico configuration tool.
-
-```shell
-wget https://github.com/Metaswitch/calico-docker/releases/download/v0.5.5/calicoctl
-chmod +x ./calicoctl
-sudo mv ./calicoctl /usr/bin
-```
-
-* Create `/etc/systemd/system/calico-node.service`
-
-```conf
-[Unit]
-Description=calicoctl node
-Requires=docker.service
-After=docker.service
-
-[Service]
-User=root
-Environment="ETCD_AUTHORITY=kube-master:4001"
-PermissionsStartOnly=true
-ExecStartPre=/usr/bin/calicoctl checksystem --fix
-ExecStart=/usr/bin/calicoctl node --ip=10.134.251.56 --detach=false
-
-[Install]
-WantedBy=multi-user.target
-```
-
->Be sure to substitute `--ip=10.134.251.56` with your Master's eth1 IP Address.
-
-* Start Calico
-
-```shell
-systemctl enable calico-node.service
-systemctl start calico-node.service
-```
-
->Starting calico for the first time may take a few minutes as the calico-node docker image is downloaded.
-
-## Setup Node
-
-### Configure the Virtual Interface - cbr0
-
-By default, docker will create and run on a virtual interface called `docker0`. This interface is automatically assigned the address range 172.17.42.1/16.
-In order to set our own address range, we will create a new virtual interface called `cbr0` and then start docker on it.
-
-* Add a virtual interface by creating `/etc/sysconfig/network-scripts/ifcfg-cbr0`:
-
-```conf
-DEVICE=cbr0
-TYPE=Bridge
-IPADDR=192.168.1.1
-NETMASK=255.255.255.0
-ONBOOT=yes
-BOOTPROTO=static
-```
-
->**Note for Multi-Node Clusters:** Each node should be assigned an IP address on a unique subnet. In this example, node-1 is using 192.168.1.1/24,
-so node-2 should be assigned another pool on the 192.168.x.0/24 subnet, e.g. 192.168.2.1/24.
-
-* Ensure that your system has bridge-utils installed. Then, restart the networking daemon to activate the new interface
-
-```shell
-systemctl restart network.service
-```
-
-### Install Docker
-
-* Install Docker
-
-```shell
-yum -y install docker
-```
-
-* Configure docker to run on `cbr0` by editing `/etc/sysconfig/docker-network`:
-
-```conf
-DOCKER_NETWORK_OPTIONS="--bridge=cbr0 --iptables=false --ip-masq=false"
-```
-
-* Start docker
-
-```shell
-systemctl start docker
-```
-
-### Install Calico
-
-* Install calicoctl, the calico configuration tool.
-
-```shell
-wget https://github.com/Metaswitch/calico-docker/releases/download/v0.5.5/calicoctl
-chmod +x ./calicoctl
-sudo mv ./calicoctl /usr/bin
-```
-
-* Create `/etc/systemd/system/calico-node.service`
-
-```conf
-[Unit]
-Description=calicoctl node
-Requires=docker.service
-After=docker.service
-
-[Service]
-User=root
-Environment="ETCD_AUTHORITY=kube-master:4001"
-PermissionsStartOnly=true
-ExecStartPre=/usr/bin/calicoctl checksystem --fix
-ExecStart=/usr/bin/calicoctl node --ip=10.134.251.55 --detach=false --kubernetes
-
-[Install]
-WantedBy=multi-user.target
-```
-
-> Note: You must replace the IP address with your node's eth1 IP Address!
-
-* Start Calico
-
-```shell
-systemctl enable calico-node.service
-systemctl start calico-node.service
-```
-
-* Configure the IP Address Pool
-
- Most Kubernetes application deployments will require communication between Pods and the kube-apiserver on Master. On a  standard Digital
-Ocean Private Network, requests sent from Pods to the kube-apiserver will not be returned as the networking fabric will drop response packets
-destined for any 192.168.0.0/16 address. To resolve this, you can have calicoctl add a masquerade rule to all outgoing traffic on the node:
-
-```shell
-ETCD_AUTHORITY=kube-master:4001 calicoctl pool add 192.168.0.0/16 --nat-outgoing
-```
-
-### Install Kubernetes
-
-* First, install Kubernetes.
-
-```shell
-yum -y install kubernetes
-```
-
-* Edit `/etc/kubernetes/config`
-
-```conf
-# How the controller-manager, scheduler, and proxy find the apiserver
-KUBE_MASTER="--master=http://kube-master:8080"
-```
-
-* Edit `/etc/kubernetes/kubelet`
-
-  We'll pass in an extra parameter - `--network-plugin=calico` to tell the Kubelet to use the Calico networking plugin. Additionally, we'll add two
-environment variables that will be used by the Calico networking plugin.
-
-```shell
-# The address for the info server to serve on (set to 0.0.0.0 or "" for all interfaces)
-KUBELET_ADDRESS="--address=0.0.0.0"
-
-# You may leave this blank to use the actual hostname
-# KUBELET_HOSTNAME="--hostname-override=127.0.0.1"
-
-# location of the api-server
-KUBELET_API_SERVER="--api-servers=http://kube-master:8080"
-
-# Add your own!
-KUBELET_ARGS="--network-plugin=calico"
-
-# The following are variables which the kubelet will pass to the calico-networking plugin
-ETCD_AUTHORITY="kube-master:4001"
-KUBE_API_ROOT="http://kube-master:8080/api/v1"
-```
-
-* Start Kubernetes on the node.
-
-```shell
-for SERVICE in kube-proxy kubelet; do 
-    systemctl restart $SERVICE
-    systemctl enable $SERVICE
-    systemctl status $SERVICE 
-done
-```
-
-## Check Running Cluster
-
-The cluster should be running! Check that your nodes are reporting as such:
-
-```shell
-kubectl get nodes
-NAME          LABELS                               STATUS
-kube-node-1   kubernetes.io/hostname=kube-node-1   Ready
-```
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/fedora/fedora_ansible_config.md b/v1.2/docs/getting-started-guides/fedora/fedora_ansible_config.md
deleted file mode 100644
index 4956f48ec8..0000000000
--- a/v1.2/docs/getting-started-guides/fedora/fedora_ansible_config.md
+++ /dev/null
@@ -1,226 +0,0 @@
----
----
-
-Configuring Kubernetes on Fedora via Ansible offers a simple way to quickly create a clustered environment with little effort.
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-1. Host able to run ansible and able to clone the following repo: [kubernetes](https://github.com/kubernetes/kubernetes.git)
-2. A Fedora 21+ host to act as cluster master
-3. As many Fedora 21+ hosts as you would like, that act as cluster nodes
-
-The hosts can be virtual or bare metal. Ansible will take care of the rest of the configuration for you - configuring networking, installing packages, handling the firewall, etc. This example will use one master and two nodes.
-
-## Architecture of the cluster
-
-A Kubernetes cluster requires etcd, a master, and n nodes, so we will create a cluster with three hosts, for example:
-
-```shell
-master,etcd = kube-master.example.com
-    node1 = kube-node-01.example.com
-    node2 = kube-node-02.example.com
-```
-
-**Make sure your local machine has**
-
- - ansible (must be 1.9.0+)
- - git
- - python-netaddr
-
-If not
-
-```shell
-yum install -y ansible git python-netaddr
-```
-
-**Now clone down the Kubernetes repository**
-
-```shell
-git clone https://github.com/kubernetes/contrib.git
-cd contrib/ansible
-```
-
-**Tell ansible about each machine and its role in your cluster**
-
-Get the IP addresses from the master and nodes.  Add those to the `~/contrib/ansible/inventory` file on the host running Ansible.
-
-```shell
-[masters]
-kube-master.example.com
-
-[etcd]
-kube-master.example.com
-
-[nodes]
-kube-node-01.example.com
-kube-node-02.example.com
-```
-
-## Setting up ansible access to your nodes
-
-If you already are running on a machine which has passwordless ssh access to the kube-master and kube-node-{01,02} nodes, and 'sudo' privileges, simply set the value of `ansible_ssh_user` in `~/contrib/ansible/group_vars/all.yaml` to the username which you use to ssh to the nodes (i.e. `fedora`), and proceed to the next step...
-
-*Otherwise* setup ssh on the machines like so (you will need to know the root password to all machines in the cluster).
-
-edit: ~/contrib/ansible/group_vars/all.yml
-
-```yaml
-ansible_ssh_user: root
-```
-
-**Configuring ssh access to the cluster**
-
-If you already have ssh access to every machine using ssh public keys you may skip to [setting up the cluster](#setting-up-the-cluster)
-
-Make sure your local machine (root) has an ssh key pair if not
-
-```shell
-ssh-keygen
-```
-
-Copy the ssh public key to **all** nodes in the cluster
-
-```shell
-for node in kube-master.example.com kube-node-01.example.com kube-node-02.example.com; do
-  ssh-copy-id ${node}
-done
-```
-
-## Setting up the cluster
-
-Although the default value of variables in `~/contrib/ansible/group_vars/all.yml` should be good enough, if not, change them as needed.
-
-```conf
-edit: ~/contrib/ansible/group_vars/all.yml
-```
-
-**Configure access to kubernetes packages**
-
-Modify `source_type` as below to access kubernetes packages through the package manager.
-
-```yaml
-source_type: packageManager
-```
-
-**Configure the IP addresses used for services**
-
-Each Kubernetes service gets its own IP address.  These are not real IPs.  You need only select a range of IPs which are not in use elsewhere in your environment.
-
-```yaml
-kube_service_addresses: 10.254.0.0/16
-```
-
-**Managing flannel**
-
-Modify `flannel_subnet`, `flannel_prefix` and `flannel_host_prefix` only if defaults are not appropriate for your cluster.
-
-
-**Managing add on services in your cluster**
-
-Set `cluster_logging` to false or true (default) to disable or enable logging with elasticsearch.
-
-```yaml
-cluster_logging: true
-```
-
-Turn `cluster_monitoring` to true (default) or false to enable or disable cluster monitoring with heapster and influxdb.
-
-```yaml
-cluster_monitoring: true
-```
-
-Turn `dns_setup` to true (recommended) or false to enable or disable whole DNS configuration.
-
-```yaml
-dns_setup: true
-```
-
-**Tell ansible to get to work!**
-
-This will finally setup your whole Kubernetes cluster for you.
-
-```shell
-cd ~/contrib/ansible/
-
-./setup.sh
-```
-
-## Testing and using your new cluster
-
-That's all there is to it.  It's really that easy.  At this point you should have a functioning Kubernetes cluster.
-
-**Show kubernetes nodes**
-
-Run the following on the kube-master:
-
-```shell
-kubectl get nodes
-```
-
-**Show services running on masters and nodes**
-
-```shell
-systemctl | grep -i kube
-```
-
-**Show firewall rules on the masters and nodes**
-
-```shell
-iptables -nvL

-```
-**Create /tmp/apache.json on the master with the following contents and deploy pod**
-
-```json
-{
-  "kind": "Pod",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "fedoraapache",
-    "labels": {
-      "name": "fedoraapache"
-    }
-  },
-  "spec": {
-    "containers": [
-      {
-        "name": "fedoraapache",
-        "image": "fedora/apache",
-        "ports": [
-          {
-            "hostPort": 80,
-            "containerPort": 80
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-```shell
-kubectl create -f /tmp/apache.json
-```
-
-**Check where the pod was created**
-
-```shell
-kubectl get pods
-```
-
-**Check Docker status on nodes**
-
-```shell
-docker ps
-docker images
-```
-
-**After the pod is 'Running' Check web server access on the node**
-
-```shell
-curl http://localhost
-```
-
-That's it !
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md b/v1.2/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md
deleted file mode 100644
index e816b545c3..0000000000
--- a/v1.2/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md
+++ /dev/null
@@ -1,173 +0,0 @@
----
----
-
-This document describes how to deploy Kubernetes on multiple hosts to set up a multi-node cluster and networking with flannel. Follow fedora [getting started guide](/{{page.version}}/docs/getting-started-guides/fedora/fedora_manual_config) to setup 1 master (fed-master) and 2 or more nodes. Make sure that all nodes have different names (fed-node1, fed-node2 and so on) and labels (fed-node1-label, fed-node2-label, and so on) to avoid any conflict. Also make sure that the Kubernetes master host is running etcd, kube-controller-manager, kube-scheduler, and kube-apiserver services, and the nodes are running docker, kube-proxy and kubelet services. Now install flannel on Kubernetes nodes. flannel on each node configures an overlay network that docker uses. flannel runs on each node to setup a unique class-C container network.
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-You need 2 or more machines with Fedora installed.
-
-## Master Setup
-
-**Perform following commands on the Kubernetes master**
-
-Configure flannel by creating a `flannel-config.json` in your current directory on fed-master. flannel provides udp and vxlan among other overlay networking backend options. In this guide, we choose kernel based vxlan backend. The contents of the json are:
-
-```json
-{
-    "Network": "18.16.0.0/16",
-    "SubnetLen": 24,
-    "Backend": {
-        "Type": "vxlan",
-        "VNI": 1
-     }
-}
-```
-
-**NOTE:** Choose an IP range that is *NOT* part of the public IP address range.
-
-Add the configuration to the etcd server on fed-master.
-
-```shell
-etcdctl set /coreos.com/network/config < flannel-config.json
-```
-
-* Verify the key exists in the etcd server on fed-master.
-
-```shell
-etcdctl get /coreos.com/network/config
-```
-
-## Node Setup
-
-**Perform following commands on all Kubernetes nodes**
-
-Edit the flannel configuration file /etc/sysconfig/flanneld as follows:
-
-```shell
-# Flanneld configuration options
-
-# etcd url location.  Point this to the server where etcd runs
-FLANNEL_ETCD="http://fed-master:4001"
-
-# etcd config key.  This is the configuration key that flannel queries
-# For address range assignment
-FLANNEL_ETCD_KEY="/coreos.com/network"
-
-# Any additional options that you want to pass
-FLANNEL_OPTIONS=""
-```
-
-**Note:** By default, flannel uses the interface for the default route. If you have multiple interfaces and would like to use an interface other than the default route one, you could add "-iface=" to FLANNEL_OPTIONS. For additional options, run `flanneld --help` on command line.
-
-Enable the flannel service.
-
-```shell
-systemctl enable flanneld
-```
-
-If docker is not running, then starting flannel service is enough and skip the next step.
-
-```shell
-systemctl start flanneld
-```
-
-If docker is already running, then stop docker, delete docker bridge (docker0), start flanneld and restart docker as follows. Another alternative is to just reboot the system (`systemctl reboot`).
-
-```shell
-systemctl stop docker
-ip link delete docker0
-systemctl start flanneld
-systemctl start docker
-```
-
-
-## **Test the cluster and flannel configuration**
-
-Now check the interfaces on the nodes. Notice there is now a flannel.1 interface, and the ip addresses of docker0 and flannel.1 interfaces are in the same network. You will notice that docker0 is assigned a subnet (18.16.29.0/24 as shown below) on each Kubernetes node out of the IP range configured above. A working output should look like this:
-
-```shell
-# ip -4 a|grep inet
-    inet 127.0.0.1/8 scope host lo
-    inet 192.168.122.77/24 brd 192.168.122.255 scope global dynamic eth0
-    inet 18.16.29.0/16 scope global flannel.1
-    inet 18.16.29.1/24 scope global docker0
-```
-
-From any node in the cluster, check the cluster members by issuing a query to etcd server via curl (only partial output is shown using `grep -E "\{|\}|key|value"`). If you set up a 1 master and 3 nodes cluster, you should see one block for each node showing the subnets they have been assigned. You can associate those subnets to each node by the MAC address (VtepMAC) and IP address (Public IP) that is listed in the output.
-
-```shell
-curl -s http://fed-master:4001/v2/keys/coreos.com/network/subnets | python -mjson.tool
-```
-
-```json
-{
-    "node": {
-        "key": "/coreos.com/network/subnets",
-            {
-                "key": "/coreos.com/network/subnets/18.16.29.0-24",
-                "value": "{\"PublicIP\":\"192.168.122.77\",\"BackendType\":\"vxlan\",\"BackendData\":{\"VtepMAC\":\"46:f1:d0:18:d0:65\"}}"
-            },
-            {
-                "key": "/coreos.com/network/subnets/18.16.83.0-24",
-                "value": "{\"PublicIP\":\"192.168.122.36\",\"BackendType\":\"vxlan\",\"BackendData\":{\"VtepMAC\":\"ca:38:78:fc:72:29\"}}"
-            },
-            {
-                "key": "/coreos.com/network/subnets/18.16.90.0-24",
-                "value": "{\"PublicIP\":\"192.168.122.127\",\"BackendType\":\"vxlan\",\"BackendData\":{\"VtepMAC\":\"92:e2:80:ba:2d:4d\"}}"
-            }
-    }
-}
-```
-
-From all nodes, review the `/run/flannel/subnet.env` file.  This file was generated automatically by flannel.
-
-```shell
-# cat /run/flannel/subnet.env
-FLANNEL_SUBNET=18.16.29.1/24
-FLANNEL_MTU=1450
-FLANNEL_IPMASQ=false
-```
-
-At this point, we have etcd running on the Kubernetes master, and flannel / docker running on Kubernetes nodes. Next steps are for testing cross-host container communication which will confirm that docker and flannel are configured properly.
-
-Issue the following commands on any 2 nodes:
-
-```shell
-# docker run -it fedora:latest bash
-bash-4.3# 
-```
-
-This will place you inside the container. Install iproute and iputils packages to install ip and ping utilities. Due to a [bug](https://bugzilla.redhat.com/show_bug.cgi?id=1142311), it is required to modify capabilities of ping binary to work around "Operation not permitted" error.
-
-```shell
-bash-4.3# yum -y install iproute iputils
-bash-4.3# setcap cap_net_raw-ep /usr/bin/ping
-```
-
-Now note the IP address on the first node:
-
-```shell
-bash-4.3# ip -4 a l eth0 | grep inet
-    inet 18.16.29.4/24 scope global eth0
-```
-
-And also note the IP address on the other node:
-
-```shell
-bash-4.3# ip a l eth0 | grep inet
-    inet 18.16.90.4/24 scope global eth0
-```
-Now ping from the first node to the other node:
-
-```shell
-bash-4.3# ping 18.16.90.4
-PING 18.16.90.4 (18.16.90.4) 56(84) bytes of data.
-64 bytes from 18.16.90.4: icmp_seq=1 ttl=62 time=0.275 ms
-64 bytes from 18.16.90.4: icmp_seq=2 ttl=62 time=0.372 ms
-```
-
-Now Kubernetes multi-node cluster is set up with overlay networking set up by flannel.
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/gce.md b/v1.2/docs/getting-started-guides/gce.md
deleted file mode 100644
index 09786b54dc..0000000000
--- a/v1.2/docs/getting-started-guides/gce.md
+++ /dev/null
@@ -1,215 +0,0 @@
----
----
-
-
-The example below creates a Kubernetes cluster with 4 worker node Virtual Machines and a master Virtual Machine (i.e. 5 VMs in your cluster). This cluster is set up and controlled from your workstation (or wherever you find convenient).
-
-* TOC
-{:toc}
-
-### Before you start
-
-If you want a simplified getting started experience and GUI for managing clusters, please consider trying [Google Container Engine](https://cloud.google.com/container-engine/) (GKE) for hosted cluster installation and management.
-
-If you want to use custom binaries or pure open source Kubernetes, please continue with the instructions below.
-
-### Prerequisites
-
-1. You need a Google Cloud Platform account with billing enabled. Visit the [Google Developers Console](http://cloud.google.com/console) for more details.
-1. Install `gcloud` as necessary. `gcloud` can be installed as a part of the [Google Cloud SDK](https://cloud.google.com/sdk/).
-1. Then, make sure you have the `gcloud preview` command line component installed. Run `gcloud preview` at the command line - if it asks to install any components, go ahead and install them. If it simply shows help text, you're good to go. This is required as the cluster setup script uses GCE [Instance Groups](https://cloud.google.com/compute/docs/instance-groups/), which are in the gcloud preview namespace. You will also need to **enable [`Compute Engine Instance Group Manager API`](https://developers.google.com/console/help/new/#activatingapis)** in the developers console.
-1. Make sure that gcloud is set to use the Google Cloud Platform project you want. You can check the current project using `gcloud config list project` and change it via `gcloud config set project <project-id>`.
-1. Make sure you have credentials for GCloud by running ` gcloud auth login`.
-1. Make sure you can start up a GCE VM from the command line.  At least make sure you can do the [Create an instance](https://cloud.google.com/compute/docs/instances/#startinstancegcloud) part of the GCE Quickstart.
-1. Make sure you can ssh into the VM without interactive prompts.  See the [Log in to the instance](https://cloud.google.com/compute/docs/instances/#sshing) part of the GCE Quickstart.
-
-### Starting a cluster
-
-You can install a client and start a cluster with either one of these commands (we list both in case only one is installed on your machine):
-
-
-```shell
-curl -sS https://get.k8s.io | bash
-```
-
-or
-
-```shell
-wget -q -O - https://get.k8s.io | bash
-```
-
-Once this command completes, you will have a master VM and four worker VMs, running as a Kubernetes cluster.
-
-By default, some containers will already be running on your cluster. Containers like `kibana` and `elasticsearch` provide [logging](/{{page.version}}/docs/getting-started-guides/logging), while `heapster` provides [monitoring](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/README.md) services.
-
-The script run by the commands above creates a cluster with the name/prefix "kubernetes". It defines one specific cluster config, so you can't run it more than once.
-
-Alternately, you can download and install the latest Kubernetes release from [this page](https://github.com/kubernetes/kubernetes/releases), then run the `<kubernetes>/cluster/kube-up.sh` script to start the cluster:
-
-```shell
-cd kubernetes
-cluster/kube-up.sh
-```
-
-If you want more than one cluster running in your project, want to use a different name, or want a different number of worker nodes, see the `<kubernetes>/cluster/gce/config-default.sh` file for more fine-grained configuration before you start up your cluster.
-
-If you run into trouble, please see the section on [troubleshooting](/{{page.version}}/docs/getting-started-guides/gce/#troubleshooting), post to the
-[google-containers group](https://groups.google.com/forum/#!forum/google-containers), or come ask questions on [Slack](/{{page.version}}/docs/troubleshooting/#slack).
-
-The next few steps will show you:
-
-1. how to set up the command line client on your workstation to manage the cluster
-1. examples of how to use the cluster
-1. how to delete the cluster
-1. how to start clusters with non-default options (like larger clusters)
-
-### Installing the Kubernetes command line tools on your workstation
-
-The cluster startup script will leave you with a running cluster and a `kubernetes` directory on your workstation.
-The next step is to make sure the `kubectl` tool is in your path.
-
-The [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl) tool controls the Kubernetes cluster manager.  It lets you inspect your cluster resources, create, delete, and update components, and much more.
-You will use it to look at your new cluster and bring up example apps.
-
-Add the appropriate binary folder to your `PATH` to access kubectl:
-
-```shell
-# OS X
-export PATH=<path/to/kubernetes-directory>/platforms/darwin/amd64:$PATH
-# Linux
-export PATH=<path/to/kubernetes-directory>/platforms/linux/amd64:$PATH
-```
-
-**Note**: gcloud also ships with `kubectl`, which by default is added to your path.
-However the gcloud bundled kubectl version may be older than the one downloaded by the
-get.k8s.io install script. We recommend you use the downloaded binary to avoid
-potential issues with client/server version skew.
-
-#### Enabling bash completion of the Kubernetes command line tools
-
-You may find it useful to enable `kubectl` bash completion:
-
-```
-$ source ./contrib/completions/bash/kubectl
-```
-
-**Note**: This will last for the duration of your bash session. If you want to make this permanent you need to add this line in your bash profile.
-
-Alternatively, on most linux distributions you can also move the completions file to your bash_completions.d like this:
-
-```
-$ cp ./contrib/completions/bash/kubectl /etc/bash_completion.d/
-```
-
-but then you have to update it when you update kubectl.
-
-### Getting started with your cluster
-
-#### Inspect your cluster
-
-Once `kubectl` is in your path, you can use it to look at your cluster. E.g., running:
-
-```shell
-$ kubectl get --all-namespaces services
-```
-
-should show a set of [services](/{{page.version}}/docs/user-guide/services) that look something like this:
-
-```shell
-NAMESPACE     NAME                  CLUSTER_IP       EXTERNAL_IP       PORT(S)       SELECTOR               AGE
-default       kubernetes            10.0.0.1         <none>            443/TCP       <none>                 1d
-kube-system   kube-dns              10.0.0.2         <none>            53/TCP,53/UDP k8s-app=kube-dns       1d
-kube-system   kube-ui               10.0.0.3         <none>            80/TCP        k8s-app=kube-ui        1d
-...
-```
-
-Similarly, you can take a look at the set of [pods](/{{page.version}}/docs/user-guide/pods) that were created during cluster startup.
-You can do this via the
-
-```shell
-$ kubectl get --all-namespaces pods
-```
-
-command.
-
-You'll see a list of pods that looks something like this (the name specifics will be different):
-
-```shell
-NAMESPACE     NAME                                           READY     STATUS    RESTARTS   AGE
-kube-system   fluentd-cloud-logging-kubernetes-minion-63uo   1/1       Running   0          14m
-kube-system   fluentd-cloud-logging-kubernetes-minion-c1n9   1/1       Running   0          14m
-kube-system   fluentd-cloud-logging-kubernetes-minion-c4og   1/1       Running   0          14m
-kube-system   fluentd-cloud-logging-kubernetes-minion-ngua   1/1       Running   0          14m
-kube-system   kube-dns-v5-7ztia                              3/3       Running   0          15m
-kube-system   kube-ui-v1-curt1                               1/1       Running   0          15m
-kube-system   monitoring-heapster-v5-ex4u3                   1/1       Running   1          15m
-kube-system   monitoring-influx-grafana-v1-piled             2/2       Running   0          15m
-```
-
-Some of the pods may take a few seconds to start up (during this time they'll show `Pending`), but check that they all show as `Running` after a short period.
-
-#### Run some examples
-
-Then, see [a simple nginx example](/{{page.version}}/docs/user-guide/simple-nginx) to try out your new cluster.
-
-For more complete applications, please look in the [examples directory](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/).  The [guestbook example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/) is a good "getting started" walkthrough.
-
-### Tearing down the cluster
-
-To remove/delete/teardown the cluster, use the `kube-down.sh` script.
-
-```shell
-cd kubernetes
-cluster/kube-down.sh
-```
-
-Likewise, the `kube-up.sh` in the same directory will bring it back up. You do not need to rerun the `curl` or `wget` command: everything needed to setup the Kubernetes cluster is now on your workstation.
-
-### Customizing
-
-The script above relies on Google Storage to stage the Kubernetes release. It
-then will start (by default) a single master VM along with 4 worker VMs.  You
-can tweak some of these parameters by editing `kubernetes/cluster/gce/config-default.sh`
-You can view a transcript of a successful cluster creation
-[here](https://gist.github.com/satnam6502/fc689d1b46db9772adea).
-
-### Troubleshooting
-
-#### Project settings
-
-You need to have the Google Cloud Storage API, and the Google Cloud Storage
-JSON API enabled. It is activated by default for new projects. Otherwise, it
-can be done in the Google Cloud Console.  See the [Google Cloud Storage JSON
-API Overview](https://cloud.google.com/storage/docs/json_api/) for more
-details.
-
-Also ensure that-- as listed in the [Prerequsites section](#prerequisites)-- you've enabled the `Compute Engine Instance Group Manager API`, and can start up a GCE VM from the command line as in the [GCE Quickstart](https://cloud.google.com/compute/docs/quickstart) instructions.
-
-#### Cluster initialization hang
-
-If the Kubernetes startup script hangs waiting for the API to be reachable, you can troubleshoot by SSHing into the master and node VMs and looking at logs such as `/var/log/startupscript.log`.
-
-**Once you fix the issue, you should run `kube-down.sh` to cleanup** after the partial cluster creation, before running `kube-up.sh` to try again.
-
-#### SSH
-
-If you're having trouble SSHing into your instances, ensure the GCE firewall
-isn't blocking port 22 to your VMs.  By default, this should work but if you
-have edited firewall rules or created a new non-default network, you'll need to
-expose it: `gcloud compute firewall-rules create default-ssh --network=<network-name>
---description "SSH allowed from anywhere" --allow tcp:22`
-
-Additionally, your GCE SSH key must either have no passcode or you need to be
-using `ssh-agent`.
-
-#### Networking
-
-The instances must be able to connect to each other using their private IP. The
-script uses the "default" network which should have a firewall rule called
-"default-allow-internal" which allows traffic on any port on the private IPs.
-If this rule is missing from the default network or if you change the network
-being used in `cluster/config-default.sh` create a new rule with the following
-field values:
-
-* Source Ranges: `10.0.0.0/8`
-* Allowed Protocols and Port: `tcp:1-65535;udp:1-65535;icmp`
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/index.md b/v1.2/docs/getting-started-guides/index.md
deleted file mode 100644
index 9218b643b7..0000000000
--- a/v1.2/docs/getting-started-guides/index.md
+++ /dev/null
@@ -1,177 +0,0 @@
----
----
-
-Kubernetes can run on a range of platforms, from your laptop, to VMs on a cloud provider, to rack of
-bare metal servers.  The effort required to set up a cluster varies from running a single command to
-crafting your own customized cluster.  We'll guide you in picking a solution that fits for your needs.
-
-If you just want to "kick the tires" on Kubernetes, we recommend the [local Docker-based](/{{page.version}}/docs/getting-started-guides/docker) solution.
-
-The local Docker-based solution is one of several [Local cluster](#local-machine-solutions) solutions
-that are quick to set up, but are limited to running on one machine.
-
-When you are ready to scale up to more machines and higher availability, a [Hosted](#hosted-solutions)
-solution is the easiest to create and maintain.
-
-[Turn-key cloud solutions](#turn-key-cloud-solutions) require only a few commands to create
-and cover a wider range of cloud providers.
-
-[Custom solutions](#custom-solutions) require more effort to setup but cover and even
-they vary from step-by-step instructions to general advice for setting up
-a Kubernetes cluster from scratch.
-
-* TOC
-{:toc}
-
-### Local-machine Solutions
-
-Local-machine solutions create a single cluster with one or more Kubernetes nodes on a single
-physical machine.  Setup is completely automated and doesn't require a cloud provider account.
-But their size and availability is limited to that of a single machine.
-
-The local-machine solutions are:
-
-- [Local Docker-based](/{{page.version}}/docs/getting-started-guides/docker) (recommended starting point)
-- [Vagrant](/{{page.version}}/docs/getting-started-guides/vagrant) (works on any platform with Vagrant: Linux, MacOS, or Windows.)
-- [No-VM local cluster](/{{page.version}}/docs/getting-started-guides/locally) (Linux only)
-
-
-### Hosted Solutions
-
-[Google Container Engine](https://cloud.google.com/container-engine) offers managed Kubernetes
-clusters.
-
-### Turn-key Cloud Solutions
-
-These solutions allow you to create Kubernetes clusters on a range of Cloud IaaS providers with only a
-few commands, and have active community support.
-
-- [GCE](/{{page.version}}/docs/getting-started-guides/gce)
-- [AWS](/{{page.version}}/docs/getting-started-guides/aws)
-- [Azure](/{{page.version}}/docs/getting-started-guides/coreos/azure/)
-
-### Custom Solutions
-
-Kubernetes can run on a wide range of Cloud providers and bare-metal environments, and with many
-base operating systems.
-
-If you can find a guide below that matches your needs, use it.  It may be a little out of date, but
-it will be easier than starting from scratch.  If you do want to start from scratch because you
-have special requirements or just because you want to understand what is underneath a Kubernetes
-cluster, try the [Getting Started from Scratch](/{{page.version}}/docs/getting-started-guides/scratch) guide.
-
-If you are interested in supporting Kubernetes on a new platform, check out our [advice for
-writing a new solution](/{{page.version}}/docs/devel/writing-a-getting-started-guide).
-
-#### Cloud
-
-These solutions are combinations of cloud provider and OS not covered by the above solutions.
-
-- [AWS + coreos](/{{page.version}}/docs/getting-started-guides/coreos)
-- [GCE + CoreOS](/{{page.version}}/docs/getting-started-guides/coreos)
-- [AWS + Ubuntu](/{{page.version}}/docs/getting-started-guides/juju)
-- [Joyent + Ubuntu](/{{page.version}}/docs/getting-started-guides/juju)
-- [Rackspace + CoreOS](/{{page.version}}/docs/getting-started-guides/rackspace)
-
-#### On-Premises VMs
-
-- [Vagrant](/{{page.version}}/docs/getting-started-guides/coreos) (uses CoreOS and flannel)
-- [CloudStack](/{{page.version}}/docs/getting-started-guides/cloudstack) (uses Ansible, CoreOS and flannel)
-- [Vmware](/{{page.version}}/docs/getting-started-guides/vsphere)  (uses Debian)
-- [juju.md](/{{page.version}}/docs/getting-started-guides/juju) (uses Juju, Ubuntu and flannel)
-- [Vmware](/{{page.version}}/docs/getting-started-guides/coreos)  (uses CoreOS and flannel)
-- [libvirt-coreos.md](/{{page.version}}/docs/getting-started-guides/libvirt-coreos)  (uses CoreOS)
-- [oVirt](/{{page.version}}/docs/getting-started-guides/ovirt)
-- [libvirt](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster) (uses Fedora and flannel)
-- [KVM](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster)  (uses Fedora and flannel)
-
-#### Bare Metal
-
-- [Offline](/{{page.version}}/docs/getting-started-guides/coreos/bare_metal_offline) (no internet required.  Uses CoreOS and Flannel)
-- [fedora/fedora_ansible_config.md](/{{page.version}}/docs/getting-started-guides/fedora/fedora_ansible_config)
-- [Fedora single node](/{{page.version}}/docs/getting-started-guides/fedora/fedora_manual_config)
-- [Fedora multi node](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster)
-- [Centos](/{{page.version}}/docs/getting-started-guides/centos/centos_manual_config)
-- [Ubuntu](/{{page.version}}/docs/getting-started-guides/ubuntu)
-- [Docker Multi Node](/{{page.version}}/docs/getting-started-guides/docker-multinode)
-
-#### Integrations
-
-These solutions provide integration with 3rd party schedulers, resource managers, and/or lower level platforms.
-
-- [Kubernetes on Mesos](/{{page.version}}/docs/getting-started-guides/mesos)
-  - Instructions specify GCE, but are generic enough to be adapted to most existing Mesos clusters
-- [Kubernetes on DCOS](/{{page.version}}/docs/getting-started-guides/dcos)
-  - Community Edition DCOS uses AWS
-  - Enterprise Edition DCOS supports cloud hosting, on-premise VMs, and bare metal
-
-## Table of Solutions
-
-Here are all the solutions mentioned above in table form.
-
-IaaS Provider        | Config. Mgmt | OS     | Networking  | Docs                                              | Conforms | Support Level
--------------------- | ------------ | ------ | ----------  | ---------------------------------------------     | ---------| ----------------------------
-GKE                  |              |        | GCE         | [docs](https://cloud.google.com/container-engine) | ['œ“][3]   | Commercial
-Vagrant              | Saltstack    | Fedora | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/vagrant)                                | ['œ“][2]   | Project
-GCE                  | Saltstack    | Debian | GCE         | [docs](/{{page.version}}/docs/getting-started-guides/gce)                                    | ['œ“][1]   | Project
-Azure                | CoreOS       | CoreOS | Weave       | [docs](/{{page.version}}/docs/getting-started-guides/coreos/azure/)                    |          | Community ([@errordeveloper](https://github.com/errordeveloper), [@squillace](https://github.com/squillace), [@chanezon](https://github.com/chanezon), [@crossorigin](https://github.com/crossorigin))
-Docker Single Node   | custom       | N/A    | local       | [docs](/{{page.version}}/docs/getting-started-guides/docker)                                 |          | Project ([@brendandburns](https://github.com/brendandburns))
-Docker Multi Node    | Flannel      | N/A    | local       | [docs](/{{page.version}}/docs/getting-started-guides/docker-multinode)                       |          | Project ([@brendandburns](https://github.com/brendandburns))
-Bare-metal           | Ansible      | Fedora | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/fedora/fedora_ansible_config)           |          | Project
-Digital Ocean        | custom       | Fedora | Calico      | [docs](/{{page.version}}/docs/getting-started-guides/fedora/fedora-calico)                   |          | Community (@djosborne)
-Bare-metal           | custom       | Fedora | _none_      | [docs](/{{page.version}}/docs/getting-started-guides/fedora/fedora_manual_config)            |          | Project
-Bare-metal           | custom       | Fedora | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
-libvirt              | custom       | Fedora | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
-KVM                  | custom       | Fedora | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/fedora/flannel_multi_node_cluster)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
-Mesos/Docker         | custom       | Ubuntu | Docker      | [docs](/{{page.version}}/docs/getting-started-guides/mesos-docker)                           |          | Community ([Kubernetes-Mesos Authors](https://github.com/mesosphere/kubernetes-mesos/blob/master/AUTHORS.md))
-Mesos/GCE            |              |        |             | [docs](/{{page.version}}/docs/getting-started-guides/mesos)                                  |          | Community ([Kubernetes-Mesos Authors](https://github.com/mesosphere/kubernetes-mesos/blob/master/AUTHORS.md))
-DCOS                 | Marathon   | CoreOS/Alpine | custom | [docs](/{{page.version}}/docs/getting-started-guides/dcos)                                   |          | Community ([Kubernetes-Mesos Authors](https://github.com/mesosphere/kubernetes-mesos/blob/master/AUTHORS.md))
-AWS                  | CoreOS       | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/coreos)                                 |          | Community
-GCE                  | CoreOS       | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/coreos)                                 |          | Community ([@pires](https://github.com/pires))
-Vagrant              | CoreOS       | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/coreos)                                 |          | Community ([@pires](https://github.com/pires), [@AntonioMeireles](https://github.com/AntonioMeireles))
-Bare-metal (Offline) | CoreOS       | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/coreos/bare_metal_offline)              |          | Community ([@jeffbean](https://github.com/jeffbean))
-Bare-metal           | CoreOS       | CoreOS | Calico      | [docs](/{{page.version}}/docs/getting-started-guides/coreos/bare_metal_calico)               |          | Community ([@caseydavenport](https://github.com/caseydavenport))
-CloudStack           | Ansible      | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/cloudstack)                             |          | Community ([@runseb](https://github.com/runseb))
-Vmware               |              | Debian | OVS         | [docs](/{{page.version}}/docs/getting-started-guides/vsphere)                                |          | Community ([@pietern](https://github.com/pietern))
-Bare-metal           | custom       | CentOS | _none_      | [docs](/{{page.version}}/docs/getting-started-guides/centos/centos_manual_config)            |          | Community ([@coolsvap](https://github.com/coolsvap))
-AWS                  | Juju         | Ubuntu | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/juju)                                   |          | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) )
-OpenStack/HPCloud    | Juju         | Ubuntu | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/juju)                                   |          | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) )
-Joyent               | Juju         | Ubuntu | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/juju)                                   |          | [Community](https://github.com/whitmo/bundle-kubernetes) ( [@whit](https://github.com/whitmo), [@matt](https://github.com/mbruzek), [@chuck](https://github.com/chuckbutler) )
-AWS                  | Saltstack    | Ubuntu | OVS         | [docs](/{{page.version}}/docs/getting-started-guides/aws)                                    |          | Community ([@justinsb](https://github.com/justinsb))
-Bare-metal           | custom       | Ubuntu | Calico      | [docs](/{{page.version}}/docs/getting-started-guides/ubuntu-calico)                          |          | Community ([@djosborne](https://github.com/djosborne))
-Bare-metal           | custom       | Ubuntu | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/ubuntu)                                 |          | Community ([@resouer](https://github.com/resouer), [@WIZARD-CXY](https://github.com/WIZARD-CXY))
-Local                |              |        | _none_      | [docs](/{{page.version}}/docs/getting-started-guides/locally)                                |          | Community ([@preillyme](https://github.com/preillyme))
-libvirt/KVM          | CoreOS       | CoreOS | libvirt/KVM | [docs](/{{page.version}}/docs/getting-started-guides/libvirt-coreos)                         |          | Community ([@lhuard1A](https://github.com/lhuard1A))
-oVirt                |              |        |             | [docs](/{{page.version}}/docs/getting-started-guides/ovirt)                                  |          | Community ([@simon3z](https://github.com/simon3z))
-Rackspace            | CoreOS       | CoreOS | flannel     | [docs](/{{page.version}}/docs/getting-started-guides/rackspace)                              |          | Community ([@doublerr](https://github.com/doublerr))
-any                  | any          | any    | any         | [docs](/{{page.version}}/docs/getting-started-guides/scratch)                                |          | Community ([@erictune](https://github.com/erictune))
-
-
-*Note*: The above table is ordered by version test/used in notes followed by support level.
-
-Definition of columns:
-
-- **IaaS Provider** is who/what provides the virtual or physical machines (nodes) that Kubernetes runs on.
-- **OS** is the base operating system of the nodes.
-- **Config. Mgmt** is the configuration management system that helps install and maintain Kubernetes software on the
-  nodes.
-- **Networking** is what implements the [networking model](/{{page.version}}/docs/admin/networking).  Those with networking type
-  _none_ may not support more than one node, or may support multiple VM nodes only in the same physical node.
-- **Conformance** indicates whether a cluster created with this configuration has passed the project's conformance
-  tests for supporting the API and base features of Kubernetes v1.0.0.
-- Support Levels
-  - **Project**:  Kubernetes Committers regularly use this configuration, so it usually works with the latest release
-    of Kubernetes.
-  - **Commercial**: A commercial offering with its own support arrangements.
-  - **Community**: Actively supported by community contributions. May not work with more recent releases of Kubernetes.
-  - **Inactive**: No active maintainer.  Not recommended for first-time Kubernetes users, and may be deleted soon.
-- **Notes** is relevant information such as the version of Kubernetes used.
-
-
-<!-- reference style links below here -->
-<!-- GCE conformance test result -->
-[1]: https://gist.github.com/erictune/4cabc010906afbcc5061
-<!-- Vagrant conformance test result -->
-[2]: https://gist.github.com/derekwaynecarr/505e56036cdf010bf6b6
-<!-- GKE conformance test result -->
-[3]: https://gist.github.com/erictune/2f39b22f72565365e59b
diff --git a/v1.2/docs/getting-started-guides/juju.md b/v1.2/docs/getting-started-guides/juju.md
deleted file mode 100644
index c5de10069a..0000000000
--- a/v1.2/docs/getting-started-guides/juju.md
+++ /dev/null
@@ -1,250 +0,0 @@
----
----
-
-[Juju](https://jujucharms.com/docs/stable/about-juju) makes it easy to deploy
-Kubernetes by provisioning, installing and configuring all the systems in
-the cluster.  Once deployed the cluster can easily scale up with one command
-to increase the cluster size.
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-> Note: If you're running kube-up, on Ubuntu - all of the dependencies
-> will be handled for you. You may safely skip to the section:
-> [Launch Kubernetes Cluster](#launch-kubernetes-cluster)
-
-### On Ubuntu
-
-[Install the Juju client](https://jujucharms.com/get-started) on your
-local Ubuntu system:
-
-```shell
-sudo add-apt-repository ppa:juju/stable
-sudo apt-get update
-sudo apt-get install juju-core juju-quickstart
-```
-
-### With Docker
-
-If you are not using Ubuntu or prefer the isolation of Docker, you may
-run the following:
-
-```shell
-mkdir ~/.juju
-sudo docker run -v ~/.juju:/home/ubuntu/.juju -ti jujusolutions/jujubox:latest
-```
-
-At this point from either path you will have access to the `juju
-quickstart` command.
-
-To set up the credentials for your chosen cloud run:
-
-```shell
-juju quickstart --constraints="mem=3.75G" -i
-```
-
-> The `constraints` flag is optional, it changes the size of virtual machines
-> that Juju will generate when it requests a new machine.  Larger machines
-> will run faster but cost more money than smaller machines.
-
-Follow the dialogue and choose `save` and `use`.  Quickstart will now
-bootstrap the juju root node and setup the juju web based user
-interface.
-
-
-## Launch Kubernetes cluster
-
-You will need to export the `KUBERNETES_PROVIDER` environment variable before
-bringing up the cluster.
-
-```shell
-export KUBERNETES_PROVIDER=juju
-cluster/kube-up.sh
-```
-
-If this is your first time running the `kube-up.sh` script, it will install
-the required dependencies to get started with Juju, additionally it will
-launch a curses based configuration utility allowing you to select your cloud
-provider and enter the proper access credentials.
-
-Next it will deploy the kubernetes master, etcd, 2 nodes with flannel based
-Software Defined Networking (SDN) so containers on different hosts can
-communicate with each other.
-
-
-## Exploring the cluster
-
-The `juju status` command provides information about each unit in the cluster:
-
-```shell
-$ juju status --format=oneline
-- docker/0: 52.4.92.78 (started)
-  - flannel-docker/0: 52.4.92.78 (started)
-  - kubernetes/0: 52.4.92.78 (started)
-- docker/1: 52.6.104.142 (started)
-  - flannel-docker/1: 52.6.104.142 (started)
-  - kubernetes/1: 52.6.104.142 (started)
-- etcd/0: 52.5.216.210 (started) 4001/tcp
-- juju-gui/0: 52.5.205.174 (started) 80/tcp, 443/tcp
-- kubernetes-master/0: 52.6.19.238 (started) 8080/tcp
-```
-
-You can use `juju ssh` to access any of the units:
-
-```shell
-juju ssh kubernetes-master/0
-```
-
-## Run some containers!
-
-`kubectl` is available on the Kubernetes master node.  We'll ssh in to
-launch some containers, but one could use `kubectl` locally by setting
-`KUBERNETES_MASTER` to point at the ip address of "kubernetes-master/0".
-
-No pods will be available before starting a container:
-
-```shell
-kubectl get pods
-NAME READY STATUSRESTARTS   AGE
-
-kubectl get replicationcontrollers
-CONTROLLER  CONTAINER(S)  IMAGE(S)  SELECTOR  REPLICAS
-```
-
-We'll follow the aws-coreos example. Create a pod manifest: `pod.json`
-
-```json
-{
-  "apiVersion": "v1",
-  "kind": "Pod",
-  "metadata": {
-"name": "hello",
-"labels": {
-  "name": "hello",
-  "environment": "testing"
-}
-  },
-  "spec": {
-"containers": [{
-  "name": "hello",
-  "image": "quay.io/kelseyhightower/hello",
-  "ports": [{
-"containerPort": 80,
-"hostPort": 80
-  }]
-}]
-  }
-}
-```
-
-Create the pod with kubectl:
-
-```shell
-kubectl create -f pod.json
-```
-
-Get info on the pod:
-
-```shell
-kubectl get pods
-```
-
-To test the hello app, we need to locate which node is hosting
-the container. Better tooling for using Juju to introspect container
-is in the works but we can use `juju run` and `juju status` to find
-our hello app.
-
-Exit out of our ssh session and run:
-
-```shell
-juju run --unit kubernetes/0 "docker ps -n=1"
-...
-juju run --unit kubernetes/1 "docker ps -n=1"
-CONTAINER IDIMAGE  COMMAND CREATED STATUS  PORTS   NAMES
-02beb61339d8quay.io/kelseyhightower/hello:latest   /hello  About an hour ago   Up About an hourk8s_hello....
-```
-
-We see "kubernetes/1" has our container, we can open port 80:
-
-```shell
-juju run --unit kubernetes/1 "open-port 80"
-juju expose kubernetes
-sudo apt-get install curl
-curl $(juju status --format=oneline kubernetes/1 | cut -d' ' -f3)
-```
-
-Finally delete the pod:
-
-```shell
-juju ssh kubernetes-master/0
-kubectl delete pods hello
-```
-
-## Scale out cluster
-
-We can add node units like so:
-
-```shell
-juju add-unit docker # creates unit docker/2, kubernetes/2, docker-flannel/2
-```
-
-## Launch the "k8petstore" example app
-
-The [k8petstore example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/k8petstore/) is available as a
-[juju action](https://jujucharms.com/docs/devel/actions).
-
-```shell
-juju action do kubernetes-master/0
-```
-
-> Note: this example includes curl statements to exercise the app, which
-> automatically generates "petstore" transactions written to redis, and allows
-> you to visualize the throughput in your browser.
-
-## Tear down cluster
-
-```shell
-./kube-down.sh
-```
-
-or destroy your current Juju environment (using the `juju env` command):
-
-```shell
-juju destroy-environment --force `juju env`
-```
-
-
-## More Info
-
-The Kubernetes charms and bundles can be found in the `kubernetes` project on
-github.com:
-
- - [Bundle Repository](http://releases.k8s.io/{{page.githubbranch}}/cluster/juju/bundles)
-   * [Kubernetes master charm](https://releases.k8s.io/{{page.githubbranch}}/cluster/juju/charms/trusty/kubernetes-master)
-   * [Kubernetes node charm](https://releases.k8s.io/{{page.githubbranch}}/cluster/juju/charms/trusty/kubernetes)
- - [More about Juju](https://jujucharms.com)
-
-
-### Cloud compatibility
-
-Juju runs natively against a variety of public cloud providers. Juju currently
-works with:
-
-- [Amazon Web Service](https://jujucharms.com/docs/stable/config-aws)
-- [Windows Azure](https://jujucharms.com/docs/stable/config-azure)
-- [DigitalOcean](https://jujucharms.com/docs/stable/config-digitalocean)
-- [Google Compute Engine](https://jujucharms.com/docs/stable/config-gce)
-- [HP Public Cloud](https://jujucharms.com/docs/stable/config-hpcloud)
-- [Joyent](https://jujucharms.com/docs/stable/config-joyent)
-- [LXC](https://jujucharms.com/docs/stable/config-LXC)
-- Any [OpenStack](https://jujucharms.com/docs/stable/config-openstack) deployment
-- [Vagrant](https://jujucharms.com/docs/stable/config-vagrant)
-- [Vmware vSphere](https://jujucharms.com/docs/stable/config-vmware)
-
-If you do not see your favorite cloud provider listed many clouds can be
-configured for [manual provisioning](https://jujucharms.com/docs/stable/config-manual).
-
-The Kubernetes bundle has been tested on GCE and AWS and found to work with
-version 1.0.0.
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/libvirt-coreos.md b/v1.2/docs/getting-started-guides/libvirt-coreos.md
deleted file mode 100644
index b52a6bc717..0000000000
--- a/v1.2/docs/getting-started-guides/libvirt-coreos.md
+++ /dev/null
@@ -1,293 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-### Highlights
-
-* Super-fast cluster boot-up (few seconds instead of several minutes for vagrant)
-* Reduced disk usage thanks to [COW](https://en.wikibooks.org/wiki/QEMU/Images#Copy_on_write)
-* Reduced memory footprint thanks to [KSM](https://www.kernel.org/doc/Documentation/vm/ksm.txt)
-
-### Warnings about `libvirt-coreos` use case
-
-The primary goal of the `libvirt-coreos` cluster provider is to deploy a multi-node Kubernetes cluster on local VMs as fast as possible and to be as light as possible in term of resources used.
-
-In order to achieve that goal, its deployment is very different from the 'standard production deployment'? method used on other providers. This was done on purpose in order to implement some optimizations made possible by the fact that we know that all VMs will be running on the same physical machine.
-
-The `libvirt-coreos` cluster provider doesn't aim at being production look-alike.
-
-Another difference is that no security is enforced on `libvirt-coreos` at all. For example,
-
-* Kube API server is reachable via a clear-text connection (no SSL);
-* Kube API server requires no credentials;
-* etcd access is not protected;
-* Kubernetes secrets are not protected as securely as they are on production environments;
-* etc.
-
-So, an k8s application developer should not validate its interaction with Kubernetes on `libvirt-coreos` because he might technically succeed in doing things that are prohibited on a production environment like:
-
-* un-authenticated access to Kube API server;
-* Access to Kubernetes private data structures inside etcd;
-* etc.
-
-On the other hand, `libvirt-coreos` might be useful for people investigating low level implementation of Kubernetes because debugging techniques like sniffing the network traffic or introspecting the etcd content are easier on `libvirt-coreos` than on a production deployment.
-
-### Prerequisites
-
-1. Install [dnsmasq](http://www.thekelleys.org.uk/dnsmasq/doc)
-2. Install [ebtables](http://ebtables.netfilter.org/)
-3. Install [qemu](http://wiki.qemu.org/Main_Page)
-4. Install [libvirt](http://libvirt.org/)
-5. Enable and start the libvirt daemon, e.g:
-   * ``systemctl enable libvirtd``
-   * ``systemctl start libvirtd``
-6. [Grant libvirt access to your user&sup1;](https://libvirt.org/aclpolkit)
-7. Check that your $HOME is accessible to the qemu user&sup2;
-
-#### &sup1; Depending on your distribution, libvirt access may be denied by default or may require a password at each access.
-
-You can test it with the following command:
-
-```shell
-virsh -c qemu:///system pool-list
-```
-
-If you have access error messages, please read https://libvirt.org/acl.html and https://libvirt.org/aclpolkit.html .
-
-In short, if your libvirt has been compiled with Polkit support (ex: Arch, Fedora 21), you can create `/etc/polkit-1/rules.d/50-org.libvirt.unix.manage.rules` as follows to grant full access to libvirt to `$USER`
-
-```shell
-sudo /bin/sh -c "cat - > /etc/polkit-1/rules.d/50-org.libvirt.unix.manage.rules" << EOF
-```
-
-```conf
-polkit.addRule(function(action, subject) {
-        if (action.id == "org.libvirt.unix.manage" &&
-            subject.user == "$USER") {
-                return polkit.Result.YES;
-                polkit.log("action=" + action);
-                polkit.log("subject=" + subject);
-        }
-});
-EOF
-```
-
-If your libvirt has not been compiled with Polkit (ex: Ubuntu 14.04.1 LTS), check the permissions on the libvirt unix socket:
-
-```shell
-$ ls -l /var/run/libvirt/libvirt-sock
-srwxrwx--- 1 root libvirtd 0 févr. 12 16:03 /var/run/libvirt/libvirt-sock
-
-$ usermod -a -G libvirtd $USER
-# $USER needs to logout/login to have the new group be taken into account
-```
-
-(Replace `$USER` with your login name)
-
-#### &sup2; Qemu will run with a specific user. It must have access to the VMs drives
-
-All the disk drive resources needed by the VM (CoreOS disk image, Kubernetes binaries, cloud-init files, etc.) are put inside `./cluster/libvirt-coreos/libvirt_storage_pool`.
-
-As we're using the `qemu:///system` instance of libvirt, qemu will run with a specific `user:group` distinct from your user. It is configured in `/etc/libvirt/qemu.conf`. That qemu user must have access to that libvirt storage pool.
-
-If your `$HOME` is world readable, everything is fine. If your $HOME is private, `cluster/kube-up.sh` will fail with an error message like:
-
-```shell
-error: Cannot access storage file '$HOME/.../kubernetes/cluster/libvirt-coreos/libvirt_storage_pool/kubernetes_master.img' (as uid:99, gid:78): Permission denied
-```
-
-In order to fix that issue, you have several possibilities:
-
-* set `POOL_PATH` inside `cluster/libvirt-coreos/config-default.sh` to a directory:
-  * backed by a filesystem with a lot of free disk space
-  * writable by your user;
-  * accessible by the qemu user.
-* Grant the qemu user access to the storage pool.
-
-On Arch:
-
-```shell
-setfacl -m g:kvm:--x ~
-```
-
-### Setup
-
-By default, the libvirt-coreos setup will create a single Kubernetes master and 3 Kubernetes nodes. Because the VM drives use Copy-on-Write and because of memory ballooning and KSM, there is a lot of resource over-allocation.
-
-To start your local cluster, open a shell and run:
-
-```shell
-cd kubernetes
-
-export KUBERNETES_PROVIDER=libvirt-coreos
-cluster/kube-up.sh
-```
-
-The `KUBERNETES_PROVIDER` environment variable tells all of the various cluster management scripts which variant to use.  If you forget to set this, the assumption is you are running on Google Compute Engine.
-
-The `NUM_MINIONS` environment variable may be set to specify the number of nodes to start. If it is not set, the number of nodes defaults to 3.
-
-The `KUBE_PUSH` environment variable may be set to specify which Kubernetes binaries must be deployed on the cluster. Its possible values are:
-
-* `release` (default if `KUBE_PUSH` is not set) will deploy the binaries of `_output/release-tars/kubernetes-server-'|.tar.gz`. This is built with `make release` or `make release-skip-tests`.
-* `local` will deploy the binaries of `_output/local/go/bin`. These are built with `make`.
-
-You can check that your machines are there and running with:
-
-```shell
-$ virsh -c qemu:///system list
- Id    Name                           State
-----------------------------------------------------
- 15    kubernetes_master              running
- 16    kubernetes_minion-01           running
- 17    kubernetes_minion-02           running
- 18    kubernetes_minion-03           running
-```
-
-You can check that the Kubernetes cluster is working with:
-
-```shell
-$ kubectl get nodes
-NAME                LABELS              STATUS
-192.168.10.2        <none>              Ready
-192.168.10.3        <none>              Ready
-192.168.10.4        <none>              Ready
-```
-
-The VMs are running [CoreOS](https://coreos.com/).
-Your ssh keys have already been pushed to the VM. (It looks for ~/.ssh/id_*.pub)
-The user to use to connect to the VM is `core`.
-The IP to connect to the master is 192.168.10.1.
-The IPs to connect to the nodes are 192.168.10.2 and onwards.
-
-Connect to `kubernetes_master`:
-
-```shell
-ssh core@192.168.10.1
-```
-
-Connect to `kubernetes_minion-01`:
-
-```shell
-ssh core@192.168.10.2
-```
-
-### Interacting with your Kubernetes cluster with the `kube-*` scripts.
-
-All of the following commands assume you have set `KUBERNETES_PROVIDER` appropriately:
-
-```shell
-export KUBERNETES_PROVIDER=libvirt-coreos
-```
-
-Bring up a libvirt-CoreOS cluster of 5 nodes
-
-```shell
-NUM_MINIONS=5 cluster/kube-up.sh
-```
-
-Destroy the libvirt-CoreOS cluster
-
-```shell
-cluster/kube-down.sh
-```
-
-Update the libvirt-CoreOS cluster with a new Kubernetes release produced by `make release` or `make release-skip-tests`:
-
-```shell
-cluster/kube-push.sh
-```
-
-Update the libvirt-CoreOS cluster with the locally built Kubernetes binaries produced by `make`:
-
-```shell
-KUBE_PUSH=local cluster/kube-push.sh
-```
-
-Interact with the cluster
-
-```shell
-kubectl ...
-```
-
-### Troubleshooting
-
-#### !!! Cannot find kubernetes-server-linux-amd64.tar.gz
-
-Build the release tarballs:
-
-```shell
-make release
-```
-
-#### Can't find virsh in PATH, please fix and retry.
-
-Install libvirt
-
-On Arch:
-
-```shell
-pacman -S qemu libvirt
-```
-
-On Ubuntu 14.04.1:
-
-```shell
-aptitude install qemu-system-x86 libvirt-bin
-```
-
-On Fedora 21:
-
-```shell
-yum install qemu libvirt
-```
-
-#### error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory
-
-Start the libvirt daemon
-
-On Arch:
-
-```shell
-systemctl start libvirtd
-```
-
-On Ubuntu 14.04.1:
-
-```shell
-service libvirt-bin start
-```
-
-#### error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
-
-Fix libvirt access permission (Remember to adapt `$USER`)
-
-On Arch and Fedora 21:
-
-```shell
-cat > /etc/polkit-1/rules.d/50-org.libvirt.unix.manage.rules <<EOF
-```
-
-```conf
-polkit.addRule(function(action, subject) {
-        if (action.id == "org.libvirt.unix.manage" &&
-            subject.user == "$USER") {
-                return polkit.Result.YES;
-                polkit.log("action=" + action);
-                polkit.log("subject=" + subject);
-        }
-});
-EOF
-```
-
-On Ubuntu:
-
-```shell
-usermod -a -G libvirtd $USER
-```
-
-#### error: Out of memory initializing network (virsh net-create...)
-
-Ensure libvirtd has been restarted since ebtables was installed.
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/logging-elasticsearch.md b/v1.2/docs/getting-started-guides/logging-elasticsearch.md
deleted file mode 100644
index 80af1d2975..0000000000
--- a/v1.2/docs/getting-started-guides/logging-elasticsearch.md
+++ /dev/null
@@ -1,243 +0,0 @@
----
----
-
-On the Google Compute Engine (GCE) platform the default cluster level logging support targets
-[Google Cloud Logging](https://cloud.google.com/logging/docs/) as described at the [Logging](/{{page.version}}/docs/getting-started-guides/logging) getting
-started page. Here we describe how to set up a cluster to ingest logs into Elasticsearch and view them using Kibana as an
-alternative to Google Cloud Logging.
-
-To use Elasticsearch and Kibana for cluster logging you should set the following environment variable as shown below:
-
-```shell
-KUBE_LOGGING_DESTINATION=elasticsearch
-```
-
-You should also ensure that `KUBE_ENABLE_NODE_LOGGING=true` (which is the default for the GCE platform).
-
-Now when you create a cluster a message will indicate that the Fluentd node-level log collectors
-will target Elasticsearch:
-
-```shell
-$ cluster/kube-up.sh
-...
-Project: kubernetes-satnam
-Zone: us-central1-b
-... calling kube-up
-Project: kubernetes-satnam
-Zone: us-central1-b
-+++ Staging server tars to Google Storage: gs://kubernetes-staging-e6d0e81793/devel
-+++ kubernetes-server-linux-amd64.tar.gz uploaded (sha1 = 6987c098277871b6d69623141276924ab687f89d)
-+++ kubernetes-salt.tar.gz uploaded (sha1 = bdfc83ed6b60fa9e3bff9004b542cfc643464cd0)
-Looking for already existing resources
-Starting master and configuring firewalls
-Created [https://www.googleapis.com/compute/v1/projects/kubernetes-satnam/zones/us-central1-b/disks/kubernetes-master-pd].
-NAME                 ZONE          SIZE_GB TYPE   STATUS
-kubernetes-master-pd us-central1-b 20      pd-ssd READY
-Created [https://www.googleapis.com/compute/v1/projects/kubernetes-satnam/regions/us-central1/addresses/kubernetes-master-ip].
-+++ Logging using Fluentd to elasticsearch
-```
-
-The node level Fluentd collector pods and the Elasticsearech pods used to ingest cluster logs and the pod for the Kibana
-viewer should be running in the kube-system namespace soon after the cluster comes to life.
-
-```shell
-$ kubectl get pods --namespace=kube-system
-NAME                                           READY     REASON    RESTARTS   AGE
-elasticsearch-logging-v1-78nog                 1/1       Running   0          2h
-elasticsearch-logging-v1-nj2nb                 1/1       Running   0          2h
-fluentd-elasticsearch-kubernetes-minion-5oq0   1/1       Running   0          2h
-fluentd-elasticsearch-kubernetes-minion-6896   1/1       Running   0          2h
-fluentd-elasticsearch-kubernetes-minion-l1ds   1/1       Running   0          2h
-fluentd-elasticsearch-kubernetes-minion-lz9j   1/1       Running   0          2h
-kibana-logging-v1-bhpo8                        1/1       Running   0          2h
-kube-dns-v3-7r1l9                              3/3       Running   0          2h
-monitoring-heapster-v4-yl332                   1/1       Running   1          2h
-monitoring-influx-grafana-v1-o79xf             2/2       Running   0          2h
-```
-
-Here we see that for a four node cluster there is a `fluent-elasticsearch` pod running which gathers
-the Docker container logs and sends them to Elasticsearch. The Fluentd collector communicates to
-a Kubernetes service that maps requests to specific Elasticsearch pods. Similarly, Kibana can also be
-accessed via a Kubernetes service definition.
-
-
-```shell
-$ kubectl get services --namespace=kube-system
-NAME                    LABELS                                                                                              SELECTOR                        IP(S)          PORT(S)
-elasticsearch-logging   k8s-app=elasticsearch-logging,kubernetes.io/cluster-service=true,kubernetes.io/name=Elasticsearch   k8s-app=elasticsearch-logging   10.0.222.57    9200/TCP
-kibana-logging          k8s-app=kibana-logging,kubernetes.io/cluster-service=true,kubernetes.io/name=Kibana                 k8s-app=kibana-logging          10.0.193.226   5601/TCP
-kube-dns                k8s-app=kube-dns,kubernetes.io/cluster-service=true,kubernetes.io/name=KubeDNS                      k8s-app=kube-dns                10.0.0.10      53/UDP
-                                                                                                                                                                           53/TCP
-kubernetes              component=apiserver,provider=kubernetes                                                             <none>                          10.0.0.1       443/TCP
-monitoring-grafana      kubernetes.io/cluster-service=true,kubernetes.io/name=Grafana                                       k8s-app=influxGrafana           10.0.167.139   80/TCP
-monitoring-heapster     kubernetes.io/cluster-service=true,kubernetes.io/name=Heapster                                      k8s-app=heapster                10.0.208.221   80/TCP
-monitoring-influxdb     kubernetes.io/cluster-service=true,kubernetes.io/name=InfluxDB                                      k8s-app=influxGrafana           10.0.188.57    8083/TCP
-```
-
-By default two Elasticsearch replicas are created and one Kibana replica is created.
-
-```shell
-$ kubectl get rc --namespace=kube-system
-CONTROLLER                     CONTAINER(S)            IMAGE(S)                                          SELECTOR                                   REPLICAS
-elasticsearch-logging-v1       elasticsearch-logging   gcr.io/google_containers/elasticsearch:1.4        k8s-app=elasticsearch-logging,version=v1   2
-kibana-logging-v1              kibana-logging          gcr.io/google_containers/kibana:1.3               k8s-app=kibana-logging,version=v1          1
-kube-dns-v3                    etcd                    gcr.io/google_containers/etcd:2.0.9               k8s-app=kube-dns,version=v3                1
-                               kube2sky                gcr.io/google_containers/kube2sky:1.9                                                        
-                               skydns                  gcr.io/google_containers/skydns:2015-03-11-001                                               
-monitoring-heapster-v4         heapster                gcr.io/google_containers/heapster:v0.14.3         k8s-app=heapster,version=v4                1
-monitoring-influx-grafana-v1   influxdb                gcr.io/google_containers/heapster_influxdb:v0.3   k8s-app=influxGrafana,version=v1           1
-                               grafana                 gcr.io/google_containers/heapster_grafana:v0.7                                         
-```
-
-The Elasticsearch and Kibana services are not directly exposed via a publicly reachable IP address. Instead,
-they can be accessed via the service proxy running at the master. The URLs for accessing Elasticsearch
-and Kibana via the service proxy can be found using the `kubectl cluster-info` command.
-
-```shell
-$ kubectl cluster-info
-Kubernetes master is running at https://146.148.94.154
-Elasticsearch is running at https://146.148.94.154/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging
-Kibana is running at https://146.148.94.154/api/v1/proxy/namespaces/kube-system/services/kibana-logging
-KubeDNS is running at https://146.148.94.154/api/v1/proxy/namespaces/kube-system/services/kube-dns
-KubeUI is running at https://146.148.94.154/api/v1/proxy/namespaces/kube-system/services/kube-ui
-Grafana is running at https://146.148.94.154/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
-Heapster is running at https://146.148.94.154/api/v1/proxy/namespaces/kube-system/services/monitoring-heapster
-InfluxDB is running at https://146.148.94.154/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb
-```
-
-Before accessing the logs ingested into Elasticsearch using a browser and the service proxy URL we need to find out
-the `admin` password for the cluster using `kubectl config view`.
-
-```shell
-$ kubectl config view
-...
-- name: kubernetes-satnam_kubernetes-basic-auth
-  user:
-    password: 7GlspJ9Q43OnGIJO
-    username: admin
-...
-```
-
-The first time you try to access the cluster from a browser a dialog box appears asking for the username and password.
-Use the username `admin` and provide the basic auth password reported by `kubectl config view` for the
-cluster you are trying to connect to. Connecting to the Elasticsearch URL should then give the
-status page for Elasticsearch.
-
-![Elasticsearch Status](/images/docs/es-browser.png)
-
-You can now type Elasticsearch queries directly into the browser. Alternatively you can query Elasticsearch
-from your local machine using `curl` but first you need to know what your bearer token is:
-
-```shell
-$ kubectl config view --minify
-```
-
-```conf
-apiVersion: v1
-clusters:
-- cluster:
-    certificate-authority-data: REDACTED
-    server: https://146.148.94.154
-  name: kubernetes-satnam_kubernetes
-contexts:
-- context:
-    cluster: kubernetes-satnam_kubernetes
-    user: kubernetes-satnam_kubernetes
-  name: kubernetes-satnam_kubernetes
-current-context: kubernetes-satnam_kubernetes
-kind: Config
-preferences: {}
-users:
-- name: kubernetes-satnam_kubernetes
-  user:
-    client-certificate-data: REDACTED
-    client-key-data: REDACTED
-    token: JsUe2Z3cXqa17UQqQ8qWGGf4nOSLwSnp
-```
-
-Now you can issue requests to Elasticsearch:
-
-```shell
-$ curl --header "Authorization: Bearer JsUe2Z3cXqa17UQqQ8qWGGf4nOSLwSnp" --insecure https://146.148.94.154/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging/
-```
-
-```json
-{
-  "status" : 200,
-  "name" : "Vance Astrovik",
-  "cluster_name" : "kubernetes-logging",
-  "version" : {
-    "number" : "1.5.2",
-    "build_hash" : "62ff9868b4c8a0c45860bebb259e21980778ab1c",
-    "build_timestamp" : "2015-04-27T09:21:06Z",
-    "build_snapshot" : false,
-    "lucene_version" : "4.10.4"
-  },
-  "tagline" : "You Know, for Search"
-}
-```
-
-Note that you need the trailing slash at the end of the service proxy URL. Here is an example of a search:
-
-```shell
-$ curl --header "Authorization: Bearer JsUe2Z3cXqa17UQqQ8qWGGf4nOSLwSnp" --insecure https://146.148.94.154/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging/_search?pretty=true
-```
-
-```json
-{
-  "took" : 7,
-  "timed_out" : false,
-  "_shards" : {
-    "total" : 6,
-    "successful" : 6,
-    "failed" : 0
-  },
-  "hits" : {
-    "total" : 123711,
-    "max_score" : 1.0,
-    "hits" : [ {
-      "_index" : ".kibana",
-      "_type" : "config",
-      "_id" : "4.0.2",
-      "_score" : 1.0,
-      "_source":{"buildNum":6004,"defaultIndex":"logstash-*"}
-    }, {
-...
-      "_index" : "logstash-2015.06.22",
-      "_type" : "fluentd",
-      "_id" : "AU4c_GvFZL5p_gZ8dxtx",
-      "_score" : 1.0,
-      "_source":{"log":"synthetic-logger-10lps-pod: 31: 2015-06-22 20:35:33.597918073+00:00\n","stream":"stdout","tag":"kubernetes.synthetic-logger-10lps-pod_default_synth-lgr","@timestamp":"2015-06-22T20:35:33+00:00"}
-    }, {
-      "_index" : "logstash-2015.06.22",
-      "_type" : "fluentd",
-      "_id" : "AU4c_GvFZL5p_gZ8dxt2",
-      "_score" : 1.0,
-      "_source":{"log":"synthetic-logger-10lps-pod: 36: 2015-06-22 20:35:34.108780133+00:00\n","stream":"stdout","tag":"kubernetes.synthetic-logger-10lps-pod_default_synth-lgr","@timestamp":"2015-06-22T20:35:34+00:00"}
-    } ]
-  }
-}
-```
-
-The Elasticsearch website contains information about [URI search queries](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-uri-request) which can be used to extract the required logs.
-
-Alternatively you can view the ingested logs using Kibana. The first time you visit the Kibana URL you will be
-presented with a page that asks you to configure your view of the ingested logs. Select the option for
-timeseries values and select `@timestamp`. On the following page select the `Discover` tab and then you
-should be able to see the ingested logs. You can set the refresh interval to 5 seconds to have the logs
-regulary refreshed. Here is a typical view of ingested logs from the Kibana viewer.
-
-![Kibana logs](/images/docs/kibana-logs.png)
-
-Another way to access Elasticsearch and Kibana in the cluster is to use `kubectl proxy` which will serve
-a local proxy to the remote master:
-
-```shell
-$ kubectl proxy
-Starting to serve on localhost:8001
-```
-
-Now you can visit the URL [http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging](http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/elasticsearch-logging) to contact Elasticsearch and [http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kibana-logging](http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kibana-logging) to access the Kibana viewer.
-
-
-
diff --git a/v1.2/docs/getting-started-guides/logging.md b/v1.2/docs/getting-started-guides/logging.md
deleted file mode 100644
index ecebe877ac..0000000000
--- a/v1.2/docs/getting-started-guides/logging.md
+++ /dev/null
@@ -1,218 +0,0 @@
----
----
-
-A Kubernetes cluster will typically be humming along running many system and application pods. How does the system administrator collect, manage and query the logs of the system pods? How does a user query the logs of their application which is composed of many pods which may be restarted or automatically generated by the Kubernetes system? These questions are addressed by the Kubernetes **cluster level logging** services.
-
-Cluster level logging for Kubernetes allows us to collect logs which persist beyond the lifetime of the pod's container images or the lifetime of the pod or even cluster. In this article we assume that a Kubernetes cluster has been created with cluster level logging support for sending logs to Google Cloud Logging. After a cluster has been created you will have a collection of system pods running in the `kube-system` namespace that support monitoring,
-logging and DNS resolution for names of Kubernetes services:
-
-```shell
-$ kubectl get pods --namespace=kube-system
-NAME                                           READY     REASON    RESTARTS   AGE
-fluentd-cloud-logging-kubernetes-minion-0f64   1/1       Running   0          32m
-fluentd-cloud-logging-kubernetes-minion-27gf   1/1       Running   0          32m
-fluentd-cloud-logging-kubernetes-minion-pk22   1/1       Running   0          31m
-fluentd-cloud-logging-kubernetes-minion-20ej   1/1       Running   0          31m
-kube-dns-v3-pk22                               3/3       Running   0          32m
-monitoring-heapster-v1-20ej                    0/1       Running   9          32m
-```
-
-Here is the same information in a picture which shows how the pods might be placed on specific nodes.
-
-![Cluster](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/blog-logging/diagrams/cloud-logging.png)
-
-This diagram shows four nodes created on a Google Compute Engine cluster with the name of each VM node on a purple background. The internal and public IPs of each node are shown on gray boxes and the pods running in each node are shown in green boxes. Each pod box shows the name of the pod and the namespace it runs in, the IP address of the pod and the images which are run as part of the pod's execution. Here we see that every node is running a fluentd-cloud-logging pod which is collecting the log output of the containers running on the same node and sending them to Google Cloud Logging. A pod which provides the
-[cluster DNS service](/{{page.version}}/docs/admin/dns) runs on one of the nodes and a pod which provides monitoring support runs on another node.
-
-To help explain how cluster level logging works let's start off with a synthetic log generator pod specification [counter-pod.yaml](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/blog-logging/counter-pod.yaml):
-
-<!-- BEGIN MUNGE: EXAMPLE ../../examples/blog-logging/counter-pod.yaml -->
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: counter
-spec:
-  containers:
-  - name: count
-    image: ubuntu:14.04
-    args: [bash, -c, 
-           'for ((i = 0; ; i++)); do echo "$i: $(date)"; sleep 1; done']
-```
-
-[Download example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/blog-logging/counter-pod.yaml)
-<!-- END MUNGE: EXAMPLE ../../examples/blog-logging/counter-pod.yaml -->
-
-This pod specification has one container which runs a bash script when the container is born. This script simply writes out the value of a counter and the date once per second and runs indefinitely. Let's create the pod in the default
-namespace.
-
-```shell
-$ kubectl create -f examples/blog-logging/counter-pod.yaml
- pods/counter
-```
-
-We can observe the running pod:
-
-```shell
-$ kubectl get pods
-NAME                                           READY     STATUS    RESTARTS   AGE
-counter                                        1/1       Running   0          5m
-```
-
-This step may take a few minutes to download the ubuntu:14.04 image during which the pod status will be shown as `Pending`.
-
-One of the nodes is now running the counter pod:
-
-![Counter Pod](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/blog-logging/diagrams/27gf-counter.png)
-
-When the pod status changes to `Running` we can use the kubectl logs command to view the output of this counter pod.
-
-```shell
-$ kubectl logs counter
-0: Tue Jun  2 21:37:31 UTC 2015
-1: Tue Jun  2 21:37:32 UTC 2015
-2: Tue Jun  2 21:37:33 UTC 2015
-3: Tue Jun  2 21:37:34 UTC 2015
-4: Tue Jun  2 21:37:35 UTC 2015
-5: Tue Jun  2 21:37:36 UTC 2015
-...
-```
-
-This command fetches the log text from the Docker log file for the image that is running in this container. We can connect to the running container and observe the running counter bash script.
-
-```shell
-$ kubectl exec -i counter bash
-ps aux
-USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
-root         1  0.0  0.0  17976  2888 ?        Ss   00:02   0:00 bash -c for ((i = 0; ; i++)); do echo "$i: $(date)"; sleep 1; done
-root       468  0.0  0.0  17968  2904 ?        Ss   00:05   0:00 bash
-root       479  0.0  0.0   4348   812 ?        S    00:05   0:00 sleep 1
-root       480  0.0  0.0  15572  2212 ?        R    00:05   0:00 ps aux
-```
-
-What happens if for any reason the image in this pod is killed off and then restarted by Kubernetes? Will we still see the log lines from the previous invocation of the container followed by the log lines for the started container? Or will we lose the log lines from the original container's execution and only see the log lines for the new container? Let's find out. First let's stop the currently running counter.
-
-```shell
-$ kubectl stop pod counter
-pods/counter
-```
-
-Now let's restart the counter.
-
-```shell
-$ kubectl create -f examples/blog-logging/counter-pod.yaml
-pods/counter
-```
-
-Let's wait for the container to restart and get the log lines again.
-
-```shell
-$ kubectl logs counter
-0: Tue Jun  2 21:51:40 UTC 2015
-1: Tue Jun  2 21:51:41 UTC 2015
-2: Tue Jun  2 21:51:42 UTC 2015
-3: Tue Jun  2 21:51:43 UTC 2015
-4: Tue Jun  2 21:51:44 UTC 2015
-5: Tue Jun  2 21:51:45 UTC 2015
-6: Tue Jun  2 21:51:46 UTC 2015
-7: Tue Jun  2 21:51:47 UTC 2015
-8: Tue Jun  2 21:51:48 UTC 2015
-```
-
-We've lost the log lines from the first invocation of the container in this pod! Ideally, we want to preserve all the log lines from each invocation of each container in the pod. Furthermore, even if the pod is restarted we would still like to preserve all the log lines that were ever emitted by the containers in the pod. But don't fear, this is the functionality provided by cluster level logging in Kubernetes. When a cluster is created, the standard output and standard error output of each container can be ingested using a [Fluentd](http://www.fluentd.org/) agent running on each node into either [Google Cloud Logging](https://cloud.google.com/logging/docs/) or into Elasticsearch and viewed with Kibana.
-
-When a Kubernetes cluster is created with logging to Google Cloud Logging enabled, the system creates a pod called `fluentd-cloud-logging` on each node of the cluster to collect Docker container logs. These pods were shown at the start of this blog article in the response to the first get pods command.
-
-This log collection pod has a specification which looks something like this:
-
-<!-- BEGIN MUNGE: EXAMPLE ../../cluster/saltbase/salt/fluentd-gcp/fluentd-gcp.yaml -->
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: fluentd-cloud-logging
-  namespace: kube-system
-spec:
-  containers:
-  - name: fluentd-cloud-logging
-    image: gcr.io/google_containers/fluentd-gcp:1.14
-    resources:
-      limits:
-        cpu: 100m
-        memory: 200Mi
-    env:
-    - name: FLUENTD_ARGS
-      value: -q
-    volumeMounts:
-    - name: varlog
-      mountPath: /var/log
-    - name: varlibdockercontainers
-      mountPath: /var/lib/docker/containers
-      readOnly: true
-  terminationGracePeriodSeconds: 30
-  volumes:
-  - name: varlog
-    hostPath:
-      path: /var/log
-  - name: varlibdockercontainers
-    hostPath:
-      path: /var/lib/docker/containers
-```
-
-[Download example](https://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/salt/fluentd-gcp/fluentd-gcp.yaml)
-<!-- END MUNGE: EXAMPLE ../../cluster/saltbase/salt/fluentd-gcp/fluentd-gcp.yaml -->
-
-This pod specification maps the directory on the host containing the Docker log files, `/var/lib/docker/containers`, to a directory inside the container which has the same path. The pod runs one image, `gcr.io/google_containers/fluentd-gcp:1.6`, which is configured to collect the Docker log files from the logs directory and ingest them into Google Cloud Logging. One instance of this pod runs on each node of the cluster. Kubernetes will notice if this pod fails and automatically restart it.
-
-We can click on the Logs item under the Monitoring section of the Google Developer Console and select the logs for the counter container, which will be called kubernetes.counter_default_count.  This identifies the name of the pod (counter), the namespace (default) and the name of the container (count) for which the log collection occurred. Using this name we can select just the logs for our counter container from the drop down menu:
-
-![Cloud Logging Console](/images/docs/cloud-logging-console.png)
-
-When we view the logs in the Developer Console we observe the logs for both invocations of the container.
-
-![Both Logs](/images/docs/all-lines.png)
-
-Note the first container counted to 108 and then it was terminated. When the next container image restarted the counting process resumed from 0. Similarly if we deleted the pod and restarted it we would capture the logs for all instances of the containers in the pod whenever the pod was running.
-
- Logs ingested into Google Cloud Logging may be exported to various other destinations including [Google Cloud Storage](https://cloud.google.com/storage/) buckets and [BigQuery](https://cloud.google.com/bigquery/). Use the Exports tab in the Cloud Logging console to specify where logs should be streamed to. You can also follow this link to the
- [settings tab](https://pantheon.corp.google.com/project/_/logs/settings).
-
- We could query the ingested logs from BigQuery using the SQL query which reports the counter log lines showing the newest lines first:
-
-```shell
-SELECT metadata.timestamp, structPayload.log
- FROM [mylogs.kubernetes_counter_default_count_20150611] 
- ORDER BY metadata.timestamp DESC
-```
-
-Here is some sample output:
-
-![BigQuery](/images/docs/bigquery-logging.png)
-
-We could also fetch the logs from Google Cloud Storage buckets to our desktop or laptop and then search them locally. The following command fetches logs for the counter pod running in a cluster which is itself in a Compute Engine project called `myproject`. Only logs for the date 2015-06-11 are fetched.
-
-
-```shell
-$ gsutil -m cp -r gs://myproject/kubernetes.counter_default_count/2015/06/11 .
-```
-
-Now we can run queries over the ingested logs. The example below uses the [jq](http://stedolan.github.io/jq/) program to extract just the log lines.
-
-```shell
-$ cat 21\:00\:00_21\:59\:59_S0.json | jq '.structPayload.log'
-"0: Thu Jun 11 21:39:38 UTC 2015\n"
-"1: Thu Jun 11 21:39:39 UTC 2015\n"
-"2: Thu Jun 11 21:39:40 UTC 2015\n"
-"3: Thu Jun 11 21:39:41 UTC 2015\n"
-"4: Thu Jun 11 21:39:42 UTC 2015\n"
-"5: Thu Jun 11 21:39:43 UTC 2015\n"
-"6: Thu Jun 11 21:39:44 UTC 2015\n"
-"7: Thu Jun 11 21:39:45 UTC 2015\n"
-...
-```
-
-This page has touched briefly on the underlying mechanisms that support gathering cluster level logs on a Kubernetes deployment. The approach here only works for gathering the standard output and standard error output of the processes running in the pod's containers. To gather other logs that are stored in files one can use a sidecar container to gather the required files as described at the page [Collecting log files within containers with Fluentd](http://releases.k8s.io/{{page.githubbranch}}/contrib/logging/fluentd-sidecar-gcp/README.md) and sending them to the Google Cloud Logging service.
-
-Some of the material in this section also appears in the blog article [Cluster Level Logging with Kubernetes](http://blog.kubernetes.io/2015/06/cluster-level-logging-with-kubernetes)
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/meanstack.md b/v1.2/docs/getting-started-guides/meanstack.md
deleted file mode 100644
index 57a7ba39a1..0000000000
--- a/v1.2/docs/getting-started-guides/meanstack.md
+++ /dev/null
@@ -1,444 +0,0 @@
----
----
-
-**By: Sandeep Dinesh** - _July 29, 2015_
-
-![image](/images/docs/meanstack/image_0.png)
-
-In [a recent post](http://blog.sandeepdinesh.com/2015/07/running-mean-web-application-in-docker.html), I talked about running a MEAN stack with [Docker Containers.](http://docker.com/)
-
-Manually deploying Containers is all fine and dandy, but is rather fragile and clumsy. What happens if the app crashes? How can the app be updated? Rolled back?
-
-Thankfully, there is a system we can use to manage our containers in a cluster environment called Kubernetes. Even better, Google has a managed version of Kubernetes called [Google Container Engine](https://cloud.google.com/container-engine/) so you can get up and running in minutes.
-
-* TOC
-{:toc}
-
-## The Basics of Using Kubernetes
-
-Before we jump in and start kube’ing it up, it’s important to understand some of the fundamentals of Kubernetes.
-
-* Containers: These are the Docker, rtk, AppC, or whatever Container you are running. You can think of these like subatomic particles; everything is made up of them, but you rarely (if ever) interact with them directly.
-* Pods: Pods are the basic component of Kubernetes. They are a group of Containers that are scheduled, live, and die together. Why would you want to have a group of containers instead of just a single container? Let’s say you had a log processor, a web server, and a database. If you couldn't use Pods, you would have to bundle the log processor in the web server and database containers, and each time you updated one you would have to update the other. With Pods, you can just reuse the same log processor for both the web server and database.
-* Replication Controllers: This is the management component of Kubernetes, and it’s pretty cool. You give it a set of Pods, tell it "I want three copies of this," and it creates those copies on your cluster. It will do its best to keep those copies always running, so if one crashes it will start another.
-* Services: This is the other side to Replication Controllers. A service is the single point of contact for a group of Pods. For example, let’s say you have a Replication Controller that creates four copies of a web server pod. A Service will split the traffic to each of the four copies. Services are "permanent" while the pods behind them can come and go, so it’s a good idea to use Services.
-
-
-## Step 1: Creating the Container
-
-In my previous post, I used off-the-shelf containers to keep things simple.
-
-I had a stock MongoDB container and a stock Node.js container. The Mongo container ran fine without any modification. However, I had to manually enter the Node container to pull and run the code. Obviously this isn't ideal in Kubernetes land, as you aren't supposed to log into your servers!
-
-Instead, you have to build a custom container that has the code already inside it and runs automatically.
-
-To do this, you need to use more Docker. Make sure you have the latest version installed for the rest of this tutorial.
-
-Getting the code:
-
-Before starting, let’s get some code to run. You can follow along on your personal machine or a Linux VM in the cloud. I recommend using Linux or a Linux VM; running Docker on Mac and Windows is outside the scope of this tutorial.
-
-```shell
-$ git clone https://github.com/ijason/NodeJS-Sample-App.git app
-$ mv app/EmployeeDB/* app/
-$ sed -i -- 's/localhost/mongo/g' ./app/app.js
-```
-
-This is the same sample app we ran before. The second line just moves everything from the `EmployeeDB` subfolder up into the app folder so it’s easier to access. The third line, once again, replaces the hardcoded `localhost` with the `mongo` proxy.
-
-Building the Docker image:
-
-First, you need a `Dockerfile`. This is basically the list of instructions Docker uses to build a container image.
-
-Here is the `Dockerfile` for the web server:
-
-```shell
-FROM node:0.10.40
-
-RUN mkdir -p /usr/src/app
-WORKDIR /usr/src/app
-COPY ./app/ ./
-RUN npm install
-
-CMD ["node", "app.js"]
-```
-
-A `Dockerfile` is pretty self explanatory, and this one is dead simple.
-
-First, it uses the official Node.js image as the base image.
-
-Then, it creates a folder to store the code, `cd`s into that directory, copies the code in, and installs the dependencies with npm.
-
-Finally, it specifies the command Docker should run when the container starts, which is to start the app.
-
-
-## Step 2: Building our Container
-
-Right now, the directory should look like this:
-
-```shell
-$ ls
-
-Dockerfile app
-```
-
-Let’s build.
-
-```shell
-$ docker build -t myapp .
-```
-
-This will build a new Docker image for your app. This might take a few minutes as it is downloading and building everything.
-
-After that is done, test it out:
-
-```shell
-$ docker run myapp
-```
-
-At this point, you should have a server running on `http://localhost:3000` (or wherever Docker tells you). The website will error out as there is no database running, but we know it works!
-
-![image](/images/docs/meanstack/image_1.png)
-
-
-## Step 3: Pushing our Container
-
-Now you have a custom Docker image, you have to actually access it from the cloud.
-
-As we are going to be using the image with Google Container Engine, the best place to push the image is the [Google Container Registry](https://cloud.google.com/tools/container-registry/). The Container Registry is built on top of [Google Cloud Storage](https://cloud.google.com/storage/), so you get the advantage of scalable storage and very fast access from Container Engine.
-
-First, make sure you have the latest version of the [Google Cloud SDK installed](https://cloud.google.com/sdk/).
-
-[Windows users click here.](https://dl.google.com/dl/cloudsdk/release/GoogleCloudSDKInstaller.exe)
-
-For Linux/Mac:
-
-```shell
-$ curl https://sdk.cloud.google.com | bash
-```
-
-Then, make sure you log in and update.
-
-```shell
-$ gcloud auth login
-$ gcloud components update
-```
-
-You're ready to push your container live, but you'll need a destination. Create a Project in [the Google Cloud Platform Console](https://console.developers.google.com/), and leave it blank. Use the Project ID below, and push your project live.
-
-```shell
-$ docker tag myapp gcr.io/<YOUR-PROJECT-ID>/myapp
-$ gcloud docker push gcr.io/<YOUR-PROJECT-ID>/myapp
-```
-
-After some time, it will finish. You can check the console to see the container has been pushed up.
-
-![image](/images/docs/meanstack/image_2.png)
-
-
-## **Step 4: Creating the Cluster**
-
-So now you have the custom container, let’s create a cluster to run it.
-
-Currently, a cluster can be as small as one machine to as big as 100 machines. You can pick any machine type you want, so you can have a cluster of a single `f1-micro` instance, 100 `n1-standard-32` instances (3,200 cores!), and anything in between.
-
-For this tutorial I'm going to use the following:
-
-* Create a cluster named `mean-cluster`
-* Give it a size of 2 nodes
-* Machine type will be `n1-standard-1`
-* Zone will be `us-central-1f` (Use a zone close to you)
-
-There are two ways to create this cluster. Take your pick.
-
-**Command Line:**
-
-```shell
-$ gcloud beta container \
- --project "<YOUR-PROJECT-ID>" \
- clusters create "mean-cluster" \
- --zone "us-central1-f" \
- --machine-type "n1-standard-1" \
- --num-nodes "2" \
- --network "default"
-```
-
-**GUI:**
-
-![image](/images/docs/meanstack/image_3.png)
-
-After a few minutes, you should see this in the console.
-
-![image](/images/docs/meanstack/image_4.png)
-
-
-## **Step 5: Creating the Database Service**
-
-Three things need to be created:
-
-1. Persistent Disk to store the data (pods are ephemeral, so we shouldn't save data locally)
-2. Replication Controller running MongoDB
-3. Service mapping to that Replication Controller
-
-To create the disk, run this:
-
-```shell
-$ gcloud compute disks create \
- --project "<YOUR-PROJECT-ID>" \
- --zone "us-central1-f" \
- --size 200GB \
- mongo-disk
-```
-
-Pick the same zone as your cluster and an appropriate disk size for your application.
-
-Now, we need to create a Replication Controller that will run the database. I’m using a Replication Controller and not a Pod, because if a standalone Pod dies, it won't restart automatically.
-
-### `db-controller.yml`
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
- labels:
-   name: mongo
- name: mongo-controller
-spec:
- replicas: 1
- template:
-   metadata:
-     labels:
-       name: mongo
-   spec:
-     containers:
-     - image: mongo
-       name: mongo
-       ports:
-       - name: mongo
-         containerPort: 27017
-         hostPort: 27017
-       volumeMounts:
-           - name: mongo-persistent-storage
-             mountPath: /data/db
-     volumes:
-       - name: mongo-persistent-storage
-         gcePersistentDisk:
-           pdName: mongo-disk
-           fsType: ext4
-```
-
-We call the controller `mongo-controller`, specify one replica, and open the appropriate ports. The image is `mongo`, which is the off the shelf MongoDB image.
-
-The `volumes` section creates the volume for Kubernetes to use. There is a Google Container Engine-specific `gcePersistentDisk` section that maps the disk we made into a Kubernetes volume, and we mount the volume into the `/data/db` directory (as described in the MongoDB Docker documentation)
-
-Now we have the Controller, let’s create the Service:
-
-### `db-service.yml`
-
-```yaml
-apiVersion: v1
-kind: Service
-metadata:
- labels:
-   name: mongo
- name: mongo
-spec:
- ports:
-   - port: 27017
-     targetPort: 27017
- selector:
-   name: mongo
-```
-
-Again, pretty simple stuff. We "select" the mongo Controller to be served, open up the ports, and call the service `mongo`.
-
-This is just like the "link" command line option we used with Docker in my previous post. Instead of connecting to `localhost`, we connect to `mongo`, and Kubernetes redirects traffic to the mongo service!
-
-At this point, the local directory looks like this:
-
-```shell
-$ ls
-
-Dockerfile
-app
-db-controller.yml
-db-service.yml
-```
-
-## Step 6: Running the Database
-
-First, let’s "log in" to the cluster
-
-```shell
-$ gcloud container clusters get-credentials mean-cluster
-```
-
-Now create the controller.
-
-```shell
-$ kubectl create -f db-controller.yml
-```
-
-And the Service.
-
-```shell
-$ kubectl create -f db-service.yml
-```
-
-`kubectl` is the Kubernetes command line tool (automatically installed with the Google Cloud SDK). We are just creating the resources specified in the files.
-
-At this point, the database is spinning up! You can check progress with the following command:
-
-```shell
-$ kubectl get pods
-```
-
-Once you see the mongo pod in running status, we are good to go!
-
-```shell
-$ kubectl get pods
-
-NAME                    READY  REASON   RESTARTS AGE
-mongo-controller-xxxx   1/1    Running  0        3m
-```
-
-
-## Step 7: Creating the Web Server
-
-Now the database is running, let’s start the web server.
-
-We need two things:
-
-1. Replication Controller to spin up and down web server pods
-2. Service to expose our website to the interwebs
-
-Let’s look at the Replication Controller configuration:
-
-### `web-controller.yml`
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
- labels:
-   name: web
- name: web-controller
-spec:
- replicas: 2
- template:
-   metadata:
-     labels:
-       name: web
-   spec:
-     containers:
-     - image: gcr.io/<YOUR-PROJECT-ID>/myapp
-       name: web
-       ports:
-       - containerPort: 3000
-         name: http-server
-```
-
-Here, we create a controller called `web-controller`, and we tell it to create two replicas. Replicas of what you ask? You may notice the `template` section looks just like a Pod configuration, and that's because it is. We are creating a Pod with our custom Node.js container and exposing port 3000.
-
-
-Now for the Service
-
-### `web-service.yml`
-
-```yaml
-apiVersion: v1
-kind: Service
-metadata:
- name: web
- labels:
-   name: web
-spec:
- type: LoadBalancer
- ports:
-   - port: 80
-     targetPort: 3000
-     protocol: TCP
- selector:
-   name: web
-```
-
-Notice two things here:
-
-1. The type is *LoadBalancer*. This is a cool feature that will make Google Cloud Platform create an external network load balancer automatically for this service!
-2. We map external port 80 to the internal port 3000, so we can serve HTTP traffic without messing with Firewalls.
-
-At this point, the local directory looks like this
-
-```shell
-$ ls
-
-Dockerfile app db-pod.yml db-service.yml web-service.yml web-controller.yml
-```
-
-
-## Step 8: Running the Web Server
-
-Create the Controller.
-
-```shell
-$ kubectl create -f web-controller.yml
-```
-
-And the Service.
-
-```shell
-$ kubectl create -f web-service.yml
-```
-
-And check the status.
-
-```shell
-$ kubectl get pods
-```
-
-Once you see the web pods in running status, we are good to go!
-
-```shell
-$ kubectl get pods
-
-NAME                   READY     REASON    RESTARTS   AGE
-mongo-controller-xxxx  1/1       Running   0          4m
-web-controller-xxxx    1/1       Running   0          1m
-web-controller-xxxx    1/1       Running   0          1m
-```
-
-
-## Step 9: Accessing the App
-
-At this point, everything is up and running. The architecture looks something like this:
-
-![image](/images/docs/meanstack/image_5.png)
-
-By default, port 80 should be open on the load balancer. In order to find the IP address of our app, run this command:
-
-```shell
-$ gcloud compute forwarding-rules list
-
-NAME     REGION        IP_ADDRESS       IP_PROTOCOL TARGET
-abcdef   us-central1   104.197.XXX.XXX  TCP         us-xxxx
-```
-
-If you go to the IP address listed, you should see the app up and running!
-
-![image](/images/docs/meanstack/image_6.png)
-
-And the Database works!
-
-![image](/images/docs/meanstack/image_7.png)
-
-
-#### **Final Thoughts**
-
-By using Container Engine and Kubernetes, we have a very robust, container based MEAN stack running in production.
-
-[In anoter post](https://medium.com/google-cloud/mongodb-replica-sets-with-kubernetes-d96606bd9474#.e93x7kuq5), I cover how to setup a MongoDB replica set. This is very important for running in production.
-
-Hopefully I can do some more posts about advanced Kubernetes topics such as changing the cluster size and number of Node.js web server replicas, using different environments (dev, staging, prod) on the same cluster, and doing rolling updates.
-
-Thanks to [Mark Mandel](https://medium.com/@markmandel), [Aja Hammerly](https://medium.com/@thagomizer), and [Jack Wilber](https://medium.com/@jack.g.wilber). [Some rights reserved](http://creativecommons.org/licenses/by/4.0/) by the author.
-
diff --git a/v1.2/docs/getting-started-guides/mesos.md b/v1.2/docs/getting-started-guides/mesos.md
deleted file mode 100644
index 2b4068ad80..0000000000
--- a/v1.2/docs/getting-started-guides/mesos.md
+++ /dev/null
@@ -1,335 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## About Kubernetes on Mesos
-
-<!-- TODO: Update, clean up. -->
-
-Mesos allows dynamic sharing of cluster resources between Kubernetes and other first-class Mesos frameworks such as [Hadoop][1], [Spark][2], and [Chronos][3].
-Mesos also ensures applications from different frameworks running on your cluster are isolated and that resources are allocated fairly among them.
-
-Mesos clusters can be deployed on nearly every IaaS cloud provider infrastructure or in your own physical datacenter. Kubernetes on Mesos runs on-top of that and therefore allows you to easily move Kubernetes workloads from one of these environments to the other.
-
-This tutorial will walk you through setting up Kubernetes on a Mesos cluster.
-It provides a step by step walk through of adding Kubernetes to a Mesos cluster and starting your first pod with an nginx webserver.
-
-**NOTE:** There are [known issues with the current implementation][7] and support for centralized logging and monitoring is not yet available.
-Please [file an issue against the kubernetes-mesos project][8] if you have problems completing the steps below.
-
-Further information is available in the Kubernetes on Mesos [contrib directory][13].
-
-### Prerequisites
-
-- Understanding of [Apache Mesos][6]
-- A running [Mesos cluster on Google Compute Engine][5]
-- A [VPN connection][10] to the cluster
-- A machine in the cluster which should become the Kubernetes *master node* with:
-  - GoLang > 1.2
-  - make (i.e. build-essential)
-  - Docker
-
-**Note**: You *can*, but you *don't have to* deploy Kubernetes-Mesos on the same machine the Mesos master is running on.
-
-### Deploy Kubernetes-Mesos
-
-Log into the future Kubernetes *master node* over SSH, replacing the placeholder below with the correct IP address.
-
-```shell
-ssh jclouds@${ip_address_of_master_node}
-```
-
-Build Kubernetes-Mesos.
-
-```shell
-git clone https://github.com/kubernetes/kubernetes
-cd kubernetes
-export KUBERNETES_CONTRIB=mesos
-make
-```
-
-Set some environment variables.
-The internal IP address of the master may be obtained via `hostname -i`.
-
-```shell
-export KUBERNETES_MASTER_IP=$(hostname -i)
-export KUBERNETES_MASTER=http://${KUBERNETES_MASTER_IP}:8888
-```
-
-Note that KUBERNETES_MASTER is used as the api endpoint. If you have existing `~/.kube/config` and point to another endpoint, you need to add option `--server=${KUBERNETES_MASTER}` to kubectl in later steps.
-
-### Deploy etcd
-
-Start etcd and verify that it is running:
-
-```shell
-sudo docker run -d --hostname $(uname -n) --name etcd \
-  -p 4001:4001 -p 7001:7001 quay.io/coreos/etcd:v2.0.12 \
-  --listen-client-urls http://0.0.0.0:4001 \
-  --advertise-client-urls http://${KUBERNETES_MASTER_IP}:4001
-```
-
-```shell
-$ sudo docker ps
-CONTAINER ID   IMAGE                        COMMAND   CREATED   STATUS   PORTS                NAMES
-fd7bac9e2301   quay.io/coreos/etcd:v2.0.12  "/etcd"   5s ago    Up 3s    2379/tcp, 2380/...   etcd
-```
-
-It's also a good idea to ensure your etcd instance is reachable by testing it
-
-```shell
-curl -L http://${KUBERNETES_MASTER_IP}:4001/v2/keys/
-```
-
-If connectivity is OK, you will see an output of the available keys in etcd (if any).
-
-### Start Kubernetes-Mesos Services
-
-Update your PATH to more easily run the Kubernetes-Mesos binaries:
-
-```shell
-export PATH="$(pwd)/_output/local/go/bin:$PATH"
-```
-
-Identify your Mesos master: depending on your Mesos installation this is either a `host:port` like `mesos-master:5050` or a ZooKeeper URL like `zk://zookeeper:2181/mesos`.
-In order to let Kubernetes survive Mesos master changes, the ZooKeeper URL is recommended for production environments.
-
-```shell
-export MESOS_MASTER=<host:port or zk:// url>
-```
-
-Create a cloud config file `mesos-cloud.conf` in the current directory with the following contents:
-
-```shell
-$ cat <<EOF >mesos-cloud.conf
-[mesos-cloud]
-        mesos-master        = ${MESOS_MASTER}
-EOF
-```
-
-Now start the kubernetes-mesos API server, controller manager, and scheduler on the master node:
-
-```shell
-$ km apiserver \
-  --address=${KUBERNETES_MASTER_IP} \
-  --etcd-servers=http://${KUBERNETES_MASTER_IP}:4001 \
-  --service-cluster-ip-range=10.10.10.0/24 \
-  --port=8888 \
-  --cloud-provider=mesos \
-  --cloud-config=mesos-cloud.conf \
-  --secure-port=0 \
-  --v=1 >apiserver.log 2>&1 &
-
-$ km controller-manager \
-  --master=${KUBERNETES_MASTER_IP}:8888 \
-  --cloud-provider=mesos \
-  --cloud-config=./mesos-cloud.conf  \
-  --v=1 >controller.log 2>&1 &
-
-$ km scheduler \
-  --address=${KUBERNETES_MASTER_IP} \
-  --mesos-master=${MESOS_MASTER} \
-  --etcd-servers=http://${KUBERNETES_MASTER_IP}:4001 \
-  --mesos-user=root \
-  --api-servers=${KUBERNETES_MASTER_IP}:8888 \
-  --cluster-dns=10.10.10.10 \
-  --cluster-domain=cluster.local \
-  --v=2 >scheduler.log 2>&1 &
-```
-
-Disown your background jobs so that they'll stay running if you log out.
-
-```shell
-disown -a
-```
-
-#### Validate KM Services
-
-Add the appropriate binary folder to your `PATH` to access kubectl:
-
-```shell
-export PATH=<path/to/kubernetes-directory>/platforms/linux/amd64:$PATH
-```
-
-Interact with the kubernetes-mesos framework via `kubectl`:
-
-```shell
-$ kubectl get pods
-NAME      READY     STATUS    RESTARTS   AGE
-```
-
-```shell
-# NOTE: your service IPs will likely differ
-$ kubectl get services
-NAME             LABELS                                    SELECTOR   IP(S)          PORT(S)
-k8sm-scheduler   component=scheduler,provider=k8sm         <none>     10.10.10.113   10251/TCP
-kubernetes       component=apiserver,provider=kubernetes   <none>     10.10.10.1     443/TCP
-```
-
-Lastly, look for Kubernetes in the Mesos web GUI by pointing your browser to
-`http://<mesos-master-ip:port>`. Make sure you have an active VPN connection.
-Go to the Frameworks tab, and look for an active framework named "Kubernetes".
-
-## Spin up a pod
-
-Write a JSON pod description to a local file:
-
-```shell
-$ cat <<EOPOD >nginx.yaml
-```
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    ports:
-    - containerPort: 80
-EOPOD
-```
-
-Send the pod description to Kubernetes using the `kubectl` CLI:
-
-```shell
-$ kubectl create -f ./nginx.yaml
-pods/nginx
-```
-
-Wait a minute or two while `dockerd` downloads the image layers from the internet.
-We can use the `kubectl` interface to monitor the status of our pod:
-
-```shell
-$ kubectl get pods
-NAME      READY     STATUS    RESTARTS   AGE
-nginx     1/1       Running   0          14s
-```
-
-Verify that the pod task is running in the Mesos web GUI. Click on the
-Kubernetes framework. The next screen should show the running Mesos task that
-started the Kubernetes pod.
-
-## Launching kube-dns
-
-Kube-dns is an addon for Kubernetes which adds DNS-based service discovery to the cluster. For a detailed explanation see [DNS in Kubernetes][4].
-
-The kube-dns addon runs as a pod inside the cluster. The pod consists of three co-located containers:
-
-- a local etcd instance
-- the [skydns][11] DNS server
-- the kube2sky process to glue skydns to the state of the Kubernetes cluster.
-
-The skydns container offers DNS service via port 53 to the cluster. The etcd communication works via local 127.0.0.1 communication
-
-We assume that kube-dns will use
-
-- the service IP `10.10.10.10`
-- and the `cluster.local` domain.
-
-Note that we have passed these two values already as parameter to the apiserver above.
-
-A template for an replication controller spinning up the pod with the 3 containers can be found at [cluster/addons/dns/skydns-rc.yaml.in][11] in the repository. The following steps are necessary in order to get a valid replication controller yaml file:
-
-- replace `{{ pillar['dns_replicas'] }}`  with `1`
-- replace `{{ pillar['dns_domain'] }}` with `cluster.local.`
-- add `--kube_master_url=${KUBERNETES_MASTER}` parameter to the kube2sky container command.
-
-In addition the service template at [cluster/addons/dns/skydns-svc.yaml.in][12] needs the following replacement:
-
-- `{{ pillar['dns_server'] }}` with `10.10.10.10`.
-
-To do this automatically:
-
-```shell
-sed -e "s/{{ pillar\['dns_replicas'\] }}/1/g;"\
-"s,\(command = \"/kube2sky\"\),\\1\\"$'\n'"        - --kube_master_url=${KUBERNETES_MASTER},;"\
-"s/{{ pillar\['dns_domain'\] }}/cluster.local/g" \
-  cluster/addons/dns/skydns-rc.yaml.in > skydns-rc.yaml
-sed -e "s/{{ pillar\['dns_server'\] }}/10.10.10.10/g" \
-  cluster/addons/dns/skydns-svc.yaml.in > skydns-svc.yaml
-```
-
-Now the kube-dns pod and service are ready to be launched:
-
-```shell
-kubectl create -f ./skydns-rc.yaml
-kubectl create -f ./skydns-svc.yaml
-```
-
-Check with `kubectl get pods --namespace=kube-system` that 3/3 containers of the pods are eventually up and running. Note that the kube-dns pods run in the `kube-system` namespace, not in  `default`.
-
-To check that the new DNS service in the cluster works, we start a busybox pod and use that to do a DNS lookup. First create the `busybox.yaml` pod spec:
-
-```shell
-cat <<EOF >busybox.yaml
-```
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: busybox
-  namespace: default
-spec:
-  containers:
-  - image: busybox
-    command:
-      - sleep
-      - "3600"
-    imagePullPolicy: IfNotPresent
-    name: busybox
-  restartPolicy: Always
-EOF
-```
-
-Then start the pod:
-
-```shell
-kubectl create -f ./busybox.yaml
-```
-
-When the pod is up and running, start a lookup for the Kubernetes master service, made available on 10.10.10.1 by default:
-
-```shell
-kubectl  exec busybox -- nslookup kubernetes
-```
-
-If everything works fine, you will get this output:
-
-```shell
-Server:    10.10.10.10
-Address 1: 10.10.10.10
-
-Name:      kubernetes
-Address 1: 10.10.10.1
-```
-
-## What next?
-
-Try out some of the standard [Kubernetes examples][9].
-
-Read about Kubernetes on Mesos' architecture in the [contrib directory][13].
-
-**NOTE:** Some examples require Kubernetes DNS to be installed on the cluster.
-Future work will add instructions to this guide to enable support for Kubernetes DNS.
-
-**NOTE:** Please be aware that there are [known issues with the current Kubernetes-Mesos implementation][7].
-
-[1]: http://mesosphere.com/docs/tutorials/run-hadoop-on-mesos-using-installer
-[2]: http://mesosphere.com/docs/tutorials/run-spark-on-mesos
-[3]: http://mesosphere.com/docs/tutorials/run-chronos-on-mesos
-[4]: https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/README.md
-[5]: http://open.mesosphere.com/getting-started/cloud/google/mesosphere/
-[6]: http://mesos.apache.org/
-[7]: https://releases.k8s.io/{{page.githubbranch}}/contrib/mesos/docs/issues.md
-[8]: https://github.com/mesosphere/kubernetes-mesos/issues
-[9]: https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples
-[10]: http://open.mesosphere.com/getting-started/cloud/google/mesosphere/#vpn-setup
-[11]: https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/skydns-rc.yaml.in
-[12]: https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/skydns-svc.yaml.in
-[13]: https://releases.k8s.io/{{page.githubbranch}}/contrib/mesos/README.md
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/ovirt.md b/v1.2/docs/getting-started-guides/ovirt.md
deleted file mode 100644
index 183a8cc107..0000000000
--- a/v1.2/docs/getting-started-guides/ovirt.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## What is oVirt
-
-oVirt is a virtual datacenter manager that delivers powerful management of multiple virtual machines on multiple hosts. Using KVM and libvirt, oVirt can be installed on Fedora, CentOS, or Red Hat Enterprise Linux hosts to set up and manage your virtual data center.
-
-## oVirt Cloud Provider Deployment
-
-The oVirt cloud provider allows to easily discover and automatically add new VM instances as nodes to your Kubernetes cluster.
-At the moment there are no community-supported or pre-loaded VM images including Kubernetes but it is possible to [import] or [install] Project Atomic (or Fedora) in a VM to [generate a template]. Any other distribution that includes Kubernetes may work as well.
-
-It is mandatory to [install the ovirt-guest-agent] in the guests for the VM ip address and hostname to be reported to ovirt-engine and ultimately to Kubernetes.
-
-Once the Kubernetes template is available it is possible to start instantiating VMs that can be discovered by the cloud provider.
-
-[import]: http://ovedou.blogspot.it/2014/03/importing-glance-images-as-ovirt.html
-[install]: http://www.ovirt.org/Quick_Start_Guide#Create_Virtual_Machines
-[generate a template]: http://www.ovirt.org/Quick_Start_Guide#Using_Templates
-[install the ovirt-guest-agent]: http://www.ovirt.org/How_to_install_the_guest_agent_in_Fedora
-
-## Using the oVirt Cloud Provider
-
-The oVirt Cloud Provider requires access to the oVirt REST-API to gather the proper information, the required credential should be specified in the `ovirt-cloud.conf` file:
-
-    [connection]
-    uri = https://localhost:8443/ovirt-engine/api
-    username = admin@internal
-    password = admin
-
-In the same file it is possible to specify (using the `filters` section) what search query to use to identify the VMs to be reported to Kubernetes:
-
-    [filters]
-    # Search query used to find nodes
-    vms = tag=kubernetes
-
-In the above example all the VMs tagged with the `kubernetes` label will be reported as nodes to Kubernetes.
-
-The `ovirt-cloud.conf` file then must be specified in kube-controller-manager:
-
-    kube-controller-manager ... --cloud-provider=ovirt --cloud-config=/path/to/ovirt-cloud.conf ...
-
-## oVirt Cloud Provider Screencast
-
-This short screencast demonstrates how the oVirt Cloud Provider can be used to dynamically add VMs to your Kubernetes cluster.
-
-[![Screencast](http://img.youtube.com/vi/JyyST4ZKne8/0.jpg)](http://www.youtube.com/watch?v=JyyST4ZKne8)
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/rackspace.md b/v1.2/docs/getting-started-guides/rackspace.md
deleted file mode 100644
index b9f01e7fb9..0000000000
--- a/v1.2/docs/getting-started-guides/rackspace.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
----
-
-* Supported Version: v0.18.1
-
-In general, the dev-build-and-up.sh workflow for Rackspace is the similar to Google Compute Engine. The specific implementation is different due to the use of CoreOS, Rackspace Cloud Files and the overall network design.
-
-These scripts should be used to deploy development environments for Kubernetes. If your account leverages RackConnect or non-standard networking, these scripts will most likely not work without modification.
-
-NOTE: The rackspace scripts do NOT rely on `saltstack` and instead rely on cloud-init for configuration.
-
-The current cluster design is inspired by:
-
-- [corekube](https://github.com/metral/corekube)
-- [Angus Lees](https://github.com/anguslees/kube-openstack)
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-1. Python2.7
-2. You need to have both `nova` and `swiftly` installed. It's recommended to use a python virtualenv to install these packages into.
-3. Make sure you have the appropriate environment variables set to interact with the OpenStack APIs. See [Rackspace Documentation](http://docs.rackspace.com/servers/api/v2/cs-gettingstarted/content/section_gs_install_nova) for more details.
-
-## Provider: Rackspace
-
-- To build your own released version from source use `export KUBERNETES_PROVIDER=rackspace` and run the `bash hack/dev-build-and-up.sh`
-- Note: The get.k8s.io install method is not working yet for our scripts.
-  * To install the latest released version of Kubernetes use `export KUBERNETES_PROVIDER=rackspace; wget -q -O - https://get.k8s.io | bash`
-
-## Build
-
-1. The Kubernetes binaries will be built via the common build scripts in `build/`.
-2. If you've set the ENV `KUBERNETES_PROVIDER=rackspace`, the scripts will upload `kubernetes-server-linux-amd64.tar.gz` to Cloud Files.
-2. A cloud files container will be created via the `swiftly` CLI and a temp URL will be enabled on the object.
-3. The built `kubernetes-server-linux-amd64.tar.gz` will be uploaded to this container and the URL will be passed to master/nodes when booted.
-
-## Cluster
-
-There is a specific `cluster/rackspace` directory with the scripts for the following steps:
-
-1. A cloud network will be created and all instances will be attached to this network.
-  - flanneld uses this network for next hop routing. These routes allow the containers running on each node to communicate with one another on this private network.
-2. A SSH key will be created and uploaded if needed. This key must be used to ssh into the machines (we do not capture the password).
-3. The master server and additional nodes will be created via the `nova` CLI. A `cloud-config.yaml` is generated and provided as user-data with the entire configuration for the systems.
-4. We then boot as many nodes as defined via `$NUM_MINIONS`.
-
-## Some notes
-
-- The scripts expect `eth2` to be the cloud network that the containers will communicate across.
-- A number of the items in `config-default.sh` are overridable via environment variables.
-- For older versions please either:
- * Sync back to `v0.9` with `git checkout v0.9`
-  * Download a [snapshot of `v0.9`](https://github.com/kubernetes/kubernetes/archive/v0.9.tar.gz)
- * Sync back to `v0.3` with `git checkout v0.3`
-  * Download a [snapshot of `v0.3`](https://github.com/kubernetes/kubernetes/archive/v0.3.tar.gz)
-
-## Network Design
-
-- eth0 - Public Interface used for servers/containers to reach the internet
-- eth1 - ServiceNet - Intra-cluster communication (k8s, etcd, etc) communicate via this interface. The `cloud-config` files use the special CoreOS identifier `$private_ipv4` to configure the services.
-- eth2 - Cloud Network - Used for k8s pods to communicate with one another. The proxy service will pass traffic via this interface.
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/ubuntu-calico.md b/v1.2/docs/getting-started-guides/ubuntu-calico.md
deleted file mode 100644
index e71c0c8982..0000000000
--- a/v1.2/docs/getting-started-guides/ubuntu-calico.md
+++ /dev/null
@@ -1,273 +0,0 @@
----
----
-
-This document describes how to deploy Kubernetes on Ubuntu bare metal nodes with Calico Networking plugin. See [projectcalico.org](http://projectcalico.org) for more information on what Calico is, and [the calicoctl github](https://github.com/projectcalico/calico-docker) for more information on the command-line tool, `calicoctl`.
-
-This guide will set up a simple Kubernetes cluster with a master and two nodes. We will start the following processes with systemd:
-
-On the Master:
-
-- `etcd`
-- `kube-apiserver`
-- `kube-controller-manager`
-- `kube-scheduler`
-- `calico-node`
-
-On each Node:
-
-- `kube-proxy`
-- `kube-kubelet`
-- `calico-node`
-
-## Prerequisites
-
-1. This guide uses `systemd` and thus uses Ubuntu 15.04 which supports systemd natively.
-2. All machines should have the latest docker stable version installed. At the time of writing, that is Docker 1.7.0.
-	- To install docker, follow [these instructions](https://docs.docker.com/installation/ubuntulinux/)
-3. All hosts should be able to communicate with each other, as well as the internet, to download the necessary files.
-4. This demo assumes that none of the hosts have been configured with any Kubernetes or Calico software yet.
-
-## Setup Master
-
-First, get the sample configurations for this tutorial
-
-```shell
-wget https://github.com/Metaswitch/calico-kubernetes-ubuntu-demo/archive/master.tar.gz
-tar -xvf master.tar.gz
-```
-
-### Setup environment variables for systemd services on Master
-
-Many of the sample systemd services provided rely on environment variables on a per-node basis. Here we'll edit those environment variables and move them into place.
-
-1.) Copy the network-environment-template from the `master` directory for editing.
-
-```shell
-cp calico-kubernetes-ubuntu-demo-master/master/network-environment-template network-environment
-```
-
-2.) Edit `network-environment` to represent your current host's settings.
-
-3.) Move the `network-environment` into `/etc`
-
-```shell
-sudo mv -f network-environment /etc
-```
-
-### Install Kubernetes on Master
-
-1.) Build & Install Kubernetes binaries
-
-```shell
-# Get the Kubernetes Source
-wget https://github.com/kubernetes/kubernetes/releases/download/v1.0.3/kubernetes.tar.gz
-
-# Untar it
-tar -xf kubernetes.tar.gz
-tar -xf kubernetes/server/kubernetes-server-linux-amd64.tar.gz
-kubernetes/cluster/ubuntu/build.sh
-
-# Add binaries to /usr/bin
-sudo cp -f binaries/master/* /usr/bin
-sudo cp -f binaries/kubectl /usr/bin
-```
-
-2.) Install the sample systemd processes settings for launching kubernetes services
-
-```shell
-sudo cp -f calico-kubernetes-ubuntu-demo-master/master/*.service /etc/systemd
-sudo systemctl enable /etc/systemd/etcd.service
-sudo systemctl enable /etc/systemd/kube-apiserver.service
-sudo systemctl enable /etc/systemd/kube-controller-manager.service
-sudo systemctl enable /etc/systemd/kube-scheduler.service
-```
-
-3.) Launch the processes.
-
-```shell
-sudo systemctl start etcd.service
-sudo systemctl start kube-apiserver.service
-sudo systemctl start kube-controller-manager.service
-sudo systemctl start kube-scheduler.service
-```
-
-### Install Calico on Master
-
-In order to allow the master to route to pods on our nodes, we will launch the calico-node daemon on our master. This will allow it to learn routes over BGP from the other calico-node daemons in the cluster. The docker daemon should already be running before calico is started.
-
-```shell
-# Install the calicoctl binary, which will be used to launch calico
-wget https://github.com/projectcalico/calico-docker/releases/download/v0.5.5/calicoctl
-chmod +x calicoctl
-sudo cp -f calicoctl /usr/bin
-
-# Install and start the calico service
-sudo cp -f calico-kubernetes-ubuntu-demo-master/master/calico-node.service /etc/systemd
-sudo systemctl enable /etc/systemd/calico-node.service
-sudo systemctl start calico-node.service
-```
-
-> Note: calico-node may take a few minutes on first boot while it downloads the calico-node docker image.
-
-## Setup Nodes
-
-Perform these steps **once on each node**, ensuring you appropriately set the environment variables on each node
-
-### Setup environment variables for systemd services on the Node
-
-1.) Get the sample configurations for this tutorial
-
-```shell
-wget https://github.com/Metaswitch/calico-kubernetes-ubuntu-demo/archive/master.tar.gz
-tar -xvf master.tar.gz
-```
-
-2.) Copy the network-environment-template from the `node` directory
-
-```shell
-cp calico-kubernetes-ubuntu-demo-master/node/network-environment-template network-environment
-```
-
-3.) Edit `network-environment` to represent your current host's settings.
-
-4.) Move `network-environment` into `/etc`
-
-```shell
-sudo mv -f network-environment /etc
-```
-
-### Configure Docker on the Node
-
-#### Create the veth
-
-Instead of using docker's default interface (docker0), we will configure a new one to use desired IP ranges
-
-```shell
-sudo apt-get install -y bridge-utils
-sudo brctl addbr cbr0
-sudo ifconfig cbr0 up
-sudo ifconfig cbr0 <IP>/24
-```
-
-> Replace \<IP\>  with the subnet for this host's containers. Example topology:
-
-  Node  |   cbr0 IP
-------- | -------------
-node-1  | 192.168.1.1/24
-node-2  | 192.168.2.1/24
-node-X  | 192.168.X.1/24
-
-#### Start docker on cbr0
-
-The Docker daemon must be started and told to use the already configured cbr0 instead of using the usual docker0, as well as disabling ip-masquerading and modification of the ip-tables.
-
-1.) Edit the ubuntu-15.04 docker.service for systemd at: `/lib/systemd/system/docker.service`
-
-2.) Find the line that reads `ExecStart=/usr/bin/docker -d -H fd://` and append the following flags: `--bridge=cbr0 --iptables=false --ip-masq=false`
-
-3.) Reload systemctl and restart docker.
-
-```shell
-sudo systemctl daemon-reload
-sudo systemctl restart docker
-```
-
-### Install Calico on the Node
-
-1.) Install Calico
-
-```shell
-# Get the calicoctl binary
-wget https://github.com/projectcalico/calico-docker/releases/download/v0.5.5/calicoctl
-chmod +x calicoctl
-sudo cp -f calicoctl /usr/bin
-
-# Start calico on this node
-sudo cp calico-kubernetes-ubuntu-demo-master/node/calico-node.service /etc/systemd
-sudo systemctl enable /etc/systemd/calico-node.service
-sudo systemctl start calico-node.service
-```
-
->The calico-node service will automatically get the kubernetes-calico plugin binary and install it on the host system.
-
-2.) Use calicoctl to add an IP pool. We must specify the IP and port that the master's etcd is listening on.
-**NOTE: This step only needs to be performed once per Kubernetes deployment, as it covers all the node's IP ranges.**
-
-```shell
-ETCD_AUTHORITY=<MASTER_IP>:4001 calicoctl pool add 192.168.0.0/16
-```
-
-### Install Kubernetes on the Node
-
-1.) Build & Install Kubernetes binaries
-
-```shell
-# Get the Kubernetes Source
-wget https://github.com/kubernetes/kubernetes/releases/download/v1.0.3/kubernetes.tar.gz
-
-# Untar it
-tar -xf kubernetes.tar.gz
-tar -xf kubernetes/server/kubernetes-server-linux-amd64.tar.gz
-kubernetes/cluster/ubuntu/build.sh
-
-# Add binaries to /usr/bin
-sudo cp -f binaries/minion/* /usr/bin
-
-# Get the iptables based kube-proxy reccomended for this demo
-wget https://github.com/projectcalico/calico-kubernetes/releases/download/v0.1.1/kube-proxy
-sudo cp kube-proxy /usr/bin/
-sudo chmod +x /usr/bin/kube-proxy
-```
-
-2.) Install and launch the sample systemd processes settings for launching Kubernetes services
-
-```shell
-sudo cp calico-kubernetes-ubuntu-demo-master/node/kube-proxy.service /etc/systemd/
-sudo cp calico-kubernetes-ubuntu-demo-master/node/kube-kubelet.service /etc/systemd/
-sudo systemctl enable /etc/systemd/kube-proxy.service
-sudo systemctl enable /etc/systemd/kube-kubelet.service
-sudo systemctl start kube-proxy.service
-sudo systemctl start kube-kubelet.service
-```
-
-> *You may want to consider checking their status after to ensure everything is running*
-
-## Install the DNS Addon
-
-Most Kubernetes deployments will require the DNS addon for service discovery.  For more on DNS service discovery, check [here](https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns).
-
-The config repository for this guide comes with manifest files to start the DNS addon.  To install DNS, do the following on your Master node.
-
-Replace `<MASTER_IP>` in `calico-kubernetes-ubuntu-demo-master/dns/skydns-rc.yaml` with your Master's IP address.  Then, create `skydns-rc.yaml` and `skydns-svc.yaml` using `kubectl create -f <FILE>`.
-
-## Launch other Services With Calico-Kubernetes
-
-At this point, you have a fully functioning cluster running on kubernetes with a master and 2 nodes networked with Calico. You can now follow any of the [standard documentation](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/) to set up other services on your cluster.
-
-## Connectivity to outside the cluster
-
-With this sample configuration, because the containers have private `192.168.0.0/16` IPs, you will need NAT to allow   connectivity between containers and the internet. However, in a full datacenter deployment, NAT is not always necessary, since Calico can peer with the border routers over BGP.
-
-### NAT on the nodes
-
-The simplest method for enabling connectivity from containers to the internet is to use an iptables masquerade rule. This is the standard mechanism [recommended](/{{page.version}}/docs/admin/networking/#google-compute-engine-gce) in the Kubernetes GCE environment.
-
-We need to NAT traffic that has a destination outside of the cluster. Internal traffic includes the master/nodes, and the container IP pools. A suitable masquerade chain would follow the pattern below, replacing the following variables:
-
-- `CONTAINER_SUBNET`: The cluster-wide subnet from which container IPs are chosen.  All cbr0 bridge subnets fall within this range. The above example uses `192.168.0.0/16`.
-- `KUBERNETES_HOST_SUBNET`: The subnet from which Kubernetes node / master IP addresses have been chosen.
-- `HOST_INTERFACE`: The interface on the Kubernetes node which is used for external connectivity.  The above example uses `eth0`
-
-```shell
-sudo iptables -t nat -N KUBE-OUTBOUND-NAT
-sudo iptables -t nat -A KUBE-OUTBOUND-NAT -d <CONTAINER_SUBNET> -o <HOST_INTERFACE> -j RETURN
-sudo iptables -t nat -A KUBE-OUTBOUND-NAT -d <KUBERNETES_HOST_SUBNET> -o <HOST_INTERFACE> -j RETURN
-sudo iptables -t nat -A KUBE-OUTBOUND-NAT -j MASQUERADE
-sudo iptables -t nat -A POSTROUTING -j KUBE-OUTBOUND-NAT
-```
-
-This chain should be applied on the master and all nodes. In production, these rules should be persisted, e.g. with `iptables-persistent`.
-
-### NAT at the border router
-
-In a datacenter environment, it is recommended to configure Calico to peer with the border routers over BGP. This means that the container IPs will be routable anywhere in the datacenter, and so NAT is not needed on the nodes (though it may be enabled at the datacenter edge to allow outbound-only internet connectivity).
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/ubuntu.md b/v1.2/docs/getting-started-guides/ubuntu.md
deleted file mode 100644
index a8de4a3a28..0000000000
--- a/v1.2/docs/getting-started-guides/ubuntu.md
+++ /dev/null
@@ -1,261 +0,0 @@
----
----
-
-This document describes how to deploy kubernetes on ubuntu nodes, 1 master and 3 nodes involved
-in the given examples. You can scale to **any number of nodes** by changing some settings with ease.
-The original idea was heavily inspired by @jainvipin 's ubuntu single node
-work, which has been merge into this document.
-
-[Cloud team from Zhejiang University](https://github.com/ZJU-SEL) will maintain this work.
-
-* TOC
-{:toc}
-
-## Prerequisites
-
-1. The nodes have installed docker version 1.2+ and bridge-utils to manipulate linux bridge.
-2. All machines can communicate with each other. Master node needs to connect the Internet to download the necessary files, while working nodes do not.
-3. These guide is tested OK on Ubuntu 14.04 LTS 64bit server, but it can not work with
-Ubuntu 15 which use systemd instead of upstart. We are working around fixing this.
-4. Dependencies of this guide: etcd-2.0.12, flannel-0.4.0, k8s-1.0.3, may work with higher versions.
-5. All the remote servers can be ssh logged in without a password by using key authentication.
-
-
-## Starting a Cluster
-
-### Download binaries
-
-First clone the kubernetes github repo
-
-```shell
-$ git clone https://github.com/kubernetes/kubernetes.git
-```
-
-Then download all the needed binaries into given directory (cluster/ubuntu/binaries)
-
-```shell
-$ cd kubernetes/cluster/ubuntu
-$ ./build.sh
-```
-
-You can customize your etcd version, flannel version, k8s version by changing corresponding variables
-`ETCD_VERSION` , `FLANNEL_VERSION` and `KUBE_VERSION` in build.sh, by default etcd version is 2.0.12,
-flannel version is 0.4.0 and k8s version is 1.0.3.
-
-Make sure that the involved binaries are located properly in the binaries/master
-or binaries/minion directory before you go ahead to the next step .
-
-Note that we use flannel here to set up overlay network, yet it's optional. Actually you can build up k8s
-cluster natively, or use flannel, Open vSwitch or any other SDN tool you like.
-
-#### Configure and start the Kubernetes cluster
-
-An example cluster is listed below:
-
-| IP Address  |   Role   |
-|-------------|----------|
-|10.10.103.223|   node   |
-|10.10.103.162|   node   |
-|10.10.103.250| both master and node|
-
-First configure the cluster information in cluster/ubuntu/config-default.sh, below is a simple sample.
-
-```shell
-export nodes="vcap@10.10.103.250 vcap@10.10.103.162 vcap@10.10.103.223"
-
-export role="ai i i"
-
-export NUM_MINIONS=${NUM_MINIONS:-3}
-
-export SERVICE_CLUSTER_IP_RANGE=192.168.3.0/24
-
-export FLANNEL_NET=172.16.0.0/16
-```
-
-The first variable `nodes` defines all your cluster nodes, MASTER node comes first and
-separated with blank space like `<user_1@ip_1> <user_2@ip_2> <user_3@ip_3> `
-
-Then the `role` variable defines the role of above machine in the same order, "ai" stands for machine
-acts as both master and node, "a" stands for master, "i" stands for node.
-
-The `NUM_MINIONS` variable defines the total number of nodes.
-
-The `SERVICE_CLUSTER_IP_RANGE` variable defines the kubernetes service IP range. Please make sure
-that you do have a valid private ip range defined here, because some IaaS provider may reserve private ips.
-You can use below three private network range according to rfc1918. Besides you'd better not choose the one
-that conflicts with your own private network range.
-
-```shell
-10.0.0.0        -   10.255.255.255  (10/8 prefix)
-
-172.16.0.0      -   172.31.255.255  (172.16/12 prefix)
-
-192.168.0.0     -   192.168.255.255 (192.168/16 prefix)
-```
-
-The `FLANNEL_NET` variable defines the IP range used for flannel overlay network,
-should not conflict with above `SERVICE_CLUSTER_IP_RANGE`.
-
-**Note:** When deploying, master needs to connect the Internet to download the necessary files. If your machines locate in a private network that need proxy setting to connect the Internet, you can set the config `PROXY_SETTING` in cluster/ubuntu/config-default.sh such as:
-
-```shell
-PROXY_SETTING="http_proxy=http://server:port https_proxy=https://server:port"
-```
-
-After all the above variables being set correctly, we can use following command in cluster/ directory to bring up the whole cluster.
-
-```shell
-KUBERNETES_PROVIDER=ubuntu ./kube-up.sh
-```
-
-The scripts automatically scp binaries and config files to all the machines and start the k8s service on them.
-The only thing you need to do is to type the sudo password when promoted.
-
-```shell
-Deploying minion on machine 10.10.103.223
-...
-[sudo] password to copy files and start minion: 
-```
-
-If all things goes right, you will see the below message from console indicating the k8s is up.
-
-```shell
-Cluster validation succeeded
-```
-
-### Test it out
-
-You can use `kubectl` command to check if the newly created k8s is working correctly.
-The `kubectl` binary is under the `cluster/ubuntu/binaries` directory.
-You can make it available via PATH, then you can use the below command smoothly.
-
-For example, use `$ kubectl get nodes` to see if all of your nodes are ready.
-
-```shell
-$ kubectl get nodes
-NAME            LABELS                                 STATUS
-10.10.103.162   kubernetes.io/hostname=10.10.103.162   Ready
-10.10.103.223   kubernetes.io/hostname=10.10.103.223   Ready
-10.10.103.250   kubernetes.io/hostname=10.10.103.250   Ready
-```
-
-Also you can run Kubernetes [guest-example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/) to build a redis backend cluster on the k8s．
-
-
-### Deploy addons
-
-Assuming you have a starting cluster now, this section will tell you how to deploy addons like DNS
-and UI onto the existing cluster.
-
-The configuration of DNS is configured in cluster/ubuntu/config-default.sh.
-
-```shell
-ENABLE_CLUSTER_DNS="${KUBE_ENABLE_CLUSTER_DNS:-true}"
-
-DNS_SERVER_IP="192.168.3.10"
-
-DNS_DOMAIN="cluster.local"
-
-DNS_REPLICAS=1
-```
-
-The `DNS_SERVER_IP` is defining the ip of dns server which must be in the `SERVICE_CLUSTER_IP_RANGE`.
-The `DNS_REPLICAS` describes how many dns pod running in the cluster.
-
-By default, we also take care of kube-ui addon.
-
-```shell
-ENABLE_CLUSTER_UI="${KUBE_ENABLE_CLUSTER_UI:-true}"
-```
-
-After all the above variables have been set, just type the following command.
-
-```shell
-$ cd cluster/ubuntu
-$ KUBERNETES_PROVIDER=ubuntu ./deployAddons.sh
-```
-
-After some time, you can use `$ kubectl get pods --namespace=kube-system` to see the DNS and UI pods are running in the cluster.
-
-### On going
-
-We are working on these features which we'd like to let everybody know:
-
-1. Run kubernetes binaries in Docker using [kube-in-docker](https://github.com/ZJU-SEL/kube-in-docker/tree/baremetal-kube),
-to eliminate OS-distro differences.
-2. Tearing Down scripts: clear and re-create the whole stack by one click.
-
-### Trouble shooting
-
-Generally, what this approach does is quite simple:
-
-1. Download and copy binaries and configuration files to proper directories on every node
-2. Configure `etcd` using IPs based on input from user
-3. Create and start flannel network
-
-So if you encounter a problem, **check etcd configuration first**
-
-Please try:
-
-1. Check `/var/log/upstart/etcd.log` for suspicious etcd log
-2. Check `/etc/default/etcd`, as we do not have much input validation, a right config should be like:
-
-```shell
-ETCD_OPTS="-name infra1 -initial-advertise-peer-urls <http://ip_of_this_node:2380> -listen-peer-urls <http://ip_of_this_node:2380> -initial-cluster-token etcd-cluster-1 -initial-cluster infra1=<http://ip_of_this_node:2380>,infra2=<http://ip_of_another_node:2380>,infra3=<http://ip_of_another_node:2380> -initial-cluster-state new"
-```
-
-3. You may find following commands useful, the former one to bring down the cluster, while
-the latter one could start it again.
-
-```shell
-KUBERNETES_PROVIDER=ubuntu ./kube-down.sh
-KUBERNETES_PROVIDER=ubuntu ./kube-up.sh
-```
-
-4. You can also customize your own settings in `/etc/default/{component_name}`.
-
-
-### Upgrading a Cluster
-
-If you already have a kubernetes cluster, and want to upgrade to a new version,
-you can use following command in cluster/ directory to update the whole cluster or a specified node to a new version.
-
-```shell
-KUBERNETES_PROVIDER=ubuntu ./kube-push.sh [-m|-n <node id>] <version>
-```
-
-It can be done for all components (by default), master(`-m`) or specified node(`-n`).
-If the version is not specified, the script will try to use local binaries.You should ensure all the binaries are well prepared in path `cluster/ubuntu/binaries`.
-
-```shell
-$ tree cluster/ubuntu/binaries
-binaries/
-'��'��'�� kubectl
-'��'��'�� master
-'��   '��'��'�� etcd
-'��   '��'��'�� etcdctl
-'��   '��'��'�� flanneld
-'��   '��'��'�� kube-apiserver
-'��   '��'��'�� kube-controller-manager
-'��   '��'��'�� kube-scheduler
-'��'��'�� minion
-    '��'��'�� flanneld
-    '��'��'�� kubelet
-    '��'��'�� kube-proxy
-```
-
-Upgrading single node is experimental now. You can use following command to get a help.
-
-```shell
-KUBERNETES_PROVIDER=ubuntu ./kube-push.sh -h
-```
-
-Some examples are as follows:
-
-* upgrade master to version 1.0.5: `$ KUBERNETES_PROVIDER=ubuntu ./kube-push.sh -m 1.0.5`
-* upgrade node 10.10.103.223 to version 1.0.5 : `$ KUBERNETES_PROVIDER=ubuntu ./kube-push.sh -n 10.10.103.223 1.0.5`
-* upgrade master and all nodes to version 1.0.5: `$ KUBERNETES_PROVIDER=ubuntu ./kube-push.sh 1.0.5`
-
-The script will not delete any resources of your cluster, it just replaces the binaries.
-You can use `kubectl` command to check if the newly upgraded k8s is working correctly.
-For example, use `$ kubectl get nodes` to see if all of your nodes are ready.Or refer to [test-it-out](/{{page.version}}/docs/getting-started-guides/ubuntu/#test-it-out)
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/vagrant.md b/v1.2/docs/getting-started-guides/vagrant.md
deleted file mode 100644
index 9bea0df0a1..0000000000
--- a/v1.2/docs/getting-started-guides/vagrant.md
+++ /dev/null
@@ -1,336 +0,0 @@
----
----
-
-Running Kubernetes with Vagrant (and VirtualBox) is an easy way to run/test/develop on your local machine (Linux, Mac OS X).
-
-* TOC
-{:toc}
-
-### Prerequisites
-
-1. Install latest version >= 1.6.2 of vagrant from http://www.vagrantup.com/downloads.html
-2. Install one of:
-   1. Version 4.3.28 of Virtual Box from https://www.virtualbox.org/wiki/Download_Old_Builds_4_3
-   2. [VMWare Fusion](https://www.vmware.com/products/fusion/) version 5 or greater as well as the appropriate [Vagrant VMWare Fusion provider](https://www.vagrantup.com/vmware)
-   3. [VMWare Workstation](https://www.vmware.com/products/workstation/) version 9 or greater as well as the [Vagrant VMWare Workstation provider](https://www.vagrantup.com/vmware)
-   4. [Parallels Desktop](https://www.parallels.com/products/desktop/) version 9 or greater as well as the [Vagrant Parallels provider](https://parallels.github.io/vagrant-parallels/)
-   5. libvirt with KVM and enable support of hardware virtualisation. [Vagrant-libvirt](https://github.com/pradels/vagrant-libvirt). For fedora provided official rpm, and possible to use `yum install vagrant-libvirt`
-
-### Setup
-
-Setting up a cluster is as simple as running:
-
-```shell
-export KUBERNETES_PROVIDER=vagrant
-curl -sS https://get.k8s.io | bash
-```
-
-Alternatively, you can download [Kubernetes release](https://github.com/kubernetes/kubernetes/releases) and extract the archive. To start your local cluster, open a shell and run:
-
-```shell
-cd kubernetes
-
-export KUBERNETES_PROVIDER=vagrant
-./cluster/kube-up.sh
-```
-
-The `KUBERNETES_PROVIDER` environment variable tells all of the various cluster management scripts which variant to use.  If you forget to set this, the assumption is you are running on Google Compute Engine.
-
-By default, the Vagrant setup will create a single master VM (called kubernetes-master) and one node (called kubernetes-minion-1). Each VM will take 1 GB, so make sure you have at least 2GB to 4GB of free memory (plus appropriate free disk space).
-
-Vagrant will provision each machine in the cluster with all the necessary components to run Kubernetes.  The initial setup can take a few minutes to complete on each machine.
-
-If you installed more than one Vagrant provider, Kubernetes will usually pick the appropriate one. However, you can override which one Kubernetes will use by setting the [`VAGRANT_DEFAULT_PROVIDER`](https://docs.vagrantup.com/v2/providers/default) environment variable:
-
-```shell
-export VAGRANT_DEFAULT_PROVIDER=parallels
-export KUBERNETES_PROVIDER=vagrant
-./cluster/kube-up.sh
-```
-
-By default, each VM in the cluster is running Fedora.
-
-To access the master or any node:
-
-```shell
-vagrant ssh master
-vagrant ssh minion-1
-```
-
-If you are running more than one node, you can access the others by:
-
-```shell
-vagrant ssh minion-2
-vagrant ssh minion-3
-```
-
-Each node in the cluster installs the docker daemon and the kubelet.
-
-The master node instantiates the Kubernetes master components as pods on the machine.
-
-To view the service status and/or logs on the kubernetes-master:
-
-```shell
-[vagrant@kubernetes-master ~] $ vagrant ssh master
-[vagrant@kubernetes-master ~] $ sudo su
-
-[root@kubernetes-master ~] $ systemctl status kubelet
-[root@kubernetes-master ~] $ journalctl -ru kubelet
-
-[root@kubernetes-master ~] $ systemctl status docker
-[root@kubernetes-master ~] $ journalctl -ru docker
-
-[root@kubernetes-master ~] $ tail -f /var/log/kube-apiserver.log
-[root@kubernetes-master ~] $ tail -f /var/log/kube-controller-manager.log
-[root@kubernetes-master ~] $ tail -f /var/log/kube-scheduler.log
-```
-
-To view the services on any of the nodes:
-
-```shell
-[vagrant@kubernetes-master ~] $ vagrant ssh minion-1
-[vagrant@kubernetes-master ~] $ sudo su
-
-[root@kubernetes-master ~] $ systemctl status kubelet
-[root@kubernetes-master ~] $ journalctl -ru kubelet
-
-[root@kubernetes-master ~] $ systemctl status docker
-[root@kubernetes-master ~] $ journalctl -ru docker
-```
-
-### Interacting with your Kubernetes cluster with Vagrant.
-
-With your Kubernetes cluster up, you can manage the nodes in your cluster with the regular Vagrant commands.
-
-To push updates to new Kubernetes code after making source changes:
-
-```shell
-./cluster/kube-push.sh
-```
-
-To stop and then restart the cluster:
-
-```shell
-vagrant halt
-./cluster/kube-up.sh
-```
-
-To destroy the cluster:
-
-```shell
-vagrant destroy
-```
-
-Once your Vagrant machines are up and provisioned, the first thing to do is to check that you can use the `kubectl.sh` script.
-
-You may need to build the binaries first, you can do this with `make`
-
-```shell
-$ ./cluster/kubectl.sh get nodes
-
-NAME                LABELS
-10.245.1.4          <none>
-10.245.1.5          <none>
-10.245.1.3          <none>
-```
-
-### Authenticating with your master
-
-When using the vagrant provider in Kubernetes, the `cluster/kubectl.sh` script will cache your credentials in a `~/.kubernetes_vagrant_auth` file so you will not be prompted for them in the future.
-
-```shell
-cat ~/.kubernetes_vagrant_auth
-```
-
-```json
-{ "User": "vagrant",
-  "Password": "vagrant",
-  "CAFile": "/home/k8s_user/.kubernetes.vagrant.ca.crt",
-  "CertFile": "/home/k8s_user/.kubecfg.vagrant.crt",
-  "KeyFile": "/home/k8s_user/.kubecfg.vagrant.key"
-}
-```
-
-You should now be set to use the `cluster/kubectl.sh` script. For example try to list the nodes that you have started with:
-
-```shell
-./cluster/kubectl.sh get nodes
-```
-
-### Running containers
-
-Your cluster is running, you can list the nodes in your cluster:
-
-```shell
-$ ./cluster/kubectl.sh get nodes
-
-NAME                 LABELS
-10.245.2.4           <none>
-10.245.2.3           <none>
-10.245.2.2           <none>
-```
-
-Now start running some containers!
-
-You can now use any of the `cluster/kube-*.sh` commands to interact with your VM machines.
-Before starting a container there will be no pods, services and replication controllers.
-
-```shell
-$ ./cluster/kubectl.sh get pods
-NAME        READY     STATUS    RESTARTS   AGE
-
-$ ./cluster/kubectl.sh get services
-NAME              CLUSTER_IP       EXTERNAL_IP       PORT(S)       SELECTOR               AGE
-
-$ ./cluster/kubectl.sh get replicationcontrollers
-CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR   REPLICAS
-```
-
-Start a container running nginx with a replication controller and three replicas
-
-```shell
-$ ./cluster/kubectl.sh run my-nginx --image=nginx --replicas=3 --port=80
-```
-
-When listing the pods, you will see that three containers have been started and are in Waiting state:
-
-```shell
-$ ./cluster/kubectl.sh get pods
-NAME             READY     STATUS    RESTARTS   AGE
-my-nginx-5kq0g   0/1       Pending   0          10s
-my-nginx-gr3hh   0/1       Pending   0          10s
-my-nginx-xql4j   0/1       Pending   0          10s
-```
-
-You need to wait for the provisioning to complete, you can monitor the nodes by doing:
-
-```shell
-$ vagrant ssh minion-1 -c 'sudo docker images'
-kubernetes-minion-1:
-    REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
-    <none>              <none>              96864a7d2df3        26 hours ago        204.4 MB
-    google/cadvisor     latest              e0575e677c50        13 days ago         12.64 MB
-    kubernetes/pause    latest              6c4579af347b        8 weeks ago         239.8 kB
-```
-
-Once the docker image for nginx has been downloaded, the container will start and you can list it:
-
-```shell
-$ vagrant ssh minion-1 -c 'sudo docker ps'
-kubernetes-minion-1:
-    CONTAINER ID        IMAGE                     COMMAND                CREATED             STATUS              PORTS                    NAMES
-    dbe79bf6e25b        nginx:latest              "nginx"                21 seconds ago      Up 19 seconds                                k8s--mynginx.8c5b8a3a--7813c8bd_-_3ffe_-_11e4_-_9036_-_0800279696e1.etcd--7813c8bd_-_3ffe_-_11e4_-_9036_-_0800279696e1--fcfa837f
-    fa0e29c94501        kubernetes/pause:latest   "/pause"               8 minutes ago       Up 8 minutes        0.0.0.0:8080->80/tcp     k8s--net.a90e7ce4--7813c8bd_-_3ffe_-_11e4_-_9036_-_0800279696e1.etcd--7813c8bd_-_3ffe_-_11e4_-_9036_-_0800279696e1--baf5b21b
-    aa2ee3ed844a        google/cadvisor:latest    "/usr/bin/cadvisor"    38 minutes ago      Up 38 minutes                                k8s--cadvisor.9e90d182--cadvisor_-_agent.file--4626b3a2
-    65a3a926f357        kubernetes/pause:latest   "/pause"               39 minutes ago      Up 39 minutes       0.0.0.0:4194->8080/tcp   k8s--net.c5ba7f0e--cadvisor_-_agent.file--342fd561
-```
-
-Going back to listing the pods, services and replicationcontrollers, you now have:
-
-```shell
-$ ./cluster/kubectl.sh get pods
-NAME             READY     STATUS    RESTARTS   AGE
-my-nginx-5kq0g   1/1       Running   0          1m
-my-nginx-gr3hh   1/1       Running   0          1m
-my-nginx-xql4j   1/1       Running   0          1m
-
-$ ./cluster/kubectl.sh get services
-NAME              CLUSTER_IP       EXTERNAL_IP       PORT(S)       SELECTOR               AGE
-my-nginx          10.0.0.1         <none>            80/TCP        run=my-nginx           1h
-```
-
-We did not start any services, hence there are none listed. But we see three replicas displayed properly.
-Check the [guestbook](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/) application to learn how to create a service.
-You can already play with scaling the replicas with:
-
-```shell
-$ ./cluster/kubectl.sh scale rc my-nginx --replicas=2
-$ ./cluster/kubectl.sh get pods
-NAME             READY     STATUS    RESTARTS   AGE
-my-nginx-5kq0g   1/1       Running   0          2m
-my-nginx-gr3hh   1/1       Running   0          2m
-```
-
-Congratulations!
-
-### Troubleshooting
-
-#### I keep downloading the same (large) box all the time!
-
-By default the Vagrantfile will download the box from S3. You can change this (and cache the box locally) by providing a name and an alternate URL when calling `kube-up.sh`
-
-```shell
-export KUBERNETES_BOX_NAME=choose_your_own_name_for_your_kuber_box
-export KUBERNETES_BOX_URL=path_of_your_kuber_box
-export KUBERNETES_PROVIDER=vagrant
-./cluster/kube-up.sh
-```
-
-#### I just created the cluster, but I am getting authorization errors!
-
-You probably have an incorrect ~/.kubernetes_vagrant_auth file for the cluster you are attempting to contact.
-
-```shell
-rm ~/.kubernetes_vagrant_auth
-```
-
-After using kubectl.sh make sure that the correct credentials are set:
-
-```shell
-cat ~/.kubernetes_vagrant_auth
-```
-
-```json
-{
-  "User": "vagrant",
-  "Password": "vagrant"
-}
-```
-
-#### I just created the cluster, but I do not see my container running!
-
-If this is your first time creating the cluster, the kubelet on each node schedules a number of docker pull requests to fetch prerequisite images.  This can take some time and as a result may delay your initial pod getting provisioned.
-
-#### I want to make changes to Kubernetes code!
-
-To set up a vagrant cluster for hacking, follow the [vagrant developer guide](/{{page.version}}/docs/devel/developer-guides/vagrant).
-
-#### I have brought Vagrant up but the nodes cannot validate!
-
-Log on to one of the nodes (`vagrant ssh minion-1`) and inspect the salt minion log (`sudo cat /var/log/salt/minion`).
-
-#### I want to change the number of nodes!
-
-You can control the number of nodes that are instantiated via the environment variable `NUM_MINIONS` on your host machine.  If you plan to work with replicas, we strongly encourage you to work with enough nodes to satisfy your largest intended replica size.  If you do not plan to work with replicas, you can save some system resources by running with a single node. You do this, by setting `NUM_MINIONS` to 1 like so:
-
-```shell
-export NUM_MINIONS=1
-```
-
-#### I want my VMs to have more memory!
-
-You can control the memory allotted to virtual machines with the `KUBERNETES_MEMORY` environment variable.
-Just set it to the number of megabytes you would like the machines to have. For example:
-
-```shell
-export KUBERNETES_MEMORY=2048
-```
-
-If you need more granular control, you can set the amount of memory for the master and nodes independently. For example:
-
-```shell
-export KUBERNETES_MASTER_MEMORY=1536
-export KUBERNETES_MINION_MEMORY=2048
-```
-
-#### I ran vagrant suspend and nothing works!
-
-`vagrant suspend` seems to mess up the network.  This is not supported at this time.
-
-#### I want vagrant to sync folders via nfs!
-
-You can ensure that vagrant uses nfs to sync folders with virtual machines by setting the KUBERNETES_VAGRANT_USE_NFS environment variable to 'true'. nfs is faster than virtualbox or vmware's 'shared folders' and does not require guest additions. See the [vagrant docs](http://docs.vagrantup.com/v2/synced-folders/nfs) for details on configuring nfs on the host. This setting will have no effect on the libvirt provider, which uses nfs by default. For example:
-
-```shell
-export KUBERNETES_VAGRANT_USE_NFS=true
-```
\ No newline at end of file
diff --git a/v1.2/docs/getting-started-guides/vsphere.md b/v1.2/docs/getting-started-guides/vsphere.md
deleted file mode 100644
index e41175bcac..0000000000
--- a/v1.2/docs/getting-started-guides/vsphere.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
----
-
-The example below creates a Kubernetes cluster with 4 worker node Virtual
-Machines and a master Virtual Machine (i.e. 5 VMs in your cluster). This
-cluster is set up and controlled from your workstation (or wherever you find
-convenient).
-
-* TOC
-{:toc}
-
-### Prerequisites
-
-1. You need administrator credentials to an ESXi machine or vCenter instance.
-2. You must have Go (version 1.2 or later) installed: [www.golang.org](http://www.golang.org).
-3. You must have your `GOPATH` set up and include `$GOPATH/bin` in your `PATH`.
-
-```shell
-export GOPATH=$HOME/src/go
-   mkdir -p $GOPATH
-   export PATH=$PATH:$GOPATH/bin
-```
-
-4. Install the govc tool to interact with ESXi/vCenter:
-
-```shell
-go get github.com/vmware/govmomi/govc
-```
-
-5. Get or build a [binary release](/{{page.version}}/docs/getting-started-guides/binary_release)
-
-### Setup
-
-Download a prebuilt Debian 7.7 VMDK that we'll use as a base image:
-
-```shell
-curl --remote-name-all https://storage.googleapis.com/govmomi/vmdk/2014-11-11/kube.vmdk.gz{,.md5}
-md5sum -c kube.vmdk.gz.md5
-gzip -d kube.vmdk.gz
-```
-
-Import this VMDK into your vSphere datastore:
-
-```shell
-export GOVC_URL='user:pass@hostname'
-export GOVC_INSECURE=1 # If the host above uses a self-signed cert
-export GOVC_DATASTORE='target datastore'
-export GOVC_RESOURCE_POOL='resource pool or cluster with access to datastore'
-
-govc import.vmdk kube.vmdk ./kube/
-```
-
-Verify that the VMDK was correctly uploaded and expanded to ~3GiB:
-
-```shell
-govc datastore.ls ./kube/
-```
-
-Take a look at the file `cluster/vsphere/config-common.sh` fill in the required
-parameters. The guest login for the image that you imported is `kube:kube`.
-
-### Starting a cluster
-
-Now, let's continue with deploying Kubernetes.
-This process takes about ~10 minutes.
-
-```shell
-cd kubernetes # Extracted binary release OR repository root
-export KUBERNETES_PROVIDER=vsphere
-cluster/kube-up.sh
-```
-
-Refer to the top level README and the getting started guide for Google Compute
-Engine. Once you have successfully reached this point, your vSphere Kubernetes
-deployment works just as any other one!
-
-**Enjoy!**
-
-### Extra: debugging deployment failure
-
-The output of `kube-up.sh` displays the IP addresses of the VMs it deploys. You
-can log into any VM as the `kube` user to poke around and figure out what is
-going on (find yourself authorized with your SSH key, or use the password
-`kube` otherwise).
\ No newline at end of file
diff --git a/v1.2/docs/index.md b/v1.2/docs/index.md
deleted file mode 100644
index dd7900d609..0000000000
--- a/v1.2/docs/index.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
----
-
-* The [User's guide](/{{page.version}}/docs/user-guide/) is for anyone who wants to run programs and
-  services on an existing Kubernetes cluster.
-
-* The [Cluster Admin's guide](/{{page.version}}/docs/admin/) is for anyone setting up
-  a Kubernetes cluster or administering it.
-
-* The [Developer guide](/{{page.version}}/docs/devel/) is for anyone wanting to write
-  programs that access the Kubernetes API, write plugins or extensions, or
-  modify the core code of Kubernetes.
-
-* The [Kubectl Command Line Interface](/{{page.version}}/docs/user-guide/kubectl/kubectl) is a detailed reference on
-  the `kubectl` CLI.
-
-* The [API object documentation](http://kubernetes.io/third_party/swagger-ui/)
-  is a detailed description of all fields found in core API objects.
-
-* An overview of the [Design of Kubernetes](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/)
-
-* There are example files and walkthroughs in the [examples](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples)
-  folder.
-
-* If something went wrong, see the [troubleshooting](/{{page.version}}/docs/troubleshooting) document for how to debug.
-You should also check the [known issues](/{{page.version}}/docs/user-guide/known-issues) for the release you're using.
-
-* To report a security issue, see [Reporting a Security Issue](/{{page.version}}/docs/reporting-security-issues).
-
-
-
diff --git a/v1.2/docs/reporting-security-issues.md b/v1.2/docs/reporting-security-issues.md
deleted file mode 100644
index 5a3dc601be..0000000000
--- a/v1.2/docs/reporting-security-issues.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
----
-
-If you believe you have discovered a vulnerability or a have a security incident to report, please follow the steps below. This applies to Kubernetes releases v1.0 or later.
-
-To watch for security and major API announcements, please join our [kubernetes-announce](https://groups.google.com/forum/#!forum/kubernetes-announce) group.
-
-## Reporting a security issue
-
-To report an issue, please:
-
-- Submit a bug report [here](http://goo.gl/vulnz).
-  - Select 'I want to report a technical security bug in a Google product (SQLi, XSS, etc.).'?
-  - Select 'Other'? as the Application Type.
-- Under reproduction steps, please additionally include
-  - the words "Kubernetes Security issue"
-  - Description of the issue
-  - Kubernetes release (e.g. output of `kubectl version` command, which includes server version.)
-  - Environment setup (e.g.  which "Getting Started Guide" you followed, if any; what node operating system used; what service or software creates your virtual machines, if any)
-
-An online submission will have the fastest response; however, if you prefer email, please send mail to security@google.com. If you feel the need, please use the [PGP public key](https://services.google.com/corporate/publickey.txt) to encrypt communications.
-
-
-
diff --git a/v1.2/docs/roadmap.md b/v1.2/docs/roadmap.md
deleted file mode 100644
index 67c8ca45d6..0000000000
--- a/v1.2/docs/roadmap.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
----
-
-## Kubernetes 1.1
-
-### Timeline
-
-We are targetting late October for our 1.1 release of Kubernetes.  We plan on cutting a first release candidate
-in early October.  We will enter feature freeze for the 1.1 release on September 21st.  Note this does not mean
-that the master branch is fully frozen, but all 1.1 features *must* be in by September 21st and large-scale
-refactors of the codebase will be blocked until the 1.1 release is finalized to ensure easy cherry-picks.
-
-### Scope
-
-The 1.1 release of Kubernetes will be a purely additive releases, the `v1` API will be maintained, with a set
-of newly added features.
-
-#### Blocking Features
-
-The following features are considered blocking for the 1.1 release:
-   * Docker 1.8.x
-   * Graceful pod termination
-   * IPtables based kube-proxy (tbd if this is the default for all platforms)
-   * Improvements to kubectl usability and features
-   * Support for 250 node clusters
-   * Horizontal Pod autoscaling
-   * Support for experimental APIs and API groups.
-   * Job objects
-
-#### Nice to have features
-
-The following features will be part of 1.1 if complete, but will not block the release:
-   * Deployment API
-   * ScheduledJob API
-   * Daemon Controller
-   * ConfigData API
-   * HTTP(S) load balancer support
-   * Rolling update improvements
-   * Third party CRUD resources
-
-## Post 1.1
-
-We're in the process of prioritizing changes to be made after 1.1.
-
-Please watch the [Github milestones] (https://github.com/kubernetes/kubernetes/milestones) for our future plans.
-
-
-
diff --git a/v1.2/docs/troubleshooting.md b/v1.2/docs/troubleshooting.md
deleted file mode 100644
index fd79413735..0000000000
--- a/v1.2/docs/troubleshooting.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
----
-
-## Troubleshooting
-
-Sometimes things go wrong.  This guide is aimed at making them right.  It has two sections:
-
-   * [Troubleshooting your application](/{{page.version}}/docs/user-guide/application-troubleshooting) - Useful for users who are deploying code into Kubernetes and wondering why it is not working.
-   * [Troubleshooting your cluster](/{{page.version}}/docs/admin/cluster-troubleshooting) - Useful for cluster administrators and people whose Kubernetes cluster is unhappy.
-
-You should also check the [known issues](/{{page.version}}/docs/user-guide/known-issues) for the release you're using.
-
-# Getting help
-
-If your problem isn't answered by any of the guides above, there are variety of ways for you to get help from the Kubernetes team.
-
-## Questions
-
-If you aren't familiar with it, many of your questions may be answered by the [user guide](/{{page.version}}/docs/user-guide/).
-
-We also have a number of FAQ pages:
-
-   * [User FAQ](https://github.com/kubernetes/kubernetes/wiki/User-FAQ)
-   * [Debugging FAQ](https://github.com/kubernetes/kubernetes/wiki/Debugging-FAQ)
-   * [Services FAQ](https://github.com/kubernetes/kubernetes/wiki/Services-FAQ)
-
-You may also find the Stack Overflow topics relevant:
-
-   * [Kubernetes](http://stackoverflow.com/questions/tagged/kubernetes)
-   * [Google Container Engine - GKE](http://stackoverflow.com/questions/tagged/google-container-engine)
-
-# Help! My question isn't covered!  I need help now!
-
-## Stack Overflow
-
-Someone else from the community may have already asked a similar question or may be able to help with your problem. The Kubernetes team will also monitor [posts tagged kubernetes](http://stackoverflow.com/questions/tagged/kubernetes). If there aren't any existing questions that help, please [ask a new one](http://stackoverflow.com/questions/ask?tags=kubernetes)!
-
-## <a name="slack"></a>Slack
-
-The Kubernetes team hangs out on Slack in the `#kubernetes-users` channel.  You can participate in the Kubernetes team [here](https://kubernetes.slack.com).  Slack requires registration, but the Kubernetes team is open invitation to anyone to register [here](http://slack.kubernetes.io).  Feel free to come and ask any and all questions.
-
-## Mailing List
-
-The Google Container Engine mailing list is [google-containers@googlegroups.com](https://groups.google.com/forum/#!forum/google-containers)
-
-## Bugs and Feature requests
-
-If you have what looks like a bug, or you would like to make a feature request, please use the [Github issue tracking system](https://github.com/kubernetes/kubernetes/issues).
-
-Before you file an issue, please search existing issues to see if your issue is already covered.
-
-If filing a bug, please include detailed information about how to reproduce the problem, such as:
-
-* Kubernetes version: `kubectl version`
-* Cloud provider, OS distro, network configuration, and Docker version
-* Steps to reproduce the problem
-
-
diff --git a/v1.2/docs/user-guide/application-troubleshooting.md b/v1.2/docs/user-guide/application-troubleshooting.md
deleted file mode 100644
index 9f3ea06aaf..0000000000
--- a/v1.2/docs/user-guide/application-troubleshooting.md
+++ /dev/null
@@ -1,191 +0,0 @@
----
----
-
-This guide is to help users debug applications that are deployed into Kubernetes and not behaving correctly.
-This is *not* a guide for people who want to debug their cluster.  For that you should check out
-[this guide](/{{page.version}}/docs/admin/cluster-troubleshooting)
-
-* TOC
-{:toc}
-
-## FAQ
-
-Users are highly encouraged to check out our [FAQ](https://github.com/kubernetes/kubernetes/wiki/User-FAQ)
-
-## Diagnosing the problem
-
-The first step in troubleshooting is triage.  What is the problem?  Is it your Pods, your Replication Controller or
-your Service?
-
-   * [Debugging Pods](#debugging-pods)
-   * [Debugging Replication Controllers](#debugging-replication-controllers)
-   * [Debugging Services](#debugging-services)
-
-### Debugging Pods
-
-The first step in debugging a Pod is taking a look at it.  Check the current state of the Pod and recent events with the following command:
-
-```shell
-$ kubectl describe pods ${POD_NAME}
-```
-
-Look at the state of the containers in the pod.  Are they all `Running`?  Have there been recent restarts?
-
-Continue debugging depending on the state of the pods.
-
-#### My pod stays pending
-
-If a Pod is stuck in `Pending` it means that it can not be scheduled onto a node.  Generally this is because
-there are insufficient resources of one type or another that prevent scheduling.  Look at the output of the
-`kubectl describe ...` command above.  There should be messages from the scheduler about why it can not schedule
-your pod.  Reasons include:
-
-* **You don't have enough resources**:  You may have exhausted the supply of CPU or Memory in your cluster, in this case
-you need to delete Pods, adjust resource requests, or add new nodes to your cluster. See [Compute Resources document](/{{page.version}}/docs/user-guide/compute-resources/#my-pods-are-pending-with-event-message-failedscheduling) for more information.
-
-* **You are using `hostPort`**:  When you bind a Pod to a `hostPort` there are a limited number of places that pod can be
-scheduled.  In most cases, `hostPort` is unnecessary, try using a Service object to expose your Pod.  If you do require
-`hostPort` then you can only schedule as many Pods as there are nodes in your Kubernetes cluster.
-
-
-#### My pod stays waiting
-
-If a Pod is stuck in the `Waiting` state, then it has been scheduled to a worker node, but it can't run on that machine.
-Again, the information from `kubectl describe ...` should be informative.  The most common cause of `Waiting` pods is a failure to pull the image.  There are three things to check:
-
-* Make sure that you have the name of the image correct
-* Have you pushed the image to the repository?
-* Run a manual `docker pull <image>` on your machine to see if the image can be pulled.
-
-#### My pod is crashing or otherwise unhealthy
-
-First, take a look at the logs of
-the current container:
-
-```shell
-$ kubectl logs ${POD_NAME} ${CONTAINER_NAME}
-```
-
-If your container has previously crashed, you can access the previous container's crash log with:
-
-```shell
-$ kubectl logs --previous ${POD_NAME} ${CONTAINER_NAME}
-```
-
-Alternately, you can run commands inside that container with `exec`:
-
-```shell
-$ kubectl exec ${POD_NAME} -c ${CONTAINER_NAME} -- ${CMD} ${ARG1} ${ARG2} ... ${ARGN}
-```
-
-Note that `-c ${CONTAINER_NAME}` is optional and can be omitted for Pods that only contain a single container.
-
-As an example, to look at the logs from a running Cassandra pod, you might run
-
-```shell
-$ kubectl exec cassandra -- cat /var/log/cassandra/system.log
-```
-
-If none of these approaches work, you can find the host machine that the pod is running on and SSH into that host,
-but this should generally not be necessary given tools in the Kubernetes API. Therefore, if you find yourself needing to ssh into a machine, please file a
-feature request on GitHub describing your use case and why these tools are insufficient.
-
-#### My pod is running but not doing what I told it to do
-
-If your pod is not behaving as you expected, it may be that there was an error in your
-pod description (e.g. `mypod.yaml` file on your local machine), and that the error
-was silently ignored when you created the pod.  Often a section of the pod description
-is nested incorrectly, or a key name is typed incorrectly, and so the key is ignored.
-For example, if you misspelled `command` as `commnd` then the pod will be created but
-will not use the command line you intended it to use.
-
-The first thing to do is to delete your pod and try creating it again with the `--validate` option.
-For example, run `kubectl create --validate -f mypod.yaml`.
-If you misspelled `command` as `commnd` then  will give an error like this:
-
-```shell
-I0805 10:43:25.129850   46757 schema.go:126] unknown field: commnd
-I0805 10:43:25.129973   46757 schema.go:129] this may be a false alarm, see https://github.com/kubernetes/kubernetes/issues/6842
-pods/mypod
-```
-
-<!-- TODO: Now that #11914 is merged, this advice may need to be updated -->
-
-The next thing to check is whether the pod on the apiserver
-matches the pod you meant to create (e.g. in a yaml file on your local machine).
-For example, run `kubectl get pods/mypod -o yaml > mypod-on-apiserver.yaml` and then
-manually compare the original pod description, `mypod.yaml` with the one you got
-back from apiserver, `mypod-on-apiserver.yaml`.  There will typically be some
-lines on the "apiserver" version that are not on the original version.  This is
-expected.  However, if there are lines on the original that are not on the apiserver
-version, then this may indicate a problem with your pod spec.
-
-### Debugging Replication Controllers
-
-Replication controllers are fairly straightforward.  They can either create Pods or they can't.  If they can't
-create pods, then please refer to the [instructions above](#debugging-pods) to debug your pods.
-
-You can also use `kubectl describe rc ${CONTROLLER_NAME}` to introspect events related to the replication
-controller.
-
-### Debugging Services
-
-Services provide load balancing across a set of pods.  There are several common problems that can make Services
-not work properly.  The following instructions should help debug Service problems.
-
-First, verify that there are endpoints for the service. For every Service object, the apiserver makes an `endpoints` resource available.
-
-You can view this resource with:
-
-```shell
-$ kubectl get endpoints ${SERVICE_NAME}
-```
-
-Make sure that the endpoints match up with the number of containers that you expect to be a member of your service.
-For example, if your Service is for an nginx container with 3 replicas, you would expect to see three different
-IP addresses in the Service's endpoints.
-
-#### My service is missing endpoints
-
-If you are missing endpoints, try listing pods using the labels that Service uses.  Imagine that you have
-a Service where the labels are:
-
-```yaml
-...
-spec:
-  - selector:
-     name: nginx
-     type: frontend
-```
-
-You can use:
-
-```shell
-$ kubectl get pods --selector=name=nginx,type=frontend
-```
-
-to list pods that match this selector.  Verify that the list matches the Pods that you expect to provide your Service.
-
-If the list of pods matches expectations, but your endpoints are still empty, it's possible that you don't
-have the right ports exposed.  If your service has a `containerPort` specified, but the Pods that are
-selected don't have that port listed, then they won't be added to the endpoints list.
-
-Verify that the pod's `containerPort` matches up with the Service's `containerPort`
-
-#### Network traffic is not forwarded
-
-If you can connect to the service, but the connection is immediately dropped, and there are endpoints
-in the endpoints list, it's likely that the proxy can't contact your pods.
-
-There are three things to
-check:
-
-   * Are your pods working correctly?  Look for restart count, and [debug pods](#debugging-pods)
-   * Can you connect to your pods directly?  Get the IP address for the Pod, and try to connect directly to that IP
-   * Is your application serving on the port that you configured?  Kubernetes doesn't do port remapping, so if your application serves on 8080, the `containerPort` field needs to be 8080.
-
-#### More information
-
-If none of the above solves your problem, follow the instructions in [Debugging Service document](/{{page.version}}/docs/user-guide/debugging-services) to make sure that your `Service` is running, has `Endpoints`, and your `Pods` are actually serving; you have DNS working, iptables rules installed, and kube-proxy does not seem to be misbehaving.
-
-You may also visit [troubleshooting document](/{{page.version}}/docs/troubleshooting/) for more information.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/compute-resources.md b/v1.2/docs/user-guide/compute-resources.md
deleted file mode 100644
index 533edd866f..0000000000
--- a/v1.2/docs/user-guide/compute-resources.md
+++ /dev/null
@@ -1,249 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-When specifying a [pod](/{{page.version}}/docs/user-guide/pods), you can optionally specify how much CPU and memory (RAM) each
-container needs.  When containers have their resource requests specified, the scheduler is
-able to make better decisions about which nodes to place pods on; and when containers have their
-limits specified, contention for resources on a node can be handled in a specified manner. For
-more details about the difference between requests and limits, please refer to
-[Resource QoS](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/proposals/resource-qos.md).
-
-*CPU* and *memory* are each a *resource type*.  A resource type has a base unit.  CPU is specified
-in units of cores.  Memory is specified in units of bytes.
-
-CPU and RAM are collectively referred to as *compute resources*, or just *resources*.  Compute
-resources are measureable quantities which can be requested, allocated, and consumed.  They are
-distinct from [API resources](/{{page.version}}/docs/user-guide/working-with-resources).  API resources, such as pods and
-[services](/{{page.version}}/docs/user-guide/services) are objects that can be written to and retrieved from the Kubernetes API
-server.
-
-## Resource Requests and Limits of Pod and Container
-
-Each container of a Pod can optionally specify `spec.container[].resources.limits.cpu` and/or
-`spec.container[].resources.limits.memory` and/or `spec.container[].resources.requests.cpu`
-and/or `spec.container[].resources.requests.memory`.
-
-Specifying resource requests and/or limits is optional. In some clusters, unset limits or requests
-may be replaced with default values when a pod is created or updated. The default value depends on
-how the cluster is configured. If value of requests is not specified, they are set to be equal
-to limits by default. Please note that resource limits must be greater than or equal to resource
-requests.
-
-Although requests/limits can only be specified on individual containers, it is convenient to talk
-about pod resource requests/limits.  A *pod resource request/limit* for a particular resource
-type is the sum of the resource requests/limits of that type for each container in the pod, with
-unset values treated as zero (or equal to default values in some cluster configurations).
-
-The following pod has two containers.  Each has a request of 0.25 core of cpu and 64MiB
-(2<sup>20</sup> bytes) of memory and a limit of 0.5 core of cpu and 128MiB of memory. The pod can
-be said to have a request of 0.5 core and 128 MiB of memory and a limit of 1 core and 256MiB of
-memory.
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: frontend
-spec:
-  containers:
-  - name: db
-    image: mysql
-    resources:
-      requests:
-        memory: "64Mi"
-        cpu: "250m"
-      limits:
-        memory: "128Mi"
-        cpu: "500m"
-  - name: wp
-    image: wordpress
-    resources:
-      requests:
-        memory: "64Mi"
-        cpu: "250m"
-      limits:
-        memory: "128Mi"
-        cpu: "500m"
-```
-
-## How Pods with Resource Requests are Scheduled
-
-When a pod is created, the Kubernetes scheduler selects a node for the pod to
-run on.  Each node has a maximum capacity for each of the resource types: the
-amount of CPU and memory it can provide for pods.  The scheduler ensures that,
-for each resource type (CPU and memory), the sum of the resource requests of the
-containers scheduled to the node is less than the capacity of the node.  Note
-that although actual memory or CPU resource usage on nodes is very low, the
-scheduler will still refuse to place pods onto nodes if the capacity check
-fails.  This protects against a resource shortage on a node when resource usage
-later increases, such as due to a daily peak in request rate.
-
-## How Pods with Resource Limits are Run
-
-When kubelet starts a container of a pod, it passes the CPU and memory limits to the container
-runner (Docker or rkt).
-
-When using Docker:
-
-- The `spec.container[].resources.limits.cpu` is multiplied by 1024, converted to an integer, and
-  used as the value of the [`--cpu-shares`](
-  https://docs.docker.com/reference/run/#runtime-constraints-on-resources) flag to the `docker run`
-  command.
-- The `spec.container[].resources.limits.memory` is converted to an integer, and used as the value
-  of the [`--memory`](https://docs.docker.com/reference/run/#runtime-constraints-on-resources) flag
-  to the `docker run` command.
-
-**TODO: document behavior for rkt**
-
-If a container exceeds its memory limit, it may be terminated.  If it is restartable, it will be
-restarted by kubelet, as will any other type of runtime failure.
-
-A container may or may not be allowed to exceed its CPU limit for extended periods of time.
-However, it will not be killed for excessive CPU usage.
-
-To determine if a container cannot be scheduled or is being killed due to resource limits, see the
-"Troubleshooting" section below.
-
-## Monitoring Compute Resource Usage
-
-The resource usage of a pod is reported as part of the Pod status.
-
-If [optional monitoring](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/README.md) is configured for your cluster,
-then pod resource usage can be retrieved from the monitoring system.
-
-## Troubleshooting
-
-### My pods are pending with event message failedScheduling
-
-If the scheduler cannot find any node where a pod can fit, then the pod will remain unscheduled
-until a place can be found.    An event will be produced each time the scheduler fails to find a
-place for the pod, like this:
-
-```shell
-$ kubectl describe pod frontend | grep -A 3 Events
-Events:
-  FirstSeen	LastSeen	 Count	From          Subobject   PathReason			Message
-  36s		5s		 6	    {scheduler }              FailedScheduling	Failed for reason PodExceedsFreeCPU and possibly others
-```
-
-In the case shown above, the pod "frontend" fails to be scheduled due to insufficient
-CPU resource on the node. Similar error messages can also suggest failure due to insufficient
-memory (PodExceedsFreeMemory). In general, if a pod or pods are pending with this message and
-alike, then there are several things to try:
-
-- Add more nodes to the cluster.
-- Terminate unneeded pods to make room for pending pods.
-- Check that the pod is not larger than all the nodes.  For example, if all the nodes
-have a capacity of `cpu: 1`, then a pod with a limit of `cpu: 1.1` will never be scheduled.
-
-You can check node capacities and amounts allocated with the `kubectl describe nodes` command.
-For example:
-
-```shell
-$ kubectl describe nodes gke-cluster-4-386701dd-node-ww4p
-Name:			gke-cluster-4-386701dd-node-ww4p
-[ ... lines removed for clarity ...]
-Capacity:
- cpu:		1
- memory:	464Mi
- pods:		40
-Allocated resources (total requests):
- cpu:		910m
- memory:	2370Mi
- pods:		4
-[ ... lines removed for clarity ...]
-Pods:				(4 in total)
-  Namespace			Name								CPU(milliCPU)			Memory(bytes)
-  frontend 			webserver-ffj8j							500 (50% of total)		2097152000 (50% of total)
-  kube-system			fluentd-cloud-logging-gke-cluster-4-386701dd-node-ww4p		100 (10% of total)		209715200 (5% of total)
-  kube-system			kube-dns-v8-qopgw						310 (31% of total)		178257920 (4% of total)
-TotalResourceLimits:
-  CPU(milliCPU):		910 (91% of total)
-  Memory(bytes):		2485125120 (59% of total)
-[ ... lines removed for clarity ...]
-```
-
-Here you can see from the `Allocated resources` section that that a pod which ask for more than
-90 millicpus or more than 1341MiB of memory will not be able to fit on this node.
-
-Looking at the `Pods` section, you can see which pods are taking up space on the node.
-
-The [resource quota](/{{page.version}}/docs/admin/resource-quota) feature can be configured
-to limit the total amount of resources that can be consumed.  If used in conjunction
-with namespaces, it can prevent one team from hogging all the resources.
-
-### My container is terminated
-
-Your container may be terminated because it's resource-starved. To check if a container is being killed because it is hitting a resource limit, call `kubectl describe pod`
-on the pod you are interested in:
-
-```shell
-[12:54:41] $ ./cluster/kubectl.sh describe pod simmemleak-hra99
-Name:                           simmemleak-hra99
-Namespace:                      default
-Image(s):                       saadali/simmemleak
-Node:                           kubernetes-minion-tf0f/10.240.216.66
-Labels:                         name=simmemleak
-Status:                         Running
-Reason:             
-Message:            
-IP:                             10.244.2.75
-Replication Controllers:        simmemleak (1/1 replicas created)
-Containers:
-  simmemleak:
-    Image:  saadali/simmemleak
-    Limits:
-      cpu:                      100m
-      memory:                   50Mi
-    State:                      Running
-      Started:                  Tue, 07 Jul 2015 12:54:41 -0700
-    Last Termination State:     Terminated
-      Exit Code:                1
-      Started:                  Fri, 07 Jul 2015 12:54:30 -0700
-      Finished:                 Fri, 07 Jul 2015 12:54:33 -0700
-    Ready:                      False
-    Restart Count:              5
-Conditions:
-  Type      Status
-  Ready     False 
-Events:
-  FirstSeen                         LastSeen                         Count  From                              SubobjectPath                       Reason      Message
-  Tue, 07 Jul 2015 12:53:51 -0700   Tue, 07 Jul 2015 12:53:51 -0700  1      {scheduler }                                                          scheduled   Successfully assigned simmemleak-hra99 to kubernetes-minion-tf0f
-  Tue, 07 Jul 2015 12:53:51 -0700   Tue, 07 Jul 2015 12:53:51 -0700  1      {kubelet kubernetes-minion-tf0f}  implicitly required container POD   pulled      Pod container image "gcr.io/google_containers/pause:0.8.0" already present on machine
-  Tue, 07 Jul 2015 12:53:51 -0700   Tue, 07 Jul 2015 12:53:51 -0700  1      {kubelet kubernetes-minion-tf0f}  implicitly required container POD   created     Created with docker id 6a41280f516d
-  Tue, 07 Jul 2015 12:53:51 -0700   Tue, 07 Jul 2015 12:53:51 -0700  1      {kubelet kubernetes-minion-tf0f}  implicitly required container POD   started     Started with docker id 6a41280f516d
-  Tue, 07 Jul 2015 12:53:51 -0700   Tue, 07 Jul 2015 12:53:51 -0700  1      {kubelet kubernetes-minion-tf0f}  spec.containers{simmemleak}         created     Created with docker id 87348f12526a
-```
-
-The `Restart Count:  5` indicates that the `simmemleak` container in this pod was terminated and restarted 5 times.
-
-You can call `get pod` with the `-o go-template=...` option to fetch the status of previously terminated containers:
-
-```shell
-[13:59:01] $ ./cluster/kubectl.sh  get pod -o go-template='{{range.status.containerStatuses}}{{"Container Name: "}}{{.name}}{{"\r\nLastState: "}}{{.lastState}}{{end}}'  simmemleak-60xbc
-Container Name: simmemleak
-LastState: map[terminated:map[exitCode:137 reason:OOM Killed startedAt:2015-07-07T20:58:43Z finishedAt:2015-07-07T20:58:43Z containerID:docker://0e4095bba1feccdfe7ef9fb6ebffe972b4b14285d5acdec6f0d3ae8a22fad8b2]][13:59:03] clusterScaleDoc ~/go/src/github.com/kubernetes/kubernetes $ 
-```
-
-We can see that this container was terminated because `reason:OOM Killed`, where *OOM* stands for Out Of Memory.
-
-## Planned Improvements
-
-The current system only allows resource quantities to be specified on a container.
-It is planned to improve accounting for resources which are shared by all containers in a pod,
-such as [EmptyDir volumes](/{{page.version}}/docs/user-guide/volumes/#emptydir).
-
-The current system only supports container requests and limits for CPU and Memory.
-It is planned to add new resource types, including a node disk space
-resource, and a framework for adding custom [resource types](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/resources.md#resource-types).
-
-Kubernetes supports overcommitment of resources by supporting multiple levels of [Quality of Service](http://issue.k8s.io/168).
-
-Currently, one unit of CPU means different things on different cloud providers, and on different
-machine types within the same cloud providers.  For example, on AWS, the capacity of a node
-is reported in [ECUs](http://aws.amazon.com/ec2/faqs/), while in GCE it is reported in logical
-cores.  We plan to revise the definition of the cpu resource to allow for more consistency
-across providers and platforms.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/connecting-applications.md b/v1.2/docs/user-guide/connecting-applications.md
deleted file mode 100644
index 0788094ec3..0000000000
--- a/v1.2/docs/user-guide/connecting-applications.md
+++ /dev/null
@@ -1,386 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-# The Kubernetes model for connecting containers
-
-Now that you have a continuously running, replicated application you can expose it on a network. Before discussing the Kubernetes approach to networking, it is worthwhile to contrast it with the "normal" way networking works with Docker.
-
-By default, Docker uses host-private networking, so containers can talk to other containers only if they are on the same machine. In order for Docker containers to communicate across nodes, they must be allocated ports on the machine's own IP address, which are then forwarded or proxied to the containers. This obviously means that containers must either coordinate which ports they use very carefully or else be allocated ports dynamically.
-
-Coordinating ports across multiple developers is very difficult to do at scale and exposes users to cluster-level issues outside of their control. Kubernetes assumes that pods can communicate with other pods, regardless of which host they land on. We give every pod its own cluster-private-IP address so you do not need to explicitly create links between pods or mapping container ports to host ports. This means that containers within a Pod can all reach each other's ports on localhost, and all pods in a cluster can see each other without NAT. The rest of this document will elaborate on how you can run reliable services on such a networking model.
-
-This guide uses a simple nginx server to demonstrate proof of concept. The same principles are embodied in a more complete [Jenkins CI application](http://blog.kubernetes.io/2015/07/strong-simple-ssl-for-kubernetes).
-
-## Exposing pods to the cluster
-
-We did this in a previous example, but lets do it once again and focus on the networking perspective. Create an nginx pod, and note that it has a container port specification:
-
-```yaml
-$ cat nginxrc.yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx
-spec:
-  replicas: 2
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        ports:
-        - containerPort: 80
-```
-
-This makes it accessible from any node in your cluster. Check the nodes the pod is running on:
-
-```shell
-$ kubectl create -f ./nginxrc.yaml
-$ kubectl get pods -l app=nginx -o wide
-my-nginx-6isf4   1/1       Running   0          2h        e2e-test-beeps-minion-93ly
-my-nginx-t26zt   1/1       Running   0          2h        e2e-test-beeps-minion-93ly
-```
-
-Check your pods' IPs:
-
-```shell
-$ kubectl get pods -l app=nginx -o json | grep podIP
-                "podIP": "10.245.0.15",
-                "podIP": "10.245.0.14",
-```
-
-You should be able to ssh into any node in your cluster and curl both IPs. Note that the containers are *not* using port 80 on the node, nor are there any special NAT rules to route traffic to the pod. This means you can run multiple nginx pods on the same node all using the same containerPort and access them from any other pod or node in your cluster using IP. Like Docker, ports can still be published to the host node's interface(s), but the need for this is radically diminished because of the networking model.
-
-You can read more about [how we achieve this](/{{page.version}}/docs/admin/networking/#how-to-achieve-this) if you're curious.
-
-## Creating a Service
-
-So we have pods running nginx in a flat, cluster wide, address space. In theory, you could talk to these pods directly, but what happens when a node dies? The pods die with it, and the replication controller will create new ones, with different IPs. This is the problem a Service solves.
-
-A Kubernetes Service is an abstraction which defines a logical set of Pods running somewhere in your cluster, that all provide the same functionality. When created, each Service is assigned a unique IP address (also called clusterIP). This address is tied to the lifespan of the Service, and will not change while the Service is alive. Pods can be configured to talk to the Service, and know that communication to the Service will be automatically load-balanced out to some pod that is a member of the Service.
-
-You can create a Service for your 2 nginx replicas with the following yaml:
-
-```yaml
-$ cat nginxsvc.yaml
-apiVersion: v1
-kind: Service
-metadata:
-  name: nginxsvc
-  labels:
-    app: nginx
-spec:
-  ports:
-  - port: 80
-    protocol: TCP
-  selector:
-    app: nginx
-```
-
-This specification will create a Service which targets TCP port 80 on any Pod with the `app=nginx` label, and expose it on an abstracted Service port (`targetPort`: is the port the container accepts traffic on, `port`: is the abstracted Service port, which can be any port other pods use to access the Service). View [service API object](http://kubernetes.io/v1.1/docs/api-reference/v1/definitions/#_v1_service) to see the list of supported fields in service definition.
-Check your Service:
-
-```shell
-$ kubectl get svc
-NAME         CLUSTER_IP       EXTERNAL_IP       PORT(S)                SELECTOR     AGE
-kubernetes   10.179.240.1     <none>            443/TCP                <none>       8d
-nginxsvc     10.179.252.126   122.222.183.144   80/TCP,81/TCP,82/TCP   run=nginx2   11m
-```
-
-As mentioned previously, a Service is backed by a group of pods. These pods are exposed through `endpoints`. The Service's selector will be evaluated continuously and the results will be POSTed to an Endpoints object also named `nginxsvc`. When a pod dies, it is automatically removed from the endpoints, and new pods matching the Service's selector will automatically get added to the endpoints. Check the endpoints, and note that the IPs are the same as the pods created in the first step:
-
-```shell
-$ kubectl describe svc nginxsvc
-Name:			nginxsvc
-Namespace:		default
-Labels:			app=nginx
-Selector:		app=nginx
-Type:			ClusterIP
-IP:			10.0.116.146
-Port:			<unnamed>	80/TCP
-Endpoints:		10.245.0.14:80,10.245.0.15:80
-Session Affinity:	None
-No events.
-
-$ kubectl get ep
-NAME         ENDPOINTS
-nginxsvc     10.245.0.14:80,10.245.0.15:80
-```
-
-You should now be able to curl the nginx Service on `10.0.116.146:80` from any node in your cluster. Note that the Service IP is completely virtual, it never hits the wire, if you're curious about how this works you can read more about the [service proxy](/{{page.version}}/docs/user-guide/services/#virtual-ips-and-service-proxies).
-
-## Accessing the Service
-
-Kubernetes supports 2 primary modes of finding a Service - environment variables and DNS. The former works out of the box while the latter requires the [kube-dns cluster addon](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/README.md).
-
-### Environment Variables
-
-When a Pod is run on a Node, the kubelet adds a set of environment variables for each active Service. This introduces an ordering problem. To see why, inspect the environment of your running nginx pods:
-
-```shell
-$ kubectl exec my-nginx-6isf4 -- printenv | grep SERVICE
-KUBERNETES_SERVICE_HOST=10.0.0.1
-KUBERNETES_SERVICE_PORT=443
-```
-
-Note there's no mention of your Service. This is because you created the replicas before the Service. Another disadvantage of doing this is that the scheduler might put both pods on the same machine, which will take your entire Service down if it dies. We can do this the right way by killing the 2 pods and waiting for the replication controller to recreate them. This time around the Service exists *before* the replicas. This will given you scheduler level Service spreading of your pods (provided all your nodes have equal capacity), as well as the right environment variables:
-
-```shell
-$ kubectl scale rc my-nginx --replicas=0; kubectl scale rc my-nginx --replicas=2;
-$ kubectl get pods -l app=nginx -o wide
-NAME             READY   STATUS     RESTARTS   AGE   NODE
-my-nginx-5j8ok   1/1     Running   	0         2m    node1
-my-nginx-90vaf   1/1     Running   0          2m    node2
-
-$ kubectl exec my-nginx-5j8ok -- printenv | grep SERVICE
-KUBERNETES_SERVICE_PORT=443
-NGINXSVC_SERVICE_HOST=10.0.116.146
-KUBERNETES_SERVICE_HOST=10.0.0.1
-NGINXSVC_SERVICE_PORT=80
-```
-
-### DNS
-
-Kubernetes offers a DNS cluster addon Service that uses skydns to automatically assign dns names to other Services. You can check if it's running on your cluster:
-
-```shell
-$ kubectl get services kube-dns --namespace=kube-system
-NAME       CLUSTER_IP      EXTERNAL_IP   PORT(S)         SELECTOR           AGE
-kube-dns   10.179.240.10   <none>        53/UDP,53/TCP   k8s-app=kube-dns   8d
-```
-
-If it isn't running, you can [enable it](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/README.md#how-do-i-configure-it). The rest of this section will assume you have a Service with a long lived IP (nginxsvc), and a dns server that has assigned a name to that IP (the kube-dns cluster addon), so you can talk to the Service from any pod in your cluster using standard methods (e.g. gethostbyname). Let's create another pod to test this:
-
-```yaml
-$ cat curlpod.yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: curlpod
-spec:
-  containers:
-  - image: radial/busyboxplus:curl
-    command:
-      - sleep
-      - "3600"
-    imagePullPolicy: IfNotPresent
-    name: curlcontainer
-  restartPolicy: Always
-```
-
-And perform a lookup of the nginx Service
-
-```shell
-$ kubectl create -f ./curlpod.yaml
-default/curlpod
-$ kubectl get pods curlpod
-NAME      READY     STATUS    RESTARTS   AGE
-curlpod   1/1       Running   0          18s
-
-$ kubectl exec curlpod -- nslookup nginxsvc
-Server:    10.0.0.10
-Address 1: 10.0.0.10
-Name:      nginxsvc
-Address 1: 10.0.116.146
-```
-
-## Securing the Service
-
-Till now we have only accessed the nginx server from within the cluster. Before exposing the Service to the internet, you want to make sure the communication channel is secure. For this, you will need:
-
-* Self signed certificates for https (unless you already have an identity certificate)
-* An nginx server configured to use the certificates
-* A [secret](/{{page.version}}/docs/user-guide/secrets) that makes the certificates accessible to pods
-
-You can acquire all these from the [nginx https example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/https-nginx/), in short:
-
-```shell
-$ make keys secret KEY=/tmp/nginx.key CERT=/tmp/nginx.crt SECRET=/tmp/secret.json
-$ kubectl create -f /tmp/secret.json
-secrets/nginxsecret
-$ kubectl get secrets
-NAME                  TYPE                                  DATA
-default-token-il9rc   kubernetes.io/service-account-token   1
-nginxsecret           Opaque                                2
-```
-
-Now modify your nginx replicas to start a https server using the certificate in the secret, and the Service, to expose both ports (80 and 443):
-
-```yaml
-$ cat nginx-app.yaml
-apiVersion: v1
-kind: Service
-metadata:
-  name: nginxsvc
-  labels:
-    app: nginx
-spec:
-  type: NodePort
-  ports:
-  - port: 8080
-    targetPort: 80
-    protocol: TCP
-    name: http
-  - port: 443
-    protocol: TCP
-    name: https
-  selector:
-    app: nginx
----
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx
-spec:
-  replicas: 1
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      volumes:
-      - name: secret-volume
-        secret:
-          secretName: nginxsecret
-      containers:
-      - name: nginxhttps
-        image: bprashanth/nginxhttps:1.0
-        ports:
-        - containerPort: 443
-        - containerPort: 80
-        volumeMounts:
-        - mountPath: /etc/nginx/ssl
-          name: secret-volume
-```
-
-Noteworthy points about the nginx-app manifest:
-
-- It contains both rc and service specification in the same file
-- The [nginx server](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/https-nginx/default.conf) serves http traffic on port 80 and https traffic on 443, and nginx Service exposes both ports.
-- Each container has access to the keys through a volume mounted at /etc/nginx/ssl. This is setup *before* the nginx server is started.
-
-```shell
-$ kubectl delete rc,svc -l app=nginx; kubectl create -f ./nginx-app.yaml
-replicationcontrollers/my-nginx
-services/nginxsvc
-services/nginxsvc
-replicationcontrollers/my-nginx
-```
-
-At this point you can reach the nginx server from any node.
-
-```shell
-$ kubectl get pods -o json | grep -i podip
-    "podIP": "10.1.0.80",
-node $ curl -k https://10.1.0.80
-...
-<h1>Welcome to nginx!</h1>
-```
-
-Note how we supplied the `-k` parameter to curl in the last step, this is because we don't know anything about the pods running nginx at certificate generation time,
-so we have to tell curl to ignore the CName mismatch. By creating a Service we linked the CName used in the certificate with the actual DNS name used by pods during Service lookup.
-Lets test this from a pod (the same secret is being reused for simplicity, the pod only needs nginx.crt to access the Service):
-
-```shell
-$ cat curlpod.yaml
-vapiVersion: v1
-kind: ReplicationController
-metadata:
-  name: curlrc
-spec:
-  replicas: 1
-  template:
-    metadata:
-      labels:
-        app: curlpod
-    spec:
-      volumes:
-      - name: secret-volume
-        secret:
-          secretName: nginxsecret
-      containers:
-      - name: curlpod
-        command:
-        - sh
-        - -c
-        - while true; do sleep 1; done
-        image: radial/busyboxplus:curl
-        volumeMounts:
-        - mountPath: /etc/nginx/ssl
-          name: secret-volume
-
-$ kubectl create -f ./curlpod.yaml
-$ kubectl get pods
-NAME             READY     STATUS    RESTARTS   AGE
-curlpod          1/1       Running   0          2m
-my-nginx-7006w   1/1       Running   0          24m
-
-$ kubectl exec curlpod -- curl https://nginxsvc --cacert /etc/nginx/ssl/nginx.crt
-...
-<title>Welcome to nginx!</title>
-...
-```
-
-## Exposing the Service
-
-For some parts of your applications you may want to expose a Service onto an external IP address. Kubernetes supports two ways of doing this: NodePorts and LoadBalancers. The Service created in the last section already used `NodePort`, so your nginx https replica is ready to serve traffic on the internet if your node has a public IP.
-
-```shell
-$ kubectl get svc nginxsvc -o json | grep -i nodeport -C 5
-            {
-                "name": "http",
-                "protocol": "TCP",
-                "port": 80,
-                "targetPort": 80,
-                "nodePort": 32188
-            },
-            {
-                "name": "https",
-                "protocol": "TCP",
-                "port": 443,
-                "targetPort": 443,
-                "nodePort": 30645
-            }
-
-$ kubectl get nodes -o json | grep ExternalIP -C 2
-                    {
-                        "type": "ExternalIP",
-                        "address": "104.197.63.17"
-                    }
---
-                    },
-                    {
-                        "type": "ExternalIP",
-                        "address": "104.154.89.170"
-                    }
-$ curl https://104.197.63.17:30645 -k
-...
-<h1>Welcome to nginx!</h1>
-```
-
-Lets now recreate the Service to use a cloud load balancer, just change the `Type` of Service in the nginx-app.yaml from `NodePort` to `LoadBalancer`:
-
-```shell
-$ kubectl delete rc, svc -l app=nginx
-$ kubectl create -f ./nginx-app.yaml
-$ kubectl get svc nginxsvc
-NAME      CLUSTER_IP       EXTERNAL_IP       PORT(S)                SELECTOR     AGE
-nginxsvc  10.179.252.126   162.222.184.144   80/TCP,81/TCP,82/TCP   run=nginx2   13m
-
-$ curl https://162.22.184.144 -k
-...
-<title>Welcome to nginx!</title>
-```
-
-The IP address in the `EXTERNAL_IP` column is the one that is available on the public internet.  The `CLUSTER_IP` is only available inside your
-cluster/private cloud network.
-
-## What's next?
-
-[Learn about more Kubernetes features that will help you run containers reliably in production.](/{{page.version}}/docs/user-guide/production-pods)
diff --git a/v1.2/docs/user-guide/connecting-to-applications-port-forward.md b/v1.2/docs/user-guide/connecting-to-applications-port-forward.md
deleted file mode 100644
index c74dfaa0c5..0000000000
--- a/v1.2/docs/user-guide/connecting-to-applications-port-forward.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
----
-
-kubectl port-forward forwards connections to a local port to a port on a pod. Its man page is available [here](/{{page.version}}/docs/user-guide/kubectl/kubectl_port-forward). Compared to [kubectl proxy](/{{page.version}}/docs/user-guide/accessing-the-cluster/#using-kubectl-proxy), `kubectl port-forward` is more generic as it can forward TCP traffic while `kubectl proxy` can only forward HTTP traffic. This guide demonstrates how to use `kubectl port-forward` to connect to a Redis database, which may be useful for database debugging.
-
-## Creating a Redis master
-
-```shell
-$ kubectl create examples/redis/redis-master.yaml
-pods/redis-master
-```
-
-wait until the Redis master pod is Running and Ready,
-
-```shell
-$ kubectl get pods
-NAME           READY     STATUS    RESTARTS   AGE
-redis-master   2/2       Running   0          41s
-```
-
-## Connecting to the Redis master[a]
-
-The Redis master is listening on port 6397, to verify this,
-
-```shell
-$ kubectl get pods redis-master -t='{{(index (index .spec.containers 0).ports 0).containerPort}}{{"\n"}}'
-6379
-```
-
-then we forward the port 6379 on the local workstation to the port 6379 of pod redis-master,
-
-```shell
-$ kubectl port-forward redis-master 6379:6379
-I0710 14:43:38.274550    3655 portforward.go:225] Forwarding from 127.0.0.1:6379 -> 6379
-I0710 14:43:38.274797    3655 portforward.go:225] Forwarding from [::1]:6379 -> 6379
-```
-
-To verify the connection is successful, we run a redis-cli on the local workstation,
-
-```shell
-$ redis-cli
-127.0.0.1:6379> ping
-PONG
-```
-
-Now one can debug the database from the local workstation.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/containers.md b/v1.2/docs/user-guide/containers.md
deleted file mode 100644
index 215a87430c..0000000000
--- a/v1.2/docs/user-guide/containers.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## Containers and commands
-
-So far the Pods we've seen have all used the `image` field to indicate what process Kubernetes
-should run in a container.  In this case, Kubernetes runs the image's default command.  If we want
-to run a particular command or override the image's defaults, there are two additional fields that
-we can use:
-
-1.  `Command`: Controls the actual command run by the image
-2.  `Args`: Controls the arguments passed to the command
-
-### How docker handles command and arguments
-
-Docker images have metadata associated with them that is used to store information about the image.
-The image author may use this to define defaults for the command and arguments to run a container
-when the user does not supply values. Docker calls the fields for commands and arguments
-`Entrypoint` and `Cmd` respectively. The full details for this feature are too complicated to
-describe here, mostly due to the fact that the Docker API allows users to specify both of these
-fields as either a string array or a string and there are subtle differences in how those cases are
-handled.  We encourage the curious to check out Docker's documentation for this feature.
-
-Kubernetes allows you to override both the image's default command (docker `Entrypoint`) and args
-(docker `Cmd`) with the `Command` and `Args` fields of `Container`.  The rules are:
-
-1.  If you do not supply a `Command` or `Args` for a container, the defaults defined by the image
-    will be used
-2.  If you supply a `Command` but no `Args` for a container, only the supplied `Command` will be
-    used; the image's default arguments are ignored
-3.  If you supply only `Args`, the image's default command will be used with the arguments you
-    supply
-4.  If you supply a `Command` **and** `Args`, the image's defaults will be ignored and the values
-    you supply will be used
-
-Here are examples for these rules in table format
-
-| Image `Entrypoint` |    Image `Cmd`   | Container `Command` |  Container `Args`  |    Command Run   |
-|--------------------|------------------|---------------------|--------------------|------------------|
-|     `[/ep-1]`      |   `[foo bar]`    |   &lt;not set&gt;   |   &lt;not set&gt;  | `[ep-1 foo bar]` |
-|     `[/ep-1]`      |   `[foo bar]`    |      `[/ep-2]`      |   &lt;not set&gt;  |     `[ep-2]`     |
-|     `[/ep-1]`      |   `[foo bar]`    |   &lt;not set&gt;   |     `[zoo boo]`    | `[ep-1 zoo boo]` |
-|     `[/ep-1]`      |   `[foo bar]`    |      `[/ep-2]`      |     `[zoo boo]`    | `[ep-2 zoo boo]` |
-
-
-## Capabilities
-
-By default, Docker containers are "unprivileged" and cannot, for example, run a Docker daemon inside a Docker container. We can have fine grain control over the capabilities using cap-add and cap-drop.More details [here](https://docs.docker.com/reference/run/#runtime-privilege-linux-capabilities-and-lxc-configuration).
-
-The relationship between Docker's capabilities and [Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7)
-
-| Docker's capabilities | Linux capabilities |
-| ---- | ---- |
-| SETPCAP |  CAP_SETPCAP |
-| SYS_MODULE |  CAP_SYS_MODULE |
-| SYS_RAWIO |  CAP_SYS_RAWIO |
-| SYS_PACCT |  CAP_SYS_PACCT |
-| SYS_ADMIN |  CAP_SYS_ADMIN |
-| SYS_NICE |  CAP_SYS_NICE |
-| SYS_RESOURCE |  CAP_SYS_RESOURCE |
-| SYS_TIME |  CAP_SYS_TIME |
-| SYS_TTY_CONFIG |  CAP_SYS_TTY_CONFIG |
-| MKNOD |  CAP_MKNOD |
-| AUDIT_WRITE |  CAP_AUDIT_WRITE |
-| AUDIT_CONTROL |  CAP_AUDIT_CONTROL |
-| MAC_OVERRIDE |  CAP_MAC_OVERRIDE |
-| MAC_ADMIN |  CAP_MAC_ADMIN |
-| NET_ADMIN |  CAP_NET_ADMIN |
-| SYSLOG |  CAP_SYSLOG |
-| CHOWN |  CAP_CHOWN |
-| NET_RAW |  CAP_NET_RAW |
-| DAC_OVERRIDE |  CAP_DAC_OVERRIDE |
-| FOWNER |  CAP_FOWNER |
-| DAC_READ_SEARCH |  CAP_DAC_READ_SEARCH |
-| FSETID |  CAP_FSETID |
-| KILL |  CAP_KILL |
-| SETGID |  CAP_SETGID |
-| SETUID |  CAP_SETUID |
-| LINUX_IMMUTABLE |  CAP_LINUX_IMMUTABLE |
-| NET_BIND_SERVICE |  CAP_NET_BIND_SERVICE |
-| NET_BROADCAST |  CAP_NET_BROADCAST |
-| IPC_LOCK |  CAP_IPC_LOCK |
-| IPC_OWNER |  CAP_IPC_OWNER |
-| SYS_CHROOT |  CAP_SYS_CHROOT |
-| SYS_PTRACE |  CAP_SYS_PTRACE |
-| SYS_BOOT |  CAP_SYS_BOOT |
-| LEASE |  CAP_LEASE |
-| SETFCAP |  CAP_SETFCAP |
-| WAKE_ALARM |  CAP_WAKE_ALARM |
-| BLOCK_SUSPEND |  CAP_BLOCK_SUSPEND |
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/debugging-services.md b/v1.2/docs/user-guide/debugging-services.md
deleted file mode 100644
index b0aea4739b..0000000000
--- a/v1.2/docs/user-guide/debugging-services.md
+++ /dev/null
@@ -1,503 +0,0 @@
----
----
-
-An issue that comes up rather frequently for new installations of Kubernetes is
-that `Services` are not working properly.  You've run all your `Pod`s and
-`ReplicationController`s, but you get no response when you try to access them.
-This document will hopefully help you to figure out what's going wrong.
-
-* TOC
-{:toc}
-
-
-## Conventions
-
-Throughout this doc you will see various commands that you can run.  Some
-commands need to be run within `Pod`, others on a Kubernetes `Node`, and others
-can run anywhere you have `kubectl` and credentials for the cluster.  To make it
-clear what is expected, this document will use the following conventions.
-
-If the command "COMMAND" is expected to run in a `Pod` and produce "OUTPUT":
-
-```shell
-u@pod$ COMMAND
-OUTPUT
-```
-
-If the command "COMMAND" is expected to run on a `Node` and produce "OUTPUT":
-
-```shell
-u@node$ COMMAND
-OUTPUT
-```
-
-If the command is "kubectl ARGS":
-
-```shell
-$ kubectl ARGS
-OUTPUT
-```
-
-## Running commands in a Pod
-
-For many steps here you will want to see what a `Pod` running in the cluster
-sees.  Kubernetes does not directly support interactive `Pod`s (yet), but you can
-approximate it:
-
-```shell
-$ cat <<EOF | kubectl create -f -
-apiVersion: v1
-kind: Pod
-metadata:
-  name: busybox-sleep
-spec:
-  containers:
-  - name: busybox
-    image: busybox
-    args:
-    - sleep
-    - "1000000"
-EOF
-pods/busybox-sleep
-```
-
-Now, when you need to run a command (even an interactive shell) in a `Pod`-like
-context, use:
-
-```shell
-$ kubectl exec busybox-sleep -- <COMMAND>
-```
-
-or
-
-```shell
-$ kubectl exec -ti busybox-sleep sh
-/ #
-```
-
-## Setup
-
-For the purposes of this walk-through, let's run some `Pod`s.  Since you're
-probably debugging your own `Service` you can substitute your own details, or you
-can follow along and get a second data point.
-
-```shell
-$ kubectl run hostnames --image=gcr.io/google_containers/serve_hostname \
-                        --labels=app=hostnames \
-                        --port=9376 \
-                        --replicas=3
-CONTROLLER   CONTAINER(S)   IMAGE(S)                                  SELECTOR        REPLICAS
-hostnames    hostnames      gcr.io/google_containers/serve_hostname   app=hostnames   3
-```
-
-Note that this is the same as if you had started the `ReplicationController` with
-the following YAML:
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: hostnames
-spec:
-  selector:
-    app: hostnames
-  replicas: 3
-  template:
-    metadata:
-      labels:
-        app: hostnames
-    spec:
-      containers:
-      - name: hostnames
-        image: gcr.io/google_containers/serve_hostname
-        ports:
-        - containerPort: 9376
-          protocol: TCP
-```
-
-Confirm your `Pod`s are running:
-
-```shell
-$ kubectl get pods -l app=hostnames
-NAME              READY     STATUS    RESTARTS   AGE
-hostnames-0uton   1/1       Running   0          12s
-hostnames-bvc05   1/1       Running   0          12s
-hostnames-yp2kp   1/1       Running   0          12s
-```
-
-## Does the Service exist?
-
-The astute reader will have noticed that we did not actually create a `Service`
-yet - that is intentional.  This is a step that sometimes gets forgotten, and
-is the first thing to check.
-
-So what would happen if I tried to access a non-existent `Service`?  Assuming you
-have another `Pod` that consumes this `Service` by name you would get something
-like:
-
-```shell
-u@pod$ wget -qO- hostnames
-wget: bad address 'hostname'
-```
-
-or:
-
-```shell
-u@pod$ echo $HOSTNAMES_SERVICE_HOST
-```
-
-So the first thing to check is whether that `Service` actually exists:
-
-```shell
-$ kubectl get svc hostnames
-Error from server: service "hostnames" not found
-```
-
-So we have a culprit, let's create the `Service`.  As before, this is for the
-walk-through - you can use your own `Service`'s details here.
-
-```shell
-$ kubectl expose rc hostnames --port=80 --target-port=9376
-service "hostnames" exposed
-```
-
-And read it back, just to be sure:
-
-```shell
-$ kubectl get svc hostnames
-NAME              CLUSTER_IP       EXTERNAL_IP       PORT(S)       SELECTOR               AGE
-hostnames         10.0.0.1         <none>            80/TCP        run=hostnames          1h
-```
-
-As before, this is the same as if you had started the `Service` with YAML:
-
-```yaml
-apiVersion: v1
-kind: Service
-metadata:
-  name: hostnames
-spec:
-  selector:
-    app: hostnames
-  ports:
-  - name: default
-    protocol: TCP
-    port: 80
-    targetPort: 9376
-```
-
-Now you can confirm that the `Service` exists.
-
-## Does the Service work by DNS?
-
-From a `Pod` in the same `Namespace`:
-
-```shell
-u@pod$ nslookup hostnames
-Server:         10.0.0.10
-Address:        10.0.0.10#53
-
-Name:   hostnames
-Address: 10.0.1.175
-```
-
-If this fails, perhaps your `Pod` and `Service` are in different
-`Namespace`s, try a namespace-qualified name:
-
-```shell
-u@pod$ nslookup hostnames.default
-Server:         10.0.0.10
-Address:        10.0.0.10#53
-
-Name:   hostnames.default
-Address: 10.0.1.175
-```
-
-If this works, you'll need to ensure that `Pod`s and `Service`s run in the same
-`Namespace`.  If this still fails, try a fully-qualified name:
-
-```shell
-u@pod$ nslookup hostnames.default.svc.cluster.local
-Server:         10.0.0.10
-Address:        10.0.0.10#53
-
-Name:   hostnames.default.svc.cluster.local
-Address: 10.0.1.175
-```
-
-Note the suffix here: "default.svc.cluster.local".  The "default" is the
-`Namespace` we're operating in.  The "svc" denotes that this is a `Service`.
-The "cluster.local" is your cluster domain.
-
-You can also try this from a `Node` in the cluster (note: 10.0.0.10 is my DNS
-`Service`):
-
-```shell
-u@node$ nslookup hostnames.default.svc.cluster.local 10.0.0.10
-Server:         10.0.0.10
-Address:        10.0.0.10#53
-
-Name:   hostnames.default.svc.cluster.local
-Address: 10.0.1.175
-```
-
-If you are able to do a fully-qualified name lookup but not a relative one, you
-need to check that your `kubelet` is running with the right flags.
-The `--cluster-dns` flag needs to point to your DNS `Service`'s IP and the
-`--cluster-domain` flag needs to be your cluster's domain - we assumed
-"cluster.local" in this document, but yours might be different, in which case
-you should change that in all of the commands above.
-
-### Does any Service exist in DNS?
-
-If the above still fails - DNS lookups are not working for your `Service` - we
-can take a step back and see what else is not working.  The Kubernetes master
-`Service` should always work:
-
-```shell
-u@pod$ nslookup kubernetes.default
-Server:    10.0.0.10
-Address 1: 10.0.0.10
-
-Name:      kubernetes
-Address 1: 10.0.0.1
-```
-
-If this fails, you might need to go to the kube-proxy section of this doc, or
-even go back to the top of this document and start over, but instead of
-debugging your own `Service`, debug DNS.
-
-## Does the Service work by IP?
-
-The next thing to test is whether your `Service` works at all.  From a
-`Node` in your cluster, access the `Service`'s IP (from `kubectl get` above).
-
-```shell
-u@node$ curl 10.0.1.175:80
-hostnames-0uton
-
-u@node$ curl 10.0.1.175:80
-hostnames-yp2kp
-
-u@node$ curl 10.0.1.175:80
-hostnames-bvc05
-```
-
-If your `Service` is working, you should get correct responses.  If not, there
-are a number of things that could be going wrong.  Read on.
-
-## Is the Service correct?
-
-It might sound silly, but you should really double and triple check that your
-`Service` is correct and matches your `Pods`.  Read back your `Service` and
-verify it:
-
-```shell
-$ kubectl get service hostnames -o json
-{
-    "kind": "Service",
-    "apiVersion": "v1",
-    "metadata": {
-        "name": "hostnames",
-        "namespace": "default",
-        "selfLink": "/api/v1/namespaces/default/services/hostnames",
-        "uid": "428c8b6c-24bc-11e5-936d-42010af0a9bc",
-        "resourceVersion": "347189",
-        "creationTimestamp": "2015-07-07T15:24:29Z",
-        "labels": {
-            "app": "hostnames"
-        }
-    },
-    "spec": {
-        "ports": [
-            {
-                "name": "default",
-                "protocol": "TCP",
-                "port": 80,
-                "targetPort": 9376,
-                "nodePort": 0
-            }
-        ],
-        "selector": {
-            "app": "hostnames"
-        },
-        "clusterIP": "10.0.1.175",
-        "type": "ClusterIP",
-        "sessionAffinity": "None"
-    },
-    "status": {
-        "loadBalancer": {}
-    }
-}
-```
-
-Is the port you are trying to access in `spec.ports[]`?  Is the `targetPort`
-correct for your `Pod`s?  If you meant it to be a numeric port, is it a number
-(9376) or a string "9376"?  If you meant it to be a named port, do your `Pod`s
-expose a port with the same name?  Is the port's `protocol` the same as the
-`Pod`'s?
-
-## Does the Service have any Endpoints?
-
-If you got this far, we assume that you have confirmed that your `Service`
-exists and resolves by DNS.  Now let's check that the `Pod`s you ran are
-actually being selected by the `Service`.
-
-Earlier we saw that the `Pod`s were running.  We can re-check that:
-
-```shell
-$ kubectl get pods -l app=hostnames
-NAME              READY     STATUS    RESTARTS   AGE
-hostnames-0uton   1/1       Running   0          1h
-hostnames-bvc05   1/1       Running   0          1h
-hostnames-yp2kp   1/1       Running   0          1h
-```
-
-The "AGE" column says that these `Pod`s are about an hour old, which implies that
-they are running fine and not crashing.
-
-The `-l app=hostnames` argument is a label selector - just like our `Service`
-has.  Inside the Kubernetes system is a control loop which evaluates the
-selector of every `Service` and save the results into an `Endpoints` object.
-
-```shell
-$ kubectl get endpoints hostnames
-NAME        ENDPOINTS
-hostnames   10.244.0.5:9376,10.244.0.6:9376,10.244.0.7:9376
-```
-
-This confirms that the control loop has found the correct `Pod`s for your
-`Service`.  If the `hostnames` row is blank, you should check that the
-`spec.selector` field of your `Service` actually selects for `metadata.labels`
-values on your `Pod`s.
-
-## Are the Pods working?
-
-At this point, we know that your `Service` exists and has selected your `Pod`s.
-Let's check that the `Pod`s are actually working - we can bypass the `Service`
-mechanism and go straight to the `Pod`s.
-
-```shell
-u@pod$ wget -qO- 10.244.0.5:9376
-hostnames-0uton
-
-pod $ wget -qO- 10.244.0.6:9376
-hostnames-bvc05
-
-u@pod$ wget -qO- 10.244.0.7:9376
-hostnames-yp2kp
-```
-
-We expect each `Pod` in the `Endpoints` list to return its own hostname.  If
-this is not what happens (or whatever the correct behavior is for your own
-`Pod`s), you should investigate what's happening there.  You might find
-`kubectl logs` to be useful or `kubectl exec` directly to your `Pod`s and check
-service from there.
-
-## Is the kube-proxy working?
-
-If you get here, your `Service` is running, has `Endpoints`, and your `Pod`s
-are actually serving.  At this point, the whole `Service` proxy mechanism is
-suspect.  Let's confirm it, piece by piece.
-
-### Is kube-proxy running?
-
-Confirm that `kube-proxy` is running on your `Node`s.  You should get something
-like the below:
-
-```shell
-u@node$ ps auxw | grep kube-proxy
-root  4194  0.4  0.1 101864 17696 ?    Sl Jul04  25:43 /usr/local/bin/kube-proxy --master=https://kubernetes-master --kubeconfig=/var/lib/kube-proxy/kubeconfig --v=2
-```
-
-Next, confirm that it is not failing something obvious, like contacting the
-master.  To do this, you'll have to look at the logs.  Accessing the logs
-depends on your `Node` OS.  On some OSes it is a file, such as
-/var/log/kube-proxy.log, while other OSes use `journalctl` to access logs.  You
-should see something like:
-
-```shell
-I0707 17:34:53.945651   30031 server.go:88] Running in resource-only container "/kube-proxy"
-I0707 17:34:53.945921   30031 proxier.go:121] Setting proxy IP to 10.240.115.247 and initializing iptables
-I0707 17:34:54.053023   30031 roundrobin.go:262] LoadBalancerRR: Setting endpoints for default/kubernetes: to [10.240.169.188:443]
-I0707 17:34:54.053175   30031 roundrobin.go:262] LoadBalancerRR: Setting endpoints for default/hostnames:default to [10.244.0.5:9376 10.244.0.6:9376 10.244.0.7:9376]
-I0707 17:34:54.053284   30031 roundrobin.go:262] LoadBalancerRR: Setting endpoints for default/kube-dns:dns to [10.244.3.3:53]
-I0707 17:34:54.053310   30031 roundrobin.go:262] LoadBalancerRR: Setting endpoints for default/kube-dns:dns-tcp to [10.244.3.3:53]
-I0707 17:34:54.054780   30031 proxier.go:306] Adding new service "default/kubernetes:" at 10.0.0.1:443/TCP
-I0707 17:34:54.054903   30031 proxier.go:247] Proxying for service "default/kubernetes:" on TCP port 40074
-I0707 17:34:54.079181   30031 proxier.go:306] Adding new service "default/hostnames:default" at 10.0.1.175:80/TCP
-I0707 17:34:54.079273   30031 proxier.go:247] Proxying for service "default/hostnames:default" on TCP port 48577
-I0707 17:34:54.113665   30031 proxier.go:306] Adding new service "default/kube-dns:dns" at 10.0.0.10:53/UDP
-I0707 17:34:54.113776   30031 proxier.go:247] Proxying for service "default/kube-dns:dns" on UDP port 34149
-I0707 17:34:54.120224   30031 proxier.go:306] Adding new service "default/kube-dns:dns-tcp" at 10.0.0.10:53/TCP
-I0707 17:34:54.120297   30031 proxier.go:247] Proxying for service "default/kube-dns:dns-tcp" on TCP port 53476
-I0707 17:34:54.902313   30031 proxysocket.go:130] Accepted TCP connection from 10.244.3.3:42670 to 10.244.3.1:40074
-I0707 17:34:54.903107   30031 proxysocket.go:130] Accepted TCP connection from 10.244.3.3:42671 to 10.244.3.1:40074
-I0707 17:35:46.015868   30031 proxysocket.go:246] New UDP connection from 10.244.3.2:57493
-I0707 17:35:46.017061   30031 proxysocket.go:246] New UDP connection from 10.244.3.2:55471
-```
-
-If you see error messages about not being able to contact the master, you
-should double-check your `Node` configuration and installation steps.
-
-### Is kube-proxy writing iptables rules?
-
-One of the main responsibilities of `kube-proxy` is to write the `iptables`
-rules which implement `Service`s.  Let's check that those rules are getting
-written.
-
-```shell
-u@node$ iptables-save | grep hostnames
--A KUBE-PORTALS-CONTAINER -d 10.0.1.175/32 -p tcp -m comment --comment "default/hostnames:default" -m tcp --dport 80 -j REDIRECT --to-ports 48577
--A KUBE-PORTALS-HOST -d 10.0.1.175/32 -p tcp -m comment --comment "default/hostnames:default" -m tcp --dport 80 -j DNAT --to-destination 10.240.115.247:48577
-```
-
-There should be 2 rules for each port on your `Service` (just one in this
-example) - a "KUBE-PORTALS-CONTAINER" and a "KUBE-PORTALS-HOST".  If you do
-not see these, try restarting `kube-proxy` with the `-V` flag set to 4, and
-then look at the logs again.
-
-### Is kube-proxy proxying?
-
-Assuming you do see the above rules, try again to access your `Service` by IP:
-
-```shell
-u@node$ curl 10.0.1.175:80
-hostnames-0uton
-```
-
-If this fails, we can try accessing the proxy directly.  Look back at the
-`iptables-save` output above, and extract the port number that `kube-proxy` is
-using for your `Service`.  In the above examples it is "48577".  Now connect to
-that:
-
-```shell
-u@node$ curl localhost:48577
-hostnames-yp2kp
-```
-
-If this still fails, look at the `kube-proxy` logs for specific lines like:
-
-```shell
-Setting endpoints for default/hostnames:default to [10.244.0.5:9376 10.244.0.6:9376 10.244.0.7:9376]
-```
-
-If you don't see those, try restarting `kube-proxy` with the `-V` flag set to 4, and
-then look at the logs again.
-
-## Seek help
-
-If you get this far, something very strange is happening.  Your `Service` is
-running, has `Endpoints`, and your `Pod`s are actually serving.  You have DNS
-working, `iptables` rules installed, and `kube-proxy` does not seem to be
-misbehaving.  And yet your `Service` is not working.  You should probably let
-us know, so we can help investigate!
-
-Contact us on
-[Slack](/{{page.version}}/docs/troubleshooting/#slack) or
-[email](https://groups.google.com/forum/#!forum/google-containers) or
-[GitHub](https://github.com/kubernetes/kubernetes).
-
-## More information
-
-Visit [troubleshooting document](/{{page.version}}/docs/troubleshooting/) for more information.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/deploying-applications.md b/v1.2/docs/user-guide/deploying-applications.md
deleted file mode 100644
index 6bd8c1cb93..0000000000
--- a/v1.2/docs/user-guide/deploying-applications.md
+++ /dev/null
@@ -1,114 +0,0 @@
----
----
-
-You previously read about how to quickly deploy a simple replicated application using [`kubectl run`](/{{page.version}}/docs/user-guide/quick-start) and how to configure and launch single-run containers using pods ([Configuring containers](/{{page.version}}/docs/user-guide/configuring-containers)). Here you'll use the configuration-based approach to deploy a continuously running, replicated application.
-
-* TOC
-{:toc}
-
-## Launching a set of replicas using a configuration file
-
-Kubernetes creates and manages sets of replicated containers (actually, replicated [Pods](/{{page.version}}/docs/user-guide/pods)) using [*Replication Controllers*](/{{page.version}}/docs/user-guide/replication-controller).
-
-A replication controller simply ensures that a specified number of pod "replicas" are running at any one time. If there are too many, it will kill some. If there are too few, it will start more. It's analogous to Google Compute Engine's [Instance Group Manager](https://cloud.google.com/compute/docs/instance-groups/manager/) or AWS's [Auto-scaling Group](http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/AutoScalingGroup) (with no scaling policies).
-
-The replication controller created to run nginx by `kubectl run` in the [Quick start](/{{page.version}}/docs/user-guide/quick-start) could be specified using YAML as follows:
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx
-spec:
-  replicas: 2
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        ports:
-        - containerPort: 80
-```
-
-Some differences compared to specifying just a pod are that the `kind` is `ReplicationController`, the number of `replicas` desired is specified, and the pod specification is under the `template` field. The names of the pods don't need to be specified explicitly because they are generated from the name of the replication controller.
-View the [replication controller API
-object](http://kubernetes.io/v1.1/docs/api-reference/v1/definitions/#_v1_replicationcontroller)
-to view the list of supported fields.
-
-This replication controller can be created using `create`, just as with pods:
-
-```shell
-$ kubectl create -f ./nginx-rc.yaml
-replicationcontrollers/my-nginx
-```
-
-Unlike in the case where you directly create pods, a replication controller replaces pods that are deleted or terminated for any reason, such as in the case of node failure. For this reason, we recommend that you use a replication controller for a continuously running application even if your application requires only a single pod, in which case you can omit `replicas` and it will default to a single replica.
-
-## Viewing replication controller status
-
-You can view the replication controller you created using `get`:
-
-```shell
-$ kubectl get rc
-CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR    REPLICAS
-my-nginx     nginx          nginx      app=nginx   2
-```
-
-This tells you that your controller will ensure that you have two nginx replicas.
-
-You can see those replicas using `get`, just as with pods you created directly:
-
-```shell
-$ kubectl get pods
-NAME             READY     STATUS    RESTARTS   AGE
-my-nginx-065jq   1/1       Running   0          51s
-my-nginx-buaiq   1/1       Running   0          51s
-```
-
-## Deleting replication controllers
-
-When you want to kill your application, delete your replication controller, as in the [Quick start](/{{page.version}}/docs/user-guide/quick-start):
-
-```shell
-$ kubectl delete rc my-nginx
-replicationcontrollers/my-nginx
-```
-
-By default, this will also cause the pods managed by the replication controller to be deleted. If there were a large number of pods, this may take a while to complete. If you want to leave the pods running, specify `--cascade=false`.
-
-If you try to delete the pods before deleting the replication controller, it will just replace them, as it is supposed to do.
-
-## Labels
-
-Kubernetes uses user-defined key-value attributes called [*labels*](/{{page.version}}/docs/user-guide/labels) to categorize and identify sets of resources, such as pods and replication controllers. The example above specified a single label in the pod template, with key `app` and value `nginx`. All pods created carry that label, which can be viewed using `-L`:
-
-```shell
-$ kubectl get pods -L app
-NAME             READY     STATUS    RESTARTS   AGE       APP
-my-nginx-afv12   0/1       Running   0          3s        nginx
-my-nginx-lg99z   0/1       Running   0          3s        nginx
-```
-
-The labels from the pod template are copied to the replication controller's labels by default, as well -- all resources in Kubernetes support labels:
-
-```shell
-$ kubectl get rc my-nginx -L app
-CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR    REPLICAS   APP
-my-nginx     nginx          nginx      app=nginx   2          nginx
-```
-
-More importantly, the pod template's labels are used to create a [`selector`](/{{page.version}}/docs/user-guide/labels/#label-selectors) that will match pods carrying those labels. You can see this field by requesting it using the [Go template output format of `kubectl get`](/{{page.version}}/docs/user-guide/kubectl/kubectl_get):
-
-```shell
-$ kubectl get rc my-nginx -o template --template="{{.spec.selector}}"
-map[app:nginx]
-```
-
-You could also specify the `selector` explicitly, such as if you wanted to specify labels in the pod template that you didn't want to select on, but you should ensure that the selector will match the labels of the pods created from the pod template, and that it won't match pods created by other replication controllers. The most straightforward way to ensure the latter is to create a unique label value for the replication controller, and to specify it in both the pod template's labels and in the selector.
-
-## What's next?
-
-[Learn about exposing applications to users and clients, and connecting tiers of your application together.](/{{page.version}}/docs/user-guide/connecting-applications)
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/docker-cli-to-kubectl.md b/v1.2/docs/user-guide/docker-cli-to-kubectl.md
deleted file mode 100644
index 71e31f6087..0000000000
--- a/v1.2/docs/user-guide/docker-cli-to-kubectl.md
+++ /dev/null
@@ -1,266 +0,0 @@
----
----
-
-In this doc, we introduce the Kubernetes command line for interacting with the api to docker-cli users. The tool, kubectl, is designed to be familiar to docker-cli users but there are a few necessary differences. Each section of this doc highlights a docker subcommand explains the kubectl equivalent.
-
-* TOC
-{:toc}
-
-#### docker run
-
-How do I run an nginx container and expose it to the world? Checkout [kubectl run](/{{page.version}}/docs/user-guide/kubectl/kubectl_run).
-
-With docker:
-
-```shell
-$ docker run -d --restart=always -e DOMAIN=cluster --name nginx-app -p 80:80 nginx
-a9ec34d9878748d2f33dc20cb25c714ff21da8d40558b45bfaec9955859075d0
-$ docker ps
-CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS                         NAMES
-a9ec34d98787        nginx               "nginx -g 'daemon of   2 seconds ago       Up 2 seconds        0.0.0.0:80->80/tcp, 443/tcp   nginx-app 
-```
-
-With kubectl:
-
-```shell
-# start the pod running nginx
-$ kubectl run --image=nginx nginx-app --port=80 --env="DOMAIN=cluster"
-replicationcontroller "nginx-app" created
-# expose a port through with a service
-$ kubectl expose rc nginx-app --port=80 --name=nginx-http
-```
-
-With kubectl, we create a [replication controller](/{{page.version}}/docs/user-guide/replication-controller) which will make sure that N pods are running nginx (where N is the number of replicas stated in the spec, which defaults to 1). We also create a [service](/{{page.version}}/docs/user-guide/services) with a selector that matches the replication controller's selector. See the [Quick start](/{{page.version}}/docs/user-guide/quick-start) for more information.
-
-By default images are run in the background, similar to `docker run -d ...`, if you want to run things in the foreground, use:
-
-```shell
-kubectl run [-i] [--tty] --attach <name> --image=<image>
-```
-
-Unlike `docker run ...`, if `--attach` is specified, we attach to `stdin`, `stdout` and `stderr`, there is no ability to control which streams are attached (`docker -a ...`).
-
-Because we start a replication controller for your container, it will be restarted if you terminate the attached process (e.g. `ctrl-c`), this is different than `docker run -it`.
-To destroy the replication controller (and it's pods)  you need to run `kubectl delete rc <name>`
-
-#### docker ps
-
-How do I list what is currently running? Checkout [kubectl get](/{{page.version}}/docs/user-guide/kubectl/kubectl_get).
-
-With docker:
-
-```shell
-$ docker ps
-CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS                         NAMES
-a9ec34d98787        nginx               "nginx -g 'daemon of   About an hour ago   Up About an hour    0.0.0.0:80->80/tcp, 443/tcp   nginx-app
-```
-
-With kubectl:
-
-```shell
-$ kubectl get po
-NAME              READY     STATUS    RESTARTS   AGE
-nginx-app-5jyvm   1/1       Running   0          1h
-```
-
-#### docker attach
-
-How do I attach to a process that is already running in a container?  Checkout [kubectl attach](/{{page.version}}/docs/user-guide/kubectl/kubectl_attach)
-
-With docker:
-
-```shell
-$ docker ps
-CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS                         NAMES
-a9ec34d98787        nginx               "nginx -g 'daemon of   8 minutes ago       Up 8 minutes        0.0.0.0:80->80/tcp, 443/tcp   nginx-app
-$ docker attach -it a9ec34d98787
-...
-```
-
-With kubectl:
-
-```shell
-$ kubectl get pods
-NAME              READY     STATUS    RESTARTS   AGE
-nginx-app-5jyvm   1/1       Running   0          10m
-$ kubectl attach -it nginx-app-5jyvm
-...
-```
-
-#### docker exec
-
-How do I execute a command in a container? Checkout [kubectl exec](/{{page.version}}/docs/user-guide/kubectl/kubectl_exec).
-
-With docker:
-
-```shell
-$ docker ps
-CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS                         NAMES
-a9ec34d98787        nginx               "nginx -g 'daemon of   8 minutes ago       Up 8 minutes        0.0.0.0:80->80/tcp, 443/tcp   nginx-app
-$ docker exec a9ec34d98787 cat /etc/hostname
-a9ec34d98787
-```
-
-With kubectl:
-
-```shell
-$ kubectl get po
-NAME              READY     STATUS    RESTARTS   AGE
-nginx-app-5jyvm   1/1       Running   0          10m
-$ kubectl exec nginx-app-5jyvm -- cat /etc/hostname
-nginx-app-5jyvm
-```
-
-What about interactive commands?
-
-
-With docker:
-
-```shell
-$ docker exec -ti a9ec34d98787 /bin/sh
-# exit
-```
-
-With kubectl:
-
-```shell
-$ kubectl exec -ti nginx-app-5jyvm -- /bin/sh      
-# exit
-```
-
-For more information see [Getting into containers](/{{page.version}}/docs/user-guide/getting-into-containers).
-
-#### docker logs
-
-How do I follow stdout/stderr of a running process? Checkout [kubectl logs](/{{page.version}}/docs/user-guide/kubectl/kubectl_logs).
-
-
-With docker:
-
-```shell
-$ docker logs -f a9e
-192.168.9.1 - - [14/Jul/2015:01:04:02 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.35.0" "-"
-192.168.9.1 - - [14/Jul/2015:01:04:03 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.35.0" "-"
-```
-
-With kubectl:
-
-```shell
-$ kubectl logs -f nginx-app-zibvs
-10.240.63.110 - - [14/Jul/2015:01:09:01 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.26.0" "-"
-10.240.63.110 - - [14/Jul/2015:01:09:02 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.26.0" "-"
-```
-
-Now's a good time to mention slight difference between pods and containers; by default pods will not terminate if their processes exit. Instead it will restart the process. This is similar to the docker run option `--restart=always` with one major difference. In docker, the output for each invocation of the process is concatenated but for Kubernetes, each invocation is separate. To see the output from a previous run in Kubernetes, do this:
-
-```shell
-$ kubectl logs --previous nginx-app-zibvs
-10.240.63.110 - - [14/Jul/2015:01:09:01 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.26.0" "-"
-10.240.63.110 - - [14/Jul/2015:01:09:02 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.26.0" "-"
-```
-
-See [Logging](/{{page.version}}/docs/user-guide/logging) for more information.
-
-#### docker stop and docker rm
-
-How do I stop and delete a running process? Checkout [kubectl delete](/{{page.version}}/docs/user-guide/kubectl/kubectl_delete).
-
-With docker
-
-```shell
-$ docker ps
-CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS                         NAMES
-a9ec34d98787        nginx               "nginx -g 'daemon of   22 hours ago        Up 22 hours         0.0.0.0:80->80/tcp, 443/tcp   nginx-app
-$ docker stop a9ec34d98787
-a9ec34d98787
-$ docker rm a9ec34d98787
-a9ec34d98787
-```
-
-With kubectl:
-
-```shell
-$ kubectl get rc nginx-app
-CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR        REPLICAS
-nginx-app    nginx-app      nginx      run=nginx-app   1
-$ kubectl get po
-NAME              READY     STATUS    RESTARTS   AGE
-nginx-app-aualv   1/1       Running   0          16s
-$ kubectl delete rc nginx-app
-NAME              READY     STATUS    RESTARTS   AGE
-nginx-app-aualv   1/1       Running   0          16s
-$ kubectl get po
-NAME      READY     STATUS    RESTARTS   AGE
-```
-
-Notice that we don't delete the pod directly. With kubectl we want to delete the replication controller that owns the pod. If we delete the pod directly, the replication controller will recreate the pod.
-
-#### docker login
-
-There is no direct analog of `docker login` in kubectl. If you are interested in using Kubernetes with a private registry, see [Using a Private Registry](/{{page.version}}/docs/user-guide/images/#using-a-private-registry).
-
-#### docker version
-
-How do I get the version of my client and server? Checkout [kubectl version](/{{page.version}}/docs/user-guide/kubectl/kubectl_version).
-
-With docker:
-
-```shell
-$ docker version
-Client version: 1.7.0
-Client API version: 1.19
-Go version (client): go1.4.2
-Git commit (client): 0baf609
-OS/Arch (client): linux/amd64
-Server version: 1.7.0
-Server API version: 1.19
-Go version (server): go1.4.2
-Git commit (server): 0baf609
-OS/Arch (server): linux/amd64
-```
-
-With kubectl:
-
-```shell
-$ kubectl version
-Client Version: version.Info{Major:"0", Minor:"20.1", GitVersion:"v0.20.1", GitCommit:"", GitTreeState:"not a git tree"}
-Server Version: version.Info{Major:"0", Minor:"21+", GitVersion:"v0.21.1-411-g32699e873ae1ca-dirty", GitCommit:"32699e873ae1caa01812e41de7eab28df4358ee4", GitTreeState:"dirty"}
-```
-
-#### docker info
-
-How do I get miscellaneous info about my environment and configuration? Checkout [kubectl cluster-info](/{{page.version}}/docs/user-guide/kubectl/kubectl_cluster-info).
-
-With docker:
-
-```shell
-$ docker info
-Containers: 40
-Images: 168
-Storage Driver: aufs
- Root Dir: /usr/local/google/docker/aufs
- Backing Filesystem: extfs
- Dirs: 248
- Dirperm1 Supported: false
-Execution Driver: native-0.2
-Logging Driver: json-file
-Kernel Version: 3.13.0-53-generic
-Operating System: Ubuntu 14.04.2 LTS
-CPUs: 12
-Total Memory: 31.32 GiB
-Name: k8s-is-fun.mtv.corp.google.com
-ID: ADUV:GCYR:B3VJ:HMPO:LNPQ:KD5S:YKFQ:76VN:IANZ:7TFV:ZBF4:BYJO
-WARNING: No swap limit support
-```
-
-With kubectl:
-
-```shell
-$ kubectl cluster-info
-Kubernetes master is running at https://108.59.85.141
-KubeDNS is running at https://108.59.85.141/api/v1/proxy/namespaces/kube-system/services/kube-dns
-KubeUI is running at https://108.59.85.141/api/v1/proxy/namespaces/kube-system/services/kube-ui
-Grafana is running at https://108.59.85.141/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
-Heapster is running at https://108.59.85.141/api/v1/proxy/namespaces/kube-system/services/monitoring-heapster
-InfluxDB is running at https://108.59.85.141/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb
-```
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/downward-api.md b/v1.2/docs/user-guide/downward-api.md
deleted file mode 100644
index e9e4a320eb..0000000000
--- a/v1.2/docs/user-guide/downward-api.md
+++ /dev/null
@@ -1,154 +0,0 @@
----
----
-
-It is sometimes useful for a container to have information about itself, but we
-want to be careful not to over-couple containers to Kubernetes. The downward
-API allows containers to consume information about themselves or the system and
-expose that information how they want it, without necessarily coupling to the
-Kubernetes client or REST API.
-
-An example of this is a "legacy" app that is already written assuming
-that a particular environment variable will hold a unique identifier.  While it
-is often possible to "wrap" such applications, this is tedious and error prone,
-and violates the goal of low coupling.  Instead, the user should be able to use
-the Pod's name, for example, and inject it into this well-known variable.
-
-## Capabilities
-
-The following information is available to a `Pod` through the downward API:
-
-*   The pod's name
-*   The pod's namespace
-*   The pod's IP
-
-More information will be exposed through this same API over time.
-
-## Exposing pod information into a container
-
-Containers consume information from the downward API using environment
-variables or using a volume plugin.
-
-### Environment variables
-
-Most environment variables in the Kubernetes API use the `value` field to carry
-simple values.  However, the alternate `valueFrom` field allows you to specify
-a `fieldRef` to select fields from the pod's definition.  The `fieldRef` field
-is a structure that has an `apiVersion` field and a `fieldPath` field.  The
-`fieldPath` field is an expression designating a field of the pod.  The
-`apiVersion` field is the version of the API schema that the `fieldPath` is
-written in terms of.  If the `apiVersion` field is not specified it is
-defaulted to the API version of the enclosing object.
-
-The `fieldRef` is evaluated and the resulting value is used as the value for
-the environment variable.  This allows users to publish their pod's name in any
-environment variable they want.
-
-## Example
-
-This is an example of a pod that consumes its name and namespace via the
-downward API:
-
-<!-- BEGIN MUNGE: EXAMPLE downward-api/dapi-pod.yaml -->
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: dapi-test-pod
-spec:
-  containers:
-    - name: test-container
-      image: gcr.io/google_containers/busybox
-      command: [ "/bin/sh", "-c", "env" ]
-      env:
-        - name: MY_POD_NAME
-          valueFrom:
-            fieldRef:
-              fieldPath: metadata.name
-        - name: MY_POD_NAMESPACE
-          valueFrom:
-            fieldRef:
-              fieldPath: metadata.namespace
-        - name: MY_POD_IP
-          valueFrom:
-            fieldRef:
-              fieldPath: status.podIP
-  restartPolicy: Never
-```
-
-[Download example](/{{page.version}}/docs/user-guide/downward-api/dapi-pod.yaml)
-<!-- END MUNGE: EXAMPLE downward-api/dapi-pod.yaml -->
-
-
-### Downward API volume
-
-Using a similar syntax it's possible to expose pod information to containers using plain text files.
-Downward API are dumped to a mounted volume. This is achieved using a `downwardAPI`
-volume type and the different items represent the files to be created. `fieldPath` references the field to be exposed.
-
-Downward API volume permits to store more complex data like [`metadata.labels`](/{{page.version}}/docs/user-guide/labels) and [`metadata.annotations`](/{{page.version}}/docs/user-guide/annotations). Currently key/value pair set fields are saved using `key="value"` format:
-
-```conf
-key1="value1"
-key2="value2"
-```
-
-In future, it will be possible to specify an output format option.
-
-Downward API volumes can expose:
-
-*   The pod's name
-*   The pod's namespace
-*   The pod's labels
-*   The pod's annotations
-
-The downward API volume refreshes its data in step with the kubelet refresh loop. When labels will be modifiable on the fly without respawning the pod containers will be able to detect changes through mechanisms such as [inotify](https://en.wikipedia.org/wiki/Inotify).
-
-In future, it will be possible to specify a specific annotation or label.
-
-## Example
-
-This is an example of a pod that consumes its labels and annotations via the downward API volume, labels and annotations are dumped in `/etc/podlabels` and in `/etc/annotations`, respectively:
-
-<!-- BEGIN MUNGE: EXAMPLE downward-api/volume/dapi-volume.yaml -->
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: kubernetes-downwardapi-volume-example
-  labels:
-    zone: us-est-coast
-    cluster: test-cluster1
-    rack: rack-22
-  annotations:
-    build: two
-    builder: john-doe
-spec:
-  containers:
-    - name: client-container
-      image: gcr.io/google_containers/busybox
-      command: ["sh", "-c", "while true; do if [[ -e /etc/labels ]]; then cat /etc/labels; fi; if [[ -e /etc/annotations ]]; then cat /etc/annotations; fi; sleep 5; done"]
-      volumeMounts:
-        - name: podinfo
-          mountPath: /etc
-          readOnly: false
-  volumes:
-    - name: podinfo
-      downwardAPI:
-        items:
-          - path: "labels"
-            fieldRef:
-              fieldPath: metadata.labels
-          - path: "annotations"
-            fieldRef:
-              fieldPath: metadata.annotations
-```
-
-[Download example](/{{page.version}}/docs/user-guide/downward-api/volume/dapi-volume.yaml)
-<!-- END MUNGE: EXAMPLE downward-api/volume/dapi-volume.yaml -->
-
-Some more thorough examples:
-
-   * [environment variables](/{{page.version}}/docs/user-guide/environment-guide/)
-   * [downward API](/{{page.version}}/docs/user-guide/downward-api/)
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/downward-api/dapi-pod.yaml b/v1.2/docs/user-guide/downward-api/dapi-pod.yaml
deleted file mode 100644
index 7d688aa0e9..0000000000
--- a/v1.2/docs/user-guide/downward-api/dapi-pod.yaml
+++ /dev/null
@@ -1,23 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: dapi-test-pod
-spec:
-  containers:
-    - name: test-container
-      image: gcr.io/google_containers/busybox
-      command: [ "/bin/sh", "-c", "env" ]
-      env:
-        - name: MY_POD_NAME
-          valueFrom:
-            fieldRef:
-              fieldPath: metadata.name
-        - name: MY_POD_NAMESPACE
-          valueFrom:
-            fieldRef:
-              fieldPath: metadata.namespace
-        - name: MY_POD_IP
-          valueFrom:
-            fieldRef:
-              fieldPath: status.podIP
-  restartPolicy: Never
diff --git a/v1.2/docs/user-guide/downward-api/volume/dapi-volume.yaml b/v1.2/docs/user-guide/downward-api/volume/dapi-volume.yaml
deleted file mode 100644
index be926498d1..0000000000
--- a/v1.2/docs/user-guide/downward-api/volume/dapi-volume.yaml
+++ /dev/null
@@ -1,30 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: kubernetes-downwardapi-volume-example
-  labels:
-    zone: us-est-coast
-    cluster: test-cluster1
-    rack: rack-22
-  annotations:
-    build: two
-    builder: john-doe
-spec:
-  containers:
-    - name: client-container
-      image: gcr.io/google_containers/busybox
-      command: ["sh", "-c", "while true; do if [[ -e /etc/labels ]]; then cat /etc/labels; fi; if [[ -e /etc/annotations ]]; then cat /etc/annotations; fi; sleep 5; done"]
-      volumeMounts:
-        - name: podinfo
-          mountPath: /etc
-          readOnly: false
-  volumes:
-    - name: podinfo
-      downwardAPI:
-        items:
-          - path: "labels"
-            fieldRef:
-              fieldPath: metadata.labels
-          - path: "annotations"
-            fieldRef:
-              fieldPath: metadata.annotations
diff --git a/v1.2/docs/user-guide/downward-api/volume/index.md b/v1.2/docs/user-guide/downward-api/volume/index.md
deleted file mode 100644
index 1894903d94..0000000000
--- a/v1.2/docs/user-guide/downward-api/volume/index.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
----
-
-Following this example, you will create a pod with a downward API volume.
-A downward API volume is a k8s volume plugin with the ability to save some pod information in a plain text file. The pod information can be  for example some [metadata](/{{page.version}}/docs/devel/api-conventions/#metadata).
-
-Supported metadata fields:
-
-1. `metadata.annotations`
-2. `metadata.namespace`
-3. `metadata.name`
-4. `metadata.labels`
-
-### Step Zero: Prerequisites
-
-This example assumes you have a Kubernetes cluster installed and running, and the `kubectl`
-command line tool somewhere in your path. Please see the [gettingstarted](/{{page.version}}/docs/getting-started-guides/) for installation instructions for your platform.
-
-### Step One: Create the pod
-
-Use the `docs/user-guide/downward-api/dapi-volume.yaml` file to create a Pod with a  downward API volume which stores pod labels and pod annotations to `/etc/labels` and  `/etc/annotations` respectively.
-
-```shell
-$ kubectl create -f  docs/user-guide/downward-api/volume/dapi-volume.yaml
-```
-
-### Step Two: Examine pod/container output
-
-The pod displays (every 5 seconds) the content of the dump files which can be executed via the usual `kubectl log` command
-
-```shell
-$ kubectl logs kubernetes-downwardapi-volume-example
-cluster="test-cluster1"
-rack="rack-22"
-zone="us-est-coast"
-build="two"
-builder="john-doe"
-kubernetes.io/config.seen="2015-08-24T13:47:23.432459138Z"
-kubernetes.io/config.source="api"
-```
-
-### Internals
-
-In pod's `/etc` directory one may find the file created by the plugin (system files elided):
-
-```shell
-$ kubectl exec kubernetes-downwardapi-volume-example -i -t -- sh
-/ # ls -laR /etc
-/etc:
-total 32
-drwxrwxrwt    3 0        0              180 Aug 24 13:03 .
-drwxr-xr-x    1 0        0             4096 Aug 24 13:05 ..
-drwx------    2 0        0               80 Aug 24 13:03 ..2015_08_24_13_03_44259413923
-lrwxrwxrwx    1 0        0               30 Aug 24 13:03 ..downwardapi -> ..2015_08_24_13_03_44259413923
-lrwxrwxrwx    1 0        0               25 Aug 24 13:03 annotations -> ..downwardapi/annotations
-lrwxrwxrwx    1 0        0               20 Aug 24 13:03 labels -> ..downwardapi/labels
-
-/etc/..2015_08_24_13_03_44259413923:
-total 8
-drwx------    2 0        0               80 Aug 24 13:03 .
-drwxrwxrwt    3 0        0              180 Aug 24 13:03 ..
--rw-r--r--    1 0        0              115 Aug 24 13:03 annotations
--rw-r--r--    1 0        0               53 Aug 24 13:03 labels
-/ #
-```
-
-The file `labels` is stored in a temporary directory (`..2015_08_24_13_03_44259413923` in the example above) which is symlinked to by `..downwardapi`. Symlinks for annotations and labels in `/etc` point to files containing the actual metadata through the `..downwardapi` indirection.  This structure allows for dynamic atomic refresh of the metadata: updates are written to a new temporary directory, and the `..downwardapi` symlink is updated atomically using `rename(2)`.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/environment-guide/backend-rc.yaml b/v1.2/docs/user-guide/environment-guide/backend-rc.yaml
deleted file mode 100644
index 6c57b95dac..0000000000
--- a/v1.2/docs/user-guide/environment-guide/backend-rc.yaml
+++ /dev/null
@@ -1,30 +0,0 @@
----
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: backend-rc
-  labels:
-    type: backend-type
-spec:
-  replicas: 3
-  template:
-    metadata:
-      labels:
-        type: backend-type
-    spec:
-      containers:
-      - name: backend-container
-        image: gcr.io/google-samples/env-backend:1.1
-        imagePullPolicy: Always
-        ports:
-        - containerPort: 5000
-          protocol: TCP
-        env:
-        - name: POD_NAME
-          valueFrom:
-            fieldRef:
-              fieldPath: metadata.name
-        - name: POD_NAMESPACE
-          valueFrom:
-            fieldRef:
-              fieldPath: metadata.namespace
diff --git a/v1.2/docs/user-guide/environment-guide/backend-srv.yaml b/v1.2/docs/user-guide/environment-guide/backend-srv.yaml
deleted file mode 100644
index 7083b37bf8..0000000000
--- a/v1.2/docs/user-guide/environment-guide/backend-srv.yaml
+++ /dev/null
@@ -1,13 +0,0 @@
----
-apiVersion: v1
-kind: Service
-metadata:
-  name: backend-srv
-  labels:
-    type: backend-type
-spec:
-  ports:
-  - port: 5000
-    protocol: TCP
-  selector:
-    type: backend-type
diff --git a/v1.2/docs/user-guide/environment-guide/containers/backend/Dockerfile b/v1.2/docs/user-guide/environment-guide/containers/backend/Dockerfile
deleted file mode 100644
index 3fa58ff7ab..0000000000
--- a/v1.2/docs/user-guide/environment-guide/containers/backend/Dockerfile
+++ /dev/null
@@ -1,2 +0,0 @@
-FROM golang:onbuild
-EXPOSE 8080
diff --git a/v1.2/docs/user-guide/environment-guide/containers/backend/backend.go b/v1.2/docs/user-guide/environment-guide/containers/backend/backend.go
deleted file mode 100644
index b4edf75ff5..0000000000
--- a/v1.2/docs/user-guide/environment-guide/containers/backend/backend.go
+++ /dev/null
@@ -1,37 +0,0 @@
-/*
-Copyright 2015 The Kubernetes Authors All rights reserved.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-*/
-
-package main
-
-import (
-	"fmt"
-	"log"
-	"net/http"
-	"os"
-)
-
-func printInfo(resp http.ResponseWriter, req *http.Request) {
-	name := os.Getenv("POD_NAME")
-	namespace := os.Getenv("POD_NAMESPACE")
-	fmt.Fprintf(resp, "Backend Container\n")
-	fmt.Fprintf(resp, "Backend Pod Name: %v\n", name)
-	fmt.Fprintf(resp, "Backend Namespace: %v\n", namespace)
-}
-
-func main() {
-	http.HandleFunc("/", printInfo)
-	log.Fatal(http.ListenAndServe(":5000", nil))
-}
diff --git a/v1.2/docs/user-guide/environment-guide/containers/index.md b/v1.2/docs/user-guide/environment-guide/containers/index.md
deleted file mode 100644
index 4c77d3f1c9..0000000000
--- a/v1.2/docs/user-guide/environment-guide/containers/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
----
-
-
-## Building
-
-For each container, the build steps are the same. The examples below
-are for the `show` container. Replace `show` with `backend` for the
-backend container.
-
-## Google Container Registry ([GCR](https://cloud.google.com/tools/container-registry/))
-
-    docker build -t gcr.io/<project-name>/show .
-    gcloud docker push gcr.io/<project-name>/show
-
-## Docker Hub
-
-    docker build -t <username>/show .
-    docker push <username>/show
-
-## Change Pod Definitions
-
-Edit both `show-rc.yaml` and `backend-rc.yaml` and replace the
-specified `image:` with the one that you built.
-
-
-
diff --git a/v1.2/docs/user-guide/environment-guide/containers/show/Dockerfile b/v1.2/docs/user-guide/environment-guide/containers/show/Dockerfile
deleted file mode 100644
index 3fa58ff7ab..0000000000
--- a/v1.2/docs/user-guide/environment-guide/containers/show/Dockerfile
+++ /dev/null
@@ -1,2 +0,0 @@
-FROM golang:onbuild
-EXPOSE 8080
diff --git a/v1.2/docs/user-guide/environment-guide/containers/show/show.go b/v1.2/docs/user-guide/environment-guide/containers/show/show.go
deleted file mode 100644
index 9a2cfc639d..0000000000
--- a/v1.2/docs/user-guide/environment-guide/containers/show/show.go
+++ /dev/null
@@ -1,95 +0,0 @@
-/*
-Copyright 2015 The Kubernetes Authors All rights reserved.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-*/
-
-package main
-
-import (
-	"fmt"
-	"io"
-	"log"
-	"net/http"
-	"os"
-	"sort"
-	"strings"
-)
-
-func getKubeEnv() (map[string]string, error) {
-	environS := os.Environ()
-	environ := make(map[string]string)
-	for _, val := range environS {
-		split := strings.Split(val, "=")
-		if len(split) != 2 {
-			return environ, fmt.Errorf("Some weird env vars")
-		}
-		environ[split[0]] = split[1]
-	}
-	for key := range environ {
-		if !(strings.HasSuffix(key, "_SERVICE_HOST") ||
-			strings.HasSuffix(key, "_SERVICE_PORT")) {
-			delete(environ, key)
-		}
-	}
-	return environ, nil
-}
-
-func printInfo(resp http.ResponseWriter, req *http.Request) {
-	kubeVars, err := getKubeEnv()
-	if err != nil {
-		http.Error(resp, err.Error(), http.StatusInternalServerError)
-		return
-	}
-
-	backendHost := os.Getenv("BACKEND_SRV_SERVICE_HOST")
-	backendPort := os.Getenv("BACKEND_SRV_SERVICE_PORT")
-	backendRsp, backendErr := http.Get(fmt.Sprintf(
-		"http://%v:%v/",
-		backendHost,
-		backendPort))
-	if backendErr == nil {
-		defer backendRsp.Body.Close()
-	}
-
-	name := os.Getenv("POD_NAME")
-	namespace := os.Getenv("POD_NAMESPACE")
-	fmt.Fprintf(resp, "Pod Name: %v \n", name)
-	fmt.Fprintf(resp, "Pod Namespace: %v \n", namespace)
-
-	envvar := os.Getenv("USER_VAR")
-	fmt.Fprintf(resp, "USER_VAR: %v \n", envvar)
-
-	fmt.Fprintf(resp, "\nKubernetes environment variables\n")
-	var keys []string
-	for key := range kubeVars {
-		keys = append(keys, key)
-	}
-	sort.Strings(keys)
-	for _, key := range keys {
-		fmt.Fprintf(resp, "%v = %v \n", key, kubeVars[key])
-	}
-
-	fmt.Fprintf(resp, "\nFound backend ip: %v port: %v\n", backendHost, backendPort)
-	if backendErr == nil {
-		fmt.Fprintf(resp, "Response from backend\n")
-		io.Copy(resp, backendRsp.Body)
-	} else {
-		fmt.Fprintf(resp, "Error from backend: %v", backendErr.Error())
-	}
-}
-
-func main() {
-	http.HandleFunc("/", printInfo)
-	log.Fatal(http.ListenAndServe(":8080", nil))
-}
diff --git a/v1.2/docs/user-guide/environment-guide/show-rc.yaml b/v1.2/docs/user-guide/environment-guide/show-rc.yaml
deleted file mode 100644
index 4de94c06ca..0000000000
--- a/v1.2/docs/user-guide/environment-guide/show-rc.yaml
+++ /dev/null
@@ -1,32 +0,0 @@
----
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: show-rc
-  labels:
-    type: show-type
-spec:
-  replicas: 3
-  template:
-    metadata:
-      labels:
-        type: show-type
-    spec:
-      containers:
-      - name: show-container
-        image: gcr.io/google-samples/env-show:1.1
-        imagePullPolicy: Always
-        ports:
-        - containerPort: 8080
-          protocol: TCP
-        env:
-        - name: USER_VAR
-          value: important information
-        - name: POD_NAME
-          valueFrom:
-            fieldRef:
-              fieldPath: metadata.name
-        - name: POD_NAMESPACE
-          valueFrom:
-            fieldRef:
-              fieldPath: metadata.namespace
diff --git a/v1.2/docs/user-guide/environment-guide/show-srv.yaml b/v1.2/docs/user-guide/environment-guide/show-srv.yaml
deleted file mode 100644
index 25a2d7473e..0000000000
--- a/v1.2/docs/user-guide/environment-guide/show-srv.yaml
+++ /dev/null
@@ -1,15 +0,0 @@
----
-apiVersion: v1
-kind: Service
-metadata:
-  name: show-srv
-  labels:
-    type: show-type
-spec:
-  type: LoadBalancer
-  ports:
-  - port: 80
-    protocol: TCP
-    targetPort: 8080
-  selector:
-    type: show-type
diff --git a/v1.2/docs/user-guide/getting-into-containers.md b/v1.2/docs/user-guide/getting-into-containers.md
deleted file mode 100644
index 03b0109a2c..0000000000
--- a/v1.2/docs/user-guide/getting-into-containers.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
----
-
-Developers can use `kubectl exec` to run commands in a container. This guide demonstrates two use cases.
-
-## Using kubectl exec to check the environment variables of a container
-
-Kubernetes exposes [services](/{{page.version}}/docs/user-guide/services/#environment-variables) through environment variables. It is convenient to check these environment variables using `kubectl exec`.
-
-We first create a pod and a service,
-
-```shell
-$ kubectl create -f examples/guestbook/redis-master-controller.yaml
-$ kubectl create -f examples/guestbook/redis-master-service.yaml
-```
-wait until the pod is Running and Ready,
-
-```shell
-$ kubectl get pod
-NAME                 READY     REASON       RESTARTS   AGE
-redis-master-ft9ex   1/1       Running      0          12s
-```
-
-then we can check the environment variables of the pod,
-
-```shell
-$ kubectl exec redis-master-ft9ex env
-...
-REDIS_MASTER_SERVICE_PORT=6379
-REDIS_MASTER_SERVICE_HOST=10.0.0.219
-...
-```
-
-We can use these environment variables in applications to find the service.
-
-
-## Using kubectl exec to check the mounted volumes
-
-It is convenient to use `kubectl exec` to check if the volumes are mounted as expected.
-We first create a Pod with a volume mounted at /data/redis,
-
-```shell
-kubectl create -f docs/user-guide/walkthrough/pod-redis.yaml
-```
-
-wait until the pod is Running and Ready,
-
-```shell
-$ kubectl get pods
-NAME      READY     REASON    RESTARTS   AGE
-storage   1/1       Running   0          1m
-```
-
-we then use `kubectl exec` to verify that the volume is mounted at /data/redis,
-
-```shell
-$ kubectl exec storage ls /data
-redis
-```
-
-## Using kubectl exec to open a bash terminal in a pod
-
-After all, open a terminal in a pod is the most direct way to introspect the pod. Assuming the pod/storage is still running, run
-
-```shell
-$ kubectl exec -ti storage -- bash
-root@storage:/data#
-```
-
-This gets you a terminal.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/horizontal-pod-autoscaler.md b/v1.2/docs/user-guide/horizontal-pod-autoscaler.md
deleted file mode 100644
index 1ad4cc651a..0000000000
--- a/v1.2/docs/user-guide/horizontal-pod-autoscaler.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
----
-
-This document describes the current state of Horizontal Pod Autoscaler in Kubernetes.
-
-## What is Horizontal Pod Autoscaler?
-
-Horizontal pod autoscaling allows the number of pods in a replication controller or deployment
-to scale automatically based on observed CPU utilization.
-It is a [beta](/{{page.version}}/docs/api/)#api-versioning) feature in Kubernetes 1.1.
-
-The autoscaler is implemented as a Kubernetes API resource and a controller.
-The resource describes behavior of the controller.
-The controller periodically adjusts the number of replicas in a replication controller or deployment
-to match the observed average CPU utilization to the target specified by user.
-
-
-## How does Horizontal Pod Autoscaler work?
-
-![Horizontal Pod Autoscaler diagram](/images/docs/horizontal-pod-autoscaler.svg)
-
-The autoscaler is implemented as a control loop.
-It periodically queries CPU utilization for the pods it targets.
-(The period of the autoscaler is controlled by `--horizontal-pod-autoscaler-sync-period` flag of controller manager.
-The default value is 30 seconds).
-Then, it compares the arithmetic mean of the pods' CPU utilization with the target and adjust the number of replicas if needed.
-
-CPU utilization is the recent CPU usage of a pod divided by the sum of CPU requested by the pod's containers.
-Please note that if some of the pod's containers do not have CPU request set,
-CPU utilization for the pod will not be defined and the autoscaler will not take any action.
-Further details of the autoscaling algorithm are given [here](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/horizontal-pod-autoscaler.md#autoscaling-algorithm).
-
-Autoscaler uses heapster to collect CPU utilization.
-Therefore, it is required to deploy heapster monitoring in your cluster for autoscaling to work.
-
-Autoscaler accesses corresponding replication controller or deployment by scale sub-resource.
-Scale is an interface which allows to dynamically set the number of replicas and to learn the current state of them.
-More details on scale sub-resource can be found [here](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/horizontal-pod-autoscaler.md#scale-subresource).
-
-
-## API Object
-
-Horizontal pod autoscaler is a top-level resource in the Kubernetes REST API (currently in [beta](/{{page.version}}/docs/api/)#api-versioning)).
-More details about the API object can be found at
-[HorizontalPodAutoscaler Object](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/horizontal-pod-autoscaler.md#horizontalpodautoscaler-object).
-
-## Support for horizontal pod autoscaler in kubectl
-
-Horizontal pod autoscaler, like every API resource, is supported in a standard way by `kubectl`.
-We can create a new autoscaler using `kubectl create` command.
-We can list autoscalers by `kubectl get hpa` and get detailed description by `kubectl describe hpa`.
-Finally, we can delete an autoscaler using `kubectl delete hpa`.
-
-In addition, there is a special `kubectl autoscale` command that allows for easy creation of horizontal pod autoscaler.
-For instance, executing `kubectl autoscale rc foo --min=2 --max=5 --cpu-percent=80`
-will create an autoscaler for replication controller *foo*, with target CPU utilization set to `80%`
-and the number of replicas between 2 and 5.
-The detailed documentation of `kubectl autoscale` can be found [here](/{{page.version}}/docs/user-guide/kubectl/kubectl_autoscale).
-
-
-## Autoscaling during rolling update
-
-Currently in Kubernetes, it is possible to perform a rolling update by managing replication controllers directly,
-or by using the deployment object, which manages the underlying replication controllers for you.
-Horizontal pod autoscaler only supports the latter approach: the horizontal pod autoscaler is bound to the deployment object,
-it sets the size for the deployment object, and the deployment is responsible for setting sizes of underlying replication controllers.
-
-Horizontal pod autoscaler does not work with rolling update using direct manipulation of replication controllers,
-i.e. you cannot bind a horizontal pod autoscaler to a replication controller and do rolling update (e.g. using `kubectl rolling-update`).
-The reason this doesn't work is that when rolling update creates a new replication controller,
-the horizontal pod autoscaler will not be bound to the new replication controller.
-
-
-## Further reading
-
-* Design documentation: [Horizontal Pod Autoscaling](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/horizontal-pod-autoscaler.md).
-* Manual of autoscale command in kubectl: [kubectl autoscale](/{{page.version}}/docs/user-guide/kubectl/kubectl_autoscale).
-* Usage example of [Horizontal Pod Autoscaler](/{{page.version}}/docs/user-guide/horizontal-pod-autoscaling/).
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml b/v1.2/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml
deleted file mode 100644
index 1a2067714d..0000000000
--- a/v1.2/docs/user-guide/horizontal-pod-autoscaling/hpa-php-apache.yaml
+++ /dev/null
@@ -1,14 +0,0 @@
-apiVersion: extensions/v1beta1
-kind: HorizontalPodAutoscaler
-metadata:
-  name: php-apache
-  namespace: default
-spec:
-  scaleRef:
-    kind: ReplicationController
-    name: php-apache
-    namespace: default
-  minReplicas: 1
-  maxReplicas: 10
-  cpuUtilization:
-    targetPercentage: 50
diff --git a/v1.2/docs/user-guide/horizontal-pod-autoscaling/image/Dockerfile b/v1.2/docs/user-guide/horizontal-pod-autoscaling/image/Dockerfile
deleted file mode 100644
index 56f2d6252e..0000000000
--- a/v1.2/docs/user-guide/horizontal-pod-autoscaling/image/Dockerfile
+++ /dev/null
@@ -1,5 +0,0 @@
-FROM php:5-apache
-
-ADD index.php /var/www/html/index.php
-
-RUN chmod a+rx index.php
diff --git a/v1.2/docs/user-guide/horizontal-pod-autoscaling/image/index.php b/v1.2/docs/user-guide/horizontal-pod-autoscaling/image/index.php
deleted file mode 100755
index 8f0b1c0cf3..0000000000
--- a/v1.2/docs/user-guide/horizontal-pod-autoscaling/image/index.php
+++ /dev/null
@@ -1,7 +0,0 @@
-<?php
-$x = 0.0001;
-for ($i = 0; $i <= 1000000; $i++) {
-	$x += sqrt($x);
-}
-echo "OK!";
-?>
diff --git a/v1.2/docs/user-guide/identifiers.md b/v1.2/docs/user-guide/identifiers.md
deleted file mode 100644
index 44d820c6ab..0000000000
--- a/v1.2/docs/user-guide/identifiers.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
----
-
-All objects in the Kubernetes REST API are unambiguously identified by a Name and a UID.
-
-For non-unique user-provided attributes, Kubernetes provides [labels](/{{page.version}}/docs/user-guide/labels) and [annotations](/{{page.version}}/docs/user-guide/annotations).
-
-## Names
-
-Names are generally client-provided.  Only one object of a given kind can have a given name at a time (i.e., they are spatially unique).  But if you delete an object, you can make a new object with the same name.  Names are the used to refer to an object in a resource URL, such as `/api/v1/pods/some-name`.   By convention, the names of Kubernetes resources should be up to maximum length of 253 characters and consist of lower case alphanumeric characters, `-`, and `.`, but certain resources have more specific restrictions.  See the [identifiers design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/identifiers.md) for the precise syntax rules for names.
-
-## UIDs
-
-UID are generated by Kubernetes.  Every object created over the whole lifetime of a Kubernetes cluster has a distinct UID (i.e., they are spatially and temporally unique).
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/images.md b/v1.2/docs/user-guide/images.md
deleted file mode 100644
index 05020328f1..0000000000
--- a/v1.2/docs/user-guide/images.md
+++ /dev/null
@@ -1,237 +0,0 @@
----
----
-
-Each container in a pod has its own image.  Currently, the only type of image supported is a [Docker Image](https://docs.docker.com/userguide/dockerimages/).
-
-You create your Docker image and push it to a registry before referring to it in a Kubernetes pod.
-
-The `image` property of a container supports the same syntax as the `docker` command does, including private registries and tags.
-
-* TOC
-{:toc}
-
-
-## Updating Images
-
-The default pull policy is `IfNotPresent` which causes the Kubelet to not
-pull an image if it already exists. If you would like to always force a pull
-you must set a pull image policy of `Always` or specify a `:latest` tag on
-your image.
-
-## Using a Private Registry
-
-Private registries may require keys to read images from them.
-Credentials can be provided in several ways:
-
-  - Using Google Container Registry
-    - Per-cluster
-    - automatically configured on Google Compute Engine or Google Container Engine
-    - all pods can read the project's private registry
-  - Configuring Nodes to Authenticate to a Private Registry
-    - all pods can read any configured private registries
-    - requires node configuration by cluster administrator
-  - Pre-pulling Images
-    - all pods can use any images cached on a node
-    - requires root access to all nodes to setup
-  - Specifying ImagePullSecrets on a Pod
-    - only pods which provide own keys can access the private registry
-Each option is described in more detail below.
-
-
-### Using Google Container Registry
-
-Kubernetes has native support for the [Google Container
-Registry (GCR)](https://cloud.google.com/tools/container-registry/), when running on Google Compute
-Engine (GCE).  If you are running your cluster on GCE or Google Container Engine (GKE), simply
-use the full image name (e.g. gcr.io/my_project/image:tag).
-
-All pods in a cluster will have read access to images in this registry.
-
-The kubelet will authenticate to GCR using the instance's
-Google service account.  The service account on the instance
-will have a `https://www.googleapis.com/auth/devstorage.read_only`,
-so it can pull from the project's GCR, but not push.
-
-### Configuring Nodes to Authenticate to a Private Repository
-
-**Note:** if you are running on Google Container Engine (GKE), there will already be a `.dockercfg` on each node
-with credentials for Google Container Registry.  You cannot use this approach.
-
-**Note:** this approach is suitable if you can control node configuration.  It
-will not work reliably on GCE, and any other cloud provider that does automatic
-node replacement.
-
-Docker stores keys for private registries in the `$HOME/.dockercfg` file.  If you put this
-in the `$HOME` of `root` on a kubelet, then docker will use it.
-
-Here are the recommended steps to configuring your nodes to use a private registry.  In this
-example, run these on your desktop/laptop:
-
-   1. run `docker login [server]` for each set of credentials you want to use.
-   1. view `$HOME/.dockercfg` in an editor to ensure it contains just the credentials you want to use.
-   1. get a list of your nodes
-      - for example: `nodes=$(kubectl get nodes -o template --template='{{range.items}}{{.metadata.name}} {{end}}')`
-   1. copy your local `.dockercfg` to the home directory of root on each node.
-      - for example: `for n in $nodes; do scp ~/.dockercfg root@$n:/root/.dockercfg; done`
-
-Verify by creating a pod that uses a private image, e.g.:
-
-```yaml
-$ cat <<EOF > /tmp/private-image-test-1.yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: private-image-test-1
-spec:
-  containers:
-    - name: uses-private-image
-      image: $PRIVATE_IMAGE_NAME
-      imagePullPolicy: Always
-      command: [ "echo", "SUCCESS" ]
-EOF
-$ kubectl create -f /tmp/private-image-test-1.yaml
-pods/private-image-test-1
-$
-```
-
-If everything is working, then, after a few moments, you should see:
-
-```shell
-$ kubectl logs private-image-test-1
-SUCCESS
-```
-
-If it failed, then you will see:
-
-```shell
-$ kubectl describe pods/private-image-test-1 | grep "Failed"
-  Fri, 26 Jun 2015 15:36:13 -0700	Fri, 26 Jun 2015 15:39:13 -0700	19	{kubelet node-i2hq}	spec.containers{uses-private-image}	failed		Failed to pull image "user/privaterepo:v1": Error: image user/privaterepo:v1 not found
-```
-
-You must ensure all nodes in the cluster have the same `.dockercfg`.  Otherwise, pods will run on
-some nodes and fail to run on others.  For example, if you use node autoscaling, then each instance
-template needs to include the `.dockercfg` or mount a drive that contains it.
-
-All pods will have read access to images in any private registry once private
-registry keys are added to the `.dockercfg`.
-
-**This was tested with a private docker repository as of 26 June with Kubernetes version v0.19.3.
-It should also work for a private registry such as quay.io, but that has not been tested.**
-
-### Pre-pulling Images
-
-**Note:** if you are running on Google Container Engine (GKE), there will already be a `.dockercfg` on each node
-with credentials for Google Container Registry.  You cannot use this approach.
-
-**Note:** this approach is suitable if you can control node configuration.  It
-will not work reliably on GCE, and any other cloud provider that does automatic
-node replacement.
-
-Be default, the kubelet will try to pull each image from the specified registry.
-However, if the `imagePullPolicy` property of the container is set to `IfNotPresent` or `Never`,
-then a local image is used (preferentially or exclusively, respectively).
-
-If you want to rely on pre-pulled images as a substitute for registry authentication,
-you must ensure all nodes in the cluster have the same pre-pulled images.
-
-This can be used to preload certain images for speed or as an alternative to authenticating to a private registry.
-
-All pods will have read access to any pre-pulled images.
-
-### Specifying ImagePullSecrets on a Pod
-
-**Note:** This approach is currently the recommended approach for GKE, GCE, and any cloud-providers
-where node creation is automated.
-
-Kubernetes supports specifying registry keys on a pod.
-
-First, create a `.dockercfg`, such as running `docker login <registry.domain>`.
-Then put the resulting `.dockercfg` file into a [secret resource](/{{page.version}}/docs/user-guide/secrets).  For example:
-
-```shell
-$ docker login
-Username: janedoe
-Password: '�?'�?'�?'�?'�?'�?'�?'�?'�?'�?'�?
-Email: jdoe@example.com
-WARNING: login credentials saved in /Users/jdoe/.dockercfg.
-Login Succeeded
-
-$ echo $(cat ~/.dockercfg)
-{ "https://index.docker.io/v1/": { "auth": "ZmFrZXBhc3N3b3JkMTIK", "email": "jdoe@example.com" } }
-
-$ cat ~/.dockercfg | base64
-eyAiaHR0cHM6Ly9pbmRleC5kb2NrZXIuaW8vdjEvIjogeyAiYXV0aCI6ICJabUZyWlhCaGMzTjNiM0prTVRJSyIsICJlbWFpbCI6ICJqZG9lQGV4YW1wbGUuY29tIiB9IH0K
-
-$ cat > /tmp/image-pull-secret.yaml <<EOF
-apiVersion: v1
-kind: Secret
-metadata:
-  name: myregistrykey
-data:
-  .dockercfg: eyAiaHR0cHM6Ly9pbmRleC5kb2NrZXIuaW8vdjEvIjogeyAiYXV0aCI6ICJabUZyWlhCaGMzTjNiM0prTVRJSyIsICJlbWFpbCI6ICJqZG9lQGV4YW1wbGUuY29tIiB9IH0K
-type: kubernetes.io/dockercfg
-EOF
-
-$ kubectl create -f /tmp/image-pull-secret.yaml
-secrets/myregistrykey
-$
-```
-
-If you get the error message `error: no objects passed to create`, it may mean the base64 encoded string is invalid.
-If you get an error message like `Secret "myregistrykey" is invalid: data[.dockercfg]: invalid value ...` it means
-the data was successfully un-base64 encoded, but could not be parsed as a dockercfg file.
-
-This process only needs to be done one time (per namespace).
-
-Now, you can create pods which reference that secret by adding an `imagePullSecrets`
-section to a pod definition.
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: foo
-spec:
-  containers:
-    - name: foo
-      image: janedoe/awesomeapp:v1
-  imagePullSecrets:
-    - name: myregistrykey
-```
-
-This needs to be done for each pod that is using a private registry.
-However, setting of this field can be automated by setting the imagePullSecrets
-in a [serviceAccount](/{{page.version}}/docs/user-guide/service-accounts) resource.
-
-Currently, all pods will potentially have read access to any images which were
-pulled using imagePullSecrets.  That is, imagePullSecrets does *NOT* protect your
-images from being seen by other users in the cluster.  Our intent
-is to fix that.
-
-You can use this in conjunction with a per-node `.dockerfile`.  The credentials
-will be merged.  This approach will work on Google Container Engine (GKE).
-
-### Use Cases
-
-There are a number of solutions for configuring private registries.  Here are some
-common use cases and suggested solutions.
-
- 1. Cluster running only non-proprietary (e.g open-source) images.  No need to hide images.
-   - Use public images on the Docker hub.
-     - no configuration required
-     - on GCE/GKE, a local mirror is automatically used for improved speed and availability
- 1. Cluster running some proprietary images which should be hidden to those outside the company, but
-   visible to all cluster users.
-   - Use a hosted private [Docker registry](https://docs.docker.com/registry/)
-     - may be hosted on the [Docker Hub](https://hub.docker.com/account/signup/), or elsewhere.
-     - manually configure .dockercfg on each node as described above
-   - Or, run an internal private registry behind your firewall with open read access.
-     - no Kubernetes configuration required
-   - Or, when on GCE/GKE, use the project's Google Container Registry.
-     - will work better with cluster autoscaling than manual node configuration
-   - Or, on a cluster where changing the node configuration is inconvenient, use `imagePullSecrets`.
-  1. Cluster with a proprietary images, a few of which require stricter access control
-     - Move sensitive data into a "Secret" resource, instead of packaging it in an image.
-     - DO NOT use imagePullSecrets for this use case yet.
-  1. A multi-tenant cluster where each tenant needs own private registry
-     - NOT supported yet.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/index.md b/v1.2/docs/user-guide/index.md
deleted file mode 100644
index 6447b85d81..0000000000
--- a/v1.2/docs/user-guide/index.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-The user guide is intended for anyone who wants to run programs and services on an existing Kubernetes cluster.  Setup and administration of a Kubernetes cluster is described in the [Cluster Admin Guide](/{{page.version}}/docs/admin/). The [Developer Guide](/{{page.version}}/docs/devel/) is for anyone wanting to either write code which directly accesses the Kubernetes API, or to contribute directly to the Kubernetes project.
-
-Please ensure you have completed the [prerequisites for running examples from the user guide](/{{page.version}}/docs/user-guide/prereqs).
-
-## Quick walkthrough
-
-1. [Kubernetes 101](/{{page.version}}/docs/user-guide/walkthrough/)
-1. [Kubernetes 201](/{{page.version}}/docs/user-guide/walkthrough/k8s201)
-
-## Thorough walkthrough
-
-If you don't have much familiarity with Kubernetes, we recommend you read the following sections in order:
-
-1. [Quick start: launch and expose an application](/{{page.version}}/docs/user-guide/quick-start)
-1. [Configuring and launching containers: configuring common container parameters](/{{page.version}}/docs/user-guide/configuring-containers)
-1. [Deploying continuously running applications](/{{page.version}}/docs/user-guide/deploying-applications)
-1. [Connecting applications: exposing applications to clients and users](/{{page.version}}/docs/user-guide/connecting-applications)
-1. [Working with containers in production](/{{page.version}}/docs/user-guide/production-pods)
-1. [Managing deployments](/{{page.version}}/docs/user-guide/managing-deployments)
-1. [Application introspection and debugging](/{{page.version}}/docs/user-guide/introspection-and-debugging)
-    1. [Using the Kubernetes web user interface](/{{page.version}}/docs/user-guide/ui)
-    1. [Logging](/{{page.version}}/docs/user-guide/logging)
-    1. [Monitoring](/{{page.version}}/docs/user-guide/monitoring)
-    1. [Getting into containers via `exec`](/{{page.version}}/docs/user-guide/getting-into-containers)
-    1. [Connecting to containers via proxies](/{{page.version}}/docs/user-guide/connecting-to-applications-proxy)
-    1. [Connecting to containers via port forwarding](/{{page.version}}/docs/user-guide/connecting-to-applications-port-forward)
-
-## Concept guide
-
-[**Overview**](/{{page.version}}/docs/user-guide/overview)
-: A brief overview of Kubernetes concepts.
-
-[**Cluster**](/{{page.version}}/docs/admin/)
-: A cluster is a set of physical or virtual machines and other infrastructure resources used by Kubernetes to run your applications.
-
-[**Node**](/{{page.version}}/docs/admin/node)
-: A node is a physical or virtual machine running Kubernetes, onto which pods can be scheduled.
-
-[**Pod**](/{{page.version}}/docs/user-guide/pods)
-: A pod is a co-located group of containers and volumes.
-
-[**Label**](/{{page.version}}/docs/user-guide/labels)
-: A label is a key/value pair that is attached to a resource, such as a pod, to convey a user-defined identifying attribute. Labels can be used to organize and to select subsets of resources.
-
-[**Selector**](/{{page.version}}/docs/user-guide/labels/#label-selectors)
-: A selector is an expression that matches labels in order to identify related resources, such as which pods are targeted by a load-balanced service.
-
-[**Replication Controller**](/{{page.version}}/docs/user-guide/replication-controller)
-: A replication controller ensures that a specified number of pod replicas are running at any one time. It both allows for easy scaling of replicated systems and handles re-creation of a pod when the machine it is on reboots or otherwise fails.
-
-[**Service**](/{{page.version}}/docs/user-guide/services)
-: A service defines a set of pods and a means by which to access them, such as single stable IP address and corresponding DNS name.
-
-[**Volume**](/{{page.version}}/docs/user-guide/volumes)
-: A volume is a directory, possibly with some data in it, which is accessible to a Container as part of its filesystem.  Kubernetes volumes build upon [Docker Volumes](https://docs.docker.com/userguide/dockervolumes/), adding provisioning of the volume directory and/or device.
-
-[**Secret**](/{{page.version}}/docs/user-guide/secrets)
-: A secret stores sensitive data, such as authentication tokens, which can be made available to containers upon request.
-
-[**Name**](/{{page.version}}/docs/user-guide/identifiers)
-: A user- or client-provided name for a resource.
-
-[**Namespace**](/{{page.version}}/docs/user-guide/namespaces)
-: A namespace is like a prefix to the name of a resource. Namespaces help different projects, teams, or customers to share a cluster, such as by preventing name collisions between unrelated teams.
-
-[**Annotation**](/{{page.version}}/docs/user-guide/annotations)
-: A key/value pair that can hold larger (compared to a label), and possibly not human-readable, data, intended to store non-identifying auxiliary data, especially data manipulated by tools and system extensions.  Efficient filtering by annotation values is not supported.
-
-## Further reading
-
-* API resources
-  * [Working with resources](/{{page.version}}/docs/user-guide/working-with-resources)
-
-* Pods and containers
-  * [Pod lifecycle and restart policies](/{{page.version}}/docs/user-guide/pod-states)
-  * [Lifecycle hooks](/{{page.version}}/docs/user-guide/container-environment)
-  * [Compute resources, such as cpu and memory](/{{page.version}}/docs/user-guide/compute-resources)
-  * [Specifying commands and requesting capabilities](/{{page.version}}/docs/user-guide/containers)
-  * [Downward API: accessing system configuration from a pod](/{{page.version}}/docs/user-guide/downward-api)
-  * [Images and registries](/{{page.version}}/docs/user-guide/images)
-  * [Migrating from docker-cli to kubectl](/{{page.version}}/docs/user-guide/docker-cli-to-kubectl)
-  * [Tips and tricks when working with config](/{{page.version}}/docs/user-guide/config-best-practices)
-  * [Assign pods to selected nodes](/{{page.version}}/docs/user-guide/node-selection/)
-  * [Perform a rolling update on a running group of pods](/{{page.version}}/docs/user-guide/update-demo/)
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/ingress.md b/v1.2/docs/user-guide/ingress.md
deleted file mode 100644
index b84db5c494..0000000000
--- a/v1.2/docs/user-guide/ingress.md
+++ /dev/null
@@ -1,265 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-__Terminology__
-
-Throughout this doc you will see a few terms that are sometimes used interchangably elsewhere, that might cause confusion. This section attempts to clarify them.
-
-* Node: A single virtual or physical machine in a Kubernetes cluster.
-* Cluster: A group of nodes firewalled from the internet, that are the primary compute resources managed by Kubernetes.
-* Edge router: A router that enforces the firewall policy for your cluster. This could be a gateway managed by a cloudprovider or a physical piece of hardware.
-* Cluster network: A set of links, logical or physical, that facilitate communication within a cluster according to the [Kubernetes networking model](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/admin/networking.md). Examples of a Cluster network include Overlays such as [flannel](https://github.com/coreos/flannel#flannel) or SDNs such as [OVS](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/admin/ovs-networking.md).
-* Service: A Kubernetes [Service](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/services.md) that identifies a set of pods using label selectors. Unless mentioned otherwise, Services are assumed to have virtual IPs only routable within the cluster network.
-
-## What is Ingress?
-
-Typically, services and pods have IPs only routable by the cluster network. All traffic that ends up at an edge router is either dropped or forwarded elsewhere. Conceptually, this might look like:
-
-```
-internet
-        |
-  ------------
-  [ Services ]
-```
-
-An Ingress is a collection of rules that allow inbound connections to reach the cluster services.
-
-```
-internet
-        |
-   [ Ingress ]
-   --|-----|--
-   [ Services ]
-```
-
-It can be configured to give services externally-reachable urls, load balance traffic, terminate SSL, offer name based virtual hosting etc. Users request ingress by POSTing the Ingress resource to the API server. An [Ingress controller](#ingress-controllers) is responsible for fulfilling the Ingress, usually with a loadbalancer, though it may also configure your edge router or additional frontends to help handle the traffic in an HA manner.
-
-## Prerequisites
-
-Before you start using the Ingress resource, there are a few things you should understand:
-
-* The Ingress resource is not available in any Kubernetes release prior to 1.1
-* You need an Ingress controller to satisfy an Ingress. Simply creating the resource will have no effect.
-* On GCE/GKE there should be a [L7 cluster addon](https://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-loadbalancing/glbc/README.md#prerequisites), on other platforms you either need to write your own or [deploy an existing controller](https://github.com/kubernetes/contrib/tree/master/Ingress) as a pod.
-* The resource currently does not support HTTPS, but will do so before it leaves beta.
-
-## The Ingress Resource
-
-A minimal Ingress might look like:
-
-```yaml
-apiVersion: extensions/v1beta1
-kind: Ingress
-metadata:
-name: test-ingress
-spec:
-rules:
-- http:
-    paths:
-    - path: /testpath
-    backend:
-        serviceName: test
-        servicePort: 80
-```
-
-*POSTing this to the API server will have no effect if you have not configured an [Ingress controller](#ingress-controllers).*
-
-__Lines 1-4__: As with all other Kubernetes config, an Ingress needs `apiVersion`, `kind`, and `metadata` fields.  For general information about working with config files, see [here](/{{page.version}}/docs/user-guide/simple-yaml), [here](/{{page.version}}/docs/user-guide/configuring-containers), and [here](/{{page.version}}/docs/user-guide/working-with-resources).
-
-__Lines 5-7__: Ingress [spec](/{{page.version}}/docs/devel/api-conventions/#spec-and-status) has all the information needed to configure a loadbalancer or proxy server. Most importantly, it contains a list of rules matched against all incoming requests. Currently the Ingress resource only supports http rules.
-
-__Lines 8-9__: Each http rule contains the following information: A host (eg: foo.bar.com, defaults to * in this example), a list of paths (eg: /testpath) each of which has an associated backend (test:80). Both the host and path must match the content of an incoming request before the loadbalancer directs traffic to the backend.
-
-__Lines 10-12__: A backend is a service:port combination as described in the [services doc](/{{page.version}}/docs/user-guide/services). Ingress traffic is typically sent directly to the endpoints matching a backend.
-
-__Global Parameters__: For the sake of simplicity the example Ingress has no global parameters, see the [api-reference](https://releases.k8s.io/{{page.githubbranch}}/pkg/apis/extensions/v1beta1/types.go) for a full definition of the resource. One can specify a global default backend in the absence of which requests that don't match a path in the spec are sent to the default backend of the Ingress controller. Though the Ingress resource doesn't support HTTPS yet, security configs would also be global.
-
-## Ingress controllers
-
-In order for the Ingress resource to work, the cluster must have an Ingress controller running. This is unlike other types of controllers, which typically run as part of the `kube-controller-manager` binary, and which are typically started automatically as part of cluster creation. You need to choose the ingress controller implementation that is the best fit for your cluster, or implement one.  Examples and instructions can be found [here](https://github.com/kubernetes/contrib/tree/master/Ingress).
-
-## Types of Ingress
-
-### Single Service Ingress
-
-There are existing Kubernetes concepts that allow you to expose a single service (see [alternatives](#alternatives)), however you can do so through an Ingress as well, by specifying a *default backend* with no rules.
-
-<!-- BEGIN MUNGE: EXAMPLE ingress.yaml -->
-
-```yaml
-apiVersion: extensions/v1beta1
-kind: Ingress
-metadata:
-  name: test-ingress
-spec:
-  backend:
-    serviceName: testsvc
-    servicePort: 80
-```
-
-[Download example](/{{page.version}}/docs/user-guide/ingress.yaml)
-<!-- END MUNGE: EXAMPLE ingress.yaml -->
-
-If you create it using `kubectl -f` you should see:
-
-```shell
-$ kubectl get ing
-NAME                RULE          BACKEND        ADDRESS
-test-ingress        -             testsvc:80     107.178.254.228
-```
-
-Where `107.178.254.228` is the IP allocated by the Ingress controller to satisfy this Ingress. The `RULE` column shows that all traffic send to the IP is directed to the Kubernetes Service listed under `BACKEND`.
-
-### Simple fanout
-
-As described previously, pods within kubernetes have ips only visible on the cluster network, so we need something at the edge accepting ingress traffic and proxying it to the right endpoints. This component is usually a highly available loadbalancer/s. An Ingress allows you to keep the number of loadbalancers down to a minimum, for example, a setup like:
-
-```shell
-foo.bar.com -> 178.91.123.132 -> / foo    s1:80
-                                 / bar    s2:80
-```
-
-would require an Ingress such as:
-
-```yaml
-apiVersion: extensions/v1beta1
-kind: Ingress
-metadata:
-  name: test
-spec:
-  rules:
-  - host: foo.bar.com
-    http:
-      paths:
-      - path: /foo
-        backend:
-          serviceName: s1
-          servicePort: 80
-      - path: /bar
-        backend:
-          serviceName: s2
-          servicePort: 80
-```
-
-When you create the Ingress with `kubectl create -f`:
-
-```shell
-$ kubectl get ing
-NAME      RULE          BACKEND   ADDRESS
-test      -
-          foo.bar.com
-          /foo          s1:80
-          /bar          s2:80
-```
-The Ingress controller will provision an implementation specific loadbalancer that satisfies the Ingress, as long as the services (s1, s2) exist. When it has done so, you will see the address of the loadbalancer under the last column of the Ingress.
-
-### Name based virtual hosting
-
-Name-based virtual hosts use multiple host names for the same IP address.
-
-```
-foo.bar.com --|                 |-> foo.bar.com s1:80
-              | 178.91.123.132  |
-bar.foo.com --|                 |-> bar.foo.com s2:80
-```
-
-The following Ingress tells the backing loadbalancer to route requests based on the [Host header](https://tools.ietf.org/html/rfc7230#section-5.4).
-
-```yaml
-apiVersion: extensions/v1beta1
-kind: Ingress
-metadata:
-  name: test
-spec:
-  rules:
-  - host: foo.bar.com
-    http:
-      paths:
-      - backend:
-          serviceName: s1
-          servicePort: 80
-  - host: bar.foo.com
-    http:
-      paths:
-      - backend:
-          serviceName: s2
-          servicePort: 80
-```
-
-__Default Backends__: An Ingress with no rules, like the one shown in the previous section, sends all traffic to a single default backend. You can use the same technique to tell a loadbalancer where to find your website's 404 page, by specifying a set of rules *and* a default backend. Traffic is routed to your default backend if none of the Hosts in your Ingress match the Host in the request header, and/or none of the paths match the url of the request.
-
-### Loadbalancing
-
-An Ingress controller is bootstrapped with some loadbalancing policy settings that it applies to all Ingress, such as the loadbalancing algorithm, backend weight scheme etc. More advanced loadbalancing concepts (eg: persistent sessions, dynamic weights) are not yet exposed through the Ingress. You can still get these features through the [service loadbalancer](https://github.com/kubernetes/contrib/tree/master/service-loadbalancer). With time, we plan to distil loadbalancing patterns that are applicable cross platform into the Ingress resource.
-
-It's also worth noting that even though health checks are not exposed directly through the Ingress, there exist parallel concepts in Kubernetes such as [readiness probes](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/production-pods.md#liveness-and-readiness-probes-aka-health-checks) which allow you to achieve the same end result.
-
-## Updating an Ingress
-
-Say you'd like to add a new Host to an existing Ingress, you can update it by editing the resource:
-
-```shell
-$ kubectl get ing
-NAME      RULE          BACKEND   ADDRESS
-test      -                       178.91.123.132
-          foo.bar.com
-          /foo          s1:80
-$ kubectl edit ing test
-```
-
-This should pop up an editor with the existing yaml, modify it to include the new Host.
-
-```yaml
-spec:
-  rules:
-  - host: foo.bar.com
-    http:
-      paths:
-      - backend:
-          serviceName: s1
-          servicePort: 80
-        path: /foo
-  - host: bar.baz.com
-    http:
-      paths:
-      - backend:
-          serviceName: s2
-          servicePort: 80
-        path: /foo
-..
-```
-
-saving it will update the resource in the API server, which should tell the Ingress controller to reconfigure the loadbalancer.
-
-```shell
-$ kubectl get ing
-NAME      RULE          BACKEND   ADDRESS
-test      -                       178.91.123.132
-          foo.bar.com
-          /foo          s1:80
-          bar.baz.com
-          /foo          s2:80
-```
-
-You can achieve the same by invoking `kubectl replace -f` on a modified Ingress yaml file.
-
-## Future Work
-
-* Various modes of HTTPS/TLS support (edge termination, sni etc)
-* Requesting an IP or Hostname via claims
-* Combining L4 and L7 Ingress
-* More Ingress controllers
-
-Please track the [L7 and Ingress proposal](https://github.com/kubernetes/kubernetes/pull/12827) for more details on the evolution of the resource, and the [Ingress sub-repository](https://github.com/kubernetes/contrib/tree/master/Ingress) for more details on the evolution of various Ingress controllers.
-
-## Alternatives
-
-You can expose a Service in multiple ways that don't directly involve the Ingress resource:
-
-* Use [Service.Type=LoadBalancer](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/services.md#type-loadbalancer)
-* Use [Service.Type=NodePort](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/services.md#type-nodeport)
-* Use a [Port Proxy] (https://github.com/kubernetes/contrib/tree/master/for-demos/proxy-to-service)
-* Deploy the [Service loadbalancer](https://github.com/kubernetes/contrib/tree/master/service-loadbalancer). This allows you to share a single IP among multiple Services and achieve more advanced loadbalancing through Service Annotations.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/ingress.yaml b/v1.2/docs/user-guide/ingress.yaml
deleted file mode 100644
index 163c1d5b9d..0000000000
--- a/v1.2/docs/user-guide/ingress.yaml
+++ /dev/null
@@ -1,9 +0,0 @@
-apiVersion: extensions/v1beta1
-kind: Ingress
-metadata:
-  name: test-ingress
-spec:
-  backend:
-    serviceName: testsvc
-    servicePort: 80
-
diff --git a/v1.2/docs/user-guide/introspection-and-debugging.md b/v1.2/docs/user-guide/introspection-and-debugging.md
deleted file mode 100644
index 3933342eaf..0000000000
--- a/v1.2/docs/user-guide/introspection-and-debugging.md
+++ /dev/null
@@ -1,316 +0,0 @@
----
----
-
-Once your application is running, you'll inevitably need to debug problems with it.
-Earlier we described how you can use `kubectl get pods` to retrieve simple status information about
-your pods. But there are a number of ways to get even more information about your application.
-
-* TOC
-{:toc}
-
-## Using `kubectl describe pod` to fetch details about pods
-
-For this example we'll use a ReplicationController to create two pods, similar to the earlier example.
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx
-spec:
-  replicas: 2
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        resources:
-          limits:
-            memory: "128Mi"
-            cpu: "500m"
-        ports:
-        - containerPort: 80
-```
-
-```shell
-$ kubectl create -f ./my-nginx-rc.yaml
-replicationcontrollers/my-nginx
-```
-
-```shell
-$ kubectl get pods
-NAME             READY     REASON    RESTARTS   AGE
-my-nginx-gy1ij   1/1       Running   0          1m
-my-nginx-yv5cn   1/1       Running   0          1m
-```
-
-We can retrieve a lot more information about each of these pods using `kubectl describe pod`. For example:
-
-```shell
-$ kubectl describe pod my-nginx-gy1ij
-Name:				my-nginx-gy1ij
-Image(s):			nginx
-Node:				kubernetes-minion-y3vk/10.240.154.168
-Labels:				app=nginx
-Status:				Running
-Reason:				
-Message:			
-IP:				10.244.1.4
-Replication Controllers:	my-nginx (2/2 replicas created)
-Containers:
-  nginx:
-    Image:	nginx
-    Limits:
-      cpu:		500m
-      memory:		128Mi
-    State:		Running
-      Started:		Thu, 09 Jul 2015 15:33:07 -0700
-    Ready:		True
-    Restart Count:	0
-Conditions:
-  Type		Status
-  Ready 	True 
-Events:
-  FirstSeen				LastSeen			Count	From					SubobjectPath				Reason		Message
-  Thu, 09 Jul 2015 15:32:58 -0700	Thu, 09 Jul 2015 15:32:58 -0700	1	{scheduler }									scheduled	Successfully assigned my-nginx-gy1ij to kubernetes-minion-y3vk
-  Thu, 09 Jul 2015 15:32:58 -0700	Thu, 09 Jul 2015 15:32:58 -0700	1	{kubelet kubernetes-minion-y3vk}	implicitly required container POD	pulled		Pod container image "gcr.io/google_containers/pause:0.8.0" already present on machine
-  Thu, 09 Jul 2015 15:32:58 -0700	Thu, 09 Jul 2015 15:32:58 -0700	1	{kubelet kubernetes-minion-y3vk}	implicitly required container POD	created		Created with docker id cd1644065066
-  Thu, 09 Jul 2015 15:32:58 -0700	Thu, 09 Jul 2015 15:32:58 -0700	1	{kubelet kubernetes-minion-y3vk}	implicitly required container POD	started		Started with docker id cd1644065066
-  Thu, 09 Jul 2015 15:33:06 -0700	Thu, 09 Jul 2015 15:33:06 -0700	1	{kubelet kubernetes-minion-y3vk}	spec.containers{nginx}			pulled		Successfully pulled image "nginx"
-  Thu, 09 Jul 2015 15:33:06 -0700	Thu, 09 Jul 2015 15:33:06 -0700	1	{kubelet kubernetes-minion-y3vk}	spec.containers{nginx}			created		Created with docker id 56d7a7b14dac
-  Thu, 09 Jul 2015 15:33:07 -0700	Thu, 09 Jul 2015 15:33:07 -0700	1	{kubelet kubernetes-minion-y3vk}	spec.containers{nginx}			started		Started with docker id 56d7a7b14dac
-```
-
-Here you can see configuration information about the container(s) and Pod (labels, resource requirements, etc.), as well as status information about the container(s) and Pod (state, readiness, restart count, events, etc.)
-
-The container state is one of Waiting, Running, or Terminated. Depending on the state, additional information will be provided -- here you can see that for a container in Running state, the system tells you when the container started.
-
-Ready tells you whether the container passed its last readiness probe. (In this case, the container does not have a readiness probe configured; the container is assumed to be ready if no readiness probe is configured.)
-
-Restart Count tells you how many times the container has restarted; this information can be useful for detecting crash loops in containers that are configured with a restart policy of 'always.'?
-
-Currently the only Condition associated with a Pod is the binary Ready condition, which indicates that the pod is able to service requests and should be added to the load balancing pools of all matching services.
-
-Lastly, you see a log of recent events related to your Pod. The system compresses multiple identical events by indicating the first and last time it was seen and the number of times it was seen. "From" indicates the component that is logging the event, "SubobjectPath" tells you which object (e.g. container within the pod) is being referred to, and "Reason" and "Message" tell you what happened.
-
-## Example: debugging Pending Pods
-
-A common scenario that you can detect using events is when you've created a Pod that won't fit on any node. For example, the Pod might request more resources than are free on any node, or it might specify a label selector that doesn't match any nodes. Let's say we created the previous Replication Controller with 5 replicas (instead of 2) and requesting 600 millicores instead of 500, on a four-node cluster where each (virtual) machine has 1 CPU. In that case one of the Pods will not be able to schedule. (Note that because of the cluster addon pods such as fluentd, skydns, etc., that run on each node, if we requested 1000 millicores then none of the Pods would be able to schedule.)
-
-```shell
-$ kubectl get pods
-NAME             READY     REASON    RESTARTS   AGE
-my-nginx-9unp9   0/1       Pending   0          8s
-my-nginx-b7zs9   0/1       Running   0          8s
-my-nginx-i595c   0/1       Running   0          8s
-my-nginx-iichp   0/1       Running   0          8s
-my-nginx-tc2j9   0/1       Running   0          8s
-```
-
-To find out why the my-nginx-9unp9 pod is not running, we can use `kubectl describe pod` on the pending Pod and look at its events:
-
-```shell
-$ kubectl describe pod my-nginx-9unp9 
-Name:				my-nginx-9unp9
-Image(s):			nginx
-Node:				/
-Labels:				app=nginx
-Status:				Pending
-Reason:				
-Message:			
-IP:				
-Replication Controllers:	my-nginx (5/5 replicas created)
-Containers:
-  nginx:
-    Image:	nginx
-    Limits:
-      cpu:		600m
-      memory:		128Mi
-    State:		Waiting
-    Ready:		False
-    Restart Count:	0
-Events:
-  FirstSeen				LastSeen			Count	From		SubobjectPath	Reason			Message
-  Thu, 09 Jul 2015 23:56:21 -0700	Fri, 10 Jul 2015 00:01:30 -0700	21	{scheduler }			failedScheduling	Failed for reason PodFitsResources and possibly others
-```
-
-Here you can see the event generated by the scheduler saying that the Pod failed to schedule for reason `PodFitsResources` (and possibly others). `PodFitsResources` means there were not enough resources for the Pod on any of the nodes. Due to the way the event is generated, there may be other reasons as well, hence "and possibly others."
-
-To correct this situation, you can use `kubectl scale` to update your Replication Controller to specify four or fewer replicas. (Or you could just leave the one Pod pending, which is harmless.)
-
-Events such as the ones you saw at the end of `kubectl describe pod` are persisted in etcd and provide high-level information on what is happening in the cluster. To list all events you can use
-
-```shell
-kubectl get events
-```
-
-but you have to remember that events are namespaced. This means that if you're interested in events for some namespaced object (e.g. what happened with Pods in namespace `my-namespace`) you need to explicitly provide a namespace to the command:
-
-```shell
-kubectl get events --namespace=my-namespace
-```
-
-To see events from all namespaces, you can use the `--all-namespaces` argument.
-
-In addition to `kubectl describe pod`, another way to get extra information about a pod (beyond what is provided by `kubectl get pod`) is to pass the `-o yaml` output format flag to `kubectl get pod`. This will give you, in YAML format, even more information than `kubectl describe pod`--essentially all of the information the system has about the Pod. Here you will see things like annotations (which are key-value metadata without the label restrictions, that is used internally by Kubernetes system components), restart policy, ports, and volumes.
-
-```yaml
-$ kubectl get pod my-nginx-i595c -o yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  annotations:
-    kubernetes.io/created-by: '{"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicationController","namespace":"default","name":"my-nginx","uid":"c555c14f-26d0-11e5-99cb-42010af00e4b","apiVersion":"v1","resourceVersion":"26174"}}'
-  creationTimestamp: 2015-07-10T06:56:21Z
-  generateName: my-nginx-
-  labels:
-    app: nginx
-  name: my-nginx-i595c
-  namespace: default
-  resourceVersion: "26243"
-  selfLink: /api/v1/namespaces/default/pods/my-nginx-i595c
-  uid: c558e44b-26d0-11e5-99cb-42010af00e4b
-spec:
-  containers:
-  - image: nginx
-    imagePullPolicy: IfNotPresent
-    name: nginx
-    ports:
-    - containerPort: 80
-      protocol: TCP
-    resources:
-      limits:
-        cpu: 600m
-        memory: 128Mi
-    terminationMessagePath: /dev/termination-log
-    volumeMounts:
-    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
-      name: default-token-zkhkk
-      readOnly: true
-  dnsPolicy: ClusterFirst
-  nodeName: kubernetes-minion-u619
-  restartPolicy: Always
-  serviceAccountName: default
-  volumes:
-  - name: default-token-zkhkk
-    secret:
-      secretName: default-token-zkhkk
-status:
-  conditions:
-  - status: "True"
-    type: Ready
-  containerStatuses:
-  - containerID: docker://9506ace0eb91fbc31aef1d249e0d1d6d6ef5ebafc60424319aad5b12e3a4e6a9
-    image: nginx
-    imageID: docker://319d2015d149943ff4d2a20ddea7d7e5ce06a64bbab1792334c0d3273bbbff1e
-    lastState: {}
-    name: nginx
-    ready: true
-    restartCount: 0
-    state:
-      running:
-        startedAt: 2015-07-10T06:56:28Z
-  hostIP: 10.240.112.234
-  phase: Running
-  podIP: 10.244.3.4
-  startTime: 2015-07-10T06:56:21Z
-```
-
-## Example: debugging a down/unreachable node
-
-Sometimes when debugging it can be useful to look at the status of a node -- for example, because you've noticed strange behavior of a Pod that's running on the node, or to find out why a Pod won't schedule onto the node. As with Pods, you can use `kubectl describe node` and `kubectl get node -o yaml` to retrieve detailed information about nodes. For example, here's what you'll see if a node is down (disconnected from the network, or kubelet dies and won't restart, etc.). Notice the events that show the node is NotReady, and also notice that the pods are no longer running (they are evicted after five minutes of NotReady status).
-
-```shell
-$ kubectl get nodes
-NAME                     LABELS                                          STATUS
-kubernetes-minion-861h   kubernetes.io/hostname=kubernetes-minion-861h   NotReady
-kubernetes-minion-bols   kubernetes.io/hostname=kubernetes-minion-bols   Ready
-kubernetes-minion-st6x   kubernetes.io/hostname=kubernetes-minion-st6x   Ready
-kubernetes-minion-unaj   kubernetes.io/hostname=kubernetes-minion-unaj   Ready
-
-$ kubectl describe node kubernetes-minion-861h
-Name:			kubernetes-minion-861h
-Labels:			kubernetes.io/hostname=kubernetes-minion-861h
-CreationTimestamp:	Fri, 10 Jul 2015 14:32:29 -0700
-Conditions:
-  Type		Status		LastHeartbeatTime			LastTransitionTime			Reason					Message
-  Ready 	Unknown 	Fri, 10 Jul 2015 14:34:32 -0700 	Fri, 10 Jul 2015 14:35:15 -0700 	Kubelet stopped posting node status. 	
-Addresses:	10.240.115.55,104.197.0.26
-Capacity:
- cpu:		1
- memory:	3800808Ki
- pods:		100
-Version:
- Kernel Version:		3.16.0-0.bpo.4-amd64
- OS Image:			Debian GNU/Linux 7 (wheezy)
- Container Runtime Version:	docker://Unknown
- Kubelet Version:		v0.21.1-185-gffc5a86098dc01
- Kube-Proxy Version:		v0.21.1-185-gffc5a86098dc01
-PodCIDR:			10.244.0.0/24
-ExternalID:			15233045891481496305
-Pods:				(0 in total)
-  Namespace			Name
-Events:
-  FirstSeen				LastSeen			Count	From					SubobjectPath	Reason		Message
-  Fri, 10 Jul 2015 14:32:28 -0700	Fri, 10 Jul 2015 14:32:28 -0700	1	{kubelet kubernetes-minion-861h}			NodeNotReady	Node kubernetes-minion-861h status is now: NodeNotReady
-  Fri, 10 Jul 2015 14:32:30 -0700	Fri, 10 Jul 2015 14:32:30 -0700	1	{kubelet kubernetes-minion-861h}			NodeNotReady	Node kubernetes-minion-861h status is now: NodeNotReady
-  Fri, 10 Jul 2015 14:33:00 -0700	Fri, 10 Jul 2015 14:33:00 -0700	1	{kubelet kubernetes-minion-861h}			starting	Starting kubelet.
-  Fri, 10 Jul 2015 14:33:02 -0700	Fri, 10 Jul 2015 14:33:02 -0700	1	{kubelet kubernetes-minion-861h}			NodeReady	Node kubernetes-minion-861h status is now: NodeReady
-  Fri, 10 Jul 2015 14:35:15 -0700	Fri, 10 Jul 2015 14:35:15 -0700	1	{controllermanager }					NodeNotReady	Node kubernetes-minion-861h status is now: NodeNotReady
-
-
-$ kubectl get node kubernetes-minion-861h -o yaml
-apiVersion: v1
-kind: Node
-metadata:
-  creationTimestamp: 2015-07-10T21:32:29Z
-  labels:
-    kubernetes.io/hostname: kubernetes-minion-861h
-  name: kubernetes-minion-861h
-  resourceVersion: "757"
-  selfLink: /api/v1/nodes/kubernetes-minion-861h
-  uid: 2a69374e-274b-11e5-a234-42010af0d969
-spec:
-  externalID: "15233045891481496305"
-  podCIDR: 10.244.0.0/24
-  providerID: gce://striped-torus-760/us-central1-b/kubernetes-minion-861h
-status:
-  addresses:
-  - address: 10.240.115.55
-    type: InternalIP
-  - address: 104.197.0.26
-    type: ExternalIP
-  capacity:
-    cpu: "1"
-    memory: 3800808Ki
-    pods: "100"
-  conditions:
-  - lastHeartbeatTime: 2015-07-10T21:34:32Z
-    lastTransitionTime: 2015-07-10T21:35:15Z
-    reason: Kubelet stopped posting node status.
-    status: Unknown
-    type: Ready
-  nodeInfo:
-    bootID: 4e316776-b40d-4f78-a4ea-ab0d73390897
-    containerRuntimeVersion: docker://Unknown
-    kernelVersion: 3.16.0-0.bpo.4-amd64
-    kubeProxyVersion: v0.21.1-185-gffc5a86098dc01
-    kubeletVersion: v0.21.1-185-gffc5a86098dc01
-    machineID: ""
-    osImage: Debian GNU/Linux 7 (wheezy)
-    systemUUID: ABE5F6B4-D44B-108B-C46A-24CCE16C8B6E
-```
-
-## What's next?
-
-Learn about additional debugging tools, including:
-
-* [Logging](/{{page.version}}/docs/user-guide/logging)
-* [Monitoring](/{{page.version}}/docs/user-guide/monitoring)
-* [Getting into containers via `exec`](/{{page.version}}/docs/user-guide/getting-into-containers)
-* [Connecting to containers via proxies](/{{page.version}}/docs/user-guide/connecting-to-applications-proxy)
-* [Connecting to containers via port forwarding](/{{page.version}}/docs/user-guide/connecting-to-applications-port-forward)
-
diff --git a/v1.2/docs/user-guide/job.yaml b/v1.2/docs/user-guide/job.yaml
deleted file mode 100644
index c1c7008233..0000000000
--- a/v1.2/docs/user-guide/job.yaml
+++ /dev/null
@@ -1,20 +0,0 @@
-apiVersion: extensions/v1beta1
-kind: Job
-metadata:
-  name: pi
-spec:
-  selector:
-    matchLabels:
-      app: pi
-  template:
-    metadata:
-      name: pi
-      labels:
-        app: pi
-    spec:
-      containers:
-      - name: pi
-        image: perl
-        command: ["perl",  "-Mbignum=bpi", "-wle", "print bpi(2000)"]
-      restartPolicy: Never
-
diff --git a/v1.2/docs/user-guide/jobs.md b/v1.2/docs/user-guide/jobs.md
deleted file mode 100644
index 5363e492d4..0000000000
--- a/v1.2/docs/user-guide/jobs.md
+++ /dev/null
@@ -1,210 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-## What is a _job_?
-
-A _job_ creates one or more pods and ensures that a specified number of them successfully terminate.
-As pods successfully complete, the _job_ tracks the successful completions.  When a specified number
-of successful completions is reached, the job itself is complete.  Deleting a Job will cleanup the
-pods it created.
-
-A simple case is to create 1 Job object in order to reliably run one Pod to completion.
-A Job can also be used to run multiple pods in parallel.
-
-## Running an example Job
-
-Here is an example Job config.  It computes π to 2000 places and prints it out.
-It takes around 10s to complete.
-<!-- BEGIN MUNGE: EXAMPLE job.yaml -->
-
-```yaml
-apiVersion: extensions/v1beta1
-kind: Job
-metadata:
-  name: pi
-spec:
-  selector:
-    matchLabels:
-      app: pi
-  template:
-    metadata:
-      name: pi
-      labels:
-        app: pi
-    spec:
-      containers:
-      - name: pi
-        image: perl
-        command: ["perl",  "-Mbignum=bpi", "-wle", "print bpi(2000)"]
-      restartPolicy: Never
-```
-
-[Download example](/{{page.version}}/docs/user-guide/job.yaml)
-<!-- END MUNGE: EXAMPLE job.yaml -->
-
-Run the example job by downloading the example file and then running this command:
-
-```shell
-$ kubectl create -f ./job.yaml
-jobs/pi
-```
-
-Check on the status of the job using this command:
-
-```shell
-$ kubectl describe jobs/pi
-Name:		pi
-Namespace:	default
-Image(s):	perl
-Selector:	app=pi
-Parallelism:	2
-Completions:	1
-Labels:		<none>
-Pods Statuses:	1 Running / 0 Succeeded / 0 Failed
-Events:
-  FirstSeen	LastSeen	Count	From	SubobjectPath	Reason			Message
-  '��'��'��'��'��'��'��'��'��	'��'��'��'��'��'��'��'��	'��'��'��'��'��	'��'��'��'��	'��'��'��'��'��'��'��'��'��'��'��'��'��	'��'��'��'��'��'��			'��'��'��'��'��'��'��
-  1m		1m		1	{job }			SuccessfulCreate	Created pod: pi-z548a
-```
-
-To view completed pods of a job, use `kubectl get pods --show-all`.  The `--show-all` will show completed pods too.
-
-To list all the pods that belong to job in a machine readable form, you can use a command like this:
-
-```shell
-$ pods=$(kubectl get pods --selector=app=pi --output=jsonpath={.items..metadata.name})
-echo $pods
-pi-aiw0a
-```
-
-Here, the selector is the same as the selector for the job.  The `--output=jsonpath` option specifies an expression
-that just gets the name from each pod in the returned list.
-
-View the standard output of one of the pods:
-
-```shell
-$ kubectl logs pi-aiw0a
-3.1415926535897932384626433832795028841971693993751058209749445923078164062862089986280348253421170679821480865132823066470938446095505822317253594081284811174502841027019385211055596446229489549303819644288109756659334461284756482337867831652712019091456485669234603486104543266482133936072602491412737245870066063155881748815209209628292540917153643678925903600113305305488204665213841469519415116094330572703657595919530921861173819326117931051185480744623799627495673518857527248912279381830119491298336733624406566430860213949463952247371907021798609437027705392171762931767523846748184676694051320005681271452635608277857713427577896091736371787214684409012249534301465495853710507922796892589235420199561121290219608640344181598136297747713099605187072113499999983729780499510597317328160963185950244594553469083026425223082533446850352619311881710100031378387528865875332083814206171776691473035982534904287554687311595628638823537875937519577818577805321712268066130019278766111959092164201989380952572010654858632788659361533818279682303019520353018529689957736225994138912497217752834791315155748572424541506959508295331168617278558890750983817546374649393192550604009277016711390098488240128583616035637076601047101819429555961989467678374494482553797747268471040475346462080466842590694912933136770289891521047521620569660240580381501935112533824300355876402474964732639141992726042699227967823547816360093417216412199245863150302861829745557067498385054945885869269956909272107975093029553211653449872027559602364806654991198818347977535663698074265425278625518184175746728909777727938000816470600161452491921732172147723501414419735685481613611573525521334757418494684385233239073941433345477624168625189835694855620992192221842725502542568876717904946016534668049886272327917860857843838279679766814541009538837863609506800642251252051173929848960841284886269456042419652850222106611863067442786220391949450471237137869609563643719172874677646575739624138908658326459958133904780275901
-```
-
-## Writing a Job Spec
-
-As with all other Kubernetes config, a Job needs `apiVersion`, `kind`, and `metadata` fields.  For
-general information about working with config files, see [here](/{{page.version}}/docs/user-guide/simple-yaml),
-[here](/{{page.version}}/docs/user-guide/configuring-containers), and [here](working-with-resources).
-
-A Job also needs a [`.spec` section](/{{page.version}}/docs/devel/api-conventions/#spec-and-status).
-
-### Pod Template
-
-The `.spec.template` is the only required field of the `.spec`.
-
-The `.spec.template` is a [pod template](/{{page.version}}/docs/user-guide/replication-controller/#pod-template).  It has exactly
-the same schema as a [pod](/{{page.version}}/docs/user-guide/pods), except it is nested and does not have an `apiVersion` or
-`kind`.
-
-In addition to required fields for a Pod, a pod template in a job must specify appropriate
-lables (see [pod selector](#pod-selector) and an appropriate restart policy.
-
-Only a [`RestartPolicy`](/{{page.version}}/docs/user-guide/pod-states) equal to `Never` or `OnFailure` are allowed.
-
-### Pod Selector
-
-The `.spec.selector` field is a label query over a set of pods.
-
-The `spec.selector` is an object consisting of two fields:
-
-* `matchLabels` - works the same as the `.spec.selector` of a [ReplicationController](/{{page.version}}/docs/user-guide/replication-controller)
-* `matchExpressions` - allows to build more sophisticated selectors by specyfing key,
-  list of values and an operator that relates the key and values.
-
-When the two are specified the result is ANDed.
-
-If `.spec.selector` is unspecified, `.spec.selector.matchLabels` will be defaulted to
-`.spec.template.metadata.labels`.
-
-Also you should not normally create any pods whose labels match this selector, either directly,
-via another Job, or via another controller such as ReplicationController.  Otherwise, the Job will
-think that those pods were created by it.  Kubernetes will not stop you from doing this.
-
-### Multiple Completions
-
-By default, a Job is complete when one Pod runs to successful completion.  You can also specify that
-this needs to happen multiple times by specifying `.spec.completions` with a value greater than 1.
-When multiple completions are requested, each Pod created by the Job controller has an identical
-[`spec`](/{{page.version}}/docs/devel/api-conventions/#spec-and-status).  In particular, all pods will have
-the same command line and the same image, the same volumes, and mostly the same environment
-variables.  It is up to the user to arrange for the pods to do work on different things.  For
-example, the pods might all access a shared work queue service to acquire work units.
-
-To create multiple pods which are similar, but have slightly different arguments, environment
-variables or images, use multiple Jobs.
-
-### Parallelism
-
-You can suggest how many pods should run concurrently by setting `.spec.parallelism` to the number
-of pods you would like to have running concurrently.  This number is a suggestion. The number
-running concurrently may be lower or higher for a variety of reasons.  For example, it may be lower
-if the number of remaining completions is less, or as the controller is ramping up, or if it is
-throttling the job due to excessive failures.  It may be higher for example if a pod is gracefully
-shutdown, and the replacement starts early.
-
-If you do not specify `.spec.parallelism`, then it defaults to `.spec.completions`.
-
-## Handling Pod and Container Failures
-
-A Container in a Pod may fail for a number of reasons, such as because the process in it exited with
-a non-zero exit code, or the Container was killed for exceeding a memory limit, etc.  If this
-happens, and the `.spec.template.containers[].restartPolicy = "OnFailure"`, then the Pod stays
-on the node, but the Container is re-run.  Therefore, your program needs to handle the the case when it is
-restarted locally, or else specify `.spec.template.containers[].restartPolicy = "Never"`.
-See [pods-states](/{{page.version}}/docs/user-guide/pod-states) for more information on `restartPolicy`.
-
-An entire Pod can also fail, for a number of reasons, such as when the pod is kicked off the node
-(node is upgraded, rebooted, delelted, etc.), or if a container of the Pod fails and the
-`.spec.template.containers[].restartPolicy = "Never"`.  When a Pod fails, then the Job controller
-starts a new Pod.  Therefore, your program needs to handle the case when it is restarted in a new
-pod.  In particular, it needs to handle temporary files, locks, incomplete output and the like
-caused by previous runs.
-
-Note that even if you specify `.spec.parallelism = 1` and `.spec.completions = 1` and
-`.spec.template.containers[].restartPolicy = "Never"`, the same program may
-sometimes be started twice.
-
-If you do specify `.spec.parallelism` and `.spec.completions` both greater than 1, then there may be
-multiple pods running at once.  Therefore, your pods must also be tolerant of concurrency.
-
-## Alternatives to Job
-
-### Bare Pods
-
-When the node that a pod is running on reboots or fails, the pod is terminated
-and will not be restarted.  However, a Job will create new pods to replace terminated ones.
-For this reason, we recommend that you use a job rather than a bare pod, even if your application
-requires only a single pod.
-
-### Replication Controller
-
-Jobs are complementary to [Replication Controllers](/{{page.version}}/docs/user-guide/replication-controller).
-A Replication Controller manages pods which are not expected to terminate (e.g. web servers), and a Job
-manages pods that are expected to terminate (e.g. batch jobs).
-
-As discussed in [life of a pod](/{{page.version}}/docs/user-guide/pod-states), `Job` is *only* appropriate for pods with
-`RestartPolicy` equal to `OnFailure` or `Never`.  (Note: If `RestartPolicy` is not set, the default
-value is `Always`.)
-
-## Caveats
-
-Job objects are in the [`extensions` API Group](/{{page.version}}/docs/api/#api-groups).
-
-Job objects have [API version `v1beta1`](/{{page.version}}/docs/api/)#api-versioning).  Beta objects may
-undergo changes to their schema and/or semantics in future software releases, but
-similar functionality will be supported.
-
-## Future work
-
-Support for creating Jobs at specified times/dates (i.e. cron) is expected in the next minor
-release.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/jsonpath.md b/v1.2/docs/user-guide/jsonpath.md
deleted file mode 100644
index 63e8e3274b..0000000000
--- a/v1.2/docs/user-guide/jsonpath.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
----
-
-JSONPath template is composed of JSONPath expressions enclosed by {}.
-And we add three functions in addition to the original JSONPath syntax:
-
-1. The `$` operator is optional since the expression always start from the root object by default.
-2. We can use `""` to quote text inside JSONPath expression.
-3. We can use `range` operator to iterate list.
-
-The result object is printed as its String() function.
-
-Given the input:
-
-```json
-{
-  "kind": "List",
-  "items":[
-    {
-      "kind":"None",
-      "metadata":{"name":"127.0.0.1"},
-      "status":{
-        "capacity":{"cpu":"4"},
-        "addresses":[{"type": "LegacyHostIP", "address":"127.0.0.1"}]
-      }
-    },
-    {
-      "kind":"None",
-      "metadata":{"name":"127.0.0.2"},
-      "status":{
-        "capacity":{"cpu":"8"},
-        "addresses":[
-          {"type": "LegacyHostIP", "address":"127.0.0.2"},
-          {"type": "another", "address":"127.0.0.3"}
-        ]
-      }
-    }
-  ],
-  "users":[
-    {
-      "name": "myself",
-      "user": {}
-    },
-    {
-      "name": "e2e",
-      "user": {"username": "admin", "password": "secret"}
-    }
-  ]
-}
-```
-
-Function | Description        | Example            | Result
----------|--------------------|--------------------|------------------
-text     | the plain text     | kind is {.kind}    | kind is List
-""       | quote              | {"{"}              | {
-@        | the current object | {@}                | the same as input
-. or []  | child operator     | {.kind} or {['kind']}| List
-..       | recursive descent  | {..name}           | 127.0.0.1 127.0.0.2 myself e2e
-*        | wildcard. Get all objects| {.items[*].metadata.name} | [127.0.0.1 127.0.0.2]
-[start:end :step] | subscript operator | {.users[0].name}| myself
-[,]      | union operator     | {.items[*]['metadata.name', 'status.capacity']} | 127.0.0.1 127.0.0.2 map[cpu:4] map[cpu:8]
-?()      | filter             | {.users[?(@.name=="e2e")].user.password} | secret
-range, end | iterate list | {range .items[*]}[{.metadata.name}, {.status.capacity}] {end} | [127.0.0.1, map[cpu:4]] [127.0.0.2, map[cpu:8]]
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/known-issues.md b/v1.2/docs/user-guide/known-issues.md
deleted file mode 100644
index 9652da3610..0000000000
--- a/v1.2/docs/user-guide/known-issues.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
----
-
-This document summarizes known issues with existing Kubernetes releases.
-
-Please consult this document before filing new bugs.
-
-### Release 1.0.1
-
-   * `exec` liveness/readiness probes leak resources due to Docker exec leaking resources (#10659)
-   * `docker load` sometimes hangs which causes the `kube-apiserver` not to start.  Restarting the Docker daemon should fix the issue (#10868)
-   * The kubelet on the master node doesn't register with the `kube-apiserver` so statistics aren't collected for master daemons (#10891)
-   * Heapster and InfluxDB both leak memory (#10653)
-   * Wrong node cpu/memory limit metrics from Heapster (https://github.com/GoogleCloudPlatform/heapster/issues/399)
-   * Services that set `type=LoadBalancer` can not use port `10250` because of Google Compute Engine firewall limitations
-   * Add-on services can not be created or deleted via `kubectl` or the Kubernetes API (#11435)
-   * If a pod with a GCE PD is created and deleted in rapid succession, it may fail to attach/mount correctly leaving PD data inaccessible (or corrupted in the worst case). (http://issue.k8s.io/11231#issuecomment-122049113)
-      * Suggested temporary work around: introduce a 1-2 minute delay between deleting and recreating a pod with a PD on the same node.
-   * Explicit errors while detaching GCE PD could prevent PD from ever being detached (#11321)
-   * GCE PDs may sometimes fail to attach (#11302)
-   * If multiple Pods use the same RBD volume in read-write mode, it is possible data on the RBD volume could get corrupted. This problem has been found in environments where both apiserver and etcd rebooted and Pods were redistributed.
-      * A workaround is to ensure there is no other Ceph client using the RBD volume before mapping RBD image in read-write mode. For example, `rados -p poolname listwatchers image_name.rbd` can list RBD clients that are mapping the image.
-
-
-
diff --git a/v1.2/docs/user-guide/liveness/exec-liveness.yaml b/v1.2/docs/user-guide/liveness/exec-liveness.yaml
deleted file mode 100644
index 7b2af47c03..0000000000
--- a/v1.2/docs/user-guide/liveness/exec-liveness.yaml
+++ /dev/null
@@ -1,21 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  labels:
-    test: liveness
-  name: liveness-exec
-spec:
-  containers:
-  - args:
-    - /bin/sh
-    - -c
-    - echo ok > /tmp/health; sleep 10; rm -rf /tmp/health; sleep 600
-    image: gcr.io/google_containers/busybox
-    livenessProbe:
-      exec:
-        command:
-        - cat
-        - /tmp/health
-      initialDelaySeconds: 15
-      timeoutSeconds: 1
-    name: liveness
diff --git a/v1.2/docs/user-guide/liveness/http-liveness.yaml b/v1.2/docs/user-guide/liveness/http-liveness.yaml
deleted file mode 100644
index ca8d212ae2..0000000000
--- a/v1.2/docs/user-guide/liveness/http-liveness.yaml
+++ /dev/null
@@ -1,18 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  labels:
-    test: liveness
-  name: liveness-http
-spec:
-  containers:
-  - args:
-    - /server
-    image: gcr.io/google_containers/liveness
-    livenessProbe:
-      httpGet:
-        path: /healthz
-        port: 8080
-      initialDelaySeconds: 15
-      timeoutSeconds: 1
-    name: liveness
diff --git a/v1.2/docs/user-guide/liveness/image/Dockerfile b/v1.2/docs/user-guide/liveness/image/Dockerfile
deleted file mode 100644
index d057ecd309..0000000000
--- a/v1.2/docs/user-guide/liveness/image/Dockerfile
+++ /dev/null
@@ -1,4 +0,0 @@
-FROM scratch
-
-ADD server /server
-
diff --git a/v1.2/docs/user-guide/liveness/image/Makefile b/v1.2/docs/user-guide/liveness/image/Makefile
deleted file mode 100644
index 3eb9f0e2fe..0000000000
--- a/v1.2/docs/user-guide/liveness/image/Makefile
+++ /dev/null
@@ -1,13 +0,0 @@
-all: push
-
-server: server.go
-	CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -ldflags '-w' ./server.go
-
-container: server
-	docker build -t gcr.io/google_containers/liveness .
-
-push: container
-	gcloud docker push gcr.io/google_containers/liveness
-
-clean:
-	rm -f server
diff --git a/v1.2/docs/user-guide/liveness/image/server.go b/v1.2/docs/user-guide/liveness/image/server.go
deleted file mode 100644
index 26c337e767..0000000000
--- a/v1.2/docs/user-guide/liveness/image/server.go
+++ /dev/null
@@ -1,46 +0,0 @@
-/*
-Copyright 2014 The Kubernetes Authors All rights reserved.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-*/
-
-// A simple server that is alive for 10 seconds, then reports unhealthy for
-// the rest of its (hopefully) short existence.
-package main
-
-import (
-	"fmt"
-	"log"
-	"net/http"
-	"time"
-)
-
-func main() {
-	started := time.Now()
-	http.HandleFunc("/started", func(w http.ResponseWriter, r *http.Request) {
-		w.WriteHeader(200)
-		data := (time.Now().Sub(started)).String()
-		w.Write([]byte(data))
-	})
-	http.HandleFunc("/healthz", func(w http.ResponseWriter, r *http.Request) {
-		duration := time.Now().Sub(started)
-		if duration.Seconds() > 10 {
-			w.WriteHeader(500)
-			w.Write([]byte(fmt.Sprintf("error: %v", duration.Seconds())))
-		} else {
-			w.WriteHeader(200)
-			w.Write([]byte("ok"))
-		}
-	})
-	log.Fatal(http.ListenAndServe(":8080", nil))
-}
diff --git a/v1.2/docs/user-guide/liveness/index.md b/v1.2/docs/user-guide/liveness/index.md
deleted file mode 100644
index 3f5c99eac4..0000000000
--- a/v1.2/docs/user-guide/liveness/index.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
----
-
-This example shows two types of pod [health checks](/{{page.version}}/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks): HTTP checks and container execution checks.
-
-The [exec-liveness.yaml](/{{page.version}}/docs/user-guide/liveness/exec-liveness.yaml) demonstrates the container execution check.
-
-```yaml
-livenessProbe:
-      exec:
-        command:
-        - cat
-        - /tmp/health
-      initialDelaySeconds: 15
-      timeoutSeconds: 1
-```
-
-Kubelet executes the command `cat /tmp/health` in the container and reports failure if the command returns a non-zero exit code.
-
-Note that the container removes the `/tmp/health` file after 10 seconds,
-
-```shell
-echo ok > /tmp/health; sleep 10; rm -rf /tmp/health; sleep 600
-```
-
-so when Kubelet executes the health check 15 seconds (defined by initialDelaySeconds) after the container started, the check would fail.
-
-
-The [http-liveness.yaml](/{{page.version}}/docs/user-guide/liveness/http-liveness.yaml) demonstrates the HTTP check.
-
-```yaml
-livenessProbe:
-      httpGet:
-        path: /healthz
-        port: 8080
-      initialDelaySeconds: 15
-      timeoutSeconds: 1
-```
-
-The Kubelet sends an HTTP request to the specified path and port to perform the health check. If you take a look at image/server.go, you will see the server starts to respond with an error code 500 after 10 seconds, so the check fails. The Kubelet sends the probe to the container's ip address by default which could be specified with `host` as part of httpGet probe. If the container listens on `127.0.0.1`, `host` should be specified as `127.0.0.1`. In general, if the container listens on its ip address or on all interfaces (0.0.0.0), there is no need to specify the `host` as part of the httpGet probe.
-
-This [guide](/{{page.version}}/docs/user-guide/k8s201/#health-checking) has more information on health checks.
-
-## Get your hands dirty
-
-To show the health check is actually working, first create the pods:
-
-```shell
-$ kubectl create -f docs/user-guide/liveness/exec-liveness.yaml
-$ kubectl create -f docs/user-guide/liveness/http-liveness.yaml
-```
-
-Check the status of the pods once they are created:
-
-```shell
-$ kubectl get pods
-NAME                                           READY     STATUS       RESTARTS   AGE
-[...]
-liveness-exec                                  1/1       Running      0          13s
-liveness-http                                  1/1       Running      0          13s
-```
-
-Check the status half a minute later, you will see the container restart count being incremented:
-
-```shell
-$ kubectl get pods
-NAME                                           READY     STATUS       RESTARTS   AGE
-[...]
-liveness-exec                                  1/1       Running      1          36s
-liveness-http                                  1/1       Running      1          36s
-```
-
-At the bottom of the *kubectl describe* output there are messages indicating that the liveness probes have failed, and the containers have been killed and recreated.
-
-```shell
-$ kubectl describe pods liveness-exec
-[...]
-Sat, 27 Jun 2015 13:43:03 +0200    Sat, 27 Jun 2015 13:44:34 +0200    4    {kubelet kubernetes-minion-6fbi}    spec.containers{liveness}    unhealthy  Liveness probe failed: cat: can't open '/tmp/health': No such file or directory
-Sat, 27 Jun 2015 13:44:44 +0200    Sat, 27 Jun 2015 13:44:44 +0200    1    {kubelet kubernetes-minion-6fbi}    spec.containers{liveness}    killing    Killing with docker id 65b52d62c635
-Sat, 27 Jun 2015 13:44:44 +0200    Sat, 27 Jun 2015 13:44:44 +0200    1    {kubelet kubernetes-minion-6fbi}    spec.containers{liveness}    created    Created with docker id ed6bb004ee10
-Sat, 27 Jun 2015 13:44:44 +0200    Sat, 27 Jun 2015 13:44:44 +0200    1    {kubelet kubernetes-minion-6fbi}    spec.containers{liveness}    started    Started with docker id ed6bb004ee10
-```
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/logging-demo/Makefile b/v1.2/docs/user-guide/logging-demo/Makefile
deleted file mode 100644
index 810a83f3b7..0000000000
--- a/v1.2/docs/user-guide/logging-demo/Makefile
+++ /dev/null
@@ -1,26 +0,0 @@
-# Makefile for launching synthetic logging sources (any platform)
-# and for reporting the forwarding rules for the
-# Elasticsearch and Kibana pods for the GCE platform.
-# For examples of how to observe the ingested logs please
-# see the appropriate getting started guide e.g.
-# Google Cloud Logging: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/getting-started-guides/logging.md
-# With Elasticsearch and Kibana logging: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/getting-started-guides/logging-elasticsearch.md
-
-.PHONY: up down logger-up logger-down logger10-up logger10-down
-
-up:	logger-up logger10-up
-
-down:	logger-down logger10-down
-
-logger-up:
-	kubectl create -f synthetic_0_25lps.yaml
-
-logger-down:
-	kubectl delete pod synthetic-logger-0.25lps-pod
-
-logger10-up:
-	kubectl create -f synthetic_10lps.yaml
-
-logger10-down:
-	kubectl delete pod synthetic-logger-10lps-pod
-
diff --git a/v1.2/docs/user-guide/logging-demo/index.md b/v1.2/docs/user-guide/logging-demo/index.md
deleted file mode 100644
index 32460c5608..0000000000
--- a/v1.2/docs/user-guide/logging-demo/index.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
----
-
-This directory contains two [pod](/{{page.version}}/docs/user-guide/pods) specifications which can be used as synthetic
-logging sources. The pod specification in [synthetic_0_25lps.yaml](/{{page.version}}/docs/user-guide/logging-demo/synthetic_0_25lps.yaml)
-describes a pod that just emits a log message once every 4 seconds. The pod specification in
-[synthetic_10lps.yaml](/{{page.version}}/docs/user-guide/logging-demo/synthetic_10lps.yaml)
-describes a pod that just emits 10 log lines per second.
-
-See [logging document](/{{page.version}}/docs/user-guide/logging/) for more details about logging. To observe the ingested log lines when using Google Cloud Logging please see the getting
-started instructions
-at [Cluster Level Logging to Google Cloud Logging](/{{page.version}}/docs/getting-started-guides/logging).
-To observe the ingested log lines when using Elasticsearch and Kibana please see the getting
-started instructions
-at [Cluster Level Logging with Elasticsearch and Kibana](/{{page.version}}/docs/getting-started-guides/logging-elasticsearch).
-
-
-
diff --git a/v1.2/docs/user-guide/logging-demo/synthetic_0_25lps.yaml b/v1.2/docs/user-guide/logging-demo/synthetic_0_25lps.yaml
deleted file mode 100644
index 93516706c0..0000000000
--- a/v1.2/docs/user-guide/logging-demo/synthetic_0_25lps.yaml
+++ /dev/null
@@ -1,30 +0,0 @@
-# This pod specification creates an instance of a synthetic logger. The logger
-# is simply a program that writes out the hostname of the pod, a count which increments
-# by one on each iteration (to help notice missing log enteries) and the date using
-# a long format (RFC-3339) to nano-second precision. This program logs at a frequency
-# of 0.25 lines per second. The shellscript program is given directly to bash as -c argument
-# and could have been written out as:
-#   i="0"
-#   while true
-#   do
-#     echo -n "`hostname`: $i: "
-#     date --rfc-3339 ns
-#     sleep 4
-#     i=$[$i+1]
-#   done
-apiVersion: v1
-kind: Pod
-metadata:
-  labels:
-    name: synth-logging-source
-  name: synthetic-logger-0.25lps-pod
-spec:
-  containers:
-  - name: synth-lgr
-    image: ubuntu:14.04
-    args:
-    - bash
-    - -c
-    - 'i="0"; while true; do echo -n "`hostname`: $i: "; date --rfc-3339 ns; sleep
-      4; i=$[$i+1]; done'
-    
diff --git a/v1.2/docs/user-guide/logging-demo/synthetic_10lps.yaml b/v1.2/docs/user-guide/logging-demo/synthetic_10lps.yaml
deleted file mode 100644
index 6e3c1ca929..0000000000
--- a/v1.2/docs/user-guide/logging-demo/synthetic_10lps.yaml
+++ /dev/null
@@ -1,30 +0,0 @@
-# This pod specification creates an instance of a synthetic logger. The logger
-# is simply a program that writes out the hostname of the pod, a count which increments
-# by one on each iteration (to help notice missing log enteries) and the date using
-# a long format (RFC-3339) to nano-second precision. This program logs at a frequency
-# of 0.25 lines per second. The shellscript program is given directly to bash as -c argument
-# and could have been written out as:
-#   i="0"
-#   while true
-#   do
-#     echo -n "`hostname`: $i: "
-#     date --rfc-3339 ns
-#     sleep 4
-#     i=$[$i+1]
-#   done
-apiVersion: v1
-kind: Pod
-metadata:
-  labels:
-    name: synth-logging-source
-  name: synthetic-logger-10lps-pod
-spec:
-  containers:
-  - name: synth-lgr
-    image: ubuntu:14.04
-    args:
-    - bash
-    - -c
-    - 'i="0"; while true; do echo -n "`hostname`: $i: "; date --rfc-3339 ns; sleep
-      0.1; i=$[$i+1]; done'
-        
diff --git a/v1.2/docs/user-guide/managing-deployments.md b/v1.2/docs/user-guide/managing-deployments.md
deleted file mode 100644
index d0f56ac419..0000000000
--- a/v1.2/docs/user-guide/managing-deployments.md
+++ /dev/null
@@ -1,409 +0,0 @@
----
----
-
-You've deployed your application and exposed it via a service. Now what? Kubernetes provides a number of tools to help you manage your application deployment, including scaling and updating. Among the features we'll discuss in more depth are [configuration files](/{{page.version}}/docs/user-guide/configuring-containers/#configuration-in-kubernetes) and [labels](/{{page.version}}/docs/user-guide/deploying-applications/#labels).
-
-* TOC
-{:toc}
-
-## Organizing resource configurations
-
-Many applications require multiple resources to be created, such as a Replication Controller and a Service. Management of multiple resources can be simplified by grouping them together in the same file (separated by `---` in YAML). For example:
-
-```yaml
-apiVersion: v1
-kind: Service
-metadata:
-  name: my-nginx-svc
-  labels:
-    app: nginx
-spec:
-  type: LoadBalancer
-  ports:
-  - port: 80
-  selector:
-    app: nginx
----
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx
-spec:
-  replicas: 2
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        ports:
-        - containerPort: 80
-```
-
-Multiple resources can be created the same way as a single resource:
-
-```shell
-$ kubectl create -f ./nginx-app.yaml
-services/my-nginx-svc
-replicationcontrollers/my-nginx
-```
-
-The resources will be created in the order they appear in the file. Therefore, it's best to specify the service first, since that will ensure the scheduler can spread the pods associated with the service as they are created by the replication controller(s).
-
-`kubectl create` also accepts multiple `-f` arguments:
-
-```shell
-$ kubectl create -f ./nginx-svc.yaml -f ./nginx-rc.yaml
-```
-
-And a directory can be specified rather than or in addition to individual files:
-
-```shell
-$ kubectl create -f ./nginx/
-```
-
-`kubectl` will read any files with suffixes `.yaml`, `.yml`, or `.json`.
-
-It is a recommended practice to put resources related to the same microservice or application tier into the same file, and to group all of the files associated with your application in the same directory. If the tiers of your application bind to each other using DNS, then you can then simply deploy all of the components of your stack en masse.
-
-A URL can also be specified as a configuration source, which is handy for deploying directly from configuration files checked into github:
-
-```shell
-$ kubectl create -f https://raw.githubusercontent.com/GoogleCloudPlatform/kubernetes/master/docs/user-guide/replication.yaml
-replicationcontrollers/nginx
-```
-
-## Bulk operations in kubectl
-
-Resource creation isn't the only operation that `kubectl` can perform in bulk. It can also extract resource names from configuration files in order to perform other operations, in particular to delete the same resources you created:
-
-```shell
-$ kubectl delete -f ./nginx/
-replicationcontrollers/my-nginx
-services/my-nginx-svc
-```
-
-In the case of just two resources, it's also easy to specify both on the command line using the resource/name syntax:
-
-```shell
-$ kubectl delete replicationcontrollers/my-nginx services/my-nginx-svc
-```
-
-For larger numbers of resources, one can use labels to filter resources. The selector is specified using `-l`:
-
-```shell
-$ kubectl delete all -lapp=nginx
-replicationcontrollers/my-nginx
-services/my-nginx-svc
-```
-
-Because `kubectl` outputs resource names in the same syntax it accepts, it's easy to chain operations using `$()` or `xargs`:
-
-```shell
-$ kubectl get $(kubectl create -f ./nginx/ | grep my-nginx)
-CONTROLLER   CONTAINER(S)   IMAGE(S)   SELECTOR    REPLICAS
-my-nginx     nginx          nginx      app=nginx   2
-NAME           LABELS      SELECTOR    IP(S)          PORT(S)
-my-nginx-svc   app=nginx   app=nginx   10.0.152.174   80/TCP
-```
-
-## Using labels effectively
-
-The examples we've used so far apply at most a single label to any resource. There are many scenarios where multiple labels should be used to distinguish sets from one another.
-
-For instance, different applications would use different values for the `app` label, but a multi-tier application, such as the [guestbook example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/), would additionally need to distinguish each tier. The frontend could carry the following labels:
-
-```yaml
-labels:
-        app: guestbook
-        tier: frontend
-```
-
-while the Redis master and slave would have different `tier` labels, and perhaps even an additional `role` label:
-
-```yaml
-labels:
-        app: guestbook
-        tier: backend
-        role: master
-```
-
-and
-
-```yaml
-labels:
-        app: guestbook
-        tier: backend
-        role: slave
-```
-
-The labels allow us to slice and dice our resources along any dimension specified by a label:
-
-```shell
-$ kubectl create -f ./guestbook-fe.yaml -f ./redis-master.yaml -f ./redis-slave.yaml
-replicationcontrollers/guestbook-fe
-replicationcontrollers/guestbook-redis-master
-replicationcontrollers/guestbook-redis-slave
-$ kubectl get pods -Lapp -Ltier -Lrole
-NAME                           READY     STATUS    RESTARTS   AGE       APP         TIER       ROLE
-guestbook-fe-4nlpb             1/1       Running   0          1m        guestbook   frontend   <n/a>
-guestbook-fe-ght6d             1/1       Running   0          1m        guestbook   frontend   <n/a>
-guestbook-fe-jpy62             1/1       Running   0          1m        guestbook   frontend   <n/a>
-guestbook-redis-master-5pg3b   1/1       Running   0          1m        guestbook   backend    master
-guestbook-redis-slave-2q2yf    1/1       Running   0          1m        guestbook   backend    slave
-guestbook-redis-slave-qgazl    1/1       Running   0          1m        guestbook   backend    slave
-my-nginx-divi2                 1/1       Running   0          29m       nginx       <n/a>      <n/a>
-my-nginx-o0ef1                 1/1       Running   0          29m       nginx       <n/a>      <n/a>
-$ kubectl get pods -lapp=guestbook,role=slave
-NAME                          READY     STATUS    RESTARTS   AGE
-guestbook-redis-slave-2q2yf   1/1       Running   0          3m
-guestbook-redis-slave-qgazl   1/1       Running   0          3m
-```
-
-## Canary deployments
-
-Another scenario where multiple labels are needed is to distinguish deployments of different releases or configurations of the same component. For example, it is common practice to deploy a *canary* of a new application release (specified via image tag) side by side with the previous release so that the new release can receive live production traffic before fully rolling it out. For instance, a new release of the guestbook frontend might carry the following labels:
-
-```yaml
-labels:
-        app: guestbook
-        tier: frontend
-        track: canary
-```
-
-and the primary, stable release would have a different value of the `track` label, so that the sets of pods controlled by the two replication controllers would not overlap:
-
-```yaml
-labels:
-        app: guestbook
-        tier: frontend
-        track: stable
-```
-
-The frontend service would span both sets of replicas by selecting the common subset of their labels, omitting the `track` label:
-
-```yaml
-selector:
-     app: guestbook
-     tier: frontend
-```
-
-## Updating labels
-
-Sometimes existing pods and other resources need to be relabeled before creating new resources. This can be done with `kubectl label`. For example:
-
-```shell
-$ kubectl label pods -lapp=nginx tier=fe
-NAME                READY     STATUS    RESTARTS   AGE
-my-nginx-v4-9gw19   1/1       Running   0          14m
-NAME                READY     STATUS    RESTARTS   AGE
-my-nginx-v4-hayza   1/1       Running   0          13m
-NAME                READY     STATUS    RESTARTS   AGE
-my-nginx-v4-mde6m   1/1       Running   0          17m
-NAME                READY     STATUS    RESTARTS   AGE
-my-nginx-v4-sh6m8   1/1       Running   0          18m
-NAME                READY     STATUS    RESTARTS   AGE
-my-nginx-v4-wfof4   1/1       Running   0          16m
-$ kubectl get pods -lapp=nginx -Ltier
-NAME                READY     STATUS    RESTARTS   AGE       TIER
-my-nginx-v4-9gw19   1/1       Running   0          15m       fe
-my-nginx-v4-hayza   1/1       Running   0          14m       fe
-my-nginx-v4-mde6m   1/1       Running   0          18m       fe
-my-nginx-v4-sh6m8   1/1       Running   0          19m       fe
-my-nginx-v4-wfof4   1/1       Running   0          16m       fe
-```
-
-## Scaling your application
-
-When load on your application grows or shrinks, it's easy to scale with `kubectl`. For instance, to increase the number of nginx replicas from 2 to 3, do:
-
-```shell
-$ kubectl scale rc my-nginx --replicas=3
-scaled
-$ kubectl get pods -lapp=nginx
-NAME             READY     STATUS    RESTARTS   AGE
-my-nginx-1jgkf   1/1       Running   0          3m
-my-nginx-divi2   1/1       Running   0          1h
-my-nginx-o0ef1   1/1       Running   0          1h
-```
-
-## Updating your application without a service outage
-
-At some point, you'll eventually need to update your deployed application, typically by specifying a new image or image tag, as in the canary deployment scenario above. `kubectl` supports several update operations, each of which is applicable to different scenarios.
-
-To update a service without an outage, `kubectl` supports what is called ['rolling update'?](/{{page.version}}/docs/user-guide/kubectl/kubectl_rolling-update), which updates one pod at a time, rather than taking down the entire service at the same time. See the [rolling update design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/simple-rolling-update.md) and the [example of rolling update](/{{page.version}}/docs/user-guide/update-demo/) for more information.
-
-Let's say you were running version 1.7.9 of nginx:
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx
-spec:
-  replicas: 5
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx:1.7.9
-        ports:
-        - containerPort: 80
-```
-
-To update to version 1.9.1, you can use [`kubectl rolling-update --image`](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/simple-rolling-update.md):
-
-```shell
-$ kubectl rolling-update my-nginx --image=nginx:1.9.1
-Creating my-nginx-ccba8fbd8cc8160970f63f9a2696fc46
-```
-
-In another window, you can see that `kubectl` added a `deployment` label to the pods, whose value is a hash of the configuration, to distinguish the new pods from the old:
-
-```shell
-$ kubectl get pods -lapp=nginx -Ldeployment
-NAME                                              READY     STATUS    RESTARTS   AGE       DEPLOYMENT
-my-nginx-1jgkf                                    1/1       Running   0          1h        2d1d7a8f682934a254002b56404b813e
-my-nginx-ccba8fbd8cc8160970f63f9a2696fc46-k156z   1/1       Running   0          1m        ccba8fbd8cc8160970f63f9a2696fc46
-my-nginx-ccba8fbd8cc8160970f63f9a2696fc46-v95yh   1/1       Running   0          35s       ccba8fbd8cc8160970f63f9a2696fc46
-my-nginx-divi2                                    1/1       Running   0          2h        2d1d7a8f682934a254002b56404b813e
-my-nginx-o0ef1                                    1/1       Running   0          2h        2d1d7a8f682934a254002b56404b813e
-my-nginx-q6all                                    1/1       Running   0          8m        2d1d7a8f682934a254002b56404b813e
-```
-
-`kubectl rolling-update` reports progress as it progresses:
-
-```shell
-Updating my-nginx replicas: 4, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 1
-At end of loop: my-nginx replicas: 4, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 1
-At beginning of loop: my-nginx replicas: 3, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 2
-Updating my-nginx replicas: 3, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 2
-At end of loop: my-nginx replicas: 3, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 2
-At beginning of loop: my-nginx replicas: 2, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 3
-Updating my-nginx replicas: 2, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 3
-At end of loop: my-nginx replicas: 2, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 3
-At beginning of loop: my-nginx replicas: 1, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 4
-Updating my-nginx replicas: 1, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 4
-At end of loop: my-nginx replicas: 1, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 4
-At beginning of loop: my-nginx replicas: 0, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 5
-Updating my-nginx replicas: 0, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 5
-At end of loop: my-nginx replicas: 0, my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 replicas: 5
-Update succeeded. Deleting old controller: my-nginx
-Renaming my-nginx-ccba8fbd8cc8160970f63f9a2696fc46 to my-nginx
-my-nginx
-```
-
-If you encounter a problem, you can stop the rolling update midway and revert to the previous version using `--rollback`:
-
-```shell
-$ kubectl kubectl rolling-update my-nginx  --image=nginx:1.9.1 --rollback
-Found existing update in progress (my-nginx-ccba8fbd8cc8160970f63f9a2696fc46), resuming.
-Found desired replicas.Continuing update with existing controller my-nginx.
-Stopping my-nginx-02ca3e87d8685813dbe1f8c164a46f02 replicas: 1 -> 0
-Update succeeded. Deleting my-nginx-ccba8fbd8cc8160970f63f9a2696fc46
-my-nginx
-```
-
-This is one example where the immutability of containers is a huge asset.
-
-If you need to update more than just the image (e.g., command arguments, environment variables), you can create a new replication controller, with a new name and distinguishing label value, such as:
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx-v4
-spec:
-  replicas: 5
-  selector:
-    app: nginx
-    deployment: v4
-  template:
-    metadata:
-      labels:
-        app: nginx
-        deployment: v4
-    spec:
-      containers:
-      - name: nginx
-        image: nginx:1.9.2
-        args: ['nginx'?,'?-T'?]
-        ports:
-        - containerPort: 80
-```
-
-and roll it out:
-
-```shell
-$ kubectl rolling-update my-nginx -f ./nginx-rc.yaml
-Creating my-nginx-v4
-At beginning of loop: my-nginx replicas: 4, my-nginx-v4 replicas: 1
-Updating my-nginx replicas: 4, my-nginx-v4 replicas: 1
-At end of loop: my-nginx replicas: 4, my-nginx-v4 replicas: 1
-At beginning of loop: my-nginx replicas: 3, my-nginx-v4 replicas: 2
-Updating my-nginx replicas: 3, my-nginx-v4 replicas: 2
-At end of loop: my-nginx replicas: 3, my-nginx-v4 replicas: 2
-At beginning of loop: my-nginx replicas: 2, my-nginx-v4 replicas: 3
-Updating my-nginx replicas: 2, my-nginx-v4 replicas: 3
-At end of loop: my-nginx replicas: 2, my-nginx-v4 replicas: 3
-At beginning of loop: my-nginx replicas: 1, my-nginx-v4 replicas: 4
-Updating my-nginx replicas: 1, my-nginx-v4 replicas: 4
-At end of loop: my-nginx replicas: 1, my-nginx-v4 replicas: 4
-At beginning of loop: my-nginx replicas: 0, my-nginx-v4 replicas: 5
-Updating my-nginx replicas: 0, my-nginx-v4 replicas: 5
-At end of loop: my-nginx replicas: 0, my-nginx-v4 replicas: 5
-Update succeeded. Deleting my-nginx
-my-nginx-v4
-```
-
-You can also run the [update demo](/{{page.version}}/docs/user-guide/update-demo/) to see a visual representation of the rolling update process.
-
-## In-place updates of resources
-
-Sometimes it's necessary to make narrow, non-disruptive updates to resources you've created. For instance, you might want to add an [annotation](/{{page.version}}/docs/user-guide/annotations) with a description of your object. That's easiest to do with `kubectl patch`:
-
-```shell
-$ kubectl patch rc my-nginx-v4 -p '{"metadata": {"annotations": {"description": "my frontend running nginx"}}}' 
-my-nginx-v4
-$ kubectl get rc my-nginx-v4 -o yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  annotations:
-    description: my frontend running nginx
-...
-```
-
-The patch is specified using json.
-
-For more significant changes, you can `get` the resource, edit it, and then `replace` the resource with the updated version:
-
-```shell
-$ kubectl get rc my-nginx-v4 -o yaml > /tmp/nginx.yaml
-$ vi /tmp/nginx.yaml
-$ kubectl replace -f /tmp/nginx.yaml
-replicationcontrollers/my-nginx-v4
-$ rm $TMP
-```
-
-The system ensures that you don't clobber changes made by other users or components by confirming that the `resourceVersion` doesn't differ from the version you edited. If you want to update regardless of other changes, remove the `resourceVersion` field when you edit the resource. However, if you do this, don't use your original configuration file as the source since additional fields most likely were set in the live state.
-
-## Disruptive updates
-
-In some cases, you may need to update resource fields that cannot be updated once initialized, or you may just want to make a recursive change immediately, such as to fix broken pods created by a replication controller. To change such fields, use `replace --force`, which deletes and re-creates the resource. In this case, you can simply modify your original configuration file:
-
-```shell
-$ kubectl replace -f ./nginx-rc.yaml --force
-replicationcontrollers/my-nginx-v4
-replicationcontrollers/my-nginx-v4
-```
-
-## What's next?
-
-- [Learn about how to use `kubectl` for application introspection and debugging.](/{{page.version}}/docs/user-guide/introspection-and-debugging)
-- [Tips and tricks when working with config](/{{page.version}}/docs/user-guide/config-best-practices
diff --git a/v1.2/docs/user-guide/monitoring.md b/v1.2/docs/user-guide/monitoring.md
deleted file mode 100644
index d47a3be2bb..0000000000
--- a/v1.2/docs/user-guide/monitoring.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
----
-
-Understanding how an application behaves when deployed is crucial to scaling the application and providing a reliable service. In a Kubernetes cluster, application performance can be examined at many different levels: containers, [pods](/{{page.version}}/docs/user-guide/pods), [services](/{{page.version}}/docs/user-guide/services), and whole clusters. As part of Kubernetes we want to provide users with detailed resource usage information about their running applications at all these levels. This will give users deep insights into how their applications are performing and where possible application bottlenecks may be found. In comes [Heapster](https://github.com/GoogleCloudPlatform/heapster), a project meant to provide a base monitoring platform on Kubernetes.
-
-### Overview
-
-Heapster is a cluster-wide aggregator of monitoring and event data. It currently supports Kubernetes natively and works on all Kubernetes setups. Heapster runs as a pod in the cluster, similar to how any Kubernetes application would run. The Heapster pod discovers all nodes in the cluster and queries usage information from the nodes' [Kubelet](https://releases.k8s.io/{{page.githubbranch}}/DESIGN.md#kubelet)s, the on-machine Kubernetes agent. The Kubelet itself fetches the data from [cAdvisor](https://github.com/google/cadvisor). Heapster groups the information by pod along with the relevant labels. This data is then pushed to a configurable backend for storage and visualization. Currently supported backends include [InfluxDB](http://influxdb.com/) (with [Grafana](http://grafana.org/) for visualization) and [Google Cloud Monitoring](https://cloud.google.com/monitoring/). The overall architecture of the service can be seen below:
-
-![overall monitoring architecture](/images/docs/monitoring-architecture.png)
-
-Let's look at some of the other components in more detail.
-
-### cAdvisor
-
-cAdvisor is an open source container resource usage and performance analysis agent. It is purpose built for containers and supports Docker containers natively. In Kubernetes, cadvisor is integrated into the Kubelet binary. cAdvisor auto-discovers all containers in the machine and collects CPU, memory, filesystem, and network usage statistics. cAdvisor also provides the overall machine usage by analyzing the 'root'? container on the machine.
-
-On most Kubernetes clusters, cAdvisor exposes a simple UI for on-machine containers on port 4194. Here is a snapshot of part of cAdvisor's UI that shows the overall machine usage:
-
-![cAdvisor](/images/docs/cadvisor.png)
-
-### Kubelet
-
-The Kubelet acts as a bridge between the Kubernetes master and the nodes. It manages the pods and containers running on a machine. Kubelet translates each pod into its constituent containers and fetches individual container usage statistics from cAdvisor. It then exposes the aggregated pod resource usage statistics via a REST API.
-
-## Storage Backends
-
-### InfluxDB and Grafana
-
-A Grafana setup with InfluxDB is a very popular combination for monitoring in the open source world. InfluxDB exposes an easy to use API to write and fetch time series data. Heapster is setup to use this storage backend by default on most Kubernetes clusters. A detailed setup guide can be found [here](https://github.com/GoogleCloudPlatform/heapster/blob/master/docs/influxdb.md). InfluxDB and Grafana run in Pods. The pod exposes itself as a Kubernetes service which is how Heapster discovers it.
-
-The Grafana container serves Grafana's UI which provides an easy to configure dashboard interface. The default dashboard for Kubernetes contains an example dashboard that monitors resource usage of the cluster and the pods inside of it. This dashboard can easily be customized and expanded. Take a look at the storage schema for InfluxDB [here](https://github.com/GoogleCloudPlatform/heapster/blob/master/docs/storage-schema.md#metrics).
-
-Here is a video showing how to monitor a Kubernetes cluster using heapster, InfluxDB and Grafana:
-
-[![How to monitor a Kubernetes cluster using heapster, InfluxDB and Grafana](http://img.youtube.com/vi/SZgqjMrxo3g/0.jpg)](http://www.youtube.com/watch?v=SZgqjMrxo3g)
-
-Here is a snapshot of the default Kubernetes Grafana dashboard that shows the CPU and Memory usage of the entire cluster, individual pods and containers:
-
-![snapshot of the default Kubernetes Grafana dashboard](/images/docs/influx.png)
-
-### Google Cloud Monitoring
-
-Google Cloud Monitoring is a hosted monitoring service that allows you to visualize and alert on important metrics in your application. Heapster can be setup to automatically push all collected metrics to Google Cloud Monitoring. These metrics are then available in the [Cloud Monitoring Console](https://app.google.stackdriver.com/). This storage backend is the easiest to setup and maintain. The monitoring console allows you to easily create and customize dashboards using the exported data.
-
-Here is a video showing how to setup and run a Google Cloud Monitoring backed Heapster:
-
-[![how to setup and run a Google Cloud Monitoring backed Heapster](http://img.youtube.com/vi/xSMNR2fcoLs/0.jpg)](http://www.youtube.com/watch?v=xSMNR2fcoLs)
-
-Here is a snapshot of the a Google Cloud Monitoring dashboard showing cluster-wide resource usage.
-
-![Google Cloud Monitoring dashboard](/images/docs/gcm.png)
-
-## Try it out!
-
-Now that you've learned a bit about Heapster, feel free to try it out on your own clusters! The [Heapster repository](https://github.com/kubernetes/heapster) is available on GitHub. It contains detailed instructions to setup Heapster and its storage backends. Heapster runs by default on most Kubernetes clusters, so you may already have it! Feedback is always welcome. Please let us know if you run into any issues via the troubleshooting [channels](/{{page.version}}/docs/troubleshooting/).
-
-***
-*Authors: Vishnu Kannan and Victor Marmol, Google Software Engineers.*
-*This article was originally posted in [Kubernetes blog](http://blog.kubernetes.io/2015/05/resource-usage-monitoring-kubernetes).*
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/multi-pod.yaml b/v1.2/docs/user-guide/multi-pod.yaml
deleted file mode 100644
index 7f7d0a5745..0000000000
--- a/v1.2/docs/user-guide/multi-pod.yaml
+++ /dev/null
@@ -1,49 +0,0 @@
----
-apiVersion: v1
-kind: Pod
-metadata:
-  labels:
-    name: redis
-    redis-sentinel: "true"
-    role: master
-  name: redis-master
-spec:
-  containers:
-    - name: master
-      image: kubernetes/redis:v1
-      env:
-        - name: MASTER
-          value: "true"
-      ports:
-        - containerPort: 6379
-      resources:
-        limits:
-          cpu: "0.5"
-      volumeMounts:
-        - mountPath: /redis-master-data
-          name: data
-    - name: sentinel
-      image: kubernetes/redis:v1
-      env:
-        - name: SENTINEL
-          value: "true"
-      ports:
-        - containerPort: 26379
-  volumes:
-    - name: data
-      emptyDir: {}
----
-apiVersion: v1
-kind: Pod
-metadata:
-  labels:
-    name: redis-proxy
-    role: proxy
-  name: redis-proxy
-spec:
-  containers:
-  - name: proxy
-    image: kubernetes/redis-proxy:v1
-    ports:
-    - containerPort: 6379
-      name: api
diff --git a/v1.2/docs/user-guide/new-nginx-deployment.yaml b/v1.2/docs/user-guide/new-nginx-deployment.yaml
deleted file mode 100644
index 47c57adefb..0000000000
--- a/v1.2/docs/user-guide/new-nginx-deployment.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-apiVersion: extensions/v1beta1
-kind: Deployment
-metadata:
-  name: nginx-deployment
-spec:
-  replicas: 3
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx:1.9.1
-        ports:
-        - containerPort: 80
diff --git a/v1.2/docs/user-guide/nginx-deployment.yaml b/v1.2/docs/user-guide/nginx-deployment.yaml
deleted file mode 100644
index 7a0dd431ef..0000000000
--- a/v1.2/docs/user-guide/nginx-deployment.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-apiVersion: extensions/v1beta1
-kind: Deployment
-metadata:
-  name: nginx-deployment
-spec:
-  replicas: 3
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx:1.7.9
-        ports:
-        - containerPort: 80
diff --git a/v1.2/docs/user-guide/node-selection/index.md b/v1.2/docs/user-guide/node-selection/index.md
deleted file mode 100644
index f3ee5dd838..0000000000
--- a/v1.2/docs/user-guide/node-selection/index.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
----
-
-This example shows how to assign a [pod](/{{page.version}}/docs/user-guide/pods/) to a specific [node](/{{page.version}}/docs/admin/node/) or to one of a set of nodes using node labels and the nodeSelector field in a pod specification. Generally this is unnecessary, as the scheduler will take care of things for you, but you may want to do so in certain circumstances like to ensure that your pod ends up on a machine with an SSD attached to it.
-
-### Step Zero: Prerequisites
-
-This example assumes that you have a basic understanding of Kubernetes pods and that you have [turned up a Kubernetes cluster](https://github.com/kubernetes/kubernetes#documentation).
-
-### Step One: Attach label to the node
-
-Run `kubectl get nodes` to get the names of your cluster's nodes. Pick out the one that you want to add a label to.
-
-Then, to add a label to the node you've chosen, run `kubectl label nodes <node-name> <label-key>=<label-value>`. For example, if my node name is 'kubernetes-foo-node-1.c.a-robinson.internal' and my desired label is 'disktype=ssd', then I can run `kubectl label nodes kubernetes-foo-node-1.c.a-robinson.internal disktype=ssd`.
-
-If this fails with an "invalid command" error, you're likely using an older version of kubectl that doesn't have the `label` command. In that case, see the [previous version](https://github.com/kubernetes/kubernetes/blob/a053dbc313572ed60d89dae9821ecab8bfd676dc/examples/node-selection/README.md) of this guide for instructions on how to manually set labels on a node.
-
-Also, note that label keys must be in the form of DNS labels (as described in the [identifiers doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/identifiers.md)), meaning that they are not allowed to contain any upper-case letters.
-
-You can verify that it worked by re-running `kubectl get nodes` and checking that the node now has a label.
-
-### Step Two: Add a nodeSelector field to your pod configuration
-
-Take whatever pod config file you want to run, and add a nodeSelector section to it, like this. For example, if this is my pod config:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-  labels:
-    env: test
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-```
-
-Then add a nodeSelector like so:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-  labels:
-    env: test
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    imagePullPolicy: IfNotPresent
-  <b>nodeSelector:
-    disktype: ssd</b>
-```
-
-When you then run `kubectl create -f pod.yaml`, the pod will get scheduled on the node that you attached the label to! You can verify that it worked by running `kubectl get pods -o wide` and looking at the "NODE" that the pod was assigned to.
-
-### Conclusion
-
-While this example only covered one node, you can attach labels to as many nodes as you want. Then when you schedule a pod with a nodeSelector, it can be scheduled on any of the nodes that satisfy that nodeSelector. Be careful that it will match at least one node, however, because if it doesn't the pod won't be scheduled at all.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/node-selection/pod.yaml b/v1.2/docs/user-guide/node-selection/pod.yaml
deleted file mode 100644
index 134ddae2aa..0000000000
--- a/v1.2/docs/user-guide/node-selection/pod.yaml
+++ /dev/null
@@ -1,13 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-  labels:
-    env: test
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    imagePullPolicy: IfNotPresent
-  nodeSelector:
-    disktype: ssd
diff --git a/v1.2/docs/user-guide/overview.md b/v1.2/docs/user-guide/overview.md
deleted file mode 100644
index 74594d02b0..0000000000
--- a/v1.2/docs/user-guide/overview.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
----
-
-Kubernetes is an open-source system for managing containerized applications across multiple hosts in a cluster. Kubernetes is intended to make deploying containerized/microservice-based applications easy but powerful.
-
-Kubernetes provides mechanisms for application deployment, scheduling, updating, maintenance, and scaling. A key feature of Kubernetes is that it actively manages the containers to ensure that the state of the cluster continually matches the user's intentions. An operations user should be able to launch a micro-service, letting the scheduler find the right placement. We also want to improve the tools and experience for how users can roll-out applications through patterns like canary deployments.
-
-Kubernetes supports [Docker](http://www.docker.io) and [Rocket](https://coreos.com/blog/rocket/) containers, and other container image formats and container runtimes will be supported in the future.
-
-While Kubernetes currently focuses on continuously-running stateless (e.g. web server or in-memory object cache) and "cloud native" stateful applications (e.g. NoSQL datastores), in the near future it will support all the other workload types commonly found in production cluster environments, such as batch, stream processing, and traditional databases.
-
-In Kubernetes, all containers run inside [pods](/{{page.version}}/docs/user-guide/pods). A pod can host a single container, or multiple cooperating containers; in the latter case, the containers in the pod are guaranteed to be co-located on the same machine and can share resources. A pod can also contain zero or more [volumes](/{{page.version}}/docs/user-guide/volumes), which are directories that are private to a container or shared across containers in a pod. For each pod the user creates, the system finds a machine that is healthy and that has sufficient available capacity, and starts up the corresponding container(s) there. If a container fails it can be automatically restarted by Kubernetes' node agent, called the Kubelet. But if the pod or its machine fails, it is not automatically moved or restarted unless the user also defines a [replication controller](/{{page.version}}/docs/user-guide/replication-controller), which we discuss next.
-
-Users can create and manage pods themselves, but Kubernetes drastically simplifies system management by allowing users to delegate two common pod-related activities: deploying multiple pod replicas based on the same pod configuration, and creating replacement pods when a pod or its machine fails. The Kubernetes API object that manages these behaviors is called a [replication controller](/{{page.version}}/docs/user-guide/replication-controller). It defines a pod in terms of a template, that the system then instantiates as some number of pods (specified by the user). The replicated set of pods might constitute an entire application, a micro-service, or one layer in a multi-tier application. Once the pods are created, the system continually monitors their health and that of the machines they are running on; if a pod fails due to a software problem or machine failure, the replication controller automatically creates a new pod on a healthy machine, to maintain the set of pods at the desired replication level. Multiple pods from the same or different applications can share the same machine. Note that a replication controller is needed even in the case of a single non-replicated pod if the user wants it to be re-created when it or its machine fails.
-
-Frequently it is useful to refer to a set of pods, for example to limit the set of pods on which a mutating operation should be performed, or that should be queried for status. As a general mechanism, users can attach to most Kubernetes API objects arbitrary key-value pairs called [labels](/{{page.version}}/docs/user-guide/labels), and then use a set of label selectors (key-value queries over labels) to constrain the target of API operations. Each resource also has a map of string keys and values that can be used by external tooling to store and retrieve arbitrary metadata about this object, called [annotations](/{{page.version}}/docs/user-guide/annotations).
-
-Kubernetes supports a unique [networking model](/{{page.version}}/docs/admin/networking). Kubernetes encourages a flat address space and does not dynamically allocate ports, instead allowing users to select whichever ports are convenient for them. To achieve this, it allocates an IP address for each pod.
-
-Modern Internet applications are commonly built by layering micro-services, for example a set of web front-ends talking to a distributed in-memory key-value store talking to a replicated storage service. To facilitate this architecture, Kubernetes offers the [service](/{{page.version}}/docs/user-guide/services) abstraction, which provides a stable IP address and [DNS name](/{{page.version}}/docs/admin/dns) that corresponds to a dynamic set of pods such as the set of pods constituting a micro-service. The set is defined using a label selector and thus can refer to any set of pods. When a container running in a Kubernetes pod connects to this address, the connection is forwarded by a local agent (called the kube proxy) running on the source machine, to one of the corresponding back-end containers. The exact back-end is chosen using a round-robin policy to balance load. The kube proxy takes care of tracking the dynamic set of back-ends as pods are replaced by new pods on new hosts, so that the service IP address (and DNS name) never changes.
-
-Every resource in Kubernetes, such as a pod, is identified by a URI and has a UID. Important components of the URI are the kind of object (e.g. pod), the object's name, and the object's [namespace](/{{page.version}}/docs/user-guide/namespaces). For a certain object kind, every name is unique within its namespace. In contexts where an object name is provided without a namespace, it is assumed to be in the default namespace. UID is unique across time and space.
-
-
-
diff --git a/v1.2/docs/user-guide/persistent-volumes/claims/claim-01.yaml b/v1.2/docs/user-guide/persistent-volumes/claims/claim-01.yaml
deleted file mode 100644
index 7bf0e87dcc..0000000000
--- a/v1.2/docs/user-guide/persistent-volumes/claims/claim-01.yaml
+++ /dev/null
@@ -1,10 +0,0 @@
-kind: PersistentVolumeClaim
-apiVersion: v1
-metadata:
-  name: myclaim-1
-spec:
-  accessModes:
-    - ReadWriteOnce
-  resources:
-    requests:
-      storage: 3Gi
diff --git a/v1.2/docs/user-guide/persistent-volumes/claims/claim-02.yaml b/v1.2/docs/user-guide/persistent-volumes/claims/claim-02.yaml
deleted file mode 100644
index 89e3263897..0000000000
--- a/v1.2/docs/user-guide/persistent-volumes/claims/claim-02.yaml
+++ /dev/null
@@ -1,10 +0,0 @@
-kind: PersistentVolumeClaim
-apiVersion: v1
-metadata:
-  name: myclaim-2
-spec:
-  accessModes:
-    - ReadWriteOnce
-  resources:
-    requests:
-      storage: 8Gi
diff --git a/v1.2/docs/user-guide/persistent-volumes/claims/claim-03.json b/v1.2/docs/user-guide/persistent-volumes/claims/claim-03.json
deleted file mode 100644
index 8b8a9e95fb..0000000000
--- a/v1.2/docs/user-guide/persistent-volumes/claims/claim-03.json
+++ /dev/null
@@ -1,17 +0,0 @@
-{
-    "kind": "PersistentVolumeClaim",
-    "apiVersion": "v1",
-    "metadata": {
-        "name": "myclaim-3"
-    }, "spec": {
-        "accessModes": [
-            "ReadWriteOnce",
-            "ReadOnlyMany"
-        ],
-        "resources": {
-            "requests": {
-                "storage": "10G"
-            }
-        }
-    }
-}
diff --git a/v1.2/docs/user-guide/persistent-volumes/index.md b/v1.2/docs/user-guide/persistent-volumes/index.md
deleted file mode 100644
index ee996b58de..0000000000
--- a/v1.2/docs/user-guide/persistent-volumes/index.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
----
-
-The purpose of this guide is to help you become familiar with [Kubernetes Persistent Volumes](/{{page.version}}/docs/user-guide/persistent-volumes/).  By the end of the guide, we'll have
-nginx serving content from your persistent volume.
-
-This guide assumes knowledge of Kubernetes fundamentals and that you have a cluster up and running.
-
-See [Persistent Storage design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/persistent-storage.md) for more information.
-
-## Provisioning
-
-A Persistent Volume (PV) in Kubernetes represents a real piece of underlying storage capacity in the infrastructure.  Cluster administrators
-must first create storage (create their Google Compute Engine (GCE) disks, export their NFS shares, etc.) in order for Kubernetes to mount it.
-
-PVs are intended for "network volumes" like GCE Persistent Disks, NFS shares, and AWS ElasticBlockStore volumes.  `HostPath` was included
-for ease of development and testing.  You'll create a local `HostPath` for this example.
-
-> IMPORTANT! For `HostPath` to work, you will need to run a single node cluster.  Kubernetes does not
-support local storage on the host at this time.  There is no guarantee your pod ends up on the correct node where the `HostPath` resides.
-
-```shell
-# This will be nginx's webroot
-$ mkdir /tmp/data01
-$ echo 'I love Kubernetes storage!' > /tmp/data01/index.html
-```
-
-PVs are created by posting them to the API server.
-
-```shell
-$ kubectl create -f docs/user-guide/persistent-volumes/volumes/local-01.yaml
-NAME      LABELS       CAPACITY      ACCESSMODES   STATUS      CLAIM     REASON
-pv0001    type=local   10737418240   RWO           Available 
-```
-
-## Requesting storage
-
-Users of Kubernetes request persistent storage for their pods.  They don't know how the underlying cluster is provisioned.
-They just know they can rely on their claim to storage and can manage its lifecycle independently from the many pods that may use it.
-
-Claims must be created in the same namespace as the pods that use them.
-
-```shell
-$ kubectl create -f docs/user-guide/persistent-volumes/claims/claim-01.yaml
-
-$ kubectl get pvc
-NAME                LABELS              STATUS              VOLUME
-myclaim-1           map[]                                   
-           
-           
-# A background process will attempt to match this claim to a volume.
-# The eventual state of your claim will look something like this:
-
-$ kubectl get pvc
-NAME        LABELS    STATUS    VOLUME
-myclaim-1   map[]     Bound     pv0001
-
-$ kubectl get pv
-NAME      LABELS       CAPACITY      ACCESSMODES   STATUS    CLAIM               REASON
-pv0001    type=local   10737418240   RWO           Bound     default/myclaim-1 
-```
-
-## Using your claim as a volume
-
-Claims are used as volumes in pods.  Kubernetes uses the claim to look up its bound PV.  The PV is then exposed to the pod.
-
-```shell
-$ kubectl create -f docs/user-guide/persistent-volumes/simpletest/pod.yaml
-
-$ kubectl get pods
-NAME      READY     STATUS    RESTARTS   AGE
-mypod     1/1       Running   0          1h
-
-$ kubectl create -f docs/user-guide/persistent-volumes/simpletest/service.json
-$ kubectl get services
-NAME              CLUSTER_IP       EXTERNAL_IP       PORT(S)       SELECTOR           AGE
-frontendservice   10.0.0.241       <none>            3000/TCP      name=frontendhttp  1d
-kubernetes        10.0.0.2         <none>            443/TCP       <none>             2d
-```
-
-## Next steps
-
-You should be able to query your service endpoint and see what content nginx is serving.  A "forbidden" error might mean you
-need to disable SELinux (setenforce 0).
-
-```shell
-$ curl 10.0.0.241:3000
-I love Kubernetes storage!
-```
-
-Hopefully this simple guide is enough to get you started with PersistentVolumes.  If you have any questions, join the team on [Slack](/{{page.version}}/docs/troubleshooting/#slack) and ask!
-
-Enjoy!
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/persistent-volumes/simpletest/namespace.json b/v1.2/docs/user-guide/persistent-volumes/simpletest/namespace.json
deleted file mode 100644
index 79e2c3521e..0000000000
--- a/v1.2/docs/user-guide/persistent-volumes/simpletest/namespace.json
+++ /dev/null
@@ -1,10 +0,0 @@
-{
-    "kind": "Namespace",
-    "apiVersion":"v1",
-    "metadata": {
-        "name": "myns",
-        "labels": {
-            "name": "development"
-        }
-    }
-}
diff --git a/v1.2/docs/user-guide/persistent-volumes/simpletest/pod.yaml b/v1.2/docs/user-guide/persistent-volumes/simpletest/pod.yaml
deleted file mode 100644
index 3edf2963b3..0000000000
--- a/v1.2/docs/user-guide/persistent-volumes/simpletest/pod.yaml
+++ /dev/null
@@ -1,20 +0,0 @@
-kind: Pod
-apiVersion: v1
-metadata:
-  name: mypod
-  labels:
-    name: frontendhttp
-spec:
-  containers:
-    - name: myfrontend
-      image: nginx
-      ports:
-        - containerPort: 80
-          name: "http-server"
-      volumeMounts:
-      - mountPath: "/var/www/html"
-        name: mypd
-  volumes:
-    - name: mypd
-      persistentVolumeClaim:
-       claimName: myclaim-1
diff --git a/v1.2/docs/user-guide/persistent-volumes/simpletest/service.json b/v1.2/docs/user-guide/persistent-volumes/simpletest/service.json
deleted file mode 100644
index 0e06aa9f03..0000000000
--- a/v1.2/docs/user-guide/persistent-volumes/simpletest/service.json
+++ /dev/null
@@ -1,19 +0,0 @@
-{
-  "kind": "Service",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "frontendservice"
-  },
-  "spec": {
-    "ports": [
-      {
-        "protocol": "TCP",
-        "port": 3000,
-        "targetPort": "http-server"
-      }
-    ],
-    "selector": {
-      "name": "frontendhttp"
-    }
-  }
-}
diff --git a/v1.2/docs/user-guide/persistent-volumes/volumes/gce.yaml b/v1.2/docs/user-guide/persistent-volumes/volumes/gce.yaml
deleted file mode 100644
index 87cb7fa3dc..0000000000
--- a/v1.2/docs/user-guide/persistent-volumes/volumes/gce.yaml
+++ /dev/null
@@ -1,13 +0,0 @@
-kind: PersistentVolume
-apiVersion: v1
-metadata:
-  name: pv0003
-spec:
-  capacity:
-    storage: 10Gi
-  accessModes:
-    - ReadWriteOnce
-    - ReadOnlyMany
-  gcePersistentDisk:
-    pdName: "abc123"
-    fsType: "ext4"
diff --git a/v1.2/docs/user-guide/persistent-volumes/volumes/local-01.yaml b/v1.2/docs/user-guide/persistent-volumes/volumes/local-01.yaml
deleted file mode 100644
index a465c65149..0000000000
--- a/v1.2/docs/user-guide/persistent-volumes/volumes/local-01.yaml
+++ /dev/null
@@ -1,13 +0,0 @@
-kind: PersistentVolume
-apiVersion: v1
-metadata:
-  name: pv0001
-  labels:
-    type: local
-spec:
-  capacity:
-    storage: 10Gi
-  accessModes:
-    - ReadWriteOnce
-  hostPath:
-    path: "/tmp/data01"
diff --git a/v1.2/docs/user-guide/persistent-volumes/volumes/local-02.yaml b/v1.2/docs/user-guide/persistent-volumes/volumes/local-02.yaml
deleted file mode 100644
index b946e7105d..0000000000
--- a/v1.2/docs/user-guide/persistent-volumes/volumes/local-02.yaml
+++ /dev/null
@@ -1,14 +0,0 @@
-kind: PersistentVolume
-apiVersion: v1
-metadata:
-  name: pv0002
-  labels:
-    type: local
-spec:
-  capacity:
-    storage: 8Gi
-  accessModes:
-    - ReadWriteOnce
-  hostPath:
-    path: "/tmp/data02"
-  persistentVolumeReclaimPolicy: Recycle
diff --git a/v1.2/docs/user-guide/persistent-volumes/volumes/nfs.yaml b/v1.2/docs/user-guide/persistent-volumes/volumes/nfs.yaml
deleted file mode 100644
index a6dc2ed250..0000000000
--- a/v1.2/docs/user-guide/persistent-volumes/volumes/nfs.yaml
+++ /dev/null
@@ -1,12 +0,0 @@
-apiVersion: v1
-kind: PersistentVolume
-metadata:
-  name: pv0003
-spec:
-  capacity:
-    storage: 5Gi
-  accessModes:
-    - ReadWriteOnce
-  nfs:
-    path: /tmp
-    server: 172.17.0.2
diff --git a/v1.2/docs/user-guide/pod-states.md b/v1.2/docs/user-guide/pod-states.md
deleted file mode 100644
index 83e9bb8466..0000000000
--- a/v1.2/docs/user-guide/pod-states.md
+++ /dev/null
@@ -1,125 +0,0 @@
----
----
-
-Updated: 4/14/2015
-
-This document covers the lifecycle of a pod.  It is not an exhaustive document, but an introduction to the topic.
-
-## Pod Phase
-
-As consistent with the overall [API convention](/{{page.version}}/docs/devel/api-conventions/#typical-status-properties), phase is a simple, high-level summary of the phase of the lifecycle of a pod. It is not intended to be a comprehensive rollup of observations of container-level or even pod-level conditions or other state, nor is it intended to be a comprehensive state machine.
-
-The number and meanings of `PodPhase` values are tightly guarded.  Other than what is documented here, nothing should be assumed about pods with a given `PodPhase`.
-
-* Pending: The pod has been accepted by the system, but one or more of the container images has not been created.  This includes time before being scheduled as well as time spent downloading images over the network, which could take a while.
-* Running: The pod has been bound to a node, and all of the containers have been created.  At least one container is still running, or is in the process of starting or restarting.
-* Succeeded: All containers in the pod have terminated in success, and will not be restarted.
-* Failed: All containers in the pod have terminated, at least one container has terminated in failure (exited with non-zero exit status or was terminated by the system).
-* Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod.
-
-## Pod Conditions
-
-A pod containing containers that specify readiness probes will also report the Ready condition. Condition status values may be `True`, `False`, or `Unknown`.
-
-## Container Probes
-
-A [Probe](https://godoc.org/k8s.io/kubernetes/pkg/api/v1#Probe) is a diagnostic performed periodically by the kubelet on a container. Specifically the diagnostic is one of three [Handlers](https://godoc.org/k8s.io/kubernetes/pkg/api/v1#Handler):
-
-* `ExecAction`: executes a specified command inside the container expecting on success that the command exits with status code 0.
-* `TCPSocketAction`: performs a tcp check against the container's IP address on a specified port expecting on success that the port is open.
-* `HTTPGetAction`: performs an HTTP Get against the container's IP address on a specified port and path expecting on success that the response has a status code greater than or equal to 200 and less than 400.
-
-Each probe will have one of three results:
-
-* `Success`: indicates that the container passed the diagnostic.
-* `Failure`: indicates that the container failed the diagnostic.
-* `Unknown`: indicates that the diagnostic failed so no action should be taken.
-
-Currently, the kubelet optionally performs two independent diagnostics on running containers which trigger action:
-
-* `LivenessProbe`: indicates whether the container is *live*, i.e. still running. The LivenessProbe hints to the kubelet when a container is unhealthy. If the LivenessProbe fails, the kubelet will kill the container and the container will be subjected to it's [RestartPolicy](#restartpolicy). The default state of Liveness before the initial delay is `Success`. The state of Liveness for a container when no probe is provided is assumed to be `Success`.
-* `ReadinessProbe`: indicates whether the container is *ready* to service requests. If the ReadinessProbe fails, the endpoints controller will remove the pod's IP address from the endpoints of all services that match the pod. Thus, the ReadinessProbe is sometimes useful to signal to the endpoints controller that even though a pod may be running, it should not receive traffic from the proxy (e.g. the container has a long startup time before it starts listening or the container is down for maintenance). The default state of Readiness before the initial delay is `Failure`. The state of Readiness for a container when no probe is provided is assumed to be `Success`.
-
-## Container Statuses
-
-More detailed information about the current (and previous) container statuses can be found in [ContainerStatuses](https://godoc.org/k8s.io/kubernetes/pkg/api/v1#PodStatus). The information reported depends on the current [ContainerState](https://godoc.org/k8s.io/kubernetes/pkg/api/v1#ContainerState), which may be Waiting, Running, or Terminated.
-
-## RestartPolicy
-
-The possible values for RestartPolicy are `Always`, `OnFailure`, or `Never`. If RestartPolicy is not set, the default value is `Always`. RestartPolicy applies to all containers in the pod. RestartPolicy only refers to restarts of the containers by the Kubelet on the same node. Failed containers that are restarted by Kubelet, are restarted with an exponential back-off delay, the delay is in multiples of sync-frequency 0, 1x, 2x, 4x, 8x ... capped at 5 minutes and is reset after 10 minutes of successful execution. As discussed in the [pods document](/{{page.version}}/docs/user-guide/pods/#durability-of-pods-or-lack-thereof), once bound to a node, a pod will never be rebound to another node. This means that some kind of controller is necessary in order for a pod to survive node failure, even if just a single pod at a time is desired.
-
-Three types of controllers are currently available:
-
-- Use a [`Job`](/{{page.version}}/docs/user-guide/jobs) for pods which are expected to terminate (e.g. batch computations).
-- Use a [`ReplicationController`](/{{page.version}}/docs/user-guide/replication-controller) for pods which are not expected to
-
-  terminate, and where (e.g. web servers).
-- Use a [`DaemonSet`](/{{page.version}}/docs/admin/daemons): Use for pods which need to run 1 per machine because they provide a
-  machine-specific system service.
-If you are unsure whether to use ReplicationController or Daemon, then see [Daemon Set versus
-Replication Controller](/{{page.version}}/docs/admin/daemons/#daemon-set-versus-replication-controller).
-
-`ReplicationController` is *only* appropriate for pods with `RestartPolicy = Always`.
-`Job` is *only* appropriate for pods with `RestartPolicy` equal to `OnFailure` or `Never`.
-
-All 3 types of controllers contain a PodTemplate, which has all the same fields as a Pod.
-It is recommended to create the appropriate controller and let it create pods, rather than to
-directly create pods yourself.  That is because pods alone are not resilient to machine failures,
-but Controllers are.
-
-## Pod lifetime
-
-In general, pods which are created do not disappear until someone destroys them.  This might be a human or a `ReplicationController`, or another controller.  The only exception to this rule is that pods with a `PodPhase` of `Succeeded` or `Failed` for more than some duration (determined by the master) will expire and be automatically reaped.
-
-If a node dies or is disconnected from the rest of the cluster, some entity within the system (call it the NodeController for now) is responsible for applying policy (e.g. a timeout) and marking any pods on the lost node as `Failed`.
-
-## Examples
-
-   * Pod is `Running`, 1 container, container exits success
-     * Log completion event
-     * If RestartPolicy is:
-       * Always: restart container, pod stays `Running`
-       * OnFailure: pod becomes `Succeeded`
-       * Never: pod becomes `Succeeded`
-
-   * Pod is `Running`, 1 container, container exits failure
-     * Log failure event
-     * If RestartPolicy is:
-       * Always: restart container, pod stays `Running`
-       * OnFailure: restart container, pod stays `Running`
-       * Never: pod becomes `Failed`
-
-   * Pod is `Running`, 2 containers, container 1 exits failure
-     * Log failure event
-     * If RestartPolicy is:
-       * Always: restart container, pod stays `Running`
-       * OnFailure: restart container, pod stays `Running`
-       * Never: pod stays `Running`
-     * When container 2 exits...
-       * Log failure event
-       * If RestartPolicy is:
-         * Always: restart container, pod stays `Running`
-         * OnFailure: restart container, pod stays `Running`
-         * Never: pod becomes `Failed`
-
-   * Pod is `Running`, container becomes OOM
-     * Container terminates in failure
-     * Log OOM event
-     * If RestartPolicy is:
-       * Always: restart container, pod stays `Running`
-       * OnFailure: restart container, pod stays `Running`
-       * Never: log failure event, pod becomes `Failed`
-
-   * Pod is `Running`, a disk dies
-     * All containers are killed
-     * Log appropriate event
-     * Pod becomes `Failed`
-     * If running under a controller, pod will be recreated elsewhere
-
-   * Pod is `Running`, its node is segmented out
-     * NodeController waits for timeout
-     * NodeController marks pod `Failed`
-     * If running under a controller, pod will be recreated elsewhere
-
-
-
diff --git a/v1.2/docs/user-guide/pod.yaml b/v1.2/docs/user-guide/pod.yaml
deleted file mode 100644
index 7053af0be4..0000000000
--- a/v1.2/docs/user-guide/pod.yaml
+++ /dev/null
@@ -1,12 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-  labels:
-    app: nginx
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    ports:
-    - containerPort: 80
diff --git a/v1.2/docs/user-guide/pods.md b/v1.2/docs/user-guide/pods.md
deleted file mode 100644
index eb018929f3..0000000000
--- a/v1.2/docs/user-guide/pods.md
+++ /dev/null
@@ -1,124 +0,0 @@
----
----
-
-* TOC
-{:toc}
-
-In Kubernetes, rather than individual application containers, _pods_ are the smallest deployable units that can be created, scheduled, and managed.
-
-## What is a _pod_?
-
-A _pod_ (as in a pod of whales or pea pod) corresponds to a colocated group of applications running with a shared context. Within that context, the applications may also have individual cgroup isolations applied. A pod models an application-specific "logical host" in a containerized environment. It may contain one or more applications which are relatively tightly coupled &mdash; in a pre-container world, they would have executed on the same physical or virtual host.
-
-The context of the pod can be defined as the conjunction of several Linux namespaces:
-
-* PID namespace (applications within the pod can see each other's processes)
-* network namespace (applications within the pod have access to the same IP and port space)
-* IPC namespace (applications within the pod can use SystemV IPC or POSIX message queues to communicate)
-* UTS namespace (applications within the pod share a hostname)
-
-Applications within a pod also have access to shared volumes, which are defined at the pod level and made available in each application's filesystem. Additionally, a pod may define top-level cgroup isolations which form an outer bound to any individual isolation applied to constituent applications.
-
-In terms of [Docker](https://www.docker.com/) constructs, a pod consists of a colocated group of Docker containers with shared [volumes](/{{page.version}}/docs/user-guide/volumes). PID namespace sharing is not yet implemented with Docker.
-
-Like individual application containers, pods are considered to be relatively ephemeral rather than durable entities. As discussed in [life of a pod](/{{page.version}}/docs/user-guide/pod-states), pods are scheduled to nodes and remain there until termination (according to restart policy) or deletion. When a node dies, the pods scheduled to that node are deleted. Specific pods are never rescheduled to new nodes; instead, they must be replaced (see [/{{page.version}}/docs/user-guide/replication controller](/{{page.version}}/docs/user-guide/replication-controller) for more details). (In the future, a higher-level API may support pod migration.)
-
-## Motivation for pods
-
-### Resource sharing and communication
-
-Pods facilitate data sharing and communication among their constituents.
-
-The applications in the pod all use the same network namespace/IP and port space, and can find and communicate with each other using localhost. Each pod has an IP address in a flat shared networking namespace that has full communication with other physical computers and containers across the network. The hostname is set to the pod's Name for the application containers within the pod. [More details on networking](/{{page.version}}/docs/admin/networking).
-
-In addition to defining the application containers that run in the pod, the pod specifies a set of shared storage volumes. Volumes enable data to survive container restarts and to be shared among the applications within the pod.
-
-### Management
-
-Pods also simplify application deployment and management by providing a higher-level abstraction than the raw, low-level container interface. Pods serve as units of deployment and horizontal scaling/replication. Co-location (co-scheduling), fate sharing, coordinated replication, resource sharing, and dependency management are handled automatically.
-
-## Uses of pods
-
-Pods can be used to host vertically integrated application stacks, but their primary motivation is to support co-located, co-managed helper programs, such as:
-
-* content management systems, file and data loaders, local cache managers, etc.
-* log and checkpoint backup, compression, rotation, snapshotting, etc.
-* data change watchers, log tailers, logging and monitoring adapters, event publishers, etc.
-* proxies, bridges, and adapters
-* controllers, managers, configurators, and updaters
-
-Individual pods are not intended to run multiple instances of the same application, in general.
-
-For a longer explanation, see [The Distributed System ToolKit: Patterns for Composite Containers](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns).
-
-## Alternatives considered
-
-_Why not just run multiple programs in a single (Docker) container?_
-
-1. Transparency. Making the containers within the pod visible to the infrastructure enables the infrastructure to provide services to those containers, such as process management and resource monitoring. This facilitates a number of conveniences for users.
-2. Decoupling software dependencies. The individual containers may be rebuilt and redeployed independently. Kubernetes may even support live updates of individual containers someday.
-3. Ease of use. Users don't need to run their own process managers, worry about signal and exit-code propagation, etc.
-4. Efficiency. Because the infrastructure takes on more responsibility, containers can be lighter weight.
-
-_Why not support affinity-based co-scheduling of containers?_
-
-That approach would provide co-location, but would not provide most of the benefits of pods, such as resource sharing, IPC, guaranteed fate sharing, and simplified management.
-
-## Durability of pods (or lack thereof)
-
-Pods aren't intended to be treated as durable [pets](https://blog.engineyard.com/2014/pets-vs-cattle). They won't survive scheduling failures, node failures, or other evictions, such as due to lack of resources, or in the case of node maintenance.
-
-In general, users shouldn't need to create pods directly. They should almost always use controllers (e.g., [replication controller](/{{page.version}}/docs/user-guide/replication-controller)), even for singletons.  Controllers provide self-healing with a cluster scope, as well as replication and rollout management.
-
-The use of collective APIs as the primary user-facing primitive is relatively common among cluster scheduling systems, including [Borg](https://research.google.com/pubs/pub43438), [Marathon](https://mesosphere.github.io/marathon/docs/rest-api), [Aurora](http://aurora.apache.org/documentation/latest/configuration-reference/#job-schema), and [Tupperware](http://www.slideshare.net/Docker/aravindnarayanan-facebook140613153626phpapp02-37588997).
-
-Pod is exposed as a primitive in order to facilitate:
-
-* scheduler and controller pluggability
-* support for pod-level operations without the need to "proxy" them via controller APIs
-* decoupling of pod lifetime from controller lifetime, such as for bootstrapping
-* decoupling of controllers and services &mdash; the endpoint controller just watches pods
-* clean composition of Kubelet-level functionality with cluster-level functionality &mdash; Kubelet is effectively the "pod controller"
-* high-availability applications, which will expect pods to be replaced in advance of their termination and certainly in advance of deletion, such as in the case of planned evictions, image prefetching, or live pod migration [#3949](http://issue.k8s.io/3949)
-
-The current best practice for pets is to create a replication controller with `replicas` equal to `1` and a corresponding service. If you find this cumbersome, please comment on [issue #260](http://issue.k8s.io/260).
-
-## Termination of Pods
-
-Because pods represent running processes on nodes in the cluster, it is important to allow those processes to gracefully terminate when they are no longer needed (vs being violently killed with a KILL signal and having no chance to clean up). Users should be able to request deletion and know when processes terminate, but also be able to ensure that deletes eventually complete. When a user requests deletion of a pod the system records the intended grace period before the pod is allowed to be forcefully killed, and a TERM signal is sent to the main process in each container. Once the grace period has expired the KILL signal is sent to those processes and the pod is then deleted from the API server. If the Kubelet or the container manager is restarted while waiting for processes to terminate, the termination will be retried with the full grace period.
-
-An example flow:
-
-1. User sends command to delete Pod, with default grace period (30s)
-2. The Pod in the API server is updated with the time beyond which the Pod is considered "dead" along with the grace period.
-3. Pod shows up as "Terminating" when listed in client commands
-4. (simultaneous with 3) When the Kubelet sees that a Pod has been marked as terminating because the time in 2 has been set, it begins the pod shutdown process.
-  1. If the pod has defined a [preStop hook](/{{page.version}}/docs/user-guide/container-environment/#hook-details), it is invoked inside of the pod. If the `preStop` hook is still running after the grace period expires, step 2 is then invoked with a small (2 second) extended grace period.
-  2. The processes in the Pod are sent the TERM signal.
-5. (simultaneous with 3), Pod is removed from endpoints list for service, and are no longer considered part of the set of running pods for replication controllers. Pods that shutdown slowly can continue to serve traffic as load balancers (like the service proxy) remove them from their rotations.
-6. When the grace period expires, any processes still running in the Pod are killed with SIGKILL.
-7. The Kubelet will finish deleting the Pod on the API server by setting grace period 0 (immediate deletion). The Pod disappears from the API and is no longer visible from the client.
-
-By default, all deletes are graceful within 30 seconds. The `kubectl delete` command supports the `--grace-period=<seconds>` option which allows a user to override the default and specify their own value. The value `0` indicates that delete should be immediate, and removes the pod in the API immediately so a new pod can be created with the same name. On the node pods that are set to terminate immediately will still be given a small grace period before being force killed.
-
-## Privileged mode for pod containers
-
-From kubernetes v1.1, any container in a pod can enable privileged mode, using the `privileged` flag on the `SecurityContext` of the container spec. This is useful for containers that want to use linux capabilities like manipulating the network stack and accessing devices. Processes within the container get almost the same privileges that are available to processes outside a container. With privileged mode, it should be easier to write network and volume plugins as seperate pods that don't need to be compiled into the kubelet.
-
-If the master is running kubernetes v1.1 or higher, and the nodes are running a version lower than v1.1, then new privileged pods will be accepted by api-server, but will not be launched. They will be pending state.
-If user calls `kubectl describe pod FooPodName`, user can see the reason why the pod is in pending state. The events table in the describe command output will say:
-`Error validating pod "FooPodName"."FooPodNamespace" from api, ignoring: spec.containers[0].securityContext.privileged: forbidden '<*>(0xc2089d3248)true'`
-
-
-If the master is running a version lower than v1.1, then privileged pods cannot be created. If user attempts to create a pod, that has a privileged container, the user will get the following error:
-`The Pod "FooPodName" is invalid.
-spec.containers[0].securityContext.privileged: forbidden '<*>(0xc20b222db0)true'`
-
-## API Object
-
-Pod is a top-level resource in the kubernetes REST API. More details about the
-API object can be found at: [Pod API
-object](http://kubernetes.io/v1.1/docs/api-reference/v1/definitions/#_v1_pod).
-
-
-
diff --git a/v1.2/docs/user-guide/prereqs.md b/v1.2/docs/user-guide/prereqs.md
deleted file mode 100644
index 45ced79a73..0000000000
--- a/v1.2/docs/user-guide/prereqs.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
----
-
-To deploy and manage applications on Kubernetes, you'll use the Kubernetes command-line tool, [kubectl](/{{page.version}}/docs/user-guide/kubectl/kubectl). It lets you inspect your cluster resources, create, delete, and update components, and much more. You will use it to look at your new cluster and bring up example apps.
-
-## Installing kubectl
-
-If you downloaded a pre-compiled [release](https://github.com/kubernetes/kubernetes/releases), kubectl should be under `platforms/<os>/<arch>` from the tar bundle.
-
-If you built from source, kubectl should be either under `_output/local/bin/<os>/<arch>` or `_output/dockerized/bin/<os>/<arch>`.
-
-The kubectl binary doesn't have to be installed to be executable, but the rest of the walkthrough will assume that it's in your PATH.
-
-The simplest way to install is to copy or move kubectl into a dir already in PATH (e.g. `/usr/local/bin`). For example:
-
-```shell
-# OS X
-$ sudo cp kubernetes/platforms/darwin/amd64/kubectl /usr/local/bin/kubectl
-# Linux
-$ sudo cp kubernetes/platforms/linux/amd64/kubectl /usr/local/bin/kubectl
-```
-
-You also need to ensure it's executable:
-
-```shell
-$ sudo chmod +x /usr/local/bin/kubectl
-```
-
-If you prefer not to copy kubectl, you need to ensure the tool is in your path:
-
-```shell
-# OS X
-export PATH=<path/to/kubernetes-directory>/platforms/darwin/amd64:$PATH
-
-# Linux
-export PATH=<path/to/kubernetes-directory>/platforms/linux/amd64:$PATH
-```
-
-## Configuring kubectl
-
-In order for kubectl to find and access the Kubernetes cluster, it needs a [kubeconfig file](/{{page.version}}/docs/user-guide/kubeconfig-file), which is created automatically when creating a cluster using kube-up.sh (see the [getting started guides](/{{page.version}}/docs/getting-started-guides/) for more about creating clusters). If you need access to a cluster you didn't create, see the [Sharing Cluster Access document](/{{page.version}}/docs/user-guide/sharing-clusters).
-By default, kubectl configuration lives at `~/.kube/config`.
-
-#### Making sure you're ready
-
-Check that kubectl is properly configured by getting the cluster state:
-
-```shell
-$ kubectl cluster-info
-```
-
-If you see a url response, you are ready to go.
-
-## What's next?
-
-[Learn how to launch and expose your application.](/{{page.version}}/docs/user-guide/quick-start)
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/production-pods.md b/v1.2/docs/user-guide/production-pods.md
deleted file mode 100644
index 8be9ee4328..0000000000
--- a/v1.2/docs/user-guide/production-pods.md
+++ /dev/null
@@ -1,343 +0,0 @@
----
----
-
-You've seen [how to configure and deploy pods and containers](/{{page.version}}/docs/user-guide/configuring-containers), using some of the most common configuration parameters. This section dives into additional features that are especially useful for running applications in production.
-
-* TOC
-{:toc}
-
-## Persistent storage
-
-The container file system only lives as long as the container does, so when a container crashes and restarts, changes to the filesystem will be lost and the container will restart from a clean slate. To access more-persistent storage, outside the container file system, you need a [*volume*](/{{page.version}}/docs/user-guide/volumes). This is especially important to stateful applications, such as key-value stores and databases.
-
-For example, [Redis](http://redis.io/) is a key-value cache and store, which we use in the [guestbook](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/) and other examples. We can add a volume to it to store persistent data as follows:
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: redis
-spec:
-  template:
-    metadata:
-      labels:
-        app: redis
-        tier: backend
-    spec:
-      # Provision a fresh volume for the pod
-      volumes:
-        - name: data
-          emptyDir: {}
-      containers:
-      - name: redis
-        image: kubernetes/redis:v1
-        ports:
-        - containerPort: 6379
-        # Mount the volume into the pod
-        volumeMounts:
-        - mountPath: /redis-master-data
-          name: data   # must match the name of the volume, above
-```
-
-`emptyDir` volumes live for the lifespan of the [pod](/{{page.version}}/docs/user-guide/pods), which is longer than the lifespan of any one container, so if the container fails and is restarted, our storage will live on.
-
-In addition to the local disk storage provided by `emptyDir`, Kubernetes supports many different network-attached storage solutions, including PD on GCE and EBS on EC2, which are preferred for critical data, and will handle details such as mounting and unmounting the devices on the nodes. See [the volumes doc](/{{page.version}}/docs/user-guide/volumes) for more details.
-
-## Distributing credentials
-
-Many applications need credentials, such as passwords, OAuth tokens, and TLS keys, to authenticate with other applications, databases, and services. Storing these credentials in container images or environment variables is less than ideal, since the credentials can then be copied by anyone with access to the image, pod/container specification, host file system, or host Docker daemon.
-
-Kubernetes provides a mechanism, called [*secrets*](/{{page.version}}/docs/user-guide/secrets), that facilitates delivery of sensitive credentials to applications. A `Secret` is a simple resource containing a map of data. For instance, a simple secret with a username and password might look as follows:
-
-```yaml
-apiVersion: v1
-kind: Secret
-metadata:
-  name: mysecret
-type: Opaque
-data:
-  password: dmFsdWUtMg0K
-  username: dmFsdWUtMQ0K
-```
-
-As with other resources, this secret can be instantiated using `create` and can be viewed with `get`:
-
-```shell
-$ kubectl create -f ./secret.yaml
-secrets/mysecret
-$ kubectl get secrets
-NAME                  TYPE                                  DATA
-default-token-v9pyz   kubernetes.io/service-account-token   2
-mysecret              Opaque                                2
-```
-
-To use the secret, you need to reference it in a pod or pod template. The `secret` volume source enables you to mount it as an in-memory directory into your containers.
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: redis
-spec:
-  template:
-    metadata:
-      labels:
-        app: redis
-        tier: backend
-    spec:
-      volumes:
-        - name: data
-          emptyDir: {}
-        - name: supersecret
-          secret:
-            secretName: mysecret
-      containers:
-      - name: redis
-        image: kubernetes/redis:v1
-        ports:
-        - containerPort: 6379
-        # Mount the volume into the pod
-        volumeMounts:
-        - mountPath: /redis-master-data
-          name: data   # must match the name of the volume, above
-        - mountPath: /var/run/secrets/super
-          name: supersecret
-```
-
-For more details, see the [secrets document](/{{page.version}}/docs/user-guide/secrets), [example](/{{page.version}}/docs/user-guide/secrets/) and [design doc](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/secrets.md).
-
-## Authenticating with a private image registry
-
-Secrets can also be used to pass [image registry credentials](/{{page.version}}/docs/user-guide/images/#using-a-private-registry).
-
-First, create a `.dockercfg` file, such as running `docker login <registry.domain>`.
-Then put the resulting `.dockercfg` file into a [secret resource](/{{page.version}}/docs/user-guide/secrets).  For example:
-
-```shell
-$ docker login
-Username: janedoe
-Password: *******
-Email: jdoe@example.com
-WARNING: login credentials saved in /Users/jdoe/.dockercfg.
-Login Succeeded
-
-$ echo $(cat ~/.dockercfg)
-{ "https://index.docker.io/v1/": { "auth": "ZmFrZXBhc3N3b3JkMTIK", "email": "jdoe@example.com" } }
-
-$ cat ~/.dockercfg | base64
-eyAiaHR0cHM6Ly9pbmRleC5kb2NrZXIuaW8vdjEvIjogeyAiYXV0aCI6ICJabUZyWlhCaGMzTjNiM0prTVRJSyIsICJlbWFpbCI6ICJqZG9lQGV4YW1wbGUuY29tIiB9IH0K
-
-$ cat > /tmp/image-pull-secret.yaml <<EOF
-apiVersion: v1
-kind: Secret
-metadata:
-  name: myregistrykey
-data:
-  .dockercfg: eyAiaHR0cHM6Ly9pbmRleC5kb2NrZXIuaW8vdjEvIjogeyAiYXV0aCI6ICJabUZyWlhCaGMzTjNiM0prTVRJSyIsICJlbWFpbCI6ICJqZG9lQGV4YW1wbGUuY29tIiB9IH0K
-type: kubernetes.io/dockercfg
-EOF
-
-$ kubectl create -f ./image-pull-secret.yaml
-secrets/myregistrykey
-```
-
-Now, you can create pods which reference that secret by adding an `imagePullSecrets`
-section to a pod definition.
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: foo
-spec:
-  containers:
-    - name: foo
-      image: janedoe/awesomeapp:v1
-  imagePullSecrets:
-    - name: myregistrykey
-```
-
-## Helper containers
-
-[Pods](/{{page.version}}/docs/user-guide/pods) support running multiple containers co-located together. They can be used to host vertically integrated application stacks, but their primary motivation is to support auxiliary helper programs that assist the primary application. Typical examples are data pullers, data pushers, and proxies.
-
-Such containers typically need to communicate with one another, often through the file system. This can be achieved by mounting the same volume into both containers. An example of this pattern would be a web server with a [program that polls a git repository](http://releases.k8s.io/{{page.githubbranch}}/contrib/git-sync/) for new updates:
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx
-spec:
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      volumes:
-      - name: www-data
-        emptyDir: {}
-      containers:
-      - name: nginx
-        image: nginx
-        # This container reads from the www-data volume
-        volumeMounts:
-        - mountPath: /srv/www
-          name: www-data
-          readOnly: true
-      - name: git-monitor
-        image: myrepo/git-monitor
-        env:
-        - name: GIT_REPO
-          value: http://github.com/some/repo.git
-        # This container writes to the www-data volume
-        volumeMounts:
-        - mountPath: /data
-          name: www-data
-```
-
-More examples can be found in our [blog article](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns) and [presentation slides](http://www.slideshare.net/Docker/slideshare-burns).
-
-## Resource management
-
-Kubernetes's scheduler will place applications only where they have adequate CPU and memory, but it can only do so if it knows how much [resources they require](/{{page.version}}/docs/user-guide/compute-resources). The consequence of specifying too little CPU is that the containers could be starved of CPU if too many other containers were scheduled onto the same node. Similarly, containers could die unpredictably due to running out of memory if no memory were requested, which can be especially likely for large-memory applications.
-
-If no resource requirements are specified, a nominal amount of resources is assumed. (This default is applied via a [LimitRange](/{{page.version}}/docs/admin/limitrange/) for the default [Namespace](/{{page.version}}/docs/user-guide/namespaces). It can be viewed with `kubectl describe limitrange limits`.) You may explicitly specify the amount of resources required as follows:
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx
-spec:
-  replicas: 2
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        ports:
-        - containerPort: 80
-        resources:
-          limits:
-            # cpu units are cores
-            cpu: 500m
-            # memory units are bytes
-            memory: 64Mi
-          requests:
-            # cpu units are cores
-            cpu: 500m
-            # memory units are bytes
-            memory: 64Mi
-```
-
-The container will die due to OOM (out of memory) if it exceeds its specified limit, so specifying a value a little higher than expected generally improves reliability. By specifying request, pod is guaranteed to be able to use that much of resource when needed. See [Resource QoS](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/proposals/resource-qos.md) for the difference between resource limits and requests.
-
-If you're not sure how much resources to request, you can first launch the application without specifying resources, and use [resource usage monitoring](/{{page.version}}/docs/user-guide/monitoring) to determine appropriate values.
-
-## Liveness and readiness probes (aka health checks)
-
-Many applications running for long periods of time eventually transition to broken states, and cannot recover except by restarting them. Kubernetes provides [*liveness probes*](/{{page.version}}/docs/user-guide/pod-states/#container-probes) to detect and remedy such situations.
-
-A common way to probe an application is using HTTP, which can be specified as follows:
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx
-spec:
-  replicas: 2
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        ports:
-        - containerPort: 80
-        livenessProbe:
-          httpGet:
-            # Path to probe; should be cheap, but representative of typical behavior
-            path: /index.html
-            port: 80
-          initialDelaySeconds: 30
-          timeoutSeconds: 1
-```
-
-Other times, applications are only temporarily unable to serve, and will recover on their own. Typically in such cases you'd prefer not to kill the application, but don't want to send it requests, either, since the application won't respond correctly or at all. A common such scenario is loading large data or configuration files during application startup. Kubernetes provides *readiness probes* to detect and mitigate such situations. Readiness probes are configured similarly to liveness probes, just using the `readinessProbe` field. A pod with containers reporting that they are not ready will not receive traffic through Kubernetes [services](/{{page.version}}/docs/user-guide/connecting-applications).
-
-For more details (e.g., how to specify command-based probes), see the [example in the walkthrough](/{{page.version}}/docs/user-guide/walkthrough/k8s201/#health-checking), the [standalone example](/{{page.version}}/docs/user-guide/liveness/), and the [documentation](/{{page.version}}/docs/user-guide/pod-states/#container-probes).
-
-## Lifecycle hooks and termination notice
-
-Of course, nodes and applications may fail at any time, but many applications benefit from clean shutdown, such as to complete in-flight requests, when the termination of the application is deliberate. To support such cases, Kubernetes supports two kinds of notifications:
-
-* Kubernetes will send SIGTERM to applications, which can be handled in order to effect graceful termination. SIGKILL is sent a configurable number of seconds later if the application does not terminate sooner (defaults to 30 seconds, controlled by `spec.terminationGracePeriodSeconds`).
-* Kubernetes supports the (optional) specification of a [*pre-stop lifecycle hook*](/{{page.version}}/docs/user-guide/container-environment/#container-hooks), which will execute prior to sending SIGTERM.
-
-The specification of a pre-stop hook is similar to that of probes, but without the timing-related parameters. For example:
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: my-nginx
-spec:
-  replicas: 2
-  template:
-    metadata:
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        ports:
-        - containerPort: 80
-        lifecycle:
-          preStop:
-            exec:
-              # SIGTERM triggers a quick exit; gracefully terminate instead
-              command: ["/usr/sbin/nginx","-s","quit"]
-```
-
-## Termination message
-
-In order to achieve a reasonably high level of availability, especially for actively developed applications, it's important to debug failures quickly. Kubernetes can speed debugging by surfacing causes of fatal errors in a way that can be display using [`kubectl`](/{{page.version}}/docs/user-guide/kubectl/kubectl) or the [UI](/{{page.version}}/docs/user-guide/ui), in addition to general [log collection](/{{page.version}}/docs/user-guide/logging). It is possible to specify a `terminationMessagePath` where a container will write its 'death rattle'?, such as assertion failure messages, stack traces, exceptions, and so on. The default path is `/dev/termination-log`.
-
-Here is a toy example:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: pod-w-message
-spec:
-  containers:
-  - name: messager
-    image: "ubuntu:14.04"
-    command: ["/bin/sh","-c"]
-    args: ["sleep 60 && /bin/echo Sleep expired > /dev/termination-log"]
-```
-
-The message is recorded along with the other state of the last (i.e., most recent) termination:
-
-```shell{% raw %}
-$ kubectl create -f ./pod.yaml
-pods/pod-w-message
-$ sleep 70
-$ kubectl get pods/pod-w-message -o go-template="{{range .status.containerStatuses}}{{.lastState.terminated.message}}{{end}}"
-Sleep expired
-$ kubectl get pods/pod-w-message -o go-template="{{range .status.containerStatuses}}{{.lastState.terminated.exitCode}}{{end}}"
-0
-{% endraw %}```
-
-## What's next?
-
-[Learn more about managing deployments.](/{{page.version}}/docs/user-guide/managing-deployments)
diff --git a/v1.2/docs/user-guide/replication.yaml b/v1.2/docs/user-guide/replication.yaml
deleted file mode 100644
index 6eff0b9b57..0000000000
--- a/v1.2/docs/user-guide/replication.yaml
+++ /dev/null
@@ -1,19 +0,0 @@
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: nginx
-spec:
-  replicas: 3
-  selector:
-    app: nginx
-  template:
-    metadata:
-      name: nginx
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        ports:
-        - containerPort: 80
diff --git a/v1.2/docs/user-guide/resourcequota/index.md b/v1.2/docs/user-guide/resourcequota/index.md
deleted file mode 100644
index e2de1b99b0..0000000000
--- a/v1.2/docs/user-guide/resourcequota/index.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
----
-
-This page has been moved to [here](/{{page.version}}/docs/admin/resourcequota/)
-
-
diff --git a/v1.2/docs/user-guide/secrets/index.md b/v1.2/docs/user-guide/secrets/index.md
deleted file mode 100644
index aa4b229dfd..0000000000
--- a/v1.2/docs/user-guide/secrets/index.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
----
-
-Following this example, you will create a secret and a [pod](/{{page.version}}/docs/user-guide/pods/) that consumes that secret in a [volume](/{{page.version}}/docs/user-guide/volumes/). See [Secrets design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/secrets.md) for more information.
-
-## Step Zero: Prerequisites
-
-This example assumes you have a Kubernetes cluster installed and running, and that you have
-installed the `kubectl` command line tool somewhere in your path. Please see the [getting
-started](/{{page.version}}/docs/getting-started-guides/) for installation instructions for your platform.
-
-## Step One: Create the secret
-
-A secret contains a set of named byte arrays.
-
-Use the [`examples/secrets/secret.yaml`](/{{page.version}}/docs/user-guide/secrets/secret.yaml) file to create a secret:
-
-```shell
-$ kubectl create -f docs/user-guide/secrets/secret.yaml
-```
-
-You can use `kubectl` to see information about the secret:
-
-```shell
-$ kubectl get secrets
-NAME          TYPE      DATA
-test-secret   Opaque    2
-
-$ kubectl describe secret test-secret
-Name:          test-secret
-Labels:        <none>
-Annotations:   <none>
-
-Type:   Opaque
-
-Data
-====
-data-1: 9 bytes
-data-2: 11 bytes
-```
-
-## Step Two: Create a pod that consumes a secret
-
-Pods consume secrets in volumes.  Now that you have created a secret, you can create a pod that
-consumes it.
-
-Use the [`examples/secrets/secret-pod.yaml`](/{{page.version}}/docs/user-guide/secrets/secret-pod.yaml) file to create a Pod that consumes the secret.
-
-```shell
-$ kubectl create -f docs/user-guide/secrets/secret-pod.yaml
-```
-
-This pod runs a binary that displays the content of one of the pieces of secret data in the secret
-volume:
-
-```shell
-$ kubectl logs secret-test-pod
-2015-04-29T21:17:24.712206409Z content of file "/etc/secret-volume/data-1": value-1
-```
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/secrets/secret-pod.yaml b/v1.2/docs/user-guide/secrets/secret-pod.yaml
deleted file mode 100644
index f5b73a01ed..0000000000
--- a/v1.2/docs/user-guide/secrets/secret-pod.yaml
+++ /dev/null
@@ -1,18 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: secret-test-pod
-spec:
-  containers:
-    - name: test-container
-      image: kubernetes/mounttest:0.1
-      command: [ "/mt", "--file_content=/etc/secret-volume/data-1" ]
-      volumeMounts:
-          # name must match the volume name below
-          - name: secret-volume
-            mountPath: /etc/secret-volume
-  volumes:
-    - name: secret-volume
-      secret:
-        secretName: test-secret
-  restartPolicy: Never
diff --git a/v1.2/docs/user-guide/secrets/secret.yaml b/v1.2/docs/user-guide/secrets/secret.yaml
deleted file mode 100644
index 4a547dc522..0000000000
--- a/v1.2/docs/user-guide/secrets/secret.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-apiVersion: v1
-kind: Secret
-metadata:
-  name: test-secret
-data:
-  data-1: dmFsdWUtMQ0K
-  data-2: dmFsdWUtMg0KDQo=
diff --git a/v1.2/docs/user-guide/security-context.md b/v1.2/docs/user-guide/security-context.md
deleted file mode 100644
index 434ae29d38..0000000000
--- a/v1.2/docs/user-guide/security-context.md
+++ /dev/null
@@ -1,4 +0,0 @@
----
----
-
-A security context defines the operating system security settings (uid, gid, capabilities, SELinux role, etc..) applied to a container. See [security context design](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/security_context.md) for more details.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/services-firewalls.md b/v1.2/docs/user-guide/services-firewalls.md
deleted file mode 100644
index b7f48116cd..0000000000
--- a/v1.2/docs/user-guide/services-firewalls.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
----
-
-Many cloud providers (e.g. Google Compute Engine) define firewalls that help prevent inadvertent
-exposure to the internet.  When exposing a service to the external world, you may need to open up
-one or more ports in these firewalls to serve traffic.  This document describes this process, as
-well as any provider specific details that may be necessary.
-
-### Google Compute Engine
-
-When using a Service with `spec.type: LoadBalancer`, the firewall will be
-opened automatically.  When using `spec.type: NodePort`, however, the firewall
-is *not* opened by default.
-
-Google Compute Engine firewalls are documented [elsewhere](https://cloud.google.com/compute/docs/networking#firewalls_1).
-
-You can add a firewall with the `gcloud` command line tool:
-
-```shell
-$ gcloud compute firewall-rules create my-rule --allow=tcp:<port>
-```
-
-**Note**
-There is one important security note when using firewalls on Google Compute Engine:
-
-as of Kubernetes v1.0.0, GCE firewalls are defined per-vm, rather than per-ip
-address.  This means that when you open a firewall for a service's ports,
-anything that serves on that port on that VM's host IP address may potentially
-serve traffic.  Note that this is not a problem for other Kubernetes services,
-as they listen on IP addresses that are different than the host node's external
-IP address.
-
-Consider:
-
-   * You create a Service with an external load balancer (IP Address 1.2.3.4)
-     and port 80
-   * You open the firewall for port 80 for all nodes in your cluster, so that
-     the external Service actually can deliver packets to your Service
-   * You start an nginx server, running on port 80 on the host virtual machine
-     (IP Address 2.3.4.5).  This nginx is **also** exposed to the internet on
-     the VM's external IP address.
-
-Consequently, please be careful when opening firewalls in Google Compute Engine
-or Google Container Engine.  You may accidentally be exposing other services to
-the wilds of the internet.
-
-This will be fixed in an upcoming release of Kubernetes.
-
-### Other cloud providers
-
-Coming soon.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/sharing-clusters.md b/v1.2/docs/user-guide/sharing-clusters.md
deleted file mode 100644
index 01d96b063e..0000000000
--- a/v1.2/docs/user-guide/sharing-clusters.md
+++ /dev/null
@@ -1,119 +0,0 @@
----
----
-
-Client access to a running Kubernetes cluster can be shared by copying
-the `kubectl` client config bundle ([kubeconfig](/{{page.version}}/docs/user-guide/kubeconfig-file)).
-This config bundle lives in `$HOME/.kube/config`, and is generated
-by `cluster/kube-up.sh`. Sample steps for sharing `kubeconfig` below.
-
-**1. Create a cluster**
-
-```shell
-$ cluster/kube-up.sh
-```
-
-**2. Copy `kubeconfig` to new host**
-
-```shell
-$ scp $HOME/.kube/config user@remotehost:/path/to/.kube/config
-```
-
-**3. On new host, make copied `config` available to `kubectl`**
-
-* Option A: copy to default location
-
-```shell
-$ mv /path/to/.kube/config $HOME/.kube/config
-```
-
-* Option B: copy to working directory (from which kubectl is run)
-
-```shell
-$ mv /path/to/.kube/config $PWD
-```
-
-* Option C: manually pass `kubeconfig` location to `kubectl`
-
-```shell
-# via environment variable
-$ export KUBECONFIG=/path/to/.kube/config
-
-# via commandline flag
-$ kubectl ... --kubeconfig=/path/to/.kube/config
-```
-
-## Manually Generating `kubeconfig`
-
-`kubeconfig` is generated by `kube-up` but you can generate your own
-using (any desired subset of) the following commands.
-
-```shell
-# create kubeconfig entry
-$ kubectl config set-cluster $CLUSTER_NICK \
-    --server=https://1.1.1.1 \
-    --certificate-authority=/path/to/apiserver/ca_file \
-    --embed-certs=true \
-    # Or if tls not needed, replace --certificate-authority and --embed-certs with
-    --insecure-skip-tls-verify=true \
-    --kubeconfig=/path/to/standalone/.kube/config
-
-# create user entry
-$ kubectl config set-credentials $USER_NICK \
-    # bearer token credentials, generated on kube master
-    --token=$token \
-    # use either username|password or token, not both
-    --username=$username \
-    --password=$password \
-    --client-certificate=/path/to/crt_file \
-    --client-key=/path/to/key_file \
-    --embed-certs=true \
-    --kubeconfig=/path/to/standalone/.kube/config
-
-# create context entry
-$ kubectl config set-context $CONTEXT_NAME --cluster=$CLUSTER_NICKNAME --user=$USER_NICK
-```
-
-Notes:
-
-* The `--embed-certs` flag is needed to generate a standalone
-`kubeconfig`, that will work as-is on another host.
-* `--kubeconfig` is both the preferred file to load config from and the file to
-save config too. In the above commands the `--kubeconfig` file could be
-omitted if you first run
-
-```shell
-$ export KUBECONFIG=/path/to/standalone/.kube/config
-```
-
-* The ca_file, key_file, and cert_file referenced above are generated on the
-kube master at cluster turnup. They can be found on the master under
-`/srv/kubernetes`. Bearer token/basic auth are also generated on the kube master.
-
-For more details on `kubeconfig` see [kubeconfig-file.md](/{{page.version}}/docs/user-guide/kubeconfig-file),
-and/or run `kubectl config -h`.
-
-## Merging `kubeconfig` Example
-
-`kubectl` loads and merges config from the following locations (in order)
-
-1. `--kubeconfig=/path/to/.kube/config` command line flag
-2. `KUBECONFIG=/path/to/.kube/config` env variable
-3. `$PWD/.kube/config`
-4. `$HOME/.kube/config`
-
-If you create clusters A, B on host1, and clusters C, D on host2, you can
-make all four clusters available on both hosts by running
-
-```shell
-# on host2, copy host1's default kubeconfig, and merge it from env
-$ scp host1:/path/to/home1/.kube/config /path/to/other/.kube/config
-
-$ export $KUBECONFIG=/path/to/other/.kube/config
-
-# on host1, copy host2's default kubeconfig and merge it from env
-$ scp host2:/path/to/home2/.kube/config /path/to/other/.kube/config
-
-$ export $KUBECONFIG=/path/to/other/.kube/config
-```
-
-Detailed examples and explanation of `kubeconfig` loading/merging rules can be found in [kubeconfig-file](/{{page.version}}/docs/user-guide/kubeconfig-file).
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/simple-nginx.md b/v1.2/docs/user-guide/simple-nginx.md
deleted file mode 100644
index 225b056429..0000000000
--- a/v1.2/docs/user-guide/simple-nginx.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
----
-
-Ok, you've run one of the [getting started guides](/{{page.version}}/docs/getting-started-guides/) and you have
-successfully turned up a Kubernetes cluster.  Now what?  This guide will help you get oriented
-to Kubernetes and running your first containers on the cluster.
-
-### Running a container (simple version)
-
-From this point onwards, it is assumed that `kubectl` is on your path from one of the getting started guides.
-
-The [`kubectl run`](/{{page.version}}/docs/user-guide/kubectl/kubectl_run) line below will create two [nginx](https://registry.hub.docker.com/_/nginx/) [pods](/{{page.version}}/docs/user-guide/pods) listening on port 80. It will also create a [replication controller](/{{page.version}}/docs/user-guide/replication-controller) named `my-nginx` to ensure that there are always two pods running.
-
-```shell
-kubectl run my-nginx --image=nginx --replicas=2 --port=80
-```
-
-Once the pods are created, you can list them to see what is up and running:
-
-```shell
-kubectl get pods
-```
-
-You can also see the replication controller that was created:
-
-```shell
-kubectl get rc
-```
-
-To stop the two replicated containers, stop the replication controller:
-
-```shell
-kubectl stop rc my-nginx
-```
-
-### Exposing your pods to the internet.
-
-On some platforms (for example Google Compute Engine) the kubectl command can integrate with your cloud provider to add a [public IP address](/{{page.version}}/docs/user-guide/services/#external-services) for the pods,
-to do this run:
-
-```shell
-kubectl expose rc my-nginx --port=80 --type=LoadBalancer
-```
-
-This should print the service that has been created, and map an external IP address to the service. Where to find this external IP address will depend on the environment you run in.  For instance, for Google Compute Engine the external IP address is listed as part of the newly created service and can be retrieved by running
-
-```shell
-kubectl get services
-```
-
-In order to access your nginx landing page, you also have to make sure that traffic from external IPs is allowed. Do this by opening a firewall to allow traffic on port 80.
-
-### Next: Configuration files
-
-Most people will eventually want to use declarative configuration files for creating/modifying their applications.  A [simplified introduction](/{{page.version}}/docs/user-guide/simple-yaml)
-is given in a different document.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/simple-yaml.md b/v1.2/docs/user-guide/simple-yaml.md
deleted file mode 100644
index 165e7464b3..0000000000
--- a/v1.2/docs/user-guide/simple-yaml.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
----
-
-In addition to the imperative style commands described [elsewhere](/{{page.version}}/docs/user-guide/simple-nginx), Kubernetes
-supports declarative YAML or JSON configuration files.  Often times config files are preferable
-to imperative commands, since they can be checked into version control and changes to the files
-can be code reviewed, producing a more robust, reliable and archival system.
-
-### Running a container from a pod configuration file
-
-```shell
-$ cd kubernetes
-$ kubectl create -f ./pod.yaml
-```
-
-Where pod.yaml contains something like:
-
-<!-- BEGIN MUNGE: EXAMPLE pod.yaml -->
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-  labels:
-    app: nginx
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    ports:
-    - containerPort: 80
-```
-
-[Download example](/{{page.version}}/docs/user-guide/pod.yaml)
-<!-- END MUNGE: EXAMPLE pod.yaml -->
-
-You can see your cluster's pods:
-
-```shell
-$ kubectl get pods
-```
-
-and delete the pod you just created:
-
-```shell
-$ kubectl delete pods nginx
-```
-
-### Running a replicated set of containers from a configuration file
-
-To run replicated containers, you need a [Replication Controller](/{{page.version}}/docs/user-guide/replication-controller).
-A replication controller is responsible for ensuring that a specific number of pods exist in the
-cluster.
-
-```shell
-$ cd kubernetes
-$ kubectl create -f ./replication.yaml
-```
-
-Where `replication.yaml` contains:
-
-<!-- BEGIN MUNGE: EXAMPLE replication.yaml -->
-
-```yaml
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: nginx
-spec:
-  replicas: 3
-  selector:
-    app: nginx
-  template:
-    metadata:
-      name: nginx
-      labels:
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        ports:
-        - containerPort: 80
-```
-
-[Download example](/{{page.version}}/docs/user-guide/replication.yaml)
-<!-- END MUNGE: EXAMPLE replication.yaml -->
-
-To delete the replication controller (and the pods it created):
-
-```shell
-$ kubectl delete rc nginx
-```
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/ui.md b/v1.2/docs/user-guide/ui.md
deleted file mode 100644
index 011b4501d4..0000000000
--- a/v1.2/docs/user-guide/ui.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
----
-
-Kubernetes has a web-based user interface that displays the current cluster state graphically.
-
-## Accessing the UI
-
-By default, the Kubernetes UI is deployed as a cluster addon. To access it, visit `https://<kubernetes-master>/ui`, which redirects to `https://<kubernetes-master>/api/v1/proxy/namespaces/kube-system/services/kube-ui/#/dashboard/`.
-
-If you find that you're not able to access the UI, it may be because the kube-ui service has not been started on your cluster. In that case, you can start it manually with:
-
-```shell
-kubectl create -f cluster/addons/kube-ui/kube-ui-rc.yaml --namespace=kube-system
-kubectl create -f cluster/addons/kube-ui/kube-ui-svc.yaml --namespace=kube-system
-```
-
-Normally, this should be taken care of automatically by the [`kube-addons.sh`](http://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/salt/kube-addons/kube-addons.sh) script that runs on the master.
-
-## Using the UI
-
-The Kubernetes UI can be used to introspect your current cluster, such as checking how resources are used, or looking at error messages. You cannot, however, use the UI to modify your cluster.
-
-### Node Resource Usage
-
-After accessing Kubernetes UI, you'll see a homepage dynamically listing out all nodes in your current cluster, with related information including internal IP addresses, CPU usage, memory usage, and file systems usage.
-
-![Kubernetes UI home page](/images/docs/k8s-ui-overview.png)
-
-### Dashboard Views
-
-Click on the "Views" button in the top-right of the page to see other views available, which include: Explore, Pods, Nodes, Replication Controllers, Services, and Events.
-
-#### Explore View
-
-The "Explore" view allows your to see the pods, replication controllers, and services in current cluster easily.
-
-![Kubernetes UI Explore View](/images/docs/k8s-ui-explore.png)
-
-The "Group by" dropdown list allows you to group these resources by a number of factors, such as type, name, host, etc.
-
-![Kubernetes UI Explore View - Group by](/images/docs/k8s-ui-explore-groupby.png)
-
-You can also create filters by clicking on the down triangle of any listed resource instances and choose which filters you want to add.
-
-![Kubernetes UI Explore View - Filter](/images/docs/k8s-ui-explore-filter.png)
-
-To see more details of each resource instance, simply click on it.
-
-![Kubernetes UI - Pod](/images/docs/k8s-ui-explore-poddetail.png)
-
-### Other Views
-
-Other views (Pods, Nodes, Replication Controllers, Services, and Events) simply list information about each type of resource. You can also click on any instance for more details.
-
-![Kubernetes UI - Nodes](/images/docs/k8s-ui-nodes.png)
-
-## More Information
-
-For more information, see the [Kubernetes UI development document](http://releases.k8s.io/{{page.githubbranch}}/www/README.md) in the www directory.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/update-demo/build-images.sh b/v1.2/docs/user-guide/update-demo/build-images.sh
deleted file mode 100755
index 63c0fe9298..0000000000
--- a/v1.2/docs/user-guide/update-demo/build-images.sh
+++ /dev/null
@@ -1,30 +0,0 @@
-#!/bin/bash
-
-# Copyright 2014 The Kubernetes Authors All rights reserved.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# This script will build and push the images necessary for the demo.
-
-set -o errexit
-set -o nounset
-set -o pipefail
-
-DOCKER_HUB_USER=${DOCKER_HUB_USER:-kubernetes}
-
-set -x
-
-docker build -t "${DOCKER_HUB_USER}/update-demo:kitten" images/kitten
-docker build -t "${DOCKER_HUB_USER}/update-demo:nautilus" images/nautilus
-
-docker push "${DOCKER_HUB_USER}/update-demo"
diff --git a/v1.2/docs/user-guide/update-demo/images/kitten/Dockerfile b/v1.2/docs/user-guide/update-demo/images/kitten/Dockerfile
deleted file mode 100644
index b053138b35..0000000000
--- a/v1.2/docs/user-guide/update-demo/images/kitten/Dockerfile
+++ /dev/null
@@ -1,17 +0,0 @@
-# Copyright 2014 Google Inc. All rights reserved.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-FROM kubernetes/test-webserver
-COPY html/kitten.jpg kitten.jpg
-COPY html/data.json data.json
diff --git a/v1.2/docs/user-guide/update-demo/images/kitten/html/data.json b/v1.2/docs/user-guide/update-demo/images/kitten/html/data.json
deleted file mode 100644
index 0be61a42b3..0000000000
--- a/v1.2/docs/user-guide/update-demo/images/kitten/html/data.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "image": "kitten.jpg"
-}
diff --git a/v1.2/docs/user-guide/update-demo/images/kitten/html/kitten.jpg b/v1.2/docs/user-guide/update-demo/images/kitten/html/kitten.jpg
deleted file mode 100644
index a382bf16ac..0000000000
Binary files a/v1.2/docs/user-guide/update-demo/images/kitten/html/kitten.jpg and /dev/null differ
diff --git a/v1.2/docs/user-guide/update-demo/images/nautilus/Dockerfile b/v1.2/docs/user-guide/update-demo/images/nautilus/Dockerfile
deleted file mode 100644
index 2904a10791..0000000000
--- a/v1.2/docs/user-guide/update-demo/images/nautilus/Dockerfile
+++ /dev/null
@@ -1,17 +0,0 @@
-# Copyright 2014 Google Inc. All rights reserved.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-FROM kubernetes/test-webserver
-COPY html/nautilus.jpg nautilus.jpg
-COPY html/data.json data.json
diff --git a/v1.2/docs/user-guide/update-demo/images/nautilus/html/data.json b/v1.2/docs/user-guide/update-demo/images/nautilus/html/data.json
deleted file mode 100644
index 2debee09a9..0000000000
--- a/v1.2/docs/user-guide/update-demo/images/nautilus/html/data.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "image": "nautilus.jpg"
-}
diff --git a/v1.2/docs/user-guide/update-demo/images/nautilus/html/nautilus.jpg b/v1.2/docs/user-guide/update-demo/images/nautilus/html/nautilus.jpg
deleted file mode 100644
index 544d2bd471..0000000000
Binary files a/v1.2/docs/user-guide/update-demo/images/nautilus/html/nautilus.jpg and /dev/null differ
diff --git a/v1.2/docs/user-guide/update-demo/kitten-rc.yaml b/v1.2/docs/user-guide/update-demo/kitten-rc.yaml
deleted file mode 100644
index 91f1aa06c3..0000000000
--- a/v1.2/docs/user-guide/update-demo/kitten-rc.yaml
+++ /dev/null
@@ -1,20 +0,0 @@
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: update-demo-kitten
-spec:
-  selector:
-    name: update-demo
-    version: kitten
-  template:
-    metadata:
-      labels:
-        name: update-demo
-        version: kitten
-    spec:
-      containers:
-      - image: gcr.io/google_containers/update-demo:kitten
-        name: update-demo
-        ports:
-        - containerPort: 80
-          protocol: TCP
diff --git a/v1.2/docs/user-guide/update-demo/local/LICENSE.angular b/v1.2/docs/user-guide/update-demo/local/LICENSE.angular
deleted file mode 100644
index 020f87acd2..0000000000
--- a/v1.2/docs/user-guide/update-demo/local/LICENSE.angular
+++ /dev/null
@@ -1,21 +0,0 @@
-The MIT License
-
-Copyright (c) 2010-2014 Google, Inc. http://angularjs.org
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
diff --git a/v1.2/docs/user-guide/update-demo/local/angular.min.js b/v1.2/docs/user-guide/update-demo/local/angular.min.js
deleted file mode 100644
index 43f31f6708..0000000000
--- a/v1.2/docs/user-guide/update-demo/local/angular.min.js
+++ /dev/null
@@ -1,210 +0,0 @@
-/*
- AngularJS v1.2.16
- (c) 2010-2014 Google, Inc. http://angularjs.org
- License: MIT
-*/
-(function(O,U,s){'use strict';function t(b){return function(){var a=arguments[0],c,a="["+(b?b+":":"")+a+"] http://errors.angularjs.org/1.2.16/"+(b?b+"/":"")+a;for(c=1;c<arguments.length;c++)a=a+(1==c?"?":"&")+"p"+(c-1)+"="+encodeURIComponent("function"==typeof arguments[c]?arguments[c].toString().replace(/ \{[\s\S]*$/,""):"undefined"==typeof arguments[c]?"undefined":"string"!=typeof arguments[c]?JSON.stringify(arguments[c]):arguments[c]);return Error(a)}}function ab(b){if(null==b||Ca(b))return!1;
-var a=b.length;return 1===b.nodeType&&a?!0:w(b)||M(b)||0===a||"number"===typeof a&&0<a&&a-1 in b}function q(b,a,c){var d;if(b)if(P(b))for(d in b)"prototype"==d||("length"==d||"name"==d||b.hasOwnProperty&&!b.hasOwnProperty(d))||a.call(c,b[d],d);else if(b.forEach&&b.forEach!==q)b.forEach(a,c);else if(ab(b))for(d=0;d<b.length;d++)a.call(c,b[d],d);else for(d in b)b.hasOwnProperty(d)&&a.call(c,b[d],d);return b}function Qb(b){var a=[],c;for(c in b)b.hasOwnProperty(c)&&a.push(c);return a.sort()}function Sc(b,
-a,c){for(var d=Qb(b),e=0;e<d.length;e++)a.call(c,b[d[e]],d[e]);return d}function Rb(b){return function(a,c){b(c,a)}}function bb(){for(var b=ka.length,a;b;){b--;a=ka[b].charCodeAt(0);if(57==a)return ka[b]="A",ka.join("");if(90==a)ka[b]="0";else return ka[b]=String.fromCharCode(a+1),ka.join("")}ka.unshift("0");return ka.join("")}function Sb(b,a){a?b.$$hashKey=a:delete b.$$hashKey}function D(b){var a=b.$$hashKey;q(arguments,function(a){a!==b&&q(a,function(a,c){b[c]=a})});Sb(b,a);return b}function Y(b){return parseInt(b,
-10)}function Tb(b,a){return D(new (D(function(){},{prototype:b})),a)}function C(){}function Da(b){return b}function aa(b){return function(){return b}}function E(b){return"undefined"===typeof b}function B(b){return"undefined"!==typeof b}function X(b){return null!=b&&"object"===typeof b}function w(b){return"string"===typeof b}function vb(b){return"number"===typeof b}function Na(b){return"[object Date]"===wa.call(b)}function M(b){return"[object Array]"===wa.call(b)}function P(b){return"function"===typeof b}
-function cb(b){return"[object RegExp]"===wa.call(b)}function Ca(b){return b&&b.document&&b.location&&b.alert&&b.setInterval}function Tc(b){return!(!b||!(b.nodeName||b.prop&&b.attr&&b.find))}function Uc(b,a,c){var d=[];q(b,function(b,g,f){d.push(a.call(c,b,g,f))});return d}function db(b,a){if(b.indexOf)return b.indexOf(a);for(var c=0;c<b.length;c++)if(a===b[c])return c;return-1}function Oa(b,a){var c=db(b,a);0<=c&&b.splice(c,1);return a}function ba(b,a){if(Ca(b)||b&&b.$evalAsync&&b.$watch)throw Pa("cpws");
-if(a){if(b===a)throw Pa("cpi");if(M(b))for(var c=a.length=0;c<b.length;c++)a.push(ba(b[c]));else{c=a.$$hashKey;q(a,function(b,c){delete a[c]});for(var d in b)a[d]=ba(b[d]);Sb(a,c)}}else(a=b)&&(M(b)?a=ba(b,[]):Na(b)?a=new Date(b.getTime()):cb(b)?a=RegExp(b.source):X(b)&&(a=ba(b,{})));return a}function Ub(b,a){a=a||{};for(var c in b)!b.hasOwnProperty(c)||"$"===c.charAt(0)&&"$"===c.charAt(1)||(a[c]=b[c]);return a}function xa(b,a){if(b===a)return!0;if(null===b||null===a)return!1;if(b!==b&&a!==a)return!0;
-var c=typeof b,d;if(c==typeof a&&"object"==c)if(M(b)){if(!M(a))return!1;if((c=b.length)==a.length){for(d=0;d<c;d++)if(!xa(b[d],a[d]))return!1;return!0}}else{if(Na(b))return Na(a)&&b.getTime()==a.getTime();if(cb(b)&&cb(a))return b.toString()==a.toString();if(b&&b.$evalAsync&&b.$watch||a&&a.$evalAsync&&a.$watch||Ca(b)||Ca(a)||M(a))return!1;c={};for(d in b)if("$"!==d.charAt(0)&&!P(b[d])){if(!xa(b[d],a[d]))return!1;c[d]=!0}for(d in a)if(!c.hasOwnProperty(d)&&"$"!==d.charAt(0)&&a[d]!==s&&!P(a[d]))return!1;
-return!0}return!1}function Vb(){return U.securityPolicy&&U.securityPolicy.isActive||U.querySelector&&!(!U.querySelector("[ng-csp]")&&!U.querySelector("[data-ng-csp]"))}function eb(b,a){var c=2<arguments.length?ya.call(arguments,2):[];return!P(a)||a instanceof RegExp?a:c.length?function(){return arguments.length?a.apply(b,c.concat(ya.call(arguments,0))):a.apply(b,c)}:function(){return arguments.length?a.apply(b,arguments):a.call(b)}}function Vc(b,a){var c=a;"string"===typeof b&&"$"===b.charAt(0)?c=
-s:Ca(a)?c="$WINDOW":a&&U===a?c="$DOCUMENT":a&&(a.$evalAsync&&a.$watch)&&(c="$SCOPE");return c}function qa(b,a){return"undefined"===typeof b?s:JSON.stringify(b,Vc,a?"  ":null)}function Wb(b){return w(b)?JSON.parse(b):b}function Qa(b){"function"===typeof b?b=!0:b&&0!==b.length?(b=K(""+b),b=!("f"==b||"0"==b||"false"==b||"no"==b||"n"==b||"[]"==b)):b=!1;return b}function ha(b){b=y(b).clone();try{b.empty()}catch(a){}var c=y("<div>").append(b).html();try{return 3===b[0].nodeType?K(c):c.match(/^(<[^>]+>)/)[1].replace(/^<([\w\-]+)/,
-function(a,b){return"<"+K(b)})}catch(d){return K(c)}}function Xb(b){try{return decodeURIComponent(b)}catch(a){}}function Yb(b){var a={},c,d;q((b||"").split("&"),function(b){b&&(c=b.split("="),d=Xb(c[0]),B(d)&&(b=B(c[1])?Xb(c[1]):!0,a[d]?M(a[d])?a[d].push(b):a[d]=[a[d],b]:a[d]=b))});return a}function Zb(b){var a=[];q(b,function(b,d){M(b)?q(b,function(b){a.push(za(d,!0)+(!0===b?"":"="+za(b,!0)))}):a.push(za(d,!0)+(!0===b?"":"="+za(b,!0)))});return a.length?a.join("&"):""}function wb(b){return za(b,
-!0).replace(/%26/gi,"&").replace(/%3D/gi,"=").replace(/%2B/gi,"+")}function za(b,a){return encodeURIComponent(b).replace(/%40/gi,"@").replace(/%3A/gi,":").replace(/%24/g,"$").replace(/%2C/gi,",").replace(/%20/g,a?"%20":"+")}function Wc(b,a){function c(a){a&&d.push(a)}var d=[b],e,g,f=["ng:app","ng-app","x-ng-app","data-ng-app"],h=/\sng[:\-]app(:\s*([\w\d_]+);?)?\s/;q(f,function(a){f[a]=!0;c(U.getElementById(a));a=a.replace(":","\\:");b.querySelectorAll&&(q(b.querySelectorAll("."+a),c),q(b.querySelectorAll("."+
-a+"\\:"),c),q(b.querySelectorAll("["+a+"]"),c))});q(d,function(a){if(!e){var b=h.exec(" "+a.className+" ");b?(e=a,g=(b[2]||"").replace(/\s+/g,",")):q(a.attributes,function(b){!e&&f[b.name]&&(e=a,g=b.value)})}});e&&a(e,g?[g]:[])}function $b(b,a){var c=function(){b=y(b);if(b.injector()){var c=b[0]===U?"document":ha(b);throw Pa("btstrpd",c);}a=a||[];a.unshift(["$provide",function(a){a.value("$rootElement",b)}]);a.unshift("ng");c=ac(a);c.invoke(["$rootScope","$rootElement","$compile","$injector","$animate",
-function(a,b,c,d,e){a.$apply(function(){b.data("$injector",d);c(b)(a)})}]);return c},d=/^NG_DEFER_BOOTSTRAP!/;if(O&&!d.test(O.name))return c();O.name=O.name.replace(d,"");Ea.resumeBootstrap=function(b){q(b,function(b){a.push(b)});c()}}function fb(b,a){a=a||"_";return b.replace(Xc,function(b,d){return(d?a:"")+b.toLowerCase()})}function xb(b,a,c){if(!b)throw Pa("areq",a||"?",c||"required");return b}function Ra(b,a,c){c&&M(b)&&(b=b[b.length-1]);xb(P(b),a,"not a function, got "+(b&&"object"==typeof b?
-b.constructor.name||"Object":typeof b));return b}function Aa(b,a){if("hasOwnProperty"===b)throw Pa("badname",a);}function bc(b,a,c){if(!a)return b;a=a.split(".");for(var d,e=b,g=a.length,f=0;f<g;f++)d=a[f],b&&(b=(e=b)[d]);return!c&&P(b)?eb(e,b):b}function yb(b){var a=b[0];b=b[b.length-1];if(a===b)return y(a);var c=[a];do{a=a.nextSibling;if(!a)break;c.push(a)}while(a!==b);return y(c)}function Yc(b){var a=t("$injector"),c=t("ng");b=b.angular||(b.angular={});b.$$minErr=b.$$minErr||t;return b.module||
-(b.module=function(){var b={};return function(e,g,f){if("hasOwnProperty"===e)throw c("badname","module");g&&b.hasOwnProperty(e)&&(b[e]=null);return b[e]||(b[e]=function(){function b(a,d,e){return function(){c[e||"push"]([a,d,arguments]);return n}}if(!g)throw a("nomod",e);var c=[],d=[],m=b("$injector","invoke"),n={_invokeQueue:c,_runBlocks:d,requires:g,name:e,provider:b("$provide","provider"),factory:b("$provide","factory"),service:b("$provide","service"),value:b("$provide","value"),constant:b("$provide",
-"constant","unshift"),animation:b("$animateProvider","register"),filter:b("$filterProvider","register"),controller:b("$controllerProvider","register"),directive:b("$compileProvider","directive"),config:m,run:function(a){d.push(a);return this}};f&&m(f);return n}())}}())}function Zc(b){D(b,{bootstrap:$b,copy:ba,extend:D,equals:xa,element:y,forEach:q,injector:ac,noop:C,bind:eb,toJson:qa,fromJson:Wb,identity:Da,isUndefined:E,isDefined:B,isString:w,isFunction:P,isObject:X,isNumber:vb,isElement:Tc,isArray:M,
-version:$c,isDate:Na,lowercase:K,uppercase:Fa,callbacks:{counter:0},$$minErr:t,$$csp:Vb});Sa=Yc(O);try{Sa("ngLocale")}catch(a){Sa("ngLocale",[]).provider("$locale",ad)}Sa("ng",["ngLocale"],["$provide",function(a){a.provider({$$sanitizeUri:bd});a.provider("$compile",cc).directive({a:cd,input:dc,textarea:dc,form:dd,script:ed,select:fd,style:gd,option:hd,ngBind:id,ngBindHtml:jd,ngBindTemplate:kd,ngClass:ld,ngClassEven:md,ngClassOdd:nd,ngCloak:od,ngController:pd,ngForm:qd,ngHide:rd,ngIf:sd,ngInclude:td,
-ngInit:ud,ngNonBindable:vd,ngPluralize:wd,ngRepeat:xd,ngShow:yd,ngStyle:zd,ngSwitch:Ad,ngSwitchWhen:Bd,ngSwitchDefault:Cd,ngOptions:Dd,ngTransclude:Ed,ngModel:Fd,ngList:Gd,ngChange:Hd,required:ec,ngRequired:ec,ngValue:Id}).directive({ngInclude:Jd}).directive(zb).directive(fc);a.provider({$anchorScroll:Kd,$animate:Ld,$browser:Md,$cacheFactory:Nd,$controller:Od,$document:Pd,$exceptionHandler:Qd,$filter:gc,$interpolate:Rd,$interval:Sd,$http:Td,$httpBackend:Ud,$location:Vd,$log:Wd,$parse:Xd,$rootScope:Yd,
-$q:Zd,$sce:$d,$sceDelegate:ae,$sniffer:be,$templateCache:ce,$timeout:de,$window:ee,$$rAF:fe,$$asyncCallback:ge})}])}function Ta(b){return b.replace(he,function(a,b,d,e){return e?d.toUpperCase():d}).replace(ie,"Moz$1")}function Ab(b,a,c,d){function e(b){var e=c&&b?[this.filter(b)]:[this],l=a,k,m,n,p,r,z;if(!d||null!=b)for(;e.length;)for(k=e.shift(),m=0,n=k.length;m<n;m++)for(p=y(k[m]),l?p.triggerHandler("$destroy"):l=!l,r=0,p=(z=p.children()).length;r<p;r++)e.push(Ga(z[r]));return g.apply(this,arguments)}
-var g=Ga.fn[b],g=g.$original||g;e.$original=g;Ga.fn[b]=e}function N(b){if(b instanceof N)return b;w(b)&&(b=ca(b));if(!(this instanceof N)){if(w(b)&&"<"!=b.charAt(0))throw Bb("nosel");return new N(b)}if(w(b)){var a=b;b=U;var c;if(c=je.exec(a))b=[b.createElement(c[1])];else{var d=b,e;b=d.createDocumentFragment();c=[];if(Cb.test(a)){d=b.appendChild(d.createElement("div"));e=(ke.exec(a)||["",""])[1].toLowerCase();e=ea[e]||ea._default;d.innerHTML="<div>&#160;</div>"+e[1]+a.replace(le,"<$1></$2>")+e[2];
-d.removeChild(d.firstChild);for(a=e[0];a--;)d=d.lastChild;a=0;for(e=d.childNodes.length;a<e;++a)c.push(d.childNodes[a]);d=b.firstChild;d.textContent=""}else c.push(d.createTextNode(a));b.textContent="";b.innerHTML="";b=c}Db(this,b);y(U.createDocumentFragment()).append(this)}else Db(this,b)}function Eb(b){return b.cloneNode(!0)}function Ha(b){hc(b);var a=0;for(b=b.childNodes||[];a<b.length;a++)Ha(b[a])}function ic(b,a,c,d){if(B(d))throw Bb("offargs");var e=la(b,"events");la(b,"handle")&&(E(a)?q(e,
-function(a,c){Fb(b,c,a);delete e[c]}):q(a.split(" "),function(a){E(c)?(Fb(b,a,e[a]),delete e[a]):Oa(e[a]||[],c)}))}function hc(b,a){var c=b[gb],d=Ua[c];d&&(a?delete Ua[c].data[a]:(d.handle&&(d.events.$destroy&&d.handle({},"$destroy"),ic(b)),delete Ua[c],b[gb]=s))}function la(b,a,c){var d=b[gb],d=Ua[d||-1];if(B(c))d||(b[gb]=d=++me,d=Ua[d]={}),d[a]=c;else return d&&d[a]}function jc(b,a,c){var d=la(b,"data"),e=B(c),g=!e&&B(a),f=g&&!X(a);d||f||la(b,"data",d={});if(e)d[a]=c;else if(g){if(f)return d&&d[a];
-D(d,a)}else return d}function Gb(b,a){return b.getAttribute?-1<(" "+(b.getAttribute("class")||"")+" ").replace(/[\n\t]/g," ").indexOf(" "+a+" "):!1}function hb(b,a){a&&b.setAttribute&&q(a.split(" "),function(a){b.setAttribute("class",ca((" "+(b.getAttribute("class")||"")+" ").replace(/[\n\t]/g," ").replace(" "+ca(a)+" "," ")))})}function ib(b,a){if(a&&b.setAttribute){var c=(" "+(b.getAttribute("class")||"")+" ").replace(/[\n\t]/g," ");q(a.split(" "),function(a){a=ca(a);-1===c.indexOf(" "+a+" ")&&
-(c+=a+" ")});b.setAttribute("class",ca(c))}}function Db(b,a){if(a){a=a.nodeName||!B(a.length)||Ca(a)?[a]:a;for(var c=0;c<a.length;c++)b.push(a[c])}}function kc(b,a){return jb(b,"$"+(a||"ngController")+"Controller")}function jb(b,a,c){b=y(b);9==b[0].nodeType&&(b=b.find("html"));for(a=M(a)?a:[a];b.length;){for(var d=b[0],e=0,g=a.length;e<g;e++)if((c=b.data(a[e]))!==s)return c;b=y(d.parentNode||11===d.nodeType&&d.host)}}function lc(b){for(var a=0,c=b.childNodes;a<c.length;a++)Ha(c[a]);for(;b.firstChild;)b.removeChild(b.firstChild)}
-function mc(b,a){var c=kb[a.toLowerCase()];return c&&nc[b.nodeName]&&c}function ne(b,a){var c=function(c,e){c.preventDefault||(c.preventDefault=function(){c.returnValue=!1});c.stopPropagation||(c.stopPropagation=function(){c.cancelBubble=!0});c.target||(c.target=c.srcElement||U);if(E(c.defaultPrevented)){var g=c.preventDefault;c.preventDefault=function(){c.defaultPrevented=!0;g.call(c)};c.defaultPrevented=!1}c.isDefaultPrevented=function(){return c.defaultPrevented||!1===c.returnValue};var f=Ub(a[e||
-c.type]||[]);q(f,function(a){a.call(b,c)});8>=S?(c.preventDefault=null,c.stopPropagation=null,c.isDefaultPrevented=null):(delete c.preventDefault,delete c.stopPropagation,delete c.isDefaultPrevented)};c.elem=b;return c}function Ia(b){var a=typeof b,c;"object"==a&&null!==b?"function"==typeof(c=b.$$hashKey)?c=b.$$hashKey():c===s&&(c=b.$$hashKey=bb()):c=b;return a+":"+c}function Va(b){q(b,this.put,this)}function oc(b){var a,c;"function"==typeof b?(a=b.$inject)||(a=[],b.length&&(c=b.toString().replace(oe,
-""),c=c.match(pe),q(c[1].split(qe),function(b){b.replace(re,function(b,c,d){a.push(d)})})),b.$inject=a):M(b)?(c=b.length-1,Ra(b[c],"fn"),a=b.slice(0,c)):Ra(b,"fn",!0);return a}function ac(b){function a(a){return function(b,c){if(X(b))q(b,Rb(a));else return a(b,c)}}function c(a,b){Aa(a,"service");if(P(b)||M(b))b=n.instantiate(b);if(!b.$get)throw Wa("pget",a);return m[a+h]=b}function d(a,b){return c(a,{$get:b})}function e(a){var b=[],c,d,g,h;q(a,function(a){if(!k.get(a)){k.put(a,!0);try{if(w(a))for(c=
-Sa(a),b=b.concat(e(c.requires)).concat(c._runBlocks),d=c._invokeQueue,g=0,h=d.length;g<h;g++){var f=d[g],l=n.get(f[0]);l[f[1]].apply(l,f[2])}else P(a)?b.push(n.invoke(a)):M(a)?b.push(n.invoke(a)):Ra(a,"module")}catch(m){throw M(a)&&(a=a[a.length-1]),m.message&&(m.stack&&-1==m.stack.indexOf(m.message))&&(m=m.message+"\n"+m.stack),Wa("modulerr",a,m.stack||m.message||m);}}});return b}function g(a,b){function c(d){if(a.hasOwnProperty(d)){if(a[d]===f)throw Wa("cdep",l.join(" <- "));return a[d]}try{return l.unshift(d),
-a[d]=f,a[d]=b(d)}catch(e){throw a[d]===f&&delete a[d],e;}finally{l.shift()}}function d(a,b,e){var g=[],h=oc(a),f,l,k;l=0;for(f=h.length;l<f;l++){k=h[l];if("string"!==typeof k)throw Wa("itkn",k);g.push(e&&e.hasOwnProperty(k)?e[k]:c(k))}a.$inject||(a=a[f]);return a.apply(b,g)}return{invoke:d,instantiate:function(a,b){var c=function(){},e;c.prototype=(M(a)?a[a.length-1]:a).prototype;c=new c;e=d(a,c,b);return X(e)||P(e)?e:c},get:c,annotate:oc,has:function(b){return m.hasOwnProperty(b+h)||a.hasOwnProperty(b)}}}
-var f={},h="Provider",l=[],k=new Va,m={$provide:{provider:a(c),factory:a(d),service:a(function(a,b){return d(a,["$injector",function(a){return a.instantiate(b)}])}),value:a(function(a,b){return d(a,aa(b))}),constant:a(function(a,b){Aa(a,"constant");m[a]=b;p[a]=b}),decorator:function(a,b){var c=n.get(a+h),d=c.$get;c.$get=function(){var a=r.invoke(d,c);return r.invoke(b,null,{$delegate:a})}}}},n=m.$injector=g(m,function(){throw Wa("unpr",l.join(" <- "));}),p={},r=p.$injector=g(p,function(a){a=n.get(a+
-h);return r.invoke(a.$get,a)});q(e(b),function(a){r.invoke(a||C)});return r}function Kd(){var b=!0;this.disableAutoScrolling=function(){b=!1};this.$get=["$window","$location","$rootScope",function(a,c,d){function e(a){var b=null;q(a,function(a){b||"a"!==K(a.nodeName)||(b=a)});return b}function g(){var b=c.hash(),d;b?(d=f.getElementById(b))?d.scrollIntoView():(d=e(f.getElementsByName(b)))?d.scrollIntoView():"top"===b&&a.scrollTo(0,0):a.scrollTo(0,0)}var f=a.document;b&&d.$watch(function(){return c.hash()},
-function(){d.$evalAsync(g)});return g}]}function ge(){this.$get=["$$rAF","$timeout",function(b,a){return b.supported?function(a){return b(a)}:function(b){return a(b,0,!1)}}]}function se(b,a,c,d){function e(a){try{a.apply(null,ya.call(arguments,1))}finally{if(z--,0===z)for(;u.length;)try{u.pop()()}catch(b){c.error(b)}}}function g(a,b){(function T(){q(F,function(a){a()});v=b(T,a)})()}function f(){x=null;J!=h.url()&&(J=h.url(),q(ma,function(a){a(h.url())}))}var h=this,l=a[0],k=b.location,m=b.history,
-n=b.setTimeout,p=b.clearTimeout,r={};h.isMock=!1;var z=0,u=[];h.$$completeOutstandingRequest=e;h.$$incOutstandingRequestCount=function(){z++};h.notifyWhenNoOutstandingRequests=function(a){q(F,function(a){a()});0===z?a():u.push(a)};var F=[],v;h.addPollFn=function(a){E(v)&&g(100,n);F.push(a);return a};var J=k.href,A=a.find("base"),x=null;h.url=function(a,c){k!==b.location&&(k=b.location);m!==b.history&&(m=b.history);if(a){if(J!=a)return J=a,d.history?c?m.replaceState(null,"",a):(m.pushState(null,"",
-a),A.attr("href",A.attr("href"))):(x=a,c?k.replace(a):k.href=a),h}else return x||k.href.replace(/%27/g,"'")};var ma=[],L=!1;h.onUrlChange=function(a){if(!L){if(d.history)y(b).on("popstate",f);if(d.hashchange)y(b).on("hashchange",f);else h.addPollFn(f);L=!0}ma.push(a);return a};h.baseHref=function(){var a=A.attr("href");return a?a.replace(/^(https?\:)?\/\/[^\/]*/,""):""};var Q={},da="",H=h.baseHref();h.cookies=function(a,b){var d,e,g,h;if(a)b===s?l.cookie=escape(a)+"=;path="+H+";expires=Thu, 01 Jan 1970 00:00:00 GMT":
-w(b)&&(d=(l.cookie=escape(a)+"="+escape(b)+";path="+H).length+1,4096<d&&c.warn("Cookie '"+a+"' possibly not set or overflowed because it was too large ("+d+" > 4096 bytes)!"));else{if(l.cookie!==da)for(da=l.cookie,d=da.split("; "),Q={},g=0;g<d.length;g++)e=d[g],h=e.indexOf("="),0<h&&(a=unescape(e.substring(0,h)),Q[a]===s&&(Q[a]=unescape(e.substring(h+1))));return Q}};h.defer=function(a,b){var c;z++;c=n(function(){delete r[c];e(a)},b||0);r[c]=!0;return c};h.defer.cancel=function(a){return r[a]?(delete r[a],
-p(a),e(C),!0):!1}}function Md(){this.$get=["$window","$log","$sniffer","$document",function(b,a,c,d){return new se(b,d,a,c)}]}function Nd(){this.$get=function(){function b(b,d){function e(a){a!=n&&(p?p==a&&(p=a.n):p=a,g(a.n,a.p),g(a,n),n=a,n.n=null)}function g(a,b){a!=b&&(a&&(a.p=b),b&&(b.n=a))}if(b in a)throw t("$cacheFactory")("iid",b);var f=0,h=D({},d,{id:b}),l={},k=d&&d.capacity||Number.MAX_VALUE,m={},n=null,p=null;return a[b]={put:function(a,b){if(k<Number.MAX_VALUE){var c=m[a]||(m[a]={key:a});
-e(c)}if(!E(b))return a in l||f++,l[a]=b,f>k&&this.remove(p.key),b},get:function(a){if(k<Number.MAX_VALUE){var b=m[a];if(!b)return;e(b)}return l[a]},remove:function(a){if(k<Number.MAX_VALUE){var b=m[a];if(!b)return;b==n&&(n=b.p);b==p&&(p=b.n);g(b.n,b.p);delete m[a]}delete l[a];f--},removeAll:function(){l={};f=0;m={};n=p=null},destroy:function(){m=h=l=null;delete a[b]},info:function(){return D({},h,{size:f})}}}var a={};b.info=function(){var b={};q(a,function(a,e){b[e]=a.info()});return b};b.get=function(b){return a[b]};
-return b}}function ce(){this.$get=["$cacheFactory",function(b){return b("templates")}]}function cc(b,a){var c={},d="Directive",e=/^\s*directive\:\s*([\d\w\-_]+)\s+(.*)$/,g=/(([\d\w\-_]+)(?:\:([^;]+))?;?)/,f=/^(on[a-z]+|formaction)$/;this.directive=function l(a,e){Aa(a,"directive");w(a)?(xb(e,"directiveFactory"),c.hasOwnProperty(a)||(c[a]=[],b.factory(a+d,["$injector","$exceptionHandler",function(b,d){var e=[];q(c[a],function(c,g){try{var f=b.invoke(c);P(f)?f={compile:aa(f)}:!f.compile&&f.link&&(f.compile=
-aa(f.link));f.priority=f.priority||0;f.index=g;f.name=f.name||a;f.require=f.require||f.controller&&f.name;f.restrict=f.restrict||"A";e.push(f)}catch(l){d(l)}});return e}])),c[a].push(e)):q(a,Rb(l));return this};this.aHrefSanitizationWhitelist=function(b){return B(b)?(a.aHrefSanitizationWhitelist(b),this):a.aHrefSanitizationWhitelist()};this.imgSrcSanitizationWhitelist=function(b){return B(b)?(a.imgSrcSanitizationWhitelist(b),this):a.imgSrcSanitizationWhitelist()};this.$get=["$injector","$interpolate",
-"$exceptionHandler","$http","$templateCache","$parse","$controller","$rootScope","$document","$sce","$animate","$$sanitizeUri",function(a,b,m,n,p,r,z,u,F,v,J,A){function x(a,b,c,d,e){a instanceof y||(a=y(a));q(a,function(b,c){3==b.nodeType&&b.nodeValue.match(/\S+/)&&(a[c]=y(b).wrap("<span></span>").parent()[0])});var g=L(a,b,a,c,d,e);ma(a,"ng-scope");return function(b,c,d){xb(b,"scope");var e=c?Ja.clone.call(a):a;q(d,function(a,b){e.data("$"+b+"Controller",a)});d=0;for(var f=e.length;d<f;d++){var l=
-e[d].nodeType;1!==l&&9!==l||e.eq(d).data("$scope",b)}c&&c(e,b);g&&g(b,e,e);return e}}function ma(a,b){try{a.addClass(b)}catch(c){}}function L(a,b,c,d,e,g){function f(a,c,d,e){var g,k,m,r,n,p,z;g=c.length;var I=Array(g);for(n=0;n<g;n++)I[n]=c[n];z=n=0;for(p=l.length;n<p;z++)k=I[z],c=l[n++],g=l[n++],m=y(k),c?(c.scope?(r=a.$new(),m.data("$scope",r)):r=a,(m=c.transclude)||!e&&b?c(g,r,k,d,Q(a,m||b)):c(g,r,k,d,e)):g&&g(a,k.childNodes,s,e)}for(var l=[],k,m,r,n,p=0;p<a.length;p++)k=new Hb,m=da(a[p],[],k,
-0===p?d:s,e),(g=m.length?ia(m,a[p],k,b,c,null,[],[],g):null)&&g.scope&&ma(y(a[p]),"ng-scope"),k=g&&g.terminal||!(r=a[p].childNodes)||!r.length?null:L(r,g?g.transclude:b),l.push(g,k),n=n||g||k,g=null;return n?f:null}function Q(a,b){return function(c,d,e){var g=!1;c||(c=a.$new(),g=c.$$transcluded=!0);d=b(c,d,e);if(g)d.on("$destroy",eb(c,c.$destroy));return d}}function da(a,b,c,d,f){var k=c.$attr,l;switch(a.nodeType){case 1:T(b,na(Ka(a).toLowerCase()),"E",d,f);var m,r,n;l=a.attributes;for(var p=0,z=
-l&&l.length;p<z;p++){var u=!1,F=!1;m=l[p];if(!S||8<=S||m.specified){r=m.name;n=na(r);W.test(n)&&(r=fb(n.substr(6),"-"));var J=n.replace(/(Start|End)$/,"");n===J+"Start"&&(u=r,F=r.substr(0,r.length-5)+"end",r=r.substr(0,r.length-6));n=na(r.toLowerCase());k[n]=r;c[n]=m=ca(m.value);mc(a,n)&&(c[n]=!0);N(a,b,m,n);T(b,n,"A",d,f,u,F)}}a=a.className;if(w(a)&&""!==a)for(;l=g.exec(a);)n=na(l[2]),T(b,n,"C",d,f)&&(c[n]=ca(l[3])),a=a.substr(l.index+l[0].length);break;case 3:t(b,a.nodeValue);break;case 8:try{if(l=
-e.exec(a.nodeValue))n=na(l[1]),T(b,n,"M",d,f)&&(c[n]=ca(l[2]))}catch(x){}}b.sort(E);return b}function H(a,b,c){var d=[],e=0;if(b&&a.hasAttribute&&a.hasAttribute(b)){do{if(!a)throw ja("uterdir",b,c);1==a.nodeType&&(a.hasAttribute(b)&&e++,a.hasAttribute(c)&&e--);d.push(a);a=a.nextSibling}while(0<e)}else d.push(a);return y(d)}function R(a,b,c){return function(d,e,g,f,l){e=H(e[0],b,c);return a(d,e,g,f,l)}}function ia(a,c,d,e,g,f,l,n,p){function u(a,b,c,d){if(a){c&&(a=R(a,c,d));a.require=G.require;if(Q===
-G||G.$$isolateScope)a=qc(a,{isolateScope:!0});l.push(a)}if(b){c&&(b=R(b,c,d));b.require=G.require;if(Q===G||G.$$isolateScope)b=qc(b,{isolateScope:!0});n.push(b)}}function F(a,b,c){var d,e="data",g=!1;if(w(a)){for(;"^"==(d=a.charAt(0))||"?"==d;)a=a.substr(1),"^"==d&&(e="inheritedData"),g=g||"?"==d;d=null;c&&"data"===e&&(d=c[a]);d=d||b[e]("$"+a+"Controller");if(!d&&!g)throw ja("ctreq",a,t);}else M(a)&&(d=[],q(a,function(a){d.push(F(a,b,c))}));return d}function J(a,e,g,f,p){function u(a,b){var c;2>arguments.length&&
-(b=a,a=s);D&&(c=lb);return p(a,b,c)}var I,x,v,A,R,H,lb={},da;I=c===g?d:Ub(d,new Hb(y(g),d.$attr));x=I.$$element;if(Q){var T=/^\s*([@=&])(\??)\s*(\w*)\s*$/;f=y(g);H=e.$new(!0);ia&&ia===Q.$$originalDirective?f.data("$isolateScope",H):f.data("$isolateScopeNoTemplate",H);ma(f,"ng-isolate-scope");q(Q.scope,function(a,c){var d=a.match(T)||[],g=d[3]||c,f="?"==d[2],d=d[1],l,m,n,p;H.$$isolateBindings[c]=d+g;switch(d){case "@":I.$observe(g,function(a){H[c]=a});I.$$observers[g].$$scope=e;I[g]&&(H[c]=b(I[g])(e));
-break;case "=":if(f&&!I[g])break;m=r(I[g]);p=m.literal?xa:function(a,b){return a===b};n=m.assign||function(){l=H[c]=m(e);throw ja("nonassign",I[g],Q.name);};l=H[c]=m(e);H.$watch(function(){var a=m(e);p(a,H[c])||(p(a,l)?n(e,a=H[c]):H[c]=a);return l=a},null,m.literal);break;case "&":m=r(I[g]);H[c]=function(a){return m(e,a)};break;default:throw ja("iscp",Q.name,c,a);}})}da=p&&u;L&&q(L,function(a){var b={$scope:a===Q||a.$$isolateScope?H:e,$element:x,$attrs:I,$transclude:da},c;R=a.controller;"@"==R&&(R=
-I[a.name]);c=z(R,b);lb[a.name]=c;D||x.data("$"+a.name+"Controller",c);a.controllerAs&&(b.$scope[a.controllerAs]=c)});f=0;for(v=l.length;f<v;f++)try{A=l[f],A(A.isolateScope?H:e,x,I,A.require&&F(A.require,x,lb),da)}catch(G){m(G,ha(x))}f=e;Q&&(Q.template||null===Q.templateUrl)&&(f=H);a&&a(f,g.childNodes,s,p);for(f=n.length-1;0<=f;f--)try{A=n[f],A(A.isolateScope?H:e,x,I,A.require&&F(A.require,x,lb),da)}catch(B){m(B,ha(x))}}p=p||{};for(var v=-Number.MAX_VALUE,A,L=p.controllerDirectives,Q=p.newIsolateScopeDirective,
-ia=p.templateDirective,T=p.nonTlbTranscludeDirective,E=!1,D=p.hasElementTranscludeDirective,Z=d.$$element=y(c),G,t,V,Xa=e,O,N=0,S=a.length;N<S;N++){G=a[N];var ra=G.$$start,W=G.$$end;ra&&(Z=H(c,ra,W));V=s;if(v>G.priority)break;if(V=G.scope)A=A||G,G.templateUrl||(K("new/isolated scope",Q,G,Z),X(V)&&(Q=G));t=G.name;!G.templateUrl&&G.controller&&(V=G.controller,L=L||{},K("'"+t+"' controller",L[t],G,Z),L[t]=G);if(V=G.transclude)E=!0,G.$$tlb||(K("transclusion",T,G,Z),T=G),"element"==V?(D=!0,v=G.priority,
-V=H(c,ra,W),Z=d.$$element=y(U.createComment(" "+t+": "+d[t]+" ")),c=Z[0],mb(g,y(ya.call(V,0)),c),Xa=x(V,e,v,f&&f.name,{nonTlbTranscludeDirective:T})):(V=y(Eb(c)).contents(),Z.empty(),Xa=x(V,e));if(G.template)if(K("template",ia,G,Z),ia=G,V=P(G.template)?G.template(Z,d):G.template,V=Y(V),G.replace){f=G;V=Cb.test(V)?y(V):[];c=V[0];if(1!=V.length||1!==c.nodeType)throw ja("tplrt",t,"");mb(g,Z,c);S={$attr:{}};V=da(c,[],S);var $=a.splice(N+1,a.length-(N+1));Q&&pc(V);a=a.concat(V).concat($);B(d,S);S=a.length}else Z.html(V);
-if(G.templateUrl)K("template",ia,G,Z),ia=G,G.replace&&(f=G),J=C(a.splice(N,a.length-N),Z,d,g,Xa,l,n,{controllerDirectives:L,newIsolateScopeDirective:Q,templateDirective:ia,nonTlbTranscludeDirective:T}),S=a.length;else if(G.compile)try{O=G.compile(Z,d,Xa),P(O)?u(null,O,ra,W):O&&u(O.pre,O.post,ra,W)}catch(aa){m(aa,ha(Z))}G.terminal&&(J.terminal=!0,v=Math.max(v,G.priority))}J.scope=A&&!0===A.scope;J.transclude=E&&Xa;p.hasElementTranscludeDirective=D;return J}function pc(a){for(var b=0,c=a.length;b<c;b++)a[b]=
-Tb(a[b],{$$isolateScope:!0})}function T(b,e,g,f,k,n,r){if(e===k)return null;k=null;if(c.hasOwnProperty(e)){var p;e=a.get(e+d);for(var z=0,u=e.length;z<u;z++)try{p=e[z],(f===s||f>p.priority)&&-1!=p.restrict.indexOf(g)&&(n&&(p=Tb(p,{$$start:n,$$end:r})),b.push(p),k=p)}catch(F){m(F)}}return k}function B(a,b){var c=b.$attr,d=a.$attr,e=a.$$element;q(a,function(d,e){"$"!=e.charAt(0)&&(b[e]&&(d+=("style"===e?";":" ")+b[e]),a.$set(e,d,!0,c[e]))});q(b,function(b,g){"class"==g?(ma(e,b),a["class"]=(a["class"]?
-a["class"]+" ":"")+b):"style"==g?(e.attr("style",e.attr("style")+";"+b),a.style=(a.style?a.style+";":"")+b):"$"==g.charAt(0)||a.hasOwnProperty(g)||(a[g]=b,d[g]=c[g])})}function C(a,b,c,d,e,g,f,l){var k=[],m,r,z=b[0],u=a.shift(),F=D({},u,{templateUrl:null,transclude:null,replace:null,$$originalDirective:u}),x=P(u.templateUrl)?u.templateUrl(b,c):u.templateUrl;b.empty();n.get(v.getTrustedResourceUrl(x),{cache:p}).success(function(n){var p,J;n=Y(n);if(u.replace){n=Cb.test(n)?y(n):[];p=n[0];if(1!=n.length||
-1!==p.nodeType)throw ja("tplrt",u.name,x);n={$attr:{}};mb(d,b,p);var v=da(p,[],n);X(u.scope)&&pc(v);a=v.concat(a);B(c,n)}else p=z,b.html(n);a.unshift(F);m=ia(a,p,c,e,b,u,g,f,l);q(d,function(a,c){a==p&&(d[c]=b[0])});for(r=L(b[0].childNodes,e);k.length;){n=k.shift();J=k.shift();var A=k.shift(),R=k.shift(),v=b[0];if(J!==z){var H=J.className;l.hasElementTranscludeDirective&&u.replace||(v=Eb(p));mb(A,y(J),v);ma(y(v),H)}J=m.transclude?Q(n,m.transclude):R;m(r,n,v,d,J)}k=null}).error(function(a,b,c,d){throw ja("tpload",
-d.url);});return function(a,b,c,d,e){k?(k.push(b),k.push(c),k.push(d),k.push(e)):m(r,b,c,d,e)}}function E(a,b){var c=b.priority-a.priority;return 0!==c?c:a.name!==b.name?a.name<b.name?-1:1:a.index-b.index}function K(a,b,c,d){if(b)throw ja("multidir",b.name,c.name,a,ha(d));}function t(a,c){var d=b(c,!0);d&&a.push({priority:0,compile:aa(function(a,b){var c=b.parent(),e=c.data("$binding")||[];e.push(d);ma(c.data("$binding",e),"ng-binding");a.$watch(d,function(a){b[0].nodeValue=a})})})}function O(a,b){if("srcdoc"==
-b)return v.HTML;var c=Ka(a);if("xlinkHref"==b||"FORM"==c&&"action"==b||"IMG"!=c&&("src"==b||"ngSrc"==b))return v.RESOURCE_URL}function N(a,c,d,e){var g=b(d,!0);if(g){if("multiple"===e&&"SELECT"===Ka(a))throw ja("selmulti",ha(a));c.push({priority:100,compile:function(){return{pre:function(c,d,l){d=l.$$observers||(l.$$observers={});if(f.test(e))throw ja("nodomevents");if(g=b(l[e],!0,O(a,e)))l[e]=g(c),(d[e]||(d[e]=[])).$$inter=!0,(l.$$observers&&l.$$observers[e].$$scope||c).$watch(g,function(a,b){"class"===
-e&&a!=b?l.$updateClass(a,b):l.$set(e,a)})}}}})}}function mb(a,b,c){var d=b[0],e=b.length,g=d.parentNode,f,l;if(a)for(f=0,l=a.length;f<l;f++)if(a[f]==d){a[f++]=c;l=f+e-1;for(var k=a.length;f<k;f++,l++)l<k?a[f]=a[l]:delete a[f];a.length-=e-1;break}g&&g.replaceChild(c,d);a=U.createDocumentFragment();a.appendChild(d);c[y.expando]=d[y.expando];d=1;for(e=b.length;d<e;d++)g=b[d],y(g).remove(),a.appendChild(g),delete b[d];b[0]=c;b.length=1}function qc(a,b){return D(function(){return a.apply(null,arguments)},
-a,b)}var Hb=function(a,b){this.$$element=a;this.$attr=b||{}};Hb.prototype={$normalize:na,$addClass:function(a){a&&0<a.length&&J.addClass(this.$$element,a)},$removeClass:function(a){a&&0<a.length&&J.removeClass(this.$$element,a)},$updateClass:function(a,b){var c=rc(a,b),d=rc(b,a);0===c.length?J.removeClass(this.$$element,d):0===d.length?J.addClass(this.$$element,c):J.setClass(this.$$element,c,d)},$set:function(a,b,c,d){var e=mc(this.$$element[0],a);e&&(this.$$element.prop(a,b),d=e);this[a]=b;d?this.$attr[a]=
-d:(d=this.$attr[a])||(this.$attr[a]=d=fb(a,"-"));e=Ka(this.$$element);if("A"===e&&"href"===a||"IMG"===e&&"src"===a)this[a]=b=A(b,"src"===a);!1!==c&&(null===b||b===s?this.$$element.removeAttr(d):this.$$element.attr(d,b));(c=this.$$observers)&&q(c[a],function(a){try{a(b)}catch(c){m(c)}})},$observe:function(a,b){var c=this,d=c.$$observers||(c.$$observers={}),e=d[a]||(d[a]=[]);e.push(b);u.$evalAsync(function(){e.$$inter||b(c[a])});return b}};var Z=b.startSymbol(),ra=b.endSymbol(),Y="{{"==Z||"}}"==ra?
-Da:function(a){return a.replace(/\{\{/g,Z).replace(/}}/g,ra)},W=/^ngAttr[A-Z]/;return x}]}function na(b){return Ta(b.replace(te,""))}function rc(b,a){var c="",d=b.split(/\s+/),e=a.split(/\s+/),g=0;a:for(;g<d.length;g++){for(var f=d[g],h=0;h<e.length;h++)if(f==e[h])continue a;c+=(0<c.length?" ":"")+f}return c}function Od(){var b={},a=/^(\S+)(\s+as\s+(\w+))?$/;this.register=function(a,d){Aa(a,"controller");X(a)?D(b,a):b[a]=d};this.$get=["$injector","$window",function(c,d){return function(e,g){var f,
-h,l;w(e)&&(f=e.match(a),h=f[1],l=f[3],e=b.hasOwnProperty(h)?b[h]:bc(g.$scope,h,!0)||bc(d,h,!0),Ra(e,h,!0));f=c.instantiate(e,g);if(l){if(!g||"object"!=typeof g.$scope)throw t("$controller")("noscp",h||e.name,l);g.$scope[l]=f}return f}}]}function Pd(){this.$get=["$window",function(b){return y(b.document)}]}function Qd(){this.$get=["$log",function(b){return function(a,c){b.error.apply(b,arguments)}}]}function sc(b){var a={},c,d,e;if(!b)return a;q(b.split("\n"),function(b){e=b.indexOf(":");c=K(ca(b.substr(0,
-e)));d=ca(b.substr(e+1));c&&(a[c]=a[c]?a[c]+(", "+d):d)});return a}function tc(b){var a=X(b)?b:s;return function(c){a||(a=sc(b));return c?a[K(c)]||null:a}}function uc(b,a,c){if(P(c))return c(b,a);q(c,function(c){b=c(b,a)});return b}function Td(){var b=/^\s*(\[|\{[^\{])/,a=/[\}\]]\s*$/,c=/^\)\]\}',?\n/,d={"Content-Type":"application/json;charset=utf-8"},e=this.defaults={transformResponse:[function(d){w(d)&&(d=d.replace(c,""),b.test(d)&&a.test(d)&&(d=Wb(d)));return d}],transformRequest:[function(a){return X(a)&&
-"[object File]"!==wa.call(a)&&"[object Blob]"!==wa.call(a)?qa(a):a}],headers:{common:{Accept:"application/json, text/plain, */*"},post:ba(d),put:ba(d),patch:ba(d)},xsrfCookieName:"XSRF-TOKEN",xsrfHeaderName:"X-XSRF-TOKEN"},g=this.interceptors=[],f=this.responseInterceptors=[];this.$get=["$httpBackend","$browser","$cacheFactory","$rootScope","$q","$injector",function(a,b,c,d,n,p){function r(a){function c(a){var b=D({},a,{data:uc(a.data,a.headers,d.transformResponse)});return 200<=a.status&&300>a.status?
-b:n.reject(b)}var d={method:"get",transformRequest:e.transformRequest,transformResponse:e.transformResponse},g=function(a){function b(a){var c;q(a,function(b,d){P(b)&&(c=b(),null!=c?a[d]=c:delete a[d])})}var c=e.headers,d=D({},a.headers),g,f,c=D({},c.common,c[K(a.method)]);b(c);b(d);a:for(g in c){a=K(g);for(f in d)if(K(f)===a)continue a;d[g]=c[g]}return d}(a);D(d,a);d.headers=g;d.method=Fa(d.method);(a=Ib(d.url)?b.cookies()[d.xsrfCookieName||e.xsrfCookieName]:s)&&(g[d.xsrfHeaderName||e.xsrfHeaderName]=
-a);var f=[function(a){g=a.headers;var b=uc(a.data,tc(g),a.transformRequest);E(a.data)&&q(g,function(a,b){"content-type"===K(b)&&delete g[b]});E(a.withCredentials)&&!E(e.withCredentials)&&(a.withCredentials=e.withCredentials);return z(a,b,g).then(c,c)},s],h=n.when(d);for(q(v,function(a){(a.request||a.requestError)&&f.unshift(a.request,a.requestError);(a.response||a.responseError)&&f.push(a.response,a.responseError)});f.length;){a=f.shift();var k=f.shift(),h=h.then(a,k)}h.success=function(a){h.then(function(b){a(b.data,
-b.status,b.headers,d)});return h};h.error=function(a){h.then(null,function(b){a(b.data,b.status,b.headers,d)});return h};return h}function z(b,c,g){function f(a,b,c,e){v&&(200<=a&&300>a?v.put(s,[a,b,sc(c),e]):v.remove(s));l(b,a,c,e);d.$$phase||d.$apply()}function l(a,c,d,e){c=Math.max(c,0);(200<=c&&300>c?p.resolve:p.reject)({data:a,status:c,headers:tc(d),config:b,statusText:e})}function k(){var a=db(r.pendingRequests,b);-1!==a&&r.pendingRequests.splice(a,1)}var p=n.defer(),z=p.promise,v,q,s=u(b.url,
-b.params);r.pendingRequests.push(b);z.then(k,k);(b.cache||e.cache)&&(!1!==b.cache&&"GET"==b.method)&&(v=X(b.cache)?b.cache:X(e.cache)?e.cache:F);if(v)if(q=v.get(s),B(q)){if(q.then)return q.then(k,k),q;M(q)?l(q[1],q[0],ba(q[2]),q[3]):l(q,200,{},"OK")}else v.put(s,z);E(q)&&a(b.method,s,c,f,g,b.timeout,b.withCredentials,b.responseType);return z}function u(a,b){if(!b)return a;var c=[];Sc(b,function(a,b){null===a||E(a)||(M(a)||(a=[a]),q(a,function(a){X(a)&&(a=qa(a));c.push(za(b)+"="+za(a))}))});0<c.length&&
-(a+=(-1==a.indexOf("?")?"?":"&")+c.join("&"));return a}var F=c("$http"),v=[];q(g,function(a){v.unshift(w(a)?p.get(a):p.invoke(a))});q(f,function(a,b){var c=w(a)?p.get(a):p.invoke(a);v.splice(b,0,{response:function(a){return c(n.when(a))},responseError:function(a){return c(n.reject(a))}})});r.pendingRequests=[];(function(a){q(arguments,function(a){r[a]=function(b,c){return r(D(c||{},{method:a,url:b}))}})})("get","delete","head","jsonp");(function(a){q(arguments,function(a){r[a]=function(b,c,d){return r(D(d||
-{},{method:a,url:b,data:c}))}})})("post","put");r.defaults=e;return r}]}function ue(b){if(8>=S&&(!b.match(/^(get|post|head|put|delete|options)$/i)||!O.XMLHttpRequest))return new O.ActiveXObject("Microsoft.XMLHTTP");if(O.XMLHttpRequest)return new O.XMLHttpRequest;throw t("$httpBackend")("noxhr");}function Ud(){this.$get=["$browser","$window","$document",function(b,a,c){return ve(b,ue,b.defer,a.angular.callbacks,c[0])}]}function ve(b,a,c,d,e){function g(a,b){var c=e.createElement("script"),d=function(){c.onreadystatechange=
-c.onload=c.onerror=null;e.body.removeChild(c);b&&b()};c.type="text/javascript";c.src=a;S&&8>=S?c.onreadystatechange=function(){/loaded|complete/.test(c.readyState)&&d()}:c.onload=c.onerror=function(){d()};e.body.appendChild(c);return d}var f=-1;return function(e,l,k,m,n,p,r,z){function u(){v=f;A&&A();x&&x.abort()}function F(a,d,e,g,f){L&&c.cancel(L);A=x=null;0===d&&(d=e?200:"file"==sa(l).protocol?404:0);a(1223===d?204:d,e,g,f||"");b.$$completeOutstandingRequest(C)}var v;b.$$incOutstandingRequestCount();
-l=l||b.url();if("jsonp"==K(e)){var J="_"+(d.counter++).toString(36);d[J]=function(a){d[J].data=a};var A=g(l.replace("JSON_CALLBACK","angular.callbacks."+J),function(){d[J].data?F(m,200,d[J].data):F(m,v||-2);d[J]=Ea.noop})}else{var x=a(e);x.open(e,l,!0);q(n,function(a,b){B(a)&&x.setRequestHeader(b,a)});x.onreadystatechange=function(){if(x&&4==x.readyState){var a=null,b=null;v!==f&&(a=x.getAllResponseHeaders(),b="response"in x?x.response:x.responseText);F(m,v||x.status,b,a,x.statusText||"")}};r&&(x.withCredentials=
-!0);if(z)try{x.responseType=z}catch(s){if("json"!==z)throw s;}x.send(k||null)}if(0<p)var L=c(u,p);else p&&p.then&&p.then(u)}}function Rd(){var b="{{",a="}}";this.startSymbol=function(a){return a?(b=a,this):b};this.endSymbol=function(b){return b?(a=b,this):a};this.$get=["$parse","$exceptionHandler","$sce",function(c,d,e){function g(g,k,m){for(var n,p,r=0,z=[],u=g.length,F=!1,v=[];r<u;)-1!=(n=g.indexOf(b,r))&&-1!=(p=g.indexOf(a,n+f))?(r!=n&&z.push(g.substring(r,n)),z.push(r=c(F=g.substring(n+f,p))),
-r.exp=F,r=p+h,F=!0):(r!=u&&z.push(g.substring(r)),r=u);(u=z.length)||(z.push(""),u=1);if(m&&1<z.length)throw vc("noconcat",g);if(!k||F)return v.length=u,r=function(a){try{for(var b=0,c=u,f;b<c;b++)"function"==typeof(f=z[b])&&(f=f(a),f=m?e.getTrusted(m,f):e.valueOf(f),null===f||E(f)?f="":"string"!=typeof f&&(f=qa(f))),v[b]=f;return v.join("")}catch(h){a=vc("interr",g,h.toString()),d(a)}},r.exp=g,r.parts=z,r}var f=b.length,h=a.length;g.startSymbol=function(){return b};g.endSymbol=function(){return a};
-return g}]}function Sd(){this.$get=["$rootScope","$window","$q",function(b,a,c){function d(d,f,h,l){var k=a.setInterval,m=a.clearInterval,n=c.defer(),p=n.promise,r=0,z=B(l)&&!l;h=B(h)?h:0;p.then(null,null,d);p.$$intervalId=k(function(){n.notify(r++);0<h&&r>=h&&(n.resolve(r),m(p.$$intervalId),delete e[p.$$intervalId]);z||b.$apply()},f);e[p.$$intervalId]=n;return p}var e={};d.cancel=function(a){return a&&a.$$intervalId in e?(e[a.$$intervalId].reject("canceled"),clearInterval(a.$$intervalId),delete e[a.$$intervalId],
-!0):!1};return d}]}function ad(){this.$get=function(){return{id:"en-us",NUMBER_FORMATS:{DECIMAL_SEP:".",GROUP_SEP:",",PATTERNS:[{minInt:1,minFrac:0,maxFrac:3,posPre:"",posSuf:"",negPre:"-",negSuf:"",gSize:3,lgSize:3},{minInt:1,minFrac:2,maxFrac:2,posPre:"\u00a4",posSuf:"",negPre:"(\u00a4",negSuf:")",gSize:3,lgSize:3}],CURRENCY_SYM:"$"},DATETIME_FORMATS:{MONTH:"January February March April May June July August September October November December".split(" "),SHORTMONTH:"Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec".split(" "),
-DAY:"Sunday Monday Tuesday Wednesday Thursday Friday Saturday".split(" "),SHORTDAY:"Sun Mon Tue Wed Thu Fri Sat".split(" "),AMPMS:["AM","PM"],medium:"MMM d, y h:mm:ss a","short":"M/d/yy h:mm a",fullDate:"EEEE, MMMM d, y",longDate:"MMMM d, y",mediumDate:"MMM d, y",shortDate:"M/d/yy",mediumTime:"h:mm:ss a",shortTime:"h:mm a"},pluralCat:function(b){return 1===b?"one":"other"}}}}function wc(b){b=b.split("/");for(var a=b.length;a--;)b[a]=wb(b[a]);return b.join("/")}function xc(b,a,c){b=sa(b,c);a.$$protocol=
-b.protocol;a.$$host=b.hostname;a.$$port=Y(b.port)||we[b.protocol]||null}function yc(b,a,c){var d="/"!==b.charAt(0);d&&(b="/"+b);b=sa(b,c);a.$$path=decodeURIComponent(d&&"/"===b.pathname.charAt(0)?b.pathname.substring(1):b.pathname);a.$$search=Yb(b.search);a.$$hash=decodeURIComponent(b.hash);a.$$path&&"/"!=a.$$path.charAt(0)&&(a.$$path="/"+a.$$path)}function oa(b,a){if(0===a.indexOf(b))return a.substr(b.length)}function Ya(b){var a=b.indexOf("#");return-1==a?b:b.substr(0,a)}function Jb(b){return b.substr(0,
-Ya(b).lastIndexOf("/")+1)}function zc(b,a){this.$$html5=!0;a=a||"";var c=Jb(b);xc(b,this,b);this.$$parse=function(a){var e=oa(c,a);if(!w(e))throw Kb("ipthprfx",a,c);yc(e,this,b);this.$$path||(this.$$path="/");this.$$compose()};this.$$compose=function(){var a=Zb(this.$$search),b=this.$$hash?"#"+wb(this.$$hash):"";this.$$url=wc(this.$$path)+(a?"?"+a:"")+b;this.$$absUrl=c+this.$$url.substr(1)};this.$$rewrite=function(d){var e;if((e=oa(b,d))!==s)return d=e,(e=oa(a,e))!==s?c+(oa("/",e)||e):b+d;if((e=oa(c,
-d))!==s)return c+e;if(c==d+"/")return c}}function Lb(b,a){var c=Jb(b);xc(b,this,b);this.$$parse=function(d){var e=oa(b,d)||oa(c,d),e="#"==e.charAt(0)?oa(a,e):this.$$html5?e:"";if(!w(e))throw Kb("ihshprfx",d,a);yc(e,this,b);d=this.$$path;var g=/^\/?.*?:(\/.*)/;0===e.indexOf(b)&&(e=e.replace(b,""));g.exec(e)||(d=(e=g.exec(d))?e[1]:d);this.$$path=d;this.$$compose()};this.$$compose=function(){var c=Zb(this.$$search),e=this.$$hash?"#"+wb(this.$$hash):"";this.$$url=wc(this.$$path)+(c?"?"+c:"")+e;this.$$absUrl=
-b+(this.$$url?a+this.$$url:"")};this.$$rewrite=function(a){if(Ya(b)==Ya(a))return a}}function Ac(b,a){this.$$html5=!0;Lb.apply(this,arguments);var c=Jb(b);this.$$rewrite=function(d){var e;if(b==Ya(d))return d;if(e=oa(c,d))return b+a+e;if(c===d+"/")return c}}function nb(b){return function(){return this[b]}}function Bc(b,a){return function(c){if(E(c))return this[b];this[b]=a(c);this.$$compose();return this}}function Vd(){var b="",a=!1;this.hashPrefix=function(a){return B(a)?(b=a,this):b};this.html5Mode=
-function(b){return B(b)?(a=b,this):a};this.$get=["$rootScope","$browser","$sniffer","$rootElement",function(c,d,e,g){function f(a){c.$broadcast("$locationChangeSuccess",h.absUrl(),a)}var h,l=d.baseHref(),k=d.url();a?(l=k.substring(0,k.indexOf("/",k.indexOf("//")+2))+(l||"/"),e=e.history?zc:Ac):(l=Ya(k),e=Lb);h=new e(l,"#"+b);h.$$parse(h.$$rewrite(k));g.on("click",function(a){if(!a.ctrlKey&&!a.metaKey&&2!=a.which){for(var b=y(a.target);"a"!==K(b[0].nodeName);)if(b[0]===g[0]||!(b=b.parent())[0])return;
-var e=b.prop("href");X(e)&&"[object SVGAnimatedString]"===e.toString()&&(e=sa(e.animVal).href);var f=h.$$rewrite(e);e&&(!b.attr("target")&&f&&!a.isDefaultPrevented())&&(a.preventDefault(),f!=d.url()&&(h.$$parse(f),c.$apply(),O.angular["ff-684208-preventDefault"]=!0))}});h.absUrl()!=k&&d.url(h.absUrl(),!0);d.onUrlChange(function(a){h.absUrl()!=a&&(c.$evalAsync(function(){var b=h.absUrl();h.$$parse(a);c.$broadcast("$locationChangeStart",a,b).defaultPrevented?(h.$$parse(b),d.url(b)):f(b)}),c.$$phase||
-c.$digest())});var m=0;c.$watch(function(){var a=d.url(),b=h.$$replace;m&&a==h.absUrl()||(m++,c.$evalAsync(function(){c.$broadcast("$locationChangeStart",h.absUrl(),a).defaultPrevented?h.$$parse(a):(d.url(h.absUrl(),b),f(a))}));h.$$replace=!1;return m});return h}]}function Wd(){var b=!0,a=this;this.debugEnabled=function(a){return B(a)?(b=a,this):b};this.$get=["$window",function(c){function d(a){a instanceof Error&&(a.stack?a=a.message&&-1===a.stack.indexOf(a.message)?"Error: "+a.message+"\n"+a.stack:
-a.stack:a.sourceURL&&(a=a.message+"\n"+a.sourceURL+":"+a.line));return a}function e(a){var b=c.console||{},e=b[a]||b.log||C;a=!1;try{a=!!e.apply}catch(l){}return a?function(){var a=[];q(arguments,function(b){a.push(d(b))});return e.apply(b,a)}:function(a,b){e(a,null==b?"":b)}}return{log:e("log"),info:e("info"),warn:e("warn"),error:e("error"),debug:function(){var c=e("debug");return function(){b&&c.apply(a,arguments)}}()}}]}function fa(b,a){if("constructor"===b)throw Ba("isecfld",a);return b}function Za(b,
-a){if(b){if(b.constructor===b)throw Ba("isecfn",a);if(b.document&&b.location&&b.alert&&b.setInterval)throw Ba("isecwindow",a);if(b.children&&(b.nodeName||b.prop&&b.attr&&b.find))throw Ba("isecdom",a);}return b}function ob(b,a,c,d,e){e=e||{};a=a.split(".");for(var g,f=0;1<a.length;f++){g=fa(a.shift(),d);var h=b[g];h||(h={},b[g]=h);b=h;b.then&&e.unwrapPromises&&(ta(d),"$$v"in b||function(a){a.then(function(b){a.$$v=b})}(b),b.$$v===s&&(b.$$v={}),b=b.$$v)}g=fa(a.shift(),d);return b[g]=c}function Cc(b,
-a,c,d,e,g,f){fa(b,g);fa(a,g);fa(c,g);fa(d,g);fa(e,g);return f.unwrapPromises?function(f,l){var k=l&&l.hasOwnProperty(b)?l:f,m;if(null==k)return k;(k=k[b])&&k.then&&(ta(g),"$$v"in k||(m=k,m.$$v=s,m.then(function(a){m.$$v=a})),k=k.$$v);if(!a)return k;if(null==k)return s;(k=k[a])&&k.then&&(ta(g),"$$v"in k||(m=k,m.$$v=s,m.then(function(a){m.$$v=a})),k=k.$$v);if(!c)return k;if(null==k)return s;(k=k[c])&&k.then&&(ta(g),"$$v"in k||(m=k,m.$$v=s,m.then(function(a){m.$$v=a})),k=k.$$v);if(!d)return k;if(null==
-k)return s;(k=k[d])&&k.then&&(ta(g),"$$v"in k||(m=k,m.$$v=s,m.then(function(a){m.$$v=a})),k=k.$$v);if(!e)return k;if(null==k)return s;(k=k[e])&&k.then&&(ta(g),"$$v"in k||(m=k,m.$$v=s,m.then(function(a){m.$$v=a})),k=k.$$v);return k}:function(g,f){var k=f&&f.hasOwnProperty(b)?f:g;if(null==k)return k;k=k[b];if(!a)return k;if(null==k)return s;k=k[a];if(!c)return k;if(null==k)return s;k=k[c];if(!d)return k;if(null==k)return s;k=k[d];return e?null==k?s:k=k[e]:k}}function xe(b,a){fa(b,a);return function(a,
-d){return null==a?s:(d&&d.hasOwnProperty(b)?d:a)[b]}}function ye(b,a,c){fa(b,c);fa(a,c);return function(c,e){if(null==c)return s;c=(e&&e.hasOwnProperty(b)?e:c)[b];return null==c?s:c[a]}}function Dc(b,a,c){if(Mb.hasOwnProperty(b))return Mb[b];var d=b.split("."),e=d.length,g;if(a.unwrapPromises||1!==e)if(a.unwrapPromises||2!==e)if(a.csp)g=6>e?Cc(d[0],d[1],d[2],d[3],d[4],c,a):function(b,g){var f=0,h;do h=Cc(d[f++],d[f++],d[f++],d[f++],d[f++],c,a)(b,g),g=s,b=h;while(f<e);return h};else{var f="var p;\n";
-q(d,function(b,d){fa(b,c);f+="if(s == null) return undefined;\ns="+(d?"s":'((k&&k.hasOwnProperty("'+b+'"))?k:s)')+'["'+b+'"];\n'+(a.unwrapPromises?'if (s && s.then) {\n pw("'+c.replace(/(["\r\n])/g,"\\$1")+'");\n if (!("$$v" in s)) {\n p=s;\n p.$$v = undefined;\n p.then(function(v) {p.$$v=v;});\n}\n s=s.$$v\n}\n':"")});var f=f+"return s;",h=new Function("s","k","pw",f);h.toString=aa(f);g=a.unwrapPromises?function(a,b){return h(a,b,ta)}:h}else g=ye(d[0],d[1],c);else g=xe(d[0],c);"hasOwnProperty"!==
-b&&(Mb[b]=g);return g}function Xd(){var b={},a={csp:!1,unwrapPromises:!1,logPromiseWarnings:!0};this.unwrapPromises=function(b){return B(b)?(a.unwrapPromises=!!b,this):a.unwrapPromises};this.logPromiseWarnings=function(b){return B(b)?(a.logPromiseWarnings=b,this):a.logPromiseWarnings};this.$get=["$filter","$sniffer","$log",function(c,d,e){a.csp=d.csp;ta=function(b){a.logPromiseWarnings&&!Ec.hasOwnProperty(b)&&(Ec[b]=!0,e.warn("[$parse] Promise found in the expression `"+b+"`. Automatic unwrapping of promises in Angular expressions is deprecated."))};
-return function(d){var e;switch(typeof d){case "string":if(b.hasOwnProperty(d))return b[d];e=new Nb(a);e=(new $a(e,c,a)).parse(d,!1);"hasOwnProperty"!==d&&(b[d]=e);return e;case "function":return d;default:return C}}}]}function Zd(){this.$get=["$rootScope","$exceptionHandler",function(b,a){return ze(function(a){b.$evalAsync(a)},a)}]}function ze(b,a){function c(a){return a}function d(a){return f(a)}var e=function(){var f=[],k,m;return m={resolve:function(a){if(f){var c=f;f=s;k=g(a);c.length&&b(function(){for(var a,
-b=0,d=c.length;b<d;b++)a=c[b],k.then(a[0],a[1],a[2])})}},reject:function(a){m.resolve(h(a))},notify:function(a){if(f){var c=f;f.length&&b(function(){for(var b,d=0,e=c.length;d<e;d++)b=c[d],b[2](a)})}},promise:{then:function(b,g,h){var m=e(),u=function(d){try{m.resolve((P(b)?b:c)(d))}catch(e){m.reject(e),a(e)}},F=function(b){try{m.resolve((P(g)?g:d)(b))}catch(c){m.reject(c),a(c)}},v=function(b){try{m.notify((P(h)?h:c)(b))}catch(d){a(d)}};f?f.push([u,F,v]):k.then(u,F,v);return m.promise},"catch":function(a){return this.then(null,
-a)},"finally":function(a){function b(a,c){var d=e();c?d.resolve(a):d.reject(a);return d.promise}function d(e,g){var f=null;try{f=(a||c)()}catch(h){return b(h,!1)}return f&&P(f.then)?f.then(function(){return b(e,g)},function(a){return b(a,!1)}):b(e,g)}return this.then(function(a){return d(a,!0)},function(a){return d(a,!1)})}}}},g=function(a){return a&&P(a.then)?a:{then:function(c){var d=e();b(function(){d.resolve(c(a))});return d.promise}}},f=function(a){var b=e();b.reject(a);return b.promise},h=function(c){return{then:function(g,
-f){var h=e();b(function(){try{h.resolve((P(f)?f:d)(c))}catch(b){h.reject(b),a(b)}});return h.promise}}};return{defer:e,reject:f,when:function(h,k,m,n){var p=e(),r,z=function(b){try{return(P(k)?k:c)(b)}catch(d){return a(d),f(d)}},u=function(b){try{return(P(m)?m:d)(b)}catch(c){return a(c),f(c)}},F=function(b){try{return(P(n)?n:c)(b)}catch(d){a(d)}};b(function(){g(h).then(function(a){r||(r=!0,p.resolve(g(a).then(z,u,F)))},function(a){r||(r=!0,p.resolve(u(a)))},function(a){r||p.notify(F(a))})});return p.promise},
-all:function(a){var b=e(),c=0,d=M(a)?[]:{};q(a,function(a,e){c++;g(a).then(function(a){d.hasOwnProperty(e)||(d[e]=a,--c||b.resolve(d))},function(a){d.hasOwnProperty(e)||b.reject(a)})});0===c&&b.resolve(d);return b.promise}}}function fe(){this.$get=["$window","$timeout",function(b,a){var c=b.requestAnimationFrame||b.webkitRequestAnimationFrame||b.mozRequestAnimationFrame,d=b.cancelAnimationFrame||b.webkitCancelAnimationFrame||b.mozCancelAnimationFrame||b.webkitCancelRequestAnimationFrame,e=!!c,g=e?
-function(a){var b=c(a);return function(){d(b)}}:function(b){var c=a(b,16.66,!1);return function(){a.cancel(c)}};g.supported=e;return g}]}function Yd(){var b=10,a=t("$rootScope"),c=null;this.digestTtl=function(a){arguments.length&&(b=a);return b};this.$get=["$injector","$exceptionHandler","$parse","$browser",function(d,e,g,f){function h(){this.$id=bb();this.$$phase=this.$parent=this.$$watchers=this.$$nextSibling=this.$$prevSibling=this.$$childHead=this.$$childTail=null;this["this"]=this.$root=this;
-this.$$destroyed=!1;this.$$asyncQueue=[];this.$$postDigestQueue=[];this.$$listeners={};this.$$listenerCount={};this.$$isolateBindings={}}function l(b){if(p.$$phase)throw a("inprog",p.$$phase);p.$$phase=b}function k(a,b){var c=g(a);Ra(c,b);return c}function m(a,b,c){do a.$$listenerCount[c]-=b,0===a.$$listenerCount[c]&&delete a.$$listenerCount[c];while(a=a.$parent)}function n(){}h.prototype={constructor:h,$new:function(a){a?(a=new h,a.$root=this.$root,a.$$asyncQueue=this.$$asyncQueue,a.$$postDigestQueue=
-this.$$postDigestQueue):(a=function(){},a.prototype=this,a=new a,a.$id=bb());a["this"]=a;a.$$listeners={};a.$$listenerCount={};a.$parent=this;a.$$watchers=a.$$nextSibling=a.$$childHead=a.$$childTail=null;a.$$prevSibling=this.$$childTail;this.$$childHead?this.$$childTail=this.$$childTail.$$nextSibling=a:this.$$childHead=this.$$childTail=a;return a},$watch:function(a,b,d){var e=k(a,"watch"),g=this.$$watchers,f={fn:b,last:n,get:e,exp:a,eq:!!d};c=null;if(!P(b)){var h=k(b||C,"listener");f.fn=function(a,
-b,c){h(c)}}if("string"==typeof a&&e.constant){var l=f.fn;f.fn=function(a,b,c){l.call(this,a,b,c);Oa(g,f)}}g||(g=this.$$watchers=[]);g.unshift(f);return function(){Oa(g,f);c=null}},$watchCollection:function(a,b){var c=this,d,e,f,h=1<b.length,l=0,k=g(a),m=[],n={},p=!0,q=0;return this.$watch(function(){d=k(c);var a,b;if(X(d))if(ab(d))for(e!==m&&(e=m,q=e.length=0,l++),a=d.length,q!==a&&(l++,e.length=q=a),b=0;b<a;b++)e[b]!==e[b]&&d[b]!==d[b]||e[b]===d[b]||(l++,e[b]=d[b]);else{e!==n&&(e=n={},q=0,l++);a=
-0;for(b in d)d.hasOwnProperty(b)&&(a++,e.hasOwnProperty(b)?e[b]!==d[b]&&(l++,e[b]=d[b]):(q++,e[b]=d[b],l++));if(q>a)for(b in l++,e)e.hasOwnProperty(b)&&!d.hasOwnProperty(b)&&(q--,delete e[b])}else e!==d&&(e=d,l++);return l},function(){p?(p=!1,b(d,d,c)):b(d,f,c);if(h)if(X(d))if(ab(d)){f=Array(d.length);for(var a=0;a<d.length;a++)f[a]=d[a]}else for(a in f={},d)Fc.call(d,a)&&(f[a]=d[a]);else f=d})},$digest:function(){var d,g,f,h,k=this.$$asyncQueue,m=this.$$postDigestQueue,q,x,s=b,L,Q=[],y,H,R;l("$digest");
-c=null;do{x=!1;for(L=this;k.length;){try{R=k.shift(),R.scope.$eval(R.expression)}catch(B){p.$$phase=null,e(B)}c=null}a:do{if(h=L.$$watchers)for(q=h.length;q--;)try{if(d=h[q])if((g=d.get(L))!==(f=d.last)&&!(d.eq?xa(g,f):"number"==typeof g&&"number"==typeof f&&isNaN(g)&&isNaN(f)))x=!0,c=d,d.last=d.eq?ba(g):g,d.fn(g,f===n?g:f,L),5>s&&(y=4-s,Q[y]||(Q[y]=[]),H=P(d.exp)?"fn: "+(d.exp.name||d.exp.toString()):d.exp,H+="; newVal: "+qa(g)+"; oldVal: "+qa(f),Q[y].push(H));else if(d===c){x=!1;break a}}catch(w){p.$$phase=
-null,e(w)}if(!(h=L.$$childHead||L!==this&&L.$$nextSibling))for(;L!==this&&!(h=L.$$nextSibling);)L=L.$parent}while(L=h);if((x||k.length)&&!s--)throw p.$$phase=null,a("infdig",b,qa(Q));}while(x||k.length);for(p.$$phase=null;m.length;)try{m.shift()()}catch(T){e(T)}},$destroy:function(){if(!this.$$destroyed){var a=this.$parent;this.$broadcast("$destroy");this.$$destroyed=!0;this!==p&&(q(this.$$listenerCount,eb(null,m,this)),a.$$childHead==this&&(a.$$childHead=this.$$nextSibling),a.$$childTail==this&&
-(a.$$childTail=this.$$prevSibling),this.$$prevSibling&&(this.$$prevSibling.$$nextSibling=this.$$nextSibling),this.$$nextSibling&&(this.$$nextSibling.$$prevSibling=this.$$prevSibling),this.$parent=this.$$nextSibling=this.$$prevSibling=this.$$childHead=this.$$childTail=this.$root=null,this.$$listeners={},this.$$watchers=this.$$asyncQueue=this.$$postDigestQueue=[],this.$destroy=this.$digest=this.$apply=C,this.$on=this.$watch=function(){return C})}},$eval:function(a,b){return g(a)(this,b)},$evalAsync:function(a){p.$$phase||
-p.$$asyncQueue.length||f.defer(function(){p.$$asyncQueue.length&&p.$digest()});this.$$asyncQueue.push({scope:this,expression:a})},$$postDigest:function(a){this.$$postDigestQueue.push(a)},$apply:function(a){try{return l("$apply"),this.$eval(a)}catch(b){e(b)}finally{p.$$phase=null;try{p.$digest()}catch(c){throw e(c),c;}}},$on:function(a,b){var c=this.$$listeners[a];c||(this.$$listeners[a]=c=[]);c.push(b);var d=this;do d.$$listenerCount[a]||(d.$$listenerCount[a]=0),d.$$listenerCount[a]++;while(d=d.$parent);
-var e=this;return function(){c[db(c,b)]=null;m(e,1,a)}},$emit:function(a,b){var c=[],d,g=this,f=!1,h={name:a,targetScope:g,stopPropagation:function(){f=!0},preventDefault:function(){h.defaultPrevented=!0},defaultPrevented:!1},l=[h].concat(ya.call(arguments,1)),k,m;do{d=g.$$listeners[a]||c;h.currentScope=g;k=0;for(m=d.length;k<m;k++)if(d[k])try{d[k].apply(null,l)}catch(n){e(n)}else d.splice(k,1),k--,m--;if(f)break;g=g.$parent}while(g);return h},$broadcast:function(a,b){for(var c=this,d=this,g={name:a,
-targetScope:this,preventDefault:function(){g.defaultPrevented=!0},defaultPrevented:!1},f=[g].concat(ya.call(arguments,1)),h,k;c=d;){g.currentScope=c;d=c.$$listeners[a]||[];h=0;for(k=d.length;h<k;h++)if(d[h])try{d[h].apply(null,f)}catch(l){e(l)}else d.splice(h,1),h--,k--;if(!(d=c.$$listenerCount[a]&&c.$$childHead||c!==this&&c.$$nextSibling))for(;c!==this&&!(d=c.$$nextSibling);)c=c.$parent}return g}};var p=new h;return p}]}function bd(){var b=/^\s*(https?|ftp|mailto|tel|file):/,a=/^\s*(https?|ftp|file):|data:image\//;
-this.aHrefSanitizationWhitelist=function(a){return B(a)?(b=a,this):b};this.imgSrcSanitizationWhitelist=function(b){return B(b)?(a=b,this):a};this.$get=function(){return function(c,d){var e=d?a:b,g;if(!S||8<=S)if(g=sa(c).href,""!==g&&!g.match(e))return"unsafe:"+g;return c}}}function Ae(b){if("self"===b)return b;if(w(b)){if(-1<b.indexOf("***"))throw ua("iwcard",b);b=b.replace(/([-()\[\]{}+?*.$\^|,:#<!\\])/g,"\\$1").replace(/\x08/g,"\\x08").replace("\\*\\*",".*").replace("\\*","[^:/.?&;]*");return RegExp("^"+
-b+"$")}if(cb(b))return RegExp("^"+b.source+"$");throw ua("imatcher");}function Gc(b){var a=[];B(b)&&q(b,function(b){a.push(Ae(b))});return a}function ae(){this.SCE_CONTEXTS=ga;var b=["self"],a=[];this.resourceUrlWhitelist=function(a){arguments.length&&(b=Gc(a));return b};this.resourceUrlBlacklist=function(b){arguments.length&&(a=Gc(b));return a};this.$get=["$injector",function(c){function d(a){var b=function(a){this.$$unwrapTrustedValue=function(){return a}};a&&(b.prototype=new a);b.prototype.valueOf=
-function(){return this.$$unwrapTrustedValue()};b.prototype.toString=function(){return this.$$unwrapTrustedValue().toString()};return b}var e=function(a){throw ua("unsafe");};c.has("$sanitize")&&(e=c.get("$sanitize"));var g=d(),f={};f[ga.HTML]=d(g);f[ga.CSS]=d(g);f[ga.URL]=d(g);f[ga.JS]=d(g);f[ga.RESOURCE_URL]=d(f[ga.URL]);return{trustAs:function(a,b){var c=f.hasOwnProperty(a)?f[a]:null;if(!c)throw ua("icontext",a,b);if(null===b||b===s||""===b)return b;if("string"!==typeof b)throw ua("itype",a);return new c(b)},
-getTrusted:function(c,d){if(null===d||d===s||""===d)return d;var g=f.hasOwnProperty(c)?f[c]:null;if(g&&d instanceof g)return d.$$unwrapTrustedValue();if(c===ga.RESOURCE_URL){var g=sa(d.toString()),m,n,p=!1;m=0;for(n=b.length;m<n;m++)if("self"===b[m]?Ib(g):b[m].exec(g.href)){p=!0;break}if(p)for(m=0,n=a.length;m<n;m++)if("self"===a[m]?Ib(g):a[m].exec(g.href)){p=!1;break}if(p)return d;throw ua("insecurl",d.toString());}if(c===ga.HTML)return e(d);throw ua("unsafe");},valueOf:function(a){return a instanceof
-g?a.$$unwrapTrustedValue():a}}}]}function $d(){var b=!0;this.enabled=function(a){arguments.length&&(b=!!a);return b};this.$get=["$parse","$sniffer","$sceDelegate",function(a,c,d){if(b&&c.msie&&8>c.msieDocumentMode)throw ua("iequirks");var e=ba(ga);e.isEnabled=function(){return b};e.trustAs=d.trustAs;e.getTrusted=d.getTrusted;e.valueOf=d.valueOf;b||(e.trustAs=e.getTrusted=function(a,b){return b},e.valueOf=Da);e.parseAs=function(b,c){var d=a(c);return d.literal&&d.constant?d:function(a,c){return e.getTrusted(b,
-d(a,c))}};var g=e.parseAs,f=e.getTrusted,h=e.trustAs;q(ga,function(a,b){var c=K(b);e[Ta("parse_as_"+c)]=function(b){return g(a,b)};e[Ta("get_trusted_"+c)]=function(b){return f(a,b)};e[Ta("trust_as_"+c)]=function(b){return h(a,b)}});return e}]}function be(){this.$get=["$window","$document",function(b,a){var c={},d=Y((/android (\d+)/.exec(K((b.navigator||{}).userAgent))||[])[1]),e=/Boxee/i.test((b.navigator||{}).userAgent),g=a[0]||{},f=g.documentMode,h,l=/^(Moz|webkit|O|ms)(?=[A-Z])/,k=g.body&&g.body.style,
-m=!1,n=!1;if(k){for(var p in k)if(m=l.exec(p)){h=m[0];h=h.substr(0,1).toUpperCase()+h.substr(1);break}h||(h="WebkitOpacity"in k&&"webkit");m=!!("transition"in k||h+"Transition"in k);n=!!("animation"in k||h+"Animation"in k);!d||m&&n||(m=w(g.body.style.webkitTransition),n=w(g.body.style.webkitAnimation))}return{history:!(!b.history||!b.history.pushState||4>d||e),hashchange:"onhashchange"in b&&(!f||7<f),hasEvent:function(a){if("input"==a&&9==S)return!1;if(E(c[a])){var b=g.createElement("div");c[a]="on"+
-a in b}return c[a]},csp:Vb(),vendorPrefix:h,transitions:m,animations:n,android:d,msie:S,msieDocumentMode:f}}]}function de(){this.$get=["$rootScope","$browser","$q","$exceptionHandler",function(b,a,c,d){function e(e,h,l){var k=c.defer(),m=k.promise,n=B(l)&&!l;h=a.defer(function(){try{k.resolve(e())}catch(a){k.reject(a),d(a)}finally{delete g[m.$$timeoutId]}n||b.$apply()},h);m.$$timeoutId=h;g[h]=k;return m}var g={};e.cancel=function(b){return b&&b.$$timeoutId in g?(g[b.$$timeoutId].reject("canceled"),
-delete g[b.$$timeoutId],a.defer.cancel(b.$$timeoutId)):!1};return e}]}function sa(b,a){var c=b;S&&(W.setAttribute("href",c),c=W.href);W.setAttribute("href",c);return{href:W.href,protocol:W.protocol?W.protocol.replace(/:$/,""):"",host:W.host,search:W.search?W.search.replace(/^\?/,""):"",hash:W.hash?W.hash.replace(/^#/,""):"",hostname:W.hostname,port:W.port,pathname:"/"===W.pathname.charAt(0)?W.pathname:"/"+W.pathname}}function Ib(b){b=w(b)?sa(b):b;return b.protocol===Hc.protocol&&b.host===Hc.host}
-function ee(){this.$get=aa(O)}function gc(b){function a(d,e){if(X(d)){var g={};q(d,function(b,c){g[c]=a(c,b)});return g}return b.factory(d+c,e)}var c="Filter";this.register=a;this.$get=["$injector",function(a){return function(b){return a.get(b+c)}}];a("currency",Ic);a("date",Jc);a("filter",Be);a("json",Ce);a("limitTo",De);a("lowercase",Ee);a("number",Kc);a("orderBy",Lc);a("uppercase",Fe)}function Be(){return function(b,a,c){if(!M(b))return b;var d=typeof c,e=[];e.check=function(a){for(var b=0;b<e.length;b++)if(!e[b](a))return!1;
-return!0};"function"!==d&&(c="boolean"===d&&c?function(a,b){return Ea.equals(a,b)}:function(a,b){if(a&&b&&"object"===typeof a&&"object"===typeof b){for(var d in a)if("$"!==d.charAt(0)&&Fc.call(a,d)&&c(a[d],b[d]))return!0;return!1}b=(""+b).toLowerCase();return-1<(""+a).toLowerCase().indexOf(b)});var g=function(a,b){if("string"==typeof b&&"!"===b.charAt(0))return!g(a,b.substr(1));switch(typeof a){case "boolean":case "number":case "string":return c(a,b);case "object":switch(typeof b){case "object":return c(a,
-b);default:for(var d in a)if("$"!==d.charAt(0)&&g(a[d],b))return!0}return!1;case "array":for(d=0;d<a.length;d++)if(g(a[d],b))return!0;return!1;default:return!1}};switch(typeof a){case "boolean":case "number":case "string":a={$:a};case "object":for(var f in a)(function(b){"undefined"!=typeof a[b]&&e.push(function(c){return g("$"==b?c:c&&c[b],a[b])})})(f);break;case "function":e.push(a);break;default:return b}d=[];for(f=0;f<b.length;f++){var h=b[f];e.check(h)&&d.push(h)}return d}}function Ic(b){var a=
-b.NUMBER_FORMATS;return function(b,d){E(d)&&(d=a.CURRENCY_SYM);return Mc(b,a.PATTERNS[1],a.GROUP_SEP,a.DECIMAL_SEP,2).replace(/\u00A4/g,d)}}function Kc(b){var a=b.NUMBER_FORMATS;return function(b,d){return Mc(b,a.PATTERNS[0],a.GROUP_SEP,a.DECIMAL_SEP,d)}}function Mc(b,a,c,d,e){if(null==b||!isFinite(b)||X(b))return"";var g=0>b;b=Math.abs(b);var f=b+"",h="",l=[],k=!1;if(-1!==f.indexOf("e")){var m=f.match(/([\d\.]+)e(-?)(\d+)/);m&&"-"==m[2]&&m[3]>e+1?f="0":(h=f,k=!0)}if(k)0<e&&(-1<b&&1>b)&&(h=b.toFixed(e));
-else{f=(f.split(Nc)[1]||"").length;E(e)&&(e=Math.min(Math.max(a.minFrac,f),a.maxFrac));f=Math.pow(10,e);b=Math.round(b*f)/f;b=(""+b).split(Nc);f=b[0];b=b[1]||"";var m=0,n=a.lgSize,p=a.gSize;if(f.length>=n+p)for(m=f.length-n,k=0;k<m;k++)0===(m-k)%p&&0!==k&&(h+=c),h+=f.charAt(k);for(k=m;k<f.length;k++)0===(f.length-k)%n&&0!==k&&(h+=c),h+=f.charAt(k);for(;b.length<e;)b+="0";e&&"0"!==e&&(h+=d+b.substr(0,e))}l.push(g?a.negPre:a.posPre);l.push(h);l.push(g?a.negSuf:a.posSuf);return l.join("")}function Ob(b,
-a,c){var d="";0>b&&(d="-",b=-b);for(b=""+b;b.length<a;)b="0"+b;c&&(b=b.substr(b.length-a));return d+b}function $(b,a,c,d){c=c||0;return function(e){e=e["get"+b]();if(0<c||e>-c)e+=c;0===e&&-12==c&&(e=12);return Ob(e,a,d)}}function pb(b,a){return function(c,d){var e=c["get"+b](),g=Fa(a?"SHORT"+b:b);return d[g][e]}}function Jc(b){function a(a){var b;if(b=a.match(c)){a=new Date(0);var g=0,f=0,h=b[8]?a.setUTCFullYear:a.setFullYear,l=b[8]?a.setUTCHours:a.setHours;b[9]&&(g=Y(b[9]+b[10]),f=Y(b[9]+b[11]));
-h.call(a,Y(b[1]),Y(b[2])-1,Y(b[3]));g=Y(b[4]||0)-g;f=Y(b[5]||0)-f;h=Y(b[6]||0);b=Math.round(1E3*parseFloat("0."+(b[7]||0)));l.call(a,g,f,h,b)}return a}var c=/^(\d{4})-?(\d\d)-?(\d\d)(?:T(\d\d)(?::?(\d\d)(?::?(\d\d)(?:\.(\d+))?)?)?(Z|([+-])(\d\d):?(\d\d))?)?$/;return function(c,e){var g="",f=[],h,l;e=e||"mediumDate";e=b.DATETIME_FORMATS[e]||e;w(c)&&(c=Ge.test(c)?Y(c):a(c));vb(c)&&(c=new Date(c));if(!Na(c))return c;for(;e;)(l=He.exec(e))?(f=f.concat(ya.call(l,1)),e=f.pop()):(f.push(e),e=null);q(f,function(a){h=
-Ie[a];g+=h?h(c,b.DATETIME_FORMATS):a.replace(/(^'|'$)/g,"").replace(/''/g,"'")});return g}}function Ce(){return function(b){return qa(b,!0)}}function De(){return function(b,a){if(!M(b)&&!w(b))return b;a=Y(a);if(w(b))return a?0<=a?b.slice(0,a):b.slice(a,b.length):"";var c=[],d,e;a>b.length?a=b.length:a<-b.length&&(a=-b.length);0<a?(d=0,e=a):(d=b.length+a,e=b.length);for(;d<e;d++)c.push(b[d]);return c}}function Lc(b){return function(a,c,d){function e(a,b){return Qa(b)?function(b,c){return a(c,b)}:a}
-function g(a,b){var c=typeof a,d=typeof b;return c==d?("string"==c&&(a=a.toLowerCase(),b=b.toLowerCase()),a===b?0:a<b?-1:1):c<d?-1:1}if(!M(a)||!c)return a;c=M(c)?c:[c];c=Uc(c,function(a){var c=!1,d=a||Da;if(w(a)){if("+"==a.charAt(0)||"-"==a.charAt(0))c="-"==a.charAt(0),a=a.substring(1);d=b(a);if(d.constant){var f=d();return e(function(a,b){return g(a[f],b[f])},c)}}return e(function(a,b){return g(d(a),d(b))},c)});for(var f=[],h=0;h<a.length;h++)f.push(a[h]);return f.sort(e(function(a,b){for(var d=
-0;d<c.length;d++){var e=c[d](a,b);if(0!==e)return e}return 0},d))}}function va(b){P(b)&&(b={link:b});b.restrict=b.restrict||"AC";return aa(b)}function Oc(b,a,c,d){function e(a,c){c=c?"-"+fb(c,"-"):"";d.removeClass(b,(a?qb:rb)+c);d.addClass(b,(a?rb:qb)+c)}var g=this,f=b.parent().controller("form")||sb,h=0,l=g.$error={},k=[];g.$name=a.name||a.ngForm;g.$dirty=!1;g.$pristine=!0;g.$valid=!0;g.$invalid=!1;f.$addControl(g);b.addClass(La);e(!0);g.$addControl=function(a){Aa(a.$name,"input");k.push(a);a.$name&&
-(g[a.$name]=a)};g.$removeControl=function(a){a.$name&&g[a.$name]===a&&delete g[a.$name];q(l,function(b,c){g.$setValidity(c,!0,a)});Oa(k,a)};g.$setValidity=function(a,b,c){var d=l[a];if(b)d&&(Oa(d,c),d.length||(h--,h||(e(b),g.$valid=!0,g.$invalid=!1),l[a]=!1,e(!0,a),f.$setValidity(a,!0,g)));else{h||e(b);if(d){if(-1!=db(d,c))return}else l[a]=d=[],h++,e(!1,a),f.$setValidity(a,!1,g);d.push(c);g.$valid=!1;g.$invalid=!0}};g.$setDirty=function(){d.removeClass(b,La);d.addClass(b,tb);g.$dirty=!0;g.$pristine=
-!1;f.$setDirty()};g.$setPristine=function(){d.removeClass(b,tb);d.addClass(b,La);g.$dirty=!1;g.$pristine=!0;q(k,function(a){a.$setPristine()})}}function pa(b,a,c,d){b.$setValidity(a,c);return c?d:s}function Je(b,a,c){var d=c.prop("validity");X(d)&&b.$parsers.push(function(c){if(b.$error[a]||!(d.badInput||d.customError||d.typeMismatch)||d.valueMissing)return c;b.$setValidity(a,!1)})}function ub(b,a,c,d,e,g){var f=a.prop("validity");if(!e.android){var h=!1;a.on("compositionstart",function(a){h=!0});
-a.on("compositionend",function(){h=!1;l()})}var l=function(){if(!h){var e=a.val();Qa(c.ngTrim||"T")&&(e=ca(e));if(d.$viewValue!==e||f&&""===e&&!f.valueMissing)b.$$phase?d.$setViewValue(e):b.$apply(function(){d.$setViewValue(e)})}};if(e.hasEvent("input"))a.on("input",l);else{var k,m=function(){k||(k=g.defer(function(){l();k=null}))};a.on("keydown",function(a){a=a.keyCode;91===a||(15<a&&19>a||37<=a&&40>=a)||m()});if(e.hasEvent("paste"))a.on("paste cut",m)}a.on("change",l);d.$render=function(){a.val(d.$isEmpty(d.$viewValue)?
-"":d.$viewValue)};var n=c.ngPattern;n&&((e=n.match(/^\/(.*)\/([gim]*)$/))?(n=RegExp(e[1],e[2]),e=function(a){return pa(d,"pattern",d.$isEmpty(a)||n.test(a),a)}):e=function(c){var e=b.$eval(n);if(!e||!e.test)throw t("ngPattern")("noregexp",n,e,ha(a));return pa(d,"pattern",d.$isEmpty(c)||e.test(c),c)},d.$formatters.push(e),d.$parsers.push(e));if(c.ngMinlength){var p=Y(c.ngMinlength);e=function(a){return pa(d,"minlength",d.$isEmpty(a)||a.length>=p,a)};d.$parsers.push(e);d.$formatters.push(e)}if(c.ngMaxlength){var r=
-Y(c.ngMaxlength);e=function(a){return pa(d,"maxlength",d.$isEmpty(a)||a.length<=r,a)};d.$parsers.push(e);d.$formatters.push(e)}}function Pb(b,a){b="ngClass"+b;return["$animate",function(c){function d(a,b){var c=[],d=0;a:for(;d<a.length;d++){for(var e=a[d],m=0;m<b.length;m++)if(e==b[m])continue a;c.push(e)}return c}function e(a){if(!M(a)){if(w(a))return a.split(" ");if(X(a)){var b=[];q(a,function(a,c){a&&b.push(c)});return b}}return a}return{restrict:"AC",link:function(g,f,h){function l(a,b){var c=
-f.data("$classCounts")||{},d=[];q(a,function(a){if(0<b||c[a])c[a]=(c[a]||0)+b,c[a]===+(0<b)&&d.push(a)});f.data("$classCounts",c);return d.join(" ")}function k(b){if(!0===a||g.$index%2===a){var k=e(b||[]);if(!m){var r=l(k,1);h.$addClass(r)}else if(!xa(b,m)){var q=e(m),r=d(k,q),k=d(q,k),k=l(k,-1),r=l(r,1);0===r.length?c.removeClass(f,k):0===k.length?c.addClass(f,r):c.setClass(f,r,k)}}m=ba(b)}var m;g.$watch(h[b],k,!0);h.$observe("class",function(a){k(g.$eval(h[b]))});"ngClass"!==b&&g.$watch("$index",
-function(c,d){var f=c&1;if(f!==d&1){var k=e(g.$eval(h[b]));f===a?(f=l(k,1),h.$addClass(f)):(f=l(k,-1),h.$removeClass(f))}})}}}]}var K=function(b){return w(b)?b.toLowerCase():b},Fc=Object.prototype.hasOwnProperty,Fa=function(b){return w(b)?b.toUpperCase():b},S,y,Ga,ya=[].slice,Ke=[].push,wa=Object.prototype.toString,Pa=t("ng"),Ea=O.angular||(O.angular={}),Sa,Ka,ka=["0","0","0"];S=Y((/msie (\d+)/.exec(K(navigator.userAgent))||[])[1]);isNaN(S)&&(S=Y((/trident\/.*; rv:(\d+)/.exec(K(navigator.userAgent))||
-[])[1]));C.$inject=[];Da.$inject=[];var ca=function(){return String.prototype.trim?function(b){return w(b)?b.trim():b}:function(b){return w(b)?b.replace(/^\s\s*/,"").replace(/\s\s*$/,""):b}}();Ka=9>S?function(b){b=b.nodeName?b:b[0];return b.scopeName&&"HTML"!=b.scopeName?Fa(b.scopeName+":"+b.nodeName):b.nodeName}:function(b){return b.nodeName?b.nodeName:b[0].nodeName};var Xc=/[A-Z]/g,$c={full:"1.2.16",major:1,minor:2,dot:16,codeName:"badger-enumeration"},Ua=N.cache={},gb=N.expando="ng-"+(new Date).getTime(),
-me=1,Pc=O.document.addEventListener?function(b,a,c){b.addEventListener(a,c,!1)}:function(b,a,c){b.attachEvent("on"+a,c)},Fb=O.document.removeEventListener?function(b,a,c){b.removeEventListener(a,c,!1)}:function(b,a,c){b.detachEvent("on"+a,c)};N._data=function(b){return this.cache[b[this.expando]]||{}};var he=/([\:\-\_]+(.))/g,ie=/^moz([A-Z])/,Bb=t("jqLite"),je=/^<(\w+)\s*\/?>(?:<\/\1>|)$/,Cb=/<|&#?\w+;/,ke=/<([\w:]+)/,le=/<(?!area|br|col|embed|hr|img|input|link|meta|param)(([\w:]+)[^>]*)\/>/gi,ea=
-{option:[1,'<select multiple="multiple">',"</select>"],thead:[1,"<table>","</table>"],col:[2,"<table><colgroup>","</colgroup></table>"],tr:[2,"<table><tbody>","</tbody></table>"],td:[3,"<table><tbody><tr>","</tr></tbody></table>"],_default:[0,"",""]};ea.optgroup=ea.option;ea.tbody=ea.tfoot=ea.colgroup=ea.caption=ea.thead;ea.th=ea.td;var Ja=N.prototype={ready:function(b){function a(){c||(c=!0,b())}var c=!1;"complete"===U.readyState?setTimeout(a):(this.on("DOMContentLoaded",a),N(O).on("load",a))},toString:function(){var b=
-[];q(this,function(a){b.push(""+a)});return"["+b.join(", ")+"]"},eq:function(b){return 0<=b?y(this[b]):y(this[this.length+b])},length:0,push:Ke,sort:[].sort,splice:[].splice},kb={};q("multiple selected checked disabled readOnly required open".split(" "),function(b){kb[K(b)]=b});var nc={};q("input select option textarea button form details".split(" "),function(b){nc[Fa(b)]=!0});q({data:jc,inheritedData:jb,scope:function(b){return y(b).data("$scope")||jb(b.parentNode||b,["$isolateScope","$scope"])},
-isolateScope:function(b){return y(b).data("$isolateScope")||y(b).data("$isolateScopeNoTemplate")},controller:kc,injector:function(b){return jb(b,"$injector")},removeAttr:function(b,a){b.removeAttribute(a)},hasClass:Gb,css:function(b,a,c){a=Ta(a);if(B(c))b.style[a]=c;else{var d;8>=S&&(d=b.currentStyle&&b.currentStyle[a],""===d&&(d="auto"));d=d||b.style[a];8>=S&&(d=""===d?s:d);return d}},attr:function(b,a,c){var d=K(a);if(kb[d])if(B(c))c?(b[a]=!0,b.setAttribute(a,d)):(b[a]=!1,b.removeAttribute(d));
-else return b[a]||(b.attributes.getNamedItem(a)||C).specified?d:s;else if(B(c))b.setAttribute(a,c);else if(b.getAttribute)return b=b.getAttribute(a,2),null===b?s:b},prop:function(b,a,c){if(B(c))b[a]=c;else return b[a]},text:function(){function b(b,d){var e=a[b.nodeType];if(E(d))return e?b[e]:"";b[e]=d}var a=[];9>S?(a[1]="innerText",a[3]="nodeValue"):a[1]=a[3]="textContent";b.$dv="";return b}(),val:function(b,a){if(E(a)){if("SELECT"===Ka(b)&&b.multiple){var c=[];q(b.options,function(a){a.selected&&
-c.push(a.value||a.text)});return 0===c.length?null:c}return b.value}b.value=a},html:function(b,a){if(E(a))return b.innerHTML;for(var c=0,d=b.childNodes;c<d.length;c++)Ha(d[c]);b.innerHTML=a},empty:lc},function(b,a){N.prototype[a]=function(a,d){var e,g;if(b!==lc&&(2==b.length&&b!==Gb&&b!==kc?a:d)===s){if(X(a)){for(e=0;e<this.length;e++)if(b===jc)b(this[e],a);else for(g in a)b(this[e],g,a[g]);return this}e=b.$dv;g=e===s?Math.min(this.length,1):this.length;for(var f=0;f<g;f++){var h=b(this[f],a,d);e=
-e?e+h:h}return e}for(e=0;e<this.length;e++)b(this[e],a,d);return this}});q({removeData:hc,dealoc:Ha,on:function a(c,d,e,g){if(B(g))throw Bb("onargs");var f=la(c,"events"),h=la(c,"handle");f||la(c,"events",f={});h||la(c,"handle",h=ne(c,f));q(d.split(" "),function(d){var g=f[d];if(!g){if("mouseenter"==d||"mouseleave"==d){var m=U.body.contains||U.body.compareDocumentPosition?function(a,c){var d=9===a.nodeType?a.documentElement:a,e=c&&c.parentNode;return a===e||!!(e&&1===e.nodeType&&(d.contains?d.contains(e):
-a.compareDocumentPosition&&a.compareDocumentPosition(e)&16))}:function(a,c){if(c)for(;c=c.parentNode;)if(c===a)return!0;return!1};f[d]=[];a(c,{mouseleave:"mouseout",mouseenter:"mouseover"}[d],function(a){var c=a.relatedTarget;c&&(c===this||m(this,c))||h(a,d)})}else Pc(c,d,h),f[d]=[];g=f[d]}g.push(e)})},off:ic,one:function(a,c,d){a=y(a);a.on(c,function g(){a.off(c,d);a.off(c,g)});a.on(c,d)},replaceWith:function(a,c){var d,e=a.parentNode;Ha(a);q(new N(c),function(c){d?e.insertBefore(c,d.nextSibling):
-e.replaceChild(c,a);d=c})},children:function(a){var c=[];q(a.childNodes,function(a){1===a.nodeType&&c.push(a)});return c},contents:function(a){return a.contentDocument||a.childNodes||[]},append:function(a,c){q(new N(c),function(c){1!==a.nodeType&&11!==a.nodeType||a.appendChild(c)})},prepend:function(a,c){if(1===a.nodeType){var d=a.firstChild;q(new N(c),function(c){a.insertBefore(c,d)})}},wrap:function(a,c){c=y(c)[0];var d=a.parentNode;d&&d.replaceChild(c,a);c.appendChild(a)},remove:function(a){Ha(a);
-var c=a.parentNode;c&&c.removeChild(a)},after:function(a,c){var d=a,e=a.parentNode;q(new N(c),function(a){e.insertBefore(a,d.nextSibling);d=a})},addClass:ib,removeClass:hb,toggleClass:function(a,c,d){c&&q(c.split(" "),function(c){var g=d;E(g)&&(g=!Gb(a,c));(g?ib:hb)(a,c)})},parent:function(a){return(a=a.parentNode)&&11!==a.nodeType?a:null},next:function(a){if(a.nextElementSibling)return a.nextElementSibling;for(a=a.nextSibling;null!=a&&1!==a.nodeType;)a=a.nextSibling;return a},find:function(a,c){return a.getElementsByTagName?
-a.getElementsByTagName(c):[]},clone:Eb,triggerHandler:function(a,c,d){c=(la(a,"events")||{})[c];d=d||[];var e=[{preventDefault:C,stopPropagation:C}];q(c,function(c){c.apply(a,e.concat(d))})}},function(a,c){N.prototype[c]=function(c,e,g){for(var f,h=0;h<this.length;h++)E(f)?(f=a(this[h],c,e,g),B(f)&&(f=y(f))):Db(f,a(this[h],c,e,g));return B(f)?f:this};N.prototype.bind=N.prototype.on;N.prototype.unbind=N.prototype.off});Va.prototype={put:function(a,c){this[Ia(a)]=c},get:function(a){return this[Ia(a)]},
-remove:function(a){var c=this[a=Ia(a)];delete this[a];return c}};var pe=/^function\s*[^\(]*\(\s*([^\)]*)\)/m,qe=/,/,re=/^\s*(_?)(\S+?)\1\s*$/,oe=/((\/\/.*$)|(\/\*[\s\S]*?\*\/))/mg,Wa=t("$injector"),Le=t("$animate"),Ld=["$provide",function(a){this.$$selectors={};this.register=function(c,d){var e=c+"-animation";if(c&&"."!=c.charAt(0))throw Le("notcsel",c);this.$$selectors[c.substr(1)]=e;a.factory(e,d)};this.classNameFilter=function(a){1===arguments.length&&(this.$$classNameFilter=a instanceof RegExp?
-a:null);return this.$$classNameFilter};this.$get=["$timeout","$$asyncCallback",function(a,d){return{enter:function(a,c,f,h){f?f.after(a):(c&&c[0]||(c=f.parent()),c.append(a));h&&d(h)},leave:function(a,c){a.remove();c&&d(c)},move:function(a,c,d,h){this.enter(a,c,d,h)},addClass:function(a,c,f){c=w(c)?c:M(c)?c.join(" "):"";q(a,function(a){ib(a,c)});f&&d(f)},removeClass:function(a,c,f){c=w(c)?c:M(c)?c.join(" "):"";q(a,function(a){hb(a,c)});f&&d(f)},setClass:function(a,c,f,h){q(a,function(a){ib(a,c);hb(a,
-f)});h&&d(h)},enabled:C}}]}],ja=t("$compile");cc.$inject=["$provide","$$sanitizeUriProvider"];var te=/^(x[\:\-_]|data[\:\-_])/i,vc=t("$interpolate"),Me=/^([^\?#]*)(\?([^#]*))?(#(.*))?$/,we={http:80,https:443,ftp:21},Kb=t("$location");Ac.prototype=Lb.prototype=zc.prototype={$$html5:!1,$$replace:!1,absUrl:nb("$$absUrl"),url:function(a,c){if(E(a))return this.$$url;var d=Me.exec(a);d[1]&&this.path(decodeURIComponent(d[1]));(d[2]||d[1])&&this.search(d[3]||"");this.hash(d[5]||"",c);return this},protocol:nb("$$protocol"),
-host:nb("$$host"),port:nb("$$port"),path:Bc("$$path",function(a){return"/"==a.charAt(0)?a:"/"+a}),search:function(a,c){switch(arguments.length){case 0:return this.$$search;case 1:if(w(a))this.$$search=Yb(a);else if(X(a))this.$$search=a;else throw Kb("isrcharg");break;default:E(c)||null===c?delete this.$$search[a]:this.$$search[a]=c}this.$$compose();return this},hash:Bc("$$hash",Da),replace:function(){this.$$replace=!0;return this}};var Ba=t("$parse"),Ec={},ta,Ma={"null":function(){return null},"true":function(){return!0},
-"false":function(){return!1},undefined:C,"+":function(a,c,d,e){d=d(a,c);e=e(a,c);return B(d)?B(e)?d+e:d:B(e)?e:s},"-":function(a,c,d,e){d=d(a,c);e=e(a,c);return(B(d)?d:0)-(B(e)?e:0)},"*":function(a,c,d,e){return d(a,c)*e(a,c)},"/":function(a,c,d,e){return d(a,c)/e(a,c)},"%":function(a,c,d,e){return d(a,c)%e(a,c)},"^":function(a,c,d,e){return d(a,c)^e(a,c)},"=":C,"===":function(a,c,d,e){return d(a,c)===e(a,c)},"!==":function(a,c,d,e){return d(a,c)!==e(a,c)},"==":function(a,c,d,e){return d(a,c)==e(a,
-c)},"!=":function(a,c,d,e){return d(a,c)!=e(a,c)},"<":function(a,c,d,e){return d(a,c)<e(a,c)},">":function(a,c,d,e){return d(a,c)>e(a,c)},"<=":function(a,c,d,e){return d(a,c)<=e(a,c)},">=":function(a,c,d,e){return d(a,c)>=e(a,c)},"&&":function(a,c,d,e){return d(a,c)&&e(a,c)},"||":function(a,c,d,e){return d(a,c)||e(a,c)},"&":function(a,c,d,e){return d(a,c)&e(a,c)},"|":function(a,c,d,e){return e(a,c)(a,c,d(a,c))},"!":function(a,c,d){return!d(a,c)}},Ne={n:"\n",f:"\f",r:"\r",t:"\t",v:"\v","'":"'",'"':'"'},
-Nb=function(a){this.options=a};Nb.prototype={constructor:Nb,lex:function(a){this.text=a;this.index=0;this.ch=s;this.lastCh=":";this.tokens=[];var c;for(a=[];this.index<this.text.length;){this.ch=this.text.charAt(this.index);if(this.is("\"'"))this.readString(this.ch);else if(this.isNumber(this.ch)||this.is(".")&&this.isNumber(this.peek()))this.readNumber();else if(this.isIdent(this.ch))this.readIdent(),this.was("{,")&&("{"===a[0]&&(c=this.tokens[this.tokens.length-1]))&&(c.json=-1===c.text.indexOf("."));
-else if(this.is("(){}[].,;:?"))this.tokens.push({index:this.index,text:this.ch,json:this.was(":[,")&&this.is("{[")||this.is("}]:,")}),this.is("{[")&&a.unshift(this.ch),this.is("}]")&&a.shift(),this.index++;else if(this.isWhitespace(this.ch)){this.index++;continue}else{var d=this.ch+this.peek(),e=d+this.peek(2),g=Ma[this.ch],f=Ma[d],h=Ma[e];h?(this.tokens.push({index:this.index,text:e,fn:h}),this.index+=3):f?(this.tokens.push({index:this.index,text:d,fn:f}),this.index+=2):g?(this.tokens.push({index:this.index,
-text:this.ch,fn:g,json:this.was("[,:")&&this.is("+-")}),this.index+=1):this.throwError("Unexpected next character ",this.index,this.index+1)}this.lastCh=this.ch}return this.tokens},is:function(a){return-1!==a.indexOf(this.ch)},was:function(a){return-1!==a.indexOf(this.lastCh)},peek:function(a){a=a||1;return this.index+a<this.text.length?this.text.charAt(this.index+a):!1},isNumber:function(a){return"0"<=a&&"9">=a},isWhitespace:function(a){return" "===a||"\r"===a||"\t"===a||"\n"===a||"\v"===a||"\u00a0"===
-a},isIdent:function(a){return"a"<=a&&"z">=a||"A"<=a&&"Z">=a||"_"===a||"$"===a},isExpOperator:function(a){return"-"===a||"+"===a||this.isNumber(a)},throwError:function(a,c,d){d=d||this.index;c=B(c)?"s "+c+"-"+this.index+" ["+this.text.substring(c,d)+"]":" "+d;throw Ba("lexerr",a,c,this.text);},readNumber:function(){for(var a="",c=this.index;this.index<this.text.length;){var d=K(this.text.charAt(this.index));if("."==d||this.isNumber(d))a+=d;else{var e=this.peek();if("e"==d&&this.isExpOperator(e))a+=
-d;else if(this.isExpOperator(d)&&e&&this.isNumber(e)&&"e"==a.charAt(a.length-1))a+=d;else if(!this.isExpOperator(d)||e&&this.isNumber(e)||"e"!=a.charAt(a.length-1))break;else this.throwError("Invalid exponent")}this.index++}a*=1;this.tokens.push({index:c,text:a,json:!0,fn:function(){return a}})},readIdent:function(){for(var a=this,c="",d=this.index,e,g,f,h;this.index<this.text.length;){h=this.text.charAt(this.index);if("."===h||this.isIdent(h)||this.isNumber(h))"."===h&&(e=this.index),c+=h;else break;
-this.index++}if(e)for(g=this.index;g<this.text.length;){h=this.text.charAt(g);if("("===h){f=c.substr(e-d+1);c=c.substr(0,e-d);this.index=g;break}if(this.isWhitespace(h))g++;else break}d={index:d,text:c};if(Ma.hasOwnProperty(c))d.fn=Ma[c],d.json=Ma[c];else{var l=Dc(c,this.options,this.text);d.fn=D(function(a,c){return l(a,c)},{assign:function(d,e){return ob(d,c,e,a.text,a.options)}})}this.tokens.push(d);f&&(this.tokens.push({index:e,text:".",json:!1}),this.tokens.push({index:e+1,text:f,json:!1}))},
-readString:function(a){var c=this.index;this.index++;for(var d="",e=a,g=!1;this.index<this.text.length;){var f=this.text.charAt(this.index),e=e+f;if(g)"u"===f?(f=this.text.substring(this.index+1,this.index+5),f.match(/[\da-f]{4}/i)||this.throwError("Invalid unicode escape [\\u"+f+"]"),this.index+=4,d+=String.fromCharCode(parseInt(f,16))):d=(g=Ne[f])?d+g:d+f,g=!1;else if("\\"===f)g=!0;else{if(f===a){this.index++;this.tokens.push({index:c,text:e,string:d,json:!0,fn:function(){return d}});return}d+=
-f}this.index++}this.throwError("Unterminated quote",c)}};var $a=function(a,c,d){this.lexer=a;this.$filter=c;this.options=d};$a.ZERO=D(function(){return 0},{constant:!0});$a.prototype={constructor:$a,parse:function(a,c){this.text=a;this.json=c;this.tokens=this.lexer.lex(a);c&&(this.assignment=this.logicalOR,this.functionCall=this.fieldAccess=this.objectIndex=this.filterChain=function(){this.throwError("is not valid json",{text:a,index:0})});var d=c?this.primary():this.statements();0!==this.tokens.length&&
-this.throwError("is an unexpected token",this.tokens[0]);d.literal=!!d.literal;d.constant=!!d.constant;return d},primary:function(){var a;if(this.expect("("))a=this.filterChain(),this.consume(")");else if(this.expect("["))a=this.arrayDeclaration();else if(this.expect("{"))a=this.object();else{var c=this.expect();(a=c.fn)||this.throwError("not a primary expression",c);c.json&&(a.constant=!0,a.literal=!0)}for(var d;c=this.expect("(","[",".");)"("===c.text?(a=this.functionCall(a,d),d=null):"["===c.text?
-(d=a,a=this.objectIndex(a)):"."===c.text?(d=a,a=this.fieldAccess(a)):this.throwError("IMPOSSIBLE");return a},throwError:function(a,c){throw Ba("syntax",c.text,a,c.index+1,this.text,this.text.substring(c.index));},peekToken:function(){if(0===this.tokens.length)throw Ba("ueoe",this.text);return this.tokens[0]},peek:function(a,c,d,e){if(0<this.tokens.length){var g=this.tokens[0],f=g.text;if(f===a||f===c||f===d||f===e||!(a||c||d||e))return g}return!1},expect:function(a,c,d,e){return(a=this.peek(a,c,d,
-e))?(this.json&&!a.json&&this.throwError("is not valid json",a),this.tokens.shift(),a):!1},consume:function(a){this.expect(a)||this.throwError("is unexpected, expecting ["+a+"]",this.peek())},unaryFn:function(a,c){return D(function(d,e){return a(d,e,c)},{constant:c.constant})},ternaryFn:function(a,c,d){return D(function(e,g){return a(e,g)?c(e,g):d(e,g)},{constant:a.constant&&c.constant&&d.constant})},binaryFn:function(a,c,d){return D(function(e,g){return c(e,g,a,d)},{constant:a.constant&&d.constant})},
-statements:function(){for(var a=[];;)if(0<this.tokens.length&&!this.peek("}",")",";","]")&&a.push(this.filterChain()),!this.expect(";"))return 1===a.length?a[0]:function(c,d){for(var e,g=0;g<a.length;g++){var f=a[g];f&&(e=f(c,d))}return e}},filterChain:function(){for(var a=this.expression(),c;;)if(c=this.expect("|"))a=this.binaryFn(a,c.fn,this.filter());else return a},filter:function(){for(var a=this.expect(),c=this.$filter(a.text),d=[];;)if(a=this.expect(":"))d.push(this.expression());else{var e=
-function(a,e,h){h=[h];for(var l=0;l<d.length;l++)h.push(d[l](a,e));return c.apply(a,h)};return function(){return e}}},expression:function(){return this.assignment()},assignment:function(){var a=this.ternary(),c,d;return(d=this.expect("="))?(a.assign||this.throwError("implies assignment but ["+this.text.substring(0,d.index)+"] can not be assigned to",d),c=this.ternary(),function(d,g){return a.assign(d,c(d,g),g)}):a},ternary:function(){var a=this.logicalOR(),c,d;if(this.expect("?")){c=this.ternary();
-if(d=this.expect(":"))return this.ternaryFn(a,c,this.ternary());this.throwError("expected :",d)}else return a},logicalOR:function(){for(var a=this.logicalAND(),c;;)if(c=this.expect("||"))a=this.binaryFn(a,c.fn,this.logicalAND());else return a},logicalAND:function(){var a=this.equality(),c;if(c=this.expect("&&"))a=this.binaryFn(a,c.fn,this.logicalAND());return a},equality:function(){var a=this.relational(),c;if(c=this.expect("==","!=","===","!=="))a=this.binaryFn(a,c.fn,this.equality());return a},
-relational:function(){var a=this.additive(),c;if(c=this.expect("<",">","<=",">="))a=this.binaryFn(a,c.fn,this.relational());return a},additive:function(){for(var a=this.multiplicative(),c;c=this.expect("+","-");)a=this.binaryFn(a,c.fn,this.multiplicative());return a},multiplicative:function(){for(var a=this.unary(),c;c=this.expect("*","/","%");)a=this.binaryFn(a,c.fn,this.unary());return a},unary:function(){var a;return this.expect("+")?this.primary():(a=this.expect("-"))?this.binaryFn($a.ZERO,a.fn,
-this.unary()):(a=this.expect("!"))?this.unaryFn(a.fn,this.unary()):this.primary()},fieldAccess:function(a){var c=this,d=this.expect().text,e=Dc(d,this.options,this.text);return D(function(c,d,h){return e(h||a(c,d))},{assign:function(e,f,h){return ob(a(e,h),d,f,c.text,c.options)}})},objectIndex:function(a){var c=this,d=this.expression();this.consume("]");return D(function(e,g){var f=a(e,g),h=d(e,g),l;if(!f)return s;(f=Za(f[h],c.text))&&(f.then&&c.options.unwrapPromises)&&(l=f,"$$v"in f||(l.$$v=s,l.then(function(a){l.$$v=
-a})),f=f.$$v);return f},{assign:function(e,g,f){var h=d(e,f);return Za(a(e,f),c.text)[h]=g}})},functionCall:function(a,c){var d=[];if(")"!==this.peekToken().text){do d.push(this.expression());while(this.expect(","))}this.consume(")");var e=this;return function(g,f){for(var h=[],l=c?c(g,f):g,k=0;k<d.length;k++)h.push(d[k](g,f));k=a(g,f,l)||C;Za(l,e.text);Za(k,e.text);h=k.apply?k.apply(l,h):k(h[0],h[1],h[2],h[3],h[4]);return Za(h,e.text)}},arrayDeclaration:function(){var a=[],c=!0;if("]"!==this.peekToken().text){do{if(this.peek("]"))break;
-var d=this.expression();a.push(d);d.constant||(c=!1)}while(this.expect(","))}this.consume("]");return D(function(c,d){for(var f=[],h=0;h<a.length;h++)f.push(a[h](c,d));return f},{literal:!0,constant:c})},object:function(){var a=[],c=!0;if("}"!==this.peekToken().text){do{if(this.peek("}"))break;var d=this.expect(),d=d.string||d.text;this.consume(":");var e=this.expression();a.push({key:d,value:e});e.constant||(c=!1)}while(this.expect(","))}this.consume("}");return D(function(c,d){for(var e={},l=0;l<
-a.length;l++){var k=a[l];e[k.key]=k.value(c,d)}return e},{literal:!0,constant:c})}};var Mb={},ua=t("$sce"),ga={HTML:"html",CSS:"css",URL:"url",RESOURCE_URL:"resourceUrl",JS:"js"},W=U.createElement("a"),Hc=sa(O.location.href,!0);gc.$inject=["$provide"];Ic.$inject=["$locale"];Kc.$inject=["$locale"];var Nc=".",Ie={yyyy:$("FullYear",4),yy:$("FullYear",2,0,!0),y:$("FullYear",1),MMMM:pb("Month"),MMM:pb("Month",!0),MM:$("Month",2,1),M:$("Month",1,1),dd:$("Date",2),d:$("Date",1),HH:$("Hours",2),H:$("Hours",
-1),hh:$("Hours",2,-12),h:$("Hours",1,-12),mm:$("Minutes",2),m:$("Minutes",1),ss:$("Seconds",2),s:$("Seconds",1),sss:$("Milliseconds",3),EEEE:pb("Day"),EEE:pb("Day",!0),a:function(a,c){return 12>a.getHours()?c.AMPMS[0]:c.AMPMS[1]},Z:function(a){a=-1*a.getTimezoneOffset();return a=(0<=a?"+":"")+(Ob(Math[0<a?"floor":"ceil"](a/60),2)+Ob(Math.abs(a%60),2))}},He=/((?:[^yMdHhmsaZE']+)|(?:'(?:[^']|'')*')|(?:E+|y+|M+|d+|H+|h+|m+|s+|a|Z))(.*)/,Ge=/^\-?\d+$/;Jc.$inject=["$locale"];var Ee=aa(K),Fe=aa(Fa);Lc.$inject=
-["$parse"];var cd=aa({restrict:"E",compile:function(a,c){8>=S&&(c.href||c.name||c.$set("href",""),a.append(U.createComment("IE fix")));if(!c.href&&!c.xlinkHref&&!c.name)return function(a,c){var g="[object SVGAnimatedString]"===wa.call(c.prop("href"))?"xlink:href":"href";c.on("click",function(a){c.attr(g)||a.preventDefault()})}}}),zb={};q(kb,function(a,c){if("multiple"!=a){var d=na("ng-"+c);zb[d]=function(){return{priority:100,link:function(a,g,f){a.$watch(f[d],function(a){f.$set(c,!!a)})}}}}});q(["src",
-"srcset","href"],function(a){var c=na("ng-"+a);zb[c]=function(){return{priority:99,link:function(d,e,g){var f=a,h=a;"href"===a&&"[object SVGAnimatedString]"===wa.call(e.prop("href"))&&(h="xlinkHref",g.$attr[h]="xlink:href",f=null);g.$observe(c,function(a){a&&(g.$set(h,a),S&&f&&e.prop(f,g[h]))})}}}});var sb={$addControl:C,$removeControl:C,$setValidity:C,$setDirty:C,$setPristine:C};Oc.$inject=["$element","$attrs","$scope","$animate"];var Qc=function(a){return["$timeout",function(c){return{name:"form",
-restrict:a?"EAC":"E",controller:Oc,compile:function(){return{pre:function(a,e,g,f){if(!g.action){var h=function(a){a.preventDefault?a.preventDefault():a.returnValue=!1};Pc(e[0],"submit",h);e.on("$destroy",function(){c(function(){Fb(e[0],"submit",h)},0,!1)})}var l=e.parent().controller("form"),k=g.name||g.ngForm;k&&ob(a,k,f,k);if(l)e.on("$destroy",function(){l.$removeControl(f);k&&ob(a,k,s,k);D(f,sb)})}}}}}]},dd=Qc(),qd=Qc(!0),Oe=/^(ftp|http|https):\/\/(\w+:{0,1}\w*@)?(\S+)(:[0-9]+)?(\/|\/([\w#!:.?+=&%@!\-\/]))?$/,
-Pe=/^[a-z0-9!#$%&'*+/=?^_`{|}~.-]+@[a-z0-9-]+(\.[a-z0-9-]+)*$/i,Qe=/^\s*(\-|\+)?(\d+|(\d*(\.\d*)))\s*$/,Rc={text:ub,number:function(a,c,d,e,g,f){ub(a,c,d,e,g,f);e.$parsers.push(function(a){var c=e.$isEmpty(a);if(c||Qe.test(a))return e.$setValidity("number",!0),""===a?null:c?a:parseFloat(a);e.$setValidity("number",!1);return s});Je(e,"number",c);e.$formatters.push(function(a){return e.$isEmpty(a)?"":""+a});d.min&&(a=function(a){var c=parseFloat(d.min);return pa(e,"min",e.$isEmpty(a)||a>=c,a)},e.$parsers.push(a),
-e.$formatters.push(a));d.max&&(a=function(a){var c=parseFloat(d.max);return pa(e,"max",e.$isEmpty(a)||a<=c,a)},e.$parsers.push(a),e.$formatters.push(a));e.$formatters.push(function(a){return pa(e,"number",e.$isEmpty(a)||vb(a),a)})},url:function(a,c,d,e,g,f){ub(a,c,d,e,g,f);a=function(a){return pa(e,"url",e.$isEmpty(a)||Oe.test(a),a)};e.$formatters.push(a);e.$parsers.push(a)},email:function(a,c,d,e,g,f){ub(a,c,d,e,g,f);a=function(a){return pa(e,"email",e.$isEmpty(a)||Pe.test(a),a)};e.$formatters.push(a);
-e.$parsers.push(a)},radio:function(a,c,d,e){E(d.name)&&c.attr("name",bb());c.on("click",function(){c[0].checked&&a.$apply(function(){e.$setViewValue(d.value)})});e.$render=function(){c[0].checked=d.value==e.$viewValue};d.$observe("value",e.$render)},checkbox:function(a,c,d,e){var g=d.ngTrueValue,f=d.ngFalseValue;w(g)||(g=!0);w(f)||(f=!1);c.on("click",function(){a.$apply(function(){e.$setViewValue(c[0].checked)})});e.$render=function(){c[0].checked=e.$viewValue};e.$isEmpty=function(a){return a!==g};
-e.$formatters.push(function(a){return a===g});e.$parsers.push(function(a){return a?g:f})},hidden:C,button:C,submit:C,reset:C,file:C},dc=["$browser","$sniffer",function(a,c){return{restrict:"E",require:"?ngModel",link:function(d,e,g,f){f&&(Rc[K(g.type)]||Rc.text)(d,e,g,f,c,a)}}}],rb="ng-valid",qb="ng-invalid",La="ng-pristine",tb="ng-dirty",Re=["$scope","$exceptionHandler","$attrs","$element","$parse","$animate",function(a,c,d,e,g,f){function h(a,c){c=c?"-"+fb(c,"-"):"";f.removeClass(e,(a?qb:rb)+c);
-f.addClass(e,(a?rb:qb)+c)}this.$modelValue=this.$viewValue=Number.NaN;this.$parsers=[];this.$formatters=[];this.$viewChangeListeners=[];this.$pristine=!0;this.$dirty=!1;this.$valid=!0;this.$invalid=!1;this.$name=d.name;var l=g(d.ngModel),k=l.assign;if(!k)throw t("ngModel")("nonassign",d.ngModel,ha(e));this.$render=C;this.$isEmpty=function(a){return E(a)||""===a||null===a||a!==a};var m=e.inheritedData("$formController")||sb,n=0,p=this.$error={};e.addClass(La);h(!0);this.$setValidity=function(a,c){p[a]!==
-!c&&(c?(p[a]&&n--,n||(h(!0),this.$valid=!0,this.$invalid=!1)):(h(!1),this.$invalid=!0,this.$valid=!1,n++),p[a]=!c,h(c,a),m.$setValidity(a,c,this))};this.$setPristine=function(){this.$dirty=!1;this.$pristine=!0;f.removeClass(e,tb);f.addClass(e,La)};this.$setViewValue=function(d){this.$viewValue=d;this.$pristine&&(this.$dirty=!0,this.$pristine=!1,f.removeClass(e,La),f.addClass(e,tb),m.$setDirty());q(this.$parsers,function(a){d=a(d)});this.$modelValue!==d&&(this.$modelValue=d,k(a,d),q(this.$viewChangeListeners,
-function(a){try{a()}catch(d){c(d)}}))};var r=this;a.$watch(function(){var c=l(a);if(r.$modelValue!==c){var d=r.$formatters,e=d.length;for(r.$modelValue=c;e--;)c=d[e](c);r.$viewValue!==c&&(r.$viewValue=c,r.$render())}return c})}],Fd=function(){return{require:["ngModel","^?form"],controller:Re,link:function(a,c,d,e){var g=e[0],f=e[1]||sb;f.$addControl(g);a.$on("$destroy",function(){f.$removeControl(g)})}}},Hd=aa({require:"ngModel",link:function(a,c,d,e){e.$viewChangeListeners.push(function(){a.$eval(d.ngChange)})}}),
-ec=function(){return{require:"?ngModel",link:function(a,c,d,e){if(e){d.required=!0;var g=function(a){if(d.required&&e.$isEmpty(a))e.$setValidity("required",!1);else return e.$setValidity("required",!0),a};e.$formatters.push(g);e.$parsers.unshift(g);d.$observe("required",function(){g(e.$viewValue)})}}}},Gd=function(){return{require:"ngModel",link:function(a,c,d,e){var g=(a=/\/(.*)\//.exec(d.ngList))&&RegExp(a[1])||d.ngList||",";e.$parsers.push(function(a){if(!E(a)){var c=[];a&&q(a.split(g),function(a){a&&
-c.push(ca(a))});return c}});e.$formatters.push(function(a){return M(a)?a.join(", "):s});e.$isEmpty=function(a){return!a||!a.length}}}},Se=/^(true|false|\d+)$/,Id=function(){return{priority:100,compile:function(a,c){return Se.test(c.ngValue)?function(a,c,g){g.$set("value",a.$eval(g.ngValue))}:function(a,c,g){a.$watch(g.ngValue,function(a){g.$set("value",a)})}}}},id=va(function(a,c,d){c.addClass("ng-binding").data("$binding",d.ngBind);a.$watch(d.ngBind,function(a){c.text(a==s?"":a)})}),kd=["$interpolate",
-function(a){return function(c,d,e){c=a(d.attr(e.$attr.ngBindTemplate));d.addClass("ng-binding").data("$binding",c);e.$observe("ngBindTemplate",function(a){d.text(a)})}}],jd=["$sce","$parse",function(a,c){return function(d,e,g){e.addClass("ng-binding").data("$binding",g.ngBindHtml);var f=c(g.ngBindHtml);d.$watch(function(){return(f(d)||"").toString()},function(c){e.html(a.getTrustedHtml(f(d))||"")})}}],ld=Pb("",!0),nd=Pb("Odd",0),md=Pb("Even",1),od=va({compile:function(a,c){c.$set("ngCloak",s);a.removeClass("ng-cloak")}}),
-pd=[function(){return{scope:!0,controller:"@",priority:500}}],fc={};q("click dblclick mousedown mouseup mouseover mouseout mousemove mouseenter mouseleave keydown keyup keypress submit focus blur copy cut paste".split(" "),function(a){var c=na("ng-"+a);fc[c]=["$parse",function(d){return{compile:function(e,g){var f=d(g[c]);return function(c,d,e){d.on(K(a),function(a){c.$apply(function(){f(c,{$event:a})})})}}}}]});var sd=["$animate",function(a){return{transclude:"element",priority:600,terminal:!0,restrict:"A",
-$$tlb:!0,link:function(c,d,e,g,f){var h,l,k;c.$watch(e.ngIf,function(g){Qa(g)?l||(l=c.$new(),f(l,function(c){c[c.length++]=U.createComment(" end ngIf: "+e.ngIf+" ");h={clone:c};a.enter(c,d.parent(),d)})):(k&&(k.remove(),k=null),l&&(l.$destroy(),l=null),h&&(k=yb(h.clone),a.leave(k,function(){k=null}),h=null))})}}}],td=["$http","$templateCache","$anchorScroll","$animate","$sce",function(a,c,d,e,g){return{restrict:"ECA",priority:400,terminal:!0,transclude:"element",controller:Ea.noop,compile:function(f,
-h){var l=h.ngInclude||h.src,k=h.onload||"",m=h.autoscroll;return function(f,h,q,s,u){var F=0,v,y,A,x=function(){y&&(y.remove(),y=null);v&&(v.$destroy(),v=null);A&&(e.leave(A,function(){y=null}),y=A,A=null)};f.$watch(g.parseAsResourceUrl(l),function(g){var l=function(){!B(m)||m&&!f.$eval(m)||d()},q=++F;g?(a.get(g,{cache:c}).success(function(a){if(q===F){var c=f.$new();s.template=a;a=u(c,function(a){x();e.enter(a,null,h,l)});v=c;A=a;v.$emit("$includeContentLoaded");f.$eval(k)}}).error(function(){q===
-F&&x()}),f.$emit("$includeContentRequested")):(x(),s.template=null)})}}}}],Jd=["$compile",function(a){return{restrict:"ECA",priority:-400,require:"ngInclude",link:function(c,d,e,g){d.html(g.template);a(d.contents())(c)}}}],ud=va({priority:450,compile:function(){return{pre:function(a,c,d){a.$eval(d.ngInit)}}}}),vd=va({terminal:!0,priority:1E3}),wd=["$locale","$interpolate",function(a,c){var d=/{}/g;return{restrict:"EA",link:function(e,g,f){var h=f.count,l=f.$attr.when&&g.attr(f.$attr.when),k=f.offset||
-0,m=e.$eval(l)||{},n={},p=c.startSymbol(),r=c.endSymbol(),s=/^when(Minus)?(.+)$/;q(f,function(a,c){s.test(c)&&(m[K(c.replace("when","").replace("Minus","-"))]=g.attr(f.$attr[c]))});q(m,function(a,e){n[e]=c(a.replace(d,p+h+"-"+k+r))});e.$watch(function(){var c=parseFloat(e.$eval(h));if(isNaN(c))return"";c in m||(c=a.pluralCat(c-k));return n[c](e,g,!0)},function(a){g.text(a)})}}}],xd=["$parse","$animate",function(a,c){var d=t("ngRepeat");return{transclude:"element",priority:1E3,terminal:!0,$$tlb:!0,
-link:function(e,g,f,h,l){var k=f.ngRepeat,m=k.match(/^\s*([\s\S]+?)\s+in\s+([\s\S]+?)(?:\s+track\s+by\s+([\s\S]+?))?\s*$/),n,p,r,s,u,F,v={$id:Ia};if(!m)throw d("iexp",k);f=m[1];h=m[2];(m=m[3])?(n=a(m),p=function(a,c,d){F&&(v[F]=a);v[u]=c;v.$index=d;return n(e,v)}):(r=function(a,c){return Ia(c)},s=function(a){return a});m=f.match(/^(?:([\$\w]+)|\(([\$\w]+)\s*,\s*([\$\w]+)\))$/);if(!m)throw d("iidexp",f);u=m[3]||m[1];F=m[2];var B={};e.$watchCollection(h,function(a){var f,h,m=g[0],n,v={},H,R,w,C,T,t,
-E=[];if(ab(a))T=a,n=p||r;else{n=p||s;T=[];for(w in a)a.hasOwnProperty(w)&&"$"!=w.charAt(0)&&T.push(w);T.sort()}H=T.length;h=E.length=T.length;for(f=0;f<h;f++)if(w=a===T?f:T[f],C=a[w],C=n(w,C,f),Aa(C,"`track by` id"),B.hasOwnProperty(C))t=B[C],delete B[C],v[C]=t,E[f]=t;else{if(v.hasOwnProperty(C))throw q(E,function(a){a&&a.scope&&(B[a.id]=a)}),d("dupes",k,C);E[f]={id:C};v[C]=!1}for(w in B)B.hasOwnProperty(w)&&(t=B[w],f=yb(t.clone),c.leave(f),q(f,function(a){a.$$NG_REMOVED=!0}),t.scope.$destroy());
-f=0;for(h=T.length;f<h;f++){w=a===T?f:T[f];C=a[w];t=E[f];E[f-1]&&(m=E[f-1].clone[E[f-1].clone.length-1]);if(t.scope){R=t.scope;n=m;do n=n.nextSibling;while(n&&n.$$NG_REMOVED);t.clone[0]!=n&&c.move(yb(t.clone),null,y(m));m=t.clone[t.clone.length-1]}else R=e.$new();R[u]=C;F&&(R[F]=w);R.$index=f;R.$first=0===f;R.$last=f===H-1;R.$middle=!(R.$first||R.$last);R.$odd=!(R.$even=0===(f&1));t.scope||l(R,function(a){a[a.length++]=U.createComment(" end ngRepeat: "+k+" ");c.enter(a,null,y(m));m=a;t.scope=R;t.clone=
-a;v[t.id]=t})}B=v})}}}],yd=["$animate",function(a){return function(c,d,e){c.$watch(e.ngShow,function(c){a[Qa(c)?"removeClass":"addClass"](d,"ng-hide")})}}],rd=["$animate",function(a){return function(c,d,e){c.$watch(e.ngHide,function(c){a[Qa(c)?"addClass":"removeClass"](d,"ng-hide")})}}],zd=va(function(a,c,d){a.$watch(d.ngStyle,function(a,d){d&&a!==d&&q(d,function(a,d){c.css(d,"")});a&&c.css(a)},!0)}),Ad=["$animate",function(a){return{restrict:"EA",require:"ngSwitch",controller:["$scope",function(){this.cases=
-{}}],link:function(c,d,e,g){var f,h,l,k=[];c.$watch(e.ngSwitch||e.on,function(d){var n,p=k.length;if(0<p){if(l){for(n=0;n<p;n++)l[n].remove();l=null}l=[];for(n=0;n<p;n++){var r=h[n];k[n].$destroy();l[n]=r;a.leave(r,function(){l.splice(n,1);0===l.length&&(l=null)})}}h=[];k=[];if(f=g.cases["!"+d]||g.cases["?"])c.$eval(e.change),q(f,function(d){var e=c.$new();k.push(e);d.transclude(e,function(c){var e=d.element;h.push(c);a.enter(c,e.parent(),e)})})})}}}],Bd=va({transclude:"element",priority:800,require:"^ngSwitch",
-link:function(a,c,d,e,g){e.cases["!"+d.ngSwitchWhen]=e.cases["!"+d.ngSwitchWhen]||[];e.cases["!"+d.ngSwitchWhen].push({transclude:g,element:c})}}),Cd=va({transclude:"element",priority:800,require:"^ngSwitch",link:function(a,c,d,e,g){e.cases["?"]=e.cases["?"]||[];e.cases["?"].push({transclude:g,element:c})}}),Ed=va({link:function(a,c,d,e,g){if(!g)throw t("ngTransclude")("orphan",ha(c));g(function(a){c.empty();c.append(a)})}}),ed=["$templateCache",function(a){return{restrict:"E",terminal:!0,compile:function(c,
-d){"text/ng-template"==d.type&&a.put(d.id,c[0].text)}}}],Te=t("ngOptions"),Dd=aa({terminal:!0}),fd=["$compile","$parse",function(a,c){var d=/^\s*([\s\S]+?)(?:\s+as\s+([\s\S]+?))?(?:\s+group\s+by\s+([\s\S]+?))?\s+for\s+(?:([\$\w][\$\w]*)|(?:\(\s*([\$\w][\$\w]*)\s*,\s*([\$\w][\$\w]*)\s*\)))\s+in\s+([\s\S]+?)(?:\s+track\s+by\s+([\s\S]+?))?$/,e={$setViewValue:C};return{restrict:"E",require:["select","?ngModel"],controller:["$element","$scope","$attrs",function(a,c,d){var l=this,k={},m=e,n;l.databound=
-d.ngModel;l.init=function(a,c,d){m=a;n=d};l.addOption=function(c){Aa(c,'"option value"');k[c]=!0;m.$viewValue==c&&(a.val(c),n.parent()&&n.remove())};l.removeOption=function(a){this.hasOption(a)&&(delete k[a],m.$viewValue==a&&this.renderUnknownOption(a))};l.renderUnknownOption=function(c){c="? "+Ia(c)+" ?";n.val(c);a.prepend(n);a.val(c);n.prop("selected",!0)};l.hasOption=function(a){return k.hasOwnProperty(a)};c.$on("$destroy",function(){l.renderUnknownOption=C})}],link:function(e,f,h,l){function k(a,
-c,d,e){d.$render=function(){var a=d.$viewValue;e.hasOption(a)?(A.parent()&&A.remove(),c.val(a),""===a&&w.prop("selected",!0)):E(a)&&w?c.val(""):e.renderUnknownOption(a)};c.on("change",function(){a.$apply(function(){A.parent()&&A.remove();d.$setViewValue(c.val())})})}function m(a,c,d){var e;d.$render=function(){var a=new Va(d.$viewValue);q(c.find("option"),function(c){c.selected=B(a.get(c.value))})};a.$watch(function(){xa(e,d.$viewValue)||(e=ba(d.$viewValue),d.$render())});c.on("change",function(){a.$apply(function(){var a=
-[];q(c.find("option"),function(c){c.selected&&a.push(c.value)});d.$setViewValue(a)})})}function n(e,f,g){function h(){var a={"":[]},c=[""],d,k,s,t,z;t=g.$modelValue;z=y(e)||[];var E=n?Qb(z):z,F,I,A;I={};s=!1;var D,H;if(r)if(w&&M(t))for(s=new Va([]),A=0;A<t.length;A++)I[m]=t[A],s.put(w(e,I),t[A]);else s=new Va(t);for(A=0;F=E.length,A<F;A++){k=A;if(n){k=E[A];if("$"===k.charAt(0))continue;I[n]=k}I[m]=z[k];d=p(e,I)||"";(k=a[d])||(k=a[d]=[],c.push(d));r?d=B(s.remove(w?w(e,I):q(e,I))):(w?(d={},d[m]=t,d=
-w(e,d)===w(e,I)):d=t===q(e,I),s=s||d);D=l(e,I);D=B(D)?D:"";k.push({id:w?w(e,I):n?E[A]:A,label:D,selected:d})}r||(u||null===t?a[""].unshift({id:"",label:"",selected:!s}):s||a[""].unshift({id:"?",label:"",selected:!0}));I=0;for(E=c.length;I<E;I++){d=c[I];k=a[d];x.length<=I?(t={element:C.clone().attr("label",d),label:k.label},z=[t],x.push(z),f.append(t.element)):(z=x[I],t=z[0],t.label!=d&&t.element.attr("label",t.label=d));D=null;A=0;for(F=k.length;A<F;A++)s=k[A],(d=z[A+1])?(D=d.element,d.label!==s.label&&
-D.text(d.label=s.label),d.id!==s.id&&D.val(d.id=s.id),d.selected!==s.selected&&D.prop("selected",d.selected=s.selected)):(""===s.id&&u?H=u:(H=v.clone()).val(s.id).attr("selected",s.selected).text(s.label),z.push({element:H,label:s.label,id:s.id,selected:s.selected}),D?D.after(H):t.element.append(H),D=H);for(A++;z.length>A;)z.pop().element.remove()}for(;x.length>I;)x.pop()[0].element.remove()}var k;if(!(k=t.match(d)))throw Te("iexp",t,ha(f));var l=c(k[2]||k[1]),m=k[4]||k[6],n=k[5],p=c(k[3]||""),q=
-c(k[2]?k[1]:m),y=c(k[7]),w=k[8]?c(k[8]):null,x=[[{element:f,label:""}]];u&&(a(u)(e),u.removeClass("ng-scope"),u.remove());f.empty();f.on("change",function(){e.$apply(function(){var a,c=y(e)||[],d={},h,k,l,p,t,v,u;if(r)for(k=[],p=0,v=x.length;p<v;p++)for(a=x[p],l=1,t=a.length;l<t;l++){if((h=a[l].element)[0].selected){h=h.val();n&&(d[n]=h);if(w)for(u=0;u<c.length&&(d[m]=c[u],w(e,d)!=h);u++);else d[m]=c[h];k.push(q(e,d))}}else{h=f.val();if("?"==h)k=s;else if(""===h)k=null;else if(w)for(u=0;u<c.length;u++){if(d[m]=
-c[u],w(e,d)==h){k=q(e,d);break}}else d[m]=c[h],n&&(d[n]=h),k=q(e,d);1<x[0].length&&x[0][1].id!==h&&(x[0][1].selected=!1)}g.$setViewValue(k)})});g.$render=h;e.$watch(h)}if(l[1]){var p=l[0];l=l[1];var r=h.multiple,t=h.ngOptions,u=!1,w,v=y(U.createElement("option")),C=y(U.createElement("optgroup")),A=v.clone();h=0;for(var x=f.children(),D=x.length;h<D;h++)if(""===x[h].value){w=u=x.eq(h);break}p.init(l,u,A);r&&(l.$isEmpty=function(a){return!a||0===a.length});t?n(e,f,l):r?m(e,f,l):k(e,f,l,p)}}}}],hd=["$interpolate",
-function(a){var c={addOption:C,removeOption:C};return{restrict:"E",priority:100,compile:function(d,e){if(E(e.value)){var g=a(d.text(),!0);g||e.$set("value",d.text())}return function(a,d,e){var k=d.parent(),m=k.data("$selectController")||k.parent().data("$selectController");m&&m.databound?d.prop("selected",!1):m=c;g?a.$watch(g,function(a,c){e.$set("value",a);a!==c&&m.removeOption(c);m.addOption(a)}):m.addOption(e.value);d.on("$destroy",function(){m.removeOption(e.value)})}}}}],gd=aa({restrict:"E",
-terminal:!0});O.angular.bootstrap?console.log("WARNING: Tried to load angular more than once."):((Ga=O.jQuery)?(y=Ga,D(Ga.fn,{scope:Ja.scope,isolateScope:Ja.isolateScope,controller:Ja.controller,injector:Ja.injector,inheritedData:Ja.inheritedData}),Ab("remove",!0,!0,!1),Ab("empty",!1,!1,!1),Ab("html",!1,!1,!0)):y=N,Ea.element=y,Zc(Ea),y(U).ready(function(){Wc(U,$b)}))})(window,document);!angular.$$csp()&&angular.element(document).find("head").prepend('<style type="text/css">@charset "UTF-8";[ng\\:cloak],[ng-cloak],[data-ng-cloak],[x-ng-cloak],.ng-cloak,.x-ng-cloak,.ng-hide{display:none !important;}ng\\:form{display:block;}.ng-animate-block-transitions{transition:0s all!important;-webkit-transition:0s all!important;}</style>');
-//# sourceMappingURL=angular.min.js.map
diff --git a/v1.2/docs/user-guide/update-demo/local/angular.min.js.map b/v1.2/docs/user-guide/update-demo/local/angular.min.js.map
deleted file mode 100644
index 0dddf2aab5..0000000000
--- a/v1.2/docs/user-guide/update-demo/local/angular.min.js.map
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-"version":3,
-"file":"angular.min.js",
-"lineCount":209,
-"mappings":"A;;;;;aAKC,SAAQ,CAACA,CAAD,CAASC,CAAT,CAAmBC,CAAnB,CAA8B,CA8BvCC,QAAAA,EAAAA,CAAAA,CAAAA,CAAAA,CAAAA,MAAAA,SAAAA,EAAAA,CAAAA,IAAAA,EAAAA,SAAAA,CAAAA,CAAAA,CAAAA,CAAAA,CAAAA,CAAAA,EAAAA,GAAAA,EAAAA,CAAAA,CAAAA,CAAAA,CAAAA,GAAAA,CAAAA,EAAAA,EAAAA,CAAAA,CAAAA,uCAAAA,EAAAA,CAAAA,CAAAA,CAAAA,CAAAA,GAAAA,CAAAA,EAAAA,EAAAA,CAAAA,KAAAA,CAAAA,CAAAA,CAAAA,CAAAA,CAAAA,CAAAA,SAAAA,OAAAA,CAAAA,CAAAA,EAAAA,CAAAA,CAAAA,CAAAA,CAAAA,EAAAA,CAAAA,EAAAA,CAAAA,CAAAA,GAAAA,CAAAA,GAAAA,EAAAA,GAAAA,EAAAA,CAAAA,CAAAA,CAAAA,EAAAA,GAAAA,CAAAA,kBAAAA,CAAAA,UAAAA,EAAAA,MAAAA,UAAAA,CAAAA,CAAAA,CAAAA,CAAAA,SAAAA,CAAAA,CAAAA,CAAAA,SAAAA,EAAAA,QAAAA,CAAAA,aAAAA,CAAAA,EAAAA,CAAAA,CAAAA,WAAAA,EAAAA,MAAAA,UAAAA,CAAAA,CAAAA,CAAAA,CAAAA,WAAAA,CAAAA,QAAAA,EAAAA,MAAAA,UAAAA,CAAAA,CAAAA,CAAAA,CAAAA,IAAAA,UAAAA,CAAAA,SAAAA,CAAAA,CAAAA,CAAAA,CAAAA,CAAAA,SAAAA,CAAAA,CAAAA,CAAAA,CAAAA,OAAAA,MAAAA,CAAAA,CAAAA,CAAAA,CAAAA,CAuOAC,QAASA,GAAW,CAACC,CAAD,CAAM,CACxB,GAAW,IAAX,EAAIA,CAAJ,EAAmBC,EAAA,CAASD,CAAT,CAAnB,CACE,MAAO,CAAA,CAGT;IAAIE,EAASF,CAAAE,OAEb,OAAqB,EAArB,GAAIF,CAAAG,SAAJ,EAA0BD,CAA1B,CACS,CAAA,CADT,CAIOE,CAAA,CAASJ,CAAT,CAJP,EAIwBK,CAAA,CAAQL,CAAR,CAJxB,EAImD,CAJnD,GAIwCE,CAJxC,EAKyB,QALzB,GAKO,MAAOA,EALd,EAK8C,CAL9C,CAKqCA,CALrC,EAKoDA,CALpD,CAK6D,CAL7D,GAKmEF,EAZ3C,CA4C1BM,QAASA,EAAO,CAACN,CAAD,CAAMO,CAAN,CAAgBC,CAAhB,CAAyB,CACvC,IAAIC,CACJ,IAAIT,CAAJ,CACE,GAAIU,CAAA,CAAWV,CAAX,CAAJ,CACE,IAAKS,CAAL,GAAYT,EAAZ,CAGa,WAAX,EAAIS,CAAJ,GAAiC,QAAjC,EAA0BA,CAA1B,EAAoD,MAApD,EAA6CA,CAA7C,EAAgET,CAAAW,eAAhE,EAAsF,CAAAX,CAAAW,eAAA,CAAmBF,CAAnB,CAAtF,GACEF,CAAAK,KAAA,CAAcJ,CAAd,CAAuBR,CAAA,CAAIS,CAAJ,CAAvB,CAAiCA,CAAjC,CALN,KAQO,IAAIT,CAAAM,QAAJ,EAAmBN,CAAAM,QAAnB,GAAmCA,CAAnC,CACLN,CAAAM,QAAA,CAAYC,CAAZ,CAAsBC,CAAtB,CADK,KAEA,IAAIT,EAAA,CAAYC,CAAZ,CAAJ,CACL,IAAKS,CAAL,CAAW,CAAX,CAAcA,CAAd,CAAoBT,CAAAE,OAApB,CAAgCO,CAAA,EAAhC,CACEF,CAAAK,KAAA,CAAcJ,CAAd,CAAuBR,CAAA,CAAIS,CAAJ,CAAvB,CAAiCA,CAAjC,CAFG,KAIL,KAAKA,CAAL,GAAYT,EAAZ,CACMA,CAAAW,eAAA,CAAmBF,CAAnB,CAAJ,EACEF,CAAAK,KAAA,CAAcJ,CAAd,CAAuBR,CAAA,CAAIS,CAAJ,CAAvB,CAAiCA,CAAjC,CAKR,OAAOT,EAxBgC,CA2BzCa,QAASA,GAAU,CAACb,CAAD,CAAM,CACvB,IAAIc,EAAO,EAAX,CACSL,CAAT,KAASA,CAAT,GAAgBT,EAAhB,CACMA,CAAAW,eAAA,CAAmBF,CAAnB,CAAJ,EACEK,CAAAC,KAAA,CAAUN,CAAV,CAGJ,OAAOK,EAAAE,KAAA,EAPgB,CAUzBC,QAASA,GAAa,CAACjB,CAAD;AAAMO,CAAN,CAAgBC,CAAhB,CAAyB,CAE7C,IADA,IAAIM,EAAOD,EAAA,CAAWb,CAAX,CAAX,CACUkB,EAAI,CAAd,CAAiBA,CAAjB,CAAqBJ,CAAAZ,OAArB,CAAkCgB,CAAA,EAAlC,CACEX,CAAAK,KAAA,CAAcJ,CAAd,CAAuBR,CAAA,CAAIc,CAAA,CAAKI,CAAL,CAAJ,CAAvB,CAAqCJ,CAAA,CAAKI,CAAL,CAArC,CAEF,OAAOJ,EALsC,CAc/CK,QAASA,GAAa,CAACC,CAAD,CAAa,CACjC,MAAO,SAAQ,CAACC,CAAD,CAAQZ,CAAR,CAAa,CAAEW,CAAA,CAAWX,CAAX,CAAgBY,CAAhB,CAAF,CADK,CAYnCC,QAASA,GAAO,EAAG,CAIjB,IAHA,IAAIC,EAAQC,EAAAtB,OAAZ,CACIuB,CAEJ,CAAMF,CAAN,CAAA,CAAa,CACXA,CAAA,EACAE,EAAA,CAAQD,EAAA,CAAID,CAAJ,CAAAG,WAAA,CAAsB,CAAtB,CACR,IAAa,EAAb,EAAID,CAAJ,CAEE,MADAD,GAAA,CAAID,CAAJ,CACO,CADM,GACN,CAAAC,EAAAG,KAAA,CAAS,EAAT,CAET,IAAa,EAAb,EAAIF,CAAJ,CACED,EAAA,CAAID,CAAJ,CAAA,CAAa,GADf,KAIE,OADAC,GAAA,CAAID,CAAJ,CACO,CADMK,MAAAC,aAAA,CAAoBJ,CAApB,CAA4B,CAA5B,CACN,CAAAD,EAAAG,KAAA,CAAS,EAAT,CAXE,CAcbH,EAAAM,QAAA,CAAY,GAAZ,CACA,OAAON,GAAAG,KAAA,CAAS,EAAT,CAnBU,CA4BnBI,QAASA,GAAU,CAAC/B,CAAD,CAAMgC,CAAN,CAAS,CACtBA,CAAJ,CACEhC,CAAAiC,UADF,CACkBD,CADlB,CAIE,OAAOhC,CAAAiC,UALiB,CAuB5BC,QAASA,EAAM,CAACC,CAAD,CAAM,CACnB,IAAIH,EAAIG,CAAAF,UACR3B,EAAA,CAAQ8B,SAAR,CAAmB,QAAQ,CAACpC,CAAD,CAAK,CAC1BA,CAAJ,GAAYmC,CAAZ,EACE7B,CAAA,CAAQN,CAAR,CAAa,QAAQ,CAACqB,CAAD,CAAQZ,CAAR,CAAY,CAC/B0B,CAAA,CAAI1B,CAAJ,CAAA,CAAWY,CADoB,CAAjC,CAF4B,CAAhC,CAQAU,GAAA,CAAWI,CAAX,CAAeH,CAAf,CACA,OAAOG,EAXY,CAcrBE,QAASA,EAAG,CAACC,CAAD,CAAM,CAChB,MAAOC,SAAA,CAASD,CAAT;AAAc,EAAd,CADS,CAKlBE,QAASA,GAAO,CAACC,CAAD,CAASC,CAAT,CAAgB,CAC9B,MAAOR,EAAA,CAAO,KAAKA,CAAA,CAAO,QAAQ,EAAG,EAAlB,CAAsB,WAAWO,CAAX,CAAtB,CAAL,CAAP,CAA0DC,CAA1D,CADuB,CAoBhCC,QAASA,EAAI,EAAG,EAoBhBC,QAASA,GAAQ,CAACC,CAAD,CAAI,CAAC,MAAOA,EAAR,CAIrBC,QAASA,GAAO,CAACzB,CAAD,CAAQ,CAAC,MAAO,SAAQ,EAAG,CAAC,MAAOA,EAAR,CAAnB,CAcxB0B,QAASA,EAAW,CAAC1B,CAAD,CAAO,CAAC,MAAwB,WAAxB,GAAO,MAAOA,EAAf,CAe3B2B,QAASA,EAAS,CAAC3B,CAAD,CAAO,CAAC,MAAwB,WAAxB,GAAO,MAAOA,EAAf,CAgBzB4B,QAASA,EAAQ,CAAC5B,CAAD,CAAO,CAAC,MAAgB,KAAhB,EAAOA,CAAP,EAAyC,QAAzC,GAAwB,MAAOA,EAAhC,CAexBjB,QAASA,EAAQ,CAACiB,CAAD,CAAO,CAAC,MAAwB,QAAxB,GAAO,MAAOA,EAAf,CAexB6B,QAASA,GAAQ,CAAC7B,CAAD,CAAO,CAAC,MAAwB,QAAxB,GAAO,MAAOA,EAAf,CAexB8B,QAASA,GAAM,CAAC9B,CAAD,CAAO,CACpB,MAAgC,eAAhC,GAAO+B,EAAAxC,KAAA,CAAcS,CAAd,CADa,CAiBtBhB,QAASA,EAAO,CAACgB,CAAD,CAAQ,CACtB,MAAgC,gBAAhC,GAAO+B,EAAAxC,KAAA,CAAcS,CAAd,CADe,CAiBxBX,QAASA,EAAU,CAACW,CAAD,CAAO,CAAC,MAAwB,UAAxB,GAAO,MAAOA,EAAf,CA9lBa;AAwmBvCgC,QAASA,GAAQ,CAAChC,CAAD,CAAQ,CACvB,MAAgC,iBAAhC,GAAO+B,EAAAxC,KAAA,CAAcS,CAAd,CADgB,CAYzBpB,QAASA,GAAQ,CAACD,CAAD,CAAM,CACrB,MAAOA,EAAP,EAAcA,CAAAJ,SAAd,EAA8BI,CAAAsD,SAA9B,EAA8CtD,CAAAuD,MAA9C,EAA2DvD,CAAAwD,YADtC,CAoDvBC,QAASA,GAAS,CAACC,CAAD,CAAO,CACvB,MAAO,EAAGA,CAAAA,CAAH,EACJ,EAAAA,CAAAC,SAAA,EACGD,CAAAE,KADH,EACgBF,CAAAG,KADhB,EAC6BH,CAAAI,KAD7B,CADI,CADgB,CA+BzBC,QAASA,GAAG,CAAC/D,CAAD,CAAMO,CAAN,CAAgBC,CAAhB,CAAyB,CACnC,IAAIwD,EAAU,EACd1D,EAAA,CAAQN,CAAR,CAAa,QAAQ,CAACqB,CAAD,CAAQE,CAAR,CAAe0C,CAAf,CAAqB,CACxCD,CAAAjD,KAAA,CAAaR,CAAAK,KAAA,CAAcJ,CAAd,CAAuBa,CAAvB,CAA8BE,CAA9B,CAAqC0C,CAArC,CAAb,CADwC,CAA1C,CAGA,OAAOD,EAL4B,CAwCrCE,QAASA,GAAO,CAACC,CAAD,CAAQnE,CAAR,CAAa,CAC3B,GAAImE,CAAAD,QAAJ,CAAmB,MAAOC,EAAAD,QAAA,CAAclE,CAAd,CAE1B,KAAK,IAAIkB,EAAI,CAAb,CAAgBA,CAAhB,CAAoBiD,CAAAjE,OAApB,CAAkCgB,CAAA,EAAlC,CACE,GAAIlB,CAAJ,GAAYmE,CAAA,CAAMjD,CAAN,CAAZ,CAAsB,MAAOA,EAE/B,OAAQ,EANmB,CAS7BkD,QAASA,GAAW,CAACD,CAAD,CAAQ9C,CAAR,CAAe,CACjC,IAAIE,EAAQ2C,EAAA,CAAQC,CAAR,CAAe9C,CAAf,CACA,EAAZ,EAAIE,CAAJ,EACE4C,CAAAE,OAAA,CAAa9C,CAAb,CAAoB,CAApB,CACF,OAAOF,EAJ0B,CA4EnCiD,QAASA,GAAI,CAACC,CAAD,CAASC,CAAT,CAAqB,CAChC,GAAIvE,EAAA,CAASsE,CAAT,CAAJ,EAAgCA,CAAhC,EAAgCA,CA3MlBE,WA2Md,EAAgCF,CA3MAG,OA2MhC,CACE,KAAMC,GAAA,CAAS,MAAT,CAAN;AAIF,GAAKH,CAAL,CAaO,CACL,GAAID,CAAJ,GAAeC,CAAf,CAA4B,KAAMG,GAAA,CAAS,KAAT,CAAN,CAE5B,GAAItE,CAAA,CAAQkE,CAAR,CAAJ,CAEE,IAAM,IAAIrD,EADVsD,CAAAtE,OACUgB,CADW,CACrB,CAAiBA,CAAjB,CAAqBqD,CAAArE,OAArB,CAAoCgB,CAAA,EAApC,CACEsD,CAAAzD,KAAA,CAAiBuD,EAAA,CAAKC,CAAA,CAAOrD,CAAP,CAAL,CAAjB,CAHJ,KAKO,CACDc,CAAAA,CAAIwC,CAAAvC,UACR3B,EAAA,CAAQkE,CAAR,CAAqB,QAAQ,CAACnD,CAAD,CAAQZ,CAAR,CAAY,CACvC,OAAO+D,CAAA,CAAY/D,CAAZ,CADgC,CAAzC,CAGA,KAAMA,IAAIA,CAAV,GAAiB8D,EAAjB,CACEC,CAAA,CAAY/D,CAAZ,CAAA,CAAmB6D,EAAA,CAAKC,CAAA,CAAO9D,CAAP,CAAL,CAErBsB,GAAA,CAAWyC,CAAX,CAAuBxC,CAAvB,CARK,CARF,CAbP,IAEE,CADAwC,CACA,CADcD,CACd,IACMlE,CAAA,CAAQkE,CAAR,CAAJ,CACEC,CADF,CACgBF,EAAA,CAAKC,CAAL,CAAa,EAAb,CADhB,CAEWpB,EAAA,CAAOoB,CAAP,CAAJ,CACLC,CADK,CACS,IAAII,IAAJ,CAASL,CAAAM,QAAA,EAAT,CADT,CAEIxB,EAAA,CAASkB,CAAT,CAAJ,CACLC,CADK,CACaM,MAAJ,CAAWP,CAAAA,OAAX,CADT,CAEItB,CAAA,CAASsB,CAAT,CAFJ,GAGLC,CAHK,CAGSF,EAAA,CAAKC,CAAL,CAAa,EAAb,CAHT,CALT,CA8BF,OAAOC,EAtCyB,CA4ClCO,QAASA,GAAW,CAACC,CAAD,CAAM7C,CAAN,CAAW,CAC7BA,CAAA,CAAMA,CAAN,EAAa,EAEb,KAAI1B,IAAIA,CAAR,GAAeuE,EAAf,CAGM,CAAAA,CAAArE,eAAA,CAAmBF,CAAnB,CAAJ,EAAmD,GAAnD,GAAiCA,CAAAwE,OAAA,CAAW,CAAX,CAAjC,EAA4E,GAA5E,GAA0DxE,CAAAwE,OAAA,CAAW,CAAX,CAA1D,GACE9C,CAAA,CAAI1B,CAAJ,CADF,CACauE,CAAA,CAAIvE,CAAJ,CADb,CAKF,OAAO0B,EAXsB,CA4C/B+C,QAASA,GAAM,CAACC,CAAD,CAAKC,CAAL,CAAS,CACtB,GAAID,CAAJ,GAAWC,CAAX,CAAe,MAAO,CAAA,CACtB,IAAW,IAAX,GAAID,CAAJ,EAA0B,IAA1B,GAAmBC,CAAnB,CAAgC,MAAO,CAAA,CACvC,IAAID,CAAJ,GAAWA,CAAX,EAAiBC,CAAjB,GAAwBA,CAAxB,CAA4B,MAAO,CAAA,CAHb;IAIlBC,EAAK,MAAOF,EAJM,CAIsB1E,CAC5C,IAAI4E,CAAJ,EADyBC,MAAOF,EAChC,EACY,QADZ,EACMC,CADN,CAEI,GAAIhF,CAAA,CAAQ8E,CAAR,CAAJ,CAAiB,CACf,GAAI,CAAC9E,CAAA,CAAQ+E,CAAR,CAAL,CAAkB,MAAO,CAAA,CACzB,KAAKlF,CAAL,CAAciF,CAAAjF,OAAd,GAA4BkF,CAAAlF,OAA5B,CAAuC,CACrC,IAAIO,CAAJ,CAAQ,CAAR,CAAWA,CAAX,CAAeP,CAAf,CAAuBO,CAAA,EAAvB,CACE,GAAI,CAACyE,EAAA,CAAOC,CAAA,CAAG1E,CAAH,CAAP,CAAgB2E,CAAA,CAAG3E,CAAH,CAAhB,CAAL,CAA+B,MAAO,CAAA,CAExC,OAAO,CAAA,CAJ8B,CAFxB,CAAjB,IAQO,CAAA,GAAI0C,EAAA,CAAOgC,CAAP,CAAJ,CACL,MAAOhC,GAAA,CAAOiC,CAAP,CAAP,EAAqBD,CAAAN,QAAA,EAArB,EAAqCO,CAAAP,QAAA,EAChC,IAAIxB,EAAA,CAAS8B,CAAT,CAAJ,EAAoB9B,EAAA,CAAS+B,CAAT,CAApB,CACL,MAAOD,EAAA/B,SAAA,EAAP,EAAwBgC,CAAAhC,SAAA,EAExB,IAAY+B,CAAZ,EAAYA,CAtTJV,WAsTR,EAAYU,CAtTcT,OAsT1B,EAA2BU,CAA3B,EAA2BA,CAtTnBX,WAsTR,EAA2BW,CAtTDV,OAsT1B,EAAkCzE,EAAA,CAASkF,CAAT,CAAlC,EAAkDlF,EAAA,CAASmF,CAAT,CAAlD,EAAkE/E,CAAA,CAAQ+E,CAAR,CAAlE,CAA+E,MAAO,CAAA,CACtFG,EAAA,CAAS,EACT,KAAI9E,CAAJ,GAAW0E,EAAX,CACE,GAAsB,GAAtB,GAAI1E,CAAAwE,OAAA,CAAW,CAAX,CAAJ,EAA6B,CAAAvE,CAAA,CAAWyE,CAAA,CAAG1E,CAAH,CAAX,CAA7B,CAAA,CACA,GAAI,CAACyE,EAAA,CAAOC,CAAA,CAAG1E,CAAH,CAAP,CAAgB2E,CAAA,CAAG3E,CAAH,CAAhB,CAAL,CAA+B,MAAO,CAAA,CACtC8E,EAAA,CAAO9E,CAAP,CAAA,CAAc,CAAA,CAFd,CAIF,IAAIA,CAAJ,GAAW2E,EAAX,CACE,GAAI,CAACG,CAAA5E,eAAA,CAAsBF,CAAtB,CAAL,EACsB,GADtB,GACIA,CAAAwE,OAAA,CAAW,CAAX,CADJ,EAEIG,CAAA,CAAG3E,CAAH,CAFJ,GAEgBZ,CAFhB,EAGI,CAACa,CAAA,CAAW0E,CAAA,CAAG3E,CAAH,CAAX,CAHL,CAG0B,MAAO,CAAA,CAEnC;MAAO,CAAA,CAlBF,CAsBX,MAAO,CAAA,CArCe,CAyCxB+E,QAASA,GAAG,EAAG,CACb,MAAQ5F,EAAA6F,eAAR,EAAmC7F,CAAA6F,eAAAC,SAAnC,EACK9F,CAAA+F,cADL,EAEI,EAAG,CAAA/F,CAAA+F,cAAA,CAAuB,UAAvB,CAAH,EAAyC,CAAA/F,CAAA+F,cAAA,CAAuB,eAAvB,CAAzC,CAHS,CAmCfC,QAASA,GAAI,CAACC,CAAD,CAAOC,CAAP,CAAW,CACtB,IAAIC,EAA+B,CAAnB,CAAA3D,SAAAlC,OAAA,CAxBT8F,EAAApF,KAAA,CAwB0CwB,SAxB1C,CAwBqD6D,CAxBrD,CAwBS,CAAiD,EACjE,OAAI,CAAAvF,CAAA,CAAWoF,CAAX,CAAJ,EAAwBA,CAAxB,WAAsChB,OAAtC,CAcSgB,CAdT,CACSC,CAAA7F,OACA,CAAH,QAAQ,EAAG,CACT,MAAOkC,UAAAlC,OACA,CAAH4F,CAAAI,MAAA,CAASL,CAAT,CAAeE,CAAAI,OAAA,CAAiBH,EAAApF,KAAA,CAAWwB,SAAX,CAAsB,CAAtB,CAAjB,CAAf,CAAG,CACH0D,CAAAI,MAAA,CAASL,CAAT,CAAeE,CAAf,CAHK,CAAR,CAKH,QAAQ,EAAG,CACT,MAAO3D,UAAAlC,OACA,CAAH4F,CAAAI,MAAA,CAASL,CAAT,CAAezD,SAAf,CAAG,CACH0D,CAAAlF,KAAA,CAAQiF,CAAR,CAHK,CATK,CAqBxBO,QAASA,GAAc,CAAC3F,CAAD,CAAMY,CAAN,CAAa,CAClC,IAAIgF,EAAMhF,CAES,SAAnB,GAAI,MAAOZ,EAAX,EAAiD,GAAjD,GAA+BA,CAAAwE,OAAA,CAAW,CAAX,CAA/B,CACEoB,CADF;AACQxG,CADR,CAEWI,EAAA,CAASoB,CAAT,CAAJ,CACLgF,CADK,CACC,SADD,CAEIhF,CAAJ,EAAczB,CAAd,GAA2ByB,CAA3B,CACLgF,CADK,CACC,WADD,CAEYhF,CAFZ,GAEYA,CA5YLoD,WA0YP,EAEYpD,CA5YaqD,OA0YzB,IAGL2B,CAHK,CAGC,QAHD,CAMP,OAAOA,EAb2B,CA+BpCC,QAASA,GAAM,CAACtG,CAAD,CAAMuG,CAAN,CAAc,CAC3B,MAAmB,WAAnB,GAAI,MAAOvG,EAAX,CAAuCH,CAAvC,CACO2G,IAAAC,UAAA,CAAezG,CAAf,CAAoBoG,EAApB,CAAoCG,CAAA,CAAS,IAAT,CAAgB,IAApD,CAFoB,CAkB7BG,QAASA,GAAQ,CAACC,CAAD,CAAO,CACtB,MAAOvG,EAAA,CAASuG,CAAT,CACA,CAADH,IAAAI,MAAA,CAAWD,CAAX,CAAC,CACDA,CAHgB,CAOxBE,QAASA,GAAS,CAACxF,CAAD,CAAQ,CACH,UAArB,GAAI,MAAOA,EAAX,CACEA,CADF,CACU,CAAA,CADV,CAEWA,CAAJ,EAA8B,CAA9B,GAAaA,CAAAnB,OAAb,EACD4G,CACJ,CADQC,CAAA,CAAU,EAAV,CAAe1F,CAAf,CACR,CAAAA,CAAA,CAAQ,EAAO,GAAP,EAAEyF,CAAF,EAAmB,GAAnB,EAAcA,CAAd,EAA+B,OAA/B,EAA0BA,CAA1B,EAA+C,IAA/C,EAA0CA,CAA1C,EAA4D,GAA5D,EAAuDA,CAAvD,EAAwE,IAAxE,EAAmEA,CAAnE,CAFH,EAILzF,CAJK,CAIG,CAAA,CAEV,OAAOA,EATiB,CAe1B2F,QAASA,GAAW,CAACC,CAAD,CAAU,CAC5BA,CAAA,CAAUC,CAAA,CAAOD,CAAP,CAAAE,MAAA,EACV,IAAI,CAGFF,CAAAG,MAAA,EAHE,CAIF,MAAMC,CAAN,CAAS,EAGX,IAAIC,EAAWJ,CAAA,CAAO,OAAP,CAAAK,OAAA,CAAuBN,CAAvB,CAAAO,KAAA,EACf,IAAI,CACF,MAHcC,EAGP,GAAAR,CAAA,CAAQ,CAAR,CAAA9G,SAAA,CAAoC4G,CAAA,CAAUO,CAAV,CAApC,CACHA,CAAAI,MAAA,CACQ,YADR,CACA,CAAsB,CAAtB,CAAAC,QAAA,CACU,aADV;AACyB,QAAQ,CAACD,CAAD,CAAQ/D,CAAR,CAAkB,CAAE,MAAO,GAAP,CAAaoD,CAAA,CAAUpD,CAAV,CAAf,CADnD,CAHF,CAKF,MAAM0D,CAAN,CAAS,CACT,MAAON,EAAA,CAAUO,CAAV,CADE,CAfiB,CAgC9BM,QAASA,GAAqB,CAACvG,CAAD,CAAQ,CACpC,GAAI,CACF,MAAOwG,mBAAA,CAAmBxG,CAAnB,CADL,CAEF,MAAMgG,CAAN,CAAS,EAHyB,CAatCS,QAASA,GAAa,CAAYC,CAAZ,CAAsB,CAAA,IACtC/H,EAAM,EADgC,CAC5BgI,CAD4B,CACjBvH,CACzBH,EAAA,CAAS2H,CAAAF,CAAAE,EAAY,EAAZA,OAAA,CAAsB,GAAtB,CAAT,CAAqC,QAAQ,CAACF,CAAD,CAAU,CAChDA,CAAL,GACEC,CAEA,CAFYD,CAAAE,MAAA,CAAe,GAAf,CAEZ,CADAxH,CACA,CADMmH,EAAA,CAAsBI,CAAA,CAAU,CAAV,CAAtB,CACN,CAAKhF,CAAA,CAAUvC,CAAV,CAAL,GACM4F,CACJ,CADUrD,CAAA,CAAUgF,CAAA,CAAU,CAAV,CAAV,CAAA,CAA0BJ,EAAA,CAAsBI,CAAA,CAAU,CAAV,CAAtB,CAA1B,CAAgE,CAAA,CAC1E,CAAKhI,CAAA,CAAIS,CAAJ,CAAL,CAEUJ,CAAA,CAAQL,CAAA,CAAIS,CAAJ,CAAR,CAAH,CACLT,CAAA,CAAIS,CAAJ,CAAAM,KAAA,CAAcsF,CAAd,CADK,CAGLrG,CAAA,CAAIS,CAAJ,CAHK,CAGM,CAACT,CAAA,CAAIS,CAAJ,CAAD,CAAU4F,CAAV,CALb,CACErG,CAAA,CAAIS,CAAJ,CADF,CACa4F,CAHf,CAHF,CADqD,CAAvD,CAgBA,OAAOrG,EAlBmC,CAqB5CkI,QAASA,GAAU,CAAClI,CAAD,CAAM,CACvB,IAAImI,EAAQ,EACZ7H,EAAA,CAAQN,CAAR,CAAa,QAAQ,CAACqB,CAAD,CAAQZ,CAAR,CAAa,CAC5BJ,CAAA,CAAQgB,CAAR,CAAJ,CACEf,CAAA,CAAQe,CAAR,CAAe,QAAQ,CAAC+G,CAAD,CAAa,CAClCD,CAAApH,KAAA,CAAWsH,EAAA,CAAe5H,CAAf,CAAoB,CAAA,CAApB,CAAX,EAC2B,CAAA,CAAf,GAAA2H,CAAA,CAAsB,EAAtB,CAA2B,GAA3B,CAAiCC,EAAA,CAAeD,CAAf,CAA2B,CAAA,CAA3B,CAD7C,EADkC,CAApC,CADF,CAMAD,CAAApH,KAAA,CAAWsH,EAAA,CAAe5H,CAAf,CAAoB,CAAA,CAApB,CAAX,EACsB,CAAA,CAAV,GAAAY,CAAA,CAAiB,EAAjB,CAAsB,GAAtB,CAA4BgH,EAAA,CAAehH,CAAf,CAAsB,CAAA,CAAtB,CADxC,EAPgC,CAAlC,CAWA,OAAO8G,EAAAjI,OAAA,CAAeiI,CAAAxG,KAAA,CAAW,GAAX,CAAf,CAAiC,EAbjB,CA4BzB2G,QAASA,GAAgB,CAACjC,CAAD,CAAM,CAC7B,MAAOgC,GAAA,CAAehC,CAAf;AAAoB,CAAA,CAApB,CAAAsB,QAAA,CACY,OADZ,CACqB,GADrB,CAAAA,QAAA,CAEY,OAFZ,CAEqB,GAFrB,CAAAA,QAAA,CAGY,OAHZ,CAGqB,GAHrB,CADsB,CAmB/BU,QAASA,GAAc,CAAChC,CAAD,CAAMkC,CAAN,CAAuB,CAC5C,MAAOC,mBAAA,CAAmBnC,CAAnB,CAAAsB,QAAA,CACY,OADZ,CACqB,GADrB,CAAAA,QAAA,CAEY,OAFZ,CAEqB,GAFrB,CAAAA,QAAA,CAGY,MAHZ,CAGoB,GAHpB,CAAAA,QAAA,CAIY,OAJZ,CAIqB,GAJrB,CAAAA,QAAA,CAKY,MALZ,CAKqBY,CAAA,CAAkB,KAAlB,CAA0B,GAL/C,CADqC,CAwD9CE,QAASA,GAAW,CAACxB,CAAD,CAAUyB,CAAV,CAAqB,CAOvCnB,QAASA,EAAM,CAACN,CAAD,CAAU,CACvBA,CAAA,EAAW0B,CAAA5H,KAAA,CAAckG,CAAd,CADY,CAPc,IACnC0B,EAAW,CAAC1B,CAAD,CADwB,CAEnC2B,CAFmC,CAGnCC,CAHmC,CAInCC,EAAQ,CAAC,QAAD,CAAW,QAAX,CAAqB,UAArB,CAAiC,aAAjC,CAJ2B,CAKnCC,EAAsB,mCAM1BzI,EAAA,CAAQwI,CAAR,CAAe,QAAQ,CAACE,CAAD,CAAO,CAC5BF,CAAA,CAAME,CAAN,CAAA,CAAc,CAAA,CACdzB,EAAA,CAAO3H,CAAAqJ,eAAA,CAAwBD,CAAxB,CAAP,CACAA,EAAA,CAAOA,CAAArB,QAAA,CAAa,GAAb,CAAkB,KAAlB,CACHV,EAAAiC,iBAAJ,GACE5I,CAAA,CAAQ2G,CAAAiC,iBAAA,CAAyB,GAAzB,CAA+BF,CAA/B,CAAR,CAA8CzB,CAA9C,CAEA,CADAjH,CAAA,CAAQ2G,CAAAiC,iBAAA,CAAyB,GAAzB;AAA+BF,CAA/B,CAAsC,KAAtC,CAAR,CAAsDzB,CAAtD,CACA,CAAAjH,CAAA,CAAQ2G,CAAAiC,iBAAA,CAAyB,GAAzB,CAA+BF,CAA/B,CAAsC,GAAtC,CAAR,CAAoDzB,CAApD,CAHF,CAJ4B,CAA9B,CAWAjH,EAAA,CAAQqI,CAAR,CAAkB,QAAQ,CAAC1B,CAAD,CAAU,CAClC,GAAI,CAAC2B,CAAL,CAAiB,CAEf,IAAIlB,EAAQqB,CAAAI,KAAA,CADI,GACJ,CADUlC,CAAAmC,UACV,CAD8B,GAC9B,CACR1B,EAAJ,EACEkB,CACA,CADa3B,CACb,CAAA4B,CAAA,CAAUlB,CAAAD,CAAA,CAAM,CAAN,CAAAC,EAAY,EAAZA,SAAA,CAAwB,MAAxB,CAAgC,GAAhC,CAFZ,EAIErH,CAAA,CAAQ2G,CAAAoC,WAAR,CAA4B,QAAQ,CAACxF,CAAD,CAAO,CACpC+E,CAAAA,CAAL,EAAmBE,CAAA,CAAMjF,CAAAmF,KAAN,CAAnB,GACEJ,CACA,CADa3B,CACb,CAAA4B,CAAA,CAAShF,CAAAxC,MAFX,CADyC,CAA3C,CAPa,CADiB,CAApC,CAiBIuH,EAAJ,EACEF,CAAA,CAAUE,CAAV,CAAsBC,CAAA,CAAS,CAACA,CAAD,CAAT,CAAoB,EAA1C,CAxCqC,CAkGzCH,QAASA,GAAS,CAACzB,CAAD,CAAUqC,CAAV,CAAmB,CACnC,IAAIC,EAAcA,QAAQ,EAAG,CAC3BtC,CAAA,CAAUC,CAAA,CAAOD,CAAP,CAEV,IAAIA,CAAAuC,SAAA,EAAJ,CAAwB,CACtB,IAAIC,EAAOxC,CAAA,CAAQ,CAAR,CAAD,GAAgBrH,CAAhB,CAA4B,UAA5B,CAAyCoH,EAAA,CAAYC,CAAZ,CACnD,MAAMtC,GAAA,CAAS,SAAT,CAAwE8E,CAAxE,CAAN,CAFsB,CAKxBH,CAAA,CAAUA,CAAV,EAAqB,EACrBA,EAAAxH,QAAA,CAAgB,CAAC,UAAD,CAAa,QAAQ,CAAC4H,CAAD,CAAW,CAC9CA,CAAArI,MAAA,CAAe,cAAf,CAA+B4F,CAA/B,CAD8C,CAAhC,CAAhB,CAGAqC,EAAAxH,QAAA,CAAgB,IAAhB,CACI0H,EAAAA,CAAWG,EAAA,CAAeL,CAAf,CACfE,EAAAI,OAAA,CAAgB,CAAC,YAAD,CAAe,cAAf,CAA+B,UAA/B,CAA2C,WAA3C,CAAwD,UAAxD;AACb,QAAQ,CAACC,CAAD,CAAQ5C,CAAR,CAAiB6C,CAAjB,CAA0BN,CAA1B,CAAoCO,CAApC,CAA6C,CACpDF,CAAAG,OAAA,CAAa,QAAQ,EAAG,CACtB/C,CAAAgD,KAAA,CAAa,WAAb,CAA0BT,CAA1B,CACAM,EAAA,CAAQ7C,CAAR,CAAA,CAAiB4C,CAAjB,CAFsB,CAAxB,CADoD,CADxC,CAAhB,CAQA,OAAOL,EAtBoB,CAA7B,CAyBIU,EAAqB,sBAEzB,IAAIvK,CAAJ,EAAc,CAACuK,CAAAC,KAAA,CAAwBxK,CAAAqJ,KAAxB,CAAf,CACE,MAAOO,EAAA,EAGT5J,EAAAqJ,KAAA,CAAcrJ,CAAAqJ,KAAArB,QAAA,CAAoBuC,CAApB,CAAwC,EAAxC,CACdE,GAAAC,gBAAA,CAA0BC,QAAQ,CAACC,CAAD,CAAe,CAC/CjK,CAAA,CAAQiK,CAAR,CAAsB,QAAQ,CAAC1B,CAAD,CAAS,CACrCS,CAAAvI,KAAA,CAAa8H,CAAb,CADqC,CAAvC,CAGAU,EAAA,EAJ+C,CAjCd,CA0CrCiB,QAASA,GAAU,CAACxB,CAAD,CAAOyB,CAAP,CAAiB,CAClCA,CAAA,CAAYA,CAAZ,EAAyB,GACzB,OAAOzB,EAAArB,QAAA,CAAa+C,EAAb,CAAgC,QAAQ,CAACC,CAAD,CAASC,CAAT,CAAc,CAC3D,OAAQA,CAAA,CAAMH,CAAN,CAAkB,EAA1B,EAAgCE,CAAAE,YAAA,EAD2B,CAAtD,CAF2B,CAkCpCC,QAASA,GAAS,CAACC,CAAD,CAAM/B,CAAN,CAAYgC,CAAZ,CAAoB,CACpC,GAAI,CAACD,CAAL,CACE,KAAMpG,GAAA,CAAS,MAAT,CAA2CqE,CAA3C,EAAmD,GAAnD,CAA0DgC,CAA1D,EAAoE,UAApE,CAAN,CAEF,MAAOD,EAJ6B,CAOtCE,QAASA,GAAW,CAACF,CAAD,CAAM/B,CAAN,CAAYkC,CAAZ,CAAmC,CACjDA,CAAJ,EAA6B7K,CAAA,CAAQ0K,CAAR,CAA7B,GACIA,CADJ,CACUA,CAAA,CAAIA,CAAA7K,OAAJ,CAAiB,CAAjB,CADV,CAIA4K,GAAA,CAAUpK,CAAA,CAAWqK,CAAX,CAAV,CAA2B/B,CAA3B,CAAiC,sBAAjC,EACK+B,CAAA,EAAqB,QAArB,EAAO,MAAOA,EAAd;AAAgCA,CAAAI,YAAAnC,KAAhC,EAAwD,QAAxD,CAAmE,MAAO+B,EAD/E,EAEA,OAAOA,EAP8C,CAevDK,QAASA,GAAuB,CAACpC,CAAD,CAAOxI,CAAP,CAAgB,CAC9C,GAAa,gBAAb,GAAIwI,CAAJ,CACE,KAAMrE,GAAA,CAAS,SAAT,CAA8DnE,CAA9D,CAAN,CAF4C,CAchD6K,QAASA,GAAM,CAACrL,CAAD,CAAMsL,CAAN,CAAYC,CAAZ,CAA2B,CACxC,GAAI,CAACD,CAAL,CAAW,MAAOtL,EACdc,EAAAA,CAAOwK,CAAArD,MAAA,CAAW,GAAX,CAKX,KAJA,IAAIxH,CAAJ,CACI+K,EAAexL,CADnB,CAEIyL,EAAM3K,CAAAZ,OAFV,CAISgB,EAAI,CAAb,CAAgBA,CAAhB,CAAoBuK,CAApB,CAAyBvK,CAAA,EAAzB,CACET,CACA,CADMK,CAAA,CAAKI,CAAL,CACN,CAAIlB,CAAJ,GACEA,CADF,CACQ,CAACwL,CAAD,CAAgBxL,CAAhB,EAAqBS,CAArB,CADR,CAIF,OAAI,CAAC8K,CAAL,EAAsB7K,CAAA,CAAWV,CAAX,CAAtB,CACS4F,EAAA,CAAK4F,CAAL,CAAmBxL,CAAnB,CADT,CAGOA,CAhBiC,CAwB1C0L,QAASA,GAAgB,CAACC,CAAD,CAAQ,CAAA,IAC3BC,EAAYD,CAAA,CAAM,CAAN,CACZE,EAAAA,CAAUF,CAAA,CAAMA,CAAAzL,OAAN,CAAqB,CAArB,CACd,IAAI0L,CAAJ,GAAkBC,CAAlB,CACE,MAAO3E,EAAA,CAAO0E,CAAP,CAIT,KAAIjD,EAAW,CAAC1B,CAAD,CAEf,GAAG,CACDA,CAAA,CAAUA,CAAA6E,YACV,IAAI,CAAC7E,CAAL,CAAc,KACd0B,EAAA5H,KAAA,CAAckG,CAAd,CAHC,CAAH,MAISA,CAJT,GAIqB4E,CAJrB,CAMA,OAAO3E,EAAA,CAAOyB,CAAP,CAhBwB,CA4BjCoD,QAASA,GAAiB,CAACpM,CAAD,CAAS,CAEjC,IAAIqM,EAAkBlM,CAAA,CAAO,WAAP,CAAtB,CACI6E,EAAW7E,CAAA,CAAO,IAAP,CAMXsK,EAAAA,CAAiBzK,CAHZ,QAGLyK,GAAiBzK,CAHE,QAGnByK,CAH+B,EAG/BA,CAGJA,EAAA6B,SAAA,CAAmB7B,CAAA6B,SAAnB,EAAuCnM,CAEvC,OAAcsK,EARL,OAQT;CAAcA,CARS,OAQvB,CAAiC8B,QAAQ,EAAG,CAE1C,IAAI5C,EAAU,EAqDd,OAAOT,SAAe,CAACG,CAAD,CAAOmD,CAAP,CAAiBC,CAAjB,CAA2B,CAE7C,GAAa,gBAAb,GAKsBpD,CALtB,CACE,KAAMrE,EAAA,CAAS,SAAT,CAIoBnE,QAJpB,CAAN,CAKA2L,CAAJ,EAAgB7C,CAAA3I,eAAA,CAAuBqI,CAAvB,CAAhB,GACEM,CAAA,CAAQN,CAAR,CADF,CACkB,IADlB,CAGA,OAAcM,EA1ET,CA0EkBN,CA1ElB,CA0EL,GAAcM,CA1EK,CA0EIN,CA1EJ,CA0EnB,CAA6BkD,QAAQ,EAAG,CAgNtCG,QAASA,EAAW,CAACC,CAAD,CAAWC,CAAX,CAAmBC,CAAnB,CAAiC,CACnD,MAAO,SAAQ,EAAG,CAChBC,CAAA,CAAYD,CAAZ,EAA4B,MAA5B,CAAA,CAAoC,CAACF,CAAD,CAAWC,CAAX,CAAmBnK,SAAnB,CAApC,CACA,OAAOsK,EAFS,CADiC,CA/MrD,GAAI,CAACP,CAAL,CACE,KAAMH,EAAA,CAAgB,OAAhB,CAEiDhD,CAFjD,CAAN,CAMF,IAAIyD,EAAc,EAAlB,CAGIE,EAAY,EAHhB,CAKIC,EAASP,CAAA,CAAY,WAAZ,CAAyB,QAAzB,CALb,CAQIK,EAAiB,cAELD,CAFK,YAGPE,CAHO,UAcTR,CAdS,MAuBbnD,CAvBa,UAoCTqD,CAAA,CAAY,UAAZ,CAAwB,UAAxB,CApCS,SA+CVA,CAAA,CAAY,UAAZ,CAAwB,SAAxB,CA/CU,SA0DVA,CAAA,CAAY,UAAZ,CAAwB,SAAxB,CA1DU,OAqEZA,CAAA,CAAY,UAAZ,CAAwB,OAAxB,CArEY,UAiFTA,CAAA,CAAY,UAAZ;AAAwB,UAAxB,CAAoC,SAApC,CAjFS,WAmHRA,CAAA,CAAY,kBAAZ,CAAgC,UAAhC,CAnHQ,QA8HXA,CAAA,CAAY,iBAAZ,CAA+B,UAA/B,CA9HW,YA0IPA,CAAA,CAAY,qBAAZ,CAAmC,UAAnC,CA1IO,WAuJRA,CAAA,CAAY,kBAAZ,CAAgC,WAAhC,CAvJQ,QAkKXO,CAlKW,KA8KdC,QAAQ,CAACC,CAAD,CAAQ,CACnBH,CAAA5L,KAAA,CAAe+L,CAAf,CACA,OAAO,KAFY,CA9KF,CAoLjBV,EAAJ,EACEQ,CAAA,CAAOR,CAAP,CAGF,OAAQM,EAxM8B,CA1ET,EA0E/B,CAX+C,CAvDP,CART,EAQnC,CAdiC,CAiZnCK,QAASA,GAAkB,CAAC3C,CAAD,CAAS,CAClClI,CAAA,CAAOkI,CAAP,CAAgB,WACD1B,EADC,MAENpE,EAFM,QAGJpC,CAHI,QAIJgD,EAJI,SAKHgC,CALG,SAMH5G,CANG,UAOFqJ,EAPE,MAQPhH,CARO,MASPiD,EATO,QAUJU,EAVI,UAWFI,EAXE,UAYH9D,EAZG,aAaCG,CAbD,WAcDC,CAdC,UAeF5C,CAfE,YAgBAM,CAhBA,UAiBFuC,CAjBE,UAkBFC,EAlBE,WAmBDO,EAnBC,SAoBHpD,CApBG;QAqBH2M,EArBG,QAsBJ7J,EAtBI,WAuBD4D,CAvBC,WAwBDkG,EAxBC,WAyBD,SAAU,CAAV,CAzBC,UA0BFnN,CA1BE,OA2BL0F,EA3BK,CAAhB,CA8BA0H,GAAA,CAAgBnB,EAAA,CAAkBpM,CAAlB,CAChB,IAAI,CACFuN,EAAA,CAAc,UAAd,CADE,CAEF,MAAO7F,CAAP,CAAU,CACV6F,EAAA,CAAc,UAAd,CAA0B,EAA1B,CAAAZ,SAAA,CAAuC,SAAvC,CAAkDa,EAAlD,CADU,CAIZD,EAAA,CAAc,IAAd,CAAoB,CAAC,UAAD,CAApB,CAAkC,CAAC,UAAD,CAChCE,QAAiB,CAAC1D,CAAD,CAAW,CAE1BA,CAAA4C,SAAA,CAAkB,eACDe,EADC,CAAlB,CAGA3D,EAAA4C,SAAA,CAAkB,UAAlB,CAA8BgB,EAA9B,CAAAC,UAAA,CACY,GACHC,EADG,OAECC,EAFD,UAGIA,EAHJ,MAIAC,EAJA,QAKEC,EALF,QAMEC,EANF,OAOCC,EAPD,QAQEC,EARF,QASEC,EATF,YAUMC,EAVN,gBAWUC,EAXV,SAYGC,EAZH,aAaOC,EAbP,YAcMC,EAdN,SAeGC,EAfH,cAgBQC,EAhBR,QAiBEC,EAjBF,QAkBEC,EAlBF,MAmBAC,EAnBA,WAoBKC,EApBL;OAqBEC,EArBF,eAsBSC,EAtBT,aAuBOC,EAvBP,UAwBIC,EAxBJ,QAyBEC,EAzBF,SA0BGC,EA1BH,UA2BIC,EA3BJ,cA4BQC,EA5BR,iBA6BWC,EA7BX,WA8BKC,EA9BL,cA+BQC,EA/BR,SAgCGC,EAhCH,QAiCEC,EAjCF,UAkCIC,EAlCJ,UAmCIC,EAnCJ,YAoCMA,EApCN,SAqCGC,EArCH,CADZ,CAAAnC,UAAA,CAwCY,WACGoC,EADH,CAxCZ,CAAApC,UAAA,CA2CYqC,EA3CZ,CAAArC,UAAA,CA4CYsC,EA5CZ,CA6CAnG,EAAA4C,SAAA,CAAkB,eACDwD,EADC,UAENC,EAFM,UAGNC,EAHM,eAIDC,EAJC,aAKHC,EALG,WAMLC,EANK,mBAOGC,EAPH,SAQPC,EARO,cASFC,EATE,WAULC,EAVK,OAWTC,EAXS,cAYFC,EAZE,WAaLC,EAbK,MAcVC,EAdU,QAeRC,EAfQ,YAgBJC,EAhBI;GAiBZC,EAjBY,MAkBVC,EAlBU,cAmBFC,EAnBE,UAoBNC,EApBM,gBAqBAC,EArBA,UAsBNC,EAtBM,SAuBPC,EAvBO,OAwBTC,EAxBS,iBAyBEC,EAzBF,CAAlB,CAlD0B,CADI,CAAlC,CAtCkC,CAwPpCC,QAASA,GAAS,CAACvI,CAAD,CAAO,CACvB,MAAOA,EAAArB,QAAA,CACG6J,EADH,CACyB,QAAQ,CAACC,CAAD,CAAIhH,CAAJ,CAAeE,CAAf,CAAuB+G,CAAvB,CAA+B,CACnE,MAAOA,EAAA,CAAS/G,CAAAgH,YAAA,EAAT,CAAgChH,CAD4B,CADhE,CAAAhD,QAAA,CAIGiK,EAJH,CAIoB,OAJpB,CADgB,CAgBzBC,QAASA,GAAuB,CAAC7I,CAAD,CAAO8I,CAAP,CAAqBC,CAArB,CAAkCC,CAAlC,CAAuD,CAMrFC,QAASA,EAAW,CAACC,CAAD,CAAQ,CAAA,IAEtBjO,EAAO8N,CAAA,EAAeG,CAAf,CAAuB,CAAC,IAAAC,OAAA,CAAYD,CAAZ,CAAD,CAAvB,CAA8C,CAAC,IAAD,CAF/B,CAGtBE,EAAYN,CAHU,CAItBO,CAJsB,CAIjBC,CAJiB,CAIPC,CAJO,CAKtBtL,CALsB,CAKbuL,CALa,CAKYC,CAEtC,IAAI,CAACT,CAAL,EAAqC,IAArC,EAA4BE,CAA5B,CACE,IAAA,CAAMjO,CAAA/D,OAAN,CAAA,CAEE,IADAmS,CACkB,CADZpO,CAAAyO,MAAA,EACY,CAAdJ,CAAc,CAAH,CAAG,CAAAC,CAAA,CAAYF,CAAAnS,OAA9B,CAA0CoS,CAA1C,CAAqDC,CAArD,CAAgED,CAAA,EAAhE,CAOE,IANArL,CAMoB,CANVC,CAAA,CAAOmL,CAAA,CAAIC,CAAJ,CAAP,CAMU,CALhBF,CAAJ,CACEnL,CAAA0L,eAAA,CAAuB,UAAvB,CADF,CAGEP,CAHF,CAGc,CAACA,CAEK,CAAhBI,CAAgB,CAAH,CAAG,CAAAI,CAAA,CAAe1S,CAAAuS,CAAAvS,CAAW+G,CAAAwL,SAAA,EAAXvS,QAAnC,CACIsS,CADJ,CACiBI,CADjB,CAEIJ,CAAA,EAFJ,CAGEvO,CAAAlD,KAAA,CAAU8R,EAAA,CAAOJ,CAAA,CAASD,CAAT,CAAP,CAAV,CAKR,OAAOM,EAAA5M,MAAA,CAAmB,IAAnB,CAAyB9D,SAAzB,CAzBmB,CANyD;AACrF,IAAI0Q,EAAeD,EAAA/M,GAAA,CAAUkD,CAAV,CAAnB,CACA8J,EAAeA,CAAAC,UAAfD,EAAyCA,CACzCb,EAAAc,UAAA,CAAwBD,CACxBD,GAAA/M,GAAA,CAAUkD,CAAV,CAAA,CAAkBiJ,CAJmE,CAyGvFe,QAASA,EAAM,CAAC/L,CAAD,CAAU,CACvB,GAAIA,CAAJ,WAAuB+L,EAAvB,CACE,MAAO/L,EAEL7G,EAAA,CAAS6G,CAAT,CAAJ,GACEA,CADF,CACYgM,EAAA,CAAKhM,CAAL,CADZ,CAGA,IAAI,EAAE,IAAF,WAAkB+L,EAAlB,CAAJ,CAA+B,CAC7B,GAAI5S,CAAA,CAAS6G,CAAT,CAAJ,EAA8C,GAA9C,EAAyBA,CAAAhC,OAAA,CAAe,CAAf,CAAzB,CACE,KAAMiO,GAAA,CAAa,OAAb,CAAN,CAEF,MAAO,KAAIF,CAAJ,CAAW/L,CAAX,CAJsB,CAO/B,GAAI7G,CAAA,CAAS6G,CAAT,CAAJ,CAAuB,CACgBA,IAAAA,EAAAA,CA1BvCzG,EAAA,CAAqBZ,CACrB,KAAIuT,CAEJ,IAAKA,CAAL,CAAcC,EAAAjK,KAAA,CAAuB3B,CAAvB,CAAd,CACS,CAAA,CAAA,CAAA,CAAA,cAAA,CAAA,CAAA,CAAA,CAAA,CAAA,CAAA,CADT,KAAA,CAIO,IAAA,EAAA,CAAA,CA1CQiC,CACX4J,EAAAA,CAAW7S,CAAA8S,uBAAA,EACX3H,EAAAA,CAAQ,EAEZ,IARQ4H,EAAApJ,KAAA,CA8CD3C,CA9CC,CAQR,CAGO,CACLgM,CAAA,CAAMH,CAAAI,YAAA,CAAqBjT,CAAAkT,cAAA,CAAsB,KAAtB,CAArB,CAENjK,EAAA,CAAM,CAACkK,EAAAxK,KAAA,CAgCF3B,CAhCE,CAAD,EAA+B,CAAC,EAAD,CAAK,EAAL,CAA/B,EAAyC,CAAzC,CAAAqD,YAAA,EACN+I,EAAA,CAAOC,EAAA,CAAQpK,CAAR,CAAP,EAAuBoK,EAAAC,SACvBN,EAAAO,UAAA,CAAgB,mBAAhB,CACEH,CAAA,CAAK,CAAL,CADF,CA8BKpM,CA7BOG,QAAA,CAAaqM,EAAb,CAA+B,WAA/B,CADZ,CAC0DJ,CAAA,CAAK,CAAL,CAC1DJ;CAAAS,YAAA,CAAgBT,CAAAU,WAAhB,CAIA,KADAhT,CACA,CADI0S,CAAA,CAAK,CAAL,CACJ,CAAO1S,CAAA,EAAP,CAAA,CACEsS,CAAA,CAAMA,CAAAW,UAGHC,EAAA,CAAE,CAAP,KAAUC,CAAV,CAAab,CAAAc,WAAApU,OAAb,CAAoCkU,CAApC,CAAsCC,CAAtC,CAA0C,EAAED,CAA5C,CAA+CzI,CAAA5K,KAAA,CAAWyS,CAAAc,WAAA,CAAeF,CAAf,CAAX,CAE/CZ,EAAA,CAAMH,CAAAa,WACNV,EAAAe,YAAA,CAAkB,EAlBb,CAHP,IAEE5I,EAAA5K,KAAA,CAAWP,CAAAgU,eAAA,CAoCNhN,CApCM,CAAX,CAuBF6L,EAAAkB,YAAA,CAAuB,EACvBlB,EAAAU,UAAA,CAAqB,EACrB,EAAA,CAAOpI,CAOP,CAuBE8I,EAAA,CAAe,IAAf,CAvBF,CAuBE,CACevN,EAAAmM,CAAOzT,CAAA0T,uBAAA,EAAPD,CACf9L,OAAA,CAAgB,IAAhB,CAHqB,CAAvB,IAKEkN,GAAA,CAAe,IAAf,CAAqBxN,CAArB,CAnBqB,CAuBzByN,QAASA,GAAW,CAACzN,CAAD,CAAU,CAC5B,MAAOA,EAAA0N,UAAA,CAAkB,CAAA,CAAlB,CADqB,CAI9BC,QAASA,GAAY,CAAC3N,CAAD,CAAS,CAC5B4N,EAAA,CAAiB5N,CAAjB,CAD4B,KAElB/F,EAAI,CAAd,KAAiBuR,CAAjB,CAA4BxL,CAAAqN,WAA5B,EAAkD,EAAlD,CAAsDpT,CAAtD,CAA0DuR,CAAAvS,OAA1D,CAA2EgB,CAAA,EAA3E,CACE0T,EAAA,CAAanC,CAAA,CAASvR,CAAT,CAAb,CAH0B,CAO9B4T,QAASA,GAAS,CAAC7N,CAAD,CAAU8N,CAAV,CAAgBjP,CAAhB,CAAoBkP,CAApB,CAAiC,CACjD,GAAIhS,CAAA,CAAUgS,CAAV,CAAJ,CAA4B,KAAM9B,GAAA,CAAa,SAAb,CAAN,CADqB,IAG7C+B,EAASC,EAAA,CAAmBjO,CAAnB,CAA4B,QAA5B,CACAiO,GAAAC,CAAmBlO,CAAnBkO,CAA4B,QAA5BA,CAEb,GAEIpS,CAAA,CAAYgS,CAAZ,CAAJ,CACEzU,CAAA,CAAQ2U,CAAR;AAAgB,QAAQ,CAACG,CAAD,CAAeL,CAAf,CAAqB,CAC3CM,EAAA,CAAsBpO,CAAtB,CAA+B8N,CAA/B,CAAqCK,CAArC,CACA,QAAOH,CAAA,CAAOF,CAAP,CAFoC,CAA7C,CADF,CAMEzU,CAAA,CAAQyU,CAAA9M,MAAA,CAAW,GAAX,CAAR,CAAyB,QAAQ,CAAC8M,CAAD,CAAO,CAClChS,CAAA,CAAY+C,CAAZ,CAAJ,EACEuP,EAAA,CAAsBpO,CAAtB,CAA+B8N,CAA/B,CAAqCE,CAAA,CAAOF,CAAP,CAArC,CACA,CAAA,OAAOE,CAAA,CAAOF,CAAP,CAFT,EAIE3Q,EAAA,CAAY6Q,CAAA,CAAOF,CAAP,CAAZ,EAA4B,EAA5B,CAAgCjP,CAAhC,CALoC,CAAxC,CARF,CANiD,CAyBnD+O,QAASA,GAAgB,CAAC5N,CAAD,CAAU+B,CAAV,CAAgB,CAAA,IACnCsM,EAAYrO,CAAA,CAAQsO,EAAR,CADuB,CAEnCC,EAAeC,EAAA,CAAQH,CAAR,CAEfE,EAAJ,GACMxM,CAAJ,CACE,OAAOyM,EAAA,CAAQH,CAAR,CAAArL,KAAA,CAAwBjB,CAAxB,CADT,EAKIwM,CAAAL,OAKJ,GAJEK,CAAAP,OAAAS,SACA,EADgCF,CAAAL,OAAA,CAAoB,EAApB,CAAwB,UAAxB,CAChC,CAAAL,EAAA,CAAU7N,CAAV,CAGF,EADA,OAAOwO,EAAA,CAAQH,CAAR,CACP,CAAArO,CAAA,CAAQsO,EAAR,CAAA,CAAkB1V,CAVlB,CADF,CAJuC,CAmBzCqV,QAASA,GAAkB,CAACjO,CAAD,CAAUxG,CAAV,CAAeY,CAAf,CAAsB,CAAA,IAC3CiU,EAAYrO,CAAA,CAAQsO,EAAR,CAD+B,CAE3CC,EAAeC,EAAA,CAAQH,CAAR,EAAsB,EAAtB,CAEnB,IAAItS,CAAA,CAAU3B,CAAV,CAAJ,CACOmU,CAIL,GAHEvO,CAAA,CAAQsO,EAAR,CACA,CADkBD,CAClB,CA1NuB,EAAEK,EA0NzB,CAAAH,CAAA,CAAeC,EAAA,CAAQH,CAAR,CAAf,CAAoC,EAEtC,EAAAE,CAAA,CAAa/U,CAAb,CAAA,CAAoBY,CALtB,KAOE,OAAOmU,EAAP,EAAuBA,CAAA,CAAa/U,CAAb,CAXsB,CAejDmV,QAASA,GAAU,CAAC3O,CAAD,CAAUxG,CAAV,CAAeY,CAAf,CAAsB,CAAA,IACnC4I,EAAOiL,EAAA,CAAmBjO,CAAnB,CAA4B,MAA5B,CAD4B,CAEnC4O,EAAW7S,CAAA,CAAU3B,CAAV,CAFwB,CAGnCyU,EAAa,CAACD,CAAdC,EAA0B9S,CAAA,CAAUvC,CAAV,CAHS,CAInCsV,EAAiBD,CAAjBC,EAA+B,CAAC9S,CAAA,CAASxC,CAAT,CAE/BwJ,EAAL,EAAc8L,CAAd,EACEb,EAAA,CAAmBjO,CAAnB,CAA4B,MAA5B,CAAoCgD,CAApC,CAA2C,EAA3C,CAGF,IAAI4L,CAAJ,CACE5L,CAAA,CAAKxJ,CAAL,CAAA,CAAYY,CADd,KAGE,IAAIyU,CAAJ,CAAgB,CACd,GAAIC,CAAJ,CAEE,MAAO9L,EAAP,EAAeA,CAAA,CAAKxJ,CAAL,CAEfyB;CAAA,CAAO+H,CAAP,CAAaxJ,CAAb,CALY,CAAhB,IAQE,OAAOwJ,EArB4B,CA0BzC+L,QAASA,GAAc,CAAC/O,CAAD,CAAUgP,CAAV,CAAoB,CACzC,MAAKhP,EAAAiP,aAAL,CAEuC,EAFvC,CACSvO,CAAA,GAAAA,EAAOV,CAAAiP,aAAA,CAAqB,OAArB,CAAPvO,EAAwC,EAAxCA,EAA8C,GAA9CA,SAAA,CAA2D,SAA3D,CAAsE,GAAtE,CAAAzD,QAAA,CACI,GADJ,CACU+R,CADV,CACqB,GADrB,CADT,CAAkC,CAAA,CADO,CAM3CE,QAASA,GAAiB,CAAClP,CAAD,CAAUmP,CAAV,CAAsB,CAC1CA,CAAJ,EAAkBnP,CAAAoP,aAAlB,EACE/V,CAAA,CAAQ8V,CAAAnO,MAAA,CAAiB,GAAjB,CAAR,CAA+B,QAAQ,CAACqO,CAAD,CAAW,CAChDrP,CAAAoP,aAAA,CAAqB,OAArB,CAA8BpD,EAAA,CACzBtL,CAAA,GAAAA,EAAOV,CAAAiP,aAAA,CAAqB,OAArB,CAAPvO,EAAwC,EAAxCA,EAA8C,GAA9CA,SAAA,CACQ,SADR,CACmB,GADnB,CAAAA,QAAA,CAEQ,GAFR,CAEcsL,EAAA,CAAKqD,CAAL,CAFd,CAE+B,GAF/B,CAEoC,GAFpC,CADyB,CAA9B,CADgD,CAAlD,CAF4C,CAYhDC,QAASA,GAAc,CAACtP,CAAD,CAAUmP,CAAV,CAAsB,CAC3C,GAAIA,CAAJ,EAAkBnP,CAAAoP,aAAlB,CAAwC,CACtC,IAAIG,EAAmB7O,CAAA,GAAAA,EAAOV,CAAAiP,aAAA,CAAqB,OAArB,CAAPvO,EAAwC,EAAxCA,EAA8C,GAA9CA,SAAA,CACU,SADV,CACqB,GADrB,CAGvBrH,EAAA,CAAQ8V,CAAAnO,MAAA,CAAiB,GAAjB,CAAR,CAA+B,QAAQ,CAACqO,CAAD,CAAW,CAChDA,CAAA,CAAWrD,EAAA,CAAKqD,CAAL,CAC4C,GAAvD,GAAIE,CAAAtS,QAAA,CAAwB,GAAxB,CAA8BoS,CAA9B,CAAyC,GAAzC,CAAJ;CACEE,CADF,EACqBF,CADrB,CACgC,GADhC,CAFgD,CAAlD,CAOArP,EAAAoP,aAAA,CAAqB,OAArB,CAA8BpD,EAAA,CAAKuD,CAAL,CAA9B,CAXsC,CADG,CAgB7C/B,QAASA,GAAc,CAACgC,CAAD,CAAO9N,CAAP,CAAiB,CACtC,GAAIA,CAAJ,CAAc,CACZA,CAAA,CAAaA,CAAAhF,SACF,EADuB,CAAAX,CAAA,CAAU2F,CAAAzI,OAAV,CACvB,EADsDD,EAAA,CAAS0I,CAAT,CACtD,CACP,CAAEA,CAAF,CADO,CAAPA,CAEJ,KAAI,IAAIzH,EAAE,CAAV,CAAaA,CAAb,CAAiByH,CAAAzI,OAAjB,CAAkCgB,CAAA,EAAlC,CACEuV,CAAA1V,KAAA,CAAU4H,CAAA,CAASzH,CAAT,CAAV,CALU,CADwB,CAWxCwV,QAASA,GAAgB,CAACzP,CAAD,CAAU+B,CAAV,CAAgB,CACvC,MAAO2N,GAAA,CAAoB1P,CAApB,CAA6B,GAA7B,EAAoC+B,CAApC,EAA4C,cAA5C,EAA+D,YAA/D,CADgC,CAIzC2N,QAASA,GAAmB,CAAC1P,CAAD,CAAU+B,CAAV,CAAgB3H,CAAhB,CAAuB,CACjD4F,CAAA,CAAUC,CAAA,CAAOD,CAAP,CAIgB,EAA1B,EAAGA,CAAA,CAAQ,CAAR,CAAA9G,SAAH,GACE8G,CADF,CACYA,CAAAnD,KAAA,CAAa,MAAb,CADZ,CAKA,KAFIgF,CAEJ,CAFYzI,CAAA,CAAQ2I,CAAR,CAAA,CAAgBA,CAAhB,CAAuB,CAACA,CAAD,CAEnC,CAAO/B,CAAA/G,OAAP,CAAA,CAAuB,CAErB,IADA,IAAIwD,EAAOuD,CAAA,CAAQ,CAAR,CAAX,CACS/F,EAAI,CADb,CACgB0V,EAAK9N,CAAA5I,OAArB,CAAmCgB,CAAnC,CAAuC0V,CAAvC,CAA2C1V,CAAA,EAA3C,CACE,IAAKG,CAAL,CAAa4F,CAAAgD,KAAA,CAAanB,CAAA,CAAM5H,CAAN,CAAb,CAAb,IAAyCrB,CAAzC,CAAoD,MAAOwB,EAM7D4F,EAAA,CAAUC,CAAA,CAAOxD,CAAAmT,WAAP,EAA6C,EAA7C,GAA2BnT,CAAAvD,SAA3B,EAAmDuD,CAAAoT,KAAnD,CATW,CAV0B,CAuBnDC,QAASA,GAAW,CAAC9P,CAAD,CAAU,CAC5B,IAD4B,IACnB/F,EAAI,CADe,CACZoT,EAAarN,CAAAqN,WAA7B,CAAiDpT,CAAjD,CAAqDoT,CAAApU,OAArD,CAAwEgB,CAAA,EAAxE,CACE0T,EAAA,CAAaN,CAAA,CAAWpT,CAAX,CAAb,CAEF,KAAA,CAAO+F,CAAAiN,WAAP,CAAA,CACEjN,CAAAgN,YAAA,CAAoBhN,CAAAiN,WAApB,CAL0B,CAp7ES;AAm/EvC8C,QAASA,GAAkB,CAAC/P,CAAD,CAAU+B,CAAV,CAAgB,CAEzC,IAAIiO,EAAcC,EAAA,CAAalO,CAAA6B,YAAA,EAAb,CAGlB,OAAOoM,EAAP,EAAsBE,EAAA,CAAiBlQ,CAAAtD,SAAjB,CAAtB,EAA4DsT,CALnB,CAgM3CG,QAASA,GAAkB,CAACnQ,CAAD,CAAUgO,CAAV,CAAkB,CAC3C,IAAIG,EAAeA,QAAS,CAACiC,CAAD,CAAQtC,CAAR,CAAc,CACnCsC,CAAAC,eAAL,GACED,CAAAC,eADF,CACyBC,QAAQ,EAAG,CAChCF,CAAAG,YAAA,CAAoB,CAAA,CADY,CADpC,CAMKH,EAAAI,gBAAL,GACEJ,CAAAI,gBADF,CAC0BC,QAAQ,EAAG,CACjCL,CAAAM,aAAA,CAAqB,CAAA,CADY,CADrC,CAMKN,EAAAO,OAAL,GACEP,CAAAO,OADF,CACiBP,CAAAQ,WADjB,EACqCjY,CADrC,CAIA,IAAImD,CAAA,CAAYsU,CAAAS,iBAAZ,CAAJ,CAAyC,CACvC,IAAIC,EAAUV,CAAAC,eACdD,EAAAC,eAAA,CAAuBC,QAAQ,EAAG,CAChCF,CAAAS,iBAAA,CAAyB,CAAA,CACzBC,EAAAnX,KAAA,CAAayW,CAAb,CAFgC,CAIlCA,EAAAS,iBAAA,CAAyB,CAAA,CANc,CASzCT,CAAAW,mBAAA,CAA2BC,QAAQ,EAAG,CACpC,MAAOZ,EAAAS,iBAAP,EAAuD,CAAA,CAAvD,GAAiCT,CAAAG,YADG,CAKtC,KAAIU,EAAoBnT,EAAA,CAAYkQ,CAAA,CAAOF,CAAP;AAAesC,CAAAtC,KAAf,CAAZ,EAA0C,EAA1C,CAExBzU,EAAA,CAAQ4X,CAAR,CAA2B,QAAQ,CAACpS,CAAD,CAAK,CACtCA,CAAAlF,KAAA,CAAQqG,CAAR,CAAiBoQ,CAAjB,CADsC,CAAxC,CAMY,EAAZ,EAAIc,CAAJ,EAEEd,CAAAC,eAEA,CAFuB,IAEvB,CADAD,CAAAI,gBACA,CADwB,IACxB,CAAAJ,CAAAW,mBAAA,CAA2B,IAJ7B,GAOE,OAAOX,CAAAC,eAEP,CADA,OAAOD,CAAAI,gBACP,CAAA,OAAOJ,CAAAW,mBATT,CAvCwC,CAmD1C5C,EAAAgD,KAAA,CAAoBnR,CACpB,OAAOmO,EArDoC,CA+S7CiD,QAASA,GAAO,CAACrY,CAAD,CAAM,CAAA,IAChBsY,EAAU,MAAOtY,EADD,CAEhBS,CAEW,SAAf,EAAI6X,CAAJ,EAAmC,IAAnC,GAA2BtY,CAA3B,CACsC,UAApC,EAAI,OAAQS,CAAR,CAAcT,CAAAiC,UAAd,CAAJ,CAEExB,CAFF,CAEQT,CAAAiC,UAAA,EAFR,CAGWxB,CAHX,GAGmBZ,CAHnB,GAIEY,CAJF,CAIQT,CAAAiC,UAJR,CAIwBX,EAAA,EAJxB,CADF,CAQEb,CARF,CAQQT,CAGR,OAAOsY,EAAP,CAAiB,GAAjB,CAAuB7X,CAfH,CAqBtB8X,QAASA,GAAO,CAACpU,CAAD,CAAO,CACrB7D,CAAA,CAAQ6D,CAAR,CAAe,IAAAqU,IAAf,CAAyB,IAAzB,CADqB,CAkGvBC,QAASA,GAAQ,CAAC3S,CAAD,CAAK,CAAA,IAChB4S,CADgB,CAEhBC,CAIa,WAAjB,EAAI,MAAO7S,EAAX,EACQ4S,CADR,CACkB5S,CAAA4S,QADlB,IAEIA,CAUA,CAVU,EAUV,CATI5S,CAAA5F,OASJ,GAREyY,CAEA,CAFS7S,CAAA1C,SAAA,EAAAuE,QAAA,CAAsBiR,EAAtB;AAAsC,EAAtC,CAET,CADAC,CACA,CADUF,CAAAjR,MAAA,CAAaoR,EAAb,CACV,CAAAxY,CAAA,CAAQuY,CAAA,CAAQ,CAAR,CAAA5Q,MAAA,CAAiB8Q,EAAjB,CAAR,CAAwC,QAAQ,CAAChO,CAAD,CAAK,CACnDA,CAAApD,QAAA,CAAYqR,EAAZ,CAAoB,QAAQ,CAACC,CAAD,CAAMC,CAAN,CAAkBlQ,CAAlB,CAAuB,CACjD0P,CAAA3X,KAAA,CAAaiI,CAAb,CADiD,CAAnD,CADmD,CAArD,CAMF,EAAAlD,CAAA4S,QAAA,CAAaA,CAZjB,EAcWrY,CAAA,CAAQyF,CAAR,CAAJ,EACLqT,CAEA,CAFOrT,CAAA5F,OAEP,CAFmB,CAEnB,CADA+K,EAAA,CAAYnF,CAAA,CAAGqT,CAAH,CAAZ,CAAsB,IAAtB,CACA,CAAAT,CAAA,CAAU5S,CAAAE,MAAA,CAAS,CAAT,CAAYmT,CAAZ,CAHL,EAKLlO,EAAA,CAAYnF,CAAZ,CAAgB,IAAhB,CAAsB,CAAA,CAAtB,CAEF,OAAO4S,EA3Ba,CAygBtB/O,QAASA,GAAc,CAACyP,CAAD,CAAgB,CAmCrCC,QAASA,EAAa,CAACC,CAAD,CAAW,CAC/B,MAAO,SAAQ,CAAC7Y,CAAD,CAAMY,CAAN,CAAa,CAC1B,GAAI4B,CAAA,CAASxC,CAAT,CAAJ,CACEH,CAAA,CAAQG,CAAR,CAAaU,EAAA,CAAcmY,CAAd,CAAb,CADF,KAGE,OAAOA,EAAA,CAAS7Y,CAAT,CAAcY,CAAd,CAJiB,CADG,CAUjCiL,QAASA,EAAQ,CAACtD,CAAD,CAAOuQ,CAAP,CAAkB,CACjCnO,EAAA,CAAwBpC,CAAxB,CAA8B,SAA9B,CACA,IAAItI,CAAA,CAAW6Y,CAAX,CAAJ,EAA6BlZ,CAAA,CAAQkZ,CAAR,CAA7B,CACEA,CAAA,CAAYC,CAAAC,YAAA,CAA6BF,CAA7B,CAEd,IAAI,CAACA,CAAAG,KAAL,CACE,KAAM1N,GAAA,CAAgB,MAAhB,CAA2EhD,CAA3E,CAAN,CAEF,MAAO2Q,EAAA,CAAc3Q,CAAd,CAAqB4Q,CAArB,CAAP,CAA8CL,CARb,CAWnCrN,QAASA,EAAO,CAAClD,CAAD,CAAO6Q,CAAP,CAAkB,CAAE,MAAOvN,EAAA,CAAStD,CAAT,CAAe,MAAQ6Q,CAAR,CAAf,CAAT,CA6BlCC,QAASA,EAAW,CAACV,CAAD,CAAe,CAAA,IAC7BzM,EAAY,EADiB,CACboN,CADa,CACHtN,CADG,CACUvL,CADV,CACa0V,CAC9CtW,EAAA,CAAQ8Y,CAAR,CAAuB,QAAQ,CAACvQ,CAAD,CAAS,CACtC,GAAI,CAAAmR,CAAAC,IAAA,CAAkBpR,CAAlB,CAAJ,CAAA,CACAmR,CAAAxB,IAAA,CAAkB3P,CAAlB,CAA0B,CAAA,CAA1B,CAEA,IAAI,CACF,GAAIzI,CAAA,CAASyI,CAAT,CAAJ,CAIE,IAHAkR,CAGgD;AAHrC7M,EAAA,CAAcrE,CAAd,CAGqC,CAFhD8D,CAEgD,CAFpCA,CAAAxG,OAAA,CAAiB2T,CAAA,CAAYC,CAAA5N,SAAZ,CAAjB,CAAAhG,OAAA,CAAwD4T,CAAAG,WAAxD,CAEoC,CAA5CzN,CAA4C,CAA9BsN,CAAAI,aAA8B,CAAPjZ,CAAO,CAAH,CAAG,CAAA0V,CAAA,CAAKnK,CAAAvM,OAArD,CAAyEgB,CAAzE,CAA6E0V,CAA7E,CAAiF1V,CAAA,EAAjF,CAAsF,CAAA,IAChFkZ,EAAa3N,CAAA,CAAYvL,CAAZ,CADmE,CAEhFoL,EAAWkN,CAAAS,IAAA,CAAqBG,CAAA,CAAW,CAAX,CAArB,CAEf9N,EAAA,CAAS8N,CAAA,CAAW,CAAX,CAAT,CAAAlU,MAAA,CAA8BoG,CAA9B,CAAwC8N,CAAA,CAAW,CAAX,CAAxC,CAJoF,CAJxF,IAUW1Z,EAAA,CAAWmI,CAAX,CAAJ,CACH8D,CAAA5L,KAAA,CAAeyY,CAAA5P,OAAA,CAAwBf,CAAxB,CAAf,CADG,CAEIxI,CAAA,CAAQwI,CAAR,CAAJ,CACH8D,CAAA5L,KAAA,CAAeyY,CAAA5P,OAAA,CAAwBf,CAAxB,CAAf,CADG,CAGLoC,EAAA,CAAYpC,CAAZ,CAAoB,QAApB,CAhBA,CAkBF,MAAOxB,CAAP,CAAU,CAYV,KAXIhH,EAAA,CAAQwI,CAAR,CAWE,GAVJA,CAUI,CAVKA,CAAA,CAAOA,CAAA3I,OAAP,CAAuB,CAAvB,CAUL,EARFmH,CAAAgT,QAQE,GARWhT,CAAAiT,MAQX,EARqD,EAQrD,EARsBjT,CAAAiT,MAAApW,QAAA,CAAgBmD,CAAAgT,QAAhB,CAQtB,IAFJhT,CAEI,CAFAA,CAAAgT,QAEA,CAFY,IAEZ,CAFmBhT,CAAAiT,MAEnB,EAAAtO,EAAA,CAAgB,UAAhB,CACInD,CADJ,CACYxB,CAAAiT,MADZ,EACuBjT,CAAAgT,QADvB,EACoChT,CADpC,CAAN,CAZU,CArBZ,CADsC,CAAxC,CAsCA,OAAOsF,EAxC0B,CA+CnC4N,QAASA,EAAsB,CAACC,CAAD,CAAQtO,CAAR,CAAiB,CAE9CuO,QAASA,EAAU,CAACC,CAAD,CAAc,CAC/B,GAAIF,CAAA7Z,eAAA,CAAqB+Z,CAArB,CAAJ,CAAuC,CACrC,GAAIF,CAAA,CAAME,CAAN,CAAJ,GAA2BC,CAA3B,CACE,KAAM3O,GAAA,CAAgB,MAAhB,CAA0DV,CAAA3J,KAAA,CAAU,MAAV,CAA1D,CAAN,CAEF,MAAO6Y,EAAA,CAAME,CAAN,CAJ8B,CAMrC,GAAI,CAGF,MAFApP,EAAAxJ,QAAA,CAAa4Y,CAAb,CAEO;AADPF,CAAA,CAAME,CAAN,CACO,CADcC,CACd,CAAAH,CAAA,CAAME,CAAN,CAAA,CAAqBxO,CAAA,CAAQwO,CAAR,CAH1B,CAIF,MAAOE,CAAP,CAAY,CAIZ,KAHIJ,EAAA,CAAME,CAAN,CAGEE,GAHqBD,CAGrBC,EAFJ,OAAOJ,CAAA,CAAME,CAAN,CAEHE,CAAAA,CAAN,CAJY,CAJd,OASU,CACRtP,CAAAoH,MAAA,EADQ,CAhBmB,CAsBjC9I,QAASA,EAAM,CAAC9D,CAAD,CAAKD,CAAL,CAAWgV,CAAX,CAAkB,CAAA,IAC3BC,EAAO,EADoB,CAE3BpC,EAAUD,EAAA,CAAS3S,CAAT,CAFiB,CAG3B5F,CAH2B,CAGnBgB,CAHmB,CAI3BT,CAEAS,EAAA,CAAI,CAAR,KAAWhB,CAAX,CAAoBwY,CAAAxY,OAApB,CAAoCgB,CAApC,CAAwChB,CAAxC,CAAgDgB,CAAA,EAAhD,CAAqD,CACnDT,CAAA,CAAMiY,CAAA,CAAQxX,CAAR,CACN,IAAmB,QAAnB,GAAI,MAAOT,EAAX,CACE,KAAMuL,GAAA,CAAgB,MAAhB,CACyEvL,CADzE,CAAN,CAGFqa,CAAA/Z,KAAA,CACE8Z,CACA,EADUA,CAAAla,eAAA,CAAsBF,CAAtB,CACV,CAAEoa,CAAA,CAAOpa,CAAP,CAAF,CACEga,CAAA,CAAWha,CAAX,CAHJ,CANmD,CAYhDqF,CAAA4S,QAAL,GAEE5S,CAFF,CAEOA,CAAA,CAAG5F,CAAH,CAFP,CAOA,OAAO4F,EAAAI,MAAA,CAASL,CAAT,CAAeiV,CAAf,CAzBwB,CAyCjC,MAAO,QACGlR,CADH,aAbP6P,QAAoB,CAACsB,CAAD,CAAOF,CAAP,CAAe,CAAA,IAC7BG,EAAcA,QAAQ,EAAG,EADI,CAEnBC,CAIdD,EAAAE,UAAA,CAAyBA,CAAA7a,CAAA,CAAQ0a,CAAR,CAAA,CAAgBA,CAAA,CAAKA,CAAA7a,OAAL,CAAmB,CAAnB,CAAhB,CAAwC6a,CAAxCG,WACzBC,EAAA,CAAW,IAAIH,CACfC,EAAA,CAAgBrR,CAAA,CAAOmR,CAAP,CAAaI,CAAb,CAAuBN,CAAvB,CAEhB,OAAO5X,EAAA,CAASgY,CAAT,CAAA,EAA2Bva,CAAA,CAAWua,CAAX,CAA3B,CAAuDA,CAAvD,CAAuEE,CAV7C,CAa5B,KAGAV,CAHA,UAIKhC,EAJL,KAKA2C,QAAQ,CAACpS,CAAD,CAAO,CAClB,MAAO2Q,EAAAhZ,eAAA,CAA6BqI,CAA7B,CAAoC4Q,CAApC,CAAP,EAA8DY,CAAA7Z,eAAA,CAAqBqI,CAArB,CAD5C,CALf,CAjEuC,CApIX;AAAA,IACjC2R,EAAgB,EADiB,CAEjCf,EAAiB,UAFgB,CAGjCtO,EAAO,EAH0B,CAIjC0O,EAAgB,IAAIzB,EAJa,CAKjCoB,EAAgB,UACJ,UACIN,CAAA,CAAc/M,CAAd,CADJ,SAEG+M,CAAA,CAAcnN,CAAd,CAFH,SAGGmN,CAAA,CAiDnBgC,QAAgB,CAACrS,CAAD,CAAOmC,CAAP,CAAoB,CAClC,MAAOe,EAAA,CAAQlD,CAAR,CAAc,CAAC,WAAD,CAAc,QAAQ,CAACsS,CAAD,CAAY,CACrD,MAAOA,EAAA7B,YAAA,CAAsBtO,CAAtB,CAD8C,CAAlC,CAAd,CAD2B,CAjDjB,CAHH,OAICkO,CAAA,CAsDjBhY,QAAc,CAAC2H,CAAD,CAAO3C,CAAP,CAAY,CAAE,MAAO6F,EAAA,CAAQlD,CAAR,CAAclG,EAAA,CAAQuD,CAAR,CAAd,CAAT,CAtDT,CAJD,UAKIgT,CAAA,CAuDpBkC,QAAiB,CAACvS,CAAD,CAAO3H,CAAP,CAAc,CAC7B+J,EAAA,CAAwBpC,CAAxB,CAA8B,UAA9B,CACA2Q,EAAA,CAAc3Q,CAAd,CAAA,CAAsB3H,CACtBma,EAAA,CAAcxS,CAAd,CAAA,CAAsB3H,CAHO,CAvDX,CALJ,WAkEhBoa,QAAkB,CAACf,CAAD,CAAcgB,CAAd,CAAuB,CAAA,IACnCC,EAAenC,CAAAS,IAAA,CAAqBS,CAArB,CAAmCd,CAAnC,CADoB,CAEnCgC,EAAWD,CAAAjC,KAEfiC,EAAAjC,KAAA,CAAoBmC,QAAQ,EAAG,CAC7B,IAAIC,EAAeC,CAAAnS,OAAA,CAAwBgS,CAAxB,CAAkCD,CAAlC,CACnB,OAAOI,EAAAnS,OAAA,CAAwB8R,CAAxB,CAAiC,IAAjC,CAAuC,WAAYI,CAAZ,CAAvC,CAFsB,CAJQ,CAlEzB,CADI,CALiB,CAejCtC,EAAoBG,CAAA2B,UAApB9B,CACIe,CAAA,CAAuBZ,CAAvB,CAAsC,QAAQ,EAAG,CAC/C,KAAM3N,GAAA,CAAgB,MAAhB,CAAiDV,CAAA3J,KAAA,CAAU,MAAV,CAAjD,CAAN,CAD+C,CAAjD,CAhB6B,CAmBjC6Z,EAAgB,EAnBiB,CAoBjCO,EAAoBP,CAAAF,UAApBS,CACIxB,CAAA,CAAuBiB,CAAvB,CAAsC,QAAQ,CAACQ,CAAD,CAAc,CACtD1P,CAAAA,CAAWkN,CAAAS,IAAA,CAAqB+B,CAArB;AAAmCpC,CAAnC,CACf,OAAOmC,EAAAnS,OAAA,CAAwB0C,CAAAoN,KAAxB,CAAuCpN,CAAvC,CAFmD,CAA5D,CAMRhM,EAAA,CAAQwZ,CAAA,CAAYV,CAAZ,CAAR,CAAoC,QAAQ,CAACtT,CAAD,CAAK,CAAEiW,CAAAnS,OAAA,CAAwB9D,CAAxB,EAA8BnD,CAA9B,CAAF,CAAjD,CAEA,OAAOoZ,EA7B8B,CAkQvCjM,QAASA,GAAqB,EAAG,CAE/B,IAAImM,EAAuB,CAAA,CAE3B,KAAAC,qBAAA,CAA4BC,QAAQ,EAAG,CACrCF,CAAA,CAAuB,CAAA,CADc,CAIvC,KAAAvC,KAAA,CAAY,CAAC,SAAD,CAAY,WAAZ,CAAyB,YAAzB,CAAuC,QAAQ,CAAC0C,CAAD,CAAUC,CAAV,CAAqBC,CAArB,CAAiC,CAO1FC,QAASA,EAAc,CAACtY,CAAD,CAAO,CAC5B,IAAIuY,EAAS,IACblc,EAAA,CAAQ2D,CAAR,CAAc,QAAQ,CAACgD,CAAD,CAAU,CACzBuV,CAAL,EAA+C,GAA/C,GAAezV,CAAA,CAAUE,CAAAtD,SAAV,CAAf,GAAoD6Y,CAApD,CAA6DvV,CAA7D,CAD8B,CAAhC,CAGA,OAAOuV,EALqB,CAQ9BC,QAASA,EAAM,EAAG,CAAA,IACZC,EAAOL,CAAAK,KAAA,EADK,CACaC,CAGxBD,EAAL,CAGK,CAAKC,CAAL,CAAW/c,CAAAqJ,eAAA,CAAwByT,CAAxB,CAAX,EAA2CC,CAAAC,eAAA,EAA3C,CAGA,CAAKD,CAAL,CAAWJ,CAAA,CAAe3c,CAAAid,kBAAA,CAA2BH,CAA3B,CAAf,CAAX,EAA8DC,CAAAC,eAAA,EAA9D,CAGa,KAHb,GAGIF,CAHJ,EAGoBN,CAAAU,SAAA,CAAiB,CAAjB,CAAoB,CAApB,CATzB,CAAWV,CAAAU,SAAA,CAAiB,CAAjB,CAAoB,CAApB,CAJK,CAdlB,IAAIld,EAAWwc,CAAAxc,SAgCXqc,EAAJ,EACEK,CAAA5X,OAAA,CAAkBqY,QAAwB,EAAG,CAAC,MAAOV,EAAAK,KAAA,EAAR,CAA7C;AACEM,QAA8B,EAAG,CAC/BV,CAAA7X,WAAA,CAAsBgY,CAAtB,CAD+B,CADnC,CAMF,OAAOA,EAxCmF,CAAhF,CARmB,CA0SjCnL,QAASA,GAAuB,EAAE,CAChC,IAAAoI,KAAA,CAAY,CAAC,OAAD,CAAU,UAAV,CAAsB,QAAQ,CAACuD,CAAD,CAAQC,CAAR,CAAkB,CAC1D,MAAOD,EAAAE,UACA,CAAH,QAAQ,CAACrX,CAAD,CAAK,CAAE,MAAOmX,EAAA,CAAMnX,CAAN,CAAT,CAAV,CACH,QAAQ,CAACA,CAAD,CAAK,CACb,MAAOoX,EAAA,CAASpX,CAAT,CAAa,CAAb,CAAgB,CAAA,CAAhB,CADM,CAHyC,CAAhD,CADoB,CAgClCsX,QAASA,GAAO,CAACzd,CAAD,CAASC,CAAT,CAAmByd,CAAnB,CAAyBC,CAAzB,CAAmC,CAsBjDC,QAASA,EAA0B,CAACzX,CAAD,CAAK,CACtC,GAAI,CACFA,CAAAI,MAAA,CAAS,IAAT,CArvGGF,EAAApF,KAAA,CAqvGsBwB,SArvGtB,CAqvGiC6D,CArvGjC,CAqvGH,CADE,CAAJ,OAEU,CAER,GADAuX,CAAA,EACI,CAA4B,CAA5B,GAAAA,CAAJ,CACE,IAAA,CAAMC,CAAAvd,OAAN,CAAA,CACE,GAAI,CACFud,CAAAC,IAAA,EAAA,EADE,CAEF,MAAOrW,CAAP,CAAU,CACVgW,CAAAM,MAAA,CAAWtW,CAAX,CADU,CANR,CAH4B,CAmExCuW,QAASA,EAAW,CAACC,CAAD,CAAWC,CAAX,CAAuB,CACxCC,SAASA,EAAK,EAAG,CAChBzd,CAAA,CAAQ0d,CAAR,CAAiB,QAAQ,CAACC,CAAD,CAAQ,CAAEA,CAAA,EAAF,CAAjC,CACAC,EAAA,CAAcJ,CAAA,CAAWC,CAAX,CAAkBF,CAAlB,CAFE,CAAjBE,CAAA,EADwC,CAuE3CI,QAASA,EAAa,EAAG,CACvBC,CAAA,CAAc,IACVC,EAAJ,EAAsBxY,CAAAyY,IAAA,EAAtB,GAEAD,CACA,CADiBxY,CAAAyY,IAAA,EACjB,CAAAhe,CAAA,CAAQie,EAAR,CAA4B,QAAQ,CAACC,CAAD,CAAW,CAC7CA,CAAA,CAAS3Y,CAAAyY,IAAA,EAAT,CAD6C,CAA/C,CAHA,CAFuB,CAhKwB,IAC7CzY,EAAO,IADsC,CAE7C4Y,EAAc7e,CAAA,CAAS,CAAT,CAF+B,CAG7C0D,EAAW3D,CAAA2D,SAHkC,CAI7Cob,EAAU/e,CAAA+e,QAJmC;AAK7CZ,EAAane,CAAAme,WALgC,CAM7Ca,EAAehf,CAAAgf,aAN8B,CAO7CC,EAAkB,EAEtB/Y,EAAAgZ,OAAA,CAAc,CAAA,CAEd,KAAIrB,EAA0B,CAA9B,CACIC,EAA8B,EAGlC5X,EAAAiZ,6BAAA,CAAoCvB,CACpC1X,EAAAkZ,6BAAA,CAAoCC,QAAQ,EAAG,CAAExB,CAAA,EAAF,CA6B/C3X,EAAAoZ,gCAAA,CAAuCC,QAAQ,CAACC,CAAD,CAAW,CAIxD7e,CAAA,CAAQ0d,CAAR,CAAiB,QAAQ,CAACC,CAAD,CAAQ,CAAEA,CAAA,EAAF,CAAjC,CAEgC,EAAhC,GAAIT,CAAJ,CACE2B,CAAA,EADF,CAGE1B,CAAA1c,KAAA,CAAiCoe,CAAjC,CATsD,CA7CT,KA6D7CnB,EAAU,EA7DmC,CA8D7CE,CAaJrY,EAAAuZ,UAAA,CAAiBC,QAAQ,CAACvZ,CAAD,CAAK,CACxB/C,CAAA,CAAYmb,CAAZ,CAAJ,EAA8BN,CAAA,CAAY,GAAZ,CAAiBE,CAAjB,CAC9BE,EAAAjd,KAAA,CAAa+E,CAAb,CACA,OAAOA,EAHqB,CA3EmB,KAoG7CuY,EAAiB/a,CAAAgc,KApG4B,CAqG7CC,EAAc3f,CAAAkE,KAAA,CAAc,MAAd,CArG+B,CAsG7Csa,EAAc,IAqBlBvY,EAAAyY,IAAA,CAAWkB,QAAQ,CAAClB,CAAD,CAAM3W,CAAN,CAAe,CAE5BrE,CAAJ,GAAiB3D,CAAA2D,SAAjB,GAAkCA,CAAlC,CAA6C3D,CAAA2D,SAA7C,CACIob,EAAJ,GAAgB/e,CAAA+e,QAAhB,GAAgCA,CAAhC,CAA0C/e,CAAA+e,QAA1C,CAGA,IAAIJ,CAAJ,CACE,IAAID,CAAJ,EAAsBC,CAAtB,CAiBA,MAhBAD,EAgBOxY,CAhBUyY,CAgBVzY,CAfHyX,CAAAoB,QAAJ,CACM/W,CAAJ,CAAa+W,CAAAe,aAAA,CAAqB,IAArB,CAA2B,EAA3B,CAA+BnB,CAA/B,CAAb,EAEEI,CAAAgB,UAAA,CAAkB,IAAlB,CAAwB,EAAxB;AAA4BpB,CAA5B,CAEA,CAAAiB,CAAA1b,KAAA,CAAiB,MAAjB,CAAyB0b,CAAA1b,KAAA,CAAiB,MAAjB,CAAzB,CAJF,CADF,EAQEua,CACA,CADcE,CACd,CAAI3W,CAAJ,CACErE,CAAAqE,QAAA,CAAiB2W,CAAjB,CADF,CAGEhb,CAAAgc,KAHF,CAGkBhB,CAZpB,CAeOzY,CAAAA,CAjBP,CADF,IAwBE,OAAOuY,EAAP,EAAsB9a,CAAAgc,KAAA3X,QAAA,CAAsB,MAAtB,CAA6B,GAA7B,CA9BQ,CA3He,KA6J7C4W,GAAqB,EA7JwB,CA8J7CoB,EAAgB,CAAA,CAiCpB9Z,EAAA+Z,YAAA,CAAmBC,QAAQ,CAACV,CAAD,CAAW,CAEpC,GAAI,CAACQ,CAAL,CAAoB,CAMlB,GAAIrC,CAAAoB,QAAJ,CAAsBxX,CAAA,CAAOvH,CAAP,CAAAmgB,GAAA,CAAkB,UAAlB,CAA8B3B,CAA9B,CAEtB,IAAIb,CAAAyC,WAAJ,CAAyB7Y,CAAA,CAAOvH,CAAP,CAAAmgB,GAAA,CAAkB,YAAlB,CAAgC3B,CAAhC,CAAzB,KAEKtY,EAAAuZ,UAAA,CAAejB,CAAf,CAELwB,EAAA,CAAgB,CAAA,CAZE,CAepBpB,EAAAxd,KAAA,CAAwBoe,CAAxB,CACA,OAAOA,EAlB6B,CAkCtCtZ,EAAAma,SAAA,CAAgBC,QAAQ,EAAG,CACzB,IAAIX,EAAOC,CAAA1b,KAAA,CAAiB,MAAjB,CACX,OAAOyb,EAAA,CAAOA,CAAA3X,QAAA,CAAa,wBAAb,CAAuC,EAAvC,CAAP,CAAoD,EAFlC,CAQ3B,KAAIuY,EAAc,EAAlB,CACIC,GAAmB,EADvB,CAEIC,EAAava,CAAAma,SAAA,EAsBjBna,EAAAwa,QAAA,CAAeC,QAAQ,CAACtX,CAAD,CAAO3H,CAAP,CAAc,CAAA,IAE/Bkf,CAF+B,CAEJC,CAFI,CAEItf,CAFJ,CAEOK,CAE1C,IAAIyH,CAAJ,CACM3H,CAAJ,GAAcxB,CAAd,CACE4e,CAAA+B,OADF,CACuBC,MAAA,CAAOzX,CAAP,CADvB,CACsC,SADtC,CACkDoX,CADlD,CAE0B,wCAF1B;AAIMhgB,CAAA,CAASiB,CAAT,CAJN,GAKIkf,CAOA,CAPgBrgB,CAAAue,CAAA+B,OAAAtgB,CAAqBugB,MAAA,CAAOzX,CAAP,CAArB9I,CAAoC,GAApCA,CAA0CugB,MAAA,CAAOpf,CAAP,CAA1CnB,CACM,QADNA,CACiBkgB,CADjBlgB,QAOhB,CANsD,CAMtD,CAAmB,IAAnB,CAAIqgB,CAAJ,EACElD,CAAAqD,KAAA,CAAU,UAAV,CAAsB1X,CAAtB,CACE,6DADF,CAEEuX,CAFF,CAEiB,iBAFjB,CAbN,CADF,KAoBO,CACL,GAAI9B,CAAA+B,OAAJ,GAA2BL,EAA3B,CAKE,IAJAA,EAIK,CAJc1B,CAAA+B,OAId,CAHLG,CAGK,CAHSR,EAAAlY,MAAA,CAAuB,IAAvB,CAGT,CAFLiY,CAEK,CAFS,EAET,CAAAhf,CAAA,CAAI,CAAT,CAAYA,CAAZ,CAAgByf,CAAAzgB,OAAhB,CAAoCgB,CAAA,EAApC,CACEsf,CAEA,CAFSG,CAAA,CAAYzf,CAAZ,CAET,CADAK,CACA,CADQif,CAAAtc,QAAA,CAAe,GAAf,CACR,CAAY,CAAZ,CAAI3C,CAAJ,GACEyH,CAIA,CAJO4X,QAAA,CAASJ,CAAAK,UAAA,CAAiB,CAAjB,CAAoBtf,CAApB,CAAT,CAIP,CAAI2e,CAAA,CAAYlX,CAAZ,CAAJ,GAA0BnJ,CAA1B,GACEqgB,CAAA,CAAYlX,CAAZ,CADF,CACsB4X,QAAA,CAASJ,CAAAK,UAAA,CAAiBtf,CAAjB,CAAyB,CAAzB,CAAT,CADtB,CALF,CAWJ,OAAO2e,EApBF,CAxB4B,CA+DrCra,EAAAib,MAAA,CAAaC,QAAQ,CAACjb,CAAD,CAAKkb,CAAL,CAAY,CAC/B,IAAIC,CACJzD,EAAA,EACAyD,EAAA,CAAYnD,CAAA,CAAW,QAAQ,EAAG,CAChC,OAAOc,CAAA,CAAgBqC,CAAhB,CACP1D,EAAA,CAA2BzX,CAA3B,CAFgC,CAAtB,CAGTkb,CAHS,EAGA,CAHA,CAIZpC,EAAA,CAAgBqC,CAAhB,CAAA,CAA6B,CAAA,CAC7B,OAAOA,EARwB,CAsBjCpb,EAAAib,MAAAI,OAAA,CAAoBC,QAAQ,CAACC,CAAD,CAAU,CACpC,MAAIxC,EAAA,CAAgBwC,CAAhB,CAAJ,EACE,OAAOxC,CAAA,CAAgBwC,CAAhB,CAGA;AAFPzC,CAAA,CAAayC,CAAb,CAEO,CADP7D,CAAA,CAA2B5a,CAA3B,CACO,CAAA,CAAA,CAJT,EAMO,CAAA,CAP6B,CAtVW,CAkWnDqN,QAASA,GAAgB,EAAE,CACzB,IAAA0J,KAAA,CAAY,CAAC,SAAD,CAAY,MAAZ,CAAoB,UAApB,CAAgC,WAAhC,CACR,QAAQ,CAAE0C,CAAF,CAAaiB,CAAb,CAAqBC,CAArB,CAAiC+D,CAAjC,CAA2C,CACjD,MAAO,KAAIjE,EAAJ,CAAYhB,CAAZ,CAAqBiF,CAArB,CAAgChE,CAAhC,CAAsCC,CAAtC,CAD0C,CAD3C,CADa,CAsF3BrN,QAASA,GAAqB,EAAG,CAE/B,IAAAyJ,KAAA,CAAY4H,QAAQ,EAAG,CAGrBC,QAASA,EAAY,CAACC,CAAD,CAAUC,CAAV,CAAmB,CAwMtCC,QAASA,EAAO,CAACC,CAAD,CAAQ,CAClBA,CAAJ,EAAaC,CAAb,GACOC,CAAL,CAEWA,CAFX,EAEuBF,CAFvB,GAGEE,CAHF,CAGaF,CAAAG,EAHb,EACED,CADF,CACaF,CAQb,CAHAI,CAAA,CAAKJ,CAAAG,EAAL,CAAcH,CAAAK,EAAd,CAGA,CAFAD,CAAA,CAAKJ,CAAL,CAAYC,CAAZ,CAEA,CADAA,CACA,CADWD,CACX,CAAAC,CAAAE,EAAA,CAAa,IAVf,CADsB,CAmBxBC,QAASA,EAAI,CAACE,CAAD,CAAYC,CAAZ,CAAuB,CAC9BD,CAAJ,EAAiBC,CAAjB,GACMD,CACJ,GADeA,CAAAD,EACf,CAD6BE,CAC7B,EAAIA,CAAJ,GAAeA,CAAAJ,EAAf,CAA6BG,CAA7B,CAFF,CADkC,CA1NpC,GAAIT,CAAJ,GAAeW,EAAf,CACE,KAAMriB,EAAA,CAAO,eAAP,CAAA,CAAwB,KAAxB,CAAkE0hB,CAAlE,CAAN,CAFoC,IAKlCY,EAAO,CAL2B,CAMlCC,EAAQngB,CAAA,CAAO,EAAP,CAAWuf,CAAX,CAAoB,IAAKD,CAAL,CAApB,CAN0B,CAOlCvX,EAAO,EAP2B,CAQlCqY,EAAYb,CAAZa,EAAuBb,CAAAa,SAAvBA,EAA4CC,MAAAC,UARV,CASlCC,EAAU,EATwB,CAUlCb,EAAW,IAVuB,CAWlCC,EAAW,IAyCf,OAAOM,EAAA,CAAOX,CAAP,CAAP,CAAyB,KAoBlBhJ,QAAQ,CAAC/X,CAAD,CAAMY,CAAN,CAAa,CACxB,GAAIihB,CAAJ,CAAeC,MAAAC,UAAf,CAAiC,CAC/B,IAAIE,EAAWD,CAAA,CAAQhiB,CAAR,CAAXiiB,GAA4BD,CAAA,CAAQhiB,CAAR,CAA5BiiB,CAA2C,KAAMjiB,CAAN,CAA3CiiB,CAEJhB;CAAA,CAAQgB,CAAR,CAH+B,CAMjC,GAAI,CAAA3f,CAAA,CAAY1B,CAAZ,CAAJ,CAQA,MAPMZ,EAOCY,GAPM4I,EAON5I,EAPa+gB,CAAA,EAOb/gB,CANP4I,CAAA,CAAKxJ,CAAL,CAMOY,CANKA,CAMLA,CAJH+gB,CAIG/gB,CAJIihB,CAIJjhB,EAHL,IAAAshB,OAAA,CAAYd,CAAAphB,IAAZ,CAGKY,CAAAA,CAfiB,CApBH,KAiDlB4Y,QAAQ,CAACxZ,CAAD,CAAM,CACjB,GAAI6hB,CAAJ,CAAeC,MAAAC,UAAf,CAAiC,CAC/B,IAAIE,EAAWD,CAAA,CAAQhiB,CAAR,CAEf,IAAI,CAACiiB,CAAL,CAAe,MAEfhB,EAAA,CAAQgB,CAAR,CAL+B,CAQjC,MAAOzY,EAAA,CAAKxJ,CAAL,CATU,CAjDI,QAwEfkiB,QAAQ,CAACliB,CAAD,CAAM,CACpB,GAAI6hB,CAAJ,CAAeC,MAAAC,UAAf,CAAiC,CAC/B,IAAIE,EAAWD,CAAA,CAAQhiB,CAAR,CAEf,IAAI,CAACiiB,CAAL,CAAe,MAEXA,EAAJ,EAAgBd,CAAhB,GAA0BA,CAA1B,CAAqCc,CAAAV,EAArC,CACIU,EAAJ,EAAgBb,CAAhB,GAA0BA,CAA1B,CAAqCa,CAAAZ,EAArC,CACAC,EAAA,CAAKW,CAAAZ,EAAL,CAAgBY,CAAAV,EAAhB,CAEA,QAAOS,CAAA,CAAQhiB,CAAR,CATwB,CAYjC,OAAOwJ,CAAA,CAAKxJ,CAAL,CACP2hB,EAAA,EAdoB,CAxEC,WAkGZQ,QAAQ,EAAG,CACpB3Y,CAAA,CAAO,EACPmY,EAAA,CAAO,CACPK,EAAA,CAAU,EACVb,EAAA,CAAWC,CAAX,CAAsB,IAJF,CAlGC,SAmHdgB,QAAQ,EAAG,CAGlBJ,CAAA,CADAJ,CACA,CAFApY,CAEA,CAFO,IAGP,QAAOkY,CAAA,CAAOX,CAAP,CAJW,CAnHG,MA2IjBsB,QAAQ,EAAG,CACf,MAAO5gB,EAAA,CAAO,EAAP,CAAWmgB,CAAX,CAAkB,MAAOD,CAAP,CAAlB,CADQ,CA3IM,CApDa,CAFxC,IAAID,EAAS,EA+ObZ,EAAAuB,KAAA,CAAoBC,QAAQ,EAAG,CAC7B,IAAID,EAAO,EACXxiB,EAAA,CAAQ6hB,CAAR,CAAgB,QAAQ,CAAC3H,CAAD,CAAQgH,CAAR,CAAiB,CACvCsB,CAAA,CAAKtB,CAAL,CAAA,CAAgBhH,CAAAsI,KAAA,EADuB,CAAzC,CAGA,OAAOA,EALsB,CAmB/BvB,EAAAtH,IAAA,CAAmB+I,QAAQ,CAACxB,CAAD,CAAU,CACnC,MAAOW,EAAA,CAAOX,CAAP,CAD4B,CAKrC;MAAOD,EAxQc,CAFQ,CAwTjCrQ,QAASA,GAAsB,EAAG,CAChC,IAAAwI,KAAA,CAAY,CAAC,eAAD,CAAkB,QAAQ,CAACuJ,CAAD,CAAgB,CACpD,MAAOA,EAAA,CAAc,WAAd,CAD6C,CAA1C,CADoB,CAmgBlC3V,QAASA,GAAgB,CAAC5D,CAAD,CAAWwZ,CAAX,CAAkC,CAAA,IACrDC,EAAgB,EADqC,CAErDC,EAAS,WAF4C,CAGrDC,EAA2B,wCAH0B,CAIrDC,EAAyB,gCAJ4B,CASrDC,EAA4B,yBAiB/B,KAAAhW,UAAA,CAAiBiW,QAASC,EAAiB,CAACza,CAAD,CAAO0a,CAAP,CAAyB,CACnEtY,EAAA,CAAwBpC,CAAxB,CAA8B,WAA9B,CACI5I,EAAA,CAAS4I,CAAT,CAAJ,EACE8B,EAAA,CAAU4Y,CAAV,CAA4B,kBAA5B,CA2BA,CA1BKP,CAAAxiB,eAAA,CAA6BqI,CAA7B,CA0BL,GAzBEma,CAAA,CAAcna,CAAd,CACA,CADsB,EACtB,CAAAU,CAAAwC,QAAA,CAAiBlD,CAAjB,CAAwBoa,CAAxB,CAAgC,CAAC,WAAD,CAAc,mBAAd,CAC9B,QAAQ,CAAC9H,CAAD,CAAYqI,CAAZ,CAA+B,CACrC,IAAIC,EAAa,EACjBtjB,EAAA,CAAQ6iB,CAAA,CAAcna,CAAd,CAAR,CAA6B,QAAQ,CAAC0a,CAAD,CAAmBniB,CAAnB,CAA0B,CAC7D,GAAI,CACF,IAAIgM,EAAY+N,CAAA1R,OAAA,CAAiB8Z,CAAjB,CACZhjB,EAAA,CAAW6M,CAAX,CAAJ,CACEA,CADF,CACc,SAAWzK,EAAA,CAAQyK,CAAR,CAAX,CADd,CAEYzD,CAAAyD,CAAAzD,QAFZ,EAEiCyD,CAAAwU,KAFjC,GAGExU,CAAAzD,QAHF;AAGsBhH,EAAA,CAAQyK,CAAAwU,KAAR,CAHtB,CAKAxU,EAAAsW,SAAA,CAAqBtW,CAAAsW,SAArB,EAA2C,CAC3CtW,EAAAhM,MAAA,CAAkBA,CAClBgM,EAAAvE,KAAA,CAAiBuE,CAAAvE,KAAjB,EAAmCA,CACnCuE,EAAAuW,QAAA,CAAoBvW,CAAAuW,QAApB,EAA0CvW,CAAAwW,WAA1C,EAAkExW,CAAAvE,KAClEuE,EAAAyW,SAAA,CAAqBzW,CAAAyW,SAArB,EAA2C,GAC3CJ,EAAA7iB,KAAA,CAAgBwM,CAAhB,CAZE,CAaF,MAAOlG,CAAP,CAAU,CACVsc,CAAA,CAAkBtc,CAAlB,CADU,CAdiD,CAA/D,CAkBA,OAAOuc,EApB8B,CADT,CAAhC,CAwBF,EAAAT,CAAA,CAAcna,CAAd,CAAAjI,KAAA,CAAyB2iB,CAAzB,CA5BF,EA8BEpjB,CAAA,CAAQ0I,CAAR,CAAc7H,EAAA,CAAcsiB,CAAd,CAAd,CAEF,OAAO,KAlC4D,CA0DrE,KAAAQ,2BAAA,CAAkCC,QAAQ,CAACC,CAAD,CAAS,CACjD,MAAInhB,EAAA,CAAUmhB,CAAV,CAAJ,EACEjB,CAAAe,2BAAA,CAAiDE,CAAjD,CACO,CAAA,IAFT,EAISjB,CAAAe,2BAAA,EALwC,CA8BnD,KAAAG,4BAAA,CAAmCC,QAAQ,CAACF,CAAD,CAAS,CAClD,MAAInhB,EAAA,CAAUmhB,CAAV,CAAJ,EACEjB,CAAAkB,4BAAA,CAAkDD,CAAlD,CACO,CAAA,IAFT,EAISjB,CAAAkB,4BAAA,EALyC,CASpD,KAAA1K,KAAA,CAAY,CACF,WADE,CACW,cADX;AAC2B,mBAD3B,CACgD,OADhD,CACyD,gBADzD,CAC2E,QAD3E,CAEF,aAFE,CAEa,YAFb,CAE2B,WAF3B,CAEwC,MAFxC,CAEgD,UAFhD,CAE4D,eAF5D,CAGV,QAAQ,CAAC4B,CAAD,CAAcgJ,CAAd,CAA8BX,CAA9B,CAAmDY,CAAnD,CAA4DC,CAA5D,CAA8EC,CAA9E,CACCC,CADD,CACgBpI,CADhB,CAC8B+E,CAD9B,CAC2CsD,CAD3C,CACmDC,CADnD,CAC+DC,CAD/D,CAC8E,CAqLtF/a,QAASA,EAAO,CAACgb,CAAD,CAAgBC,CAAhB,CAA8BC,CAA9B,CAA2CC,CAA3C,CACIC,CADJ,CAC4B,CACpCJ,CAAN,WAA+B5d,EAA/B,GAGE4d,CAHF,CAGkB5d,CAAA,CAAO4d,CAAP,CAHlB,CAOAxkB,EAAA,CAAQwkB,CAAR,CAAuB,QAAQ,CAACphB,CAAD,CAAOnC,CAAP,CAAa,CACrB,CAArB,EAAImC,CAAAvD,SAAJ,EAA0CuD,CAAAyhB,UAAAzd,MAAA,CAAqB,KAArB,CAA1C,GACEod,CAAA,CAAcvjB,CAAd,CADF,CACgC2F,CAAA,CAAOxD,CAAP,CAAAkQ,KAAA,CAAkB,eAAlB,CAAAnR,OAAA,EAAA,CAA4C,CAA5C,CADhC,CAD0C,CAA5C,CAKA,KAAI2iB,EACIC,CAAA,CAAaP,CAAb,CAA4BC,CAA5B,CAA0CD,CAA1C,CACaE,CADb,CAC0BC,CAD1B,CAC2CC,CAD3C,CAERI,GAAA,CAAaR,CAAb,CAA4B,UAA5B,CACA,OAAOS,SAAqB,CAAC1b,CAAD,CAAQ2b,CAAR,CAAwBC,CAAxB,CAA8C,CACxE3a,EAAA,CAAUjB,CAAV,CAAiB,OAAjB,CAGA,KAAI6b,EAAYF,CACA,CAAZG,EAAAxe,MAAAvG,KAAA,CAA2BkkB,CAA3B,CAAY,CACZA,CAEJxkB,EAAA,CAAQmlB,CAAR,CAA+B,QAAQ,CAACtK,CAAD,CAAWnS,CAAX,CAAiB,CACtD0c,CAAAzb,KAAA,CAAe,GAAf,CAAqBjB,CAArB,CAA4B,YAA5B,CAA0CmS,CAA1C,CADsD,CAAxD,CAKQja,EAAAA,CAAI,CAAZ,KAAI,IAAW0V,EAAK8O,CAAAxlB,OAApB,CAAsCgB,CAAtC,CAAwC0V,CAAxC,CAA4C1V,CAAA,EAA5C,CAAiD,CAC/C,IACIf;AADOulB,CAAAhiB,CAAUxC,CAAVwC,CACIvD,SACE,EAAjB,GAAIA,CAAJ,EAAiD,CAAjD,GAAoCA,CAApC,EACEulB,CAAAE,GAAA,CAAa1kB,CAAb,CAAA+I,KAAA,CAAqB,QAArB,CAA+BJ,CAA/B,CAJ6C,CAQ7C2b,CAAJ,EAAoBA,CAAA,CAAeE,CAAf,CAA0B7b,CAA1B,CAChBub,EAAJ,EAAqBA,CAAA,CAAgBvb,CAAhB,CAAuB6b,CAAvB,CAAkCA,CAAlC,CACrB,OAAOA,EAvBiE,CAjBhC,CA4C5CJ,QAASA,GAAY,CAACO,CAAD,CAAWzc,CAAX,CAAsB,CACzC,GAAI,CACFyc,CAAAC,SAAA,CAAkB1c,CAAlB,CADE,CAEF,MAAM/B,CAAN,CAAS,EAH8B,CAwB3Cge,QAASA,EAAY,CAACU,CAAD,CAAWhB,CAAX,CAAyBiB,CAAzB,CAAuChB,CAAvC,CAAoDC,CAApD,CACGC,CADH,CAC2B,CAoC9CE,QAASA,EAAe,CAACvb,CAAD,CAAQkc,CAAR,CAAkBC,CAAlB,CAAgCC,CAAhC,CAAmD,CAAA,IACzDC,CADyD,CAC5CxiB,CAD4C,CACtCyiB,CADsC,CAC/BC,CAD+B,CACAllB,CADA,CACG0V,CADH,CACOkL,CAG5EuE,EAAAA,CAAiBN,CAAA7lB,OAArB,KACIomB,EAAqBC,KAAJ,CAAUF,CAAV,CACrB,KAAKnlB,CAAL,CAAS,CAAT,CAAYA,CAAZ,CAAgBmlB,CAAhB,CAAgCnlB,CAAA,EAAhC,CACEolB,CAAA,CAAeplB,CAAf,CAAA,CAAoB6kB,CAAA,CAAS7kB,CAAT,CAGX4gB,EAAP,CAAA5gB,CAAA,CAAI,CAAR,KAAkB0V,CAAlB,CAAuB4P,CAAAtmB,OAAvB,CAAuCgB,CAAvC,CAA2C0V,CAA3C,CAA+CkL,CAAA,EAA/C,CACEpe,CAKA,CALO4iB,CAAA,CAAexE,CAAf,CAKP,CAJA2E,CAIA,CAJaD,CAAA,CAAQtlB,CAAA,EAAR,CAIb,CAHAglB,CAGA,CAHcM,CAAA,CAAQtlB,CAAA,EAAR,CAGd,CAFAilB,CAEA,CAFQjf,CAAA,CAAOxD,CAAP,CAER,CAAI+iB,CAAJ,EACMA,CAAA5c,MAAJ,EACEuc,CACA,CADavc,CAAA6c,KAAA,EACb,CAAAP,CAAAlc,KAAA,CAAW,QAAX,CAAqBmc,CAArB,CAFF,EAIEA,CAJF,CAIevc,CAGf,CAAA,CADA8c,CACA,CADoBF,CAAAG,WACpB,GAA2BX,CAAAA,CAA3B,EAAgDlB,CAAhD,CACE0B,CAAA,CAAWP,CAAX,CAAwBE,CAAxB,CAAoC1iB,CAApC,CAA0CsiB,CAA1C,CACEa,CAAA,CAAwBhd,CAAxB,CAA+B8c,CAA/B,EAAoD5B,CAApD,CADF,CADF,CAKE0B,CAAA,CAAWP,CAAX,CAAwBE,CAAxB,CAAoC1iB,CAApC,CAA0CsiB,CAA1C,CAAwDC,CAAxD,CAbJ,EAeWC,CAfX,EAgBEA,CAAA,CAAYrc,CAAZ,CAAmBnG,CAAA4Q,WAAnB,CAAoCzU,CAApC,CAA+ComB,CAA/C,CAhCqE,CAhC3E,IAJ8C,IAC1CO,EAAU,EADgC,CAE1CM,CAF0C,CAEnClD,CAFmC,CAEXtP,CAFW,CAEcyS,CAFd,CAIrC7lB,EAAI,CAAb,CAAgBA,CAAhB,CAAoB6kB,CAAA7lB,OAApB,CAAqCgB,CAAA,EAArC,CACE4lB,CAyBA,CAzBQ,IAAIE,EAyBZ,CAtBApD,CAsBA,CAtBaqD,EAAA,CAAkBlB,CAAA,CAAS7kB,CAAT,CAAlB,CAA+B,EAA/B,CAAmC4lB,CAAnC;AAAgD,CAAN,GAAA5lB,CAAA,CAAU8jB,CAAV,CAAwBnlB,CAAlE,CACmBolB,CADnB,CAsBb,EAnBAwB,CAmBA,CAnBc7C,CAAA1jB,OACD,CAAPgnB,EAAA,CAAsBtD,CAAtB,CAAkCmC,CAAA,CAAS7kB,CAAT,CAAlC,CAA+C4lB,CAA/C,CAAsD/B,CAAtD,CAAoEiB,CAApE,CACwB,IADxB,CAC8B,EAD9B,CACkC,EADlC,CACsCd,CADtC,CAAO,CAEP,IAgBN,GAdkBuB,CAAA5c,MAclB,EAbEyb,EAAA,CAAape,CAAA,CAAO6e,CAAA,CAAS7kB,CAAT,CAAP,CAAb,CAAkC,UAAlC,CAaF,CAVAglB,CAUA,CAVeO,CAGD,EAHeA,CAAAU,SAGf,EAFA,EAAE7S,CAAF,CAAeyR,CAAA,CAAS7kB,CAAT,CAAAoT,WAAf,CAEA,EADA,CAACA,CAAApU,OACD,CAAR,IAAQ,CACRmlB,CAAA,CAAa/Q,CAAb,CACGmS,CAAA,CAAaA,CAAAG,WAAb,CAAqC7B,CADxC,CAMN,CAHAyB,CAAAzlB,KAAA,CAAa0lB,CAAb,CAAyBP,CAAzB,CAGA,CAFAa,CAEA,CAFcA,CAEd,EAF6BN,CAE7B,EAF2CP,CAE3C,CAAAhB,CAAA,CAAyB,IAI3B,OAAO6B,EAAA,CAAc3B,CAAd,CAAgC,IAlCO,CA0EhDyB,QAASA,EAAuB,CAAChd,CAAD,CAAQkb,CAAR,CAAsB,CACpD,MAAOkB,SAA0B,CAACmB,CAAD,CAAmBC,CAAnB,CAA4BC,CAA5B,CAAyC,CACxE,IAAIC,EAAe,CAAA,CAEdH,EAAL,GACEA,CAEA,CAFmBvd,CAAA6c,KAAA,EAEnB,CAAAa,CAAA,CADAH,CAAAI,cACA,CADiC,CAAA,CAFnC,CAMIrgB,EAAAA,CAAQ4d,CAAA,CAAaqC,CAAb,CAA+BC,CAA/B,CAAwCC,CAAxC,CACZ,IAAIC,CAAJ,CACEpgB,CAAA2Y,GAAA,CAAS,UAAT,CAAqBla,EAAA,CAAKwhB,CAAL,CAAuBA,CAAA1R,SAAvB,CAArB,CAEF,OAAOvO,EAbiE,CADtB,CA4BtD8f,QAASA,GAAiB,CAACvjB,CAAD,CAAOkgB,CAAP,CAAmBkD,CAAnB,CAA0B9B,CAA1B,CAAuCC,CAAvC,CAAwD,CAAA,IAE5EwC,EAAWX,CAAAY,MAFiE,CAG5EhgB,CAGJ,QALehE,CAAAvD,SAKf,EACE,KAAK,CAAL,CAEEwnB,CAAA,CAAa/D,CAAb,CACIgE,EAAA,CAAmBC,EAAA,CAAUnkB,CAAV,CAAAmH,YAAA,EAAnB,CADJ,CACuD,GADvD,CAC4Dma,CAD5D,CACyEC,CADzE,CAFF,KAMWphB,CANX,CAMiBmF,CANjB,CAMuB8e,CAA0BC,EAAAA,CAASrkB,CAAA2F,WAAxD,KANF,IAOW+K,EAAI,CAPf,CAOkBC;AAAK0T,CAAL1T,EAAe0T,CAAA7nB,OAD/B,CAC8CkU,CAD9C,CACkDC,CADlD,CACsDD,CAAA,EADtD,CAC2D,CACzD,IAAI4T,EAAgB,CAAA,CAApB,CACIC,EAAc,CAAA,CAElBpkB,EAAA,CAAOkkB,CAAA,CAAO3T,CAAP,CACP,IAAI,CAAC+D,CAAL,EAAqB,CAArB,EAAaA,CAAb,EAA0BtU,CAAAqkB,UAA1B,CAA0C,CACxClf,CAAA,CAAOnF,CAAAmF,KAEPmf,EAAA,CAAaP,EAAA,CAAmB5e,CAAnB,CACTof,EAAAje,KAAA,CAAqBge,CAArB,CAAJ,GACEnf,CADF,CACSwB,EAAA,CAAW2d,CAAAE,OAAA,CAAkB,CAAlB,CAAX,CAAiC,GAAjC,CADT,CAIA,KAAIC,EAAiBH,CAAAxgB,QAAA,CAAmB,cAAnB,CAAmC,EAAnC,CACjBwgB,EAAJ,GAAmBG,CAAnB,CAAoC,OAApC,GACEN,CAEA,CAFgBhf,CAEhB,CADAif,CACA,CADcjf,CAAAqf,OAAA,CAAY,CAAZ,CAAerf,CAAA9I,OAAf,CAA6B,CAA7B,CACd,CADgD,KAChD,CAAA8I,CAAA,CAAOA,CAAAqf,OAAA,CAAY,CAAZ,CAAerf,CAAA9I,OAAf,CAA6B,CAA7B,CAHT,CAMA4nB,EAAA,CAAQF,EAAA,CAAmB5e,CAAA6B,YAAA,EAAnB,CACR4c,EAAA,CAASK,CAAT,CAAA,CAAkB9e,CAClB8d,EAAA,CAAMgB,CAAN,CAAA,CAAezmB,CAAf,CAAuB4R,EAAA,CAAKpP,CAAAxC,MAAL,CACnB2V,GAAA,CAAmBtT,CAAnB,CAAyBokB,CAAzB,CAAJ,GACEhB,CAAA,CAAMgB,CAAN,CADF,CACiB,CAAA,CADjB,CAGAS,EAAA,CAA4B7kB,CAA5B,CAAkCkgB,CAAlC,CAA8CviB,CAA9C,CAAqDymB,CAArD,CACAH,EAAA,CAAa/D,CAAb,CAAyBkE,CAAzB,CAAgC,GAAhC,CAAqC9C,CAArC,CAAkDC,CAAlD,CAAmE+C,CAAnE,CACcC,CADd,CAtBwC,CALe,CAiC3D7e,CAAA,CAAY1F,CAAA0F,UACZ,IAAIhJ,CAAA,CAASgJ,CAAT,CAAJ,EAAyC,EAAzC,GAA2BA,CAA3B,CACE,IAAA,CAAO1B,CAAP,CAAe4b,CAAAna,KAAA,CAA4BC,CAA5B,CAAf,CAAA,CACE0e,CAIA,CAJQF,EAAA,CAAmBlgB,CAAA,CAAM,CAAN,CAAnB,CAIR,CAHIigB,CAAA,CAAa/D,CAAb,CAAyBkE,CAAzB,CAAgC,GAAhC,CAAqC9C,CAArC,CAAkDC,CAAlD,CAGJ,GAFE6B,CAAA,CAAMgB,CAAN,CAEF,CAFiB7U,EAAA,CAAKvL,CAAA,CAAM,CAAN,CAAL,CAEjB,EAAA0B,CAAA,CAAYA,CAAAif,OAAA,CAAiB3gB,CAAAnG,MAAjB,CAA+BmG,CAAA,CAAM,CAAN,CAAAxH,OAA/B,CAGhB,MACF,MAAK,CAAL,CACEsoB,CAAA,CAA4B5E,CAA5B,CAAwClgB,CAAAyhB,UAAxC,CACA,MACF,MAAK,CAAL,CACE,GAAI,CAEF,GADAzd,CACA;AADQ2b,CAAAla,KAAA,CAA8BzF,CAAAyhB,UAA9B,CACR,CACE2C,CACA,CADQF,EAAA,CAAmBlgB,CAAA,CAAM,CAAN,CAAnB,CACR,CAAIigB,CAAA,CAAa/D,CAAb,CAAyBkE,CAAzB,CAAgC,GAAhC,CAAqC9C,CAArC,CAAkDC,CAAlD,CAAJ,GACE6B,CAAA,CAAMgB,CAAN,CADF,CACiB7U,EAAA,CAAKvL,CAAA,CAAM,CAAN,CAAL,CADjB,CAJA,CAQF,MAAOL,CAAP,CAAU,EAhEhB,CAwEAuc,CAAA5iB,KAAA,CAAgBynB,CAAhB,CACA,OAAO7E,EA/EyE,CA0FlF8E,QAASA,EAAS,CAAChlB,CAAD,CAAOilB,CAAP,CAAkBC,CAAlB,CAA2B,CAC3C,IAAIjd,EAAQ,EAAZ,CACIkd,EAAQ,CACZ,IAAIF,CAAJ,EAAiBjlB,CAAAolB,aAAjB,EAAsCplB,CAAAolB,aAAA,CAAkBH,CAAlB,CAAtC,EAEE,EAAG,CACD,GAAI,CAACjlB,CAAL,CACE,KAAMqlB,GAAA,CAAe,SAAf,CAEIJ,CAFJ,CAEeC,CAFf,CAAN,CAImB,CAArB,EAAIllB,CAAAvD,SAAJ,GACMuD,CAAAolB,aAAA,CAAkBH,CAAlB,CACJ,EADkCE,CAAA,EAClC,CAAInlB,CAAAolB,aAAA,CAAkBF,CAAlB,CAAJ,EAAgCC,CAAA,EAFlC,CAIAld,EAAA5K,KAAA,CAAW2C,CAAX,CACAA,EAAA,CAAOA,CAAAoI,YAXN,CAAH,MAYiB,CAZjB,CAYS+c,CAZT,CAFF,KAgBEld,EAAA5K,KAAA,CAAW2C,CAAX,CAGF,OAAOwD,EAAA,CAAOyE,CAAP,CAtBoC,CAiC7Cqd,QAASA,EAA0B,CAACC,CAAD,CAASN,CAAT,CAAoBC,CAApB,CAA6B,CAC9D,MAAO,SAAQ,CAAC/e,CAAD,CAAQ5C,CAAR,CAAiB6f,CAAjB,CAAwBQ,CAAxB,CAAqCvC,CAArC,CAAmD,CAChE9d,CAAA,CAAUyhB,CAAA,CAAUzhB,CAAA,CAAQ,CAAR,CAAV,CAAsB0hB,CAAtB,CAAiCC,CAAjC,CACV,OAAOK,EAAA,CAAOpf,CAAP,CAAc5C,CAAd,CAAuB6f,CAAvB,CAA8BQ,CAA9B,CAA2CvC,CAA3C,CAFyD,CADJ,CA8BhEmC,QAASA,GAAqB,CAACtD,CAAD,CAAasF,CAAb,CAA0BC,CAA1B,CAAyCpE,CAAzC,CACCqE,CADD,CACeC,CADf,CACyCC,CADzC,CACqDC,CADrD,CAECrE,CAFD,CAEyB,CAiMrDsE,QAASA,EAAU,CAACC,CAAD,CAAMC,CAAN,CAAYf,CAAZ,CAAuBC,CAAvB,CAAgC,CACjD,GAAIa,CAAJ,CAAS,CACHd,CAAJ,GAAec,CAAf,CAAqBT,CAAA,CAA2BS,CAA3B,CAAgCd,CAAhC,CAA2CC,CAA3C,CAArB,CACAa,EAAA3F,QAAA,CAAcvW,CAAAuW,QACd,IAAI6F,CAAJ;AAAiCpc,CAAjC,EAA8CA,CAAAqc,eAA9C,CACEH,CAAA,CAAMI,EAAA,CAAmBJ,CAAnB,CAAwB,cAAe,CAAA,CAAf,CAAxB,CAERH,EAAAvoB,KAAA,CAAgB0oB,CAAhB,CANO,CAQT,GAAIC,CAAJ,CAAU,CACJf,CAAJ,GAAee,CAAf,CAAsBV,CAAA,CAA2BU,CAA3B,CAAiCf,CAAjC,CAA4CC,CAA5C,CAAtB,CACAc,EAAA5F,QAAA,CAAevW,CAAAuW,QACf,IAAI6F,CAAJ,GAAiCpc,CAAjC,EAA8CA,CAAAqc,eAA9C,CACEF,CAAA,CAAOG,EAAA,CAAmBH,CAAnB,CAAyB,cAAe,CAAA,CAAf,CAAzB,CAETH,EAAAxoB,KAAA,CAAiB2oB,CAAjB,CANQ,CATuC,CAoBnDI,QAASA,EAAc,CAAChG,CAAD,CAAU+B,CAAV,CAAoBkE,CAApB,CAAwC,CAAA,IACzD1oB,CADyD,CAClD2oB,EAAkB,MADgC,CACxBC,EAAW,CAAA,CAChD,IAAI7pB,CAAA,CAAS0jB,CAAT,CAAJ,CAAuB,CACrB,IAAA,CAAqC,GAArC,GAAOziB,CAAP,CAAeyiB,CAAA7e,OAAA,CAAe,CAAf,CAAf,GAAqD,GAArD,EAA4C5D,CAA5C,CAAA,CACEyiB,CAIA,CAJUA,CAAAuE,OAAA,CAAe,CAAf,CAIV,CAHa,GAGb,EAHIhnB,CAGJ,GAFE2oB,CAEF,CAFoB,eAEpB,EAAAC,CAAA,CAAWA,CAAX,EAAgC,GAAhC,EAAuB5oB,CAEzBA,EAAA,CAAQ,IAEJ0oB,EAAJ,EAA8C,MAA9C,GAA0BC,CAA1B,GACE3oB,CADF,CACU0oB,CAAA,CAAmBjG,CAAnB,CADV,CAGAziB,EAAA,CAAQA,CAAR,EAAiBwkB,CAAA,CAASmE,CAAT,CAAA,CAA0B,GAA1B,CAAgClG,CAAhC,CAA0C,YAA1C,CAEjB,IAAI,CAACziB,CAAL,EAAc,CAAC4oB,CAAf,CACE,KAAMlB,GAAA,CAAe,OAAf,CAEFjF,CAFE,CAEOoG,CAFP,CAAN,CAhBmB,CAAvB,IAqBW7pB,EAAA,CAAQyjB,CAAR,CAAJ,GACLziB,CACA,CADQ,EACR,CAAAf,CAAA,CAAQwjB,CAAR,CAAiB,QAAQ,CAACA,CAAD,CAAU,CACjCziB,CAAAN,KAAA,CAAW+oB,CAAA,CAAehG,CAAf,CAAwB+B,CAAxB,CAAkCkE,CAAlC,CAAX,CADiC,CAAnC,CAFK,CAMP,OAAO1oB,EA7BsD,CAiC/DolB,QAASA,EAAU,CAACP,CAAD,CAAcrc,CAAd,CAAqBsgB,CAArB,CAA+BnE,CAA/B,CAA6CC,CAA7C,CAAgE,CAmKjFmE,QAASA,EAA0B,CAACvgB,CAAD,CAAQwgB,CAAR,CAAuB,CACxD,IAAI5E,CAGmB,EAAvB,CAAIrjB,SAAAlC,OAAJ;CACEmqB,CACA,CADgBxgB,CAChB,CAAAA,CAAA,CAAQhK,CAFV,CAKIyqB,EAAJ,GACE7E,CADF,CAC0BsE,EAD1B,CAIA,OAAO9D,EAAA,CAAkBpc,CAAlB,CAAyBwgB,CAAzB,CAAwC5E,CAAxC,CAbiD,CAnKuB,IAC7EqB,CAD6E,CACtEjB,CADsE,CACzDjP,CADyD,CACrDqS,CADqD,CAC7ClF,CAD6C,CACjCwG,CADiC,CACnBR,GAAqB,EADF,CACMhF,EAGrF+B,EAAA,CADEoC,CAAJ,GAAoBiB,CAApB,CACUhB,CADV,CAGUpkB,EAAA,CAAYokB,CAAZ,CAA2B,IAAInC,EAAJ,CAAe9f,CAAA,CAAOijB,CAAP,CAAf,CAAiChB,CAAAzB,MAAjC,CAA3B,CAEV7B,EAAA,CAAWiB,CAAA0D,UAEX,IAAIb,CAAJ,CAA8B,CAC5B,IAAIc,EAAe,8BACf/E,EAAAA,CAAYxe,CAAA,CAAOijB,CAAP,CAEhBI,EAAA,CAAe1gB,CAAA6c,KAAA,CAAW,CAAA,CAAX,CAEXgE,GAAJ,EAA0BA,EAA1B,GAAgDf,CAAAgB,oBAAhD,CACEjF,CAAAzb,KAAA,CAAe,eAAf,CAAgCsgB,CAAhC,CADF,CAGE7E,CAAAzb,KAAA,CAAe,yBAAf,CAA0CsgB,CAA1C,CAKFjF,GAAA,CAAaI,CAAb,CAAwB,kBAAxB,CAEAplB,EAAA,CAAQqpB,CAAA9f,MAAR,CAAwC,QAAQ,CAAC+gB,CAAD,CAAaC,CAAb,CAAwB,CAAA,IAClEnjB,EAAQkjB,CAAAljB,MAAA,CAAiB+iB,CAAjB,CAAR/iB,EAA0C,EADwB,CAElEojB,EAAWpjB,CAAA,CAAM,CAAN,CAAXojB,EAAuBD,CAF2C,CAGlEZ,EAAwB,GAAxBA,EAAYviB,CAAA,CAAM,CAAN,CAHsD,CAIlEqjB,EAAOrjB,CAAA,CAAM,CAAN,CAJ2D,CAKlEsjB,CALkE,CAMlEC,CANkE,CAMvDC,CANuD,CAM5CC,CAE1BZ,EAAAa,kBAAA,CAA+BP,CAA/B,CAAA,CAA4CE,CAA5C,CAAmDD,CAEnD,QAAQC,CAAR,EAEE,KAAK,GAAL,CACEjE,CAAAuE,SAAA,CAAeP,CAAf,CAAyB,QAAQ,CAACzpB,CAAD,CAAQ,CACvCkpB,CAAA,CAAaM,CAAb,CAAA,CAA0BxpB,CADa,CAAzC,CAGAylB,EAAAwE,YAAA,CAAkBR,CAAlB,CAAAS,QAAA,CAAsC1hB,CAClCid,EAAA,CAAMgE,CAAN,CAAJ,GAGEP,CAAA,CAAaM,CAAb,CAHF,CAG4BvG,CAAA,CAAawC,CAAA,CAAMgE,CAAN,CAAb,CAAA,CAA8BjhB,CAA9B,CAH5B,CAKA;KAEF,MAAK,GAAL,CACE,GAAIogB,CAAJ,EAAgB,CAACnD,CAAA,CAAMgE,CAAN,CAAjB,CACE,KAEFG,EAAA,CAAYxG,CAAA,CAAOqC,CAAA,CAAMgE,CAAN,CAAP,CAEVK,EAAA,CADEF,CAAAO,QAAJ,CACYtmB,EADZ,CAGYimB,QAAQ,CAACM,CAAD,CAAGC,CAAH,CAAM,CAAE,MAAOD,EAAP,GAAaC,CAAf,CAE1BR,EAAA,CAAYD,CAAAU,OAAZ,EAAgC,QAAQ,EAAG,CAEzCX,CAAA,CAAYT,CAAA,CAAaM,CAAb,CAAZ,CAAsCI,CAAA,CAAUphB,CAAV,CACtC,MAAMkf,GAAA,CAAe,WAAf,CAEFjC,CAAA,CAAMgE,CAAN,CAFE,CAEenB,CAAA3gB,KAFf,CAAN,CAHyC,CAO3CgiB,EAAA,CAAYT,CAAA,CAAaM,CAAb,CAAZ,CAAsCI,CAAA,CAAUphB,CAAV,CACtC0gB,EAAA7lB,OAAA,CAAoBknB,QAAyB,EAAG,CAC9C,IAAIC,EAAcZ,CAAA,CAAUphB,CAAV,CACbshB,EAAA,CAAQU,CAAR,CAAqBtB,CAAA,CAAaM,CAAb,CAArB,CAAL,GAEOM,CAAA,CAAQU,CAAR,CAAqBb,CAArB,CAAL,CAKEE,CAAA,CAAUrhB,CAAV,CAAiBgiB,CAAjB,CAA+BtB,CAAA,CAAaM,CAAb,CAA/B,CALF,CAEEN,CAAA,CAAaM,CAAb,CAFF,CAE4BgB,CAJ9B,CAUA,OAAOb,EAAP,CAAmBa,CAZ2B,CAAhD,CAaG,IAbH,CAaSZ,CAAAO,QAbT,CAcA,MAEF,MAAK,GAAL,CACEP,CAAA,CAAYxG,CAAA,CAAOqC,CAAA,CAAMgE,CAAN,CAAP,CACZP,EAAA,CAAaM,CAAb,CAAA,CAA0B,QAAQ,CAAChQ,CAAD,CAAS,CACzC,MAAOoQ,EAAA,CAAUphB,CAAV,CAAiBgR,CAAjB,CADkC,CAG3C,MAEF,SACE,KAAMkO,GAAA,CAAe,MAAf,CAGFY,CAAA3gB,KAHE,CAG6B6hB,CAH7B,CAGwCD,CAHxC,CAAN,CAxDJ,CAVsE,CAAxE,CAhB4B,CAyF9B7F,EAAA,CAAekB,CAAf,EAAoCmE,CAChC0B,EAAJ,EACExrB,CAAA,CAAQwrB,CAAR,CAA8B,QAAQ,CAACve,CAAD,CAAY,CAAA,IAC5CsN,EAAS,QACHtN,CAAA,GAAcoc,CAAd,EAA0Cpc,CAAAqc,eAA1C,CAAqEW,CAArE,CAAoF1gB,CADjF,UAEDgc,CAFC,QAGHiB,CAHG,aAIE/B,EAJF,CADmC,CAM7CgH,CAEHhI,EAAA,CAAaxW,CAAAwW,WACK,IAAlB,EAAIA,CAAJ,GACEA,CADF;AACe+C,CAAA,CAAMvZ,CAAAvE,KAAN,CADf,CAIA+iB,EAAA,CAAqBrH,CAAA,CAAYX,CAAZ,CAAwBlJ,CAAxB,CAMrBkP,GAAA,CAAmBxc,CAAAvE,KAAnB,CAAA,CAAqC+iB,CAChCzB,EAAL,EACEzE,CAAA5b,KAAA,CAAc,GAAd,CAAoBsD,CAAAvE,KAApB,CAAqC,YAArC,CAAmD+iB,CAAnD,CAGExe,EAAAye,aAAJ,GACEnR,CAAAoR,OAAA,CAAc1e,CAAAye,aAAd,CADF,CAC0CD,CAD1C,CAxBgD,CAAlD,CA+BE7qB,EAAA,CAAI,CAAR,KAAW0V,CAAX,CAAgB0S,CAAAppB,OAAhB,CAAmCgB,CAAnC,CAAuC0V,CAAvC,CAA2C1V,CAAA,EAA3C,CACE,GAAI,CACF+nB,CACA,CADSK,CAAA,CAAWpoB,CAAX,CACT,CAAA+nB,CAAA,CAAOA,CAAAsB,aAAA,CAAsBA,CAAtB,CAAqC1gB,CAA5C,CAAmDgc,CAAnD,CAA6DiB,CAA7D,CACImC,CAAAnF,QADJ,EACsBgG,CAAA,CAAeb,CAAAnF,QAAf,CAA+B+B,CAA/B,CAAyCkE,EAAzC,CADtB,CACoFhF,EADpF,CAFE,CAIF,MAAO1d,CAAP,CAAU,CACVsc,CAAA,CAAkBtc,CAAlB,CAAqBL,EAAA,CAAY6e,CAAZ,CAArB,CADU,CAQVqG,CAAAA,CAAeriB,CACf8f,EAAJ,GAAiCA,CAAAwC,SAAjC,EAA+G,IAA/G,GAAsExC,CAAAyC,YAAtE,IACEF,CADF,CACiB3B,CADjB,CAGArE,EAAA,EAAeA,CAAA,CAAYgG,CAAZ,CAA0B/B,CAAA7V,WAA1B,CAA+CzU,CAA/C,CAA0DomB,CAA1D,CAGf,KAAI/kB,CAAJ,CAAQqoB,CAAArpB,OAAR,CAA6B,CAA7B,CAAqC,CAArC,EAAgCgB,CAAhC,CAAwCA,CAAA,EAAxC,CACE,GAAI,CACF+nB,CACA,CADSM,CAAA,CAAYroB,CAAZ,CACT,CAAA+nB,CAAA,CAAOA,CAAAsB,aAAA,CAAsBA,CAAtB,CAAqC1gB,CAA5C,CAAmDgc,CAAnD,CAA6DiB,CAA7D,CACImC,CAAAnF,QADJ,EACsBgG,CAAA,CAAeb,CAAAnF,QAAf,CAA+B+B,CAA/B,CAAyCkE,EAAzC,CADtB,CACoFhF,EADpF,CAFE,CAIF,MAAO1d,CAAP,CAAU,CACVsc,CAAA,CAAkBtc,CAAlB,CAAqBL,EAAA,CAAY6e,CAAZ,CAArB,CADU,CA7JmE,CArPnFX,CAAA,CAAyBA,CAAzB,EAAmD,EAoBnD,KArBqD,IAGjDmH,EAAmB,CAAC9J,MAAAC,UAH6B,CAIjD8J,CAJiD,CAKjDR,EAAuB5G,CAAA4G,qBAL0B,CAMjDnC,EAA2BzE,CAAAyE,yBANsB;AAOjDe,GAAoBxF,CAAAwF,kBAP6B,CAQjD6B,EAA4BrH,CAAAqH,0BARqB,CASjDC,EAAyB,CAAA,CATwB,CAUjDlC,EAAgCpF,CAAAoF,8BAViB,CAWjDmC,EAAetD,CAAAqB,UAAfiC,CAAyCvlB,CAAA,CAAOgiB,CAAP,CAXQ,CAYjD3b,CAZiD,CAajD2c,CAbiD,CAcjDwC,CAdiD,CAgBjD/F,GAAoB5B,CAhB6B,CAiBjDkE,CAjBiD,CAqB7C/nB,EAAI,CArByC,CAqBtC0V,EAAKgN,CAAA1jB,OAApB,CAAuCgB,CAAvC,CAA2C0V,CAA3C,CAA+C1V,CAAA,EAA/C,CAAoD,CAClDqM,CAAA,CAAYqW,CAAA,CAAW1iB,CAAX,CACZ,KAAIynB,GAAYpb,CAAAof,QAAhB,CACI/D,EAAUrb,CAAAqf,MAGVjE,GAAJ,GACE8D,CADF,CACiB/D,CAAA,CAAUQ,CAAV,CAAuBP,EAAvB,CAAkCC,CAAlC,CADjB,CAGA8D,EAAA,CAAY7sB,CAEZ,IAAIwsB,CAAJ,CAAuB9e,CAAAsW,SAAvB,CACE,KAGF,IAAIgJ,CAAJ,CAAqBtf,CAAA1D,MAArB,CACEyiB,CAIA,CAJoBA,CAIpB,EAJyC/e,CAIzC,CAAKA,CAAA6e,YAAL,GACEU,CAAA,CAAkB,oBAAlB,CAAwCnD,CAAxC,CAAkEpc,CAAlE,CACkBkf,CADlB,CAEA,CAAIxpB,CAAA,CAAS4pB,CAAT,CAAJ,GACElD,CADF,CAC6Bpc,CAD7B,CAHF,CASF2c,EAAA,CAAgB3c,CAAAvE,KAEXojB,EAAA7e,CAAA6e,YAAL,EAA8B7e,CAAAwW,WAA9B,GACE8I,CAIA,CAJiBtf,CAAAwW,WAIjB,CAHA+H,CAGA,CAHuBA,CAGvB,EAH+C,EAG/C,CAFAgB,CAAA,CAAkB,GAAlB,CAAwB5C,CAAxB,CAAwC,cAAxC,CACI4B,CAAA,CAAqB5B,CAArB,CADJ,CACyC3c,CADzC,CACoDkf,CADpD,CAEA,CAAAX,CAAA,CAAqB5B,CAArB,CAAA,CAAsC3c,CALxC,CAQA,IAAIsf,CAAJ,CAAqBtf,CAAAqZ,WAArB,CACE4F,CAUA,CAVyB,CAAA,CAUzB,CALKjf,CAAAwf,MAKL,GAJED,CAAA,CAAkB,cAAlB,CAAkCP,CAAlC,CAA6Dhf,CAA7D,CAAwEkf,CAAxE,CACA,CAAAF,CAAA,CAA4Bhf,CAG9B,EAAsB,SAAtB,EAAIsf,CAAJ,EACEvC,CASA,CATgC,CAAA,CAShC,CARA+B,CAQA,CARmB9e,CAAAsW,SAQnB;AAPA6I,CAOA,CAPYhE,CAAA,CAAUQ,CAAV,CAAuBP,EAAvB,CAAkCC,CAAlC,CAOZ,CANA6D,CAMA,CANetD,CAAAqB,UAMf,CALItjB,CAAA,CAAOtH,CAAAotB,cAAA,CAAuB,GAAvB,CAA6B9C,CAA7B,CAA6C,IAA7C,CACuBf,CAAA,CAAce,CAAd,CADvB,CACsD,GADtD,CAAP,CAKJ,CAHAhB,CAGA,CAHcuD,CAAA,CAAa,CAAb,CAGd,CAFAQ,EAAA,CAAY7D,CAAZ,CAA0BliB,CAAA,CA1pK7BlB,EAAApF,KAAA,CA0pK8C8rB,CA1pK9C,CAA+B,CAA/B,CA0pK6B,CAA1B,CAAwDxD,CAAxD,CAEA,CAAAvC,EAAA,CAAoB7c,CAAA,CAAQ4iB,CAAR,CAAmB3H,CAAnB,CAAiCsH,CAAjC,CACQa,CADR,EAC4BA,CAAAlkB,KAD5B,CACmD,2BAQdujB,CARc,CADnD,CAVtB,GAsBEG,CAEA,CAFYxlB,CAAA,CAAOwN,EAAA,CAAYwU,CAAZ,CAAP,CAAAiE,SAAA,EAEZ,CADAV,CAAArlB,MAAA,EACA,CAAAuf,EAAA,CAAoB7c,CAAA,CAAQ4iB,CAAR,CAAmB3H,CAAnB,CAxBtB,CA4BF,IAAIxX,CAAA4e,SAAJ,CAUE,GATAW,CAAA,CAAkB,UAAlB,CAA8BpC,EAA9B,CAAiDnd,CAAjD,CAA4Dkf,CAA5D,CASI9kB,CARJ+iB,EAQI/iB,CARgB4F,CAQhB5F,CANJklB,CAMIllB,CANcjH,CAAA,CAAW6M,CAAA4e,SAAX,CACD,CAAX5e,CAAA4e,SAAA,CAAmBM,CAAnB,CAAiCtD,CAAjC,CAAW,CACX5b,CAAA4e,SAIFxkB,CAFJklB,CAEIllB,CAFaylB,CAAA,CAAoBP,CAApB,CAEbllB,CAAA4F,CAAA5F,QAAJ,CAAuB,CACrBulB,CAAA,CAAmB3f,CAEjBmf,EAAA,CAz8HJnZ,EAAApJ,KAAA,CAw8HuB0iB,CAx8HvB,CAw8HE,CAGc3lB,CAAA,CAAO2lB,CAAP,CAHd,CACc,EAId3D,EAAA,CAAcwD,CAAA,CAAU,CAAV,CAEd,IAAwB,CAAxB,EAAIA,CAAAxsB,OAAJ,EAAsD,CAAtD,GAA6BgpB,CAAA/oB,SAA7B,CACE,KAAM4oB,GAAA,CAAe,OAAf,CAEFmB,CAFE,CAEa,EAFb,CAAN,CAKF+C,EAAA,CAAY7D,CAAZ,CAA0BqD,CAA1B,CAAwCvD,CAAxC,CAEImE,EAAAA,CAAmB,OAAQ,EAAR,CAOnBC,EAAAA,CAAqBrG,EAAA,CAAkBiC,CAAlB,CAA+B,EAA/B,CAAmCmE,CAAnC,CACzB,KAAIE,EAAwB3J,CAAAvf,OAAA,CAAkBnD,CAAlB,CAAsB,CAAtB,CAAyB0iB,CAAA1jB,OAAzB,EAA8CgB,CAA9C,CAAkD,CAAlD,EAExByoB,EAAJ,EACE6D,EAAA,CAAwBF,CAAxB,CAEF1J,EAAA,CAAaA,CAAAzd,OAAA,CAAkBmnB,CAAlB,CAAAnnB,OAAA,CAA6ConB,CAA7C,CACbE,EAAA,CAAwBtE,CAAxB,CAAuCkE,CAAvC,CAEAzW,EAAA,CAAKgN,CAAA1jB,OAjCgB,CAAvB,IAmCEusB,EAAAjlB,KAAA,CAAkBqlB,CAAlB,CAIJ;GAAItf,CAAA6e,YAAJ,CACEU,CAAA,CAAkB,UAAlB,CAA8BpC,EAA9B,CAAiDnd,CAAjD,CAA4Dkf,CAA5D,CAcA,CAbA/B,EAaA,CAboBnd,CAapB,CAXIA,CAAA5F,QAWJ,GAVEulB,CAUF,CAVqB3f,CAUrB,EAPAkZ,CAOA,CAPaiH,CAAA,CAAmB9J,CAAAvf,OAAA,CAAkBnD,CAAlB,CAAqB0iB,CAAA1jB,OAArB,CAAyCgB,CAAzC,CAAnB,CAAgEurB,CAAhE,CACTtD,CADS,CACMC,CADN,CACoBzC,EADpB,CACuC2C,CADvC,CACmDC,CADnD,CACgE,sBACjDuC,CADiD,0BAE7CnC,CAF6C,mBAGpDe,EAHoD,2BAI5C6B,CAJ4C,CADhE,CAOb,CAAA3V,CAAA,CAAKgN,CAAA1jB,OAfP,KAgBO,IAAIqN,CAAAzD,QAAJ,CACL,GAAI,CACFmf,CACA,CADS1b,CAAAzD,QAAA,CAAkB2iB,CAAlB,CAAgCtD,CAAhC,CAA+CxC,EAA/C,CACT,CAAIjmB,CAAA,CAAWuoB,CAAX,CAAJ,CACEO,CAAA,CAAW,IAAX,CAAiBP,CAAjB,CAAyBN,EAAzB,CAAoCC,CAApC,CADF,CAEWK,CAFX,EAGEO,CAAA,CAAWP,CAAAQ,IAAX,CAAuBR,CAAAS,KAAvB,CAAoCf,EAApC,CAA+CC,CAA/C,CALA,CAOF,MAAOvhB,EAAP,CAAU,CACVsc,CAAA,CAAkBtc,EAAlB,CAAqBL,EAAA,CAAYylB,CAAZ,CAArB,CADU,CAKVlf,CAAA4Z,SAAJ,GACEV,CAAAU,SACA,CADsB,CAAA,CACtB,CAAAkF,CAAA,CAAmBsB,IAAAC,IAAA,CAASvB,CAAT,CAA2B9e,CAAAsW,SAA3B,CAFrB,CA5JkD,CAmKpD4C,CAAA5c,MAAA,CAAmByiB,CAAnB,EAAoE,CAAA,CAApE,GAAwCA,CAAAziB,MACxC4c,EAAAG,WAAA,CAAwB4F,CAAxB,EAAkD7F,EAClDzB,EAAAoF,8BAAA,CAAuDA,CAGvD,OAAO7D,EA7L8C,CA2avD+G,QAASA,GAAuB,CAAC5J,CAAD,CAAa,CAE3C,IAF2C,IAElCxP,EAAI,CAF8B,CAE3BC,EAAKuP,CAAA1jB,OAArB,CAAwCkU,CAAxC,CAA4CC,CAA5C,CAAgDD,CAAA,EAAhD,CACEwP,CAAA,CAAWxP,CAAX,CAAA;AAAgB5R,EAAA,CAAQohB,CAAA,CAAWxP,CAAX,CAAR,CAAuB,gBAAiB,CAAA,CAAjB,CAAvB,CAHyB,CAqB7CuT,QAASA,EAAY,CAACkG,CAAD,CAAc7kB,CAAd,CAAoB1F,CAApB,CAA8B0hB,CAA9B,CAA2CC,CAA3C,CAA4D6I,CAA5D,CACCC,CADD,CACc,CACjC,GAAI/kB,CAAJ,GAAaic,CAAb,CAA8B,MAAO,KACjCvd,EAAAA,CAAQ,IACZ,IAAIyb,CAAAxiB,eAAA,CAA6BqI,CAA7B,CAAJ,CAAwC,CAAA,IAC9BuE,CAAWqW,EAAAA,CAAatI,CAAArB,IAAA,CAAcjR,CAAd,CAAqBoa,CAArB,CAAhC,KADsC,IAElCliB,EAAI,CAF8B,CAE3B0V,EAAKgN,CAAA1jB,OADhB,CACmCgB,CADnC,CACqC0V,CADrC,CACyC1V,CAAA,EADzC,CAEE,GAAI,CACFqM,CACA,CADYqW,CAAA,CAAW1iB,CAAX,CACZ,EAAM8jB,CAAN,GAAsBnlB,CAAtB,EAAmCmlB,CAAnC,CAAiDzX,CAAAsW,SAAjD,GAC8C,EAD9C,EACKtW,CAAAyW,SAAA9f,QAAA,CAA2BZ,CAA3B,CADL,GAEMwqB,CAIJ,GAHEvgB,CAGF,CAHc/K,EAAA,CAAQ+K,CAAR,CAAmB,SAAUugB,CAAV,OAAgCC,CAAhC,CAAnB,CAGd,EADAF,CAAA9sB,KAAA,CAAiBwM,CAAjB,CACA,CAAA7F,CAAA,CAAQ6F,CANV,CAFE,CAUF,MAAMlG,CAAN,CAAS,CAAEsc,CAAA,CAAkBtc,CAAlB,CAAF,CAbyB,CAgBxC,MAAOK,EAnB0B,CA+BnC+lB,QAASA,EAAuB,CAACtrB,CAAD,CAAM6C,CAAN,CAAW,CAAA,IACrCgpB,EAAUhpB,CAAA0iB,MAD2B,CAErCuG,EAAU9rB,CAAAulB,MAF2B,CAGrC7B,EAAW1jB,CAAAqoB,UAGflqB,EAAA,CAAQ6B,CAAR,CAAa,QAAQ,CAACd,CAAD,CAAQZ,CAAR,CAAa,CACX,GAArB,EAAIA,CAAAwE,OAAA,CAAW,CAAX,CAAJ,GACMD,CAAA,CAAIvE,CAAJ,CAGJ,GAFEY,CAEF,GAFoB,OAAR,GAAAZ,CAAA,CAAkB,GAAlB,CAAwB,GAEpC,EAF2CuE,CAAA,CAAIvE,CAAJ,CAE3C,EAAA0B,CAAA+rB,KAAA,CAASztB,CAAT,CAAcY,CAAd,CAAqB,CAAA,CAArB,CAA2B2sB,CAAA,CAAQvtB,CAAR,CAA3B,CAJF,CADgC,CAAlC,CAUAH,EAAA,CAAQ0E,CAAR,CAAa,QAAQ,CAAC3D,CAAD,CAAQZ,CAAR,CAAa,CACrB,OAAX,EAAIA,CAAJ,EACE6kB,EAAA,CAAaO,CAAb,CAAuBxkB,CAAvB,CACA,CAAAc,CAAA,CAAI,OAAJ,CAAA,EAAgBA,CAAA,CAAI,OAAJ,CAAA;AAAeA,CAAA,CAAI,OAAJ,CAAf,CAA8B,GAA9B,CAAoC,EAApD,EAA0Dd,CAF5D,EAGkB,OAAX,EAAIZ,CAAJ,EACLolB,CAAAhiB,KAAA,CAAc,OAAd,CAAuBgiB,CAAAhiB,KAAA,CAAc,OAAd,CAAvB,CAAgD,GAAhD,CAAsDxC,CAAtD,CACA,CAAAc,CAAA,MAAA,EAAgBA,CAAA,MAAA,CAAeA,CAAA,MAAf,CAA8B,GAA9B,CAAoC,EAApD,EAA0Dd,CAFrD,EAMqB,GANrB,EAMIZ,CAAAwE,OAAA,CAAW,CAAX,CANJ,EAM6B9C,CAAAxB,eAAA,CAAmBF,CAAnB,CAN7B,GAOL0B,CAAA,CAAI1B,CAAJ,CACA,CADWY,CACX,CAAA4sB,CAAA,CAAQxtB,CAAR,CAAA,CAAeutB,CAAA,CAAQvtB,CAAR,CARV,CAJyB,CAAlC,CAhByC,CAkC3CitB,QAASA,EAAkB,CAAC9J,CAAD,CAAa6I,CAAb,CAA2B0B,CAA3B,CACvBnI,CADuB,CACTW,CADS,CACU2C,CADV,CACsBC,CADtB,CACmCrE,CADnC,CAC2D,CAAA,IAChFkJ,EAAY,EADoE,CAEhFC,CAFgF,CAGhFC,CAHgF,CAIhFC,EAA4B9B,CAAA,CAAa,CAAb,CAJoD,CAKhF+B,EAAqB5K,CAAAlR,MAAA,EAL2D,CAOhF+b,EAAuBvsB,CAAA,CAAO,EAAP,CAAWssB,CAAX,CAA+B,aACvC,IADuC,YACrB,IADqB,SACN,IADM,qBACqBA,CADrB,CAA/B,CAPyD,CAUhFpC,EAAe1rB,CAAA,CAAW8tB,CAAApC,YAAX,CACD,CAARoC,CAAApC,YAAA,CAA+BK,CAA/B,CAA6C0B,CAA7C,CAAQ,CACRK,CAAApC,YAEVK,EAAArlB,MAAA,EAEAmd,EAAAtK,IAAA,CAAU0K,CAAA+J,sBAAA,CAA2BtC,CAA3B,CAAV,CAAmD,OAAQ5H,CAAR,CAAnD,CAAAmK,QAAA,CACU,QAAQ,CAACC,CAAD,CAAU,CAAA,IACpB1F,CADoB,CACuB2F,CAE/CD,EAAA,CAAUxB,CAAA,CAAoBwB,CAApB,CAEV,IAAIJ,CAAA7mB,QAAJ,CAAgC,CAE5B+kB,CAAA,CAp3IJnZ,EAAApJ,KAAA,CAm3IuBykB,CAn3IvB,CAm3IE,CAGc1nB,CAAA,CAAO0nB,CAAP,CAHd,CACc,EAId1F,EAAA,CAAcwD,CAAA,CAAU,CAAV,CAEd,IAAwB,CAAxB,EAAIA,CAAAxsB,OAAJ;AAAsD,CAAtD,GAA6BgpB,CAAA/oB,SAA7B,CACE,KAAM4oB,GAAA,CAAe,OAAf,CAEFyF,CAAAxlB,KAFE,CAEuBojB,CAFvB,CAAN,CAKF0C,CAAA,CAAoB,OAAQ,EAAR,CACpB7B,GAAA,CAAYjH,CAAZ,CAA0ByG,CAA1B,CAAwCvD,CAAxC,CACA,KAAIoE,EAAqBrG,EAAA,CAAkBiC,CAAlB,CAA+B,EAA/B,CAAmC4F,CAAnC,CAErB7rB,EAAA,CAASurB,CAAA3kB,MAAT,CAAJ,EACE2jB,EAAA,CAAwBF,CAAxB,CAEF1J,EAAA,CAAa0J,CAAAnnB,OAAA,CAA0Byd,CAA1B,CACb6J,EAAA,CAAwBU,CAAxB,CAAgCW,CAAhC,CAtB8B,CAAhC,IAwBE5F,EACA,CADcqF,CACd,CAAA9B,CAAAjlB,KAAA,CAAkBonB,CAAlB,CAGFhL,EAAA9hB,QAAA,CAAmB2sB,CAAnB,CAEAJ,EAAA,CAA0BnH,EAAA,CAAsBtD,CAAtB,CAAkCsF,CAAlC,CAA+CiF,CAA/C,CACtBxH,CADsB,CACH8F,CADG,CACW+B,CADX,CAC+BlF,CAD/B,CAC2CC,CAD3C,CAEtBrE,CAFsB,CAG1B5kB,EAAA,CAAQ0lB,CAAR,CAAsB,QAAQ,CAACtiB,CAAD,CAAOxC,CAAP,CAAU,CAClCwC,CAAJ,EAAYwlB,CAAZ,GACElD,CAAA,CAAa9kB,CAAb,CADF,CACoBurB,CAAA,CAAa,CAAb,CADpB,CADsC,CAAxC,CAQA,KAHA6B,CAGA,CAH2BjJ,CAAA,CAAaoH,CAAA,CAAa,CAAb,CAAAnY,WAAb,CAAyCqS,CAAzC,CAG3B,CAAMyH,CAAAluB,OAAN,CAAA,CAAwB,CAClB2J,CAAAA,CAAQukB,CAAA1b,MAAA,EACRqc,EAAAA,CAAyBX,CAAA1b,MAAA,EAFP,KAGlBsc,EAAkBZ,CAAA1b,MAAA,EAHA,CAIlBuT,EAAoBmI,CAAA1b,MAAA,EAJF,CAKlByX,EAAWsC,CAAA,CAAa,CAAb,CAEf,IAAIsC,CAAJ,GAA+BR,CAA/B,CAA0D,CACxD,IAAIU,EAAaF,CAAA3lB,UAEX8b,EAAAoF,8BAAN,EACIkE,CAAA7mB,QADJ,GAGEwiB,CAHF,CAGazV,EAAA,CAAYwU,CAAZ,CAHb,CAMA+D,GAAA,CAAY+B,CAAZ,CAA6B9nB,CAAA,CAAO6nB,CAAP,CAA7B,CAA6D5E,CAA7D,CAGA7E,GAAA,CAAape,CAAA,CAAOijB,CAAP,CAAb,CAA+B8E,CAA/B,CAZwD,CAexDJ,CAAA,CADER,CAAAzH,WAAJ,CAC2BC,CAAA,CAAwBhd,CAAxB,CAA+BwkB,CAAAzH,WAA/B,CAD3B,CAG2BX,CAE3BoI,EAAA,CAAwBC,CAAxB,CAAkDzkB,CAAlD,CAAyDsgB,CAAzD,CAAmEnE,CAAnE,CACE6I,CADF,CA1BsB,CA6BxBT,CAAA,CAAY,IA3EY,CAD5B,CAAAzQ,MAAA,CA8EQ,QAAQ,CAACuR,CAAD,CAAWC,CAAX,CAAiBC,CAAjB,CAA0BxiB,CAA1B,CAAkC,CAC9C,KAAMmc,GAAA,CAAe,QAAf;AAAyDnc,CAAA0R,IAAzD,CAAN,CAD8C,CA9ElD,CAkFA,OAAO+Q,SAA0B,CAACC,CAAD,CAAoBzlB,CAApB,CAA2BnG,CAA3B,CAAiC6rB,CAAjC,CAA8CtJ,CAA9C,CAAiE,CAC5FmI,CAAJ,EACEA,CAAArtB,KAAA,CAAe8I,CAAf,CAGA,CAFAukB,CAAArtB,KAAA,CAAe2C,CAAf,CAEA,CADA0qB,CAAArtB,KAAA,CAAewuB,CAAf,CACA,CAAAnB,CAAArtB,KAAA,CAAeklB,CAAf,CAJF,EAMEoI,CAAA,CAAwBC,CAAxB,CAAkDzkB,CAAlD,CAAyDnG,CAAzD,CAA+D6rB,CAA/D,CAA4EtJ,CAA5E,CAP8F,CAlGd,CAkHtFwC,QAASA,EAAU,CAACgD,CAAD,CAAIC,CAAJ,CAAO,CACxB,IAAI8D,EAAO9D,CAAA7H,SAAP2L,CAAoB/D,CAAA5H,SACxB,OAAa,EAAb,GAAI2L,CAAJ,CAAuBA,CAAvB,CACI/D,CAAAziB,KAAJ,GAAe0iB,CAAA1iB,KAAf,CAA+ByiB,CAAAziB,KAAD,CAAU0iB,CAAA1iB,KAAV,CAAqB,EAArB,CAAyB,CAAvD,CACOyiB,CAAAlqB,MADP,CACiBmqB,CAAAnqB,MAJO,CAQ1BurB,QAASA,EAAiB,CAAC2C,CAAD,CAAOC,CAAP,CAA0BniB,CAA1B,CAAqCtG,CAArC,CAA8C,CACtE,GAAIyoB,CAAJ,CACE,KAAM3G,GAAA,CAAe,UAAf,CACF2G,CAAA1mB,KADE,CACsBuE,CAAAvE,KADtB,CACsCymB,CADtC,CAC4CzoB,EAAA,CAAYC,CAAZ,CAD5C,CAAN,CAFoE,CAQxEuhB,QAASA,EAA2B,CAAC5E,CAAD,CAAa+L,CAAb,CAAmB,CACrD,IAAIC,EAAgBtL,CAAA,CAAaqL,CAAb,CAAmB,CAAA,CAAnB,CAChBC,EAAJ,EACEhM,CAAA7iB,KAAA,CAAgB,UACJ,CADI,SAEL+B,EAAA,CAAQ+sB,QAA8B,CAAChmB,CAAD,CAAQnG,CAAR,CAAc,CAAA,IACvDjB,EAASiB,CAAAjB,OAAA,EAD8C,CAEvDqtB,EAAWrtB,CAAAwH,KAAA,CAAY,UAAZ,CAAX6lB,EAAsC,EAC1CA,EAAA/uB,KAAA,CAAc6uB,CAAd,CACAtK,GAAA,CAAa7iB,CAAAwH,KAAA,CAAY,UAAZ,CAAwB6lB,CAAxB,CAAb,CAAgD,YAAhD,CACAjmB,EAAAnF,OAAA,CAAakrB,CAAb,CAA4BG,QAAiC,CAAC1uB,CAAD,CAAQ,CACnEqC,CAAA,CAAK,CAAL,CAAAyhB,UAAA,CAAoB9jB,CAD+C,CAArE,CAL2D,CAApD,CAFK,CAAhB,CAHmD,CAmBvD2uB,QAASA,EAAiB,CAACtsB,CAAD,CAAOusB,CAAP,CAA2B,CACnD,GAA0B,QAA1B;AAAIA,CAAJ,CACE,MAAOtL,EAAAuL,KAET,KAAIzmB,EAAMoe,EAAA,CAAUnkB,CAAV,CAEV,IAA0B,WAA1B,EAAIusB,CAAJ,EACY,MADZ,EACKxmB,CADL,EAC4C,QAD5C,EACsBwmB,CADtB,EAEY,KAFZ,EAEKxmB,CAFL,GAE4C,KAF5C,EAEsBwmB,CAFtB,EAG4C,OAH5C,EAGsBA,CAHtB,EAIE,MAAOtL,EAAAwL,aAV0C,CAerD5H,QAASA,EAA2B,CAAC7kB,CAAD,CAAOkgB,CAAP,CAAmBviB,CAAnB,CAA0B2H,CAA1B,CAAgC,CAClE,IAAI4mB,EAAgBtL,CAAA,CAAajjB,CAAb,CAAoB,CAAA,CAApB,CAGpB,IAAKuuB,CAAL,CAAA,CAGA,GAAa,UAAb,GAAI5mB,CAAJ,EAA+C,QAA/C,GAA2B6e,EAAA,CAAUnkB,CAAV,CAA3B,CACE,KAAMqlB,GAAA,CAAe,UAAf,CAEF/hB,EAAA,CAAYtD,CAAZ,CAFE,CAAN,CAKFkgB,CAAA7iB,KAAA,CAAgB,UACJ,GADI,SAEL+I,QAAQ,EAAG,CAChB,MAAO,KACAsmB,QAAiC,CAACvmB,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CACvDynB,CAAAA,CAAeznB,CAAAynB,YAAfA,GAAoCznB,CAAAynB,YAApCA,CAAuD,EAAvDA,CAEJ,IAAI/H,CAAApZ,KAAA,CAA+BnB,CAA/B,CAAJ,CACE,KAAM+f,GAAA,CAAe,aAAf,CAAN,CAWF,GAJA6G,CAIA,CAJgBtL,CAAA,CAAazgB,CAAA,CAAKmF,CAAL,CAAb,CAAyB,CAAA,CAAzB,CAA+BgnB,CAAA,CAAkBtsB,CAAlB,CAAwBsF,CAAxB,CAA/B,CAIhB,CAIAnF,CAAA,CAAKmF,CAAL,CAEC,CAFY4mB,CAAA,CAAc/lB,CAAd,CAEZ,CADAwmB,CAAA/E,CAAA,CAAYtiB,CAAZ,CAAAqnB,GAAsB/E,CAAA,CAAYtiB,CAAZ,CAAtBqnB,CAA0C,EAA1CA,UACA,CADyD,CAAA,CACzD,CAAA3rB,CAAAb,CAAAynB,YAAA5mB,EAAoBb,CAAAynB,YAAA,CAAiBtiB,CAAjB,CAAAuiB,QAApB7mB,EAAsDmF,CAAtDnF,QAAA,CACQkrB,CADR,CACuBG,QAAiC,CAACO,CAAD,CAAWC,CAAX,CAAqB,CAO9D,OAAZ;AAAGvnB,CAAH,EAAuBsnB,CAAvB,EAAmCC,CAAnC,CACE1sB,CAAA2sB,aAAA,CAAkBF,CAAlB,CAA4BC,CAA5B,CADF,CAGE1sB,CAAAqqB,KAAA,CAAUllB,CAAV,CAAgBsnB,CAAhB,CAVwE,CAD7E,CArB0D,CADxD,CADS,CAFN,CAAhB,CATA,CAJkE,CAqEpErD,QAASA,GAAW,CAACjH,CAAD,CAAeyK,CAAf,CAAiCC,CAAjC,CAA0C,CAAA,IACxDC,EAAuBF,CAAA,CAAiB,CAAjB,CADiC,CAExDG,EAAcH,CAAAvwB,OAF0C,CAGxDuC,EAASkuB,CAAA9Z,WAH+C,CAIxD3V,CAJwD,CAIrD0V,CAEP,IAAIoP,CAAJ,CACE,IAAI9kB,CAAO,CAAH,CAAG,CAAA0V,CAAA,CAAKoP,CAAA9lB,OAAhB,CAAqCgB,CAArC,CAAyC0V,CAAzC,CAA6C1V,CAAA,EAA7C,CACE,GAAI8kB,CAAA,CAAa9kB,CAAb,CAAJ,EAAuByvB,CAAvB,CAA6C,CAC3C3K,CAAA,CAAa9kB,CAAA,EAAb,CAAA,CAAoBwvB,CACJG,EAAAA,CAAKzc,CAALyc,CAASD,CAATC,CAAuB,CAAvC,KAAK,IACIxc,EAAK2R,CAAA9lB,OADd,CAEKkU,CAFL,CAESC,CAFT,CAEaD,CAAA,EAAA,CAAKyc,CAAA,EAFlB,CAGMA,CAAJ,CAASxc,CAAT,CACE2R,CAAA,CAAa5R,CAAb,CADF,CACoB4R,CAAA,CAAa6K,CAAb,CADpB,CAGE,OAAO7K,CAAA,CAAa5R,CAAb,CAGX4R,EAAA9lB,OAAA,EAAuB0wB,CAAvB,CAAqC,CACrC,MAZ2C,CAiB7CnuB,CAAJ,EACEA,CAAAquB,aAAA,CAAoBJ,CAApB,CAA6BC,CAA7B,CAEEtd,EAAAA,CAAWzT,CAAA0T,uBAAA,EACfD,EAAAI,YAAA,CAAqBkd,CAArB,CACAD,EAAA,CAAQxpB,CAAA6pB,QAAR,CAAA,CAA0BJ,CAAA,CAAqBzpB,CAAA6pB,QAArB,CACjBC,EAAAA,CAAI,CAAb,KAAgBC,CAAhB,CAAqBR,CAAAvwB,OAArB,CAA8C8wB,CAA9C,CAAkDC,CAAlD,CAAsDD,CAAA,EAAtD,CACM/pB,CAGJ,CAHcwpB,CAAA,CAAiBO,CAAjB,CAGd,CAFA9pB,CAAA,CAAOD,CAAP,CAAA0b,OAAA,EAEA,CADAtP,CAAAI,YAAA,CAAqBxM,CAArB,CACA,CAAA,OAAOwpB,CAAA,CAAiBO,CAAjB,CAGTP,EAAA,CAAiB,CAAjB,CAAA,CAAsBC,CACtBD,EAAAvwB,OAAA,CAA0B,CAvCkC,CA2C9D2pB,QAASA,GAAkB,CAAC/jB,CAAD,CAAKorB,CAAL,CAAiB,CAC1C,MAAOhvB,EAAA,CAAO,QAAQ,EAAG,CAAE,MAAO4D,EAAAI,MAAA,CAAS,IAAT,CAAe9D,SAAf,CAAT,CAAlB;AAAyD0D,CAAzD,CAA6DorB,CAA7D,CADmC,CAjxC5C,IAAIlK,GAAaA,QAAQ,CAAC/f,CAAD,CAAUpD,CAAV,CAAgB,CACvC,IAAA2mB,UAAA,CAAiBvjB,CACjB,KAAAygB,MAAA,CAAa7jB,CAAb,EAAqB,EAFkB,CAKzCmjB,GAAA9L,UAAA,CAAuB,YACT0M,EADS,WAeTuJ,QAAQ,CAACC,CAAD,CAAW,CAC1BA,CAAH,EAAiC,CAAjC,CAAeA,CAAAlxB,OAAf,EACE0kB,CAAAkB,SAAA,CAAkB,IAAA0E,UAAlB,CAAkC4G,CAAlC,CAF2B,CAfV,cAgCNC,QAAQ,CAACD,CAAD,CAAW,CAC7BA,CAAH,EAAiC,CAAjC,CAAeA,CAAAlxB,OAAf,EACE0kB,CAAA0M,YAAA,CAAqB,IAAA9G,UAArB,CAAqC4G,CAArC,CAF8B,CAhCb,cAkDNZ,QAAQ,CAACe,CAAD,CAAatC,CAAb,CAAyB,CAC9C,IAAIuC,EAAQC,EAAA,CAAgBF,CAAhB,CAA4BtC,CAA5B,CAAZ,CACIyC,EAAWD,EAAA,CAAgBxC,CAAhB,CAA4BsC,CAA5B,CAEK,EAApB,GAAGC,CAAAtxB,OAAH,CACE0kB,CAAA0M,YAAA,CAAqB,IAAA9G,UAArB,CAAqCkH,CAArC,CADF,CAE8B,CAAvB,GAAGA,CAAAxxB,OAAH,CACL0kB,CAAAkB,SAAA,CAAkB,IAAA0E,UAAlB,CAAkCgH,CAAlC,CADK,CAGL5M,CAAA+M,SAAA,CAAkB,IAAAnH,UAAlB,CAAkCgH,CAAlC,CAAyCE,CAAzC,CAT4C,CAlD3B,MAwEfxD,QAAQ,CAACztB,CAAD,CAAMY,CAAN,CAAauwB,CAAb,CAAwB9G,CAAxB,CAAkC,CAAA,IAK1C+G,EAAa7a,EAAA,CAAmB,IAAAwT,UAAA,CAAe,CAAf,CAAnB,CAAsC/pB,CAAtC,CAIboxB,EAAJ,GACE,IAAArH,UAAA5mB,KAAA,CAAoBnD,CAApB,CAAyBY,CAAzB,CACA,CAAAypB,CAAA,CAAW+G,CAFb,CAKA,KAAA,CAAKpxB,CAAL,CAAA,CAAYY,CAGRypB,EAAJ,CACE,IAAApD,MAAA,CAAWjnB,CAAX,CADF;AACoBqqB,CADpB,EAGEA,CAHF,CAGa,IAAApD,MAAA,CAAWjnB,CAAX,CAHb,IAKI,IAAAinB,MAAA,CAAWjnB,CAAX,CALJ,CAKsBqqB,CALtB,CAKiCtgB,EAAA,CAAW/J,CAAX,CAAgB,GAAhB,CALjC,CASAkD,EAAA,CAAWkkB,EAAA,CAAU,IAAA2C,UAAV,CAGX,IAAkB,GAAlB,GAAK7mB,CAAL,EAAiC,MAAjC,GAAyBlD,CAAzB,EACkB,KADlB,GACKkD,CADL,EACmC,KADnC,GAC2BlD,CAD3B,CAEE,IAAA,CAAKA,CAAL,CAAA,CAAYY,CAAZ,CAAoBwjB,CAAA,CAAcxjB,CAAd,CAA6B,KAA7B,GAAqBZ,CAArB,CAGJ,EAAA,CAAlB,GAAImxB,CAAJ,GACgB,IAAd,GAAIvwB,CAAJ,EAAsBA,CAAtB,GAAgCxB,CAAhC,CACE,IAAA2qB,UAAAsH,WAAA,CAA0BhH,CAA1B,CADF,CAGE,IAAAN,UAAA3mB,KAAA,CAAoBinB,CAApB,CAA8BzpB,CAA9B,CAJJ,CAUA,EADIiqB,CACJ,CADkB,IAAAA,YAClB,GAAehrB,CAAA,CAAQgrB,CAAA,CAAY7qB,CAAZ,CAAR,CAA0B,QAAQ,CAACqF,CAAD,CAAK,CACpD,GAAI,CACFA,CAAA,CAAGzE,CAAH,CADE,CAEF,MAAOgG,CAAP,CAAU,CACVsc,CAAA,CAAkBtc,CAAlB,CADU,CAHwC,CAAvC,CA5C+B,CAxE3B,UAgJXgkB,QAAQ,CAAC5qB,CAAD,CAAMqF,CAAN,CAAU,CAAA,IACtBghB,EAAQ,IADc,CAEtBwE,EAAexE,CAAAwE,YAAfA,GAAqCxE,CAAAwE,YAArCA,CAAyD,EAAzDA,CAFsB,CAGtByG,EAAazG,CAAA,CAAY7qB,CAAZ,CAAbsxB,GAAkCzG,CAAA,CAAY7qB,CAAZ,CAAlCsxB,CAAqD,EAArDA,CAEJA,EAAAhxB,KAAA,CAAe+E,CAAf,CACAwW,EAAA7X,WAAA,CAAsB,QAAQ,EAAG,CAC1BstB,CAAA1B,QAAL,EAEEvqB,CAAA,CAAGghB,CAAA,CAAMrmB,CAAN,CAAH,CAH6B,CAAjC,CAMA,OAAOqF,EAZmB,CAhJP,CAP+D,KAuKlFksB,EAAc1N,CAAA0N,YAAA,EAvKoE,CAwKlFC,GAAY3N,CAAA2N,UAAA,EAxKsE,CAyKlF7E,EAAsC,IAChB,EADC4E,CACD,EADsC,IACtC,EADwBC,EACxB;AAAhBrvB,EAAgB,CAChBwqB,QAA4B,CAACjB,CAAD,CAAW,CACvC,MAAOA,EAAAxkB,QAAA,CAAiB,OAAjB,CAA0BqqB,CAA1B,CAAArqB,QAAA,CAA+C,KAA/C,CAAsDsqB,EAAtD,CADgC,CA3KqC,CA8KlF7J,EAAkB,cAGtB,OAAOte,EAjL+E,CAJ5E,CA3H6C,CAo6C3D8d,QAASA,GAAkB,CAAC5e,CAAD,CAAO,CAChC,MAAOuI,GAAA,CAAUvI,CAAArB,QAAA,CAAauqB,EAAb,CAA4B,EAA5B,CAAV,CADyB,CA4DlCT,QAASA,GAAe,CAACU,CAAD,CAAOC,CAAP,CAAa,CAAA,IAC/BC,EAAS,EADsB,CAE/BC,EAAUH,CAAAlqB,MAAA,CAAW,KAAX,CAFqB,CAG/BsqB,EAAUH,CAAAnqB,MAAA,CAAW,KAAX,CAHqB,CAM3B/G,EAAI,CADZ,EAAA,CACA,IAAA,CAAeA,CAAf,CAAmBoxB,CAAApyB,OAAnB,CAAmCgB,CAAA,EAAnC,CAAwC,CAEtC,IADA,IAAIsxB,EAAQF,CAAA,CAAQpxB,CAAR,CAAZ,CACQkT,EAAI,CAAZ,CAAeA,CAAf,CAAmBme,CAAAryB,OAAnB,CAAmCkU,CAAA,EAAnC,CACE,GAAGoe,CAAH,EAAYD,CAAA,CAAQne,CAAR,CAAZ,CAAwB,SAAS,CAEnCie,EAAA,GAA2B,CAAhB,CAAAA,CAAAnyB,OAAA,CAAoB,GAApB,CAA0B,EAArC,EAA2CsyB,CALL,CAOxC,MAAOH,EAb4B,CA0BrCniB,QAASA,GAAmB,EAAG,CAAA,IACzBoX,EAAc,EADW,CAEzBmL,EAAY,yBAWhB,KAAAC,SAAA,CAAgBC,QAAQ,CAAC3pB,CAAD,CAAOmC,CAAP,CAAoB,CAC1CC,EAAA,CAAwBpC,CAAxB,CAA8B,YAA9B,CACI/F,EAAA,CAAS+F,CAAT,CAAJ,CACE9G,CAAA,CAAOolB,CAAP,CAAoBte,CAApB,CADF,CAGEse,CAAA,CAAYte,CAAZ,CAHF,CAGsBmC,CALoB,CAU5C,KAAAuO,KAAA,CAAY,CAAC,WAAD,CAAc,SAAd,CAAyB,QAAQ,CAAC4B,CAAD,CAAYc,CAAZ,CAAqB,CAwBhE,MAAO,SAAQ,CAACwW,CAAD,CAAa/X,CAAb,CAAqB,CAAA,IAC9BM,CAD8B;AACbhQ,CADa,CACA0nB,CAE/BzyB,EAAA,CAASwyB,CAAT,CAAH,GACElrB,CAOA,CAPQkrB,CAAAlrB,MAAA,CAAiB+qB,CAAjB,CAOR,CANAtnB,CAMA,CANczD,CAAA,CAAM,CAAN,CAMd,CALAmrB,CAKA,CALanrB,CAAA,CAAM,CAAN,CAKb,CAJAkrB,CAIA,CAJatL,CAAA3mB,eAAA,CAA2BwK,CAA3B,CACA,CAAPmc,CAAA,CAAYnc,CAAZ,CAAO,CACPE,EAAA,CAAOwP,CAAAoR,OAAP,CAAsB9gB,CAAtB,CAAmC,CAAA,CAAnC,CADO,EACqCE,EAAA,CAAO+Q,CAAP,CAAgBjR,CAAhB,CAA6B,CAAA,CAA7B,CAElD,CAAAF,EAAA,CAAY2nB,CAAZ,CAAwBznB,CAAxB,CAAqC,CAAA,CAArC,CARF,CAWAgQ,EAAA,CAAWG,CAAA7B,YAAA,CAAsBmZ,CAAtB,CAAkC/X,CAAlC,CAEX,IAAIgY,CAAJ,CAAgB,CACd,GAAMhY,CAAAA,CAAN,EAAwC,QAAxC,EAAgB,MAAOA,EAAAoR,OAAvB,CACE,KAAMnsB,EAAA,CAAO,aAAP,CAAA,CAAsB,OAAtB,CAEFqL,CAFE,EAEaynB,CAAA5pB,KAFb,CAE8B6pB,CAF9B,CAAN,CAKFhY,CAAAoR,OAAA,CAAc4G,CAAd,CAAA,CAA4B1X,CAPd,CAUhB,MAAOA,EA1B2B,CAxB4B,CAAtD,CAvBiB,CAsG/BhL,QAASA,GAAiB,EAAE,CAC1B,IAAAuJ,KAAA,CAAY,CAAC,SAAD,CAAY,QAAQ,CAAC/Z,CAAD,CAAQ,CACtC,MAAOuH,EAAA,CAAOvH,CAAAC,SAAP,CAD+B,CAA5B,CADc,CAsC5BwQ,QAASA,GAAyB,EAAG,CACnC,IAAAsJ,KAAA,CAAY,CAAC,MAAD,CAAS,QAAQ,CAAC2D,CAAD,CAAO,CAClC,MAAO,SAAQ,CAACyV,CAAD,CAAYC,CAAZ,CAAmB,CAChC1V,CAAAM,MAAAzX,MAAA,CAAiBmX,CAAjB,CAAuBjb,SAAvB,CADgC,CADA,CAAxB,CADuB,CAcrC4wB,QAASA,GAAY,CAAC5D,CAAD,CAAU,CAAA,IACzBjc,EAAS,EADgB,CACZ1S,CADY,CACP4F,CADO,CACFnF,CAE3B,IAAI,CAACkuB,CAAL,CAAc,MAAOjc,EAErB7S,EAAA,CAAQ8uB,CAAAnnB,MAAA,CAAc,IAAd,CAAR,CAA6B,QAAQ,CAACgrB,CAAD,CAAO,CAC1C/xB,CAAA,CAAI+xB,CAAA/uB,QAAA,CAAa,GAAb,CACJzD,EAAA,CAAMsG,CAAA,CAAUkM,EAAA,CAAKggB,CAAA5K,OAAA,CAAY,CAAZ;AAAennB,CAAf,CAAL,CAAV,CACNmF,EAAA,CAAM4M,EAAA,CAAKggB,CAAA5K,OAAA,CAAYnnB,CAAZ,CAAgB,CAAhB,CAAL,CAEFT,EAAJ,GAEI0S,CAAA,CAAO1S,CAAP,CAFJ,CACM0S,CAAA,CAAO1S,CAAP,CAAJ,CACE0S,CAAA,CAAO1S,CAAP,CADF,EACiB,IADjB,CACwB4F,CADxB,EAGgBA,CAJlB,CAL0C,CAA5C,CAcA,OAAO8M,EAnBsB,CAmC/B+f,QAASA,GAAa,CAAC9D,CAAD,CAAU,CAC9B,IAAI+D,EAAalwB,CAAA,CAASmsB,CAAT,CAAA,CAAoBA,CAApB,CAA8BvvB,CAE/C,OAAO,SAAQ,CAACmJ,CAAD,CAAO,CACfmqB,CAAL,GAAiBA,CAAjB,CAA+BH,EAAA,CAAa5D,CAAb,CAA/B,CAEA,OAAIpmB,EAAJ,CACSmqB,CAAA,CAAWpsB,CAAA,CAAUiC,CAAV,CAAX,CADT,EACwC,IADxC,CAIOmqB,CAPa,CAHQ,CAyBhCC,QAASA,GAAa,CAACnpB,CAAD,CAAOmlB,CAAP,CAAgBiE,CAAhB,CAAqB,CACzC,GAAI3yB,CAAA,CAAW2yB,CAAX,CAAJ,CACE,MAAOA,EAAA,CAAIppB,CAAJ,CAAUmlB,CAAV,CAET9uB,EAAA,CAAQ+yB,CAAR,CAAa,QAAQ,CAACvtB,CAAD,CAAK,CACxBmE,CAAA,CAAOnE,CAAA,CAAGmE,CAAH,CAASmlB,CAAT,CADiB,CAA1B,CAIA,OAAOnlB,EARkC,CAiB3CuG,QAASA,GAAa,EAAG,CAAA,IACnB8iB,EAAa,kBADM,CAEnBC,EAAW,YAFQ,CAGnBC,EAAoB,cAHD,CAInBC,EAAgC,CAAC,cAAD,CAAiB,gCAAjB,CAJb,CAMnBC,EAAW,IAAAA,SAAXA,CAA2B,mBAEV,CAAC,QAAQ,CAACzpB,CAAD,CAAO,CAC7B7J,CAAA,CAAS6J,CAAT,CAAJ,GAEEA,CACA,CADOA,CAAAtC,QAAA,CAAa6rB,CAAb,CAAgC,EAAhC,CACP,CAAIF,CAAAnpB,KAAA,CAAgBF,CAAhB,CAAJ,EAA6BspB,CAAAppB,KAAA,CAAcF,CAAd,CAA7B,GACEA,CADF,CACSvD,EAAA,CAASuD,CAAT,CADT,CAHF,CAMA,OAAOA,EAP0B,CAAhB,CAFU,kBAaX,CAAC,QAAQ,CAAC0pB,CAAD,CAAI,CAC7B,MAAO1wB,EAAA,CAAS0wB,CAAT,CAAA;AAvhNmB,eAuhNnB,GAvhNJvwB,EAAAxC,KAAA,CAuhN2B+yB,CAvhN3B,CAuhNI,EAlhNmB,eAkhNnB,GAlhNJvwB,EAAAxC,KAAA,CAkhNyC+yB,CAlhNzC,CAkhNI,CAA0CrtB,EAAA,CAAOqtB,CAAP,CAA1C,CAAsDA,CADhC,CAAb,CAbW,SAkBpB,QACC,QACI,mCADJ,CADD,MAICrvB,EAAA,CAAKmvB,CAAL,CAJD,KAKCnvB,EAAA,CAAKmvB,CAAL,CALD,OAMCnvB,EAAA,CAAKmvB,CAAL,CAND,CAlBoB,gBA2Bb,YA3Ba,gBA4Bb,cA5Ba,CANR,CAyCnBG,EAAuB,IAAAC,aAAvBD,CAA2C,EAzCxB,CA+CnBE,EAA+B,IAAAC,qBAA/BD,CAA2D,EAE/D,KAAApa,KAAA,CAAY,CAAC,cAAD,CAAiB,UAAjB,CAA6B,eAA7B,CAA8C,YAA9C,CAA4D,IAA5D,CAAkE,WAAlE,CACR,QAAQ,CAACsa,CAAD,CAAeC,CAAf,CAAyBhR,CAAzB,CAAwC3G,CAAxC,CAAoD4X,CAApD,CAAwD5Y,CAAxD,CAAmE,CAihB7EiJ,QAASA,EAAK,CAAC4P,CAAD,CAAgB,CA6E5BC,QAASA,EAAiB,CAAClF,CAAD,CAAW,CAEnC,IAAImF,EAAOnyB,CAAA,CAAO,EAAP,CAAWgtB,CAAX,CAAqB,MACxBkE,EAAA,CAAclE,CAAAjlB,KAAd,CAA6BilB,CAAAE,QAA7B,CAA+CxiB,CAAAwnB,kBAA/C,CADwB,CAArB,CAGX,OAzpBC,IA0pBM,EADWlF,CAAAoF,OACX,EA1pBoB,GA0pBpB,CADWpF,CAAAoF,OACX;AAAHD,CAAG,CACHH,CAAAK,OAAA,CAAUF,CAAV,CAP+B,CA5ErC,IAAIznB,EAAS,QACH,KADG,kBAEO8mB,CAAAc,iBAFP,mBAGQd,CAAAU,kBAHR,CAAb,CAKIhF,EAiFJqF,QAAqB,CAAC7nB,CAAD,CAAS,CA2B5B8nB,QAASA,EAAW,CAACtF,CAAD,CAAU,CAC5B,IAAIuF,CAEJr0B,EAAA,CAAQ8uB,CAAR,CAAiB,QAAQ,CAACwF,CAAD,CAAWC,CAAX,CAAmB,CACtCn0B,CAAA,CAAWk0B,CAAX,CAAJ,GACED,CACA,CADgBC,CAAA,EAChB,CAAqB,IAArB,EAAID,CAAJ,CACEvF,CAAA,CAAQyF,CAAR,CADF,CACoBF,CADpB,CAGE,OAAOvF,CAAA,CAAQyF,CAAR,CALX,CAD0C,CAA5C,CAH4B,CA3BF,IACxBC,EAAapB,CAAAtE,QADW,CAExB2F,EAAa7yB,CAAA,CAAO,EAAP,CAAW0K,CAAAwiB,QAAX,CAFW,CAGxB4F,CAHwB,CAGeC,CAHf,CAK5BH,EAAa5yB,CAAA,CAAO,EAAP,CAAW4yB,CAAAI,OAAX,CAA8BJ,CAAA,CAAW/tB,CAAA,CAAU6F,CAAAL,OAAV,CAAX,CAA9B,CAGbmoB,EAAA,CAAYI,CAAZ,CACAJ,EAAA,CAAYK,CAAZ,CAGA,EAAA,CACA,IAAKC,CAAL,GAAsBF,EAAtB,CAAkC,CAChCK,CAAA,CAAyBpuB,CAAA,CAAUiuB,CAAV,CAEzB,KAAKC,CAAL,GAAsBF,EAAtB,CACE,GAAIhuB,CAAA,CAAUkuB,CAAV,CAAJ,GAAiCE,CAAjC,CACE,SAAS,CAIbJ,EAAA,CAAWC,CAAX,CAAA,CAA4BF,CAAA,CAAWE,CAAX,CATI,CAYlC,MAAOD,EAzBqB,CAjFhB,CAAaZ,CAAb,CAEdjyB,EAAA,CAAO0K,CAAP,CAAeunB,CAAf,CACAvnB,EAAAwiB,QAAA,CAAiBA,CACjBxiB,EAAAL,OAAA,CAAgBU,EAAA,CAAUL,CAAAL,OAAV,CAKhB,EAHI6oB,CAGJ,CAHgBC,EAAA,CAAgBzoB,CAAA0R,IAAhB,CACA,CAAV2V,CAAA5T,QAAA,EAAA,CAAmBzT,CAAA0oB,eAAnB,EAA4C5B,CAAA4B,eAA5C,CAAU,CACVz1B,CACN,IACEuvB,CAAA,CAASxiB,CAAA2oB,eAAT,EAAkC7B,CAAA6B,eAAlC,CADF;AACgEH,CADhE,CA0BA,KAAII,EAAQ,CArBQC,QAAQ,CAAC7oB,CAAD,CAAS,CACnCwiB,CAAA,CAAUxiB,CAAAwiB,QACV,KAAIsG,EAAUtC,EAAA,CAAcxmB,CAAA3C,KAAd,CAA2BipB,EAAA,CAAc9D,CAAd,CAA3B,CAAmDxiB,CAAA4nB,iBAAnD,CAGVzxB,EAAA,CAAY6J,CAAA3C,KAAZ,CAAJ,EACE3J,CAAA,CAAQ8uB,CAAR,CAAiB,QAAQ,CAAC/tB,CAAD,CAAQwzB,CAAR,CAAgB,CACb,cAA1B,GAAI9tB,CAAA,CAAU8tB,CAAV,CAAJ,EACI,OAAOzF,CAAA,CAAQyF,CAAR,CAF4B,CAAzC,CAOE9xB,EAAA,CAAY6J,CAAA+oB,gBAAZ,CAAJ,EAA4C,CAAA5yB,CAAA,CAAY2wB,CAAAiC,gBAAZ,CAA5C,GACE/oB,CAAA+oB,gBADF,CAC2BjC,CAAAiC,gBAD3B,CAKA,OAAOC,EAAA,CAAQhpB,CAAR,CAAgB8oB,CAAhB,CAAyBtG,CAAzB,CAAAyG,KAAA,CAAuCzB,CAAvC,CAA0DA,CAA1D,CAlB4B,CAqBzB,CAAgBv0B,CAAhB,CAAZ,CACIi2B,EAAU5B,CAAA6B,KAAA,CAAQnpB,CAAR,CAYd,KATAtM,CAAA,CAAQ01B,CAAR,CAA8B,QAAQ,CAACC,CAAD,CAAc,CAClD,CAAIA,CAAAC,QAAJ,EAA2BD,CAAAE,aAA3B,GACEX,CAAA1zB,QAAA,CAAcm0B,CAAAC,QAAd,CAAmCD,CAAAE,aAAnC,CAEF,EAAIF,CAAA/G,SAAJ,EAA4B+G,CAAAG,cAA5B,GACEZ,CAAAz0B,KAAA,CAAWk1B,CAAA/G,SAAX,CAAiC+G,CAAAG,cAAjC,CALgD,CAApD,CASA,CAAMZ,CAAAt1B,OAAN,CAAA,CAAoB,CACdm2B,CAAAA,CAASb,CAAA9iB,MAAA,EACb,KAAI4jB,EAAWd,CAAA9iB,MAAA,EAAf,CAEAojB,EAAUA,CAAAD,KAAA,CAAaQ,CAAb,CAAqBC,CAArB,CAJQ,CAOpBR,CAAAnH,QAAA,CAAkB4H,QAAQ,CAACzwB,CAAD,CAAK,CAC7BgwB,CAAAD,KAAA,CAAa,QAAQ,CAAC3G,CAAD,CAAW,CAC9BppB,CAAA,CAAGopB,CAAAjlB,KAAH;AAAkBilB,CAAAoF,OAAlB,CAAmCpF,CAAAE,QAAnC,CAAqDxiB,CAArD,CAD8B,CAAhC,CAGA,OAAOkpB,EAJsB,CAO/BA,EAAAnY,MAAA,CAAgB6Y,QAAQ,CAAC1wB,CAAD,CAAK,CAC3BgwB,CAAAD,KAAA,CAAa,IAAb,CAAmB,QAAQ,CAAC3G,CAAD,CAAW,CACpCppB,CAAA,CAAGopB,CAAAjlB,KAAH,CAAkBilB,CAAAoF,OAAlB,CAAmCpF,CAAAE,QAAnC,CAAqDxiB,CAArD,CADoC,CAAtC,CAGA,OAAOkpB,EAJoB,CAO7B,OAAOA,EA3EqB,CAiQ9BF,QAASA,EAAO,CAAChpB,CAAD,CAAS8oB,CAAT,CAAkBX,CAAlB,CAA8B,CAqD5C0B,QAASA,EAAI,CAACnC,CAAD,CAASpF,CAAT,CAAmBwH,CAAnB,CAAkCC,CAAlC,CAA8C,CACrDnc,CAAJ,GA93BC,GA+3BC,EAAc8Z,CAAd,EA/3ByB,GA+3BzB,CAAcA,CAAd,CACE9Z,CAAAhC,IAAA,CAAU8F,CAAV,CAAe,CAACgW,CAAD,CAASpF,CAAT,CAAmB8D,EAAA,CAAa0D,CAAb,CAAnB,CAAgDC,CAAhD,CAAf,CADF,CAIEnc,CAAAmI,OAAA,CAAarE,CAAb,CALJ,CASAsY,EAAA,CAAe1H,CAAf,CAAyBoF,CAAzB,CAAiCoC,CAAjC,CAAgDC,CAAhD,CACKra,EAAAua,QAAL,EAAyBva,CAAAtS,OAAA,EAXgC,CAkB3D4sB,QAASA,EAAc,CAAC1H,CAAD,CAAWoF,CAAX,CAAmBlF,CAAnB,CAA4BuH,CAA5B,CAAwC,CAE7DrC,CAAA,CAAS3G,IAAAC,IAAA,CAAS0G,CAAT,CAAiB,CAAjB,CAER,EAn5BA,GAm5BA,EAAUA,CAAV,EAn5B0B,GAm5B1B,CAAUA,CAAV,CAAoBwC,CAAAC,QAApB,CAAuCD,CAAAvC,OAAvC,EAAwD,MACjDrF,CADiD,QAE/CoF,CAF+C,SAG9CpB,EAAA,CAAc9D,CAAd,CAH8C,QAI/CxiB,CAJ+C,YAK1C+pB,CAL0C,CAAxD,CAJ4D,CAc/DK,QAASA,EAAgB,EAAG,CAC1B,IAAIC,EAAM/yB,EAAA,CAAQqgB,CAAA2S,gBAAR,CAA+BtqB,CAA/B,CACG,GAAb,GAAIqqB,CAAJ,EAAgB1S,CAAA2S,gBAAA7yB,OAAA,CAA6B4yB,CAA7B,CAAkC,CAAlC,CAFU,CArFgB,IACxCH,EAAW5C,CAAApT,MAAA,EAD6B,CAExCgV,EAAUgB,CAAAhB,QAF8B,CAGxCtb,CAHwC,CAIxC2c,CAJwC,CAKxC7Y,EAAM8Y,CAAA,CAASxqB,CAAA0R,IAAT;AAAqB1R,CAAAyqB,OAArB,CAEV9S,EAAA2S,gBAAAn2B,KAAA,CAA2B6L,CAA3B,CACAkpB,EAAAD,KAAA,CAAamB,CAAb,CAA+BA,CAA/B,CAGA,EAAKpqB,CAAA4N,MAAL,EAAqBkZ,CAAAlZ,MAArB,IAAyD,CAAA,CAAzD,GAAwC5N,CAAA4N,MAAxC,EAAmF,KAAnF,EAAkE5N,CAAAL,OAAlE,IACEiO,CADF,CACUvX,CAAA,CAAS2J,CAAA4N,MAAT,CAAA,CAAyB5N,CAAA4N,MAAzB,CACAvX,CAAA,CAASywB,CAAAlZ,MAAT,CAAA,CAA2BkZ,CAAAlZ,MAA3B,CACA8c,CAHV,CAMA,IAAI9c,CAAJ,CAEE,GADA2c,CACI,CADS3c,CAAAP,IAAA,CAAUqE,CAAV,CACT,CAAAtb,CAAA,CAAUm0B,CAAV,CAAJ,CAA2B,CACzB,GAAIA,CAAAtB,KAAJ,CAGE,MADAsB,EAAAtB,KAAA,CAAgBmB,CAAhB,CAAkCA,CAAlC,CACOG,CAAAA,CAGH92B,EAAA,CAAQ82B,CAAR,CAAJ,CACEP,CAAA,CAAeO,CAAA,CAAW,CAAX,CAAf,CAA8BA,CAAA,CAAW,CAAX,CAA9B,CAA6C7yB,EAAA,CAAK6yB,CAAA,CAAW,CAAX,CAAL,CAA7C,CAAkEA,CAAA,CAAW,CAAX,CAAlE,CADF,CAGEP,CAAA,CAAeO,CAAf,CAA2B,GAA3B,CAAgC,EAAhC,CAAoC,IAApC,CAVqB,CAA3B,IAeE3c,EAAAhC,IAAA,CAAU8F,CAAV,CAAewX,CAAf,CAKA/yB,EAAA,CAAYo0B,CAAZ,CAAJ,EACEnD,CAAA,CAAapnB,CAAAL,OAAb,CAA4B+R,CAA5B,CAAiCoX,CAAjC,CAA0Ce,CAA1C,CAAgD1B,CAAhD,CAA4DnoB,CAAA2qB,QAA5D,CACI3qB,CAAA+oB,gBADJ,CAC4B/oB,CAAA4qB,aAD5B,CAIF,OAAO1B,EA5CqC,CA4F9CsB,QAASA,EAAQ,CAAC9Y,CAAD,CAAM+Y,CAAN,CAAc,CACzB,GAAI,CAACA,CAAL,CAAa,MAAO/Y,EACpB,KAAInW,EAAQ,EACZlH,GAAA,CAAco2B,CAAd,CAAsB,QAAQ,CAACh2B,CAAD,CAAQZ,CAAR,CAAa,CAC3B,IAAd,GAAIY,CAAJ,EAAsB0B,CAAA,CAAY1B,CAAZ,CAAtB,GACKhB,CAAA,CAAQgB,CAAR,CAEL,GAFqBA,CAErB,CAF6B,CAACA,CAAD,CAE7B,EAAAf,CAAA,CAAQe,CAAR,CAAe,QAAQ,CAACyF,CAAD,CAAI,CACrB7D,CAAA,CAAS6D,CAAT,CAAJ,GACEA,CADF,CACMR,EAAA,CAAOQ,CAAP,CADN,CAGAqB,EAAApH,KAAA,CAAWsH,EAAA,CAAe5H,CAAf,CAAX,CAAiC,GAAjC,CACW4H,EAAA,CAAevB,CAAf,CADX,CAJyB,CAA3B,CAHA,CADyC,CAA3C,CAYkB,EAAlB,CAAGqB,CAAAjI,OAAH;CACEoe,CADF,GACgC,EAAtB,EAACA,CAAApa,QAAA,CAAY,GAAZ,CAAD,CAA2B,GAA3B,CAAiC,GAD3C,EACkDiE,CAAAxG,KAAA,CAAW,GAAX,CADlD,CAGA,OAAO2c,EAlBkB,CA52B/B,IAAIgZ,EAAerU,CAAA,CAAc,OAAd,CAAnB,CAOI+S,EAAuB,EAE3B11B,EAAA,CAAQszB,CAAR,CAA8B,QAAQ,CAAC6D,CAAD,CAAqB,CACzDzB,CAAAl0B,QAAA,CAA6B1B,CAAA,CAASq3B,CAAT,CACA,CAAvBnc,CAAArB,IAAA,CAAcwd,CAAd,CAAuB,CAAanc,CAAA1R,OAAA,CAAiB6tB,CAAjB,CAD1C,CADyD,CAA3D,CAKAn3B,EAAA,CAAQwzB,CAAR,CAAsC,QAAQ,CAAC2D,CAAD,CAAqBl2B,CAArB,CAA4B,CACxE,IAAIm2B,EAAat3B,CAAA,CAASq3B,CAAT,CACA,CAAXnc,CAAArB,IAAA,CAAcwd,CAAd,CAAW,CACXnc,CAAA1R,OAAA,CAAiB6tB,CAAjB,CAONzB,EAAA3xB,OAAA,CAA4B9C,CAA5B,CAAmC,CAAnC,CAAsC,UAC1B2tB,QAAQ,CAACA,CAAD,CAAW,CAC3B,MAAOwI,EAAA,CAAWxD,CAAA6B,KAAA,CAAQ7G,CAAR,CAAX,CADoB,CADO,eAIrBkH,QAAQ,CAAClH,CAAD,CAAW,CAChC,MAAOwI,EAAA,CAAWxD,CAAAK,OAAA,CAAUrF,CAAV,CAAX,CADyB,CAJE,CAAtC,CAVwE,CAA1E,CAooBA3K,EAAA2S,gBAAA,CAAwB,EA+FxBS,UAA2B,CAAC7uB,CAAD,CAAQ,CACjCxI,CAAA,CAAQ8B,SAAR,CAAmB,QAAQ,CAAC4G,CAAD,CAAO,CAChCub,CAAA,CAAMvb,CAAN,CAAA,CAAc,QAAQ,CAACsV,CAAD,CAAM1R,CAAN,CAAc,CAClC,MAAO2X,EAAA,CAAMriB,CAAA,CAAO0K,CAAP,EAAiB,EAAjB,CAAqB,QACxB5D,CADwB,KAE3BsV,CAF2B,CAArB,CAAN,CAD2B,CADJ,CAAlC,CADiC,CAAnCqZ,CA7CA,CAAmB,KAAnB,CAA0B,QAA1B,CAAoC,MAApC,CAA4C,OAA5C,CAyDAC,UAAmC,CAAC5uB,CAAD,CAAO,CACxC1I,CAAA,CAAQ8B,SAAR,CAAmB,QAAQ,CAAC4G,CAAD,CAAO,CAChCub,CAAA,CAAMvb,CAAN,CAAA,CAAc,QAAQ,CAACsV,CAAD,CAAMrU,CAAN,CAAY2C,CAAZ,CAAoB,CACxC,MAAO2X,EAAA,CAAMriB,CAAA,CAAO0K,CAAP;AAAiB,EAAjB,CAAqB,QACxB5D,CADwB,KAE3BsV,CAF2B,MAG1BrU,CAH0B,CAArB,CAAN,CADiC,CADV,CAAlC,CADwC,CAA1C2tB,CA9BA,CAA2B,MAA3B,CAAmC,KAAnC,CAYArT,EAAAmP,SAAA,CAAiBA,CAGjB,OAAOnP,EAhvBsE,CADnE,CAjDW,CAy7BzBsT,QAASA,GAAS,CAACtrB,CAAD,CAAS,CAIvB,GAAY,CAAZ,EAAI4L,CAAJ,GAAkB,CAAC5L,CAAA7E,MAAA,CAAa,uCAAb,CAAnB,EACE,CAAC/H,CAAAm4B,eADH,EAEE,MAAO,KAAIn4B,CAAAo4B,cAAJ,CAAyB,mBAAzB,CACF,IAAIp4B,CAAAm4B,eAAJ,CACL,MAAO,KAAIn4B,CAAAm4B,eAGb,MAAMh4B,EAAA,CAAO,cAAP,CAAA,CAAuB,OAAvB,CAAN,CAXuB,CA8B3B2Q,QAASA,GAAoB,EAAG,CAC9B,IAAAiJ,KAAA,CAAY,CAAC,UAAD,CAAa,SAAb,CAAwB,WAAxB,CAAqC,QAAQ,CAACua,CAAD,CAAW7X,CAAX,CAAoBiF,CAApB,CAA+B,CACtF,MAAO2W,GAAA,CAAkB/D,CAAlB,CAA4B4D,EAA5B,CAAuC5D,CAAAnT,MAAvC,CAAuD1E,CAAAhS,QAAA6tB,UAAvD,CAAkF5W,CAAA,CAAU,CAAV,CAAlF,CAD+E,CAA5E,CADkB,CAMhC2W,QAASA,GAAiB,CAAC/D,CAAD,CAAW4D,CAAX,CAAsBK,CAAtB,CAAqCD,CAArC,CAAgDxZ,CAAhD,CAA6D,CA4HrF0Z,QAASA,EAAQ,CAAC7Z,CAAD,CAAMmY,CAAN,CAAY,CAAA,IAIvB2B,EAAS3Z,CAAA/K,cAAA,CAA0B,QAA1B,CAJc,CAKvB2kB,EAAcA,QAAQ,EAAG,CACvBD,CAAAE,mBAAA;AAA4BF,CAAAG,OAA5B,CAA4CH,CAAAI,QAA5C,CAA6D,IAC7D/Z,EAAAga,KAAAxkB,YAAA,CAA6BmkB,CAA7B,CACI3B,EAAJ,EAAUA,CAAA,EAHa,CAM7B2B,EAAArjB,KAAA,CAAc,iBACdqjB,EAAApzB,IAAA,CAAasZ,CAETnG,EAAJ,EAAoB,CAApB,EAAYA,CAAZ,CACEigB,CAAAE,mBADF,CAC8BI,QAAQ,EAAG,CACjC,iBAAAvuB,KAAA,CAAuBiuB,CAAAO,WAAvB,CAAJ,EACEN,CAAA,EAFmC,CADzC,CAOED,CAAAG,OAPF,CAOkBH,CAAAI,QAPlB,CAOmCI,QAAQ,EAAG,CAC1CP,CAAA,EAD0C,CAK9C5Z,EAAAga,KAAAhlB,YAAA,CAA6B2kB,CAA7B,CACA,OAAOC,EA3BoB,CA3H7B,IAAIQ,EAAW,EAGf,OAAO,SAAQ,CAACtsB,CAAD,CAAS+R,CAAT,CAAcoL,CAAd,CAAoBvK,CAApB,CAA8BiQ,CAA9B,CAAuCmI,CAAvC,CAAgD5B,CAAhD,CAAiE6B,CAAjE,CAA+E,CA6F5FsB,QAASA,EAAc,EAAG,CACxBxE,CAAA,CAASuE,CACTE,EAAA,EAAaA,CAAA,EACbC,EAAA,EAAOA,CAAAC,MAAA,EAHiB,CAM1BC,QAASA,EAAe,CAAC/Z,CAAD,CAAWmV,CAAX,CAAmBpF,CAAnB,CAA6BwH,CAA7B,CAA4CC,CAA5C,CAAwD,CAE9E1V,CAAA,EAAaiX,CAAAhX,OAAA,CAAqBD,CAArB,CACb8X,EAAA,CAAYC,CAAZ,CAAkB,IAKH,EAAf,GAAI1E,CAAJ,GACEA,CADF,CACWpF,CAAA,CAAW,GAAX,CAA6C,MAA5B,EAAAiK,EAAA,CAAW7a,CAAX,CAAA8a,SAAA,CAAqC,GAArC,CAA2C,CADvE,CAQAja,EAAA,CAHoB,IAAXmV,GAAAA,CAAAA,CAAkB,GAAlBA,CAAwBA,CAGjC,CAAiBpF,CAAjB,CAA2BwH,CAA3B,CAFaC,CAEb,EAF2B,EAE3B,CACA1C,EAAAnV,6BAAA,CAAsCnc,CAAtC,CAjB8E,CAlGhF,IAAI2xB,CACJL,EAAAlV,6BAAA,EACAT;CAAA,CAAMA,CAAN,EAAa2V,CAAA3V,IAAA,EAEb,IAAyB,OAAzB,EAAIvX,CAAA,CAAUwF,CAAV,CAAJ,CAAkC,CAChC,IAAI8sB,EAAa,GAAbA,CAAoBj2B,CAAA60B,CAAAqB,QAAA,EAAAl2B,UAAA,CAA8B,EAA9B,CACxB60B,EAAA,CAAUoB,CAAV,CAAA,CAAwB,QAAQ,CAACpvB,CAAD,CAAO,CACrCguB,CAAA,CAAUoB,CAAV,CAAApvB,KAAA,CAA6BA,CADQ,CAIvC,KAAI8uB,EAAYZ,CAAA,CAAS7Z,CAAA3W,QAAA,CAAY,eAAZ,CAA6B,oBAA7B,CAAoD0xB,CAApD,CAAT,CACZ,QAAQ,EAAG,CACTpB,CAAA,CAAUoB,CAAV,CAAApvB,KAAJ,CACEivB,CAAA,CAAgB/Z,CAAhB,CAA0B,GAA1B,CAA+B8Y,CAAA,CAAUoB,CAAV,CAAApvB,KAA/B,CADF,CAGEivB,CAAA,CAAgB/Z,CAAhB,CAA0BmV,CAA1B,EAAqC,EAArC,CAEF2D,EAAA,CAAUoB,CAAV,CAAA,CAAwBjvB,EAAAzH,KANX,CADC,CANgB,CAAlC,IAeO,CAEL,IAAIq2B,EAAMnB,CAAA,CAAUtrB,CAAV,CAEVysB,EAAAO,KAAA,CAAShtB,CAAT,CAAiB+R,CAAjB,CAAsB,CAAA,CAAtB,CACAhe,EAAA,CAAQ8uB,CAAR,CAAiB,QAAQ,CAAC/tB,CAAD,CAAQZ,CAAR,CAAa,CAChCuC,CAAA,CAAU3B,CAAV,CAAJ,EACI23B,CAAAQ,iBAAA,CAAqB/4B,CAArB,CAA0BY,CAA1B,CAFgC,CAAtC,CASA23B,EAAAV,mBAAA,CAAyBmB,QAAQ,EAAG,CAQlC,GAAIT,CAAJ,EAA6B,CAA7B,EAAWA,CAAAL,WAAX,CAAgC,CAAA,IAC1Be,EAAkB,IADQ,CAE1BxK,EAAW,IAEZoF,EAAH,GAAcuE,CAAd,GACEa,CAIA,CAJkBV,CAAAW,sBAAA,EAIlB,CAAAzK,CAAA,CAAY,UAAD,EAAe8J,EAAf,CAAsBA,CAAA9J,SAAtB,CAAqC8J,CAAAY,aALlD,CAQAV,EAAA,CAAgB/Z,CAAhB,CACImV,CADJ,EACc0E,CAAA1E,OADd,CAEIpF,CAFJ,CAGIwK,CAHJ,CAIIV,CAAArC,WAJJ,EAIsB,EAJtB,CAZ8B,CARE,CA4BhChB,EAAJ,GACEqD,CAAArD,gBADF;AACwB,CAAA,CADxB,CAIA,IAAI6B,CAAJ,CACE,GAAI,CACFwB,CAAAxB,aAAA,CAAmBA,CADjB,CAEF,MAAOnwB,CAAP,CAAU,CAQV,GAAqB,MAArB,GAAImwB,CAAJ,CACE,KAAMnwB,EAAN,CATQ,CAcd2xB,CAAAa,KAAA,CAASnQ,CAAT,EAAiB,IAAjB,CA/DK,CAkEP,GAAc,CAAd,CAAI6N,CAAJ,CACE,IAAItW,EAAYiX,CAAA,CAAcY,CAAd,CAA8BvB,CAA9B,CADlB,KAEWA,EAAJ,EAAeA,CAAA1B,KAAf,EACL0B,CAAA1B,KAAA,CAAaiD,CAAb,CAzF0F,CAJT,CAiMvFxoB,QAASA,GAAoB,EAAG,CAC9B,IAAI0hB,EAAc,IAAlB,CACIC,EAAY,IAWhB,KAAAD,YAAA,CAAmB8H,QAAQ,CAACz4B,CAAD,CAAO,CAChC,MAAIA,EAAJ,EACE2wB,CACO,CADO3wB,CACP,CAAA,IAFT,EAIS2wB,CALuB,CAkBlC,KAAAC,UAAA,CAAiB8H,QAAQ,CAAC14B,CAAD,CAAO,CAC9B,MAAIA,EAAJ,EACE4wB,CACO,CADK5wB,CACL,CAAA,IAFT,EAIS4wB,CALqB,CAUhC,KAAAvY,KAAA,CAAY,CAAC,QAAD,CAAW,mBAAX,CAAgC,MAAhC,CAAwC,QAAQ,CAAC+K,CAAD,CAASd,CAAT,CAA4BgB,CAA5B,CAAkC,CA0C5FL,QAASA,EAAY,CAACqL,CAAD,CAAOqK,CAAP,CAA2BC,CAA3B,CAA2C,CAW9D,IAX8D,IAC1Dh0B,CAD0D,CAE1Di0B,CAF0D,CAG1D34B,EAAQ,CAHkD,CAI1D4G,EAAQ,EAJkD,CAK1DjI,EAASyvB,CAAAzvB,OALiD,CAM1Di6B,EAAmB,CAAA,CANuC,CAS1Dh0B,EAAS,EAEb,CAAM5E,CAAN,CAAcrB,CAAd,CAAA,CAC4D,EAA1D,GAAO+F,CAAP,CAAoB0pB,CAAAzrB,QAAA,CAAa8tB,CAAb,CAA0BzwB,CAA1B,CAApB,GAC+E,EAD/E,GACO24B,CADP,CACkBvK,CAAAzrB,QAAA,CAAa+tB,CAAb,CAAwBhsB,CAAxB,CAAqCm0B,CAArC,CADlB,GAEG74B,CAID,EAJU0E,CAIV,EAJyBkC,CAAApH,KAAA,CAAW4uB,CAAA9O,UAAA,CAAetf,CAAf,CAAsB0E,CAAtB,CAAX,CAIzB,CAHAkC,CAAApH,KAAA,CAAW+E,CAAX,CAAgB2e,CAAA,CAAO4V,CAAP,CAAa1K,CAAA9O,UAAA,CAAe5a,CAAf,CAA4Bm0B,CAA5B,CAA+CF,CAA/C,CAAb,CAAhB,CAGA;AAFAp0B,CAAAu0B,IAEA,CAFSA,CAET,CADA94B,CACA,CADQ24B,CACR,CADmBI,CACnB,CAAAH,CAAA,CAAmB,CAAA,CANrB,GASG54B,CACD,EADUrB,CACV,EADqBiI,CAAApH,KAAA,CAAW4uB,CAAA9O,UAAA,CAAetf,CAAf,CAAX,CACrB,CAAAA,CAAA,CAAQrB,CAVV,CAcF,EAAMA,CAAN,CAAeiI,CAAAjI,OAAf,IAEEiI,CAAApH,KAAA,CAAW,EAAX,CACA,CAAAb,CAAA,CAAS,CAHX,CAYA,IAAI+5B,CAAJ,EAAqC,CAArC,CAAsB9xB,CAAAjI,OAAtB,CACI,KAAMq6B,GAAA,CAAmB,UAAnB,CAGsD5K,CAHtD,CAAN,CAMJ,GAAI,CAACqK,CAAL,EAA4BG,CAA5B,CA8BE,MA7BAh0B,EAAAjG,OA6BO4F,CA7BS5F,CA6BT4F,CA5BPA,CA4BOA,CA5BFA,QAAQ,CAACtF,CAAD,CAAU,CACrB,GAAI,CACF,IADE,IACMU,EAAI,CADV,CACa0V,EAAK1W,CADlB,CAC0Bs6B,CAA5B,CAAkCt5B,CAAlC,CAAoC0V,CAApC,CAAwC1V,CAAA,EAAxC,CACkC,UAahC,EAbI,OAAQs5B,CAAR,CAAeryB,CAAA,CAAMjH,CAAN,CAAf,CAaJ,GAZEs5B,CAMA,CANOA,CAAA,CAAKh6B,CAAL,CAMP,CAJEg6B,CAIF,CALIP,CAAJ,CACStV,CAAA8V,WAAA,CAAgBR,CAAhB,CAAgCO,CAAhC,CADT,CAGS7V,CAAA+V,QAAA,CAAaF,CAAb,CAET,CAAa,IAAb,GAAIA,CAAJ,EAAqBz3B,CAAA,CAAYy3B,CAAZ,CAArB,CACEA,CADF,CACS,EADT,CAE0B,QAF1B,EAEW,MAAOA,EAFlB,GAGEA,CAHF,CAGSl0B,EAAA,CAAOk0B,CAAP,CAHT,CAMF,EAAAr0B,CAAA,CAAOjF,CAAP,CAAA,CAAYs5B,CAEd,OAAOr0B,EAAAxE,KAAA,CAAY,EAAZ,CAjBL,CAmBJ,MAAMiZ,CAAN,CAAW,CACL+f,CAEJ,CAFaJ,EAAA,CAAmB,QAAnB,CAA4D5K,CAA5D,CACT/U,CAAAxX,SAAA,EADS,CAEb,CAAAugB,CAAA,CAAkBgX,CAAlB,CAHS,CApBU,CA4BhB70B,CAFPA,CAAAu0B,IAEOv0B,CAFE6pB,CAEF7pB,CADPA,CAAAqC,MACOrC,CADIqC,CACJrC,CAAAA,CA3EqD,CA1C4B,IACxFs0B,EAAoBpI,CAAA9xB,OADoE,CAExFo6B,EAAkBrI,CAAA/xB,OAmItBokB,EAAA0N,YAAA,CAA2B4I,QAAQ,EAAG,CACpC,MAAO5I,EAD6B,CAgBtC1N,EAAA2N,UAAA,CAAyB4I,QAAQ,EAAG,CAClC,MAAO5I,EAD2B,CAIpC;MAAO3N,EAzJqF,CAAlF,CAzCkB,CAsMhC/T,QAASA,GAAiB,EAAG,CAC3B,IAAAmJ,KAAA,CAAY,CAAC,YAAD,CAAe,SAAf,CAA0B,IAA1B,CACP,QAAQ,CAAC4C,CAAD,CAAeF,CAAf,CAA0B8X,CAA1B,CAA8B,CA+HzCrW,QAASA,EAAQ,CAAC/X,CAAD,CAAKkb,CAAL,CAAY8Z,CAAZ,CAAmBC,CAAnB,CAAgC,CAAA,IAC3Cv3B,EAAc4Y,CAAA5Y,YAD6B,CAE3Cw3B,EAAgB5e,CAAA4e,cAF2B,CAG3ClE,EAAW5C,CAAApT,MAAA,EAHgC,CAI3CgV,EAAUgB,CAAAhB,QAJiC,CAK3CmF,EAAY,CAL+B,CAM3CC,EAAal4B,CAAA,CAAU+3B,CAAV,CAAbG,EAAuC,CAACH,CAE5CD,EAAA,CAAQ93B,CAAA,CAAU83B,CAAV,CAAA,CAAmBA,CAAnB,CAA2B,CAEnChF,EAAAD,KAAA,CAAa,IAAb,CAAmB,IAAnB,CAAyB/vB,CAAzB,CAEAgwB,EAAAqF,aAAA,CAAuB33B,CAAA,CAAY43B,QAAa,EAAG,CACjDtE,CAAAuE,OAAA,CAAgBJ,CAAA,EAAhB,CAEY,EAAZ,CAAIH,CAAJ,EAAiBG,CAAjB,EAA8BH,CAA9B,GACEhE,CAAAC,QAAA,CAAiBkE,CAAjB,CAEA,CADAD,CAAA,CAAclF,CAAAqF,aAAd,CACA,CAAA,OAAOG,CAAA,CAAUxF,CAAAqF,aAAV,CAHT,CAMKD,EAAL,EAAgB5e,CAAAtS,OAAA,EATiC,CAA5B,CAWpBgX,CAXoB,CAavBsa,EAAA,CAAUxF,CAAAqF,aAAV,CAAA,CAAkCrE,CAElC,OAAOhB,EA3BwC,CA9HjD,IAAIwF,EAAY,EAuKhBzd,EAAAqD,OAAA,CAAkBqa,QAAQ,CAACzF,CAAD,CAAU,CAClC,MAAIA,EAAJ,EAAeA,CAAAqF,aAAf,GAAuCG,EAAvC,EACEA,CAAA,CAAUxF,CAAAqF,aAAV,CAAA5G,OAAA,CAAuC,UAAvC,CAGO,CAFPyG,aAAA,CAAclF,CAAAqF,aAAd,CAEO,CADP,OAAOG,CAAA,CAAUxF,CAAAqF,aAAV,CACA;AAAA,CAAA,CAJT,EAMO,CAAA,CAP2B,CAUpC,OAAOtd,EAlLkC,CAD/B,CADe,CAkM7B1Q,QAASA,GAAe,EAAE,CACxB,IAAAuM,KAAA,CAAY4H,QAAQ,EAAG,CACrB,MAAO,IACD,OADC,gBAGW,aACD,GADC,WAEH,GAFG,UAGJ,CACR,QACU,CADV,SAEW,CAFX,SAGW,CAHX,QAIU,EAJV,QAKU,EALV,QAMU,GANV,QAOU,EAPV,OAQS,CART,QASU,CATV,CADQ,CAWN,QACQ,CADR,SAES,CAFT,SAGS,CAHT,QAIQ,QAJR,QAKQ,EALR,QAMQ,SANR,QAOQ,GAPR,OAQO,CARP,QASQ,CATR,CAXM,CAHI,cA0BA,GA1BA,CAHX,kBAgCa,OAEZ,uFAAA,MAAA,CAAA,GAAA,CAFY,YAIH,iDAAA,MAAA,CAAA,GAAA,CAJG;IAKX,0DAAA,MAAA,CAAA,GAAA,CALW,UAMN,6BAAA,MAAA,CAAA,GAAA,CANM,OAOT,CAAC,IAAD,CAAM,IAAN,CAPS,QAQR,oBARQ,CAShBka,OATgB,CAST,eATS,UAUN,iBAVM,UAWN,WAXM,YAYJ,UAZI,WAaL,QAbK,YAcJ,WAdI,WAeL,QAfK,CAhCb,WAkDMC,QAAQ,CAACC,CAAD,CAAM,CACvB,MAAY,EAAZ,GAAIA,CAAJ,CACS,KADT,CAGO,OAJgB,CAlDpB,CADc,CADC,CAyE1BC,QAASA,GAAU,CAACrwB,CAAD,CAAO,CACpBswB,CAAAA,CAAWtwB,CAAArD,MAAA,CAAW,GAAX,CAGf,KAHA,IACI/G,EAAI06B,CAAA17B,OAER,CAAOgB,CAAA,EAAP,CAAA,CACE06B,CAAA,CAAS16B,CAAT,CAAA,CAAcoH,EAAA,CAAiBszB,CAAA,CAAS16B,CAAT,CAAjB,CAGhB,OAAO06B,EAAAj6B,KAAA,CAAc,GAAd,CARiB,CAW1Bk6B,QAASA,GAAgB,CAACC,CAAD,CAAcC,CAAd,CAA2BC,CAA3B,CAAoC,CACvDC,CAAAA,CAAY9C,EAAA,CAAW2C,CAAX,CAAwBE,CAAxB,CAEhBD,EAAAG,WAAA;AAAyBD,CAAA7C,SACzB2C,EAAAI,OAAA,CAAqBF,CAAAG,SACrBL,EAAAM,OAAA,CAAqBh6B,CAAA,CAAI45B,CAAAK,KAAJ,CAArB,EAA4CC,EAAA,CAAcN,CAAA7C,SAAd,CAA5C,EAAiF,IALtB,CAS7DoD,QAASA,GAAW,CAACC,CAAD,CAAcV,CAAd,CAA2BC,CAA3B,CAAoC,CACtD,IAAIU,EAAsC,GAAtCA,GAAYD,CAAAx3B,OAAA,CAAmB,CAAnB,CACZy3B,EAAJ,GACED,CADF,CACgB,GADhB,CACsBA,CADtB,CAGI/0B,EAAAA,CAAQyxB,EAAA,CAAWsD,CAAX,CAAwBT,CAAxB,CACZD,EAAAY,OAAA,CAAqB90B,kBAAA,CAAmB60B,CAAA,EAAyC,GAAzC,GAAYh1B,CAAAk1B,SAAA33B,OAAA,CAAsB,CAAtB,CAAZ,CACpCyC,CAAAk1B,SAAA/b,UAAA,CAAyB,CAAzB,CADoC,CACNnZ,CAAAk1B,SADb,CAErBb,EAAAc,SAAA,CAAuB/0B,EAAA,CAAcJ,CAAAo1B,OAAd,CACvBf,EAAAgB,OAAA,CAAqBl1B,kBAAA,CAAmBH,CAAAgV,KAAnB,CAGjBqf,EAAAY,OAAJ,EAA0D,GAA1D,EAA0BZ,CAAAY,OAAA13B,OAAA,CAA0B,CAA1B,CAA1B,GACE82B,CAAAY,OADF,CACuB,GADvB,CAC6BZ,CAAAY,OAD7B,CAZsD,CAyBxDK,QAASA,GAAU,CAACC,CAAD,CAAQC,CAAR,CAAe,CAChC,GAA6B,CAA7B,GAAIA,CAAAh5B,QAAA,CAAc+4B,CAAd,CAAJ,CACE,MAAOC,EAAA7U,OAAA,CAAa4U,CAAA/8B,OAAb,CAFuB,CAOlCi9B,QAASA,GAAS,CAAC7e,CAAD,CAAM,CACtB,IAAI/c,EAAQ+c,CAAApa,QAAA,CAAY,GAAZ,CACZ,OAAiB,EAAV,EAAA3C,CAAA,CAAc+c,CAAd,CAAoBA,CAAA+J,OAAA,CAAW,CAAX,CAAc9mB,CAAd,CAFL,CAMxB67B,QAASA,GAAS,CAAC9e,CAAD,CAAM,CACtB,MAAOA,EAAA+J,OAAA,CAAW,CAAX;AAAc8U,EAAA,CAAU7e,CAAV,CAAA+e,YAAA,CAA2B,GAA3B,CAAd,CAAgD,CAAhD,CADe,CAkBxBC,QAASA,GAAgB,CAACtB,CAAD,CAAUuB,CAAV,CAAsB,CAC7C,IAAAC,QAAA,CAAe,CAAA,CACfD,EAAA,CAAaA,CAAb,EAA2B,EAC3B,KAAIE,EAAgBL,EAAA,CAAUpB,CAAV,CACpBH,GAAA,CAAiBG,CAAjB,CAA0B,IAA1B,CAAgCA,CAAhC,CAQA,KAAA0B,QAAA,CAAeC,QAAQ,CAACrf,CAAD,CAAM,CAC3B,IAAIsf,EAAUZ,EAAA,CAAWS,CAAX,CAA0Bnf,CAA1B,CACd,IAAI,CAACle,CAAA,CAASw9B,CAAT,CAAL,CACE,KAAMC,GAAA,CAAgB,UAAhB,CAA6Evf,CAA7E,CACFmf,CADE,CAAN,CAIFjB,EAAA,CAAYoB,CAAZ,CAAqB,IAArB,CAA2B5B,CAA3B,CAEK,KAAAW,OAAL,GACE,IAAAA,OADF,CACgB,GADhB,CAIA,KAAAmB,UAAA,EAb2B,CAoB7B,KAAAA,UAAA,CAAiBC,QAAQ,EAAG,CAAA,IACtBjB,EAAS50B,EAAA,CAAW,IAAA20B,SAAX,CADa,CAEtBngB,EAAO,IAAAqgB,OAAA,CAAc,GAAd,CAAoBz0B,EAAA,CAAiB,IAAAy0B,OAAjB,CAApB,CAAoD,EAE/D,KAAAiB,MAAA,CAAarC,EAAA,CAAW,IAAAgB,OAAX,CAAb,EAAwCG,CAAA,CAAS,GAAT,CAAeA,CAAf,CAAwB,EAAhE,EAAsEpgB,CACtE,KAAAuhB,SAAA,CAAgBR,CAAhB,CAAgC,IAAAO,MAAA3V,OAAA,CAAkB,CAAlB,CALN,CAQ5B,KAAA6V,UAAA,CAAiBC,QAAQ,CAAC7f,CAAD,CAAM,CAAA,IACzB8f,CAEJ,KAAMA,CAAN,CAAepB,EAAA,CAAWhB,CAAX,CAAoB1d,CAApB,CAAf,IAA6Cze,CAA7C,CAEE,MADAw+B,EACA,CADaD,CACb,CAAA,CAAMA,CAAN,CAAepB,EAAA,CAAWO,CAAX,CAAuBa,CAAvB,CAAf,IAAmDv+B,CAAnD,CACS49B,CADT,EAC0BT,EAAA,CAAW,GAAX,CAAgBoB,CAAhB,CAD1B,EACqDA,CADrD,EAGSpC,CAHT,CAGmBqC,CAEd,KAAMD,CAAN,CAAepB,EAAA,CAAWS,CAAX;AAA0Bnf,CAA1B,CAAf,IAAmDze,CAAnD,CACL,MAAO49B,EAAP,CAAuBW,CAClB,IAAIX,CAAJ,EAAqBnf,CAArB,CAA2B,GAA3B,CACL,MAAOmf,EAboB,CAxCc,CAoE/Ca,QAASA,GAAmB,CAACtC,CAAD,CAAUuC,CAAV,CAAsB,CAChD,IAAId,EAAgBL,EAAA,CAAUpB,CAAV,CAEpBH,GAAA,CAAiBG,CAAjB,CAA0B,IAA1B,CAAgCA,CAAhC,CAQA,KAAA0B,QAAA,CAAeC,QAAQ,CAACrf,CAAD,CAAM,CAC3B,IAAIkgB,EAAiBxB,EAAA,CAAWhB,CAAX,CAAoB1d,CAApB,CAAjBkgB,EAA6CxB,EAAA,CAAWS,CAAX,CAA0Bnf,CAA1B,CAAjD,CACImgB,EAA6C,GAC5B,EADAD,CAAAv5B,OAAA,CAAsB,CAAtB,CACA,CAAf+3B,EAAA,CAAWuB,CAAX,CAAuBC,CAAvB,CAAe,CACd,IAAAhB,QACD,CAAEgB,CAAF,CACE,EAER,IAAI,CAACp+B,CAAA,CAASq+B,CAAT,CAAL,CACE,KAAMZ,GAAA,CAAgB,UAAhB,CAA6Evf,CAA7E,CACFigB,CADE,CAAN,CAGF/B,EAAA,CAAYiC,CAAZ,CAA4B,IAA5B,CAAkCzC,CAAlC,CAEqCW,EAAAA,CAAAA,IAAAA,OAoBnC,KAAI+B,EAAqB,gBAKC,EAA1B,GAAIpgB,CAAApa,QAAA,CAzB4D83B,CAyB5D,CAAJ,GACE1d,CADF,CACQA,CAAA3W,QAAA,CA1BwDq0B,CA0BxD,CAAkB,EAAlB,CADR,CAQI0C,EAAAv1B,KAAA,CAAwBmV,CAAxB,CAAJ,GAKA,CALA,CAKO,CADPqgB,CACO,CADiBD,CAAAv1B,KAAA,CAAwBmC,CAAxB,CACjB,EAAwBqzB,CAAA,CAAsB,CAAtB,CAAxB,CAAmDrzB,CAL1D,CAjCF,KAAAqxB,OAAA,CAAc,CAEd,KAAAmB,UAAA,EAhB2B,CA4D7B,KAAAA,UAAA,CAAiBC,QAAQ,EAAG,CAAA,IACtBjB,EAAS50B,EAAA,CAAW,IAAA20B,SAAX,CADa,CAEtBngB,EAAO,IAAAqgB,OAAA,CAAc,GAAd,CAAoBz0B,EAAA,CAAiB,IAAAy0B,OAAjB,CAApB,CAAoD,EAE/D,KAAAiB,MAAA,CAAarC,EAAA,CAAW,IAAAgB,OAAX,CAAb,EAAwCG,CAAA,CAAS,GAAT,CAAeA,CAAf,CAAwB,EAAhE,EAAsEpgB,CACtE,KAAAuhB,SAAA;AAAgBjC,CAAhB,EAA2B,IAAAgC,MAAA,CAAaO,CAAb,CAA0B,IAAAP,MAA1B,CAAuC,EAAlE,CAL0B,CAQ5B,KAAAE,UAAA,CAAiBC,QAAQ,CAAC7f,CAAD,CAAM,CAC7B,GAAG6e,EAAA,CAAUnB,CAAV,CAAH,EAAyBmB,EAAA,CAAU7e,CAAV,CAAzB,CACE,MAAOA,EAFoB,CA/EiB,CAgGlDsgB,QAASA,GAA0B,CAAC5C,CAAD,CAAUuC,CAAV,CAAsB,CACvD,IAAAf,QAAA,CAAe,CAAA,CACfc,GAAAp4B,MAAA,CAA0B,IAA1B,CAAgC9D,SAAhC,CAEA,KAAIq7B,EAAgBL,EAAA,CAAUpB,CAAV,CAEpB,KAAAkC,UAAA,CAAiBC,QAAQ,CAAC7f,CAAD,CAAM,CAC7B,IAAI8f,CAEJ,IAAKpC,CAAL,EAAgBmB,EAAA,CAAU7e,CAAV,CAAhB,CACE,MAAOA,EACF,IAAM8f,CAAN,CAAepB,EAAA,CAAWS,CAAX,CAA0Bnf,CAA1B,CAAf,CACL,MAAO0d,EAAP,CAAiBuC,CAAjB,CAA8BH,CACzB,IAAKX,CAAL,GAAuBnf,CAAvB,CAA6B,GAA7B,CACL,MAAOmf,EARoB,CANwB,CAsNzDoB,QAASA,GAAc,CAACC,CAAD,CAAW,CAChC,MAAO,SAAQ,EAAG,CAChB,MAAO,KAAA,CAAKA,CAAL,CADS,CADc,CAOlCC,QAASA,GAAoB,CAACD,CAAD,CAAWE,CAAX,CAAuB,CAClD,MAAO,SAAQ,CAAC39B,CAAD,CAAQ,CACrB,GAAI0B,CAAA,CAAY1B,CAAZ,CAAJ,CACE,MAAO,KAAA,CAAKy9B,CAAL,CAET,KAAA,CAAKA,CAAL,CAAA,CAAiBE,CAAA,CAAW39B,CAAX,CACjB,KAAAy8B,UAAA,EAEA,OAAO,KAPc,CAD2B,CA6CpDptB,QAASA,GAAiB,EAAE,CAAA,IACtB6tB,EAAa,EADS,CAEtBU,EAAY,CAAA,CAShB,KAAAV,WAAA,CAAkBW,QAAQ,CAACC,CAAD,CAAS,CACjC,MAAIn8B,EAAA,CAAUm8B,CAAV,CAAJ,EACEZ,CACO,CADMY,CACN,CAAA,IAFT,EAISZ,CALwB,CAgBnC,KAAAU,UAAA;AAAiBG,QAAQ,CAACrU,CAAD,CAAO,CAC9B,MAAI/nB,EAAA,CAAU+nB,CAAV,CAAJ,EACEkU,CACO,CADKlU,CACL,CAAA,IAFT,EAISkU,CALqB,CAoChC,KAAAvlB,KAAA,CAAY,CAAC,YAAD,CAAe,UAAf,CAA2B,UAA3B,CAAuC,cAAvC,CACR,QAAQ,CAAE4C,CAAF,CAAgB2X,CAAhB,CAA4B3W,CAA5B,CAAwC0I,CAAxC,CAAsD,CAuGhEqZ,QAASA,EAAmB,CAACC,CAAD,CAAS,CACnChjB,CAAAijB,WAAA,CAAsB,wBAAtB,CAAgDljB,CAAAmjB,OAAA,EAAhD,CAAoEF,CAApE,CADmC,CAvG2B,IAC5DjjB,CAD4D,CAG5D2D,EAAWiU,CAAAjU,SAAA,EAHiD,CAI5Dyf,EAAaxL,CAAA3V,IAAA,EAGb2gB,EAAJ,EACEjD,CACA,CADqByD,CAlgBlB5e,UAAA,CAAc,CAAd,CAkgBkB4e,CAlgBDv7B,QAAA,CAAY,GAAZ,CAkgBCu7B,CAlgBgBv7B,QAAA,CAAY,IAAZ,CAAjB,CAAqC,CAArC,CAAjB,CAmgBH,EADoC8b,CACpC,EADgD,GAChD,EAAA0f,CAAA,CAAepiB,CAAAoB,QAAA,CAAmB4e,EAAnB,CAAsCsB,EAFvD,GAIE5C,CACA,CADUmB,EAAA,CAAUsC,CAAV,CACV,CAAAC,CAAA,CAAepB,EALjB,CAOAjiB,EAAA,CAAY,IAAIqjB,CAAJ,CAAiB1D,CAAjB,CAA0B,GAA1B,CAAgCuC,CAAhC,CACZliB,EAAAqhB,QAAA,CAAkBrhB,CAAA6hB,UAAA,CAAoBuB,CAApB,CAAlB,CAEAzZ,EAAAlG,GAAA,CAAgB,OAAhB,CAAyB,QAAQ,CAACzI,CAAD,CAAQ,CAIvC,GAAIsoB,CAAAtoB,CAAAsoB,QAAJ,EAAqBC,CAAAvoB,CAAAuoB,QAArB,EAAqD,CAArD,EAAsCvoB,CAAAwoB,MAAtC,CAAA,CAKA,IAHA,IAAIljB,EAAMzV,CAAA,CAAOmQ,CAAAO,OAAP,CAGV,CAAsC,GAAtC,GAAO7Q,CAAA,CAAU4V,CAAA,CAAI,CAAJ,CAAAhZ,SAAV,CAAP,CAAA,CAEE,GAAIgZ,CAAA,CAAI,CAAJ,CAAJ,GAAeqJ,CAAA,CAAa,CAAb,CAAf,EAAkC,CAAC,CAACrJ,CAAD,CAAOA,CAAAla,OAAA,EAAP,EAAqB,CAArB,CAAnC,CAA4D,MAG9D;IAAIq9B,EAAUnjB,CAAA/Y,KAAA,CAAS,MAAT,CAEVX,EAAA,CAAS68B,CAAT,CAAJ,EAAgD,4BAAhD,GAAyBA,CAAA18B,SAAA,EAAzB,GAGE08B,CAHF,CAGY3G,EAAA,CAAW2G,CAAAC,QAAX,CAAAzgB,KAHZ,CAMA,KAAI0gB,EAAe3jB,CAAA6hB,UAAA,CAAoB4B,CAApB,CAEfA,EAAJ,GAAgB,CAAAnjB,CAAA9Y,KAAA,CAAS,QAAT,CAAhB,EAAsCm8B,CAAtC,EAAuD,CAAA3oB,CAAAW,mBAAA,EAAvD,IACEX,CAAAC,eAAA,EACA,CAAI0oB,CAAJ,EAAoB/L,CAAA3V,IAAA,EAApB,GAEEjC,CAAAqhB,QAAA,CAAkBsC,CAAlB,CAGA,CAFA1jB,CAAAtS,OAAA,EAEA,CAAArK,CAAAyK,QAAA,CAAe,0BAAf,CAAA,CAA6C,CAAA,CAL/C,CAFF,CApBA,CAJuC,CAAzC,CAsCIiS,EAAAmjB,OAAA,EAAJ,EAA0BC,CAA1B,EACExL,CAAA3V,IAAA,CAAajC,CAAAmjB,OAAA,EAAb,CAAiC,CAAA,CAAjC,CAIFvL,EAAArU,YAAA,CAAqB,QAAQ,CAACqgB,CAAD,CAAS,CAChC5jB,CAAAmjB,OAAA,EAAJ,EAA0BS,CAA1B,GACE3jB,CAAA7X,WAAA,CAAsB,QAAQ,EAAG,CAC/B,IAAI66B,EAASjjB,CAAAmjB,OAAA,EAEbnjB,EAAAqhB,QAAA,CAAkBuC,CAAlB,CACI3jB,EAAAijB,WAAA,CAAsB,sBAAtB,CAA8CU,CAA9C,CACsBX,CADtB,CAAAxnB,iBAAJ,EAEEuE,CAAAqhB,QAAA,CAAkB4B,CAAlB,CACA,CAAArL,CAAA3V,IAAA,CAAaghB,CAAb,CAHF,EAKED,CAAA,CAAoBC,CAApB,CAT6B,CAAjC,CAYA,CAAKhjB,CAAAua,QAAL;AAAyBva,CAAA4jB,QAAA,EAb3B,CADoC,CAAtC,CAmBA,KAAIC,EAAgB,CACpB7jB,EAAA5X,OAAA,CAAkB07B,QAAuB,EAAG,CAC1C,IAAId,EAASrL,CAAA3V,IAAA,EAAb,CACI+hB,EAAiBhkB,CAAAikB,UAEhBH,EAAL,EAAsBb,CAAtB,EAAgCjjB,CAAAmjB,OAAA,EAAhC,GACEW,CAAA,EACA,CAAA7jB,CAAA7X,WAAA,CAAsB,QAAQ,EAAG,CAC3B6X,CAAAijB,WAAA,CAAsB,sBAAtB,CAA8CljB,CAAAmjB,OAAA,EAA9C,CAAkEF,CAAlE,CAAAxnB,iBAAJ,CAEEuE,CAAAqhB,QAAA,CAAkB4B,CAAlB,CAFF,EAIErL,CAAA3V,IAAA,CAAajC,CAAAmjB,OAAA,EAAb,CAAiCa,CAAjC,CACA,CAAAhB,CAAA,CAAoBC,CAApB,CALF,CAD+B,CAAjC,CAFF,CAYAjjB,EAAAikB,UAAA,CAAsB,CAAA,CAEtB,OAAOH,EAlBmC,CAA5C,CAqBA,OAAO9jB,EArGyD,CADtD,CA/Dc,CAuN5B1L,QAASA,GAAY,EAAE,CAAA,IACjB4vB,EAAQ,CAAA,CADS,CAEjB16B,EAAO,IASX,KAAA26B,aAAA,CAAoBC,QAAQ,CAACC,CAAD,CAAO,CACjC,MAAI19B,EAAA,CAAU09B,CAAV,CAAJ,EACEH,CACK,CADGG,CACH,CAAA,IAFP,EAISH,CALwB,CASnC,KAAA7mB,KAAA,CAAY,CAAC,SAAD,CAAY,QAAQ,CAAC0C,CAAD,CAAS,CAwDvCukB,QAASA,EAAW,CAAC51B,CAAD,CAAM,CACpBA,CAAJ,WAAmB61B,MAAnB,GACM71B,CAAAuP,MAAJ,CACEvP,CADF,CACSA,CAAAsP,QACD,EADoD,EACpD,GADgBtP,CAAAuP,MAAApW,QAAA,CAAkB6G,CAAAsP,QAAlB,CAChB,CAAA,SAAA,CAAYtP,CAAAsP,QAAZ,CAA0B,IAA1B,CAAiCtP,CAAAuP,MAAjC;AACAvP,CAAAuP,MAHR,CAIWvP,CAAA81B,UAJX,GAKE91B,CALF,CAKQA,CAAAsP,QALR,CAKsB,IALtB,CAK6BtP,CAAA81B,UAL7B,CAK6C,GAL7C,CAKmD91B,CAAAkoB,KALnD,CADF,CASA,OAAOloB,EAViB,CAa1B+1B,QAASA,EAAU,CAAC/rB,CAAD,CAAO,CAAA,IACpBgsB,EAAU3kB,CAAA2kB,QAAVA,EAA6B,EADT,CAEpBC,EAAQD,CAAA,CAAQhsB,CAAR,CAARisB,EAAyBD,CAAAE,IAAzBD,EAAwCr+B,CACxCu+B,EAAAA,CAAW,CAAA,CAIf,IAAI,CACFA,CAAA,CAAW,CAAC,CAACF,CAAA96B,MADX,CAEF,MAAOmB,CAAP,CAAU,EAEZ,MAAI65B,EAAJ,CACS,QAAQ,EAAG,CAChB,IAAIpmB,EAAO,EACXxa,EAAA,CAAQ8B,SAAR,CAAmB,QAAQ,CAAC2I,CAAD,CAAM,CAC/B+P,CAAA/Z,KAAA,CAAU4/B,CAAA,CAAY51B,CAAZ,CAAV,CAD+B,CAAjC,CAGA,OAAOi2B,EAAA96B,MAAA,CAAY66B,CAAZ,CAAqBjmB,CAArB,CALS,CADpB,CAYO,QAAQ,CAACqmB,CAAD,CAAOC,CAAP,CAAa,CAC1BJ,CAAA,CAAMG,CAAN,CAAoB,IAAR,EAAAC,CAAA,CAAe,EAAf,CAAoBA,CAAhC,CAD0B,CAvBJ,CApE1B,MAAO,KAQAN,CAAA,CAAW,KAAX,CARA,MAiBCA,CAAA,CAAW,MAAX,CAjBD,MA0BCA,CAAA,CAAW,MAAX,CA1BD,OAmCEA,CAAA,CAAW,OAAX,CAnCF,OA4CG,QAAS,EAAG,CAClB,IAAIh7B,EAAKg7B,CAAA,CAAW,OAAX,CAET,OAAO,SAAQ,EAAG,CACZP,CAAJ,EACEz6B,CAAAI,MAAA,CAASL,CAAT,CAAezD,SAAf,CAFc,CAHA,CAAZ,EA5CH,CADgC,CAA7B,CApBS,CAwJvBi/B,QAASA,GAAoB,CAACr4B,CAAD,CAAOs4B,CAAP,CAAuB,CAClD,GAAa,aAAb,GAAIt4B,CAAJ,CACE,KAAMu4B,GAAA,CAAa,SAAb,CAEFD,CAFE,CAAN,CAIF,MAAOt4B,EAN2C,CASpDw4B,QAASA,GAAgB,CAACxhC,CAAD;AAAMshC,CAAN,CAAsB,CAE7C,GAAIthC,CAAJ,CAAS,CACP,GAAIA,CAAAmL,YAAJ,GAAwBnL,CAAxB,CACE,KAAMuhC,GAAA,CAAa,QAAb,CAEFD,CAFE,CAAN,CAGK,GACHthC,CAAAJ,SADG,EACaI,CAAAsD,SADb,EAC6BtD,CAAAuD,MAD7B,EAC0CvD,CAAAwD,YAD1C,CAEL,KAAM+9B,GAAA,CAAa,YAAb,CAEFD,CAFE,CAAN,CAGK,GACHthC,CAAAyS,SADG,GACczS,CAAA2D,SADd,EAC+B3D,CAAA4D,KAD/B,EAC2C5D,CAAA6D,KAD3C,EACuD7D,CAAA8D,KADvD,EAEL,KAAMy9B,GAAA,CAAa,SAAb,CAEFD,CAFE,CAAN,CAZK,CAiBT,MAAOthC,EAnBsC,CA4yB/CyhC,QAASA,GAAM,CAACzhC,CAAD,CAAMsL,CAAN,CAAYo2B,CAAZ,CAAsBC,CAAtB,CAA+BlgB,CAA/B,CAAwC,CAErDA,CAAA,CAAUA,CAAV,EAAqB,EAEjBxa,EAAAA,CAAUqE,CAAArD,MAAA,CAAW,GAAX,CACd,KADA,IAA+BxH,CAA/B,CACSS,EAAI,CAAb,CAAiC,CAAjC,CAAgB+F,CAAA/G,OAAhB,CAAoCgB,CAAA,EAApC,CAAyC,CACvCT,CAAA,CAAM4gC,EAAA,CAAqBp6B,CAAAyL,MAAA,EAArB,CAAsCivB,CAAtC,CACN,KAAIC,EAAc5hC,CAAA,CAAIS,CAAJ,CACbmhC,EAAL,GACEA,CACA,CADc,EACd,CAAA5hC,CAAA,CAAIS,CAAJ,CAAA,CAAWmhC,CAFb,CAIA5hC,EAAA,CAAM4hC,CACF5hC,EAAA61B,KAAJ,EAAgBpU,CAAAogB,eAAhB,GACEC,EAAA,CAAeH,CAAf,CASA,CARM,KAQN,EARe3hC,EAQf,EAPG,QAAQ,CAAC81B,CAAD,CAAU,CACjBA,CAAAD,KAAA,CAAa,QAAQ,CAACxvB,CAAD,CAAM,CAAEyvB,CAAAiM,IAAA,CAAc17B,CAAhB,CAA3B,CADiB,CAAlB,CAECrG,CAFD,CAOH,CAHIA,CAAA+hC,IAGJ,GAHgBliC,CAGhB,GAFEG,CAAA+hC,IAEF,CAFY,EAEZ,EAAA/hC,CAAA,CAAMA,CAAA+hC,IAVR,CARuC,CAqBzCthC,CAAA,CAAM4gC,EAAA,CAAqBp6B,CAAAyL,MAAA,EAArB,CAAsCivB,CAAtC,CAEN,OADA3hC,EAAA,CAAIS,CAAJ,CACA,CADWihC,CA3B0C,CAsCvDM,QAASA,GAAe,CAACC,CAAD;AAAOC,CAAP,CAAaC,CAAb,CAAmBC,CAAnB,CAAyBC,CAAzB,CAA+BV,CAA/B,CAAwClgB,CAAxC,CAAiD,CACvE4f,EAAA,CAAqBY,CAArB,CAA2BN,CAA3B,CACAN,GAAA,CAAqBa,CAArB,CAA2BP,CAA3B,CACAN,GAAA,CAAqBc,CAArB,CAA2BR,CAA3B,CACAN,GAAA,CAAqBe,CAArB,CAA2BT,CAA3B,CACAN,GAAA,CAAqBgB,CAArB,CAA2BV,CAA3B,CAEA,OAAQlgB,EAAAogB,eACD,CAwBDS,QAAoC,CAACz4B,CAAD,CAAQgR,CAAR,CAAgB,CAAA,IAC9C0nB,EAAW1nB,CAAD,EAAWA,CAAAla,eAAA,CAAsBshC,CAAtB,CAAX,CAA0CpnB,CAA1C,CAAmDhR,CADf,CAE9CisB,CAEJ,IAAe,IAAf,EAAIyM,CAAJ,CAAqB,MAAOA,EAG5B,EADAA,CACA,CADUA,CAAA,CAAQN,CAAR,CACV,GAAeM,CAAA1M,KAAf,GACEiM,EAAA,CAAeH,CAAf,CAMA,CALM,KAKN,EALeY,EAKf,GAJEzM,CAEA,CAFUyM,CAEV,CADAzM,CAAAiM,IACA,CADcliC,CACd,CAAAi2B,CAAAD,KAAA,CAAa,QAAQ,CAACxvB,CAAD,CAAM,CAAEyvB,CAAAiM,IAAA,CAAc17B,CAAhB,CAA3B,CAEF,EAAAk8B,CAAA,CAAUA,CAAAR,IAPZ,CAUA,IAAI,CAACG,CAAL,CAAW,MAAOK,EAClB,IAAe,IAAf,EAAIA,CAAJ,CAAqB,MAAO1iC,EAE5B,EADA0iC,CACA,CADUA,CAAA,CAAQL,CAAR,CACV,GAAeK,CAAA1M,KAAf,GACEiM,EAAA,CAAeH,CAAf,CAMA,CALM,KAKN,EALeY,EAKf,GAJEzM,CAEA,CAFUyM,CAEV,CADAzM,CAAAiM,IACA,CADcliC,CACd,CAAAi2B,CAAAD,KAAA,CAAa,QAAQ,CAACxvB,CAAD,CAAM,CAAEyvB,CAAAiM,IAAA,CAAc17B,CAAhB,CAA3B,CAEF,EAAAk8B,CAAA,CAAUA,CAAAR,IAPZ,CAUA,IAAI,CAACI,CAAL,CAAW,MAAOI,EAClB,IAAe,IAAf,EAAIA,CAAJ,CAAqB,MAAO1iC,EAE5B,EADA0iC,CACA,CADUA,CAAA,CAAQJ,CAAR,CACV,GAAeI,CAAA1M,KAAf,GACEiM,EAAA,CAAeH,CAAf,CAMA,CALM,KAKN,EALeY,EAKf,GAJEzM,CAEA,CAFUyM,CAEV,CADAzM,CAAAiM,IACA,CADcliC,CACd,CAAAi2B,CAAAD,KAAA,CAAa,QAAQ,CAACxvB,CAAD,CAAM,CAAEyvB,CAAAiM,IAAA,CAAc17B,CAAhB,CAA3B,CAEF,EAAAk8B,CAAA,CAAUA,CAAAR,IAPZ,CAUA,IAAI,CAACK,CAAL,CAAW,MAAOG,EAClB,IAAe,IAAf;AAAIA,CAAJ,CAAqB,MAAO1iC,EAE5B,EADA0iC,CACA,CADUA,CAAA,CAAQH,CAAR,CACV,GAAeG,CAAA1M,KAAf,GACEiM,EAAA,CAAeH,CAAf,CAMA,CALM,KAKN,EALeY,EAKf,GAJEzM,CAEA,CAFUyM,CAEV,CADAzM,CAAAiM,IACA,CADcliC,CACd,CAAAi2B,CAAAD,KAAA,CAAa,QAAQ,CAACxvB,CAAD,CAAM,CAAEyvB,CAAAiM,IAAA,CAAc17B,CAAhB,CAA3B,CAEF,EAAAk8B,CAAA,CAAUA,CAAAR,IAPZ,CAUA,IAAI,CAACM,CAAL,CAAW,MAAOE,EAClB,IAAe,IAAf,EAAIA,CAAJ,CAAqB,MAAO1iC,EAE5B,EADA0iC,CACA,CADUA,CAAA,CAAQF,CAAR,CACV,GAAeE,CAAA1M,KAAf,GACEiM,EAAA,CAAeH,CAAf,CAMA,CALM,KAKN,EALeY,EAKf,GAJEzM,CAEA,CAFUyM,CAEV,CADAzM,CAAAiM,IACA,CADcliC,CACd,CAAAi2B,CAAAD,KAAA,CAAa,QAAQ,CAACxvB,CAAD,CAAM,CAAEyvB,CAAAiM,IAAA,CAAc17B,CAAhB,CAA3B,CAEF,EAAAk8B,CAAA,CAAUA,CAAAR,IAPZ,CASA,OAAOQ,EApE2C,CAxBnD,CAADC,QAAsB,CAAC34B,CAAD,CAAQgR,CAAR,CAAgB,CACpC,IAAI0nB,EAAW1nB,CAAD,EAAWA,CAAAla,eAAA,CAAsBshC,CAAtB,CAAX,CAA0CpnB,CAA1C,CAAmDhR,CAEjE,IAAe,IAAf,EAAI04B,CAAJ,CAAqB,MAAOA,EAC5BA,EAAA,CAAUA,CAAA,CAAQN,CAAR,CAEV,IAAI,CAACC,CAAL,CAAW,MAAOK,EAClB,IAAe,IAAf,EAAIA,CAAJ,CAAqB,MAAO1iC,EAC5B0iC,EAAA,CAAUA,CAAA,CAAQL,CAAR,CAEV,IAAI,CAACC,CAAL,CAAW,MAAOI,EAClB,IAAe,IAAf,EAAIA,CAAJ,CAAqB,MAAO1iC,EAC5B0iC,EAAA,CAAUA,CAAA,CAAQJ,CAAR,CAEV,IAAI,CAACC,CAAL,CAAW,MAAOG,EAClB,IAAe,IAAf,EAAIA,CAAJ,CAAqB,MAAO1iC,EAC5B0iC,EAAA,CAAUA,CAAA,CAAQH,CAAR,CAEV,OAAKC,EAAL,CACe,IAAf,EAAIE,CAAJ,CAA4B1iC,CAA5B,CACA0iC,CADA,CACUA,CAAA,CAAQF,CAAR,CAFV,CAAkBE,CAlBkB,CAR2B,CAwGzEE,QAASA,GAAe,CAACR,CAAD,CAAON,CAAP,CAAgB,CACtCN,EAAA,CAAqBY,CAArB,CAA2BN,CAA3B,CAEA,OAAOc,SAAwB,CAAC54B,CAAD;AAAQgR,CAAR,CAAgB,CAC7C,MAAa,KAAb,EAAIhR,CAAJ,CAA0BhK,CAA1B,CACO,CAAEgb,CAAD,EAAWA,CAAAla,eAAA,CAAsBshC,CAAtB,CAAX,CAA0CpnB,CAA1C,CAAmDhR,CAApD,EAA2Do4B,CAA3D,CAFsC,CAHT,CASxCS,QAASA,GAAe,CAACT,CAAD,CAAOC,CAAP,CAAaP,CAAb,CAAsB,CAC5CN,EAAA,CAAqBY,CAArB,CAA2BN,CAA3B,CACAN,GAAA,CAAqBa,CAArB,CAA2BP,CAA3B,CAEA,OAAOe,SAAwB,CAAC74B,CAAD,CAAQgR,CAAR,CAAgB,CAC7C,GAAa,IAAb,EAAIhR,CAAJ,CAAmB,MAAOhK,EAC1BgK,EAAA,CAAQ,CAAEgR,CAAD,EAAWA,CAAAla,eAAA,CAAsBshC,CAAtB,CAAX,CAA0CpnB,CAA1C,CAAmDhR,CAApD,EAA2Do4B,CAA3D,CACR,OAAgB,KAAT,EAAAp4B,CAAA,CAAgBhK,CAAhB,CAA4BgK,CAAA,CAAMq4B,CAAN,CAHU,CAJH,CAW9CS,QAASA,GAAQ,CAACr3B,CAAD,CAAOmW,CAAP,CAAgBkgB,CAAhB,CAAyB,CAIxC,GAAIiB,EAAAjiC,eAAA,CAA6B2K,CAA7B,CAAJ,CACE,MAAOs3B,GAAA,CAAct3B,CAAd,CAL+B,KAQpCu3B,EAAWv3B,CAAArD,MAAA,CAAW,GAAX,CARyB,CASpC66B,EAAiBD,CAAA3iC,OATmB,CAUpC4F,CAIJ,IAAK2b,CAAAogB,eAAL,EAAkD,CAAlD,GAA+BiB,CAA/B,CAEO,GAAKrhB,CAAAogB,eAAL,EAAkD,CAAlD,GAA+BiB,CAA/B,CAEA,GAAIrhB,CAAAjc,IAAJ,CAEHM,CAAA,CADmB,CAArB,CAAIg9B,CAAJ,CACOd,EAAA,CAAgBa,CAAA,CAAS,CAAT,CAAhB,CAA6BA,CAAA,CAAS,CAAT,CAA7B,CAA0CA,CAAA,CAAS,CAAT,CAA1C,CAAuDA,CAAA,CAAS,CAAT,CAAvD,CAAoEA,CAAA,CAAS,CAAT,CAApE,CAAiFlB,CAAjF,CACelgB,CADf,CADP,CAIO3b,QAAQ,CAAC+D,CAAD,CAAQgR,CAAR,CAAgB,CAAA,IACvB3Z,EAAI,CADmB,CAChBmF,CACX,GACEA,EAIA,CAJM27B,EAAA,CAAgBa,CAAA,CAAS3hC,CAAA,EAAT,CAAhB,CAA+B2hC,CAAA,CAAS3hC,CAAA,EAAT,CAA/B,CAA8C2hC,CAAA,CAAS3hC,CAAA,EAAT,CAA9C,CAA6D2hC,CAAA,CAAS3hC,CAAA,EAAT,CAA7D,CACgB2hC,CAAA,CAAS3hC,CAAA,EAAT,CADhB,CAC+BygC,CAD/B,CACwClgB,CADxC,CAAA,CACiD5X,CADjD,CACwDgR,CADxD,CAIN,CADAA,CACA,CADShb,CACT,CAAAgK,CAAA,CAAQxD,CALV,OAMSnF,CANT,CAMa4hC,CANb,CAOA,OAAOz8B,EAToB,CAL1B,KAiBA,CACL,IAAI8oB,EAAO,UACX7uB;CAAA,CAAQuiC,CAAR,CAAkB,QAAQ,CAACpiC,CAAD,CAAMc,CAAN,CAAa,CACrC8/B,EAAA,CAAqB5gC,CAArB,CAA0BkhC,CAA1B,CACAxS,EAAA,EAAQ,qCAAR,EACe5tB,CAEA,CAAG,GAAH,CAEG,yBAFH,CAE+Bd,CAF/B,CAEqC,UALpD,EAKkE,IALlE,CAKyEA,CALzE,CAKsF,OALtF,EAMSghB,CAAAogB,eACA,CAAG,2BAAH,CACaF,CAAAh6B,QAAA,CAAgB,YAAhB,CAA8B,MAA9B,CADb,CAQC,4GARD,CASG,EAhBZ,CAFqC,CAAvC,CAoBA,KAAAwnB,EAAAA,CAAAA,CAAQ,WAAR,CAGI4T,EAAiB,IAAIC,QAAJ,CAAa,GAAb,CAAkB,GAAlB,CAAuB,IAAvB,CAA6B7T,CAA7B,CAErB4T,EAAA3/B,SAAA,CAA0BN,EAAA,CAAQqsB,CAAR,CAC1BrpB,EAAA,CAAK2b,CAAAogB,eAAA,CAAyB,QAAQ,CAACh4B,CAAD,CAAQgR,CAAR,CAAgB,CACpD,MAAOkoB,EAAA,CAAel5B,CAAf,CAAsBgR,CAAtB,CAA8BinB,EAA9B,CAD6C,CAAjD,CAEDiB,CA9BC,CAnBA,IACLj9B,EAAA,CAAK48B,EAAA,CAAgBG,CAAA,CAAS,CAAT,CAAhB,CAA6BA,CAAA,CAAS,CAAT,CAA7B,CAA0ClB,CAA1C,CAHP,KACE77B,EAAA,CAAK28B,EAAA,CAAgBI,CAAA,CAAS,CAAT,CAAhB,CAA6BlB,CAA7B,CAuDM,iBAAb;AAAIr2B,CAAJ,GACEs3B,EAAA,CAAct3B,CAAd,CADF,CACwBxF,CADxB,CAGA,OAAOA,EAzEiC,CAgI1C8K,QAASA,GAAc,EAAG,CACxB,IAAI4J,EAAQ,EAAZ,CAEIyoB,EAAgB,KACb,CAAA,CADa,gBAEF,CAAA,CAFE,oBAGE,CAAA,CAHF,CAmDpB,KAAApB,eAAA,CAAsBqB,QAAQ,CAAC7hC,CAAD,CAAQ,CACpC,MAAI2B,EAAA,CAAU3B,CAAV,CAAJ,EACE4hC,CAAApB,eACO,CADwB,CAAC,CAACxgC,CAC1B,CAAA,IAFT,EAIS4hC,CAAApB,eAL2B,CA2BvC,KAAAsB,mBAAA,CAA0BC,QAAQ,CAAC/hC,CAAD,CAAQ,CACvC,MAAI2B,EAAA,CAAU3B,CAAV,CAAJ,EACE4hC,CAAAE,mBACO,CAD4B9hC,CAC5B,CAAA,IAFT,EAIS4hC,CAAAE,mBAL8B,CAUzC,KAAAzpB,KAAA,CAAY,CAAC,SAAD,CAAY,UAAZ,CAAwB,MAAxB,CAAgC,QAAQ,CAAC2pB,CAAD,CAAU/lB,CAAV,CAAoBD,CAApB,CAA0B,CAC5E4lB,CAAAz9B,IAAA,CAAoB8X,CAAA9X,IAEpBs8B,GAAA,CAAiBA,QAAyB,CAACH,CAAD,CAAU,CAC7CsB,CAAAE,mBAAL,EAAyC,CAAAG,EAAA3iC,eAAA,CAAmCghC,CAAnC,CAAzC,GACA2B,EAAA,CAAoB3B,CAApB,CACA,CAD+B,CAAA,CAC/B,CAAAtkB,CAAAqD,KAAA,CAAU,4CAAV,CAAyDihB,CAAzD,CACI,2EADJ,CAFA,CADkD,CAOpD;MAAO,SAAQ,CAACtH,CAAD,CAAM,CACnB,IAAIkJ,CAEJ,QAAQ,MAAOlJ,EAAf,EACE,KAAK,QAAL,CAEE,GAAI7f,CAAA7Z,eAAA,CAAqB05B,CAArB,CAAJ,CACE,MAAO7f,EAAA,CAAM6f,CAAN,CAGLmJ,EAAAA,CAAQ,IAAIC,EAAJ,CAAUR,CAAV,CAEZM,EAAA,CAAmB38B,CADN88B,IAAIC,EAAJD,CAAWF,CAAXE,CAAkBL,CAAlBK,CAA2BT,CAA3BS,CACM98B,OAAA,CAAayzB,CAAb,CAAkB,CAAA,CAAlB,CAEP,iBAAZ,GAAIA,CAAJ,GAGE7f,CAAA,CAAM6f,CAAN,CAHF,CAGekJ,CAHf,CAMA,OAAOA,EAET,MAAK,UAAL,CACE,MAAOlJ,EAET,SACE,MAAO13B,EAvBX,CAHmB,CAVuD,CAAlE,CA3FY,CA6S1BmO,QAASA,GAAU,EAAG,CAEpB,IAAA4I,KAAA,CAAY,CAAC,YAAD,CAAe,mBAAf,CAAoC,QAAQ,CAAC4C,CAAD,CAAaqH,CAAb,CAAgC,CACtF,MAAOigB,GAAA,CAAS,QAAQ,CAACzkB,CAAD,CAAW,CACjC7C,CAAA7X,WAAA,CAAsB0a,CAAtB,CADiC,CAA5B,CAEJwE,CAFI,CAD+E,CAA5E,CAFQ,CAkBtBigB,QAASA,GAAQ,CAACC,CAAD,CAAWC,CAAX,CAA6B,CAyR5CC,QAASA,EAAe,CAAC1iC,CAAD,CAAQ,CAC9B,MAAOA,EADuB,CAKhC2iC,QAASA,EAAc,CAACh5B,CAAD,CAAS,CAC9B,MAAOupB,EAAA,CAAOvpB,CAAP,CADuB,CAlRhC,IAAI8V,EAAQA,QAAQ,EAAG,CAAA,IACjBmjB,EAAU,EADO,CAEjB5iC,CAFiB,CAEVy1B,CA+HX,OA7HAA,EA6HA,CA7HW,SAEAC,QAAQ,CAAC1wB,CAAD,CAAM,CACrB,GAAI49B,CAAJ,CAAa,CACX,IAAIhM,EAAYgM,CAChBA,EAAA,CAAUpkC,CACVwB,EAAA,CAAQ6iC,CAAA,CAAI79B,CAAJ,CAEJ4xB,EAAA/3B,OAAJ,EACE2jC,CAAA,CAAS,QAAQ,EAAG,CAElB,IADA,IAAI1kB,CAAJ;AACSje,EAAI,CADb,CACgB0V,EAAKqhB,CAAA/3B,OAArB,CAAuCgB,CAAvC,CAA2C0V,CAA3C,CAA+C1V,CAAA,EAA/C,CACEie,CACA,CADW8Y,CAAA,CAAU/2B,CAAV,CACX,CAAAG,CAAAw0B,KAAA,CAAW1W,CAAA,CAAS,CAAT,CAAX,CAAwBA,CAAA,CAAS,CAAT,CAAxB,CAAqCA,CAAA,CAAS,CAAT,CAArC,CAJgB,CAApB,CANS,CADQ,CAFd,QAqBDoV,QAAQ,CAACvpB,CAAD,CAAS,CACvB8rB,CAAAC,QAAA,CAAiBoN,CAAA,CAA8Bn5B,CAA9B,CAAjB,CADuB,CArBhB,QA0BDqwB,QAAQ,CAAC+I,CAAD,CAAW,CACzB,GAAIH,CAAJ,CAAa,CACX,IAAIhM,EAAYgM,CAEZA,EAAA/jC,OAAJ,EACE2jC,CAAA,CAAS,QAAQ,EAAG,CAElB,IADA,IAAI1kB,CAAJ,CACSje,EAAI,CADb,CACgB0V,EAAKqhB,CAAA/3B,OAArB,CAAuCgB,CAAvC,CAA2C0V,CAA3C,CAA+C1V,CAAA,EAA/C,CACEie,CACA,CADW8Y,CAAA,CAAU/2B,CAAV,CACX,CAAAie,CAAA,CAAS,CAAT,CAAA,CAAYilB,CAAZ,CAJgB,CAApB,CAJS,CADY,CA1BlB,SA2CA,MACDvO,QAAQ,CAAC1W,CAAD,CAAWklB,CAAX,CAAoBC,CAApB,CAAkC,CAC9C,IAAI9nB,EAASsE,CAAA,EAAb,CAEIyjB,EAAkBA,QAAQ,CAACljC,CAAD,CAAQ,CACpC,GAAI,CACFmb,CAAAua,QAAA,CAAgB,CAAAr2B,CAAA,CAAWye,CAAX,CAAA,CAAuBA,CAAvB,CAAkC4kB,CAAlC,EAAmD1iC,CAAnD,CAAhB,CADE,CAEF,MAAMgG,CAAN,CAAS,CACTmV,CAAA+X,OAAA,CAAcltB,CAAd,CACA,CAAAy8B,CAAA,CAAiBz8B,CAAjB,CAFS,CAHyB,CAFtC,CAWIm9B,EAAiBA,QAAQ,CAACx5B,CAAD,CAAS,CACpC,GAAI,CACFwR,CAAAua,QAAA,CAAgB,CAAAr2B,CAAA,CAAW2jC,CAAX,CAAA,CAAsBA,CAAtB,CAAgCL,CAAhC,EAAgDh5B,CAAhD,CAAhB,CADE,CAEF,MAAM3D,CAAN,CAAS,CACTmV,CAAA+X,OAAA,CAAcltB,CAAd,CACA,CAAAy8B,CAAA,CAAiBz8B,CAAjB,CAFS,CAHyB,CAXtC,CAoBIo9B,EAAsBA,QAAQ,CAACL,CAAD,CAAW,CAC3C,GAAI,CACF5nB,CAAA6e,OAAA,CAAe,CAAA36B,CAAA,CAAW4jC,CAAX,CAAA,CAA2BA,CAA3B,CAA0CP,CAA1C,EAA2DK,CAA3D,CAAf,CADE,CAEF,MAAM/8B,CAAN,CAAS,CACTy8B,CAAA,CAAiBz8B,CAAjB,CADS,CAHgC,CAQzC48B,EAAJ,CACEA,CAAAljC,KAAA,CAAa,CAACwjC,CAAD,CAAkBC,CAAlB,CAAkCC,CAAlC,CAAb,CADF,CAGEpjC,CAAAw0B,KAAA,CAAW0O,CAAX,CAA4BC,CAA5B,CAA4CC,CAA5C,CAGF,OAAOjoB,EAAAsZ,QAnCuC,CADzC,CAuCP,OAvCO,CAuCE4O,QAAQ,CAACvlB,CAAD,CAAW,CAC1B,MAAO,KAAA0W,KAAA,CAAU,IAAV;AAAgB1W,CAAhB,CADmB,CAvCrB,CA2CP,SA3CO,CA2CIwlB,QAAQ,CAACxlB,CAAD,CAAW,CAE5BylB,QAASA,EAAW,CAACvjC,CAAD,CAAQwjC,CAAR,CAAkB,CACpC,IAAIroB,EAASsE,CAAA,EACT+jB,EAAJ,CACEroB,CAAAua,QAAA,CAAe11B,CAAf,CADF,CAGEmb,CAAA+X,OAAA,CAAclzB,CAAd,CAEF,OAAOmb,EAAAsZ,QAP6B,CAUtCgP,QAASA,EAAc,CAACzjC,CAAD,CAAQ0jC,CAAR,CAAoB,CACzC,IAAIC,EAAiB,IACrB,IAAI,CACFA,CAAA,CAAkB,CAAA7lB,CAAA,EAAW4kB,CAAX,GADhB,CAEF,MAAM18B,CAAN,CAAS,CACT,MAAOu9B,EAAA,CAAYv9B,CAAZ,CAAe,CAAA,CAAf,CADE,CAGX,MAAI29B,EAAJ,EAAsBtkC,CAAA,CAAWskC,CAAAnP,KAAX,CAAtB,CACSmP,CAAAnP,KAAA,CAAoB,QAAQ,EAAG,CACpC,MAAO+O,EAAA,CAAYvjC,CAAZ,CAAmB0jC,CAAnB,CAD6B,CAA/B,CAEJ,QAAQ,CAACpnB,CAAD,CAAQ,CACjB,MAAOinB,EAAA,CAAYjnB,CAAZ,CAAmB,CAAA,CAAnB,CADU,CAFZ,CADT,CAOSinB,CAAA,CAAYvjC,CAAZ,CAAmB0jC,CAAnB,CAdgC,CAkB3C,MAAO,KAAAlP,KAAA,CAAU,QAAQ,CAACx0B,CAAD,CAAQ,CAC/B,MAAOyjC,EAAA,CAAezjC,CAAf,CAAsB,CAAA,CAAtB,CADwB,CAA1B,CAEJ,QAAQ,CAACsc,CAAD,CAAQ,CACjB,MAAOmnB,EAAA,CAAennB,CAAf,CAAsB,CAAA,CAAtB,CADU,CAFZ,CA9BqB,CA3CvB,CA3CA,CAJU,CAAvB,CAqIIumB,EAAMA,QAAQ,CAAC7iC,CAAD,CAAQ,CACxB,MAAIA,EAAJ,EAAaX,CAAA,CAAWW,CAAAw0B,KAAX,CAAb,CAA4Cx0B,CAA5C,CACO,MACCw0B,QAAQ,CAAC1W,CAAD,CAAW,CACvB,IAAI3C,EAASsE,CAAA,EACb+iB,EAAA,CAAS,QAAQ,EAAG,CAClBrnB,CAAAua,QAAA,CAAe5X,CAAA,CAAS9d,CAAT,CAAf,CADkB,CAApB,CAGA,OAAOmb,EAAAsZ,QALgB,CADpB,CAFiB,CArI1B,CAuLIvB,EAASA,QAAQ,CAACvpB,CAAD,CAAS,CAC5B,IAAIwR,EAASsE,CAAA,EACbtE,EAAA+X,OAAA,CAAcvpB,CAAd,CACA,OAAOwR,EAAAsZ,QAHqB,CAvL9B,CA6LIqO,EAAgCA,QAAQ,CAACn5B,CAAD,CAAS,CACnD,MAAO,MACC6qB,QAAQ,CAAC1W,CAAD;AAAWklB,CAAX,CAAoB,CAChC,IAAI7nB,EAASsE,CAAA,EACb+iB,EAAA,CAAS,QAAQ,EAAG,CAClB,GAAI,CACFrnB,CAAAua,QAAA,CAAgB,CAAAr2B,CAAA,CAAW2jC,CAAX,CAAA,CAAsBA,CAAtB,CAAgCL,CAAhC,EAAgDh5B,CAAhD,CAAhB,CADE,CAEF,MAAM3D,CAAN,CAAS,CACTmV,CAAA+X,OAAA,CAAcltB,CAAd,CACA,CAAAy8B,CAAA,CAAiBz8B,CAAjB,CAFS,CAHO,CAApB,CAQA,OAAOmV,EAAAsZ,QAVyB,CAD7B,CAD4C,CAiIrD,OAAO,OACEhV,CADF,QAEGyT,CAFH,MAlGIwB,QAAQ,CAAC10B,CAAD,CAAQ8d,CAAR,CAAkBklB,CAAlB,CAA2BC,CAA3B,CAAyC,CAAA,IACtD9nB,EAASsE,CAAA,EAD6C,CAEtD2V,CAFsD,CAItD8N,EAAkBA,QAAQ,CAACljC,CAAD,CAAQ,CACpC,GAAI,CACF,MAAQ,CAAAX,CAAA,CAAWye,CAAX,CAAA,CAAuBA,CAAvB,CAAkC4kB,CAAlC,EAAmD1iC,CAAnD,CADN,CAEF,MAAOgG,CAAP,CAAU,CAEV,MADAy8B,EAAA,CAAiBz8B,CAAjB,CACO,CAAAktB,CAAA,CAAOltB,CAAP,CAFG,CAHwB,CAJoB,CAatDm9B,EAAiBA,QAAQ,CAACx5B,CAAD,CAAS,CACpC,GAAI,CACF,MAAQ,CAAAtK,CAAA,CAAW2jC,CAAX,CAAA,CAAsBA,CAAtB,CAAgCL,CAAhC,EAAgDh5B,CAAhD,CADN,CAEF,MAAO3D,CAAP,CAAU,CAEV,MADAy8B,EAAA,CAAiBz8B,CAAjB,CACO,CAAAktB,CAAA,CAAOltB,CAAP,CAFG,CAHwB,CAboB,CAsBtDo9B,EAAsBA,QAAQ,CAACL,CAAD,CAAW,CAC3C,GAAI,CACF,MAAQ,CAAA1jC,CAAA,CAAW4jC,CAAX,CAAA,CAA2BA,CAA3B,CAA0CP,CAA1C,EAA2DK,CAA3D,CADN,CAEF,MAAO/8B,CAAP,CAAU,CACVy8B,CAAA,CAAiBz8B,CAAjB,CADU,CAH+B,CAQ7Cw8B,EAAA,CAAS,QAAQ,EAAG,CAClBK,CAAA,CAAI7iC,CAAJ,CAAAw0B,KAAA,CAAgB,QAAQ,CAACx0B,CAAD,CAAQ,CAC1Bo1B,CAAJ,GACAA,CACA,CADO,CAAA,CACP,CAAAja,CAAAua,QAAA,CAAemN,CAAA,CAAI7iC,CAAJ,CAAAw0B,KAAA,CAAgB0O,CAAhB,CAAiCC,CAAjC,CAAiDC,CAAjD,CAAf,CAFA,CAD8B,CAAhC,CAIG,QAAQ,CAACz5B,CAAD,CAAS,CACdyrB,CAAJ,GACAA,CACA,CADO,CAAA,CACP,CAAAja,CAAAua,QAAA,CAAeyN,CAAA,CAAex5B,CAAf,CAAf,CAFA,CADkB,CAJpB,CAQG,QAAQ,CAACo5B,CAAD,CAAW,CAChB3N,CAAJ,EACAja,CAAA6e,OAAA,CAAcoJ,CAAA,CAAoBL,CAApB,CAAd,CAFoB,CARtB,CADkB,CAApB,CAeA,OAAO5nB,EAAAsZ,QA7CmD,CAkGrD;IAxBP7c,QAAY,CAACgsB,CAAD,CAAW,CAAA,IACjBnO,EAAWhW,CAAA,EADM,CAEjBwY,EAAU,CAFO,CAGjBt1B,EAAU3D,CAAA,CAAQ4kC,CAAR,CAAA,CAAoB,EAApB,CAAyB,EAEvC3kC,EAAA,CAAQ2kC,CAAR,CAAkB,QAAQ,CAACnP,CAAD,CAAUr1B,CAAV,CAAe,CACvC64B,CAAA,EACA4K,EAAA,CAAIpO,CAAJ,CAAAD,KAAA,CAAkB,QAAQ,CAACx0B,CAAD,CAAQ,CAC5B2C,CAAArD,eAAA,CAAuBF,CAAvB,CAAJ,GACAuD,CAAA,CAAQvD,CAAR,CACA,CADeY,CACf,CAAM,EAAEi4B,CAAR,EAAkBxC,CAAAC,QAAA,CAAiB/yB,CAAjB,CAFlB,CADgC,CAAlC,CAIG,QAAQ,CAACgH,CAAD,CAAS,CACdhH,CAAArD,eAAA,CAAuBF,CAAvB,CAAJ,EACAq2B,CAAAvC,OAAA,CAAgBvpB,CAAhB,CAFkB,CAJpB,CAFuC,CAAzC,CAYgB,EAAhB,GAAIsuB,CAAJ,EACExC,CAAAC,QAAA,CAAiB/yB,CAAjB,CAGF,OAAO8yB,EAAAhB,QArBc,CAwBhB,CA1UqC,CAkV9CzkB,QAASA,GAAa,EAAE,CACtB,IAAAqI,KAAA,CAAY,CAAC,SAAD,CAAY,UAAZ,CAAwB,QAAQ,CAAC0C,CAAD,CAAUc,CAAV,CAAoB,CAC9D,IAAIgoB,EAAwB9oB,CAAA8oB,sBAAxBA,EACwB9oB,CAAA+oB,4BADxBD,EAEwB9oB,CAAAgpB,yBAF5B,CAIIC,EAAuBjpB,CAAAipB,qBAAvBA,EACuBjpB,CAAAkpB,2BADvBD,EAEuBjpB,CAAAmpB,wBAFvBF,EAGuBjpB,CAAAopB,kCAP3B,CASIC,EAAe,CAAC,CAACP,CATrB,CAUIQ,EAAMD,CACA;AAAN,QAAQ,CAAC3/B,CAAD,CAAK,CACX,IAAI6/B,EAAKT,CAAA,CAAsBp/B,CAAtB,CACT,OAAO,SAAQ,EAAG,CAChBu/B,CAAA,CAAqBM,CAArB,CADgB,CAFP,CAAP,CAMN,QAAQ,CAAC7/B,CAAD,CAAK,CACX,IAAI8/B,EAAQ1oB,CAAA,CAASpX,CAAT,CAAa,KAAb,CAAoB,CAAA,CAApB,CACZ,OAAO,SAAQ,EAAG,CAChBoX,CAAAgE,OAAA,CAAgB0kB,CAAhB,CADgB,CAFP,CAOjBF,EAAAvoB,UAAA,CAAgBsoB,CAEhB,OAAOC,EA3BuD,CAApD,CADU,CAmGxB70B,QAASA,GAAkB,EAAE,CAC3B,IAAIg1B,EAAM,EAAV,CACIC,EAAmBhmC,CAAA,CAAO,YAAP,CADvB,CAEIimC,EAAiB,IAErB,KAAAC,UAAA,CAAiBC,QAAQ,CAAC5kC,CAAD,CAAQ,CAC3Be,SAAAlC,OAAJ,GACE2lC,CADF,CACQxkC,CADR,CAGA,OAAOwkC,EAJwB,CAOjC,KAAAnsB,KAAA,CAAY,CAAC,WAAD,CAAc,mBAAd,CAAmC,QAAnC,CAA6C,UAA7C,CACR,QAAQ,CAAE4B,CAAF,CAAeqI,CAAf,CAAoCc,CAApC,CAA8CwP,CAA9C,CAAwD,CA0ClEiS,QAASA,EAAK,EAAG,CACf,IAAAC,IAAA,CAAW7kC,EAAA,EACX,KAAAu1B,QAAA,CAAe,IAAAuP,QAAf,CAA8B,IAAAC,WAA9B,CACe,IAAAC,cADf,CACoC,IAAAC,cADpC,CAEe,IAAAC,YAFf,CAEkC,IAAAC,YAFlC,CAEqD,IACrD,KAAA,CAAK,MAAL,CAAA,CAAe,IAAAC,MAAf,CAA6B,IAC7B;IAAAC,YAAA,CAAmB,CAAA,CACnB,KAAAC,aAAA,CAAoB,EACpB,KAAAC,kBAAA,CAAyB,EACzB,KAAAC,YAAA,CAAmB,EACnB,KAAAC,gBAAA,CAAuB,EACvB,KAAA3b,kBAAA,CAAyB,EAXV,CA48BjB4b,QAASA,EAAU,CAACC,CAAD,CAAQ,CACzB,GAAI3qB,CAAAua,QAAJ,CACE,KAAMiP,EAAA,CAAiB,QAAjB,CAAsDxpB,CAAAua,QAAtD,CAAN,CAGFva,CAAAua,QAAA,CAAqBoQ,CALI,CAY3BC,QAASA,EAAW,CAAC7M,CAAD,CAAMrxB,CAAN,CAAY,CAC9B,IAAIlD,EAAK2e,CAAA,CAAO4V,CAAP,CACTpvB,GAAA,CAAYnF,CAAZ,CAAgBkD,CAAhB,CACA,OAAOlD,EAHuB,CAMhCqhC,QAASA,EAAsB,CAACC,CAAD,CAAUtM,CAAV,CAAiB9xB,CAAjB,CAAuB,CACpD,EACEo+B,EAAAL,gBAAA,CAAwB/9B,CAAxB,CAEA,EAFiC8xB,CAEjC,CAAsC,CAAtC,GAAIsM,CAAAL,gBAAA,CAAwB/9B,CAAxB,CAAJ,EACE,OAAOo+B,CAAAL,gBAAA,CAAwB/9B,CAAxB,CAJX,OAMUo+B,CANV,CAMoBA,CAAAhB,QANpB,CADoD,CActDiB,QAASA,EAAY,EAAG,EAt9BxBnB,CAAAhrB,UAAA,CAAkB,aACHgrB,CADG,MA0BVxf,QAAQ,CAAC4gB,CAAD,CAAU,CAIlBA,CAAJ,EACEC,CAIA,CAJQ,IAAIrB,CAIZ,CAHAqB,CAAAb,MAGA,CAHc,IAAAA,MAGd,CADAa,CAAAX,aACA,CADqB,IAAAA,aACrB,CAAAW,CAAAV,kBAAA;AAA0B,IAAAA,kBAL5B,GAOEW,CAKA,CALaA,QAAQ,EAAG,EAKxB,CAFAA,CAAAtsB,UAEA,CAFuB,IAEvB,CADAqsB,CACA,CADQ,IAAIC,CACZ,CAAAD,CAAApB,IAAA,CAAY7kC,EAAA,EAZd,CAcAimC,EAAA,CAAM,MAAN,CAAA,CAAgBA,CAChBA,EAAAT,YAAA,CAAoB,EACpBS,EAAAR,gBAAA,CAAwB,EACxBQ,EAAAnB,QAAA,CAAgB,IAChBmB,EAAAlB,WAAA,CAAmBkB,CAAAjB,cAAnB,CAAyCiB,CAAAf,YAAzC,CAA6De,CAAAd,YAA7D,CAAiF,IACjFc,EAAAhB,cAAA,CAAsB,IAAAE,YAClB,KAAAD,YAAJ,CAEE,IAAAC,YAFF,CACE,IAAAA,YAAAH,cADF,CACmCiB,CADnC,CAIE,IAAAf,YAJF,CAIqB,IAAAC,YAJrB,CAIwCc,CAExC,OAAOA,EA9Be,CA1BR,QAyKR7iC,QAAQ,CAAC+iC,CAAD,CAAWjpB,CAAX,CAAqBkpB,CAArB,CAAqC,CAAA,IAE/CztB,EAAMitB,CAAA,CAAYO,CAAZ,CAAsB,OAAtB,CAFyC,CAG/CtjC,EAFQ0F,IAEAw8B,WAHuC,CAI/CsB,EAAU,IACJnpB,CADI,MAEF6oB,CAFE,KAGHptB,CAHG,KAIHwtB,CAJG,IAKJ,CAAC,CAACC,CALE,CAQd3B,EAAA,CAAiB,IAGjB,IAAI,CAACrlC,CAAA,CAAW8d,CAAX,CAAL,CAA2B,CACzB,IAAIopB,EAAWV,CAAA,CAAY1oB,CAAZ,EAAwB7b,CAAxB,CAA8B,UAA9B,CACfglC,EAAA7hC,GAAA,CAAa+hC,QAAQ,CAACC,CAAD;AAASC,CAAT,CAAiBl+B,CAAjB,CAAwB,CAAC+9B,CAAA,CAAS/9B,CAAT,CAAD,CAFpB,CAK3B,GAAuB,QAAvB,EAAI,MAAO49B,EAAX,EAAmCxtB,CAAAsB,SAAnC,CAAiD,CAC/C,IAAIysB,EAAaL,CAAA7hC,GACjB6hC,EAAA7hC,GAAA,CAAa+hC,QAAQ,CAACC,CAAD,CAASC,CAAT,CAAiBl+B,CAAjB,CAAwB,CAC3Cm+B,CAAApnC,KAAA,CAAgB,IAAhB,CAAsBknC,CAAtB,CAA8BC,CAA9B,CAAsCl+B,CAAtC,CACAzF,GAAA,CAAYD,CAAZ,CAAmBwjC,CAAnB,CAF2C,CAFE,CAQ5CxjC,CAAL,GACEA,CADF,CA3BY0F,IA4BFw8B,WADV,CAC6B,EAD7B,CAKAliC,EAAArC,QAAA,CAAc6lC,CAAd,CAEA,OAAO,SAAQ,EAAG,CAChBvjC,EAAA,CAAYD,CAAZ,CAAmBwjC,CAAnB,CACA5B,EAAA,CAAiB,IAFD,CAnCiC,CAzKrC,kBA0QEkC,QAAQ,CAACjoC,CAAD,CAAMwe,CAAN,CAAgB,CACxC,IAAI3Y,EAAO,IAAX,CAEIyqB,CAFJ,CAKIC,CALJ,CAOI2X,CAPJ,CASIC,EAAuC,CAAvCA,CAAqB3pB,CAAAte,OATzB,CAUIkoC,EAAiB,CAVrB,CAWIC,EAAY5jB,CAAA,CAAOzkB,CAAP,CAXhB,CAYIsoC,EAAgB,EAZpB,CAaIC,EAAiB,EAbrB,CAcIC,EAAU,CAAA,CAdd,CAeIC,EAAY,CAsGhB,OAAO,KAAA/jC,OAAA,CApGPgkC,QAA8B,EAAG,CAC/BpY,CAAA,CAAW+X,CAAA,CAAUxiC,CAAV,CADoB,KAE3B8iC,CAF2B,CAEhBloC,CAEf,IAAKwC,CAAA,CAASqtB,CAAT,CAAL,CAKO,GAAIvwB,EAAA,CAAYuwB,CAAZ,CAAJ,CAgBL,IAfIC,CAeKrvB,GAfQonC,CAeRpnC,GAbPqvB,CAEA,CAFW+X,CAEX,CADAG,CACA,CADYlY,CAAArwB,OACZ,CAD8B,CAC9B,CAAAkoC,CAAA,EAWOlnC,EARTynC,CAQSznC,CARGovB,CAAApwB,OAQHgB,CANLunC,CAMKvnC,GANSynC,CAMTznC,GAJPknC,CAAA,EACA,CAAA7X,CAAArwB,OAAA,CAAkBuoC,CAAlB,CAA8BE,CAGvBznC,EAAAA,CAAAA,CAAI,CAAb,CAAgBA,CAAhB,CAAoBynC,CAApB,CAA+BznC,CAAA,EAA/B,CACiBqvB,CAAA,CAASrvB,CAAT,CAEf,GAF+BqvB,CAAA,CAASrvB,CAAT,CAE/B,EADKovB,CAAA,CAASpvB,CAAT,CACL,GADqBovB,CAAA,CAASpvB,CAAT,CACrB,EAAiBqvB,CAAA,CAASrvB,CAAT,CAAjB,GAAiCovB,CAAA,CAASpvB,CAAT,CAAjC,GACEknC,CAAA,EACA,CAAA7X,CAAA,CAASrvB,CAAT,CAAA,CAAcovB,CAAA,CAASpvB,CAAT,CAFhB,CAnBG,KAwBA,CACDqvB,CAAJ,GAAiBgY,CAAjB,GAEEhY,CAEA,CAFWgY,CAEX,CAF4B,EAE5B,CADAE,CACA,CADY,CACZ,CAAAL,CAAA,EAJF,CAOAO,EAAA;AAAY,CACZ,KAAKloC,CAAL,GAAY6vB,EAAZ,CACMA,CAAA3vB,eAAA,CAAwBF,CAAxB,CAAJ,GACEkoC,CAAA,EACA,CAAIpY,CAAA5vB,eAAA,CAAwBF,CAAxB,CAAJ,CACM8vB,CAAA,CAAS9vB,CAAT,CADN,GACwB6vB,CAAA,CAAS7vB,CAAT,CADxB,GAEI2nC,CAAA,EACA,CAAA7X,CAAA,CAAS9vB,CAAT,CAAA,CAAgB6vB,CAAA,CAAS7vB,CAAT,CAHpB,GAMEgoC,CAAA,EAEA,CADAlY,CAAA,CAAS9vB,CAAT,CACA,CADgB6vB,CAAA,CAAS7vB,CAAT,CAChB,CAAA2nC,CAAA,EARF,CAFF,CAcF,IAAIK,CAAJ,CAAgBE,CAAhB,CAGE,IAAIloC,CAAJ,GADA2nC,EAAA,EACW7X,CAAAA,CAAX,CACMA,CAAA5vB,eAAA,CAAwBF,CAAxB,CAAJ,EAAqC,CAAA6vB,CAAA3vB,eAAA,CAAwBF,CAAxB,CAArC,GACEgoC,CAAA,EACA,CAAA,OAAOlY,CAAA,CAAS9vB,CAAT,CAFT,CA5BC,CA7BP,IACM8vB,EAAJ,GAAiBD,CAAjB,GACEC,CACA,CADWD,CACX,CAAA8X,CAAA,EAFF,CA+DF,OAAOA,EApEwB,CAoG1B,CA7BPQ,QAA+B,EAAG,CAC5BJ,CAAJ,EACEA,CACA,CADU,CAAA,CACV,CAAAhqB,CAAA,CAAS8R,CAAT,CAAmBA,CAAnB,CAA6BzqB,CAA7B,CAFF,EAIE2Y,CAAA,CAAS8R,CAAT,CAAmB4X,CAAnB,CAAiCriC,CAAjC,CAIF,IAAIsiC,CAAJ,CACE,GAAKllC,CAAA,CAASqtB,CAAT,CAAL,CAGO,GAAIvwB,EAAA,CAAYuwB,CAAZ,CAAJ,CAA2B,CAChC4X,CAAA,CAAmB3hB,KAAJ,CAAU+J,CAAApwB,OAAV,CACf,KAAK,IAAIgB,EAAI,CAAb,CAAgBA,CAAhB,CAAoBovB,CAAApwB,OAApB,CAAqCgB,CAAA,EAArC,CACEgnC,CAAA,CAAahnC,CAAb,CAAA,CAAkBovB,CAAA,CAASpvB,CAAT,CAHY,CAA3B,IAOL,KAAST,CAAT,GADAynC,EACgB5X,CADD,EACCA,CAAAA,CAAhB,CACM3vB,EAAAC,KAAA,CAAoB0vB,CAApB,CAA8B7vB,CAA9B,CAAJ,GACEynC,CAAA,CAAaznC,CAAb,CADF,CACsB6vB,CAAA,CAAS7vB,CAAT,CADtB,CAXJ,KAEEynC,EAAA,CAAe5X,CAZa,CA6B3B,CAtHiC,CA1Q1B,SAkbP4P,QAAQ,EAAG,CAAA,IACd2I,CADc,CACPxnC,CADO,CACA8X,CADA,CAEd2vB,CAFc,CAGdC,EAAa,IAAAnC,aAHC,CAIdoC,EAAkB,IAAAnC,kBAJJ,CAKd3mC,CALc,CAMd+oC,CANc,CAMPC,EAAMrD,CANC,CAORuB,CAPQ,CAQd+B,EAAW,EARG,CASdC,CATc,CASNC,CATM,CASEC,CAEpBtC,EAAA,CAAW,SAAX,CAEAjB;CAAA,CAAiB,IAEjB,GAAG,CACDkD,CAAA,CAAQ,CAAA,CAGR,KAFA7B,CAEA,CAZ0BxvB,IAY1B,CAAMmxB,CAAA7oC,OAAN,CAAA,CAAyB,CACvB,GAAI,CACFopC,CACA,CADYP,CAAAr2B,MAAA,EACZ,CAAA42B,CAAAz/B,MAAA0/B,MAAA,CAAsBD,CAAA1W,WAAtB,CAFE,CAGF,MAAOvrB,CAAP,CAAU,CAsflBiV,CAAAua,QApfQ,CAofa,IApfb,CAAAlT,CAAA,CAAkBtc,CAAlB,CAFU,CAIZ0+B,CAAA,CAAiB,IARM,CAWzB,CAAA,CACA,EAAG,CACD,GAAK+C,CAAL,CAAgB1B,CAAAf,WAAhB,CAGE,IADAnmC,CACA,CADS4oC,CAAA5oC,OACT,CAAOA,CAAA,EAAP,CAAA,CACE,GAAI,CAIF,GAHA2oC,CAGA,CAHQC,CAAA,CAAS5oC,CAAT,CAGR,CACE,IAAKmB,CAAL,CAAawnC,CAAA5uB,IAAA,CAAUmtB,CAAV,CAAb,KAAsCjuB,CAAtC,CAA6C0vB,CAAA1vB,KAA7C,GACI,EAAE0vB,CAAAjjB,GACA,CAAI1gB,EAAA,CAAO7D,CAAP,CAAc8X,CAAd,CAAJ,CACqB,QADrB,EACK,MAAO9X,EADZ,EACgD,QADhD,EACiC,MAAO8X,EADxC,EAEQqwB,KAAA,CAAMnoC,CAAN,CAFR,EAEwBmoC,KAAA,CAAMrwB,CAAN,CAH1B,CADJ,CAKE8vB,CAIA,CAJQ,CAAA,CAIR,CAHAlD,CAGA,CAHiB8C,CAGjB,CAFAA,CAAA1vB,KAEA,CAFa0vB,CAAAjjB,GAAA,CAAWthB,EAAA,CAAKjD,CAAL,CAAX,CAAyBA,CAEtC,CADAwnC,CAAA/iC,GAAA,CAASzE,CAAT,CAAkB8X,CAAD,GAAUkuB,CAAV,CAA0BhmC,CAA1B,CAAkC8X,CAAnD,CAA0DiuB,CAA1D,CACA,CAAU,CAAV,CAAI8B,CAAJ,GACEE,CAMA,CANS,CAMT,CANaF,CAMb,CALKC,CAAA,CAASC,CAAT,CAKL,GALuBD,CAAA,CAASC,CAAT,CAKvB,CAL0C,EAK1C,EAJAC,CAIA,CAJU3oC,CAAA,CAAWmoC,CAAAxO,IAAX,CACD,CAAH,MAAG,EAAOwO,CAAAxO,IAAArxB,KAAP,EAAyB6/B,CAAAxO,IAAAj3B,SAAA,EAAzB,EACHylC,CAAAxO,IAEN,CADAgP,CACA,EADU,YACV,CADyB/iC,EAAA,CAAOjF,CAAP,CACzB,CADyC,YACzC,CADwDiF,EAAA,CAAO6S,CAAP,CACxD,CAAAgwB,CAAA,CAASC,CAAT,CAAAroC,KAAA,CAAsBsoC,CAAtB,CAPF,CATF,KAkBO,IAAIR,CAAJ,GAAc9C,CAAd,CAA8B,CAGnCkD,CAAA,CAAQ,CAAA,CACR,OAAM,CAJ6B,CAvBrC,CA8BF,MAAO5hC,CAAP,CAAU,CA2ctBiV,CAAAua,QAzcY;AAycS,IAzcT,CAAAlT,CAAA,CAAkBtc,CAAlB,CAFU,CAUhB,GAAI,EAAEoiC,CAAF,CAAUrC,CAAAZ,YAAV,EACCY,CADD,GArEoBxvB,IAqEpB,EACuBwvB,CAAAd,cADvB,CAAJ,CAEE,IAAA,CAAMc,CAAN,GAvEsBxvB,IAuEtB,EAA4B,EAAE6xB,CAAF,CAASrC,CAAAd,cAAT,CAA5B,CAAA,CACEc,CAAA,CAAUA,CAAAhB,QAhDb,CAAH,MAmDUgB,CAnDV,CAmDoBqC,CAnDpB,CAuDA,KAAIR,CAAJ,EAAaF,CAAA7oC,OAAb,GAAmC,CAAEgpC,CAAA,EAArC,CAEE,KAqbN5sB,EAAAua,QArbY,CAqbS,IArbT,CAAAiP,CAAA,CAAiB,QAAjB,CAGFD,CAHE,CAGGv/B,EAAA,CAAO6iC,CAAP,CAHH,CAAN,CAzED,CAAH,MA+ESF,CA/ET,EA+EkBF,CAAA7oC,OA/ElB,CAmFA,KA2aFoc,CAAAua,QA3aE,CA2amB,IA3anB,CAAMmS,CAAA9oC,OAAN,CAAA,CACE,GAAI,CACF8oC,CAAAt2B,MAAA,EAAA,EADE,CAEF,MAAOrL,CAAP,CAAU,CACVsc,CAAA,CAAkBtc,CAAlB,CADU,CArGI,CAlbJ,UAgkBNqO,QAAQ,EAAG,CAEnB,GAAIixB,CAAA,IAAAA,YAAJ,CAAA,CACA,IAAIlkC,EAAS,IAAA2jC,QAEb,KAAA7G,WAAA,CAAgB,UAAhB,CACA,KAAAoH,YAAA,CAAmB,CAAA,CACf,KAAJ,GAAarqB,CAAb,GAEAhc,CAAA,CAAQ,IAAAymC,gBAAR,CAA8BnhC,EAAA,CAAK,IAAL,CAAWuhC,CAAX,CAAmC,IAAnC,CAA9B,CA2BA,CAvBI1kC,CAAA+jC,YAuBJ,EAvB0B,IAuB1B,GAvBgC/jC,CAAA+jC,YAuBhC,CAvBqD,IAAAF,cAuBrD,EAtBI7jC,CAAAgkC,YAsBJ,EAtB0B,IAsB1B;CAtBgChkC,CAAAgkC,YAsBhC,CAtBqD,IAAAF,cAsBrD,EArBI,IAAAA,cAqBJ,GArBwB,IAAAA,cAAAD,cAqBxB,CArB2D,IAAAA,cAqB3D,EApBI,IAAAA,cAoBJ,GApBwB,IAAAA,cAAAC,cAoBxB,CApB2D,IAAAA,cAoB3D,EATA,IAAAH,QASA,CATe,IAAAE,cASf,CAToC,IAAAC,cASpC,CATyD,IAAAC,YASzD,CARI,IAAAC,YAQJ,CARuB,IAAAC,MAQvB,CARoC,IAQpC,CALA,IAAAI,YAKA,CALmB,EAKnB,CAJA,IAAAT,WAIA,CAJkB,IAAAO,aAIlB,CAJsC,IAAAC,kBAItC,CAJ+D,EAI/D,CADA,IAAAnxB,SACA,CADgB,IAAAwqB,QAChB,CAD+B,IAAAl2B,OAC/B,CAD6CrH,CAC7C,CAAA,IAAA+mC,IAAA,CAAW,IAAAhlC,OAAX,CAAyBilC,QAAQ,EAAG,CAAE,MAAOhnC,EAAT,CA7BpC,CALA,CAFmB,CAhkBL,OAmoBT4mC,QAAQ,CAACK,CAAD,CAAO/uB,CAAP,CAAe,CAC5B,MAAO4J,EAAA,CAAOmlB,CAAP,CAAA,CAAa,IAAb,CAAmB/uB,CAAnB,CADqB,CAnoBd,YAoqBJpW,QAAQ,CAACmlC,CAAD,CAAO,CAGpBttB,CAAAua,QAAL;AAA4Bva,CAAAsqB,aAAA1mC,OAA5B,EACE+zB,CAAAnT,MAAA,CAAe,QAAQ,EAAG,CACpBxE,CAAAsqB,aAAA1mC,OAAJ,EACEoc,CAAA4jB,QAAA,EAFsB,CAA1B,CAOF,KAAA0G,aAAA7lC,KAAA,CAAuB,OAAQ,IAAR,YAA0B6oC,CAA1B,CAAvB,CAXyB,CApqBX,cAkrBDC,QAAQ,CAAC/jC,CAAD,CAAK,CAC1B,IAAA+gC,kBAAA9lC,KAAA,CAA4B+E,CAA5B,CAD0B,CAlrBZ,QAmuBRkE,QAAQ,CAAC4/B,CAAD,CAAO,CACrB,GAAI,CAEF,MADA5C,EAAA,CAAW,QAAX,CACO,CAAA,IAAAuC,MAAA,CAAWK,CAAX,CAFL,CAGF,MAAOviC,CAAP,CAAU,CACVsc,CAAA,CAAkBtc,CAAlB,CADU,CAHZ,OAKU,CAsNZiV,CAAAua,QAAA,CAAqB,IApNjB,IAAI,CACFva,CAAA4jB,QAAA,EADE,CAEF,MAAO74B,CAAP,CAAU,CAEV,KADAsc,EAAA,CAAkBtc,CAAlB,CACMA,CAAAA,CAAN,CAFU,CAJJ,CANW,CAnuBP,KA8wBXqiC,QAAQ,CAAC1gC,CAAD,CAAOwV,CAAP,CAAiB,CAC5B,IAAIsrB,EAAiB,IAAAhD,YAAA,CAAiB99B,CAAjB,CAChB8gC,EAAL,GACE,IAAAhD,YAAA,CAAiB99B,CAAjB,CADF,CAC2B8gC,CAD3B,CAC4C,EAD5C,CAGAA,EAAA/oC,KAAA,CAAoByd,CAApB,CAEA,KAAI4oB,EAAU,IACd,GACOA,EAAAL,gBAAA,CAAwB/9B,CAAxB,CAGL,GAFEo+B,CAAAL,gBAAA,CAAwB/9B,CAAxB,CAEF,CAFkC,CAElC,EAAAo+B,CAAAL,gBAAA,CAAwB/9B,CAAxB,CAAA,EAJF,OAKUo+B,CALV,CAKoBA,CAAAhB,QALpB,CAOA;IAAIvgC,EAAO,IACX,OAAO,SAAQ,EAAG,CAChBikC,CAAA,CAAe5lC,EAAA,CAAQ4lC,CAAR,CAAwBtrB,CAAxB,CAAf,CAAA,CAAoD,IACpD2oB,EAAA,CAAuBthC,CAAvB,CAA6B,CAA7B,CAAgCmD,CAAhC,CAFgB,CAhBU,CA9wBd,OA2zBT+gC,QAAQ,CAAC/gC,CAAD,CAAO8R,CAAP,CAAa,CAAA,IACtB1T,EAAQ,EADc,CAEtB0iC,CAFsB,CAGtBjgC,EAAQ,IAHc,CAItB4N,EAAkB,CAAA,CAJI,CAKtBJ,EAAQ,MACArO,CADA,aAEOa,CAFP,iBAGW4N,QAAQ,EAAG,CAACA,CAAA,CAAkB,CAAA,CAAnB,CAHtB,gBAIUH,QAAQ,EAAG,CACzBD,CAAAS,iBAAA,CAAyB,CAAA,CADA,CAJrB,kBAOY,CAAA,CAPZ,CALc,CActBkyB,EAAsBC,CAAC5yB,CAAD4yB,CA92WzB9jC,OAAA,CAAcH,EAAApF,KAAA,CA82WoBwB,SA92WpB,CA82W+Bb,CA92W/B,CAAd,CAg2WyB,CAetBL,CAfsB,CAenBhB,CAEP,GAAG,CACD4pC,CAAA,CAAiBjgC,CAAAi9B,YAAA,CAAkB99B,CAAlB,CAAjB,EAA4C5B,CAC5CiQ,EAAA6yB,aAAA,CAAqBrgC,CAChB3I,EAAA,CAAE,CAAP,KAAUhB,CAAV,CAAiB4pC,CAAA5pC,OAAjB,CAAwCgB,CAAxC,CAA0ChB,CAA1C,CAAkDgB,CAAA,EAAlD,CAGE,GAAK4oC,CAAA,CAAe5oC,CAAf,CAAL,CAMA,GAAI,CAEF4oC,CAAA,CAAe5oC,CAAf,CAAAgF,MAAA,CAAwB,IAAxB,CAA8B8jC,CAA9B,CAFE,CAGF,MAAO3iC,CAAP,CAAU,CACVsc,CAAA,CAAkBtc,CAAlB,CADU,CATZ,IACEyiC,EAAAzlC,OAAA,CAAsBnD,CAAtB,CAAyB,CAAzB,CAEA,CADAA,CAAA,EACA,CAAAhB,CAAA,EAWJ,IAAIuX,CAAJ,CAAqB,KAErB5N,EAAA,CAAQA,CAAAu8B,QAtBP,CAAH,MAuBSv8B,CAvBT,CAyBA,OAAOwN,EA1CmB,CA3zBZ,YA83BJkoB,QAAQ,CAACv2B,CAAD,CAAO8R,CAAP,CAAa,CAgB/B,IAhB+B,IAE3BssB,EADSxvB,IADkB,CAG3B6xB,EAFS7xB,IADkB,CAI3BP,EAAQ,MACArO,CADA;YAHC4O,IAGD,gBAGUN,QAAQ,EAAG,CACzBD,CAAAS,iBAAA,CAAyB,CAAA,CADA,CAHrB,kBAMY,CAAA,CANZ,CAJmB,CAY3BkyB,EAAsBC,CAAC5yB,CAAD4yB,CA/6WzB9jC,OAAA,CAAcH,EAAApF,KAAA,CA+6WoBwB,SA/6WpB,CA+6W+Bb,CA/6W/B,CAAd,CAm6W8B,CAahBL,CAbgB,CAabhB,CAGlB,CAAQknC,CAAR,CAAkBqC,CAAlB,CAAA,CAAyB,CACvBpyB,CAAA6yB,aAAA,CAAqB9C,CACrBrV,EAAA,CAAYqV,CAAAN,YAAA,CAAoB99B,CAApB,CAAZ,EAAyC,EACpC9H,EAAA,CAAE,CAAP,KAAUhB,CAAV,CAAmB6xB,CAAA7xB,OAAnB,CAAqCgB,CAArC,CAAuChB,CAAvC,CAA+CgB,CAAA,EAA/C,CAEE,GAAK6wB,CAAA,CAAU7wB,CAAV,CAAL,CAOA,GAAI,CACF6wB,CAAA,CAAU7wB,CAAV,CAAAgF,MAAA,CAAmB,IAAnB,CAAyB8jC,CAAzB,CADE,CAEF,MAAM3iC,CAAN,CAAS,CACTsc,CAAA,CAAkBtc,CAAlB,CADS,CATX,IACE0qB,EAAA1tB,OAAA,CAAiBnD,CAAjB,CAAoB,CAApB,CAEA,CADAA,CAAA,EACA,CAAAhB,CAAA,EAeJ,IAAI,EAAEupC,CAAF,CAAWrC,CAAAL,gBAAA,CAAwB/9B,CAAxB,CAAX,EAA4Co+B,CAAAZ,YAA5C,EACCY,CADD,GAtCOxvB,IAsCP,EACuBwvB,CAAAd,cADvB,CAAJ,CAEE,IAAA,CAAMc,CAAN,GAxCSxvB,IAwCT,EAA4B,EAAE6xB,CAAF,CAASrC,CAAAd,cAAT,CAA5B,CAAA,CACEc,CAAA,CAAUA,CAAAhB,QA1BS,CA+BzB,MAAO/uB,EA/CwB,CA93BjB,CAi7BlB,KAAIiF,EAAa,IAAI4pB,CAErB,OAAO5pB,EAn/B2D,CADxD,CAZe,CA2iC7BjP,QAASA,GAAqB,EAAG,CAAA,IAC3B4W,EAA6B,mCADF,CAE7BG,EAA8B,qCAkBhC;IAAAH,2BAAA,CAAkCC,QAAQ,CAACC,CAAD,CAAS,CACjD,MAAInhB,EAAA,CAAUmhB,CAAV,CAAJ,EACEF,CACO,CADsBE,CACtB,CAAA,IAFT,EAIOF,CAL0C,CAyBnD,KAAAG,4BAAA,CAAmCC,QAAQ,CAACF,CAAD,CAAS,CAClD,MAAInhB,EAAA,CAAUmhB,CAAV,CAAJ,EACEC,CACO,CADuBD,CACvB,CAAA,IAFT,EAIOC,CAL2C,CAQpD,KAAA1K,KAAA,CAAY4H,QAAQ,EAAG,CACrB,MAAO6oB,SAAoB,CAACC,CAAD,CAAMC,CAAN,CAAe,CACxC,IAAIC,EAAQD,CAAA,CAAUjmB,CAAV,CAAwCH,CAApD,CACIsmB,CAEJ,IAAI,CAACpyB,CAAL,EAAqB,CAArB,EAAaA,CAAb,CAEE,GADAoyB,CACI,CADYpR,EAAA,CAAWiR,CAAX,CAAA9qB,KACZ,CAAkB,EAAlB,GAAAirB,CAAA,EAAwB,CAACA,CAAA7iC,MAAA,CAAoB4iC,CAApB,CAA7B,CACE,MAAO,SAAP,CAAiBC,CAGrB,OAAOH,EAViC,CADrB,CArDQ,CA4FjCI,QAASA,GAAa,CAACC,CAAD,CAAU,CAC9B,GAAgB,MAAhB,GAAIA,CAAJ,CACE,MAAOA,EACF,IAAIrqC,CAAA,CAASqqC,CAAT,CAAJ,CAAuB,CAK5B,GAA8B,EAA9B,CAAIA,CAAAvmC,QAAA,CAAgB,KAAhB,CAAJ,CACE,KAAMwmC,GAAA,CAAW,QAAX,CACsDD,CADtD,CAAN,CAGFA,CAAA,CAA0BA,CAjBrB9iC,QAAA,CAAU,+BAAV,CAA2C,MAA3C,CAAAA,QAAA,CACU,OADV,CACmB,OADnB,CAiBKA,QAAA,CACY,QADZ,CACsB,IADtB,CAAAA,QAAA,CAEY,KAFZ,CAEmB,YAFnB,CAGV,OAAW7C,OAAJ,CAAW,GAAX;AAAiB2lC,CAAjB,CAA2B,GAA3B,CAZqB,CAavB,GAAIpnC,EAAA,CAASonC,CAAT,CAAJ,CAIL,MAAW3lC,OAAJ,CAAW,GAAX,CAAiB2lC,CAAAlmC,OAAjB,CAAkC,GAAlC,CAEP,MAAMmmC,GAAA,CAAW,UAAX,CAAN,CAtB4B,CA4BhCC,QAASA,GAAc,CAACC,CAAD,CAAW,CAChC,IAAIC,EAAmB,EACnB7nC,EAAA,CAAU4nC,CAAV,CAAJ,EACEtqC,CAAA,CAAQsqC,CAAR,CAAkB,QAAQ,CAACH,CAAD,CAAU,CAClCI,CAAA9pC,KAAA,CAAsBypC,EAAA,CAAcC,CAAd,CAAtB,CADkC,CAApC,CAIF,OAAOI,EAPyB,CA4ElC75B,QAASA,GAAoB,EAAG,CAC9B,IAAA85B,aAAA,CAAoBA,EADU,KAI1BC,EAAuB,CAAC,MAAD,CAJG,CAK1BC,EAAuB,EAwB3B,KAAAD,qBAAA,CAA4BE,QAAS,CAAC5pC,CAAD,CAAQ,CACvCe,SAAAlC,OAAJ,GACE6qC,CADF,CACyBJ,EAAA,CAAetpC,CAAf,CADzB,CAGA,OAAO0pC,EAJoC,CAkC7C,KAAAC,qBAAA,CAA4BE,QAAS,CAAC7pC,CAAD,CAAQ,CACvCe,SAAAlC,OAAJ,GACE8qC,CADF,CACyBL,EAAA,CAAetpC,CAAf,CADzB,CAGA,OAAO2pC,EAJoC,CAO7C,KAAAtxB,KAAA,CAAY,CAAC,WAAD,CAAc,QAAQ,CAAC4B,CAAD,CAAY,CA0C5C6vB,QAASA,EAAkB,CAACC,CAAD,CAAO,CAChC,IAAIC,EAAaA,QAA+B,CAACC,CAAD,CAAe,CAC7D,IAAAC,qBAAA,CAA4BC,QAAQ,EAAG,CACrC,MAAOF,EAD8B,CADsB,CAK3DF,EAAJ,GACEC,CAAAnwB,UADF,CACyB,IAAIkwB,CAD7B,CAGAC,EAAAnwB,UAAAwf,QAAA;AAA+B+Q,QAAmB,EAAG,CACnD,MAAO,KAAAF,qBAAA,EAD4C,CAGrDF,EAAAnwB,UAAA9X,SAAA,CAAgCsoC,QAAoB,EAAG,CACrD,MAAO,KAAAH,qBAAA,EAAAnoC,SAAA,EAD8C,CAGvD,OAAOioC,EAfyB,CAxClC,IAAIM,EAAgBA,QAAsB,CAACnkC,CAAD,CAAO,CAC/C,KAAMkjC,GAAA,CAAW,QAAX,CAAN,CAD+C,CAI7CpvB,EAAAF,IAAA,CAAc,WAAd,CAAJ,GACEuwB,CADF,CACkBrwB,CAAArB,IAAA,CAAc,WAAd,CADlB,CAN4C,KA4DxC2xB,EAAyBT,CAAA,EA5De,CA6DxCU,EAAS,EAEbA,EAAA,CAAOf,EAAA5a,KAAP,CAAA,CAA4Bib,CAAA,CAAmBS,CAAnB,CAC5BC,EAAA,CAAOf,EAAAgB,IAAP,CAAA,CAA2BX,CAAA,CAAmBS,CAAnB,CAC3BC,EAAA,CAAOf,EAAAiB,IAAP,CAAA,CAA2BZ,CAAA,CAAmBS,CAAnB,CAC3BC,EAAA,CAAOf,EAAAkB,GAAP,CAAA,CAA0Bb,CAAA,CAAmBS,CAAnB,CAC1BC,EAAA,CAAOf,EAAA3a,aAAP,CAAA,CAAoCgb,CAAA,CAAmBU,CAAA,CAAOf,EAAAiB,IAAP,CAAnB,CAyGpC,OAAO,SAtFPE,QAAgB,CAACl3B,CAAD,CAAOu2B,CAAP,CAAqB,CACnC,IAAItwB,EAAe6wB,CAAAlrC,eAAA,CAAsBoU,CAAtB,CAAA,CAA8B82B,CAAA,CAAO92B,CAAP,CAA9B,CAA6C,IAChE,IAAI,CAACiG,CAAL,CACE,KAAM0vB,GAAA,CAAW,UAAX,CAEF31B,CAFE,CAEIu2B,CAFJ,CAAN,CAIF,GAAqB,IAArB,GAAIA,CAAJ,EAA6BA,CAA7B,GAA8CzrC,CAA9C,EAA4E,EAA5E,GAA2DyrC,CAA3D,CACE,MAAOA,EAIT,IAA4B,QAA5B,GAAI,MAAOA,EAAX,CACE,KAAMZ,GAAA,CAAW,OAAX,CAEF31B,CAFE,CAAN,CAIF,MAAO,KAAIiG,CAAJ,CAAgBswB,CAAhB,CAjB4B,CAsF9B;WAzBP7Q,QAAmB,CAAC1lB,CAAD,CAAOm3B,CAAP,CAAqB,CACtC,GAAqB,IAArB,GAAIA,CAAJ,EAA6BA,CAA7B,GAA8CrsC,CAA9C,EAA4E,EAA5E,GAA2DqsC,CAA3D,CACE,MAAOA,EAET,KAAI/gC,EAAe0gC,CAAAlrC,eAAA,CAAsBoU,CAAtB,CAAA,CAA8B82B,CAAA,CAAO92B,CAAP,CAA9B,CAA6C,IAChE,IAAI5J,CAAJ,EAAmB+gC,CAAnB,WAA2C/gC,EAA3C,CACE,MAAO+gC,EAAAX,qBAAA,EAKT,IAAIx2B,CAAJ,GAAa+1B,EAAA3a,aAAb,CAAwC,CAzIpC8L,IAAAA,EAAY9C,EAAA,CA0ImB+S,CA1IR9oC,SAAA,EAAX,CAAZ64B,CACA/6B,CADA+6B,CACGna,CADHma,CACMkQ,EAAU,CAAA,CAEfjrC,EAAA,CAAI,CAAT,KAAY4gB,CAAZ,CAAgBipB,CAAA7qC,OAAhB,CAA6CgB,CAA7C,CAAiD4gB,CAAjD,CAAoD5gB,CAAA,EAApD,CACE,GAbc,MAAhB,GAae6pC,CAAAN,CAAqBvpC,CAArBupC,CAbf,CACSpV,EAAA,CAY+B4G,CAZ/B,CADT,CAae8O,CAAAN,CAAqBvpC,CAArBupC,CATJthC,KAAA,CAS6B8yB,CAThB3c,KAAb,CAST,CAAkD,CAChD6sB,CAAA,CAAU,CAAA,CACV,MAFgD,CAKpD,GAAIA,CAAJ,CAEE,IAAKjrC,CAAO,CAAH,CAAG,CAAA4gB,CAAA,CAAIkpB,CAAA9qC,OAAhB,CAA6CgB,CAA7C,CAAiD4gB,CAAjD,CAAoD5gB,CAAA,EAApD,CACE,GArBY,MAAhB,GAqBiB8pC,CAAAP,CAAqBvpC,CAArBupC,CArBjB,CACSpV,EAAA,CAoBiC4G,CApBjC,CADT,CAqBiB+O,CAAAP,CAAqBvpC,CAArBupC,CAjBNthC,KAAA,CAiB+B8yB,CAjBlB3c,KAAb,CAiBP,CAAkD,CAChD6sB,CAAA,CAAU,CAAA,CACV,MAFgD,CA8HpD,GAxHKA,CAwHL,CACE,MAAOD,EAEP,MAAMxB,GAAA,CAAW,UAAX,CAEFwB,CAAA9oC,SAAA,EAFE,CAAN,CAJoC,CAQjC,GAAI2R,CAAJ,GAAa+1B,EAAA5a,KAAb,CACL,MAAOyb,EAAA,CAAcO,CAAd,CAET,MAAMxB,GAAA,CAAW,QAAX,CAAN,CAtBsC,CAyBjC,SAhDPhQ,QAAgB,CAACwR,CAAD,CAAe,CAC7B,MAAIA,EAAJ;AAA4BN,CAA5B,CACSM,CAAAX,qBAAA,EADT,CAGSW,CAJoB,CAgDxB,CA5KqC,CAAlC,CAtEkB,CAmhBhCn7B,QAASA,GAAY,EAAG,CACtB,IAAIq7B,EAAU,CAAA,CAad,KAAAA,QAAA,CAAeC,QAAS,CAAChrC,CAAD,CAAQ,CAC1Be,SAAAlC,OAAJ,GACEksC,CADF,CACY,CAAC,CAAC/qC,CADd,CAGA,OAAO+qC,EAJuB,CAsDhC,KAAA1yB,KAAA,CAAY,CAAC,QAAD,CAAW,UAAX,CAAuB,cAAvB,CAAuC,QAAQ,CAC7C+K,CAD6C,CACnCnH,CADmC,CACvBgvB,CADuB,CACT,CAGhD,GAAIF,CAAJ,EAAe9uB,CAAAnF,KAAf,EAA4D,CAA5D,CAAgCmF,CAAAivB,iBAAhC,CACE,KAAM7B,GAAA,CAAW,UAAX,CAAN,CAMF,IAAI8B,EAAMloC,EAAA,CAAKwmC,EAAL,CAaV0B,EAAAC,UAAA,CAAgBC,QAAS,EAAG,CAC1B,MAAON,EADmB,CAG5BI,EAAAP,QAAA,CAAcK,CAAAL,QACdO,EAAA/R,WAAA,CAAiB6R,CAAA7R,WACjB+R,EAAA9R,QAAA,CAAc4R,CAAA5R,QAET0R,EAAL,GACEI,CAAAP,QACA,CADcO,CAAA/R,WACd,CAD+BkS,QAAQ,CAAC53B,CAAD,CAAO1T,CAAP,CAAc,CAAE,MAAOA,EAAT,CACrD,CAAAmrC,CAAA9R,QAAA,CAAc93B,EAFhB,CAwBA4pC,EAAAI,QAAA,CAAcC,QAAmB,CAAC93B,CAAD,CAAO60B,CAAP,CAAa,CAC5C,IAAIz2B,EAASsR,CAAA,CAAOmlB,CAAP,CACb,OAAIz2B,EAAAqY,QAAJ,EAAsBrY,CAAAoI,SAAtB,CACSpI,CADT,CAGS25B,QAA0B,CAACjnC,CAAD,CAAOgV,CAAP,CAAe,CAC9C,MAAO2xB,EAAA/R,WAAA,CAAe1lB,CAAf;AAAqB5B,CAAA,CAAOtN,CAAP,CAAagV,CAAb,CAArB,CADuC,CALN,CAtDE,KAoT5CjU,EAAQ4lC,CAAAI,QApToC,CAqT5CnS,EAAa+R,CAAA/R,WArT+B,CAsT5CwR,EAAUO,CAAAP,QAEd3rC,EAAA,CAAQwqC,EAAR,CAAsB,QAAS,CAACiC,CAAD,CAAY/jC,CAAZ,CAAkB,CAC/C,IAAIgkC,EAAQjmC,CAAA,CAAUiC,CAAV,CACZwjC,EAAA,CAAIj7B,EAAA,CAAU,WAAV,CAAwBy7B,CAAxB,CAAJ,CAAA,CAAsC,QAAS,CAACpD,CAAD,CAAO,CACpD,MAAOhjC,EAAA,CAAMmmC,CAAN,CAAiBnD,CAAjB,CAD6C,CAGtD4C,EAAA,CAAIj7B,EAAA,CAAU,cAAV,CAA2By7B,CAA3B,CAAJ,CAAA,CAAyC,QAAS,CAAC3rC,CAAD,CAAQ,CACxD,MAAOo5B,EAAA,CAAWsS,CAAX,CAAsB1rC,CAAtB,CADiD,CAG1DmrC,EAAA,CAAIj7B,EAAA,CAAU,WAAV,CAAwBy7B,CAAxB,CAAJ,CAAA,CAAsC,QAAS,CAAC3rC,CAAD,CAAQ,CACrD,MAAO4qC,EAAA,CAAQc,CAAR,CAAmB1rC,CAAnB,CAD8C,CARR,CAAjD,CAaA,OAAOmrC,EArUyC,CADtC,CApEU,CA6ZxBv7B,QAASA,GAAgB,EAAG,CAC1B,IAAAyI,KAAA,CAAY,CAAC,SAAD,CAAY,WAAZ,CAAyB,QAAQ,CAAC0C,CAAD,CAAUiF,CAAV,CAAqB,CAAA,IAC5D4rB,EAAe,EAD6C,CAE5DC,EACE7qC,CAAA,CAAI,CAAC,eAAA8G,KAAA,CAAqBpC,CAAA,CAAWomC,CAAA/wB,CAAAgxB,UAAAD,EAAqB,EAArBA,WAAX,CAArB,CAAD,EAAyE,EAAzE,EAA6E,CAA7E,CAAJ,CAH0D,CAI5DE,EAAQ,QAAAljC,KAAA,CAAegjC,CAAA/wB,CAAAgxB,UAAAD,EAAqB,EAArBA,WAAf,CAJoD,CAK5DvtC,EAAWyhB,CAAA,CAAU,CAAV,CAAXzhB,EAA2B,EALiC,CAM5D0tC,EAAe1tC,CAAA0tC,aAN6C,CAO5DC,CAP4D,CAQ5DC,EAAc,6BAR8C,CAS5DC,EAAY7tC,CAAA64B,KAAZgV,EAA6B7tC,CAAA64B,KAAAiV,MAT+B;AAU5DC,EAAc,CAAA,CAV8C,CAW5DC,EAAa,CAAA,CAGjB,IAAIH,CAAJ,CAAe,CACb,IAAI7pC,IAAIA,CAAR,GAAgB6pC,EAAhB,CACE,GAAG/lC,CAAH,CAAW8lC,CAAArkC,KAAA,CAAiBvF,CAAjB,CAAX,CAAmC,CACjC2pC,CAAA,CAAe7lC,CAAA,CAAM,CAAN,CACf6lC,EAAA,CAAeA,CAAAllB,OAAA,CAAoB,CAApB,CAAuB,CAAvB,CAAA1W,YAAA,EAAf,CAAyD47B,CAAAllB,OAAA,CAAoB,CAApB,CACzD,MAHiC,CAOjCklB,CAAJ,GACEA,CADF,CACkB,eADlB,EACqCE,EADrC,EACmD,QADnD,CAIAE,EAAA,CAAc,CAAC,EAAG,YAAH,EAAmBF,EAAnB,EAAkCF,CAAlC,CAAiD,YAAjD,EAAiEE,EAAjE,CACfG,EAAA,CAAc,CAAC,EAAG,WAAH,EAAkBH,EAAlB,EAAiCF,CAAjC,CAAgD,WAAhD,EAA+DE,EAA/D,CAEXP,EAAAA,CAAJ,EAAiBS,CAAjB,EAA+BC,CAA/B,GACED,CACA,CADcvtC,CAAA,CAASR,CAAA64B,KAAAiV,MAAAG,iBAAT,CACd,CAAAD,CAAA,CAAaxtC,CAAA,CAASR,CAAA64B,KAAAiV,MAAAI,gBAAT,CAFf,CAhBa,CAuBf,MAAO,SAUI,EAAGpvB,CAAAtC,CAAAsC,QAAH,EAAsBgB,CAAAtD,CAAAsC,QAAAgB,UAAtB,EAA+D,CAA/D,CAAqDwtB,CAArD,EAAsEG,CAAtE,CAVJ,YAYO,cAZP,EAYyBjxB,EAZzB,GAcQ,CAACkxB,CAdT,EAcwC,CAdxC,CAcyBA,CAdzB,WAeKS,QAAQ,CAAC12B,CAAD,CAAQ,CAIxB,GAAa,OAAb,EAAIA,CAAJ,EAAgC,CAAhC,EAAwBc,CAAxB,CAAmC,MAAO,CAAA,CAE1C,IAAIpV,CAAA,CAAYkqC,CAAA,CAAa51B,CAAb,CAAZ,CAAJ,CAAsC,CACpC,IAAI22B,EAASpuC,CAAA8T,cAAA,CAAuB,KAAvB,CACbu5B,EAAA,CAAa51B,CAAb,CAAA,CAAsB,IAAtB;AAA6BA,CAA7B,GAAsC22B,EAFF,CAKtC,MAAOf,EAAA,CAAa51B,CAAb,CAXiB,CAfrB,KA4BA7R,EAAA,EA5BA,cA6BS+nC,CA7BT,aA8BSI,CA9BT,YA+BQC,CA/BR,SAgCIV,CAhCJ,MAiCE/0B,CAjCF,kBAkCam1B,CAlCb,CArCyD,CAAtD,CADc,CA6E5Bn8B,QAASA,GAAgB,EAAG,CAC1B,IAAAuI,KAAA,CAAY,CAAC,YAAD,CAAe,UAAf,CAA2B,IAA3B,CAAiC,mBAAjC,CACP,QAAQ,CAAC4C,CAAD,CAAe2X,CAAf,CAA2BC,CAA3B,CAAiCvQ,CAAjC,CAAoD,CA6B/D4T,QAASA,EAAO,CAACzxB,CAAD,CAAKkb,CAAL,CAAY+Z,CAAZ,CAAyB,CAAA,IACnCjE,EAAW5C,CAAApT,MAAA,EADwB,CAEnCgV,EAAUgB,CAAAhB,QAFyB,CAGnCoF,EAAal4B,CAAA,CAAU+3B,CAAV,CAAbG,EAAuC,CAACH,CAG5C9Z,EAAA,CAAYgT,CAAAnT,MAAA,CAAe,QAAQ,EAAG,CACpC,GAAI,CACFgW,CAAAC,QAAA,CAAiBjxB,CAAA,EAAjB,CADE,CAEF,MAAMuB,CAAN,CAAS,CACTyvB,CAAAvC,OAAA,CAAgBltB,CAAhB,CACA,CAAAsc,CAAA,CAAkBtc,CAAlB,CAFS,CAFX,OAMQ,CACN,OAAO4mC,CAAA,CAAUnY,CAAAoY,YAAV,CADD,CAIHhT,CAAL,EAAgB5e,CAAAtS,OAAA,EAXoB,CAA1B,CAYTgX,CAZS,CAcZ8U,EAAAoY,YAAA,CAAsBjtB,CACtBgtB,EAAA,CAAUhtB,CAAV,CAAA,CAAuB6V,CAEvB,OAAOhB,EAvBgC,CA5BzC,IAAImY,EAAY,EAmEhB1W,EAAArW,OAAA,CAAiBitB,QAAQ,CAACrY,CAAD,CAAU,CACjC,MAAIA,EAAJ,EAAeA,CAAAoY,YAAf,GAAsCD,EAAtC,EACEA,CAAA,CAAUnY,CAAAoY,YAAV,CAAA3Z,OAAA,CAAsC,UAAtC,CAEO;AADP,OAAO0Z,CAAA,CAAUnY,CAAAoY,YAAV,CACA,CAAAja,CAAAnT,MAAAI,OAAA,CAAsB4U,CAAAoY,YAAtB,CAHT,EAKO,CAAA,CAN0B,CASnC,OAAO3W,EA7EwD,CADrD,CADc,CAkJ5B4B,QAASA,GAAU,CAAC7a,CAAD,CAAM8vB,CAAN,CAAY,CAC7B,IAAI9uB,EAAOhB,CAEPnG,EAAJ,GAGEk2B,CAAAh4B,aAAA,CAA4B,MAA5B,CAAoCiJ,CAApC,CACA,CAAAA,CAAA,CAAO+uB,CAAA/uB,KAJT,CAOA+uB,EAAAh4B,aAAA,CAA4B,MAA5B,CAAoCiJ,CAApC,CAGA,OAAO,MACC+uB,CAAA/uB,KADD,UAEK+uB,CAAAjV,SAAA,CAA0BiV,CAAAjV,SAAAzxB,QAAA,CAAgC,IAAhC,CAAsC,EAAtC,CAA1B,CAAsE,EAF3E,MAGC0mC,CAAAv3B,KAHD,QAIGu3B,CAAAvR,OAAA,CAAwBuR,CAAAvR,OAAAn1B,QAAA,CAA8B,KAA9B,CAAqC,EAArC,CAAxB,CAAmE,EAJtE,MAKC0mC,CAAA3xB,KAAA,CAAsB2xB,CAAA3xB,KAAA/U,QAAA,CAA4B,IAA5B,CAAkC,EAAlC,CAAtB,CAA8D,EAL/D,UAMK0mC,CAAAjS,SANL,MAOCiS,CAAA/R,KAPD,UAQ4C,GACvC,GADC+R,CAAAzR,SAAA33B,OAAA,CAA+B,CAA/B,CACD,CAANopC,CAAAzR,SAAM,CACN,GADM,CACAyR,CAAAzR,SAVL,CAbsB,CAkC/BvH,QAASA,GAAe,CAACiZ,CAAD,CAAa,CAC/Bn7B,CAAAA,CAAU/S,CAAA,CAASkuC,CAAT,CAAD,CAAyBnV,EAAA,CAAWmV,CAAX,CAAzB,CAAkDA,CAC/D,OAAQn7B,EAAAimB,SAAR,GAA4BmV,EAAAnV,SAA5B,EACQjmB,CAAA2D,KADR,GACwBy3B,EAAAz3B,KAHW,CAr0bE;AAm3bvC1F,QAASA,GAAe,EAAE,CACxB,IAAAsI,KAAA,CAAY5W,EAAA,CAAQnD,CAAR,CADY,CA+E1B0Q,QAASA,GAAe,CAAC3G,CAAD,CAAW,CAWjCgpB,QAASA,EAAQ,CAAC1pB,CAAD,CAAOkD,CAAP,CAAgB,CAC/B,GAAGjJ,CAAA,CAAS+F,CAAT,CAAH,CAAmB,CACjB,IAAIwlC,EAAU,EACdluC,EAAA,CAAQ0I,CAAR,CAAc,QAAQ,CAACmJ,CAAD,CAAS1R,CAAT,CAAc,CAClC+tC,CAAA,CAAQ/tC,CAAR,CAAA,CAAeiyB,CAAA,CAASjyB,CAAT,CAAc0R,CAAd,CADmB,CAApC,CAGA,OAAOq8B,EALU,CAOjB,MAAO9kC,EAAAwC,QAAA,CAAiBlD,CAAjB,CAAwBylC,CAAxB,CAAgCviC,CAAhC,CARsB,CAVjC,IAAIuiC,EAAS,QAqBb,KAAA/b,SAAA,CAAgBA,CAEhB,KAAAhZ,KAAA,CAAY,CAAC,WAAD,CAAc,QAAQ,CAAC4B,CAAD,CAAY,CAC5C,MAAO,SAAQ,CAACtS,CAAD,CAAO,CACpB,MAAOsS,EAAArB,IAAA,CAAcjR,CAAd,CAAqBylC,CAArB,CADa,CADsB,CAAlC,CAoBZ/b,EAAA,CAAS,UAAT,CAAqBgc,EAArB,CACAhc,EAAA,CAAS,MAAT,CAAiBic,EAAjB,CACAjc,EAAA,CAAS,QAAT,CAAmBkc,EAAnB,CACAlc,EAAA,CAAS,MAAT,CAAiBmc,EAAjB,CACAnc,EAAA,CAAS,SAAT,CAAoBoc,EAApB,CACApc,EAAA,CAAS,WAAT,CAAsBqc,EAAtB,CACArc,EAAA,CAAS,QAAT,CAAmBsc,EAAnB,CACAtc,EAAA,CAAS,SAAT,CAAoBuc,EAApB,CACAvc,EAAA,CAAS,WAAT,CAAsBwc,EAAtB,CApDiC,CAwKnCN,QAASA,GAAY,EAAG,CACtB,MAAO,SAAQ,CAACzqC,CAAD,CAAQyuB,CAAR,CAAoBuc,CAApB,CAAgC,CAC7C,GAAI,CAAC9uC,CAAA,CAAQ8D,CAAR,CAAL,CAAqB,MAAOA,EADiB,KAGzCirC,EAAiB,MAAOD,EAHiB,CAIzCE,EAAa,EAEjBA,EAAAtxB,MAAA,CAAmBuxB,QAAQ,CAACjuC,CAAD,CAAQ,CACjC,IAAK,IAAI+S,EAAI,CAAb,CAAgBA,CAAhB,CAAoBi7B,CAAAnvC,OAApB,CAAuCkU,CAAA,EAAvC,CACE,GAAG,CAACi7B,CAAA,CAAWj7B,CAAX,CAAA,CAAc/S,CAAd,CAAJ,CACE,MAAO,CAAA,CAGX;MAAO,CAAA,CAN0B,CASZ,WAAvB,GAAI+tC,CAAJ,GAEID,CAFJ,CACyB,SAAvB,GAAIC,CAAJ,EAAoCD,CAApC,CACeA,QAAQ,CAACnvC,CAAD,CAAM2vB,CAAN,CAAY,CAC/B,MAAOvlB,GAAAlF,OAAA,CAAelF,CAAf,CAAoB2vB,CAApB,CADwB,CADnC,CAKewf,QAAQ,CAACnvC,CAAD,CAAM2vB,CAAN,CAAY,CAC/B,GAAI3vB,CAAJ,EAAW2vB,CAAX,EAAkC,QAAlC,GAAmB,MAAO3vB,EAA1B,EAA8D,QAA9D,GAA8C,MAAO2vB,EAArD,CAAwE,CACtE,IAAK4f,IAAIA,CAAT,GAAmBvvC,EAAnB,CACE,GAAyB,GAAzB,GAAIuvC,CAAAtqC,OAAA,CAAc,CAAd,CAAJ,EAAgCtE,EAAAC,KAAA,CAAoBZ,CAApB,CAAyBuvC,CAAzB,CAAhC,EACIJ,CAAA,CAAWnvC,CAAA,CAAIuvC,CAAJ,CAAX,CAAwB5f,CAAA,CAAK4f,CAAL,CAAxB,CADJ,CAEE,MAAO,CAAA,CAGX,OAAO,CAAA,CAP+D,CASxE5f,CAAA,CAAQ9kB,CAAA,EAAAA,CAAG8kB,CAAH9kB,aAAA,EACR,OAA+C,EAA/C,CAAQA,CAAA,EAAAA,CAAG7K,CAAH6K,aAAA,EAAA3G,QAAA,CAA8ByrB,CAA9B,CAXuB,CANrC,CAsBA,KAAImN,EAASA,QAAQ,CAAC98B,CAAD,CAAM2vB,CAAN,CAAW,CAC9B,GAAmB,QAAnB,EAAI,MAAOA,EAAX,EAAkD,GAAlD,GAA+BA,CAAA1qB,OAAA,CAAY,CAAZ,CAA/B,CACE,MAAO,CAAC63B,CAAA,CAAO98B,CAAP,CAAY2vB,CAAAtH,OAAA,CAAY,CAAZ,CAAZ,CAEV,QAAQ,MAAOroB,EAAf,EACE,KAAK,SAAL,CACA,KAAK,QAAL,CACA,KAAK,QAAL,CACE,MAAOmvC,EAAA,CAAWnvC,CAAX,CAAgB2vB,CAAhB,CACT,MAAK,QAAL,CACE,OAAQ,MAAOA,EAAf,EACE,KAAK,QAAL,CACE,MAAOwf,EAAA,CAAWnvC,CAAX;AAAgB2vB,CAAhB,CACT,SACE,IAAM4f,IAAIA,CAAV,GAAoBvvC,EAApB,CACE,GAAyB,GAAzB,GAAIuvC,CAAAtqC,OAAA,CAAc,CAAd,CAAJ,EAAgC63B,CAAA,CAAO98B,CAAA,CAAIuvC,CAAJ,CAAP,CAAoB5f,CAApB,CAAhC,CACE,MAAO,CAAA,CANf,CAWA,MAAO,CAAA,CACT,MAAK,OAAL,CACE,IAAUzuB,CAAV,CAAc,CAAd,CAAiBA,CAAjB,CAAqBlB,CAAAE,OAArB,CAAiCgB,CAAA,EAAjC,CACE,GAAI47B,CAAA,CAAO98B,CAAA,CAAIkB,CAAJ,CAAP,CAAeyuB,CAAf,CAAJ,CACE,MAAO,CAAA,CAGX,OAAO,CAAA,CACT,SACE,MAAO,CAAA,CA1BX,CAJ8B,CAiChC,QAAQ,MAAOiD,EAAf,EACE,KAAK,SAAL,CACA,KAAK,QAAL,CACA,KAAK,QAAL,CAEEA,CAAA,CAAa,GAAGA,CAAH,CAEf,MAAK,QAAL,CAEE,IAAKnyB,IAAIA,CAAT,GAAgBmyB,EAAhB,CACG,SAAQ,CAACtnB,CAAD,CAAO,CACiB,WAA/B,EAAI,MAAOsnB,EAAA,CAAWtnB,CAAX,CAAX,EACA+jC,CAAAtuC,KAAA,CAAgB,QAAQ,CAACM,CAAD,CAAQ,CAC9B,MAAOy7B,EAAA,CAAe,GAAR,EAAAxxB,CAAA,CAAcjK,CAAd,CAAuBA,CAAvB,EAAgCA,CAAA,CAAMiK,CAAN,CAAvC,CAAqDsnB,CAAA,CAAWtnB,CAAX,CAArD,CADuB,CAAhC,CAFc,CAAf,CAAA,CAKE7K,CALF,CAOH,MACF,MAAK,UAAL,CACE4uC,CAAAtuC,KAAA,CAAgB6xB,CAAhB,CACA,MACF,SACE,MAAOzuB,EAtBX,CAwBIqrC,CAAAA,CAAW,EACf,KAAUp7B,CAAV,CAAc,CAAd,CAAiBA,CAAjB,CAAqBjQ,CAAAjE,OAArB,CAAmCkU,CAAA,EAAnC,CAAwC,CACtC,IAAI/S,EAAQ8C,CAAA,CAAMiQ,CAAN,CACRi7B,EAAAtxB,MAAA,CAAiB1c,CAAjB,CAAJ,EACEmuC,CAAAzuC,KAAA,CAAcM,CAAd,CAHoC,CAMxC,MAAOmuC,EArGsC,CADzB,CA0JxBd,QAASA,GAAc,CAACe,CAAD,CAAU,CAC/B,IAAIC;AAAUD,CAAAE,eACd,OAAO,SAAQ,CAACC,CAAD,CAASC,CAAT,CAAwB,CACjC9sC,CAAA,CAAY8sC,CAAZ,CAAJ,GAAiCA,CAAjC,CAAkDH,CAAAI,aAAlD,CACA,OAAOC,GAAA,CAAaH,CAAb,CAAqBF,CAAAM,SAAA,CAAiB,CAAjB,CAArB,CAA0CN,CAAAO,UAA1C,CAA6DP,CAAAQ,YAA7D,CAAkF,CAAlF,CAAAvoC,QAAA,CACa,SADb,CACwBkoC,CADxB,CAF8B,CAFR,CA4DjCb,QAASA,GAAY,CAACS,CAAD,CAAU,CAC7B,IAAIC,EAAUD,CAAAE,eACd,OAAO,SAAQ,CAACQ,CAAD,CAASC,CAAT,CAAuB,CACpC,MAAOL,GAAA,CAAaI,CAAb,CAAqBT,CAAAM,SAAA,CAAiB,CAAjB,CAArB,CAA0CN,CAAAO,UAA1C,CAA6DP,CAAAQ,YAA7D,CACLE,CADK,CAD6B,CAFT,CAS/BL,QAASA,GAAY,CAACI,CAAD,CAASE,CAAT,CAAkBC,CAAlB,CAA4BC,CAA5B,CAAwCH,CAAxC,CAAsD,CACzE,GAAc,IAAd,EAAID,CAAJ,EAAsB,CAACK,QAAA,CAASL,CAAT,CAAvB,EAA2CltC,CAAA,CAASktC,CAAT,CAA3C,CAA6D,MAAO,EAEpE,KAAIM,EAAsB,CAAtBA,CAAaN,CACjBA,EAAA,CAASxiB,IAAA+iB,IAAA,CAASP,CAAT,CAJgE,KAKrEQ,EAASR,CAATQ,CAAkB,EALmD,CAMrEC,EAAe,EANsD,CAOrEzoC,EAAQ,EAP6D,CASrE0oC,EAAc,CAAA,CAClB,IAA6B,EAA7B,GAAIF,CAAAzsC,QAAA,CAAe,GAAf,CAAJ,CAAgC,CAC9B,IAAIwD,EAAQipC,CAAAjpC,MAAA,CAAa,qBAAb,CACRA,EAAJ,EAAyB,GAAzB,EAAaA,CAAA,CAAM,CAAN,CAAb,EAAgCA,CAAA,CAAM,CAAN,CAAhC,CAA2C0oC,CAA3C,CAA0D,CAA1D,CACEO,CADF,CACW,GADX,EAGEC,CACA,CADeD,CACf,CAAAE,CAAA,CAAc,CAAA,CAJhB,CAF8B,CAUhC,GAAKA,CAAL,CA2CqB,CAAnB,CAAIT,CAAJ,GAAkC,EAAlC,CAAwBD,CAAxB,EAAgD,CAAhD,CAAuCA,CAAvC,IACES,CADF,CACiBT,CAAAW,QAAA,CAAeV,CAAf,CADjB,CA3CF;IAAkB,CACZW,CAAAA,CAAe7wC,CAAAywC,CAAA1oC,MAAA,CAAaioC,EAAb,CAAA,CAA0B,CAA1B,CAAAhwC,EAAgC,EAAhCA,QAGf6C,EAAA,CAAYqtC,CAAZ,CAAJ,GACEA,CADF,CACiBziB,IAAAqjB,IAAA,CAASrjB,IAAAC,IAAA,CAASyiB,CAAAY,QAAT,CAA0BF,CAA1B,CAAT,CAAiDV,CAAAa,QAAjD,CADjB,CAIIC,EAAAA,CAAMxjB,IAAAwjB,IAAA,CAAS,EAAT,CAAaf,CAAb,CACVD,EAAA,CAASxiB,IAAAyjB,MAAA,CAAWjB,CAAX,CAAoBgB,CAApB,CAAT,CAAoCA,CAChCE,EAAAA,CAAYppC,CAAA,EAAAA,CAAKkoC,CAALloC,OAAA,CAAmBioC,EAAnB,CACZhT,EAAAA,CAAQmU,CAAA,CAAS,CAAT,CACZA,EAAA,CAAWA,CAAA,CAAS,CAAT,CAAX,EAA0B,EAEnBzmC,KAAAA,EAAM,CAANA,CACH0mC,EAASjB,CAAAkB,OADN3mC,CAEH4mC,EAAQnB,CAAAoB,MAEZ,IAAIvU,CAAAh9B,OAAJ,EAAqBoxC,CAArB,CAA8BE,CAA9B,CAEE,IADA5mC,CACK,CADCsyB,CAAAh9B,OACD,CADgBoxC,CAChB,CAAApwC,CAAA,CAAI,CAAT,CAAYA,CAAZ,CAAgB0J,CAAhB,CAAqB1J,CAAA,EAArB,CAC0B,CAGxB,IAHK0J,CAGL,CAHW1J,CAGX,EAHcswC,CAGd,EAHmC,CAGnC,GAH6BtwC,CAG7B,GAFE0vC,CAEF,EAFkBN,CAElB,EAAAM,CAAA,EAAgB1T,CAAAj4B,OAAA,CAAa/D,CAAb,CAIpB,KAAKA,CAAL,CAAS0J,CAAT,CAAc1J,CAAd,CAAkBg8B,CAAAh9B,OAAlB,CAAgCgB,CAAA,EAAhC,CACoC,CAGlC,IAHKg8B,CAAAh9B,OAGL,CAHoBgB,CAGpB,EAHuBowC,CAGvB,EAH6C,CAG7C,GAHuCpwC,CAGvC,GAFE0vC,CAEF,EAFkBN,CAElB,EAAAM,CAAA,EAAgB1T,CAAAj4B,OAAA,CAAa/D,CAAb,CAIlB,KAAA,CAAMmwC,CAAAnxC,OAAN,CAAwBkwC,CAAxB,CAAA,CACEiB,CAAA,EAAY,GAGVjB,EAAJ,EAAqC,GAArC,GAAoBA,CAApB,GAA0CQ,CAA1C,EAA0DL,CAA1D,CAAuEc,CAAAhpB,OAAA,CAAgB,CAAhB,CAAmB+nB,CAAnB,CAAvE,CAxCgB,CAgDlBjoC,CAAApH,KAAA,CAAW0vC,CAAA,CAAaJ,CAAAqB,OAAb,CAA8BrB,CAAAsB,OAAzC,CACAxpC,EAAApH,KAAA,CAAW6vC,CAAX,CACAzoC,EAAApH,KAAA,CAAW0vC,CAAA,CAAaJ,CAAAuB,OAAb,CAA8BvB,CAAAwB,OAAzC,CACA,OAAO1pC,EAAAxG,KAAA,CAAW,EAAX,CAvEkE,CA0E3EmwC,QAASA,GAAS,CAACpW,CAAD;AAAMqW,CAAN,CAAc9+B,CAAd,CAAoB,CACpC,IAAI++B,EAAM,EACA,EAAV,CAAItW,CAAJ,GACEsW,CACA,CADO,GACP,CAAAtW,CAAA,CAAM,CAACA,CAFT,CAKA,KADAA,CACA,CADM,EACN,CADWA,CACX,CAAMA,CAAAx7B,OAAN,CAAmB6xC,CAAnB,CAAA,CAA2BrW,CAAA,CAAM,GAAN,CAAYA,CACnCzoB,EAAJ,GACEyoB,CADF,CACQA,CAAArT,OAAA,CAAWqT,CAAAx7B,OAAX,CAAwB6xC,CAAxB,CADR,CAEA,OAAOC,EAAP,CAAatW,CAVuB,CActCuW,QAASA,EAAU,CAACjpC,CAAD,CAAOoZ,CAAP,CAAa1Q,CAAb,CAAqBuB,CAArB,CAA2B,CAC5CvB,CAAA,CAASA,CAAT,EAAmB,CACnB,OAAO,SAAQ,CAACwgC,CAAD,CAAO,CAChB7wC,CAAAA,CAAQ6wC,CAAA,CAAK,KAAL,CAAalpC,CAAb,CAAA,EACZ,IAAa,CAAb,CAAI0I,CAAJ,EAAkBrQ,CAAlB,CAA0B,CAACqQ,CAA3B,CACErQ,CAAA,EAASqQ,CACG,EAAd,GAAIrQ,CAAJ,EAA8B,GAA9B,EAAmBqQ,CAAnB,GAAmCrQ,CAAnC,CAA2C,EAA3C,CACA,OAAOywC,GAAA,CAAUzwC,CAAV,CAAiB+gB,CAAjB,CAAuBnP,CAAvB,CALa,CAFsB,CAW9Ck/B,QAASA,GAAa,CAACnpC,CAAD,CAAOopC,CAAP,CAAkB,CACtC,MAAO,SAAQ,CAACF,CAAD,CAAOxC,CAAP,CAAgB,CAC7B,IAAIruC,EAAQ6wC,CAAA,CAAK,KAAL,CAAalpC,CAAb,CAAA,EAAZ,CACIiR,EAAMhN,EAAA,CAAUmlC,CAAA,CAAa,OAAb,CAAuBppC,CAAvB,CAA+BA,CAAzC,CAEV,OAAO0mC,EAAA,CAAQz1B,CAAR,CAAA,CAAa5Y,CAAb,CAJsB,CADO,CAuIxCstC,QAASA,GAAU,CAACc,CAAD,CAAU,CAK3B4C,QAASA,EAAgB,CAACC,CAAD,CAAS,CAChC,IAAI5qC,CACJ,IAAIA,CAAJ,CAAY4qC,CAAA5qC,MAAA,CAAa6qC,CAAb,CAAZ,CAAyC,CACnCL,CAAAA,CAAO,IAAIttC,IAAJ,CAAS,CAAT,CAD4B,KAEnC4tC,EAAS,CAF0B,CAGnCC,EAAS,CAH0B,CAInCC,EAAahrC,CAAA,CAAM,CAAN,CAAA,CAAWwqC,CAAAS,eAAX,CAAiCT,CAAAU,YAJX,CAKnCC,EAAanrC,CAAA,CAAM,CAAN,CAAA,CAAWwqC,CAAAY,YAAX,CAA8BZ,CAAAa,SAE3CrrC,EAAA,CAAM,CAAN,CAAJ,GACE8qC,CACA,CADSnwC,CAAA,CAAIqF,CAAA,CAAM,CAAN,CAAJ,CAAeA,CAAA,CAAM,EAAN,CAAf,CACT,CAAA+qC,CAAA,CAAQpwC,CAAA,CAAIqF,CAAA,CAAM,CAAN,CAAJ,CAAeA,CAAA,CAAM,EAAN,CAAf,CAFV,CAIAgrC;CAAA9xC,KAAA,CAAgBsxC,CAAhB,CAAsB7vC,CAAA,CAAIqF,CAAA,CAAM,CAAN,CAAJ,CAAtB,CAAqCrF,CAAA,CAAIqF,CAAA,CAAM,CAAN,CAAJ,CAArC,CAAqD,CAArD,CAAwDrF,CAAA,CAAIqF,CAAA,CAAM,CAAN,CAAJ,CAAxD,CACI1F,EAAAA,CAAIK,CAAA,CAAIqF,CAAA,CAAM,CAAN,CAAJ,EAAc,CAAd,CAAJ1F,CAAuBwwC,CACvBQ,EAAAA,CAAI3wC,CAAA,CAAIqF,CAAA,CAAM,CAAN,CAAJ,EAAc,CAAd,CAAJsrC,CAAuBP,CACvBQ,EAAAA,CAAI5wC,CAAA,CAAIqF,CAAA,CAAM,CAAN,CAAJ,EAAc,CAAd,CACJwrC,EAAAA,CAAKvlB,IAAAyjB,MAAA,CAA8C,GAA9C,CAAW+B,UAAA,CAAW,IAAX,EAAmBzrC,CAAA,CAAM,CAAN,CAAnB,EAA6B,CAA7B,EAAX,CACTmrC,EAAAjyC,KAAA,CAAgBsxC,CAAhB,CAAsBlwC,CAAtB,CAAyBgxC,CAAzB,CAA4BC,CAA5B,CAA+BC,CAA/B,CAhBuC,CAmBzC,MAAOZ,EArByB,CAFlC,IAAIC,EAAgB,sGA2BpB,OAAO,SAAQ,CAACL,CAAD,CAAOkB,CAAP,CAAe,CAAA,IACxBzjB,EAAO,EADiB,CAExBxnB,EAAQ,EAFgB,CAGxBrC,CAHwB,CAGpB4B,CAER0rC,EAAA,CAASA,CAAT,EAAmB,YACnBA,EAAA,CAAS3D,CAAA4D,iBAAA,CAAyBD,CAAzB,CAAT,EAA6CA,CACzChzC,EAAA,CAAS8xC,CAAT,CAAJ,GAEIA,CAFJ,CACMoB,EAAAnpC,KAAA,CAAmB+nC,CAAnB,CAAJ,CACS7vC,CAAA,CAAI6vC,CAAJ,CADT,CAGSG,CAAA,CAAiBH,CAAjB,CAJX,CAQIhvC,GAAA,CAASgvC,CAAT,CAAJ,GACEA,CADF,CACS,IAAIttC,IAAJ,CAASstC,CAAT,CADT,CAIA,IAAI,CAAC/uC,EAAA,CAAO+uC,CAAP,CAAL,CACE,MAAOA,EAGT,KAAA,CAAMkB,CAAN,CAAA,CAEE,CADA1rC,CACA,CADQ6rC,EAAApqC,KAAA,CAAwBiqC,CAAxB,CACR,GACEjrC,CACA,CADeA,CA9pbdhC,OAAA,CAAcH,EAAApF,KAAA,CA8pbO8G,CA9pbP,CA8pbcnG,CA9pbd,CAAd,CA+pbD,CAAA6xC,CAAA,CAASjrC,CAAAuV,IAAA,EAFX,GAIEvV,CAAApH,KAAA,CAAWqyC,CAAX,CACA,CAAAA,CAAA,CAAS,IALX,CASF9yC,EAAA,CAAQ6H,CAAR,CAAe,QAAQ,CAAC9G,CAAD,CAAO,CAC5ByE,CAAA;AAAK0tC,EAAA,CAAanyC,CAAb,CACLsuB,EAAA,EAAQ7pB,CAAA,CAAKA,CAAA,CAAGosC,CAAH,CAASzC,CAAA4D,iBAAT,CAAL,CACKhyC,CAAAsG,QAAA,CAAc,UAAd,CAA0B,EAA1B,CAAAA,QAAA,CAAsC,KAAtC,CAA6C,GAA7C,CAHe,CAA9B,CAMA,OAAOgoB,EAxCqB,CA9BH,CAuG7Bkf,QAASA,GAAU,EAAG,CACpB,MAAO,SAAQ,CAAC4E,CAAD,CAAS,CACtB,MAAOntC,GAAA,CAAOmtC,CAAP,CAAe,CAAA,CAAf,CADe,CADJ,CAiGtB3E,QAASA,GAAa,EAAE,CACtB,MAAO,SAAQ,CAAC4E,CAAD,CAAQC,CAAR,CAAe,CAC5B,GAAI,CAACtzC,CAAA,CAAQqzC,CAAR,CAAL,EAAuB,CAACtzC,CAAA,CAASszC,CAAT,CAAxB,CAAyC,MAAOA,EAEhDC,EAAA,CAAQtxC,CAAA,CAAIsxC,CAAJ,CAER,IAAIvzC,CAAA,CAASszC,CAAT,CAAJ,CAEE,MAAIC,EAAJ,CACkB,CAAT,EAAAA,CAAA,CAAaD,CAAA1tC,MAAA,CAAY,CAAZ,CAAe2tC,CAAf,CAAb,CAAqCD,CAAA1tC,MAAA,CAAY2tC,CAAZ,CAAmBD,CAAAxzC,OAAnB,CAD9C,CAGS,EAViB,KAcxB0zC,EAAM,EAdkB,CAe1B1yC,CAf0B,CAevB4gB,CAGD6xB,EAAJ,CAAYD,CAAAxzC,OAAZ,CACEyzC,CADF,CACUD,CAAAxzC,OADV,CAESyzC,CAFT,CAEiB,CAACD,CAAAxzC,OAFlB,GAGEyzC,CAHF,CAGU,CAACD,CAAAxzC,OAHX,CAKY,EAAZ,CAAIyzC,CAAJ,EACEzyC,CACA,CADI,CACJ,CAAA4gB,CAAA,CAAI6xB,CAFN,GAIEzyC,CACA,CADIwyC,CAAAxzC,OACJ,CADmByzC,CACnB,CAAA7xB,CAAA,CAAI4xB,CAAAxzC,OALN,CAQA,KAAA,CAAOgB,CAAP,CAAS4gB,CAAT,CAAY5gB,CAAA,EAAZ,CACE0yC,CAAA7yC,KAAA,CAAS2yC,CAAA,CAAMxyC,CAAN,CAAT,CAGF,OAAO0yC,EAnCqB,CADR,CAqGxB3E,QAASA,GAAa,CAACxqB,CAAD,CAAQ,CAC5B,MAAO,SAAQ,CAACtgB,CAAD,CAAQ0vC,CAAR,CAAuBC,CAAvB,CAAqC,CAkClDC,QAASA,EAAiB,CAACC,CAAD,CAAOC,CAAP,CAAmB,CAC3C,MAAOptC,GAAA,CAAUotC,CAAV,CACA,CAAD,QAAQ,CAACxoB,CAAD,CAAGC,CAAH,CAAK,CAAC,MAAOsoB,EAAA,CAAKtoB,CAAL,CAAOD,CAAP,CAAR,CAAZ,CACDuoB,CAHqC,CAlCK;AAuClD7oB,QAASA,EAAO,CAAC+oB,CAAD,CAAKC,CAAL,CAAQ,CACtB,IAAI9uC,EAAK,MAAO6uC,EAAhB,CACI5uC,EAAK,MAAO6uC,EAChB,OAAI9uC,EAAJ,EAAUC,CAAV,EACY,QAIV,EAJID,CAIJ,GAHG6uC,CACA,CADKA,CAAArpC,YAAA,EACL,CAAAspC,CAAA,CAAKA,CAAAtpC,YAAA,EAER,EAAIqpC,CAAJ,GAAWC,CAAX,CAAsB,CAAtB,CACOD,CAAA,CAAKC,CAAL,CAAW,EAAX,CAAe,CANxB,EAQS9uC,CAAA,CAAKC,CAAL,CAAW,EAAX,CAAe,CAXF,CArCxB,GADI,CAACjF,CAAA,CAAQ8D,CAAR,CACL,EAAI,CAAC0vC,CAAL,CAAoB,MAAO1vC,EAC3B0vC,EAAA,CAAgBxzC,CAAA,CAAQwzC,CAAR,CAAA,CAAyBA,CAAzB,CAAwC,CAACA,CAAD,CACxDA,EAAA,CAAgB9vC,EAAA,CAAI8vC,CAAJ,CAAmB,QAAQ,CAACO,CAAD,CAAW,CAAA,IAChDH,EAAa,CAAA,CADmC,CAC5Bh6B,EAAMm6B,CAANn6B,EAAmBrX,EAC3C,IAAIxC,CAAA,CAASg0C,CAAT,CAAJ,CAAyB,CACvB,GAA4B,GAA5B,EAAKA,CAAAnvC,OAAA,CAAiB,CAAjB,CAAL,EAA0D,GAA1D,EAAmCmvC,CAAAnvC,OAAA,CAAiB,CAAjB,CAAnC,CACEgvC,CACA,CADoC,GACpC,EADaG,CAAAnvC,OAAA,CAAiB,CAAjB,CACb,CAAAmvC,CAAA,CAAYA,CAAAvzB,UAAA,CAAoB,CAApB,CAEd5G,EAAA,CAAMwK,CAAA,CAAO2vB,CAAP,CACN,IAAIn6B,CAAAsB,SAAJ,CAAkB,CAChB,IAAI9a,EAAMwZ,CAAA,EACV,OAAO85B,EAAA,CAAkB,QAAQ,CAACtoB,CAAD,CAAGC,CAAH,CAAM,CACrC,MAAOP,EAAA,CAAQM,CAAA,CAAEhrB,CAAF,CAAR,CAAgBirB,CAAA,CAAEjrB,CAAF,CAAhB,CAD8B,CAAhC,CAEJwzC,CAFI,CAFS,CANK,CAazB,MAAOF,EAAA,CAAkB,QAAQ,CAACtoB,CAAD,CAAGC,CAAH,CAAK,CACpC,MAAOP,EAAA,CAAQlR,CAAA,CAAIwR,CAAJ,CAAR,CAAexR,CAAA,CAAIyR,CAAJ,CAAf,CAD6B,CAA/B,CAEJuoB,CAFI,CAf6C,CAAtC,CAoBhB,KADA,IAAII,EAAY,EAAhB,CACUnzC,EAAI,CAAd,CAAiBA,CAAjB,CAAqBiD,CAAAjE,OAArB,CAAmCgB,CAAA,EAAnC,CAA0CmzC,CAAAtzC,KAAA,CAAeoD,CAAA,CAAMjD,CAAN,CAAf,CAC1C,OAAOmzC,EAAArzC,KAAA,CAAe+yC,CAAA,CAEtB5E,QAAmB,CAAChqC,CAAD,CAAKC,CAAL,CAAQ,CACzB,IAAM,IAAIlE;AAAI,CAAd,CAAiBA,CAAjB,CAAqB2yC,CAAA3zC,OAArB,CAA2CgB,CAAA,EAA3C,CAAgD,CAC9C,IAAI8yC,EAAOH,CAAA,CAAc3yC,CAAd,CAAA,CAAiBiE,CAAjB,CAAqBC,CAArB,CACX,IAAa,CAAb,GAAI4uC,CAAJ,CAAgB,MAAOA,EAFuB,CAIhD,MAAO,EALkB,CAFL,CAA8BF,CAA9B,CAAf,CAzB2C,CADxB,CAyD9BQ,QAASA,GAAW,CAAC/mC,CAAD,CAAY,CAC1B7M,CAAA,CAAW6M,CAAX,CAAJ,GACEA,CADF,CACc,MACJA,CADI,CADd,CAKAA,EAAAyW,SAAA,CAAqBzW,CAAAyW,SAArB,EAA2C,IAC3C,OAAOlhB,GAAA,CAAQyK,CAAR,CAPuB,CAqfhCgnC,QAASA,GAAc,CAACttC,CAAD,CAAU6f,CAAV,CAAiBmF,CAAjB,CAAyBrH,CAAzB,CAAmC,CAqBxD4vB,QAASA,EAAc,CAACC,CAAD,CAAUC,CAAV,CAA8B,CACnDA,CAAA,CAAqBA,CAAA,CAAqB,GAArB,CAA2BlqC,EAAA,CAAWkqC,CAAX,CAA+B,GAA/B,CAA3B,CAAiE,EACtF9vB,EAAA0M,YAAA,CAAqBrqB,CAArB,EAA+BwtC,CAAA,CAAUE,EAAV,CAA0BC,EAAzD,EAAwEF,CAAxE,CACA9vB,EAAAkB,SAAA,CAAkB7e,CAAlB,EAA4BwtC,CAAA,CAAUG,EAAV,CAAwBD,EAApD,EAAqED,CAArE,CAHmD,CArBG,IACpDG,EAAO,IAD6C,CAEpDC,EAAa7tC,CAAAxE,OAAA,EAAAshB,WAAA,CAA4B,MAA5B,CAAb+wB,EAAoDC,EAFA,CAGpDC,EAAe,CAHqC,CAIpDC,EAASJ,CAAAK,OAATD,CAAuB,EAJ6B,CAKpDE,EAAW,EAGfN,EAAAO,MAAA,CAAatuB,CAAA9d,KAAb,EAA2B8d,CAAAuuB,OAC3BR,EAAAS,OAAA,CAAc,CAAA,CACdT,EAAAU,UAAA,CAAiB,CAAA,CACjBV,EAAAW,OAAA,CAAc,CAAA,CACdX,EAAAY,SAAA,CAAgB,CAAA,CAEhBX,EAAAY,YAAA,CAAuBb,CAAvB,CAGA5tC,EAAA6e,SAAA,CAAiB6vB,EAAjB,CACAnB,EAAA,CAAe,CAAA,CAAf,CAkBAK,EAAAa,YAAA,CAAmBE,QAAQ,CAACC,CAAD,CAAU,CAGnCzqC,EAAA,CAAwByqC,CAAAT,MAAxB,CAAuC,OAAvC,CACAD,EAAAp0C,KAAA,CAAc80C,CAAd,CAEIA,EAAAT,MAAJ;CACEP,CAAA,CAAKgB,CAAAT,MAAL,CADF,CACwBS,CADxB,CANmC,CAoBrChB,EAAAiB,eAAA,CAAsBC,QAAQ,CAACF,CAAD,CAAU,CAClCA,CAAAT,MAAJ,EAAqBP,CAAA,CAAKgB,CAAAT,MAAL,CAArB,GAA6CS,CAA7C,EACE,OAAOhB,CAAA,CAAKgB,CAAAT,MAAL,CAET90C,EAAA,CAAQ20C,CAAR,CAAgB,QAAQ,CAACe,CAAD,CAAQC,CAAR,CAAyB,CAC/CpB,CAAAqB,aAAA,CAAkBD,CAAlB,CAAmC,CAAA,CAAnC,CAAyCJ,CAAzC,CAD+C,CAAjD,CAIAzxC,GAAA,CAAY+wC,CAAZ,CAAsBU,CAAtB,CARsC,CAoBxChB,EAAAqB,aAAA,CAAoBC,QAAQ,CAACF,CAAD,CAAkBxB,CAAlB,CAA2BoB,CAA3B,CAAoC,CAC9D,IAAIG,EAAQf,CAAA,CAAOgB,CAAP,CAEZ,IAAIxB,CAAJ,CACMuB,CAAJ,GACE5xC,EAAA,CAAY4xC,CAAZ,CAAmBH,CAAnB,CACA,CAAKG,CAAA91C,OAAL,GACE80C,CAAA,EAQA,CAPKA,CAOL,GANER,CAAA,CAAeC,CAAf,CAEA,CADAI,CAAAW,OACA,CADc,CAAA,CACd,CAAAX,CAAAY,SAAA,CAAgB,CAAA,CAIlB,EAFAR,CAAA,CAAOgB,CAAP,CAEA,CAF0B,CAAA,CAE1B,CADAzB,CAAA,CAAe,CAAA,CAAf,CAAqByB,CAArB,CACA,CAAAnB,CAAAoB,aAAA,CAAwBD,CAAxB,CAAyC,CAAA,CAAzC,CAA+CpB,CAA/C,CATF,CAFF,CADF,KAgBO,CACAG,CAAL,EACER,CAAA,CAAeC,CAAf,CAEF,IAAIuB,CAAJ,CACE,IAtwdyB,EAswdzB,EAtwdC9xC,EAAA,CAswdY8xC,CAtwdZ,CAswdmBH,CAtwdnB,CAswdD,CAA8B,MAA9B,CADF,IAGEZ,EAAA,CAAOgB,CAAP,CAGA,CAH0BD,CAG1B,CAHkC,EAGlC,CAFAhB,CAAA,EAEA,CADAR,CAAA,CAAe,CAAA,CAAf,CAAsByB,CAAtB,CACA,CAAAnB,CAAAoB,aAAA,CAAwBD,CAAxB,CAAyC,CAAA,CAAzC,CAAgDpB,CAAhD,CAEFmB,EAAAj1C,KAAA,CAAW80C,CAAX,CAEAhB,EAAAW,OAAA,CAAc,CAAA,CACdX,EAAAY,SAAA,CAAgB,CAAA,CAfX,CAnBuD,CAgDhEZ,EAAAuB,UAAA,CAAiBC,QAAQ,EAAG,CAC1BzxB,CAAA0M,YAAA,CAAqBrqB,CAArB,CAA8B0uC,EAA9B,CACA/wB,EAAAkB,SAAA,CAAkB7e,CAAlB,CAA2BqvC,EAA3B,CACAzB,EAAAS,OAAA,CAAc,CAAA,CACdT,EAAAU,UAAA;AAAiB,CAAA,CACjBT,EAAAsB,UAAA,EAL0B,CAsB5BvB,EAAA0B,aAAA,CAAoBC,QAAS,EAAG,CAC9B5xB,CAAA0M,YAAA,CAAqBrqB,CAArB,CAA8BqvC,EAA9B,CACA1xB,EAAAkB,SAAA,CAAkB7e,CAAlB,CAA2B0uC,EAA3B,CACAd,EAAAS,OAAA,CAAc,CAAA,CACdT,EAAAU,UAAA,CAAiB,CAAA,CACjBj1C,EAAA,CAAQ60C,CAAR,CAAkB,QAAQ,CAACU,CAAD,CAAU,CAClCA,CAAAU,aAAA,EADkC,CAApC,CAL8B,CAlJwB,CAwyB1DE,QAASA,GAAQ,CAACC,CAAD,CAAOC,CAAP,CAAsBC,CAAtB,CAAgCv1C,CAAhC,CAAsC,CACrDq1C,CAAAR,aAAA,CAAkBS,CAAlB,CAAiCC,CAAjC,CACA,OAAOA,EAAA,CAAWv1C,CAAX,CAAmBxB,CAF2B,CAMvDg3C,QAASA,GAAwB,CAACH,CAAD,CAAOC,CAAP,CAAsB1vC,CAAtB,CAA+B,CAC9D,IAAI2vC,EAAW3vC,CAAArD,KAAA,CAAa,UAAb,CACXX,EAAA,CAAS2zC,CAAT,CAAJ,EAWEF,CAAAI,SAAA/1C,KAAA,CAVgBg2C,QAAQ,CAAC11C,CAAD,CAAQ,CAG9B,GAAKq1C,CAAAxB,OAAA,CAAYyB,CAAZ,CAAL,EAAoC,EAAAC,CAAAI,SAAA,EAAqBJ,CAAAK,YAArB,EAChCL,CAAAM,aADgC,CAApC,EAC+BN,CAAAO,aAD/B,CAKA,MAAO91C,EAHLq1C,EAAAR,aAAA,CAAkBS,CAAlB,CAAiC,CAAA,CAAjC,CAL4B,CAUhC,CAb4D,CAiBhES,QAASA,GAAa,CAACvtC,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB6yC,CAAvB,CAA6Bp5B,CAA7B,CAAuC2W,CAAvC,CAAiD,CACrE,IAAI2iB,EAAW3vC,CAAArD,KAAA,CAAa,UAAb,CAIf,IAAI,CAAC0Z,CAAA4vB,QAAL,CAAuB,CACrB,IAAImK,EAAY,CAAA,CAEhBpwC,EAAA6Y,GAAA,CAAW,kBAAX,CAA+B,QAAQ,CAAC7V,CAAD,CAAO,CAC5CotC,CAAA,CAAY,CAAA,CADgC,CAA9C,CAIApwC;CAAA6Y,GAAA,CAAW,gBAAX,CAA6B,QAAQ,EAAG,CACtCu3B,CAAA,CAAY,CAAA,CACZ74B,EAAA,EAFsC,CAAxC,CAPqB,CAavB,IAAIA,EAAWA,QAAQ,EAAG,CACxB,GAAI64B,CAAAA,CAAJ,CAAA,CACA,IAAIh2C,EAAQ4F,CAAAZ,IAAA,EAKRQ,GAAA,CAAUhD,CAAAyzC,OAAV,EAAyB,GAAzB,CAAJ,GACEj2C,CADF,CACU4R,EAAA,CAAK5R,CAAL,CADV,CAIA,IAAIq1C,CAAAa,WAAJ,GAAwBl2C,CAAxB,EAIKu1C,CAJL,EAI2B,EAJ3B,GAIiBv1C,CAJjB,EAIiC,CAACu1C,CAAAO,aAJlC,CAKMttC,CAAAgtB,QAAJ,CACE6f,CAAAc,cAAA,CAAmBn2C,CAAnB,CADF,CAGEwI,CAAAG,OAAA,CAAa,QAAQ,EAAG,CACtB0sC,CAAAc,cAAA,CAAmBn2C,CAAnB,CADsB,CAAxB,CAlBJ,CADwB,CA4B1B,IAAIic,CAAAywB,SAAA,CAAkB,OAAlB,CAAJ,CACE9mC,CAAA6Y,GAAA,CAAW,OAAX,CAAoBtB,CAApB,CADF,KAEO,CACL,IAAI+Y,CAAJ,CAEIkgB,EAAgBA,QAAQ,EAAG,CACxBlgB,CAAL,GACEA,CADF,CACYtD,CAAAnT,MAAA,CAAe,QAAQ,EAAG,CAClCtC,CAAA,EACA+Y,EAAA,CAAU,IAFwB,CAA1B,CADZ,CAD6B,CAS/BtwB,EAAA6Y,GAAA,CAAW,SAAX,CAAsB,QAAQ,CAACzI,CAAD,CAAQ,CAChC5W,CAAAA,CAAM4W,CAAAqgC,QAIE,GAAZ,GAAIj3C,CAAJ,GAAmB,EAAnB,CAAwBA,CAAxB,EAAqC,EAArC,CAA+BA,CAA/B,EAA6C,EAA7C,EAAmDA,CAAnD,EAAiE,EAAjE,EAA0DA,CAA1D,GAEAg3C,CAAA,EAPoC,CAAtC,CAWA,IAAIn6B,CAAAywB,SAAA,CAAkB,OAAlB,CAAJ,CACE9mC,CAAA6Y,GAAA,CAAW,WAAX,CAAwB23B,CAAxB,CAxBG,CA8BPxwC,CAAA6Y,GAAA,CAAW,QAAX,CAAqBtB,CAArB,CAEAk4B,EAAAiB,QAAA,CAAeC,QAAQ,EAAG,CACxB3wC,CAAAZ,IAAA,CAAYqwC,CAAAmB,SAAA,CAAcnB,CAAAa,WAAd,CAAA;AAAiC,EAAjC,CAAsCb,CAAAa,WAAlD,CADwB,CAhF2C,KAqFjElH,EAAUxsC,CAAAi0C,UAIVzH,EAAJ,GAKE,CADA3oC,CACA,CADQ2oC,CAAA3oC,MAAA,CAAc,oBAAd,CACR,GACE2oC,CACA,CADcvrC,MAAJ,CAAW4C,CAAA,CAAM,CAAN,CAAX,CAAqBA,CAAA,CAAM,CAAN,CAArB,CACV,CAAAqwC,CAAA,CAAmBA,QAAQ,CAAC12C,CAAD,CAAQ,CACjC,MANKo1C,GAAA,CAASC,CAAT,CAAe,SAAf,CAA0BA,CAAAmB,SAAA,CAMDx2C,CANC,CAA1B,EAMgBgvC,CANkClmC,KAAA,CAMzB9I,CANyB,CAAlD,CAMyBA,CANzB,CAK4B,CAFrC,EAME02C,CANF,CAMqBA,QAAQ,CAAC12C,CAAD,CAAQ,CACjC,IAAI22C,EAAanuC,CAAA0/B,MAAA,CAAY8G,CAAZ,CAEjB,IAAI,CAAC2H,CAAL,EAAmB,CAACA,CAAA7tC,KAApB,CACE,KAAMrK,EAAA,CAAO,WAAP,CAAA,CAAoB,UAApB,CACqDuwC,CADrD,CAEJ2H,CAFI,CAEQhxC,EAAA,CAAYC,CAAZ,CAFR,CAAN,CAIF,MAjBKwvC,GAAA,CAASC,CAAT,CAAe,SAAf,CAA0BA,CAAAmB,SAAA,CAiBEx2C,CAjBF,CAA1B,EAiBgB22C,CAjBkC7tC,KAAA,CAiBtB9I,CAjBsB,CAAlD,CAiB4BA,CAjB5B,CAS4B,CAarC,CADAq1C,CAAAuB,YAAAl3C,KAAA,CAAsBg3C,CAAtB,CACA,CAAArB,CAAAI,SAAA/1C,KAAA,CAAmBg3C,CAAnB,CAxBF,CA4BA,IAAIl0C,CAAAq0C,YAAJ,CAAsB,CACpB,IAAIC,EAAY91C,CAAA,CAAIwB,CAAAq0C,YAAJ,CACZE,EAAAA,CAAqBA,QAAQ,CAAC/2C,CAAD,CAAQ,CACvC,MAAOo1C,GAAA,CAASC,CAAT,CAAe,WAAf,CAA4BA,CAAAmB,SAAA,CAAcx2C,CAAd,CAA5B,EAAoDA,CAAAnB,OAApD,EAAoEi4C,CAApE,CAA+E92C,CAA/E,CADgC,CAIzCq1C,EAAAI,SAAA/1C,KAAA,CAAmBq3C,CAAnB,CACA1B,EAAAuB,YAAAl3C,KAAA,CAAsBq3C,CAAtB,CAPoB,CAWtB,GAAIv0C,CAAAw0C,YAAJ,CAAsB,CACpB,IAAIC;AAAYj2C,CAAA,CAAIwB,CAAAw0C,YAAJ,CACZE,EAAAA,CAAqBA,QAAQ,CAACl3C,CAAD,CAAQ,CACvC,MAAOo1C,GAAA,CAASC,CAAT,CAAe,WAAf,CAA4BA,CAAAmB,SAAA,CAAcx2C,CAAd,CAA5B,EAAoDA,CAAAnB,OAApD,EAAoEo4C,CAApE,CAA+Ej3C,CAA/E,CADgC,CAIzCq1C,EAAAI,SAAA/1C,KAAA,CAAmBw3C,CAAnB,CACA7B,EAAAuB,YAAAl3C,KAAA,CAAsBw3C,CAAtB,CAPoB,CAhI+C,CAyyCvEC,QAASA,GAAc,CAACxvC,CAAD,CAAOiN,CAAP,CAAiB,CACtCjN,CAAA,CAAO,SAAP,CAAmBA,CACnB,OAAO,CAAC,UAAD,CAAa,QAAQ,CAAC4b,CAAD,CAAW,CAiFrC6zB,QAASA,EAAe,CAACnmB,CAAD,CAAUC,CAAV,CAAmB,CACzC,IAAIF,EAAS,EAAb,CAGQnxB,EAAI,CADZ,EAAA,CACA,IAAA,CAAeA,CAAf,CAAmBoxB,CAAApyB,OAAnB,CAAmCgB,CAAA,EAAnC,CAAwC,CAEtC,IADA,IAAIsxB,EAAQF,CAAA,CAAQpxB,CAAR,CAAZ,CACQkT,EAAI,CAAZ,CAAeA,CAAf,CAAmBme,CAAAryB,OAAnB,CAAmCkU,CAAA,EAAnC,CACE,GAAGoe,CAAH,EAAYD,CAAA,CAAQne,CAAR,CAAZ,CAAwB,SAAS,CAEnCie,EAAAtxB,KAAA,CAAYyxB,CAAZ,CALsC,CAOxC,MAAOH,EAXkC,CAc3CqmB,QAASA,EAAa,CAACtnB,CAAD,CAAW,CAC/B,GAAI,CAAA/wB,CAAA,CAAQ+wB,CAAR,CAAJ,CAEO,CAAA,GAAIhxB,CAAA,CAASgxB,CAAT,CAAJ,CACL,MAAOA,EAAAnpB,MAAA,CAAe,GAAf,CACF,IAAIhF,CAAA,CAASmuB,CAAT,CAAJ,CAAwB,CAAA,IACzBunB,EAAU,EACdr4C,EAAA,CAAQ8wB,CAAR,CAAkB,QAAQ,CAACtqB,CAAD,CAAIkqB,CAAJ,CAAO,CAC3BlqB,CAAJ,EACE6xC,CAAA53C,KAAA,CAAaiwB,CAAb,CAF6B,CAAjC,CAKA,OAAO2nB,EAPsB,CAFxB,CAWP,MAAOvnB,EAdwB,CA9FjC,MAAO,UACK,IADL,MAECrP,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CAiCnC+0C,QAASA,EAAkB,CAACD,CAAD,CAAU7d,CAAV,CAAiB,CAC1C,IAAI+d;AAAc5xC,CAAAgD,KAAA,CAAa,cAAb,CAAd4uC,EAA8C,EAAlD,CACIC,EAAkB,EACtBx4C,EAAA,CAAQq4C,CAAR,CAAiB,QAAS,CAACvvC,CAAD,CAAY,CACpC,GAAY,CAAZ,CAAI0xB,CAAJ,EAAiB+d,CAAA,CAAYzvC,CAAZ,CAAjB,CACEyvC,CAAA,CAAYzvC,CAAZ,CACA,EAD0ByvC,CAAA,CAAYzvC,CAAZ,CAC1B,EADoD,CACpD,EADyD0xB,CACzD,CAAI+d,CAAA,CAAYzvC,CAAZ,CAAJ,GAA+B,EAAU,CAAV,CAAE0xB,CAAF,CAA/B,EACEge,CAAA/3C,KAAA,CAAqBqI,CAArB,CAJgC,CAAtC,CAQAnC,EAAAgD,KAAA,CAAa,cAAb,CAA6B4uC,CAA7B,CACA,OAAOC,EAAAn3C,KAAA,CAAqB,GAArB,CAZmC,CA8B5Co3C,QAASA,EAAkB,CAACjR,CAAD,CAAS,CAClC,GAAiB,CAAA,CAAjB,GAAI7xB,CAAJ,EAAyBpM,CAAAmvC,OAAzB,CAAwC,CAAxC,GAA8C/iC,CAA9C,CAAwD,CACtD,IAAIsb,EAAamnB,CAAA,CAAa5Q,CAAb,EAAuB,EAAvB,CACjB,IAAI,CAACC,CAAL,CAAa,CA1Cf,IAAIxW,EAAaqnB,CAAA,CA2CFrnB,CA3CE,CAA2B,CAA3B,CACjB1tB,EAAAstB,UAAA,CAAeI,CAAf,CAyCe,CAAb,IAEO,IAAI,CAACrsB,EAAA,CAAO4iC,CAAP,CAAcC,CAAd,CAAL,CAA4B,CAEnB9Y,IAAAA,EADGypB,CAAAzpB,CAAa8Y,CAAb9Y,CACHA,CArBduC,EAAQinB,CAAA,CAqBkBlnB,CArBlB,CAA4BtC,CAA5B,CAqBMA,CApBdyC,EAAW+mB,CAAA,CAAgBxpB,CAAhB,CAoBesC,CApBf,CAoBGtC,CAnBlByC,EAAWknB,CAAA,CAAkBlnB,CAAlB,CAA6B,EAA7B,CAmBOzC,CAlBlBuC,EAAQonB,CAAA,CAAkBpnB,CAAlB,CAAyB,CAAzB,CAEa,EAArB,GAAIA,CAAAtxB,OAAJ,CACE0kB,CAAA0M,YAAA,CAAqBrqB,CAArB,CAA8ByqB,CAA9B,CADF,CAE+B,CAAxB,GAAIA,CAAAxxB,OAAJ,CACL0kB,CAAAkB,SAAA,CAAkB7e,CAAlB,CAA2BuqB,CAA3B,CADK,CAGL5M,CAAA+M,SAAA,CAAkB1qB,CAAlB,CAA2BuqB,CAA3B,CAAkCE,CAAlC,CASmC,CAJmB,CASxDqW,CAAA,CAASzjC,EAAA,CAAKwjC,CAAL,CAVyB,CA9DpC,IAAIC,CAEJl+B,EAAAnF,OAAA,CAAab,CAAA,CAAKmF,CAAL,CAAb,CAAyB+vC,CAAzB,CAA6C,CAAA,CAA7C,CAEAl1C,EAAAwnB,SAAA,CAAc,OAAd,CAAuB,QAAQ,CAAChqB,CAAD,CAAQ,CACrC03C,CAAA,CAAmBlvC,CAAA0/B,MAAA,CAAY1lC,CAAA,CAAKmF,CAAL,CAAZ,CAAnB,CADqC,CAAvC,CAKa,UAAb,GAAIA,CAAJ,EACEa,CAAAnF,OAAA,CAAa,QAAb;AAAuB,QAAQ,CAACs0C,CAAD,CAASC,CAAT,CAAoB,CAEjD,IAAIC,EAAMF,CAANE,CAAe,CACnB,IAAIA,CAAJ,GAAYD,CAAZ,CAAwB,CAAxB,CAA2B,CACzB,IAAIN,EAAUD,CAAA,CAAa7uC,CAAA0/B,MAAA,CAAY1lC,CAAA,CAAKmF,CAAL,CAAZ,CAAb,CACdkwC,EAAA,GAAQjjC,CAAR,EAQAsb,CACJ,CADiBqnB,CAAA,CAPAD,CAOA,CAA2B,CAA3B,CACjB,CAAA90C,CAAAstB,UAAA,CAAeI,CAAf,CATI,GAaAA,CACJ,CADiBqnB,CAAA,CAXGD,CAWH,CAA4B,EAA5B,CACjB,CAAA90C,CAAAwtB,aAAA,CAAkBE,CAAlB,CAdI,CAFyB,CAHsB,CAAnD,CAXiC,CAFhC,CAD8B,CAAhC,CAF+B,CAzziBxC,IAAIxqB,EAAYA,QAAQ,CAACurC,CAAD,CAAQ,CAAC,MAAOlyC,EAAA,CAASkyC,CAAT,CAAA,CAAmBA,CAAAznC,YAAA,EAAnB,CAA0CynC,CAAlD,CAAhC,CACI3xC,GAAiBw4C,MAAAj+B,UAAAva,eADrB,CAaIsM,GAAYA,QAAQ,CAACqlC,CAAD,CAAQ,CAAC,MAAOlyC,EAAA,CAASkyC,CAAT,CAAA,CAAmBA,CAAA3gC,YAAA,EAAnB,CAA0C2gC,CAAlD,CAbhC,CAwCIn6B,CAxCJ,CAyCIjR,CAzCJ,CA0CI2L,EA1CJ,CA2CI7M,GAAoB,EAAAA,MA3CxB,CA4CIjF,GAAoB,EAAAA,KA5CxB,CA6CIqC,GAAoB+1C,MAAAj+B,UAAA9X,SA7CxB,CA8CIuB,GAAoB7E,CAAA,CAAO,IAAP,CA9CxB,CAmDIsK,GAAoBzK,CAAAyK,QAApBA,GAAuCzK,CAAAyK,QAAvCA,CAAwD,EAAxDA,CAnDJ,CAoDI8C,EApDJ,CAqDI2a,EArDJ,CAsDIrmB,GAAoB,CAAC,GAAD,CAAM,GAAN,CAAW,GAAX,CAMxB2W,EAAA,CAAO9V,CAAA,CAAI,CAAC,YAAA8G,KAAA,CAAkBpC,CAAA,CAAUqmC,SAAAD,UAAV,CAAlB,CAAD,EAAsD,EAAtD,EAA0D,CAA1D,CAAJ,CACH3D,MAAA,CAAMrxB,CAAN,CAAJ,GACEA,CADF,CACS9V,CAAA,CAAI,CAAC,uBAAA8G,KAAA,CAA6BpC,CAAA,CAAUqmC,SAAAD,UAAV,CAA7B,CAAD;AAAiE,EAAjE,EAAqE,CAArE,CAAJ,CADT,CAiNAxqC,EAAA+V,QAAA,CAAe,EAoBf9V,GAAA8V,QAAA,CAAmB,EA8KnB,KAAIzF,GAAQ,QAAQ,EAAG,CAIrB,MAAKrR,OAAAsZ,UAAAjI,KAAL,CAKO,QAAQ,CAAC5R,CAAD,CAAQ,CACrB,MAAOjB,EAAA,CAASiB,CAAT,CAAA,CAAkBA,CAAA4R,KAAA,EAAlB,CAAiC5R,CADnB,CALvB,CACS,QAAQ,CAACA,CAAD,CAAQ,CACrB,MAAOjB,EAAA,CAASiB,CAAT,CAAA,CAAkBA,CAAAsG,QAAA,CAAc,QAAd,CAAwB,EAAxB,CAAAA,QAAA,CAAoC,QAApC,CAA8C,EAA9C,CAAlB,CAAsEtG,CADxD,CALJ,CAAX,EA8CVwmB,GAAA,CADS,CAAX,CAAI1P,CAAJ,CACc0P,QAAQ,CAAC5gB,CAAD,CAAU,CAC5BA,CAAA,CAAUA,CAAAtD,SAAA,CAAmBsD,CAAnB,CAA6BA,CAAA,CAAQ,CAAR,CACvC,OAAQA,EAAA4jB,UACD,EAD2C,MAC3C,EADsB5jB,CAAA4jB,UACtB,CAAH5d,EAAA,CAAUhG,CAAA4jB,UAAV,CAA8B,GAA9B,CAAoC5jB,CAAAtD,SAApC,CAAG,CAAqDsD,CAAAtD,SAHhC,CADhC,CAOckkB,QAAQ,CAAC5gB,CAAD,CAAU,CAC5B,MAAOA,EAAAtD,SAAA,CAAmBsD,CAAAtD,SAAnB,CAAsCsD,CAAA,CAAQ,CAAR,CAAAtD,SADjB,CAurBhC,KAAI+G,GAAoB,QAAxB,CAmgBIsC,GAAU,MACN,QADM,OAEL,CAFK,OAGL,CAHK,KAIP,EAJO,UAKF,oBALE,CAngBd,CAsuBIyI,GAAUzC,CAAAwH,MAAV/E,CAAyB,EAtuB7B,CAuuBIF,GAASvC,CAAA+d,QAATxb,CAA0B,KAA1BA,CAAkC1Q,CAAA,IAAID,IAAJC,SAAA,EAvuBtC;AAwuBI8Q,GAAO,CAxuBX,CAyuBIyjC,GAAsBz5C,CAAAC,SAAAy5C,iBACA,CAAlB,QAAQ,CAACpyC,CAAD,CAAU8N,CAAV,CAAgBjP,CAAhB,CAAoB,CAACmB,CAAAoyC,iBAAA,CAAyBtkC,CAAzB,CAA+BjP,CAA/B,CAAmC,CAAA,CAAnC,CAAD,CAAV,CAClB,QAAQ,CAACmB,CAAD,CAAU8N,CAAV,CAAgBjP,CAAhB,CAAoB,CAACmB,CAAAqyC,YAAA,CAAoB,IAApB,CAA2BvkC,CAA3B,CAAiCjP,CAAjC,CAAD,CA3uBpC,CA4uBIuP,GAAyB1V,CAAAC,SAAA25C,oBACA,CAArB,QAAQ,CAACtyC,CAAD,CAAU8N,CAAV,CAAgBjP,CAAhB,CAAoB,CAACmB,CAAAsyC,oBAAA,CAA4BxkC,CAA5B,CAAkCjP,CAAlC,CAAsC,CAAA,CAAtC,CAAD,CAAP,CACrB,QAAQ,CAACmB,CAAD,CAAU8N,CAAV,CAAgBjP,CAAhB,CAAoB,CAACmB,CAAAuyC,YAAA,CAAoB,IAApB,CAA2BzkC,CAA3B,CAAiCjP,CAAjC,CAAD,CAKvBkN,EAAAymC,MAAb,CAA4BC,QAAQ,CAACh2C,CAAD,CAAO,CAEzC,MAAO,KAAA8W,MAAA,CAAW9W,CAAA,CAAK,IAAAqtB,QAAL,CAAX,CAAP,EAAyC,EAFA,CAQ3C,KAAIvf,GAAuB,iBAA3B,CACII,GAAkB,aADtB,CAEIsB,GAAepT,CAAA,CAAO,QAAP,CAFnB,CA4DIsT,GAAoB,4BA5DxB,CA6DIG,GAAc,WA7DlB,CA8DII,GAAkB,WA9DtB,CA+DIK,GAAmB,yEA/DvB,CAiEIH;AAAU,QACF,CAAC,CAAD,CAAI,8BAAJ,CAAoC,WAApC,CADE,OAGH,CAAC,CAAD,CAAI,SAAJ,CAAe,UAAf,CAHG,KAIL,CAAC,CAAD,CAAI,mBAAJ,CAAyB,qBAAzB,CAJK,IAKN,CAAC,CAAD,CAAI,gBAAJ,CAAsB,kBAAtB,CALM,IAMN,CAAC,CAAD,CAAI,oBAAJ,CAA0B,uBAA1B,CANM,UAOA,CAAC,CAAD,CAAI,EAAJ,CAAQ,EAAR,CAPA,CAUdA,GAAA8lC,SAAA,CAAmB9lC,EAAA+lC,OACnB/lC,GAAAgmC,MAAA,CAAgBhmC,EAAAimC,MAAhB,CAAgCjmC,EAAAkmC,SAAhC,CAAmDlmC,EAAAmmC,QAAnD,CAAqEnmC,EAAAomC,MACrEpmC,GAAAqmC,GAAA,CAAarmC,EAAAsmC,GAgQb,KAAIx0B,GAAkB3S,CAAAkI,UAAlByK,CAAqC,OAChCy0B,QAAQ,CAACt0C,CAAD,CAAK,CAGlBu0C,QAASA,EAAO,EAAG,CACbC,CAAJ,GACAA,CACA,CADQ,CAAA,CACR,CAAAx0C,CAAA,EAFA,CADiB,CAFnB,IAAIw0C,EAAQ,CAAA,CASgB,WAA5B,GAAI16C,CAAA+4B,WAAJ,CACE7a,UAAA,CAAWu8B,CAAX,CADF,EAGE,IAAAv6B,GAAA,CAAQ,kBAAR,CAA4Bu6B,CAA5B,CAGA,CAAArnC,CAAA,CAAOrT,CAAP,CAAAmgB,GAAA,CAAkB,MAAlB,CAA0Bu6B,CAA1B,CANF,CAVkB,CADmB,UAqB7Bj3C,QAAQ,EAAG,CACnB,IAAI/B;AAAQ,EACZf,EAAA,CAAQ,IAAR,CAAc,QAAQ,CAAC+G,CAAD,CAAG,CAAEhG,CAAAN,KAAA,CAAW,EAAX,CAAgBsG,CAAhB,CAAF,CAAzB,CACA,OAAO,GAAP,CAAahG,CAAAM,KAAA,CAAW,IAAX,CAAb,CAAgC,GAHb,CArBkB,IA2BnCikB,QAAQ,CAACrkB,CAAD,CAAQ,CAChB,MAAiB,EAAV,EAACA,CAAD,CAAe2F,CAAA,CAAO,IAAA,CAAK3F,CAAL,CAAP,CAAf,CAAqC2F,CAAA,CAAO,IAAA,CAAK,IAAAhH,OAAL,CAAmBqB,CAAnB,CAAP,CAD5B,CA3BmB,QA+B/B,CA/B+B,MAgCjCR,EAhCiC,MAiCjC,EAAAC,KAjCiC,QAkC/B,EAAAqD,OAlC+B,CAAzC,CA0CI6S,GAAe,EACnB5W,EAAA,CAAQ,2DAAA,MAAA,CAAA,GAAA,CAAR,CAAgF,QAAQ,CAACe,CAAD,CAAQ,CAC9F6V,EAAA,CAAanQ,CAAA,CAAU1F,CAAV,CAAb,CAAA,CAAiCA,CAD6D,CAAhG,CAGA,KAAI8V,GAAmB,EACvB7W,EAAA,CAAQ,kDAAA,MAAA,CAAA,GAAA,CAAR,CAAuE,QAAQ,CAACe,CAAD,CAAQ,CACrF8V,EAAA,CAAiBlK,EAAA,CAAU5L,CAAV,CAAjB,CAAA,CAAqC,CAAA,CADgD,CAAvF,CAYAf,EAAA,CAAQ,MACAsV,EADA,eAESe,EAFT,OAIC9M,QAAQ,CAAC5C,CAAD,CAAU,CAEvB,MAAOC,EAAA,CAAOD,CAAP,CAAAgD,KAAA,CAAqB,QAArB,CAAP,EAAyC0M,EAAA,CAAoB1P,CAAA4P,WAApB,EAA0C5P,CAA1C,CAAmD,CAAC,eAAD,CAAkB,QAAlB,CAAnD,CAFlB,CAJnB;aASQsjB,QAAQ,CAACtjB,CAAD,CAAU,CAE9B,MAAOC,EAAA,CAAOD,CAAP,CAAAgD,KAAA,CAAqB,eAArB,CAAP,EAAgD/C,CAAA,CAAOD,CAAP,CAAAgD,KAAA,CAAqB,yBAArB,CAFlB,CAT1B,YAcMyM,EAdN,UAgBIlN,QAAQ,CAACvC,CAAD,CAAU,CAC1B,MAAO0P,GAAA,CAAoB1P,CAApB,CAA6B,WAA7B,CADmB,CAhBtB,YAoBM6qB,QAAQ,CAAC7qB,CAAD,CAAS+B,CAAT,CAAe,CACjC/B,CAAAszC,gBAAA,CAAwBvxC,CAAxB,CADiC,CApB7B,UAwBIgN,EAxBJ,KA0BDwkC,QAAQ,CAACvzC,CAAD,CAAU+B,CAAV,CAAgB3H,CAAhB,CAAuB,CAClC2H,CAAA,CAAOuI,EAAA,CAAUvI,CAAV,CAEP,IAAIhG,CAAA,CAAU3B,CAAV,CAAJ,CACE4F,CAAAymC,MAAA,CAAc1kC,CAAd,CAAA,CAAsB3H,CADxB,KAEO,CACL,IAAIgF,CAEQ,EAAZ,EAAI8R,CAAJ,GAEE9R,CACA,CADMY,CAAAwzC,aACN,EAD8BxzC,CAAAwzC,aAAA,CAAqBzxC,CAArB,CAC9B,CAAY,EAAZ,GAAI3C,CAAJ,GAAgBA,CAAhB,CAAsB,MAAtB,CAHF,CAMAA,EAAA,CAAMA,CAAN,EAAaY,CAAAymC,MAAA,CAAc1kC,CAAd,CAED,EAAZ,EAAImP,CAAJ,GAEE9R,CAFF,CAEiB,EAAT,GAACA,CAAD,CAAexG,CAAf,CAA2BwG,CAFnC,CAKA,OAAQA,EAhBH,CAL2B,CA1B9B,MAmDAxC,QAAQ,CAACoD,CAAD,CAAU+B,CAAV,CAAgB3H,CAAhB,CAAsB,CAClC,IAAIq5C,EAAiB3zC,CAAA,CAAUiC,CAAV,CACrB,IAAIkO,EAAA,CAAawjC,CAAb,CAAJ,CACE,GAAI13C,CAAA,CAAU3B,CAAV,CAAJ,CACQA,CAAN,EACE4F,CAAA,CAAQ+B,CAAR,CACA,CADgB,CAAA,CAChB,CAAA/B,CAAAoP,aAAA,CAAqBrN,CAArB,CAA2B0xC,CAA3B,CAFF,GAIEzzC,CAAA,CAAQ+B,CAAR,CACA,CADgB,CAAA,CAChB,CAAA/B,CAAAszC,gBAAA,CAAwBG,CAAxB,CALF,CADF;IASE,OAAQzzC,EAAA,CAAQ+B,CAAR,CAED,EADGkf,CAAAjhB,CAAAoC,WAAAsxC,aAAA,CAAgC3xC,CAAhC,CAAAkf,EAAwCvlB,CAAxCulB,WACH,CAAEwyB,CAAF,CACE76C,CAbb,KAeO,IAAImD,CAAA,CAAU3B,CAAV,CAAJ,CACL4F,CAAAoP,aAAA,CAAqBrN,CAArB,CAA2B3H,CAA3B,CADK,KAEA,IAAI4F,CAAAiP,aAAJ,CAKL,MAFI0kC,EAEG,CAFG3zC,CAAAiP,aAAA,CAAqBlN,CAArB,CAA2B,CAA3B,CAEH,CAAQ,IAAR,GAAA4xC,CAAA,CAAe/6C,CAAf,CAA2B+6C,CAxBF,CAnD9B,MA+EAh3C,QAAQ,CAACqD,CAAD,CAAU+B,CAAV,CAAgB3H,CAAhB,CAAuB,CACnC,GAAI2B,CAAA,CAAU3B,CAAV,CAAJ,CACE4F,CAAA,CAAQ+B,CAAR,CAAA,CAAgB3H,CADlB,KAGE,OAAO4F,EAAA,CAAQ+B,CAAR,CAJ0B,CA/E/B,MAuFC,QAAQ,EAAG,CAYhB6xC,QAASA,EAAO,CAAC5zC,CAAD,CAAU5F,CAAV,CAAiB,CAC/B,IAAIy5C,EAAWC,CAAA,CAAwB9zC,CAAA9G,SAAxB,CACf,IAAI4C,CAAA,CAAY1B,CAAZ,CAAJ,CACE,MAAOy5C,EAAA,CAAW7zC,CAAA,CAAQ6zC,CAAR,CAAX,CAA+B,EAExC7zC,EAAA,CAAQ6zC,CAAR,CAAA,CAAoBz5C,CALW,CAXjC,IAAI05C,EAA0B,EACnB,EAAX,CAAI5iC,CAAJ,EACE4iC,CAAA,CAAwB,CAAxB,CACA,CAD6B,WAC7B,CAAAA,CAAA,CAAwB,CAAxB,CAAA,CAA6B,WAF/B,EAIEA,CAAA,CAAwB,CAAxB,CAJF,CAKEA,CAAA,CAAwB,CAAxB,CALF,CAK+B,aAE/BF,EAAAG,IAAA,CAAc,EACd,OAAOH,EAVS,CAAX,EAvFD,KA4GDx0C,QAAQ,CAACY,CAAD,CAAU5F,CAAV,CAAiB,CAC5B,GAAI0B,CAAA,CAAY1B,CAAZ,CAAJ,CAAwB,CACtB,GAA2B,QAA3B,GAAIwmB,EAAA,CAAU5gB,CAAV,CAAJ,EAAuCA,CAAAg0C,SAAvC,CAAyD,CACvD,IAAIz+B,EAAS,EACblc,EAAA,CAAQ2G,CAAAwa,QAAR,CAAyB,QAAS,CAACm4B,CAAD,CAAS,CACrCA,CAAAsB,SAAJ;AACE1+B,CAAAzb,KAAA,CAAY64C,CAAAv4C,MAAZ,EAA4Bu4C,CAAAjqB,KAA5B,CAFuC,CAA3C,CAKA,OAAyB,EAAlB,GAAAnT,CAAAtc,OAAA,CAAsB,IAAtB,CAA6Bsc,CAPmB,CASzD,MAAOvV,EAAA5F,MAVe,CAYxB4F,CAAA5F,MAAA,CAAgBA,CAbY,CA5GxB,MA4HAmG,QAAQ,CAACP,CAAD,CAAU5F,CAAV,CAAiB,CAC7B,GAAI0B,CAAA,CAAY1B,CAAZ,CAAJ,CACE,MAAO4F,EAAA8M,UAET,KAJ6B,IAIpB7S,EAAI,CAJgB,CAIboT,EAAarN,CAAAqN,WAA7B,CAAiDpT,CAAjD,CAAqDoT,CAAApU,OAArD,CAAwEgB,CAAA,EAAxE,CACE0T,EAAA,CAAaN,CAAA,CAAWpT,CAAX,CAAb,CAEF+F,EAAA8M,UAAA,CAAoB1S,CAPS,CA5HzB,OAsIC0V,EAtID,CAAR,CAuIG,QAAQ,CAACjR,CAAD,CAAKkD,CAAL,CAAU,CAInBgK,CAAAkI,UAAA,CAAiBlS,CAAjB,CAAA,CAAyB,QAAQ,CAACm4B,CAAD,CAAOC,CAAP,CAAa,CAAA,IACxClgC,CADwC,CACrCT,CAKP,IAAIqF,CAAJ,GAAWiR,EAAX,GACoB,CAAd,EAACjR,CAAA5F,OAAD,EAAoB4F,CAApB,GAA2BkQ,EAA3B,EAA6ClQ,CAA7C,GAAoD4Q,EAApD,CAAyEyqB,CAAzE,CAAgFC,CADtF,IACgGvhC,CADhG,CAC4G,CAC1G,GAAIoD,CAAA,CAASk+B,CAAT,CAAJ,CAAoB,CAGlB,IAAKjgC,CAAL,CAAS,CAAT,CAAYA,CAAZ,CAAgB,IAAAhB,OAAhB,CAA6BgB,CAAA,EAA7B,CACE,GAAI4E,CAAJ,GAAW8P,EAAX,CAEE9P,CAAA,CAAG,IAAA,CAAK5E,CAAL,CAAH,CAAYigC,CAAZ,CAFF,KAIE,KAAK1gC,CAAL,GAAY0gC,EAAZ,CACEr7B,CAAA,CAAG,IAAA,CAAK5E,CAAL,CAAH,CAAYT,CAAZ,CAAiB0gC,CAAA,CAAK1gC,CAAL,CAAjB,CAKN,OAAO,KAdW,CAiBdY,CAAAA,CAAQyE,CAAAk1C,IAER3mC,EAAAA,CAAMhT,CAAD,GAAWxB,CAAX,CAAwB8tB,IAAAqjB,IAAA,CAAS,IAAA9wC,OAAT,CAAsB,CAAtB,CAAxB,CAAmD,IAAAA,OAC5D,KAAK,IAAIkU,EAAI,CAAb,CAAgBA,CAAhB,CAAoBC,CAApB,CAAwBD,CAAA,EAAxB,CAA6B,CAC3B,IAAI+Q,EAAYrf,CAAA,CAAG,IAAA,CAAKsO,CAAL,CAAH,CAAY+sB,CAAZ,CAAkBC,CAAlB,CAChB//B,EAAA;AAAQA,CAAA,CAAQA,CAAR,CAAgB8jB,CAAhB,CAA4BA,CAFT,CAI7B,MAAO9jB,EAzBiG,CA6B1G,IAAKH,CAAL,CAAS,CAAT,CAAYA,CAAZ,CAAgB,IAAAhB,OAAhB,CAA6BgB,CAAA,EAA7B,CACE4E,CAAA,CAAG,IAAA,CAAK5E,CAAL,CAAH,CAAYigC,CAAZ,CAAkBC,CAAlB,CAGF,OAAO,KAxCmC,CAJ3B,CAvIrB,CAqPA9gC,EAAA,CAAQ,YACMuU,EADN,QAGED,EAHF,IAKFumC,QAASA,EAAI,CAACl0C,CAAD,CAAU8N,CAAV,CAAgBjP,CAAhB,CAAoBkP,CAApB,CAAgC,CAC/C,GAAIhS,CAAA,CAAUgS,CAAV,CAAJ,CAA4B,KAAM9B,GAAA,CAAa,QAAb,CAAN,CADmB,IAG3C+B,EAASC,EAAA,CAAmBjO,CAAnB,CAA4B,QAA5B,CAHkC,CAI3CkO,EAASD,EAAA,CAAmBjO,CAAnB,CAA4B,QAA5B,CAERgO,EAAL,EAAaC,EAAA,CAAmBjO,CAAnB,CAA4B,QAA5B,CAAsCgO,CAAtC,CAA+C,EAA/C,CACRE,EAAL,EAAaD,EAAA,CAAmBjO,CAAnB,CAA4B,QAA5B,CAAsCkO,CAAtC,CAA+CiC,EAAA,CAAmBnQ,CAAnB,CAA4BgO,CAA5B,CAA/C,CAEb3U,EAAA,CAAQyU,CAAA9M,MAAA,CAAW,GAAX,CAAR,CAAyB,QAAQ,CAAC8M,CAAD,CAAM,CACrC,IAAIqmC,EAAWnmC,CAAA,CAAOF,CAAP,CAEf,IAAI,CAACqmC,CAAL,CAAe,CACb,GAAY,YAAZ,EAAIrmC,CAAJ,EAAoC,YAApC,EAA4BA,CAA5B,CAAkD,CAChD,IAAIsmC,EAAWz7C,CAAA64B,KAAA4iB,SAAA,EAA0Bz7C,CAAA64B,KAAA6iB,wBAA1B,CACf,QAAQ,CAAE7vB,CAAF,CAAKC,CAAL,CAAS,CAAA,IAEX6vB,EAAuB,CAAf,GAAA9vB,CAAAtrB,SAAA,CAAmBsrB,CAAA+vB,gBAAnB,CAAuC/vB,CAFpC,CAGfgwB,EAAM/vB,CAAN+vB,EAAW/vB,CAAA7U,WACX,OAAO4U,EAAP,GAAagwB,CAAb,EAAoB,CAAC,EAAGA,CAAH,EAA2B,CAA3B,GAAUA,CAAAt7C,SAAV,GACnBo7C,CAAAF,SAAA,CACAE,CAAAF,SAAA,CAAgBI,CAAhB,CADA;AAEAhwB,CAAA6vB,wBAFA,EAE6B7vB,CAAA6vB,wBAAA,CAA2BG,CAA3B,CAF7B,CAEgE,EAH7C,EAJN,CADF,CAWb,QAAQ,CAAEhwB,CAAF,CAAKC,CAAL,CAAS,CACf,GAAKA,CAAL,CACE,IAAA,CAASA,CAAT,CAAaA,CAAA7U,WAAb,CAAA,CACE,GAAK6U,CAAL,GAAWD,CAAX,CACE,MAAO,CAAA,CAIb,OAAO,CAAA,CARQ,CAWnBxW,EAAA,CAAOF,CAAP,CAAA,CAAe,EAOfomC,EAAA,CAAKl0C,CAAL,CAFey0C,YAAe,UAAfA,YAAwC,WAAxCA,CAED,CAAS3mC,CAAT,CAAd,CAA8B,QAAQ,CAACsC,CAAD,CAAQ,CAC5C,IAAmBskC,EAAUtkC,CAAAukC,cAGvBD,EAAN,GAAkBA,CAAlB,GAHa/jC,IAGb,EAAyCyjC,CAAA,CAH5BzjC,IAG4B,CAAiB+jC,CAAjB,CAAzC,GACExmC,CAAA,CAAOkC,CAAP,CAActC,CAAd,CAL0C,CAA9C,CA9BgD,CAAlD,IAwCEqkC,GAAA,CAAmBnyC,CAAnB,CAA4B8N,CAA5B,CAAkCI,CAAlC,CACA,CAAAF,CAAA,CAAOF,CAAP,CAAA,CAAe,EAEjBqmC,EAAA,CAAWnmC,CAAA,CAAOF,CAAP,CA5CE,CA8CfqmC,CAAAr6C,KAAA,CAAc+E,CAAd,CAjDqC,CAAvC,CAT+C,CAL3C,KAmEDgP,EAnEC,KAqED+mC,QAAQ,CAAC50C,CAAD,CAAU8N,CAAV,CAAgBjP,CAAhB,CAAoB,CAC/BmB,CAAA,CAAUC,CAAA,CAAOD,CAAP,CAKVA,EAAA6Y,GAAA,CAAW/K,CAAX,CAAiBomC,QAASA,EAAI,EAAG,CAC/Bl0C,CAAA60C,IAAA,CAAY/mC,CAAZ,CAAkBjP,CAAlB,CACAmB,EAAA60C,IAAA,CAAY/mC,CAAZ,CAAkBomC,CAAlB,CAF+B,CAAjC,CAIAl0C,EAAA6Y,GAAA,CAAW/K,CAAX,CAAiBjP,CAAjB,CAV+B,CArE3B,aAkFOmnB,QAAQ,CAAChmB,CAAD,CAAU80C,CAAV,CAAuB,CAAA,IACtCx6C,CADsC,CAC/BkB,EAASwE,CAAA4P,WACpBjC,GAAA,CAAa3N,CAAb,CACA3G,EAAA,CAAQ,IAAI0S,CAAJ,CAAW+oC,CAAX,CAAR,CAAiC,QAAQ,CAACr4C,CAAD,CAAM,CACzCnC,CAAJ,CACEkB,CAAAu5C,aAAA,CAAoBt4C,CAApB,CAA0BnC,CAAAuK,YAA1B,CADF;AAGErJ,CAAAquB,aAAA,CAAoBptB,CAApB,CAA0BuD,CAA1B,CAEF1F,EAAA,CAAQmC,CANqC,CAA/C,CAH0C,CAlFtC,UA+FI+O,QAAQ,CAACxL,CAAD,CAAU,CAC1B,IAAIwL,EAAW,EACfnS,EAAA,CAAQ2G,CAAAqN,WAAR,CAA4B,QAAQ,CAACrN,CAAD,CAAS,CAClB,CAAzB,GAAIA,CAAA9G,SAAJ,EACEsS,CAAA1R,KAAA,CAAckG,CAAd,CAFyC,CAA7C,CAIA,OAAOwL,EANmB,CA/FtB,UAwGI0a,QAAQ,CAAClmB,CAAD,CAAU,CAC1B,MAAOA,EAAAg1C,gBAAP,EAAkCh1C,CAAAqN,WAAlC,EAAwD,EAD9B,CAxGtB,QA4GE/M,QAAQ,CAACN,CAAD,CAAUvD,CAAV,CAAgB,CAC9BpD,CAAA,CAAQ,IAAI0S,CAAJ,CAAWtP,CAAX,CAAR,CAA0B,QAAQ,CAAC6jC,CAAD,CAAO,CACd,CAAzB,GAAItgC,CAAA9G,SAAJ,EAAmD,EAAnD,GAA8B8G,CAAA9G,SAA9B,EACE8G,CAAAwM,YAAA,CAAoB8zB,CAApB,CAFqC,CAAzC,CAD8B,CA5G1B,SAoHG2U,QAAQ,CAACj1C,CAAD,CAAUvD,CAAV,CAAgB,CAC/B,GAAyB,CAAzB,GAAIuD,CAAA9G,SAAJ,CAA4B,CAC1B,IAAIoB,EAAQ0F,CAAAiN,WACZ5T,EAAA,CAAQ,IAAI0S,CAAJ,CAAWtP,CAAX,CAAR,CAA0B,QAAQ,CAAC6jC,CAAD,CAAO,CACvCtgC,CAAA+0C,aAAA,CAAqBzU,CAArB,CAA4BhmC,CAA5B,CADuC,CAAzC,CAF0B,CADG,CApH3B,MA6HAqS,QAAQ,CAAC3M,CAAD,CAAUk1C,CAAV,CAAoB,CAChCA,CAAA,CAAWj1C,CAAA,CAAOi1C,CAAP,CAAA,CAAiB,CAAjB,CACX,KAAI15C,EAASwE,CAAA4P,WACTpU,EAAJ,EACEA,CAAAquB,aAAA,CAAoBqrB,CAApB,CAA8Bl1C,CAA9B,CAEFk1C,EAAA1oC,YAAA,CAAqBxM,CAArB,CANgC,CA7H5B,QAsIE0b,QAAQ,CAAC1b,CAAD,CAAU,CACxB2N,EAAA,CAAa3N,CAAb,CACA;IAAIxE,EAASwE,CAAA4P,WACTpU,EAAJ,EAAYA,CAAAwR,YAAA,CAAmBhN,CAAnB,CAHY,CAtIpB,OA4ICm1C,QAAQ,CAACn1C,CAAD,CAAUo1C,CAAV,CAAsB,CAAA,IAC/B96C,EAAQ0F,CADuB,CACdxE,EAASwE,CAAA4P,WAC9BvW,EAAA,CAAQ,IAAI0S,CAAJ,CAAWqpC,CAAX,CAAR,CAAgC,QAAQ,CAAC34C,CAAD,CAAM,CAC5CjB,CAAAu5C,aAAA,CAAoBt4C,CAApB,CAA0BnC,CAAAuK,YAA1B,CACAvK,EAAA,CAAQmC,CAFoC,CAA9C,CAFmC,CA5I/B,UAoJI6S,EApJJ,aAqJOJ,EArJP,aAuJOmmC,QAAQ,CAACr1C,CAAD,CAAUgP,CAAV,CAAoBsmC,CAApB,CAA+B,CAC9CtmC,CAAJ,EACE3V,CAAA,CAAQ2V,CAAAhO,MAAA,CAAe,GAAf,CAAR,CAA6B,QAAQ,CAACmB,CAAD,CAAW,CAC9C,IAAIozC,EAAiBD,CACjBx5C,EAAA,CAAYy5C,CAAZ,CAAJ,GACEA,CADF,CACmB,CAACxmC,EAAA,CAAe/O,CAAf,CAAwBmC,CAAxB,CADpB,CAGC,EAAAozC,CAAA,CAAiBjmC,EAAjB,CAAkCJ,EAAlC,EAAqDlP,CAArD,CAA8DmC,CAA9D,CAL6C,CAAhD,CAFgD,CAvJ9C,QAmKE3G,QAAQ,CAACwE,CAAD,CAAU,CAExB,MAAO,CADHxE,CACG,CADMwE,CAAA4P,WACN,GAA8B,EAA9B,GAAUpU,CAAAtC,SAAV,CAAmCsC,CAAnC,CAA4C,IAF3B,CAnKpB,MAwKAgnC,QAAQ,CAACxiC,CAAD,CAAU,CACtB,GAAIA,CAAAw1C,mBAAJ,CACE,MAAOx1C,EAAAw1C,mBAKT,KADI9/B,CACJ,CADU1V,CAAA6E,YACV,CAAc,IAAd,EAAO6Q,CAAP,EAAuC,CAAvC,GAAsBA,CAAAxc,SAAtB,CAAA,CACEwc,CAAA,CAAMA,CAAA7Q,YAER,OAAO6Q,EAVe,CAxKlB,MAqLA7Y,QAAQ,CAACmD,CAAD,CAAUgP,CAAV,CAAoB,CAChC,MAAIhP,EAAAy1C,qBAAJ;AACSz1C,CAAAy1C,qBAAA,CAA6BzmC,CAA7B,CADT,CAGS,EAJuB,CArL5B,OA6LCvB,EA7LD,gBA+LU/B,QAAQ,CAAC1L,CAAD,CAAU01C,CAAV,CAAqBC,CAArB,CAAgC,CAClDxB,CAAAA,CAAW,CAAClmC,EAAA,CAAmBjO,CAAnB,CAA4B,QAA5B,CAAD,EAA0C,EAA1C,EAA8C01C,CAA9C,CAEfC,EAAA,CAAYA,CAAZ,EAAyB,EAEzB,KAAIvlC,EAAQ,CAAC,gBACK1U,CADL,iBAEMA,CAFN,CAAD,CAKZrC,EAAA,CAAQ86C,CAAR,CAAkB,QAAQ,CAACt1C,CAAD,CAAK,CAC7BA,CAAAI,MAAA,CAASe,CAAT,CAAkBoQ,CAAAlR,OAAA,CAAay2C,CAAb,CAAlB,CAD6B,CAA/B,CAVsD,CA/LlD,CAAR,CA6MG,QAAQ,CAAC92C,CAAD,CAAKkD,CAAL,CAAU,CAInBgK,CAAAkI,UAAA,CAAiBlS,CAAjB,CAAA,CAAyB,QAAQ,CAACm4B,CAAD,CAAOC,CAAP,CAAayb,CAAb,CAAmB,CAElD,IADA,IAAIx7C,CAAJ,CACQH,EAAE,CAAV,CAAaA,CAAb,CAAiB,IAAAhB,OAAjB,CAA8BgB,CAAA,EAA9B,CACM6B,CAAA,CAAY1B,CAAZ,CAAJ,EACEA,CACA,CADQyE,CAAA,CAAG,IAAA,CAAK5E,CAAL,CAAH,CAAYigC,CAAZ,CAAkBC,CAAlB,CAAwByb,CAAxB,CACR,CAAI75C,CAAA,CAAU3B,CAAV,CAAJ,GAEEA,CAFF,CAEU6F,CAAA,CAAO7F,CAAP,CAFV,CAFF,EAOEoT,EAAA,CAAepT,CAAf,CAAsByE,CAAA,CAAG,IAAA,CAAK5E,CAAL,CAAH,CAAYigC,CAAZ,CAAkBC,CAAlB,CAAwByb,CAAxB,CAAtB,CAGJ,OAAO75C,EAAA,CAAU3B,CAAV,CAAA,CAAmBA,CAAnB,CAA2B,IAbgB,CAiBpD2R,EAAAkI,UAAAtV,KAAA,CAAwBoN,CAAAkI,UAAA4E,GACxB9M,EAAAkI,UAAA4hC,OAAA,CAA0B9pC,CAAAkI,UAAA4gC,IAtBP,CA7MrB,CA0QAvjC,GAAA2C,UAAA,CAAoB,KAMb1C,QAAQ,CAAC/X,CAAD,CAAMY,CAAN,CAAa,CACxB,IAAA,CAAKgX,EAAA,CAAQ5X,CAAR,CAAL,CAAA,CAAqBY,CADG,CANR,KAcb4Y,QAAQ,CAACxZ,CAAD,CAAM,CACjB,MAAO,KAAA,CAAK4X,EAAA,CAAQ5X,CAAR,CAAL,CADU,CAdD;OAsBVkiB,QAAQ,CAACliB,CAAD,CAAM,CACpB,IAAIY,EAAQ,IAAA,CAAKZ,CAAL,CAAW4X,EAAA,CAAQ5X,CAAR,CAAX,CACZ,QAAO,IAAA,CAAKA,CAAL,CACP,OAAOY,EAHa,CAtBJ,CA0FpB,KAAIyX,GAAU,oCAAd,CACIC,GAAe,GADnB,CAEIC,GAAS,sBAFb,CAGIJ,GAAiB,kCAHrB,CAII5M,GAAkBlM,CAAA,CAAO,WAAP,CAJtB,CAo0BIi9C,GAAiBj9C,CAAA,CAAO,UAAP,CAp0BrB,CAm1BIiQ,GAAmB,CAAC,UAAD,CAAa,QAAQ,CAACrG,CAAD,CAAW,CAGrD,IAAAszC,YAAA,CAAmB,EAkCnB,KAAAtqB,SAAA,CAAgBC,QAAQ,CAAC3pB,CAAD,CAAOkD,CAAP,CAAgB,CACtC,IAAIzL,EAAMuI,CAANvI,CAAa,YACjB,IAAIuI,CAAJ,EAA8B,GAA9B,EAAYA,CAAA/D,OAAA,CAAY,CAAZ,CAAZ,CAAmC,KAAM83C,GAAA,CAAe,SAAf,CACoB/zC,CADpB,CAAN,CAEnC,IAAAg0C,YAAA,CAAiBh0C,CAAAqf,OAAA,CAAY,CAAZ,CAAjB,CAAA,CAAmC5nB,CACnCiJ,EAAAwC,QAAA,CAAiBzL,CAAjB,CAAsByL,CAAtB,CALsC,CAsBxC,KAAA+wC,gBAAA,CAAuBC,QAAQ,CAACtqB,CAAD,CAAa,CAClB,CAAxB,GAAGxwB,SAAAlC,OAAH,GACE,IAAAi9C,kBADF,CAC4BvqB,CAAD,WAAuB9tB,OAAvB;AAAiC8tB,CAAjC,CAA8C,IADzE,CAGA,OAAO,KAAAuqB,kBAJmC,CAO5C,KAAAzjC,KAAA,CAAY,CAAC,UAAD,CAAa,iBAAb,CAAgC,QAAQ,CAACwD,CAAD,CAAWkgC,CAAX,CAA4B,CAuB9E,MAAO,OAiBGC,QAAQ,CAACp2C,CAAD,CAAUxE,CAAV,CAAkB25C,CAAlB,CAAyB3lB,CAAzB,CAA+B,CACzC2lB,CAAJ,CACEA,CAAAA,MAAA,CAAYn1C,CAAZ,CADF,EAGOxE,CAGL,EAHgBA,CAAA,CAAO,CAAP,CAGhB,GAFEA,CAEF,CAFW25C,CAAA35C,OAAA,EAEX,EAAAA,CAAA8E,OAAA,CAAcN,CAAd,CANF,CAQMwvB,EA9CR,EAAM2mB,CAAA,CA8CE3mB,CA9CF,CAqCyC,CAjB1C,OAwCG6mB,QAAQ,CAACr2C,CAAD,CAAUwvB,CAAV,CAAgB,CAC9BxvB,CAAA0b,OAAA,EACM8T,EA9DR,EAAM2mB,CAAA,CA8DE3mB,CA9DF,CA4D0B,CAxC3B,MA+DE8mB,QAAQ,CAACt2C,CAAD,CAAUxE,CAAV,CAAkB25C,CAAlB,CAAyB3lB,CAAzB,CAA+B,CAG5C,IAAA4mB,MAAA,CAAWp2C,CAAX,CAAoBxE,CAApB,CAA4B25C,CAA5B,CAAmC3lB,CAAnC,CAH4C,CA/DzC,UAkFM3Q,QAAQ,CAAC7e,CAAD,CAAUmC,CAAV,CAAqBqtB,CAArB,CAA2B,CAC5CrtB,CAAA,CAAYhJ,CAAA,CAASgJ,CAAT,CAAA,CACEA,CADF,CAEE/I,CAAA,CAAQ+I,CAAR,CAAA,CAAqBA,CAAAzH,KAAA,CAAe,GAAf,CAArB,CAA2C,EACzDrB,EAAA,CAAQ2G,CAAR,CAAiB,QAAS,CAACA,CAAD,CAAU,CAClCsP,EAAA,CAAetP,CAAf,CAAwBmC,CAAxB,CADkC,CAApC,CAGMqtB,EA7GR,EAAM2mB,CAAA,CA6GE3mB,CA7GF,CAsGwC,CAlFzC,aAyGSnF,QAAQ,CAACrqB,CAAD,CAAUmC,CAAV,CAAqBqtB,CAArB,CAA2B,CAC/CrtB,CAAA,CAAYhJ,CAAA,CAASgJ,CAAT,CAAA,CACEA,CADF,CAEE/I,CAAA,CAAQ+I,CAAR,CAAA,CAAqBA,CAAAzH,KAAA,CAAe,GAAf,CAArB,CAA2C,EACzDrB,EAAA,CAAQ2G,CAAR,CAAiB,QAAS,CAACA,CAAD,CAAU,CAClCkP,EAAA,CAAkBlP,CAAlB,CAA2BmC,CAA3B,CADkC,CAApC,CAGMqtB,EApIR,EAAM2mB,CAAA,CAoIE3mB,CApIF,CA6H2C,CAzG5C,UAiIM9E,QAAQ,CAAC1qB,CAAD,CAAUu2C,CAAV,CAAe76B,CAAf,CAAuB8T,CAAvB,CAA6B,CAC9Cn2B,CAAA,CAAQ2G,CAAR,CAAiB,QAAS,CAACA,CAAD,CAAU,CAClCsP,EAAA,CAAetP,CAAf,CAAwBu2C,CAAxB,CACArnC,GAAA,CAAkBlP,CAAlB;AAA2B0b,CAA3B,CAFkC,CAApC,CAIM8T,EA1JR,EAAM2mB,CAAA,CA0JE3mB,CA1JF,CAqJ0C,CAjI3C,SAyIK9zB,CAzIL,CAvBuE,CAApE,CAlEyC,CAAhC,CAn1BvB,CAm0EIomB,GAAiBjpB,CAAA,CAAO,UAAP,CASrBwN,GAAAoL,QAAA,CAA2B,CAAC,UAAD,CAAa,uBAAb,CAy5C3B,KAAIwZ,GAAgB,0BAApB,CAi8CIqI,GAAqBz6B,CAAA,CAAO,cAAP,CAj8CzB,CA66DI29C,GAAa,iCA76DjB,CA86DIlhB,GAAgB,MAAS,EAAT,OAAsB,GAAtB,KAAkC,EAAlC,CA96DpB,CA+6DIsB,GAAkB/9B,CAAA,CAAO,WAAP,CA6QtB8+B,GAAA1jB,UAAA,CACEojB,EAAApjB,UADF,CAEEoiB,EAAApiB,UAFF,CAE+B,SAMpB,CAAA,CANoB,WAYlB,CAAA,CAZkB,QA0BrB2jB,EAAA,CAAe,UAAf,CA1BqB,KA2CxBvgB,QAAQ,CAACA,CAAD,CAAM3W,CAAN,CAAe,CAC1B,GAAI5E,CAAA,CAAYub,CAAZ,CAAJ,CACE,MAAO,KAAA0f,MAET,KAAIt2B,EAAQ+1C,EAAAt0C,KAAA,CAAgBmV,CAAhB,CACR5W,EAAA,CAAM,CAAN,CAAJ,EAAc,IAAA4D,KAAA,CAAUzD,kBAAA,CAAmBH,CAAA,CAAM,CAAN,CAAnB,CAAV,CACd,EAAIA,CAAA,CAAM,CAAN,CAAJ,EAAgBA,CAAA,CAAM,CAAN,CAAhB,GAA0B,IAAAo1B,OAAA,CAAYp1B,CAAA,CAAM,CAAN,CAAZ,EAAwB,EAAxB,CAC1B,KAAAgV,KAAA,CAAUhV,CAAA,CAAM,CAAN,CAAV,EAAsB,EAAtB,CAA0BC,CAA1B,CAEA,OAAO,KATmB,CA3CC,UAkEnBk3B,EAAA,CAAe,YAAf,CAlEmB;KA+EvBA,EAAA,CAAe,QAAf,CA/EuB,MA4FvBA,EAAA,CAAe,QAAf,CA5FuB,MA+GvBE,EAAA,CAAqB,QAArB,CAA+B,QAAQ,CAACzzB,CAAD,CAAO,CAClD,MAAyB,GAAlB,EAAAA,CAAArG,OAAA,CAAY,CAAZ,CAAA,CAAwBqG,CAAxB,CAA+B,GAA/B,CAAqCA,CADM,CAA9C,CA/GuB,QAwIrBwxB,QAAQ,CAACA,CAAD,CAAS4gB,CAAT,CAAqB,CACnC,OAAQt7C,SAAAlC,OAAR,EACE,KAAK,CAAL,CACE,MAAO,KAAA28B,SACT,MAAK,CAAL,CACE,GAAIz8B,CAAA,CAAS08B,CAAT,CAAJ,CACE,IAAAD,SAAA,CAAgB/0B,EAAA,CAAcg1B,CAAd,CADlB,KAEO,IAAI75B,CAAA,CAAS65B,CAAT,CAAJ,CACL,IAAAD,SAAA,CAAgBC,CADX,KAGL,MAAMe,GAAA,CAAgB,UAAhB,CAAN,CAGF,KACF,SACM96B,CAAA,CAAY26C,CAAZ,CAAJ,EAA8C,IAA9C,GAA+BA,CAA/B,CACE,OAAO,IAAA7gB,SAAA,CAAcC,CAAd,CADT,CAGE,IAAAD,SAAA,CAAcC,CAAd,CAHF,CAG0B4gB,CAjB9B,CAqBA,IAAA5f,UAAA,EACA,OAAO,KAvB4B,CAxIR,MAgLvBiB,EAAA,CAAqB,QAArB,CAA+Bn8B,EAA/B,CAhLuB,SA0LpB+E,QAAQ,EAAG,CAClB,IAAA24B,UAAA,CAAiB,CAAA,CACjB,OAAO,KAFW,CA1LS,CAkkB/B,KAAIiB,GAAezhC,CAAA,CAAO,QAAP,CAAnB,CACIwjC,GAAsB,EAD1B,CAEIxB,EAFJ,CAgEI6b,GAAY,CAEZ,MAFY,CAELC,QAAQ,EAAE,CAAC,MAAO,KAAR,CAFL,CAGZ,MAHY,CAGLC,QAAQ,EAAE,CAAC,MAAO,CAAA,CAAR,CAHL;AAIZ,OAJY,CAIJC,QAAQ,EAAE,CAAC,MAAO,CAAA,CAAR,CAJN,WAKFn7C,CALE,CAMZ,GANY,CAMRo7C,QAAQ,CAACl4C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAC7BD,CAAA,CAAEA,CAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAiB6Q,EAAA,CAAEA,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CACrB,OAAI7X,EAAA,CAAUyoB,CAAV,CAAJ,CACMzoB,CAAA,CAAU0oB,CAAV,CAAJ,CACSD,CADT,CACaC,CADb,CAGOD,CAJT,CAMOzoB,CAAA,CAAU0oB,CAAV,CAAA,CAAaA,CAAb,CAAe7rB,CARO,CANnB,CAeZ,GAfY,CAeRm+C,QAAQ,CAACn4C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CACzBD,CAAA,CAAEA,CAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAiB6Q,EAAA,CAAEA,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CACrB,QAAQ7X,CAAA,CAAUyoB,CAAV,CAAA,CAAaA,CAAb,CAAe,CAAvB,GAA2BzoB,CAAA,CAAU0oB,CAAV,CAAA,CAAaA,CAAb,CAAe,CAA1C,CAFyB,CAfnB,CAmBZ,GAnBY,CAmBRuyB,QAAQ,CAACp4C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,CAAuB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAxB,CAnBnB,CAoBZ,GApBY,CAoBRqjC,QAAQ,CAACr4C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,CAAuB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAxB,CApBnB,CAqBZ,GArBY,CAqBRsjC,QAAQ,CAACt4C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,CAAuB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAxB,CArBnB,CAsBZ,GAtBY,CAsBRujC,QAAQ,CAACv4C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,CAAuB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAxB,CAtBnB,CAuBZ,GAvBY,CAuBRlY,CAvBQ,CAwBZ,KAxBY,CAwBN07C,QAAQ,CAACx4C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAkBC,CAAlB,CAAoB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,GAAyB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAA1B,CAxBtB,CAyBZ,KAzBY,CAyBNyjC,QAAQ,CAACz4C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAkBC,CAAlB,CAAoB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,GAAyB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAA1B,CAzBtB,CA0BZ,IA1BY,CA0BP0jC,QAAQ,CAAC14C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,EAAwB6Q,CAAA,CAAE7lB,CAAF;AAAQgV,CAAR,CAAzB,CA1BpB,CA2BZ,IA3BY,CA2BP2jC,QAAQ,CAAC34C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,EAAwB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAzB,CA3BpB,CA4BZ,GA5BY,CA4BR4jC,QAAQ,CAAC54C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,CAAuB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAxB,CA5BnB,CA6BZ,GA7BY,CA6BR6jC,QAAQ,CAAC74C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,CAAuB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAxB,CA7BnB,CA8BZ,IA9BY,CA8BP8jC,QAAQ,CAAC94C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,EAAwB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAzB,CA9BpB,CA+BZ,IA/BY,CA+BP+jC,QAAQ,CAAC/4C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,EAAwB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAzB,CA/BpB,CAgCZ,IAhCY,CAgCPgkC,QAAQ,CAACh5C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,EAAwB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAzB,CAhCpB,CAiCZ,IAjCY,CAiCPikC,QAAQ,CAACj5C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,EAAwB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAzB,CAjCpB,CAkCZ,GAlCY,CAkCRkkC,QAAQ,CAACl5C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOD,EAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAP,CAAuB6Q,CAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAxB,CAlCnB,CAoCZ,GApCY,CAoCRmkC,QAAQ,CAACn5C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiBC,CAAjB,CAAmB,CAAC,MAAOA,EAAA,CAAE7lB,CAAF,CAAQgV,CAAR,CAAA,CAAgBhV,CAAhB,CAAsBgV,CAAtB,CAA8B4Q,CAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAA9B,CAAR,CApCnB,CAqCZ,GArCY,CAqCRokC,QAAQ,CAACp5C,CAAD,CAAOgV,CAAP,CAAe4Q,CAAf,CAAiB,CAAC,MAAO,CAACA,CAAA,CAAE5lB,CAAF,CAAQgV,CAAR,CAAT,CArCjB,CAhEhB,CAwGIqkC,GAAS,GAAK,IAAL,GAAe,IAAf,GAAyB,IAAzB,GAAmC,IAAnC,GAA6C,IAA7C,CAAmD,GAAnD,CAAuD,GAAvD,CAA4D,GAA5D,CAAgE,GAAhE,CAxGb;AAiHIzb,GAAQA,QAAS,CAAChiB,CAAD,CAAU,CAC7B,IAAAA,QAAA,CAAeA,CADc,CAI/BgiB,GAAAvoB,UAAA,CAAkB,aACHuoB,EADG,KAGX0b,QAAS,CAACxvB,CAAD,CAAO,CACnB,IAAAA,KAAA,CAAYA,CAEZ,KAAApuB,MAAA,CAAa,CACb,KAAA69C,GAAA,CAAUv/C,CACV,KAAAw/C,OAAA,CAAc,GAEd,KAAAC,OAAA,CAAc,EAEd,KAAI9sB,CAGJ,KAFI7rB,CAEJ,CAFW,EAEX,CAAO,IAAApF,MAAP,CAAoB,IAAAouB,KAAAzvB,OAApB,CAAA,CAAsC,CACpC,IAAAk/C,GAAA,CAAU,IAAAzvB,KAAA1qB,OAAA,CAAiB,IAAA1D,MAAjB,CACV,IAAI,IAAAg+C,GAAA,CAAQ,KAAR,CAAJ,CACE,IAAAC,WAAA,CAAgB,IAAAJ,GAAhB,CADF,KAEO,IAAI,IAAAl8C,SAAA,CAAc,IAAAk8C,GAAd,CAAJ,EAA8B,IAAAG,GAAA,CAAQ,GAAR,CAA9B,EAA8C,IAAAr8C,SAAA,CAAc,IAAAu8C,KAAA,EAAd,CAA9C,CACL,IAAAC,WAAA,EADK,KAEA,IAAI,IAAAC,QAAA,CAAa,IAAAP,GAAb,CAAJ,CACL,IAAAQ,UAAA,EAEA,CAAI,IAAAC,IAAA,CAAS,IAAT,CAAJ,GAAkC,GAAlC,GAAsBl5C,CAAA,CAAK,CAAL,CAAtB,GACK6rB,CADL,CACa,IAAA8sB,OAAA,CAAY,IAAAA,OAAAp/C,OAAZ,CAAiC,CAAjC,CADb,KAEEsyB,CAAA7rB,KAFF,CAE4C,EAF5C,GAEe6rB,CAAA7C,KAAAzrB,QAAA,CAAmB,GAAnB,CAFf,CAHK;IAOA,IAAI,IAAAq7C,GAAA,CAAQ,aAAR,CAAJ,CACL,IAAAD,OAAAv+C,KAAA,CAAiB,OACR,IAAAQ,MADQ,MAET,IAAA69C,GAFS,MAGR,IAAAS,IAAA,CAAS,KAAT,CAHQ,EAGW,IAAAN,GAAA,CAAQ,IAAR,CAHX,EAG6B,IAAAA,GAAA,CAAQ,MAAR,CAH7B,CAAjB,CAOA,CAFI,IAAAA,GAAA,CAAQ,IAAR,CAEJ,EAFmB54C,CAAA7E,QAAA,CAAa,IAAAs9C,GAAb,CAEnB,CADI,IAAAG,GAAA,CAAQ,IAAR,CACJ,EADmB54C,CAAA+L,MAAA,EACnB,CAAA,IAAAnR,MAAA,EARK,KASA,IAAI,IAAAu+C,aAAA,CAAkB,IAAAV,GAAlB,CAAJ,CAAgC,CACrC,IAAA79C,MAAA,EACA,SAFqC,CAAhC,IAGA,CACL,IAAIw+C,EAAM,IAAAX,GAANW,CAAgB,IAAAN,KAAA,EAApB,CACIO,EAAMD,CAANC,CAAY,IAAAP,KAAA,CAAU,CAAV,CADhB,CAEI35C,EAAK63C,EAAA,CAAU,IAAAyB,GAAV,CAFT,CAGIa,EAAMtC,EAAA,CAAUoC,CAAV,CAHV,CAIIG,EAAMvC,EAAA,CAAUqC,CAAV,CACNE,EAAJ,EACE,IAAAZ,OAAAv+C,KAAA,CAAiB,OAAQ,IAAAQ,MAAR,MAA0By+C,CAA1B,IAAmCE,CAAnC,CAAjB,CACA,CAAA,IAAA3+C,MAAA,EAAc,CAFhB,EAGW0+C,CAAJ,EACL,IAAAX,OAAAv+C,KAAA,CAAiB,OAAQ,IAAAQ,MAAR,MAA0Bw+C,CAA1B,IAAmCE,CAAnC,CAAjB,CACA,CAAA,IAAA1+C,MAAA,EAAc,CAFT,EAGIuE,CAAJ,EACL,IAAAw5C,OAAAv+C,KAAA,CAAiB,OACR,IAAAQ,MADQ;KAET,IAAA69C,GAFS,IAGXt5C,CAHW,MAIR,IAAA+5C,IAAA,CAAS,KAAT,CAJQ,EAIW,IAAAN,GAAA,CAAQ,IAAR,CAJX,CAAjB,CAMA,CAAA,IAAAh+C,MAAA,EAAc,CAPT,EASL,IAAA4+C,WAAA,CAAgB,4BAAhB,CAA8C,IAAA5+C,MAA9C,CAA0D,IAAAA,MAA1D,CAAuE,CAAvE,CArBG,CAwBP,IAAA89C,OAAA,CAAc,IAAAD,GAjDsB,CAmDtC,MAAO,KAAAE,OA/DY,CAHL,IAqEZC,QAAQ,CAACa,CAAD,CAAQ,CAClB,MAAmC,EAAnC,GAAOA,CAAAl8C,QAAA,CAAc,IAAAk7C,GAAd,CADW,CArEJ,KAyEXS,QAAQ,CAACO,CAAD,CAAQ,CACnB,MAAuC,EAAvC,GAAOA,CAAAl8C,QAAA,CAAc,IAAAm7C,OAAd,CADY,CAzEL,MA6EVI,QAAQ,CAACv+C,CAAD,CAAI,CACZw6B,CAAAA,CAAMx6B,CAANw6B,EAAW,CACf,OAAQ,KAAAn6B,MAAD,CAAcm6B,CAAd,CAAoB,IAAA/L,KAAAzvB,OAApB,CAAwC,IAAAyvB,KAAA1qB,OAAA,CAAiB,IAAA1D,MAAjB,CAA8Bm6B,CAA9B,CAAxC,CAA6E,CAAA,CAFpE,CA7EF,UAkFNx4B,QAAQ,CAACk8C,CAAD,CAAK,CACrB,MAAQ,GAAR,EAAeA,CAAf,EAA2B,GAA3B,EAAqBA,CADA,CAlFP,cAsFFU,QAAQ,CAACV,CAAD,CAAK,CAEzB,MAAe,GAAf,GAAQA,CAAR,EAA6B,IAA7B,GAAsBA,CAAtB,EAA4C,IAA5C,GAAqCA,CAArC,EACe,IADf,GACQA,CADR,EAC8B,IAD9B,GACuBA,CADvB,EAC6C,QAD7C;AACsCA,CAHb,CAtFX,SA4FPO,QAAQ,CAACP,CAAD,CAAK,CACpB,MAAQ,GAAR,EAAeA,CAAf,EAA2B,GAA3B,EAAqBA,CAArB,EACQ,GADR,EACeA,CADf,EAC2B,GAD3B,EACqBA,CADrB,EAEQ,GAFR,GAEgBA,CAFhB,EAE6B,GAF7B,GAEsBA,CAHF,CA5FN,eAkGDiB,QAAQ,CAACjB,CAAD,CAAK,CAC1B,MAAe,GAAf,GAAQA,CAAR,EAA6B,GAA7B,GAAsBA,CAAtB,EAAoC,IAAAl8C,SAAA,CAAck8C,CAAd,CADV,CAlGZ,YAsGJe,QAAQ,CAACxiC,CAAD,CAAQ2iC,CAAR,CAAeC,CAAf,CAAoB,CACtCA,CAAA,CAAMA,CAAN,EAAa,IAAAh/C,MACTi/C,EAAAA,CAAUx9C,CAAA,CAAUs9C,CAAV,CACA,CAAJ,IAAI,CAAGA,CAAH,CAAY,GAAZ,CAAkB,IAAA/+C,MAAlB,CAA+B,IAA/B,CAAsC,IAAAouB,KAAA9O,UAAA,CAAoBy/B,CAApB,CAA2BC,CAA3B,CAAtC,CAAwE,GAAxE,CACJ,GADI,CACEA,CAChB,MAAMhf,GAAA,CAAa,QAAb,CACF5jB,CADE,CACK6iC,CADL,CACa,IAAA7wB,KADb,CAAN,CALsC,CAtGxB,YA+GJ+vB,QAAQ,EAAG,CAGrB,IAFA,IAAIvP,EAAS,EAAb,CACImQ,EAAQ,IAAA/+C,MACZ,CAAO,IAAAA,MAAP,CAAoB,IAAAouB,KAAAzvB,OAApB,CAAA,CAAsC,CACpC,IAAIk/C,EAAKr4C,CAAA,CAAU,IAAA4oB,KAAA1qB,OAAA,CAAiB,IAAA1D,MAAjB,CAAV,CACT,IAAU,GAAV,EAAI69C,CAAJ,EAAiB,IAAAl8C,SAAA,CAAck8C,CAAd,CAAjB,CACEjP,CAAA,EAAUiP,CADZ,KAEO,CACL,IAAIqB,EAAS,IAAAhB,KAAA,EACb,IAAU,GAAV,EAAIL,CAAJ,EAAiB,IAAAiB,cAAA,CAAmBI,CAAnB,CAAjB,CACEtQ,CAAA;AAAUiP,CADZ,KAEO,IAAI,IAAAiB,cAAA,CAAmBjB,CAAnB,CAAJ,EACHqB,CADG,EACO,IAAAv9C,SAAA,CAAcu9C,CAAd,CADP,EAEiC,GAFjC,EAEHtQ,CAAAlrC,OAAA,CAAckrC,CAAAjwC,OAAd,CAA8B,CAA9B,CAFG,CAGLiwC,CAAA,EAAUiP,CAHL,KAIA,IAAI,CAAA,IAAAiB,cAAA,CAAmBjB,CAAnB,CAAJ,EACDqB,CADC,EACU,IAAAv9C,SAAA,CAAcu9C,CAAd,CADV,EAEiC,GAFjC,EAEHtQ,CAAAlrC,OAAA,CAAckrC,CAAAjwC,OAAd,CAA8B,CAA9B,CAFG,CAKL,KALK,KAGL,KAAAigD,WAAA,CAAgB,kBAAhB,CAXG,CAgBP,IAAA5+C,MAAA,EApBoC,CAsBtC4uC,CAAA,EAAS,CACT,KAAAmP,OAAAv+C,KAAA,CAAiB,OACRu/C,CADQ,MAETnQ,CAFS,MAGT,CAAA,CAHS,IAIXrqC,QAAQ,EAAG,CAAE,MAAOqqC,EAAT,CAJA,CAAjB,CA1BqB,CA/GP,WAiJLyP,QAAQ,EAAG,CAQpB,IAPA,IAAIlc,EAAS,IAAb,CAEIgd,EAAQ,EAFZ,CAGIJ,EAAQ,IAAA/+C,MAHZ,CAKIo/C,CALJ,CAKaC,CALb,CAKwBC,CALxB,CAKoCzB,CAEpC,CAAO,IAAA79C,MAAP,CAAoB,IAAAouB,KAAAzvB,OAApB,CAAA,CAAsC,CACpCk/C,CAAA,CAAK,IAAAzvB,KAAA1qB,OAAA,CAAiB,IAAA1D,MAAjB,CACL,IAAW,GAAX,GAAI69C,CAAJ,EAAkB,IAAAO,QAAA,CAAaP,CAAb,CAAlB,EAAsC,IAAAl8C,SAAA,CAAck8C,CAAd,CAAtC,CACa,GACX,GADIA,CACJ,GADgBuB,CAChB,CAD0B,IAAAp/C,MAC1B,EAAAm/C,CAAA,EAAStB,CAFX,KAIE,MAEF;IAAA79C,MAAA,EARoC,CAYtC,GAAIo/C,CAAJ,CAEE,IADAC,CACA,CADY,IAAAr/C,MACZ,CAAOq/C,CAAP,CAAmB,IAAAjxB,KAAAzvB,OAAnB,CAAA,CAAqC,CACnCk/C,CAAA,CAAK,IAAAzvB,KAAA1qB,OAAA,CAAiB27C,CAAjB,CACL,IAAW,GAAX,GAAIxB,CAAJ,CAAgB,CACdyB,CAAA,CAAaH,CAAAr4B,OAAA,CAAas4B,CAAb,CAAuBL,CAAvB,CAA+B,CAA/B,CACbI,EAAA,CAAQA,CAAAr4B,OAAA,CAAa,CAAb,CAAgBs4B,CAAhB,CAA0BL,CAA1B,CACR,KAAA/+C,MAAA,CAAaq/C,CACb,MAJc,CAMhB,GAAI,IAAAd,aAAA,CAAkBV,CAAlB,CAAJ,CACEwB,CAAA,EADF,KAGE,MAXiC,CAiBnCpuB,CAAAA,CAAQ,OACH8tB,CADG,MAEJI,CAFI,CAMZ,IAAI/C,EAAAh9C,eAAA,CAAyB+/C,CAAzB,CAAJ,CACEluB,CAAA1sB,GACA,CADW63C,EAAA,CAAU+C,CAAV,CACX,CAAAluB,CAAA7rB,KAAA,CAAag3C,EAAA,CAAU+C,CAAV,CAFf,KAGO,CACL,IAAIr1C,EAASs3B,EAAA,CAAS+d,CAAT,CAAgB,IAAAj/B,QAAhB,CAA8B,IAAAkO,KAA9B,CACb6C,EAAA1sB,GAAA,CAAW5D,CAAA,CAAO,QAAQ,CAAC2D,CAAD,CAAOgV,CAAP,CAAe,CACvC,MAAQxP,EAAA,CAAOxF,CAAP,CAAagV,CAAb,CAD+B,CAA9B,CAER,QACO8Q,QAAQ,CAAC9lB,CAAD,CAAOxE,CAAP,CAAc,CAC5B,MAAOogC,GAAA,CAAO57B,CAAP,CAAa66C,CAAb,CAAoBr/C,CAApB,CAA2BqiC,CAAA/T,KAA3B,CAAwC+T,CAAAjiB,QAAxC,CADqB,CAD7B,CAFQ,CAFN,CAWP,IAAA69B,OAAAv+C,KAAA,CAAiByxB,CAAjB,CAEIquB,EAAJ,GACE,IAAAvB,OAAAv+C,KAAA,CAAiB,OACT4/C,CADS,MAET,GAFS,MAGT,CAAA,CAHS,CAAjB,CAKA,CAAA,IAAArB,OAAAv+C,KAAA,CAAiB,OACR4/C,CADQ,CACE,CADF,MAETE,CAFS,MAGT,CAAA,CAHS,CAAjB,CANF,CA7DoB,CAjJN;WA4NJrB,QAAQ,CAACsB,CAAD,CAAQ,CAC1B,IAAIR,EAAQ,IAAA/+C,MACZ,KAAAA,MAAA,EAIA,KAHA,IAAI+wC,EAAS,EAAb,CACIyO,EAAYD,CADhB,CAEIrgC,EAAS,CAAA,CACb,CAAO,IAAAlf,MAAP,CAAoB,IAAAouB,KAAAzvB,OAApB,CAAA,CAAsC,CACpC,IAAIk/C,EAAK,IAAAzvB,KAAA1qB,OAAA,CAAiB,IAAA1D,MAAjB,CAAT,CACAw/C,EAAAA,CAAAA,CAAa3B,CACb,IAAI3+B,CAAJ,CACa,GAAX,GAAI2+B,CAAJ,EACM4B,CAIJ,CAJU,IAAArxB,KAAA9O,UAAA,CAAoB,IAAAtf,MAApB,CAAiC,CAAjC,CAAoC,IAAAA,MAApC,CAAiD,CAAjD,CAIV,CAHKy/C,CAAAt5C,MAAA,CAAU,aAAV,CAGL,EAFE,IAAAy4C,WAAA,CAAgB,6BAAhB,CAAgDa,CAAhD,CAAsD,GAAtD,CAEF,CADA,IAAAz/C,MACA,EADc,CACd,CAAA+wC,CAAA,EAAU1wC,MAAAC,aAAA,CAAoBU,QAAA,CAASy+C,CAAT,CAAc,EAAd,CAApB,CALZ,EASI1O,CATJ,CAQE,CADI2O,CACJ,CADU/B,EAAA,CAAOE,CAAP,CACV,EACE9M,CADF,CACY2O,CADZ,CAGE3O,CAHF,CAGY8M,CAGd,CAAA3+B,CAAA,CAAS,CAAA,CAfX,KAgBO,IAAW,IAAX,GAAI2+B,CAAJ,CACL3+B,CAAA,CAAS,CAAA,CADJ,KAEA,CAAA,GAAI2+B,CAAJ,GAAW0B,CAAX,CAAkB,CACvB,IAAAv/C,MAAA,EACA,KAAA+9C,OAAAv+C,KAAA,CAAiB,OACRu/C,CADQ,MAETS,CAFS,QAGPzO,CAHO,MAIT,CAAA,CAJS,IAKXxsC,QAAQ,EAAG,CAAE,MAAOwsC,EAAT,CALA,CAAjB,CAOA,OATuB,CAWvBA,CAAA;AAAU8M,CAXL,CAaP,IAAA79C,MAAA,EAlCoC,CAoCtC,IAAA4+C,WAAA,CAAgB,oBAAhB,CAAsCG,CAAtC,CA1C0B,CA5NZ,CA8QlB,KAAI3c,GAASA,QAAS,CAACH,CAAD,CAAQH,CAAR,CAAiB5hB,CAAjB,CAA0B,CAC9C,IAAA+hB,MAAA,CAAaA,CACb,KAAAH,QAAA,CAAeA,CACf,KAAA5hB,QAAA,CAAeA,CAH+B,CAMhDkiB,GAAAud,KAAA,CAAch/C,CAAA,CAAO,QAAS,EAAG,CAC/B,MAAO,EADwB,CAAnB,CAEX,UACS,CAAA,CADT,CAFW,CAMdyhC,GAAAzoB,UAAA,CAAmB,aACJyoB,EADI,OAGV/8B,QAAS,CAAC+oB,CAAD,CAAOhpB,CAAP,CAAa,CAC3B,IAAAgpB,KAAA,CAAYA,CAGZ,KAAAhpB,KAAA,CAAYA,CAEZ,KAAA24C,OAAA,CAAc,IAAA9b,MAAA2b,IAAA,CAAexvB,CAAf,CAEVhpB,EAAJ,GAGE,IAAAw6C,WAEA,CAFkB,IAAAC,UAElB,CAAA,IAAAC,aAAA,CACA,IAAAC,YADA,CAEA,IAAAC,YAFA,CAGA,IAAAC,YAHA,CAGmBC,QAAQ,EAAG,CAC5B,IAAAtB,WAAA,CAAgB,mBAAhB,CAAqC,MAAOxwB,CAAP,OAAoB,CAApB,CAArC,CAD4B,CARhC,CAaA,KAAItuB,EAAQsF,CAAA,CAAO,IAAA+6C,QAAA,EAAP,CAAwB,IAAAC,WAAA,EAET,EAA3B,GAAI,IAAArC,OAAAp/C,OAAJ;AACE,IAAAigD,WAAA,CAAgB,wBAAhB,CAA0C,IAAAb,OAAA,CAAY,CAAZ,CAA1C,CAGFj+C,EAAAmqB,QAAA,CAAgB,CAAC,CAACnqB,CAAAmqB,QAClBnqB,EAAAka,SAAA,CAAiB,CAAC,CAACla,CAAAka,SAEnB,OAAOla,EA9BoB,CAHZ,SAoCRqgD,QAAS,EAAG,CACnB,IAAIA,CACJ,IAAI,IAAAE,OAAA,CAAY,GAAZ,CAAJ,CACEF,CACA,CADU,IAAAF,YAAA,EACV,CAAA,IAAAK,QAAA,CAAa,GAAb,CAFF,KAGO,IAAI,IAAAD,OAAA,CAAY,GAAZ,CAAJ,CACLF,CAAA,CAAU,IAAAI,iBAAA,EADL,KAEA,IAAI,IAAAF,OAAA,CAAY,GAAZ,CAAJ,CACLF,CAAA,CAAU,IAAAjO,OAAA,EADL,KAEA,CACL,IAAIjhB,EAAQ,IAAAovB,OAAA,EAEZ,EADAF,CACA,CADUlvB,CAAA1sB,GACV,GACE,IAAAq6C,WAAA,CAAgB,0BAAhB,CAA4C3tB,CAA5C,CAEEA,EAAA7rB,KAAJ,GACE+6C,CAAAnmC,SACA,CADmB,CAAA,CACnB,CAAAmmC,CAAAl2B,QAAA,CAAkB,CAAA,CAFpB,CANK,CAaP,IADA,IAAUhrB,CACV,CAAQipC,CAAR,CAAe,IAAAmY,OAAA,CAAY,GAAZ,CAAiB,GAAjB,CAAsB,GAAtB,CAAf,CAAA,CACoB,GAAlB,GAAInY,CAAA9Z,KAAJ,EACE+xB,CACA,CADU,IAAAL,aAAA,CAAkBK,CAAlB,CAA2BlhD,CAA3B,CACV,CAAAA,CAAA,CAAU,IAFZ,EAGyB,GAAlB,GAAIipC,CAAA9Z,KAAJ;CACLnvB,CACA,CADUkhD,CACV,CAAAA,CAAA,CAAU,IAAAH,YAAA,CAAiBG,CAAjB,CAFL,EAGkB,GAAlB,GAAIjY,CAAA9Z,KAAJ,EACLnvB,CACA,CADUkhD,CACV,CAAAA,CAAA,CAAU,IAAAJ,YAAA,CAAiBI,CAAjB,CAFL,EAIL,IAAAvB,WAAA,CAAgB,YAAhB,CAGJ,OAAOuB,EApCY,CApCJ,YA2ELvB,QAAQ,CAAC4B,CAAD,CAAMvvB,CAAN,CAAa,CAC/B,KAAM+O,GAAA,CAAa,QAAb,CAEA/O,CAAA7C,KAFA,CAEYoyB,CAFZ,CAEkBvvB,CAAAjxB,MAFlB,CAEgC,CAFhC,CAEoC,IAAAouB,KAFpC,CAE+C,IAAAA,KAAA9O,UAAA,CAAoB2R,CAAAjxB,MAApB,CAF/C,CAAN,CAD+B,CA3EhB,WAiFNygD,QAAQ,EAAG,CACpB,GAA2B,CAA3B,GAAI,IAAA1C,OAAAp/C,OAAJ,CACE,KAAMqhC,GAAA,CAAa,MAAb,CAA0D,IAAA5R,KAA1D,CAAN,CACF,MAAO,KAAA2vB,OAAA,CAAY,CAAZ,CAHa,CAjFL,MAuFXG,QAAQ,CAACwC,CAAD,CAAKC,CAAL,CAASC,CAAT,CAAaC,CAAb,CAAiB,CAC7B,GAAyB,CAAzB,CAAI,IAAA9C,OAAAp/C,OAAJ,CAA4B,CAC1B,IAAIsyB,EAAQ,IAAA8sB,OAAA,CAAY,CAAZ,CAAZ,CACI+C,EAAI7vB,CAAA7C,KACR,IAAI0yB,CAAJ,GAAUJ,CAAV,EAAgBI,CAAhB,GAAsBH,CAAtB,EAA4BG,CAA5B,GAAkCF,CAAlC,EAAwCE,CAAxC,GAA8CD,CAA9C,EACK,EAACH,CAAD,EAAQC,CAAR,EAAeC,CAAf,EAAsBC,CAAtB,CADL,CAEE,MAAO5vB,EALiB,CAQ5B,MAAO,CAAA,CATsB,CAvFd,QAmGTovB,QAAQ,CAACK,CAAD,CAAKC,CAAL,CAASC,CAAT,CAAaC,CAAb,CAAgB,CAE9B,MAAA,CADI5vB,CACJ,CADY,IAAAitB,KAAA,CAAUwC,CAAV,CAAcC,CAAd,CAAkBC,CAAlB;AAAsBC,CAAtB,CACZ,GACM,IAAAz7C,KAIG6rB,EAJW7rB,CAAA6rB,CAAA7rB,KAIX6rB,EAHL,IAAA2tB,WAAA,CAAgB,mBAAhB,CAAqC3tB,CAArC,CAGKA,CADP,IAAA8sB,OAAA5sC,MAAA,EACO8f,CAAAA,CALT,EAOO,CAAA,CATuB,CAnGf,SA+GRqvB,QAAQ,CAACI,CAAD,CAAI,CACd,IAAAL,OAAA,CAAYK,CAAZ,CAAL,EACE,IAAA9B,WAAA,CAAgB,4BAAhB,CAA+C8B,CAA/C,CAAoD,GAApD,CAAyD,IAAAxC,KAAA,EAAzD,CAFiB,CA/GJ,SAqHR6C,QAAQ,CAACx8C,CAAD,CAAKy8C,CAAL,CAAY,CAC3B,MAAOrgD,EAAA,CAAO,QAAQ,CAAC2D,CAAD,CAAOgV,CAAP,CAAe,CACnC,MAAO/U,EAAA,CAAGD,CAAH,CAASgV,CAAT,CAAiB0nC,CAAjB,CAD4B,CAA9B,CAEJ,UACQA,CAAAhnC,SADR,CAFI,CADoB,CArHZ,WA6HNinC,QAAQ,CAACC,CAAD,CAAOC,CAAP,CAAeH,CAAf,CAAqB,CACtC,MAAOrgD,EAAA,CAAO,QAAQ,CAAC2D,CAAD,CAAOgV,CAAP,CAAc,CAClC,MAAO4nC,EAAA,CAAK58C,CAAL,CAAWgV,CAAX,CAAA,CAAqB6nC,CAAA,CAAO78C,CAAP,CAAagV,CAAb,CAArB,CAA4C0nC,CAAA,CAAM18C,CAAN,CAAYgV,CAAZ,CADjB,CAA7B,CAEJ,UACS4nC,CAAAlnC,SADT,EAC0BmnC,CAAAnnC,SAD1B,EAC6CgnC,CAAAhnC,SAD7C,CAFI,CAD+B,CA7HvB,UAqIPonC,QAAQ,CAACF,CAAD,CAAO38C,CAAP,CAAWy8C,CAAX,CAAkB,CAClC,MAAOrgD,EAAA,CAAO,QAAQ,CAAC2D,CAAD,CAAOgV,CAAP,CAAe,CACnC,MAAO/U,EAAA,CAAGD,CAAH,CAASgV,CAAT,CAAiB4nC,CAAjB,CAAuBF,CAAvB,CAD4B,CAA9B,CAEJ,UACQE,CAAAlnC,SADR,EACyBgnC,CAAAhnC,SADzB,CAFI,CAD2B,CArInB;WA6ILomC,QAAQ,EAAG,CAErB,IADA,IAAIA,EAAa,EACjB,CAAA,CAAA,CAGE,GAFyB,CAErB,CAFA,IAAArC,OAAAp/C,OAEA,EAF2B,CAAA,IAAAu/C,KAAA,CAAU,GAAV,CAAe,GAAf,CAAoB,GAApB,CAAyB,GAAzB,CAE3B,EADFkC,CAAA5gD,KAAA,CAAgB,IAAAygD,YAAA,EAAhB,CACE,CAAA,CAAC,IAAAI,OAAA,CAAY,GAAZ,CAAL,CAGE,MAA8B,EACvB,GADCD,CAAAzhD,OACD,CAADyhD,CAAA,CAAW,CAAX,CAAC,CACD,QAAQ,CAAC97C,CAAD,CAAOgV,CAAP,CAAe,CAErB,IADA,IAAIxZ,CAAJ,CACSH,EAAI,CAAb,CAAgBA,CAAhB,CAAoBygD,CAAAzhD,OAApB,CAAuCgB,CAAA,EAAvC,CAA4C,CAC1C,IAAI0hD,EAAYjB,CAAA,CAAWzgD,CAAX,CACZ0hD,EAAJ,GACEvhD,CADF,CACUuhD,CAAA,CAAU/8C,CAAV,CAAgBgV,CAAhB,CADV,CAF0C,CAM5C,MAAOxZ,EARc,CAVZ,CA7IN,aAqKJmgD,QAAQ,EAAG,CAGtB,IAFA,IAAIiB,EAAO,IAAA7vB,WAAA,EAAX,CACIJ,CACJ,CAAA,CAAA,CACE,GAAKA,CAAL,CAAa,IAAAovB,OAAA,CAAY,GAAZ,CAAb,CACEa,CAAA,CAAO,IAAAE,SAAA,CAAcF,CAAd,CAAoBjwB,CAAA1sB,GAApB,CAA8B,IAAAqM,OAAA,EAA9B,CADT,KAGE,OAAOswC,EAPW,CArKP,QAiLTtwC,QAAQ,EAAG,CAIjB,IAHA,IAAIqgB,EAAQ,IAAAovB,OAAA,EAAZ,CACI97C,EAAK,IAAAu9B,QAAA,CAAa7Q,CAAA7C,KAAb,CADT,CAEIkzB,EAAS,EACb,CAAA,CAAA,CACE,GAAKrwB,CAAL,CAAa,IAAAovB,OAAA,CAAY,GAAZ,CAAb,CACEiB,CAAA9hD,KAAA,CAAY,IAAA6xB,WAAA,EAAZ,CADF,KAEO,CACL,IAAIkwB;AAAWA,QAAQ,CAACj9C,CAAD,CAAOgV,CAAP,CAAe64B,CAAf,CAAsB,CACvC54B,CAAAA,CAAO,CAAC44B,CAAD,CACX,KAAK,IAAIxyC,EAAI,CAAb,CAAgBA,CAAhB,CAAoB2hD,CAAA3iD,OAApB,CAAmCgB,CAAA,EAAnC,CACE4Z,CAAA/Z,KAAA,CAAU8hD,CAAA,CAAO3hD,CAAP,CAAA,CAAU2E,CAAV,CAAgBgV,CAAhB,CAAV,CAEF,OAAO/U,EAAAI,MAAA,CAASL,CAAT,CAAeiV,CAAf,CALoC,CAO7C,OAAO,SAAQ,EAAG,CAChB,MAAOgoC,EADS,CARb,CAPQ,CAjLF,YAuMLlwB,QAAQ,EAAG,CACrB,MAAO,KAAAuuB,WAAA,EADc,CAvMN,YA2MLA,QAAQ,EAAG,CACrB,IAAIsB,EAAO,IAAAM,QAAA,EAAX,CACIR,CADJ,CAEI/vB,CACJ,OAAA,CAAKA,CAAL,CAAa,IAAAovB,OAAA,CAAY,GAAZ,CAAb,GACOa,CAAA92B,OAKE,EAJL,IAAAw0B,WAAA,CAAgB,0BAAhB,CACI,IAAAxwB,KAAA9O,UAAA,CAAoB,CAApB,CAAuB2R,CAAAjxB,MAAvB,CADJ,CAC0C,0BAD1C,CACsEixB,CADtE,CAIK,CADP+vB,CACO,CADC,IAAAQ,QAAA,EACD,CAAA,QAAQ,CAACl5C,CAAD,CAAQgR,CAAR,CAAgB,CAC7B,MAAO4nC,EAAA92B,OAAA,CAAY9hB,CAAZ,CAAmB04C,CAAA,CAAM14C,CAAN,CAAagR,CAAb,CAAnB,CAAyCA,CAAzC,CADsB,CANjC,EAUO4nC,CAdc,CA3MN,SA4NRM,QAAQ,EAAG,CAClB,IAAIN,EAAO,IAAArB,UAAA,EAAX,CACIsB,CADJ,CAEIlwB,CACJ,IAAa,IAAAovB,OAAA,CAAY,GAAZ,CAAb,CAAgC,CAC9Bc,CAAA,CAAS,IAAAK,QAAA,EACT;GAAKvwB,CAAL,CAAa,IAAAovB,OAAA,CAAY,GAAZ,CAAb,CACE,MAAO,KAAAY,UAAA,CAAeC,CAAf,CAAqBC,CAArB,CAA6B,IAAAK,QAAA,EAA7B,CAEP,KAAA5C,WAAA,CAAgB,YAAhB,CAA8B3tB,CAA9B,CAL4B,CAAhC,IAQE,OAAOiwB,EAZS,CA5NH,WA4ONrB,QAAQ,EAAG,CAGpB,IAFA,IAAIqB,EAAO,IAAAO,WAAA,EAAX,CACIxwB,CACJ,CAAA,CAAA,CACE,GAAKA,CAAL,CAAa,IAAAovB,OAAA,CAAY,IAAZ,CAAb,CACEa,CAAA,CAAO,IAAAE,SAAA,CAAcF,CAAd,CAAoBjwB,CAAA1sB,GAApB,CAA8B,IAAAk9C,WAAA,EAA9B,CADT,KAGE,OAAOP,EAPS,CA5OL,YAwPLO,QAAQ,EAAG,CACrB,IAAIP,EAAO,IAAAQ,SAAA,EAAX,CACIzwB,CACJ,IAAKA,CAAL,CAAa,IAAAovB,OAAA,CAAY,IAAZ,CAAb,CACEa,CAAA,CAAO,IAAAE,SAAA,CAAcF,CAAd,CAAoBjwB,CAAA1sB,GAApB,CAA8B,IAAAk9C,WAAA,EAA9B,CAET,OAAOP,EANc,CAxPN,UAiQPQ,QAAQ,EAAG,CACnB,IAAIR,EAAO,IAAAS,WAAA,EAAX,CACI1wB,CACJ,IAAKA,CAAL,CAAa,IAAAovB,OAAA,CAAY,IAAZ,CAAiB,IAAjB,CAAsB,KAAtB,CAA4B,KAA5B,CAAb,CACEa,CAAA,CAAO,IAAAE,SAAA,CAAcF,CAAd,CAAoBjwB,CAAA1sB,GAApB,CAA8B,IAAAm9C,SAAA,EAA9B,CAET,OAAOR,EANY,CAjQJ;WA0QLS,QAAQ,EAAG,CACrB,IAAIT,EAAO,IAAAU,SAAA,EAAX,CACI3wB,CACJ,IAAKA,CAAL,CAAa,IAAAovB,OAAA,CAAY,GAAZ,CAAiB,GAAjB,CAAsB,IAAtB,CAA4B,IAA5B,CAAb,CACEa,CAAA,CAAO,IAAAE,SAAA,CAAcF,CAAd,CAAoBjwB,CAAA1sB,GAApB,CAA8B,IAAAo9C,WAAA,EAA9B,CAET,OAAOT,EANc,CA1QN,UAmRPU,QAAQ,EAAG,CAGnB,IAFA,IAAIV,EAAO,IAAAW,eAAA,EAAX,CACI5wB,CACJ,CAAQA,CAAR,CAAgB,IAAAovB,OAAA,CAAY,GAAZ,CAAgB,GAAhB,CAAhB,CAAA,CACEa,CAAA,CAAO,IAAAE,SAAA,CAAcF,CAAd,CAAoBjwB,CAAA1sB,GAApB,CAA8B,IAAAs9C,eAAA,EAA9B,CAET,OAAOX,EANY,CAnRJ,gBA4RDW,QAAQ,EAAG,CAGzB,IAFA,IAAIX,EAAO,IAAAY,MAAA,EAAX,CACI7wB,CACJ,CAAQA,CAAR,CAAgB,IAAAovB,OAAA,CAAY,GAAZ,CAAgB,GAAhB,CAAoB,GAApB,CAAhB,CAAA,CACEa,CAAA,CAAO,IAAAE,SAAA,CAAcF,CAAd,CAAoBjwB,CAAA1sB,GAApB,CAA8B,IAAAu9C,MAAA,EAA9B,CAET,OAAOZ,EANkB,CA5RV,OAqSVY,QAAQ,EAAG,CAChB,IAAI7wB,CACJ,OAAI,KAAAovB,OAAA,CAAY,GAAZ,CAAJ,CACS,IAAAF,QAAA,EADT,CAEO,CAAKlvB,CAAL,CAAa,IAAAovB,OAAA,CAAY,GAAZ,CAAb,EACE,IAAAe,SAAA,CAAchf,EAAAud,KAAd,CAA2B1uB,CAAA1sB,GAA3B;AAAqC,IAAAu9C,MAAA,EAArC,CADF,CAEA,CAAK7wB,CAAL,CAAa,IAAAovB,OAAA,CAAY,GAAZ,CAAb,EACE,IAAAU,QAAA,CAAa9vB,CAAA1sB,GAAb,CAAuB,IAAAu9C,MAAA,EAAvB,CADF,CAGE,IAAA3B,QAAA,EATO,CArSD,aAkTJJ,QAAQ,CAAC7N,CAAD,CAAS,CAC5B,IAAI/P,EAAS,IAAb,CACI4f,EAAQ,IAAA1B,OAAA,EAAAjyB,KADZ,CAEItkB,EAASs3B,EAAA,CAAS2gB,CAAT,CAAgB,IAAA7hC,QAAhB,CAA8B,IAAAkO,KAA9B,CAEb,OAAOztB,EAAA,CAAO,QAAQ,CAAC2H,CAAD,CAAQgR,CAAR,CAAgBhV,CAAhB,CAAsB,CAC1C,MAAOwF,EAAA,CAAOxF,CAAP,EAAe4tC,CAAA,CAAO5pC,CAAP,CAAcgR,CAAd,CAAf,CADmC,CAArC,CAEJ,QACO8Q,QAAQ,CAAC9hB,CAAD,CAAQxI,CAAR,CAAewZ,CAAf,CAAuB,CACrC,MAAO4mB,GAAA,CAAOgS,CAAA,CAAO5pC,CAAP,CAAcgR,CAAd,CAAP,CAA8ByoC,CAA9B,CAAqCjiD,CAArC,CAA4CqiC,CAAA/T,KAA5C,CAAyD+T,CAAAjiB,QAAzD,CAD8B,CADtC,CAFI,CALqB,CAlTb,aAgUJ8/B,QAAQ,CAACvhD,CAAD,CAAM,CACzB,IAAI0jC,EAAS,IAAb,CAEI6f,EAAU,IAAA3wB,WAAA,EACd,KAAAivB,QAAA,CAAa,GAAb,CAEA,OAAO3/C,EAAA,CAAO,QAAQ,CAAC2D,CAAD,CAAOgV,CAAP,CAAe,CAAA,IAC/B2oC,EAAIxjD,CAAA,CAAI6F,CAAJ,CAAUgV,CAAV,CAD2B,CAE/B3Z,EAAIqiD,CAAA,CAAQ19C,CAAR,CAAcgV,CAAd,CAF2B,CAG5BmH,CAEP,IAAI,CAACwhC,CAAL,CAAQ,MAAO3jD,EAEf,EADAiH,CACA,CADI06B,EAAA,CAAiBgiB,CAAA,CAAEtiD,CAAF,CAAjB,CAAuBwiC,CAAA/T,KAAvB,CACJ,IAAS7oB,CAAA+uB,KAAT,EAAmB6N,CAAAjiB,QAAAogB,eAAnB,IACE7f,CAKA,CALIlb,CAKJ,CAJM,KAIN,EAJeA,EAIf,GAHEkb,CAAA+f,IACA,CADQliC,CACR,CAAAmiB,CAAA6T,KAAA,CAAO,QAAQ,CAACxvB,CAAD,CAAM,CAAE2b,CAAA+f,IAAA;AAAQ17B,CAAV,CAArB,CAEF,EAAAS,CAAA,CAAIA,CAAAi7B,IANN,CAQA,OAAOj7B,EAf4B,CAA9B,CAgBJ,QACO6kB,QAAQ,CAAC9lB,CAAD,CAAOxE,CAAP,CAAcwZ,CAAd,CAAsB,CACpC,IAAIpa,EAAM8iD,CAAA,CAAQ19C,CAAR,CAAcgV,CAAd,CAGV,OADW2mB,GAAAiiB,CAAiBzjD,CAAA,CAAI6F,CAAJ,CAAUgV,CAAV,CAAjB4oC,CAAoC/f,CAAA/T,KAApC8zB,CACJ,CAAKhjD,CAAL,CAAP,CAAmBY,CAJiB,CADrC,CAhBI,CANkB,CAhUV,cAgWHggD,QAAQ,CAACv7C,CAAD,CAAK49C,CAAL,CAAoB,CACxC,IAAIb,EAAS,EACb,IAA8B,GAA9B,GAAI,IAAAb,UAAA,EAAAryB,KAAJ,EACE,EACEkzB,EAAA9hD,KAAA,CAAY,IAAA6xB,WAAA,EAAZ,CADF,OAES,IAAAgvB,OAAA,CAAY,GAAZ,CAFT,CADF,CAKA,IAAAC,QAAA,CAAa,GAAb,CAEA,KAAIne,EAAS,IAEb,OAAO,SAAQ,CAAC75B,CAAD,CAAQgR,CAAR,CAAgB,CAI7B,IAHA,IAAIC,EAAO,EAAX,CACIta,EAAUkjD,CAAA,CAAgBA,CAAA,CAAc75C,CAAd,CAAqBgR,CAArB,CAAhB,CAA+ChR,CAD7D,CAGS3I,EAAI,CAAb,CAAgBA,CAAhB,CAAoB2hD,CAAA3iD,OAApB,CAAmCgB,CAAA,EAAnC,CACE4Z,CAAA/Z,KAAA,CAAU8hD,CAAA,CAAO3hD,CAAP,CAAA,CAAU2I,CAAV,CAAiBgR,CAAjB,CAAV,CAEE8oC,EAAAA,CAAQ79C,CAAA,CAAG+D,CAAH,CAAUgR,CAAV,CAAkBra,CAAlB,CAARmjD,EAAsChhD,CAE1C6+B,GAAA,CAAiBhhC,CAAjB,CAA0BkjC,CAAA/T,KAA1B,CACA6R,GAAA,CAAiBmiB,CAAjB,CAAwBjgB,CAAA/T,KAAxB,CAGI7oB,EAAAA,CAAI68C,CAAAz9C,MACA,CAAAy9C,CAAAz9C,MAAA,CAAY1F,CAAZ,CAAqBsa,CAArB,CAAA,CACA6oC,CAAA,CAAM7oC,CAAA,CAAK,CAAL,CAAN,CAAeA,CAAA,CAAK,CAAL,CAAf,CAAwBA,CAAA,CAAK,CAAL,CAAxB,CAAiCA,CAAA,CAAK,CAAL,CAAjC,CAA0CA,CAAA,CAAK,CAAL,CAA1C,CAER,OAAO0mB,GAAA,CAAiB16B,CAAjB,CAAoB48B,CAAA/T,KAApB,CAjBsB,CAXS,CAhWzB,kBAiYCmyB,QAAS,EAAG,CAC5B,IAAI8B,EAAa,EAAjB,CACIC,EAAc,CAAA,CAClB,IAA8B,GAA9B,GAAI,IAAA7B,UAAA,EAAAryB,KAAJ,EACE,EAAG,CACD,GAAI,IAAA8vB,KAAA,CAAU,GAAV,CAAJ,CAEE,KAEF;IAAIqE,EAAY,IAAAlxB,WAAA,EAChBgxB,EAAA7iD,KAAA,CAAgB+iD,CAAhB,CACKA,EAAAvoC,SAAL,GACEsoC,CADF,CACgB,CAAA,CADhB,CAPC,CAAH,MAUS,IAAAjC,OAAA,CAAY,GAAZ,CAVT,CADF,CAaA,IAAAC,QAAA,CAAa,GAAb,CAEA,OAAO3/C,EAAA,CAAO,QAAQ,CAAC2D,CAAD,CAAOgV,CAAP,CAAe,CAEnC,IADA,IAAI1W,EAAQ,EAAZ,CACSjD,EAAI,CAAb,CAAgBA,CAAhB,CAAoB0iD,CAAA1jD,OAApB,CAAuCgB,CAAA,EAAvC,CACEiD,CAAApD,KAAA,CAAW6iD,CAAA,CAAW1iD,CAAX,CAAA,CAAc2E,CAAd,CAAoBgV,CAApB,CAAX,CAEF,OAAO1W,EAL4B,CAA9B,CAMJ,SACQ,CAAA,CADR,UAES0/C,CAFT,CANI,CAlBqB,CAjYb,QA+ZTpQ,QAAS,EAAG,CAClB,IAAIsQ,EAAY,EAAhB,CACIF,EAAc,CAAA,CAClB,IAA8B,GAA9B,GAAI,IAAA7B,UAAA,EAAAryB,KAAJ,EACE,EAAG,CACD,GAAI,IAAA8vB,KAAA,CAAU,GAAV,CAAJ,CAEE,KAHD,KAKGjtB,EAAQ,IAAAovB,OAAA,EALX,CAMDnhD,EAAM+xB,CAAA8f,OAAN7xC,EAAsB+xB,CAAA7C,KACtB,KAAAkyB,QAAA,CAAa,GAAb,CACA,KAAIxgD,EAAQ,IAAAuxB,WAAA,EACZmxB,EAAAhjD,KAAA,CAAe,KAAMN,CAAN,OAAkBY,CAAlB,CAAf,CACKA,EAAAka,SAAL,GACEsoC,CADF,CACgB,CAAA,CADhB,CAVC,CAAH,MAaS,IAAAjC,OAAA,CAAY,GAAZ,CAbT,CADF,CAgBA,IAAAC,QAAA,CAAa,GAAb,CAEA,OAAO3/C,EAAA,CAAO,QAAQ,CAAC2D,CAAD,CAAOgV,CAAP,CAAe,CAEnC,IADA,IAAI44B,EAAS,EAAb,CACSvyC,EAAI,CAAb,CAAgBA,CAAhB;AAAoB6iD,CAAA7jD,OAApB,CAAsCgB,CAAA,EAAtC,CAA2C,CACzC,IAAI6G,EAAWg8C,CAAA,CAAU7iD,CAAV,CACfuyC,EAAA,CAAO1rC,CAAAtH,IAAP,CAAA,CAAuBsH,CAAA1G,MAAA,CAAewE,CAAf,CAAqBgV,CAArB,CAFkB,CAI3C,MAAO44B,EAN4B,CAA9B,CAOJ,SACQ,CAAA,CADR,UAESoQ,CAFT,CAPI,CArBW,CA/ZH,CAsenB,KAAIjhB,GAAgB,EAApB,CAumEI8H,GAAa5qC,CAAA,CAAO,MAAP,CAvmEjB,CAymEIgrC,GAAe,MACX,MADW,KAEZ,KAFY,KAGZ,KAHY,cAMH,aANG,IAOb,IAPa,CAzmEnB,CA6zGIuD,EAAiBzuC,CAAA8T,cAAA,CAAuB,GAAvB,CA7zGrB,CA8zGI66B,GAAYpV,EAAA,CAAWx5B,CAAA2D,SAAAgc,KAAX,CAAiC,CAAA,CAAjC,CAqNhBjP,GAAAqI,QAAA,CAA0B,CAAC,UAAD,CAkU1Bg2B,GAAAh2B,QAAA,CAAyB,CAAC,SAAD,CA4DzBs2B,GAAAt2B,QAAA,CAAuB,CAAC,SAAD,CASvB,KAAIw3B,GAAc,GAAlB,CA2HIsD,GAAe,MACXvB,CAAA,CAAW,UAAX,CAAuB,CAAvB,CADW,IAEXA,CAAA,CAAW,UAAX,CAAuB,CAAvB,CAA0B,CAA1B,CAA6B,CAAA,CAA7B,CAFW,GAGXA,CAAA,CAAW,UAAX,CAAuB,CAAvB,CAHW,MAIXE,EAAA,CAAc,OAAd,CAJW,KAKXA,EAAA,CAAc,OAAd,CAAuB,CAAA,CAAvB,CALW,IAMXF,CAAA,CAAW,OAAX,CAAoB,CAApB,CAAuB,CAAvB,CANW,GAOXA,CAAA,CAAW,OAAX,CAAoB,CAApB,CAAuB,CAAvB,CAPW,IAQXA,CAAA,CAAW,MAAX,CAAmB,CAAnB,CARW,GASXA,CAAA,CAAW,MAAX,CAAmB,CAAnB,CATW,IAUXA,CAAA,CAAW,OAAX,CAAoB,CAApB,CAVW,GAWXA,CAAA,CAAW,OAAX;AAAoB,CAApB,CAXW,IAYXA,CAAA,CAAW,OAAX,CAAoB,CAApB,CAAwB,GAAxB,CAZW,GAaXA,CAAA,CAAW,OAAX,CAAoB,CAApB,CAAwB,GAAxB,CAbW,IAcXA,CAAA,CAAW,SAAX,CAAsB,CAAtB,CAdW,GAeXA,CAAA,CAAW,SAAX,CAAsB,CAAtB,CAfW,IAgBXA,CAAA,CAAW,SAAX,CAAsB,CAAtB,CAhBW,GAiBXA,CAAA,CAAW,SAAX,CAAsB,CAAtB,CAjBW,KAoBXA,CAAA,CAAW,cAAX,CAA2B,CAA3B,CApBW,MAqBXE,EAAA,CAAc,KAAd,CArBW,KAsBXA,EAAA,CAAc,KAAd,CAAqB,CAAA,CAArB,CAtBW,GAJnB6R,QAAmB,CAAC9R,CAAD,CAAOxC,CAAP,CAAgB,CACjC,MAAyB,GAAlB,CAAAwC,CAAA+R,SAAA,EAAA,CAAuBvU,CAAAwU,MAAA,CAAc,CAAd,CAAvB,CAA0CxU,CAAAwU,MAAA,CAAc,CAAd,CADhB,CAIhB,GAdnBC,QAAuB,CAACjS,CAAD,CAAO,CACxBkS,CAAAA,CAAQ,EAARA,CAAYlS,CAAAmS,kBAAA,EAMhB,OAHAC,EAGA,EAL0B,CAATA,EAACF,CAADE,CAAc,GAAdA,CAAoB,EAKrC,GAHcxS,EAAA,CAAUnkB,IAAA,CAAY,CAAP,CAAAy2B,CAAA,CAAW,OAAX,CAAqB,MAA1B,CAAA,CAAkCA,CAAlC,CAAyC,EAAzC,CAAV,CAAwD,CAAxD,CAGd,CAFctS,EAAA,CAAUnkB,IAAA+iB,IAAA,CAAS0T,CAAT,CAAgB,EAAhB,CAAV,CAA+B,CAA/B,CAEd,CAP4B,CAcX,CA3HnB,CAsJI7Q,GAAqB,8EAtJzB,CAuJID,GAAgB,UAmFpB3E,GAAAj2B,QAAA,CAAqB,CAAC,SAAD,CAuHrB,KAAIq2B,GAAkBjsC,EAAA,CAAQiE,CAAR,CAAtB,CAWImoC,GAAkBpsC,EAAA,CAAQmK,EAAR,CA2KtBgiC,GAAAv2B,QAAA;AAAwB,CAAC,QAAD,CAiFxB,KAAIlL,GAAsB1K,EAAA,CAAQ,UACtB,GADsB,SAEvBgH,QAAQ,CAAC7C,CAAD,CAAUpD,CAAV,CAAgB,CAEnB,CAAZ,EAAIsU,CAAJ,GAIOtU,CAAAyb,KAQL,EARmBzb,CAAAmF,KAQnB,EAPEnF,CAAAqqB,KAAA,CAAU,MAAV,CAAkB,EAAlB,CAOF,CAAAjnB,CAAAM,OAAA,CAAe3H,CAAAotB,cAAA,CAAuB,QAAvB,CAAf,CAZF,CAeA,IAAI,CAACnpB,CAAAyb,KAAL,EAAkB,CAACzb,CAAA0gD,UAAnB,EAAqC,CAAC1gD,CAAAmF,KAAtC,CACE,MAAO,SAAQ,CAACa,CAAD,CAAQ5C,CAAR,CAAiB,CAE9B,IAAIqY,EAA+C,4BAAxC,GAAAlc,EAAAxC,KAAA,CAAcqG,CAAArD,KAAA,CAAa,MAAb,CAAd,CAAA,CACA,YADA,CACe,MAC1BqD,EAAA6Y,GAAA,CAAW,OAAX,CAAoB,QAAQ,CAACzI,CAAD,CAAO,CAE5BpQ,CAAApD,KAAA,CAAayb,CAAb,CAAL,EACEjI,CAAAC,eAAA,EAH+B,CAAnC,CAJ8B,CAlBH,CAFD,CAAR,CAA1B,CAuXI1H,GAA6B,EAIjCtP,EAAA,CAAQ4W,EAAR,CAAsB,QAAQ,CAACstC,CAAD,CAAW15B,CAAX,CAAqB,CAEjD,GAAgB,UAAhB,EAAI05B,CAAJ,CAAA,CAEA,IAAIC,EAAa78B,EAAA,CAAmB,KAAnB,CAA2BkD,CAA3B,CACjBlb,GAAA,CAA2B60C,CAA3B,CAAA,CAAyC,QAAQ,EAAG,CAClD,MAAO,UACK,GADL,MAEC1iC,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CACnCgG,CAAAnF,OAAA,CAAab,CAAA,CAAK4gD,CAAL,CAAb,CAA+BC,QAAiC,CAACrjD,CAAD,CAAQ,CACtEwC,CAAAqqB,KAAA,CAAUpD,CAAV,CAAoB,CAAC,CAACzpB,CAAtB,CADsE,CAAxE,CADmC,CAFhC,CAD2C,CAHpD,CAFiD,CAAnD,CAmBAf,EAAA,CAAQ,CAAC,KAAD;AAAQ,QAAR,CAAkB,MAAlB,CAAR,CAAmC,QAAQ,CAACwqB,CAAD,CAAW,CACpD,IAAI25B,EAAa78B,EAAA,CAAmB,KAAnB,CAA2BkD,CAA3B,CACjBlb,GAAA,CAA2B60C,CAA3B,CAAA,CAAyC,QAAQ,EAAG,CAClD,MAAO,UACK,EADL,MAEC1iC,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CAAA,IAC/B2gD,EAAW15B,CADoB,CAE/B9hB,EAAO8hB,CAEM,OAAjB,GAAIA,CAAJ,EAC4C,4BAD5C,GACI1nB,EAAAxC,KAAA,CAAcqG,CAAArD,KAAA,CAAa,MAAb,CAAd,CADJ,GAEEoF,CAEA,CAFO,WAEP,CADAnF,CAAA6jB,MAAA,CAAW1e,CAAX,CACA,CADmB,YACnB,CAAAw7C,CAAA,CAAW,IAJb,CAOA3gD,EAAAwnB,SAAA,CAAco5B,CAAd,CAA0B,QAAQ,CAACpjD,CAAD,CAAQ,CACnCA,CAAL,GAGAwC,CAAAqqB,KAAA,CAAUllB,CAAV,CAAgB3H,CAAhB,CAMA,CAAI8W,CAAJ,EAAYqsC,CAAZ,EAAsBv9C,CAAArD,KAAA,CAAa4gD,CAAb,CAAuB3gD,CAAA,CAAKmF,CAAL,CAAvB,CATtB,CADwC,CAA1C,CAXmC,CAFhC,CAD2C,CAFA,CAAtD,CAkCA,KAAI+rC,GAAe,aACJpyC,CADI,gBAEDA,CAFC,cAGHA,CAHG,WAINA,CAJM,cAKHA,CALG,CA6CnB4xC,GAAA77B,QAAA,CAAyB,CAAC,UAAD,CAAa,QAAb,CAAuB,QAAvB,CAAiC,UAAjC,CA+TzB,KAAIisC,GAAuBA,QAAQ,CAACC,CAAD,CAAW,CAC5C,MAAO,CAAC,UAAD,CAAa,QAAQ,CAAC1nC,CAAD,CAAW,CAoDrC,MAnDoBxP,MACZ,MADYA;SAERk3C,CAAA,CAAW,KAAX,CAAmB,GAFXl3C,YAGN6mC,EAHM7mC,SAIT5D,QAAQ,EAAG,CAClB,MAAO,KACA2f,QAAQ,CAAC5f,CAAD,CAAQg7C,CAAR,CAAqBhhD,CAArB,CAA2BkgB,CAA3B,CAAuC,CAClD,GAAI,CAAClgB,CAAAihD,OAAL,CAAkB,CAOhB,IAAIC,EAAyBA,QAAQ,CAAC1tC,CAAD,CAAQ,CAC3CA,CAAAC,eACA,CAAID,CAAAC,eAAA,EAAJ,CACID,CAAAG,YADJ,CACwB,CAAA,CAHmB,CAM7C4hC,GAAA,CAAmByL,CAAA,CAAY,CAAZ,CAAnB,CAAmC,QAAnC,CAA6CE,CAA7C,CAIAF,EAAA/kC,GAAA,CAAe,UAAf,CAA2B,QAAQ,EAAG,CACpC5C,CAAA,CAAS,QAAQ,EAAG,CAClB7H,EAAA,CAAsBwvC,CAAA,CAAY,CAAZ,CAAtB,CAAsC,QAAtC,CAAgDE,CAAhD,CADkB,CAApB,CAEG,CAFH,CAEM,CAAA,CAFN,CADoC,CAAtC,CAjBgB,CADgC,IAyB9CC,EAAiBH,CAAApiD,OAAA,EAAAshB,WAAA,CAAgC,MAAhC,CAzB6B,CA0B9CkhC,EAAQphD,CAAAmF,KAARi8C,EAAqBphD,CAAAwxC,OAErB4P,EAAJ,EACExjB,EAAA,CAAO53B,CAAP,CAAco7C,CAAd,CAAqBlhC,CAArB,CAAiCkhC,CAAjC,CAEF,IAAID,CAAJ,CACEH,CAAA/kC,GAAA,CAAe,UAAf,CAA2B,QAAQ,EAAG,CACpCklC,CAAAlP,eAAA,CAA8B/xB,CAA9B,CACIkhC,EAAJ,EACExjB,EAAA,CAAO53B,CAAP,CAAco7C,CAAd,CAAqBplD,CAArB,CAAgColD,CAAhC,CAEF/iD,EAAA,CAAO6hB,CAAP,CAAmBgxB,EAAnB,CALoC,CAAtC,CAhCgD,CAD/C,CADW,CAJFrnC,CADiB,CAAhC,CADqC,CAA9C,CAyDIA,GAAgBi3C,EAAA,EAzDpB,CA0DIp2C,GAAkBo2C,EAAA,CAAqB,CAAA,CAArB,CA1DtB,CAoEIO,GAAa,qFApEjB;AAqEIC,GAAe,4DArEnB,CAsEIC,GAAgB,oCAtEpB,CAwEIC,GAAY,MA6ENjO,EA7EM,QAokBhBkO,QAAwB,CAACz7C,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB6yC,CAAvB,CAA6Bp5B,CAA7B,CAAuC2W,CAAvC,CAAiD,CACvEmjB,EAAA,CAAcvtC,CAAd,CAAqB5C,CAArB,CAA8BpD,CAA9B,CAAoC6yC,CAApC,CAA0Cp5B,CAA1C,CAAoD2W,CAApD,CAEAyiB,EAAAI,SAAA/1C,KAAA,CAAmB,QAAQ,CAACM,CAAD,CAAQ,CACjC,IAAI+F,EAAQsvC,CAAAmB,SAAA,CAAcx2C,CAAd,CACZ,IAAI+F,CAAJ,EAAag+C,EAAAj7C,KAAA,CAAmB9I,CAAnB,CAAb,CAEE,MADAq1C,EAAAR,aAAA,CAAkB,QAAlB,CAA4B,CAAA,CAA5B,CACO,CAAU,EAAV,GAAA70C,CAAA,CAAe,IAAf,CAAuB+F,CAAA,CAAQ/F,CAAR,CAAgB8xC,UAAA,CAAW9xC,CAAX,CAE9Cq1C,EAAAR,aAAA,CAAkB,QAAlB,CAA4B,CAAA,CAA5B,CACA,OAAOr2C,EAPwB,CAAnC,CAWAg3C,GAAA,CAAyBH,CAAzB,CAA+B,QAA/B,CAAyCzvC,CAAzC,CAEAyvC,EAAAuB,YAAAl3C,KAAA,CAAsB,QAAQ,CAACM,CAAD,CAAQ,CACpC,MAAOq1C,EAAAmB,SAAA,CAAcx2C,CAAd,CAAA,CAAuB,EAAvB,CAA4B,EAA5B,CAAiCA,CADJ,CAAtC,CAIIwC,EAAAmtC,IAAJ,GACMuU,CAMJ,CANmBA,QAAQ,CAAClkD,CAAD,CAAQ,CACjC,IAAI2vC,EAAMmC,UAAA,CAAWtvC,CAAAmtC,IAAX,CACV,OAAOyF,GAAA,CAASC,CAAT,CAAe,KAAf,CAAsBA,CAAAmB,SAAA,CAAcx2C,CAAd,CAAtB,EAA8CA,CAA9C,EAAuD2vC,CAAvD,CAA4D3vC,CAA5D,CAF0B,CAMnC,CADAq1C,CAAAI,SAAA/1C,KAAA,CAAmBwkD,CAAnB,CACA;AAAA7O,CAAAuB,YAAAl3C,KAAA,CAAsBwkD,CAAtB,CAPF,CAUI1hD,EAAA+pB,IAAJ,GACM43B,CAMJ,CANmBA,QAAQ,CAACnkD,CAAD,CAAQ,CACjC,IAAIusB,EAAMulB,UAAA,CAAWtvC,CAAA+pB,IAAX,CACV,OAAO6oB,GAAA,CAASC,CAAT,CAAe,KAAf,CAAsBA,CAAAmB,SAAA,CAAcx2C,CAAd,CAAtB,EAA8CA,CAA9C,EAAuDusB,CAAvD,CAA4DvsB,CAA5D,CAF0B,CAMnC,CADAq1C,CAAAI,SAAA/1C,KAAA,CAAmBykD,CAAnB,CACA,CAAA9O,CAAAuB,YAAAl3C,KAAA,CAAsBykD,CAAtB,CAPF,CAUA9O,EAAAuB,YAAAl3C,KAAA,CAAsB,QAAQ,CAACM,CAAD,CAAQ,CACpC,MAAOo1C,GAAA,CAASC,CAAT,CAAe,QAAf,CAAyBA,CAAAmB,SAAA,CAAcx2C,CAAd,CAAzB,EAAiD6B,EAAA,CAAS7B,CAAT,CAAjD,CAAkEA,CAAlE,CAD6B,CAAtC,CAxCuE,CApkBzD,KAinBhBokD,QAAqB,CAAC57C,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB6yC,CAAvB,CAA6Bp5B,CAA7B,CAAuC2W,CAAvC,CAAiD,CACpEmjB,EAAA,CAAcvtC,CAAd,CAAqB5C,CAArB,CAA8BpD,CAA9B,CAAoC6yC,CAApC,CAA0Cp5B,CAA1C,CAAoD2W,CAApD,CAEIyxB,EAAAA,CAAeA,QAAQ,CAACrkD,CAAD,CAAQ,CACjC,MAAOo1C,GAAA,CAASC,CAAT,CAAe,KAAf,CAAsBA,CAAAmB,SAAA,CAAcx2C,CAAd,CAAtB,EAA8C6jD,EAAA/6C,KAAA,CAAgB9I,CAAhB,CAA9C,CAAsEA,CAAtE,CAD0B,CAInCq1C,EAAAuB,YAAAl3C,KAAA,CAAsB2kD,CAAtB,CACAhP,EAAAI,SAAA/1C,KAAA,CAAmB2kD,CAAnB,CARoE,CAjnBtD,OA4nBhBC,QAAuB,CAAC97C,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB6yC,CAAvB,CAA6Bp5B,CAA7B,CAAuC2W,CAAvC,CAAiD,CACtEmjB,EAAA,CAAcvtC,CAAd,CAAqB5C,CAArB,CAA8BpD,CAA9B,CAAoC6yC,CAApC,CAA0Cp5B,CAA1C,CAAoD2W,CAApD,CAEI2xB,EAAAA,CAAiBA,QAAQ,CAACvkD,CAAD,CAAQ,CACnC,MAAOo1C,GAAA,CAASC,CAAT,CAAe,OAAf,CAAwBA,CAAAmB,SAAA,CAAcx2C,CAAd,CAAxB,EAAgD8jD,EAAAh7C,KAAA,CAAkB9I,CAAlB,CAAhD,CAA0EA,CAA1E,CAD4B,CAIrCq1C,EAAAuB,YAAAl3C,KAAA,CAAsB6kD,CAAtB,CACAlP;CAAAI,SAAA/1C,KAAA,CAAmB6kD,CAAnB,CARsE,CA5nBxD,OAuoBhBC,QAAuB,CAACh8C,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB6yC,CAAvB,CAA6B,CAE9C3zC,CAAA,CAAYc,CAAAmF,KAAZ,CAAJ,EACE/B,CAAApD,KAAA,CAAa,MAAb,CAAqBvC,EAAA,EAArB,CAGF2F,EAAA6Y,GAAA,CAAW,OAAX,CAAoB,QAAQ,EAAG,CACzB7Y,CAAA,CAAQ,CAAR,CAAA6+C,QAAJ,EACEj8C,CAAAG,OAAA,CAAa,QAAQ,EAAG,CACtB0sC,CAAAc,cAAA,CAAmB3zC,CAAAxC,MAAnB,CADsB,CAAxB,CAF2B,CAA/B,CAQAq1C,EAAAiB,QAAA,CAAeC,QAAQ,EAAG,CAExB3wC,CAAA,CAAQ,CAAR,CAAA6+C,QAAA,CADYjiD,CAAAxC,MACZ,EAA+Bq1C,CAAAa,WAFP,CAK1B1zC,EAAAwnB,SAAA,CAAc,OAAd,CAAuBqrB,CAAAiB,QAAvB,CAnBkD,CAvoBpC,UA6pBhBoO,QAA0B,CAACl8C,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB6yC,CAAvB,CAA6B,CAAA,IACjDsP,EAAYniD,CAAAoiD,YADqC,CAEjDC,EAAariD,CAAAsiD,aAEZ/lD,EAAA,CAAS4lD,CAAT,CAAL,GAA0BA,CAA1B,CAAsC,CAAA,CAAtC,CACK5lD,EAAA,CAAS8lD,CAAT,CAAL,GAA2BA,CAA3B,CAAwC,CAAA,CAAxC,CAEAj/C,EAAA6Y,GAAA,CAAW,OAAX,CAAoB,QAAQ,EAAG,CAC7BjW,CAAAG,OAAA,CAAa,QAAQ,EAAG,CACtB0sC,CAAAc,cAAA,CAAmBvwC,CAAA,CAAQ,CAAR,CAAA6+C,QAAnB,CADsB,CAAxB,CAD6B,CAA/B,CAMApP,EAAAiB,QAAA,CAAeC,QAAQ,EAAG,CACxB3wC,CAAA,CAAQ,CAAR,CAAA6+C,QAAA,CAAqBpP,CAAAa,WADG,CAK1Bb,EAAAmB,SAAA,CAAgBuO,QAAQ,CAAC/kD,CAAD,CAAQ,CAC9B,MAAOA,EAAP,GAAiB2kD,CADa,CAIhCtP;CAAAuB,YAAAl3C,KAAA,CAAsB,QAAQ,CAACM,CAAD,CAAQ,CACpC,MAAOA,EAAP,GAAiB2kD,CADmB,CAAtC,CAIAtP,EAAAI,SAAA/1C,KAAA,CAAmB,QAAQ,CAACM,CAAD,CAAQ,CACjC,MAAOA,EAAA,CAAQ2kD,CAAR,CAAoBE,CADM,CAAnC,CA1BqD,CA7pBvC,QAyZJvjD,CAzZI,QA0ZJA,CA1ZI,QA2ZJA,CA3ZI,OA4ZLA,CA5ZK,MA6ZNA,CA7ZM,CAxEhB,CA+4BI8K,GAAiB,CAAC,UAAD,CAAa,UAAb,CAAyB,QAAQ,CAACwmB,CAAD,CAAW3W,CAAX,CAAqB,CACzE,MAAO,UACK,GADL,SAEI,UAFJ,MAGCyE,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB6yC,CAAvB,CAA6B,CACrCA,CAAJ,EACG,CAAA2O,EAAA,CAAUt+C,CAAA,CAAUlD,CAAAkR,KAAV,CAAV,CAAA,EAAmCswC,EAAA11B,KAAnC,EAAmD9lB,CAAnD,CAA0D5C,CAA1D,CAAmEpD,CAAnE,CAAyE6yC,CAAzE,CAA+Ep5B,CAA/E,CACmD2W,CADnD,CAFsC,CAHtC,CADkE,CAAtD,CA/4BrB,CA45BI2gB,GAAc,UA55BlB,CA65BID,GAAgB,YA75BpB,CA85BIgB,GAAiB,aA95BrB,CA+5BIW,GAAc,UA/5BlB,CAuiCI+P,GAAoB,CAAC,QAAD,CAAW,mBAAX,CAAgC,QAAhC,CAA0C,UAA1C,CAAsD,QAAtD,CAAgE,UAAhE,CACpB,QAAQ,CAACp6B,CAAD,CAAStI,CAAT,CAA4B+D,CAA5B,CAAmC7B,CAAnC,CAA6CpB,CAA7C,CAAqDG,CAArD,CAA+D,CA6DzE4vB,QAASA,EAAc,CAACC,CAAD,CAAUC,CAAV,CAA8B,CACnDA,CAAA,CAAqBA,CAAA,CAAqB,GAArB,CAA2BlqC,EAAA,CAAWkqC,CAAX,CAA+B,GAA/B,CAA3B,CAAiE,EACtF9vB,EAAA0M,YAAA,CAAqBzL,CAArB,EAAgC4uB,CAAA,CAAUE,EAAV,CAA0BC,EAA1D,EAAyEF,CAAzE,CACA9vB;CAAAkB,SAAA,CAAkBD,CAAlB,EAA6B4uB,CAAA,CAAUG,EAAV,CAAwBD,EAArD,EAAsED,CAAtE,CAHmD,CA3DrD,IAAA4R,YAAA,CADA,IAAA/O,WACA,CADkBh1B,MAAAgkC,IAElB,KAAAzP,SAAA,CAAgB,EAChB,KAAAmB,YAAA,CAAmB,EACnB,KAAAuO,qBAAA,CAA4B,EAC5B,KAAAjR,UAAA,CAAiB,CAAA,CACjB,KAAAD,OAAA,CAAc,CAAA,CACd,KAAAE,OAAA,CAAc,CAAA,CACd,KAAAC,SAAA,CAAgB,CAAA,CAChB,KAAAL,MAAA,CAAa1tB,CAAA1e,KAV4D,KAYrEy9C,EAAahiC,CAAA,CAAOiD,CAAAg/B,QAAP,CAZwD,CAarEC,EAAaF,CAAA96B,OAEjB,IAAI,CAACg7B,CAAL,CACE,KAAM7mD,EAAA,CAAO,SAAP,CAAA,CAAkB,WAAlB,CACF4nB,CAAAg/B,QADE,CACa1/C,EAAA,CAAY6e,CAAZ,CADb,CAAN,CAYF,IAAA8xB,QAAA,CAAeh1C,CAmBf,KAAAk1C,SAAA,CAAgB+O,QAAQ,CAACvlD,CAAD,CAAQ,CAC9B,MAAO0B,EAAA,CAAY1B,CAAZ,CAAP,EAAuC,EAAvC,GAA6BA,CAA7B,EAAuD,IAAvD,GAA6CA,CAA7C,EAA+DA,CAA/D,GAAyEA,CAD3C,CA/CyC,KAmDrEyzC,EAAajvB,CAAAghC,cAAA,CAAuB,iBAAvB,CAAb/R,EAA0DC,EAnDW,CAoDrEC,EAAe,CApDsD,CAqDrEE,EAAS,IAAAA,OAATA,CAAuB,EAI3BrvB,EAAAC,SAAA,CAAkB6vB,EAAlB,CACAnB,EAAA,CAAe,CAAA,CAAf,CA0BA,KAAA0B,aAAA,CAAoB4Q,QAAQ,CAACpS,CAAD,CAAqBD,CAArB,CAA8B,CAGpDS,CAAA,CAAOR,CAAP,CAAJ;AAAmC,CAACD,CAApC,GAGIA,CAAJ,EACMS,CAAA,CAAOR,CAAP,CACJ,EADgCM,CAAA,EAChC,CAAKA,CAAL,GACER,CAAA,CAAe,CAAA,CAAf,CAEA,CADA,IAAAgB,OACA,CADc,CAAA,CACd,CAAA,IAAAC,SAAA,CAAgB,CAAA,CAHlB,CAFF,GAQEjB,CAAA,CAAe,CAAA,CAAf,CAGA,CAFA,IAAAiB,SAEA,CAFgB,CAAA,CAEhB,CADA,IAAAD,OACA,CADc,CAAA,CACd,CAAAR,CAAA,EAXF,CAiBA,CAHAE,CAAA,CAAOR,CAAP,CAGA,CAH6B,CAACD,CAG9B,CAFAD,CAAA,CAAeC,CAAf,CAAwBC,CAAxB,CAEA,CAAAI,CAAAoB,aAAA,CAAwBxB,CAAxB,CAA4CD,CAA5C,CAAqD,IAArD,CApBA,CAHwD,CAoC1D,KAAA8B,aAAA,CAAoBwQ,QAAS,EAAG,CAC9B,IAAAzR,OAAA,CAAc,CAAA,CACd,KAAAC,UAAA,CAAiB,CAAA,CACjB3wB,EAAA0M,YAAA,CAAqBzL,CAArB,CAA+BywB,EAA/B,CACA1xB,EAAAkB,SAAA,CAAkBD,CAAlB,CAA4B8vB,EAA5B,CAJ8B,CA4BhC,KAAA6B,cAAA,CAAqBwP,QAAQ,CAAC3lD,CAAD,CAAQ,CACnC,IAAAk2C,WAAA,CAAkBl2C,CAGd,KAAAk0C,UAAJ,GACE,IAAAD,OAIA,CAJc,CAAA,CAId,CAHA,IAAAC,UAGA,CAHiB,CAAA,CAGjB,CAFA3wB,CAAA0M,YAAA,CAAqBzL,CAArB,CAA+B8vB,EAA/B,CAEA,CADA/wB,CAAAkB,SAAA,CAAkBD,CAAlB,CAA4BywB,EAA5B,CACA,CAAAxB,CAAAsB,UAAA,EALF,CAQA91C,EAAA,CAAQ,IAAAw2C,SAAR,CAAuB,QAAQ,CAAChxC,CAAD,CAAK,CAClCzE,CAAA,CAAQyE,CAAA,CAAGzE,CAAH,CAD0B,CAApC,CAII,KAAAilD,YAAJ,GAAyBjlD,CAAzB,GACE,IAAAilD,YAEA,CAFmBjlD,CAEnB,CADAslD,CAAA,CAAW16B,CAAX,CAAmB5qB,CAAnB,CACA,CAAAf,CAAA,CAAQ,IAAAkmD,qBAAR;AAAmC,QAAQ,CAAChoC,CAAD,CAAW,CACpD,GAAI,CACFA,CAAA,EADE,CAEF,MAAMnX,CAAN,CAAS,CACTsc,CAAA,CAAkBtc,CAAlB,CADS,CAHyC,CAAtD,CAHF,CAhBmC,CA8BrC,KAAIqvC,EAAO,IAEXzqB,EAAAvnB,OAAA,CAAcuiD,QAAqB,EAAG,CACpC,IAAI5lD,EAAQolD,CAAA,CAAWx6B,CAAX,CAGZ,IAAIyqB,CAAA4P,YAAJ,GAAyBjlD,CAAzB,CAAgC,CAAA,IAE1B6lD,EAAaxQ,CAAAuB,YAFa,CAG1BhhB,EAAMiwB,CAAAhnD,OAGV,KADAw2C,CAAA4P,YACA,CADmBjlD,CACnB,CAAM41B,CAAA,EAAN,CAAA,CACE51B,CAAA,CAAQ6lD,CAAA,CAAWjwB,CAAX,CAAA,CAAgB51B,CAAhB,CAGNq1C,EAAAa,WAAJ,GAAwBl2C,CAAxB,GACEq1C,CAAAa,WACA,CADkBl2C,CAClB,CAAAq1C,CAAAiB,QAAA,EAFF,CAV8B,CAgBhC,MAAOt2C,EApB6B,CAAtC,CApLyE,CADnD,CAviCxB,CA21CIiO,GAAmBA,QAAQ,EAAG,CAChC,MAAO,SACI,CAAC,SAAD,CAAY,QAAZ,CADJ,YAEO+2C,EAFP,MAGCtkC,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuBsjD,CAAvB,CAA8B,CAAA,IAGtCC,EAAYD,CAAA,CAAM,CAAN,CAH0B,CAItCE,EAAWF,CAAA,CAAM,CAAN,CAAXE,EAAuBtS,EAE3BsS,EAAA3R,YAAA,CAAqB0R,CAArB,CAEAv9C,EAAA6/B,IAAA,CAAU,UAAV,CAAsB,QAAQ,EAAG,CAC/B2d,CAAAvR,eAAA,CAAwBsR,CAAxB,CAD+B,CAAjC,CAR0C,CAHvC,CADyB,CA31ClC,CAy6CI53C,GAAoB1M,EAAA,CAAQ,SACrB,SADqB,MAExBif,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB6yC,CAAvB,CAA6B,CACzCA,CAAA8P,qBAAAzlD,KAAA,CAA+B,QAAQ,EAAG,CACxC8I,CAAA0/B,MAAA,CAAY1lC,CAAAyjD,SAAZ,CADwC,CAA1C,CADyC,CAFb,CAAR,CAz6CxB;AAm7CI73C,GAAoBA,QAAQ,EAAG,CACjC,MAAO,SACI,UADJ,MAECsS,QAAQ,CAAClY,CAAD,CAAQ8S,CAAR,CAAa9Y,CAAb,CAAmB6yC,CAAnB,CAAyB,CACrC,GAAKA,CAAL,CAAA,CACA7yC,CAAA0jD,SAAA,CAAgB,CAAA,CAEhB,KAAIxQ,EAAYA,QAAQ,CAAC11C,CAAD,CAAQ,CAC9B,GAAIwC,CAAA0jD,SAAJ,EAAqB7Q,CAAAmB,SAAA,CAAcx2C,CAAd,CAArB,CACEq1C,CAAAR,aAAA,CAAkB,UAAlB,CAA8B,CAAA,CAA9B,CADF,KAKE,OADAQ,EAAAR,aAAA,CAAkB,UAAlB,CAA8B,CAAA,CAA9B,CACO70C,CAAAA,CANqB,CAUhCq1C,EAAAuB,YAAAl3C,KAAA,CAAsBg2C,CAAtB,CACAL,EAAAI,SAAAh1C,QAAA,CAAsBi1C,CAAtB,CAEAlzC,EAAAwnB,SAAA,CAAc,UAAd,CAA0B,QAAQ,EAAG,CACnC0rB,CAAA,CAAUL,CAAAa,WAAV,CADmC,CAArC,CAhBA,CADqC,CAFlC,CAD0B,CAn7CnC,CAqgDIhoC,GAAkBA,QAAQ,EAAG,CAC/B,MAAO,SACI,SADJ,MAECwS,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB6yC,CAAvB,CAA6B,CACzC,IACIjsC,GADA/C,CACA+C,CADQ,UAAAtB,KAAA,CAAgBtF,CAAA2jD,OAAhB,CACR/8C,GAAyB3F,MAAJ,CAAW4C,CAAA,CAAM,CAAN,CAAX,CAArB+C,EAA6C5G,CAAA2jD,OAA7C/8C,EAA4D,GAiBhEisC,EAAAI,SAAA/1C,KAAA,CAfY6F,QAAQ,CAAC6gD,CAAD,CAAY,CAE9B,GAAI,CAAA1kD,CAAA,CAAY0kD,CAAZ,CAAJ,CAAA,CAEA,IAAIxjD,EAAO,EAEPwjD,EAAJ,EACEnnD,CAAA,CAAQmnD,CAAAx/C,MAAA,CAAgBwC,CAAhB,CAAR,CAAoC,QAAQ,CAACpJ,CAAD,CAAQ,CAC9CA,CAAJ;AAAW4C,CAAAlD,KAAA,CAAUkS,EAAA,CAAK5R,CAAL,CAAV,CADuC,CAApD,CAKF,OAAO4C,EAVP,CAF8B,CAehC,CACAyyC,EAAAuB,YAAAl3C,KAAA,CAAsB,QAAQ,CAACM,CAAD,CAAQ,CACpC,MAAIhB,EAAA,CAAQgB,CAAR,CAAJ,CACSA,CAAAM,KAAA,CAAW,IAAX,CADT,CAIO9B,CAL6B,CAAtC,CASA62C,EAAAmB,SAAA,CAAgBuO,QAAQ,CAAC/kD,CAAD,CAAQ,CAC9B,MAAO,CAACA,CAAR,EAAiB,CAACA,CAAAnB,OADY,CA7BS,CAFtC,CADwB,CArgDjC,CA6iDIwnD,GAAwB,oBA7iD5B,CAimDIh4C,GAAmBA,QAAQ,EAAG,CAChC,MAAO,UACK,GADL,SAEI5F,QAAQ,CAAC69C,CAAD,CAAMC,CAAN,CAAe,CAC9B,MAAIF,GAAAv9C,KAAA,CAA2By9C,CAAAC,QAA3B,CAAJ,CACSC,QAA4B,CAACj+C,CAAD,CAAQ8S,CAAR,CAAa9Y,CAAb,CAAmB,CACpDA,CAAAqqB,KAAA,CAAU,OAAV,CAAmBrkB,CAAA0/B,MAAA,CAAY1lC,CAAAgkD,QAAZ,CAAnB,CADoD,CADxD,CAKSE,QAAoB,CAACl+C,CAAD,CAAQ8S,CAAR,CAAa9Y,CAAb,CAAmB,CAC5CgG,CAAAnF,OAAA,CAAab,CAAAgkD,QAAb,CAA2BG,QAAyB,CAAC3mD,CAAD,CAAQ,CAC1DwC,CAAAqqB,KAAA,CAAU,OAAV,CAAmB7sB,CAAnB,CAD0D,CAA5D,CAD4C,CANlB,CAF3B,CADyB,CAjmDlC,CAsqDI0M,GAAkBumC,EAAA,CAAY,QAAQ,CAACzqC,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CAC/DoD,CAAA6e,SAAA,CAAiB,YAAjB,CAAA7b,KAAA,CAAoC,UAApC,CAAgDpG,CAAAokD,OAAhD,CACAp+C,EAAAnF,OAAA,CAAab,CAAAokD,OAAb,CAA0BC,QAA0B,CAAC7mD,CAAD,CAAQ,CAI1D4F,CAAA0oB,KAAA,CAAatuB,CAAA,EAASxB,CAAT,CAAqB,EAArB,CAA0BwB,CAAvC,CAJ0D,CAA5D,CAF+D,CAA3C,CAtqDtB,CAmuDI4M,GAA0B,CAAC,cAAD;AAAiB,QAAQ,CAACqW,CAAD,CAAe,CACpE,MAAO,SAAQ,CAACza,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CAEhC+rB,CAAAA,CAAgBtL,CAAA,CAAard,CAAApD,KAAA,CAAaA,CAAA6jB,MAAAygC,eAAb,CAAb,CACpBlhD,EAAA6e,SAAA,CAAiB,YAAjB,CAAA7b,KAAA,CAAoC,UAApC,CAAgD2lB,CAAhD,CACA/rB,EAAAwnB,SAAA,CAAc,gBAAd,CAAgC,QAAQ,CAAChqB,CAAD,CAAQ,CAC9C4F,CAAA0oB,KAAA,CAAatuB,CAAb,CAD8C,CAAhD,CAJoC,CAD8B,CAAxC,CAnuD9B,CA6xDI2M,GAAsB,CAAC,MAAD,CAAS,QAAT,CAAmB,QAAQ,CAAC2W,CAAD,CAAOF,CAAP,CAAe,CAClE,MAAO,SAAQ,CAAC5a,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CACpCoD,CAAA6e,SAAA,CAAiB,YAAjB,CAAA7b,KAAA,CAAoC,UAApC,CAAgDpG,CAAAukD,WAAhD,CAEA,KAAIj1C,EAASsR,CAAA,CAAO5gB,CAAAukD,WAAP,CAGbv+C,EAAAnF,OAAA,CAFA2jD,QAAuB,EAAG,CAAE,MAAQjlD,CAAA+P,CAAA,CAAOtJ,CAAP,CAAAzG,EAAiB,EAAjBA,UAAA,EAAV,CAE1B,CAA6BklD,QAA8B,CAACjnD,CAAD,CAAQ,CACjE4F,CAAAO,KAAA,CAAamd,CAAA4jC,eAAA,CAAoBp1C,CAAA,CAAOtJ,CAAP,CAApB,CAAb,EAAmD,EAAnD,CADiE,CAAnE,CANoC,CAD4B,CAA1C,CA7xD1B,CA8iEIqE,GAAmBsqC,EAAA,CAAe,EAAf,CAAmB,CAAA,CAAnB,CA9iEvB,CA8lEIpqC,GAAsBoqC,EAAA,CAAe,KAAf,CAAsB,CAAtB,CA9lE1B,CA8oEIrqC,GAAuBqqC,EAAA,CAAe,MAAf,CAAuB,CAAvB,CA9oE3B,CAwsEInqC,GAAmBimC,EAAA,CAAY,SACxBxqC,QAAQ,CAAC7C,CAAD,CAAUpD,CAAV,CAAgB,CAC/BA,CAAAqqB,KAAA,CAAU,SAAV,CAAqBruB,CAArB,CACAoH,EAAAqqB,YAAA,CAAoB,UAApB,CAF+B,CADA,CAAZ,CAxsEvB;AA+4EIhjB,GAAwB,CAAC,QAAQ,EAAG,CACtC,MAAO,OACE,CAAA,CADF,YAEO,GAFP,UAGK,GAHL,CAD+B,CAAZ,CA/4E5B,CAq+EIuB,GAAoB,EACxBvP,EAAA,CACE,6IAAA,MAAA,CAAA,GAAA,CADF,CAEE,QAAQ,CAAC0I,CAAD,CAAO,CACb,IAAIkhB,EAAgBtC,EAAA,CAAmB,KAAnB,CAA2B5e,CAA3B,CACpB6G,GAAA,CAAkBqa,CAAlB,CAAA,CAAmC,CAAC,QAAD,CAAW,QAAQ,CAACzF,CAAD,CAAS,CAC7D,MAAO,SACI3a,QAAQ,CAAC+b,CAAD,CAAWhiB,CAAX,CAAiB,CAChC,IAAIiC,EAAK2e,CAAA,CAAO5gB,CAAA,CAAKqmB,CAAL,CAAP,CACT,OAAO,SAAQ,CAACrgB,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CACpCoD,CAAA6Y,GAAA,CAAW/Y,CAAA,CAAUiC,CAAV,CAAX,CAA4B,QAAQ,CAACqO,CAAD,CAAQ,CAC1CxN,CAAAG,OAAA,CAAa,QAAQ,EAAG,CACtBlE,CAAA,CAAG+D,CAAH,CAAU,QAAQwN,CAAR,CAAV,CADsB,CAAxB,CAD0C,CAA5C,CADoC,CAFN,CAD7B,CADsD,CAA5B,CAFtB,CAFjB,CAgeA,KAAI5I,GAAgB,CAAC,UAAD,CAAa,QAAQ,CAACmW,CAAD,CAAW,CAClD,MAAO,YACO,SADP,UAEK,GAFL,UAGK,CAAA,CAHL,UAIK,GAJL;MAKE,CAAA,CALF,MAMC7C,QAAS,CAACkK,CAAD,CAASpG,CAAT,CAAmB6B,CAAnB,CAA0BgvB,CAA1B,CAAgC8R,CAAhC,CAA6C,CAAA,IACpD17C,CADoD,CAC7CsZ,CAD6C,CACjCqiC,CACvBx8B,EAAAvnB,OAAA,CAAcgjB,CAAAghC,KAAd,CAA0BC,QAAwB,CAACtnD,CAAD,CAAQ,CAEpDwF,EAAA,CAAUxF,CAAV,CAAJ,CACO+kB,CADP,GAEIA,CACA,CADa6F,CAAAvF,KAAA,EACb,CAAA8hC,CAAA,CAAYpiC,CAAZ,CAAwB,QAAS,CAACjf,CAAD,CAAQ,CACvCA,CAAA,CAAMA,CAAAjH,OAAA,EAAN,CAAA,CAAwBN,CAAAotB,cAAA,CAAuB,aAAvB,CAAuCtF,CAAAghC,KAAvC,CAAoD,GAApD,CAIxB57C,EAAA,CAAQ,OACC3F,CADD,CAGRyd,EAAAy4B,MAAA,CAAel2C,CAAf,CAAsB0e,CAAApjB,OAAA,EAAtB,CAAyCojB,CAAzC,CARuC,CAAzC,CAHJ,GAeK4iC,CAQH,GAPEA,CAAA9lC,OAAA,EACA,CAAA8lC,CAAA,CAAmB,IAMrB,EAJGriC,CAIH,GAHEA,CAAA1Q,SAAA,EACA,CAAA0Q,CAAA,CAAa,IAEf,EAAGtZ,CAAH,GACE27C,CAIA,CAJmB/8C,EAAA,CAAiBoB,CAAA3F,MAAjB,CAInB,CAHAyd,CAAA04B,MAAA,CAAemL,CAAf,CAAiC,QAAQ,EAAG,CAC1CA,CAAA,CAAmB,IADuB,CAA5C,CAGA,CAAA37C,CAAA,CAAQ,IALV,CAvBF,CAFwD,CAA1D,CAFwD,CANvD,CAD2C,CAAhC,CAApB,CA8MI4B,GAAqB,CAAC,OAAD,CAAU,gBAAV,CAA4B,eAA5B,CAA6C,UAA7C,CAAyD,MAAzD,CACP,QAAQ,CAAC6V,CAAD,CAAUC,CAAV,CAA4BokC,CAA5B,CAA6ChkC,CAA7C,CAAyDD,CAAzD,CAA+D,CACvF,MAAO,UACK,KADL,UAEK,GAFL,UAGK,CAAA,CAHL,YAIO,SAJP,YAKOva,EAAAzH,KALP,SAMImH,QAAQ,CAAC7C,CAAD;AAAUpD,CAAV,CAAgB,CAAA,IAC3BglD,EAAShlD,CAAAilD,UAATD,EAA2BhlD,CAAAmB,IADA,CAE3B+jD,EAAYllD,CAAA00B,OAAZwwB,EAA2B,EAFA,CAG3BC,EAAgBnlD,CAAAolD,WAEpB,OAAO,SAAQ,CAACp/C,CAAD,CAAQgc,CAAR,CAAkB6B,CAAlB,CAAyBgvB,CAAzB,CAA+B8R,CAA/B,CAA4C,CAAA,IACrDroB,EAAgB,CADqC,CAErD+J,CAFqD,CAGrDgf,CAHqD,CAIrDC,CAJqD,CAMrDC,EAA4BA,QAAQ,EAAG,CACtCF,CAAH,GACEA,CAAAvmC,OAAA,EACA,CAAAumC,CAAA,CAAkB,IAFpB,CAIGhf,EAAH,GACEA,CAAAx0B,SAAA,EACA,CAAAw0B,CAAA,CAAe,IAFjB,CAIGif,EAAH,GACEvkC,CAAA04B,MAAA,CAAe6L,CAAf,CAA+B,QAAQ,EAAG,CACxCD,CAAA,CAAkB,IADsB,CAA1C,CAIA,CADAA,CACA,CADkBC,CAClB,CAAAA,CAAA,CAAiB,IALnB,CATyC,CAkB3Ct/C,EAAAnF,OAAA,CAAaigB,CAAA0kC,mBAAA,CAAwBR,CAAxB,CAAb,CAA8CS,QAA6B,CAACtkD,CAAD,CAAM,CAC/E,IAAIukD,EAAiBA,QAAQ,EAAG,CAC1B,CAAAvmD,CAAA,CAAUgmD,CAAV,CAAJ,EAAkCA,CAAlC,EAAmD,CAAAn/C,CAAA0/B,MAAA,CAAYyf,CAAZ,CAAnD,EACEJ,CAAA,EAF4B,CAAhC,CAKIY,EAAe,EAAErpB,CAEjBn7B,EAAJ,EACEuf,CAAAtK,IAAA,CAAUjV,CAAV,CAAe,OAAQwf,CAAR,CAAf,CAAAmK,QAAA,CAAgD,QAAQ,CAACO,CAAD,CAAW,CACjE,GAAIs6B,CAAJ,GAAqBrpB,CAArB,CAAA,CACA,IAAIspB,EAAW5/C,CAAA6c,KAAA,EACfgwB,EAAAvqB,SAAA,CAAgB+C,CAQZ/nB,EAAAA,CAAQqhD,CAAA,CAAYiB,CAAZ,CAAsB,QAAQ,CAACtiD,CAAD,CAAQ,CAChDiiD,CAAA,EACAxkC,EAAAy4B,MAAA,CAAel2C,CAAf,CAAsB,IAAtB,CAA4B0e,CAA5B,CAAsC0jC,CAAtC,CAFgD,CAAtC,CAKZrf,EAAA,CAAeuf,CACfN,EAAA,CAAiBhiD,CAEjB+iC,EAAAH,MAAA,CAAmB,uBAAnB,CACAlgC,EAAA0/B,MAAA,CAAYwf,CAAZ,CAnBA,CADiE,CAAnE,CAAAprC,MAAA,CAqBS,QAAQ,EAAG,CACd6rC,CAAJ;AAAqBrpB,CAArB,EAAoCipB,CAAA,EADlB,CArBpB,CAwBA,CAAAv/C,CAAAkgC,MAAA,CAAY,0BAAZ,CAzBF,GA2BEqf,CAAA,EACA,CAAA1S,CAAAvqB,SAAA,CAAgB,IA5BlB,CAR+E,CAAjF,CAxByD,CAL5B,CAN5B,CADgF,CADhE,CA9MzB,CAoSIxc,GAAgC,CAAC,UAAD,CAClC,QAAQ,CAAC+5C,CAAD,CAAW,CACjB,MAAO,UACK,KADL,UAEM,IAFN,SAGI,WAHJ,MAIC3nC,QAAQ,CAAClY,CAAD,CAAQgc,CAAR,CAAkB6B,CAAlB,CAAyBgvB,CAAzB,CAA+B,CAC3C7wB,CAAAre,KAAA,CAAckvC,CAAAvqB,SAAd,CACAu9B,EAAA,CAAS7jC,CAAAsH,SAAA,EAAT,CAAA,CAA8BtjB,CAA9B,CAF2C,CAJxC,CADU,CADe,CApSpC,CAwWI8E,GAAkB2lC,EAAA,CAAY,UACtB,GADsB,SAEvBxqC,QAAQ,EAAG,CAClB,MAAO,KACA2f,QAAQ,CAAC5f,CAAD,CAAQ5C,CAAR,CAAiB6f,CAAjB,CAAwB,CACnCjd,CAAA0/B,MAAA,CAAYziB,CAAA6iC,OAAZ,CADmC,CADhC,CADW,CAFY,CAAZ,CAxWtB,CAmZI/6C,GAAyB0lC,EAAA,CAAY,UAAY,CAAA,CAAZ,UAA4B,GAA5B,CAAZ,CAnZ7B,CAgkBIzlC,GAAuB,CAAC,SAAD,CAAY,cAAZ,CAA4B,QAAQ,CAAC4gC,CAAD,CAAUnrB,CAAV,CAAwB,CACrF,IAAIslC,EAAQ,KACZ,OAAO,UACK,IADL,MAEC7nC,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CAAA,IAC/BgmD,EAAYhmD,CAAAi3B,MADmB,CAE/BgvB,EAAUjmD,CAAA6jB,MAAAqO,KAAV+zB,EAA6B7iD,CAAApD,KAAA,CAAaA,CAAA6jB,MAAAqO,KAAb,CAFE,CAG/BrkB,EAAS7N,CAAA6N,OAATA;AAAwB,CAHO,CAI/Bq4C,EAAQlgD,CAAA0/B,MAAA,CAAYugB,CAAZ,CAARC,EAAgC,EAJD,CAK/BC,EAAc,EALiB,CAM/Bh4B,EAAc1N,CAAA0N,YAAA,EANiB,CAO/BC,EAAY3N,CAAA2N,UAAA,EAPmB,CAQ/Bg4B,EAAS,oBAEb3pD,EAAA,CAAQuD,CAAR,CAAc,QAAQ,CAAC+uB,CAAD,CAAas3B,CAAb,CAA4B,CAC5CD,CAAA9/C,KAAA,CAAY+/C,CAAZ,CAAJ,GACEH,CAAA,CAAMhjD,CAAA,CAAUmjD,CAAAviD,QAAA,CAAsB,MAAtB,CAA8B,EAA9B,CAAAA,QAAA,CAA0C,OAA1C,CAAmD,GAAnD,CAAV,CAAN,CADF,CAEIV,CAAApD,KAAA,CAAaA,CAAA6jB,MAAA,CAAWwiC,CAAX,CAAb,CAFJ,CADgD,CAAlD,CAMA5pD,EAAA,CAAQypD,CAAR,CAAe,QAAQ,CAACn3B,CAAD,CAAanyB,CAAb,CAAkB,CACvCupD,CAAA,CAAYvpD,CAAZ,CAAA,CACE6jB,CAAA,CAAasO,CAAAjrB,QAAA,CAAmBiiD,CAAnB,CAA0B53B,CAA1B,CAAwC63B,CAAxC,CAAoD,GAApD,CACXn4C,CADW,CACFugB,CADE,CAAb,CAFqC,CAAzC,CAMApoB,EAAAnF,OAAA,CAAaylD,QAAyB,EAAG,CACvC,IAAI9oD,EAAQ8xC,UAAA,CAAWtpC,CAAA0/B,MAAA,CAAYsgB,CAAZ,CAAX,CAEZ,IAAKrgB,KAAA,CAAMnoC,CAAN,CAAL,CAME,MAAO,EAHDA,EAAN,GAAe0oD,EAAf,GAAuB1oD,CAAvB,CAA+BouC,CAAAhU,UAAA,CAAkBp6B,CAAlB,CAA0BqQ,CAA1B,CAA/B,CACC,OAAOs4C,EAAA,CAAY3oD,CAAZ,CAAA,CAAmBwI,CAAnB,CAA0B5C,CAA1B,CAAmC,CAAA,CAAnC,CAP6B,CAAzC,CAWGmjD,QAA+B,CAACtiB,CAAD,CAAS,CACzC7gC,CAAA0oB,KAAA,CAAamY,CAAb,CADyC,CAX3C,CAtBmC,CAFhC,CAF8E,CAA5D,CAhkB3B,CAkzBIh5B,GAAoB,CAAC,QAAD,CAAW,UAAX,CAAuB,QAAQ,CAAC2V,CAAD,CAASG,CAAT,CAAmB,CAExE,IAAIylC,EAAiBvqD,CAAA,CAAO,UAAP,CACrB,OAAO,YACO,SADP,UAEK,GAFL,UAGK,CAAA,CAHL,OAIE,CAAA,CAJF;KAKCiiB,QAAQ,CAACkK,CAAD,CAASpG,CAAT,CAAmB6B,CAAnB,CAA0BgvB,CAA1B,CAAgC8R,CAAhC,CAA4C,CACtD,IAAI51B,EAAalL,CAAA4iC,SAAjB,CACI5iD,EAAQkrB,CAAAlrB,MAAA,CAAiB,qEAAjB,CADZ,CAEc6iD,CAFd,CAEgCC,CAFhC,CAEgDC,CAFhD,CAEkEC,CAFlE,CAGYC,CAHZ,CAG6BC,CAH7B,CAIEC,EAAe,KAAMxyC,EAAN,CAEjB,IAAI,CAAC3Q,CAAL,CACE,KAAM2iD,EAAA,CAAe,MAAf,CACJz3B,CADI,CAAN,CAIFk4B,CAAA,CAAMpjD,CAAA,CAAM,CAAN,CACNqjD,EAAA,CAAMrjD,CAAA,CAAM,CAAN,CAGN,EAFAsjD,CAEA,CAFatjD,CAAA,CAAM,CAAN,CAEb,GACE6iD,CACA,CADmB9lC,CAAA,CAAOumC,CAAP,CACnB,CAAAR,CAAA,CAAiBA,QAAQ,CAAC/pD,CAAD,CAAMY,CAAN,CAAaE,CAAb,CAAoB,CAEvCqpD,CAAJ,GAAmBC,CAAA,CAAaD,CAAb,CAAnB,CAAiDnqD,CAAjD,CACAoqD,EAAA,CAAaF,CAAb,CAAA,CAAgCtpD,CAChCwpD,EAAA7R,OAAA,CAAsBz3C,CACtB,OAAOgpD,EAAA,CAAiBt+B,CAAjB,CAAyB4+B,CAAzB,CALoC,CAF/C,GAUEJ,CAGA,CAHmBA,QAAQ,CAAChqD,CAAD,CAAMY,CAAN,CAAa,CACtC,MAAOgX,GAAA,CAAQhX,CAAR,CAD+B,CAGxC,CAAAqpD,CAAA,CAAiBA,QAAQ,CAACjqD,CAAD,CAAM,CAC7B,MAAOA,EADsB,CAbjC,CAkBAiH,EAAA,CAAQojD,CAAApjD,MAAA,CAAU,+CAAV,CACR,IAAI,CAACA,CAAL,CACE,KAAM2iD,EAAA,CAAe,QAAf,CACoDS,CADpD,CAAN,CAGFH,CAAA,CAAkBjjD,CAAA,CAAM,CAAN,CAAlB,EAA8BA,CAAA,CAAM,CAAN,CAC9BkjD,EAAA,CAAgBljD,CAAA,CAAM,CAAN,CAOhB,KAAIujD,EAAe,EAGnBh/B,EAAAgc,iBAAA,CAAwB8iB,CAAxB,CAA6BG,QAAuB,CAACC,CAAD,CAAY,CAAA,IAC1D5pD,CAD0D,CACnDrB,CADmD,CAE1DkrD,EAAevlC,CAAA,CAAS,CAAT,CAF2C,CAG1DwlC,CAH0D,CAM1DC,EAAe,EAN2C,CAO1DC,CAP0D,CAQ1DnlC,CAR0D,CAS1D3lB,CAT0D,CASrDY,CATqD,CAY1DmqD,CAZ0D,CAa1D1+C,CAb0D;AAc1D2+C,EAAiB,EAIrB,IAAI1rD,EAAA,CAAYorD,CAAZ,CAAJ,CACEK,CACA,CADiBL,CACjB,CAAAO,CAAA,CAAclB,CAAd,EAAgCC,CAFlC,KAGO,CACLiB,CAAA,CAAclB,CAAd,EAAgCE,CAEhCc,EAAA,CAAiB,EACjB,KAAK/qD,CAAL,GAAY0qD,EAAZ,CACMA,CAAAxqD,eAAA,CAA0BF,CAA1B,CAAJ,EAAuD,GAAvD,EAAsCA,CAAAwE,OAAA,CAAW,CAAX,CAAtC,EACEumD,CAAAzqD,KAAA,CAAoBN,CAApB,CAGJ+qD,EAAAxqD,KAAA,EATK,CAYPuqD,CAAA,CAAcC,CAAAtrD,OAGdA,EAAA,CAASurD,CAAAvrD,OAAT,CAAiCsrD,CAAAtrD,OACjC,KAAIqB,CAAJ,CAAY,CAAZ,CAAeA,CAAf,CAAuBrB,CAAvB,CAA+BqB,CAAA,EAA/B,CAKC,GAJAd,CAIG,CAJI0qD,CAAD,GAAgBK,CAAhB,CAAkCjqD,CAAlC,CAA0CiqD,CAAA,CAAejqD,CAAf,CAI7C,CAHHF,CAGG,CAHK8pD,CAAA,CAAW1qD,CAAX,CAGL,CAFHkrD,CAEG,CAFSD,CAAA,CAAYjrD,CAAZ,CAAiBY,CAAjB,CAAwBE,CAAxB,CAET,CADH6J,EAAA,CAAwBugD,CAAxB,CAAmC,eAAnC,CACG,CAAAV,CAAAtqD,eAAA,CAA4BgrD,CAA5B,CAAH,CACE7+C,CAGA,CAHQm+C,CAAA,CAAaU,CAAb,CAGR,CAFA,OAAOV,CAAA,CAAaU,CAAb,CAEP,CADAL,CAAA,CAAaK,CAAb,CACA,CAD0B7+C,CAC1B,CAAA2+C,CAAA,CAAelqD,CAAf,CAAA,CAAwBuL,CAJ1B,KAKO,CAAA,GAAIw+C,CAAA3qD,eAAA,CAA4BgrD,CAA5B,CAAJ,CAML,KAJArrD,EAAA,CAAQmrD,CAAR,CAAwB,QAAQ,CAAC3+C,CAAD,CAAQ,CAClCA,CAAJ,EAAaA,CAAAjD,MAAb,GAA0BohD,CAAA,CAAan+C,CAAA64B,GAAb,CAA1B,CAAmD74B,CAAnD,CADsC,CAAxC,CAIM,CAAAu9C,CAAA,CAAe,OAAf,CACiIz3B,CADjI,CACmJ+4B,CADnJ,CAAN,CAIAF,CAAA,CAAelqD,CAAf,CAAA,CAAwB,IAAMoqD,CAAN,CACxBL,EAAA,CAAaK,CAAb,CAAA,CAA0B,CAAA,CAXrB,CAgBR,IAAKlrD,CAAL,GAAYwqD,EAAZ,CAEMA,CAAAtqD,eAAA,CAA4BF,CAA5B,CAAJ,GACEqM,CAIA,CAJQm+C,CAAA,CAAaxqD,CAAb,CAIR,CAHAgwB,CAGA,CAHmB/kB,EAAA,CAAiBoB,CAAA3F,MAAjB,CAGnB,CAFAyd,CAAA04B,MAAA,CAAe7sB,CAAf,CAEA,CADAnwB,CAAA,CAAQmwB,CAAR,CAA0B,QAAQ,CAACxpB,CAAD,CAAU,CAAEA,CAAA,aAAA,CAAsB,CAAA,CAAxB,CAA5C,CACA,CAAA6F,CAAAjD,MAAA6L,SAAA,EALF,CAUGnU;CAAA,CAAQ,CAAb,KAAgBrB,CAAhB,CAAyBsrD,CAAAtrD,OAAzB,CAAgDqB,CAAhD,CAAwDrB,CAAxD,CAAgEqB,CAAA,EAAhE,CAAyE,CACvEd,CAAA,CAAO0qD,CAAD,GAAgBK,CAAhB,CAAkCjqD,CAAlC,CAA0CiqD,CAAA,CAAejqD,CAAf,CAChDF,EAAA,CAAQ8pD,CAAA,CAAW1qD,CAAX,CACRqM,EAAA,CAAQ2+C,CAAA,CAAelqD,CAAf,CACJkqD,EAAA,CAAelqD,CAAf,CAAuB,CAAvB,CAAJ,GAA+B6pD,CAA/B,CAA0DK,CAAA3+C,CAAevL,CAAfuL,CAAuB,CAAvBA,CAwD3D3F,MAAA,CAxD2DskD,CAAA3+C,CAAevL,CAAfuL,CAAuB,CAAvBA,CAwD/C3F,MAAAjH,OAAZ,CAAiC,CAAjC,CAxDC,CAEA,IAAI4M,CAAAjD,MAAJ,CAAiB,CAGfuc,CAAA,CAAatZ,CAAAjD,MAEbwhD,EAAA,CAAWD,CACX,GACEC,EAAA,CAAWA,CAAAv/C,YADb,OAEQu/C,CAFR,EAEoBA,CAAA,aAFpB,CAIkBv+C,EAwCrB3F,MAAA,CAAY,CAAZ,CAxCG,EAA4BkkD,CAA5B,EAEEzmC,CAAA24B,KAAA,CAAc7xC,EAAA,CAAiBoB,CAAA3F,MAAjB,CAAd,CAA6C,IAA7C,CAAmDD,CAAA,CAAOkkD,CAAP,CAAnD,CAEFA,EAAA,CAA2Bt+C,CAwC9B3F,MAAA,CAxC8B2F,CAwClB3F,MAAAjH,OAAZ,CAAiC,CAAjC,CAtDkB,CAAjB,IAiBEkmB,EAAA,CAAa6F,CAAAvF,KAAA,EAGfN,EAAA,CAAWukC,CAAX,CAAA,CAA8BtpD,CAC1BupD,EAAJ,GAAmBxkC,CAAA,CAAWwkC,CAAX,CAAnB,CAA+CnqD,CAA/C,CACA2lB,EAAA4yB,OAAA,CAAoBz3C,CACpB6kB,EAAAwlC,OAAA,CAA+B,CAA/B,GAAqBrqD,CACrB6kB,EAAAylC,MAAA,CAAoBtqD,CAApB,GAA+BgqD,CAA/B,CAA6C,CAC7CnlC,EAAA0lC,QAAA,CAAqB,EAAE1lC,CAAAwlC,OAAF,EAAuBxlC,CAAAylC,MAAvB,CAErBzlC,EAAA2lC,KAAA,CAAkB,EAAE3lC,CAAA4lC,MAAF,CAAmC,CAAnC,IAAsBzqD,CAAtB,CAA4B,CAA5B,EAGbuL,EAAAjD,MAAL,EACE2+C,CAAA,CAAYpiC,CAAZ,CAAwB,QAAQ,CAACjf,CAAD,CAAQ,CACtCA,CAAA,CAAMA,CAAAjH,OAAA,EAAN,CAAA,CAAwBN,CAAAotB,cAAA,CAAuB,iBAAvB,CAA2C4F,CAA3C,CAAwD,GAAxD,CACxBhO,EAAAy4B,MAAA,CAAel2C,CAAf,CAAsB,IAAtB,CAA4BD,CAAA,CAAOkkD,CAAP,CAA5B,CACAA,EAAA,CAAejkD,CACf2F,EAAAjD,MAAA,CAAcuc,CAIdtZ,EAAA3F,MAAA;AAAcA,CACdmkD,EAAA,CAAax+C,CAAA64B,GAAb,CAAA,CAAyB74B,CATa,CAAxC,CArCqE,CAkDzEm+C,CAAA,CAAeK,CA7H+C,CAAhE,CAlDsD,CALrD,CAHiE,CAAlD,CAlzBxB,CA8oCIv8C,GAAkB,CAAC,UAAD,CAAa,QAAQ,CAAC6V,CAAD,CAAW,CACpD,MAAO,SAAQ,CAAC/a,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CACpCgG,CAAAnF,OAAA,CAAab,CAAAooD,OAAb,CAA0BC,QAA0B,CAAC7qD,CAAD,CAAO,CACzDujB,CAAA,CAAS/d,EAAA,CAAUxF,CAAV,CAAA,CAAmB,aAAnB,CAAmC,UAA5C,CAAA,CAAwD4F,CAAxD,CAAiE,SAAjE,CADyD,CAA3D,CADoC,CADc,CAAhC,CA9oCtB,CA8yCIuH,GAAkB,CAAC,UAAD,CAAa,QAAQ,CAACoW,CAAD,CAAW,CACpD,MAAO,SAAQ,CAAC/a,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CACpCgG,CAAAnF,OAAA,CAAab,CAAAsoD,OAAb,CAA0BC,QAA0B,CAAC/qD,CAAD,CAAO,CACzDujB,CAAA,CAAS/d,EAAA,CAAUxF,CAAV,CAAA,CAAmB,UAAnB,CAAgC,aAAzC,CAAA,CAAwD4F,CAAxD,CAAiE,SAAjE,CADyD,CAA3D,CADoC,CADc,CAAhC,CA9yCtB,CA81CI+H,GAAmBslC,EAAA,CAAY,QAAQ,CAACzqC,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CAChEgG,CAAAnF,OAAA,CAAab,CAAAwoD,QAAb,CAA2BC,QAA2B,CAACC,CAAD,CAAYC,CAAZ,CAAuB,CACvEA,CAAJ,EAAkBD,CAAlB,GAAgCC,CAAhC,EACElsD,CAAA,CAAQksD,CAAR,CAAmB,QAAQ,CAACnmD,CAAD,CAAMqnC,CAAN,CAAa,CAAEzmC,CAAAuzC,IAAA,CAAY9M,CAAZ,CAAmB,EAAnB,CAAF,CAAxC,CAEE6e,EAAJ,EAAetlD,CAAAuzC,IAAA,CAAY+R,CAAZ,CAJ4D,CAA7E,CAKG,CAAA,CALH,CADgE,CAA3C,CA91CvB,CAm+CIt9C,GAAoB,CAAC,UAAD,CAAa,QAAQ,CAAC2V,CAAD,CAAW,CACtD,MAAO,UACK,IADL,SAEI,UAFJ,YAKO,CAAC,QAAD,CAAW6nC,QAA2B,EAAG,CACpD,IAAAC,MAAA;AAAa,EADuC,CAAzC,CALP,MAQC3qC,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB4oD,CAAvB,CAA2C,CAAA,IAEnDE,CAFmD,CAGnDC,CAHmD,CAInDnE,CAJmD,CAKnDoE,EAAiB,EAErBhjD,EAAAnF,OAAA,CANgBb,CAAAipD,SAMhB,EANiCjpD,CAAAic,GAMjC,CAAwBitC,QAA4B,CAAC1rD,CAAD,CAAQ,CAAA,IACtDH,CADsD,CACnD0V,EAAKi2C,CAAA3sD,OACZ,IAAQ,CAAR,CAAG0W,CAAH,CAAW,CACT,GAAG6xC,CAAH,CAAqB,CACnB,IAAKvnD,CAAL,CAAS,CAAT,CAAYA,CAAZ,CAAgB0V,CAAhB,CAAoB1V,CAAA,EAApB,CACEunD,CAAA,CAAiBvnD,CAAjB,CAAAyhB,OAAA,EAEF8lC,EAAA,CAAmB,IAJA,CAOrBA,CAAA,CAAmB,EACnB,KAAKvnD,CAAL,CAAQ,CAAR,CAAWA,CAAX,CAAa0V,CAAb,CAAiB1V,CAAA,EAAjB,CAAsB,CACpB,IAAIg6C,EAAW0R,CAAA,CAAiB1rD,CAAjB,CACf2rD,EAAA,CAAe3rD,CAAf,CAAAwU,SAAA,EACA+yC,EAAA,CAAiBvnD,CAAjB,CAAA,CAAsBg6C,CACtBt2B,EAAA04B,MAAA,CAAepC,CAAf,CAAyB,QAAQ,EAAG,CAClCuN,CAAApkD,OAAA,CAAwBnD,CAAxB,CAA2B,CAA3B,CAC+B,EAA/B,GAAGunD,CAAAvoD,OAAH,GACEuoD,CADF,CACqB,IADrB,CAFkC,CAApC,CAJoB,CATb,CAsBXmE,CAAA,CAAmB,EACnBC,EAAA,CAAiB,EAEjB,IAAKF,CAAL,CAA2BF,CAAAC,MAAA,CAAyB,GAAzB,CAA+BrrD,CAA/B,CAA3B,EAAoEorD,CAAAC,MAAA,CAAyB,GAAzB,CAApE,CACE7iD,CAAA0/B,MAAA,CAAY1lC,CAAAmpD,OAAZ,CACA,CAAA1sD,CAAA,CAAQqsD,CAAR,CAA6B,QAAQ,CAACM,CAAD,CAAqB,CACxD,IAAIC,EAAgBrjD,CAAA6c,KAAA,EACpBmmC,EAAA9rD,KAAA,CAAoBmsD,CAApB,CACAD,EAAArmC,WAAA,CAA8BsmC,CAA9B,CAA6C,QAAQ,CAACC,CAAD,CAAc,CACjE,IAAIC,EAASH,CAAAhmD,QAEb2lD,EAAA7rD,KAAA,CAAsBosD,CAAtB,CACAvoC,EAAAy4B,MAAA,CAAe8P,CAAf,CAA4BC,CAAA3qD,OAAA,EAA5B,CAA6C2qD,CAA7C,CAJiE,CAAnE,CAHwD,CAA1D,CA7BwD,CAA5D,CAPuD,CARpD,CAD+C,CAAhC,CAn+CxB,CAgiDIl+C,GAAwBolC,EAAA,CAAY,YAC1B,SAD0B,UAE5B,GAF4B,SAG7B,WAH6B;KAIhCvyB,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiB6f,CAAjB,CAAwB4vB,CAAxB,CAA8B8R,CAA9B,CAA2C,CACvD9R,CAAAgW,MAAA,CAAW,GAAX,CAAiB5lC,CAAAumC,aAAjB,CAAA,CAAwC3W,CAAAgW,MAAA,CAAW,GAAX,CAAiB5lC,CAAAumC,aAAjB,CAAxC,EAAgF,EAChF3W,EAAAgW,MAAA,CAAW,GAAX,CAAiB5lC,CAAAumC,aAAjB,CAAAtsD,KAAA,CAA0C,YAAcynD,CAAd,SAAoCvhD,CAApC,CAA1C,CAFuD,CAJnB,CAAZ,CAhiD5B,CA0iDIkI,GAA2BmlC,EAAA,CAAY,YAC7B,SAD6B,UAE/B,GAF+B,SAGhC,WAHgC,MAInCvyB,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB6yC,CAAvB,CAA6B8R,CAA7B,CAA0C,CACtD9R,CAAAgW,MAAA,CAAW,GAAX,CAAA,CAAmBhW,CAAAgW,MAAA,CAAW,GAAX,CAAnB,EAAsC,EACtChW,EAAAgW,MAAA,CAAW,GAAX,CAAA3rD,KAAA,CAAqB,YAAcynD,CAAd,SAAoCvhD,CAApC,CAArB,CAFsD,CAJf,CAAZ,CA1iD/B,CA2mDIoI,GAAwBilC,EAAA,CAAY,MAChCvyB,QAAQ,CAACkK,CAAD,CAASpG,CAAT,CAAmBynC,CAAnB,CAA2BvpC,CAA3B,CAAuCykC,CAAvC,CAAoD,CAChE,GAAI,CAACA,CAAL,CACE,KAAM1oD,EAAA,CAAO,cAAP,CAAA,CAAuB,QAAvB,CAILkH,EAAA,CAAY6e,CAAZ,CAJK,CAAN,CAOF2iC,CAAA,CAAY,QAAQ,CAACrhD,CAAD,CAAQ,CAC1B0e,CAAAze,MAAA,EACAye,EAAAte,OAAA,CAAgBJ,CAAhB,CAF0B,CAA5B,CATgE,CAD5B,CAAZ,CA3mD5B,CA6pDIwG,GAAkB,CAAC,gBAAD,CAAmB,QAAQ,CAAC6W,CAAD,CAAiB,CAChE,MAAO,UACK,GADL,UAEK,CAAA,CAFL,SAGI1a,QAAQ,CAAC7C,CAAD;AAAUpD,CAAV,CAAgB,CACd,kBAAjB,EAAIA,CAAAkR,KAAJ,EAKEyP,CAAAhM,IAAA,CAJkB3U,CAAA8hC,GAIlB,CAFW1+B,CAAA,CAAQ,CAAR,CAAA0oB,KAEX,CAN6B,CAH5B,CADyD,CAA5C,CA7pDtB,CA6qDI49B,GAAkBztD,CAAA,CAAO,WAAP,CA7qDtB,CAmzDIsP,GAAqBtM,EAAA,CAAQ,UAAY,CAAA,CAAZ,CAAR,CAnzDzB,CAqzDI8K,GAAkB,CAAC,UAAD,CAAa,QAAb,CAAuB,QAAQ,CAAC87C,CAAD,CAAajlC,CAAb,CAAqB,CAAA,IAEpE+oC,EAAoB,wMAFgD,CAGpEC,EAAgB,eAAgB9qD,CAAhB,CAGpB,OAAO,UACK,GADL,SAEI,CAAC,QAAD,CAAW,UAAX,CAFJ,YAGO,CAAC,UAAD,CAAa,QAAb,CAAuB,QAAvB,CAAiC,QAAQ,CAACkjB,CAAD,CAAWoG,CAAX,CAAmBqhC,CAAnB,CAA2B,CAAA,IAC1EznD,EAAO,IADmE,CAE1E6nD,EAAa,EAF6D,CAG1EC,EAAcF,CAH4D,CAK1EG,CAGJ/nD,EAAAgoD,UAAA;AAAiBP,CAAA5G,QAGjB7gD,EAAAioD,KAAA,CAAYC,QAAQ,CAACC,CAAD,CAAeC,CAAf,CAA4BC,CAA5B,CAA4C,CAC9DP,CAAA,CAAcK,CAEdJ,EAAA,CAAgBM,CAH8C,CAOhEroD,EAAAsoD,UAAA,CAAiBC,QAAQ,CAAC/sD,CAAD,CAAQ,CAC/B+J,EAAA,CAAwB/J,CAAxB,CAA+B,gBAA/B,CACAqsD,EAAA,CAAWrsD,CAAX,CAAA,CAAoB,CAAA,CAEhBssD,EAAApW,WAAJ,EAA8Bl2C,CAA9B,GACEwkB,CAAAxf,IAAA,CAAahF,CAAb,CACA,CAAIusD,CAAAnrD,OAAA,EAAJ,EAA4BmrD,CAAAjrC,OAAA,EAF9B,CAJ+B,CAWjC9c,EAAAwoD,aAAA,CAAoBC,QAAQ,CAACjtD,CAAD,CAAQ,CAC9B,IAAAktD,UAAA,CAAeltD,CAAf,CAAJ,GACE,OAAOqsD,CAAA,CAAWrsD,CAAX,CACP,CAAIssD,CAAApW,WAAJ,EAA8Bl2C,CAA9B,EACE,IAAAmtD,oBAAA,CAAyBntD,CAAzB,CAHJ,CADkC,CAUpCwE,EAAA2oD,oBAAA,CAA2BC,QAAQ,CAACpoD,CAAD,CAAM,CACnCqoD,CAAAA,CAAa,IAAbA,CAAoBr2C,EAAA,CAAQhS,CAAR,CAApBqoD,CAAmC,IACvCd,EAAAvnD,IAAA,CAAkBqoD,CAAlB,CACA7oC,EAAAq2B,QAAA,CAAiB0R,CAAjB,CACA/nC,EAAAxf,IAAA,CAAaqoD,CAAb,CACAd,EAAAhqD,KAAA,CAAmB,UAAnB,CAA+B,CAAA,CAA/B,CALuC,CASzCiC,EAAA0oD,UAAA,CAAiBI,QAAQ,CAACttD,CAAD,CAAQ,CAC/B,MAAOqsD,EAAA/sD,eAAA,CAA0BU,CAA1B,CADwB,CAIjC4qB,EAAAyd,IAAA,CAAW,UAAX,CAAuB,QAAQ,EAAG,CAEhC7jC,CAAA2oD,oBAAA,CAA2B7rD,CAFK,CAAlC,CApD8E,CAApE,CAHP,MA6DCof,QAAQ,CAAClY,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuBsjD,CAAvB,CAA8B,CA0C1CyH,QAASA,EAAa,CAAC/kD,CAAD;AAAQglD,CAAR,CAAuBlB,CAAvB,CAAoCmB,CAApC,CAAgD,CACpEnB,CAAAhW,QAAA,CAAsBoX,QAAQ,EAAG,CAC/B,IAAItH,EAAYkG,CAAApW,WAEZuX,EAAAP,UAAA,CAAqB9G,CAArB,CAAJ,EACMmG,CAAAnrD,OAAA,EAEJ,EAF4BmrD,CAAAjrC,OAAA,EAE5B,CADAksC,CAAAxoD,IAAA,CAAkBohD,CAAlB,CACA,CAAkB,EAAlB,GAAIA,CAAJ,EAAsBuH,CAAAprD,KAAA,CAAiB,UAAjB,CAA6B,CAAA,CAA7B,CAHxB,EAKMb,CAAA,CAAY0kD,CAAZ,CAAJ,EAA8BuH,CAA9B,CACEH,CAAAxoD,IAAA,CAAkB,EAAlB,CADF,CAGEyoD,CAAAN,oBAAA,CAA+B/G,CAA/B,CAX2B,CAgBjCoH,EAAA/uC,GAAA,CAAiB,QAAjB,CAA2B,QAAQ,EAAG,CACpCjW,CAAAG,OAAA,CAAa,QAAQ,EAAG,CAClB4jD,CAAAnrD,OAAA,EAAJ,EAA4BmrD,CAAAjrC,OAAA,EAC5BgrC,EAAAnW,cAAA,CAA0BqX,CAAAxoD,IAAA,EAA1B,CAFsB,CAAxB,CADoC,CAAtC,CAjBoE,CAyBtE4oD,QAASA,EAAe,CAACplD,CAAD,CAAQglD,CAAR,CAAuBnY,CAAvB,CAA6B,CACnD,IAAIwY,CACJxY,EAAAiB,QAAA,CAAeC,QAAQ,EAAG,CACxB,IAAIuX,EAAQ,IAAI52C,EAAJ,CAAYm+B,CAAAa,WAAZ,CACZj3C,EAAA,CAAQuuD,CAAA/qD,KAAA,CAAmB,QAAnB,CAAR,CAAsC,QAAQ,CAAC81C,CAAD,CAAS,CACrDA,CAAAsB,SAAA,CAAkBl4C,CAAA,CAAUmsD,CAAAl1C,IAAA,CAAU2/B,CAAAv4C,MAAV,CAAV,CADmC,CAAvD,CAFwB,CAS1BwI,EAAAnF,OAAA,CAAa0qD,QAA4B,EAAG,CACrClqD,EAAA,CAAOgqD,CAAP,CAAiBxY,CAAAa,WAAjB,CAAL,GACE2X,CACA,CADW5qD,EAAA,CAAKoyC,CAAAa,WAAL,CACX,CAAAb,CAAAiB,QAAA,EAFF,CAD0C,CAA5C,CAOAkX,EAAA/uC,GAAA,CAAiB,QAAjB,CAA2B,QAAQ,EAAG,CACpCjW,CAAAG,OAAA,CAAa,QAAQ,EAAG,CACtB,IAAI7F;AAAQ,EACZ7D,EAAA,CAAQuuD,CAAA/qD,KAAA,CAAmB,QAAnB,CAAR,CAAsC,QAAQ,CAAC81C,CAAD,CAAS,CACjDA,CAAAsB,SAAJ,EACE/2C,CAAApD,KAAA,CAAW64C,CAAAv4C,MAAX,CAFmD,CAAvD,CAKAq1C,EAAAc,cAAA,CAAmBrzC,CAAnB,CAPsB,CAAxB,CADoC,CAAtC,CAlBmD,CA+BrDkrD,QAASA,EAAc,CAACxlD,CAAD,CAAQglD,CAAR,CAAuBnY,CAAvB,CAA6B,CA6GlD4Y,QAASA,EAAM,EAAG,CAAA,IAEZC,EAAe,CAAC,EAAD,CAAI,EAAJ,CAFH,CAGZC,EAAmB,CAAC,EAAD,CAHP,CAIZC,CAJY,CAKZC,CALY,CAMZ9V,CANY,CAOZ+V,CAPY,CAOIC,CAChBC,EAAAA,CAAanZ,CAAA4P,YACbj0B,EAAAA,CAASy9B,CAAA,CAASjmD,CAAT,CAATwoB,EAA4B,EAThB,KAUZvxB,EAAOivD,CAAA,CAAUlvD,EAAA,CAAWwxB,CAAX,CAAV,CAA+BA,CAV1B,CAYCnyB,CAZD,CAaZ8vD,CAbY,CAaAzuD,CACZsZ,EAAAA,CAAS,EAETo1C,EAAAA,CAAc,CAAA,CAhBF,KAiBZC,CAjBY,CAkBZjpD,CAGJ,IAAIg0C,CAAJ,CACE,GAAIkV,CAAJ,EAAe9vD,CAAA,CAAQwvD,CAAR,CAAf,CAEE,IADAI,CACSG,CADK,IAAI73C,EAAJ,CAAY,EAAZ,CACL63C,CAAAA,CAAAA,CAAa,CAAtB,CAAyBA,CAAzB,CAAsCP,CAAA3vD,OAAtC,CAAyDkwD,CAAA,EAAzD,CACEv1C,CAAA,CAAOw1C,CAAP,CACA,CADoBR,CAAA,CAAWO,CAAX,CACpB,CAAAH,CAAAz3C,IAAA,CAAgB23C,CAAA,CAAQtmD,CAAR,CAAegR,CAAf,CAAhB,CAAwCg1C,CAAA,CAAWO,CAAX,CAAxC,CAJJ,KAOEH,EAAA,CAAc,IAAI13C,EAAJ,CAAYs3C,CAAZ,CAKlB,KAAKtuD,CAAL,CAAa,CAAb,CAAgBrB,CAAA,CAASY,CAAAZ,OAAT,CAAsBqB,CAAtB,CAA8BrB,CAA9C,CAAsDqB,CAAA,EAAtD,CAA+D,CAE7Dd,CAAA,CAAMc,CACN,IAAIwuD,CAAJ,CAAa,CACXtvD,CAAA,CAAMK,CAAA,CAAKS,CAAL,CACN,IAAuB,GAAvB,GAAKd,CAAAwE,OAAA,CAAW,CAAX,CAAL,CAA6B,QAC7B4V,EAAA,CAAOk1C,CAAP,CAAA,CAAkBtvD,CAHP,CAMboa,CAAA,CAAOw1C,CAAP,CAAA,CAAoBh+B,CAAA,CAAO5xB,CAAP,CAEpBgvD,EAAA,CAAkBa,CAAA,CAAUzmD,CAAV,CAAiBgR,CAAjB,CAAlB,EAA8C,EAC9C,EAAM60C,CAAN,CAAoBH,CAAA,CAAaE,CAAb,CAApB,IACEC,CACA,CADcH,CAAA,CAAaE,CAAb,CACd,CAD8C,EAC9C,CAAAD,CAAAzuD,KAAA,CAAsB0uD,CAAtB,CAFF,CAIIxU,EAAJ,CACEC,CADF,CACal4C,CAAA,CACTitD,CAAAttC,OAAA,CAAmBwtC,CAAA,CAAUA,CAAA,CAAQtmD,CAAR,CAAegR,CAAf,CAAV,CAAmC/X,CAAA,CAAQ+G,CAAR,CAAegR,CAAf,CAAtD,CADS,CADb,EAKMs1C,CAAJ,EACMI,CAEJ,CAFgB,EAEhB,CADAA,CAAA,CAAUF,CAAV,CACA,CADuBR,CACvB,CAAA3U,CAAA;AAAWiV,CAAA,CAAQtmD,CAAR,CAAe0mD,CAAf,CAAX,GAAyCJ,CAAA,CAAQtmD,CAAR,CAAegR,CAAf,CAH3C,EAKEqgC,CALF,CAKa2U,CALb,GAK4B/sD,CAAA,CAAQ+G,CAAR,CAAegR,CAAf,CAE5B,CAAAo1C,CAAA,CAAcA,CAAd,EAA6B/U,CAZ/B,CAcAsV,EAAA,CAAQC,CAAA,CAAU5mD,CAAV,CAAiBgR,CAAjB,CAGR21C,EAAA,CAAQxtD,CAAA,CAAUwtD,CAAV,CAAA,CAAmBA,CAAnB,CAA2B,EACnCd,EAAA3uD,KAAA,CAAiB,IAEXovD,CAAA,CAAUA,CAAA,CAAQtmD,CAAR,CAAegR,CAAf,CAAV,CAAoCk1C,CAAA,CAAUjvD,CAAA,CAAKS,CAAL,CAAV,CAAwBA,CAFjD,OAGRivD,CAHQ,UAILtV,CAJK,CAAjB,CAlC6D,CAyC1DD,CAAL,GACMyV,CAAJ,EAAiC,IAAjC,GAAkBb,CAAlB,CAEEN,CAAA,CAAa,EAAb,CAAAztD,QAAA,CAAyB,IAAI,EAAJ,OAAc,EAAd,UAA2B,CAACmuD,CAA5B,CAAzB,CAFF,CAGYA,CAHZ,EAKEV,CAAA,CAAa,EAAb,CAAAztD,QAAA,CAAyB,IAAI,GAAJ,OAAe,EAAf,UAA4B,CAAA,CAA5B,CAAzB,CANJ,CAWKkuD,EAAA,CAAa,CAAlB,KAAqBW,CAArB,CAAmCnB,CAAAtvD,OAAnC,CACK8vD,CADL,CACkBW,CADlB,CAEKX,CAAA,EAFL,CAEmB,CAEjBP,CAAA,CAAkBD,CAAA,CAAiBQ,CAAjB,CAGlBN,EAAA,CAAcH,CAAA,CAAaE,CAAb,CAEVmB,EAAA1wD,OAAJ,EAAgC8vD,CAAhC,EAEEL,CAMA,CANiB,SACNkB,CAAA1pD,MAAA,EAAAtD,KAAA,CAA8B,OAA9B,CAAuC4rD,CAAvC,CADM,OAERC,CAAAc,MAFQ,CAMjB,CAFAZ,CAEA,CAFkB,CAACD,CAAD,CAElB,CADAiB,CAAA7vD,KAAA,CAAuB6uD,CAAvB,CACA,CAAAf,CAAAtnD,OAAA,CAAqBooD,CAAA1oD,QAArB,CARF,GAUE2oD,CAIA,CAJkBgB,CAAA,CAAkBZ,CAAlB,CAIlB,CAHAL,CAGA,CAHiBC,CAAA,CAAgB,CAAhB,CAGjB,CAAID,CAAAa,MAAJ,EAA4Bf,CAA5B,EACEE,CAAA1oD,QAAApD,KAAA,CAA4B,OAA5B,CAAqC8rD,CAAAa,MAArC,CAA4Df,CAA5D,CAfJ,CAmBAS,EAAA,CAAc,IACV3uD,EAAA,CAAQ,CAAZ,KAAerB,CAAf,CAAwBwvD,CAAAxvD,OAAxB,CAA4CqB,CAA5C,CAAoDrB,CAApD,CAA4DqB,CAAA,EAA5D,CACEq4C,CACA,CADS8V,CAAA,CAAYnuD,CAAZ,CACT,CAAA,CAAKuvD,CAAL,CAAsBlB,CAAA,CAAgBruD,CAAhB,CAAsB,CAAtB,CAAtB,GAEE2uD,CAQA,CARcY,CAAA7pD,QAQd,CAPI6pD,CAAAN,MAOJ,GAP6B5W,CAAA4W,MAO7B;AANEN,CAAAvgC,KAAA,CAAiBmhC,CAAAN,MAAjB,CAAwC5W,CAAA4W,MAAxC,CAMF,CAJIM,CAAAnrB,GAIJ,GAJ0BiU,CAAAjU,GAI1B,EAHEuqB,CAAA7pD,IAAA,CAAgByqD,CAAAnrB,GAAhB,CAAoCiU,CAAAjU,GAApC,CAGF,CAAImrB,CAAA5V,SAAJ,GAAgCtB,CAAAsB,SAAhC,EACEgV,CAAAtsD,KAAA,CAAiB,UAAjB,CAA8BktD,CAAA5V,SAA9B,CAAwDtB,CAAAsB,SAAxD,CAXJ,GAiBoB,EAAlB,GAAItB,CAAAjU,GAAJ,EAAwB+qB,CAAxB,CAEEzpD,CAFF,CAEYypD,CAFZ,CAOGrqD,CAAAY,CAAAZ,CAAU0qD,CAAA5pD,MAAA,EAAVd,KAAA,CACQuzC,CAAAjU,GADR,CAAA9hC,KAAA,CAES,UAFT,CAEqB+1C,CAAAsB,SAFrB,CAAAvrB,KAAA,CAGSiqB,CAAA4W,MAHT,CAiBH,CAXAZ,CAAA7uD,KAAA,CAAsC,SACzBkG,CADyB,OAE3B2yC,CAAA4W,MAF2B,IAG9B5W,CAAAjU,GAH8B,UAIxBiU,CAAAsB,SAJwB,CAAtC,CAWA,CALIgV,CAAJ,CACEA,CAAA9T,MAAA,CAAkBn1C,CAAlB,CADF,CAGE0oD,CAAA1oD,QAAAM,OAAA,CAA8BN,CAA9B,CAEF,CAAAipD,CAAA,CAAcjpD,CAzChB,CA8CF,KADA1F,CAAA,EACA,CAAMquD,CAAA1vD,OAAN,CAA+BqB,CAA/B,CAAA,CACEquD,CAAAlyC,IAAA,EAAAzW,QAAA0b,OAAA,EA5Ee,CAgFnB,IAAA,CAAMiuC,CAAA1wD,OAAN,CAAiC8vD,CAAjC,CAAA,CACEY,CAAAlzC,IAAA,EAAA,CAAwB,CAAxB,CAAAzW,QAAA0b,OAAA,EAzKc,CA5GlB,IAAIjb,CAEJ,IAAI,EAAEA,CAAF,CAAUspD,CAAAtpD,MAAA,CAAiB8lD,CAAjB,CAAV,CAAJ,CACE,KAAMD,GAAA,CAAgB,MAAhB,CAIJyD,CAJI,CAIQhqD,EAAA,CAAY6nD,CAAZ,CAJR,CAAN,CAJgD,IAW9C4B,EAAYhsC,CAAA,CAAO/c,CAAA,CAAM,CAAN,CAAP,EAAmBA,CAAA,CAAM,CAAN,CAAnB,CAXkC,CAY9C2oD,EAAY3oD,CAAA,CAAM,CAAN,CAAZ2oD,EAAwB3oD,CAAA,CAAM,CAAN,CAZsB,CAa9CqoD,EAAUroD,CAAA,CAAM,CAAN,CAboC,CAc9C4oD,EAAY7rC,CAAA,CAAO/c,CAAA,CAAM,CAAN,CAAP,EAAmB,EAAnB,CAdkC,CAe9C5E;AAAU2hB,CAAA,CAAO/c,CAAA,CAAM,CAAN,CAAA,CAAWA,CAAA,CAAM,CAAN,CAAX,CAAsB2oD,CAA7B,CAfoC,CAgB9CP,EAAWrrC,CAAA,CAAO/c,CAAA,CAAM,CAAN,CAAP,CAhBmC,CAkB9CyoD,EADQzoD,CAAAupD,CAAM,CAANA,CACE,CAAQxsC,CAAA,CAAO/c,CAAA,CAAM,CAAN,CAAP,CAAR,CAA2B,IAlBS,CAuB9CkpD,EAAoB,CAAC,CAAC,SAAU/B,CAAV,OAA+B,EAA/B,CAAD,CAAD,CAEpB6B,EAAJ,GAEEhH,CAAA,CAASgH,CAAT,CAAA,CAAqB7mD,CAArB,CAQA,CAJA6mD,CAAAp/B,YAAA,CAAuB,UAAvB,CAIA,CAAAo/B,CAAA/tC,OAAA,EAVF,CAcAksC,EAAAznD,MAAA,EAEAynD,EAAA/uC,GAAA,CAAiB,QAAjB,CAA2B,QAAQ,EAAG,CACpCjW,CAAAG,OAAA,CAAa,QAAQ,EAAG,CAAA,IAClB0lD,CADkB,CAElBvE,EAAa2E,CAAA,CAASjmD,CAAT,CAAbshD,EAAgC,EAFd,CAGlBtwC,EAAS,EAHS,CAIlBpa,CAJkB,CAIbY,CAJa,CAISE,CAJT,CAIgByuD,CAJhB,CAI4B9vD,CAJ5B,CAIoCywD,CAJpC,CAIiDP,CAEvE,IAAInV,CAAJ,CAEE,IADA55C,CACqB,CADb,EACa,CAAhB2uD,CAAgB,CAAH,CAAG,CAAAW,CAAA,CAAcC,CAAA1wD,OAAnC,CACK8vD,CADL,CACkBW,CADlB,CAEKX,CAAA,EAFL,CAME,IAFAN,CAEe,CAFDkB,CAAA,CAAkBZ,CAAlB,CAEC,CAAXzuD,CAAW,CAAH,CAAG,CAAArB,CAAA,CAASwvD,CAAAxvD,OAAxB,CAA4CqB,CAA5C,CAAoDrB,CAApD,CAA4DqB,CAAA,EAA5D,CACE,IAAI,CAAC2vD,CAAD,CAAiBxB,CAAA,CAAYnuD,CAAZ,CAAA0F,QAAjB,EAA6C,CAA7C,CAAAi0C,SAAJ,CAA8D,CAC5Dz6C,CAAA,CAAMywD,CAAA7qD,IAAA,EACF0pD,EAAJ,GAAal1C,CAAA,CAAOk1C,CAAP,CAAb,CAA+BtvD,CAA/B,CACA,IAAI0vD,CAAJ,CACE,IAAKC,CAAL,CAAkB,CAAlB,CAAqBA,CAArB,CAAkCjF,CAAAjrD,OAAlC,GACE2a,CAAA,CAAOw1C,CAAP,CACI,CADgBlF,CAAA,CAAWiF,CAAX,CAChB,CAAAD,CAAA,CAAQtmD,CAAR,CAAegR,CAAf,CAAA,EAA0Bpa,CAFhC,EAAqD2vD,CAAA,EAArD,EADF,IAMEv1C,EAAA,CAAOw1C,CAAP,CAAA,CAAoBlF,CAAA,CAAW1qD,CAAX,CAEtBY,EAAAN,KAAA,CAAW+B,CAAA,CAAQ+G,CAAR,CAAegR,CAAf,CAAX,CAX4D,CAA9D,CATN,IAwBO,CACLpa,CAAA,CAAMouD,CAAAxoD,IAAA,EACN,IAAW,GAAX,EAAI5F,CAAJ,CACEY,CAAA,CAAQxB,CADV,KAEO,IAAY,EAAZ,GAAIY,CAAJ,CACLY,CAAA,CAAQ,IADH,KAGL,IAAI8uD,CAAJ,CACE,IAAKC,CAAL,CAAkB,CAAlB,CAAqBA,CAArB,CAAkCjF,CAAAjrD,OAAlC,CAAqDkwD,CAAA,EAArD,CAEE,IADAv1C,CAAA,CAAOw1C,CAAP,CACI;AADgBlF,CAAA,CAAWiF,CAAX,CAChB,CAAAD,CAAA,CAAQtmD,CAAR,CAAegR,CAAf,CAAA,EAA0Bpa,CAA9B,CAAmC,CACjCY,CAAA,CAAQyB,CAAA,CAAQ+G,CAAR,CAAegR,CAAf,CACR,MAFiC,CAAnC,CAHJ,IASEA,EAAA,CAAOw1C,CAAP,CAEA,CAFoBlF,CAAA,CAAW1qD,CAAX,CAEpB,CADIsvD,CACJ,GADal1C,CAAA,CAAOk1C,CAAP,CACb,CAD+BtvD,CAC/B,EAAAY,CAAA,CAAQyB,CAAA,CAAQ+G,CAAR,CAAegR,CAAf,CAIsB,EAAlC,CAAI+1C,CAAA,CAAkB,CAAlB,CAAA1wD,OAAJ,EACM0wD,CAAA,CAAkB,CAAlB,CAAA,CAAqB,CAArB,CAAAjrB,GADN,GACqCllC,CADrC,GAEImwD,CAAA,CAAkB,CAAlB,CAAA,CAAqB,CAArB,CAAA1V,SAFJ,CAEuC,CAAA,CAFvC,CAtBK,CA4BPxE,CAAAc,cAAA,CAAmBn2C,CAAnB,CA1DsB,CAAxB,CADoC,CAAtC,CA+DAq1C,EAAAiB,QAAA,CAAe2X,CAGfzlD,EAAAnF,OAAA,CAAa4qD,CAAb,CA3GkD,CAhGpD,GAAKnI,CAAA,CAAM,CAAN,CAAL,CAAA,CAF0C,IAItC2H,EAAa3H,CAAA,CAAM,CAAN,CACbwG,EAAAA,CAAcxG,CAAA,CAAM,CAAN,CALwB,KAMtClM,EAAWp3C,CAAAo3C,SAN2B,CAOtC+V,EAAantD,CAAAstD,UAPyB,CAQtCT,EAAa,CAAA,CARyB,CAStC1B,CATsC,CAYtC+B,EAAiB7pD,CAAA,CAAOtH,CAAA8T,cAAA,CAAuB,QAAvB,CAAP,CAZqB,CAatCm9C,EAAkB3pD,CAAA,CAAOtH,CAAA8T,cAAA,CAAuB,UAAvB,CAAP,CAboB,CActCk6C,EAAgBmD,CAAA5pD,MAAA,EAGZjG,EAAAA,CAAI,CAAZ,KAjB0C,IAiB3BuR,EAAWxL,CAAAwL,SAAA,EAjBgB,CAiBImE,EAAKnE,CAAAvS,OAAnD,CAAoEgB,CAApE,CAAwE0V,CAAxE,CAA4E1V,CAAA,EAA5E,CACE,GAA0B,EAA1B,GAAIuR,CAAA,CAASvR,CAAT,CAAAG,MAAJ,CAA8B,CAC5B2tD,CAAA,CAAc0B,CAAd,CAA2Bj+C,CAAAmT,GAAA,CAAY1kB,CAAZ,CAC3B,MAF4B,CAMhC4tD,CAAAhB,KAAA,CAAgBH,CAAhB,CAA6B+C,CAA7B,CAAyC9C,CAAzC,CAGI3S,EAAJ,GACE0S,CAAA9V,SADF,CACyBuZ,QAAQ,CAAC/vD,CAAD,CAAQ,CACrC,MAAO,CAACA,CAAR,EAAkC,CAAlC,GAAiBA,CAAAnB,OADoB,CADzC,CAMI8wD,EAAJ,CAAgB3B,CAAA,CAAexlD,CAAf,CAAsB5C,CAAtB,CAA+B0mD,CAA/B,CAAhB,CACS1S,CAAJ,CAAcgU,CAAA,CAAgBplD,CAAhB,CAAuB5C,CAAvB,CAAgC0mD,CAAhC,CAAd,CACAiB,CAAA,CAAc/kD,CAAd,CAAqB5C,CAArB,CAA8B0mD,CAA9B,CAA2CmB,CAA3C,CAjCL,CAF0C,CA7DvC,CANiE,CAApD,CArzDtB,CAwvEIhhD,GAAkB,CAAC,cAAD;AAAiB,QAAQ,CAACwW,CAAD,CAAe,CAC5D,IAAI+sC,EAAiB,WACR1uD,CADQ,cAELA,CAFK,CAKrB,OAAO,UACK,GADL,UAEK,GAFL,SAGImH,QAAQ,CAAC7C,CAAD,CAAUpD,CAAV,CAAgB,CAC/B,GAAId,CAAA,CAAYc,CAAAxC,MAAZ,CAAJ,CAA6B,CAC3B,IAAIuuB,EAAgBtL,CAAA,CAAard,CAAA0oB,KAAA,EAAb,CAA6B,CAAA,CAA7B,CACfC,EAAL,EACE/rB,CAAAqqB,KAAA,CAAU,OAAV,CAAmBjnB,CAAA0oB,KAAA,EAAnB,CAHyB,CAO7B,MAAO,SAAS,CAAC9lB,CAAD,CAAQ5C,CAAR,CAAiBpD,CAAjB,CAAuB,CAAA,IAEjCpB,EAASwE,CAAAxE,OAAA,EAFwB,CAGjCqsD,EAAarsD,CAAAwH,KAAA,CAFIqnD,mBAEJ,CAAbxC,EACErsD,CAAAA,OAAA,EAAAwH,KAAA,CAHeqnD,mBAGf,CAEFxC,EAAJ,EAAkBA,CAAAjB,UAAlB,CAGE5mD,CAAArD,KAAA,CAAa,UAAb,CAAyB,CAAA,CAAzB,CAHF,CAKEkrD,CALF,CAKeuC,CAGXzhC,EAAJ,CACE/lB,CAAAnF,OAAA,CAAakrB,CAAb,CAA4B2hC,QAA+B,CAACzpB,CAAD,CAASC,CAAT,CAAiB,CAC1ElkC,CAAAqqB,KAAA,CAAU,OAAV,CAAmB4Z,CAAnB,CACIA,EAAJ,GAAeC,CAAf,EAAuB+mB,CAAAT,aAAA,CAAwBtmB,CAAxB,CACvB+mB,EAAAX,UAAA,CAAqBrmB,CAArB,CAH0E,CAA5E,CADF,CAOEgnB,CAAAX,UAAA,CAAqBtqD,CAAAxC,MAArB,CAGF4F,EAAA6Y,GAAA,CAAW,UAAX,CAAuB,QAAQ,EAAG,CAChCgvC,CAAAT,aAAA,CAAwBxqD,CAAAxC,MAAxB,CADgC,CAAlC,CAxBqC,CARR,CAH5B,CANqD,CAAxC,CAxvEtB,CAyyEIwM,GAAiB/K,EAAA,CAAQ,UACjB,GADiB;SAEjB,CAAA,CAFiB,CAAR,CAKfnD,EAAAyK,QAAA1B,UAAJ,CAEEq4B,OAAAE,IAAA,CAAY,gDAAZ,CAFF,EA5jnBA,CAFApuB,EAEA,CAFSlT,CAAAkT,OAET,GACE3L,CAYA,CAZS2L,EAYT,CAXA3Q,CAAA,CAAO2Q,EAAA/M,GAAP,CAAkB,OACT6f,EAAA9b,MADS,cAEF8b,EAAA4E,aAFE,YAGJ5E,EAAA5B,WAHI,UAIN4B,EAAAnc,SAJM,eAKDmc,EAAAkhC,cALC,CAAlB,CAWA,CAFAh1C,EAAA,CAAwB,QAAxB,CAAkC,CAAA,CAAlC,CAAwC,CAAA,CAAxC,CAA8C,CAAA,CAA9C,CAEA,CADAA,EAAA,CAAwB,OAAxB,CAAiC,CAAA,CAAjC,CAAwC,CAAA,CAAxC,CAA+C,CAAA,CAA/C,CACA,CAAAA,EAAA,CAAwB,MAAxB,CAAgC,CAAA,CAAhC,CAAuC,CAAA,CAAvC,CAA8C,CAAA,CAA9C,CAbF,EAeE3K,CAfF,CAeW8L,CAyjnBX,CAvjnBA5I,EAAAnD,QAujnBA,CAvjnBkBC,CAujnBlB,CAFA6F,EAAA,CAAmB3C,EAAnB,CAEA,CAAAlD,CAAA,CAAOtH,CAAP,CAAAw6C,MAAA,CAAuB,QAAQ,EAAG,CAChC3xC,EAAA,CAAY7I,CAAZ,CAAsB8I,EAAtB,CADgC,CAAlC,CAZA,CAh8pBqC,CAAtC,CAAA,CAg9pBE/I,MAh9pBF,CAg9pBUC,QAh9pBV,CAk9pBD,EAACwK,OAAAonD,MAAA,EAAD,EAAoBpnD,OAAAnD,QAAA,CAAgBrH,QAAhB,CAAAkE,KAAA,CAA+B,MAA/B,CAAAo4C,QAAA,CAA+C,uRAA/C;",
-"sources":["angular.js"],
-"names":["window","document","undefined","minErr","isArrayLike","obj","isWindow","length","nodeType","isString","isArray","forEach","iterator","context","key","isFunction","hasOwnProperty","call","sortedKeys","keys","push","sort","forEachSorted","i","reverseParams","iteratorFn","value","nextUid","index","uid","digit","charCodeAt","join","String","fromCharCode","unshift","setHashKey","h","$$hashKey","extend","dst","arguments","int","str","parseInt","inherit","parent","extra","noop","identity","$","valueFn","isUndefined","isDefined","isObject","isNumber","isDate","toString","isRegExp","location","alert","setInterval","isElement","node","nodeName","prop","attr","find","map","results","list","indexOf","array","arrayRemove","splice","copy","source","destination","$evalAsync","$watch","ngMinErr","Date","getTime","RegExp","shallowCopy","src","charAt","equals","o1","o2","t1","t2","keySet","csp","securityPolicy","isActive","querySelector","bind","self","fn","curryArgs","slice","startIndex","apply","concat","toJsonReplacer","val","toJson","pretty","JSON","stringify","fromJson","json","parse","toBoolean","v","lowercase","startingTag","element","jqLite","clone","empty","e","elemHtml","append","html","TEXT_NODE","match","replace","tryDecodeURIComponent","decodeURIComponent","parseKeyValue","keyValue","key_value","split","toKeyValue","parts","arrayValue","encodeUriQuery","encodeUriSegment","pctEncodeSpaces","encodeURIComponent","angularInit","bootstrap","elements","appElement","module","names","NG_APP_CLASS_REGEXP","name","getElementById","querySelectorAll","exec","className","attributes","modules","doBootstrap","injector","tag","$provide","createInjector","invoke","scope","compile","animate","$apply","data","NG_DEFER_BOOTSTRAP","test","angular","resumeBootstrap","angular.resumeBootstrap","extraModules","snake_case","separator","SNAKE_CASE_REGEXP","letter","pos","toLowerCase","assertArg","arg","reason","assertArgFn","acceptArrayAnnotation","constructor","assertNotHasOwnProperty","getter","path","bindFnToScope","lastInstance","len","getBlockElements","nodes","startNode","endNode","nextSibling","setupModuleLoader","$injectorMinErr","$$minErr","factory","requires","configFn","invokeLater","provider","method","insertMethod","invokeQueue","moduleInstance","runBlocks","config","run","block","publishExternalAPI","version","uppercase","angularModule","$LocaleProvider","ngModule","$$SanitizeUriProvider","$CompileProvider","directive","htmlAnchorDirective","inputDirective","formDirective","scriptDirective","selectDirective","styleDirective","optionDirective","ngBindDirective","ngBindHtmlDirective","ngBindTemplateDirective","ngClassDirective","ngClassEvenDirective","ngClassOddDirective","ngCloakDirective","ngControllerDirective","ngFormDirective","ngHideDirective","ngIfDirective","ngIncludeDirective","ngInitDirective","ngNonBindableDirective","ngPluralizeDirective","ngRepeatDirective","ngShowDirective","ngStyleDirective","ngSwitchDirective","ngSwitchWhenDirective","ngSwitchDefaultDirective","ngOptionsDirective","ngTranscludeDirective","ngModelDirective","ngListDirective","ngChangeDirective","requiredDirective","ngValueDirective","ngIncludeFillContentDirective","ngAttributeAliasDirectives","ngEventDirectives","$AnchorScrollProvider","$AnimateProvider","$BrowserProvider","$CacheFactoryProvider","$ControllerProvider","$DocumentProvider","$ExceptionHandlerProvider","$FilterProvider","$InterpolateProvider","$IntervalProvider","$HttpProvider","$HttpBackendProvider","$LocationProvider","$LogProvider","$ParseProvider","$RootScopeProvider","$QProvider","$SceProvider","$SceDelegateProvider","$SnifferProvider","$TemplateCacheProvider","$TimeoutProvider","$WindowProvider","$$RAFProvider","$$AsyncCallbackProvider","camelCase","SPECIAL_CHARS_REGEXP","_","offset","toUpperCase","MOZ_HACK_REGEXP","jqLitePatchJQueryRemove","dispatchThis","filterElems","getterIfNoArguments","removePatch","param","filter","fireEvent","set","setIndex","setLength","childIndex","children","shift","triggerHandler","childLength","jQuery","originalJqFn","$original","JQLite","trim","jqLiteMinErr","parsed","SINGLE_TAG_REGEXP","fragment","createDocumentFragment","HTML_REGEXP","tmp","appendChild","createElement","TAG_NAME_REGEXP","wrap","wrapMap","_default","innerHTML","XHTML_TAG_REGEXP","removeChild","firstChild","lastChild","j","jj","childNodes","textContent","createTextNode","jqLiteAddNodes","jqLiteClone","cloneNode","jqLiteDealoc","jqLiteRemoveData","jqLiteOff","type","unsupported","events","jqLiteExpandoStore","handle","eventHandler","removeEventListenerFn","expandoId","jqName","expandoStore","jqCache","$destroy","jqId","jqLiteData","isSetter","keyDefined","isSimpleGetter","jqLiteHasClass","selector","getAttribute","jqLiteRemoveClass","cssClasses","setAttribute","cssClass","jqLiteAddClass","existingClasses","root","jqLiteController","jqLiteInheritedData","ii","parentNode","host","jqLiteEmpty","getBooleanAttrName","booleanAttr","BOOLEAN_ATTR","BOOLEAN_ELEMENTS","createEventHandler","event","preventDefault","event.preventDefault","returnValue","stopPropagation","event.stopPropagation","cancelBubble","target","srcElement","defaultPrevented","prevent","isDefaultPrevented","event.isDefaultPrevented","eventHandlersCopy","msie","elem","hashKey","objType","HashMap","put","annotate","$inject","fnText","STRIP_COMMENTS","argDecl","FN_ARGS","FN_ARG_SPLIT","FN_ARG","all","underscore","last","modulesToLoad","supportObject","delegate","provider_","providerInjector","instantiate","$get","providerCache","providerSuffix","factoryFn","loadModules","moduleFn","loadedModules","get","_runBlocks","_invokeQueue","invokeArgs","message","stack","createInternalInjector","cache","getService","serviceName","INSTANTIATING","err","locals","args","Type","Constructor","returnedValue","prototype","instance","has","service","$injector","constant","instanceCache","decorator","decorFn","origProvider","orig$get","origProvider.$get","origInstance","instanceInjector","servicename","autoScrollingEnabled","disableAutoScrolling","this.disableAutoScrolling","$window","$location","$rootScope","getFirstAnchor","result","scroll","hash","elm","scrollIntoView","getElementsByName","scrollTo","autoScrollWatch","autoScrollWatchAction","$$rAF","$timeout","supported","Browser","$log","$sniffer","completeOutstandingRequest","outstandingRequestCount","outstandingRequestCallbacks","pop","error","startPoller","interval","setTimeout","check","pollFns","pollFn","pollTimeout","fireUrlChange","newLocation","lastBrowserUrl","url","urlChangeListeners","listener","rawDocument","history","clearTimeout","pendingDeferIds","isMock","$$completeOutstandingRequest","$$incOutstandingRequestCount","self.$$incOutstandingRequestCount","notifyWhenNoOutstandingRequests","self.notifyWhenNoOutstandingRequests","callback","addPollFn","self.addPollFn","href","baseElement","self.url","replaceState","pushState","urlChangeInit","onUrlChange","self.onUrlChange","on","hashchange","baseHref","self.baseHref","lastCookies","lastCookieString","cookiePath","cookies","self.cookies","cookieLength","cookie","escape","warn","cookieArray","unescape","substring","defer","self.defer","delay","timeoutId","cancel","self.defer.cancel","deferId","$document","this.$get","cacheFactory","cacheId","options","refresh","entry","freshEnd","staleEnd","n","link","p","nextEntry","prevEntry","caches","size","stats","capacity","Number","MAX_VALUE","lruHash","lruEntry","remove","removeAll","destroy","info","cacheFactory.info","cacheFactory.get","$cacheFactory","$$sanitizeUriProvider","hasDirectives","Suffix","COMMENT_DIRECTIVE_REGEXP","CLASS_DIRECTIVE_REGEXP","EVENT_HANDLER_ATTR_REGEXP","this.directive","registerDirective","directiveFactory","$exceptionHandler","directives","priority","require","controller","restrict","aHrefSanitizationWhitelist","this.aHrefSanitizationWhitelist","regexp","imgSrcSanitizationWhitelist","this.imgSrcSanitizationWhitelist","$interpolate","$http","$templateCache","$parse","$controller","$sce","$animate","$$sanitizeUri","$compileNodes","transcludeFn","maxPriority","ignoreDirective","previousCompileContext","nodeValue","compositeLinkFn","compileNodes","safeAddClass","publicLinkFn","cloneConnectFn","transcludeControllers","$linkNode","JQLitePrototype","eq","$element","addClass","nodeList","$rootElement","boundTranscludeFn","childLinkFn","$node","childScope","nodeListLength","stableNodeList","Array","linkFns","nodeLinkFn","$new","childTranscludeFn","transclude","createBoundTranscludeFn","attrs","linkFnFound","Attributes","collectDirectives","applyDirectivesToNode","terminal","transcludedScope","cloneFn","controllers","scopeCreated","$$transcluded","attrsMap","$attr","addDirective","directiveNormalize","nodeName_","nName","nAttrs","attrStartName","attrEndName","specified","ngAttrName","NG_ATTR_BINDING","substr","directiveNName","addAttrInterpolateDirective","addTextInterpolateDirective","byPriority","groupScan","attrStart","attrEnd","depth","hasAttribute","$compileMinErr","groupElementsLinkFnWrapper","linkFn","compileNode","templateAttrs","jqCollection","originalReplaceDirective","preLinkFns","postLinkFns","addLinkFns","pre","post","newIsolateScopeDirective","$$isolateScope","cloneAndAnnotateFn","getControllers","elementControllers","retrievalMethod","optional","directiveName","linkNode","controllersBoundTransclude","cloneAttachFn","hasElementTranscludeDirective","isolateScope","$$element","LOCAL_REGEXP","templateDirective","$$originalDirective","definition","scopeName","attrName","mode","lastValue","parentGet","parentSet","compare","$$isolateBindings","$observe","$$observers","$$scope","literal","a","b","assign","parentValueWatch","parentValue","controllerDirectives","controllerInstance","controllerAs","$scope","scopeToChild","template","templateUrl","terminalPriority","newScopeDirective","nonTlbTranscludeDirective","hasTranscludeDirective","$compileNode","$template","$$start","$$end","directiveValue","assertNoDuplicate","$$tlb","createComment","replaceWith","replaceDirective","contents","denormalizeTemplate","newTemplateAttrs","templateDirectives","unprocessedDirectives","markDirectivesAsIsolate","mergeTemplateAttributes","compileTemplateUrl","Math","max","tDirectives","startAttrName","endAttrName","srcAttr","dstAttr","$set","tAttrs","linkQueue","afterTemplateNodeLinkFn","afterTemplateChildLinkFn","beforeTemplateCompileNode","origAsyncDirective","derivedSyncDirective","getTrustedResourceUrl","success","content","childBoundTranscludeFn","tempTemplateAttrs","beforeTemplateLinkNode","linkRootElement","oldClasses","response","code","headers","delayedNodeLinkFn","ignoreChildLinkFn","rootElement","diff","what","previousDirective","text","interpolateFn","textInterpolateLinkFn","bindings","interpolateFnWatchAction","getTrustedContext","attrNormalizedName","HTML","RESOURCE_URL","attrInterpolatePreLinkFn","$$inter","newValue","oldValue","$updateClass","elementsToRemove","newNode","firstElementToRemove","removeCount","j2","replaceChild","expando","k","kk","annotation","$addClass","classVal","$removeClass","removeClass","newClasses","toAdd","tokenDifference","toRemove","setClass","writeAttr","booleanKey","removeAttr","listeners","startSymbol","endSymbol","PREFIX_REGEXP","str1","str2","values","tokens1","tokens2","token","CNTRL_REG","register","this.register","expression","identifier","exception","cause","parseHeaders","line","headersGetter","headersObj","transformData","fns","JSON_START","JSON_END","PROTECTION_PREFIX","CONTENT_TYPE_APPLICATION_JSON","defaults","d","interceptorFactories","interceptors","responseInterceptorFactories","responseInterceptors","$httpBackend","$browser","$q","requestConfig","transformResponse","resp","status","reject","transformRequest","mergeHeaders","execHeaders","headerContent","headerFn","header","defHeaders","reqHeaders","defHeaderName","reqHeaderName","common","lowercaseDefHeaderName","xsrfValue","urlIsSameOrigin","xsrfCookieName","xsrfHeaderName","chain","serverRequest","reqData","withCredentials","sendReq","then","promise","when","reversedInterceptors","interceptor","request","requestError","responseError","thenFn","rejectFn","promise.success","promise.error","done","headersString","statusText","resolvePromise","$$phase","deferred","resolve","removePendingReq","idx","pendingRequests","cachedResp","buildUrl","params","defaultCache","timeout","responseType","interceptorFactory","responseFn","createShortMethods","createShortMethodsWithData","createXhr","XMLHttpRequest","ActiveXObject","createHttpBackend","callbacks","$browserDefer","jsonpReq","script","doneWrapper","onreadystatechange","onload","onerror","body","script.onreadystatechange","readyState","script.onerror","ABORTED","timeoutRequest","jsonpDone","xhr","abort","completeRequest","urlResolve","protocol","callbackId","counter","open","setRequestHeader","xhr.onreadystatechange","responseHeaders","getAllResponseHeaders","responseText","send","this.startSymbol","this.endSymbol","mustHaveExpression","trustedContext","endIndex","hasInterpolation","startSymbolLength","exp","endSymbolLength","$interpolateMinErr","part","getTrusted","valueOf","newErr","$interpolate.startSymbol","$interpolate.endSymbol","count","invokeApply","clearInterval","iteration","skipApply","$$intervalId","tick","notify","intervals","interval.cancel","short","pluralCat","num","encodePath","segments","parseAbsoluteUrl","absoluteUrl","locationObj","appBase","parsedUrl","$$protocol","$$host","hostname","$$port","port","DEFAULT_PORTS","parseAppUrl","relativeUrl","prefixed","$$path","pathname","$$search","search","$$hash","beginsWith","begin","whole","stripHash","stripFile","lastIndexOf","LocationHtml5Url","basePrefix","$$html5","appBaseNoFile","$$parse","this.$$parse","pathUrl","$locationMinErr","$$compose","this.$$compose","$$url","$$absUrl","$$rewrite","this.$$rewrite","appUrl","prevAppUrl","LocationHashbangUrl","hashPrefix","withoutBaseUrl","withoutHashUrl","windowsFilePathExp","firstPathSegmentMatch","LocationHashbangInHtml5Url","locationGetter","property","locationGetterSetter","preprocess","html5Mode","this.hashPrefix","prefix","this.html5Mode","afterLocationChange","oldUrl","$broadcast","absUrl","initialUrl","LocationMode","ctrlKey","metaKey","which","absHref","animVal","rewrittenUrl","newUrl","$digest","changeCounter","$locationWatch","currentReplace","$$replace","debug","debugEnabled","this.debugEnabled","flag","formatError","Error","sourceURL","consoleLog","console","logFn","log","hasApply","arg1","arg2","ensureSafeMemberName","fullExpression","$parseMinErr","ensureSafeObject","setter","setValue","fullExp","propertyObj","unwrapPromises","promiseWarning","$$v","cspSafeGetterFn","key0","key1","key2","key3","key4","cspSafePromiseEnabledGetter","pathVal","cspSafeGetter","simpleGetterFn1","simpleGetterFn2","getterFn","getterFnCache","pathKeys","pathKeysLength","evaledFnGetter","Function","$parseOptions","this.unwrapPromises","logPromiseWarnings","this.logPromiseWarnings","$filter","promiseWarningCache","parsedExpression","lexer","Lexer","parser","Parser","qFactory","nextTick","exceptionHandler","defaultCallback","defaultErrback","pending","ref","createInternalRejectedPromise","progress","errback","progressback","wrappedCallback","wrappedErrback","wrappedProgressback","catch","finally","makePromise","resolved","handleCallback","isResolved","callbackOutput","promises","requestAnimationFrame","webkitRequestAnimationFrame","mozRequestAnimationFrame","cancelAnimationFrame","webkitCancelAnimationFrame","mozCancelAnimationFrame","webkitCancelRequestAnimationFrame","rafSupported","raf","id","timer","TTL","$rootScopeMinErr","lastDirtyWatch","digestTtl","this.digestTtl","Scope","$id","$parent","$$watchers","$$nextSibling","$$prevSibling","$$childHead","$$childTail","$root","$$destroyed","$$asyncQueue","$$postDigestQueue","$$listeners","$$listenerCount","beginPhase","phase","compileToFn","decrementListenerCount","current","initWatchVal","isolate","child","ChildScope","watchExp","objectEquality","watcher","listenFn","watcher.fn","newVal","oldVal","originalFn","$watchCollection","veryOldValue","trackVeryOldValue","changeDetected","objGetter","internalArray","internalObject","initRun","oldLength","$watchCollectionWatch","newLength","$watchCollectionAction","watch","watchers","asyncQueue","postDigestQueue","dirty","ttl","watchLog","logIdx","logMsg","asyncTask","$eval","isNaN","next","$on","this.$watch","expr","$$postDigest","namedListeners","$emit","listenerArgs","array1","currentScope","sanitizeUri","uri","isImage","regex","normalizedVal","adjustMatcher","matcher","$sceMinErr","adjustMatchers","matchers","adjustedMatchers","SCE_CONTEXTS","resourceUrlWhitelist","resourceUrlBlacklist","this.resourceUrlWhitelist","this.resourceUrlBlacklist","generateHolderType","Base","holderType","trustedValue","$$unwrapTrustedValue","this.$$unwrapTrustedValue","holderType.prototype.valueOf","holderType.prototype.toString","htmlSanitizer","trustedValueHolderBase","byType","CSS","URL","JS","trustAs","maybeTrusted","allowed","enabled","this.enabled","$sceDelegate","msieDocumentMode","sce","isEnabled","sce.isEnabled","sce.getTrusted","parseAs","sce.parseAs","sceParseAsTrusted","enumValue","lName","eventSupport","android","userAgent","navigator","boxee","documentMode","vendorPrefix","vendorRegex","bodyStyle","style","transitions","animations","webkitTransition","webkitAnimation","hasEvent","divElm","deferreds","$$timeoutId","timeout.cancel","base","urlParsingNode","requestUrl","originUrl","filters","suffix","currencyFilter","dateFilter","filterFilter","jsonFilter","limitToFilter","lowercaseFilter","numberFilter","orderByFilter","uppercaseFilter","comparator","comparatorType","predicates","predicates.check","objKey","filtered","$locale","formats","NUMBER_FORMATS","amount","currencySymbol","CURRENCY_SYM","formatNumber","PATTERNS","GROUP_SEP","DECIMAL_SEP","number","fractionSize","pattern","groupSep","decimalSep","isFinite","isNegative","abs","numStr","formatedText","hasExponent","toFixed","fractionLen","min","minFrac","maxFrac","pow","round","fraction","lgroup","lgSize","group","gSize","negPre","posPre","negSuf","posSuf","padNumber","digits","neg","dateGetter","date","dateStrGetter","shortForm","jsonStringToDate","string","R_ISO8601_STR","tzHour","tzMin","dateSetter","setUTCFullYear","setFullYear","timeSetter","setUTCHours","setHours","m","s","ms","parseFloat","format","DATETIME_FORMATS","NUMBER_STRING","DATE_FORMATS_SPLIT","DATE_FORMATS","object","input","limit","out","sortPredicate","reverseOrder","reverseComparator","comp","descending","v1","v2","predicate","arrayCopy","ngDirective","FormController","toggleValidCss","isValid","validationErrorKey","INVALID_CLASS","VALID_CLASS","form","parentForm","nullFormCtrl","invalidCount","errors","$error","controls","$name","ngForm","$dirty","$pristine","$valid","$invalid","$addControl","PRISTINE_CLASS","form.$addControl","control","$removeControl","form.$removeControl","queue","validationToken","$setValidity","form.$setValidity","$setDirty","form.$setDirty","DIRTY_CLASS","$setPristine","form.$setPristine","validate","ctrl","validatorName","validity","addNativeHtml5Validators","$parsers","validator","badInput","customError","typeMismatch","valueMissing","textInputType","composing","ngTrim","$viewValue","$setViewValue","deferListener","keyCode","$render","ctrl.$render","$isEmpty","ngPattern","patternValidator","patternObj","$formatters","ngMinlength","minlength","minLengthValidator","ngMaxlength","maxlength","maxLengthValidator","classDirective","arrayDifference","arrayClasses","classes","digestClassCounts","classCounts","classesToUpdate","ngClassWatchAction","$index","old$index","mod","Object","addEventListenerFn","addEventListener","attachEvent","removeEventListener","detachEvent","_data","JQLite._data","optgroup","option","tbody","tfoot","colgroup","caption","thead","th","td","ready","trigger","fired","removeAttribute","css","currentStyle","lowercasedName","getNamedItem","ret","getText","textProp","NODE_TYPE_TEXT_PROPERTY","$dv","multiple","selected","onFn","eventFns","contains","compareDocumentPosition","adown","documentElement","bup","eventmap","related","relatedTarget","one","off","replaceNode","insertBefore","contentDocument","prepend","wrapNode","after","newElement","toggleClass","condition","classCondition","nextElementSibling","getElementsByTagName","eventName","eventData","arg3","unbind","$animateMinErr","$$selectors","classNameFilter","this.classNameFilter","$$classNameFilter","$$asyncCallback","enter","leave","move","add","PATH_MATCH","paramValue","OPERATORS","null","true","false","+","-","*","/","%","^","===","!==","==","!=","<",">","<=",">=","&&","||","&","|","!","ESCAPE","lex","ch","lastCh","tokens","is","readString","peek","readNumber","isIdent","readIdent","was","isWhitespace","ch2","ch3","fn2","fn3","throwError","chars","isExpOperator","start","end","colStr","peekCh","ident","lastDot","peekIndex","methodName","quote","rawString","hex","rep","ZERO","assignment","logicalOR","functionCall","fieldAccess","objectIndex","filterChain","this.filterChain","primary","statements","expect","consume","arrayDeclaration","msg","peekToken","e1","e2","e3","e4","t","unaryFn","right","ternaryFn","left","middle","binaryFn","statement","argsFn","fnInvoke","ternary","logicalAND","equality","relational","additive","multiplicative","unary","field","indexFn","o","safe","contextGetter","fnPtr","elementFns","allConstant","elementFn","keyValues","ampmGetter","getHours","AMPMS","timeZoneGetter","zone","getTimezoneOffset","paddedZone","xlinkHref","propName","normalized","ngBooleanAttrWatchAction","formDirectiveFactory","isNgForm","formElement","action","preventDefaultListener","parentFormCtrl","alias","URL_REGEXP","EMAIL_REGEXP","NUMBER_REGEXP","inputType","numberInputType","minValidator","maxValidator","urlInputType","urlValidator","emailInputType","emailValidator","radioInputType","checked","checkboxInputType","trueValue","ngTrueValue","falseValue","ngFalseValue","ctrl.$isEmpty","NgModelController","$modelValue","NaN","$viewChangeListeners","ngModelGet","ngModel","ngModelSet","this.$isEmpty","inheritedData","this.$setValidity","this.$setPristine","this.$setViewValue","ngModelWatch","formatters","ctrls","modelCtrl","formCtrl","ngChange","required","ngList","viewValue","CONSTANT_VALUE_REGEXP","tpl","tplAttr","ngValue","ngValueConstantLink","ngValueLink","valueWatchAction","ngBind","ngBindWatchAction","ngBindTemplate","ngBindHtml","getStringValue","ngBindHtmlWatchAction","getTrustedHtml","$transclude","previousElements","ngIf","ngIfWatchAction","$anchorScroll","srcExp","ngInclude","onloadExp","autoScrollExp","autoscroll","previousElement","currentElement","cleanupLastIncludeContent","parseAsResourceUrl","ngIncludeWatchAction","afterAnimation","thisChangeId","newScope","$compile","ngInit","BRACE","numberExp","whenExp","whens","whensExpFns","isWhen","attributeName","ngPluralizeWatch","ngPluralizeWatchAction","ngRepeatMinErr","ngRepeat","trackByExpGetter","trackByIdExpFn","trackByIdArrayFn","trackByIdObjFn","valueIdentifier","keyIdentifier","hashFnLocals","lhs","rhs","trackByExp","lastBlockMap","ngRepeatAction","collection","previousNode","nextNode","nextBlockMap","arrayLength","collectionKeys","nextBlockOrder","trackByIdFn","trackById","$first","$last","$middle","$odd","$even","ngShow","ngShowWatchAction","ngHide","ngHideWatchAction","ngStyle","ngStyleWatchAction","newStyles","oldStyles","ngSwitchController","cases","selectedTranscludes","selectedElements","selectedScopes","ngSwitch","ngSwitchWatchAction","change","selectedTransclude","selectedScope","caseElement","anchor","ngSwitchWhen","$attrs","ngOptionsMinErr","NG_OPTIONS_REGEXP","nullModelCtrl","optionsMap","ngModelCtrl","unknownOption","databound","init","self.init","ngModelCtrl_","nullOption_","unknownOption_","addOption","self.addOption","removeOption","self.removeOption","hasOption","renderUnknownOption","self.renderUnknownOption","unknownVal","self.hasOption","setupAsSingle","selectElement","selectCtrl","ngModelCtrl.$render","emptyOption","setupAsMultiple","lastView","items","selectMultipleWatch","setupAsOptions","render","optionGroups","optionGroupNames","optionGroupName","optionGroup","existingParent","existingOptions","modelValue","valuesFn","keyName","groupIndex","selectedSet","lastElement","trackFn","trackIndex","valueName","groupByFn","modelCast","label","displayFn","nullOption","groupLength","optionGroupsCache","optGroupTemplate","existingOption","optionTemplate","optionsExp","track","optionElement","ngOptions","ngModelCtrl.$isEmpty","nullSelectCtrl","selectCtrlName","interpolateWatchAction","$$csp"]
-}
diff --git a/v1.2/docs/user-guide/update-demo/local/index.html b/v1.2/docs/user-guide/update-demo/local/index.html
deleted file mode 100644
index 47a1965b75..0000000000
--- a/v1.2/docs/user-guide/update-demo/local/index.html
+++ /dev/null
@@ -1,36 +0,0 @@
-<!--
-Copyright 2014 Google Inc. All rights reserved.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-
-<html ng-app>
-<head>
-  <script src="angular.min.js"></script>
-  <script src="script.js"></script>
-  <link rel="stylesheet" href="style.css"></link>
-</head>
-<body ng-controller="ButtonsCtrl">
-  <div ng-repeat="server in servers" class="pod">
-    <img src="/api/v1/proxy/namespaces/default/pods/{{server.podName}}/{{server.image}}" height="100px" width="100px" />
-    <b>ID:</b> {{server.podName}}<br>
-    <b>Host:</b> <a href="/api/v1/proxy/namespaces/default/pods/{{server.podName}}/data.json">{{server.host}}</a><br>
-    <b>Status:</b> {{server.status}}<br>
-    <b>Image:</b> {{server.dockerImage}}<br>
-    <b>Labels:</b>
-    <ul>
-      <li ng-repeat="(key,value) in server.labels">{{key}}={{value}}</li>
-    </ul>
-  </div>
-</body>
-</html>
diff --git a/v1.2/docs/user-guide/update-demo/local/script.js b/v1.2/docs/user-guide/update-demo/local/script.js
deleted file mode 100644
index d6edb74f73..0000000000
--- a/v1.2/docs/user-guide/update-demo/local/script.js
+++ /dev/null
@@ -1,100 +0,0 @@
-/*
-Copyright 2014 Google Inc. All rights reserved.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-*/
-
-var base = "/api/v1/";
-
-var updateImage = function($http, server) {
-  $http.get(base + "proxy/namespaces/default/pods/" + server.podName + "/data.json")
-    .success(function(data) {
-      console.log(data);
-      server.image = data.image;
-    })
-    .error(function(data) {
-      console.log(data);
-      server.image = "";
-    });
-};
-
-var updateServer = function($http, server) {
-  $http.get(base + "namespaces/default/pods/" + server.podName)
-    .success(function(data) {
-      console.log(data);
-      server.labels = data.metadata.labels;
-      server.host = data.status.hostIP.split('.')[0];
-      server.status = data.status.phase;
-      server.dockerImage = data.status.containerStatuses[0].image;
-      updateImage($http, server);
-    })
-    .error(function(data) {
-      console.log(data);
-    });
-};
-
-var updateData = function($scope, $http) {
-  var servers = $scope.servers;
-  for (var i = 0; i < servers.length; ++i) {
-    var server = servers[i];
-    updateServer($http, server);
-  }
-};
-
-var ButtonsCtrl = function ($scope, $http, $interval) {
-  $scope.servers = [];
-  update($scope, $http);
-  $interval(angular.bind({}, update, $scope, $http), 2000);
-};
-
-var getServer = function($scope, name) {
-  var servers = $scope.servers;
-  for (var i = 0; i < servers.length; ++i) {
-    if (servers[i].podName == name) {
-      return servers[i];
-    }
-  }
-  return null;
-};
-
-var isUpdateDemoPod = function(pod) {
-    return pod.metadata && pod.metadata.labels && pod.metadata.labels.name == "update-demo";
-};
-
-var update = function($scope, $http) {
-  if (!$http) {
-    console.log("No HTTP!");
-    return;
-  }
-  $http.get(base + "namespaces/default/pods")
-    .success(function(data) {
-      console.log(data);
-      var newServers = [];
-      for (var i = 0; i < data.items.length; ++i) {
-        var pod = data.items[i];
-        if (!isUpdateDemoPod(pod)) {
-          continue;
-        }
-        var server = getServer($scope, pod.metadata.name);
-        if (server == null) {
-          server = { "podName": pod.metadata.name };
-        }
-        newServers.push(server);
-      }
-      $scope.servers = newServers;
-      updateData($scope, $http);
-    })
-    .error(function(data) {
-      console.log("ERROR: " + data);
-    })
-};
diff --git a/v1.2/docs/user-guide/update-demo/local/style.css b/v1.2/docs/user-guide/update-demo/local/style.css
deleted file mode 100644
index ea8941c0ac..0000000000
--- a/v1.2/docs/user-guide/update-demo/local/style.css
+++ /dev/null
@@ -1,40 +0,0 @@
-/*
-Copyright 2014 Google Inc. All rights reserved.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-*/
-
-img {
-  height: 100px;
-  width: 100px;
-  float: right;
-  background-size: 100px 100px;
-  background-color: black;
-  margin-left: 10px;
-  border: none;
-}
-
-ul {
-  margin-top: 0;
-  margin-bottom: 0;
-}
-
-.pod {
-  font-family: Roboto, Open Sans, arial;
-  border: 1px solid black;
-  border-radius: 5px;
-  padding: 10px;
-  margin: 10px;
-  display: inline-block;
-  background-color: #D1D1D1;
-}
diff --git a/v1.2/docs/user-guide/update-demo/nautilus-rc.yaml b/v1.2/docs/user-guide/update-demo/nautilus-rc.yaml
deleted file mode 100644
index cae1a22c16..0000000000
--- a/v1.2/docs/user-guide/update-demo/nautilus-rc.yaml
+++ /dev/null
@@ -1,21 +0,0 @@
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: update-demo-nautilus
-spec:
-  replicas: 2
-  selector:
-    name: update-demo
-    version: nautilus
-  template:
-    metadata:
-      labels:
-        name: update-demo
-        version: nautilus
-    spec:
-      containers:
-      - image: gcr.io/google_containers/update-demo:nautilus
-        name: update-demo
-        ports:
-        - containerPort: 80
-          protocol: TCP
diff --git a/v1.2/docs/user-guide/volumes.md b/v1.2/docs/user-guide/volumes.md
deleted file mode 100644
index fe55dd38e2..0000000000
--- a/v1.2/docs/user-guide/volumes.md
+++ /dev/null
@@ -1,378 +0,0 @@
----
----
-
-On-disk files in a container are ephemeral, which presents some problems for
-non-trivial applications when running in containers.  First, when a container
-crashes kubelet will restart it, but the files will be lost - the
-container starts with a clean slate.  Second, when running containers together
-in a `Pod` it is often necessary to share files between those containers.  The
-Kubernetes `Volume` abstraction solves both of these problems.
-
-Familiarity with [pods](/{{page.version}}/docs/user-guide/pods) is suggested.
-
-* TOC
-{:toc}
-
-
-## Background
-
-Docker also has a concept of
-[volumes](https://docs.docker.com/userguide/dockervolumes/), though it is
-somewhat looser and less managed.  In Docker, a volume is simply a directory on
-disk or in another container.  Lifetimes are not managed and until very
-recently there were only local-disk-backed volumes.  Docker now provides volume
-drivers, but the functionality is very limited for now (e.g. as of Docker 1.7
-only one volume driver is allowed per container and there is no way to pass
-parameters to volumes).
-
-A Kubernetes volume, on the other hand, has an explicit lifetime - the same as
-the pod that encloses it.  Consequently, a volume outlives any containers that run
-within the Pod, and data is preserved across Container restarts. Of course, when a
-Pod ceases to exist, the volume will cease to exist, too.  Perhaps more
-importantly than this, Kubernetes supports many type of volumes, and a Pod can
-use any number of them simultaneously.
-
-At its core, a volume is just a directory, possibly with some data in it, which
-is accessible to the containers in a pod.  How that directory comes to be, the
-medium that backs it, and the contents of it are determined by the particular
-volume type used.
-
-To use a volume, a pod specifies what volumes to provide for the pod (the
-[`spec.volumes`](http://kubernetes.io/third_party/swagger-ui/#!/v1/createPod)
-field) and where to mount those into containers(the
-[`spec.containers.volumeMounts`](http://kubernetes.io/third_party/swagger-ui/#!/v1/createPod)
-field).
-
-A process in a container sees a filesystem view composed from their Docker
-image and volumes.  The [Docker
-image](https://docs.docker.com/userguide/dockerimages/) is at the root of the
-filesystem hierarchy, and any volumes are mounted at the specified paths within
-the image.  Volumes can not mount onto other volumes or have hard links to
-other volumes.  Each container in the Pod must independently specify where to
-mount each volume.
-
-## Types of Volumes
-
-Kubernetes supports several types of Volumes:
-
-   * `emptyDir`
-   * `hostPath`
-   * `gcePersistentDisk`
-   * `awsElasticBlockStore`
-   * `nfs`
-   * `iscsi`
-   * `flocker`
-   * `glusterfs`
-   * `rbd`
-   * `gitRepo`
-   * `secret`
-   * `persistentVolumeClaim`
-
-We welcome additional contributions.
-
-### emptyDir
-
-An `emptyDir` volume is first created when a Pod is assigned to a Node, and
-exists as long as that Pod is running on that node.  As the name says, it is
-initially empty.  Containers in the pod can all read and write the same
-files in the `emptyDir` volume, though that volume can be mounted at the same
-or different paths in each container.  When a Pod is removed from a node for
-any reason, the data in the `emptyDir` is deleted forever.  NOTE: a container
-crashing does *NOT* remove a pod from a node, so the data in an `emptyDir`
-volume is safe across container crashes.
-
-Some uses for an `emptyDir` are:
-
-* scratch space, such as for a disk-based mergesortcw
-* checkpointing a long computation for recovery from crashes
-* holding files that a content-manager container fetches while a webserver
-  container serves the data
-
-By default, `emptyDir` volumes are stored on whatever medium is backing the
-machine - that might be disk or SSD or network storage, depending on your
-environment.  However, you can set the `emptyDir.medium` field to `"Memory"`
-to tell Kubernetes to mount a tmpfs (RAM-backed filesystem) for you instead.
-While tmpfs is very fast, be aware that unlike disks, tmpfs is cleared on
-machine reboot and any files you write will count against your container's
-memory limit.
-
-### hostPath
-
-A `hostPath` volume mounts a file or directory from the host node's filesystem
-into your pod.  This is not something that most Pods will need, but it offers a
-powerful escape hatch for some applications.
-
-For example, some uses for a `hostPath` are:
-
-* running a container that needs access to Docker internals; use a `hostPath`
-  of `/var/lib/docker`
-* running cAdvisor in a container; use a `hostPath` of `/dev/cgroups`
-
-Watch out when using this type of volume, because:
-
-* pods with identical configuration (such as created from a podTemplate) may
-  behave differently on different nodes due to different files on the nodes
-* when Kubernetes adds resource-aware scheduling, as is planned, it will not be
-  able to account for resources used by a `hostPath`
-
-### gcePersistentDisk
-
-A `gcePersistentDisk` volume mounts a Google Compute Engine (GCE) [Persistent
-Disk](http://cloud.google.com/compute/docs/disks) into your pod.  Unlike
-`emptyDir`, which is erased when a Pod is removed, the contents of a PD are
-preserved and the volume is merely unmounted.  This means that a PD can be
-pre-populated with data, and that data can be "handed off" between pods.
-
-__Important: You must create a PD using `gcloud` or the GCE API or UI
-before you can use it__
-
-There are some restrictions when using a `gcePersistentDisk`:
-
-* the nodes on which pods are running must be GCE VMs
-* those VMs need to be in the same GCE project and zone as the PD
-
-A feature of PD is that they can be mounted as read-only by multiple consumers
-simultaneously.  This means that you can pre-populate a PD with your dataset
-and then serve it in parallel from as many pods as you need.  Unfortunately,
-PDs can only be mounted by a single consumer in read-write mode - no
-simultaneous readers allowed.
-
-Using a PD on a pod controlled by a ReplicationController will fail unless
-the PD is read-only or the replica count is 0 or 1.
-
-#### Creating a PD
-
-Before you can use a GCE PD with a pod, you need to create it.
-
-```shell
-gcloud compute disks create --size=500GB --zone=us-central1-a my-data-disk
-```
-
-#### Example pod
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: test-pd
-spec:
-  containers:
-  - image: gcr.io/google_containers/test-webserver
-    name: test-container
-    volumeMounts:
-    - mountPath: /test-pd
-      name: test-volume
-  volumes:
-  - name: test-volume
-    # This GCE PD must already exist.
-    gcePersistentDisk:
-      pdName: my-data-disk
-      fsType: ext4
-```
-
-### awsElasticBlockStore
-
-An `awsElasticBlockStore` volume mounts an Amazon Web Services (AWS) [EBS
-Volume](http://aws.amazon.com/ebs/) into your pod.  Unlike
-`emptyDir`, which is erased when a Pod is removed, the contents of an EBS
-volume are preserved and the volume is merely unmounted.  This means that an
-EBS volume can be pre-populated with data, and that data can be "handed off"
-between pods.
-
-__Important: You must create an EBS volume using `aws ec2 create-volume` or
-the AWS API before you can use it__
-
-There are some restrictions when using an awsElasticBlockStore volume:
-
-* the nodes on which pods are running must be AWS EC2 instances
-* those instances need to be in the same region and availability-zone as the EBS volume
-* EBS only supports a single EC2 instance mounting a volume
-
-#### Creating an EBS volume
-
-Before you can use a EBS volume with a pod, you need to create it.
-
-```shell
-aws ec2 create-volume --availability-zone eu-west-1a --size 10 --volume-type gp2
-```
-
-Make sure the zone matches the zone you brought up your cluster in.  (And also check that the size and EBS volume
-type are suitable for your use!)
-
-#### AWS EBS Example configuration
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: test-ebs
-spec:
-  containers:
-  - image: gcr.io/google_containers/test-webserver
-    name: test-container
-    volumeMounts:
-    - mountPath: /test-ebs
-      name: test-volume
-  volumes:
-  - name: test-volume
-    # This AWS EBS volume must already exist.
-    awsElasticBlockStore:
-      volumeID: aws://<availability-zone>/<volume-id>
-      fsType: ext4
-```
-
-(Note: the syntax of volumeID is currently awkward; #10181 fixes it)
-
-### nfs
-
-An `nfs` volume allows an existing NFS (Network File System) share to be
-mounted into your pod. Unlike `emptyDir`, which is erased when a Pod is
-removed, the contents of an `nfs` volume are preserved and the volume is merely
-unmounted.  This means that an NFS volume can be pre-populated with data, and
-that data can be "handed off" between pods.  NFS can be mounted by multiple
-writers simultaneously.
-
-__Important: You must have your own NFS server running with the share exported
-before you can use it__
-
-See the [NFS example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/nfs/) for more details.
-
-### iscsi
-
-An `iscsi` volume allows an existing iSCSI (SCSI over IP) volume to be mounted
-into your pod.  Unlike `emptyDir`, which is erased when a Pod is removed, the
-contents of an `iscsi` volume are preserved and the volume is merely
-unmounted.  This means that an iscsi volume can be pre-populated with data, and
-that data can be "handed off" between pods.
-
-__Important: You must have your own iSCSI server running with the volume
-created before you can use it__
-
-A feature of iSCSI is that it can be mounted as read-only by multiple consumers
-simultaneously.  This means that you can pre-populate a volume with your dataset
-and then serve it in parallel from as many pods as you need.  Unfortunately,
-iSCSI volumes can only be mounted by a single consumer in read-write mode - no
-simultaneous readers allowed.
-
-See the [iSCSI example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/iscsi/) for more details.
-
-### flocker
-
-[Flocker](https://clusterhq.com/flocker) is an open-source clustered container data volume manager. It provides management
-and orchestration of data volumes backed by a variety of storage backends.
-
-A `flocker` volume allows a Flocker dataset to be mounted into a pod. If the
-dataset does not already exist in Flocker, it needs to be created with Flocker
-CLI or the using the Flocker API. If the dataset already exists it will
-reattached by Flocker to the node that the pod is scheduled. This means data
-can be "handed off" between pods as required.
-
-__Important: You must have your own Flocker installation running before you can use it__
-
-See the [Flocker example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/flocker/) for more details.
-
-### glusterfs
-
-A `glusterfs` volume allows a [Glusterfs](http://www.gluster.org) (an open
-source networked filesystem) volume to be mounted into your pod.  Unlike
-`emptyDir`, which is erased when a Pod is removed, the contents of a
-`glusterfs` volume are preserved and the volume is merely unmounted.  This
-means that a glusterfs volume can be pre-populated with data, and that data can
-be "handed off" between pods.  GlusterFS can be mounted by multiple writers
-simultaneously.
-
-__Important: You must have your own GlusterFS installation running before you
-can use it__
-
-See the [GlusterFS example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/glusterfs/) for more details.
-
-### rbd
-
-An `rbd` volume allows a [Rados Block
-Device](http://ceph.com/docs/master/rbd/rbd/) volume to be mounted into your
-pod.  Unlike `emptyDir`, which is erased when a Pod is removed, the contents of
-a `rbd` volume are preserved and the volume is merely unmounted.  This
-means that a RBD volume can be pre-populated with data, and that data can
-be "handed off" between pods.
-
-__Important: You must have your own Ceph installation running before you
-can use RBD__
-
-A feature of RBD is that it can be mounted as read-only by multiple consumers
-simultaneously.  This means that you can pre-populate a volume with your dataset
-and then serve it in parallel from as many pods as you need.  Unfortunately,
-RBD volumes can only be mounted by a single consumer in read-write mode - no
-simultaneous writers allowed.
-
-See the [RBD example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/rbd/) for more details.
-
-### gitRepo
-
-A `gitRepo` volume is an example of what can be done as a volume plugin.  It
-mounts an empty directory and clones a git repository into it for your pod to
-use.  In the future, such volumes may be moved to an even more decoupled model,
-rather than extending the Kubernetes API for every such use case.
-
-Here is a example for gitRepo volume:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: server
-spec:
-  containers:
-  - image: nginx
-    name: nginx
-    volumeMounts:
-    - mountPath: /mypath
-      name: git-volume
-  volumes:
-  - name: git-volume
-    gitRepo:
-      repository: "git@somewhere:me/my-git-repository.git"
-      revision: "22f1d8406d464b0c0874075539c1f2e96c253775"
-```
-
-### secret
-
-A `secret` volume is used to pass sensitive information, such as passwords, to
-pods.  You can store secrets in the Kubernetes API and mount them as files for
-use by pods without coupling to Kubernetes directly.  `secret` volumes are
-backed by tmpfs (a RAM-backed filesystem) so they are never written to
-non-volatile storage.
-
-__Important: You must create a secret in the Kubernetes API before you can use
-it__
-
-Secrets are described in more detail [here](/{{page.version}}/docs/user-guide/secrets).
-
-### persistentVolumeClaim
-
-A `persistentVolumeClaim` volume is used to mount a
-[PersistentVolume](/{{page.version}}/docs/user-guide/persistent-volumes) into a pod.  PersistentVolumes are a
-way for users to "claim" durable storage (such as a GCE PersistentDisk or an
-iSCSI volume) without knowing the details of the particular cloud environment.
-
-See the [PersistentVolumes example](/{{page.version}}/docs/user-guide/persistent-volumes/) for more
-details.
-
-### downwardAPI
-
-A `downwardAPI` volume is used to make downward API data available to applications.
-It mounts a directory and writes the requested data in plain text files.
-
-See the [`downwardAPI` volume example](/{{page.version}}/docs/user-guide/downward-api/volume/)  for more details.
-
-## Resources
-
-The storage media (Disk, SSD, etc) of an `emptyDir` volume is determined by the
-medium of the filesystem holding the kubelet root dir (typically
-`/var/lib/kubelet`).  There is no limit on how much space an `emptyDir` or
-`hostPath` volume can consume, and no isolation between containers or between
-pods.
-
-In the future, we expect that `emptyDir` and `hostPath` volumes will be able to
-request a certain amount of space using a [resource](/{{page.version}}/docs/user-guide/compute-resources)
-specification, and to select the type of media to use, for clusters that have
-several media types.
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/walkthrough/index.md b/v1.2/docs/user-guide/walkthrough/index.md
deleted file mode 100644
index 88d9417418..0000000000
--- a/v1.2/docs/user-guide/walkthrough/index.md
+++ /dev/null
@@ -1,182 +0,0 @@
----
----
-
-For Kubernetes 101, we will cover kubectl, pods, volumes, and multiple containers
-
-In order for the kubectl usage examples to work, make sure you have an examples directory locally, either from [a release](https://github.com/kubernetes/kubernetes/releases) or [the source](https://github.com/kubernetes/kubernetes).
-
-* TOC
-{:toc}
-
-
-## Kubectl CLI
-
-The easiest way to interact with Kubernetes is via the [kubectl](/{{page.version}}/docs/user-guide/kubectl-overview/) command-line interface.
-
-For more info about kubectl, including its usage, commands, and parameters, see the [kubectl CLI reference](/{{page.version}}/docs/user-guide/kubectl-overview/).
-
-If you haven't installed and configured kubectl, finish the [prerequisites](/{{page.version}}/docs/user-guide/prereqs/) before continuing.
-
-## Pods
-
-In Kubernetes, a group of one or more containers is called a _pod_. Containers in a pod are deployed together, and are started, stopped, and replicated as a group.
-
-See [pods](/{{page.version}}/docs/user-guide/pods/) for more details.
-
-
-#### Pod Definition
-
-The simplest pod definition describes the deployment of a single container.  For example, an nginx web server pod might be defined as such:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    ports:
-    - containerPort: 80
-```
-
-A pod definition is a declaration of a _desired state_.  Desired state is a very important concept in the Kubernetes model.  Many things present a desired state to the system, and it is Kubernetes' responsibility to make sure that the current state matches the desired state.  For example, when you create a Pod, you declare that you want the containers in it to be running.  If the containers happen to not be running (e.g. program failure, ...), Kubernetes will continue to (re-)create them for you in order to drive them to the desired state. This process continues until the Pod is deleted.
-
-See the [design document](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/README.md) for more details.
-
-
-#### Pod Management
-
-Create a pod containing an nginx server ([pod-nginx.yaml](/{{page.version}}/docs/user-guide/walkthrough/pod-nginx.yaml)):
-
-```shell
-$ kubectl create -f docs/user-guide/walkthrough/pod-nginx.yaml
-```
-
-List all pods:
-
-```shell
-$ kubectl get pods
-```
-
-On most providers, the pod IPs are not externally accessible. The easiest way to test that the pod is working is to create a busybox pod and exec commands on it remotely. See the [command execution documentation](/{{page.version}}/docs/user-guide/getting-into-containers/) for details.
-
-Provided the pod IP is accessible, you should be able to access its http endpoint with curl on port 80:
-
-```shell
-$ curl http://$(kubectl get pod nginx -o go-template={{.status.podIP}})
-```
-
-Delete the pod by name:
-
-```shell
-$ kubectl delete pod nginx
-```
-
-#### Volumes
-
-That's great for a simple static web server, but what about persistent storage?
-
-The container file system only lives as long as the container does. So if your app's state needs to survive relocation, reboots, and crashes, you'll need to configure some persistent storage.
-
-For this example we'll be creating a Redis pod with a named volume and volume mount that defines the path to mount the volume.
-
-1. Define a volume:
-
-```yaml
-volumes:
-    - name: redis-persistent-storage
-      emptyDir: {}
-```
-
-2. Define a volume mount within a container definition:
-
-```yaml
-volumeMounts:
-    # name must match the volume name below
-    - name: redis-persistent-storage
-      # mount path within the container
-      mountPath: /data/redis
-```
-
-Example Redis pod definition with a persistent storage volume ([pod-redis.yaml](/{{page.version}}/docs/user-guide/walkthrough/pod-redis.yaml)):
-
-<!-- BEGIN MUNGE: EXAMPLE pod-redis.yaml -->
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: redis
-spec:
-  containers:
-  - name: redis
-    image: redis
-    volumeMounts:
-    - name: redis-persistent-storage
-      mountPath: /data/redis
-  volumes:
-  - name: redis-persistent-storage
-    emptyDir: {}
-```
-
-[Download example](/{{page.version}}/docs/user-guide/walkthrough/pod-redis.yaml)
-<!-- END MUNGE: EXAMPLE pod-redis.yaml -->
-
-Notes:
-
-- The volume mount name is a reference to a specific empty dir volume.
-- The volume mount path is the path to mount the empty dir volume within the container.
-
-##### Volume Types
-
-- **EmptyDir**: Creates a new directory that will persist across container failures and restarts.
-- **HostPath**: Mounts an existing directory on the node's file system (e.g. `/var/logs`).
-
-See [volumes](/{{page.version}}/docs/user-guide/volumes) for more details.
-
-
-#### Multiple Containers
-
-_Note:
-The examples below are syntactically correct, but some of the images (e.g. kubernetes/git-monitor) don't exist yet.  We're working on turning these into working examples._
-
-
-However, often you want to have two different containers that work together.  An example of this would be a web server, and a helper job that polls a git repository for new updates:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: www
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    volumeMounts:
-    - mountPath: /srv/www
-      name: www-data
-      readOnly: true
-  - name: git-monitor
-    image: kubernetes/git-monitor
-    env:
-    - name: GIT_REPO
-      value: http://github.com/some/repo.git
-    volumeMounts:
-    - mountPath: /data
-      name: www-data
-  volumes:
-  - name: www-data
-    emptyDir: {}
-```
-
-Note that we have also added a volume here.  In this case, the volume is mounted into both containers.  It is marked `readOnly` in the web server's case, since it doesn't need to write to the directory.
-
-Finally, we have also introduced an environment variable to the `git-monitor` container, which allows us to parameterize that container with the particular git repository that we want to track.
-
-
-## What's Next?
-
-Continue on to [Kubernetes 201](/{{page.version}}/docs/user-guide/walkthrough/k8s201) or
-for a complete application see the [guestbook example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook/)
\ No newline at end of file
diff --git a/v1.2/docs/user-guide/walkthrough/pod-nginx-with-label.yaml b/v1.2/docs/user-guide/walkthrough/pod-nginx-with-label.yaml
deleted file mode 100644
index 7053af0be4..0000000000
--- a/v1.2/docs/user-guide/walkthrough/pod-nginx-with-label.yaml
+++ /dev/null
@@ -1,12 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-  labels:
-    app: nginx
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    ports:
-    - containerPort: 80
diff --git a/v1.2/docs/user-guide/walkthrough/pod-nginx.yaml b/v1.2/docs/user-guide/walkthrough/pod-nginx.yaml
deleted file mode 100644
index e65ec6f5b0..0000000000
--- a/v1.2/docs/user-guide/walkthrough/pod-nginx.yaml
+++ /dev/null
@@ -1,10 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: nginx
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    ports:
-    - containerPort: 80
diff --git a/v1.2/docs/user-guide/walkthrough/pod-redis.yaml b/v1.2/docs/user-guide/walkthrough/pod-redis.yaml
deleted file mode 100644
index f000658079..0000000000
--- a/v1.2/docs/user-guide/walkthrough/pod-redis.yaml
+++ /dev/null
@@ -1,14 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: redis
-spec:
-  containers:
-  - name: redis
-    image: redis
-    volumeMounts:
-    - name: redis-persistent-storage
-      mountPath: /data/redis
-  volumes:
-  - name: redis-persistent-storage
-    emptyDir: {}
diff --git a/v1.2/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml b/v1.2/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml
deleted file mode 100644
index c697eba1df..0000000000
--- a/v1.2/docs/user-guide/walkthrough/pod-with-http-healthcheck.yaml
+++ /dev/null
@@ -1,20 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-  name: pod-with-healthcheck
-spec:
-  containers:
-  - name: nginx
-    image: nginx
-    # defines the health checking
-    livenessProbe:
-      # an http probe
-      httpGet:
-        path: /_status/healthz
-        port: 80
-      # length of time to wait for a pod to initialize
-      # after pod startup, before applying health checking
-      initialDelaySeconds: 30
-      timeoutSeconds: 1
-    ports:
-    - containerPort: 80
diff --git a/v1.2/docs/user-guide/walkthrough/podtemplate.json b/v1.2/docs/user-guide/walkthrough/podtemplate.json
deleted file mode 100644
index bd4327414a..0000000000
--- a/v1.2/docs/user-guide/walkthrough/podtemplate.json
+++ /dev/null
@@ -1,22 +0,0 @@
-  {
-    "apiVersion": "v1",
-    "kind": "PodTemplate",
-    "metadata": {
-      "name": "nginx"
-    },
-    "template": {
-      "metadata": {
-        "labels": {
-          "name": "nginx"
-        },
-        "generateName": "nginx-"
-      },
-      "spec": {
-         "containers": [{
-           "name": "nginx",
-           "image": "dockerfile/nginx",
-           "ports": [{"containerPort": 80}]
-         }]
-      }
-    }
-  }
diff --git a/v1.2/docs/user-guide/walkthrough/replication-controller.yaml b/v1.2/docs/user-guide/walkthrough/replication-controller.yaml
deleted file mode 100644
index e0dd6f73dd..0000000000
--- a/v1.2/docs/user-guide/walkthrough/replication-controller.yaml
+++ /dev/null
@@ -1,24 +0,0 @@
-apiVersion: v1
-kind: ReplicationController
-metadata:
-  name: nginx-controller
-spec:
-  replicas: 2
-  # selector identifies the set of Pods that this
-  # replication controller is responsible for managing
-  selector:
-    app: nginx
-  # podTemplate defines the 'cookie cutter' used for creating
-  # new pods when necessary
-  template:
-    metadata:
-      labels:
-        # Important: these labels need to match the selector above
-        # The api server enforces this constraint.
-        app: nginx
-    spec:
-      containers:
-      - name: nginx
-        image: nginx
-        ports:
-        - containerPort: 80
diff --git a/v1.2/docs/user-guide/walkthrough/service.yaml b/v1.2/docs/user-guide/walkthrough/service.yaml
deleted file mode 100644
index f2304d3d7f..0000000000
--- a/v1.2/docs/user-guide/walkthrough/service.yaml
+++ /dev/null
@@ -1,16 +0,0 @@
-apiVersion: v1
-kind: Service
-metadata:
-  name: nginx-service
-spec:
-  ports:
-  - port: 8000 # the port that this service should serve on
-    # the container on each pod to connect to, can be a name
-    # (e.g. 'www') or a number (e.g. 80)
-    targetPort: 80
-    protocol: TCP
-  # just like the selector in the replication controller,
-  # but this time it identifies the set of pods to load balance
-  # traffic to.
-  selector:
-    app: nginx
diff --git a/v1.2/docs/user-guide/working-with-resources.md b/v1.2/docs/user-guide/working-with-resources.md
deleted file mode 100644
index bcd1ae2f7d..0000000000
--- a/v1.2/docs/user-guide/working-with-resources.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
----
-
-*This document is aimed at users who have worked through some of the examples,
-and who want to learn more about using kubectl to manage resources such
-as pods and services.  Users who want to access the REST API directly,
-and developers who want to extend the Kubernetes API should
-refer to the [api conventions](/{{page.version}}/docs/devel/api-conventions) and
-the [api document](/{{page.version}}/docs/api/).*
-
-## Resources are Automatically Modified
-
-When you create a resource such as pod, and then retrieve the created
-resource, a number of the fields of the resource are added.
-You can see this at work in the following example:
-
-```shell
-$ cat > /tmp/original.yaml <<EOF
-apiVersion: v1
-kind: Pod
-metadata:
-  name: foo
-spec:
-  containers:
-    - name: foo
-      image: busybox
-  restartPolicy: Never
-EOF
-$ kubectl create -f /tmp/original.yaml
-pods/original
-$ kubectl get pods/original -o yaml > /tmp/current.yaml
-pods/original
-$ wc -l /tmp/original.yaml /tmp/current.yaml
-      51 /tmp/current.yaml
-       9 /tmp/original.yaml
-      60 total
-```
-
-The resource we posted had only 9 lines, but the one we got back had 51 lines.
-If you `diff -u /tmp/original.yaml /tmp/current.yaml`, you can see the fields added to the pod.
-The system adds fields in several ways:
-
-  - Some fields are added synchronously with creation of the resource and some are set asynchronously.
-    - For example: `metadata.uid` is set synchronously.  (Read more about [metadata](/{{page.version}}/docs/devel/api-conventions/#metadata)).
-    - For example, `status.hostIP` is set only after the pod has been scheduled.  This often happens fast, but you may notice pods which do not have this set yet.  This is called Late Initialization.  (Read mode about [status](/{{page.version}}/docs/devel/api-conventions/#spec-and-status) and [late initialization](/{{page.version}}/docs/devel/api-conventions/#late-initialization) ).
-  - Some fields are set to default values.  Some defaults vary by cluster and some are fixed for the API at a certain version.  (Read more about [defaulting](/{{page.version}}/docs/devel/api-conventions/#defaulting)).
-    - For example, `spec.containers[0].imagePullPolicy` always defaults to `IfNotPresent` in api v1.
-    - For example, `spec.containers[0].resources.limits.cpu` may be defaulted to  `100m` on some clusters, to some other value on others, and not defaulted at all on others.
-    
-The API will generally not modify fields that you have set; it just sets ones which were unspecified.
-
-## <a name="finding_schema_docs"></a>Finding Documentation on Resource Fields
-
-You can browse auto-generated API documentation at the [project website](/{{page.version}}/docs/api/) or on [github](https://releases.k8s.io/{{page.githubbranch}}/docs/api-reference).
\ No newline at end of file
diff --git a/v1.2/docs/whatisk8s.md b/v1.2/docs/whatisk8s.md
deleted file mode 100644
index 17cc03fefc..0000000000
--- a/v1.2/docs/whatisk8s.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
----
-Kubernetes is an open-source platform for automating deployment, scaling, and operations of application containers across clusters of hosts.
-
-With Kubernetes, you are able to quickly and efficiently respond to customer demand:
-
- - Scale your applications on the fly.
- - Seamlessly roll out new features.
- - Optimize use of your hardware by using only the resources you need.
-
-Our goal is to foster an ecosystem of components and tools that relieve the burden of running applications in public and private clouds.
-
-
-## Kubernetes is:
-
-* **lean**: lightweight, simple, accessible
-* **portable**: public, private, hybrid, multi-cloud
-* **extensible**: modular, pluggable, hookable, composable
-* **self-healing**: auto-placement, auto-restart, auto-replication
-
-The Kubernetes project was started by Google in 2014. Kubernetes builds upon a [decade and a half of experience that Google has with running production workloads at scale](https://research.google.com/pubs/pub43438), combined with best-of-breed ideas and practices from the community.
-
-
-## Why containers?
-
-Looking for reasons why you should be using [containers](http://aucouranton.com/2014/06/13/linux-containers-parallels-lxc-openvz-docker-and-more/)?
-
-Here are some key points:
-
-* **Application-centric management**:
-    Raises the level of abstraction from running an OS on virtual hardware to running an application on an OS using logical resources. This provides the simplicity of PaaS with the flexibility of IaaS and enables you to run much more than just [12-factor apps](http://12factor.net/).
-* **Dev and Ops separation of concerns**:
-    Provides separation of build and deployment; therefore, decoupling applications from infrastructure.
-* **Agile application creation and deployment**:
-    Increased ease and efficiency of container image creation compared to VM image use.
-* **Continuous development, integration, and deployment**:
-    Provides for reliable and frequent container image build and deployment with quick and easy rollbacks (due to image immutability).
-* **Loosely coupled, distributed, elastic, liberated [micro-services](http://martinfowler.com/articles/microservices)**:
-    Applications are broken into smaller, independent pieces and can be deployed and managed dynamically -- not a fat monolithic stack running on one big single-purpose machine.
-* **Environmental consistency across development, testing, and production**:
-    Runs the same on a laptop as it does in the cloud.
-* **Cloud and OS distribution portability**:
-    Runs on Ubuntu, RHEL, on-prem, or Google Container Engine, which makes sense for all environments: build, test, and production.
-* **Resource isolation**:
-    Predictable application performance.
-* **Resource utilization**:
-    High efficiency and density.
-    
-
-## What can Kubernetes do?
-
-Kubernetes can schedule and run application containers on clusters of physical or virtual machines.
-
-It can also do much more than that.
-
-Kubernetes satisfies a number of common needs of applications running in production, such as:
-
-* [co-locating helper processes](/{{page.version}}/docs/user-guide/pods),
-* [mounting storage systems](/{{page.version}}/docs/user-guide/volumes),
-* [distributing secrets](/{{page.version}}/docs/user-guide/secrets),
-* [application health checking](/{{page.version}}/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks),
-* [replicating application instances](/{{page.version}}/docs/user-guide/replication-controller),
-* [horizontal auto-scaling](/{{page.version}}/docs/user-guide/horizontal-pod-autoscaler),
-* [load balancing](/{{page.version}}/docs/user-guide/services),
-* [rolling updates](/{{page.version}}/docs/user-guide/update-demo/), and
-* [resource monitoring](/{{page.version}}/docs/user-guide/monitoring).
-
-
-## Why and how is Kubernetes a platform?
-
-Even though Kubernetes provides a lot of functionality, there are always new scenarios that would benefit from new features. Ad hoc orchestration that is acceptable initially often requires robust automation at scale. Application-specific workflows can be streamlined to accelerate developer velocity. This is why Kubernetes was also designed to serve as a platform for building an ecosystem of components and tools to make it easier to deploy, scale, and manage applications.
-
-[Labels](/{{page.version}}/docs/user-guide/labels) empower users to organize their resources however they please. [Annotations](/{{page.version}}/docs/user-guide/annotations) enable users to decorate resources with custom information to facilitate their workflows and provide an easy way for management tools to checkpoint state.
-
-Additionally, the [Kubernetes control plane](/{{page.version}}/docs/admin/cluster-components) is built upon the same [APIs](/{{page.version}}/docs/api/) that are available to developers and users. Users can write their own controllers, [schedulers](/{{page.version}}/docs/devel/scheduler), etc., if they choose, with [their own APIs](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/extending-api.md) that can be targeted by a general-purpose [command-line tool](/{{page.version}}/docs/user-guide/kubectl-overview).
-
-This [design](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/principles.md) has enabled a number of other systems to build atop Kubernetes.
-
-## Kubernetes is not:
-
-Kubernetes is not a PaaS (Platform as a Service).
-
-* Kubernetes does not limit the types of applications supported. It does not dictate application frameworks, restrict the set of supported language runtimes, nor cater to only [12-factor applications](http://12factor.net/). Kubernetes aims to support an extremely diverse variety of workloads: if an application can run in a container, it should run great on Kubernetes.
-* Kubernetes is unopinionated in the source-to-image space. It does not build your application. Continuous Integration (CI) workflow is an area where different users and projects have their own requirements and preferences, so we support layering CI workflows on Kubernetes but don't dictate how it should work.
-* On the other hand, a number of PaaS systems run *on* Kubernetes, such as [Openshift](https://github.com/openshift/origin) and [Deis](http://deis.io/). You could also roll your own custom PaaS, integrate with a CI system of your choice, or get along just fine with just Kubernetes: bring your container images and deploy them on Kubernetes.
-* Since Kubernetes operates at the application level rather than at just the hardware level, it provides some generally applicable features common to PaaS offerings, such as deployment, scaling, load balancing, logging, monitoring, etc. However, Kubernetes is not monolithic, and these default solutions are optional and pluggable.
-
-Kubernetes is not a mere "orchestration system"; it eliminates the need for orchestration:
-
-* The technical definition of "orchestration" is execution of a defined workflow: do A, then B, then C. In contrast, Kubernetes is comprised of a set of control processes that continuously drive current state towards the provided desired state. It shouldn't matter how you get from A to C: make it so. This results in a system that is easier to use and more powerful, robust, and resilient.
-
-## What does *Kubernetes* mean? K8s?
-
-The name **Kubernetes** originates from Greek, meaning "helmsman" or "pilot", and is the root of "governor" and ["cybernetic"](http://www.etymonline.com/index.php?term=cybernetics). **K8s** is an abbreviation derived by replacing the 8 letters "ubernete" with 8.
\ No newline at end of file
diff --git a/v1.2/editdocs.md b/v1.2/editdocs.md
deleted file mode 100644
index 16dc84bb43..0000000000
--- a/v1.2/editdocs.md
+++ /dev/null
@@ -1,118 +0,0 @@
----
----
-Welcome! We are very pleased you want to contribute to the docs for Kubernetes.
-
-<!-- BEGIN: Gotta keep this section JS/HTML because it swaps out content dynamically -->
-<p>&nbsp;</p>
-<script language="JavaScript">
-var forwarding=window.location.hash.replace("#","");
-$( document ).ready(function() {
-    if(forwarding) {
-    	$("#generalInstructions").hide();
-    	$("#continueEdit").show();
-    	$("#continueEditButton").text("Edit " + forwarding);
-    	$("#continueEditButton").attr("href", "https://github.com/kubernetes/kubernetes.github.io/edit/master/_includes/masterdocs" + forwarding.replace("{{page.version}}",""))
-    } else {
-        $("#generalInstructions").show();
-    	$("#continueEdit").hide();
-    }
-});
-</script>
-<div id="continueEdit">
-
-<h2>Continue your edit</h2>
-
-<p>Click the below link to edit the page you were just on. When you are done, press "Commit Changes" at the bottom of the screen. This will create a copy of our site on your GitHub account called a "fork." You can make other changes in your fork after it is created, if you want. When you are ready to send us all your changes, go to the index page for your fork and click "New Pull Request" to let us know about it.</p>
-
-<p>Note that you'll be editing the master file, which is not version-specific. This means that you'll be editing the docs for all versions of Kubernetes! If you need to document something that is specific to only *some* versions (or just one verison) of Kubernetes, check for <code>page.version</code>'s value being "v1.1" or "v1.2" with <a href="https://github.com/Shopify/liquid/wiki/Liquid-for-Designers#user-content-if--else">an if/then statement</a>. (This variable is set in <a href="https://github.com/kubernetes/kubernetes.github.io/blob/master/_config.yml">our site's _config.yml file</a>).</p>
-
-<p><a id="continueEditButton" class="button"></a></p>
-
-</div>
-<div id="generalInstructions">
-
-<h2>Edit our site in the cloud</h2>
-
-<p>Click the below button to visit the repo for our site. You can then click the "Fork" button in the upper-right area of the screen to create a copy of our site on your GitHub account called a "fork." Make any changes you want in your fork, and when you are ready to send those changes to us, go to the index page for your fork and click "New Pull Request" to let us know about it.</p>
-
-<p><a class="button" href="https://github.com/kubernetes/kubernetes.github.io/">Browse this site's source code</a></p>
-
-</div>
-<!-- END: Dynamic section -->
-
-## Staging your changes in the cloud
-
-If you want to see your changes staged without having to install anything locally,
-change your fork of our repo to be named:
-
-    YOUR_GITHUB_USERNAME.github.io
-
-Then, visit: [http://YOUR_GITHUB_USERNAME.github.io](http://YOUR_GITHUB_USERNAME.github.io)
-
-You should see a special-to-you version of the site. 
-
-## Editing and staging the site locally
-
-If you have files to upload, or just want to work offline, run the below commands to setup
-your environment for running GitHub pages locally. Then, any edits you make will be viewable
-on a lightweight webserver that runs on your local machine.
-
-First install rvm
-
-```text
-\curl -sSL https://get.rvm.io | bash -s stable
-```
-
-Then load it into your environment
-
-```shell
-source /Users/(USERNAME)/.rvm/scripts/rvm (or whatever is prompted by the installer)
-```
-
-Then install Ruby 2.2 or higher
-
-```shell
-rvm install 2.2
-rvm use 2.2 --default
-```
-
-Verify that this new version is running (optional)
-
-```shell
-which ruby
-ruby -v
-```
-
-Install the GitHub Pages package, which includes Jekyll:
-
-```shell
-gem install github-pages
-```
-
-Clone our site
-
-```shell
-git clone https://github.com/kubernetes/kubernetes.github.io.git
-```
-
-Then, to see it run locally:
-
-```shell
-cd kubernetes.github.io
-jekyll serve
-```
-
-Your copy of the site will then be viewable at: [http://0.0.0.0:4000](http://0.0.0.0:4000)
-(or wherever Ruby tells you).
-
-If you're a bit rusty with git/GitHub, you might wanna read
-[this](http://readwrite.com/2013/10/02/github-for-beginners-part-2) for a refresher.
-
-The above instructions work on Mac and Linux.
-[These instructions ](https://martinbuberl.com/blog/setup-jekyll-on-windows-and-host-it-on-github-pages/)
-might help for Windows users. 
-
-## Thank you!
-
-Kubernetes thrives on community participation and we really appreciate your
-contributions to our site and our documentation!
diff --git a/v1.2/index.md b/v1.2/index.md
deleted file mode 100644
index c09e28df8f..0000000000
--- a/v1.2/index.md
+++ /dev/null
@@ -1,116 +0,0 @@
----
----
-<style>
-h1, h2, h3, h4 {
-  border-bottom: 0px !important;
-}
-.colContainer {
-  padding-top:2px;
-  padding-left: 2px;
-  overflow: auto;
-}
-#samples a {
-  color: #000;
-}
-.col3rd {
-  display: block;
-  width: 250px;
-  float: left;
-  margin-right: 30px;
-  margin-bottom: 30px;
-}
-.col3rd h3, .col2nd h3 {
-  margin-bottom: 0px !important;
-}
-.col3rd .button, .col2nd .button {
-  margin-top: 20px;
-  border-radius: 2px;
-}
-.col3rd p, .col2nd p {
-  margin-left: 2px;
-}
-.col2nd {
-  display: block;
-  width: 400px;
-  float: left;
-  margin-right: 30px;
-  margin-bottom: 30px;
-}
-.shadowbox {
-  display: inline;
-  float: left;
-  text-transform: none;
-  font-weight: bold;
-  text-align: center;
-  text-overflow: ellipsis;
-  white-space: nowrap;
-  overflow: hidden;
-  line-height: 24px;
-  position: relative;
-  display: block;
-  cursor: pointer;
-  box-shadow: 0 2px 2px rgba(0,0,0,.24),0 0 2px rgba(0,0,0,.12);
-  border-radius: 10px;
-  background: #fff;
-  transition: all .3s;
-  padding: 16px;
-  margin: 0 16px 16px 0;
-  text-decoration: none;
-  letter-spacing: .01em;
-}
-.shadowbox img {
-    min-width: 150px;
-    max-width: 150px;
-    max-height: 50px;
-}
-</style>
-<div class="colContainer">
-  <div class="col3rd">
-    <h3>What is Kubernetes?</h3>
-    <p>Kubernetes is an open-source platform for automating deployment, scaling, and operations of application containers across clusters of hosts. Learn more about what this means for your app.</p>
-    <a href="/{{page.version}}/docs/whatisk8s/" class="button">Read the Overview</a>
-  </div>
-  <div class="col3rd">
-    <h3>5-Minute Quickstart</h3>
-    <p>In this quickstart, we’ll be creating a Kubernetes instance on your local machine that uses Docker and stands up a simple “Hello World” app using Node.js. In just 5 minutes you’ll have something that is deployable.</p>
-    <a href="/{{page.version}}/docs/hellonode/" class="button">Get Started</a>
-  </div>
-  <div class="col3rd">
-    <h3>Guided Tutorial</h3>
-    <p>If you’ve mastered the quickstart, a great next step is Kubernetes 101. You will follow a path through the various features of Kubernetes, with code examples along the way, learning all of the core concepts. There's also a <a href="/{{page.version}}/docs/user-guide/walkthrough/k8s201">Kubernetes 201</a>!</p>
-    <a href="/{{page.version}}/docs/user-guide/walkthrough/" class="button">Kubernetes 101</a>
-  </div>
-</div>
-
-## Samples
-
-<div id="samples" class="colContainer">
-<a href="/{{page.version}}/docs/getting-started-guides/meanstack/" class="shadowbox">
-  <img src="/images/docs/meanstack/image_0.png"><br/>MEAN Stack
-</a>
-<a href="https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/guestbook" target="_blank" class="shadowbox">
-  <img src="/images/docs/redis.svg"><br/>Guestbook + Redis
-</a>
-<a href="https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/cassandra" target="_blank" class="shadowbox">
-  <img src="/images/docs/cassandra.svg"><br/>Cloud Native Cassandra
-</a>
-<a href="https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/mysql-wordpress-pd/" target="_blank" class="shadowbox">
-  <img src="/images/docs/wordpress.svg"><br/>WordPress + MySQL
-</a>
-</div>
-
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-
-<div class="colContainer">
-  <div class="col2nd">
-  <h3>Contribute to Our Docs</h3>
-  <p>The docs for Kubernetes are open-source, just like the code for Kubernetes itself. The docs are on GitHub Pages, so you can fork it and it will auto-stage on username.github.io, previewing your changes!</p>
-  <a href="/{{page.version}}/editdocs/" class="button">Write Docs for K8s</a>
-  </div>
-  <div class="col2nd">
-  <h3>Need Help?</h3>
-  <p>Try consulting our <a href="/{{page.version}}/docs/troubleshooting/">troubleshooting guides</a>, or <a href="https://github.com/kubernetes/kubernetes/wiki/User-FAQ">our FAQ</a>. Kubernetes is also supported by a great community of contributors and experts who hang out in <a href="http://slack.kubernetes.io/">our Slack channel</a>, <a href="https://groups.google.com/forum/#!forum/google-containers">our Google Group</a> and <a href="http://stackoverflow.com/questions/tagged/kubernetes">Stackoverflow</a>.</p>
-  <a href="/{{page.version}}/docs/troubleshooting/" class="button">Get Support</a>
-  </div>
-</div>
\ No newline at end of file
diff --git a/v1.2/reference.md b/v1.2/reference.md
deleted file mode 100644
index 8283b2c785..0000000000
--- a/v1.2/reference.md
+++ /dev/null
@@ -1,3 +0,0 @@
----
----
-This is the landing page for the reference section.
\ No newline at end of file
diff --git a/v1.2/samples.md b/v1.2/samples.md
deleted file mode 100644
index f9315d13dc..0000000000
--- a/v1.2/samples.md
+++ /dev/null
@@ -1,3 +0,0 @@
----
----
-This is the landing page for the samples section.
\ No newline at end of file