Add origin for dynamic clusters

[skoeva]

Is your feature request related to a problem? Please describe the impact that the lack of the feature requested is creating.

Following #2536, we note that there is no way to get the origin of a dynamic cluster, because this is not stored anywhere

Describe the solution you'd like

Store the origin for the dynamic cluster somewhere so that it can be displayed in the origin column on the home page

What users will benefit from this feature?

All users using Headlamp with multiple clusters

Additional context

The only info stored in the dynamic cluster metadata is the source. maybe we can extend this somehow to include the origin (plugin name)

[knrt10]

Dynamic clusters are stored in indexDB, so I don't think so adding origin here make sense. WDYT @skoeva?

[skoeva]

@knrt10 If what you're saying is that there is no way/reason to identify individual origins of each dynamic cluster, then it probably doesn't make sense to try adding this in. Is that right?

[knrt10]

yes.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale