Add Readiness and Liveness Probes to All Deployments

[reshma2004]

---

📄 Pull Request Template

📌 Description

Please provide a clear and concise description of the changes in this PR.

What does this PR do?

1. Adds Health Monitoring: This PR adds Kubernetes readiness and liveness probes and rolling updates to all services, metadata-service.yaml, login-mysql.yaml, login-service.yaml, auth-service.yaml, notification-service.yaml, and notification-mysql.yaml.
2. Excludes Frontend: No changes were made to the frontend service as it relies on the other services being fully operational first.

Why is this change needed?

1. Enhances Reliability: These probes are necessary to improve the reliability and health monitoring of the microservices.  
2. Automated Recovery: This change helps Kubernetes automatically detect and respond to unhealthy pods, ensuring they are restarted if they fail (liveness) or not sent traffic until they are ready (readiness), which improves overall application stability and uptime.  
3. By implementing rolling updates the system can now update services by gradually replacing old pods with new ones, ensuring there is no service interruption during deployment.
4. Fulfills Project Requirement: This work directly addresses the tasks outlined in the Add Readiness and Liveness Probes to All Deployments enhancement issue.

---

🔗 Related Issue

Link the issue this PR addresses (if applicable):

Fixes #25

---

🛠️ 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?

Describe how you verified your changes:

• Docker Compose runs successfully
• Frontend loads correctly
• Service builds without errors
• Documentation renders correctly
• Manual testing

---

📸 Screenshots (if applicable)

Add screenshots or logs if this change affects UI or behavior.

---

✅ 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

Anything else the maintainers should know?
login-service.yaml had missing labels and different container image(v1.2.0). Rest other service files had container image v1.1.0 So I modified the container image and added missing labels. in login-service.yaml. However container images does not match with readme.md and setup.md. I also added rolling update.

[github-actions]

Hi @reshma2004 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]

Hey @reshma2004. Please review the changes for login-service.yaml file. Other then that every thig loogs good for me.

[reshma2004]

I changed the version back to v1.2.0

[reshma2004]

I had some difficulty pushing files. Yes, I changed the version back to v1.2.0.

[Manoj-14]

Thanks @reshma2004 for resolving the issue, will merge it to stage then will merge to master.

[reshma2004]

Hi Manoj, Thanks for merging the PR. ! I'm glad I could contribute.Looking forward to contributing. Thanks Reshma

…

On Sun, Jan 11, 2026 at 7:05 AM Manoj M ***@***.***> wrote: Closed #49 <#49>. — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGWF7RSKJEOMYKHB7TXKFD4GI37BAVCNFSM6AAAAACRJK7JQWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRRHE3DSOJSHEZDMNI> . You are receiving this because you were mentioned.Message ID: ***@***.***>