Featured image for GitOps + Kubernetes

This article introduces new Red Hat OpenShift developer console features supporting GitOps processes for applications running in the cloud. Learn about improvements and updates to the OpenShift GitOps Operator, then watch a video showing how to manage cluster configurations and deliver cloud-native applications using Red Hat OpenShift GitOps in the developer console.

What is OpenShift GitOps?

GitOps is a set of practices to manage infrastructure and application configurations using Git. GitOps automates deployments and creates repeatable processes for your clusters and applications across different environments, supporting continuous deployment.

Note: See Why should developers care about GitOps? Also check out our free courses for learning GitOps.

OpenShift GitOps supports GitOps processes for cloud-native applications. It is built on top of Argo CD, a declarative GitOps continuous delivery tool for Kubernetes, and includes OpenShift's GitOps Operator and Pipelines Operator, both available from the OpenShift OperatorHub. Figure 1 shows the development flow and tools OpenShift GitOps provides.

GitOps in OpenShift flows from a Git commit through Argo CD to deployment in Kubernetes environments.
Figure 1. GitOps in OpenShift flows from a Git commit through Argo CD to deployment.

Improvements to the OpenShift GitOps Operator

OpenShift 4.9 and OpenShift 4.10 include updates to the OpenShift GitOps Operator. Many of these are improvements in the OpenShift GitOps user interface (UI), including the following:

  • In the List page, you can now see at a glance the sync status for your applications in each environment, letting you easily identify whether any are not in sync, as well as when the most recent deployments of those applications occurred.
  • In the Application Details page, you now can see new information regarding your application in each environment, such as the latest commit details and the number of each kind of resource the application has. You're also given a visual indication when a resource becomes out of sync or degraded, allowing you to take action quickly.
  • Previously, in OpenShift 4.8, the UI contained sections regarding pod health and the container image being used. Those have now been removed to provide you with a better overall experience and information that is more likely relevant to your needs.

Watch: OpenShift GitOps in action

The following video starts off with the basic Day 1 and Day 2 operations of the GitOps Application Manager (known as kam) command-line interface, which we strongly encourage using when interacting with the OpenShift GitOps UI. The Day 1 and Day 2 operations include generating GitOps manifests, deploying applications, and adding new environments, services, and routes.

Note: See Bootstrap GitOps with Red Hat OpenShift Pipelines and kam CLI for an introduction to the GitOps Application Manager (kam).

You will also get a taste of the Argo CD UI, and be introduced to new features in the OpenShift GitOps UI. Finally, the video compares the UI in OpenShift 4.8 to the updated 4.9 and 4.10 versions, so that you can prepare for the changes when upgrading.

Try out the new OpenShift GitOps feature in the OpenShift 4.9 and OpenShift 4.10 developer console for yourself, then let us know what you think in the comments.

Note: When watching this video, please note that the GitOps Operator is version 1.3.2, which ships Argo CD 2.1.8 and GitOps Application Manager 0.0.40.

Last updated: September 20, 2023