Production readiness checklist

Summary

Looking to brainstorm some ideas that identify the path at which we would call this production ready.

Some initial thoughts:

1. Completion of any items from Move the GitLab Operator from `Minimal` to `Via... (&23 - closed) that we consider production blocking
2. Test coverage
   • Improve test coverage for GitLab Cloud Native (gitlab-org/quality/quality-engineering&7 - closed)
   • Installs and upgrades are tested
     • Also upgrade from CE to EE
   • Advanced configurations intended for production have been tested
     • Geo
     • Pages, Registry, other scenarios
     • Adding low level test for ensuring that user configuration is translated into the right set of values for Charts - #1033 (comment 1266275692)
   • Downgrades are tested
3. Performance testing via GPT:
   • OpenShift gitlab-org/quality/quality-engineering/team-tasks#749 (closed)
   • Vanilla Kubernetes cluster (GKE)
4. Data integrity
   • Backup and restore are tested and documented
   • Admin can safely move between this and other supported GitLab install methods
     • Migrate from Charts to Operator
5. Production ready documentation
   • Architecture diagrams exist
   • Limitations vs other install methods are clearly laid out and up to date
6. Security review
7. Support readiness
   • GitLab support has been onboarding