You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/docs/gke/deploy/deploy-cli.md
+16-6
Original file line number
Diff line number
Diff line change
@@ -95,6 +95,8 @@ Follow these steps to deploy Kubeflow:
95
95
The content of this directory is described in the next section.
96
96
* **${PROJECT}** - the project ID of the GCP project where you want Kubeflow
97
97
deployed.
98
+
* **${ZONE}** - You can see a list of zones [here](https://cloud.google.com/compute/docs/regions-zones/#available).
99
+
If you plan to use accelerators, make sure to pick a zone that supports the type you want.
98
100
* When you run `kfctl init` you need to choose to use either IAP or basic
99
101
authentication, as described below.
100
102
* `kfctl generate all` attempts to fetch your email address from your
@@ -103,17 +105,25 @@ Follow these steps to deploy Kubeflow:
103
105
address becomes an administrator in the configuration of your Kubeflow
104
106
deployment.
105
107
106
-
1. Check the resources deployed in namespace `kubeflow`:
108
+
109
+
1. The deployment process creates a separate deployment for your data storage. After
110
+
running `kfctl apply` you should notice two new [deployments](https://console.cloud.google.com/dm/deployments):
111
+
* **{KFAPP}-storage**: This deployment has persistent volumes for your
112
+
pipelines.
113
+
* **{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.
114
+
115
+
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:
0 commit comments