Feature Description

Currently, https://github.com/kcp-dev/multicluster-provider accepts only a hash value for the cluster.
Which is a poor usage experience when the user has only a canonical path available (from logicalcluster.From).

We should extend multicluster-provider to accept both hash and canonical paths to resolve to cluster.

This can be done already if one claims LogicalCluster, but this elevated apibinding/export contract quite high.

Proposed Solution

We should add kcp.io/path with logicalcluster annotation to every non system apibinding (there might be some clash trying to annotate system ones) in admission (github.com/kcp-dev/kcp/pkg/admission/pathannotation/pathannotation_admission.go) so every VW could be resolved both to representations of cluster.

Extend MCR to index clusters on both values and accept them.

We should not support mixed values of hash and canonical paths.

Alternative Solutions

No response

Want to contribute?

• I would like to work on this issue.

Additional Context

No response