Is your feature request related to a problem? Please describe (π if you like this request)
After the feature: [FEATURE] Support storage network for RWX volumes.
We can now make all data paths on the storage network but for the Harvester use case (which means RWX volume support for guest cluster).
We would not want to expose the storage network on the guest cluster. Could we consider supporting the other extra network interface instead of the storage network?
For example, the Harvester cluster creates vlan100 for the guest VM. Can we have the endpoint with vlan100 on the share-manager pod?
(In this case, we could not set the storage network for an endpoint on the share-manager pod)
Related issue: [ENHANCEMENT] Support various vlan for RWX volume on the guest cluster
cc @innobead, @derekbit, @c3y1huang, @bk201
Describe the solution you'd like
Could we add the network related info to the Longhorn attachment ticket?
Then, the share-manager pod would know what interface should be used for the endpoint.
Describe alternatives you've considered
No response
Additional context
No response
Is your feature request related to a problem? Please describe (π if you like this request)
After the feature: [FEATURE] Support storage network for RWX volumes.
We can now make all data paths on the storage network but for the Harvester use case (which means RWX volume support for guest cluster).
We would not want to expose the storage network on the guest cluster. Could we consider supporting the other extra network interface instead of the storage network?
For example, the Harvester cluster creates vlan100 for the guest VM. Can we have the endpoint with vlan100 on the share-manager pod?
(In this case, we could not set the storage network for an endpoint on the share-manager pod)
Related issue: [ENHANCEMENT] Support various vlan for RWX volume on the guest cluster
cc @innobead, @derekbit, @c3y1huang, @bk201
Describe the solution you'd like
Could we add the network related info to the Longhorn attachment ticket?
Then, the share-manager pod would know what interface should be used for the endpoint.
Describe alternatives you've considered
No response
Additional context
No response