Don't run the regular migrations job when deploy is a geo secondary
The following discussion from !877 (merged) should be addressed:
-
@twk3 started a discussion: (+1 comment) Should the secondary even be running the migrations job? For me the job constantly fails. (Likely my primary and secondary clusters got different versions of the rails image due to bad timing on my part.) But this highlighted that the job isn't really helpful in the secondary.
-
!1052 (merged) documentation & example secondary configuration disable the migrations via
gitlab.migrations.enabled: false
We should:
-
Add Geo migrations script to the rails image gitlab-org/build/CNG!330 (merged) -
Have Geo migrations be triggered for migrations when in secondary mode via the migrations chart. !1055 (merged) -
[X] Have the geo-logcursor container watch that DB version in thealready doesdependencies
Edited by Jason Plum