Skip to content

Commit bc9c567

Browse files
tym83claude
andcommitted
docs(roadmap): correct compliance claims, refresh stale references
Address review feedback: - Scorecard/SLSA/OpenSSF badge: state tiers as self-chosen targets, not CNCF requirements (CNCF sets no Scorecard threshold; graduation requires only OpenSSF Passing; SLSA is not a graduation requirement) - CRA: open-source regime is Article 24 (open-source software steward), not Article 23 (contributor/manufacturer) - Refresh stale refs: OSPS Baseline launched Feb 2025; pin SLSA v1.2; cozystack#1265 closed; current-state snapshot to v1.5 shipped / v1.6 rc; last-updated - Correct Docker/OCI-CRI example (containerd->CNCF, runc->OCI; lost slot via missing CRI + dockershim removal) - MCS-API Beta since Cilium ~1.17-1.18; framework count eight->ten - Disambiguate section numbering: Security subsections -> Track 3.x - Note initial roadmap ratified via maintainer review on this PR Co-Authored-By: Claude <[email protected]> Signed-off-by: tym83 <[email protected]>
1 parent 80c19ca commit bc9c567

1 file changed

Lines changed: 45 additions & 35 deletions

File tree

‎ROADMAP.md‎

Lines changed: 45 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
**Status:** Living document — updated quarterly by the maintainers.
44
**Horizon:** May 2026 – May 2028 (two-year forward window).
5-
**Last updated:** 2026-05-18.
5+
**Last updated:** 2026-07-16.
66

77
This document describes where Cozystack is heading. It is the authoritative
88
public roadmap. The granular issue-level view lives in
@@ -130,8 +130,10 @@ Cozystack is shaped as a layered offering:
130130
- `v1.3` — storage-aware scheduling via LINSTOR extender, LINSTOR GUI, VM
131131
default images, app-level observability, S3 metering, cross-namespace VM
132132
restore.
133-
- `v1.4` (rc) — backup strategies, Flux 2.8, new `cozystack-ui`, cozy-tls,
133+
- `v1.4` — backup strategies, Flux 2.8, new `cozystack-ui`, cozy-tls,
134134
Redis TLS, app scheduling, CI/e2e hardening.
135+
- `v1.5` — shipped (latest stable line).
136+
- `v1.6` — in release-candidate.
135137

136138
### 3.2 Roadmap items already completed
137139

@@ -160,7 +162,7 @@ delivered:
160162
- Selecting managed application versions (#1246) — rescheduled to Q3 2026.
161163
- Grafana dashboard with SLA for each service (#1262) — rescheduled to
162164
Q3 2026.
163-
- API Gateway support (#1265) — rescheduled to Q3 2026.
165+
- API Gateway support (#1265) — closed.
164166
- Distroless images (#1261) — Q3 2026.
165167
- Automated platform updates (#1266) — Q3 2026.
166168

@@ -206,7 +208,7 @@ contract.
206208

207209
| Quarter | Deliverables |
208210
|---|---|
209-
| 2026 Q3 | Close in-flight items #1246 #1247 #1262 #1265. Cut `v1.5.0`. Publish `API Stability Policy` (alpha/beta/stable lanes, deprecation window). Scope the **GitOps Engine Abstraction** CzEP — decouple package delivery from the underlying engine so Flux remains the default while a second engine becomes feasible. |
211+
| 2026 Q3 | Close in-flight items #1246 #1247 #1262. Cut `v1.5.0`. Publish `API Stability Policy` (alpha/beta/stable lanes, deprecation window). Scope the **GitOps Engine Abstraction** CzEP — decouple package delivery from the underlying engine so Flux remains the default while a second engine becomes feasible. |
210212
| 2026 Q4 | Distroless images (#1261). Automated platform updates (#1266). Public **Release Trains** policy: `stable`, `fast`, `LTS`. Public support matrix for Kubernetes / host OS / Cilium / KubeVirt / storage backends / **GitOps engines**. **Argo CD experimental support** as an alternative GitOps engine — package model adapts `Package` / `PackageSource` to `Application` / `ApplicationSet` semantics; documented as `experimental` and opt-in at install time. |
211213
| 2027 Q1 | **Cozystack 2.0** — backwards-compatibility contract published; major API revision based on production feedback; HA control-plane improvements (stretched control plane, multi-AZ, etcd backup automation). **Argo CD support reaches alpha** — supported install path for greenfield clusters; not yet a migration target for existing Flux-based deployments. |
212214
| 2027 Q2 | `Platform Health API` covering operator, packages, GitOps engine (Flux or Argo CD), storage, networking, backups, ingress, auth. Explicit lifecycle states for apps, backups, restores, VMs, tenant clusters. **Argo CD support reaches beta** — feature parity with Flux for tenant app delivery, including `ApplicationSet` patterns for multi-tenant fan-out. |
@@ -235,23 +237,25 @@ Conformance Suite** that third parties can certify against.
235237
Incubation, then Graduated, and supports downstream commercial users in
236238
audited environments. **This is the largest single track in the roadmap.**
237239

238-
Cozystack's security work is structured around eight external frameworks plus
240+
Cozystack's security work is structured around ten external frameworks plus
239241
one internal program. Each is treated as a sub-project with concrete tasks.
240242

241-
#### 3.1 OpenSSF Best Practices Badge (Metal series)
243+
#### Track 3.1 — OpenSSF Best Practices Badge (Metal series)
242244

243245
The legacy and still-required "Passing / Silver / Gold" badge program.
244-
CNCF expects Passing as a minimum for Incubation and Gold for Graduation.
246+
CNCF Graduation requires only the Passing badge; Silver and Gold are suggested,
247+
not required, and are self-chosen targets here.
245248

246249
| Quarter | Target | Concrete tasks |
247250
|---|---|---|
248251
| 2026 Q3 | **Passing** (67 criteria) | Enroll project on [bestpractices.dev](https://www.bestpractices.dev/). Address all `MUST` items: public version-controlled source ✓, distinct contributing/security/code-of-conduct docs ✓ (already present), public bug tracker ✓, OSS license (Apache-2.0) ✓, build reproducibility documentation, automated test suite documented, public release notes per version, secure communication for vulnerability reports (private maintainer mailbox), warn on common cryptographic mistakes, vulnerability response policy with SLA, no public exposure of sensitive data in commits/issues. |
249252
| 2026 Q4 | **Silver** (55 additional criteria) | DCO or CLA documented and enforced, two-person review for substantive changes (already required), branch protection on all release branches, automated `golangci-lint` + `gosec` on every PR (extend coverage), documented coding standards, documented release-signing process, signed Git tags for releases, security policy with vulnerability disclosure timeline, README references security policy, contribution metadata documented (size, scope, review). |
250253
| 2027 Q2 | **Gold** (23 additional criteria) | Documented secure-design / threat model, fuzzing for critical components (blockstor, custom-scheduler, controllers), public SAST findings management, dynamic analysis (`go vet -race`, kube-conformance), CI-driven dependency-license check (FOSSA/ScanCode), reproducible builds for container images, branch protection includes required signed commits where supported. |
251254

252-
#### 3.2 OSPS Baseline (Open Source Project Security Baseline)
255+
#### Track 3.2 — OSPS Baseline (Open Source Project Security Baseline)
253256

254-
The new (Feb 2026) maturity-model framework that is replacing "Gold-only"
257+
The maturity-model framework — launched Feb 2025, current version dated
258+
2026-02 — that is replacing "Gold-only"
255259
thinking. Has three levels organized by project maturity. Cozystack already
256260
qualifies for L3 by user-base; the work is bringing controls up to spec.
257261

@@ -275,10 +279,11 @@ The eight control families (each ID `OSPS-XX-YY`):
275279
The repository ships an `OSPS-BASELINE.md` self-assessment that maps every
276280
control to evidence and is regenerated on each release.
277281

278-
#### 3.3 OpenSSF Scorecard
282+
#### Track 3.3 — OpenSSF Scorecard
279283

280-
Automated weekly checks producing a numeric score. CNCF expects ≥ 7.0 for
281-
Incubation and ≥ 8.0 for Graduated.
284+
Automated weekly checks producing a numeric score. CNCF sets no numeric
285+
Scorecard threshold for either tier; the levels below are self-chosen targets
286+
(around ≥ 7.0 by Incubation, ≥ 8.0 toward Graduated).
282287

283288
| Quarter | Target | Concrete tasks |
284289
|---|---|---|
@@ -287,50 +292,53 @@ Incubation and ≥ 8.0 for Graduated.
287292
| 2027 Q2 | **≥ 8.0** | SAST integration, fuzzing presence, CII Best Practices score reflection. |
288293
| 2027 Q4 | **≥ 9.0** | All applicable checks pass; only systemic exceptions remain documented. |
289294

290-
#### 3.4 SLSA — Supply-chain Levels for Software Artifacts
295+
#### Track 3.4 — SLSA — Supply-chain Levels for Software Artifacts
291296

292-
Build-side integrity. CNCF Graduation expects SLSA Build L3.
297+
Build-side integrity, tracked against the current SLSA v1.2 specification
298+
(Build track). SLSA is not a stated CNCF graduation requirement; Build L3 is a
299+
self-chosen aspirational target.
293300

294301
| Quarter | Target | Concrete tasks |
295302
|---|---|---|
296303
| 2026 Q3 | **Build L1** | Provenance generation for every release artifact (container images, Helm charts, binaries). Publish as `.intoto.jsonl` next to releases. |
297304
| 2026 Q4 | **Build L2** | Hosted-build platform (GitHub Actions OIDC + slsa-github-generator). Authenticated provenance with signed `_provenance` files. |
298305
| 2027 Q3 | **Build L3** | Hardened build platform: isolated build steps, non-falsifiable provenance, no human override of build pipeline; reusable workflows audited; secrets handled via OIDC short-lived tokens only. |
299306

300-
#### 3.5 CNCF CLOMonitor
307+
#### Track 3.5 — CNCF CLOMonitor
301308

302309
CNCF-wide automated check dashboard. Must be all-green for Incubation review.
303310

304311
| Quarter | Deliverables |
305312
|---|---|
306313
| 2026 Q3 | Verify all CLOMonitor checks. Address gaps: project metadata, governance, security policy, adopters file completeness, contributor ladder, license, code of conduct, OpenSSF badge, artifact signing, SBOM. |
307314

308-
#### 3.6 CNCF Security Self-Assessment + Third-Party Audit
315+
#### Track 3.6 — CNCF Security Self-Assessment + Third-Party Audit
309316

310317
| Quarter | Deliverables |
311318
|---|---|
312319
| 2026 Q3 | Complete the **CNCF TAG Security self-assessment** ([template](https://github.com/cncf/tag-security/blob/main/community/assessments/guide/self-assessment.md)). Publish as `SECURITY-SELF-ASSESSMENT.md` in repo. Include attack-surface diagram, trust boundaries, threat model, and known weaknesses with mitigation status. |
313320
| 2027 Q3 | Engage a **third-party audit** (e.g. Ada Logics with OSTIF funding, or NCC Group). Scope: core controllers, blockstor, custom scheduler, multi-tenancy boundaries, supply chain. Required for Graduated tier. |
314321
| 2027 Q4 | Publish audit results and remediation status. Triage findings into milestones. |
315322

316-
#### 3.7 EU Cyber Resilience Act (CRA)
323+
#### Track 3.7 — EU Cyber Resilience Act (CRA)
317324

318325
The CRA's reporting obligations apply from **11 September 2026**; full
319-
obligations from **11 December 2027**. Cozystack itself, as a non-commercial
320-
OSS project, is technically a *contributor* under CRA Article 23, not a
321-
*manufacturer*. But downstream commercial vendors who package Cozystack are
326+
obligations from **11 December 2027**. Cozystack itself, as an OSS project,
327+
falls under the *open-source software steward* regime of CRA Article 24
328+
("Obligations of open-source software stewards"), not the *manufacturer*
329+
obligations. But downstream commercial vendors who package Cozystack are
322330
manufacturers. We document the project so that downstream compliance is
323331
tractable.
324332

325333
| Quarter | Deliverables |
326334
|---|---|
327-
| 2026 Q3 | Publish a **`CRA-COMPLIANCE.md`** describing: (a) the project's status as an OSS contributor under Article 23, (b) the CVE coordinated-disclosure process aligning with CRA timelines (24h initial / 72h info / 14d final after fix or workaround for actively exploited issues), (c) SBOM availability per release. |
335+
| 2026 Q3 | Publish a **`CRA-COMPLIANCE.md`** describing: (a) the project's status as an open-source software steward under Article 24, (b) the CVE coordinated-disclosure process aligning with CRA timelines (24h initial / 72h info / 14d final after fix or workaround for actively exploited issues), (c) SBOM availability per release. |
328336
| 2026 Q3 | Adopt **CSAF VEX** for vulnerability advisories. Publish each advisory as a CSAF JSON file alongside the GHSA. |
329337
| 2026 Q4 | SBOM in **SPDX** and **CycloneDX** formats published with every release; signed with cosign. |
330338
| 2027 Q1 | Document the **shared-responsibility matrix** between Cozystack maintainers and downstream commercial vendors for incident response. |
331339
| 2027 Q4 | Verify the disclosure pipeline against CRA timeline obligations with a tabletop exercise. |
332340

333-
#### 3.8 SOC 2 (Process Readiness, not Certification)
341+
#### Track 3.8 — SOC 2 (Process Readiness, not Certification)
334342

335343
An OSS project does not get SOC 2 itself — services do. We deliver a **process
336344
evidence pack** that any commercial Cozystack distributor can use in their
@@ -342,7 +350,7 @@ own SOC 2 audit.
342350
| 2027 Q3 | **Type II evidence-collection automation** — GitHub Actions snapshot monthly evidence (permission grants, branch-protection state, release-signing logs, CVE triage decisions) to `SOC2-EVIDENCE/`. |
343351
| 2027 Q4 | Tabletop exercise with downstream Cozystack distributors to validate the evidence pack supports their audits. |
344352

345-
#### 3.9 PCI DSS v4.0.1 (Reference Architecture)
353+
#### Track 3.9 — PCI DSS v4.0.1 (Reference Architecture)
346354

347355
A `PCI-DSS.md` reference architecture for deploying Cozystack as a CDE
348356
(Cardholder Data Environment).
@@ -352,14 +360,14 @@ A `PCI-DSS.md` reference architecture for deploying Cozystack as a CDE
352360
| 2027 Q2 | Publish `reference-architectures/pci-dss-v4/` containing: network segmentation (Cilium NetworkPolicy + Kubernetes NetworkPolicy), MFA enforcement (OIDC config), audit-log architecture (Cozystack audit log + Loki + immutable retention), vulnerability-management workflow, secure-defaults documentation, key-management (External Secrets Operator + HashiCorp Vault / OpenBao), responsibility matrix. |
353361
| 2027 Q3 | Validate the reference architecture with a friendly PCI QSA review. |
354362

355-
#### 3.10 ISO/IEC 5230 (OpenChain) — License Compliance
363+
#### Track 3.10 — ISO/IEC 5230 (OpenChain) — License Compliance
356364

357365
| Quarter | Deliverables |
358366
|---|---|
359367
| 2026 Q4 | **OpenChain self-certification** — `LICENSE-COMPLIANCE.md` documenting the project's SPDX-correct license metadata, third-party license inventory (auto-generated from `go.mod` and Helm chart dependencies), and license-clearing workflow for new dependencies. |
360368
| 2027 Q1 | Automated license-policy gate in CI (`fossa`/`scancode`). |
361369

362-
#### 3.11 Internal Security Programs
370+
#### Track 3.11 — Internal Security Programs
363371

364372
**Vulnerability response.** Formalize the **Cozystack Security Response
365373
Team** with rotating on-call.
@@ -398,7 +406,7 @@ Team** with rotating on-call.
398406
- 2027 Q3: **Fuzzing** for security-sensitive components: REST parsers,
399407
CRD validators, controller reconcilers (oss-fuzz integration).
400408

401-
#### 3.12 Certifications Roll-up
409+
#### Track 3.12 — Certifications Roll-up
402410

403411
| Cert / Badge | 2026 Q3 | 2026 Q4 | 2027 Q1 | 2027 Q2 | 2027 Q3 | 2027 Q4 | 2028 Q1+ |
404412
|---|---|---|---|---|---|---|---|
@@ -588,7 +596,7 @@ documents, marketing assets, training content, and event materials.
588596

589597
| Quarter | Deliverables |
590598
|---|---|
591-
| 2026 Q3 | **Documentation Information Architecture v2** — reorganize around user journeys: *Get Started*, *Operate*, *Develop*, *Administer*, *Reference*, *Tutorials*, *Migrate*. **Versioned docs** per supported release line (current: v1.2, v1.3, v1.4-rc; future: stable / LTS / fast). |
599+
| 2026 Q3 | **Documentation Information Architecture v2** — reorganize around user journeys: *Get Started*, *Operate*, *Develop*, *Administer*, *Reference*, *Tutorials*, *Migrate*. **Versioned docs** per supported release line (current: v1.4, v1.5, v1.6-rc; future: stable / LTS / fast). |
592600
| 2026 Q3 | **Install & upgrade docs** brought to production quality for every supported host OS profile (Talos Tier-1; Ubuntu / Debian / Flatcar Tier-2). |
593601
| 2026 Q4 | **Auto-generated API reference** from CRDs and `cozystack-api` OpenAPI spec, published per release. Tested code samples — every code block in docs runs in CI against a live cluster, broken samples block release. |
594602
| 2026 Q4 | **Operator's Handbook** — production-grade runbook collection for common operations: cluster upgrades, tenant onboarding, backup restore, DR exercises, storage migration, network troubleshooting. |
@@ -705,11 +713,12 @@ Categories are defined by **specifications, not implementations**. Linux
705713
became Linux because of POSIX, LSB, FHS, and stable kernel ABIs that allowed
706714
distributions to multiply. Kubernetes became Kubernetes because of OCI,
707715
CRI, CSI, CNI, the Operator pattern, and a Conformance Program that
708-
distinguished compliant distributions from incompatible ones. Docker had a
709-
superb reference implementation but lost the runtime category because the
710-
governance over the interface (OCI/CRI) was opened to the community while
711-
the reference implementation stayed closed. The lesson is consistent: own
712-
the specification, let the ecosystem own the implementations.
716+
distinguished compliant distributions from incompatible ones. Docker actually
717+
contributed its reference implementations to the community — containerd to the
718+
CNCF and runc to the OCI — yet Docker Engine still lost the Kubernetes runtime
719+
slot, because it never implemented the CRI interface and dockershim was
720+
eventually removed. The lesson is consistent: own the specification, let the
721+
ecosystem own the implementations.
713722

714723
This section enumerates the specifications Cozystack should define and own,
715724
the specifications Cozystack should adopt and champion, the bodies it should
@@ -979,7 +988,7 @@ evolve in a direction Cozystack benefits from.
979988
| **CNI** (Container Network Interface) | Networking | Adopted via Cilium | Cilium maintainer engagement. |
980989
| **CDI** (Container Device Interface) | Device sharing | Adopted via Talos 1.13 default | Use for first-class GPU device sharing. |
981990
| **Kubernetes Gateway API** | Ingress next-gen | `gateway-api-crds` in `packages/system`; needs roll-out | Move tenant ingress to Gateway API as default by 2027 Q2. |
982-
| **MCS-API** (Multi-Cluster Services) | Cross-cluster services | Available via Cilium 1.20 | Adopt as soon as Cilium 1.20 upgrade completes. |
991+
| **MCS-API** (Multi-Cluster Services) | Cross-cluster services | Beta in Cilium since ~1.17–1.18 | Adopt once the platform's Cilium baseline reaches a release with stable MCS-API support. |
983992
| **OpenAPI 3.1** | API specs | Adopted for `cozystack-api` | Auto-publish per release (paired with Track 12.2). |
984993
| **OpenTelemetry** | Observability | Partially adopted (metrics) | Extend to traces and logs by 2027 Q1. |
985994
| **CloudEvents** | Event-driven workflows | Not adopted | Adopt for Marketplace lifecycle hooks by 2027 Q1. |
@@ -1258,8 +1267,9 @@ goal:
12581267
this document. The current Project V2 board remains the granular
12591268
issue-level source of truth for in-quarter work; this document gives the
12601269
multi-quarter view.
1261-
- Material changes to the roadmap are proposed via a CzEP (Cozystack
1262-
Enhancement Proposal) in
1270+
- The initial roadmap (this document) is ratified via a maintainer roadmap
1271+
review on this PR; thereafter, material changes to the roadmap are proposed
1272+
via a CzEP (Cozystack Enhancement Proposal) in
12631273
[cozystack/community/design-proposals](https://github.com/cozystack/community/tree/main/design-proposals).
12641274
- The document is versioned in `git` history; major revisions are tagged.
12651275

0 commit comments

Comments
 (0)