My Oracle Support Banner

CloudNative DGW Process Issue when Kubernetes Cluster Restarts (Doc ID 2933375.1)

Last updated on MARCH 13, 2023

Applies to:

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


In the cloud Native Environment, when the kubernetes cluster is restarted Diameter Gateway (DGW) Process (Pending Status).

When the kubernetes cluster is restarted it will recreate the worker nodes, Hence worker node IP and host name is getting changed. And since customer are using nodename of worker node in the nodeSelector for DGW Process, DGW Process are not able to come up since the nodes are changed.

For this, whenever kubernetes cluster restarts user have to manually update the nodeSelector in override-values.yaml and run helm upgrade.

Note : Once worker node is resatarted all other process are coming up immediately except DGW.

Is there a way to avoid this manual intervention ?


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.