4SO LabRepeatable platforms
Blueprints and profiles replace environment-specific assembly.
PLATFORM ENGINEERING / PRIVATE CLOUD
4SO Platform FactoryBuild, import and operate application platforms
Turns raw servers or existing Kubernetes environments into standardized RKE2, OKD or imported Kubernetes platforms with catalog, fleet, release, policy, disconnected delivery and Day‑2 operations.
RKE2OKDExisting KubernetesCatalog & Fleet
4SO Platform Factory components: from raw infrastructure to target platforms
- 1Raw infrastructureRaw servers or existing Kubernetes environments enter the product lifecycle as targets.
- 2Management PlaneSelf-contained on RKE2; the Factory never migrates itself into a target distribution.
- 4Forgejo + Argo CDForgejo carries desired state; Argo CD reconciles it and detects drift.
- 5zot OCI registryThe canonical artifact plane, including disconnected delivery with oc-mirror v2 and zot.
- 6Reconciliation loopObserved state is compared with desired state; UI success never replaces runtime evidence.
- 7Managed RKE2A standard application platform the Factory builds and keeps under lifecycle.
- 8OKDDistribution-aware builds with openshift-install and oc; native OKD behavior is preserved.
- 9Existing KubernetesImport and capability discovery without installing duplicate platform stacks.
01PROBLEM & OUTCOME
Product problem
A private platform is not the sum of disconnected tools.
Kubernetes, registry, identity, policy, monitoring, upgrades and recovery become another operations burden if they are assembled without one product lifecycle.
Keep native behavior
RKE2, OKD and imported clusters share a product boundary without fake symmetry.
Day‑2 after install
Health, drift, node lifecycle and upgrade stay under fleet operations.
Trace releases
Desired state and artifacts retain identity and provenance.
02CAPABILITY SNAPSHOT
Capabilities
From infrastructure admission to workload delivery.
Factory owns platform lifecycle while target distributions keep their native capabilities.
Target lifecycle
Build a managed platform or enroll an existing cluster.
Profiles and blueprints
Versioned platform capabilities and templates.
Health and drift
Operate many targets through one product model.
Desired state
Forgejo records intent; Argo CD reconciles it.
Artifact plane and offline delivery
zot keeps canonical OCI identity; oc-mirror v2 + zot provide sealed acquisition.
Workload delivery
Application release and environment binding on observed platform capabilities.
Data protection
Policy, backup run, restore and drill for managed targets.
Node and upgrade
Drain, replace, maintenance and distribution-aware upgrade.
03TOPOLOGY / DEPLOYMENT MODEL
Deployment model
Management Plane and target distributions remain separate.
The Factory does not migrate itself into the target distribution. RKE2 management stays self-contained while RKE2, OKD and imported Kubernetes are distinct target identities.
| Target | Entry path | Ownership | Use |
|---|---|---|---|
| Managed RKE2 | Factory build | Platform lifecycle under Product Control Plane | Standard private application platform |
| Existing Kubernetes | Import + discovery | Existing runtime + 4SO lifecycle boundary | Bring existing clusters under management |
| Managed OKD | Distribution-aware build | OKD owns CVO/MCO/OVN/OLM/SCC behavior | OpenShift-compatible target |
| Existing OKD | Import + capability discovery | Native OKD + 4SO product workflows | Manage without duplicate platform stacks |
04ARCHITECTURE
Architecture
Product authority, desired state, reconciliation and runtime are different layers.
The architecture avoids making Git, Argo or the target cluster an accidental second product source of truth.
AUTHORITYPostgreSQL + Platform APIOrg/Project, catalog, fleet, release, durable operations and audit.
DESIRED STATEForgejoVersioned desired configuration and release inputs.
RECONCILIATIONArgo CDApply desired state and detect drift.
RUNTIMERKE2 / OKD / existing KubernetesDistribution-native serving behavior and observed capability state.
| Boundary | Mechanism | Operational contract |
|---|---|---|
| Artifact plane | zot | Canonical OCI registry for connected and disconnected delivery. |
| Managed OKD install | openshift-install / oc + scoped Redfish boot media | Bare-metal bootstrap follows the distribution contract. |
| Disconnected OKD | oc-mirror v2 → zot | Acquisition, inventory and mirror identity are sealed before install. |
| Dapr | Optional application runtime trait | Never replaces 4SO state/workflow/lock/secret authority. |
| Domain | Component / Mechanism | Behavior |
|---|---|---|
| Product authority | PostgreSQL + Platform API | Org/Project, Catalog, Blueprint, Fleet, Release and Durable Operation remain product authority. |
| Desired state | Forgejo | Desired configuration and release inputs are versioned; Git does not become Runtime Truth. |
| Reconciliation | Argo CD | Applies desired state and observes drift without creating an independent state authority. |
05LIFECYCLE
Lifecycle
Platform lifecycle extends past cluster creation.
A target remains a managed product resource through capability discovery, releases, node change, upgrade and recovery.
01Discoverprovider / cluster identity
02Planprofile · blueprint · capability
03Provision / Importcreate or enroll target
04Verifyobserved capability state
05Delivercatalog · release · reconcile
06Operatehealth · drift · maintenance
07Upgradedistribution-aware edges
08Recoverretry · rollback where valid · operator action
06PLATFORM PROFILES
Platform profiles
Factory turns distribution, capability and delivery contracts into Platform Profiles.
Each profile combines distribution identity, capability discovery, policy, supply chain and lifecycle. OKD and RKE2 are deliberately not forced into artificial implementation symmetry.
RKE2 PlatformMANAGED
A lightweight, self-contained Kubernetes platform.
- Managed lifecycle
- Catalog-driven add-ons
- Fleet operations
OKD PlatformDISTRIBUTION-AWARE
Uses OKD-native capabilities rather than duplicating them.
- OVN / OLM / SCC awareness
- No duplicate platform stacks
- Managed or imported
Imported KubernetesADOPT
Adopt an existing cluster without rebuilding it.
- Identity discovery
- Capability assessment
- Lifecycle admission
Application PlatformWORKLOAD
Application delivery over a managed target.
- Application Release
- Environment Binding
- Observed deployment evidence
DisconnectedSOVEREIGN
Acquire, mirror and install without runtime Internet dependency.
- Controlled acquisition
- Local registry
- Verified inventory
FleetDAY-2
Operate targets after creation.
- Node lifecycle
- Upgrade / maintenance
- Diagnostics / recovery
07ACTION & WORKFLOW CONTRACT
State and flows
Operations have explicit planning and recovery states.
Risk, approval, retry policy and runtime verification belong to the operation model rather than an informal runbook.
01PlanDRAFT → PLANNING
02ApprovalAWAITING_APPROVAL
03QueueAPPROVED → QUEUED
04ExecuteRUNNING
05RetryRETRY_WAIT
06VerifyVERIFYING
07SuccessSUCCEEDED
08RecoveryROLLING_BACK / NEEDS_OPERATOR
APPROVAL GATE
Deploy through plan and human approval
High-risk actions never reach execution without an independent approval boundary.
REQUEST
↓
PLAN
↓
APPROVAL?
EXECUTE
↙ ↘
BLOCKED
VERIFY
RECONCILIATION LOOP
Desired state ↔ observed runtime
Forgejo intent and Argo reconciliation do not create a second product authority.
FORGEJO
→
ARGO CD
↓
OBSERVE
↑
TARGET
←
DRIFT
DISCONNECTED SUPPLY CHAIN
Acquire → verify → mirror → admit
Artifact identity is sealed before target installation.
ACQUIRE
↓
DIGEST VERIFY
↓
OC-MIRROR V2
ZOT
TARGET ADMIT
Create Managed Platform
Raw infrastructure to registered target.
01Provider Input02Plan03Preflight04Provision05Distribution Bootstrap06Runtime Verify
Failure / RecoveryPLAN_FAILED remains pre-mutation; unknown side effects require reconciliation.
Import Existing Cluster
Enrollment without rebuilding the cluster.
01Credential Scope02Identity Discovery03Capability Discovery04Classify05Register06Eligibility
Failure / RecoveryIdentity or capability conflict returns to the operator.
Application Release
Release binds desired state to observed runtime.
01Artifact Admit02Policy03Desired State04Argo Reconcile05Runtime Observe06Evidence
Failure / RecoveryUnknown outcome is read back before any redispatch.
Disconnected OKD
Supply chain is sealed before install.
01Acquire02Verify Digest03Inventory04oc-mirror v205zot Mirror06Target Admit
Failure / RecoveryMissing or substituted artifacts fail closed.
Upgrade / Node Replace
Day‑2 remains distribution-aware.
01Admission02Drain / Stage03Mutation04Health Read-back05Capability Verify06Return to Fleet
Failure / RecoveryRollback is only used where the underlying workflow supports it.
ADDITIONAL OPERATIONAL FLOWS
Additional operational flows
Drift and data protection deserve visible lifecycle paths too.
Drift Reconciliation
Resolve desired/observed differences without overwriting distribution-native ownership.
01Observe Target02Diff Desired / Observed03Classify Owner04Plan Reconcile05Argo / Native Apply06Capability Read-back07Close Drift
Failure / RecoveryIf the difference belongs to a target-native subsystem, Factory preserves that ownership instead of forcing symmetry.
Backup / Restore Drill
Data protection continues through isolated restore and workload verification.
01Protection Policy02Capability Check03Create Backup04Verify Artifact05Isolated Restore06Workload Verify07Record Evidence
Failure / RecoveryAn unverified artifact or unverified restore is not accepted as recovery evidence.
| Action | Admission / Preconditions | Execution owner | Success criterion | Failure / recovery |
|---|---|---|---|---|
| Create Platform | Resolvable profile + provider/target inputs | Factory operation executor | Observed target matches desired profile | PLAN_FAILED / retry / recovery path |
| Import Cluster | Identity + access + capability discovery | Import workflow | Registered target with observed capabilities | Conflict requires operator resolution |
| Deploy Application | Immutable release + binding + policy | Forgejo/Argo + bounded executor | Observed deployment/service evidence | Unknown result is not blindly retried |
| Replace Node | Exact node identity + safety admission | Leased/fenced operation | Replacement ready; old node safely removed | Lease loss → retry wait or operator |
| Upgrade | Compatibility + health + evidence gate | Distribution-aware workflow | Observed version/capability health | Rollback only where real |
| Disconnected Delivery | Source lock + digest + inventory | acquire/mirror workflow | Target artifact identity matches sealed inventory | Mismatch fails closed |
FLOW
Failure states: PLAN_FAILED / FAILED / ROLLBACK_FAILED / NEEDS_OPERATOR / CANCELLED. Retry applies only to allowed failure classes; rollback is claimed only where the workflow supports it.
08OPERATIONS CATALOG
Operator surface
Platform engineering becomes a controlled product surface.
The operator works with targets, fleet, releases and lifecycle actions rather than per-cluster tribal procedures.
Create / import platform
Managed RKE2, OKD or existing Kubernetes.
Capability discovery
Read distribution identity and native capabilities.
Publish profile
Version reusable platform capability.
Deploy application
Bind immutable release to an environment.
Drain / replace
Change infrastructure membership safely.
Upgrade target
Use distribution-aware admission and verification.
Mirror artifacts
Seal acquisition through zot and oc-mirror v2.
Backup / Restore
Policy, run, drill and restore on the target.
Repair target
Reconcile observed state and surface operator-required cases.
Standardize the platform without erasing the distribution.
4SO owns the product lifecycle; the target keeps the native semantics that make it trustworthy.