docs: add KubeCon EU 2026 recap blog post#1359
Conversation
Signed-off-by: Jonathan Norris <[email protected]>
✅ Deploy Preview for openfeature ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a blog post recapping OpenFeature's participation in KubeCon EU 2026, covering sessions, booth activities, and detailed summaries of community discussions on topics like experimentation, OFREP, and AI. The review feedback suggests correcting an inconsistent image path in the front matter and adding an "Action items" subsection to the AI Workflow Integrations section to maintain structural consistency with other discussion summaries.
| categories: ['OpenFeature', 'KubeCon', 'Feature Flags', 'CloudNative'] | ||
| slug: 'kubecon-eu-2026-recap' | ||
| authors: ['jonathannorris'] | ||
| image: /img/blog/2026-03-19-kubecon-eu-26/kubecon-eu-26.png |
There was a problem hiding this comment.
The image path in the front matter (/img/blog/2026-03-19-kubecon-eu-26/kubecon-eu-26.png) uses a different directory structure than the inline images within the post (e.g., /img/blog/2026-03-28-kubecon-eu-26-recap/maintainer-update.jpeg). For consistency and to avoid potential broken links, it's recommended to place all images related to this blog post in a single, consistent directory, ideally one that matches the blog post's date or slug. Please update the path to reflect the correct directory.
| image: /img/blog/2026-03-19-kubecon-eu-26/kubecon-eu-26.png | |
| image: /img/blog/2026-03-28-kubecon-eu-26-recap/kubecon-eu-26.png |
| ### AI Workflow Integrations | ||
|
|
||
| The AI discussion explored how OpenFeature can better serve AI application developers and how the project itself can leverage AI tooling. | ||
|
|
||
| **OpenFeature for AI developers:** | ||
|
|
||
| - **MCP and Skills:** The OpenFeature MCP server and related tooling can help AI application developers work with feature flags more naturally. The group discussed how to make these tools more discoverable and useful. | ||
|
|
||
| - **Experimentation for AI workflows:** How can developers use OpenFeature's experimentation capabilities to tweak models and manage AI workflow rollouts? This ties back to the experimentation discussion. | ||
|
|
||
| - **Standards for flag creation:** Can we define a standard way for AI tools to create and manage feature flags? This would enable tighter integration with AI-assisted development workflows. | ||
|
|
||
| **OpenFeature using AI:** | ||
|
|
||
| - Engage with the community to understand where AI tooling (e.g. write permissions, automated flag management) can add value to the project itself. | ||
| - Validate that the community sees value in these directions before investing heavily. |
There was a problem hiding this comment.
The 'AI Workflow Integrations' section lacks an 'Action items' subsection, which is present in other discussion topics like 'Experimentation', 'OFREP', 'flagd', and 'OTel Observability'. For consistency in the blog post's structure, please add an 'Action items' section here, or clarify why it's intentionally omitted.
| title: "KubeCon EU 2026 Recap: In-Person Discussions and What's Next" | ||
| description: 'A recap of OpenFeature at KubeCon EU 2026 in Amsterdam. Sessions, booth conversations, and summaries from our in-person community discussions on experimentation, OFREP, flagd, AI workflows, and more.' | ||
| date: 2026-03-28 | ||
| categories: ['OpenFeature', 'KubeCon', 'Feature Flags', 'CloudNative'] |
There was a problem hiding this comment.
Some posts are using tags. Let's keep doing it.
| categories: ['OpenFeature', 'KubeCon', 'Feature Flags', 'CloudNative'] | |
| categories: ['OpenFeature', 'KubeCon', 'Feature Flags', 'CloudNative'] | |
| tags: [kubecon, cncf, session, talk, booth] |
|
|
||
| OpenFeature had three sessions on the schedule this year: | ||
|
|
||
| - [**Building Secure Package Pipelines**](https://sched.co/2EWfG): Andre Silva walked through how to build a secure open-source package pipeline at the Maintainer Summit, covering OIDC authentication, SBOM generation, cryptographic attestations, and automated releases. |
There was a problem hiding this comment.
| - [**Building Secure Package Pipelines**](https://sched.co/2EWfG): Andre Silva walked through how to build a secure open-source package pipeline at the Maintainer Summit, covering OIDC authentication, SBOM generation, cryptographic attestations, and automated releases. | |
| - [**Building Secure Package Pipelines**](https://sched.co/2EWfG): André Silva walked through how to build a secure open-source package pipeline at the Maintainer Summit, covering OIDC authentication, SBOM generation, cryptographic attestations, and automated releases. |
|
|
||
| - [**Building Secure Package Pipelines**](https://sched.co/2EWfG): Andre Silva walked through how to build a secure open-source package pipeline at the Maintainer Summit, covering OIDC authentication, SBOM generation, cryptographic attestations, and automated releases. | ||
|
|
||
| - [**OpenFeature Update From the Maintainers**](https://sched.co/2EF4j): Lukas Reining, Andre Silva, Thomas Poignant, and Alexandra Oberaigner shared updates on the MCP server, the OpenFeature GitHub Action for flag cleanup, and the stable release of OFREP. The session was part of the Maintainer Track on Wednesday. |
There was a problem hiding this comment.
| - [**OpenFeature Update From the Maintainers**](https://sched.co/2EF4j): Lukas Reining, Andre Silva, Thomas Poignant, and Alexandra Oberaigner shared updates on the MCP server, the OpenFeature GitHub Action for flag cleanup, and the stable release of OFREP. The session was part of the Maintainer Track on Wednesday. | |
| - [**OpenFeature Update From the Maintainers**](https://sched.co/2EF4j): Lukas Reining, André Silva, Thomas Poignant, and Alexandra Oberaigner shared updates on the MCP server, the OpenFeature GitHub Action for flag cleanup, and the stable release of OFREP. The session was part of the Maintainer Track on Wednesday. |
| - Engage with the community to understand where AI tooling (e.g. write permissions, automated flag management) can add value to the project itself. | ||
| - Validate that the community sees value in these directions before investing heavily. | ||
|
|
||
| ### Expanding the TC |
There was a problem hiding this comment.
| ### Expanding the TC | |
| ### Expanding the Technical Committee |
|
|
||
| ### Expanding the TC | ||
|
|
||
| The group discussed growing the Technical Committee to ensure broader representation and sustainable governance. |
There was a problem hiding this comment.
| The group discussed growing the Technical Committee to ensure broader representation and sustainable governance. | |
| The group discussed growing the Technical Committee (TC) to ensure broader representation and sustainable governance. |
lukas-reining
left a comment
lukas-reining
left a comment
There was a problem hiding this comment.
Love it, thanks @jonathannorris!
|
|
||
| - **Standardized context for experimentation:** Multiple participants identified that having only a targeting key is limiting. There may be a need for well-understood metadata fields (browser, geo, device type) similar to semantic conventions in OpenTelemetry, so systems can map these consistently. | ||
|
|
||
| - **Evaluation metrics in the SDK:** There was interest in having the SDK produce basic evaluation metrics (e.g. per flag key, by targeting reason, unique targeting keys) that analytics vendors could consume. This could be an official hook we publish rather than new API surface, since it's buildable with hooks today. |
There was a problem hiding this comment.
I think it is relevant to mention the OTEL SemConv here that we want to add them to?
This has an overlap with the down mentioned observability part.
|
|
||
| **Action items:** | ||
|
|
||
| - Start a SIG focused on SDK telemetry coverage |
There was a problem hiding this comment.
We do not want to add a new SIG, we already have the FF SemConv SIG that this falls under.
There was a problem hiding this comment.
3 participants
Summary