Learn Cloud Native & CNCF - How CNCF Is Run

#Introduction

After episode 2 mapped the technologies, it's time to dissect the organization that shelters them. CNCF is not just a label under a project logo — it is an organization with a clear governance structure, designed so decisions are made transparently and balanced between the interests of vendors, users, and the technical community.

This structure answers important questions: who decides which projects are accepted, who sets strategic direction, and how your voice as a user can be heard. Without understanding this structure, the way CNCF works would look like a black box.

By the end of this episode you will understand CNCF's three main pillars — the Governing Board, the TOC, and the staff — as well as how members at various levels participate in its ecosystem.

#CNCF's Organizational Structure

#The Governing Board

The Governing Board is the highest decision-making body at CNCF. It oversees the business side, budget, and strategic direction of the organization. Its members consist of representatives from member companies and elected end user representatives. Major decisions such as budget, membership, and organizational policy rest with this board.

The board meets regularly and its process is documented. This matters for transparency: decisions can't vanish without a trace, and community members can trace the reasoning behind every policy.

Within the board, voting weight is measured by membership level. Platinum companies carry more voting weight than gold or silver ones, reflecting their financial contribution to CNCF's sustainability.

This voting-weight concept sometimes draws criticism, but it reflects funding reality: organizations that finance more naturally want more influence. Balance is achieved through the presence of end user representatives and a documented process, so decisions remain accountable.

#The Technical Oversight Committee (TOC)

The Technical Oversight Committee, or TOC, is CNCF's technical pillar. Made up of around 9-11 people elected from members and the community, the TOC is responsible for technical decisions: which projects are accepted, when a project moves to incubating or graduated, and the overall technical direction of the ecosystem.

It's important to note that TOC positions are elective and periodic. This guarantees technical leadership turnover and prevents any single group from dominating CNCF's direction forever.

#Why the Separation of Roles Matters

The separation between the Governing Board and the TOC is no accident. The board handles money and business direction, while the TOC handles technical decisions. This way, commercial considerations don't directly influence technical decisions like project acceptance — and conversely, technical decisions don't automatically become business decisions.

This kind of separation of powers is common in large open source organizations. It prevents power from concentrating in a single body and ensures each type of decision is handled by the people who understand its field best.

#The Linux Foundation Staff

Behind these three pillars is the Linux Foundation staff, which runs day-to-day operations: membership administration, event organization, financial management, and legal support. CNCF has no employees of its own in the traditional sense; all operational support is provided by the Linux Foundation as its parent.

This division of roles is clean: the Governing Board sets business direction, the TOC sets technical direction, and the staff keeps the organizational wheels turning. If you're used to companies with vertical structures, this foundation-based model may feel different — and that's intentional, because it's designed for shared benefit, not for one entity's profit.

#Membership and Levels of Participation

#Platinum, Gold, and Silver

CNCF divides its members into several levels that determine the size of financial contribution and voting rights:

• Platinum members — the largest contribution with the highest voting rights on the Governing Board. Examples include Google, Microsoft, AWS, Alibaba, and Huawei.
• Gold members — a mid-level contribution with smaller voting rights.
• Silver members — a basic contribution for companies that want to support the ecosystem.

These membership levels are CNCF's main source of revenue, used to fund project infrastructure, events, and community programs.

Being a member is not just about paying dues. Member companies get voting rights, seats on various committees, and access to collaboration spaces. For companies, membership fees are often considered an investment in reputation and access to the largest container ecosystem network in the world.

#End User Members

In addition to vendors, CNCF has an end user member category for organizations that use cloud native technology without selling it. This category matters because it guarantees that the voice of users — not just sellers — is heard in CNCF governance. End users form a special community that will be explored further in episode 14.

End user membership also opens access to spaces for sharing best practices between organizations. Companies with similar problems can learn from each other without worrying that they're talking to a commercial competitor, because fellow end users are in the same position: operating the technology, not selling it.

The existence of end user membership is one of the differences that sets CNCF apart from a mere vendor association. It ensures strategic decisions take into account the real experience of people running this technology in production.

#Executive Leadership

#The Roles of Executive Director, CTO, and COO

CNCF's operations are headed by an executive team. The Executive Director leads the organization overall and is currently Jonathan Bryce. The CTO directs technical affairs and technical community relations, held by Chris Aniszczyk. There is also a COO position that manages day-to-day operations.

The executive team is the bridge between the three pillars: they carry out the Governing Board's vision, support the TOC in technical decisions, and represent CNCF to the outside world.

It's worth noting that these roles are not static. CNCF's executive structure evolves with the organization's needs, and the details of positions can always be read in CNCF's public documents. What matters for you is not the names, but the pattern: there is always a separation between business direction, technical direction, and operations.

#How Decisions Are Made

#The Flow of Strategic and Technical Decisions

Simply put, the flow works like this: business and budget proposals are discussed at the Governing Board, while technical proposals — such as accepting new projects — are discussed at the TOC. Both are supported by working groups and Technical Advisory Groups (TAGs) covered in episode 7.

Transparency is the guiding principle. TOC meetings are recorded and shared publicly, decision documents are stored in open repositories, and anyone can submit a proposal. One way to see this process firsthand is to explore the CNCF governance repository:

git clone https://github.com/cncf/toc.git
ls cncf/toc

This github.com/cncf/toc repository contains project proposals, policies, and TOC meeting notes, all open to the public. Reading the proposal history in this repository is the best way to understand how CNCF's major decisions are made — from the process, not just from the conclusions.

#Closing

Episode 3 opened CNCF's governance black box: the Governing Board that handles business, the TOC that handles technical direction, and the Linux Foundation staff that runs operations. You also understood how membership levels determine voting rights and how end users have their own place.

Key takeaways:

• CNCF is run by the Governing Board, the TOC, and the Linux Foundation staff.
• The Governing Board oversees the organization's strategic direction and budget.
• The TOC is an elective technical body of around 9-11 people.
• Platinum, gold, silver, and end user memberships determine voting weight.
• Jonathan Bryce and Chris Aniszczyk lead as Executive Director and CTO.
• The governance process is open; the cncf/toc repository can be explored by anyone.

In episode 4 we'll discuss the project lifecycle: sandbox, incubating, and graduated — how a project enters, moves up the levels, and is finally recognized as a mature project that can be relied on in production.