Open
Milestone
Jun 3, 2024–Jun 14, 2024
Sprint 3
GitLab Operator V2: Sprint 3
Overview
Context
- We continue with the remaining Deliverable items from %Sprint 2. This includes:
- Installing Puma and Workhorse (#2 (closed))
- Installing Sidekiq (#3 (closed))
- Running database migrations (#5 (closed))
- Generating Rails and Workhorse Secrets (#21)
- We use the development kit to provision the following dependencies:
- PostgreSQL
- Redis
- Gitaly
- MinIO
- NGINX Ingress Controller
- CertManager
- We have made the decision on how to integrate Ingress controller (#31 and #33) and CertManager (#32).
Objectives
- Operator can install Puma, Workhorse, and Sidekiq.
- Operator can run database migrations.
- Operator can install GitLab Registry.
- Operator can install GitLab Shell Stretch
- The code base is reorganized and the test framework is defined.
Success Criteria
The following scenario should work:
- The development kit provisions the required external dependencies.
- A GitLab custom resource is created. It includes:
- General specification of GitLab instance, including version and edition.
- Shared application configuration between core components.
- References to external dependencies.
- Operator installs a new GitLab instance with the specified version.
- The GitLab instance is accessible and usable with the scope of the core components.
- Docker images can be pulled and pushed to the GitLab instance.
- Git repositories can be pulled and pushed over SSH. Stretch