You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our team is building automation around Qdrant storage deployed with this helm chart.
We're also using the snapshot APIs and for this we need to communicate with each pod directly.
We found an elegant way to access the cluster API and each pod individually by using existing k8s facilities.
In short we:
use cert-manager.io for issuing TLS certificats
use Nginx Ingress which allows rewriting target urls
we access cluster level API via https://<fqdn>/cluster
we access each pod API via https://<fqdn>/pod-<index>
How we did it:
We use nginx ingress controller which allows to rewrite target url,
we basically followed the answer from here. Our values contains this ingress definition:
Then the backend of the per-pod Ingress object points to corresponding service (quadrant-service-0) and also has rewriting configuration for pod-0 path.
Suggestion: It would be great if Qdrant helm chart supports to optionally define per pod Ingress objects.
This would allow users like us to quite easily make each pod accessible.
Thank you!
The text was updated successfully, but these errors were encountered:
Hi Qdrant team,
Our team is building automation around Qdrant storage deployed with this helm chart.
We're also using the snapshot APIs and for this we need to communicate with each pod directly.
We found an elegant way to access the cluster API and each pod individually by using existing k8s facilities.
In short we:
https://<fqdn>/cluster
https://<fqdn>/pod-<index>
How we did it:
we basically followed the answer from here. Our values contains this ingress definition:
This ingress definition produces Ingress object pointing to the ClusterIP service which targets the three pods:
selector
section we add the pod-name label:quadrant-service-0
) and also has rewriting configuration forpod-0
path.Suggestion: It would be great if Qdrant helm chart supports to optionally define per pod Ingress objects.
This would allow users like us to quite easily make each pod accessible.
Thank you!
The text was updated successfully, but these errors were encountered: