- Overview
- Getting Started
- Quick Start Guide
- Core Concepts
- Users
- Models
- Creating a Model
- Model Card
- Creating a Release
- Uploading Files
- Uploading Images
- Model Templating
- Data Cards
- Creating a Data Card
- Managing Data Cards
- Using a Model
- Browsing the Marketplace
- Requesting Access
- Using a Pushed Docker Image
- Downloading Files
- Reviews
- Understanding Reviews
- Reviewing
- Reviewing a Release
- Reviewing an Access Request
- Reviewing a Model Card Lifecycle
- Review Outcomes
- Security Scanning
- File Scanning
- Image Scanning
- Inferencing
- Creating an Inference Service
- Managing Inference Services
- Model Mirroring
- Creating a Mirrored Model
- Editing a Mirrored Model Card
- Untrusted Models
- Untrusted Models
- Deletion
- Deleting a File
- Deleting a Model
- Soft Deletion
- Programmatic Access
- Authentication
- Personal Access Tokens
- Python Client
- OpenAPI Reference
- Webhooks
- Administration
- Getting Started
- Deployment Architecture
- App Configuration
- Model Lifecycle Configuration
- Schemas
- Understanding Schemas
- Create a Schema
- Upload a Schema
- Schema Migrations
- Review Roles
- Managing Review Roles
- Assigning Roles to Schemas
- Federation
- Peer Integration
- Microservices
- Artefact Scanners
- Helm
- Basic Usage
- Configuration
- Isolated Environments
- Migrations
- Bailo v0.4
- Bailo v2.0
- DataBase Scripts
- Reference
- Glossary
- Roles & Permissions
- Troubleshooting & FAQ
Helm Configuration
Common questions this page answers:
- How do I configure Helm values for Bailo?
- How do I override the default Helm configuration?
- What minimum configuration is required?
The default Helm configuration is stored within values.yaml. You should not alter this configuration directly, instead
overriding individual values via the command line --set flag, or by providing a custom --values file.
To override a single value, add --set <option>=<value> to either the helm install and helm upgrade commands you
run. To override multiple values, create a local.yaml (or a deployment specific name like ops.yaml) file and add
--values local.yaml to your helm install and helm upgrade commands. For example:
# reference.yaml
image:
frontendRepository: 'internal.docker.registry'
frontendTag: 'v2.0.3-rc.0'
Would be installed and upgraded using:
$ helm install --values reference.yaml bailo .
$ helm upgrade --values reference.yaml bailo .
We do not host built images of Bailo, thus at the very minimum the custom configuration should include the following:
# local.yaml
image:
frontendRepository: '<docker registry>'
frontendTag: 'v2.1.2'
backendRepository: '<docker registry>'
backendTag: 'v2.1.2'
artefactscanRepository: '<docker registry>'
artefactscanTag: 'v1.0.0'
Copyright © Crown Copyright 2026.
