8000 feat: allow overriding metrics-exporter log verbosity via env (#1793) by Slach · Pull Request #2131 · Altinity/clickhouse-operator · GitHub
[go: up one dir, main page]
Skip to content

feat: allow overriding metrics-exporter log verbosity via env (#1793) #2131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alex-zaitsev merged 5 commits into from
Nov 6, 2026
Merged

feat: allow overriding metrics-exporter log verbosity via env (#1793) #2131

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
35803ee
feat: allow overriding metrics-exporter log verbosity via env (#1793)
Slach Nov 1, 2026
db9b624
Merge branch '0.28.0' into feat/1793-metrics-exporter-verbosity
Slach Nov 3, 2026
d23892b
feat(helm): add operator.logVerbosity
Slach Nov 5, 2026
32ae653
chore(helm): regenerate chart with dev/generate_helm_chart.sh
Slach Nov 5, 2026
9d3a509
Merge branch '0.28.0' into feat/1793-metrics-exporter-verbosity
Slach Nov 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions deploy/helm/clickhouse-operator/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,7 @@ crdHook:
| metrics.image.repository | string | `"altinity/metrics-exporter"` | image repository |
| metrics.image.tag | string | `""` | image tag (chart's appVersion value will be used if not set) |
| metrics.livenessProbe | string | `nil` | optional liveness probe for the metrics-exporter container check `kubectl explain pod.spec.containers.livenessProbe` for details example: httpGet: path: /metrics port: ch-metrics initialDelaySeconds: 10 periodSeconds: 10 |
| metrics.logVerbosity | string | `""` | log verbosity level (glog `-v`) of the metrics-exporter container, e.g. `0` to reduce log noise. Rendered as `CHOP_LOGGER_V` env var, which overrides `logger.v` of the operator configuration for the metrics-exporter only. Empty value keeps `logger.v` from the operator configuration. |
| metrics.readinessProbe | string | `nil` | optional readiness probe for the metrics-exporter container check `kubectl explain pod.spec.containers.readinessProbe` for details example: httpGet: path: /metrics port: ch-metrics initialDelaySeconds: 5 periodSeconds: 5 |
| metrics.resources | object | `{}` | custom resource configuration |
| nameOverride | string | `""` | override name of the chart |
Expand All @@ -124,6 +125,7 @@ crdHook:
| operator.image.repository | string | `"altinity/clickhouse-operator"` | image repository |
| operator.image.tag | string | `""` | image tag (chart's appVersion value will be used if not set) |
| operator.livenessProbe | string | `nil` | optional liveness probe for the clickhouse-operator container check `kubectl explain pod.spec.containers.livenessProbe` for details example: httpGet: path: /metrics port: op-metrics initialDelaySeconds: 10 periodSeconds: 10 |
| operator.logVerbosity | string | `""` | log verbosity level (glog `-v`) of the clickhouse-operator container. Rendered as `CHOP_LOGGER_V` env var, which overrides `logger.v` of the operator configuration for the clickhouse-operator only. Empty value keeps `logger.v` from the operator configuration. |
| operator.priorityClassName | string | "" | priority class name for the clickhouse-operator deployment, check `kubectl explain pod.spec.priorityClassName` for details |
| operator.readinessProbe | string | `nil` | optional readiness probe for the clickhouse-operator container check `kubectl explain pod.spec.containers.readinessProbe` for details example: httpGet: path: /metrics port: op-metrics initialDelaySeconds: 5 periodSeconds: 5 |
| operator.resources | object | `{}` | custom resource configuration, check `kubectl explain pod.spec.containers.resources` for details |
Expand Down
4 changes: 2 additions & 2 deletions ...use-operator/crds/CustomResourceDefinition-clickhousebackups.clickhouse.altinity.com.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ spec:
How late, counted from the time the backup is due, it may start on a cluster: a cluster whose Job is not
created by then fails, as does the backup when it is not validated by then. Unset waits as long as it takes
diffFromRemote:
!!merge <<: *TypeBackupName
<<: *TypeBackupName
description: "Existing backup to take this backup incrementally against (clickhouse-backup --diff-from-remote). The base backup must stay in the backup storage while this backup is kept"
verify: &TypeStringBool
description: "Run a verification Job after the backup that downloads it and checks it is restorable, without touching cluster data"
Expand All @@ -151,7 +151,7 @@ spec:
# union, so we use x-kubernetes-preserve-unknown-fields: true.
x-kubernetes-preserve-unknown-fields: true
schemaOnly:
!!merge <<: *TypeStringBool
<<: *TypeStringBool
description: "Back up table/database definitions only (no data)"
replicaSelection:
type: string
Expand Down
2 changes: 1 addition & 1 deletion ...ator/crds/CustomResourceDefinition-clickhousebackupschedules.clickhouse.altinity.com.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@ spec:
How many failed finished Jobs to keep, at least 1: the operator learns from the Job of a run why
it failed and the hosts it backed up. Defaults to 1
schemaOnly:
!!merge <<: *TypeStringBool
<<: *TypeStringBool
description: "Back up table/database definitions only (no data)"
replicaSelection:
type: string
Expand Down
130 changes: 65 additions & 65 deletions ...erator/crds/CustomResourceDefinition-clickhouseinstallations.clickhouse.altinity.com.yaml
View file
Open in desktop

Large diffs are not rendered by default.

130 changes: 65 additions & 65 deletions ...rds/CustomResourceDefinition-clickhouseinstallationtemplates.clickhouse.altinity.com.yaml
View file
Open in desktop

Large diffs are not rendered by default.

48 changes: 24 additions & 24 deletions ...ustomResourceDefinition-clickhousekeeperinstallations.clickhouse-keeper.altinity.com.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -286,7 +286,7 @@ spec:
# union, so we use x-kubernetes-preserve-unknown-fields: true.
x-kubernetes-preserve-unknown-fields: true
suspend:
!!merge <<: *TypeStringBool
<<: *TypeStringBool
description: |
Suspend reconciliation of resources managed by a ClickHouse Keeper.
Works as the following:
Expand Down Expand Up @@ -351,13 +351,13 @@ spec:
- "delete"
pvc:
type: string
!!merge <<: *TypeObjectsCleanup
<<: *TypeObjectsCleanup
description: "Behavior policy for unknown PVC, `Delete` by default"
configMap:
!!merge <<: *TypeObjectsCleanup
<<: *TypeObjectsCleanup
description: "Behavior policy for unknown ConfigMap, `Delete` by default"
service:
!!merge <<: *TypeObjectsCleanup
<<: *TypeObjectsCleanup
description: "Behavior policy for unknown Service, `Delete` by default"
reconcileFailedObjects:
type: object
Expand All @@ -367,16 +367,16 @@ spec:
# nullable: true
properties:
statefulSet:
!!merge <<: *TypeObjectsCleanup
<<: *TypeObjectsCleanup
description: "Behavior policy for failed StatefulSet, `Retain` by default"
pvc:
!!merge <<: *TypeObjectsCleanup
<<: *TypeObjectsCleanup
description: "Behavior policy for failed PVC, `Retain` by default"
configMap:
!!merge <<: *TypeObjectsCleanup
<<: *TypeObjectsCleanup
description: "Behavior policy for failed ConfigMap, `Retain` by default"
service:
!!merge <<: *TypeObjectsCleanup
<<: *TypeObjectsCleanup
description: "Behavior policy for failed Service, `Retain` by default"
defaults:
type: object
Expand All @@ -386,7 +386,7 @@ spec:
# nullable: true
properties:
replicasUseFQDN:
!!merge <<: *TypeStringBool
<<: *TypeStringBool
description: |
define should replicas be specified by FQDN in `<host></host>`.
In case of "no" will use short hostname and clickhouse-server will use kubernetes default suffixes for DNS lookup
Expand Down Expand Up @@ -498,23 +498,23 @@ spec:
maxLength: 15
pattern: "^[a-zA-Z0-9-]{0,15}$"
settings:
!!merge <<: *TypeSettings
<<: *TypeSettings
description: |
optional, allows configure `clickhouse-server` settings inside <yandex>...</yandex> tag in each `Pod` only in one cluster during generate `ConfigMap` which will mount in `/etc/clickhouse-server/config.d/`
override top-level `chi.spec.configuration.settings`
More details: https://clickhouse.tech/docs/en/operations/settings/settings/
files:
!!merge <<: *TypeFiles
<<: *TypeFiles
description: |
optional, allows define content of any setting file inside each `Pod` on current cluster during generate `ConfigMap` which will mount in `/etc/clickhouse-server/config.d/` or `/etc/clickhouse-server/conf.d/` or `/etc/clickhouse-server/users.d/`
override top-level `chi.spec.configuration.files`
templates:
!!merge <<: *TypeTemplateNames
<<: *TypeTemplateNames
description: |
optional, configuration of the templates names which will use for generate Kubernetes resources according to selected cluster
override top-level `chi.spec.configuration.templates`
pdbManaged:
!!merge <<: *TypeStringBool
<<: *TypeStringBool
description: |
Specifies whether the Pod Disruption Budget (PDB) should be managed.
During the next installation, if PDB management is enabled, the operator will
Expand All @@ -538,7 +538,7 @@ spec:
with chi.spec.configuration.clusters[].security. See docs/security_hardening.md.
x-kubernetes-preserve-unknown-fields: true
insecure:
!!merge <<: *TypeStringBool
<<: *TypeStringBool
description: |
optional, controls exposure of the plaintext Keeper
client port (zk:2181). Defaults to "yes" (legacy
Expand All @@ -555,7 +555,7 @@ spec:
`insecure: no` is set without `secure: yes` (no
client port would be emitted).
secure:
!!merge <<: *TypeStringBool
<<: *TypeStringBool
description: |
optional, open secure (TLS) Keeper client ports for this cluster.
Translates into <secure>1</secure> in Raft server entries so peer
Expand Down Expand Up @@ -589,18 +589,18 @@ spec:
maxLength: 15
pattern: "^[a-zA-Z0-9-]{0,15}$"
settings:
!!merge <<: *TypeSettings
<<: *TypeSettings
description: |
optional, allows configure `clickhouse-server` settings inside <yandex>...</yandex> tag in `Pod` only in one replica during generate `ConfigMap` which will mount in `/etc/clickhouse-server/conf.d/`
override top-level `chi.spec.configuration.settings`, cluster-level `chi.spec.configuration.clusters.settings` and will ignore if shard-level `chi.spec.configuration.clusters.layout.shards` present
More details: https://clickhouse.tech/docs/en/operations/settings/settings/
files:
!!merge <<: *TypeFiles
<<: *TypeFiles
description: |
optional, allows define content of any setting file inside each `Pod` only in one replica during generate `ConfigMap` which will mount in `/etc/clickhouse-server/config.d/` or `/etc/clickhouse-server/conf.d/` or `/etc/clickhouse-server/users.d/`
override top-level `chi.spec.configuration.files` and cluster-level `chi.spec.configuration.clusters.files`, will ignore if `chi.spec.configuration.clusters.layout.shards` presents
templates:
!!merge <<: *TypeTemplateNames
<<: *TypeTemplateNames
description: |
optional, configuration of the templates names which will use for generate Kubernetes resources according to selected replica
override top-level `chi.spec.configuration.templates`, cluster-level `chi.spec.configuration.clusters.templates`
Expand Down Expand Up @@ -637,18 +637,18 @@ spec:
minimum: 1
maximum: 65535
settings:
!!merge <<: *TypeSettings
<<: *TypeSettings
description: |
optional, allows configure `clickhouse-server` settings inside <yandex>...</yandex> tag in `Pod` only in one shard related to current replica during generate `ConfigMap` which will mount in `/etc/clickhouse-server/conf.d/`
override top-level `chi.spec.configuration.settings`, cluster-level `chi.spec.configuration.clusters.settings` and replica-level `chi.spec.configuration.clusters.layout.replicas.settings`
More details: https://clickhouse.tech/docs/en/operations/settings/settings/
files:
!!merge <<: *TypeFiles
<<: *TypeFiles
description: |
optional, allows define content of any setting file inside each `Pod` only in one shard related to current replica during generate `ConfigMap` which will mount in `/etc/clickhouse-server/config.d/` or `/etc/clickhouse-server/conf.d/` or `/etc/clickhouse-server/users.d/`
override top-level `chi.spec.configuration.files` and cluster-level `chi.spec.configuration.clusters.files`, will ignore if `chi.spec.configuration.clusters.layout.shards` presents
templates:
!!merge <<: *TypeTemplateNames
<<: *TypeTemplateNames
description: |
optional, configuration of the templates names which will use for generate Kubernetes resources according to selected replica
override top-level `chi.spec.configuration.templates`, cluster-level `chi.spec.configuration.clusters.templates`, replica-level `chi.spec.configuration.clusters.layout.replicas.templates`
Expand Down Expand Up @@ -719,16 +719,16 @@ spec:
minimum: 1
maximum: 65535
settings:
!!merge <<: *TypeSettings
<<: *TypeSettings
description: |
optional, allows configure `clickhouse-server` settings inside <yandex>...</yandex> tag in each `Pod` where this template will apply during generate `ConfigMap` which will mount in `/etc/clickhouse-server/conf.d/`
More details: https://clickhouse.tech/docs/en/operations/settings/settings/
files:
!!merge <<: *TypeFiles
<<: *TypeFiles
description: |
optional, allows define content of any setting file inside each `Pod` where this template will apply during generate `ConfigMap` which will mount in `/etc/clickhouse-server/config.d/` or `/etc/clickhouse-server/conf.d/` or `/etc/clickhouse-server/users.d/`
templates:
!!merge <<: *TypeTemplateNames
<<: *TypeTemplateNames
description: "be careful, this part of CRD allows override template inside template, don't use it if you don't understand what you do"
podTemplates:
type: array
Expand Down
Loading
Loading
0