Just to add to warm fuzzy feeling, although just in a homelab, I'm using
rook for many years now, it's awesome. I trust* it with the family
photo's on a selfhosted nextcloud. All on K8s/Ceph/RGW.
Hans
* I have backups though ;)
On 3/7/22 09:45, Bo Thorsen wrote:
Hi Nico and Janne,
Thank you very much for your quick answers. I did investigate rook
already and had the feeling this might be the answer. But one of the
things that is extremely hard is to find The Right Way (TM) to handle
the setup I want. Getting the warm fuzzy feeling that I chose the proper
way forward is difficult. You helped me do that, so thank you :)
Bo.
Den 07-03-2022 kl. 09:39 skrev Nico Schottelius:
Good morning Bo,
as Janne pointing out, rook is indeed a very good solution for k8s based
clusters.
We are even replacing our native Ceph clusters with rook, as it feels
smarter in a long term perspective than setting on cephadm.
Rook also allows to inject quite some parameters and while it is a bit
learning k8s in the beginning, it is sufficiently flexible to allow any
Ceph tuning that you'd have done without it.
Bo Thorsen <bo@xxxxxxxxxxxxxxxxxx> writes:
So here's my idea on how to solve this problem: Add a 1TB SSD in each
worker node and let ceph use these disks for storage.
This is probably best done using the auto capture of disks, which rook
supports by default.
Best regards,
Nico
--
Sustainable and modern Infrastructures by ungleich.ch
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
