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
2017-07-28 08:23:11 -07:00
parent 130b72927c
commit 2e257d9707
158 changed files with 624 additions and 1011 deletions
@@ -1,8 +1,5 @@
 ---
 title: Installing Addons
-redirect_from:
- "/docs/admin/addons/"
- "/docs/admin/addons.html"
 ---

 ## Overview
@@ -3,11 +3,6 @@ assignees:
 - davidopp
 - lavalamp
 title: Cluster Administration Overview
-redirect_from:
- "/docs/admin/"
- "/docs/admin/index.html"
- "/docs/tasks/administer-cluster/overview/"
- "/docs/tasks/administer-cluster/overview.html"
 ---

 {% capture overview %}
@@ -1,12 +1,5 @@
 ---
 title: Federation
-redirect_from:
- "/docs/user-guide/federation/"
- "/docs/user-guide/federation/index.html"
- "/docs/concepts/cluster-administration/multiple-clusters/"
- "/docs/concepts/cluster-administration/multiple-clusters.html"
- "/docs/admin/multi-cluster/"
- "/docs/admin/multi-cluster.html"
 ---

 {% capture overview %}
@@ -48,7 +41,7 @@ why you might want multiple clusters are:
 * [Hybrid cloud](###hybrid-cloud-capabilities): You can have multiple clusters on different cloud providers or
  on-premises data centers.

-### Caveats 
+### Caveats

 While there are a lot of attractive use cases for federation, there are also
 some caveats:
@@ -2,9 +2,6 @@
 assignees:
 - mikedanese
 title: Configuring kubelet Garbage Collection
-redirect_from:
- "/docs/admin/garbage-collection/"
- "/docs/admin/garbage-collection.html"
 ---

 * TOC
@@ -3,12 +3,6 @@ assignees:
 - crassirostris
 - piosz
 title: Logging Architecture
-redirect_from:
- "/docs/concepts/clusters/logging/"
- "/docs/concepts/clusters/logging.html"
-redirect_from:
- "/docs/user-guide/logging/overview/"
- "/docs/user-guide/logging/overview.html"
 ---

 Application and systems logs can help you understand what is happening inside your cluster. The logs are particularly useful for debugging problems and monitoring cluster activity. Most modern applications have some kind of logging mechanism; as such, most container engines are likewise designed to support some kind of logging. The easiest and most embraced logging method for containerized applications is to write to the standard output and standard error streams.
@@ -4,9 +4,6 @@ assignees:
 - janetkuo
 - mikedanese
 title: Managing Resources
-redirect_from:
- "/docs/user-guide/managing-deployments/"
- "/docs/user-guide/managing-deployments.html"
 ---

 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).
@@ -4,9 +4,6 @@ assignees:
 - freehan
 - thockin
 title: Network Plugins
-redirect_from:
- "/docs/admin/network-plugins/"
- "/docs/admin/network-plugins.html"
 ---

 * TOC
@@ -2,9 +2,6 @@
 assignees:
 - thockin
 title: Cluster Networking
-redirect_from:
- "/docs/admin/networking/"
- "/docs/admin/networking.html"
 ---

 Kubernetes approaches networking somewhat differently than Docker does by
@@ -85,7 +82,7 @@ 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 
+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
@@ -217,9 +214,9 @@ Calico can also be run in policy enforcement mode in conjunction with other netw

 ### Weave Net from Weaveworks

-[Weave Net](https://www.weave.works/products/weave-net/) is a 
-resilient and simple to use network for Kubernetes and its hosted applications.  
-Weave Net runs as a [CNI plug-in](https://www.weave.works/docs/net/latest/cni-plugin/)  
+[Weave Net](https://www.weave.works/products/weave-net/) is a
+resilient and simple to use network for Kubernetes and its hosted applications.
+Weave Net runs as a [CNI plug-in](https://www.weave.works/docs/net/latest/cni-plugin/)
 or stand-alone.  In either version, it doesn't require any configuration or extra code
 to run, and in both cases, the network provides one IP address per pod - as is standard for Kubernetes.

@@ -1,8 +1,5 @@
 ---
 title: Proxies in Kubernetes
-redirect_from:
- "/docs/user-guide/accessing-the-cluster/"
- "/docs/user-guide/accessing-the-cluster.html"
 ---

 {% capture overview %}
@@ -2,9 +2,6 @@
 assignees:
 - sttts
 title: Using Sysctls in a Kubernetes Cluster
-redirect_from:
- "/docs/admin/sysctls/"
- "/docs/admin/sysctls.html"
 ---

 * TOC