What's Missing?
crossplane/crossplane#7339 makes a fairly significant change to how crossplane render works, which brings a few new limitations and a few new features. We should document:
- How to override the Crossplane release, image, or binary to use for rendering.
- Limitations around Docker:
- By default,
render runs the Crossplane controller image under Docker, but this can be avoided with the --crossplane-binary flag.
- Injecting or showing function pipeline context requires mounting a socket into the Crossplane docker container when using Docker mode. This does not work on Windows.
- Behavior changes since v2.2:
- Status conditions have changed as a result of using the real reconciler. More conditions are added, and they have real timestamps.
spec.resourceRefs is populated on the XR.
- With the
-x flag we now merge changes into the input XR rather than replacing the output XR's spec and metadata with those fields from the input.
What's Missing?
crossplane/crossplane#7339 makes a fairly significant change to how
crossplane renderworks, which brings a few new limitations and a few new features. We should document:renderruns the Crossplane controller image under Docker, but this can be avoided with the--crossplane-binaryflag.spec.resourceRefsis populated on the XR.-xflag we now merge changes into the input XR rather than replacing the output XR'sspecandmetadatawith those fields from the input.