logging: set clickhouse readonly profile to readonly=2 (#409)

## Why The `readonly` profile used by `logreader` sets `readonly=1`, which rejects any per-query settings change. HTTP clients (logviewer, chlog) send settings params like `max_execution_time` with their queries, so every query fails with `Code: 164 DB::Exception: Cannot modify 'max_execution_time' setting in readonly mode` — logviewer healthz returns 503 and CrashLoops, chlog queries fail. `readonly=2` keeps data access read-only while permitting settings changes, which is what HTTP clients need. ## Changes - Changes the `readonly` profile in `apps/base/logging/clickhouseinstallation.yaml` from `readonly: "1"` to `readonly: "2"` Reviewed-on: #409 Co-authored-by: unkin-agent <unkin-agent@unkin.net> Co-committed-by: unkin-agent <unkin-agent@unkin.net>
2026-08-23 22:36:52 +10:00
parent 03c56c0ff0
commit 5a23146513
1 changed files with 1 additions and 1 deletions
@@ -46,7 +46,7 @@ spec:
    profiles:
      default/max_memory_usage: "10000000000"
      default/max_execution_time: "120"
-      readonly/readonly: "1"
+      readonly/readonly: "2"
      readonly/max_memory_usage: "10000000000"
      readonly/max_execution_time: "120"
    clusters: