How to use a pull-based (agent-based) approach for GitOps

The blog post explores the pull-based or agent-based approach to GitOps, particularly focusing on the GitLab Agent for Kubernetes. This method involves installing an agent on infrastructure components, such as Kubernetes clusters, to pull configuration changes from a GitLab repository whenever discrepancies from the desired state are detected. This approach helps maintain security by not requiring exposure of Kubernetes clusters outside the firewall and distributes resource consumption by having agents handle drift correction. The GitLab Agent for Kubernetes consists of two components: the agentk, which is installed on the Kubernetes cluster, and the kas, which resides on the GitLab instance and manages authentication, authorization, and change monitoring. The post illustrates a GitOps workflow where users create and update Infrastructure as Code configurations, with changes automatically applied to the infrastructure by the agentk. Despite its benefits, this approach necessitates maintaining agents on all infrastructure components, which can consume resources. The article concludes by announcing the next part of the series, which will cover the push-based or agentless approach to GitOps.

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.