Azure
Requirements and sizing and Infrastructure give the versions each service needs. Kindo has run on every service listed here.
| Kindo needs | Azure service | Notes |
|---|---|---|
| Kubernetes | Azure Kubernetes Service (AKS) | |
| PostgreSQL | Azure Database for PostgreSQL flexible server | See PostgreSQL setup |
| Redis | Azure Managed Redis | See Redis setup |
| RabbitMQ | Your own, or one Kindo runs in the cluster | Azure has no managed RabbitMQ, and Azure Service Bus isn’t compatible. Kindo’s is a single broker with no failover; see RabbitMQ |
| Object storage | Azure Blob Storage | Kindo runs the S3 gateway in front of it. See Blob storage setup |
| Mail relay | Any mail relay | See Email |
| Secret store (optional) | Azure Key Vault | See Secret store |
| AI models | Azure OpenAI, Azure AI Foundry | See AI models |
| Ingress | Traefik in the cluster, or Application Gateway Ingress Controller (AGIC) | See the AGIC example. Not Application Gateway for Containers: it serves only the Gateway API, and Kindo creates Ingress objects |
| TLS certificates | cert-manager with Azure DNS | cert-manager reaches Azure DNS through workload identity |
PostgreSQL setup
Section titled “PostgreSQL setup”-
Allow these extensions in the server parameter, in capitals, alongside any already listed. Installing stops until the first row’s extensions are allowed.
Server Server parameter Extensions Auxiliary server, or the main server when there is no auxiliary server azure.extensionsUUID-OSSP,PG_TRGMServer that hosts Hatchet azure.extensionsBTREE_GIST -
The server that hosts Hatchet carries the Hatchet settings as server parameters.
Redis setup
Section titled “Redis setup”Kindo needs a single standalone Redis.
-
The cache uses the Non-clustered clustering policy. Azure allows it only on caches of 25 GB or smaller, so a cache that grows past that needs the policy changed first.
-
Access-key authentication is on. The eviction policy is volatile-lru; allkeys-lru also works.
-
Production caches use high availability.
-
Kindo connects over TLS on port 10000, with the access key as the password, URL-encoded, since keys can contain characters a URL reserves:
rediss://:<access-key>@<name>.<region>.redis.azure.net:10000
Blob storage setup
Section titled “Blob storage setup”Blob storage doesn’t serve the S3 API, so Kindo runs an S3 gateway in the cluster, in front of your storage account. Kindo deploys and configures the gateway, with no gateway to run and no keys to create.
-
The storage account is StorageV2 with hierarchical namespace off, and holds a private container for uploads. The container stays private: anyone can read a file from a container that allows public reads.
-
The gateway reaches the account through workload identity, which stores no key, or through the account key.
-
Users’ browsers download files from the address below, so it can’t sit behind an IP allowlist. With your own routing, see Ingress, DNS, and TLS.
Download address Config setting for another address storage.<domain>inputs.endpoints.storage: a URL with no path that no other Kindo address uses
Workload identity
Section titled “Workload identity”-
The AKS cluster has the OIDC issuer and Workload Identity enabled.
-
A user-assigned managed identity holds the Storage Blob Data Contributor role on the storage account.
-
The identity has a federated credential:
Field Value Issuer The cluster’s OIDC issuer URL Subject system:serviceaccount:kindo-s3proxy:s3proxyAudience api://AzureADTokenExchange -
The config names the account, the container, and the identity’s client ID:
inputs:storage:azureBlob:account: <storage account name>container: kindo-uploadsauth:workloadIdentity:clientId: <managed identity client ID>
Account key
Section titled “Account key”The account key gives full access to the storage account.
inputs: storage: azureBlob: account: <storage account name> container: kindo-uploads auth: accountKey: key: <storage account key>If you change the account key, the gateway and Kindo’s services keep using the old one until they restart.
Move an existing instance to Blob storage
Section titled “Move an existing instance to Blob storage”Switching an existing instance changes the download address to the one in Blob storage setup. Files already in the S3 bucket stay there, and can be copied to the container.
- Upgrading from 2026.09: the instance upgrades on S3 first. Then the storage config settings switch to Azure Blob Storage and are applied.
- Already on 2026.11: the storage config settings switch to Azure Blob Storage and are applied.
After a switch back to S3, the gateway stays installed. Applying the change names the command that removes it.
