📝 Description

This change adds backend validation for sidecar probe configurations during Nuclio function deployment.

Before deploying the function, the API now validates that each configured sidecar probe (readinessProbe, livenessProbe, startupProbe) defines exactly one Kubernetes health-check mechanism (httpGet, exec, tcpSocket, or grpc). Configurations that are missing a health check or define multiple checks are rejected with a clear 400 Bad Request error.

This validation is intentionally minimal and aligned with the Kubernetes V1Probe schema, ensuring obvious misconfigurations are caught early while avoiding deep field-level validation.

🛠️ Changes Made

• Added backend validation for sidecar probes before deployment.

✅ Checklist

• I updated the documentation (if applicable)
• I have tested the changes in this PR
• I confirmed whether my changes are covered by system tests
  • If yes, I ran all relevant system tests and ensured they passed before submitting this PR
  • I updated existing system tests and/or added new ones if needed to cover my changes
• If I introduced a deprecation:
  • I followed the Deprecation Guidelines
  • I updated the relevant Jira ticket for documentation

🧪 Testing

• Dev test: tested both negative and positive flows
• Added unit tests

🔗 References

• Ticket link: https://iguazio.atlassian.net/browse/ML-11788
• Design docs links:
• External links: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes

🚨 Breaking Changes?

• Yes (explain below)
• No

🔍️ Additional Notes

• This PR follows up on [Application Runtime] Support setting probes for the application runtime sidecars #9043