Creation of PVC and PV to isolate MySQL data
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go, kubernetes, mysql
- Domain
- databases, devops, infrastructure
Research direction
Start by locating the MySQL StatefulSet and the controller code or resource definitions that create it. Determine how the persistent volume and claim should be attached, then verify that MySQL data remains available after the pod is deleted or fails.
Written by the indexing model from the issue text.
Description
Currently the mysql data in stored within the pod
the mysql statefulset should have a persistent volume attached to it where the mysql data must be saved in case of pod deletion or failure
- Dominant language
- Go
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DiptoChakrabarty/MySQLInstanceController
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in DiptoChakrabarty/MySQLInstanceController
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100