Sebastian Woehrl

Hi @karthikbattaram. What version of the helm chart and the operator docker image (if in doubt do a `kubectl describe` on the operator pod and check its image tag) are...

That explains it, v1.0 has the bug where some fields were ignored by the operator. Can you try changing the image tag to v1.1?

Hi @NoorKumar . Can you share your cluster yaml? If you are running `main` from git, then imagePullSecrets should work. Can you please also check your `OpensearchCluster` spec after creating...

In that case, @NoorKumar it is not the bug I mentioned previously. Can you check the started pods (`my-cluster-master-0` and so on) if they have the imagePullSecrets in their specs?

@NoorKumar If the pods have the impagePullSecret then I suspect the problem lies not with the operator but more with the kubernetes cluster or the pullSecret itself.

Hi @ccodreanu. You are right, it is not supported currently. And IMO I don't see this as a feature as the main job of the operator is deploying and managing...

Fixed with PR #250

Hi @robcxyz. Each opensearch pod is deployed with an init container called `init-sysctl` that sets `vm.max_map_count` to the higher value to avoid precisely this error message. Can you check the...

Hi @robcxyz . I forgot that the init container I mentioned is not run by default. Can you please add the following to your cluster spec and try again?: ```yaml...

> Was planning on submitting a PR anyways after I successfully deployed the cluster, should this be included in the docs? Yes, good idea, this should be part of the...