fix: add 4 missing microservices and all infrastructure to K8s manifests

[DivyashreeR008]

Summary

The K8s manifests were missing 4 microservices and all 6 infrastructure components defined in \docker-compose.yml, making it impossible to deploy the full system on Kubernetes (Fix : #56).

Changes

Missing services added to \k8s/deployments.yaml\ and \k8s/services.yaml\

Service	Port
\integration-service\	8016
\employee-lifecycle-service\	8020
\security-service\	8050
\�i-service\	8065

New \k8s/infrastructure.yaml\

Component	Type	Image	Port
postgres	StatefulSet + PVC	postgres:15-alpine	5432
mongodb	StatefulSet + PVC	mongo:6	27017
redis	Deployment	redis:7-alpine	6379
rabbitmq	Deployment	rabbitmq:3-management-alpine	5672, 15672
zookeeper	Deployment	confluentinc/cp-zookeeper:7.5.0	2181
kafka	Deployment	confluentinc/cp-kafka:7.5.0	9092

New \k8s/infrastructure-services.yaml\

Services for all 6 infrastructure components, matching the internal DNS names used by microservices (e.g., \postgres:5432, \kafka:9092,
edis:6379).

Design decisions

• StatefulSets for postgres and mongodb (need stable network identities and persistent storage via \�olumeClaimTemplates)
• Deployments for redis, rabbitmq, zookeeper, kafka (stateless enough for simple dev deployment)
• Pattern consistency: All microservice deployments follow the existing convention (security context, resource requests/limits, liveness/readiness probes on /health, \envFrom\ with \�tlas-secrets)
• Infrastructure probes use \ cpSocket\ checks where health endpoints are not available
• Secrets referenced via \secretKeyRef\ with \optional: true\ for backward compatibility

Verification

• All ports, images, and environment variable names match \docker-compose.yml\
• Service DNS names match what dependent services expect (e.g., \�pi-gateway\ references \integration-service:8016, \employee-lifecycle-service:8020, \security-service:8050, \�i-service:8065\ in its env vars)

[Senthil455]

gh: Not Found (HTTP 404)
{"message":"Not Found","documentation_url":"https://docs.github.com/rest/issues/comments#get-an-issue-comment","status":"404"}