Skip to content
Permalink
Browse files

Improve readability in persistent volume introduction (#17176)

* Fix typo in persistent volume intro

* Adjust wording of compute jargon
  • Loading branch information...
christophercarney authored and k8s-ci-robot committed Nov 5, 2019
1 parent 6b261c7 commit a7a4f9d4cbc1e1b2e11411cfe10a29bc10dffd9b
Showing with 1 addition and 1 deletion.
  1. +1 −1 content/en/docs/concepts/storage/persistent-volumes.md
@@ -25,7 +25,7 @@ This document describes the current state of `PersistentVolumes` in Kubernetes.

## Introduction

Managing storage is a distinct problem from managing compute. The `PersistentVolume` subsystem provides an API for users and administrators that abstracts details of how storage is provided from how it is consumed. To do this, we introduce two new API resources: `PersistentVolume` and `PersistentVolumeClaim`.
Managing storage is a distinct problem from managing compute instances. The `PersistentVolume` subsystem provides an API for users and administrators that abstracts details of how storage is provided from how it is consumed. To do this, we introduce two new API resources: `PersistentVolume` and `PersistentVolumeClaim`.

A `PersistentVolume` (PV) is a piece of storage in the cluster that has been provisioned by an administrator or dynamically provisioned using [Storage Classes](/docs/concepts/storage/storage-classes/). It is a resource in the cluster just like a node is a cluster resource. PVs are volume plugins like Volumes, but have a lifecycle independent of any individual Pod that uses the PV. This API object captures the details of the implementation of the storage, be that NFS, iSCSI, or a cloud-provider-specific storage system.

0 comments on commit a7a4f9d

Please sign in to comment.
You can’t perform that action at this time.