Cloud Native Computing Foundation Announces Rook Graduation

For the uninitiated: Rook is a deployment tool for Ceph and a few databases on Kubernetes. The heavy lifting is done by Ceph, the name is only mentioned in passing in the 10th paragraph.

Is it just me or is the CNCF ran by a bunch of marketers and product managers?<p>The entire &#x27;ecosystem&#x27; is filled with worthless crap like this with stupid marketing like &quot;incubating&quot; and &quot;graduation&quot; to infer on it some level of acceptance.<p>Are there any foundations that don&#x27;t operate like this? Are foundations good at all for anything?

Actual project here: <a href="https:&#x2F;&#x2F;rook.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;rook.io&#x2F;</a><p>Block, file, object storage for K8S, powered by Ceph underneath. The project is diluted by also deploying databases for some reason, and I don&#x27;t recommend using it for that.<p>Overall good to see more storage options for K8S with others like Longhorn, OpenEBS, StorageOS, Portworx, etc.

I’ve ran rook for a couple of months in my test lab on virtual machines. Absolutely love it and has been super stable. Does anyone run this on bare metal in production? Running this as a hyper converge k8s setup sound like its easy to scale even if you colocate your own hardware in a dc. Which is way cheaper then cloud these days. Anyone with experience?

Has anyone used ceph in production? If so, are there are any advanatages of using Ceph over Aws S3? It used to be pretty popular during openstack days. Lately, I havent herd much about it.

Do I understand correctly that the inclusion of YugabyteDB support in Rook&#x27;s functionality is simply based on current unavailability of the relevant native Operator by Yugabyte itself? If someone from Yugabyte is reading this, I would appreciate their comment on plans to implement such Operator. That would allow people who do not need on-premise data storage to avoid establishing and maintaining an additional significant dependency in the form of Rook.

If cluster experience problems to run rook pods, then other pods that uses volumes will fail too. And it may cause situation where everything fails with timeout errors...<p>Nothing against rook, but the idea to run k8s storage in k8s is fragile