Unmanaged Private Cloud Deployment

helm registry login <repo> -u <user> -p <pass>

helm pull oci://<repo>/helm/jedox --version xx.x --untar --untardir jedox-xx.x

# NOTE: What is called "Jedox instance" in the docs, is in Helm terminology a "release".
# NOTE: This is a streamlined version of the values.yaml file. For a full list of options, please refer to the values.yaml file.
# NOTE: The jedox_values.yaml file is used to define the most common production settings for the Jedox instance.
# NOTE: In a standard deployment, you only need to modify this and only this file. Values.yaml should be ignored.
global:
  # values used by the BYOI deployment
  storage:
    # You can enable only one storage method: fromStorageClass / fromPersistentVolume / fromNfs
    external:
      fromStorageClass:
        # Set to true if you want to use StorageClass 
        enabled: false
        # For jedox_values.yaml, the storageClass must always be RWX and Use nfs 3.1 instead
        # If you cannot natively provide RWX storage, you can use the NFS option below
        # https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner
        # Name of the storage class defined in your cluster (required)
        storageClass: default
        #The disk size must always be at least 128Gi (512GB recommended)
        diskSize: 128Gi

      #To be used when you want to define your PersistentVolumeClaim manually
      fromPersistentVolume:
        # Set to true if you want to use manually defined PVC
        enabled: false
        # The below variables are used to define external NFS for Jedox
        # Please input the name of a RWX PVC that is already defined in the NS where you deploy Jedox (required)
        # pvc: rwx-pvc

      # To be used when you run your own NFS server
      # Only NFS 3 is supported
      fromNfs:
        enabled: false
        #
        # NFS server address (required)
        server: 10.100.10.10
        #
        # NFS path (required)
        path: /jedox
        #
        # NFS volume size (default is 100Gi)
        #size:
        #
        # NFS volume reclaim policy (default is Retain)
        #reclaimPolicy:
        #
        # NFS volume mount options (default is rsize=262144, wsize=262144, nconnect=8). nfsvers=3 is required and always set
        #mountOptions:
  #
  #
  #Define the PostgreSQL settings
  #Set to true if you want to use an external PostgreSQL DB
  db:
    # If both external and internal PostgreSQL options are set to false, it will fallback on H2 DB (not supported)
    # Either external or internal can be enabled at the same time.
    postgres:
      #
      # Use an external PostgreSQL server
      external:
        enabled: false
        #
        # PosgreSQL init details (required)
        #
        # for BYOI, this is the hostname or IP for the PostgreSQL DB (required)
        databaseHost:
        #
        #for BYOI, this is the name of the database you've defined in the PostgreSQL server (the DB schema should have the same name)
        databaseName:
        #
        # PostgreSQL username (required)
        databaseUser:
        # PostgreSQL password (required)
        databasePassword:
        # for BYOI, this is the port for the PostgreSQL DB (required)
        databasePort: 5432
        # Sslmode for PostgreSQL DB (required)
        sslmode: require
  # vhosts configuration
  vhosts:
    #
    # Virtual hosts. Default uses the Helm release name.
    # Format: <namespace>.<apex-domain>.
    # The namespace serves as the subdomain. E.g.:
    #hosts:
    #  - company.jedox.com
  # cert-manager configuration
  # If using cert-manager, you can add the issuer name to the values.
  cert_manager:
    enabled: false
    #
    # issuer name, default is letsencrypt-staging
    #issuerName: letsencrypt
    #
    # issuer kind, default is ClusterIssuer
    #issuerKind: Issuer
olap:
  enabled: true
  olap:
    # hardware key for licensing, at least 10 chars (required)
    #hwKey:

helm install <release-name> . --namespace <namespace> --values jedox_values.yaml

-- Step 1: Create the database
CREATE DATABASE jedox;

-- Step 2: Connect to the new database
\c jedox

-- Step 3: Create a schema with the same name as the database
CREATE SCHEMA jedox;

-- Step 4: Create a user with administrative privileges
CREATE USER jedox_admin WITH PASSWORD 'your_secure_password';

-- Step 5: Assign ownership of the database and schema to the user
ALTER DATABASE jedox OWNER TO jedox_admin;
ALTER SCHEMA jedox OWNER TO jedox_admin;

-- Step 6: Grant full privileges to the user
GRANT ALL PRIVILEGES ON DATABASE jedox TO jedox_admin;
GRANT ALL PRIVILEGES ON SCHEMA jedox TO jedox_admin;

global:
  # PostgreSQL Database Configuration
  db: 
    # If both external and internal PostgreSQL options are set to false, it will fallback on H2 DB (not supported) 
    # Either external or internal can be enabled at the same time.
    postgres: 
      # Use an external PostgreSQL server
      external:
        enabled: true  # Set to true if using an external PostgreSQL DB

        # PostgreSQL Host (required)
        databaseHost: <your-host>

        # Database Name (must match schema name)
        databaseName: jedox  

        # PostgreSQL Credentials (required)
        databaseUser: jedox_admin  
        databasePassword: your_secure_password  

        # PostgreSQL Port (default: 5432)
        databasePort: 5432  

        # SSL Mode (disable for non-TLS connections)
        sslmode: disable  

SELECT datname FROM pg_database WHERE datname ='jedox'; 
SELECT schema_name FROM information_schema.schemata WHERE schema_name ='jedox';