I have some experience with Ceph, both for work, and with homelab-y stuff. First, bear in mind that Ceph is a distributed storage system - so the idea is that you will have multiple nodes. For learning, you can definitely virtualise it all on a single box - but you'll have a better time with discrete physical machines. Also, Ceph does prefer physical access to disks (similar to ZFS). And you do need decent... - Source: Hacker News / 5 months ago

Another option is to leverage a Kubernetes-native distributed storage solution such as Rook Ceph as the storage backend for stateful components running on Kubernetes. This has the benefit of simplifying application configuration while addressing business requirements for data backup and recovery such as the ability to take volume snapshots at a regular interval and perform application-level data recovery in case... - Source: dev.to / 6 months ago

This is beyond your question but might help someone else: I switch from docker-compose to kubernetes for my home lab a while ago. The storage solution I've settled on is Rook. It was a bit of up-front work learning how to get it up but now that it's done my storage is automatically managed by Ceph. I can swap out drives and Ceph basically takes care of everything itself. Source: 12 months ago

The stumbling point I am at is I want to use rook.io(Ceph) as my storage solution for the cluster. The Ceph prerequisites are one of the following:. Source: about 1 year ago

Storage: Favor any distributed storage you know to start with for Persistent Volumes: Ceph maybe via rook.io, Longhorn if you go rancher etc. Source: over 1 year ago

The fire continued to blaze onward. We created SIGs - Special Interest Groups - to gather people weekly or bi-weekly to discuss specific areas of interest. I co-created and co-led SIG-Apps. My interest was figuring out how to make it easy to build, install and manage applications in Kubernetes and the tools we needed on top of Kubernetes. I contributed to Helm and Draft in particular around this time as there was... - Source: dev.to / 1 day ago

Step-1:  Install CloudNativePG operator on your running Kubernetes, best way to deploy using Helm. - Source: dev.to / 2 days ago

Kubernetes Documentation: https://kubernetes.io/docs/home/ Kubernetes Tutorials: https://kubernetes.io/docs/tutorials/ Kubernetes Community: https://kubernetes.io/community/ Prometheus: https://prometheus.io/ Grafana: https://grafana.com/ Elasticsearch: https://www.elastic.co/elasticsearch/ Kibana: https://www.elastic.co/kibana Helm: https://helm.sh/ Prometheus Helm Chart:... - Source: dev.to / 20 days ago

Applying Kubernetes manifests individually is problematic because files can get overlooked. Packaging your applications as Helm charts lets you version your manifests and easily repeat deployments into different environments. Helm tracks the state of each deployment as a "release" in your cluster. - Source: dev.to / about 2 months ago

It’s also well understood that having a k8s cluster is not enough to make developers able to host their services - you need a devops team to work with them, using tools like delivery pipelines, Helm, kustomize, infra as code, service mesh, ingress, secrets management, key management - the list goes on! Developer Portals like Backstage, Port and Cortex have started to emerge to help manage some of this complexity. - Source: dev.to / 4 months ago