We use cookies and other similar technology to collect data to improve your experience on our site, as described in our Privacy Policy.

AppsCode
  • KubeDB

    Run Production-Grade Databases on Kubernetes

    arrow_forward
    Stash

    Backup and Recovery Solution for Kubernetes

    arrow_forward
    KubeVault

    Run Production-Grade Vault on Kubernetes

    arrow_forward
    Voyager

    Secure HAProxy Ingress Controller for Kubernetes

    arrow_forward
    ConfigSyncer

    Kubernetes Configuration Syncer

    arrow_forward
    Guard

    Kubernetes Authentication WebHook Server

    arrow_forward
    KubeDB

    KubeDB simplifies Provision, Upgrade, Scaling, Volume Expansion, Monitor, Backup, Restore for various Databases in Kubernetes on any Public & Private Cloud

    • task_altLower administrative burden
    • task_altNative Kubernetes Support
    • task_altPerformance
    • task_altAvailability and durability
    • task_altManageability
    • task_altCost-effectiveness
    • task_altSecurity
    Stash

    A complete Kubernetes native disaster recovery solution for backup and restore your volumes and databases in Kubernetes on any public and private clouds.

    • task_altDeclarative API
    • task_altBackup Kubernetes Volumes
    • task_altBackup Database
    • task_altMultiple Storage Support
    • task_altDeduplication
    • task_altData Encryption
    • task_altVolume Snapshot
    • task_altPolicy Based Backup
    KubeVault

    KubeVault is a Git-Ops ready, production-grade solution for deploying and configuring Hashicorp's Vault on Kubernetes.

    • task_altVault Kubernetes Deployment
    • task_altAuto Initialization & Unsealing
    • task_altVault Backup & Restore
    • task_altConsume KubeVault Secrets with CSI
    • task_altManage DB Users Privileges
    • task_altStorage Backend
    • task_altAuthentication Method
    • task_altDatabase Secret Engine
    Voyager

    Secure HAProxy Ingress Controller for Kubernetes

    • task_altHTTP & TCP
    • task_altSSL
    • task_altPlatform support
    • task_altHAProxy
    • task_altPrometheus
    • task_altLet's Encrypt
    configsyncer

    Kubernetes Configuration Syncer

    • task_altConfiguration Syncer
    Guard

    Kubernetes Authentication WebHook Server

    • task_altIdentity Providers
    • task_altCLI
    • task_altRBAC
  • RESOURCES
  • Webinar New
CONTACT SALES
KubeDB KubeDB
github-icon twitterx-icon
TRY NOW FREE
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.

PerconaXtraDB Volume Expansion

This guide will give an overview on how KubeDB Enterprise operator expand the volume of PerconaXtraDB.

Before You Begin

How Volume Expansion Process Works

The following diagram shows how KubeDB Enterprise operator expand the volumes of PerconaXtraDB database components. Open the image in a new tab to see the enlarged version.

  Volume Expansion process of PerconaXtraDB
Fig: Volume Expansion process of PerconaXtraDB

The Volume Expansion process consists of the following steps:

  1. At first, a user creates a PerconaXtraDB Custom Resource (CR).

  2. KubeDB Community operator watches the PerconaXtraDB CR.

  3. When the operator finds a PerconaXtraDB CR, it creates required StatefulSet and related necessary stuff like secrets, services, etc.

  4. 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.

  5. Then, in order to expand the volume of the PerconaXtraDB database the user creates a PerconaXtraDBOpsRequest CR with desired information.

  6. KubeDB Enterprise operator watches the PerconaXtraDBOpsRequest CR.

  7. 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.

  8. Then the KubeDB Enterprise operator will expand the persistent volume to reach the expected size defined in the PerconaXtraDBOpsRequest CR.

  9. 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.

  10. 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.

What's on this Page

Search
Improve This Page