GitOps as a software engineering practice has become increasingly popular especially when it comes to applications on Kubernetes. Using a Git repository as its single source of truth, teams commit declarative configurations into Git, and these configurations are used to create environments needed for Continuous Delivery.
Benefits of GitOps.
Optimized GitOps with CAEPE.
However, GitOps management can become unwieldy as repositories multiply. CAEPE handles the latter stages of the GitOps process, ensuring that new configurations are correctly deployed to your Kubernetes clusters wherever they are. In particular, for GitOps on edge and air-gapped infrastructure, CAEPE simplifies automation, deployment, analytics, network slicing, policies & security – making management of even hundreds of edge and air-gapped clusters possible.
Developer commit changes of Kubernetes resource definitions to Git repo.
CI is triggered, creating new container image.
Developer issues a pull request.
The pull request is reviewed, and changes are merged to the main branch triggering a webhook.
CAEPE clones the repo and applies the required changes to cluster configuration.
Kubernetes reconciles the changes required to cluster resources, until it achieves the desired configuration.
CAPE monitors progress and reports that the application is in sync.