Should be able to have more than one ThirdPartyResource per domain

[polvi]

If this is the intended design, feel free to close. I could not tell if it was a bug or "feature".

If you add two ThirdPartyResources on the same domain, only one will be registered with the API. Consider this example:

$ cat example-tprs.yml
apiVersion: extensions/v1beta1
description: A foo
kind: ThirdPartyResource
metadata:
  name: foo.example.com
versions:
- name: v1

---
apiVersion: extensions/v1beta1
description: A bar
kind: ThirdPartyResource
metadata:
  name: bar.example.com
versions:
- name: v1
$ kubectl create -f example-tprs.yml 
thirdpartyresource "foo.example.com" created
thirdpartyresource "bar.example.com" created
$ kubectl get foos
the server doesn't have a resource type "foos"
$ kubectl get bars
$ curl localhost:8080/apis/example.com/v1
{
  "kind": "APIResourceList",
  "apiVersion": "v1",
  "groupVersion": "example.com/v1",
  "resources": [
    {
      "name": "bars",
      "namespaced": true,
      "kind": "Bar"
    }
  ]
}

[zhouhaibing089]

looks like this one: #23831

[nikhiljindal]

Closing as dup of #23831