CNCF Landscape
The CNCF Landscape is the Cloud Native Computing Foundation's catalog of projects and products in the cloud native ecosystem. It maps the technology space across categories like orchestration, observability, networking, storage, and security, helping teams discover and compare options.
itCloud native tools and technologies | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic - CNCF Landscape
The CNCF Landscape is a categorized map of cloud native projects and products. That sounds reassuringly like an atlas, until you notice that an atlas does not tell you where to build a bridge, how much it costs, or whether the bridge is currently on fire. The map exists to turn a large ecosystem into places where you can start asking better questions.
Begin with a requirement, which is the outcome and constraints that matter before any logo appears. Then find the capability area, category, and subcategory that describe the problem. An entry is a candidate, not a purchase order. Two entries in the same category can differ in interfaces, licenses, support, operating costs, and scope, because categories are navigation aids rather than a compatibility oath sworn beneath a very large logo wall.
The useful surprise is that landscape inclusion and CNCF project status are different signals. An entry can fit the map without being a CNCF project. A CNCF project can be Sandbox, Incubation, Graduation, or Archived, and that lifecycle stage is evidence about governance and maturity. It is not a score for the workload in front of you. The map cannot see service-level goals, regulatory duties, staff skills, contracts, or migration constraints, largely because maps are terrible at reading meeting notes.
Use the Landscape to build a long list, then reduce it with the same criteria for every candidate. Inspect official documentation, governance, release and security practices, deployment options, and support. Test a small shortlist against one scenario. Record installation work, failure behavior, resource use, integration effort, upgrade work, and removal cost. A dated decision record is the useful destination, not a screenshot with more rectangles than a sensible person requested.
Read the Intro when you need the full research method and the distinction between lifecycle and fit. Use the Slides to keep the problem-first sequence in view. Keep the Cheatsheet nearby when comparing evidence and warning signs. The Reference tab is where the map ends and the primary sources begin. That is the moment the landscape has done its job and can stop looking pleased with itself.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://github.com/cncf/landscape
Supports
- Landscape purpose as a categorized map of cloud native projects and products
- CNCF projects as one route through the broader landscape
- Listing rules and placement in one best-fit category
- Interactive filtering and sorting with project and organization metadata
- Daily generation from maintained data
- External GitHub and Crunchbase data sources and correction paths
- https://landscape.cncf.io/
Supports
- Interactive category, search, filter, and entry-detail exploration
- Current landscape presentation as of the verification date
- https://www.cncf.io/about/who-we-are/
Supports
- CNCF as part of the nonprofit Linux Foundation
- CNCF support for an open source vendor-neutral project ecosystem
- CNCF cloud native definition and example system qualities
- https://contribute.cncf.io/projects/lifecycle/
Supports
- Separate CNCF project lifecycle and evaluation process
- Sandbox, Incubation, Graduation, and Archived stage definitions
- Lifecycle stages as maturity and governance evidence
- Technical Oversight Committee role in level transitions
- https://contribute.cncf.io/community/governance/
Supports
- CNCF governance principles
- Technical Advisory Groups aligned with technical domains or common needs
- Vendor neutrality and community-driven governance
- https://contribute.cncf.io/projects/best-practices/community/vendor-neutrality/
Supports
- Vendor-neutral expectations for CNCF project communication and hosting
- Architectural decision and governance considerations
- Need for balanced project direction across organizations
- https://github.com/cncf/landscape/blob/master/landscape.yml
Supports
- Structured representation of landscape categories, subcategories, entries, statuses, and metadata
- https://www.cncf.io/reports/cncf-annual-report-2018/
Supports
- Landscape origin in November 2016 as a static image with fewer than 100 entries
- Landscape growth past 600 items by 2018
- Cloud Native Landscape 2.0 release and its interactive filters, entry details, and stateful URLs
- Cloud Native Trail Map release alongside Landscape 2.0
- https://www.cncf.io/blog/2018/03/08/introducing-the-cloud-native-landscape-2-0-interactive-edition/
Supports
- March 2018 interactive Landscape 2.0 release
- Landscape data availability in a GitHub repository
- Trail Map release as an introductory companion
- https://www.cncf.io/wp-content/uploads/2020/08/CNCF-Annual-Report-2019.pdf
Supports
- Landscape growth past 1,200 projects, products, and companies by 2019
- Addition of serverless and CNCF member landscape views
- Daily collection of GitHub, Crunchbase, market-cap, and best-practices data in the interactive landscape
- https://landscapeapp.cncf.io/cncf/guide
Supports
- Landscape Guide organization by layers, columns, and categories
- Landscape coverage of open source projects and proprietary products
- Landscape Guide publication and 2022 update timestamp
- https://www.cncf.io/blog/2022/05/18/cloud-native-maturity-model-2-0/
Supports
- Cloud Native Maturity Model launch at KubeCon 2021 to help adopters navigate the landscape and wider ecosystem
- May 2022 Cloud Native Maturity Model 2.0 update
- https://www.cncf.io/blog/2023/09/06/introducing-the-wasm-landscape/
Supports
- September 2023 CNCF Wasm Landscape launch
- Use of a dedicated landscape to chart an evolving ecosystem
- https://github.com/cncf/landscape2/releases
Supports
- Landscape2 v0.7.0 release in March 2024
- Landscape2 v1.0.0 release in May 2025
- https://www.cncf.io/reports/cto-summit-na-2022/
Supports
- Technology leaders balance standardized cloud native tools with flexibility
- Mature organizations need an agreed package rather than unrestricted tool choice
- Proof of cloud native tools and workflows through internal testing
- https://www.cncf.io/blog/2020/09/15/top-7-challenges-to-becoming-cloud-native/
Supports
- Growing landscape complexity and competing tools can overwhelm teams
- Cloud native adoption requires tools that fit organization-specific requirements and cultural change
- https://www.cncf.io/case-studies/la-redoute/
Supports
- Platform team evaluation of cloud native technologies with production readiness as a requirement
- Use of lead time, deployment frequency, change failure rate, and recovery capabilities as requirements
