kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update _index.md

This commit is contained in:
PriyanshuAhlawat 2022-10-07 22:24:35 +05:30
parent 4de555282b
commit 1f9ea5579b
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
content/en/docs/reference/labels-annotations-taints/_index.md
View File

@ -116,16 +116,17 @@ This is useful if you want to target a specific namespace with a label
### kubernetes.io/limit-ranger
Example: `kubernetes.io/limit-ranger: LimitRanger plugin set: cpu, memory request for container nginx; cpu, memory limit for container nginx`
Example: `kubernetes.io/limit-ranger: "LimitRanger plugin set: cpu, memory request for container nginx; cpu, memory limit for container nginx"`
Used on: Namespace
Used on: Pod
Kubernetes by default doesn't provide any resource limit, that means unless you explicitly define limits,
your container can consume unlimited CPU and memory.
We can define default limit for pods by creating a LimitRange in the relevant namespace.
Pods deployed after this LimitRange will have these limits applied to them.
The annotation `limit-ranger` indicates that limits were requested for the pod and they were applied successfully.
For more details - [LimitRange](/docs/concepts/policy/limit-range)
You can define a default request or default limit for pods. You do this by creating a LimitRange in the relevant namespace.
Pods deployed after you define a LimitRange will have these limits applied to them.
The annotation `kubernetes.io/limit-ranger` records that resource defaults were specified for the Pod,
and they were applied successfully.
For more details, read about [LimitRanges](/docs/concepts/policy/limit-range).
### beta.kubernetes.io/arch (deprecated)