## Goal The goal of this Iteration is to construct a remote development `server module` which has a connection to the GA4K agent via the bidirectional gRPC connection and a remote development `agent module` that allows us: - full integration with the GitLab Agent as core code **previously: Authenticate/Authorize traffic and use GA4K for communicating with Kubernetes API** ## High Level Approach See https://gitlab.com/gitlab-org/remote-development/gitlab-remote-development-docs/-/blob/main/doc/architecture.md for the latest architecture diagrams and documentation ## Requirements - Our assumptions around https://gitlab.com/gitlab-org/remote-development/gitlab-remote-development-docs/-/blob/main/doc/architecture.md are validated and working. These are **not** part of the MVC: - Integration of Remote Development to the GitLab UI and Web IDE - Authentication/Authorization with GitLab and a user - Using GA4K instead of ingress controller ## Assumptions - https://gitlab.com/gitlab-org/gitlab/-/issues/377921+ - https://gitlab.com/gitlab-org/gitlab/-/issues/383020+ ## Questions - What customer value does using the GA4K offer by default? ## User Prerequisites - ## Success criteria - Use GA4K for communication with the k8s API from the `remote_dev agent module` ## User Value - This Epic has no user facing changes in GitLab.com but sets up the needed foundation in the GA4K for us to begin building upon. ## Limitations - We are opting to use `DWO` built from the Devfile specification.  ## References - https://che.eclipseprojects.io/2021/10/12/@mario.loriedo-devfile-v2-and-the-devworkspace-operator-p1.html