v0.2.1 is a patch release that focuses on issues reported by users of function-kro.

🚨 Highlights

Kubernetes Core Type Support

In previous releases running on versions of Crossplane before v2.2, function-kro could only compose resources that had Custom Resource Definitions (CRDs) — provider-managed resources like AWS VPCs, RDS instances, etc.. Native Kubernetes types such as Secrets, ConfigMaps, and Deployments could not be composed because they don't have CRDs, and the function had no way to resolve their OpenAPI schemas.

function-kro now supports composing native Kubernetes types on any version of Crossplane v2.

The function now ships with pre-compiled OpenAPI schemas for the core API groups (core/v1, apps/v1, batch/v1, rbac.authorization.k8s.io/v1, networking.k8s.io/v1, and others). You simply define a native Kubernetes resource in your ResourceGraph the same way you would any other resource — CEL expressions, readiness conditions, and all — and function-kro handles the rest transparently on all versions of Crossplane v2.

A big thank you to @jonasz-lasut for driving this feature!

What's Changed

• [Backport release-0.2] chore: remove stale patches docs and reduce upstream diff surface by @github-actions[bot] in #41
• [Backport release-0.2] chore: bump examples to use v0.2.0 by @github-actions[bot] in #43
• [Backport release-0.2] Generate core types oapi schemas by @github-actions[bot] in #47

Full Changelog: v0.2.0...release-0.2