Document steps required to test workspaces changes on new architecture
MR: Add dev docs on testing workspaces integration ... (!201761 - closed) (Closed) see: !201761 (comment 2697379115)
Description
As we are working on removing the workspace proxy as a component as part of this epic: Simplify Workspaces setup by removing GitLab Wo... (gitlab-org#16785), and transitioning to an architecture where we rely on KAS (server component) to handle the proxy's concerns, we would need to be able to test our changes are safe in an omnibus deployment and CNG deployment.
As this is a WIP, and we do not have E2E tests currently that could automate this verification, we are including manual steps on how to verify that the changes are safe, which mainly entails installing GitLab both ways (CNG/Omnibus), but is directed towards an audience that has access to gitlab-sandbox (particularly AWS, can adapt for other providers if needed, but the main point of this doc is for a less abstract way to verify changes)
Acceptance criteria
-
Doc on testing workspace changes on CNG -
Doc on testing workspace changes on Omnibus