Deploying Apica Ascent PaaS in Azure Kubernetes Service

The following guide takes you through deploying Apica Ascent PaaS in an Azure Kubernetes Service cluster. The deployment involves the following steps:

If you have an AKS cluster that is appropriately sized for deploying Apica Ascent and handling your data ingestion rate, you can skip the AKS cluster creation step. However, you must label the nodes as specified in the Node pool configuration table failing which the pods in the cluster will not land in any of the nodes.

Creating an Azure Kubernetes Cluster

Install Azure CLI.

Connect to your Azure account using Azure CLI by running the following command.

az login --tenant “tenant-id”

Create a resource group by running the following command.

az group create --name <Resource group name> --location <location>

Configuring the node pool

Create four node pools as described and labelled in the following table. The table describes the node pool configuration for ingesting 100 GB of data per day.

Important: Ensure that the node pools are all created in the same availability zone.


Node pool

Node labels

Node count

8 Core 16 GB RAM (F8s_v2)

ingest (CPU intensive)


8 Core 16 GB RAM (F8s_v2)



4 Core 8 GB RAM (F4s_v2)



4 Core 8 GB RAM (F4s_v2)



Execute the following commands to create the AKS cluster along with the node pools described above.

az aks create --kubernetes-version 1.19.11 -g <your resource group> --name <cluster name> -l <location> --node-vm-size Standard_f8s_v2 --zones 1 --nodepool-name ingest --nodepool-labels --node-count 1 --enable-ultra-ssd

az aks nodepool add --cluster-name <cluster name> --name common --resource-group <You resource group> --zones 1 --labels --node-vm-size standard_f8s_v2 --node-count 1 --enable-ultra-ssd

az aks nodepool add --cluster-name <cluster name> --name db --resource-group <You resource group> --zones 1 --labels --node-vm-size standard_f4s_v2 --node-count 1 --enable-ultra-ssd

az aks nodepool add --cluster-name <cluster name> --name hauler --resource-group <You resource group> --zones 1 --labels --node-vm-size standard_f4s_v2 --node-count 1 --enable-ultra-ssd

The following code block depicts example commands for creating the AKS cluster with the node pool specification provided in the table above.

az aks create -g azure-test --name logiqai -l eastus --node-vm-size Standard_f8s_v2 --zones 1 --nodepool-name ingest --node-count 1 --nodepool-labels --enable-ultra-ssd

az aks nodepool add --cluster-name logiqai --name common --resource-group azure-test --zones 1 --labels --node-vm-size standard_f8s_v2 --node-count 1 --enable-ultra-ssd

az aks nodepool add --cluster-name logiqai --name hauler --resource-group azure-test --zones 1 --labels --node-vm-size standard_f4s_v2 --node-count 1 --enable-ultra-ssd

az aks nodepool add --cluster-name logiqai --name db --resource-group azure-test --zones 1 --labels --node-vm-size standard_f4s_v2 --node-count 1 --enable-ultra-ssd

Connecting with your AKS cluster

Connect to the AKS cluster by first visiting the Azure portal, navigating to the AKS cluster you created, and selecting it. Next, click on the Connect icon and follow the instructions displayed on the right panel. Execute the following command and you should see the nodes in your cluster.

kubectl get node

Creating the MinIO blob storage gateway for S3 compatibility

Follow the instructions on MinIO’s site to create an Azure blog storage account. Once you login, click the “+” button on the right hand corner of the screen to create a bucket named logiq. Note down this bucket name since we'd be using it in later steps.

Create an Azure ultra disk storage class using the YAML configuration provided below.

kind: StorageClass
name: ultra-disk-sc
volumeBindingMode: WaitForFirstConsumer # optional, but recommended if you want to wait until the pod that will use this disk is created
skuname: UltraSSD_LRS
cachingMode: None
kind: managed
diskIopsReadWrite: "3000" # minimum value: 2 IOPS/GiB
diskMbpsReadWrite: "125" # minimum value: 0.032/GiB

Verify that the storage class has been created by running the following command.

kubectl get sc ultra-disk-sc

Deploying Apica Ascent PaaS

Download the values.yaml file from this location and replace the following variables in the file.

awsServiceEndpoint: https://<your-blobstorage-accountname>
s3_bucket with the minio bucketname created at step 5.
AWS_ACCESS_KEY_ID: minio service name
AWS_SECRET_ACCESS_KEY: access key from the mino.
storageClass: ultra-disk-sc
creatStorageClass: true

Next, follow the instructions on Apica Ascent’s Quickstart guide to spin up the Apica Ascent stack on this AKS cluster.

Once you've successfully deployed Apica Ascent, you can (optionally) disable monitoring AKS with container insights on your cluster by running the following command.

az aks disable-addons -a monitoring -n <aks cluster name> -g <resource group>

Last updated