-
Notifications
You must be signed in to change notification settings - Fork 38.9k
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
Multipathing has to be supported in iscsi plugin. #39345
Comments
@rootfs PTAL. |
Can multipathed iscsi target have different Lun numbers.? For ex:
iic, its possible eventhough admins wont configure that way. If that is the case, we cannot just change the TP field in volume spec to an array and get this resolved. It need to accommodate different Lun numbers ..etc .. Any thoughts ? |
@fabiand Did you get a chance to look at this ? |
@humblec No, sadly not. |
👍 I think the change is simple - and I'd have done it the same way, by changing to a list of strings. |
I'm running into issue badly. If you have the cod change or a patch, i will be happy to test it out. |
Thanks. Let me give a try. 👍 |
Could this actually be an dupe of #21306 ? |
Automatic merge from submit-queue Add mulitpath support to iscsi plugin #issue #39345 Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
@fabiand The PR is merged in master and should be available from 1.6 :). Thanks! |
Kudos! |
Can this bug get closed? |
/assign |
/close |
Automatic merge from submit-queue Add mulitpath support to iscsi plugin #issue kubernetes/kubernetes#39345 Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
iic, most of the iscsi targets provide multipathing using
multiple iscsi target portals
for the sameIQN
, thus multiple paths through initiator connections in each of it. However, kubeiscsi
plugin is not capable of receiving multiple TPs in its volume spec, thus lack this functionality. If iscsi volume spec.target portal can receive an array ofIPs
orIPs:Port
instead of single value, the mounter can try to login in each path and get the mpath/mpio device created in the kubelet. but this require an API change.Any thoughts on this ?
The text was updated successfully, but these errors were encountered: