From f3d9c3a0cd4fa422c53337e728888fa29af7463a Mon Sep 17 00:00:00 2001 From: Amy Date: Mon, 5 Aug 2019 17:43:54 -0700 Subject: [PATCH] typo fix (#1027) --- content/docs/gke/deploy/deploy-cli.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/gke/deploy/deploy-cli.md b/content/docs/gke/deploy/deploy-cli.md index 8a55a82f90..b915bc520b 100644 --- a/content/docs/gke/deploy/deploy-cli.md +++ b/content/docs/gke/deploy/deploy-cli.md @@ -110,7 +110,7 @@ Follow these steps to deploy Kubeflow: running `kfctl apply` you should notice two new [deployments](https://console.cloud.google.com/dm/deployments): * **{KFAPP}-storage**: This deployment has persistent volumes for your pipelines. - * **{KFAPP}**: This deployment has all the components of Kubeflow, including a [GKE cluster](https://console.cloud.google.com/kubernetes/list?project=aju-vtests2) named **${KFAPP}** with Kubeflow installed. + * **{KFAPP}**: This deployment has all the components of Kubeflow, including a [GKE cluster](https://console.cloud.google.com/kubernetes/list) named **${KFAPP}** with Kubeflow installed. 1. Once the deployment finishes, check the resources installed in the namespace `kubeflow` in your new cluster. To do this from the command line, first set your `kubectl` credentials to point to the new cluster: