-
Notifications
You must be signed in to change notification settings - Fork 34
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
Question regarding physical storage #1635
Comments
Yes, that should work, though slightly different from what you are proposing. For persistence you would pass an Ignition config via PXE that instructs the worker to mount the NFS export at a desired location, then run your workloads from there, and also use it as persistent storage. A simple example can be found here: https://www.flatcar.org/docs/latest/setup/storage/mounting-storage/#mounting-nfs-exports |
To arrive at a functional configuration I recommend you iterate on a test set-up using qemu in a local VM. Our "getting started" guide has you covered: https://www.flatcar.org/docs/latest/installing/ While there are fundamental differences between in-memory PXE boot and running Flatcar in a local VM, it's likely the fastest way to get to a set-up where Flatcar mounts an NFS export and your workload applications can use it. |
Hello,
I'm planning to use Flatcar for a cluster of 3 devices.
Only one of the three has physical storage. It would act as the master node.
Each of the two others only have SPI module (16MB) to hold their bootloader.
Is it possible to perform PXE boot for the two workers sharing one NFS storage for their OS + data?
The text was updated successfully, but these errors were encountered: