Chapter 6. GitOps Console resource management


The GitOps Console plugin provides dedicated pages for viewing and managing GitOps resources. You can create, view, and manage Argo CD Applications, ApplicationSets, AppProjects, ImageUpdaters, and Argo Rollouts through the OpenShift Container Platform web console.

Important

The GitOps Console plugin is not intended to replace the Argo CD UI or Argo Rollouts UI. Use the Argo CD UI and Argo Rollouts UI for functionality that is not provided by the plugin. The plugin provides status information and basic management capabilities conveniently for users who work in the OpenShift Container Platform web console.

6.1. Prerequisites

  • You have access to an OpenShift Container Platform cluster running version 4.19 or later.
  • You have installed the Red Hat OpenShift GitOps Operator.
  • You have enabled the GitOps Console plugin. For more information, see GitOps Console plugin setup and configuration.

6.2. About Applications in the GitOps Console

The GitOps Console Plugin provides list and details pages for Argo CD Applications in the OpenShift Container Platform web console. You can view Application health and sync status, inspect sources and managed resources, review sync history, and access related events.

The Applications list page provides the following capabilities:

  • Filter Applications by sync status and health status
  • Search Applications by name
  • View Application metadata including namespace, labels, and AppProject
  • Create Applications from YAML templates

The Application details page includes the following tabs:

  • Details: Identity, status, and sync policy configuration
  • YAML: Live manifest editor
  • Sources: Repository sources for single-source and multi-source Applications
  • Resources: Managed resources in list or graph view
  • Sync Status: Latest sync operation details
  • History: Sync and deployment history
  • Events: Kubernetes events for the Application object
Important

The plugin displays the health status stored on the Application custom resource (CR). If health is missing or incorrect, set controller.resource.health.persist: "true" in the argocd-cmd-params-cm ConfigMap.

You can view, create, and manage Argo CD Applications through the GitOps Console Plugin.

Prerequisites

  • You have access to the OpenShift Container Platform web console.
  • You have enabled the GitOps Console plugin.
  • Your permissions allow you to list Applications in one or more namespaces.

Procedure

  1. Navigate to GitOps Applications in the Administrator or Core platform perspective.
  2. Optional: Select a specific project from the Project dropdown to view Applications in that namespace, or select all projects to view Applications across all namespaces.
  3. Optional: Filter Applications by sync status or health status using the available filters:

  4. To create a new Application:

    1. Click Create Application.
    2. Edit the YAML template with your repository URL, path, target revision, and cluster destination.
    3. Click Create.
  5. To view Application details, click an Application name in the list.

    The details page provides the following tabs:

    • Details: View and edit identity, status, and sync policy
    • YAML: Edit the Application manifest
    • Sources: View repository sources
    • Resources: View managed resources in list or graph view
    • Sync Status: View the latest sync operation
    • History: View sync and deployment history
    • Events: View Kubernetes events

      For more information about common console features, see Common console features.

Note

The Application kebab menu and details page do not include Sync or Rollback actions. To perform a manual sync or rollback, use the Argo CD UI or the argocd CLI.

6.4. About ApplicationSets in the GitOps Console

The GitOps Console plugin provides list and details pages for Argo CD ApplicationSets in the OpenShift Container Platform web console. You can view ApplicationSets, review generated Applications, inspect generators, and use the graphical view for owner-reference and progressive sync layouts.

The ApplicationSets list page provides the following capabilities:

  • Filter ApplicationSets by health status
  • Search ApplicationSets by name
  • View ApplicationSet metadata including generated Applications count and generators count
  • Create ApplicationSets from YAML templates

The ApplicationSet details page includes the following tabs:

  • Details: Identity, status, conditions, and related counts
  • YAML: Live manifest editor
  • Generators: Structured view of generator configuration
  • Applications: Generated Applications in list or graph view
  • Events: Kubernetes events for the ApplicationSet object

The Applications tab graph view provides two layouts:

  • Standard layout: Owner-reference tree when progressive sync is not active
  • Progressive Sync Flow View: Step groups when progressive sync is enabled

You can view, create, and manage Argo CD ApplicationSets through the GitOps Console Plugin.

Prerequisites

  • You have access to the OpenShift Container Platform web console.
  • You have enabled the GitOps Console plugin.
  • Your permissions allow you to list ApplicationSets in one or more namespaces.

Procedure

  1. Navigate to GitOps ApplicationSets in the Administrator or Core platform perspective.
  2. Optional: Select a specific project from the Project dropdown to view ApplicationSets in that namespace, or select all projects to view ApplicationSets across all namespaces.
  3. Optional: Filter ApplicationSets by health status:

  4. To create a new ApplicationSet:

    1. Click Create ApplicationSet.
    2. Edit the YAML template with your generator configuration and Application template.
    3. Click Create.
  5. To view ApplicationSet details, click an ApplicationSet name in the list.

    The details page provides the following tabs:

    • Details: View identity, status, and conditions
    • YAML: Edit the ApplicationSet manifest
    • Generators: View generator configuration in structured format
    • Applications: View generated Applications in list or graph view
    • Events: View Kubernetes events

      For more information about common console features, see Common console features.

  6. To view generated Applications:

    1. Click the Applications tab.
    2. Switch between List view and Graph view as needed.

      The graph view shows:

      • Standard owner-reference tree layout
      • Progressive Sync Flow View when progressive sync is enabled

6.6. About AppProjects in the GitOps Console

The GitOps Console plugin provides list and details pages for Argo CD AppProjects in the OpenShift Container Platform web console. You can view AppProjects, review destinations and allow or deny rules, and manage roles and sync windows.

The AppProjects list page provides the following capabilities:

  • Filter AppProjects by description, applications, project type, source repositories, and destinations
  • Search AppProjects by name
  • View AppProject metadata including application count and configuration details
  • Create AppProjects from YAML templates

The AppProject details page includes the following tabs:

  • Details: Identity and project configuration summary
  • YAML: Live manifest editor
  • Allow/Deny: Allowed sources, destinations, and resource kind lists
  • Applications: Applications that belong to this AppProject
  • Roles: Argo CD project roles and bindings
  • Sync Windows: Configured sync windows
  • Events: Kubernetes events for the AppProject object
Note

OpenShift Container Platform RBAC and Argo CD AppProject rules control different aspects. OpenShift Container Platform RBAC controls console and API access to custom resources. AppProject rules control what Argo CD may sync for Applications in that project, including source repositories, destinations, and allowed resource kinds.

You can view, create, and manage Argo CD AppProjects through the GitOps Console Plugin.

Prerequisites

  • You have access to the OpenShift Container Platform web console.
  • You have enabled the GitOps Console plugin.
  • Your permissions allow you to list AppProjects in one or more namespaces.

Procedure

  1. Navigate to GitOps AppProjects in the Administrator or Core platform perspective.
  2. Optional: Select a specific project from the Project dropdown to view AppProjects in that namespace, or select all projects to view AppProjects across all namespaces.
  3. Optional: Filter AppProjects using the available filters:

    • Description: Has Description, No Description
    • Applications: Has Applications, No Applications
    • Project Type: Default Project, Custom Projects
    • Source Repositories: Has Source Repos, No Source Repos
    • Destinations: Has Destinations, No Destinations

      For more information about filtering, searching, and pagination, see About filtering, searching, and pagination in the GitOps Console.

  4. To create a new AppProject:

    1. Click Create AppProject.
    2. Edit the YAML template with your project configuration including source repositories, destinations, and resource allow or deny lists.
    3. Click Create.
  5. To view AppProject details, click an AppProject name in the list.

    The details page provides the following tabs:

    • Details: View identity and configuration summary
    • YAML: Edit the AppProject manifest
    • Allow/Deny: View allowed sources, destinations, and resource kinds
    • Applications: View Applications that belong to this AppProject
    • Roles: View Argo CD project roles and bindings
    • Sync Windows: View configured sync windows
    • Events: View Kubernetes events

      For more information about common console features, see Common console features.

6.8. About ImageUpdaters in the GitOps Console

The GitOps Console plugin provides list and details pages for Argo CD Image Updater custom resources in the OpenShift Container Platform web console. You can view ImageUpdaters, review matched applications, managed images, and recent update activity.

The ImageUpdaters list page provides the following capabilities:

  • Filter ImageUpdaters by apps and ready status
  • Search ImageUpdaters by name
  • View ImageUpdater metadata including apps count, images count, last checked time, and ready status
  • Create ImageUpdaters from YAML templates

The ImageUpdater details page includes the following tabs:

  • Details: Identity, status, and conditions
  • Recent Updates: Image updates from the most recent reconciliation cycle
  • YAML: Live manifest editor

Details tab

The Details tab summarizes identity and ImageUpdater status.

The summary section shows:

  • Name
  • Namespace
  • Labels with inline edit
  • Annotations
  • Created at

The status and configuration section shows:

  • Ready: Whether the last reconciliation completed without errors
  • Applications Matched: Number of applications matched by this ImageUpdater
  • Images Managed: Number of images eligible for update checking
  • Last Checked At: When the controller last checked for image updates
  • Last Updated At: When the controller last performed an image update
  • Observed Generation: Generation of the resource that was last reconciled

When the ImageUpdater reports status conditions, a Conditions section appears below the summary. The conditions table helps diagnose reconciliation problems and includes condition type, status, updated time, reason, and message.

Recent Updates tab

The Recent Updates tab shows image updates from the most recent reconciliation cycle in a paginated, sortable table. Each row includes alias, image, new version, apps updated, updated time, and message. If no updates were recorded in the last cycle, the tab shows an empty state.

Note

The ImageUpdaters page is available only when the ImageUpdater custom resource definition is installed on the cluster.

You can view, create, and manage Argo CD Image Updaters through the GitOps Console plugin.

Prerequisites

  • The ImageUpdater CRD is installed on your cluster.
  • You have access to the OpenShift Container Platform web console.
  • You have enabled the GitOps Console plugin.
  • Your permissions allow you to list ImageUpdaters in one or more namespaces.

Procedure

  1. Navigate to GitOps ImageUpdaters in the Administrator or Core platform perspective.
  2. Optional: Select a specific project from the Project dropdown to view ImageUpdaters in that namespace, or select all projects to view ImageUpdaters across all namespaces.
  3. Optional: Filter ImageUpdaters using the available filters:

  4. To create a new ImageUpdater:

    1. Click Create ImageUpdater.
    2. Edit the YAML template with your ImageUpdater configuration including image list, update policy, and write-back method.
    3. Click Create.
  5. To view ImageUpdater details, click an ImageUpdater name in the list.

    The details page provides the following tabs:

    • Details: View identity, status, and conditions
    • Recent Updates: View image updates from the most recent reconciliation cycle
    • YAML: Edit the ImageUpdater manifest

      For more information about common console features, see Common console features.

6.10. About Rollouts in the GitOps Console

The GitOps Console plugin provides list and details pages for Argo Rollouts in the OpenShift Container Platform web console. You can view Rollouts, scale replicas, inspect revisions and pods, and open Rollouts in the Developer Topology view.

The Rollouts list page provides the following capabilities:

  • Filter Rollouts by rollout status
  • Search Rollouts by name
  • View Rollout metadata including status, replica count, and pod count
  • Create Rollouts from YAML templates
  • Open the Developer Topology view

The Rollout details page includes the following tabs:

  • Details: Identity, scale, strategy, and status
  • YAML: Live manifest editor
  • Revisions: Rollout revisions with Promote, Abort, Retry, and Restart actions
  • Pods: Pods managed by the Rollout
  • Events: Kubernetes events for the Rollout object

The plugin integrates with the OpenShift Container Platform Console Developer Topology view. When the Rollout custom resource definition is installed, Rollout workloads appear in the topology graph with visual decorators and context actions.

Note

The Rollouts page is available only when the Rollout custom resource definition is installed on the cluster.

You can view, create, and manage Argo Rollouts through the GitOps Console Plugin.

Prerequisites

  • The Rollout custom resource definition is installed on your cluster.
  • You have access to the OpenShift Container Platform web console.
  • You have enabled the GitOps Console plugin.
  • Your permissions allow you to list Rollouts in one or more namespaces.

Procedure

  1. Navigate to GitOps Rollouts in the Administrator or Core platform perspective.
  2. Optional: Select a specific project from the Project dropdown to view Rollouts in that namespace, or select all projects to view Rollouts across all namespaces.
  3. Optional: Filter Rollouts by rollout status:

  4. Optional: Click Topology view to open the Developer Topology graph showing Rollout workloads.
  5. To create a new Rollout:

    1. Click Create Rollout.
    2. Edit the YAML template with your rollout configuration including strategy (Blue-Green or Canary), replicas, and pod template.
    3. Click Create.
  6. To view Rollout details, click a Rollout name in the list.

    The details page provides the following tabs:

    • Details: View and edit identity, scale, strategy, and status
    • YAML: Edit the Rollout manifest
    • Revisions: View revisions and perform rollout actions (Promote, Full Promote, Abort, Retry, Restart)
    • Pods: View pods managed by the Rollout
    • Events: View Kubernetes events

      For more information about common console features, see Common console features.

  7. To scale a Rollout, click the Details tab and use the inline scale controls to adjust the replica count.
  8. To manage rollout progression, click the Revisions tab and use the header actions menu to perform Promote, Abort, Retry, or Restart actions.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top