We aim to configure -XX:MaxRAMPercentage=50.0 specifically on the worker deployments within our environment. However, we encounter a challenge as JAVA_OPTS have been globally set across all deployments through the extraEnv configuration, which includes a specific setting for logback configuration file path.
Current Configuration
Currently, JAVA_OPTS are globally set for all deployments as follows:
We need to apply -XX:MaxRAMPercentage=50.0 to the workers to better manage their JVM memory usage. However, we want to avoid altering the existing JAVA_OPTS for other deployments, which could lead to unintended changes in their configurations, especially concerning logging.
Requested Feature/Enhancement
The ability to append or set specific JAVA_OPTS for individual deployments without impacting the global settings defined in extraEnv. This feature should allow us to:
Set -XX:MaxRAMPercentage=50.0 exclusively on the worker deployments.
Preserve the global JAVA_OPTS settings for other deployments, ensuring no disruption in their configurations, particularly regarding logging.
Hi !
Description
We aim to configure
-XX:MaxRAMPercentage=50.0specifically on the worker deployments within our environment. However, we encounter a challenge asJAVA_OPTShave been globally set across all deployments through theextraEnvconfiguration, which includes a specific setting for logback configuration file path.Current Configuration
Currently,
JAVA_OPTSare globally set for all deployments as follows:Issue
We need to apply
-XX:MaxRAMPercentage=50.0to the workers to better manage their JVM memory usage. However, we want to avoid altering the existingJAVA_OPTSfor other deployments, which could lead to unintended changes in their configurations, especially concerning logging.Requested Feature/Enhancement
The ability to append or set specific
JAVA_OPTSfor individual deployments without impacting the global settings defined inextraEnv. This feature should allow us to:-XX:MaxRAMPercentage=50.0exclusively on the worker deployments.JAVA_OPTSsettings for other deployments, ensuring no disruption in their configurations, particularly regarding logging.