fix: notification service failing in Kubernetes

[cidopenup0]

📌 Description

This PR fixes the notification service failure in the Kubernetes deployment by correcting configuration mismatches and missing secrets.

What does this PR do?

• Fixes a database name mismatch between MySQL and the notification service
• Adds the missing database username to Kubernetes secrets
• Corrects the notification service URL to use internal Kubernetes service discovery

Why is this change needed?

The notification service was unable to connect to its database and receive events due to incorrect database configuration, missing authentication credentials, and improper inter-service communication. These issues prevented notifications from being stored and delivered in the Kubernetes environment.

---

🔗 Related Issue

Fixes #52

---

🛠️ Type of Change

Please mark the relevant option:

• Documentation update
• Bug fix
• New feature
• Refactor
• Configuration / DevOps change
• Other (please explain)

---

🧪 How Was This Tested?

Verification steps:

• Confirmed all pods are running in the microforge-dev-ns namespace

• Checked notification service logs for database connection errors

• Verified internal service discovery using Kubernetes DNS

• Tested /api/notifications endpoint using an in-cluster curl pod

• Confirmed notifications are triggered on user login/registration events

• Docker Compose runs successfully

• Frontend loads correctly

• Service builds without errors

• Documentation renders correctly

• Manual testing

---

📸 Screenshots

---

---

---

---

---

✅ Checklist

Please confirm the following:

• My code follows the project structure
• I tested my changes locally
• I linked the relevant issue
• I kept this PR focused and minimal
• I am open to feedback and changes

---

📝 Additional Notes

Nothing

[github-actions]

🚫 Pull Request Policy Violation

Hi @cidopenup0, thanks for your contribution!

Direct PRs to the master branch are not allowed. Please close this PR and target the stage branch instead for review.