Update links to avoid redirects. (#5605)
This commit is contained in:
@@ -35,7 +35,7 @@ administrators. Kubernetes itself is unopinionated about what classes
|
||||
represent. This concept is sometimes called "profiles" in other storage
|
||||
systems.
|
||||
|
||||
Please see the [detailed walkthrough with working examples](/docs/user-guide/persistent-volumes/walkthrough/).
|
||||
Please see the [detailed walkthrough with working examples](/docs/concepts/storage/persistent-volumes/walkthrough/).
|
||||
|
||||
|
||||
## Lifecycle of a volume and claim
|
||||
|
||||
@@ -675,7 +675,7 @@ More details and examples can be found [here](https://github.com/kubernetes/exam
|
||||
ScaleIO is a software-based storage platform that can use existing hardware to create clusters of scalable
|
||||
shared block networked storage. The ScaleIO volume plugin allows deployed pods to access existing ScaleIO
|
||||
volumes (or it can dynamically provision new volumes for persistent volume claims, see
|
||||
[ScaleIO Persistent Volumes](/docs/user-guide/persistent-volumes/#scaleio)).
|
||||
[ScaleIO Persistent Volumes](/docs/concepts/storage/persistent-volumes/#scaleio)).
|
||||
|
||||
**Important:** You must have an existing ScaleIO cluster already setup and running with the volumes created before you can use them.
|
||||
{: .caution}
|
||||
|
||||
Reference in New Issue
Block a user