docs: bump function-kro to v0.3.0 in get-started composition#1109
Merged
Conversation
Update the YAML+CEL get-started examples to function-kro v0.3.0 across the master, v2.2, and v2.3 docs. v0.3.0 moved the function input from kro.fn.crossplane.io/v1beta1 to v1alpha1, so the composition manifests need the new apiVersion to apply against a fresh install; the kind and body schema are unchanged. https://github.com/crossplane-contrib/function-kro/releases/tag/v0.3.0 Signed-off-by: Jared Watts <jbw976@gmail.com>
✅ Deploy Preview for crossplane ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
haarchri
approved these changes
Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The YAML+CEL get-started composition aggregates a Deployment's
availableReplicasinto an integerstatus.replicas, which never resolved before function-kro v0.3.0. v0.3.0 fixes integer-typed observed fields (#68), so the example now populatesstatus.replicascorrectly.This bumps the YAML+CEL examples to v0.3.0 across the
master,v2.2, andv2.3docs, including the inputapiVersionthat v0.3.0 moved tokro.fn.crossplane.io/v1alpha1.Verified end-to-end on a fresh kind cluster (Crossplane v2.3.2 + function-kro v0.3.0): the
AppXR reachedREADY=True, the composed Deployment and Service came up, andstatus.replicasresolved to the integer2.