Feature request: JSON API for upcoming KubeCon + CloudNativeCon events

[Caesarsage]

Use case

The kubernetes.io homepage shows the next few upcoming KubeCon + CloudNativeCon events. We are currently trying scrape this from the LF events calendar + individual event pages — see kubernetes/website#53519 and the fetcher script.

A JSON API would let us drop the HTML/JSON-LD scrape and would likely be useful to other projects embedding LF event info.

Proposed shape

GET /api/events?series=kubecon-cloudnativecon&status=upcoming&limit=N

Filters:

• series — selects the event family (e.g. kubecon-cloudnativecon, kubeday, cloudnativecon-day); single API surface for all LF event types
• status — upcoming | past | all
• region — optional; values we use today: North America, Europe, India, Japan, China
• limit — integer

Per-event fields we consume today:

Field	Notes
id / slug	Stable identifier (currently we key off URL, which breaks on renames)
series	Event family slug, e.g. kubecon-cloudnativecon
name	e.g. "KubeCon + CloudNativeCon Europe 2026"
start_date, end_date	ISO 8601
region	Currently parsed from the title
location.city, location.country	Some events have no venue yet — need a way to express "TBA"
location.announced	Boolean, so consumers can render "TBA" without guessing
url	Canonical event page
brand_colors	Array of hex; today we extract these from --event-color-* CSS custom properties on the event page — most fragile part of the scrape

Notes

• JSON-LD at a list endpoint (not just per-event pages) would work too.
• Brand colors as first-class fields would be the biggest win — they're currently inferred from injected CSS.
• City/country names are rendered in multiple languages downstream; stable English values are fine, translation happens on our side.

Happy to iterate on the shape if a different model fits your platform better.

[cjyabraham]

Hi @Caesarsage , thanks for the request. Can you review #1108 and let me know how it goes?