Getting Started¶
This guide walks through installing the operator and deploying a minimal Superset instance using dev mode.
Prerequisites¶
- Kubernetes 1.25+ (1.36, 1.35 officially tested; 1.29+ recommended so CEL validation is GA — see supported versions)
- Helm 3
- A PostgreSQL database accessible from the cluster
1. Install the operator¶
helm install superset-operator \
oci://ghcr.io/apache/superset-kubernetes-operator/charts/superset-operator \
--version <version> \
--namespace superset-operator-system \
--create-namespace
Replace <version> with a published chart version (e.g., 0.1.0); see
Downloads for published tags.
2. Deploy Superset¶
Create a minimal Superset instance in dev mode (inline credentials for simplicity):
kubectl apply -f - <<'EOF'
apiVersion: superset.apache.org/v1alpha1
kind: Superset
metadata:
name: my-superset
spec:
environment: Development
image:
tag: "6.1.0"
secretKey: thisIsNotSecure_changeInProduction!
metastore:
uri: postgresql+psycopg2://superset:superset@postgres:5432/superset
webServer: {}
lifecycle:
migrate: {}
init:
adminUser: {}
loadExamples: true
EOF
The operator runs database migrations and initialization, then deploys the web server.
3. Watch it come up¶
Wait for PHASE: Running. You can also inspect lifecycle task state on the
parent:
4. Access Superset¶
Open http://localhost:8088 and log in with admin / admin.
Next steps¶
- Installation — production deployment with proper secret management
- Configuration — full configuration reference
- Architecture — how the operator works under the hood