Call For Proposals (CFP)

KubeDay events connect international and local experts in global cities with adopters, developers, and practitioners to promote face-to-face collaboration and deliver rich educational experiences. The new event series is hosted by CNCF and targeted toward specific geographical regions experiencing community expansion and interest. 

Engage with the leaders of Kubernetes and other CNCF-hosted projects as we set the direction for the cloud native ecosystem. KubeDay will have both a beginner and an advanced track; about half of the speakers are international experts and half are from the local area.

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

What’s New?

After taking feedback from the community, we have expanded and consolidated tracks to optimize the attendee and submitter experience. Below are the most recent updates:

• Cloud Native Novice = Combined 101 Track and Student tracks
• SDLC (Software Development Lifecycle) = Combined Application Delivery and CI/CD tracks (includes Application Development)
• Platform Engineering = Combined Open Interfaces + Interoperability and Customizing + Extending Kubernetes tracks
• Operations + Performance = Renamed Reliability + Operational Continuity track
• Security = Combined Security + Identity, GRC, Multi-tenancy, and Runtime Performance + Constrained Environments tracks
• AI/ML + Data Processing + Storage = Combined Machine Learning + Data and Storage tracks
• Networking + Edge + Telco = Renamed the former I/O: Networking track (moved Storage topics to AI/ML + Data Processing + Storage track)
• Service Mesh = No change
• Observability = No change
• Emerging + Advanced Concepts = Renamed Research + Academia + HPC + Advanced Concepts track
• Cloud Native Experience = Combined Business Value, Lightning Talks and Community tracks. Newly added topics: Start Up and Misadventures.

New Topic Descriptions

• Cloud Native Novice – Content best suited for individuals who are new to Cloud Native and relevant to those in early career including Students. This covers foundational concepts across multiple domains through introductory presentations. Attendees to these presentations can expect to learn core cloud native networking concepts, managing storage for containerized workloads, understanding initial security activities for cloud native architectures, developing cloud native applications, how to start contributing to cloud native communities, and so much more.
• SDLC (Software Development Lifecycle) – This track focuses on application development, continuous integration and deployment. For developers building scalable and resilient applications with event-driven design, polyglot tooling, asynchronous communication, migrating legacy systems, and more. Gain insights into tools, runtime and techniques for service discovery, inter-service communication, data consistency, serverless designs, developer tools for Kubernetes, optimizing resource footprint and more. For operations and deployment, areas such as CI/CD pipelines and integrations, container builds, packaging, and delivery of cloud native applications to deployment environments. Attendees to these presentations can expect to learn elements of the SDLC including developing cloud native applications, and balancing integrations with existing software development methodologies.
• Platform Engineering – Content that covers building a platform using cloud native projects, customizing & extending cloud native projects, automating infrastructure operations, and increasing the velocity of self-service tool chains and workflows for cloud native developers. Attendees to these presentations can expect to learn about developer platforms and integrations to improve the cloud native development experience. Platform Engineering is designed to focus on the underlying components that enable SDLC.
• Operations + Performance – Content that covers operationalizing cloud native projects and technologies, improving performance and reliability of cloud native architectures, and topics that address runtime or “Day 2” challenges and learnings. This session would be of interest to attendees tasked with administering, maintaining and operating cloud-native technologies, especially administrators, SREs and DevOps folks. Attendees can expect to build expertise in areas such as autoscaling, high availability, performance optimization, operators, and reliability of cloud-native clusters.
• Security – Content that covers the security specific aspects of cloud native from detections to threat modeling, security education, identity and credential management, multi-tenancy, confidential computing, vulnerability management in cloud native, and other topics. Attendees to these presentations can expect to learn tactics and techniques in defending and designing cloud native architecture secure from attacks at all portions of the architecture and SDLC, managing credentials and identities, zero trust concepts and tooling, supply chain considerations, and learn from security audits of projects or incident post-mortems.
• ML/AI + Data Processing + Storage – Content that covers managing data models and data streaming in cloud native, novel uses of machine learning in cloud native workloads or infrastructure, and storage functions, techniques and challenges. Attendees to these presentations can expect to learn about how containerized databases can be used, MLOps and AIOps in cloud native architectures, volume provisioning, availability and scalability of storage systems, GPU utilization with Kubernetes, and more.
• Networking + Edge + Telco – Content that covers networking in cloud native environments, including topics such as load balancing, service discovery, network security, and network automation. This track also covers edge computing and telco use cases for cloud native technologies, including cloud native network functions and virtual network functions. Attendees can expect to learn about the latest networking technologies and trends, as well as best practices for deploying and managing cloud native networking infrastructure. Layer 4/7 service meshes should submit to the Service Mesh track instead.
• Service Mesh – Content that covers service mesh technologies and best practices for deploying and managing service mesh in cloud native environments. This track covers OSI Layer 4/7 service meshes in microservices architectures. Attendees can expect to learn about the benefits and challenges of service mesh, how to deploy and configure service mesh, and best practices for managing service mesh in production environments.
• Observability – Content that covers methodologies and projects for instrumenting, collecting, processing, storing, querying, curating, and correlating metrics, logging/events, trace spans, and general observational profiling of workloads. Attendees to these presentations can expect to learn good practices for meaningful alerting, queries, and operational dashboards, tooling and interoperability for observability challenges, and how to manage alerting rules definitions, thresholds and policies.
• Emerging + Advanced – Content that covers cloud native research & academia, emerging technologies, high performance computing for specialized workloads, and highly advanced cloud native computing concepts. Cloud native research and academic papers are welcome to be presented within this track alongside very early stage technical concepts, proof of concept projects, advancement of research computing, and highly specialized advanced or niche topics. Attendees interested in the latest advancements in cloud-native technology(the underlying needs associated with sustaining research and academic workloads on cloud native infrastructure, deploying and managing computationally intensive workloads, and highly advanced or in depth technical content relating to cloud native) will likely be drawn to this track.
• Cloud Native Experience – Content that deals with all the following aspects of the cloud native experience such as building & supporting a cloud native community, the business value of CNCF technologies, lightning talks, building Cloud Native startups, and openly sharing our cloud native misadventures. Attendees can expect to gain a range of insights and knowledge about building communities, the value of CNCF technologies, and learn from misadventures shared by the community.

• Session Presentation: 30 minutes, 1-2 speakers presenting on a topic
• Panel Discussion: 30 minutes of discussion amongst 3 to 5 speakers

• All speakers are required to adhere to our code of conduct. We also highly recommend that speakers take our online Inclusive Speaker Orientation Course.
• Panel submissions must include the names of all participants in the initial submission to be considered. In an effort to promote speaker diversity, CNCF does not accept submissions with all-male panels, and speakers must not all be from the same company.
• Complimentary Passes For Speakers – One complimentary pass for the event will be provided for each accepted speaker.
• Avoid sales or marketing pitches and discussing unlicensed or potentially closed-source technologies when preparing your proposal; these talks 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.
• CNCF will not select submissions that have already been presented at a previous Linux Foundation event within the past year. If your submission is similar to a previous talk, please explain how this version differs.
• You are allowed to be listed as a speaker on a maximum of two proposals submitted to the CFP, regardless of the format. If you are listed on more than two, we will contact you to remove yourself from any additional proposals.
• You may only be selected to speak on one panel and one non-panel session per event.
• All accepted speakers are required to submit their slides prior to the event.

While it is not our intention to provide you with strict instructions on how to prepare your proposal, we hope you will take a moment to review the following guidelines that we have put together to help you prepare the best submission possible. To get started, here are three things that you should consider before submitting your proposal:

1. What are you hoping to get from your presentation?
2. What do you expect the audience to gain from your presentation?
3. How will your presentation help better the ecosystem?

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.

Writing Your Proposal

Your session title will be the main point of reference for attendees to decide if they want to attend your talk, so choose it carefully. The title should accurately reflect the content of your talk and comply with The Linux Foundation’s Inclusive Language Initiative. Please use title case when inputting your title.

In the session description, make the most of your opportunity to pitch your talk to the program committee by emphasizing its problem, contribution, and relevance. Don’t forget technical details, but keep the big picture in mind. Your proposal’s description should be focused, detailed, and comply with The Linux Foundation’s Inclusive Language Initiative. It will appear on the website schedule if accepted, so ensure it’s error-free, uses full sentences, and written in the third person. This description can make or break an attendee’s decision to attend your talk, so provide enough information to aid their choice, and be concise. The competition for presentation slots is high, so a well-crafted, engaging abstract will improve your chances of acceptance.

Use this opportunity to elaborate on why your presentation is important and why attendees should care. Explain how your content will benefit the ecosystem or share any other relevant information with the co-chairs and program committee. We understand that this can be a challenging question to answer, but like the abstract, the relevance of your presentation is crucial, and it’s as significant as the content in determining acceptance.

Please indicate whether your submission is a case study. In other words, is your submission a report of an organization’s implementation of something, such as a practice, a product, a system, a service, or combination thereof? The case study can be thought of as a real-world test of how the implementation works, and how well it works.

If you have presented this talk before within the past year at a CNCF or Linux Foundation event, please explain the significant differences between that presentation and the one you are proposing in your session description.

Please list all CNCF-hosted graduated, incubating, or sandbox software(s) as well as all open source projects that your presentation will be focused on if applicable.

Since the Program Committee reviews numerous proposals, additional resources can assist in assessing a speaker’s proficiency and presentation skills. Please provide a video or audio recording of a previous talk you have given. If you do not have any prior recordings of your talk, you may create a brief YouTube video of yourself speaking for a few minutes.

How to Give a Great Talk

We want to make sure submitters receive resources to help put together a great submission and if accepted, give the best presentation possible. To help with this, we recommend viewing seasoned speaker Dawn Foster’s in-depth talk: Getting Over Your Imposter Syndrome to Become a Conference Speaker – Dawn Foster, VMware

Have More Questions? 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 and we strongly encourage first-time speakers to submit talks for our events. In the instance that you aren’t sure about your abstract, reach out to us and we will be more than happy to work with you on your proposal.

First time using Sessionize?

Sessionize is a cloud-based event content management software designed to be intuitive and user-friendly. If you need guidance, please review how to submit your session for an event to see step-by-step instructions and helpful screenshots.

Submitting on behalf of somebody else?

While speakers ordinarily submit their sessions themselves, it’s also common for them to have someone else do it in their name. Submitters can choose to submit as someone else and must fill out the necessary speaker fields, but the session submission process is otherwise identical to when the session is submitted by the speaker themselves.

Example title

OCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes

Example Description

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.

Example Benefits to the ecosystem

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.

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

CNCF and its project communities are dedicated to providing a harassment-free experience for participants at our events. All submitters are required to abide by our Code of Conduct.

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