## Problem Statement The cloud native install is currently at the **Viable** maturity level. > **Viable:** Used by users/customers to solve real problems Large organizations are rapidly adopting cloud native strategies to improve speed of delivery, scalability, and efficient use of computing resources. GitLab is seeing more interest from customers wanting to install GitLab on Kubernetes. We would like to move the cloud native install all the way to **Lovable**, but first let's define what a **Complete** maturity state looks like. > **Complete:** Contains a competitive feature set sufficient to displace other single-purpose DevOps tools. ## Acceptance Criteria * [x] Geo is supported * [x] GitLab Pages are supported * [x] Gitaly HA can be deployed * [x] Reference architectures exist for the loads that are defined for Omnibus GitLab (not attached! https://gitlab.com/groups/gitlab-org/quality/-/epics/13) * [x] Reference architectures have been tested at scale * [x] Documentation is clear and complete (https://gitlab.com/groups/gitlab-org/charts/-/epics/27) * [x] The GitLab Customer Success org is confident to recommend and support cloud native deployments at scale up to 50,000 users. At least a set of CS team members are confident to make architectural recommendations for cloud native installs * [x] GitLab Support feels well-equipped to respond to customer support requests regarding Helm deployments (https://gitlab.com/gitlab-org/charts/gitlab/issues/1658#note_279786268) * [x] At least 10 customers with a scale of 1,000+ users have deployed GitLab on Kubernetes using the GitLab Helm chart * [x] A [customer whitepaper has been published](https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/1983), which highlights the benefits of shifting to cloud native * [x] [Guidelines exist for other development teams to develop cloud native-friendly features and submit MRs for adding feature support to the Helm chart](https://gitlab.com/gitlab-org/distribution/team-tasks/-/issues/648) * [x] [Common Access Cards are supported in the Helm chart](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/988) * [x] Configuration options that are available in Omnibus are also available in the Helm chart if it makes sense for cloud native installs ### Out of scope (because they are targeted at **Lovable** maturity) * GitLab is deployed and managed using operators (https://gitlab.com/groups/gitlab-org/-/epics/5486) ## Next steps * [x] Customer interviews to validate criteria for **Complete** (Done by [the CM Scorecard](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1662) :tada:) * [x] Update the handbook https://about.gitlab.com/direction/distribution/cloud_native_installation/ with the new maturity of "Complete"