<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=464457) </details> <!--IssueSummary end--> * The main focus of the test scenario: Agent can register itself and the connection between the agent and KAS is established. (Agent =\> KAS) * This scenario will ensure that the agent correctly talks to KAS through the Cells router. * It will also ensure that KAS correctly talks to Gitlab monolith, because KAS talks Gitlab monolith to authenticate the request from the agent. * We will need two GDK instances to test Cells locally. We'll need to find a document about this. * Cells router will route the coming request to a correct cell using token sent from the agent. * KAS configured with GRPC for agent connections * KAS configured with websockets (wrapping GRPC) for agent connections * Different proxy authentications (although the routing of those may not be KAS specific): * Cookie (Dashboard) * ci access * pat access