The instructions to deploy a developer environment are useful and should
be part of the official documentation instead of being hidden in the
repo's README.md. Also, remove ancient documentation to deploy with
kubespray a multi-node env.
Also, add a warning to always run tests env in a virtual machine.
Closes: https://github.com/rook/rook/issues/9166
Signed-off-by: Sébastien Han <seb@redhat.com>
This is the first phase miscellaneous part of three phases to improve and
rework the Rook documentation for better user accessibility to the Rook
projects and with that the storage providers.
Phase two is about automatic generation of CRD documentation and phase
three is about reworking the docs themselves and, e.g., examples for
CRDs and certain use cases.
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
Both issues were already merged in Kubespray, so hopefully irrelevant anymore.
Co-authored-by: Yaniv Kaul <ykaul@redhat.com>
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
This is necessary as the current kubespray VM's dockerd engine
depreciated the --graph daemon option.
Signed-off-by: giovanism <giovanism@outlook.co.id>
This commit adds instructions to develop on a multi-node deployment,
which is somehow similar to a production setup.
It also proposes a development workflow approach to
write/build/test/ship
code to Rook.
Signed-off-by: Sébastien Han <seb@redhat.com>
Sébastien Han
Travis Nielsen
subhamkrai
Jiffin Tony Thottan
Alexander Trost
giovanism
Noah Watkins
Dmitry Yusupov
Yehuda Sadeh
Dan Mick