Framework 2.0 Decision Index

From Helm chart to service in 5 minutes. Every change transparent.

What this covers

Entry point for Framework 2.0 decisions. Links to persona solutions and individual ADRs that describe configuration language, orchestration, secrets, billing, maintenance, and testing.

TL;DR: Framework 2.0 Architecture

Framework 2.0 enables adding managed services (Redis, PostgreSQL, Keycloak, etc.) without writing code in most cases. Service Maintainers define services using annotated Helm charts.

CRDs are directly generated from Helm charts and deployed to the cluster by the framework. The service users interact with the generated CRDs to provision and manage service instances. Every change to the service is snapshotted and versioned by the framework, enabling transparency, rollbacks, and safe upgrades.

Many upstream Helm charts work out of the box, additional maturity levels (backup, monitoring, etc.) can be added by Service Maintainers using a wrapper chart and some framework-specific library charts.

We aim at keeping the framework as modular as possible, so we can upgrade and replace individual components while keeping the blast radius of changes as small as possible.

Architecture in progress

The new framework is under active development in the Github organization github.com/helmetica-framework.

Personas

  • Framework 2.0 Personas - Requirements and definitions for Service Users, Service Maintainers, Service Operators, Framework Engineers.

Documentation

  • Testing Strategy - ⚠️ [Outdated] Comprehensive five-layer testing approach for Framework 2.0

Architecture Decision Records

Archive

The following ADRs are artifacts from older PoCs. They are preserved for historical context.