Skip to content

feat: add extra_environment support to the GeoNetwork Elasticsearch deployment - #244

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

edevosc2c merged 1 commit into
mainfrom
feat/elasticsearch-extra-environment

Conversation

@edevosc2c

@edevosc2c edevosc2c commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Summary

Add extra_environment support to the GeoNetwork Elasticsearch deployment (georchestra.webapps.geonetwork.elasticsearch.extra_environment), the same way the other webapps (console, gateway, geoserver…) already support it.

Until now the env list of the Elasticsearch container was hardcoded, so there was no way to pass extra environment variables (e.g. additional JVM options through JAVA_TOOL_OPTIONS).

georchestra:
  webapps:
    geonetwork:
      elasticsearch:
        extra_environment:
          - name: MY_VARIABLE
            value: "my-value"

Changes

  • templates/geonetwork/elasticsearch/es-deployment.yaml: render extra_environment after the built-in env vars
  • values.yaml: add extra_environment: [] default for elasticsearch
  • Chart version bumped to 1.21.0, CHANGELOG updated

Testing

  • helm lint georchestra passes
  • helm template without extra_environment: rendered manifest unchanged
  • helm template with extra_environment: variables appended to the container env list

…eployment

Allows passing extra environment variables to the Elasticsearch container,
like the other webapps already do. Useful for example to set
JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics as a mitigation for
CVE-2026-114938 (Java4Shell), since ES_JAVA_OPTS is hardcoded in the template.

Bump chart version to 1.21.0.
@edevosc2c
edevosc2c merged commit e4c4f5c into main Nov 18, 2026
1 check passed
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