FDP API does not pick up `application.yml` configuration changes without rebuilding the Kubernetes deployment

[hcvdwerf]

What components are related to the issue?

No response

Which FDP are you using?

No response

Version

1.18.2

What happened?

Description

Changes to the application.yml configuration of the FDP API are not picked up by the running deployment in Kubernetes.

When modifying configuration settings (for example enabling OpenTelemetry (OTEL) logging), the changes are not applied after restarting the FDP pod. Instead, we need to rebuild and redeploy a new FDP instance before the configuration is applied.

Observed behaviour

• application.yml configuration is modified
• Restarting the FDP pod does not apply the new configuration
• Only after rebuilding and redeploying the FDP instance are the configuration changes applied

Expected behaviour

Configuration changes in application.yml should be applied after a pod restart (for example after updating a ConfigMap or restarting the deployment), without requiring a full rebuild of the FDP container or Kubernetes deployment.

Example

We attempted to configure OpenTelemetry logging through application.yml.

After updating the configuration:

• Restarting the FDP pod did not apply the changes
• Rebuilding and redeploying the FDP instance was required for the configuration to take effect

Question

Is the application.yml configuration baked into the container image, or should it be possible to change configuration via Kubernetes without rebuilding the FDP deployment?

Environment

• FDP API deployed in Kubernetes
• Configuration managed via application.yml

Relevant log output