Using unmanaged GKE clusters¶
To create a Google Kubernetes Engine (GKE) cluster, follow the Google Cloud Platform (GCP) documentation on creating a GKE cluster. We recommend that you allocate at least 16GB of memory for each cluster node. More memory may be required if you plan on running very large in-memory recipes.
You’ll be able to configure the memory allocation for each container and per-namespace in Dataiku DSS using multiple containerized execution configurations.
Follow the GCP documentation to ensure the following on your local machine (where DSS is installed):
gcloudcommand has the appropriate permission and scopes to push to the Google Container Registry (GCR) service.
kubectlcommand is installed and can interact with the cluster. This can be achieved by running the
gcloud container clusters get-credentials your-gke-cluster-namecommand.
dockercommand is installed, can build images and push them to GCR. The latter can be enabled by running the
gcloud auth configure-dockercommand.
Go to Administration > Settings > Containerized execution, and add a new execution configuration of type “Kubernetes”.
In GCP, there is only a single shared image repository URL,
gcr.io. Access control is based on image names. Therefore the repository URL to use is
Finish by clicking Push base images.
You’re now ready to run recipes and ML models in GKE.
GCP provides GPU-enabled instances with NVidia GPUs. Using GPUs for containerized execution requires the following steps.
The base image that is built by default (see setup) does not have CUDA support and cannot use NVidia GPUs.
You need to build a CUDA-enabled base image. To enable CUDA add the
--with-cuda option to the command line:
./bin/dssadmin build-base-image --type container-exec --with-cuda
We recommend that you give this image a specific tag using the
--tag option and keep the default base image “pristine”. We also recommend that you add the DSS version number in the image tag.
./bin/dssadmin build-base-image --type container-exec --with-cuda --tag dataiku-container-exec-base-cuda:X.Y.Z
where X.Y.Z is your DSS version number
This image contains CUDA 10.0 and CuDNN 7.6. You can use
--cuda-version X.Yto specify another DSS-provided version (9.0, 10.0, 10.1, 10.2, 11.0 and 11.2 are available). If you require other CUDA versions, you would have to create a custom image.
Remember that depending on which CUDA version you build the base image (by default 10.0) you will need to use the corresponding tensorflow version.
After each upgrade of DSS, you must rebuild all base images and update code envs.
Thereafter, create a new container configuration dedicated to running GPU workloads. If you specified a tag for the base image, report it in the “Base image tag” field.
Follow the GCP documentation on how to create a GKE cluster with GPU accelerators. You can also create a GPU-enabled node pool in an existing cluster.
Be sure to run the “DaemonSet” installation procedure, which needs several minutes to complete.
For your containerized execution task to run on nodes with GPUs, and for GKE to configure the CUDA driver on your containers, the corresponding pods must be created with a custom limit (in Kubernetes parlance). This indicates that you need a specific type of resource (standard resource types are CPU and memory).
You must configure this limit in the containerized execution configuration. To do this:
In the “Custom limits” section, add a new entry with key
1(to request 1 GPU).
Add the new entry and save your settings.