### Problem to solve Executing `kubectl` commands for managed clusters requires users to (generally) download a provider-specific CLI as well as install kubectl locally. ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal Provide command-line access to the cluster within GitLab by showing a "terminal" button (similar to what we do for pod web terminal)  Deploy a dedicated pod to access command-line and kill pod once session ends. ### Permissions and Security Currently only owners and maintainers have access to "Operations>>Kubernetes" which already provides access to master credentials for clusters. This should eliminate any concerns of being able to access the command-line and issue `kubectl` commands. ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references