284313f908
Some checks are pending
Bidi Control Character Guard / bidi-control-guard (push) Waiting to run
Circular Dependency Check / Check for new circular dependencies (push) Waiting to run
Citus Migration Smoke / Combined migrations on single-node Citus (push) Waiting to run
E2E Fresh Install Tests / fresh-install-e2e (push) Waiting to run
ext-v2 guardrails / Run ext-v2 guard and ESLint (push) Waiting to run
Integration Tests / Check for relevant changes (push) Waiting to run
Integration Tests / ${{ (github.event_name == 'schedule' || github.event.inputs.suite == 'full') && 'Full integration suite' || 'Tier-1 integration subset' }} (push) Blocked by required conditions
Mobile checks / Mobile lint + typecheck (push) Waiting to run
Mobile checks / Mobile unit tests (push) Waiting to run
Mobile checks / Mobile dependency audit (report) (push) Waiting to run
Mobile checks / Mobile reproducibility checks (push) Waiting to run
Secrets guard (env backups) / Ensure no tracked env backup files (push) Waiting to run
Temporal Readiness / fast-readiness (push) Waiting to run
Temporal Readiness / docker-parity (push) Waiting to run
TypeScript Type Check / Nx affected typecheck (push) Waiting to run
Unit Tests / Skipped-test budget (push) Waiting to run
Unit Tests / Nx affected unit tests (push) Waiting to run
Unit Tests / Server unit coverage (informational) (push) Waiting to run
Validate Tenant Management Schema / Check for relevant changes (push) Waiting to run
Validate Tenant Management Schema / Validate Tenant Management Schema (push) Blocked by required conditions
EE Workflows Build Guard / ee-workflows-build-guard (push) Waiting to run
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz Source: /opt/alga-psa on psa.joliet.tech
50 lines
2.2 KiB
Markdown
50 lines
2.2 KiB
Markdown
# Scratchpad - Ubuntu 24.04 k3s VM Appliance
|
|
|
|
## Metadata
|
|
- Date started: 2026-02-23
|
|
- Plan folder: `ee/docs/plans/2026-02-23-ubuntu-k3s-vm-appliance/`
|
|
- Related chart: `helm/` with base values at `helm/values.yaml`
|
|
|
|
## Decisions Locked So Far
|
|
1. Base OS: Ubuntu Server 24.04 LTS.
|
|
2. Kubernetes runtime: k3s for v1.
|
|
3. Upgrade control plane: GitOps pull model with Flux.
|
|
4. VM artifact targets: vSphere OVA and QCOW2.
|
|
5. Automation code location: `ee/` subtree under `ee/appliance/`.
|
|
6. Product posture: locked appliance, no customer host tweaking.
|
|
7. Topology path: start single-node, support migration to 3-node HA with embedded etcd.
|
|
8. Artifact distribution: hybrid model (vendor-hosted default plus signed offline bundle import).
|
|
9. Support policy: support `N`, `N-1`, and `N-2`.
|
|
10. Upgrade jump policy: sequential only (`N -> N+1`).
|
|
|
|
## Proposed Repository Layout
|
|
1. `ee/appliance/packer/`
|
|
2. `ee/appliance/cloud-init/`
|
|
3. `ee/appliance/k3s/`
|
|
4. `ee/appliance/gitops/`
|
|
5. `ee/appliance/scripts/`
|
|
6. `historical local release metadata (removed)`
|
|
|
|
## Open Decisions To Finalize
|
|
1. Concrete endpoint names and ownership for vendor-hosted artifact storage.
|
|
2. Concrete endpoint names and operator flow for signed offline bundle distribution/import.
|
|
3. Exact release promotion cadence and approval gates for `candidate -> stable`.
|
|
|
|
## Risks / Gotchas
|
|
1. If stale image rebuild policy is not enforced, "always-current" requirement fails in practice.
|
|
2. If values overlays diverge from `helm/` baseline too much, maintenance cost rises.
|
|
3. Single-node defaults can block clean HA migration if datastore and scheduling assumptions are not made now.
|
|
4. Air-gapped or restricted-network customer sites require explicit mirror/import path from day one.
|
|
|
|
## Command Notes
|
|
1. Plan folder created:
|
|
- `mkdir -p ee/docs/plans/2026-02-23-ubuntu-k3s-vm-appliance`
|
|
|
|
## Next Implementation Sequence (High-Level)
|
|
1. Scaffold `ee/appliance` filesystem and script entrypoints.
|
|
2. Add Packer templates and autoinstall seed.
|
|
3. Add first-boot k3s + GitOps bootstrap flow.
|
|
4. Add release manifest schema + publication logic.
|
|
5. Add upgrade and rollback scripts.
|
|
6. Validate single-node install and HA migration path in test environment.
|