Skip to content

feat: add extra_java_opts to the GeoNetwork Elasticsearch deployment - #245

Merged
edevosc2c merged 1 commit into
mainfrom
feat/elasticsearch-extra-java-opts
Nov 18, 2026
Merged

edevosc2c merged 1 commit into
mainfrom
feat/elasticsearch-extra-java-opts

Conversation

@edevosc2c

Copy link
Copy Markdown
Member

Summary

Add an extra_java_opts value to the GeoNetwork Elasticsearch deployment (georchestra.webapps.geonetwork.elasticsearch.extra_java_opts). It is appended to the ES_JAVA_OPTS environment variable, after the built-in log4j options.

Elasticsearch ignores JAVA_TOOL_OPTIONS and _JAVA_OPTIONS (they are unset by bin/elasticsearch-env), so extra_environment cannot be used to pass JVM options, and ES_JAVA_OPTS was hardcoded in the template.

georchestra:
  webapps:
    geonetwork:
      elasticsearch:
        extra_java_opts: "-Xlog:gc"

Changes

  • templates/geonetwork/elasticsearch/es-deployment.yaml: append extra_java_opts to ES_JAVA_OPTS
  • values.yaml: add extra_java_opts: "" default for elasticsearch
  • Chart version bumped to 1.22.0, CHANGELOG updated

Testing

  • helm lint georchestra passes
  • helm template without extra_java_opts: ES_JAVA_OPTS unchanged
  • helm template with extra_java_opts: options appended to ES_JAVA_OPTS

Elasticsearch ignores JAVA_TOOL_OPTIONS and _JAVA_OPTIONS (they are unset
by bin/elasticsearch-env), so extra JVM options must go through
ES_JAVA_OPTS, which is hardcoded in the template. The new extra_java_opts
value is appended to it.

Bump chart version to 1.22.0.
@edevosc2c
edevosc2c merged commit 61de7cf into main Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant