@parenko.dev
Reposted
A "user story" (the unit of work) describes a user's problem, not a solution. Anything we build that moves us toward a solution to that problem is fine.
December 18, 2025 at 12:09 AM
A "user story" (the unit of work) describes a user's problem, not a solution. Anything we build that moves us toward a solution to that problem is fine.
I had experimented and used -XX:InitialRAMPercentage=60 for the pods. After running a Java command in the terminal, the pod was oomkilled. Because JDK_JAVA_OPTIONS used by every JDK tool. So I wondered if it was possible to use the var only once, to avoid such trap and still remain flexible.
September 13, 2025 at 9:12 PM
I had experimented and used -XX:InitialRAMPercentage=60 for the pods. After running a Java command in the terminal, the pod was oomkilled. Because JDK_JAVA_OPTIONS used by every JDK tool. So I wondered if it was possible to use the var only once, to avoid such trap and still remain flexible.
Well, you can't remove the environment variable after the container starts. Only during your terminal session - if you don't forget.
September 13, 2025 at 5:45 PM
Well, you can't remove the environment variable after the container starts. Only during your terminal session - if you don't forget.
You mean eg ```ENV JDK_JAVA_OPTIONS="-Xmx512m -XX:+UseG1GC"
ENTRYPOINT ["/bin/sh", "-c", "java -jar app.jar && unset JDK_JAVA_OPTIONS"]```. Or in Terminal at the beginning.
ENTRYPOINT ["/bin/sh", "-c", "java -jar app.jar && unset JDK_JAVA_OPTIONS"]```. Or in Terminal at the beginning.
September 12, 2025 at 8:39 AM
You mean eg ```ENV JDK_JAVA_OPTIONS="-Xmx512m -XX:+UseG1GC"
ENTRYPOINT ["/bin/sh", "-c", "java -jar app.jar && unset JDK_JAVA_OPTIONS"]```. Or in Terminal at the beginning.
ENTRYPOINT ["/bin/sh", "-c", "java -jar app.jar && unset JDK_JAVA_OPTIONS"]```. Or in Terminal at the beginning.
Is there also a way to delete this environment variable after use? So that it is not used again when calling Java in the terminal and the pod is possibly killed because too much memory was allocated.
September 12, 2025 at 4:39 AM
Is there also a way to delete this environment variable after use? So that it is not used again when calling Java in the terminal and the pod is possibly killed because too much memory was allocated.