[Enhancement] Add Readiness and Liveness Probes to All Deployments

[Manoj-14]

Add Readiness and Liveness Probes to All Deployments

Description

To improve the reliability and health monitoring of our microservices, we need to add Kubernetes readiness and liveness probes to all deployment manifests.

Tasks

• Add appropriate readiness probes for each service
• Add appropriate liveness probes for each service
• Test the probes locally and in staging to ensure proper functionality
• Document the changes in the deployment guides

Benefits

This will help Kubernetes detect and respond to unhealthy pods quickly, improving overall application stability and uptime.

[reshma2004]

Hi Manoj! This is new to work with. Let me take this task. I finished setting up the environment. I am able to access the application login in my local system. I am doing some research on readiness probes and liveness probes. Looking at docker-compose.yaml to do changes.

[Manoj-14]

@reshma2004 Sure.

[reshma2004]

Hi Manoj! I have added health checks for all the services and checked in to the feature branch. Can you please take a look at it. I see health check end points for all services already existed in README file. What additional details do you want me to add in it. Please let me know.

[reshma2004]

Hi Manoj. Yesterday I have added health checks for all services to deploy in docker. Today I have added liveness probe and readiness probe for all services except frontend. Since it depends on all other services, I left it without any changes. I have tested in my local all services individually, all are up and running and healthy with endpoint properly assigned. Can you please confirm if it looks good or needed any changes. Also I did not understand what details to include in README file. Can you please elaborate on it.
Also I wanted to bring this to your attention that while testing login-mysql service, I used same MySQL password (DB_PASSWORD="root"). When I used the LOGIN_SERVICE_DB_PASSWORD=loginroot which is mentioned in the Environment Variables, it failed. Is that a bug in SETUP.md or I have to use that loginroot password? I assumed the same mysql password(root) throughout the application and tested! Awaiting your response.

Thanks
Reshma

[Manoj-14]

@reshma2004 let the readme file as it is instad create a issue for that.