ORY chart

To configure the ORY chart and its sub-charts, override the default values of its values.yaml file. This document describes parameters that you can configure.

TIP: See how to change Kyma settings.

Configurable parameters

This table lists the configurable parameters, their descriptions, and default values:

ParameterDescriptionDefault value
global.postgresql.postgresqlDatabaseSpecifies the name of the database saved in Hydra.db4hydra
global.postgresql.postgresqlUsernameSpecifies the username of the database saved in Hydra.hydra
global.istio.gateway.nameSpecifies the name of the Istio Gateway used in Hydra.kyma-gateway
global.istio.gateway.namespaceSpecifies the Namespace of the Istio Gateway used in Hydra.kyma-system
global.ory.oathkeeper.maester.modeSpecifies the mode in which ORY Oathkeeper Maester is expected to be deployed.sidecar
global.ory.hydra.persistence.enabledSets persistence for Hydra.true
global.ory.hydra.persistence.postgresql.enabledDefines whether Hydra should initiate the deployment of an in-cluster database. Set to false to use a self-provided database. If set to true, Hydra always uses an in-cluster database and ignores the custom database details.true
hpa.oathkeeper.minReplicasDefines the initial number of created Oathkeeper instances.1
hpa.oathkeeper.maxReplicasDefines the maximum number of created Oathkeeper instances.3
hydra.deployment.resources.limits.cpuDefines limits for CPU resources.500m
hydra.deployment.resources.limits.memoryDefines limits for memory resources.256Mi
hydra.deployment.resources.requests.cpuDefines requests for CPU resources.100m
hydra.deployment.resources.requests.memoryDefines requests for memory resources.128Mi
hydra.hydra.existingSecretSpecifies the name of an existing Kubernetes Secret containing credentials required for Hydra. A default Secret with random values is generated if this value is not provided."ory-hydra-credentials"
oathkeeper.deployment.resources.limits.cpuDefines limits for CPU resources.100m
oathkeeper.deployment.resources.limits.memoryDefines limits for memory resources.128Mi
oathkeeper.deployment.resources.requests.cpuDefines requests for CPU resources.50m
oathkeeper.deployment.resources.requests.memoryDefines requests for memory resources.64Mi
oathkeeper.oathkeeper-maester.deployment.resources.limits.cpuDefines limits for CPU resources.100m
oathkeeper.oathkeeper-maester.deployment.resources.limits.memoryDefines limits for memory resources.50Mi
oathkeeper.oathkeeper-maester.deployment.resources.requests.cpuDefines requests for CPU resources.50m
oathkeeper.oathkeeper-maester.deployment.resources.requests.memoryDefines requests for memory resources.20Mi
postgresql.resources.requests.memoryDefines requests for memory resources.256Mi
postgresql.resources.requests.cpuDefines requests for CPU resources.250m
postgresql.resources.limits.memoryDefines limits for memory resources.1024Mi
postgresql.resources.limits.cpuDefines limits for CPU resources.750m
postgresql.existingSecretSpecifies the name of an existing secret to use for PostgreSQL passwords."ory-hydra-credentials"
gcloud-sqlproxy.existingSecretSpecifies the name of the Secret in the same Namespace as the proxy, that stores the database password.ory-hydra-credentials
gcloud-sqlproxy.existingSecretKeySpecifies the name of the key in the Secret that contains the GCP service account JSON key.gcp-sa.json

TIP: See the original ORY, ORY Oathkeeper, PostgreSQL, and GCP SQL Proxy helm charts for more configuration options.