The most complicated Ceph installation yet... (Ceph Rook in Kubernetes)
HTML-код
- Опубликовано: 19 ноя 2023
- I looked into the Ceph Rook orchestrator, which is the precursor to the Ceph admin tooling. This installation uses a Kubernetes installation to deploy a cluster and scale it up and down. Sadly, the Ceph GUI doesn't have much control, so all changes are made with Kubernetes manifests from the command line.
Get Proficient knowledge in Azure services and infrastructures, managing cloud resources, cloud security with our Cloud Support Associate Certificate !
imp.i384100.net/c/3402234/203...
CodeCombat Live Online Coding Classes
codecombat.com/payments/initi...
Use promo code explorer10 at checkout for 10% discount.
Join the channel to get access to more perks:
/ @danielpersson
Or visit my blog at:
danielpersson.dev
Outro music: Sanaas Scylla
#ceph #rook #kubernetes
quite good start-up explanations! Thank you men! By your videos I've rolled into ceph understanding
What's the use case? I have ceph on my local homelab proxmox using DHCP isp, which is having the darndest time connecting kubernetes to my static ip host. My local proxmox is about 13TB, while my static host is only 200GB. I wonder if this is a good use case, or a bad use case, since 1) It's really hard to connect a kubernetes on a static IP to DHCP isp 2) only 200GB disk space on static ip host 3) only 20 MB/s upload on my homelab (300 mirrored on the other, 500 down on homelab) ?
Hi Charg
I don't think it's a good use-case in any setup. It might be a little easier to run it in Kubernetes if you only use the cluster from Kubernetes resources. Otherwise I would not use this setup at all.
I hope this helps.
Best regards
Daniel
@@DanielPersson yes, that's the idea, creating a fabric of resources using our kubernetes
@DanielPersson is the reason you would not use this setup because of the added complexity of maintaining a k3s cluster or are there configurations / features missing in rook relative to cephadm? Curious about the difference because cephadm also orchestrates containers like Kubernetes
Hi.
The reason it's more complicated is because it has more rough edges. This is the early implementation of CephAdm and all the quirks that they found when creating Rook drove them to create CephAdm to make, the flow simpler and more configurable.
I think that if you know Kubernetes well and are willing to tinker then it will be a good solution but you don't have as many helpful tools. Then again Rook is older so there might be more documentation.
I hope this clarify my thoughts. Thank you for watching my videos.
Best regards
Daniel
You seem like a kind person so i will put this politely... please don't use half of your screen to advertise some product/service. You are using the cli and the terminal is at bottom, people are not able to see sh*t!!! ffs view your edited video before you upload.Thank you