krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-09-30 00:18:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2478 from qdrant/update-priv-cloud-release

Browse Source 
feat: private-cloud release 1.9.11
This commit is contained in:
Anton Antonov
2026-07-08 13:56:53 +02:00
committed by GitHub
parent dba1c5fb6c 34ce410139
commit fbd3129f8b
2 changed files with 20 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/private-cloud/changelog.md
+13
View File
@@ -7,6 +7,19 @@ weight: 35
# Changelog
## 1.9.11 (2026-07-08)
| Component | Version |
|-------------------------|---------|
| qdrant-kubernetes-api | v1.37.1 |
| operator | 2.33.0 |
| qdrant-cluster-manager | v0.3.19 |
| qdrant-cluster-exporter | 1.8.0 |
Latest validated Qdrant version: 1.18.2
* Updated operator to 2.33.0 and qdrant-kubernetes-api 1.37.1.
## 1.9.10 (2026-06-25)
| Component | Version |
qdrant-landing/content/documentation/private-cloud/private-cloud-setup.md
+7 -7
View File
@@ -69,13 +69,13 @@ helm registry login 'registry.cloud.qdrant.io' --username 'your-username' --pass
4. Install the Qdrant Kubernetes Operator Custom Resource Definitions (CRDs):
```bash
helm upgrade --install qdrant-private-cloud-crds oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-kubernetes-api --namespace qdrant-private-cloud --version v1.37.0 --wait
helm upgrade --install qdrant-private-cloud-crds oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-kubernetes-api --namespace qdrant-private-cloud --version v1.37.1 --wait
```
5. Install Qdrant Private Cloud:
```bash
helm upgrade --install qdrant-private-cloud oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-private-cloud --namespace qdrant-private-cloud --version 1.9.10
helm upgrade --install qdrant-private-cloud oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-private-cloud --namespace qdrant-private-cloud --version 1.9.11
```
Ensure that the `qdrant-kubernetes-api` version is compatible with the `qdrant-private-cloud` version you are installing.
@@ -84,8 +84,8 @@ For a list of available versions consult the [Private Cloud Changelog](/document
Current default versions are:
* qdrant-kubernetes-api v1.37.0
* qdrant-private-cloud 1.9.10
* qdrant-kubernetes-api v1.37.1
* qdrant-private-cloud 1.9.11
For more information also see the [Helm Install Documentation](https://helm.sh/docs/helm/helm_install/).
@@ -113,7 +113,7 @@ operator:
You can configure Qdrant Private Cloud like this:
```bash
helm upgrade --install qdrant-private-cloud oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-private-cloud --namespace qdrant-private-cloud --version 1.9.10 -f values.yaml
helm upgrade --install qdrant-private-cloud oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-private-cloud --namespace qdrant-private-cloud --version 1.9.11 -f values.yaml
```
## Upgrades
@@ -121,13 +121,13 @@ helm upgrade --install qdrant-private-cloud oci://registry.cloud.qdrant.io/qdran
To upgrade Qdrant Private Cloud to a new version, first upgrade the Qdrant Kubernetes Operator Custom Resource Definitions (CRDs):
```bash
helm upgrade --install qdrant-private-cloud-crds oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-kubernetes-api --namespace qdrant-private-cloud --version v1.37.0 --wait
helm upgrade --install qdrant-private-cloud-crds oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-kubernetes-api --namespace qdrant-private-cloud --version v1.37.1 --wait
```
Then upgrade the Qdrant Private Cloud Helm chart using the same configuration values, e.g.:
```bash
helm upgrade --install qdrant-private-cloud oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-private-cloud --namespace qdrant-private-cloud --version 1.9.10 -f values.yaml
helm upgrade --install qdrant-private-cloud oci://registry.cloud.qdrant.io/qdrant-charts/qdrant-private-cloud --namespace qdrant-private-cloud --version 1.9.11 -f values.yaml
```
Note, that the image tag values are automatically derived from the chart's appVersions and should not be overridden in the `values.yaml`.