Add test that verifies multi-cluster behavior

[ncdc]

• Get an ObjectKey with cluster + name
• Get an ObjectKey with cluster + namespace + name
• List all cluster-scoped things in 1 logical cluster vs. another (make sure they're distinct)
• List all namespace-scoped things in 1 logical cluster vs. another (make sure they're distinct)
• Create works
• Update works
• Patch works
• Delete works

[stevekuznetsov]

kcp-dev/controller-runtime-example#19 verifies that the controllers function, and the controllers use the above bullets to do their job, so indirectly that PR closes this out :) Having tests here would be good, though.

[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.