feat(kibana): Add support for I18N_LOCALE environment variable #298
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This pull request introduces the ability to configure the Kibana UI language directly via an
I18N_LOCALE
environment variable. This aligns with how other core settings (likeELASTICSEARCH_HOSTS
) are configured in the Docker image, providing a more convenient setup for international users.The Problem
Currently, to change the Kibana display language in a Docker environment, users must create a custom
kibana. yml
file, mount it into the container, and ensure all other necessary configurations are included. This process can be cumbersome, especially in automated or restricted environments where file mounting is not straightforward.The Solution
This PR modifies the
kibana-docker
entrypoint script to:I18N_LOCALE
.i18n. locale
key and value into the/usr/share/kibana/config/kibana. yml
file before Kibana starts.This allows users to simply add
-e I18N_LOCALE="zh-CN"
(or any other locale) to theirdocker run
ordocker-compose. yml
file to set the language, without needing to manage custom configuration files.How to Test This Change
cd kibana
docker build -t kibana-i18n-test .