Using Microsoft Azure Kubernetes Service#

Microsoft Azure, and specifically the Microsoft Azure Kubernetes Service (AKS), is certified to work with SEP.

Online and offline deployments are supported.

AKS-specific tips can be found in this document.

You can also purchase the Azure Marketplace version of SEP.

Azure Storage account key to access Azure Blob#

You can provide an Azure Blob Storage account key for your Presto cluster as a Kubernetes secret. The secret name can be configured using the hive.azureWasbSecretName property in the Presto resource:

hive:
  azureWasbSecretName: azure-wastarburst-name

Such a secret should contain two files

  • AZURE_WASB_STORAGE_ACCOUNT

  • AZURE_WASB_ACCESS_KEY

which contain the Azure Storage account name and key.

Azure Storage account key to access ADLS Gen 2#

You can provide an Azure ADLS Gen 2 Storage account key for your Presto cluster as a Kubernetes secret. The secret name can be configured using the hive.azureAbfsSecretName property in the Presto resource:

hive:
  azureAbfsSecretName: azure-secret-namme

Such a secret should contain two files

  • AZURE_ABFS_STORAGE_ACCOUNT

  • AZURE_ABFS_ACCESS_KEY

which contain the Azure Storage account name and key.

Azure credentials to access ADLS Gen 1#

You can provide Azure credentials for ADLS Gen 1 as a Kubernetes secret. The secret name can be configured using the hive.azureAdlSecretName property in the Presto resource:

hive:
  azureAdlSecretName: azure-secret-namme

Such a secret should contain three files

  • AZURE_ADL_CLIENT_ID

  • AZURE_ADL_CREDENTIAL

  • AZURE_ADL_REFRESH_URL

See Service-to-service authentication with Azure Data Lake Storage Gen1 using Azure Active Directory for more information.