-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
federation: avoid double core group registration #42722
federation: avoid double core group registration #42722
Conversation
/lgtm |
Is this for 1.6 or later? |
@nikhiljindal I have not investigated whether there are any consequences like inconcistencies. Maybe the import order is hiding problems. wdyt? |
LGTM, thanks! |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, nikhiljindal, sttts
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@k8s-bot gce etcd3 e2e test this |
Needs rebase. |
a84b8bd
to
dcb50aa
Compare
Done. |
Automatic merge from submit-queue (batch tested with PRs 43870, 30302, 42722, 43736) |
@sttts PR needs rebase |
The federation apiserver installed its custom core group into the global
pkg/api
registry, leading to double registration. Luckily (or maybe unfortunately) we did not fail hard in this case, but the init funcs just ignored the error.This PR creates an extra apigroup registry based on the already existing federation
core.Scheme
. This decouples the two core groups (which happen to co-exist in hyperkube).