I don't use the library for long, so I can't help

It'll be much faster to fork this repo and create your own helm chart

Chart version: 8.5.1 Kubernetes version: 1.24 Kubernetes provider: E.g. GKE (Google Kubernetes Engine) EKS Helm Version: 3

Describe the bug: Logstash does not respect logstashJavaOpts value Steps to reproduce:

1. Set logstashJavaOpts: "-Xmx1500m -Xms1500m"
2. Install release
3. See env

    - env:
        - name: LS_JAVA_OPTS
          value: '-Xmx1500m -Xms1500m'

4. But logstash logs are

[INFO ][logstash.runner          ] JVM bootstrap flags: [-Xms1g, -Xmx1g,

Because of

$ cat /usr/share/logstash/config/jvm.options | grep -i xm
# Xms represents the initial size of total heap space
# Xmx represents the maximum size of total heap space
-Xms1g
-Xmx1g

Expected behavior: Java should run with LS_JAVA_OPTS instead Provide logs and/or server output (if relevant):

Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting

Any additional context:

Chart version: 8.5.1 Kubernetes version: 1.24 Kubernetes provider: E.g. GKE (Google Kubernetes Engine) EKS Helm Version: 3

Describe the bug: Logstash does not respect logstashJavaOpts value Steps to reproduce:

1. Set logstashJavaOpts: "-Xmx1500m -Xms1500m"
2. Install release
3. See env

    - env:
        - name: LS_JAVA_OPTS
          value: '-Xmx1500m -Xms1500m'

4. But logstash logs are

[INFO ][logstash.runner          ] JVM bootstrap flags: [-Xms1g, -Xmx1g,

Because of

$ cat /usr/share/logstash/config/jvm.options | grep -i xm
# Xms represents the initial size of total heap space
# Xmx represents the maximum size of total heap space
-Xms1g
-Xmx1g

Expected behavior: Java should run with LS_JAVA_OPTS instead Provide logs and/or server output (if relevant):

Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting

Any additional context:

Still an issue

What changes were proposed in this pull request?

(Please fill in changes proposed in this fix)

How was this patch tested?

(Please explain how this patch was tested. E.g. helm upgrade on minikube, helm install on gke)

Update values.yaml

@nam-co nope(