-
Notifications
You must be signed in to change notification settings - Fork 29
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
Running CVMFS CSI on macOS K8S node #133
Comments
Hi @xkzl, macOS is unfortunately not supported at the moment. Squid's platform won't have any affect on -- it's what's running on the worker node that matters, and it must be Linux. |
Thank you for pointing this out. Is there any plan to have such support ? I understand that I should remove macOS arm computers from my k8s arm cluster for the time being. |
I'll propose this internally, but unfortunately I'm leaving the project. I'll leave this ticket open so someone else can take over. Of course if you want you can propose a PR yourself, but given we have no macOS nodes for our CI (and AFAIK there is no plan to procure any) and nowhere to test this, I don't think that in the current state it's realistic to provide a reliable macOS support. Maybe CVMFS folks can join in and see if we could get this driver to their CI, which would make things more feasible. |
Either that, or use node selectors to schedule cvmfs-csi and related workloads to Linux-based nodes. |
I have a kubernetes cluster with some macOS machines included. I ran into an issue installing CVMFS CSI due to too old kernel issue (looking at logs)
Is it fine to define a Linux based node as a Squid and then use the CSI on macOS based nodes ?
Should I use this specific machine running Linux as a master? Any suggestions would be very welcome.
The text was updated successfully, but these errors were encountered: