Proxy Resource Requirements Needed With LimitRange and ResourceQuota
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
Provide documentation on using the proxy resources configuration options or annotations to workaround LimitRange and ResourceQuota requirement. On clusters where these policies are in-place, pods creation will fail if the proxies don't have any resource requirements defined.
Note that using the CLI options will have a global effect on all proxies:
linkerd install --proxy-cpu-limit="200m" --proxy-cpu-request="50m" --proxy-memory-limit="64Mi" --proxy-memory-request="32Mi"
The config annotations work only on individual workloads, until https://github.com/linkerd/linkerd2/issues/2499 lands.
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 proxy resource configuration options and annotations described in this issue; verify the CLI example and the per-workload limitation against the existing website guidance. Done means the website explains how to avoid LimitRange and ResourceQuota pod-creation failures, includes the global CLI example, and distinguishes it from workload-specific annotations and issue #2499.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100