Bug: UI shows too many `ServiceManager`

[Lasserich]

Description

Currently the UI shows four ServiceManager resources while the graph only shows two.
Also in the allItems list the ServiceManager` appears four times.
There seems to be some duplicates.

Steps to reproduce

Go to any subaccount, create one ServiceManager

Expected

One servicemanager is shown

Actual

two servicemanagers are shown

[andreaskienle]

In our playground, the backend returns two ServiceManagerLists with different versions (account.btp.sap.crossplane.io/v1beta1 vs …/v1alpha1). Each list contains two ServiceManagers, resulting in a total of four ServiceManager instances.

The ServiceManagers across the two lists are almost identical (same name, timestamps, etc.), but there are also some differences: for example different apiVersion values and differences in status.atProvider fields.

The table component doesn’t do any special filtering, it simply renders what the backend returns. The graph appears to check for duplicates by name.

Questions: (@GenosseOtt)

• Could this be a glitch in our sample playground MCP? We also have some artefacts with duplicate members, which shouldn't happen.
• What is the expected behavior in this scenario? Should the UI de-duplicate by name or display all entries as-is?

kubectl get servicemanagers returns 2 items.

[GenosseOtt]

We receive the numerous resources and visualize them accorringly

lets

• add version as another column to the table
• consider version (incl apiGroup) + name + kind for grouping in Graph and tables

[n3rdc4ptn]

I checked the GQL Gateway, it does not show duplicates. It responds with the latest available APIVersion of a CRD.

{
	typeByCategory(name: "managed") {
    group
    kind
    scope
    version
  }
}