CRUD operations via APIExport VW on resources claimed from root workspace with local maximum permission policy always return 403

[astefanutti]

Describe the bug

CRUD operations via APIExport VW on resources claimed from root workspace with local maximum permission policy always return 403.

Steps To Reproduce

1. Create an APIExport that claims permission on scheduling.kcp.dev/placements from the scheduling.kcp.dev APIExport in the root workspace
2. Bind that APIExport in a consumer workspace with the claim permission accepted
3. Create a placement resource via the APIExport VW API server
4. This returns 403, while any authenticated user is granted permission via the local maximum permission policy defined in the root workspace

Expected Behaviour

The local maximum permission policy should correctly apply to requests made to the APIExport VW API server.

Additional Context

No response

[ncdc]

@s-urbaniak do you have time to look at this?

[astefanutti]

@ncdc @s-urbaniak please see tentative fix in #2385.

[astefanutti]

/milestone v0.10

[sttts]

The solution IMO is incorrect.

[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

[kcp-ci-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

[kcp-ci-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kcp-ci-bot]

@kcp-ci-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.