-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG][Opensearch] It is not possible to deploy the chart with the default settings. #617
Comments
I ran into this problem and fixed it with: singleNode: true
rbac:
create: true
automountServiceAccountToken: true
ingress:
enabled: true
annotations:
traefik.ingress.kubernetes.io/router.entrypoints: web
kubernetes.io/ingress.class: traefik
hosts:
- opensearch.127.0.0.1.sslip.io
config:
opensearch.yml: "" #disable the default due to https://github.com/opensearch-project/helm-charts/issues/617
extraEnvs:
- name: OPENSEARCH_INITIAL_ADMIN_PASSWORD
value: <some-password> for Rancher Desktop |
Can someone give me a working values.yaml configuration? I am facing the same problem with chart versions 2.26.1 and 2.27.0 . I tried with different combinations of: config:
opensearch.yml: ""
# or the default one and with or without extraEnvs:
- name: DISABLE_INSTALL_DEMO_CONFIG
value: "true" (Also tried version 2.25.0 and got a different error: java.lang.IllegalArgumentException: Could not load codec 'Lucene95'. Did you forget to add lucene-backward-codecs.jar?) |
It works for me emptying
|
@StefanSchuhart Could you share the error message that occurs when opensearch.yml is left as an empty string? |
Describe the bug
When deploying the OpenSearch chart with default settings, an error occurs in the Security plugin, causing the deployment to fail.
To Reproduce
When deploying the default chart with only the OPENSEARCH_INITIAL_ADMIN_PASSWORD environment variable set, the deployment fails.
Error Log
Expected behavior
The chart should be deployed successfully with the default settings.
Chart Name
opensearch
Host/Environment (please complete the following information):
Additional context
"It seems that the Security Plugin's demo configuration is not working because the opensearch.yml file is declared in the values.yaml."
In the Security plugin, if the opensearch.yml file is missing, it generates demo certificates. However, since the values.yaml file creates an opensearch.yml file, the plugin skips generating demo certificates, leading to this issue. (See Link)
Previously, the Security Plugin could not detect nested YAML, resulting in the demo configuration of the Security Plugin always being executed. However, it appears that this bug has been fixed with this PR(from Security Plugin release 2.18.0 onwards).
Therefore, it appears that this issue started occurring from the Opensearch chart version 2.27.0.
Would it be okay if I submit a PR for this issue? It seems that commenting out lines 49 to 99 in values.yaml would resolve the problem.
The text was updated successfully, but these errors were encountered: