Chapter 7. GitOps Console features and troubleshooting

The GitOps Console plugin provides search, filters, and client-side pagination on resource list pages. These features improve usability and browser performance for large lists.

Search

The search field lets you match resources by Name or Label. Search is separate from filters, so you can combine search with filters to narrow results further.

Filters

Available filters vary by resource type:

You can combine multiple filters to narrow results further. Search and filters work together.

Pagination

Pagination keeps large result sets usable and improves browser performance. The console shows one page of rows at a time so long lists are easier to scan and the browser does not render every row at once.

Pagination is available on all GitOps list pages (Applications, ApplicationSets, AppProjects, ImageUpdaters, and Rollouts) and on nested tables in details pages:

Pagination behavior:

You can search, filter, and paginate resources on the GitOps Console plugin list pages.

The GitOps Console plugin provides two kinds of graphical experience:

Application graph view

On an Application Resources tab, the graph view shows immediate managed resources for the Application, not the full Argo CD resource tree. The graph displays resources as nodes with connections showing their relationships.

Graph features:

Use the Argo CD link to open the Argo CD UI and view the complete hierarchy.

ApplicationSet graph view

On an ApplicationSet Applications tab, the graph view shows Applications generated by the ApplicationSet. The list view on the same tab shows the same applications in table form.

When progressive sync is not configured, the graph uses an owner reference layout. The ApplicationSet node connects to each generated Application. Each Application node shows sync and health status. You can pan, zoom, group nodes, and open context actions from the graph toolbar.

When progressive sync is enabled and the controller reports step status, you can switch the graph to Progressive Sync Flow View. In this layout, Applications are grouped by sync step instead of shown flat under the ApplicationSet. Each step group shows:

The controller advances one step at a time. A step must reach a healthy state before the next step starts syncing.

This step-based flow is separate from sync waves on an Application’s managed resources, which is the Sync Wave column on an Application Resources tab. Progressive sync controls the order in which Applications sync; sync waves control the order of resources within a single Application sync.

Rollout topology integration

In the Developer perspective Topology view, Rollout workloads appear in graph or list view when the Rollout CRD is installed on the cluster and you are using OpenShift Container Platform 4.19 or later.

The Topology page includes the following components:

The Rollout kind appears in the filter by resource list when Rollouts exist in the project, shown with the R badge.

From the GitOps Rollouts list, Details tab, or Pods tab, use the Topology view control to open this graph. From Details or Pods, the selected Rollout is highlighted.

You can view Application resources, ApplicationSet applications, and Rollout workloads in graphical layouts.

The GitOps Console plugin provides two kinds of graphical experience:

On an Application, open the Resources tab and switch to Graph view.

The graph and table show immediate managed resources for the Application, not the full Argo CD resource tree. The graph displays resources as nodes with connections showing their relationships. You can pan, zoom, and select resources. Status filters apply to both the table and the graph.

On an ApplicationSet, open the Applications tab and switch to Graph view.

The graph shows Applications generated by the ApplicationSet. Use Filter and search to narrow by health and sync status. The list view on the same tab shows the same applications in table form.

When progressive sync is not configured, the graph uses an owner reference layout. The ApplicationSet node connects to each generated Application. Each Application node shows sync and health status. You can pan, zoom, group nodes, and open context actions from the graph toolbar.

When progressive sync is enabled on the ApplicationSet and the controller reports step status, switch the graph to Progressive Sync Flow View from the toolbar. The control is disabled until step status is available.

In this layout, Applications are grouped by sync step instead of shown flat under the ApplicationSet. Each step group shows:

The controller advances one step at a time. A step must reach a healthy state before the next step starts syncing.

Progressive sync requires:

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: progressive-sync-apps
  namespace: openshift-gitops
spec:
  generators:
    - list:
        elements:
          - name: app-stage-1
            stage: '1'
          - name: app-stage-2
            stage: '2'
          - name: app-stage-3
            stage: '3'
  strategy:
    type: RollingSync
    rollingSync:
      steps:
        - matchExpressions:
            - key: stage
              operator: In
              values:
                - '1'
        - matchExpressions:
            - key: stage
              operator: In
              values:
                - '2'
        - matchExpressions:
            - key: stage
              operator: In
              values:
                - '3'
  template:
    metadata:
      name: '{{name}}'
      labels:
        stage: '{{stage}}'
    spec:
      project: default
      source:
        repoURL: https://github.com/example/repo.git
        targetRevision: HEAD
        path: apps/{{name}}
      destination:
        server: https://kubernetes.default.svc
        namespace: '{{name}}'

The template.metadata.labels values must match the rollingSync.steps selectors. Applications that do not match any step are not synced by RollingSync and must be synced manually.

This step-based flow is separate from sync waves on an Application’s managed resources, which is the Sync Wave column on an Application Resources tab. Progressive sync controls the order in which Applications sync; sync waves control the order of resources within a single Application sync.

In the Developer perspective, open Topology to see Rollout workloads in graph or list view.

Rollout topology integration requires:

When available, the Topology page includes the following components, from top to bottom:

From the GitOps Rollouts list, Details tab, or Pods tab, use the Topology view control to open this graph. From Details or Pods, the selected Rollout is highlighted.

Progressive sync is an optional feature that requires explicit configuration.

The GitOps Console plugin provides consistent features across all GitOps resource list and details pages.

Use these troubleshooting tips to resolve common issues with the GitOps Console plugin.

GitOps is missing from the navigation

The plugin is disabled, or the plugin pods are not running. Refresh the browser after you enable the plugin.

ImageUpdaters or Rollouts are missing

Those list pages appear only when the matching CRDs are installed.

Empty lists or disabled actions

Confirm the Project (namespace) selector and that resources exist. Empty lists or disabled edit and delete actions often mean the user lacks OpenShift Container Platform RBAC (get, list, create, update, patch, or delete) on the GitOps custom resources. An AppProject can still block an Argo CD sync after a YAML save succeeds.

Health is Unknown or missing

The plugin reads health from the Application CR. Set controller.resource.health.persist: "true" in the argocd-cmd-params-cm ConfigMap, for example in the openshift-gitops namespace.

Application stays OutOfSync

Check Sync Status, History, conditions, and Events. The Application kebab and History tab do not provide Sync or Rollback. Use the Argo CD UI, YAML, or the argocd CLI.

View in Argo CD is missing or disabled

The action requires a Route to the Argo CD server for that Application’s instance. Confirm the Argo CD Route exists in the Application namespace or the instance namespace your Operator uses.

The Application graph looks incomplete

The Graph view on the Application Resources tab shows immediate managed resources only, not the full Argo CD resource tree. Use the Argo CD link on the tab for the complete hierarchy.

List pages are slow

Search, filtering, and pagination run in the browser on the loaded list. They do not use Kubernetes API limit or continue tokens. Select a narrower namespace or tighten filters.

Pagination shows unexpected totals

Totals reflect the filtered and searched result set, not the full cluster inventory. Clear filters or search, then confirm the namespace selector.

ImageUpdater shows no recent updates

Nothing was recorded in status.recentUpdates for the last reconciliation cycle. Check Ready, Conditions when present, and the ImageUpdater YAML status. Some ImageUpdater builds do not write conditions even when updates exist.

Rollout Rollback is disabled

Rollback is disabled for the current revision, which is the first revision in the tree, when the ReplicaSet is missing, or when you cannot patch the Rollout. Use a non-current revision and confirm your permissions.