Dhiraj Kumar Jain

Hi @chandranshu7 Can you add some more details in the PR?

I am still of the opinion to have release branches for charts 😄 The maintainers can branch out from `main` and have releases enabled only on branches apart from `main`.

I guess @peterzhuamazon means Kubernetes Operator Support here. If that is the case we should change the issue title in my opinion.

@DandyDeveloper Nvm, I guess I misinterpreted your previous comment 😅 , operator is same as Kubernetes Operator , it is just how some people call it. Nothing differently. [Example](https://www.redhat.com/en/topics/containers/what-is-a-kubernetes-operator) You...

> @TheAlgo Your link on the second part is wrong Updated the link 😄

I completely agree to this and it is kind of compulsory. I also wanted to have something like [this](https://github.com/opensearch-project/opensearch-devops/blob/main/Helm/opensearch/values.yaml#L314) included in readiness as well for opensearch apart from the ones...

> That would be clever, do we want to include a sane default, or would we want to leave it disabled until the user chooses to enable it? What if...

@sastorsl As far as I know the probes that are added are not present in the [statefulset](https://github.com/opensearch-project/helm-charts/blob/main/charts/opensearch/templates/statefulset.yaml). I will take a look and fix it.

@bitnik I agree with you. Readiness is a must for production use cases, it can be a basic one but it is must. It already exists in opensearch chart but...

Add Dial algorithm in python