Fix typos in local PV blog (#8537)

This commit is contained in:
Michelle Au 2018-05-29 10:18:33 -07:00 committed by k8s-ci-robot
parent 023c663f40
commit e78a169d5b
1 changed files with 4 additions and 3 deletions

View File

@ -23,8 +23,9 @@ For those reasons, most applications should continue to use highly available, re
Some use cases that are suitable for local storage include: Some use cases that are suitable for local storage include:
* Caching of datasets that can leverage data gravity for fast processing * Caching of datasets that can leverage data gravity for fast processing
* Distributed storage systems that shard or replicate data across multiple nodes * Distributed storage systems that shard or replicate data across multiple
Examples include distributed datastores like Cassandra, or distributed file systems like Gluster or Ceph. nodes. Examples include distributed datastores like Cassandra, or distributed
file systems like Gluster or Ceph.
Suitable workloads are tolerant of node failures, data unavailability, and data loss. They provide critical, latency-sensitive infrastructure services to the rest of the cluster, and should run with high priority compared to other workloads. Suitable workloads are tolerant of node failures, data unavailability, and data loss. They provide critical, latency-sensitive infrastructure services to the rest of the cluster, and should run with high priority compared to other workloads.
@ -73,7 +74,7 @@ spec:
operator: In operator: In
values: values:
- my-node - my-node
``` ```
Note that theres a new nodeAffinity field in the PersistentVolume object: this is how the Kubernetes scheduler understands that this PersistentVolume is tied to a specific node. nodeAffinity is a required field for local PersistentVolumes. Note that theres a new nodeAffinity field in the PersistentVolume object: this is how the Kubernetes scheduler understands that this PersistentVolume is tied to a specific node. nodeAffinity is a required field for local PersistentVolumes.