example for resolving a logical cluster to a workspace path

[embik]

We want to build a simple snippet (a one file main.go) that allows to resolve a logical cluster ID to a workspace path. For that, we need to fetch the respective LogicalCluster object and extract the kcp.io/path annotation value and return it.

Important: This snippet has to work against a virtual workspace (that claims LogicalClusters) but also against kcp directly, e.g. when run as system:masters (or as someone with sufficient permissions in that respective logical cluster).

[mirzakopic]

This is more something that should be in the documentation. For new starters , like Mirza :)

[kcp-ci-bot]

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[embik]

/remove-lifecycle stale

[xrstf]

Important: This snippet has to work against a virtual workspace (that claims LogicalClusters) but also against kcp directly, e.g. when run as system:masters (or as someone with sufficient permissions in that respective logical cluster).

Please explain this further. When the URL points to a virtual workspace, it logically does not point to a specific logicalcluster, so the question of "which logicalcluster does this virtual workspace URL point to?" seems like a contradiction to me.