sameersbn / sameersbn/docker-gitlab
load balancing and ssh clone
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi we have two instance of gitlab running in different machine. Git lab related folders are mounted using ceph so that both instance data are shared and DB points to a single DB. When we configure this two instance through load balancer. we have started instance in https mode with certificate and also in load balancer we use the certificate. we get 422 error while sign-in. any idea how to solve this error.
Another doubt is for both instance we give the same host name as in load balancer configuration say git-test
then https clone works perfectly whereas we will get issue in ssh clone since host points to load balancing machine. any suggesstion on how to handle this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or code entry points are identified. Start by investigating the two-instance load-balancer setup, shared Ceph storage, and single database, then reproduce the HTTPS sign-in 422 error and the SSH clone routing problem. Done means both sign-in and SSH cloning work correctly through the deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git
- Domain
- authentication, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100