About Red Hat OpenShift GitOps

A controller that that performs the following actions:

A YAML manifest that describes how you intend to deploy the resources of your Argo CD application.

A resource object representing a deployed Argo CD application instance in an environment.

A resource object and a CRD that automatically generates Argo CD applications based on the contents of an ApplicationSet CR. Cluster administrators use this CRD to define a single ApplicationSet CR to generate and update multiple corresponding Argo CD Application CRs.

A custom Kubernetes controller that exists within Argo CD and processes ApplicationSet CRs. This controller automatically creates, updates, and deletes Argo CD applications based on the contents of an ApplicationSet CR.

A CRD representing a logical grouping of applications within a project that governs where and how an application is allowed to manage resources. You can use the AppProject CRD to restrict where and how Argo CD users are allowed to access those applications. Managing the AppProject instances is an action typically restricted to Argo CD administrators.

A gRPC/REST server that exposes the API consumed by the web UI, CLI, continuous integration (CI), and continuous deployment (CD) systems.

An open-source declarative tool that automates the continuous deployment of Kubernetes-based infrastructure and applications across clusters and development lifecycles.

An application that tracks the continuous deployment of individual Kubernetes resources from the GitOps repository, where the resources are defined as manifests, to a target Kubernetes cluster.

A Kubernetes CRD that describes the wanted state for a given Argo CD cluster that allows you to configure the components that make up an Argo CD cluster.

A single installation of Argo CD within a namespace that encapsulates all of the stateful aspects of a running Argo CD. Each Argo CD instance usually has a one-to-one mapping with an ArgoCD CR.

An entity within Argo CD that refers to the Argo CD open source project’s specific concept of projects, and the corresponding AppProject CR.

An Argo CD component that performs the following actions:

A CR that describes the wanted state for a given Argo CD instance. It allows you to configure the components and settings that make up an Argo CD instance.

A server that provides the API and UI for Argo CD.

A controller that you can use for managing the progressive deployment of applications hosted on Kubernetes and OpenShift Container Platform clusters. This controller has a set of CRDs that provides advanced deployment capabilities such as blue-green, canary, canary analysis, and experimentation.

A mode in which Argo CD is configured to manage all resources on the cluster including certain cluster-specific resources such as cluster configuration, cluster RBAC, Operator resources, platform Operators, or secrets.

In the GitOps context, you can have a control plane for every Argo CD you install. A GitOps control plane is any namespace where you can install an Argo CD. This control plane allows you to provision, manage, and operate Argo CD across networks, instances, and clusters.

A declarative description of the infrastructure required in your specified environment, for system and application setup or configuration. You can specify this description in a YAML configuration file in the Git repository. The declarative setup contains an automated process to make your environment and infrastucture match the described state. Examples include defining Argo CD applications, projects, and settings declaratively by using YAML manifests.

A default instance that a Red Hat OpenShift GitOps Operator instantiates immediately after its installation, in the openshift-gitops namespace, with additional permissions for managing certain cluster-scoped resources.

A declarative way to implement continuous deployment for cloud native applications. In GitOps, a Git repository contains deployment resources, which Argo CD keeps synchronizing with its cluster state.

A tool to configure and manage Red Hat OpenShift GitOps and Argo CD resources from the command line.

Modes that determine how you want to operate an Argo CD instance. The available modes are cluster-scoped instance and namespace-scoped instance.

The live state of application resources on a target cluster.

A cluster where you install Argo CD.

In the GitOps context, a manifest is a YAML representation of Kubernetes resources defined within a GitOps repository, with the intent to deploy those resources to a target Kubernetes cluster. Examples include the YAML representation of resources such as Deployment, ConfigMap, or Secret.

A software architecture where a single software instance serves multiple distinct user groups.

A mode in which Argo CD is configured to manage resources in only certain namespaces on a cluster and use the resources for application delivery.

A controller that continuously monitors Argo CD applications and provides a flexible way to notify users about important changes in the application state.

In the GitOps context, progressive delivery is a process of releasing application updates in a controlled and gradual manner.

An Operator that uses Argo CD as the declarative GitOps engine to enable GitOps workflows across multicluster OpenShift and Kubernetes infrastructures.

The process of comparing the latest code in the Git repository with the live state and determining the difference. For example, in the Argo CD UI, when you click Refresh, Argo CD connects to an application’s target Git repository, retrieves the content, and then generates manifests from that content. Argo CD then compares that target state against the live cluster state.

A cluster that you can add to Argo CD either declaratively or by using the GitOps CLI. Remote cluster is distinct from the local cluster where Argo CD is installed.

A configuration you use to exclude resources from discovery and sync so that Argo CD is unaware of them.

A configuration you use to include resources to discover, sync, and restrict the list of managed resources globally.

A software architecture where a single software instance serves a single user or group of users.

The process of synchronizing the live state of an application’s cluster resources with the target state defined within the Git repository to ensure consistency. Examples include syncing an application by applying changes to a cluster by using the Argo CD UI.

The status of an application that indicates whether the live state matches the target state.

The wanted state of application resources, as represented by files in a Git repository.

A custom Argo CD instance that you install and deploy to manage cluster configurations or deploy applications. By default, any new user-defined instance has permissions to manage resources only in the namespace where it is deployed.

Any process, usually defined within resources such as Deployment, StatefulSet, ReplicaSet, Job, or Pod, running within a container. Examples include a Spring Boot application, a NodeJS Express application, or a Ruby on Rails application.