-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSASINFRA-3718: Draft content #99259
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
base: main
Are you sure you want to change the base?
Conversation
Add documentation for manila csi changes to allow multiple access rules
|
@gouthampacha: This pull request references OSASINFRA-3718 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.21.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 Wed Sep 17 20:04:59 - Prow CI generated the docs preview: |
modules/persistent-storage-csi-manila-dynamic-provisioning.adoc
Outdated
Show resolved
Hide resolved
maxwelldb
left a comment
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.
Very good start. TYVM! I'll have some mod docs stuff to add later.
modules/persistent-storage-csi-manila-dynamic-provisioning.adoc
Outdated
Show resolved
Hide resolved
| [NOTE] | ||
| ==== | ||
| The `nfs-ShareClient` parameter accepts various formats: | ||
| * Single IP address: `192.168.1.100` | ||
| * CIDR subnet: `10.0.0.0/24` | ||
| * Multiple entries: `10.0.0.0/24,192.168.1.100,172.16.0.0/16` | ||
| Ensure that the specified IP addresses or subnets include the {product-title} cluster nodes to allow proper mounting of the persistent volumes. | ||
| ==== | ||
|
|
||
| [IMPORTANT] | ||
| ==== | ||
| When using custom storage classes with restricted access rules, ensure that: | ||
| * The specified IP addresses or subnets include all {product-title} nodes that need to access the storage. | ||
| * The Manila service in {rh-openstack} supports the share type specified in the storage class. | ||
| * Network connectivity exists between the allowed clients and the Manila share servers. | ||
| ==== |
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.
I'll likely break this out into an additional little module. Very good start though!
|
@gouthampacha: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
|
The This is because your PR targets the If the update in your PR does NOT apply to version 4.21 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main. |
|
PR needs rebase. 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-sigs/prow repository. |
Add documentation for manila csi changes
to allow multiple access rules