-
Notifications
You must be signed in to change notification settings - Fork 4.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
the server could not find the requested resource #9622
Comments
I have found that the backend code of the master branch also has this problem, but I have not tested the latest version for this problem. |
I tested this issue with postman in release-7.10.0 and the problem persisted. Set namespace to "_all", and do not set the namespace field for content.metadata |
so I modified the pr based on 7.10.0 on a new branch, and the new branch name was 7.10.0-patch. |
What happened?
I saw a "the server could not find the requested resource " error when I created resource. Sometimes it works, sometimes it doesn't.I found inconsistencies in the body namespce field of the /api/v1/appdeploymentfromfile API.Sometimes it's "default", sometimes it's "_all". If the value is "default", the resource is successfully created.
I think this is a bug in the front-end, the back-end logic is not more scientific .
Modify the scheme as follows:
1.The namespace field is added when the resource is created
2.Modified front end
3.Modified back end,I will submit a PR
What did you expect to happen?
success
How can we reproduce it (as minimally and precisely as possible)?
apiVersion: k8s.tmlake.com/v1
kind: AclProfile
metadata:
name: test-ap
spec:
partitionName: k8s-adc
name: lj-test
aclList:
- action: allow
addr: 1.1.1.1
enable: "on"
- action: deny
addr: 2.2.2.2
enable: "off"
There is no resource namespace field
Anything else we need to know?
No response
What browsers are you seeing the problem on?
No response
Kubernetes Dashboard version
2.5.1 and 2.6.1
Kubernetes version
1.23 and 1.22
Dev environment
No response
The text was updated successfully, but these errors were encountered: