Superset
The business intelligence and dashboarding component in Data.
Component Category
Business intelligence
Component Description
Superset is the business intelligence and dashboarding component used in Data for data exploration, visualization, and analytical reporting.
Why It Is Used
In BullSequana AI, Superset provides a user-facing BI layer for exploring analytical datasets and building dashboards.
Learn More
Deployment notes
BullSequana AI deploys Superset 6.1.0 from chart 0.22.4 with one web replica and one Celery worker. A dedicated Redis 8.10.1 Deployment and its superset-redis Service provide the task broker, while the shared CloudNativePG cluster stores Superset metadata. Redis runs without persistence and requires a password that the platform generates once. Keycloak provides native OIDC authentication, and Gateway API publishes the web interface.
The Redis container runs as user and group ID 999 by default. On OpenShift, set run_as_user = 0 in the [redis] section of the Superset component variables so the platform omits these IDs and the restricted SCC assigns them.
The platform renders network policies for Superset when [network_policy] enabled is on, which is the default. Under those policies the web pod accepts traffic only from the platform gateway, and the web, worker and database initialization pods reach only cluster DNS, the shared PostgreSQL cluster, Redis and the platform's public hostnames. A policy a site adds in the superset namespace widens that; no other policy applies to these pods. Users add their analytical databases as data sources at runtime, so the web and worker pods may also reach the addresses in external_egress_cidrs on the ports in SUPERSET_NETWORK_POLICY_DATA_SOURCE_PORTS. The default is 5432,3306,1433,1521,443,8443: PostgreSQL, MySQL, SQL Server, Oracle and HTTPS endpoints. Add the port of a data source that listens elsewhere before users connect to it. The policies take effect only on a cluster that enforces network policies; see Network policies.
Access
Superset sets each user's role at every sign-in from their Keycloak groups:
| Keycloak group | Superset role |
|---|---|
platform-administrators, the platform administrators | Admin |
PROAI-DATAVIZ-ADMIN-GROUP | Admin |
PROAI-DATAVIZ-ALPHA-GROUP | Alpha |
PROAI-DATAVIZ-USERS-GROUP | Gamma |
Superset refuses a user who is in none of these groups. A user removed from a group loses its role at their next sign-in.
The platform adds no analytical data source to Superset. Admin and Alpha users can query every data source that is added, whoever added it.
Interacts With
PostgreSQL, which stores Superset service state and metadata; administrators configure analytical data sources separately.Redis, which provides the password-protected Celery task broker.Keycloak, which provides authentication and access control.Gateway APIandExternal DNS, which publish the application.