My Oracle Support Banner

Upgrade Docker Image Tag For ECE Applications (Doc ID 2898076.1)

Last updated on NOVEMBER 15, 2022

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


Customer is trying to update Elastic Charging Engine (ECE) image tag value and running HELM upgrade. Internally ECE is getting upgraded and restarting both Diameter Gateway (DGW) sts at the same time.
This creates a small downtime of ~2-10 minutes. Need to avoid this downtime and need to have them patched one by one.

One way to achieve this could be:
1. Manually upgrade, without using HELM, one diameter gateway sts and change image tag. Use kubectl patch or set image commands.
2. Wait until pods are “restarted” with new image tag.
3. Update image tag in Helm charts and run helm upgrade. Helm should only then upgrade deployments/statefulsets with different image tag.

1.Is this is a valid option to start testing in UAT environments.
2.Is there any alternative options to upgrade ECE image tag and avoid restarting both diameters at the same time.

Note that the only difference between the two images of ECE is that a class of log4j (log4j security vulnerabilities) is zipped.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.