flatcar
[Tracking] Adopter Verification & Ecosystem Documentation
This issue tracks Adopter Verification and Ecosystem Documentation:
- Adopter List: The project must provide the CNCF TOC with a list of adopters using Flatcar in production (for graduation) and/or dev/test (for incubation). This will be used for TOC verification.
- TOC Verification: TOC requires a second round of interviews/verification with adopters, similar to the previous process at incubation. Reference: Flatcar in Action, ADOPTERS.md
- Ecosystem/Adoption Documentation: Documented integrations and compatibility of Flatcar with CNCF and non-CNCF projects, as outlined in the adoption portion of the graduation criteria.
Next Steps
- [ ] Plan and execute a second round of adopter interviews (production/dev/test users)
- [ ] Update and expand ADOPTERS.md with new confirmations and details
- [ ] Document integration use cases and compatibility with CNCF/non-CNCF projects (e.g., Kubernetes, Prometheus, etc.)
- [ ] Link to adoption documentation and summary on the website and repository
- [ ] Coordinate with CNCF TOC for adopter verification and feedback
References
This issue tracks all tasks and documentation needed for CNCF Graduation Adopter/Ecosystem requirements. Please update with progress, links, and notes.
Document integration use cases and compatibility with CNCF/non-CNCF projects
We can mention the Cluster API efforts (Flatcar templates, Ignition support, etc.)
Document integration use cases and compatibility with CNCF/non-CNCF projects
We can mention the Cluster API efforts (Flatcar templates, Ignition support, etc.)
good idea
https://github.com/flatcar/Flatcar/blob/main/ADOPTERS.md#requirements-to-be-listed
Does the size of adoption matter? Is there some weight to it? How many adopters/"sizes" of adoption do we need? How can we/how should we "poach" people/companies/orgs to be interviewd? If we do not gather any telemetry on people using us