-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Status subresource returns 404 for any CR with Kind: Cluster #2811
Comments
@fabriziopandini fixed the yaml formatting for you 😄 |
So it works as long as the Kind is not Cluster? |
@ncdc - Yeah, we explicitly took the cowboys type, named it |
🤔 Might be worth adding a test case about it, could this because of the |
Yes please! |
yeah, we were suspecting probably something about path resolution and handling, either regex or not expecting cluster twice |
/unassign @s-urbaniak |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. /close |
@kcp-ci-bot: Closing this issue. In response to this:
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. |
Describe the bug
While playing around with integration between Cluster API and KCP I hit an issue where KCP returns 404 whenever we try to patch the /Status subresource on objects with Kind: Cluster.
In order to double-check the issue I have re-created the problem using wild west example and changing the Kind in it (see below)
Steps To Reproduce
Apply the following resources:
APIResourceSchema
APIExport
APIBinding (if running in a workspace different than root, adjust the path accordingly)
Sample Cluster
then run
You will get "404 page not found"
Expected Behaviour
To be able to use custom resources of Kind: Cluster
Additional Context
No response
The text was updated successfully, but these errors were encountered: