KubeCon + CloudNativeCon North America

This event has passed. Please visit the upcoming KubeCon + CloudNativeCon North America.

Call For Proposals (CFP)


The KubeCon + CloudNativeCon North America 2022 Call for Proposals (CFP) is now closed.

For any questions regarding the CFP process, please email cfp@cncf.io.

General Info + Dates to Remember

KubeCon + CloudNativeCon brings together adopters, developers, and practitioners to collaborate face-to-face. Engage with the leaders of Kubernetes, Prometheus, and other CNCF-hosted projects as we set the direction for the cloud native ecosystem.

Dates to Remember

  • CFP Opens: Monday, March 21, 2022
  • CFP Closes: Friday, June 3 at 11:59 pm PDT
  • CFP Notifications: Monday, August 1, 2022
  • Schedule Announcement: Wednesday, August 3, 2022
  • Event Dates: October 24-28, 2022

Reminder: This is a community conference — so no product and/or vendor sales pitches.

First Time Submitting? Don’t Feel Intimidated

CNCF events are an excellent way to get to know the community and share your ideas and the work that you are doing. You do not need to be a chief architect or long-time industry pundit to submit a proposal, in fact, we strongly encourage first-time speakers to submit talks for all of our events.

Our events are working conferences intended for professional networking and collaboration in the CNCF community and we work closely with our attendees, sponsors and speakers to help keep CNCF events professional, welcoming, and friendly. If you have any questions on how to submit a proposal or the event in general, please contact cfp@cncf.io.

Program Co-Chairs

Emily Fox

Emily Fox is a DevOps enthusiast, security unicorn, and advocate for Women in Technology. She promotes the cross-pollination of development and security practices. She has worked in security for over 12 years to drive a cultural change where security is unobstructive, natural, and accessible to everyone. Her technical interests include containerization, least privilege, automation, and promoting women in technology. She holds a BS in Information Systems and an MS in cybersecurity. A member of the Cloud Native Computing Foundation’s (CNCF) Technical Oversight Committee (TOC) and co-chair for KubeCon+CloudNativeCon China 2021, Europe 2022, and North America 2022, she is involved in a variety of open source communities.

Guess what? Emily is NOT A DEVELOPER – She is a Security Engineer with lots of exposure to development and sustainment.

Ricardo Rocha

Ricardo is a Computing Engineer in the CERN cloud team focusing on containerized deployments, networking, and more recently machine learning platforms. He has led for several years the internal effort to transition services and workloads to use cloud native technologies, as well as dissemination and training efforts. Ricardo got CERN to join the CNCF and is a leader of the CNCF Research User Group, as well as a CNCF TOC member. Prior to this work, Ricardo helped develop the grid computing infrastructure serving the Large Hadron Collider (LHC).

Frederick Kautz

Frederick collaborates on security and networking. He is on the SPIFFE Steering Committee, focusing on providing Zero Trust Workload Identity to compute workloads and resources. Frederick co-authored Solving the Bottom Turtle. He is a co-founder of GitBOM and maintains the reference Go implementation. He is a co-founder and maintainer of Network Service Mesh. Prior work includes creating the initial definition of Cloud-Native Network Function and initiating Red Hat Container Storage Engine.

Requirements + Considerations


  1. Any platforms or tools you are describing need to be open source.
  2. You are limited to be listed as a speaker on up to two proposals submitted to the CFP for consideration, regardless of the format. If we find that you are listed on more than two, we will contact you to remove any proposals over the limit.
  3. You may only be accepted to speak on one panel and one non-panel accepted session chosen from the CFP at KubeCon + CloudNativeCon North America.
  4. All panel submissions with 3–5 speakers are required to have at least one speaker that does not identify as a man and the speakers must not all be from the same company. The Linux Foundation does not accept submissions with all-male panels in an effort to increase speaker diversity. Additionally, panel submissions must include the names of all participants in the initial submission to be considered.
  5. We will not select a submission that has already been presented at a previous CNCF or Linux Foundation event within the last year. If your submission is very similar to a previous talk, please include information on how this version will be different.

Consider the Following as You Write Your Proposal

  1. What do you expect the audience to gain from your presentation?
  2. Why should YOU be the one to give this talk? You have a unique story. Tell it.
  3. Be prepared to explain how this fits into the CNCF and overall Open Source Ecosystem.

We definitely do not expect every presentation to have code snippets and technical deep-dives but here are two things that you should avoid when preparing your proposal because they are almost always rejected due to the fact that they take away from the integrity of our events, and are rarely well-received by conference attendees:

  1. Sales or marketing pitches
  2. Unlicensed or potentially closed-source technologies

There are plenty of ways to give a presentation about projects and technologies without focusing on company-specific efforts. Remember the things to consider that we mentioned above when writing your proposal and think of ways to make it interesting for attendees while still letting you share your experiences, educate the community about an issue, or generate interest in a project.

How to Submit Your Proposal

We have done our best to make the submission process as simple as possible. Here is what you will need to prepare:

1. Choose a submission format:

  • Solo Presentation: 35 minutes, 1 speaker presenting on a topic
  • Dual Presentation: 35 minutes, 2 speakers presenting on a topic
  • Panel Discussion: 35 minutes of discussion amongst 3 to 5 speakers, at least one speaker must not identify as a man
  • Tutorial: 90-minute, in-depth, hands-on presentation with 1–5 speakers
  • Lightning Talk:  A brief 5-minute presentation, maximum of 1 speaker

Note: Note: All submissions with 3–5 speakers are required to have at least one speaker that does not identify as a man and the speakers must not all be from the same company.

2. Choose which CNCF hosted graduated, incubating or sandbox software your presentation will be focused on :

3. Choose a topic to narrow down the focus:

  • 101content for individuals new to the conference or unfamiliar with the content of the conference
  • Application + Deliveryprojects such as Helm, Brigade, Telepresence, Buildpacks, Backstage, etc.
  • Business Valuecontent that help support and derive the business value of a CNCF project or community involvement
  • CI/CDcontent and projects that impact or assist in continuous integration and continuous deployment
  • Communitycontent, projects, and efforts around the governance, health, and prosperity in cultivating an open source community
  • Customizing + Extending Kubernetes  – projects such as KubeVirt, Volcano, CNI Genie, KUDO, Artifact Hub, Crossplane, etc.
  • Machine Learning + Datacontent and projects focused around ML and AI challenges and data management in cloud native.
  • Multi-tenancycontent and projects specifically focused around managing, securing, operating, and establishing multi-tenancy in cloud native deployments and architectures
  • I/O: Networking + Storagebased on the same technologies such as NUMA, these are mutually beneficial and fundamentally linked through north and south operational complexity. Projects such as CoreDNS, CNI, CSI, gRPC, NATS, KubeEdge, Rook, Longhorn, etc.
  • Observabilityprojects such as Fluentd, Prometheus, Jaeger, OpenTracing, OpenMetrics, Cortex, etc.
  • Open Interfaces + Interoperabilitycontent focused on multi-project solutions for common problems, interface awareness and extensibility outside of Kubernetes as well as technical use cases with corresponding solutions
  • Reliability + Operational Continuitycontent and projects that support reliability, sustainment, availability, and operations, in cloud native environments
  • Runtime Performance + Constrained Environmentscontent and projects are IOT, Edge Computing, Airgapped & on-prem, performance, runtime and serverless
  • Research + Academia + HPC + Advanced concepts – content and projects specially focused not only on new and emerging areas but also the field of research high performance computing, and academia.
  • Security + Identitycontent around creating and managing securecloud native systems as well as projects such as Notary, OPA, TUF, Falco, Parsec, SPIFFE, etc.
  • Governance + Risk + Compliance (GRC) – content around the governance, risk, compliance, and auditability of cloud native systems and the tooling and scripts to support PCI DSS, HIPAA, and other regulatory or compliance regimes.
  • Service Meshprojects such as Linkerd, SMI, Envoy, etc.
  • Student – content and topics around student and student communities in cloud native around contributions, projects, career, etc.

Note: If your presentation is a case study, please choose which topic it best associates with from the list above and then choose “yes” for the question that asks if your presentation is a case study within the form. Final tracks for the conference will be based on accepted submissions.

4. Provide a detailed and focused description with a max of 1,000 characters. This is what will be used on the online schedule if your talk is accepted.

5. Provide more in-depth information in the “Benefits to the Ecosystem” section. This is your opportunity to elaborate on your content and share any more details with the committee with a max of 1,000 characters.

6. Provide a biography for all speakers, including previous speaking experience.

7. Provide resources to enhance your proposal. These can be videos of you or your speakers presenting elsewhere, links to personal websites (including LinkedIn), links to your open source projects, or published books.

Sample Submission

Your session description will be the cornerstone of your proposal.

This is your chance to *sell* your talk to the program committee, so do your best to highlight the problem/contribution/work that you are addressing in your presentation. The technical details are still important, but the relevance of what you are presenting will help the program committee during the selection process.

This is the description that will be posted on the website schedule, so please ensure that it is in complete sentences (and not just bullet points), free of typos and that it is written in the third person (use your name instead of “I”).


OCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes – You’ve probably heard about the OCI—a standardization effort to share a common definition for container runtime, image, and image distribution. Add to that the CRI (container runtime interface) in Kubernetes—designed to abstract the container runtime from the kubelet—and you may start to wonder what all these standards and interfaces mean for you in a Kubernetes world.

As of this year, a long list of runtimes, including CNCF projects containerd and cri-o, all implement the CRI. But did you know there are quite a few others? The unique number of CRI combinations is growing, all of which use the common OCI definitions for runtime and image interoperability.

But how would you decide which container runtime is right for you? Clearly each one has tradeoffs. This talk will help describe the current landscape and give you details on the why and how of each CRI implementation available today.

Benefits to the Ecosystem

This is your chance to elaborate. Tell us how the content of your presentation will help better the ecosystem or anything you wish to share with the co-chairs and program committee. We realize that this can be a difficult question to answer, but as with the description, the relevance of your presentation is just as important as the content. Max of 1,000 characters.


It is a repeating comment across the CNCF ecosystem that the number of choices for container runtime is confusing, especially for those who are newer to our ecosystem. Even for those who many have heard the names–Docker, containerd, cri-o–even they are curious as to the reasons why there are many varied runtimes available to implement the CRI interface for Kubernetes, and what is the history that brought us to this point.

This talk helps bring clarity to the container runtime landscape, and especially shows the interesting work being done in additional isolation technologies like gVisor, AWS Firecracker, and Kata containers and why that may be of value to consider for certain security or workload constraints.

In the end, especially as we have two major runtimes as CNCF projects, this talk hopefully brings a level of insight to practitioners, developers, and operators as to why clusters may choose various runtimes and how new features in Kubernetes like RuntimeClass are making it easier to support mixed clusters that can support the needs of workloads with different isolation features or requirements.

Scoring Guidelines

To help you further understand what is considered while the program committee and co-chairs are reviewing your proposal, please review the Scoring Guidelines and Best Practices page.

Speaker Passes

All accepted speakers and panelists will receive a complimentary conference pass.

Code of Conduct

The Linux Foundation and its project communities are dedicated to providing a harassment-free experience for participants at all of our events. We encourage all submitters to review our complete Code of Conduct.

CFP Questions?

If you have any questions regarding the CFP process, please contact us at cfp@cncf.io







End User

Diversity Supporters

Media Partners