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:
After you install the Google SDK and you have setup your Google account, you can create a Kubernetes cluster with one command:
The command will also update your
For more information refer to the official Google Guide
The simplest way to create the cluster is using the Microsoft Azure Portal. Navigate to the
Kubernetes services dashboard and click on
Create a Kubernetes cluster.
On the following screen make sure that you:
- Select the default resource group or create a new one.
- Fill in the name of the cluster (ex. awesomechat).
- Select the number of nodes.
After the cluster is created, you can use the
az Azure CLI to setup access to the cluster:
The last command will update your
kubeconfig file with the proper credentials.
For more information refer to the official Microsoft Guide.
A Kubernetes cluster can be created directly on the DigitalOcean dashboard by clicking
Kubernetes. You can leave all the options default, except for the
Node plan as the default nodes might be too small for running the
Airy Core platform.
After you create the cluster you need to go through a short guided cluster setup.
After you complete the setup you can
Download Config File to save the
kubeconfig file to your machine. With the
kubeconfig file you can now access the kubernetes cluster.
For more information refer to the official DigitalOcean Guide
Airy Core can be created on Minikube with predefined settings, using the Airy CLI. However, if you want to create your custom Minikube instance, for example with custom settings for CPU and RAM, you can also do that with the Minikube utility:
apiserver.service-nodeport-range settings is needed if you want to use port 80 on the Minikube VM as the NodePort for the ingress controller service.
For more information refer to the official Minikube Documentation.
Airy Core can be created on AWS using the Airy CLI. However that approach doesn't allow you to customize parameters other then the
instanceType. To be fully in control of the creation of the Kubernetes cluster on AWS you can use create one using the AWS Console or the AWS CLI.
For creating a cluster you first need an AWS IAM Role and a VPC. Export your profile and your region:
Create a new AWS IAM Role and attach the appropriate policies:
Get the default VPC and the public subnets:
You can modify the list of subnets according to your needs, but you must have at least two subnets with the property
MapPublicIpOnLaunch set to true.
Then create the Kubernetes cluster with the following command:
To update your
kubeconfig file run:
For more information refer to the official AWS Guide.
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:
Deploy Airy Core with the latest version. You can also configure a specific version.
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:
Configure your DNS so that your desired hostname points to the IP address of LoadBalancer. In this example we will be using the hostname
airy.yaml file with the following configuration:
Run the following command to upgrade your Airy Core installation and setup Let's Encrypt:
After that you should be able to access your
Airy Core instance through HTTPS, in this example on https://awesomechat.airy.co.
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.
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
Run the following command to create the
Airy platform without the bundled installation of Kafka, Zookeeper and the Schema registry.
The default installation creates its own Beanstalkd deployment, as it is a prerequisite for using the
Run the following command to create the
Airy platform without the bundled Beanstalkd installation.
If you wish to omit both Beanstalkd and Kafka, you can use the following command:
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:
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:
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
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:
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 Coreis 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
For upgrading your
Airy Core instance using helm, refer to our upgrade document.
To view your existing Helm installation run
You can see the current revision number of your Helm deployment by running:
If you wish to rollback to a previous installation, run:
VERSION_NUMBER is a previous revision number of the
airy helm chart.
If you need further help, refer to our Troubleshooting section.