Deploy on AKS

Overview

Deploy the Access Broker as a Kubernetes Deployment on an existing Azure AKS cluster. The image is pushed to Azure Container Registry (ACR) and the broker reads its tenant and token from a Kubernetes ConfigMap.

What you’ll accomplish:

Build and push the broker image to ACR
Deploy the broker to your AKS cluster
Confirm it registers with your Britive tenant

Before You Begin

A Britive tenant with administrator access
Tenant subdomain and a broker pool token — from System Administration → Broker Pools
Azure CLI (az), docker, and kubectl configured for your AKS cluster
An ACR registry, and the AKS cluster attached to it (az aks update --attach-acr <acr-name>)
The britive-broker-2.0.0.jar file placed in the aks-deployment/ directory

For production, store the broker token in a Kubernetes Secret or Azure Key Vault (via the Secrets Store CSI driver) instead of the ConfigMap.

Deploy

Clone the onboarding repo

git clone https://github.com/britive/onboarding.git
cd "onboarding/Access Broker/aks-deployment"
cp /path/to/britive-broker-2.0.0.jar .

Set deploy variables

Edit deploy.sh with your token, ACR name, and resource group:

deploy.sh

BRITIVE_TOKEN="<broker-pool-token>"
ACR_NAME="myregistry"
RESOURCE_GROUP="my-aks-rg"

Set the ConfigMap values

Edit deployment.yaml:

deployment.yaml

data:
  broker-config.yml: |
    config:
      bootstrap:
        tenant_subdomain: mycompany
        authentication_token: "<broker-pool-token>"

Run the deploy script

chmod +x deploy.sh
./deploy.sh

The script builds the image, pushes it to ACR, and applies the Deployment to your cluster.

Verify

Check the pod is running

kubectl get pods -l app=britive-broker
# Expected: STATUS = Running

Tail the logs

kubectl logs -l app=britive-broker --follow

Confirm registration

In the Britive console, go to System Administration → Broker Pools → your pool. The broker shows as Connected.

Troubleshoot

Symptom	Cause	Fix
`ImagePullBackOff`	AKS not attached to ACR	Run `az aks update --name <cluster> --resource-group <rg> --attach-acr <acr-name>`
Pod `CrashLoopBackOff`	Bad tenant/token in ConfigMap	Fix `deployment.yaml`, re-apply, then `kubectl rollout restart deploy/britive-broker`
Broker not “Connected”	Egress blocked	Allow outbound HTTPS (443) to `*.britive-app.com` from the cluster

Next Steps

Last updated on June 7, 2026

Deploy on EKS Deploy on GKE