Describe the bug
When navigating from a namespaced v2 Composite Resource (XR) to its associated Managed Resources (MR), Crossview fails to load the resource details. The UI displays an empty YAML skeleton (metadata only) and the backend returns a 500 Internal Server Error.
Even though both the XR and the MR reside in the same namespace, the link between them in the UI seems to drop the namespace context when performing the API call to fetch the Managed Resource details.
To Reproduce
Steps to reproduce the behavior:
Go to the Composite Resources tab.
Select a namespaced XR.
Under the Managed Resources section, click on one of the resources (e.g., ForwardingRule).
The YAML view is empty/incomplete.
Check backend logs: a 500 Internal Server Error is triggered by a 404 Not Found from the Kubernetes API.
The browser sends this api call:
/api/resource?apiVersion=dns.gcp.m.upbound.io%2Fv1beta1&kind=RecordSet&name=my-record-name&context=in-cluster
It should be this one:
/api/resource?apiVersion=dns.gcp.m.upbound.io%2Fv1beta1&kind=RecordSet&name=my-record-name&namespace=my-namespace&context=in-cluster
Backend log error:
2026-05-05 08:10:04.646 ERROR gin@v1.9.1/context.go:174 Failed to get resource: failed to get resource: the server could not find the requested resource
Expected behavior
Crossview should use the namespace of the parent Composite Resource to fetch the Managed Resource. The resulting API call should correctly target /apis///namespaces///.
Additional context
When accessing managed resources directly from the dedicated menu, the api call sent by the browser contains namespace and everything works well
Describe the bug
When navigating from a namespaced v2 Composite Resource (XR) to its associated Managed Resources (MR), Crossview fails to load the resource details. The UI displays an empty YAML skeleton (metadata only) and the backend returns a 500 Internal Server Error.
Even though both the XR and the MR reside in the same namespace, the link between them in the UI seems to drop the namespace context when performing the API call to fetch the Managed Resource details.
To Reproduce
Steps to reproduce the behavior:
Go to the Composite Resources tab.
Select a namespaced XR.
Under the Managed Resources section, click on one of the resources (e.g., ForwardingRule).
The YAML view is empty/incomplete.
Check backend logs: a 500 Internal Server Error is triggered by a 404 Not Found from the Kubernetes API.
The browser sends this api call:
/api/resource?apiVersion=dns.gcp.m.upbound.io%2Fv1beta1&kind=RecordSet&name=my-record-name&context=in-clusterIt should be this one:
/api/resource?apiVersion=dns.gcp.m.upbound.io%2Fv1beta1&kind=RecordSet&name=my-record-name&namespace=my-namespace&context=in-clusterBackend log error:
2026-05-05 08:10:04.646 ERROR gin@v1.9.1/context.go:174 Failed to get resource: failed to get resource: the server could not find the requested resourceExpected behavior
Crossview should use the namespace of the parent Composite Resource to fetch the Managed Resource. The resulting API call should correctly target /apis///namespaces///.
Additional context
When accessing managed resources directly from the dedicated menu, the api call sent by the browser contains namespace and everything works well