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
We should extend the current local setup guide with a working end to end flow.
I would suggest to use two base requirements regarding the Kubernetes cluster:
Using Minikube (as we need local storage to get rook + Ceph running)
Real dev cluster and the requirements needed to get e.g. the dynamic based provisioning of Ceph running
Additionally we should add/or reference a conclusive set of sample manifests from the onmetal-api project for VolumePool, VolumeClass and Volume which can be used to validated that the cephlet manager is behaving as expected.
go >= 1.19
git, make and kubectl
[Kustomize](https://kustomize.io/)
[Minikube](https://minikube.sigs.k8s.io/docs/) or a real cluster
and
Rook cluster
Raw devices (no partitions or formatted filesystems)
This requires lvm2 to be installed on the host. To avoid this dependency, you can create a single full-disk partition on the disk (see below)
Raw partitions (no formatted filesystem)
Persistent Volumes available from a storage class in block mode
with the following steps on how to run a simple rook cluster ect. ?
Summary
We should extend the current local setup guide with a working end to end flow.
I would suggest to use two base requirements regarding the Kubernetes cluster:
Additionally we should add/or reference a conclusive set of sample manifests from the
onmetal-api
project forVolumePool
,VolumeClass
andVolume
which can be used to validated that thecephlet
manager is behaving as expected./ref
https://rook.io/docs/rook/v1.9/Getting-Started/quickstart/
/cc @EvgeniaOrfeeva
The text was updated successfully, but these errors were encountered: