KREP-003 introduces Decorators (a.k.a Collection Watching), an extension of Collections and ExternalRefs. We extend externalRef to support watching a collection of objects, rather than just a single object.
Roadmap
Track every KREP from review to release, see what lands in each milestone, and jump straight to its proposal, issues, and authors.
The roadmap brings proposal status and release planning into one place so contributors can follow active work, understand upcoming milestones, and quickly find the GitHub threads behind each item.
Release lanes
Each release can contain multiple KREPs. Hover a release to preview them, and click it to open the configured GitHub milestone.
KREP roadmap
Search, filter, and sort by keyword, release, stage, or author.
This PR adds a KREP document for supporting cluster-scoped instance CRDs in kro. This is a design proposal only - implementation will follow in a separate PR after design review and approval. Refs: #806
KREP-013: Graph Revisions
ScheduledWhen an RGD spec changed, kro hot-swapped the compiled graph with no durable record of what ran before. That made rollback and debugging harder, and left no stable revision identity for controlled migration features. This commit adds the base revision layer described in KREP-013.
the label-migration krep provides the reasons we want to migrate the labels used by kro, and the phases in which it will happen
Add a design proposal for explicit field omission in resource templates via ${expr.omitWhen(value)}.
Relates #827 Relates #822
KREP-006: Propagation Control
ScheduledKREP-006 introduces propagateWhen, a per-resource mechanism to conditionally gate mutation as changes propagate through the graph. Both propagateWhen and readyWhen are complementary and bookend when mutation for a node in the graph can start and is considered complete.
Introduces declarative resource collections to KRO, enabling dynamic creation of multiple resources based on runtime data. This addresses the fundamental limitation where each RGD resource block could only create a single Kubernetes resource, requiring static definition of all resources at design time.
🚀
Integrate KRO with the Kubernetes autoscaling ecosystem by exposing the Scale subresource on RGDs, enabling kubectl scale, HPA, and external autoscalers like keda.
- Release
- Not yet scheduled
- Authors
- Proposal PR
- #866