-
Notifications
You must be signed in to change notification settings - Fork 40.6k
apiextensions: check request scope against CRD scope correctly #80750
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
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sttts 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 |
/lgtm |
i tried POST a pod against a non-namespace path $ curl --cert /tmp/crt --key /tmp/key -XPOST -d@/tmp/pod -H 'Content-Type: application/json' -k https://127.0.0.1:6443/api/v1/pods
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {
},
"status": "Failure",
"message": "the server does not allow this method on the requested resource",
"reason": "MethodNotAllowed",
"details": {
},
"code": 405
} |
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
2 similar comments
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
New changes are detected. LGTM label has been removed. |
fixed typo |
New changes are detected. LGTM label has been removed. |
/cc @roycaihw |
LGTM |
We need to add the following release note:
|
Before this PR we did not always check that the request scope was matching the CRD. This adds consequent checks, and exhaustive tests.