System requirements¶
Software¶
Requirement |
Version |
|---|---|
Juju |
3.4 or later |
Kubernetes |
A cluster supported by Juju, with a default storage class |
Superset workload |
Selected by the charm track, for example |
Superset and its backing services all run on Kubernetes, so a single Kubernetes cloud is enough.
Resource sizing¶
For a single-host evaluation deployment (the tutorial setup, with PostgreSQL and Redis co-located):
Resource |
Minimum |
|---|---|
CPU |
2 threads, 4 recommended |
RAM |
8 GB |
Disk |
40 GB |
Production sizing depends on the number of concurrent users and the query mix. Scale the UI and worker applications horizontally rather than growing a single pod, and size PostgreSQL for the metadata database and Redis for the results cache accordingly. See Scale and tune performance.
Supported dependency channels¶
The deployment flows in this documentation are tested with:
Charm |
Channel |
Required |
|---|---|---|
14/stable |
Yes |
|
latest/edge |
Yes |
|
latest/stable |
For ingress and TLS, over the |
|
1/stable |
For an HTTPS ingress URL in testing |
|
latest/edge |
For single sign-on with an external identity provider |
|
latest/stable |
For alerts and reports |
|
latest/edge |
For the Trino integration |
|
latest/stable |
For observability |
Ports¶
Port |
Protocol |
Purpose |
|---|---|---|
8088 |
TCP |
Superset web server and API (UI) |
9102 |
TCP |
Prometheus metrics from the StatsD exporter (UI and worker) |
9103 |
TCP |
Prometheus metrics from the Celery exporter (worker) |
9125 |
UDP |
StatsD metrics ingest, in-pod (UI) |