From 7520c3a6ed5a6621c3f3f62c4a03e62c6a313df5 Mon Sep 17 00:00:00 2001 From: "opensearch-trigger-bot[bot]" <98922864+opensearch-trigger-bot[bot]@users.noreply.github.com> Date: Fri, 15 Dec 2023 15:02:07 -0800 Subject: [PATCH] Fixing OpenSearch operator helm install (#5865) (#5905) (cherry picked from commit d248daa73609b81dded65398654df5a5ffce7d69) Signed-off-by: David Tippett <17506770+dtaivpp@users.noreply.github.com> Signed-off-by: github-actions[bot] Co-authored-by: github-actions[bot] --- _clients/k8s-operator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_clients/k8s-operator.md b/_clients/k8s-operator.md index 1461b182cd..0cfeca10eb 100644 --- a/_clients/k8s-operator.md +++ b/_clients/k8s-operator.md @@ -21,7 +21,7 @@ If you use Helm to manage your Kubernetes cluster, you can use the OpenSearch Ku To begin, log in to your Kubernetes cluster and add the Helm repository (repo) from [Artifact Hub](https://artifacthub.io/packages/helm/opensearch-operator/opensearch-operator/). ``` -helm repo add opensearch-operator https://opster.github.io/opensearch-k8s-operator/ +helm repo add opensearch-operator https://opensearch-project.github.io/opensearch-k8s-operator/ ``` Make sure that the repo is included in your Kubernetes cluster.