whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #25948 from ydFu/add-code-blocks

Browse Source 
Add Code blocks in limit-storage-consumption.md
This commit is contained in:
Kubernetes Prow Robot
2021-01-04 23:47:57 -08:00
committed by GitHub
parent f8fd6d9bea 8d50a4c4d7
commit 34b84f9a7f
1 changed files with 2 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/administer-cluster/limit-storage-consumption.md
+2 -9
View File
@@ -12,7 +12,6 @@ The following resources are used in the demonstration: [ResourceQuota](/docs/con
and [PersistentVolumeClaim](/docs/concepts/storage/persistent-volumes/). and [PersistentVolumeClaim](/docs/concepts/storage/persistent-volumes/).
## {{% heading "prerequisites" %}} ## {{% heading "prerequisites" %}}
@@ -41,7 +40,7 @@ the values set by the admin.
In this example, a PVC requesting 10Gi of storage would be rejected because it exceeds the 2Gi max. In this example, a PVC requesting 10Gi of storage would be rejected because it exceeds the 2Gi max.
``` ```yaml
apiVersion: v1 apiVersion: v1
kind: LimitRange kind: LimitRange
metadata: metadata:
@@ -67,7 +66,7 @@ In this example, a 6th PVC in the namespace would be rejected because it exceeds
a 5Gi maximum quota when combined with the 2Gi max limit above, cannot have 3 PVCs where each has 2Gi. That would be 6Gi requested a 5Gi maximum quota when combined with the 2Gi max limit above, cannot have 3 PVCs where each has 2Gi. That would be 6Gi requested
for a namespace capped at 5Gi. for a namespace capped at 5Gi.
``` ```yaml
apiVersion: v1 apiVersion: v1
kind: ResourceQuota kind: ResourceQuota
metadata: metadata:
@@ -78,8 +77,6 @@ spec:
requests.storage: "5Gi" requests.storage: "5Gi"
``` ```
<!-- discussion --> <!-- discussion -->
## Summary ## Summary
@@ -87,7 +84,3 @@ spec:
A limit range can put a ceiling on how much storage is requested while a resource quota can effectively cap the storage A limit range can put a ceiling on how much storage is requested while a resource quota can effectively cap the storage
consumed by a namespace through claim counts and cumulative storage capacity. The allows a cluster-admin to plan their consumed by a namespace through claim counts and cumulative storage capacity. The allows a cluster-admin to plan their
cluster's storage budget without risk of any one project going over their allotment. cluster's storage budget without risk of any one project going over their allotment.