Skip to content
These docs are a preview of Self-Managed Kindo 2026.11, an upcoming release.

Azure

Requirements and sizing and Infrastructure give the versions each service needs. Kindo has run on every service listed here.

Kindo needsAzure serviceNotes
KubernetesAzure Kubernetes Service (AKS)
PostgreSQLAzure Database for PostgreSQL flexible serverSee PostgreSQL setup
RedisAzure Managed RedisSee Redis setup
RabbitMQYour own, or one Kindo runs in the clusterAzure has no managed RabbitMQ, and Azure Service Bus isn’t compatible. Kindo’s is a single broker with no failover; see RabbitMQ
Object storageAzure Blob StorageKindo runs the S3 gateway in front of it. See Blob storage setup
Mail relayAny mail relaySee Email
Secret store (optional)Azure Key VaultSee Secret store
AI modelsAzure OpenAI, Azure AI FoundrySee AI models
IngressTraefik 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 certificatescert-manager with Azure DNScert-manager reaches Azure DNS through workload identity
  • Allow these extensions in the server parameter, in capitals, alongside any already listed. Installing stops until the first row’s extensions are allowed.

    ServerServer parameterExtensions
    Auxiliary server, or the main server when there is no auxiliary serverazure.extensionsUUID-OSSP, PG_TRGM
    Server that hosts Hatchetazure.extensionsBTREE_GIST
  • The server that hosts Hatchet carries the Hatchet settings as server parameters.

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 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 addressConfig setting for another address
    storage.<domain>inputs.endpoints.storage: a URL with no path that no other Kindo address uses
  • 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:

    FieldValue
    IssuerThe cluster’s OIDC issuer URL
    Subjectsystem:serviceaccount:kindo-s3proxy:s3proxy
    Audienceapi://AzureADTokenExchange
  • The config names the account, the container, and the identity’s client ID:

    inputs:
    storage:
    azureBlob:
    account: <storage account name>
    container: kindo-uploads
    auth:
    workloadIdentity:
    clientId: <managed identity client ID>

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.

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.