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.

MariaDB Compute Resource Autoscaling

This guide will give an overview on how KubeDB Autoscaler operator autoscales the database compute resources i.e. cpu and memory using mariadbautoscaler crd.

Before You Begin

How Compute Autoscaling Works

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

  Auto Scaling process of MariaDB
Fig: Auto Scaling process of MariaDB

The Auto Scaling process consists of the following steps:

  1. At first, the user creates a MariaDB Custom Resource Object (CRO).

  2. KubeDB Community operator watches the MariaDB CRO.

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

  4. Then, in order to set up autoscaling of the CPU & Memory resources of the MariaDB database the user creates a MariaDBAutoscaler CRO with desired configuration.

  5. KubeDB Autoscaler operator watches the MariaDBAutoscaler CRO.

  6. KubeDB Autoscaler operator utilizes the modified version of Kubernetes official VPA-Recommender for different components of the database, as specified in the mariadbautoscaler CRO. It generates recommendations based on resource usages, & store them in the status section of the autoscaler CRO.

  7. If the generated recommendation doesn’t match the current resources of the database, then KubeDB Autoscaler operator creates a MariaDBOpsRequest CRO to scale the database to match the recommendation provided by the VPA object.

  8. KubeDB Ops-Manager operator watches the MariaDBOpsRequest CRO.

  9. Lastly, the KubeDB Ops-Manager operator will scale the database component vertically as specified on the MariaDBOpsRequest CRO.

In the next docs, we are going to show a step by step guide on Autoscaling of MariaDB database using MariaDBAutoscaler CRD.

What's on this Page

Search
Improve This Page