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

Can only and one third party resource #35093

Closed
mqliang opened this issue Oct 19, 2016 · 2 comments
Closed

Can only and one third party resource #35093

mqliang opened this issue Oct 19, 2016 · 2 comments
Labels
area/kubectl sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@mqliang
Copy link
Contributor

mqliang commented Oct 19, 2016

I add three third party resources, but it turns out only one works. Even if I restart API server, the problem still exists.

[root@iZ94uugzhjmZ ~]#curl  http://localhost:8080/apis/extensions/v1beta1/thirdpartyresources/
{
  "kind": "ThirdPartyResourceList",
  "apiVersion": "extensions/v1beta1",
  "metadata": {
    "selfLink": "/apis/extensions/v1beta1/thirdpartyresources/",
    "resourceVersion": "1238141"
  },
  "items": [
    {
      "metadata": {
        "name": "loadbalancer.k8s.io",
        "selfLink": "/apis/extensions/v1beta1/thirdpartyresources/loadbalancer.k8s.io",
        "uid": "346b89a4-95c7-11e6-9c36-00163e023784",
        "resourceVersion": "1237863",
        "creationTimestamp": "2016-10-19T06:42:29Z"
      },
      "description": "Allow user to curd a loadbalancer instance",
      "versions": [
        {
          "name": "v1"
        }
      ]
    },
    {
      "metadata": {
        "name": "loadbalancerclaim.k8s.io",
        "selfLink": "/apis/extensions/v1beta1/thirdpartyresources/loadbalancerclaim.k8s.io",
        "uid": "4d73de4a-95b2-11e6-9f6d-00163e023784",
        "resourceVersion": "1234055",
        "creationTimestamp": "2016-10-19T04:12:51Z"
      },
      "description": "Allow user to claim a loadbalancer instance",
      "versions": [
        {
          "name": "v1"
        }
      ]
    },
    {
      "metadata": {
        "name": "push.k8s.io",
        "selfLink": "/apis/extensions/v1beta1/thirdpartyresources/push.k8s.io",
        "uid": "380a801b-95c6-11e6-9f6d-00163e023784",
        "resourceVersion": "1237613",
        "creationTimestamp": "2016-10-19T06:35:25Z"
      },
      "description": "Allow user to commit and push a container to image hub",
      "versions": [
        {
          "name": "v1"
        }
      ]
    }
  ]
}
[root@iZ94uugzhjmZ ~]# kubectl get loadbalancerclaim
the server doesn't have a resource type "loadbalancerclaim"
[root@iZ94uugzhjmZ ~]# kubectl get loadbalancer
[root@iZ94uugzhjmZ ~]# kubectl get push
the server doesn't have a resource type "push"
[root@iZ94uugzhjmZ ~]# curl http://localhost:8080/apis/k8s.io/v1/
{
  "kind": "APIResourceList",
  "apiVersion": "v1",
  "groupVersion": "k8s.io/v1",
  "resources": [
    {
      "name": "loadbalancers",
      "namespaced": true,
      "kind": "Loadbalancer"
    }
  ]
}
@mqliang
Copy link
Contributor Author

mqliang commented Oct 19, 2016

@mqliang mqliang closed this as completed Oct 19, 2016
@mqliang mqliang reopened this Oct 19, 2016
@k8s-github-robot k8s-github-robot added area/kubectl sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. labels Oct 19, 2016
@mqliang mqliang changed the title Can only add one third party resource Can add only one third party resource Oct 19, 2016
@mqliang mqliang changed the title Can add only one third party resource Can only and one third party resource Oct 19, 2016
@mqliang mqliang closed this as completed Oct 19, 2016
@deads2k
Copy link
Contributor

deads2k commented Oct 19, 2016

Known problem from kubernetes/enhancements#95. You have to get them inside one sync interval. I am surprised restarting didn't help though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubectl sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Development

No branches or pull requests

3 participants