{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/35162","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/35162/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/35162/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/35162/events","html_url":"https://github.com/kubernetes/kubernetes/issues/35162","id":184093755,"number":35162,"title":"server and client should have their own instances of APIRegistrationManager","user":{"login":"nikhiljindal","id":10199099,"avatar_url":"https://avatars.githubusercontent.com/u/10199099?v=3","gravatar_id":"","url":"https://api.github.com/users/nikhiljindal","html_url":"https://github.com/nikhiljindal","followers_url":"https://api.github.com/users/nikhiljindal/followers","following_url":"https://api.github.com/users/nikhiljindal/following{/other_user}","gists_url":"https://api.github.com/users/nikhiljindal/gists{/gist_id}","starred_url":"https://api.github.com/users/nikhiljindal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nikhiljindal/subscriptions","organizations_url":"https://api.github.com/users/nikhiljindal/orgs","repos_url":"https://api.github.com/users/nikhiljindal/repos","events_url":"https://api.github.com/users/nikhiljindal/events{/privacy}","received_events_url":"https://api.github.com/users/nikhiljindal/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/team/CSI-API%20Machinery%20SIG","name":"team/CSI-API Machinery SIG","color":"d2b48c"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2016-10-19T22:48:48Z","updated_at":"2016-10-21T00:54:15Z","closed_at":null,"body":"Now that we have APIRegistrationManager, we should update the server and client to instantiate their own instances of APIRegistrationManager and register the APIs independently.\r\n\r\nCurrently, we use DefaultAPIRegistrationManager everywhere. As a result, if the client depends on an API, it is included in the server automatically.\r\n\r\nhttps://github.com/kubernetes/kubernetes/issues/26675 is an example instance of the problem that this leads to. Calling `registered.AllPreferredGroupVersions()` in api server returns all group versions including the ones that client depends on. There should be a way to get all group versions included only in the server.\r\n\r\ncc @kubernetes/sig-cluster-federation @caesarxuchao "},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/255267029","html_url":"https://github.com/kubernetes/kubernetes/issues/35162#issuecomment-255267029","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/35162","id":255267029,"user":{"login":"nikhiljindal","id":10199099,"avatar_url":"https://avatars.githubusercontent.com/u/10199099?v=3","gravatar_id":"","url":"https://api.github.com/users/nikhiljindal","html_url":"https://github.com/nikhiljindal","followers_url":"https://api.github.com/users/nikhiljindal/followers","following_url":"https://api.github.com/users/nikhiljindal/following{/other_user}","gists_url":"https://api.github.com/users/nikhiljindal/gists{/gist_id}","starred_url":"https://api.github.com/users/nikhiljindal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nikhiljindal/subscriptions","organizations_url":"https://api.github.com/users/nikhiljindal/orgs","repos_url":"https://api.github.com/users/nikhiljindal/repos","events_url":"https://api.github.com/users/nikhiljindal/events{/privacy}","received_events_url":"https://api.github.com/users/nikhiljindal/received_events","type":"User","site_admin":false},"created_at":"2016-10-21T00:54:15Z","updated_at":"2016-10-21T00:54:15Z","body":"> Registration isn't appropriate for that. Enablement validation is\r\n\r\nSorry can you elaborate on that. Is it wrong to use the list of registered group versions to validate what group versions can be enabled?\r\n\r\n> Also, storage enablement and rest API enablement are not the same thing. \r\n\r\nSo we should have 2 lists of group versions: one that can be enabled in storage and one that can be enabled in the API?\r\nClient does not care about storage versions."}}
{"actor":{"display_login":"nikhiljindal"}}