Installing Apps

The Obol Stack supports installing arbitrary Helm charts as managed applications. Each installation creates an isolated deployment with its own namespace, similar to network deployments.

Install an application

Install any Helm chart using one of the supported reference formats:

# Install from ArtifactHub (repo/chart format)
obol app install bitnami/redis

# Specific version
obol app install bitnami/[email protected]

# Direct URL to chart archive
obol app install https://charts.bitnami.com/bitnami/redis-19.0.0.tgz

# Custom name and deployment ID
obol app install bitnami/postgresql --name mydb --id production

info

Find charts at Artifact Hub.

Supported chart reference formats:

Format	Example
repo/chart	bitnami/redis (resolved via ArtifactHub)
repo/chart@version	bitnami/[email protected]
https://.../*.tgz	Direct URL to chart archive

What happens during installation:

1. Resolves the chart reference (via ArtifactHub for repo/chart format).
2. Fetches default values from the chart.
3. Generates a helmfile.yaml that references the chart remotely.
4. Saves configuration to ~/.config/obol/applications/<app>/<id>/.

Deploy to the cluster

After installing, deploy the application:

obol app sync postgresql/eager-fox

Check status:

obol kubectl get all -n postgresql-eager-fox

List applications

# Simple list
obol app list

# Detailed output
obol app list --verbose

Customize configuration

Edit the values file before deploying or re-syncing:

$EDITOR ~/.config/obol/applications/postgresql/eager-fox/values.yaml

# Re-deploy with changes
obol app sync postgresql/eager-fox

Local files per deployment:

• helmfile.yaml - Deployment configuration (references chart remotely)
• values.yaml - Configuration values (edit to customize)

Delete an application

# With confirmation prompt
obol app delete postgresql/eager-fox

# Skip confirmation
obol app delete postgresql/eager-fox --force

This removes the Kubernetes namespace, all deployed resources, and the local configuration directory.

Default infrastructure

The following services are deployed automatically when the stack starts (you do not need to install them):

Service	Namespace	Purpose
ERPC	erpc	Unified RPC load balancer for Ethereum endpoints
Obol Frontend	obol-frontend	Web management dashboard
Monitoring	monitoring	Prometheus + kube-prometheus-stack
Traefik	traefik	Gateway API ingress controller
Cloudflared	traefik	Cloudflare tunnel connector
llmspy	llm	LLM proxy/router

View all running services:

obol helm list -A