Open KubeKyrie opened 6 months ago
Hi @KubeKyrie, Thanks for opening an issue! We will look into it as soon as possible.
Hey! Such a great find @KubeKyrie. Maybe creating a unique token for each cluster and storing it in the storage layer might help.Then we can maybe create a sort of a middleware which checks on each request
This is a known result, and for global searches (paths that do not contain clusters/< cluster >), the parameters passed will only affect the results returned, but no errors will be reported unless the parameters are abnormal.
What happened?
When search for resources in a specified cluster, the response of two url query way is different. In this case, actually cluster-1 not exists. In the 2nd way, we may mistakenly assume that deployment does not exist in cluster-1, rather than cluster-1 So I think the 2nd way should also be
Error from server (BadRequest): the server could not find the requested cluster
What did you expect to happen?
Error from server (BadRequest): the server could not find the requested cluster
How can we reproduce it (as minimally and precisely as possible)?
Just
kubectl get --raw="/apis/clusterpedia.io/v1beta1/resources/apis/apps/v1/deployments?clusters=cluster-1"
Anything else we need to know?
Nope
Clusterpedia Version
None
Host Kubernetes version
None