Prerequisites and Environment Sizing

Estimated time: ~10 minutes

Learning objectives

  • Confirm the prior knowledge this workshop expects

  • Understand which platform components the lab already provisions

  • Choose a cluster sizing profile that matches your audience (userCount)

  • Know how URLs and credentials differ between GitHub Pages preview and a live showroom

Prior knowledge

You should be comfortable with:

  • Kubernetes / OpenShift basics — namespaces, Deployments, Services, Routes

  • YAML and declarative configuration

  • GitOps concepts (desired state in Git, continuous sync with Argo CD)

  • Gateway API awareness (Gateway, HTTPRoute) — deep expertise not required

  • Authentication models — difference between OIDC / JWT and API keys

If you need a refresher on the 3scale side, open Red Hat 3scale documentation in another tab. For Connectivity Link, use Connectivity Link docs.

What the lab already provides

When you join a deployed workshop instance, the cluster already includes:

  • 3scale (source) and Connectivity Link / Kuadrant (target) side by side

  • Red Hat Developer Hub, Keycloak (RHBK), Gitea, Argo CD

  • Istio (Service Mesh / Gateway API data plane)

  • Observability (Grafana, Thanos, Tempo) and the migration strategy set (Developer Hub Golden Path, Kuadrant Console, Migration Toolkit, APIShift)

You do not install these operators during the lab — you explore and migrate against them.

How to open the lab

  1. Register (or receive) workshop credentials from the registration portal.

  2. Open the Showroom URL for your cluster (pattern: https://showroom-showroom.apps.cluster.example.com).

  3. Use the Terminal tab for oc / curl, and open Developer Hub in a new browser tab if the embedded panel fails OIDC login.

The public GitHub Pages site is a documentation preview. Placeholders such as apps.cluster.example.com and apps.cluster.example.com are not live hosts. On a deployed showroom, those values are rewritten automatically to your cluster domain.

Environment sizing

Operators and instructors should size the OpenShift cluster before inviting users. Scaling is driven by a single Helm value: userCount in examples/helm/values.yaml.

Workshop infrastructure is installed from the Helm App-of-Apps chart under examples/helm/. That chart renders Argo CD Application resources for operators, demo apps, showroom, and migration UIs. The child chart components/applicationsets (enabled as connectivity-link-applicationsets in values.yaml) deploys the Argo CD ApplicationSet that discovers user Git repos in Gitea and keeps per-user Applications in sync — it is part of the same install path, not a separate manual step.

Quickstart cluster profiles

Profile Users (userCount) Control plane Workers Worker size (each)

Minimum viable

~30

3 masters

3

16 vCPU / 64 Gi

Standard demo

~100

3 masters

6

16–32 vCPU / 64–128 Gi

Full workshop

200

3 masters (16 vCPU / 64 Gi recommended)

8–12

32 vCPU / 128 Gi
Single-node (SNO) or undersized clusters are not supported for a full multi-user workshop. Plan capacity for concurrent DevSpaces workspaces if attendees will scaffold apps.

Operator / stack footprint (approximate)

Steady-state memory already consumed by platform stacks (independent of userCount):

Stack Approx RAM Example namespaces

Service Mesh (Istio ambient)

~4 Gi

istio-system, ztunnel

Connectivity Link / Kuadrant

~2 Gi

kuadrant-system

Observability (Grafana / Tempo / Thanos)

~3 Gi

openshift-cluster-observability-operator, openshift-tempo

Developer Hub

~2 Gi

developer-hub

3scale

~4 Gi

3scale-system

Migration UIs (APIShift + Toolkit + Console plugin)

~1.5 Gi

gateforge, migration-toolkit, custom-rhcl-console

Identity / SCM

~3 Gi

rhbk-operator, gitea

For RHDP KubeVirt quota details and per-user DevSpaces footprints, see the repository README section Cluster Sizing: https://github.com/maximilianoPizarro/from-3scale-to-connectivity-link#cluster-sizing

Next

Continue with Migration Overview to learn why organizations move from 3scale to Connectivity Link.