Legacy Product

Fusion 5.10
    Fusion 5.10

    Enable Superset Fusion 5.4 to 5.5

    Superset can be enabled with the Fusion Helm chart. It is not enabled by default.

    Managed Fusion users should reach out to our Customer Support team to discuss Superset. These instructions are for on-prem Fusion users.

    You can choose to deploy Superset with a dedicated gateway for extra security. If you choose this option, you log in to the gateway before logging in to Superset.

    See Use Superset with Fusion SQL for a detailed tutorial.

    How to enable Superset

    1. In your custom values YAML file, add one of the following, depending on whether you want the load balancer at the gateway or directly on the Superset container:

      Load balancer at the gateway Load balancer on the Superset container

      Use this option for the best security.

      Use this option to bypass the gateway login.

      Configuration:

      fusion-superset:
  enabled: true
  proxy:
    service:
      type: LoadBalancer

      Configuration:

      fusion-superset:
  enabled: true
  service:
    type: LoadBalancer

      For security, ingress.tls.enabled: true is also strongly recommended. Enabling TLS ensures that the basic authentication credentials sent to the gateway cannot be viewed in transit. If you enable TLS, you must create a Kubernetes TLS secret named <namespace>-fusion-sql-tls-secret that holds the certificate and key needed for Kubernetes to serve TLS traffic.

    2. Run the setup script using the --upgrade option, specifying your custom values YAML file using the --values option.

      The example below uses the setup script for Google Kubernetes Engine (GKE):

      ./setup_f5_gke.sh -c mycluster -p myproject -n mynamespace --region us-west1-c --upgrade --values gke_mycluster_mynamespace_fusion_values.yaml

    3. If you configured the load balancer at the gateway in step 1, retrieve the password for the superset_gateway service:

      1. Run kubectl --namespace <namespace> get secret superset-proxy-service-creds -o jsonpath='{.data.password}' | base64 -d

        GrDOQXzJ2hUgWrlGLLB2yh1kEjhWZABX

      2. Copy the password. The username is superset_gateway.

    4. Initialize the Superset admin user:

      1. Download the initialization script.

      2. Run the script:

        ./superset_init.sh <namespace> <superset-pod> <admin-password>

        This initializes the admin user with the password you specify (<admin-password>).

    5. Get the IP and port of the Superset load balancer:

      kubectl get services --namespace=<namespace>

    6. Connect to the Superset load balancer at https://<IP-address>:<port>/ and log in.

      • If you configured the load balancer at the gateway, log in to the gateway using the superset_gateway username and the password you retrieved above.

      • Log in to Superset as admin, with the password you set when you initialized the admin user above.

        From here, you can create additional Superset users. There is no authentication timeout, so your session persists indefinitely.

    See Use Superset with Fusion SQL for a detailed tutorial.