Use an airy.yaml configuration file to customize your Airy Core instance
The configuration workflow is as simple as:
Your Airy Core instance will start and stop components according to your configuration. For example, if you do not wish to start Facebook components, it is enough not to provide any Facebook specific configuration.
Now let's have a look at the different sections so you can make the changes you are looking for.
appImageTagthe image tag of the container images for the Airy Components
If you want to launch an older version refer to our Releases for the correct version number, or if you are feeling adventurous, try
developat your own risk.
containerRegistrythe URL of the container registry
namespacethe Kubernetes namespace that the Airy Core will use
ingressthe subdomains for the Airy Components that need to be accessed from outside the Kubernetes cluster
These settings are used to connect the Airy Components to your Kafka cluster and Redis.
brokerscomma separated list of the broker endpoints
schema-registryurl to the Schema Registry
commitIntervalthe Kafka Commit Interval if you are using the included Helm chart
systemTokenset to a long secure secret to use for machine API authentication
allowedOriginsyour site's origin to prevent CORS-based attacks (default:
oidca map of values that when set enable and define OIDC authentication
jwtSecretused to create jwt http sessions derived from oidc authentication (default: randomized on installation)
appIdset this to your Facebook App ID
appSecretset this to your Facebook App Secret
webhookSecretset this to a webhook secret of your choice (optional)
saFilecopy here the content of your Google service account key file (one line json string)
partnerKeyset this to your Google parttner key
authTokenset this to your Twilio authentication token
accountSidset this to your Twilio account SID
The Airy Controller only starts configured sources. To keep system load to a minimum, only add the sources you are using.
nameset this to the name of your webhook integration
maxBackoffset this to the maximum number of seconds the webhook should wait between retries with exponential backoff
s3Keyset this to your AWS S3 access key id
s3Secretset this to your AWS S3 secret access key
s3Bucketset this to your AWS S3 bucket
s3Regionset this to your AWS region
s3Pathset this to your AWS S3 path
These settings are used to enable or disable some external tools used to monitor or debug the Airy Core.
akhqKafka GUI for Apache Kafka (For more information visit akhq.io)
enabledset to either
trueto start AKHQ or
false(default) to disable it
For example, if you want to enable Facebook, Google and Twilio sources, as well as the webhook integration and the AKHQ tool, your
airy.yaml file should look like this: