Readiness and Liveness Probes Are Hardcoded – Can’t Use Relative URL

Summary

The readinessProbe and livenessProbe are currently hardcoded to use the /-/health endpoint.
This setup does not respect the configured relativeURLRoot, making it difficult to run GitLab behind a subpath (e.g., /gitlab).

Steps to reproduce

Set a relative URL by patching the ConfigMap:

kubectl patch configmap gitlab-webservice -n gitlab --type merge -p '{"data":{"gitlab.yml":"production:\n  gitlab:\n    relative_url_root: /gitlab\n"}}'

Current behavior

readiness Probe is failing because it is looking on /-/readiness and not realativeURL/-/readiness

Expected behavior

readiness Probe to reach for realativeURL/-/readiness

Possible Solution

Templatize the probes to account for relativeURLRoot, or allow the endpoint paths to be overridden via values.yaml.

Versions

• Chart: 9.1.1
• Platform:
  • Cloud: AKS
• Kubernetes: (kubectl version)
  • Client: v1.31.1
  • Server: v1.32.5-eks-5d4a308
• Helm: (helm version)
  • Client: v3.18.3
  • Server: