Fixed kfctl init commands and Kubeflow version for v0.6.2 (#1114)

* WIP version fixes.

* More fixes to config files and versions.

content/docs/gke/deploy/deploy-cli.md

@@ -73,18 +73,21 @@ Follow these steps to deploy Kubeflow:
     ```bash
     # The following command is optional, to make kfctl binary easier to use.
     export PATH=$PATH:<path to your kfctl file>
-    export ZONE=<your target GCP zone> # where the deployment will be created
 
-    export PROJECT=<your GCP project ID>
-    
     # Set KFAPP to the name of your Kubeflow application. See detailed
     # description in the text below this code snippet.
     # For example,  'kubeflow-test' or 'kfw-test'.
     export KFAPP=<your choice of application directory name>
-    # Run this command for the default installation which uses Cloud IAP:
-    kfctl init ${KFAPP} --project ${PROJECT} --config=https://raw.githubusercontent.com/kubeflow/kubeflow/c54401e/bootstrap/config/kfctl_gcp_iap.0.6.2.yaml -V
-    # Alternatively, run this command if you want to use basic authentication:
-    kfctl init ${KFAPP} --project ${PROJECT} --config=https://raw.githubusercontent.com/kubeflow/kubeflow/c54401e/bootstrap/config/kfctl_gcp_basic_auth.0.6.2.yaml -V --use_basic_auth
+
+    export ZONE=<your target GCP zone> # where the deployment will be created
+    export PROJECT=<your GCP project ID>
+
+    # Run the following commands for the default installation which uses Cloud IAP:
+    export CONFIG="{{% config-uri-gcp-iap %}}"
+    kfctl init ${KFAPP} --project=${PROJECT} --config=${CONFIG} -V
+    # Alternatively, run these commands if you want to use basic authentication:
+    export CONFIG="{{% config-uri-gcp-basic-auth %}}"
+    kfctl init ${KFAPP} --project=${PROJECT} --config=${CONFIG} -V --use_basic_auth
 
     cd ${KFAPP}
     kfctl generate all -V --zone ${ZONE}

content/docs/gke/deploy/monitor-iap-setup.md

@@ -136,14 +136,14 @@ problems:
     For example if you originally ran the following `kfctl init` command:
 
     ```
-    kfctl init myapp --project=myproject --platform=gcp
+    kfctl init myapp --project=myproject --config=myconfig -V
     ```
 
     Then rerun `kfctl init` with a different name that you haven't used
     before:
 
     ```
-    kfctl init myapp-unique --project=myproject --platform=gcp
+    kfctl init myapp-unique --project=myproject --config=myconfig -V
     ```
 
 1. Wait for the load balancer to report the back ends as healthy:

content/docs/gke/private-clusters.md

@@ -257,10 +257,14 @@ export PROJECT_NUMBER=$(gcloud projects describe kubeflow-dev --format='value(pr
 1. Initialize the directory containing your Kubeflow deployment config files
     
     ```bash
-    export PROJECT=<your GCP project>
+    export PROJECT=<your GCP project ID>
     export KFAPP=<your choice of application directory name>
-    # Default uses IAP.
-    kfctl init ${KFAPP} --platform gcp --project ${PROJECT}
+    # Run the following commands for the default installation which uses Cloud IAP:
+    export CONFIG="{{% config-uri-gcp-iap %}}"
+    kfctl init ${KFAPP} --project=${PROJECT} --config=${CONFIG} -V
+    # Alternatively, run these commands if you want to use basic authentication:
+    export CONFIG="{{% config-uri-gcp-basic-auth %}}"
+    kfctl init ${KFAPP} --project=${PROJECT} --config=${CONFIG} -V --use_basic_auth
 
     cd ${KFAPP}
     kfctl generate all -V
@@ -272,10 +276,8 @@ export PROJECT_NUMBER=$(gcloud projects describe kubeflow-dev --format='value(pr
      The value of this variable cannot be greater than 25 characters. It must
      contain just the directory name, not the full path to the directory.
      The content of this directory is described in the next section.
-   * **${PROJECT}** - the _name_ of the GCP project where you want Kubeflow 
+   * **${PROJECT}** - the ID of the GCP project where you want Kubeflow 
      deployed.
-   * When you run `kfctl init` you need to choose to use either IAP or basic 
-     authentication, as described below.
    * `kfctl generate all` attempts to fetch your email address from your 
      credential. If it can't find a valid email address, you need to pass a
      valid email address with flag `--email <your email address>`. This email 

content/docs/other-guides/kustomize.md

@@ -43,21 +43,21 @@ when you run `kfctl init`. For example:
 
 ```
 export KFAPP="<your choice of application directory name>"
-export CONFIG="https://raw.githubusercontent.com/kubeflow/kubeflow/{{% kf-latest-version %}}/bootstrap/config/kfctl_existing_arrikto.yaml"
+export CONFIG="{{% config-uri-existing-arrikto %}}"
 kfctl init ${KFAPP} --config=${CONFIG} -V
 ```
 
 *For details of the above deployment, see the guide to deployment using the 
 [kfctl_existing_arrikto configuration](/docs/started/k8s/kfctl-existing-arrikto/).*
 
-Some deployment processes use a default config file and you don't need to
-add the `--config` argument. For example, the 
+As another example, the 
 Google Cloud Platform (GCP) initialization command looks like this:
 
 ```
-export PROJECT="<your GCP project ID>"
 export KFAPP="<your choice of application directory name>"
-kfctl init ${KFAPP} --platform gcp --project ${PROJECT}
+export PROJECT="<your GCP project ID>"
+export CONFIG="{{% config-uri-gcp-iap %}}"
+kfctl init ${KFAPP} --project=${PROJECT} --config=${CONFIG} -V
 ```
 
 *For details of the above deployment, see the guide to deployment 

content/docs/started/k8s/kfctl-existing-arrikto.md

@@ -168,7 +168,7 @@ Follow these steps to deploy Kubeflow:
 # Add kfctl to PATH, to make the kfctl binary easier to use.
 export PATH=$PATH:"<path to kfctl>"
 export KFAPP="<your choice of application directory name>"
-export CONFIG="https://raw.githubusercontent.com/kubeflow/kubeflow/v0.6-branch/bootstrap/config/kfctl_existing_arrikto.0.6.2.yaml"
+export CONFIG="{{% config-uri-existing-arrikto %}}"
 
 # Specify credentials for the default user.
 export KUBEFLOW_USER_EMAIL="[email protected]"

content/docs/started/k8s/kfctl-k8s-istio.md

@@ -38,8 +38,8 @@ Follow these steps to deploy Kubeflow:
    # Add kfctl to PATH, to make the kfctl binary easier to use.
    export PATH=$PATH:"<path to kfctl>"
    export KFAPP="<your choice of application directory name>"
-   # Installs istio by default. Comment out istio components in the config file to skip istio installation. See https://github.com/kubeflow/kubeflow/pull/3663
-   export CONFIG="https://raw.githubusercontent.com/kubeflow/kubeflow/{{% kf-latest-version %}}/bootstrap/config/kfctl_k8s_istio.yaml"
+   # Installs Istio by default. Comment out Istio components in the config file to skip Istio installation. See https://github.com/kubeflow/kubeflow/pull/3663
+   export CONFIG="{{% config-uri-k8s-istio %}}"
 
    kfctl init ${KFAPP} --config=${CONFIG} -V
    cd ${KFAPP}

layouts/shortcodes/config-uri-existing-arrikto.html

@@ -0,0 +1 @@
+https://raw.githubusercontent.com/kubeflow/kubeflow/v0.6-branch/bootstrap/config/kfctl_existing_arrikto.0.6.2.yaml

layouts/shortcodes/config-uri-gcp-basic-auth.html

@@ -0,0 +1 @@
+https://raw.githubusercontent.com/kubeflow/kubeflow/c54401e/bootstrap/config/kfctl_gcp_basic_auth.0.6.2.yaml

layouts/shortcodes/config-uri-gcp-iap.html

@@ -0,0 +1 @@
+https://raw.githubusercontent.com/kubeflow/kubeflow/c54401e/bootstrap/config/kfctl_gcp_iap.0.6.2.yaml

layouts/shortcodes/config-uri-k8s-istio.html

@@ -0,0 +1 @@
+https://raw.githubusercontent.com/kubeflow/kubeflow/v0.6-branch/bootstrap/config/kfctl_k8s_istio.0.6.2.yaml

layouts/shortcodes/kf-latest-version.html

@@ -1 +1 @@
-v0.6.1
+v0.6.2