Unsolved
2 Posts
0
971
June 9th, 2020 02:00
Multiple Isilon CRDs defined, but only single a Storage Class created
We’ve run into a curious issue. While we can define multiple CRDs for each Isilon instance, the controller does not seem to be creating Storage Classes for each instance:
$ kubectl get csiisilon
NAME AGE
rridc02-dev 15m
rridc03-dev 31m
$ kubectl get storageclasses
NAME PROVISIONER AGE
rridc02-dev-storageclass (default) csi-isilon.dellemc.com 18m
I confirmed this by removing and republishing rridc03-dev, which resulted in this:
$ kubectl get csiisilon
NAME AGE
rridc02-dev 32m
rridc03-dev 2s
$ kubectl get storageclasses
NAME PROVISIONER AGE
rridc03-dev-storageclass (default) csi-isilon.dellemc.com 4s
The controller seems to only be creating a Storage Class for the last added CSIIsilon CRD.
No Events found!
Flo_csI
2 Intern
•
167 Posts
0
June 10th, 2020 02:00
Unfortunately, that configuration is not supported today.
The Isilon CSI Driver has the provisioner value (csi-isilon.dellemc.com) hard-coded. As a consequence, we support only access to one Isilon cluster at a time. No matter how many instances of the driver you install.
We might be able to find a workaround depending on your setup.
Please contact me in PM and indicate your email address if you want to carry on the discussion with more details on your architecture.
wltbenade
2 Posts
0
June 10th, 2020 04:00
Thanks for the confirmation, @Flo_csI
I'll PM you with our scenario to see what can be done.