Add GitLab Operator V1 support

Summary

GitLab Operator is being worked on as ready for production at gitlab-org/cloud-native&68 (closed). The issue is to add GitLab Operator support to GET if customer wants to build Cloud Native Hybrid with Operator.

Implementation

  • Add variable that will allow to switch to using GitLab Operator
  • Default CNH setup will use Helm
  • Only for new installations, support for switching from Helm is outside of the scope of this issue
  • Geo installations are out of the scope at the moment due to limited production use
Old issue description

Update - 2024-08-30

After some excellent work by @niskhakova to throughly test out the Operator we've identified some gaps compared to the Chart that we've decided to wait for to ensure the best long term compatibility with GET. As such, we're going to pause this effort at this time.

With that being the case and Operator V2 underway for next year we're now going to revisit this when V2 has sufficient production readiness and the gaps addressed.

Any questions please let @ksvoboda or myself know.

We are about to release the initial beta of our Operator. While it is very similar to Helm as far as settings, it is a different deployment model.

We may want to thinking about switching to this once it is GA, as this will reduce the number of deployment who may need to consider switching. Although that said - GET could potentially coordinate the switch relatively effectively with the hybrid model.

Edited by Nailia Iskhakova
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information