fix: notification 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]

Hi @cidopenup0 Thanks for creating a PR for your Issue! ☺️

We'll review it as soon as possible.
In the meantime, please double-check the file changes and ensure that all commits are accurate.

If there are any unresolved review comments, feel free to resolve them. 🙌🏼

[Manoj-14]

I need url to be http://api.microforge.manojm.site

[cidopenup0]

alright iam working it

[cidopenup0]

@Manoj-14 i have tried to add ip of ingress-nginx-controller cluster IP but this is considered as bad practice so i consider the old http://notification-service:8083 way as better option and using service names is standard practice for service to service communication

    spec:
+      hostAliases:
+      - ip: "10.102.83.6"  # ingress-nginx-controller ClusterIP
+        hostnames:
+        - "api.microforge.manojm.site"

[Manoj-14]

I worked on it but it not worked for some cases when it is mapped to dns resolver so please update the url

[cidopenup0]

ip is dynamic, so have to update it manually when the k8s namespace gets created

that is why i have been suggesting http://notification-service:8083 thingy

[Manoj-14]

https://github.com/Manoj-14/MicroForge/pull/54/changes#r2732869057

[cidopenup0]

https://github.com/Manoj-14/MicroForge/pull/54/changes#r2732869057

check the comment please

[cidopenup0]

@Manoj-14 any updates???