If you run or have access to a Kubernetes cluster and are comfortable with Helm, we maintain official BuildBuddy Helm charts that are easy to configure and deploy.
They have options to deploy everything necessary to use all of BuildBuddy's bells and whistles - including MySQL, nginx, remote build execution and more.
The official BuildBuddy charts live in our buildbuddy-helm repo.
- Kubernetes 1.15+ with Beta APIs enabled
- Helm v2/v3
- Tiller (the Helm v2 server-side component) installed on the cluster
To install the BuildBuddy Helm repo:
To install the chart with the release name
Helm v2 command
The command deploys BuildBuddy on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.
To uninstall/delete the
The command removes all the Kubernetes components associated with the chart and deletes the release.
If you change configuration, you can update your deployment:
You can write your Kubernetes deployment configuration to a file with release name
You can then check this configuration in to your source repository, or manually apply it to your cluster with:
Below are some examples of
.yaml files with values that could be passed to the
command with the
--values flag to get started.
Note: make sure to run
kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v0.16.1/cert-manager.crds.yaml to install CRDs before deploying this configuration.
Auth can be configured with any provider that supports OpenID Connect (OIDC) including Google GSuite, Okta, Auth0 and others.
For more example
config: blocks, see our configuration docs.
For local testing use minikube
Create local cluster using with specified Kubernetes version (e.g.
Above command is not required for Helm v3
Perform local installation
Helm v3 command
For more information on configuring your BuildBuddy Enterprise Helm deploy, check out the chart: