Configurations to Customize Superset

The customization for the Superset sub-chart is controlled using the following sections in the values.yaml file of the parent Unica Helm chart:

Procedure

  1. Add a sub-chart for Unica
    /Unica-helm-chart-location/unica/charts/superset.

  2. Enable SS Mode in commonConfigMap.yaml of Unica.
    /<chart-location>/unica/templates/common-configMap.yaml

    MODE: "PLT_CMP_INT_OFFER_RTP_SS"

  3. In the values.yaml file of the Unica Helm chart, add the following variables:
    1. Global Settings - Sets global variables for the installation paths and claims.
      global:
      	HOME_DIR: "/docker/unica"
      	SUPERSETEXISTINGCLAIM: "hcl-unica"
      	UPDATE_DASHBOARD_TAG: true
      	CLEANUP_DASHBOARD_FOR_REIMPORT: false
      	image:
      		busybox: "busybox:1.28"
      HOME_DIR Base directory for Unica and Apache Superset and related files.
      SUPERSETEXISTINGCLAIM Provide the Existing Persistent Volume Claim, if any.
      UPDATE_DASHBOARD_TAG If superset dashboard tag need to be updated. Accepted values are either true or false.
      CLEANUP_DASHBOARD_FOR_REIMPORT Set it to true when dashboards existing dashboards, charts and datasets needs to be deleted, and new dash boards need to be imported. Accepted values are either true or false.
      image.busybox Image version for busybox utilities used by Superset (required for init container).
    2. Superset Node Connection Details - Defines database and Redis connection configurations.
      superset:
      	supersetNode:
      		connections:
      			db_host: '{{ .Release.Name }}-postgresql'
      			db_port: "5432"
      			db_user: superset
      			db_pass: superset
      			db_name: superset
      			redis_host: '{{ .Release.Name }}-redis-headless'
      			redis_port: "6379"
      			redis_user: ""
      db_host PostgreSQL database hostname.
      db_port Port on which PostgreSQL is accessible.
      db_user / db_pass Credentials for Superset to access PostgreSQL.
      redis_host / redis_port Hostname and port for Redis.
    3. Environment Variables and Secret Key - Manages sensitive environment variables such as the secret key.
      extraSecretEnv:
      	SUPERSET_SECRET_KEY: 'oQecTVRqA7ERuAWair6+b6W2MzTTt1cLNu6lcM/7KnLnrmC1kKBuxZxc'
      SUPERSET_SECRET_KEY Generate the key using the command : openssl rand -base64 42
    4. Superset Docker Image - Specifies the Superset Docker image repository and version.
      image:
      	repository: apachesuperset.docker.scarf.sh/apache/superset
      	tag: 4.0.2
      repository apachesuperset.docker.scarf.sh/apache/superset
    5. Redis and PostgreSQL Images - Specifies additional services' images, like Redis and PostgreSQL.
      redis:
      	image:
      		registry:docker.io
      		repository:bitnami/redis
      		tag:7.0.10-debian-11-r4
      	postgresql:
      		registry:docker.io
      		repository:bitnami/postgresql
      		tag:"14.6.0-debian-11-r13"
      Image
      registry Example value: docker.io
      repository Example value: bitnami/redis
      tag Example value: 7.0.10-debian-11-r4
      PostgreSQL
      registry Example value: docker.io
      repository Example value: bitnami/postgresql
      tag Example value: 14.6.0-debian-11-r13
    6. Admin User Initialization - Creates the initial admin user for Superset. These credentials will be required for superset UI login.
      init:
      	adminUser:
      		username: superadmin
      		password: superadmin
      username Example value: superadmin
      password Example value: superadmin
    7. Service Port - Sets the service port for Superset.
      service:
      	port: 8088
      port Example value: 8088
    8. Superset Custom Database Configurations - Sets up various schemas and SQLAlchemy URIs for Superset connections.
      SUPERSET_CUSTOM:
      	CAMP_DBSCHAMA: ""
      	CAMP_SQLALCHEMY_URI: “”
      	PLAN_DBSCHEMA: ""
      	PLAN_SQLALCHEMY_URI: ""
      	SUPERSET_DEFAULT_LOCALE: ""
      SQLALCHEMY_URI Configure SQLALCHEMY_URI as follows for the specified Databases:
      • mariadb:// <USERNAME>:<PASSWORD>@<HOSTNAME>:<PORT>/<DBNAME>
      • oracle:// <USERNAME>:<PASSWORD>@<HOSTNAME>:<PORT>/<DBNAME>
      • db2+ibm_db:// <USERNAME>:<PASSWORD>@<HOSTNAME>:<PORT>/<DBNAME>
      • mssql+pymssql:// <USERNAME>:<PASSWORD>@<HOSTNAME>:<PORT>/<DBNAME>
      • postgresql:// <USERNAME>:<PASSWORD>@<HOSTNAME>:<PORT>/<DBNAME>
      Note: If the password contains any special character, use the hexadecimal value of the special character.

      Example: If the password is Example@123, for the following link: mariadb://<USERNAME>:<PASSWORD>@<HOSTNAME>:<PORT>/<DBNAME>, replace <PASSWORD> with Example%40123 and not Example@123.