Skip to main content

Deploy Airy with Helm

Deploy Airy with Helm, on an existing Kubernetes cluster.

The goal of this document is to provide an overview of how to run Airy Core in an already existing Kubernetes cluster Helm.



You would need an existing Kubernetes cluster and administrative access to it. The size of the cluster depends on the number of connected sources and the number of messages flowing through the Airy Core platform. It is important that the pods are running stable and that they are not restarting. You can start with a simple setup of two nodes, each of them with 4 vCPUs and 8GB RAM. After that you can add or remove computing resources, so that the cluster is not under or over provisioned.

In case you are not sure how to create a Kubernetes cluster, here is a small guide on setting up Kubernetes in different environments:

For creating a Kubernetes cluster in Google, you can use either the Google cloud dashboard or the gcloud command line tool which is part of the Google SDK.

After you install the Google SDK and you have setup your Google account, you can create a Kubernetes cluster with one command:

gcloud container clusters create awesomechat --num-nodes=2 --machine-type=e2-standard-4

The command will also update your kubeconfig file.

For more information refer to the official Google Guide

Command line utilities#

You will also need the Helm and Kubectl binaries, locally on your machine.



Before you proceed with the Helm installation, make sure that you are connected to the correct Kubernetes cluster. If you are not using your default kubeconfig file, you need to export an environment variable:

export KUBECONFIG=./kube.conf

Deploy Airy Core with the latest version. You can also configure a specific version.

VERSION=$(curl -L -s
helm install airy${VERSION}.tgz --timeout 10m

By default Airy Core creates only a HTTP listener and when running in cloud environment it is recommended to setup an encrypted connection.

Get the address of your LoadBalancer:

kubectl -n kube-system get service ingress-nginx-controller -o jsonpath='{.status.loadBalancer.ingress[0].*}{"\n"}'

Configure your DNS so that your desired hostname points to the IP address of LoadBalancer. In this example we will be using the hostname

Create an airy.yaml file with the following configuration:

https: true
letsencryptEmail: ""

Run the following command to upgrade your Airy Core installation and setup Let's Encrypt:

helm upgrade airy${VERSION}.tgz --values ./airy.yaml

After that you should be able to access your Airy Core instance through HTTPS, in this example on


Deploying Airy Core with Helm gives flexibility to customize your installation.


If you wish to deploy Airy Core to a separate namespace, you need to specify the --namespace flag to Helm.

VERSION=$(curl -L -s
helm install airy${VERSION}.tgz --timeout 10m --namespace airy


The default installation creates its own Kafka cluster. This section explains how to deploy Airy Core on an existing Kafka cluster:

The default settings in the Airy Core platform, on how to access the Kafka resources, can be overwritten in your airy.yaml file:

# Default settings
brokers: "kafka-headless:9092"
zookeepers: "zookeeper:2181"
schemaRegistryUrl: "http://schema-registry:8081"
commitInterval: 1000

Run the following command to create the Airy platform without the bundled installation of Kafka, Zookeeper and the Schema registry.

helm install airy${VERSION}.tgz --set prerequisites.kafka.enabled=false --values ./airy.yaml


The default installation creates its own Beanstalkd deployment, as it is a prerequisite for using the integration/webhook component.

Run the following command to create the Airy platform without the bundled Beanstalkd installation.

helm install airy${VERSION}.tgz --set prerequisites.beanstalkd.enabled=false --values ./airy.yaml

If you wish to omit both Beanstalkd and Kafka, you can use the following command:

helm install airy${VERSION}.tgz --set prerequisites.enabled=false --values ./airy.yaml

Ingress controller#

The default installation creates its own NGinx Kubernetes ingress controller, in the kube-system namespace. If you prefer to use your own Kubernetes ingress controller, run the following command to create Airy without the bundled one:

helm install airy${VERSION}.tgz --set ingress-controller.enabled=false --values ./airy.yaml

The Airy platform comes with defined ingress resources. Feel free to customize them in accordance with your ingress controller. For example to set a custom host parameter, run the following commands:

for ingress in $(kubectl get ingress -l -o jsonpath='{.items[*]}'); do
kubectl get ingress ${ingress} -o json | jq "(.spec.rules[0].host=\"${HOST}\")" | kubectl apply -f -


The resources for the Airy Helm chart are located under infrastructure/helm-chart. You can customize the charts and package or deploy the charts directly to your Kubernetes cluster.

As a reference you can use the script that we use to package and publish the Helm charts, which is located under scripts/

Container registry#

If you wish to build the docker images yourself and store them in your own Container registry, you can overwrite the path of the container registry with the following command:

VERSION=$(curl -L -s
helm install airy${VERSION}.tgz --timeout 10m --set global.containerRegistry=my-docker-registry

Workspace setup#

When installing with Helm, a workspace directory is not created and therefore you cannot use the Airy CLI with your Airy Core installation, without setting up your workspace directory first. The Airy CLI is needed to apply configuration, to get the status of the components and to interact with the API.

In order for the CLI to recognize a workspace directory, you need to have two files there:

  • cli.yaml - Configuration on how the CLI can access the cluster.

    • apihost - The loadBalancer or the hostname on which the API can be reached.
    • kubeconfig - The path to the Kubernetes config file.
    • contextname - The context for the cluster, inside the kubeconfig file.
    • namespace - The namespace where Airy Core is installed.
  • airy.yaml - Values you used for deploying the Helm chart. The file can also be empty, but it needs to exist.

Example of the cli.yaml file.

apihost: https://my-airy-core-fqdn
contextname: gke_us-central1-c_awesomechat
kubeconfig: /home/user/.kube/config
namespace: default


For upgrading your Airy Core instance using helm, refer to our upgrade document.


To view your existing Helm installation run helm list.

You can see the current revision number of your Helm deployment by running:

helm list --filter 'airy' -o json | jq .[].revision

If you wish to rollback to a previous installation, run:

helm rollback airy {VERSION_NUMBER}

where VERSION_NUMBER is a previous revision number of the airy helm chart.


If you need further help, refer to our Troubleshooting section.

Last updated on