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/calico-network-policy.md

@@ -2,11 +2,6 @@
 assignees:
 - caseydavenport
 title: Use Calico for NetworkPolicy
-redirect_from:
-- "/docs/getting-started-guides/network-policy/calico/"
-- "/docs/getting-started-guides/network-policy/calico.html"
-- "/docs/tasks/configure-pod-container/calico-network-policy/"
-- "/docs/tasks/configure-pod-container/calico-network-policy.html"
 ---
 
 {% capture overview %}
@@ -14,7 +9,7 @@ This page shows how to use Calico for NetworkPolicy.
 {% endcapture %}
 
 {% capture prerequisites %}
-* Install Calico for Kubernetes. 
+* Install Calico for Kubernetes.
 {% endcapture %}
 
 {% capture steps %}
@@ -34,7 +29,7 @@ See the [Calico documentation](http://docs.projectcalico.org/) for more options
 {% capture discussion %}
 ##  Understanding Calico components
 
-Deploying a cluster with Calico adds Pods that support Kubernetes NetworkPolicy.  These Pods run in the `kube-system` Namespace. 
+Deploying a cluster with Calico adds Pods that support Kubernetes NetworkPolicy.  These Pods run in the `kube-system` Namespace.
 
 To see this list of Pods run: