-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
should upgrade rook to 1.0 with rook-storage-service docs to make it work with the current develop branch #79
Comments
rook 0.9 works on teracy-dev v0.3.0, rook 1.0 did not work on teracy-dev v0.3.0 with my check, the difference was that: rook 0.9 created OSD when preparing, but rook 1.0 did not.
|
use this cluster.yaml config file with rook 1.0 and teracy-dev-k8s v0.3.0 should work: apiVersion: ceph.rook.io/v1
kind: CephCluster
metadata:
name: rook-ceph
namespace: rook-ceph
spec:
cephVersion:
# For the latest ceph images, see https://hub.docker.com/r/ceph/ceph/tags
image: ceph/ceph:v14.2.1-20190430
dataDirHostPath: /var/lib/rook
mon:
count: 3
allowMultiplePerNode: false
dashboard:
enabled: true
storage:
useAllNodes: true
useAllDevices: true
directories:
- path: /var/lib/rook note the |
should be fixed by #85 |
@hieptranquoc please verify that rook 1.0 works well on the current develop branch, following this docs https://github.com/teracyhq-incubator/teracy-dev-k8s/blob/develop/docs/rook-storage-service.md and you can deploy sample pods with PVC successfully usng the rook storageclass. |
teracy-k8s on develop branch works well on the rook version 1.0! |
to the latest version (1.0) and make sure everything works.
Currently, I could not use the storageclass for a pod to run
it works with teracy-dev-k8s v0.3.0, but not with the current develop branch.
The text was updated successfully, but these errors were encountered: