TTK Helm - The pods are not being restarted when the configmap changes

[vijayg10]

Summary:

Testing-toolkit (TTK) Backend pods do not restart after changes are made to the TTK's config via a Helm Upgrade.

Work around is to manually restart the pod for the config to take effect.

Severity:
Low

Priority:
Low

Expected Behavior

Testing-toolkit (TTK) Backend pods should auto-restart via a rolling update once changes are made to the TTK's config via a Helm Upgrade.

Steps to Reproduce

1. Install Helm v13.0.1 release
2. Modify TTK Backend Config (for example add a new parameter to the default environment config)
3. Run Helm update command
4. The changes will only to effect once the TTK Backend pod is manually restarted

Specifications

• Component (if known): TTK Backend Helm Chart
• Version: v13.0.1
• Platform: Helm
• Subsystem: n/a
• Type of testing: Helm
• Bug found/raised by: @vijayg10

Notes:

• Severity when opened: Low
• Priority when opened: Low

[mdebarros]

Supported Helm chart changes included in Mojaloop Helm v13.0.2 Release closed by mojaloop/helm/pull/448.