Configuration Assistant
Answer the questions below and the assistant assembles every file that the Production Deployment guide has you create: the Helm values for GoodData.CN and Pulsar, the size profile you pick, and the Organization custom resource. The values it asks for (the database endpoint, the bucket names, the IAM role, the hostnames) come from the cloud resources you create in the earlier steps of the Production Deployment guide, so keep that guide open as you answer. The assistant runs entirely in your browser, so nothing is sent anywhere. Review the generated files, replace any remaining placeholders, then download them one at a time or all at once.
Your answers stay in this browser so that you can leave the page and come back to them. Passwords and access keys are the exception: the assistant never stores them, so those fields reset to their example values every time you load the page.
What the assistant doesn’t do
The assistant writes configuration files. You still create everything around them, as described in Production Deployment:
- Create the cloud resources: the metadata database, the object storage buckets or containers, and the workload identity.
- Create the namespace, the license secret, and the encryption keyset secret before you run Helm.
- Connect your identity provider and create users.
Every value the chart accepts is listed in the Helm Chart Values Reference.
1. Shared answers
These answers feed more than one file, so they are asked once here instead of on the file tabs. The cloud and the storage authentication method also decide which files the assistant writes at all.
trust-policy.json and s3-policy.json are written.Object storage
GoodData.CN needs three separate buckets or containers. You created them in step 3.2 Object storage of the Production Deployment guide.
Size profile and options
Organization hostnames
2. Files
One tab per file, listed down the side in the order you apply them. Each tab asks only for what that file needs and shows the file itself, updating as you type. Four of the files need nothing beyond step 1, so those tabs show the file alone. Review every file before you apply it, and replace every remaining placeholder: the Production Deployment guide walks you through installing with them.
The IRSA trust policy for the gooddata-cn service account. Pass it to aws iam create-role, then attach the S3 policy to the role it creates.
https:// prefix.From step 1
- Cloud and the S3 authentication method decide whether this file exists at all.
trust-policy.json
s3-policy.json
pulsar-values.yaml
pulsar-values-sizing.yaml
The GoodData.CN chart configuration. Most of the form lives here: storage access, the metadata database, the secrets you create outside Helm, ingress, and tracing.
AWS access
access-key-id and secret-access-key.Azure access
S3-compatible access
Metadata PostgreSQL
An external PostgreSQL instance is required. Use the instance you created in step 3.1 Metadata database of the Production Deployment guide.
postgresql-password.Secrets
Both secrets are created outside Helm, before you install the chart.
license key.keySet key produced by tinkey.Ingress and identity
Dex settings
Dex needs its own hostname and a database SSL mode, and lists every organization hostname from step 1 as an allowed origin.
Autoscaling
Observability
See Distributed Tracing for the collector setup.
From step 1
- Cloud and the S3 authentication method — select the whole storage block.
- The three bucket names — export, Quiver cache, and datasource-fs storage.
- Deploy AI features — the GenAI and Qdrant flags.
- Create PodMonitor objects —
podMonitor.enabled. - Organization hostnames — Dex allowed origins, when Dex is the identity provider.
gdcn-values.yaml
gdcn-values-sizing.yaml
The Organization custom resource creates the tenant and its first admin. One organization per hostname from step 1, all in a single file.
The assistant never handles your admin password. Generate the hash yourself with openssl passwd -6 '<ADMIN_PASSWORD>' and paste it over the placeholder in the generated file.
From step 1
- Organization hostnames — one document per line, and the sub-forms above.