GitOps Pipelines

Use GitOps to automate deployments to Kubernetes clusters

Fully Automated, Zero-Effort Deployments

GitOps is an efficient and effective approach to continuous deployment (CD) that leverages Git as a single source of truth for both infrastructure and applications. By being declarative, it provides for better standardization, enhanced security, and ultimately, improved productivity. So why aren’t you using the same GitOps process that your developers use for Kubernetes management? With Rafay’s GitOps Pipelines, you can:

Build a multi-stage pipeline for both applications and clusters in minutes

Fully automate deployments and remove error prone, manual steps

Guarantee that the desired state specified in your Git repos are instantly enforced on Kubernetes clusters

Tightly integrate your Kubernetes management solution with GitOps deployment

Create Multiple Pipelines Each with Multiple Stages

Integrated GitOps pipelines in the Rafay KMC can comprise multiple stages. The stages in the pipeline are then executed sequentially one after another. Pipelines in Rafay can either be triggered manually or by updates to a Git repository. For production environments, users can optionally incorporate a manual approval stage in the pipeline to ensure an authorized user has to review and approve the changes before the workloads are automatically updated on remote clusters.

Instantly Update Clusters Using GitOps

For environments requiring agile development cycles, users can go from a Git push to an updated application on managed clusters in seconds — 100+ times a day. This is particularly suited for developer environments where updates are very frequent.

Support for Git or Helm Repositories and Clusters Behind Firewalls

It is a security best practice to not operate an organization’s infrastructure in a flat network where everything can see and access everything else. As a result, it is common for organizations to isolate their Git repositories and their Kubernetes clusters behind separate firewalls. Rafay enables organizations to implement a zero trust security model for GitOps ensuring that changes made to Git repos can be seamlessly propagated to remote clusters operating behind dedicated firewalls in a separate network. Organizations do not have to punch holes in their firewalls or lower their security posture to implement GitOps.

Configure Pipelines with Flexible Triggers

Triggers are external events that start a pipeline job and/or stage. Rafay supports two types of triggers: Webhooks and Cron Job-based Repository Sync. If the Webhook payload satisfies the specified criteria, the pipeline job is started (example below). For Cron Jobs, the sync operation notices that monitored files have been updated and starts the pipeline.

Easily View & Manage Multiple Pipelines

Add, modify, pause, delete, and check the status of any number of pipelines, each with any number of stages. Pipelines are integrated into Rafay’s Kubernetes Management Cloud and therefore seamlessly inherit and follow the configured RBAC and project-based isolation configuration. This ensures a seamless user experience for authorized users and makes security/governance seamless and low burden for organizations by completely eliminating the operational burden of managing yet another product just for GitOps. Every pipeline job’s details are visualized for users, including their start time, status, total run time, and history.

Download the White Paper

Sample K8s Management POC Test Plan

Customize this POC plan for your K8s POC