A new era of Kubernetes integrations on GitLab.com
Blog post from GitLab
The GitLab Agent for Kubernetes establishes a secure connection between a GitLab instance and a Kubernetes cluster, facilitating pull-based deployments and offering enhanced network security alerts. Initially released for self-managed GitLab instances, the Agent is now available on GitLab SaaS with plans for further feature expansions. It addresses previous security concerns by allowing more controlled access rights, thereby appealing to security-focused users and experienced engineers. The Agent operates through two components: agentk, the cluster-side component, and kas, the GitLab server-side component, ensuring minimal impact on cluster resources and maintaining a secure, persistent connection. It supports GitOps workflows by automatically syncing GitLab repositories with cluster resources and is built on the gitops-engine, sharing codebase elements with ArgoCD. While currently supporting pull-based deployments, future developments aim to integrate with GitLab CI for push-based deployment support. The integration with Cilium in GitLab 13.9 enables easy generation and display of network policy alerts. Ongoing efforts focus on making the Agent generally available on GitLab.com SaaS and enhancing its integration capabilities for improved usability and performance.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.