Matching controller-runtime & kcp

[fgiloux]

We need an easy way to match a controller-runtime version with a kcp release.
Looking at go.mod is cumbersome.
Ideally we would either have a branch or tag of kcp version of controller-runtime that matches a kcp release branch/tag.

[stevekuznetsov]

After e.g. APIExport virtual workspace is stable (ish), the version requirements will be very loose, right?

[ncdc]

It's mostly about lining up kcp-dev/apimachinery and kcp-dev/logicalcluster. apimachinery is still a bit of a moving target (at times), but logicalcluster can just be go get github.com/kcp-dev/logicalcluster/v2@latest.

[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