Project reference ↗

A website or service needs durable records for information such as users, orders and account balances. MySQL provides a relational database, organizing records into tables and supporting SQL queries and transactional updates. This entry's historical Kubernetes chart deployed a single server, making its role different from a complete failover system. Keeping the database useful requires persistent storage, compatible clients and a way to restore both the data and application access after failure.

Current guidance

This historical entry describes a single-node MySQL deployment, not an automatically highly available database. The central stable chart is archived, but that packaging status does not retire MySQL. Choose the server release, image and deployment manager independently and record which component owns credentials, storage and upgrades.

The MySQL manual documents permitted upgrade paths and recommends the MySQL Shell Upgrade Checker. It explicitly shows that a 5.7-to-8.4 move requires an intermediate 8.0 step for the documented upgrade path. A container tag change should not be used to skip release boundaries or substitute for compatibility analysis.

Inventory authentication plugins, character sets, SQL modes, extensions and application drivers before changing the server. Rehearse recovery with real schema constraints and representative queries, preserving a backup that can be restored independently of the old chart. Confirm ownership and retention of the PVC before uninstalling anything. Plan how writes are stopped or transferred during cutover; an old volume is not a safe rollback target after data has diverged.

Historical upstream link check · 2026-10-09

Automated availability verification was inconclusive on 2026-10-09 (connection or verification failure). Link availability does not certify the historical installation instructions or current security support. This address is the first surviving external body reference; primary project identity still requires review.

Source for this check ↗

Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.

The original record

Historical Kubedex content

Original publication: 2018-10-08T11:00:47+00:00. Preserved for context. Commands, versions, prices and results below reflect the original research.

MySQL is one of the most popular database servers in the world. Notable users include Wikipedia, Facebook and Google.

Introduction

This chart bootstraps a single node MySQL deployment on a Kubernetes cluster using the Helm package manager.

Prerequisites

  • Kubernetes 1.6+ with Beta APIs enabled
  • PV provisioner support in the underlying infrastructure

The post MySQL appeared first on kubedex.com.

Sources & further reading

  1. MySQL documented upgrade paths
  2. Recovered historical source

Spotted something that needs another look?

Help improve this page →