Timur Tukaev
1825a2d4b9
## What this PR does Finalizes the editorial layer of the General Technical Review ahead of filing the point-in-time snapshot for Incubation Due Diligence (cncf/toc#1916, tracked in cozystack/community#75). Resolves 13 `[maintainers: …]` markers whose answers are settled by repository or documentation evidence, corrects two inaccurate statements, pins the submission version, and assigns the previously-vacant Security Champion role. The DRAFT banner is rewritten so the remaining markers are grouped by *why* they stay open (measurement / maintainer confirmation / governance / organization action) instead of being mixed with editorial to-dos. Resolved with verified content: end-user case studies (Protofire, Cozyhr, CNCF announcement); compliance = no formal attestation (per self-assessment); API versioning = no stability policy yet, group is `v1alpha1`, tracked in #1251; deprecation communication; rollback = no runbook published; FinOps = not implemented, roadmap; known-failure-modes troubleshooting links; SBOM off by default (#2937); component retirement = GOVERNANCE.md sourcing policy, no formal retirement workflow; SLOs = adopter-defined with exposed SLIs enumerated. Corrections: - **Loosening tenant isolation** — removed the "shared/flat networking" claim; inter-tenant isolation is enforced by Cilium egress by design. Documented the opt-in policy labels that actually exist (per the tenants guide). - **Alpha/beta flagging** — removed "marked as such"; there is no per-application maturity field in `ApplicationDefinition` today. Project Version pinned to **v1.6.3** (latest stable, 2026-09-04); Date Updated 2026-09-11. Also **assigns the previously-vacant Security Champion role to @tym83** (weekly triage pass), which the GTR flagged as the genuine unmet target in the SCA section; surfacing the rotation cadence into `SECURITY.md` is the remaining governance step (CODEOWNER review). What remains open is genuine DD work, unchanged otherwise: measurements (load/scale, baseline overhead, upgrade→downgrade CI matrix), maintainer confirmations (Talos reboot, control-plane restart, CRD cleanup, circuit breaker), the `SECURITY.md` rotation/diversity surfacing, and organization actions (publish the CVE-pipeline policy docs; close the SCA write-back loop). ### Downstream repositories - [x] No downstream repository is affected by this change ### Release note ```release-note docs(gtr): finalize editorial GTR answers, correct tenant-isolation and alpha/beta wording, pin submission version to v1.6.3, assign Security Champion ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated the technical review for Cozystack 1.6.3 and its revision date. * Expanded deployment guidance for Talos, generic Linux/k3s, bring-your-own Kubernetes, and provider-specific installations. * Clarified API versioning, security, rollback, deprecation, scalability, cost management, troubleshooting, compliance, and maturity information. * Updated governance roles and voting information, including removal of the Directors role. * Documented security reporting responsibilities, scanner integration status, component updates, and recent nightly end-to-end test results. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Cozystack
Cozystack is a free and open-source platform and framework for building clouds.
Cozystack is a CNCF Sandbox project that was originally built and sponsored by Ænix.
With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
Use Cozystack to build your own cloud or provide a cost-effective development environment.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
Documentation
The documentation is located on the cozystack.io website.
Read the Getting Started section for a quick start.
If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.
Versioning
Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.
Contributions
Contributions are highly appreciated and very welcomed!
In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.
You are welcome to take on the fix yourself. Commits are used to generate the changelog, and their author will be referenced in it.
If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.
Community
You are welcome to join us in #cozystack, on either CNCF Slack (get an invite) or Kubernetes Slack (get an invite), in our Telegram group, and at our community meetings. Add them to your Google Calendar or iCal for convenience.
Project documents
| Document | What it covers |
|---|---|
| Governance | How decisions are made and who makes them |
| Contributor Ladder | How to grow from contributor to maintainer |
| Maintainers | Who maintains the project |
| Code of Conduct | What we expect of each other |
| Security Policy | Reporting a vulnerability, and which releases get fixes |
| Adopters | Who runs Cozystack in production |
| Roadmap | Where the project is going |
License
Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.
Commercial Support
A list of companies providing commercial support for this project can be found on official site.