You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i would like to ask for some more clearence, why mdadm was chosen?
as for now i'm trying to run eks with managed nodes + karpenter with bottlerocket, and it looks like that preparing disks before kubernetes will see active node is a bit better solution (in case we are not using old instance types, where it is needed to wait when ephemeral disk will be initialized), so i also wonder on the way how to make single space from several ephemeral disks.
my options were:
mdadm
lvm
zfs
and before creating my own bike, i found your solution... and would like to ask - what was the main reason to choose mdadm?
The text was updated successfully, but these errors were encountered:
Hello,
i would like to ask for some more clearence, why mdadm was chosen?
as for now i'm trying to run eks with managed nodes + karpenter with bottlerocket, and it looks like that preparing disks before kubernetes will see active node is a bit better solution (in case we are not using old instance types, where it is needed to wait when ephemeral disk will be initialized), so i also wonder on the way how to make single space from several ephemeral disks.
my options were:
and before creating my own bike, i found your solution... and would like to ask - what was the main reason to choose mdadm?
The text was updated successfully, but these errors were encountered: