Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add endpoint to retrieve resources by resourceIdentifier #12044

Open
lahabana opened this issue Nov 14, 2024 · 0 comments
Open

Add endpoint to retrieve resources by resourceIdentifier #12044

lahabana opened this issue Nov 14, 2024 · 0 comments
Labels
kind/design Design doc or related kind/feature New feature triage/pending This issue will be looked at on the next triage meeting

Comments

@lahabana
Copy link
Contributor

lahabana commented Nov 14, 2024

Description

We now have a systematic resourceIdentifier for everything.

There's a hash that should be computed from the resource Identifier. Is there a systematic way to compute the hash from a set of labels?

So could we have a new endpoint:

/meshes/<mesh>/<resourceType>/_resourceIdentifier/zones/<zoneName>/namespaces/<namespace>/name/<displayName>

These would always return the same as:

/meshes/<mesh>/<resourceType>/<hashedName>

This should be a MADR and this MADR should define:

  • resourceIdentifier
  • hashing algorithm from resourceIdentifier to resourceName
  • new api endpoint and how it should be implemented

This endpoint would enable the GUI to map from XDS config to resources and to hide altogether resourceNames to only rely on resourceIdentifier everywhere.

xref: kumahq/kuma-gui#2848

@lahabana lahabana added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature kind/design Design doc or related labels Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/design Design doc or related kind/feature New feature triage/pending This issue will be looked at on the next triage meeting
Projects
None yet
Development

No branches or pull requests

1 participant