Problem

The current Helm chart only supports configuring initialDelaySeconds for readiness and liveness probes. Production deployments often need to fine-tune other probe parameters for optimal health checking based on application characteristics and infrastructure requirements.

Use Case

Production deployments need flexibility to configure probe timing based on:

• Application startup characteristics: Slow-starting applications need longer timeouts
• Network latency considerations: High-latency environments need adjusted periods
• Load balancer requirements: Different failure thresholds for upstream health checks
• Monitoring system integration: Custom probe intervals for observability tools

Proposed Solution

Extend probe configuration to support all Kubernetes probe fields:

• periodSeconds - How often to perform the probe
• timeoutSeconds - Probe timeout duration
• successThreshold - Consecutive successes needed
• failureThreshold - Consecutive failures before marking unhealthy

This maintains backward compatibility by only including fields when explicitly configured.