I was able to resolve it by using the "weave net" network on k8s instead of Flannel. For this i had to reinstall the environment (thanks for Florian C).
This can be added in the documentation - that we require a specific pod network.
Also i didn't see the step for 'kubectl create namespace test' which is required to run the tests as they are in the test namespace.
acd13
3 Posts
0
December 18th, 2019 09:00
Yes that's fine.
I was able to resolve it by using the "weave net" network on k8s instead of Flannel. For this i had to reinstall the environment (thanks for Florian C).
This can be added in the documentation - that we require a specific pod network.
Also i didn't see the step for 'kubectl create namespace test' which is required to run the tests as they are in the test namespace.
Anjan
SJ-CSI
1 Rookie
•
5 Posts
0
December 17th, 2019 07:00
Hi,
Is the Isilon cluster ip and credentials (secret) provided correct? can you connect to the ip with those credentials from your K8S cluster?
SJ-CSI
1 Rookie
•
5 Posts
0
December 18th, 2019 16:00
Thanks for the updates and suggestions.
We have verified driver with Flannel. Probably some issue with the Flannel network setup.
There is step mentioned in the Product Guide to create "test" namespace under "Test the CSI Driver".
Thanks!
cocampbe
36 Posts
0
January 16th, 2020 09:00
@acd13 I am using canal and have not had this issue. I am running RKE. So YMMV.
Reem.9
5 Posts
0
February 24th, 2021 06:00
I have the same issue, is there any solution for that ?