RK2Lab Control Plane

Table of Contents

• Purpose
• Current status
• Planned structure
• Next immediate milestones

Pulumi-based management-cluster bootstrap and provisioning control plane for the RK2Lab ecosystem.

Purpose

This repository owns provisioning lifecycle logic that is intentionally separated from rke2lab runtime/manifests docs.

Primary near-term scope:

• Stage A bootstrap of the management cluster (bioskop)

• Deterministic readiness gating

• Exported bootstrap outputs for Stage B handoff

Current runtime path is intentionally Stage A-only. Workload-cluster (alcide, nikopol, etc.) provisioning manifests are applied after management bootstrap as Stage B concerns.

Current status

Initial scaffold created. First implementation target is the Stage A bootstrap contract.

Planned structure

• docs/bootstrap-contract.adoc — source-of-truth contract for inputs/outputs/readiness/failure semantics

• docs/incus-distribution-contract.adoc — reverse-engineered Incus distribution contract for seed/control-node provisioning

• docs/stagea-stageb-handoff-contract.adoc — explicit handoff assets between Stage A bootstrap and Stage B CAPI/CAPN reconciliation

• docs/rke2lab-authored-notes-import.adoc — imported historical planning notes from rke2lab carried forward as curated context

• src/main/java/ — Java Pulumi application

• Pulumi.yaml — Pulumi project metadata

• pom.xml — Maven build configuration

Next immediate milestones

1. Define contract and acceptance checks in docs/bootstrap-contract.adoc

2. Capture and normalize Incus distribution contract from rke2lab in docs/incus-distribution-contract.adoc

3. Define Stage A → Stage B handoff asset contract in docs/stagea-stageb-handoff-contract.adoc

4. Implement minimal pulumi up path for management-cluster seed

5. Export kubeconfig + endpoint outputs for Stage B consumers