Gitlab CE on Amazon EKS - Relative URL

:hugs: Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

Hello, We are currently trying to replace gitea to gitlab. Our microservices application has mulitplr opensource tools like backstage,argocd etc., They are all served using an Application LB on AWS and ingress nginx using path based routing. Example: DNS/gitea, DNS/argocd, DNS/backstage. All of them are running on Amazon EKS.

We are able to deploy Gitlab CE on EKS but we are not able to setup relative url so we can able to access gitlab at DNS/gitlab. We tried all documentation steps but the home page itself /users/signin is missing the /gitlab. We also tried to rewrite target on the ingress, but still not working. Does gitlab CE on Kubernetes support relative url so all of the urls will be able to be serviced behind /gitlab?.

Steps to reproduce

N/A

Configuration

Provide screenshots from the GitLab UI showing relevant configuration, if applicable.
On self-managed instances, add the relevant configuration settings or changes.

Versions

Please add an x whether options apply, and add the version information.

  • Self-managed
  • Versions
  • GitLab (Web: /help or self-managed system information sudo gitlab-rake gitlab:env:info):

Helpful resources

  1. Check the FAQ for helpful documentation, issues/bugs/feature proposals, and troubleshooting tips.
  2. Before opening a new topic, make sure to search for keywords in the forum search
  3. Check the GitLab project for existing issues. If you encounter a bug, please create a bug report issue.
  4. Review existing troubleshooting docs.

Thanks for taking the time to be thorough in your request, it really helps! :blush:

Maybe related Readiness and Liveness Probes Are Hardcoded – Can’t Use Relative URL (#6090) · Issues · GitLab.org / charts / GitLab Chart · GitLab If not, please open a new issue in the same project and attach all details on how GitLab is installed.

This is not for health check. We are able to see the webserver all the gitlab pods are running. we are not able to expose the webserver in a “/gitlab“ endpoint to access.