Skip to main content
This reference documents all configuration options for the Astro Private Cloud (APC) Helm chart. Use this guide to customize the values.yaml file for your APC installation.

Values file structure

The APC Helm chart uses a hierarchical structure:

Required configuration

Configure the following required values:

Global configuration

Base domain and TLS

Plane Mode (Control, Data, Unified)

Astro Private Cloud 1.0 supports split control plane and data plane deployments:

Network policies

RBAC and cluster roles

Node selection

Separate platform pods from Airflow pods:

Private registry

Use a private container registry:

Namespace pools

Pre-provision namespaces for Airflow Deployments:

Storage class

Specify a storage class for all persistent volumes:

OpenShift support

Astronomer platform components

Houston API

Houston is the core internal API that powers the platform:

Houston configuration (houston.config)

Houston accepts extensive configuration via houston.config:

Authentication

Deployment defaults

Email configuration

Prometheus integration

Commander

Commander manages Kubernetes resources for deployments:

Registry

Container registry for deployment images:

Astro UI

NGINX ingress

Prometheus (Monitoring)

Grafana

Elasticsearch (Logging)

Vector (Log Collection)

External logging

Forward logs to external Elasticsearch:

NATS (Messaging)

Database configuration

Database SSL

PgBouncer (connection pooling)

Auth sidecar (OpenShift)

For OpenShift deployments requiring auth proxy:

Logging sidecar

Add Vector sidecar to Airflow pods:

Dag-only deployments

Airflow operator

Enable Kubernetes operator-based deployments:

Extra objects

Add custom Kubernetes resources:

Complete example

Here’s an example configuration:

Validate configuration

After creating your values file, validate it:

Upgrade configuration

(Optional) When updating your values file, you can use the helm diff plugin, and then run the following command to see a diff of your changes: