Can you explain how you would configure resource requests, limits, and readiness probes for a Kubernetes deployment of a single clinical service?

In Kubernetes, resource requests and limits define the minimum and maximum CPU/memory a container can use. Setting a request ensures the scheduler can find a node with enough resources; setting a limit prevents the container from consuming more than allowed. For a clinical service, you might set a request of 500m CPU and 1Gi memory, and a limit of 1 CPU and 2Gi memory, depending on expected load. Readiness probes determine when a pod is ready to receive traffic. For a Spring Boot app, you can use an HTTP GET probe to /actuator/health or /health, with initialDelaySeconds=30, periodSeconds=10, timeoutSeconds=5, failureThreshold=3. This ensures traffic is only routed to pods that have fully started and passed health checks. Additionally, you might configure liveness probes to restart pods that become unresponsive. Using these settings helps maintain high availability and resource efficiency for the clinical service. In addition, you can annotate the pod with labels such as app=clinical-service to enable selective monitoring and scaling.