Merge pull request #1231 from qdrant/chore/bashofmann/private-cloud-u…

…pdate

Update docs for new private cloud version

qdrant-landing/content/documentation/private-cloud/private-cloud-setup.md

@@ -13,13 +13,13 @@ weight: 1
 <aside role="status">Network storage systems like NFS or object storage systems such as S3 are not supported.</aside>
 
 - **Permissions:** To install the Qdrant Kubernetes Operator you need to have `cluster-admin` access in your Kubernetes cluster.
-- **Locations:** By default, the Qdrant Cloud Agent and Operator pulls Helm charts and container images from `registry.cloud.qdrant.io`.
+- **Locations:** By default, the Qdrant Operator Helm charts and container images are served from `registry.cloud.qdrant.io`.
 
 > **Note:** You can also mirror these images and charts into your own registry and pull them from there.
 
 ### CLI tools
 
-During the onboarding, you will need to deploy the Qdrant Kubernetes Operator and Agent using Helm. Make sure you have the following tools installed:
+During the onboarding, you will need to deploy the Qdrant Kubernetes Operator using Helm. Make sure you have the following tools installed:
 
 * [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
 * [helm](https://helm.sh/docs/intro/install/)
@@ -37,7 +37,8 @@ Container images:
 Open Containers Initiative (OCI) Helm charts:
 
 - `registry.cloud.qdrant.io/qdrant-charts/qdrant-private-cloud`
-
+- `registry.cloud.qdrant.io/library/qdrant-operator-crds`
+- 
 ### Mirroring images and charts
 
 To mirror all necessary container images and Helm charts into your own registry, you can either use a replication feature that your registry provides, or you can manually sync the images with [Skopeo](https://github.com/containers/skopeo):
@@ -66,6 +67,7 @@ To sync all helm charts:
 
 ```shell
 skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/qdrant-charts/qdrant-private-cloud your-registry.example.com/qdrant-charts/qdrant-private-cloud
+skopeo sync --all --src docker --dest docker registry.cloud.qdrant.io/library/qdrant-operator-crds your-registry.example.com/qdrant-charts/qdrant-operator-crds
 ```
 
 During the installation or upgrade, you will need to adapt the repository information in the Helm chart values. See [Private Cloud Configuration](/documentation/private-cloud/configuration/) for details.
@@ -78,7 +80,8 @@ Once you are onboarded to Qdrant Private Cloud, you will receive credentials to
 kubectl create namespace qdrant-private-cloud
 kubectl create secret docker-registry qdrant-registry-creds --docker-server=registry.cloud.qdrant.io --docker-username='your-username' --docker-password='your-password' --namespace qdrant-private-cloud
 helm registry login 'registry.cloud.qdrant.io' --username 'your-username' --password 'your-password'
-helm upgrade --install qdrant-private-cloud oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-private-cloud --namespace qdrant-private-cloud --version 0.1.0
+helm upgrade --install qdrant-private-cloud-crds oci://registry.cloud.qdrant.io/library/qdrant-operator-crds --namespace qdrant-private-cloud --version 1.2.6 --wait
+helm upgrade --install qdrant-private-cloud oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-private-cloud --namespace qdrant-private-cloud --version 0.1.1
 ```
 
 For a list of available versions consult the [Private Cloud Changelog](/documentation/private-cloud/changelog/).
@@ -91,5 +94,8 @@ To uninstall the Qdrant Private Cloud solution, you can use the following comman
 
 ```bash
 helm uninstall qdrant-private-cloud --namespace qdrant-private-cloud
+helm uninstall qdrant-private-cloud-crds --namespace qdrant-private-cloud
 kubectl delete namespace qdrant-private-cloud
 ```
+
+Note that uninstalling the `qdrant-private-cloud-crds` Helm chart will remove all Custom Resource Definitions (CRDs) will also remove all Qdrant clusters that were managed by the operator.