search

opensearch-project / helm-charts

:wheel_of_dharma: A community repository for Helm Charts of OpenSearch Project.
https://opensearch.org/docs/latest/opensearch/install/helm/
Apache License 2.0
170 stars 228 forks source link

[BUG][opensearch] ARM support Amazon base image #534

Closed mrboogiee closed 5 months ago

mrboogiee commented 6 months ago

Describe the bug A clear and concise description of what the bug is. I am attempting to deploy the opensearch helm chart on a SoC using a Rockchip RK3588 CPU and I run into the following issue with the configfile statefulset (I expect the same issue on other CPUs as the RK3588 is still quite new - 2 years old):

Found 3 pods, using pod/opensearch-cluster-master-0
Fatal glibc error: This version of Amazon Linux requires a newer ARM64 processor
                   compliant with at least ARM architecture 8.2-a with Cryptographic
                   extensions. On EC2 this is Graviton 2 or later.

To Reproduce Steps to reproduce the behavior:

helm install --namespace=opensearch --create-namespace opensearch opensearch/opensearch --values=values.yaml
kubectl logs -n opensearch statefulsets/opensearch-cluster-master configfile

Expected behavior A clear and concise description of what you expected to happen. I expected Opensearch to run on my k8s environment where the base image would be more open to chipsets commonly used or desired by the community.

Chart Name have been able to backtrace the issue till helm chart version 2.14.0 so far but then in the pods instead of in the statefulset

Screenshots n/a

Host/Environment (please complete the following information):

Additional context Add any other context about the problem here.

DandyDeveloper commented 5 months ago

This won't be anything to do with the helm chart and is everything to with the image build, which are all managed through here: https://github.com/opensearch-project/OpenSearch/blob/d202d90df3991daaf3e20be325cac4b323f0ed23/distribution/docker/src/docker/Dockerfile#L4

I can't find exactly where this would have changed, but if you're desperate, I'd recommend using an older tag version of the image. There's probably a good reason for introducing this change on the base image in Opensearch, but I can't find it anywhere at the moment.