sameersbn / sameersbn/docker-gitlab
Upgrade instructions using Kubernetes
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Would be nice to have instructions on how-to handle upgrades using Kubernetes.
Right now the documentation suggests to stop the container, then run a disposable container running the backup and then run again the gitlab container.
Thanks a lot for your invaluable work, we are using this docker image on a google gke production cluster.
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
Start by locating the existing upgrade documentation described in the issue and review its stop-container, disposable-backup-container, and restart workflow. Compare that process with a Kubernetes deployment on Google GKE, then document a complete upgrade procedure whose result is a clear, usable Kubernetes-based upgrade path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gcp, kubernetes
- Domain
- cloud, devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100