Simple and easy way to expose Qdrant from your Kubernetes cluster, and use Authentication.

https://bichuetti.net/qdrant-authentication

Great blog post. Curious if you had any thoughts about to change the headless service to Nodeport w/ ingress controller/load balancer. We're enjoying developing against qdrant & thinking of multiple deployment options with auth.

Hi Tara. NodePort is the least commonly used service type. I agree with that. Other types are more versatile, allowing for a wider range of configuration and security, I believe. Having many services using NodePort makes management difficult. I would prefer to avoid using NodePort and give preference to the other alternatives. In case of deciding to use NodePort, the only positive aspect I can think of is load-balancing control, but there are options available to compensate for this.

If I deployed a Qdrant production cluster today, I would use Kong with Key Authentication. You could easily manage the keys with the Kong API. And you could use any other authentication method available in Kong as a plugin.

I appreciate your response. I'm glad you noted this, I was apprehensive about changing to NodePort service vs. just implementing an ingress controller. We've come up some approved auth mechanisms but wanted understand what other folks have experienced.