GoogleContainerTools/skaffold

Skaffold should output which kube-context + cluster is being used

Open

#6,861 opened on Nov 15, 2021

View on GitHub
 (4 comments) (3 reactions) (0 assignees)Go (1,416 forks)batch import
area/clibugbash/q4-2022good first issuehelp wantedkind/feature-requestpriority/p2

Repository metrics

Stars
 (12,822 stars)
PR merge metrics
 (Avg merge 3d 6h) (16 merged PRs in 30d)

Description

It should be more clear for users (and people trying to offer support by looking at logs!) which kube-context and cluster is being used.

$ skaffold dev
Listing files to watch...
 - skaffold-example
Generating tags...
 - skaffold-example -> skaffold-example:v1.34.0-60-gef8185519
Checking cache...
 - skaffold-example: Not found. Building
Starting build...
Building [skaffold-example]...

This information is shown with -vinfo, but most users do not run at this level:

$ skaffold dev -v info
INFO[0000] Skaffold &{Version:v1.34.0-60-gef8185519 ConfigVersion:skaffold/v2beta26 GitVersion: GitCommit:ef818551948c82de81ef4308aef7dbcb36d3dede BuildDate:2021-11-15T15:47:08Z GoVersion:go1.17.2 Compiler:gc Platform:darwin/arm64 User:}  subtask=-1 task=DevLoop
INFO[0000] Loaded Skaffold defaults from "/Users/bdealwis/.skaffold/config"  subtask=-1 task=DevLoop
INFO[0000] Using kubectl context: gke_k8s-skaffold_us-west1_test-cluster  subtask=-1 task=DevLoop
INFO[0001] build concurrency first set to 1 parsed from *local.Builder[0]  subtask=-1 task=DevLoop

Contributor guide

Research direction
Identify where the kubectl context is retrieved in the codebase and output it at the default log level. Look at how ` v info` logs the context and move that to always appear.
Tech stack
go
Domain
backendclidevopsinfrastructuredeveloper experience
Issue type
Feature
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.
1-3 hours
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
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75