sameersbn / sameersbn/docker-gitlab
Registry keys are mandatory ?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi, as usual, thanks a lot for your hard work, it is more than appreciated!
I am currently running docker-gitlab in a google gke cluster, it works like a charm.
Next step is to enable CI and registry, what i need to understand how to handle registry keys on top of my setup, which basically is like this:
client -> google cloud load balancer -> k8s ingress + kube-lego-letsencrypt-certificates -> [service]
Which means that gitlab is working behind the https load balancer, it doesn't have any ssl key stored in, can i use the same configurations for the gitlab registry ?
Thanks!
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 file or test is named. Start by reviewing the repository's registry and TLS configuration documentation for a Dockerized GitLab deployment on Google GKE behind a Google Cloud load balancer and Kubernetes ingress. Done would be a clear, documented answer explaining whether the existing HTTPS setup can serve the registry and how registry keys should be handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, google-cloud, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100