Skip to content
This repository has been archived by the owner on Apr 24, 2024. It is now read-only.

Controller not finding the widget resource when no apibinding created #29

Open
fgiloux opened this issue Sep 30, 2022 · 3 comments
Open
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@fgiloux
Copy link
Contributor

fgiloux commented Sep 30, 2022

It is a know issue and not directly related to the example that at least one APIBinding has first to be created for a controller to be able to watch a resource type through a virtual workspace.

As I have seen a couple of people loosing time in the troubleshooting of it in the context of simply running the controller runtime example I am proposing:

  • to have a word about it in the readme
  • to have an APIBinding manifest in the config/kcp directory that gets automatically created when the example is deployed (there is an open PR for that)
@ncdc
Copy link
Member

ncdc commented Sep 30, 2022

When we resolve kcp-dev/kcp#1183 we will be adjusting this repo to hold off on doing anything until there is a virtual workspace URL present in the APIExport's status. cc @nrb

@nrb
Copy link

nrb commented Oct 12, 2022

kcp-dev/kcp#2135 is merged now, so this fix should be present in v0.10.

@kcp-ci-bot
Copy link
Contributor

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 kcp-ci-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants