Skip to content

fix: Log in zap production mode - #26

Merged
0xmc merged 1 commit into
mainfrom
fix/production-logging
Oct 15, 2026
Merged

0xmc merged 1 commit into
mainfrom
fix/production-logging

Conversation

@0xmc

@0xmc 0xmc commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Closes #25.

Stops the operator from forcing controller-runtime zap's development mode, so it logs JSON at info level. Staging's logs currently read as console text with a JSON fragment, which Loki can't parse into fields, and development mode also makes DPanic panic. The zap-devel flag still turns it on for local runs.

Test plan

  • The module builds
  • After staging deploys, the operator's lines in Loki are JSON objects carrying build_version and instrumentation_version

🤖 Generated with Claude Code

The operator forced zap's development mode, so staging and production
logged console text at debug level and DPanic panicked. Loki couldn't parse
the lines into fields.

Key changes:
- stop forcing development mode; --zap-devel still enables it locally

Closes #25

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@0xmc
0xmc merged commit 8cc0afb into main Oct 15, 2026
9 checks passed
@0xmc
0xmc deleted the fix/production-logging branch October 15, 2026 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Operator logs in zap development mode

3 participants