KubeDB 0.12.0 brings MongoDB sharding and MySQL clustering support, fixes PostgreSQL WAL archiving bugs for Azure and MinIO and improves the overall stability of the operator.
[MongoDB] MongoDB sharding
Finally, MongoDB Sharding is here in KubeDB! It will be a part of kubedb
0.12.0release. Documentation is added. Try it out and feel free to give your feedback. SSL support is not added yet. Hopefully, SSL support will be a part of
[MySQL] MySQL clustering - Group replication without InnoDB
MySQL Group replication is added in
0.12.0. Documentation is also added. More MySQL clustering feature will be added in the future. Feel free to try and give your feedback.
[Postgres] WAL-archiving to Minio broken
Postgres WAL-archiving to Minio is supported now. Both SSL or non-SSL will work. Documentation is also added for minio.
[Postgres] wal-g: Postgres Continuous Archiving to Swift failing
The issue is fixed in master. It will be a part of
[Postgres] Support Local volume for PostgreSQL WAL archiving
Postgres WAL-archiving to Local volume is supported now. Documentation is also added.
[Postgres] PostgreSQL 11.2
Postgres 11.2 support is added.
[MongoDB] Use official Mongo GO Driver for testing MongoDB
Mongo has released their official GO driver recently. We have updated our driver to mongodb official go driver in mongodb E2E testing.
[CLI] kubedb - MethodNotAllowed
Users sometimes got this error while running
kubedb get dormantdatabases, because there were two resources whose plural name was
dormantdatabases. These two resources were
dormantdatabases.validators.kubedb.com. The workaround is given in issue comment. It is fixed in the master branch, so, user will not face this after
Assign resources for init containers
Resources for init containers was not applied in the past. This issue is fixed in the master branch. This will be a part of
Snapshot to minio with SSL
Snapshot to minio with SSL was failing. It is fixed in the master branch. This will be a part of
Kubedb 0.11 missing rbac permissions error
There was an issue while upgrading from
0.11.0. The workaround is given in issue comment. The issue is solved in the master branch, so, it will not be an issue while upgrading to