Install and upgrade
Offline bundles, licensing, rollback. Visible installs, reversible upgrades.
Start with one machine or go straight to HA.
Deployment profiles
| Profile | Fits | Scaling |
|---|---|---|
| Standalone | Evaluation, branch offices, edge sites | Vertical |
| Performance cluster | Larger host and container estates | gateway / collector / ClickHouse separately |
| HA cluster | Systems that cannot stop | Replicas plus failover |
Offline install
Build an offline bundle for the target profile on a release machine. It contains images, dependencies, license and a digest manifest. Move it inside, verify signatures and digests, then install.
The installer reports every step, success or failure.
cd diting-deploy
bash ci/pack-standalone-from-spec.sh \
--spec <package-spec.json> --version <version> \
--output <dist-dir> --workspace <ws-dir>
kubectl -n diting get pods
kubectl -n diting get svcUpgrade and rollback
Upgrade bundles are imported the same way. Key configuration is backed up before the upgrade, and a failed upgrade can roll back to the previous version.
Agent capture modes can be rolled back independently, without swapping binaries.
- Pre-upgrade backup
- Staged rollout
- Rollback on failure
- Agent capture-mode rollback
Licensing
The license is an offline file verified with asymmetric signatures. Renewal is offline too, with no connection to a vendor server.
Bring your system in
Tell us what you run: OS, kernel, public network or not, virtual machines or clusters. We will map the path in.