kubernetes/minikube

improve minikube tunnel output

Open

#6,309 建立於 2020年1月14日

在 GitHub 查看
 (9 留言) (0 反應) (0 負責人)Go (31,799 star) (5,222 fork)batch import
help wantedkind/cleanuplifecycle/frozenpriority/backlog

描述

currently it keeps printing the first time someone looks at it, it looks a bit scary specially with word errors repeating 4 times.

Status:	
	machine: minikube
	pid: 48635
	route: 10.96.0.0/12 -> 172.17.0.2
	minikube: Running
	services: [hello-minikube1]
    errors: 
		minikube: no errors
		router: no errors
		loadbalancer emulator: no errors

I purpose if there is no errors in all three categories, it should not print anything about errors.

貢獻者指南

技術棧
go
領域
clidevops
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic GoFamiliarity with minikube tunnel output
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Investigate the tunnel output logic in minikube's tunnel subcommand (likely in `cmd/tunnel/`). The current code always prints the errors section even when all error categories are empty. Modify the output to conditionally hide the errors block when no errors exist. Refer to maintainer comments in the issue for any specific requirements on the output format.