-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
⚠️ RESTMapper: don't treat non-existing GroupVersions as errors #2571
Conversation
Welcome @ary1992! |
Hi @ary1992. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/hold This is in direct contrast #2424 |
WDYM ? We still need this fix right? refer #2425 (comment) . PR #2425 was closed saying it was fixed with #2472 but that is not the case. The issue is still there. |
Wasn't this issue already fixed by #2472 ? |
I don't think so |
gentle ping 🙏 @alvaroaleman |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman, ary1992 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
I guess the alternate is to handle absence of an entry in the map? Not sure if it will matter too much in practise as there isn't too much data in a group and this will only happen when requesting an absent group. |
xref: kubernetes-sigs/controller-runtime#2571 Signed-off-by: Tamal Saha <[email protected]>
xref: kubernetes-sigs/controller-runtime#2571 Signed-off-by: Tamal Saha <[email protected]>
/kind bug
This PR fixes the new RESTMapper implementation to properly handle cases where an API Group / GroupVersion is not present in the system. Clients expect No{Kind,Resource}MatchErrors in this case.
The first commit increases the accuracy of the RESTMapper tests to verify the described expectations.
The second commit implements the actual fix.
The changes are from @timebertt PR #2425.
The PR #2425 is still needed as with non existing CRDs we are getting
failed to find API group
error.