Master QingCloud MySQL Plus & KubeSphere: Step‑by‑Step Cluster Setup Guide

QingCloud MySQL Plus Platform

QingCloud MySQL Plus (https://www.qingcloud.com/products/mysql-plus/) is a MySQL‑based database service that supports a primary‑replica high‑availability architecture, integrates InnoDB and TokuDB storage engines, and provides automatic backup, monitoring, and alerting.

Reference documentation: https://docs.qingcloud.com/product/ https://docs.qingcloud.com/product/database_cache/app_mysql_plus/index.html https://docs.qingcloud.com/product/operation/notification_list

API documentation: https://docs.qingcloud.com/product/api/action/appcenter2/

MySQL Plus Cluster Creation Steps

Create a MySQL Plus HA cluster in Shanghai SH1A: Use MySQL‑5.7 engine, disable automatic backup, configure a 2‑node cluster with 2 CPU, 4 GB RAM, and 50 GB disk per node.

Configure automatic disk expansion: When disk usage exceeds 80% for five consecutive periods, automatically expand the cluster by 30 GB, up to a maximum of 200 GB, and send a notification email.

Shut down the cluster via API: Use the provided API to stop the created cluster. Refer to the API documentation for details.

QingCloud KubeSphere (QKE) Service

QKE (https://www.qingcloud.com/products/kubesphereqke/) is an enterprise‑grade container platform built on Kubernetes, delivering the full capabilities of KubeSphere on QingCloud public cloud, enabling unified management of multi‑cloud Kubernetes clusters, CI/CD, micro‑services, and lifecycle operations.

Reference documentation: https://docs.qingcloud.com/product/container/qke/

API reference: https://docs.qingcloud.com/product/api/action/appcenter

Register an account on the QingCloud console (https://console.qingcloud.com) and provide your User ID to the organizers to receive a cloud host voucher.

QKE Cluster Creation Steps

Create a QKE cluster in Shanghai SH1A: Choose the basic development‑test environment, KubeSphere version v3.0.0, and install all components.

Create a Harbor private registry: Deploy an enterprise Docker Registry with local storage, Harbor version 1.9.3, configured with 2 CPU and 4 GB RAM.

Develop a Kubernetes plugin: The plugin should pull newly deployed application images into the private Harbor registry and rewrite the image references to point to the private registry (hint: implement via a mutating webhook).