Talk Intermediate MIT First Talk

Runtime Conditions Profiles: The Missing Contract Between Applications and Platforms

Rejected

Session Description

Applications don't run in isolation. They depend on databases, caches, and APIs that affect configuration and deployment. Platform engineers fulfill them with automation, but describing the intent - what the code needs - is still manual, making that first deployment needlessly painful.

Runtime Conditions Profiles create the missing contract. In this session, you'll get an overview of Runtime Conditions Profiles, including how profiles are generated from code and validated against extension vocabulary. You'll see how profiles can be stored as Kubernetes CRDs or surfaced through Backstage and Headlamp, while adapters provision the external resources needed to run a codebase successfully.

Most importantly, you'll learn how to use Runtime Conditions Profiles to automate the deployment of applications to your cluster using the platform you have today - no redesign or retooling needed.

Key Takeaways

Open-source review often ends with a reviewer requesting you to test the changes made in your PR locally first if not already done. This talk walks through actually doing that for a Backstage plugin that correlates Kubernetes CRDs to catalog components by git-URL identity instead of fragile labels, so a single profile tracks correctly across dev, staging, and prod clusters.

The CRD itself, RuntimeConditionsProfile, isn't hand-applied YAML it's delivered by a Kratix Promise, meaning the platform team defines it once and any cluster can request an instance on demand. That means Backstage doesn't care which cluster or which Promise pipeline produced the resource, only what codebase it describes.

We'll cover the work that goes through when a reviewer asks you to test it locally, no runnable app existed to test the plugin against, RBAC for the Promise's CRD was silently missing and a toolchain mismatch broke native builds across Node versions all fixed by standing up a real kind cluster, the Kratix Promise, and a Backstage instance from scratch.

Attendees leave with a pattern for identity-based CRD-to-entity correlation, how Kratix Promises fit into that picture and how to verify the work done for yourself

References

https://runtimeconditions.io/

https://github.com/runtimeconditions

Session Categories

Story of a FOSS project - from inception to growth

Talk License: MIT

Speakers

Akanksha Trehun Student | St Joseph Engineering College

I am a final-year Computer Science student at St Joseph Engineering College,Mangaluru,India,and an active open-source contributor and maintainer. Also I am a GSoC 2026 contributor at CircuitVerse,working on LTI 1.3 integration in a large Rails codebase,and mentors and serves as a project admin for GirlScript Summer of Code,where I experimented with agent-assisted maintenance workflows.I am also drawn to the intersection of automation,developer tooling, and the communities open source depends on.

https://github.com/magic-peach

Sumit Goyal Student | Indian Institute of Information Technology, Kota

Hi everyone, I’m Sumit Goyal, a final-year Computer Science student and an open source enthusiast.

Over the past year, I’ve had the opportunity to work with projects across the Kubernetes and open source ecosystem, including through Google Summer of Code and the CNCF LFX Mentorship program. I’ve also been contributing to and maintaining open source projects, while building a community of 1000+ new contributors where we help people take their first steps into open source.

But honestly, the part I enjoy the most is the journey itself. I like breaking unfamiliar codebases, asking “why” before “how”, and turning something that initially looks confusing into something I can understand and contribute to.

https://github.com/Itvi-1234

Reviews

Thanks for the submission. We're already saturated with k8s and infra talks this year, and this proposal felt both overly niche and disjointed (it reads clearly like an AI generated proposal). We encourage submitting simple and human-written proposals with a single clear focus, without getting into too many buzzwords or jargon for future submissions. As a result, we cannot include this session.

Reviewer #1 Rejected