Before you start
- Runs in Kubernetes pod mode (OOS_RUNTIME=kubernetes): Kelvo has no per-query cgroups, so the 768 MiB pod limit is the only memory, CPU and process boundary and one runaway query can restart the explorer. Landlock, the worker seccomp filter, non-root execution and a read-only root filesystem still apply.
- Nodes need Linux with Landlock ABI 3 or later.
- Use one instance per Hakopod project and environment, with fresh metadata. Set the scope to the exact scope string of the matching engine target.
- Hakopod opens the explorer only after an operator adds a target for this scope to HAKOPOD_EXPLORER_TARGETS_FILE, with this app's HTTPS address plus /synehq and a key file holding the same hakopod-explorer-key value.
Configuration that needs your attention
Pod mode trades per-query isolation for running on Kubernetes; see the OOS Kubernetes pod mode guide before deploying.
Required secrets
Configure these scoped secrets during deployment review in your Hakopod installation. Secret values stay out of the application TOML.
-
hakopod-explorer-key
This preset needs a public site URL. Set the correct origin before starting the application.
Use this preset
- Open the Catalog in your own Hakopod dashboard and select SyneHQ OOS.
- Choose the project, environment, and application name. Set the required values and secret references.
- Review the generated configuration, resource requests, networking, and storage plan.
- Deploy, then inspect readiness and logs. Configure backups for persistent data before relying on the service.
Read the upstream setup documentation ↗
View native TOML and setup notes ↗
Pinned container image
ghcr.io/synehq/synehq-oos:sha-d280c7cb3181e4342c89986e38edd35da38c45bf-hakopod@sha256:291f5417382dc9fe462c7566621226c0d6bbaa5bfcb7c7cd83b3e10bbbd3e6e5
The catalog pins this image for reproducibility. Review upstream updates and compatibility before changing it.