Commit 373d5afe authored by markturansky's avatar markturansky

fixed link in pv doc

parent bd365dda
...@@ -77,7 +77,7 @@ Each PV contains a spec and status, which is the specification and status of the ...@@ -77,7 +77,7 @@ Each PV contains a spec and status, which is the specification and status of the
### Capacity ### Capacity
Generally, a PV will have a specific storage capacity. This is set using the PV's `capacity` attribute. See the Kubernetes [Resource Model](./resources.md) to understand the units expected by `capacity`. Generally, a PV will have a specific storage capacity. This is set using the PV's `capacity` attribute. See the Kubernetes [Resource Model](./design/resources.md) to understand the units expected by `capacity`.
Currently, storage size is the only resource that can be set or requested. Future attributes may include IOPS, throughput, etc. Currently, storage size is the only resource that can be set or requested. Future attributes may include IOPS, throughput, etc.
...@@ -145,7 +145,7 @@ Claims use the same conventions as volumes when requesting storage with specific ...@@ -145,7 +145,7 @@ Claims use the same conventions as volumes when requesting storage with specific
### Resources ### Resources
Claims, like pods, can request specific quantities of a resource. In this case, the request is for storage. The same [resource model](./resources.md) applies to both volumes and claims. Claims, like pods, can request specific quantities of a resource. In this case, the request is for storage. The same [resource model](./design/resources.md) applies to both volumes and claims.
## <a name="claims-as-volumes"></a> Claims As Volumes ## <a name="claims-as-volumes"></a> Claims As Volumes
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment