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

New to KubeDB? Please start here.

MySQL Vertical Autoscaling

This guide will give an overview on how KubeDB Autoscaler operator autoscales the database storage using mysqlautoscaler crd.

Before You Begin

How Storage Autoscaling Works

The following diagram shows how KubeDB Autoscaler operator autoscales the resources of MySQL database components. Open the image in a new tab to see the enlarged version.

  Storage Autoscaling process of MySQL
Fig: Storage Autoscaling process of MySQL

The Auto Scaling process consists of the following steps:

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

  2. KubeDB Community operator watches the MySQL CR.

  3. When the operator finds a MySQL CR, it creates required number of StatefulSets and related necessary stuff like secrets, services, etc.

  4. Each StatefulSet creates a Persistent Volume 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 set up storage autoscaling of the MySQL database the user creates a MySQLAutoscaler CRO with desired configuration.

  6. KubeDB Autoscaler operator watches the MySQLAutoscaler CRO.

  7. KubeDB Autoscaler operator continuously watches persistent volumes of the databases to check if it exceeds the specified usage threshold.

  8. If the usage exceeds the specified usage threshold, then KubeDB Autoscaler operator creates a MySQLOpsRequest to expand the storage of the database.

  9. KubeDB Enterprise operator watches the MySQLOpsRequest CRO.

  10. Then the KubeDB Enterprise operator will expand the storage of the database component as specified on the MySQLOpsRequest CRO.

In the next docs, we are going to show a step by step guide on Autoscaling storage of various MySQL database components using MySQLAutoscaler CRD.

What's on this Page

Search
Improve This Page