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 Ops Manager update the version of PerconaXtraDB
database.
KubeDB
concepts:The following diagram shows how KubeDB Ops Manager used to update the version of PerconaXtraDB
. Open the image in a new tab to see the enlarged version.
The updating process consists of the following steps:
At first, a user creates a PerconaXtraDB
Custom Resource (CR).
KubeDB
Community operator watches the PerconaXtraDB
CR.
When the operator finds a PerconaXtraDB
CR, it creates required number of StatefulSets
and related necessary stuff like secrets, services, etc.
Then, in order to update the version of the PerconaXtraDB
database the user creates a PerconaXtraDBOpsRequest
CR with the desired version.
KubeDB
Enterprise operator watches the PerconaXtraDBOpsRequest
CR.
When it finds a PerconaXtraDBOpsRequest
CR, it halts the PerconaXtraDB
object which is referred from the PerconaXtraDBOpsRequest
. So, the KubeDB
Community operator doesn’t perform any operations on the PerconaXtraDB
object during the updating process.
By looking at the target version from PerconaXtraDBOpsRequest
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 PerconaXtraDB
object to reflect the updated state of the database.
After successfully updating of PerconaXtraDB
object, the KubeDB
Enterprise operator resumes the PerconaXtraDB
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 updating of a PerconaXtraDB database using update operation.