Bare-Metal Install (no Docker, no Kubernetes)
How the standalone installer brings the entire Elchi stack up as systemd services on 1, 2, or 3+ Linux VMs.
Prerequisites
OS, hardware, network, and SSH requirements for the bare-metal Elchi stack installer.
Quick Start
One-command bare-metal installs — single VM all-in-one and 3-VM clusters with key-based or interactively bootstrapped SSH.
install.sh — full flag reference
Complete reference for every install.sh flag — topology, SSH, versioning, TLS, MongoDB, VictoriaMetrics, Grafana, GSLB, backend, and op-mode.
upgrade.sh — version-diff upgrade
Version-diff upgrades with hash-based reconcile, additive or declarative variant changes, health gate, and per-binary rollback.
uninstall.sh — remove the stack
Non-destructive uninstall by default, cluster-wide fan-out from M1, and opt-in purge flags for data, packages, and secrets.
/etc/elchi/validate.sh — per-node post-install audit
Read-only per-node audit script that checks systemd, ports, service health, Envoy admin, config integrity, and system tuning.
elchi-stack — operator helper
Subcommand reference for the elchi-stack operator helper installed on every node.
Port atlas
Every port the bare-metal Elchi stack listens on, per service and per node role.
Topology
How components distribute across 1, 2, and 3+ VM clusters — Mongo RS, per-node OTel and collector, ClickHouse replication, and the M1 storage tier.
Production hardening (kernel + systemd)
The kernel sysctl baseline, MongoDB systemd drop-in, per-service systemd hardening set, and preflight RAM/swap checks applied by every install.
Supported distros + idempotency
Supported Linux distributions, why older releases are dropped, and how hash-based reconcile makes reruns idempotent.