Setup Kubernetes Components

Add e6data Helm Charts Repository

The Helm chart creates a service account that will be used by the e6data cluster to leverage OIDC (OpenID Connect) authentication and obtain read permissions to access the data buckets. It also creates roles and role bindings in the AKS cluster for the e6data control plane.

These roles and role bindings define the permissions and access levels for the control plane user within the cluster, allowing it to perform specific actions and interact with resources as required by the e6data workspace.

helm repo add e6data https://e6data.github.io/helm-charts/
helm repo update

GitHub - e6x-labs/helm-chartsGitHub

Edit values.yaml

1. Navigate to ./helm-charts/charts/workspace/

2. Open the values.yaml file

3. Replace <E6DATA_USER_ASSIGNED_IDENTITY_CLIENT_ID> with the ClientID of the managed identity created previously.

4. Replace <OBJECT_ID_OF_THE_E6DATA_APP_REGISTRATION> with the ObjectID of the app registration created previously.

5. Replace <WORKSPACE_NAME> with the name of the e6data workspace you will be creating.

6. Replace the <NODE_POOL_NAME>&<NODE_CLASS_NAME> with the name provided in the previous node pool and node class creation steps.

7. Save the edited values.yaml file

cloud:
  type: "AZURE"
  oidc_value: <E6DATA_USER_ASSIGNED_IDENTITY_CLIENT_ID>
  control_plane_user:
    - <OBJECT_ID_OF_THE_E6DATA_APP_REGISTRATION>
karpenter:
  nodepool:
    - "<NODE_POOL_NAME>"
  nodeclass:
    - "<NODE_CLASS_NAME>"

Please make note of the Workspace Name, it will be required when creating the Workspace in the e6data Console:

Run Helm Charts3

helm upgrade -i -f /path/to/your/helm/values.yaml -n <KUBERNETES_NAMESPACE> <WORKSPACE_NAME> --version "2.1.7" e6x-labs/workspace

When the Helm chart finishes running, proceed to the e6data Console to create a Workspace.