Feature Description

Currently kcp only writes the logical cluster ID (i.e. 12rm0wrvxaskt1ui) to an audit event (except for root and system workspaces for which the canonical path is written). While this is OK in the sense that it can be used to access the logical cluster again afterwards, it makes tracing by humans much more difficult than the canonical path of the workspace (i.e. root:consumers:myworkspace).

Proposed Solution

Add a second annotation to the audit event here, like tenancy.kcp.io/workspace-path that contains the canonical workspace path.

Alternative Solutions

Overwrite the existing audit event annotation tenancy.kcp.io/workspace which currently contains the logical cluster ID to have it contain the canonical path. Not sure if this works in all scenarios or could be considered a breaking change.

Want to contribute?

• I would like to work on this issue.

Additional Context

No response