GoogleContainerTools/skaffold

Logs are missed after code change

Open

#4,785 opened on Sep 15, 2020

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (1,416 forks)batch import
area/loggingarea/uxgood first issuehelp wantedidekind/bugpriority/p3

Repository metrics

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

Description

copied from https://github.com/GoogleCloudPlatform/cloud-code-intellij-internal/issues/2584#

  • Start a skaffold k8s session with an app that contains a readiness probe (the specific setup with a spring-boot app using Jib)
  • Make a code edit

expected: logs continue streaming actual: some of the application logs are not printed until the readiness probe passes (the theory); e.g. the spring boot start up logs are not printed.

See these comments from the copied issue.

Contributor guide

Research direction
Investigate the log streaming behavior after code changes, focusing on the interaction between readiness probes and log output. Trace the code path in Skaffold that handles log streaming and check if readiness probe delays affect log collection.
Tech stack
go
Domain
backenddevops
Issue type
Bug
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
GitDockerKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50