Discovery for proper handling of edxapp migrations and migrations rollback

[robrap]

See Slack conversation to kick-off discovery.

Requirements:

• Maintaining ability to run migrations on a single container (to imitate running on a single instance).
• Maintaining the ability to rollback migrations (on a single container), when required.
  Questions:
• Is it true that our other k8s pipelines are not running migrations on a single container?
  • Is that something we plan to fix? At a minimum, I do not want to copy this pattern for edxapp.
  • See this past Slack discussion on this topic.
• Do the current k8s pipelines have an ability to rollback migrations How is that done?

Based on these answers, where would be the best place to brainstorm solutions? Do we need to set up a meeting for this. or does someone want to make proposals first?

We need to ensure we know what the plan is, and whether this will be handled by SRE or Arch-BOM. It sounds like SRE might be looking this.

When and if SRE tickets are shared, add links to this ticket.

[robrap]

• SRE ticket for handling migrations outside of the main app: https://2u-internal.atlassian.net/browse/GSRE-2597
• SRE ticket for handling migrations rollback: TBD.