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 of how KubeDB enterprise operator upgrades the version of MySQL
database.
KubeDB
concepts:The following diagram shows how KubeDB enterprise operator used to upgrade the version of MySQL
. 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 MySQL
cr.
KubeDB
community operator watches for the MySQL
cr.
When it finds one, it creates a StatefulSet
and related necessary stuff like secret, service, etc.
Then, in order to upgrade the version of the MySQL
database the user creates a MySQLOpsRequest
cr with the desired version.
KubeDB
enterprise operator watches for MySQLOpsRequest
.
When it finds one, it halts the MySQL
object so that the KubeDB
community operator doesn’t perform any operation on the MySQL
during the upgrading process.
By looking at the target version from MySQLOpsRequest
cr, KubeDB
enterprise operator takes one of the following steps:
StatefulSet
for upgrading between patch/minor versions.StatefulSet
using targeted image for upgrading between major versions.After successful upgradation of the StatefulSet
and its Pod
images, the KubeDB
enterprise operator updates the image of the MySQL
object to reflect the updated cluster state.
After successful upgradation of MySQL
object, the KubeDB
enterprise operator resumes the MySQL
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 MySQL database using upgrade operation.