Tilt sometimes stops streaming the logs and updating the status
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Expected Behavior
In some occasion (it is hard to reproduce and seems a bit random), the pod is deployed correctly and works on the cluster, but in tilt we don't receive logs, port forward isn't working and the pod status is not updated. After few tilt restart it starts working again
Current Behavior
Steps to Reproduce
Difficult to reproduce, but If there is a way to debug it when it happens I'm ready to try
Context
tilt doctor Output
Tilt: v0.34.3, built 2025-05-16
System: linux-amd64
---
Docker
- Host: unix:///var/run/docker.sock
- Server Version: 27.5.0
- API Version: 1.47
- Builder: 2
- Compose Version: v2.32.4
---
Kubernetes
- Env: unknown
- Container Runtime: containerd
- Version: v1.30.13-eks-5d4a308
- Cluster Local Registry: none
---
...
About Your Use Case
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the reported Tilt v0.34.3 environment and trying to capture the failure while logs, port forwarding, and pod status all stop updating. Since reproduction is currently described as difficult and no files or tests are named, trace the relevant Kubernetes event, log-streaming, status, and port-forwarding entry points; done means identifying the cause and preventing the stalled state or documenting a reliable diagnostic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100