Managed Kubernetes clusters

In addition to leveraging existing (unmanaged) clusters, DSS can automatically start, stop and manage multiple clusters that run on the major cloud providers.

DSS provides managed Kubernetes capabilities on:

  • Amazon Web Services through EKS
  • Azure through AKS
  • Google Cloud Platform through GKE

Creating clusters

To create managed clusters, you must first install the DSS plugin corresponding to your cloud provider (EKS, AKS, or GKE). Then follow these steps:

  • Go to Administration > Clusters
  • Click Create Cluster, and for “Type”, select the appropriate cluster type
  • Fill in the required parameter
  • Click Start/Attach

Using managed clusters

Each project defines whether its recipes, notebooks, … run against unmanaged clusters or against one of the managed clusters.

Note that you do not need to use per-cluster container runtime configurations, or per-cluster Spark configurations (for Managed Spark on K8S). DSS automatically uses the requested cluster and the limits defined in the container runtime configuration.

Use a specific or dynamic cluster for scenarios

A common use case for clusters is to run one or multiple scenarios. You can use either:

  • a specific named cluster — one that is already defined in the DSS settings, but that is not the default cluster for the project
  • or a dynamic cluster — one that is created for the scenario and shut down after the end of the scenario (for fully elastic approaches).

Use a specific static cluster

In this case, you can use the variables expansion mechanism of DSS.

To denote the contextual cluster to use at the project level, use the syntax ${variable_name}, instead of the cluster identifier. At runtime, DSS will use the cluster denoted by the variable_name variable. Your scenario will then use a scenario-scoped variable to define the cluster to use for the scenario.

For example, if you want to use the cluster regular1 for the design of the project and all activities not related to the scenario, and use the fast2 cluster for a scenario, then set up your project as follows:

  • Cluster: ${clusterForScenario}
  • Default cluster: regular1

With this setup, when the clusterForScenario variable is not defined (which will be the case outside of the scenario), DSS will fall back to regular1.

In your scenario, add an initial step “Define scenario variables”, and use the following JSON definition:

{
        "clusterForScenario" : "fast2"
}

The steps of the scenario will execute on the fast2 cluster.

Use a dynamic cluster

In the case of the dynamic cluster, the idea is to create a dynamic cluster, then place the identifier of the dynamically-created cluster into a variable, and then use the variables expansion mechanism described above.

For example, if you want to use the cluster regular1 for the design of the project and all activities not related to the scenario, and use a dynamically-created cluster for a scenario, then set up your project as follows:

  • Cluster: ${clusterForScenario}
  • Default cluster: regular1

With this setup, when the clusterForScenario variable is not defined (which will be the case outside of the scenario), DSS will fall back to regular1

In your scenario, add an initial step “Setup cluster”:

  • Select the cluster type that you want to create (depending on the plugin you are using)
  • Fill in the configuration form (depending on the plugin you are using)
  • Set clusterForScenario as the “Target variable”

When the step (Setup cluster) runs, DSS creates the cluster and sets the “id” of the newly created cluster in the clusterForScenario variable. Given the project configuration, the steps of the scenario will automatically execute on the dynamically-created cluster.

At the end of the scenario (regardless of whether the scenario succeeded or failed), DSS automatically stops the dynamic cluster. Note that you can override this behavior in the scenario settings.

Warning

If DSS unexpectedly stops while the scenario is running, the cluster resources will keep running on your cloud provider. We recommend that you set up monitoring for cloud resources created by DSS.

Automate start and stop of clusters

DSS has scenario steps available for starting and stopping clusters. This feature is useful, for instance, to automatically start a cluster in the morning (so that it can be used during the day time), and then automatically shut down the cluster at night, to save on cloud consumption.

Permissions

Each cluster has an owner and groups that are granted access levels. These access levels are:

  • Use cluster: to select the cluster and use it in a project
  • Operate cluster: to modify cluster settings
  • Manage cluster users: to manage the permissions of the cluster

In addition, each group can be granted global permissions to:

  • Create clusters and manage them
  • Manage all clusters — including clusters for which they have not explicitly been granted access