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

Adding events to federation control plane #30421

Merged
merged 1 commit into from
Aug 13, 2016

Conversation

nikhiljindal
Copy link
Contributor

@nikhiljindal nikhiljindal commented Aug 11, 2016

Ref #29744

Adding events to federation control plane.

Apart from the standard changes to add a resource to federation/apis/core/v1, other changes are:

  • Adding a new federationoptions.ServerRunOptions which includes genericoptions.ServerRunOptions and EventsTTL.
  • Added a new method in pkg/api/mapper to build a RestMapper based on the passed Scheme rather than using api.Scheme. Updated federation/apis/core/install to use this new method. Without this change, if federation/apis/core/install.init() is called before pkg/api/install.init() then the registered RESTMapper in pkg/apimachinery/registered will have no resources. This second problem will be fixed once we have instances of pkg/apimachinery/registered instead of a single global singleton (generated clientset which imports pkg/api/install will have a different instance of registered, than federation-apiserver which imports federation/apis/core/install).

cc @kubernetes/sig-cluster-federation @lavalamp


This change is Reviewable

@nikhiljindal nikhiljindal added this to the v1.4 milestone Aug 11, 2016
@k8s-github-robot k8s-github-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. release-note-label-needed labels Aug 11, 2016
@nikhiljindal nikhiljindal added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-label-needed labels Aug 11, 2016
@nikhiljindal
Copy link
Contributor Author

The failures seem to be flakes. Retrying.

@k8s-bot unit test this issue: #IGNORE
@k8s-bot gce e2e test this issue: #IGNORE

@@ -83,4 +83,16 @@ func addConversionFuncs(scheme *runtime.Scheme) {
panic(err)
}
}
if err := v1.AddFieldLabelConversionsForEvent(scheme); err != nil {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any chance you can rebase on top of #25526? I've had to redo it like 5 times...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes sure. Yours is a huge PR! :)

@nikhiljindal nikhiljindal force-pushed the eventsAPI branch 2 times, most recently from e6ab2f6 to 32c25e5 Compare August 12, 2016 00:37
@nikhiljindal
Copy link
Contributor Author

Updated code as per comments

@k8s-github-robot k8s-github-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 12, 2016
@nikhiljindal nikhiljindal removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 12, 2016
@nikhiljindal
Copy link
Contributor Author

Rebased. Ready for another look

@k8s-bot
Copy link

k8s-bot commented Aug 12, 2016

GCE e2e build/test passed for commit 1d76884.

@ghost ghost added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Aug 12, 2016
@lavalamp lavalamp added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 12, 2016
@lavalamp
Copy link
Member

LGTM

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Aug 13, 2016

GCE e2e build/test passed for commit 1d76884.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit 29eda9b into kubernetes:master Aug 13, 2016
k8s-github-robot pushed a commit that referenced this pull request Aug 15, 2016
Automatic merge from submit-queue

Adding events to federation clientset and adding an e2e

Fixes #27026

events was added to federation-apiserver in #30421

cc @kubernetes/sig-cluster-federation @mfanjie
perotinus pushed a commit to kubernetes-retired/cluster-registry that referenced this pull request Sep 2, 2017
Automatic merge from submit-queue

Adding events to federation clientset and adding an e2e

Fixes kubernetes/kubernetes#27026

events was added to federation-apiserver in kubernetes/kubernetes#30421

cc @kubernetes/sig-cluster-federation @mfanjie
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/backlog Higher priority than priority/awaiting-more-evidence. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants