Changes in values.yaml for AC v4.2.4

The values.yaml file for AC v4.2.4 has got the following changes when compared to that for AC v4.2.3.

New environment variables added

  1. A new section configManagement that contains the following environment variables has been added. For more details about these variables, refer to this page.

    • CONFIG_MANAGEMENT_ENABLED

    • PROFILE

    • CONFIG_MANAGEMENT_SEGREGATION_CRITERIA

    • HASHICORP_VAULT_ENABLED

    • HASHICORP_VAULT_KV_VERSION

    • HASHICORP_VAULT_SECRET_PATH_PATTERN

    • HASHICORP_VAULT_URL

    • HASHICORP_VAULT_SECRET_BASE_PATH

    • HASHICORP_VAULT_AUTHENTICATION

    • HASHICORP_VAULT_TOKEN

    • HASHICORP_VAULT_KUBERNETES_ROLE

    • HASHICORP_VAULT_KUBERNETES_SERVICE_ACC_TOKEN_PATH

    • HASHICORP_VAULT_KUBERNETES_PATH

  2. A new environment variable DELETE_JOB_AFTER_EXECUTION has been added in the migration section with its default value as true. You can set the value for this variable to false if you don't want the migration job and its corresponding pod to be deleted after the execution completes.

  3. A new environment variable DELETE_JOB_AFTER_EXECUTION has been added in the license section with its default value as true. You can set the value for this variable to false if you don't want the cleanup job and its corresponding pod to be deleted after the execution completes.

  4. To enable or disable the creation of PDB for rabbitmq, listener, aimap, and license microservices a new environment variable CREATE_PDB has been added in their respective sections. The possible value for this variable can be true or false.
    The default value for this variable for these microservices is given in the following table.

Microservice

Default value for CREATE_PDB

Microservice

Default value for CREATE_PDB

rabbitmq

false

listener

false

aimap

true

license

true

Changes in existing variable’s default values

  1. The default value for the CPU limit and CPU requests in the runtimedeploymentmanager section have been changed as shown in the following screenshot.

  2. The default values for some variables in the startupProbe and readinessProbe subsections of the following microservices have got changes.

Microservice section

startupProbe

readinessProbe

Microservice section

startupProbe

readinessProbe

webrunner

  • timeoutSeconds: 2

  • initialDelaySeconds: 80

  • periodSeconds: 2

  • failureThreshold: 200

No change

portal

  • timeoutSeconds: 2

  • initialDelaySeconds: 55

  • periodSeconds: 2

  • failureThreshold: 200

No change

webappGateway

  • timeoutSeconds: 2

  • initialDelaySeconds: 15

  • periodSeconds: 2

  • failureThreshold: 200

  • timeoutSeconds: 2

  • initialDelaySeconds: 10

  • periodSeconds: 2

soapapi

  • timeoutSeconds: 2

  • initialDelaySeconds: 60

  • periodSeconds: 2

  • failureThreshold: 200

No change

archivalandcleanup

  • timeoutSeconds: 2

  • initialDelaySeconds: 60

  • periodSeconds: 2

  • failureThreshold: 200

No change

listener

  • timeoutSeconds: 2

  • initialDelaySeconds: 60

  • periodSeconds: 2

  • failureThreshold: 200

No change

license

  • timeoutSeconds: 2

  • initialDelaySeconds: 60

  • periodSeconds: 2

  • failureThreshold: 200

No change

restapi

  • timeoutSeconds: 2

  • initialDelaySeconds: 60

  • periodSeconds: 2

  • failureThreshold: 200

No change

event

  • timeoutSeconds: 2

  • initialDelaySeconds: 60

  • periodSeconds: 2

  • failureThreshold: 200

No change

aimap

  • timeoutSeconds: 2

  • initialDelaySeconds: 15

  • periodSeconds: 2

  • failureThreshold: 200

  • timeoutSeconds: 15

  • initialDelaySeconds: 10

  • periodSeconds: 10

apigateway

  • timeoutSeconds: 2

  • initialDelaySeconds: 10

  • periodSeconds: 2

  • failureThreshold: 200

  • timeoutSeconds: 2

  • initialDelaySeconds: 15

  • periodSeconds: 2