feature: enhance error message on not having bound the apiexport yet #112
Description
Feature Description
The scenario
- kcp is setup properly in a k8s cluster with proper workspaces
- a provider cluster exists with syncagent installed and proper publishedresource, rbac, ...
On starting the syncagent I get this error message
E1024 05:55:57.471055 1 reflector.go:158] "Unhandled Error" err="k8s.io/[email protected]/tools/cache/reflector.go:243: Failed to watch myorg.com/v1, Kind=MyService: failed to list myorg.com/v1, Kind=MyService: the server could not find the requested resource" logger="UnhandledError"
The reason for this is not in the provider cluster, everyting is fine. The problem is that no APIBinding exist in kcp yet. After ignoring the error message and creating the APIBindings in the provider and consumer workspaces everything worked fine.
Proposed Solution
For avoiding long debugging sessions to find the issue in the provider cluster it would be great to have a hint in the error message that the CRD cannot be read in the kcp workspaces (which will exist after the APIBindings are created).
Alternative Solutions
No response
Want to contribute?
- I would like to work on this issue.
Additional Context
No response