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.
1
Jul 02, 2023 (5 months ago)
Sai
10:10 AM🔗 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
Sai
10:11 AMKishore Nallan
10:15 AMreset-peers-on-error
flag for auto healing clustering, see here: https://github.com/typesense/typesense/issues/465#issuecomment-1487780839Sai
10:17 AMKindly 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
10:25 AMSai
10:27 AMTypesense
Indexed 3015 threads (79% resolved)
Similar Threads
Troubleshooting IP Update on Kubernetes Typesense
Alessandro and Damien are having issues with old IP addresses in a Kubernetes Typesense cluster not being updated. Kishore Nallan provides possible troubleshooting solutions, and mentioned the need for a fix for DNS retries. A suggested update strategy was shared by Aljosa.
Troubleshooting Typesense Issues in Kubectl v1.26
Arnob and Rubai face issues with Typesense erasing data. Jason and Kishore Nallan suggest HA setup and persistent volume usage. Sai recommends the Typesense Kubernetes operator but Arnob experiences new errors.
Testing High Availability with Raft Returns Crashes
pboros reports an issue with usual crashes when testing high availability with Raft. Kishore Nallan suggests checking the quorum recovery period and efficiently logging the crash on all nodes. The issue persists, with pboros suspecting it's due to hostname being no longer resolvable once a container is killed.