Workshop details

Module structure

The workshop is split into multiple independent modules that can be completed in any order. You won’t be writing code or hand-crafting YAML — you will mostly be deploying pre-built configurations and observing the results.

Want to see results faster? Modules 3 (GitOps Fundamentals), 4 (Secrets Management), and 5 (Namespace as a Product) provide foundational background knowledge but can be skipped if you are most interested in seeing the platform in action. Jump directly to the Developer Hub modules to experience the unified developer portal, software catalog with AI/agentic integration (MCP, Lightspeed), and self-service templates with automated supply chain security gates (SBOM generation, vulnerability scanning, compliance enforcement).

Read this page in its entirety to understand the environment and how to use the web terminal.

Your environment

You have your own dedicated OpenShift cluster. The following dependencies are pre-installed to facilitate the workshop:

graph TD subgraph portal ["Developer Portal"] RHDH["Red Hat Developer Hub"] end subgraph cicd ["Source & CI/CD"] GL["GitLab"] -->|triggers| TEK["Tekton Pipelines"] TEK -->|pushes images| Q["Quay"] end subgraph deploy ["Deployment"] ARGO["Argo CD"] end subgraph services ["Platform Services"] KC["Keycloak"] V["Vault"] --> ESO["External Secrets"] end subgraph workspace ["Development"] DS["Dev Spaces"] end RHDH -->|scaffolds repos| GL RHDH -->|launches| DS RHDH -->|monitors| TEK RHDH -->|tracks images| Q RHDH -->|views deployments| ARGO GL -->|provides manifests| ARGO ESO -->|injects secrets| ARGO KC -. "SSO" .-> RHDH KC -. "SSO" .-> GL KC -. "SSO" .-> ARGO

  • OpenShift GitOps (Argo CD) — Declarative, Git-driven deployment

  • OpenShift Pipelines (Tekton) — Cloud-native CI/CD

  • Red Hat Developer Hub Operator — Backstage-based developer portal

  • OpenShift Dev Spaces — Cloud development workspaces

  • HashiCorp Vault + External Secrets — Centralised secrets management

  • Keycloak — Identity and access management

  • GitLab — Source code management

  • Quay — Container image registry

How you will work

You will primarily use a GitOps-driven configuration approach. This means you will use OpenShift GitOps to deploy and manage platform components. Don’t worry if this is new to you — it’ll be explained as you follow the content. It essentially boils down to a set of YAML files in a Git repository being continuously reconciled against your OpenShift cluster. We’re taking a production-like approach in this workshop! 😎

Executable terminal commands

Throughout the workshop, you will see command snippets with a terminal icon in the top-right corner. Select the terminal tab on the right, then click terminal icon in the snippet to automatically execute the command in the Wetty terminal tab.

Try it now. Select the Terminal tab, then click the terminal icon in the top-right corner of the code snippet below:

oc version --client

This should display your OpenShift CLI version. You can also copy commands and paste them manually, but the play button makes it faster!

You can use the clear command at any time to clean up the terminal output and start fresh.