Built-in Crossplane UI
Work with Crossplane in the same Kubernetes environment as your resources, events and configuration. Keep investigation close to the platform team’s operating context.
Crossplane / Built in & next
Crossplane UI is built into the Lumen workspace. Keep the abstractions your teams use connected to Kubernetes context, then follow our direction toward richer composition authoring and reusable platform workflows.
01 / Crossplane in the workspace
Work with Crossplane in the same Kubernetes environment as your resources, events and configuration. Keep investigation close to the platform team’s operating context.
Our future direction includes reusable templates, schema-aware editing and validation for platform APIs. This extends the built-in UI; it is a separate capability from current resource visibility.
02 / Platform API context
Crossplane defines platform APIs through composite resource schemas and compositions. An effective engineering workspace should make it easier to reason about those definitions and the resources they compose.
The composite resource definition describes the platform API and its schema.
The composition describes the resources and configuration that implement that API.
The resulting objects and their conditions provide evidence of what the platform is doing.
03 / Future authoring workflows
Explore templates for the capabilities application teams repeatedly need, with explicit inputs, ownership and operating assumptions.
Work toward schema-aware editing and a clearer view of composition revisions and their effect on platform APIs.
Explore render and validation workflows so changes can be examined before they reach a shared environment.
Connect authoring to repository review and planned Flux and Argo CD context rather than separating infrastructure changes from delivery.
Build around your platform
Show us the platform APIs your teams use and the composition work you want to improve. Help shape the next authoring and investigation capabilities.