Skip to content
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

Support for fetching APIResourceList #3303

Closed
rohanKanojia opened this issue Jul 7, 2021 · 1 comment · Fixed by #3487
Closed

Support for fetching APIResourceList #3303

rohanKanojia opened this issue Jul 7, 2021 · 1 comment · Fixed by #3487
Assignees
Milestone

Comments

@rohanKanojia
Copy link
Member

Similar to APIGroup which is accessible via /apis endpoint(see #3294), there is another NON-Restful endpoint in Kubernetes related to all available resources in a particular API group. It specifies information regarding a resource like the name of a resource and whether it is namespaced and supported operations.

Here is how it's used:

~ : $ curl localhost:8001/apis/batch/v1
{
  "kind": "APIResourceList",
  "apiVersion": "v1",
  "groupVersion": "batch/v1",
  "resources": [
    {
      "name": "jobs",
      "singularName": "",
      "namespaced": true,
      "kind": "Job",
      "verbs": [
        "create",
        "delete",
        "deletecollection",
        "get",
        "list",
        "patch",
        "update",
        "watch"
      ],
      "categories": [
        "all"
      ],
      "storageVersionHash": "mudhfqk/qZY="
    },
    {
      "name": "jobs/status",
      "singularName": "",
      "namespaced": true,
      "kind": "Job",
      "verbs": [
        "get",
        "patch",
        "update"
      ]
    }
  ]
}

I observed is that it's only possible to get a list of APIResource objects in a particular API group. It's not possible to get a specific APIResource object.

@manusa
Copy link
Member

manusa commented Jul 7, 2021

This is what is mentioned in #3294 (comment).

I think this might be exposable through our DSL, but I really think this would be very useful internally for the #2929 implementation.

shawkins added a commit to shawkins/kubernetes-client that referenced this issue Aug 14, 2021
also trying to consolidate existing logic about openshift adapting
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Aug 14, 2021
also trying to consolidate existing logic about openshift adapting
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Aug 14, 2021
also trying to consolidate existing logic about openshift adapting
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Aug 31, 2021
also trying to consolidate existing logic about openshift adapting
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Aug 31, 2021
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Aug 31, 2021
also trying to consolidate existing logic about openshift adapting
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Aug 31, 2021
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Sep 1, 2021
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Sep 14, 2021
manusa pushed a commit to manusa/kubernetes-client that referenced this issue Sep 22, 2021
@manusa manusa added this to the 5.9.0 milestone Sep 23, 2021
manusa pushed a commit to manusa/kubernetes-client that referenced this issue Sep 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants