Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Commit

Permalink
Use 80 columns
Browse files Browse the repository at this point in the history
  • Loading branch information
rata committed Aug 14, 2019
1 parent c1e376a commit 9faf488
Showing 1 changed file with 31 additions and 21 deletions.
52 changes: 31 additions & 21 deletions docs/advanced/node-local-storage.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,9 +25,9 @@ to use one Persistent Volume in the host. However, see the section below to see
how to create more than one Persistent Volume per node.

The Kubernetes documentation on Local Persistent Volumes using filesystem mode is
[here](https://kubernetes.io/docs/concepts/storage/volumes/#local) (mixed with block mode).
[here](https://kubernetes.io/docs/concepts/storage/volumes/#local) (mixed with
block mode).


Bear in mind that this section is about the filesystem mode, not the block mode.
That will be covered on a different section of this document.

Expand Down Expand Up @@ -215,11 +215,11 @@ What if you want to delete this application and use the PVs for a different
application?

Basically, as the retain policy is set to `Retain` (just to be safe), you need
to do some manual operations documented
[here](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#retain)
to do some manual operations documented [here][1]. Note that using the `Delete`
policy this is different, so you may want to choose the policy that better fits
your use case.

Note that using the `Delete` policy this is different, so you may want to choose
the policy that better fits your use case.
[1]: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#retain

### Automatic Local Persistent Volume creation and handling

Expand Down Expand Up @@ -248,30 +248,40 @@ This is the only automated setup supported in Lokomotive at the time of this
writing.

1. You can share the volume in different PVs if you create a sub-directory per
PV, bind mount each of them and only expose the subdirectories. It is
explained in detail [here](https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/blob/master/docs/operations.md#sharing-a-disk-filesystem-by-multiple-filesystem-pvs).
But take into account that it needs to be done manually.
PV, bind mount each of them and only expose the subdirectories. It is explained
in detail [here][1]. But take into account that it needs to be done manually.

1. When using `setup_raid = "true"` the filesystem is `ext4` and there is no
way to use different one right now.

1. When using `setup_raid = "true"` the filesystem is `ext4` and there is no way
to use different one right now.
[1]: https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/blob/master/docs/operations.md#sharing-a-disk-filesystem-by-multiple-filesystem-pvs

### Operation and FAQs

* [Recommendations and tips on how to operate](https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/blob/master/docs/operations.md). Bear in mind, however, that the provisioner is not being used in Lokomotive
* [Recommendations and tips on how to operate][1]. Bear in mind, however, that the provisioner is not being used in Lokomotive
right now.

* You may also want to check out the [FAQs](https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/blob/master/docs/faqs.md)
* You may also want to check out the [FAQs][2].

[1]: https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/blob/master/docs/operations.md
[2]: https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/blob/master/docs/faqs.md

### Useful links

There are several other useful links:

* [Best practices](https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/blob/master/docs/best-practices.md). Lokomotive is following them at the time of this writing, except for using UUID in fstab.

* More documentation about [access control](https://kubernetes.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/#access-control) that might be useful for several apps
sharing a volume.

Furthermore, in [this blog post](https://kubernetes.io/blog/2019/04/04/kubernetes-1.14-local-persistent-volumes-ga/) there are some highlights not well documented anywhere else and some useful tips from Uber's experience when operating Local Persistent Volumes.
* [Best practices][1]. Lokomotive is following them at the time of this writing, except for using UUID in fstab.

* More documentation about [access control][2] that might be useful for several apps sharing a volume.

[1]: https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/blob/master/docs/best-practices.md.
[2]: https://kubernetes.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/#access-control

Furthermore, in [this blog post][3] there are some highlights not well
documented anywhere else and some useful tips from Uber's experience when
operating Local Persistent Volumes.

[3]: https://kubernetes.io/blog/2019/04/04/kubernetes-1.14-local-persistent-volumes-ga/

Here is a short copy paste of some highlights, in case the blog post is lost in
the future.
Expand Down Expand Up @@ -331,8 +341,8 @@ https://docs.okd.io/latest/install_config/configuring_local.html#local-volume-ra
## Using OpenEBS Local PV

OpenEBS seems to have a mode to use node local storage, but is not available in
any stable release as the time of this writing. For that reason, it was not
evaluated and left for future research.
any stable release as the time of writing. For that reason, it was not evaluated
and left for future research.

Some links that might be relevant when looking into this:

Expand Down

0 comments on commit 9faf488

Please sign in to comment.