<!--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=418264) </details> <!--IssueSummary end--> ### Problem to solve We need to set up a deployment of the container designed in #418261, as well as a namespace, service account, and RBAC rules allowing the pod to access the given k8s cluster. ### Proposal KAS will be responsible for deploying the web terminal to a K8s cluster. See https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/issues/479+, which introduces a new gRPC endpoint. Rails will then call the KAS gRPC endpoint through the `kas-grpc` gem, which would be updated as part of the work in KAS. Add a GraphQL mutation that will call the [KAS endpoint that deploys the web terminal to a K8s cluster](https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/issues/479). 1. Add a new table to keep a record of the deployed web terminals, ie: `cluster_agent_web_terminals` with fields: - `agent_id` - `namespace` - `pod_name` - timestamps 1. Upgrade the `kas-grpc` gem 1. Introduce a new service (e.g.: `KAS::WebTerminal::Deploy`) that will make use of the new "deploy web terminal" module in `kas-grpc`. The arguments to the `kas-grpc` module are: - web terminal image - The image tag should match GitLab's MAJOR and MINOR versions in the following pattern: `vMAJOR.MINOR`. Example argument: `registry.gitlab.com/gitlab-org/cluster-integration/shell-image:v16.4.0` - agent_id KAS optionally accepts a `service_account` argument. We can leave this blank for now. 1. In `KAS::WebTerminal::Deploy`, make sure to record the deployed web terminal details in the `cluster_agent_web_terminals` table. This will be referenced later in the workflow to delete the web terminal pod. 1. Add a GraphQL mutation (e.g.: `Mutations::KAS::WebTerminal::Deploy`) that will call the newly-introduced service The GraphQL mutation can be called like: ```shell mutation { webTerminalDeploy(input: {agentId: "gid://gitlab/Clusters::Agent/1") { errors webTerminal { namespace // e.g.: agent-namespace podName // e.g.: web-terminal-abcde } } } ``` **Note:** The `namespace` and `pod` are recorded for a later iteration around clean-up/deletion. ### Intended users Unknown <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas are described at https://about.gitlab.com/handbook/product/personas/ * [Parker (Product Manager)](https://about.gitlab.com/handbook/product/personas/#parker-product-manager) * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/product/personas/#delaney-development-team-lead) * [Presley (Product Designer)](https://about.gitlab.com/handbook/product/personas/#presley-product-designer) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/product/personas/#sasha-software-developer) * [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/product/personas/#priyanka-platform-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/product/personas/#sidney-systems-administrator) * [Rachel (Release Manager)](https://about.gitlab.com/handbook/product/personas/#rachel-release-manager) * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/product/personas/#simone-software-engineer-in-test) * [Allison (Application Ops)](https://about.gitlab.com/handbook/product/personas/#allison-application-ops) * [Ingrid (Infrastructure Operator)](https://about.gitlab.com/handbook/product/personas/#ingrid-infrastructure-operator) * [Dakota (Application Development Director)](https://about.gitlab.com/handbook/product/personas/#dakota-application-development-director) * [Dana (Data Analyst)](https://about.gitlab.com/handbook/product/personas/#dana-data-analyst) * [Eddie (Content Editor)](https://about.gitlab.com/handbook/product/personas/#eddie-content-editor) * [Amy (Application Security Engineer)](https://about.gitlab.com/handbook/product/personas/#amy-application-security-engineer) * [Isaac (Infrastructure Engineer)](https://about.gitlab.com/handbook/product/personas/#isaac-infrastructure-security-engineer) * [Alex (Security Operations Engineer)](https://about.gitlab.com/handbook/product/personas/#alex-security-operations-engineer) * [Cameron (Compliance Manager)](https://about.gitlab.com/handbook/product/personas/#cameron-compliance-manager) --> ### Feature Usage Metrics <!-- How are you going to track usage of this feature? Think about user behavior and their interaction with the product. What indicates someone is getting value from it? Create tracking issue using the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->