sonicaj 4d80c5ac5c Publish new changes in catalog 1 anno fa
..
charts 4d80c5ac5c Publish new changes in catalog 1 anno fa
ci 4d80c5ac5c Publish new changes in catalog 1 anno fa
migrations 4d80c5ac5c Publish new changes in catalog 1 anno fa
templates 4d80c5ac5c Publish new changes in catalog 1 anno fa
Chart.lock 4d80c5ac5c Publish new changes in catalog 1 anno fa
Chart.yaml 4d80c5ac5c Publish new changes in catalog 1 anno fa
README.md 4d80c5ac5c Publish new changes in catalog 1 anno fa
app-readme.md 4d80c5ac5c Publish new changes in catalog 1 anno fa
ix_values.yaml 4d80c5ac5c Publish new changes in catalog 1 anno fa
metadata.yaml 4d80c5ac5c Publish new changes in catalog 1 anno fa
questions.yaml 4d80c5ac5c Publish new changes in catalog 1 anno fa

README.md

Elastic Search

During the installation process, a container will be launched with root privileges. This is required in order to apply the correct permissions to the Elastic Search data directory. Afterward, the Elastic Search container will run as a non-root user (default 568).

If you want to apply additional configuration you can by using additional environment variables.

See the Elastic Search documentation for more information.