We use cookies and other similar technology to collect data to improve your experience on our site, as described in our Privacy Policy.
Run Production-Grade Databases on Kubernetes
Backup and Recovery Solution for Kubernetes
Run Production-Grade Vault on Kubernetes
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
KubeDB simplifies Provision, Upgrade, Scaling, Volume Expansion, Monitor, Backup, Restore for various Databases in Kubernetes on any Public & Private Cloud
A complete Kubernetes native disaster recovery solution for backup and restore your volumes and databases in Kubernetes on any public and private clouds.
KubeVault is a Git-Ops ready, production-grade solution for deploying and configuring Hashicorp's Vault on Kubernetes.
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
New to KubeDB? Please start here.
This guide will give an overview on how KubeDB Ops Manager expand the volume of PerconaXtraDB
.
KubeDB
concepts:
The following diagram shows how KubeDB Ops Manager expand the volumes of PerconaXtraDB
database components. Open the image in a new tab to see the enlarged version.
The Volume Expansion 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 StatefulSet
and related necessary stuff like secrets, services, etc.
The statefulSet creates Persistent Volumes according to the Volume Claim Template provided in the statefulset configuration. This Persistent Volume will be expanded by the KubeDB
Enterprise operator.
Then, in order to expand the volume of the PerconaXtraDB
database the user creates a PerconaXtraDBOpsRequest
CR with desired information.
KubeDB
Enterprise operator watches the PerconaXtraDBOpsRequest
CR.
When it finds a PerconaXtraDBOpsRequest
CR, it pauses 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 volume expansion process.
Then the KubeDB
Enterprise operator will expand the persistent volume to reach the expected size defined in the PerconaXtraDBOpsRequest
CR.
After the successfully expansion of the volume of the related StatefulSet Pods, the KubeDB
Enterprise operator updates the new volume size in the PerconaXtraDB
object to reflect the updated state.
After the successful Volume Expansion of the PerconaXtraDB
, the KubeDB
Enterprise operator resumes the PerconaXtraDB
object so that the KubeDB
Community operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on Volume Expansion of various PerconaXtraDB database using PerconaXtraDBOpsRequest
CRD.