Cloud Native Computing Foundation

CNCF exists to make cloud-native computing an open, collaborative field rather than a collection of proprietary platforms. The foundation was established in 2015 under the Linux Foundation, initially around Kubernetes and related technologies for deploying resilient, portable applications.¹ Its scope has since expanded to include containers, orchestration, observability, networking, storage, security, runtime systems, and developer tooling. CNCF is not a cloud provider and does not prescribe one commercial architecture; its role is to host projects and communities, protect open governance, and help maintain interoperable building blocks. The term “cloud native” commonly covers loosely coupled services, declarative APIs, automation, and infrastructure designed for rapid change and elastic operation.

CNCF manages projects through a progression from sandbox to incubating to graduated status, with graduation signaling stronger maturity, governance, adoption, and technical practices rather than simple popularity.² Kubernetes is the best-known example: it automates the deployment, scaling, and management of containerized workloads across clusters.⁵ Other prominent projects address distinct layers of the stack. Prometheus provides monitoring and alerting; containerd supplies a container runtime; Envoy functions as a high-performance proxy; Helm packages Kubernetes applications; and OpenTelemetry standardizes the collection and export of traces, metrics, and logs. The CNCF landscape maps this broader ecosystem, including projects that are independent of one another and vary considerably in maturity and use case.³

CNCF combines institutional support from the Linux Foundation with community-led technical decision-making. Technical oversight is associated with the Technical Oversight Committee, while individual projects retain their own maintainers, contributor communities, release processes, and governance documents.⁴ This separation allows a project such as Kubernetes or Prometheus to evolve according to its technical community while benefiting from shared legal, financial, marketing, security, and event infrastructure. CNCF also supports working groups, end-user communities, conformance programs, training, and KubeCon + CloudNativeCon conferences. Vendors are major participants, but membership does not give a company unilateral control over a project; the foundation’s value depends on transparent contribution rules and a credible claim to vendor neutrality.

CNCF’s influence extends beyond its most visible projects and conferences. Its landscape includes observability, policy, supply-chain security, wasm runtimes, databases, workflow systems, and specialized networking tools, illustrating that cloud-native computing is an ecosystem pattern rather than a synonym for Kubernetes.³ The lifecycle also provides a home for experimental projects that may never graduate, giving contributors a public venue to test ideas without implying production readiness. CNCF-backed technical work has helped make cross-platform telemetry more consistent through OpenTelemetry and has encouraged standardized behavior through conformance efforts, including Kubernetes conformance. A further overlooked feature is the foundation’s emphasis on end users: companies that deploy the technology participate in community feedback and help identify interoperability and operational problems beyond vendor marketing claims.

Cloud native

An approach to building and operating applications using automation, declarative interfaces, distributed services, and infrastructure suited to dynamic cloud environments.

Graduated project

A CNCF project that has demonstrated stronger technical maturity, governance, community health, and adoption than sandbox or incubating projects.

Kubernetes

An open-source system for automating deployment, scaling, and management of containerized applications.

Observability

The practice of understanding a system’s internal behavior from outputs such as metrics, logs, and traces.