Are Kubernetes Community Days limited to Kubernetes?

No! Any open source, cloud native technology is appropriate to cover at a KCD (including any combination of Kubernetes + any other CNCF project). The only requirements are that presentations not be vendor pitches. Please see the cloud native definition .

Can I call it a Cloud Native Day, Mini-KubeCon, or similar?

Sorry, but it needs to be called Kubernetes Community Day [Location] (e.g., Kubernetes Community Day Bouvet Island). There are two reasons. Kubernetes is our strongest, worldwide, brand, communicating not only cloud native technology but openness and community participation with the name. As such, the Kubernetes Community Day name is the one that the CNCF is prepared to support with our marketing and legal resources. At some point in the future this may be revisited, but not for the first two years of the program.

Can I combine a Kubernetes Community Day with another event, like DevOps Days or OpenStack Days?

No, we’re not allowing the combination at this time. Our first concern is that we are trying to build up the Kubernetes Community Days brand to have a positive and meaningful connotation, and combining events could conduse that. The other issue is that KCDs have a relatively detailed set of rules around organization, marketing, privacy policy, etc. which could have incompatibilities with other event types.

We are open to reconsidering this policy in the future, but definitely want to start out with KCDs as standalone events.

Why is CNCF mandating the use of specific tools like Eventbrite for registration, Sched for the schedule, and SM Apply for the CFP?

At launch, we want to ensure that KCDs use a set of software that CNCF staff is familiar with and can help support, and that enables KCD organizers from different cities to support each other. Additionally, we understand the privacy policies of the tools we’re using, and we’re able to ensure that each organizer in a city is on the same footing.

We acknowledge that this makes being a KCD organizer more difficult for employees of companies where they’ve already standardized on other tools. However, we think this is a worthwhile tradeoff in ensuring that all organizers have the same access and familiarity and enabling both community and CNCF support. Also, note that CNCF is paying for commercial licenses for each of these tools that cover all KCD usage.

The exception will be in places like China where the standard tools are blocked or don’t support local payment options. There, we’ll of course need to work on alternatives. CNCF is open to expanding the number of supported systems after KCDs are up and running (e.g., in 2021).

Is CNCF underwriting these events or does that fall on the organizers?

The organizers are taking on the risk for running the events.

Will CNCF host the website or does one of the organizers have to take ownership?

Organizers are responsible for creating the content, but CNCF hosts the website. All program content must be reflected on the the official CNCF-hosted page. Lots of details are in the creating website page. In particular, we don’t allow KCDs to have a separate website, because we want all changes to come through the KCD GitHub repo so that we can review changes and engage if there is any problematic content.

What corporate entity should sponsors sign a contract with?

DevOpsDays has been successful bringing on sponsors without having them sign contracts . Although we don’t forbid organizers from signing a contract (such as by having their employer as the counterparty), we recommend against it.

Why do I need a fiscal sponsor? Can I just use Stripe or Debit cards to accept payment?

Each event needs a fiscal sponsor or company that agrees to accept payments. In most cases, one of the organizer’s employers will agree to serve as a fiscal sponsor. In the future, CNCF is working on a scenario of enabling the use of Debit cards and Stripe accounts to be able to receive and distribute money.