Document Elasticsearch migrations must be finished before major upgrade
What does this MR do?
In an effort to manage the overhead of supporting our Elasticsearch integration in various states of migrations we are planning to delete all Elasticsearch migrations from the previous release in each major version release. This will ensure that we can delete legacy code paths in a reasonable amount of time.
With this we need to have clear documentation for operators about how to handle major version upgrades otherwise they may end up running into issues.
We also need clear docs for developers to explain how to correctly remove migrations in a major upgrade.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because it's just docs.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #291980 (closed)