Deploy Okera on AKS¶

This document This document prepares you to install Okera on an AKS cluster.

Prerequisites¶

A functional AKS cluster that adheres to the Okera prerequisites.
A Linux node that can execute kubectl commands against the AKS cluster - we will call this the deployer node.

Verify AKS Access¶

On the deployer node, you can verify you have AKS access by running:

$ kubectl get nodes -owide
NAME                       STATUS   ROLES   AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
aks-agentpool-35993971-0   Ready    agent   13d   v1.13.9   10.240.0.35   <none>        Ubuntu 16.04.6 LTS   4.15.0-1052-azure   docker://3.0.6
aks-agentpool-35993971-1   Ready    agent   13d   v1.13.9   10.240.0.4    <none>        Ubuntu 16.04.6 LTS   4.15.0-1052-azure   docker://3.0.6
aks-agentpool-35993971-2   Ready    agent   13d   v1.13.9   10.240.0.66   <none>        Ubuntu 16.04.6 LTS   4.15.0-1052-azure   docker://3.0.6

You should see all the nodes that you have in your AKS cluster listed.

Deploy and Configure Okera Using Helm Charts¶

See Deploy Okera Using Helm Charts for information about deploying and updating Okera using Helm charts.

Configuring Azure Credentials¶

By default, your Okera cluster will not be able to access any ADLS resources as it does not have your Azure AD Application credentials.

To add these credentials, add the following configuration values to the common.configs section of your configuration file:

ADLS_CLIENT_ID: <ADLS Client ID>
ADLS_CLIENT_PASSWORD: <ADLS Client Password>
ADLS_REFRESH_URL: <ADLS Refresh URL>
ADLS_TENANT_ID: <ADLS Tenant ID>

Note: These are the values of the Azure AD Application you created in the Prerequisites section.