Describe the issue:
We are experiencing an issue where the readiness, liveness, and startup probe paths configured in the Zeebe Gateway are not reflecting the required contextPath. This omission leads to Kubernetes probes failing, which incorrectly marks the Zeebe Gateway pods as unhealthy in console SM.

Actual behavior:
The contextPath is not being prepended to the actuator paths in the configuration, resulting in probe paths like /actuator/health/readiness without the necessary prefix. This configuration causes the probes to fail as the paths do not correctly resolve to the health endpoints.

Expected behavior:
The Zeebe Gateway's probes for readiness, liveness, and startup should include the contextPath as a prefix to the actuator paths to correctly point to the health check endpoints. For example, if contextPath is set to /zeebe, the readiness probe path should be /zeebe/actuator/health/readiness.

How to reproduce:

1. Set up the Camunda Platform Helm chart with the following values:
   zeebeGateway.contextPath to "/zeebe"
2. Deploy Helm charts
3. Observe that the readiness, liveness, and startup probes for the Zeebe Gateway pods fail due to incorrect paths in console SM.
4. Check console configmap and see that /zeebe is missing

Logs:

Environment:

Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

• Platform:
• Helm CLI version:
• Chart version:
• Values file: