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-cluster/highly-available-master.md

@@ -2,9 +2,6 @@
 assignees:
 - jszczepkowski
 title: Set up High-Availability Kubernetes Masters
-redirect_from:
-- "/docs/admin/ha-master-gce/"
-- "/docs/admin/ha-master-gce.html"
 ---
 
 * TOC
@@ -65,7 +62,7 @@ You can remove a master replica from an HA cluster by using a `kube-down` script
 * `KUBE_DELETE_NODES=false` - to restrain deletion of kubelets.
 
 * `KUBE_GCE_ZONE=zone` - the zone from where master replica will be removed.
- 
+
 * `KUBE_REPLICA_NAME=replica_name` - (optional) the name of master replica to remove.
 If empty: any replica from the given zone will be removed.
 
@@ -105,7 +102,7 @@ A two-replica cluster is thus inferior, in terms of HA, to a single replica clus
 
 * When you add a master replica, cluster state (etcd) is copied to a new instance.
 If the cluster is large, it may take a long time to duplicate its state.
-This operation may be sped up by migrating etcd data directory, as described [here](https://coreos.com/etcd/docs/latest/admin_guide.html#member-migration) 
+This operation may be sped up by migrating etcd data directory, as described [here](https://coreos.com/etcd/docs/latest/admin_guide.html#member-migration)
 (we are considering adding support for etcd data dir migration in future).
 
 ## Implementation notes