AI
The CNCF by the Numbers
The CNCF hosts 209 projects and nearly 300,000 contributors across 765 member organizations. About 135,000 people participate in the broader cloud-native community. Roughly 13,000 of them were at KubeCon that week. Membership levels matter practically: depending on tier, companies get free training credits and access to Kubernetes certifications like the CKA. Many engineers do not know their employer is already a member and miss those benefits.
Sandbox, Incubating, and Graduated: What the Levels Mean
Sandbox projects are early-stage ideas still recruiting contributors. Incubating projects have some adoption but have not yet met graduation requirements. Graduated projects must show committers from at least two organizations, documented governance, neutrality, and Linux Foundation core infrastructure best practices. Both incubating and graduated projects are considered production-ready by the CNCF. Crossplane reached graduated status recently. Archived projects are not failures; often something replaced them or maintainers stepped away.
Reading the CNCF Landscape Without Getting Lost
The landscape at landscape.cncf.io looks like hundreds of logos, but a built-in filter cuts the noise. Filtering to “graduated” shows only the projects most teams already run in production. Each logo links to live stats: contributor count, maturity level, and start date. Filtering by topic, such as observability or security, narrows it further. The speakers also noted that ask.cncf.io, built by George Castro using DOSU, answers natural-language questions about any project in the landscape.
CLO Monitor and the Projects CSV
CLO Monitor attaches a health score to every project in the landscape. Green checks pass. Red marks show gaps, including missing contributing guides or incomplete documentation. A red mark on contributing is an open invitation: Helm, one of the most widely used projects, had that gap during the demo. The downloadable projects.csv adds security audit dates, which gives engineers a concrete answer when managers require proof that a tool passed a recent audit.
Finding Your First Contribution
Most attendees in the room were end users, not yet contributors. The speakers pointed to CLO Monitor’s red marks as contribution starting points, especially documentation gaps. Sandbox projects are good targets because they need help most and the community is small enough for a new contributor to matter quickly. GitHub repos and maintainer contacts are one click away from each project page. The hallway track at KubeCon, meaning unscheduled hallway conversations, is a direct path to those maintainers.
Notable Quotes
there are 209 projects at the CNCF, which is huge. Lori · ▶ 03:33
it is a marathon, not a sprint. Yeah. It’s a marathon to get in and it’s a marathon to get out, but it’s totally worth it because of all the innovation that happens from within. Speaker · ▶ 07:32
the hallway track is really important. And if this is your first CubeCon or maybe your first conference and you don’t know what the hallway track, it literally means having conversations in the hallway. Speaker · ▶ 14:46
Key Takeaways
- The CNCF landscape filter lets you view only graduated or incubating projects instantly.
- CLO Monitor health scores show exactly where a project needs help, including documentation.
- The projects.csv download includes security audit dates, useful for compliance conversations with management.