Explore ArgoCD and APIs

This module connects the GitOps view in ArgoCD with the Software Catalog in Developer Hub and policies applied in the cluster.

View GitOps from Developer Hub (CD Tab)

The recommended way to monitor your ArgoCD applications is through the CD tab in Developer Hub:

  1. Open Developer Hub: https://backstage-developer-hub-developer-hub.apps.cluster.example.com

  2. Go to Catalog and find your component (e.g., user1-neuralbank-backend).

  3. Click on the component, then select the CD tab.

  4. You will see the ArgoCD sync status, health, and resource tree directly inside Developer Hub.

The CD tab provides the same information as the ArgoCD console but without requiring separate login. This is the easiest way for workshop participants to verify their deployments.

Alternative: Open the ArgoCD UI Directly

If you prefer to access ArgoCD directly:

  1. Go to ArgoCD: https://openshift-gitops-server-openshift-gitops.apps.cluster.example.com

  2. Log in with Log in via OpenShift.

  3. In Applications, filter by your namespace user1-neuralbank.

Workshop users have read-only access to their own applications (user1-*). If you don’t see applications after login, use the CD tab in Developer Hub instead — it provides the same visibility with integrated authentication.

ArgoCD ApplicationSet

Applications are generated automatically by an ApplicationSet that watches Gitea for new repositories:

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: workshop-neuralbank-backend
  namespace: openshift-gitops
spec:
  generators:
    - git:
        repoURL: https://gitea-gitea.apps.cluster.example.com
        revision: HEAD
        directories:
          - path: "*/neuralbank-backend"
  template:
    metadata:
      name: "\{\{path[0]}}-neuralbank-backend"
    spec:
      project: default
      source:
        repoURL: "https://gitea-gitea.apps.cluster.example.com/\{\{path[0]}}/neuralbank-backend.git"
        targetRevision: HEAD
        path: manifests
      destination:
        server: https://kubernetes.default.svc
        namespace: "\{\{path[0]}}-neuralbank"

Explore the Resource Tree

From the CD tab in Developer Hub (or ArgoCD directly):

  1. Observe Deployments, Services, Routes, ConfigMaps.

  2. For backend and MCP services, also see Gateway API resources (Gateway, HTTPRoute) and Kuadrant policies (AuthPolicy, RateLimitPolicy).

Check Sync Status: * Synced — cluster matches the manifest in Git * OutOfSync — pending changes or drift

Check Health: * Healthy, Progressing, Degraded

API Entity and OpenAPI

Many templates register an API entity alongside the Component:

  1. In the catalog, open the API entity associated with the backend.

  2. Review the embedded OpenAPI definition.

The OpenAPI definition documents paths, schemas, and examples — the reference for service consumers and the frontend.

Kuadrant Policies on OpenShift

For services exposed with the connectivity link pattern, inspect:

  • AuthPolicy — API Key authentication (primary), with optional OIDC JWT validation

  • RateLimitPolicy — rate limits applied to traffic matching the HTTPRoute

oc get authpolicy -n user1-neuralbank -o yaml
oc get ratelimitpolicy -n user1-neuralbank -o yaml

Summary

You explored GitOps state through the CD tab in Developer Hub (and optionally ArgoCD directly), located the API and its OpenAPI definition, and reviewed authentication and rate limit policies in the Kuadrant context.