You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit bc9c567
Browse filesBrowse the repository at this point in the historyBrowse files
- Grafana dashboard with SLA for each service (#1262) — rescheduled to
162
164
Q3 2026.
163
-
- API Gateway support (#1265) — rescheduled to Q3 2026.
165
+
- API Gateway support (#1265) — closed.
164
166
- Distroless images (#1261) — Q3 2026.
165
167
- Automated platform updates (#1266) — Q3 2026.
166
168
@@ -206,7 +208,7 @@ contract.
206
208
207
209
| Quarter | Deliverables |
208
210
|---|---|
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. |
210
212
| 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. |
211
213
| 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. |
212
214
| 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.
235
237
Incubation, then Graduated, and supports downstream commercial users in
236
238
audited environments. **This is the largest single track in the roadmap.**
237
239
238
-
Cozystack's security work is structured around eight external frameworks plus
240
+
Cozystack's security work is structured around ten external frameworks plus
239
241
one internal program. Each is treated as a sub-project with concrete tasks.
240
242
241
-
#### 3.1 OpenSSF Best Practices Badge (Metal series)
243
+
#### Track 3.1 — OpenSSF Best Practices Badge (Metal series)
242
244
243
245
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.
245
248
246
249
| Quarter | Target | Concrete tasks |
247
250
|---|---|---|
248
251
| 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. |
249
252
| 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). |
250
253
| 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. |
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.
293
300
294
301
| Quarter | Target | Concrete tasks |
295
302
|---|---|---|
296
303
| 2026 Q3 |**Build L1**| Provenance generation for every release artifact (container images, Helm charts, binaries). Publish as `.intoto.jsonl` next to releases. |
297
304
| 2026 Q4 |**Build L2**| Hosted-build platform (GitHub Actions OIDC + slsa-github-generator). Authenticated provenance with signed `_provenance` files. |
298
305
| 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. |
299
306
300
-
#### 3.5 CNCF CLOMonitor
307
+
#### Track 3.5 — CNCF CLOMonitor
301
308
302
309
CNCF-wide automated check dashboard. Must be all-green for Incubation review.
| 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. |
313
320
| 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. |
314
321
| 2027 Q4 | Publish audit results and remediation status. Triage findings into milestones. |
315
322
316
-
#### 3.7 EU Cyber Resilience Act (CRA)
323
+
#### Track 3.7 — EU Cyber Resilience Act (CRA)
317
324
318
325
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
322
330
manufacturers. We document the project so that downstream compliance is
323
331
tractable.
324
332
325
333
| Quarter | Deliverables |
326
334
|---|---|
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. |
328
336
| 2026 Q3 | Adopt **CSAF VEX** for vulnerability advisories. Publish each advisory as a CSAF JSON file alongside the GHSA. |
329
337
| 2026 Q4 | SBOM in **SPDX** and **CycloneDX** formats published with every release; signed with cosign. |
330
338
| 2027 Q1 | Document the **shared-responsibility matrix** between Cozystack maintainers and downstream commercial vendors for incident response. |
331
339
| 2027 Q4 | Verify the disclosure pipeline against CRA timeline obligations with a tabletop exercise. |
332
340
333
-
#### 3.8 SOC 2 (Process Readiness, not Certification)
341
+
#### Track 3.8 — SOC 2 (Process Readiness, not Certification)
334
342
335
343
An OSS project does not get SOC 2 itself — services do. We deliver a **process
336
344
evidence pack** that any commercial Cozystack distributor can use in their
| 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. |
360
368
| 2027 Q1 | Automated license-policy gate in CI (`fossa`/`scancode`). |
361
369
362
-
#### 3.11 Internal Security Programs
370
+
#### Track 3.11 — Internal Security Programs
363
371
364
372
**Vulnerability response.** Formalize the **Cozystack Security Response
365
373
Team** with rotating on-call.
@@ -398,7 +406,7 @@ Team** with rotating on-call.
398
406
- 2027 Q3: **Fuzzing** for security-sensitive components: REST parsers,
@@ -588,7 +596,7 @@ documents, marketing assets, training content, and event materials.
588
596
589
597
| Quarter | Deliverables |
590
598
|---|---|
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). |
592
600
| 2026 Q3 |**Install & upgrade docs** brought to production quality for every supported host OS profile (Talos Tier-1; Ubuntu / Debian / Flatcar Tier-2). |
593
601
| 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. |
594
602
| 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
705
713
became Linux because of POSIX, LSB, FHS, and stable kernel ABIs that allowed
706
714
distributions to multiply. Kubernetes became Kubernetes because of OCI,
707
715
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.
713
722
714
723
This section enumerates the specifications Cozystack should define and own,
715
724
the specifications Cozystack should adopt and champion, the bodies it should
@@ -979,7 +988,7 @@ evolve in a direction Cozystack benefits from.
|**CDI** (Container Device Interface) | Device sharing | Adopted via Talos 1.13 default | Use for first-class GPU device sharing. |
981
990
|**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. |
983
992
|**OpenAPI 3.1**| API specs | Adopted for `cozystack-api`| Auto-publish per release (paired with Track 12.2). |
984
993
|**OpenTelemetry**| Observability | Partially adopted (metrics) | Extend to traces and logs by 2027 Q1. |
985
994
|**CloudEvents**| Event-driven workflows | Not adopted | Adopt for Marketplace lifecycle hooks by 2027 Q1. |
@@ -1258,8 +1267,9 @@ goal:
1258
1267
this document. The current Project V2 board remains the granular
1259
1268
issue-level source of truth for in-quarter work; this document gives the
1260
1269
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
0 commit comments