Bobcares

MySQL StatefulSet Helm Chart | How to Deploy

by | Feb 5, 2024

Learn how to deploy MySQL Statefulset with Helm Chart. Our MySQL Support team is here to help you with your questions and concerns.

MySQL StatefulSet Helm Chart | How to Deploy

Deploying MySQL on Kubernetes requires special attention to data persistence and scalability. This is where MySQL Statefulset comes in handy. It ensures data consistency across pods and facilitates scaling operations seamlessly.

MySQL StatefulSet Helm Chart | How to Deploy

Today, we are going to take a look at the deployment process using Helm.

MySQL operates as a stateful application, storing important data within volumes. Without a Statefulset, data stored in pod ephemeral storage will vanish when the pod restarts.

Additionally, as demand surges, we have to scale MySQL to multiple pods. The Statefulset ensures data consistency across pods, such as mysql-0 and mysql-1, providing a stable foundation.

How to Installing the Chart

Let’s dive into the installation process using Helm to deploy MySQL on our Kubernetes cluster.

$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm install my-release bitnami/mysql

These commands start the deployment, setting up MySQL with default configurations. Next, we explore how to tailor these configurations to our specific needs.

Customizing the Installation

To customize the installation, we can use the `–set` option with `helm install` or provide a YAML file specifying parameter values.

For instance:

$ helm install my-release \
--set auth.rootPassword=secretpassword,auth.database=app_database \
bitnami/mysql

This command sets the MySQL root password and creates a database named app_database.

Creating the Service

Now, create the service using the provided service.yml configuration file:

MySQL Statefulset Helm Chart- Creating the service

Apply the service:

$ kubectl apply -f service.yml

Creating the StatefulSet

Now, it is time to create the StatefulSet using the statefulset.yml configuration file:

Creating the StatefulSet

Apply the StatefulSet:

$ kubectl apply -f statefulset.yml

Verifying and Scaling

Check the deployment status with:

$ kubectl get sts
$ kubectl get pods -l app=mysql

Access the MySQL pod:

$ kubectl exec -it mysql-0 -- mysql -u root -p

Now, we are connected to the MySQL database. We can create tables and data as needed.

To scale the replica set:

$ kubectl scale sts mysql --replicas 3

Cleaning up

To tidy up resources, follow these steps:

$ kubectl delete pod mysql-client-loop --now
$ kubectl delete statefulset mysql
$ kubectl get pods -l app=mysql
$ kubectl delete configmap,service,pvc -l app=mysql

This setup ensures the MySQL deployment is resilient and can handle evolving workloads.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to deploy MySQL Statefulset with Helm Chart.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF