storage-chown-by-maps causes high CPU usage when pods are rapidly created
Open
Nobody has claimed this yet.
bug
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
Specification
- EKS control and data plane version: 1.23
- OS: Official Ubuntu 2004 EKS image with 5.15-1026 kernel
When pods are rapidly created, storage-chown-by-maps spikes up the CPU which makes the underlining node unresponsive. This specifically started happening after kernel version 5.15-1022.
More details can be found in the below slack thread
https://nestybox-support.slack.com/archives/CS7V68QMP/p1669873174973199
CC: @ctalledo
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 with the linked Slack thread and reproduce rapid pod creation on the specified EKS 1.23 Ubuntu 20.04 environment, comparing kernel 5.15-1022 with 5.15-1026. Trace the CPU usage of storage-chown-by-maps; done means the node remains responsive without the reported CPU spike under the stated workload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, linux, ubuntu
- Domain
- infrastructure, operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100