Skip to main content
Version: 4

Extended values.yaml parameters

This document discusses the parameters you need to set in the global values.yaml before deploying the application.

Advanced configurations​

Database Secrets​

In the global > dbPullSecrets section of the values.yaml file, set the values for the parameters discussed below.

Parameter
Description
create

This setting determines whether the Helm chart creates a Kubernetes Secret in the target namespace (and the pods reference it), or whether the pods reference an already existing Secret created outside Helm for database authentication.

✅ true (Default value)

Helm creates a Secret in the same namespace where the chart is deployed.

  • The Secret name defaults to adeptia-db-secret, or can be overridden using the secretName value discussed next in this table.

  • The Secret contents are generated from the values defined under:

    • global > envSecret

  • The Kubernetes pods reference this Secret to obtain the database credentials.

❌ false

Helm does not create any Secret.

  • The Kubernetes pods will instead reference an existing Secret.

  • You must ensure this Secret is created beforehand by another internal or external system such as:

    • HashiCorp Vault / External Secrets Operator

    • a CI/CD pipeline step

    • a platform/team-managed Kubernetes Secret

  • The name of this existing Secret must be provided via secretName.

secretName

The name of the Kubernetes Secret that stores the DB credentials. Pods refer to this Secret for DB credentials.

Default value: adeptia-db-secret

Other additional parameters​

Set the following parameters in the values.yaml:

Section in the values.yaml
Parameter 
Value
Description
global > environmentVariables
WEBAPP_DOMAIN_URL

Enter the URL in the format https:<domain> to be used for accessing the application. Ensure that you enter the URL in single quotes, for example

global > deploymentmanager > runtimeEnvironmentVariables
API_GATEWAY_URL
https://ac-api-publisher-gateway (Default value)
URL to access API Gateway.




 global > webrunner > environmentVariables
DEFAULT_WEBSERVICE_PROTOCOL
https (Default value), http, or ' ' (Empty)

Specifies the protocol used by the REST/SOAP Web Service Provider.
Accepted values:

  • https (default) – The web service will be hosted over HTTPS.

  • http – The web service will be hosted over HTTP.

  • (empty) – When left blank, displays an Enable SSL checkbox in the Web Service Provider wizard. Selecting it shows the port selection field. The protocol is then determined automatically based on the port selected — for example, choosing a secure port (For example, 443) results in HTTPS, while a standard port (For example, 80) results in HTTP.

global > apigateway > environmentVariablesDEFAULT_SERVICE_PORT
  • Any valid port number
  • Default value - 443
Specifies the port number for hosting REST/SOAP Web Service Provider.

After configuring the parameters, refer to this page to continue with the application deployment steps. 

Additional steps for deploying on EKS ​

Additional steps for deploying on ARO​