You are looking at the documentation of a prior release. To read the documentation of the latest release, please
visit here.
New to KubeDB? Please start here.
This guide will give you an overview on how KubeDB Enterprise operator upgrade the version of MariaDB
database.
KubeDB
concepts:The following diagram shows how KubeDB Enterprise operator used to upgrade the version of MariaDB
. Open the image in a new tab to see the enlarged version.
The upgrading process consists of the following steps:
At first, a user creates a MariaDB
Custom Resource (CR).
KubeDB
Community operator watches the MariaDB
CR.
When the operator finds a MariaDB
CR, it creates required number of StatefulSets
and related necessary stuff like secrets, services, etc.
Then, in order to upgrade the version of the MariaDB
database the user creates a MariaDBOpsRequest
CR with the desired version.
KubeDB
Enterprise operator watches the MariaDBOpsRequest
CR.
When it finds a MariaDBOpsRequest
CR, it halts the MariaDB
object which is referred from the MariaDBOpsRequest
. So, the KubeDB
Community operator doesn’t perform any operations on the MariaDB
object during the upgrading process.
By looking at the target version from MariaDBOpsRequest
CR, KubeDB
Enterprise operator updates the images of all the StatefulSets
. After each image update, the operator performs some checks such as if the oplog is synced and database size is almost same or not.
After successfully updating the StatefulSets
and their Pods
images, the KubeDB
Enterprise operator updates the image of the MariaDB
object to reflect the updated state of the database.
After successfully updating of MariaDB
object, the KubeDB
Enterprise operator resumes the MariaDB
object so that the KubeDB
Community operator can resume its usual operations.
In the next doc, we are going to show a step by step guide on upgrading of a MariaDB database using upgrade operation.