Add Cloud Native Hybrid instructions on 2k users RA page
What does this MR do?
Changes:
- Adds 2k hybrid environment guidance based on the performance testing in https://gitlab.com/gitlab-org/quality/reference-architectures/-/issues/20#note_635661330 and gitlab-org/charts/gitlab!2125 (merged).
- Adds 2k hybrid architecture diagram
Related issues
Author's checklist
- Follow the:
- Ensure that the product tier badge is added to topic's
h1. - Request a review based on the:
- The documentation page's metadata.
- The associated Technical Writer.
If you are only adding documentation, do not add any of the following labels:
~"feature"~"frontend"~"backend"~"bug"~"database"
These labels cause the MR to be added to code verification QA issues.
Review checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
- If the content requires it, ensure the information is reviewed by a subject matter expert.
- Technical writer review items:
- Ensure docs metadata is present and up-to-date.
- Ensure the appropriate labels are added to this MR.
- If relevant to this MR, ensure content topic type principles are in use, including:
- The headings should be something you'd do a Google search for. Instead of
Default behavior, say something likeDefault behavior when you close an issue. - The headings (other than the page title) should be active. Instead of
Configuring GDK, say something likeConfigure GDK. - Any task steps should be written as a numbered list.
- If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
- The headings should be something you'd do a Google search for. Instead of
- Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
- Ensure a release milestone is set.
Edited by Nailia Iskhakova