From d9dadeadf7bb481d784265c0be40f7c970782c6d Mon Sep 17 00:00:00 2001
From: calyptia-ci <98808777+calyptia-ci@users.noreply.github.com>
Date: Mon, 26 Feb 2024 18:10:56 +0000
Subject: [PATCH] ci: update Calyptia Cloud Standalone chart from latest
 version internally (#220)

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: patrick-stephens <6388272+patrick-stephens@users.noreply.github.com>
---
 charts/calyptia-cloud-standalone/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/charts/calyptia-cloud-standalone/README.md b/charts/calyptia-cloud-standalone/README.md
index ba1c151..c9155f6 100644
--- a/charts/calyptia-cloud-standalone/README.md
+++ b/charts/calyptia-cloud-standalone/README.md
@@ -62,7 +62,7 @@ Postgres volumes can be set up using the `cloudApi.postgres.extraVolumes` and `c
 The chart auto-deploys the Calyptia Core operator and CRD charts by default.
 This includes CRD configuration but note Helm has caveats on managing existing CRDs.
 Any upgrade should first ensure the correct CRDs are installed via `kubectl replace -f crd.yaml`.
-The CRD YAML files are available on the specific release being installed here: <https://github.com/calyptia/core-operator-releases/>
+The CRD YAML files are available on the specific release being installed here: <https://github.com/chronosphereio/calyptia-core-operator-releases/>
 
 If CRDs are removed then all workloads associated with them will also be destroyed (but will be recreated when the CRD is added again if the config is in the database).