4 ms·
Do I understand correctly that the inclusion of YugabyteDB support in Rook's functionality is simply based on current unavailability of the relevant native Oper
by ablekh 6y ago
Do I understand correctly that the inclusion of YugabyteDB support in Rook'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.
- manigandham 6y agoNo, Yugabyte has their own K8S implementation, just like all the other databases that Rook supports. Rook is just reusing the storage operator to also deploy databases which I find strange and don’t recommend. Best to use it for storage only.
- ablekh 6y agoThank you for your reply. I have found relevant section in documentation. Speaking about using YugabyteDB independently, it appears that current Yugabyte K8s operator cannot be used in multi-zone configurations (which explains why I could not find mentioning it in relevant sections of documentation). Based on the following Crunchy Data documentation for related PostgreSQL K8s operator, multi-zone deployments require special considerations and, thus, K8s operators that are "multi-zone-enabled": https://access.crunchydata.com/documentation/postgres-operator/4.4.0/advanced/multi-zone-design-considerations https://access.crunchydata.com/documentation/postgres-operat....