Our current beta chart is the `omnibus-gitlab` chart, and it has some significant short comings. We should strongly consider at what point would we want users to begin using the new `gitlab` chart, as opposed to `omnibus-gitlab`. They'd really be best served by using the new charts, as soon as possible, as it already has benefits and will rapidly be improved. For example it already supports RBAC. This would also increase usage of this chart, and help us find problems earlier. If that is a bar for beta, I think our gates should be: 1. Storage should be persistent. (i.e. object storage should work) 1. No planned PVC changes. 1. Functional parity with `gitlab-omnibus` On backups, we did recently fix these in `gitlab-omnibus`. What we can do as an MVC for cloud native beta however is focus on backing up `gitaly`, as we are anyway going to recommend external PG/Redis/Object Store for any production system. These would then be backed up by that external system.