diff options
| author | Michelle Au <msau@google.com> | 2017-04-10 14:43:32 -0700 |
|---|---|---|
| committer | Michelle Au <msau@google.com> | 2017-04-10 14:43:32 -0700 |
| commit | 70301e5aa7f9310f5450d2bc8caaa6e2a4af7a55 (patch) | |
| tree | 5d55ccea5b0f94c003572761d0688c1c9c474fde | |
| parent | 86f560ac79b89483d903913130aedaf3009422d5 (diff) | |
Add FAQ about LocalStorage PV partitions
| -rw-r--r-- | contributors/design-proposals/local-storage-overview.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/contributors/design-proposals/local-storage-overview.md b/contributors/design-proposals/local-storage-overview.md index 07329a61..920a86f3 100644 --- a/contributors/design-proposals/local-storage-overview.md +++ b/contributors/design-proposals/local-storage-overview.md @@ -581,6 +581,9 @@ Since older kubelets will not surface capacity of shared partitions, the schedul Kubelet will attempt to enforce capacity limits on a best effort basis. If the underlying container runtime cannot surface usage metrics for the writable layer, then kubelet will not provide capacity isolation for the writable layer. +### Are LocalStorage PVs required to be a whole partition? + +No, but it is the recommended way to ensure capacity and performance isolation. For HDDs, a whole disk is recommended for performance isolation. In some environments, multiple storage partitions are not available, so the only option is to share the same filesystem. In that case, directories in the same filesystem can be specified, and the adminstrator could configure group quota to provide capacity isolation. # Features & Milestones |