opensearch-k8s-operator: [BUG] helm repo not found

What is the bug?

Run:

helm repo add opensearch-operator https://opster.github.io/opensearch-k8s-operator/

The operation fails as https://opster.github.io/opensearch-k8s-operator/ returns a 404 since the 1st of December or so.

How can one reproduce the bug?

helm repo add opensearch-operator https://opster.github.io/opensearch-k8s-operator/

What is the expected behavior?

The chart repo should be added.

What is your host/environment?

MacOS Sonoma

Do you have any screenshots?

n/a

Do you have any additional context?

I understand the operator is not in this repository but it is referenced by the official documentation.

About this issue

  • Original URL
  • State: closed
  • Created 7 months ago
  • Reactions: 4
  • Comments: 18 (1 by maintainers)

Commits related to this issue

Most upvoted comments

Hey Everyone, the operator repo was transferred to the opensearch org recently, We will make an announcement and we will ensure the helm install instructions as updated well. Thanks everyone for the your patience. Adding @bbarani @segalziv

Now that #673 was merged I’ve just verified basic rendering functionality from the helm charts using:

helm repo add opensearch-charts https://opensearch-project.github.io/opensearch-k8s-operator

and

helm template opensearch-operator opensearch-charts/opensearch-operator

And we should be good now. So people using the chart previously should be able to update the repo url to https://opensearch-project.github.io/opensearch-k8s-operator and should be able to carry on as they were.

For some reason, the new repo https://opensearch-project.github.io/opensearch-k8s-operator/ is still directing me to https://Opster.github.io/opensearch-k8s-operator this is kustomize which try to pull it on the fly. seeing below error

Error: failed to fetch https://Opster.github.io/opensearch-k8s-operator/opensearch-operator-2.4.0.tgz : 404 Not Found

Hey Everyone just created an issue to track all the broken operator functionaries https://github.com/opensearch-project/opensearch-k8s-operator/issues/674#issue-2025017085, please add your thoughts to the issue created. Thank you

Thanks @ammmze, @fabiocorneti and other i’m closing this issue, please re-open if required. Thanks

@wbeckler the opster repo redirects to this, and the issues etc. are all here - I think it’s been moved rather than forked.

I think this fork of Opster’s operator should solve the problem: https://github.com/eliatra/opensearch-k8s-operator