Update pvc.yaml

[Aijazkhan123]

Summary by CodeRabbit

• Chores
  • Updated database storage configuration to use general-purpose SSD storage, enhancing system performance and reliability for data persistence.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the PersistentVolumeClaim manifest for the mongo-volume-claim resource by normalizing YAML formatting and changing the storage class specification from an empty string to gp2, while maintaining existing access modes and storage capacity settings.

Changes

Cohort / File(s)	Summary
Kubernetes PVC Configuration Kubernetes-Manifests-file/Database/pvc.yaml	Updated spec.storageClassName from empty string to gp2 and normalized YAML formatting of the spec block. Access modes remain ReadWriteOnce and requested storage remains 1Gi.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A storage class now clearly declared,
From empty strings we've been spared,
With gp2 so bright,
The volumes feel right,
Our Kubernetes clusters are prepared! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update pvc.yaml' is vague and generic, using non-descriptive language that doesn't convey the specific nature of the change (updating storage class from empty string to 'gp2').	Provide a more descriptive title that specifies the main change, such as 'Update pvc.yaml storage class to gp2' or 'Set storage class for MongoDB PVC to gp2'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@Kubernetes-Manifests-file/Database/pvc.yaml`:
- Line 9: The PVC's storageClassName was changed to "gp2" which prevents binding
to the existing PV "mongo-pv" (which has no storageClassName/defaults to ""), so
either revert the PVC's storageClassName to empty/remove the storageClassName
field in Kubernetes-Manifests-file/Database/pvc.yaml to match the PV, or if you
intend to use AWS EBS, update the PV "mongo-pv" in
Kubernetes-Manifests-file/Database/pv.yaml to use storageClassName: gp2 and
replace the hostPath PV with a dynamically provisioned PV (or remove the static
PV and rely on dynamic provisioning) so PVC and PV storageClassName values
match.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 86b327c4-6c72-42c0-8a23-2adf65812702

📥 Commits

Reviewing files that changed from the base of the PR and between 82f9f75 and 41719ff.

📒 Files selected for processing (1)

• Kubernetes-Manifests-file/Database/pvc.yaml

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Critical: storageClassName mismatch will prevent PVC binding.

Changing storageClassName from "" to gp2 breaks the binding with the existing PV mongo-pv in Kubernetes-Manifests-file/Database/pv.yaml, which has no storageClassName field (defaults to "").

Impact:

• If the cluster has a gp2 StorageClass (e.g., AWS EKS), a new EBS volume will be dynamically provisioned, orphaning the existing hostPath PV and potentially losing data.
• If the cluster lacks a gp2 StorageClass, the PVC will remain Pending indefinitely, and the MongoDB pod will fail to start.

Recommended fixes:

Option 1: Revert to match the existing PV

-  storageClassName: gp2
+  storageClassName: ""

Option 2: Update the PV to use gp2 (if AWS EKS is the target)

If the intent is to use AWS EBS volumes, update Kubernetes-Manifests-file/Database/pv.yaml to remove the hostPath PV or add storageClassName: gp2 and switch from hostPath to dynamic provisioning. However, note that manually creating a PV with gp2 is unusual—dynamic provisioning is the standard approach for EBS.

# In pv.yaml - but consider removing this PV entirely for dynamic provisioning
 spec:
   capacity: 
     storage: 1Gi
+  storageClassName: gp2
   volumeMode: Filesystem
   accessModes:
     - ReadWriteOnce
-  hostPath:
-    path: /data/db
+  awsElasticBlockStore:
+    volumeID: <your-ebs-volume-id>
+    fsType: ext4

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	storageClassName: gp2
	storageClassName: ""

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@Kubernetes-Manifests-file/Database/pvc.yaml` at line 9, The PVC's
storageClassName was changed to "gp2" which prevents binding to the existing PV
"mongo-pv" (which has no storageClassName/defaults to ""), so either revert the
PVC's storageClassName to empty/remove the storageClassName field in
Kubernetes-Manifests-file/Database/pvc.yaml to match the PV, or if you intend to
use AWS EBS, update the PV "mongo-pv" in
Kubernetes-Manifests-file/Database/pv.yaml to use storageClassName: gp2 and
replace the hostPath PV with a dynamically provisioned PV (or remove the static
PV and rely on dynamic provisioning) so PVC and PV storageClassName values
match.