-
Notifications
You must be signed in to change notification settings - Fork 218
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 does not get deployed #844
Comments
@sfisli , few questions.
|
|
[Triage] |
@prudhvigodithi same issue, new yaml:
|
Hey @sfisli can you share your |
@prudhvigodithi
admin-credentials-secret:
|
Thanks @sfisli, works for me, I have matched the config keys used in the provided yaml, was able to access the dashboard and cluster, can you please check the following information?
Thank you |
@prudhvigodithi the config i provided worked on other clusters v1.27.x , do you think the operator isn't compatible with 1.26.x ? |
@sfisli when you added |
@prudhvigodithi i'am talking about the k8s cluster. |
I dont see any restriction within the operator on 1.26.x version of k8s cluster, adding @swoehrl-mw @salyh. |
There are no explicit restrictions to k8s version for the operator. We do not test all versions but I know of nothing that would limit it on k8s 1.26.x, every k8s feature the operator uses should be stable and unchanged between these versions. As a sidenote: 1.26 is EOL for some months already, so you should not use that version anymore anyway. |
Hi, same problem here with a test cluster:
Apparently some config secret is missing, but as this was a test cluster I was expecting to get something autogenerated, or actually ignored, since I disabled all tls options. EDIT:
|
What is the bug?
the opensearch cluster does not get deployed.
What is the expected behavior?
opensearch cluster up and running ( nodes and dashbaord)
What is your host/environment?
Bare Metal Kubernetes v1.26.7
Do you have any additional context?
Operator-values.yaml :
opensearch-cluster.yaml:
security-config.yaml :
Waiting to connect to the cluster
Operator logs:
The text was updated successfully, but these errors were encountered: