Workload base
Create a Java/JBoss app base in lab-workloads with deployment, service, config, health checks, and overlay placement.
Active workload spoke
spoke-dc
spoke-dc is the active workload cluster. It is the likely first target for the Java/JBoss demo app once workload placement, Kafka connectivity, and mesh onboarding are ready.
Status
Recorded current state
- GitOps
spoke-dc-cluster-configrecordedSynced/Healthyfrom local spoke Argo CD status.- Storage
- ODF remains on intended
localblocktopology. - OADP
lab-dpareconciled, BSL available, latest daily backup completed in the recorded run.- Identity
- WSO2 IS was removed. OAuth IDP is Google only.
- AMQ/Kafka
- Retired from spoke desired state. No local
kafkanamespace or Strimzi objects remain. - User workload metrics
- Enabled; user workload Prometheus, Thanos ruler, and the Prometheus operator should run here.
Service mesh
OSSM 3 state
servicemeshoperator3.v3.3.2andkiali-operator.v2.22.2CSVs recordedSucceeded.Istio/defaultandIstioCNI/defaultrecorded healthy.- Istio revision
defaultrecordedReady=Truewith versionv1.26.8. - Only
istio-ingressis labeled for injection. - No Bookinfo, metrics-demo, otel-demo, liberty-canary, or demo-orders workload namespace exists on the spoke.
App readiness
What is needed next
Kafka dependency
Use RKE2 Kafka after the advertised Kafka ingress DNS names resolve and an app-specific SCRAM user exists.
Mesh onboarding
Label the app namespace for injection only after the workload manifests and routing intent are defined.
DR choice
Decide whether the app also lands in spoke-dr as hot standby or remains active-only during initial validation.