You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on my understanding, the correct API to retrieve all pods is api/v1/pods instead of api/v1/namespaces//pods in some versions of Kube-Apiserver. It seems that the issue may be related to the incorrect API path being used.
The text was updated successfully, but these errors were encountered:
Description:
I am trying to integrate kube-scheduler-simulator with a real Kubernetes cluster.
Steps to Reproduce:
Issue a curl request to http://localhost:3131/api/v1/namespaces//pods.
Actual Behavior:
![Pasted image 20230724154040](https://private-user-images.githubusercontent.com/53330071/255521935-452dd52b-cf42-45b8-a392-5429c87c9d62.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA1ODk4NTksIm5iZiI6MTcyMDU4OTU1OSwicGF0aCI6Ii81MzMzMDA3MS8yNTU1MjE5MzUtNDUyZGQ1MmItY2Y0Mi00NWI4LWEzOTItNTQyOWM4N2M5ZDYyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzEwVDA1MzIzOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE2MDNhY2I4Y2VjZGQ4ZmUyMDc0NjUzMDlkODQ2NTc0OGIwOWI3YWJiNzcwYTM2Y2E0OWQzNGYyMDI5MmE2NDQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.IaPuOaWbfw2GkNw69XfJPz56BNLHo5G3pkIGV9YT2QA)
However, this is not a cross -domain problem.
Additional Information:
kube-apiserver version: v1.22.17
The API that should return all pods is accessed using
api/v1/namespaces//pods
. But:I found
api/v1/pods
can do this well.Solution:
Based on my understanding, the correct API to retrieve all pods is
api/v1/pods
instead ofapi/v1/namespaces//pods
in some versions of Kube-Apiserver. It seems that the issue may be related to the incorrect API path being used.The text was updated successfully, but these errors were encountered: