Deploy on GKE

Overview

Deploy the Access Broker as a Kubernetes Deployment on an existing Google GKE cluster. The image is pushed to Google Container Registry (or Artifact Registry) and the broker reads its tenant and token from a Kubernetes ConfigMap. A helper script (gcp-registry-setup.sh) configures registry authentication.

What you’ll accomplish:

Configure registry access and push the broker image
Deploy the broker to your GKE 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
gcloud CLI, docker, and kubectl configured for your GKE cluster
The britive-broker-2.0.0.jar file placed in the gke-deployment/ directory

For production, store the broker token in a Kubernetes Secret or Google Secret Manager (via Workload Identity) instead of the ConfigMap.

Deploy

Clone the onboarding repo

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

Configure registry access

chmod +x gcp-registry-setup.sh
./gcp-registry-setup.sh

Set deploy variables

Edit deploy.sh and set your token:

deploy.sh

BRITIVE_TOKEN="<broker-pool-token>"

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 the registry, 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`	Node service account can’t pull image	Re-run `gcp-registry-setup.sh`; confirm the node SA has `roles/artifactregistry.reader`
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 AKS