Typesense

Typesense is an open source, typo-tolerant search engine. Edka installs the Typesense Helm chart (version 30.2) on your own Kubernetes cluster, generates the admin API key, and wires up storage and networking. The workload runs on your cluster.

What Edka Provisions

Edka installs the Typesense Helm chart (version 30.2) and wires up everything needed to run it in production on your cluster:

• Single or multi-node clusters: Choose 1, 3, 5, or 7 nodes. Use 3 or more for high availability.
• Bootstrap admin API key: A secure 48-character admin API key is generated and stored in a Kubernetes secret for you.
• Persistent storage: Data volumes backed by your storage class (defaults to hcloud-volumes), sized from 10 GiB and adjustable after deployment.
• Internal service endpoint: Typesense is exposed on port 8108 at a stable in-cluster address for your applications to reach.
• Optional external access: Publish the Typesense API through an Envoy Gateway traffic class on a hostname of your choice.

Configuration Options

Edka surfaces Typesense’s tuning knobs directly in the deploy flow, so you can match the engine to your workload:

• CORS: Enable browser apps to call Typesense directly and whitelist specific origins.
• Search analytics: Persist aggregated query analytics on the Typesense volume, with configurable flush interval and rate limits.
• Query cache: Control how many query results Typesense caches (default 1000 entries).
• Indexing concurrency: Cap batch indexing concurrency, or let Typesense decide automatically.
• Write guardrails: Reject writes when memory or disk usage exceeds a chosen percentage.
• Result limits: Tune snapshot interval, max results per page, and max group limit.
• Resources & placement: Set CPU and memory requests/limits per pod, and pin Typesense to a specific node pool with optional taint tolerations.
• Auto-updates: Opt in to automatic chart and image updates with a patch, minor, major, custom, or all version policy on a schedule you choose.

Getting Started

1. Click “Deploy Typesense” below.
2. Pick your node count and Typesense image tag.
3. Set storage size and storage class.
4. Adjust configuration, resources, and access as needed, then deploy.
5. Connect your application to the in-cluster API endpoint on port 8108 using the generated admin API key.

Deploy Typesense