Skip to content

Install burrito with Helm

Requirements

  • Installed kubectl command-line tool
  • Installed helm command-line tool (version v3.8.0 and further)
  • Have access to a Kubernetes cluster

1. Basic installation

Info

Our Helm chart is published in an OCI-based registry (ghcr.io). You must use Helm v3.8.0 or above.

helm install burrito oci://ghcr.io/padok-team/charts/burrito -n burrito-system --create-namespace

This will create a new namespace, burrito-system, where the burrito core components will live.

You can change the chart's version with any version available on our Chart registry.

2. Burrito Helm configuration

The Burrito configuration is managed through Helm values files, which can be overridden at installation time.

You can find the default values of the Burrito Helm chart by running:

helm show values oci://ghcr.io/padok-team/charts/burrito

The source code and values file of the chart is available on burrito GitHub repository.

Here is an example of a simple burrito Helm values file that you can use to bootstrap your installation:

config:
  burrito:
    controller:
      timers:
        driftDetection: 10m # run drift detection every 10 minutes
        onError: 10s # wait 10 seconds before retrying on error
        waitAction: 1m # wait 1 minute before retrying on locked layer
        failureGracePeriod: 30s # set a grace period of 30 seconds before retrying on failure (increases exponentially with the amount of failed retries)
    datastore:
      storage:
        mock: true # use a mock storage for the datastore (useful for testing, not recommended for production)
tenants:
  - namespace:
      create: true
      name: "burrito-project"
    serviceAccounts:
    - name: burrito-runner
      annotations:
        iam.gke.io/gcp-service-account: burrito@company-project.iam.gserviceaccount.com # example: use GKE Workload Identity to have access to GCP infrastructure

Info

Learn more about these values in the chart's README file and Multi-tenant architecture.