Changes for move to Netlify (#4464)

* disable jekyll-redirect-from gem

* add _redirects file

* disable 404 redirect script

* add 301 redirect to test

* retain _redirects file

* Convert redirect_from's to _redirect file. (#4409)

* Remove redirect_from's. (#4424)

* Add 301's to _redirects. (#4427)

* add whitespace before 301

* move redirects in /js/redirects/js to _redirects

* add disabled option for cn redirect

* convert include to array in _config.yml

* enable redirects.js script for legacy support

docs/tasks/administer-federation/cluster.md

@@ -1,8 +1,5 @@
 ---
 title: Federated Cluster
-redirect_from:
-- "/docs/user-guide/federation/cluster/"
-- "/docs/user-guide/federation/cluster.html"
 ---
 
 {% capture overview %}

docs/tasks/administer-federation/configmap.md

@@ -1,8 +1,5 @@
 ---
 title: Federated ConfigMap
-redirect_from:
-- "/docs/user-guide/federation/configmap/"
-- "/docs/user-guide/federation/configmap.html"
 ---
 
 {% capture overview %}
@@ -75,7 +72,7 @@ the federation apiserver instead of sending it to a specific Kubernetes cluster.
 For example, you can do that using kubectl by running:
 
 ```shell
-kubectl --context=federation-cluster delete configmap 
+kubectl --context=federation-cluster delete configmap
 ```
 
 Note that at this point, deleting a Federated ConfigMap will not delete the

docs/tasks/administer-federation/daemonset.md

@@ -1,8 +1,5 @@
 ---
 title: Federated DaemonSet
-redirect_from:
-- "/docs/user-guide/federation/daemonsets/"
-- "/docs/user-guide/federation/daemonsets.html"
 ---
 
 {% capture overview %}
@@ -43,7 +40,7 @@ request to the Federation apiserver instead of sending it to a Kubernetes
 cluster.
 
 Once a Federated Daemonset is created, the federation control plane will create
-a matching DaemonSet in all underlying Kubernetes clusters. 
+a matching DaemonSet in all underlying Kubernetes clusters.
 You can verify this by checking each of the underlying clusters, for example:
 
 ``` shell

docs/tasks/administer-federation/deployment.md

@@ -1,8 +1,5 @@
 ---
 title: Federated Deployment
-redirect_from:
-- "/docs/user-guide/federation/deployment/"
-- "/docs/user-guide/federation/deployment.html"
 ---
 
 {% capture overview %}
@@ -14,8 +11,8 @@ Deployment](/docs/concepts/workloads/controllers/deployment/) and provide the sa
 Creating them in the federation control plane ensures that the desired number of
 replicas exist across the registered clusters.
 
-**As of Kubernetes version 1.5, Federated Deployment is an Alpha feature. The core 
-functionality of Deployment is present, but some features 
+**As of Kubernetes version 1.5, Federated Deployment is an Alpha feature. The core
+functionality of Deployment is present, but some features
 (such as full rollout compatibility) are still in development.**
 {% endcapture %}
 
@@ -60,7 +57,7 @@ These Deployments in underlying clusters will match the federation Deployment
 _except_ in the number of replicas and revision-related annotations.
 Federation control plane ensures that the
 sum of replicas in each cluster combined matches the desired number of replicas in the
-Federated Deployment. 
+Federated Deployment.
 
 ### Spreading Replicas in Underlying Clusters
 
@@ -81,7 +78,7 @@ Deployment; however, for a Federated Deployment, you must send the request to
 the federation apiserver instead of sending it to a specific Kubernetes cluster.
 The federation control plane ensures that whenever the Federated Deployment is
 updated, it updates the corresponding Deployments in all underlying clusters to
-match it. So if the rolling update strategy was chosen then the underlying 
+match it. So if the rolling update strategy was chosen then the underlying
 cluster will do the rolling update independently and `maxSurge` and `maxUnavailable`
 will apply only to individual clusters. This behavior may change in the future.
 

docs/tasks/administer-federation/events.md

@@ -1,8 +1,5 @@
 ---
 title: Federated Events
-redirect_from:
-- "/docs/user-guide/federation/events/"
-- "/docs/user-guide/federation/events.html"
 ---
 
 This guide explains how to use events in federation control plane to help in debugging.

docs/tasks/administer-federation/ingress.md

@@ -1,9 +1,7 @@
 ---
 title: Federated Ingress
-redirect_from:
-- "/docs/user-guide/federation/federated-ingress/"
-- "/docs/user-guide/federation/federated-ingress.html"
 ---
+
 {% capture overview %}
 This page explains how to use Kubernetes Federated Ingress to deploy
 a common HTTP(S) virtual IP load balancer across a federated service running in
@@ -25,7 +23,7 @@ Federated Ingress is released as an alpha feature, and supports Google Cloud Pla
 GCE and hybrid scenarios involving both) in Kubernetes v1.4.  Work is under way to support other cloud
 providers such as AWS, and other hybrid cloud scenarios (e.g. services
 spanning private on-premise as well as public cloud Kubernetes
-clusters).  
+clusters).
 
 You create Federated Ingresses in much that same way as traditional
 [Kubernetes Ingresses](/docs/concepts/services-networking/ingress/): by making an API
@@ -151,7 +149,7 @@ may take up to a few minutes).
 the network traffic directed to this ingress (that is, 'Service
 Endpoints' behind the service backing the Ingress), so the Federated Ingress does not yet consider these to
 be healthy shards and will not direct traffic to any of these clusters.
-*  The federation control system 
+*  The federation control system
 automatically reconfigures the load balancer controllers in all of the
 clusters in your federation to make them consistent, and allows
 them to share global load balancers.  But this reconfiguration can
@@ -202,7 +200,7 @@ nginx     10.63.250.98   104.199.136.89   80/TCP    9m
 Federations of Kubernetes Clusters can include clusters running in
 different cloud providers (for example, Google Cloud, AWS), and on-premises
 (for example, on OpenStack).  However, in Kubernetes v1.4, Federated Ingress is only
-supported across Google Cloud clusters.  
+supported across Google Cloud clusters.
 
 ## Discovering a federated ingress
 
@@ -301,11 +299,11 @@ Check that:
 
 {% capture whatsnext %}
 *  If you need assistance, use one of the [support channels](/docs/tasks/debug-application-cluster/troubleshooting/) to seek assistance.
- *  For details about use cases that motivated this work, see 
+ *  For details about use cases that motivated this work, see
  [Federation proposal](https://git.k8s.io/community/contributors/design-proposals/federation.md).
 {% endcapture %}
 {% include templates/task.md %}
- 
- 
- 
- 
+
+
+
+

docs/tasks/administer-federation/namespaces.md

@@ -1,8 +1,5 @@
 ---
 title: Federated Namespaces
-redirect_from:
-- "/docs/user-guide/federation/namespaces/"
-- "/docs/user-guide/federation/namespaces.html"
 ---
 
 {% capture overview %}

docs/tasks/administer-federation/replicaset.md

@@ -1,8 +1,5 @@
 ---
 title: Federated ReplicaSets
-redirect_from:
-- "/docs/user-guide/federation/replicasets/"
-- "/docs/user-guide/federation/replicasets.html"
 ---
 
 {% capture overview %}

docs/tasks/administer-federation/secret.md

@@ -1,8 +1,5 @@
 ---
 title: Federated Secrets
-redirect_from:
-- "/docs/user-guide/federation/secrets/"
-- "/docs/user-guide/federation/secrets.html"
 ---
 
 This guide explains how to use secrets in Federation control plane.
@@ -81,7 +78,7 @@ the federation apiserver instead of sending it to a specific Kubernetes cluster.
 For example, you can do that using kubectl by running:
 
 ```shell
-kubectl --context=federation-cluster delete secret mysecret 
+kubectl --context=federation-cluster delete secret mysecret
 ```
 
 Note that at this point, deleting a federated secret will not delete the