Skip to content

Orama Lake v0.1.1

Latest

Choose a tag to compare

@homer6 homer6 released this 16 Nov 11:32
05bdea7

Released 2026-11-16. A patch of v0.1.0. It pins the same component versions; what changes is how the stack is installed and how a release of this repository is checked.

Get it

$ git clone --recurse-submodules --branch v0.1.1 https://github.com/oramasearch/lake-platform.git

Every submodule is fetched over HTTPS, so the clone needs no GitHub account or key. To install the platform, start at docs/install/.

What changed

  • Every install runs the operator's helmfile. Try it and Scale it install the platform and the operator with helmfile sync from modules/orama-operator/helmfile.yaml, the one install path, instead of helm install commands of their own. CLAUDE.md records it as a design rule. (#19)
  • Observability is left out of public installs. The helmfile's kube-prometheus-stack and perses charts pull Orama's own image mirrors, which are not distributed. Lake and the operator work without them; the operator reports the monitoring CRDs as missing until a Prometheus stack is installed. (#19)
  • Try it on k0s or k3s. A single-node k0s or k3s, directly on Linux or in Docker (k3d) on macOS and Windows, then the helmfile and one Lake. On k0s, which has no load balancer, ingress-nginx syncs without waiting.
  • A release checks the bridge pointers. Before a release of this repository, liquid-bridge and zetta-bridge point at their bridge's main head, and every pin is at its component's latest release (CLAUDE.md, Cut a release). (#19)
  • release.yaml is stack version 0.1.1.

What it pins

The same as v0.1.0: lake v0.9.0, zetta v0.6.0, liquid v0.3.0, orama-operator v0.12.0, zetta-tunnel v0.3.1, liquify v0.1.0, the lake services, the runtimes and the agents at their releases, and k0s, a fork, by commit.

Known issues

  • The k0s server script installs with helm directly. Run it's hack/lake-on-k0s/install.sh installs CloudNativePG and the operator itself, not from the helmfile (k0s#52).
  • The install guides have not been run end to end on a laptop or a clean host since they moved to the helmfile.
  • The known issues of v0.1.0 still hold.

Verification

Check Result
Bridge pointers liquid-bridge at 6c7eccd1 and zetta-bridge at ac2bc052, each its bridge's main head
Every pin is a released version Every pin here and in both bridges is its component's latest release tag, except k0s (a fork, by commit) and three repositories with no releases (zetta-docs, solutions-designs, zetta-web-e2e)
scripts/check-release-manifest.py passes: every commit in release.yaml is the commit this repository pins
tools/spdx-headers.py --check passes
Anonymous recursive clone git clone --recurse-submodules with no SSH key and no credentials: 67 submodules, all fetched over HTTPS, exit 0

This repository has no build or test suite of its own.