ClickHouse: Sysaro manages its own drop-in without overwriting vendor configuration
The typed adapter only changes a Sysaro-owned file; existing vendor and manual ClickHouse configuration remains untouched. Apply goes through validation, restart, readiness and rollback on failure.
How the service fits into Sysaro
Owned configuration boundary
The Control Plane stores typed desired state while the Agent renders only the fixed Sysaro-owned drop-in.
The browser cannot choose an arbitrary configuration path, systemd unit or probe URL.
Preview exposes the exact managed file, create/change state and SHA-256 before apply.
What can be changed today
Listen address, HTTP port and native TCP port.
Maximum connections and maximum concurrent queries.
When the HTTP port changes, readiness derives it from Sysaro’s managed config and still probes loopback only.
What is intentionally not hidden
Users/access, storage layout and replication are not presented as completed management scope.
Sysaro does not overwrite vendor config or guess the architecture of an unknown existing ClickHouse deployment.
Partial writes and restart/readiness failures restore previous contents, existence state and file mode.
What this page does not claim
Detection, lifecycle or a typed subset is not described as complete management of every upstream capability. The canonical current scope is also published in service-evidence.json and the 18-service catalog.