Move the GitLab Kubernetes Agent to Core
Request for comments
There is an ongoing discussion about moving the GitLab Kubernetes Agent to Core. This issue invites the GitLab community to share feedback on this initiative.
Moved to GitLab Core
We are connecting the GitLab CI/CD with an in-cluster agent, and enable CI jobs to target kubernetes clusters through an agent using the CI tunnel. The first iteration of the CI tunnel is expected to be released in %14.1. This feature enables users to run commands against their cluster using the agent's service account, and is being moved to Core.
Together with this change, the agent registration logic is being moved to Core too.
Moreover, we plan to deliver the group-level extension of the CI tunnel - reusing the agent's service account - in GitLab Core too in a future milestone.
This decision was made in the https://gitlab.com/gitlab-com/Product/-/issues/2690#note_617899861 (internal) issue. The timeline is to deliver it as soon as we can, likely in %14.2 or %14.3.
Other features
The Agent today supports
- pull based deployments
- network security policy integrations
- ... (other features we are working on, planning)
These features are not being moved to GitLab Core and such a move is not planned at this moment. If you are interested in these features being moved, please, add your comment, possibly with a detailed use case description.