JAVA_OPTS in jenkins k8s deployment, does not seem to take into account -Xss (stack size)

[Pantelis Karamolegkos]

In my jenkins deployment (for which I am using the official helm chart

        - name: JAVA_OPTS

          value: |

            -Djava.awt.headless=true -Dorg.csanchez.jenkins.plugins.kubernetes.PodTemplate.connectionTimeout=180 -Dhudson.slaves.NodeProvisioner.initialDelay=0 -Xss512k

but when I log in to the pod:

jenkins@jenkins-cd-5f4b845c5d-cd877:/$ java -XX:+PrintFlagsFinal -version | grep ThreadStackSize

     intx CompilerThreadStackSize                   = 0                                   {pd product}

     intx ThreadStackSize                           = 1024                                {pd product}

     intx VMThreadStackSize                         = 1024                                {pd product}

why the -Xss512k has no effect and the ThreadStackSize remains at 1M?

[Vincent Latombe]

JAVA_OPTS is being passed only to the java process running Jenkins. If you run blindly java in the same container, it won't pick up any of the arguments you specified unless you explicitly pass it JAVA_OPTS.

Vincent

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c1cfc6df-757b-45a6-8377-67bbe5b4fb0eo%40googlegroups.com.