kubernetes/minikube

Feature request: Include invoked command in log output

Open

#9,520 opened on Oct 21, 2020

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
help wantedkind/featurelifecycle/frozenpriority/backlog

Description

Minikube logs currently don't have the command invoked output to the log file. It would be good to have this information when looking at the logs.

Contributor guide

Tech stack
gokubernetes
Domain
clidevopsobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingFamiliarity with minikube logging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The minikube logging system is likely in the pkg/minikube/logs directory or similar. Look for where log output is generated and find the point before command execution. Add a line to log the invoked command (e.g., using a logger like log.Infof). Review existing log formats to match style. Check if there are any configuration options for verbosity to ensure the new log line is appropriate.