Skip to content

fix: change k8s event log level from Info to Debug#157

Draft
kacpersaw wants to merge 1 commit intomainfrom
kacpersaw/k8s-events-log-level
Draft

fix: change k8s event log level from Info to Debug#157
kacpersaw wants to merge 1 commit intomainfrom
kacpersaw/k8s-events-log-level

Conversation

@kacpersaw
Copy link
Contributor

Fixes #145

Summary

Kubernetes events sent from coder-logstream-kube to Coder were displayed with a green border because they used LogLevelInfo. This confused users who associate green with "workspace ready".

Changes

Changed codersdk.LogLevelInfo to codersdk.LogLevelDebug in 3 places in logger.go:

  • "Created pod" log
  • "Queued pod from ReplicaSet" log
  • Event message log

This prevents the interim events (PVC/PV attach, image pull, etc.) from appearing with the same visual indicator as the final ready state.

Testing

  • All existing tests updated and passing

Fixes #145. Kubernetes events sent to Coder were displayed with a green
border because they used LogLevelInfo. This confused users who associate
green with 'workspace ready'. Changing to LogLevelDebug prevents these
interim events from appearing with the same visual indicator as the
final ready state.
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.

bug: kubernetes events sent from coder-logstream-kube to coder should not be displayed with a green border

1 participant