Skip to content
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

confusing documentation about rook. #161

Open
bayeslearner opened this issue Jul 30, 2023 · 1 comment
Open

confusing documentation about rook. #161

bayeslearner opened this issue Jul 30, 2023 · 1 comment
Labels
docs Improvements or additions to documentation

Comments

@bayeslearner
Copy link

In your documentation example about rook,
1,2,3 have rook:true but 3 doesn't have data disk available. 4 does have data disk available but rook:false is set.

How would this work? Shouldn't rook be needed to run on at least 3 nodes with data disks available? Although all nodes regardless whether it is also serving storage should be able run pods with rook storage claim?

@MusicDin MusicDin added the docs Improvements or additions to documentation label Jul 31, 2023
@MusicDin
Copy link
Owner

Hi @bayeslearner, thanks for pointing that out.

In the time of writing, the idea was to show how to exclude some nodes from the Rook cluster deployment (on excluded nodes, the additional volumes should remain intact and no Rook component should be deployed on them).
In addition, it was intended to show that Kubitect detects which nodes contain valid storage volumes for a Rook cluster. If a new volume is attached to the node later it will be automatically consumed by Rook.

However, with your questions in place, I see that this guide is not clear enough and needs to be updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants