[Bug] Notification Service failing in Kubernetes (Working in Docker Compose)

[Manoj-14]

[Bug]Notification Service failing in Kubernetes (Working in Docker Compose)

Description

The Notification Service is failing to retrieve or display data after migrating the application from Docker Compose to Kubernetes. While the service works correctly in the local Docker environment (populating the list with auth-service events), the Kubernetes deployment consistently shows the "No notifications yet" empty state.

📸 Evidence

Expected Behavior (Local Docker):

*

Current Behavior (Kubernetes):

*

📋 Steps to Reproduce

1. Deploy the application manifest to the Kubernetes cluster.
2. Log in as a user to generate an auth-service event.
3. Navigate to the Notifications tab in the UI.
4. Observe the empty state message.

✅ Troubleshooting Tasks

• Check logs for notification-service pod: kubectl logs -l app=notification-service
• Verify Service discovery: kubectl get endpoints notification-service
• Inspect Frontend Network tab (F12) for 404/500 errors on /api/notifications
• Compare env variables in Docker Compose vs. Kubernetes ConfigMap.

[cidopenup0]

can i work on this issue?

[Manoj-14]

@cidopenup0 can work on this issue.