Configu­ring JUDGE Helm Deploy­ments

Customizing with Helm Charts

JUDGE offers flexibility in customizing deployments through Helm charts. You can tailor your deployment according to your specific requirements by overriding default values using Helm.

Using Helm cli args

You can customize the JUDGE umbrella values.yaml file when installing our Helm charts from our registry. Helm allows you to override default values specified in the values.yaml file of the chart during installation. Here's how you can do it:

# JAR (JUDGE Artifact Registry)
helm install judge us-east4-docker.pkg.dev/judge-395516/judge-image-registry/judge-chart --set key1=value1,key2=value2

# aws marketplace ecr
helm install judge oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/testifysec/judge-chart --version 0.2.0 \
    -f values.yaml \
    --set global.registry="709825985650.dkr.ecr.us-east-1.amazonaws.com" \
    --set global.repository="testifysec" \
    --set kratos.kratos.dsn="postgres://${PGUSER}:${PGPASSWORD//,/\\,}@${PGHOST}:${PGPORT}/kratos?max_conns=20&max_idle_conns=4" \
    --set kratos.kratos.config.selfservice.methods.oidc.config.providers[0].client_id="${GITLAB_OIDC_CLIENT_ID}" \
    --set kratos.kratos.config.selfservice.methods.oidc.config.providers[0].client_secret="${GITLAB_OIDC_CLIENT_SECRET}" \
    --set kratos.kratos.config.selfservice.methods.oidc.config.providers[1].client_id="${GITHUB_OIDC_CLIENT_ID}" \
    --set kratos.kratos.config.selfservice.methods.oidc.config.providers[1].client_secret="${GITHUB_OIDC_CLIENT_SECRET}" \
    --set dex.config.connectors[0].config.clientID="${GITLAB_OIDC_CLIENT_ID}" \
    --set dex.config.connectors[0].config.clientSecret="${GITLAB_OIDC_CLIENT_SECRET}" \
    --set judge-api.sqlStore.connectionString="postgres://${PGUSER}:${PGPASSWORD//,/\\,}@${PGHOST}:${PGPORT}/judge" \
    --set archivista.sqlStore.connectionString="postgres://${PGUSER}:${PGPASSWORD//,/\\,}@${PGHOST}:${PGPORT}/archivista" \
    --set judge-api.workflows.signer.kmsUri="awskms:///${WORKFLOWKEYARN}" \
    --set judge-api.workflows.slackIntegration.channelId="${SLACK_CHANNEL_ID}" \
    --set judge-api.workflows.slackIntegration.token="${SLACK_TOKEN}" \
    --set judge-api.dapr.pubsub.sqsQueueNameOverride="${QUEUE_NAME}" \
    --set judge-api.deployment.env[0].value="${TOPIC_NAME}" \
    --set archivista.deployment.env[0].value="${TOPIC_NAME}" \
    --wait

In this command:

• judge is the name you're giving to the release.
• us-east4-docker.pkg.dev/judge-395516/judge-image-registry/judge-chart is the location of the chart in the registry.
• --set allows you to override specific values defined in the values.yaml file. You can specify multiple key-value pairs separated by commas.

Using a Separate YAML File

Alternatively, you can also use a separate YAML file to specify the custom values:

helm install judge us-east4-docker.pkg.dev/judge-395516/judge-image-registry/judge-chart -f values.yaml

In this case, values.yaml contains the custom values you want to override from the default values.yaml file of the chart. This can be very useful when you need to reconfigure many parts of JUDGE.

Configuration Knobs

Below is a table of all the configuration knobs available in JUDGE that you can override to customize your deployment:

You can override these values either directly using --set during installation or by specifying them in a separate YAML file with -f. Adjust these values according to your deployment requirements to optimize the behavior of JUDGE as per your needs.