piped is evicted from cluster due to lack of ephemeral storage
Open
Nobody has claimed this yet.
kind/bug
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened:
When I make about 30-40 application changes at a time in PipeCD, the piped pod is evicted from the ephemeral storage of the cluster node (the target node has an upper limit of 50GiB).
The node was low on resource: ephemeral-storage. Container piped was using 33556644Ki, which exceeds its request of 0.
Possible ways to handle this.
- Increase the ephemeral storage capacity of the node
- Change the PipeCD application to a smaller one.
What you expected to happen:
How to reproduce it:
Environment:
pipedversion:control-planeversion:- Others:
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
The issue names no files, tests, or entry points. Start by reviewing how the piped pod is deployed and reproducing the Kubernetes ephemeral-storage eviction during many application changes; done should identify the storage consumer and establish a verified handling or configuration change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100