rancher/k3k

Migrate from `logrus` to `zap`

Open

#561 opened on Nov 12, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (77 forks)auto 404
enhancementgood first issueteam/collie

Repository metrics

Stars
 (886 stars)
PR merge metrics
 (PR metrics pending)

Description

From the README or logrus it is in maintenance-mode. Latest release is +2y old.

We are already using Zap in our controller and kubelet, so we can use just one logging library. We can also improve the logging of the cli using the stdout to write the messages, while the stderr for the logs.

Contributor guide

Research direction
Replace all logrus calls with zap, configure zap logger to write info/debug to stdout and errors to stderr, and ensure consistency with existing zap usage in controller/kubelet.
Tech stack
go
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70