Remove AWS Kops as a docummented option (#3642)

* Remomve AWS Kops as a docummented option

This doesn't mean you can't get AWS Kops to deploy Istio, just that
nobody cares to maintain the documentation.  If in the future someone
wishes to maintain the documentation, we can consider adding this page
back in.  I would suggest however a page on any EKS specific requirements
needed for Istio as this will be the more likely path folks take to run
Istio.

* Remove link to AWS

content/docs/setup/kubernetes/install/kubernetes/index.md

@@ -25,7 +25,6 @@ This permits customization of Istio to operator specific requirements.
 1. [Kubernetes platform setup](/docs/setup/kubernetes/prepare/platform-setup/):
 
     * [Alibaba Cloud](/docs/setup/kubernetes/prepare/platform-setup/alicloud/)
-    * [Amazon Web Services (AWS) with Kops](/docs/setup/kubernetes/prepare/platform-setup/aws/)
     * [Azure](/docs/setup/kubernetes/prepare/platform-setup/azure/)
     * [Docker For Desktop](/docs/setup/kubernetes/prepare/platform-setup/docker/)
     * [Google Container Engine (GKE)](/docs/setup/kubernetes/prepare/platform-setup/gke/)

content/docs/setup/kubernetes/prepare/platform-setup/aws/index.md

@@ -1,88 +0,0 @@
----
-title: Amazon Web Services
-description: Instructions to setup an AWS cluster with Kops cluster for Istio.
-weight: 6
-skip_seealso: true
-aliases:
-    - /docs/setup/kubernetes/prepare/platform-setup/aws
-keywords: [platform-setup,aws]
----
-
-Follow these instructions to prepare an AWS cluster with Kops for Istio.
-
-When you install a new cluster with Kubernetes version 1.9, the prerequisite to
-enable `admissionregistration.k8s.io/v1beta1` is covered.
-
-Nevertheless, you must update the list of admission controllers.
-
-1. Open the configuration file:
-
-    {{< text bash >}}
-    $ kops edit cluster $YOURCLUSTER
-    {{< /text >}}
-
-1. Add the following in the configuration file:
-
-    {{< text yaml >}}
-    kubeAPIServer:
-        admissionControl:
-        - NamespaceLifecycle
-        - LimitRanger
-        - ServiceAccount
-        - PersistentVolumeLabel
-        - DefaultStorageClass
-        - DefaultTolerationSeconds
-        - MutatingAdmissionWebhook
-        - ValidatingAdmissionWebhook
-        - ResourceQuota
-        - NodeRestriction
-        - Priority
-    {{< /text >}}
-
-1. Perform the update:
-
-    {{< text bash >}}
-    $ kops update cluster
-    $ kops update cluster --yes
-    {{< /text >}}
-
-1. Launch the rolling update:
-
-    {{< text bash >}}
-    $ kops rolling-update cluster
-    $ kops rolling-update cluster --yes
-    {{< /text >}}
-
-1. Validate the update with the `kubectl` client on the `kube-api` pod, you
-   should see new admission controller:
-
-    {{< text bash >}}
-    $ for i in `kubectl \
-      get pods -n kube-system | grep api | awk '{print $1}'` ; \
-      do  kubectl describe pods -nkube-system \
-      $i | grep "/usr/local/bin/kube-apiserver"  ; done
-    {{< /text >}}
-
-1. Review the output:
-
-    Kubernetes up to 1.9:
-
-    {{< text plain >}}
-    [...]
-    --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,
-    PersistentVolumeLabel,DefaultStorageClass,DefaultTolerationSeconds,
-    MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,
-    NodeRestriction,Priority
-    [...]
-    {{< /text >}}
-
-    Kubernetes 1.10+:
-
-    {{< text plain >}}
-    [...]
-    --enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,
-    PersistentVolumeLabel,DefaultStorageClass,DefaultTolerationSeconds,
-    MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,
-    NodeRestriction,Priority
-    [...]
-    {{< /text >}}