Unmanaged Private Cloud Deployment

To deploy Jedox in your own Kubernetes cluster, ensure that the technical requirements are met and follow the steps below.

Installation Process

Step 1: Login to the Jedox container registry

Run the following command to login to the Jedox container registry:

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

The connection details will be provided to you by the Jedox team.

Step 2: Pull and export the Jedox Helm Chart

After successfully logging in, pull and export the Jedox Helm Chart to a directory on your computer using the following commands:

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

The value for the version parameter in this command is specifying the version of the Jedox Helm Chart to be pulled, and is not to be confused with the version of the Jedox Platform that will be installed with this Chart later. To define the Jedox Platform version, go to the Jedox directory within untardir, which has been created after running the helm pull command, and define the Jedox version that you want to install afterwards by running one of the following set-ver scripts:

  • For PowerShell (Windows)
    .\set-ver.ps1 -newVersion "<your_version>"; E.g: .\set-ver.ps1 -newVersion "26.1"
  • For Bash (Linux/Mac)
    ./set-ver.sh <your_version>; E.g: ./set-ver.sh 26.1
Step 3: Adjust values in YAML files

Go to the Jedox-xx.x/Jedox directory, where the Helm chart is extracted, and locate the file values.yaml. Adjust the values in this file according to your specific requirements. The below configuration serves as an example.

Copy
# 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 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 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

  # nginx-gateway-fabric (NGF) configuration
  gatewayFabric:
    enabled: true
    #
    # shared parent Gateway (pre-installed cluster infra)
    gateway:
      name: gateway-api
      namespace: nginx-gateway
      httpSectionName: http
    #
    # NGF dataplane service for internal loopback ExternalName services
    # default is gateway-api-nginx.nginx-gateway.svc.cluster.local
    dataplaneService:
    #
    # IP for cluster's internal DNS resolver service used by the nginx static config. Default is 10.0.0.10
    dnsResolverIP:
    #
    # per-release ListenerSet name, default is <release>-listeners
    #listenerSetName:
    #
    # TLS termination on the per-release ListenerSet (default true).
    # Set tls.enabled: false for internal HTTP-only access on the shared Gateway
    # port 80; no TLS secret is required in that mode.
    tls:
      enabled: false
    #
    # TLS secret for the ListenerSet HTTPS listeners (only when tls.enabled is true)
    tlsSecretName: tls-selfsigned
    #
    # namespace selector label the parent Gateway admits (must be set on release namespace)
    namespaceLabel:
      key: shared-gateway-access
      value: "true"

  # 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:

Step 4: Namespace naming convention

As per Jedox naming conventions, the namespace where you deploy the Jedox instance must have the same name as the subdomain in the DNS. For example, if your instance is accessed via the domain dev-jedox.customer.com, the namespace of the instance must be dev-Jedox.

Step 5: Deploy Jedox

Use the following Helm command to deploy Jedox to the Kubernetes cluster:

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

Replace <release-name> with the desired name for the Helm release.

Step 6: Gateway routing and certificates

When the Helm chart is deployed with enabled NGINX Gateway Fabric, it creates the following for each Jedox instance:

  • a ListenerSet named <release-name>-listeners, attached to the shared gateway-api Gateway, which terminates HTTPS on port 443
  • one HTTPRoute per Jedox service

The hostnames come from the "global.vhosts.hosts" value in the "values.yaml" file. Once set, you can access Jedox via <chart_name>.<domain>.

You must add an A or CNAME record for each FQDN. Point them to the external address of the NGINX Gateway Fabric LoadBalancer, which you can find with the following command: kubectl get svc -n nginx-gateway

Target hostnames:

Service Ingress Name Internal FQDN Purpose
OLAP Browser jedox‑olap‑browser browser.<chart_name>.<domain> Web client for OLAP browsing
OLAP Engine jedox‑olap olap.<chart_name>.<domain> Core OLAP API endpoint
PSF jedox‑psf psf.<chart_name>.<domain> Entry point for Excel 365 connector
Apache Gateway jedox‑apache <chart_name>.<domain> Single‑entry for web UI
OData jedox-odata odata.<chart_name>.<domain> Web client for OData

TLS strategy (choose one):

The ListenerSet serves <chart_name>.<domain> and *.<chart_name>.<domain> with a single Kubernetes TLS Secret, referenced in global.gatewayFabric.tlsSecretName. The certificate must cover both names or every FQDN from the above table.

Option Mechanism
A. Automated via cert‑manager Define an Issuer / ClusterIssuer in values.yaml. cert-manager requests and renews the certificate and stores it in the Secret tls-<release-name>. Set global.gatewayFabric.tlsSecretName to this same name.
B. Manual Secret reference Create and renew the certificate yourself (internal CA or OpenSSL) and store it as a Kubernetes TLS Secret in the Jedox namespace. Reference the Secret name in global.gatewayFabric.tlsSecretName.

Every Jedox endpoint must be reachable via a DNS‑resolvable FQDN and protected with TLS that meets your organization’s security policies. This can be either deployed automatically by the Cert Manager or manually via Kubernetes Secrets.

Excel COM Add-in certificate requirements:

If you use the Jedox Excel COM Add-in, the entire certificate chain used by the Jedox endpoints must be classified as trusted on the client workstations. The add-in stores certificates locally at: C:\Program Files (x86)\Jedox\Jedox Clients\excel-addin\cert\. The client.pem file must include the complete CA chain issued by your OLAP TLS certificate. Your CA must be appended at the end of the client.pem file (any existing certificates in the file must not be removed).

Step 7: Docker images

Our commitment to providing a seamless user experience includes the automatic release of Docker images whenever improvements are made. The updated Docker image is automatically released during scheduled overnight processes, ensuring you wake up to the latest, most stable version.

Your environment must successfully authenticate to the Jedox Container Registry using login credentials in the form of a username/password. If you consider using an internal container registry, in which you duplicate the images provided by Jedox, only authentication via username/password is supported.

Step 8: Set up PSQL or MSSQL database

How to set up PostgreSQL or Microsoft SQL connection for a Jedox instance using your own infrastructure:

A. Set up database and schema

1. Create a dedicated database and schema:

  • The name of the database and the schema must be identical.
  • Each Jedox instance requires its own database.
  • Ideally, the database and schema are named the same as the namespace where Jedox is deployed.

2. Create a user with administrative rights:

  • This user must have full control over the database and the schema.
  • They should be able to manage tables, indexes, and objects.
  • If you have multiple Jedox instances, each instance must have its own dedicated user.
  • Ideally, the user will be given the same name as the namespace where Jedox is deployed.

An example for the execution of commands within PostgreSQL (PSQL):

Copy
-- 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;

B. Configure the PostgreSQL connection in Helm

If you are deploying Jedox using Helm, define the PostgreSQL connection in the values.yaml file:

Copy
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  

C. Quick check

Execute the following command inside PostgresSQL using the jedox_admin user.

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

 


An example for the execution of commands within Microsoft SQL (MSSQL):

Copy
-- Step 1: Create the database
CREATE DATABASE jedox
GO
 
-- Step 2: Use the new database
USE jedox
GO

-- Step 3: Create a schema with the same name as the database
CREATE SCHEMA jedox
GO
 
-- Step 4: Create a login and user with a secure password
CREATE LOGIN jedox WITH PASSWORD = 'your_secure_password'
GO
 
CREATE USER jedox FOR LOGIN jedox
GO
 
-- Step 5: Set the user as the owner of the schema
ALTER AUTHORIZATION ON SCHEMA::jedox TO jedox
GO
 
-- Step 6: Grant full privileges to the user
ALTER ROLE db_owner ADD MEMBER jedox
GO
 
ALTER USER jedox WITH DEFAULT_SCHEMA = jedox
GO

B. Configure the MSSQL connection in Helm

If you are deploying Jedox using Helm, define the MSSQL connection in the values.yaml file:

Copy
# Only external MSSQL can enabled.
# Use an external MSSQL server
# Available for Jedox 25.1 and above
mssql:
  enabled: false
  #
  # MSSQL init details (required)
  #
  # for BYOI, this is the hostname or IP for the MSSQL DB (required)
  databaseHost:
  #
  # for BYOI, this is the name of the database you've defined in the MSSQL server (the DB schema should have the same name)
  databaseName:
  #
  # MSSQL username (required)
  databaseUser:
  #
  # MSSQL password (required)
  databasePassword:
  #
  # for BYOI, this is the port for the MSSQL DB (required)
  databasePort: 1433
  #
  # MSSQL trustServerCertificate (default is true)
  trustServerCertificate:
  #
  # MSSQL encrypt (default is false)
  encrypt:

C. Quick check

To verify connectivity and object creation, log in with the configured user and run:

Copy
SELECT * FROM INFORMATION_SCHEMA.TABLES

 


If both return results, the database and the schema are available.

Jedox supports connecting to Microsoft SQL Server / PostgreSQL only via an SQL authentication account (username and password). Windows or Active Directory–based authentication are not supported.

 

Updated October 29, 2026