Skip to main content
This page lists every configuration key you may need to touch, with its default and meaning: first the VM configuration file, then the Helm chart values. For task-oriented guidance, see the configuration guide.

VM configuration file

On a Linux VM the connector reads /etc/clicklink/config.yaml, written by clicklink clctl init and kept across re-runs unless --force is passed. Keys omitted from the file fall back to the compiled defaults below. Credentials never live in this file.

Top-level keys

api

instances

Each entry under instances.<name> describes one ClickHouse native-protocol target:

scraper

troubleshooter

observability

Per-component observability blocks overlay this base: the scraper uses 8082/9092, the troubleshooter 8084/9094, and the gateway listens on 8443 when enabled.

Default table allowlist

The troubleshooter’s default allowed_tables set, identical to the chart’s troubleshooter.allowedTables default:

Helm chart values

On Kubernetes the connector is configured through the clicklink-connector chart’s values. clicklink clctl init stages a clicklink-values.yaml overlay with everything below filled in and keeps it across re-runs unless --force is passed. The tables list the chart defaults; standard workload knobs (resources, nodeSelector, tolerations, affinity, serviceAccount.annotations, env, imagePullSecrets) exist on each component with empty defaults and are not repeated per table.

cluster

image

api

secrets

The chart consumes pre-created Secrets; init creates them before install.

scraper

troubleshooter

persistence

clctl.gateway

The session gateway for support sessions.

networkPolicy

Last modified on August 19, 2026