-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update local provisioner docs for 3.10 #8899
Conversation
---- | ||
<1> Name of the StorageClass. | ||
<2> Path to the directory on the host. It must be a subdirectory of *_/mnt/local-storage_*. | ||
<3> Path to the directory in the provisioner pod. We recommend using the same directory structure as used on the host. | ||
<3> Path to the directory in the provisioner pod. We recommend using the same directory structure as used on the host and `mountDir` can be omitted in this case. | ||
|
||
With this configuration, the provisioner creates: | ||
|
||
* One PV with StorageClass `local-ssd` for every subdirectory in *_/mnt/local-storage/ssd_*. | ||
* One PV with StorageClass `local-hdd` for every subdirectory in *_/mnt/local-storage/hdd_*. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In openshift 3.10, local provisioner will create PV just for mountpoint.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
In openshift 3.10, we can remove the "Adding New Devices" part or change this part. A new mountpoint can be created after local provisioner ds is running. But the PV still maybe not be created for permission denied. So, the administrators need run the command again: |
Do we need add a part for how to using local volume from WEBUI in this PR? |
0f7ec4b
to
0c8f854
Compare
I kept it there to mention SELinux relabeling. |
TODO: add documentation about block devices |
block devices are alpha upstream, so no documentation nor support |
@@ -27,37 +27,9 @@ The local volume provisioner allows using local storage within {product-title} a | |||
|
|||
[NOTE] | |||
==== | |||
Local volumes is an alpha feature and may change in a future release of {product-title}. | |||
Local volumes is a technical preview feature and may change in a future release of {product-title}. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/technical preview/Technology Preview
You should also add the IMPORTANT note: https://mojo.redhat.com/docs/DOC-1124368
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replaced with IMPORTANT from the mojo page.
The `LocalPersistentVolumes` alpha feature now also requires the `VolumeScheduling` alpha feature. This is a breaking change, and the following changes are required: | ||
[WARNING] | ||
==== | ||
Syntax of the ConfigMap has changed between {product-title} 3.9 and 3.10. Since this feature is in technical preview, the ConfigMap is not converted automatically during update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/technical preview/Technology Preview
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
@@ -189,13 +157,14 @@ The provisioner runs as root to be able to clean up the directories when a PV is | |||
|
|||
[[local-volume-adding-new-devices]] | |||
=== Adding New Devices | |||
Adding a new device requires several manual steps: | |||
Adding new device is semi-automatic. The provisioner periodically checks for new mounts in configured directories. Admin just needs to create a new subdirectory there, mount a device there and allow pods to use the device by applying SELinux label on it: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/Adding new device/Adding a new device
s/Admin just needs to/The administrator needs to
s/mount a device there/mount a device there,
s/by applying SELinux label on it:/by applying the SELinux label:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you consider making the other suggested changes? Thanks.
@jsafrane I suggested a few edits. Thanks. |
0c8f854
to
f64da18
Compare
@tmorriso-rh, I applied you suggestions, PTAL |
@jsafrane I think this is ready to merge. Can you remove/squash the extra commit? We require all PRs to have only 1 commit before we can merge. By squashing your merge commits into one commit, you are making it easier for us to understand the scope of your work. Thanks. |
- Fixed local provisioner config map syntax for 3.10 - Removed alpha features for local storage.
f64da18
to
d2a449a
Compare
Squashed, PTAL |
/cherrypick enterprise-3.10 |
@ahardin-rh: new pull request created: #9465 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1569911
@tmorriso-rh, PTAL