draios / draios/sysdig-cloud-scripts
Sysdig Agent Limits?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 83
- Forks
- 105
- Avg merge
- 3h 53m
- Merged PRs (30d)
- 1
Description
Install script for sysdig say \"resources\":{\"limits\":{\"cpu\":\"2000m\",\"memory\":\"1536Mi\"},\"requests\":{\"cpu\":\"600m\",\"memory\":\"512Mi\"}}
Can we reduce the limit of cpu, or still require to use unto 2 CPU, this seems a lot when we try to run a 4cpu Kube node.
Contributor guide
No contributing guide indexed for this repository
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 locating the install script and its Kubernetes resource configuration, then verify whether the stated CPU and memory limits are required by the Sysdig Agent. Compare deployment behavior on a four-CPU Kubernetes node; done means the supported limits and any required configuration change are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100