Skip to content
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.

Sign up for GitHub

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

docs: add configurable export IP in csi-unity #1054

Merged
merged 4 commits into from
Apr 18, 2024
Merged

docs: add configurable export IP in csi-unity #1054

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f34d157
docs: add configurable export IP in csi-unity
mdutka-dell Apr 4, 2024
259cb7b
docs: change release version in template
mdutka-dell Apr 11, 2024
d863b2c
fix docs folder
mdutka-dell Apr 17, 2024
64238ce
add parameter to csm operator installation page
cbartoszDell Apr 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions content/docs/csidriver/features/unity.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -711,3 +711,16 @@ data:
TENANT_NAME: ""
```
>Note: csi-unity supports Tenancy in multi-array setup, provided the TenantName is the same across Unity XT instances.

## Support custom networks for NFS I/O traffic

When `allowedNetworks` is specified for using custom networks to handle NFS traffic, and a user already
has workloads scheduled, there is a possibility that it might lead to backward compatibility issues. For example, ControllerUnPublish might not be able to completely remove clients from the NFS exports of previously created pods.

Also, the previous workload will still be using the default network and not custom networks. For previous workloads to use custom networks, the recreation of pods is required.

When csi-unity driver creates an NFS export, the traffic flows through the client specified in the export. By default, the client is the network interface for Kubernetes
communication (same IP/fqdn as k8s node) by default.

For a cluster with multiple network interfaces and if a user wants to segregate k8s traffic from NFS traffic; you can use the `allowedNetworks` option.
`allowedNetworks` takes CIDR addresses as a parameter to match the IPs to be picked up by the driver to allow and route NFS traffic.
Loading
Loading