#contributions

Release Announcement and Discussion of Typesense Operator on Kubernetes

TLDR Sai announced the release of the Typesense Operator for Kubernetes and discussed its features. Kishore Nallan highlighted a potential issue with rotation, which Sai explained is managed internally given the operator uses service DNS connections. Kishore Nallan recommended highlighting this in the README.

Powered by Struct AI

1

Jul 02, 2023 (5 months ago)
Sai
Photo of md5-6c1f32ee79d1166e54e3f17345b8d814
Sai
10:10 AM
🚀Exciting News! I'm thrilled to announce the release of Typesense Operator - An operator to manage Typesense clusters on Kubernetes! 🎉


🔗 GitHub Repository: https://lnkd.in/gV29eMGT

🌟 Key Features:
- A fully automated way to manage Typesense on Kubernetes
- Cloud agnostic
- Very first Kubernetes operator developed exclusively for Typesense

LinkedIn : https://www.linkedin.com/posts/saiprasanth-raghuraman_opensource-github-typesenseoper[…]625605246976-4CvX?utm_source=share&utm_medium=member_desktop

1

10:11
Sai
10:11 AM
cc : Jason Kishore Nallan
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
10:15 AM
This is great. We certainly miss a good Kubernetes chart / operator. One of the pain points people have had though is with rotation. Because of the way the library that we use for Raft works, the cluster either should use static IPs or the pod rotation should be 1 at a time. This causes a lot of problems on k8s when you don't enable proper pod disruption budget. Lately though I've created a reset-peers-on-error flag for auto healing clustering, see here: https://github.com/typesense/typesense/issues/465#issuecomment-1487780839
Sai
Photo of md5-6c1f32ee79d1166e54e3f17345b8d814
Sai
10:17 AM
Thanks Kishore Nallan. The operator internally uses service DNS to connect so scaling up or down shouldn't be a problem.
Kindly go through it and let me know if I'm missing or can make it better. I would be actively taking feedbacks and working towards it.
Also please spread the word 🙂
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
10:25 AM
I see. You should probably clarify this on the README because it's the trickiest part of running TS on k8s right now.
Sai
Photo of md5-6c1f32ee79d1166e54e3f17345b8d814
Sai
10:27 AM
Sure I will.