mirror of
https://github.com/outbackdingo/qdrant-helm.git
synced 2026-01-27 10:20:18 +00:00
c9e613ae2e
Add a common label `app.kubernetes.io/component` ([1]) with value `cluster-discovery` to the headless Service and the ServiceMonitor it's ensured metrics are only scraped once. Using the headless service also makes the most sense, as it has the sole purpose of discovering all Pods making up a qdrant cluster. With `publishNotReadyAddresses: true` metrics are also collected from non-ready pods, see [2]. This is helpful to also collect metrics from Pods that might never become ready to use them for e.g. alerting and problem analysis [1] https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/#labels [2] https://github.com/prometheus-operator/prometheus-operator/discussions/5693 Fixes: #207
Qdrant helm repository
This repository hosts the following helm charts:
Usage
helm repo add qdrant https://qdrant.github.io/qdrant-helm
helm repo update
helm upgrade -i your-qdrant-installation-name qdrant/qdrant
For more in-depth usage documentation, see the helm chart's README.
Upgrading
This helm chart installs the latest version of Qdrant by default. When a new version of Qdrant is available, upgrade the helm chart with the following commands:
helm repo update
helm upgrade your-qdrant-installation-name qdrant/qdrant
This command performs a rolling upgrade of your Qdrant cluster, updating one node at a time.
If you have overridden the Qdrant image tag in values.yaml, you will also need to update that tag before running helm upgrade.
image:
tag: vX.Y.Z
Contributing
See CONTRIBUTING.md.