Enhancement: Missing XR → Kubernetes Resource Relationship Visualization in Komoplane for Crossplane v2

[anujthedevopsguy]

In Crossplane v1, when using the claim-based approach, Komoplane provides a clear and useful visualization of the relationship between composite resources (XR) and the underlying Kubernetes resources (such as Deployments, Services, Ingress, ServiceAccounts, etc.). This significantly helps engineers understand resource composition, verify synchronization, and troubleshoot issues effectively.

However, in Crossplane v2, this relationship visibility appears to be missing. The UI currently only shows the relationship between the composite resource (XR) and the Composition resource, but does not display the underlying Kubernetes resources created as part of the composition.

Komoplane should:

Display all Kubernetes resources created by a Composition for a given XR
Provide a clear relationship graph between:
XR → Composed Kubernetes Resources (Deployment, Service, Ingress, etc.)
Allow engineers to quickly verify resource state and synchronization

This feature is critical for:
Debugging Crossplane compositions
Understanding resource topology
Ensuring all dependent resources are created and healthy
Improving developer/operator experience

Without this visibility, it becomes significantly harder to operate and troubleshoot systems built using Crossplane v2.

I am attaching screenshot where komoplane is showing relationship graph between XR/claim (crossplane V1) and k8s resources.

[undera]

Can you provide me with manifests to reproduce this behavior?

[anujthedevopsguy]

Step 1: install crossplane V1
helm install crossplane \\n crossplane-stable/crossplane \\n --namespace crossplane-system \\n --version 1.14.5
Step 2: create XRD and composition.
Step 3: Install k8s provider.
step 4: create claim.
Step 5: install komoplane.
Please check the attachment. It has all required file from step 2 to step 5. Having an running k8s cluster is prerequisite.

crossplane_v1_project.zip

[undera]

You say "However, in Crossplane v2, this relationship visibility appears to be missing", but your example is for crossplane V1. Can you provide example for V2?

[anujthedevopsguy]

In this screenshot, the composite resource and its relationship with the Composition are visible, which is helpful. However, it would be more useful if the UI also displayed the underlying Kubernetes resources that are part of the composite resource.

For example, the batteries-management composite resource consists of Kubernetes resources such as Deployment, Service, ServiceAccount, and Ingress.

[undera]

That does not answer original question. Komoplane never showed resources beyond Managed Resource layer, even in V1 and before the fixes.
Do you have the example case of functionality regression?

[anujthedevopsguy]

Screenshot shared in the beginning of the thread is taken from crossplane V1 and you can see that deployment object and service object are displayed as managed resource. That's all I want in V2 also.

[undera]

Thanks for the clarification. To be precise: in v1 your Deployment/Service appeared because they were wrapped in provider-kubernetes Object managed resources — Komoplane rendered the MRs, not the underlying K8s objects. Komoplane has never descended below the MR layer.

v2 lets compositions create raw K8s resources directly, bypassing the MR layer entirely. That puts them outside Crossplane's own resource model, and discovering them would mean scanning arbitrary GVKs for ownerReferences back to the XR — slow, permission-heavy, and beyond what a Crossplane-focused tool should do.

If you want that visibility in v2, the idiomatic path is still to use provider-kubernetes so your Deployment/Service show up as MRs.