feat: make operator log level configurable via Helm chart and plugin parameters
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go, helm, kubernetes
- Domain
- devops, infrastructure
Research direction
Start with kubernetes/deployment.yaml, values.yaml, and the Helm chart deployment template to trace how the operator log level is currently set. Then follow the Cluster plugins parameters handling for the per-cluster override. Done means non-Helm deployments default to info, Helm exposes a global logLevel, and a plugin parameter can override it for one cluster.
Written by the indexing model from the issue text.
Description
Summary
The operator deployment currently has --log-level=debug hardcoded in its args (both in kubernetes/deployment.yaml and the Helm chart template), and there is no way to tune log verbosity either globally or per cluster.
Current behavior
The operator emits debug-level logs unconditionally. In a production environment with multiple clusters and frequent WAL archiving, this generates a significant volume of log entries (e.g. generated patch, lifecycle reconciliation details) that are not actionable and add noise to log aggregation systems (Loki, CloudWatch, etc.).
Desired behavior
Two complementary levels of control:
1. Global — expose the log level as a configurable Helm value:
# values.yaml
logLevel: info # default: info (or warn)
Wired into the deployment args as --log-level={{ .Values.logLevel }}.
2. Per cluster — allow overriding verbosity through the plugins parameters in the Cluster spec, so individual clusters can emit debug logs without affecting the rest:
plugins:
- name: barman-cloud.cloudnative-pg.io
isWALArchiver: true
parameters:
barmanObjectName: my-store
logLevel: debug # optional, overrides the global default
Additionally, the default in kubernetes/deployment.yaml (used for non-Helm installations) should be updated from debug to info, since running with debug verbosity in production is not a sensible default regardless of the installation method.
Alternatives considered
- Patching the Deployment directly — reverted on every sync when using GitOps tools like ArgoCD.
- Filtering at the log aggregation layer — works but hides a configuration gap.
Environment
Helm chart cnpg/plugin-barman-cloud v0.6.0, operator image v0.12.0, ArgoCD with selfHeal: true.
- Dominant language
- Go
- Stars
- 192
- Forks
- 75
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 17
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudnative-pg/plugin-barman-cloud
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
cloudnative-pg/plugin-barman-cloud#1104 · 4 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
cloudnative-pg/plugin-barman-cloud#1113 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 15/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in cloudnative-pg/plugin-barman-cloud
Similar issues
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/agent-framework-go#1179 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
[Bug]: OLLAMA_KEEP_ALIVE="5m" / "24h" crashes Ollama embedding and vision models with ValueError Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
infiniflow/ragflow#20223 · 1 reaction ·
-
bug needs triage pkg/translator/faro
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
open-telemetry/opentelemetry-collector-contrib#51484 · 1 comment ·