Proposal: deploy GitLab operator directly, vs installer job
Problems we currently face
- Since we use an installer to install the operator, uninstalls leave trails behind
- How can we integrate it in our CI?
Proposed solution on how to proceed forward.
- Remove the installer completely and have helm install the operator directly using a chart
- Make the crd name prefixed by the release name in order for us to be able to have an operator for every release (example: CI) and since the user does not interact at all with the CRD directly it shouldn't be a problem
- Cleanups then won't be a problem since helm will be able to delete the whole thing upon uninstall
Amount of work I can estimate for that is nearly a week including testing and making sure it works correctly as expected.
Additionally we can remove hooks from our charts I don't think we need order any more we can just have helm install everything in a paused state (except for the operator) Check https://gitlab.com/charts/gitlab/merge_requests/503 for an example of how this works. This will make things much more deterministic for us and is an additional benefit from doing an operator
Edited by Jason Plum