update docs to refer v2.0.1 (#1675)

Author: kishorj

docs/guide/controller/installation.md

@@ -57,9 +57,9 @@
     - For Kubernetes <1.16: `kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.2/cert-manager-legacy.yaml`
 
     ### Download and apply the yaml spec
-    - https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/main/docs/install/v2_0_0_full.yaml
+    - https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/main/docs/install/v2_0_1_full.yaml
     - Edit the saved yaml file, go to the Deployment spec, and set the controller --cluster-name arg value to your EKS cluster name
-    - Apply the yaml file kubectl apply -f install_v2_0_0.yaml
+    - Apply the yaml file kubectl apply -f install_v2_0_1.yaml
 
     !!!note ""
         If you use IAM roles for service accounts, we recommend that you delete the ServiceAccount from the yaml spec. Doing so will preserve the eksctl created iamserviceaccount if you delete the installation.

docs/guide/upgrade/migrate_v1_v2.md

@@ -61,7 +61,7 @@ foo@bar:~$ kubectl describe deployment  -n kube-system  alb-ingress-controller |
         Existing Ingress resources do not need to be deleted.
 
 3. Install new AWSLoadBalancerController
-    1. Install AWSLoadBalancerController(v2.0.0) by following the [installation instructions](../controller/installation.md)
+    1. Install AWSLoadBalancerController(v2.0.1) by following the [installation instructions](../controller/installation.md)
     2. Grant [additional IAM policy](../../install/iam_policy_v1_to_v2_additional.json) needed for migration to the controller.
 
 4. Verify all Ingresses works as expected.