Moving shared-secrets creation to the gitlab-operator
Proposed next step for the GitLab Operator
@Ahmadposten , @marin and @twk3 had a meeting on this earlier today, and believe we should be look to moving the shared-secrets job into the operator as the next feature. (once the current operator MVP is stable enough to ship)
-
Shared secrets currently happens in a pre-hook, and moving it to the operator can help us reduce our helm pre-hooks to just the operator
-
We 'hack' the shared-secret job currently for the operator so when the operator is enabled, helm creates the shares secrets job, but with no parallelism (meaning it won't run). Meaning the operator is already completely controlling when this job is run. Making it a good candidate to be completely owned by the operator.