Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Private Cloud: document different deployment scopes #1349

Merged
merged 3 commits into from
Dec 18, 2024
Merged

Private Cloud: document different deployment scopes #1349

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0a0636d
Private Cloud: document different deployment scopes
bashofmann Dec 18, 2024
4f0254f
Add reason
bashofmann Dec 18, 2024
bb7a576
Fix typo
bashofmann Dec 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions qdrant-landing/content/documentation/private-cloud/private-cloud-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,36 @@ For a list of available versions consult the [Private Cloud Changelog](/document

Especially ensure, that the default values to reference `StorageClasses` and the corresponding `VolumeSnapshotClass` are set correctly in your environment.

### Scope of the operator

By default, the Qdrant Operator will only manage Qdrant clusters in the same Kubernetes namespace, where it is already deployed. The RoleBindings are also limited to this specific namespace. This default is chosen to limit the operator to the least amount of permissions necessary within a Kubernetes clusters.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

within a Kubernetes cluster or within Kubernetes clusters

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, fixed.


If you want to manage Qdrant clusters in multiple namespaces with the same operator, you can either configure a list of namespaces that the operator should watch:

```yaml
operator:
watch:
# If true, watches only the namespace where the Qdrant operator is deployed, otherwise watches the namespaces in watch.namespaces
onlyReleaseNamespace: false
# an empty list watches all namespaces.
namespaces:
- qdrant-private-cloud
- some-other-namespase
limitRBAC: true
```

Or you can configure the operator to watch all namespaces:

```yaml
operator:
watch:
# If true, watches only the namespace where the Qdrant operator is deployed, otherwise watches the namespaces in watch.namespaces
onlyReleaseNamespace: false
# an empty list watches all namespaces.
namespaces: []
limitRBAC: false
```

## Uninstallation

To uninstall the Qdrant Private Cloud solution, you can use the following command:
Expand Down
Loading