Container Gateway - Does deploying changes to helm chart values file affect the restart of the Gateway

Products

• CA API Gateway

Issue/Introduction

1) if a config change on the gateway requires a restart, so in the case raised here, changing the javaargs property for enabling and disabling the file sink doesn't come through to policy manager until a restart of the gateway is done. Is this an expected behavior.
2) if there is a way to restart the gateway without the service endpoints IP changing.
3) how to architect this so that even if the service endpoints IP changes we have some stable dns / ip to connect to the gateway.

Environment

11.1

Resolution

If you restart the container that is behind the service, the IP will change (no guarantees  on that) but kubernetes will ensure that calling the service routes you accordingly.

Basically: 1/ changes in the helm charts (such as system.properties) does require gateway restart; 2/ Kubernetes manages the mapping between the IP and the services.