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

Implementing logic for v1beta1.Event API #65782

Merged
merged 1 commit into from
May 17, 2019

Conversation

yastij
Copy link
Member

@yastij yastij commented Jul 3, 2018

What this PR does / why we need it: This PR implements kubernetes/enhancements#383 API logic. migration of relevent controller will follow after this PR

Which issue(s) this PR fixes : Fixes #56694

Special notes for your reviewer:

Release note:

Implementing deduplication logic for v1beta1.Event API

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 3, 2018
@yastij
Copy link
Member Author

yastij commented Jul 3, 2018

/assign @timothysc @wojtek-t

@idealhack
Copy link
Member

/ok-to-test

@k8s-ci-robot k8s-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jul 4, 2018
@timothysc
Copy link
Member

/cc @kubernetes/sig-api-machinery-pr-reviews

@k8s-ci-robot k8s-ci-robot added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Jul 13, 2018
@timothysc timothysc removed their assignment Jul 13, 2018
@wojtek-t
Copy link
Member

/assign @gmarek

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 12, 2018
@yastij
Copy link
Member Author

yastij commented Oct 12, 2018

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 12, 2018
@wojtek-t
Copy link
Member

@yastij - what's the status of this PR?
It's marked as WIP so I would like to understand its status and how do you expect to proceed with this.

@yastij yastij changed the title WIP: Implementing logic for v1beta1.Event API Implementing logic for v1beta1.Event API Oct 22, 2018
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 22, 2018
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 10, 2018
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 28, 2018
@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels May 13, 2019
Copy link
Member

@wojtek-t wojtek-t left a comment

Choose a reason for hiding this comment

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

Please don't resolve comments - especially given most of them are still not addressed.

Most of them are from the previous round are not addressed - I'm not going to take another round of review until you those will be addressed.

eventBroadcaster.mu.RLock()
defer eventBroadcaster.mu.RUnlock()
for _, event := range eventBroadcaster.eventCache {

Copy link
Member

Choose a reason for hiding this comment

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

not solved

@yastij yastij force-pushed the eventv2-eventf branch 3 times, most recently from 1c32a26 to b37f793 Compare May 13, 2019 20:39
staging/src/k8s.io/client-go/tools/events/interfaces.go Outdated Show resolved Hide resolved
staging/src/k8s.io/client-go/tools/events/interfaces.go Outdated Show resolved Hide resolved
staging/src/k8s.io/client-go/tools/events/interfaces.go Outdated Show resolved Hide resolved
staging/src/k8s.io/client-go/tools/events/interfaces.go Outdated Show resolved Hide resolved
@yastij
Copy link
Member Author

yastij commented May 16, 2019

/retest

@yastij
Copy link
Member Author

yastij commented May 16, 2019

@wojtek-t - updated and squashed.

Signed-off-by: Yassine TIJANI <ytijani@vmware.com>
@yastij
Copy link
Member Author

yastij commented May 17, 2019

/retest

@wojtek-t
Copy link
Member

/lgtm
/approve

Let's have this merged and iterate on this further.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 17, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wojtek-t, yastij

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 17, 2019
@k8s-ci-robot k8s-ci-robot merged commit e67c266 into kubernetes:master May 17, 2019
@tedyu
Copy link
Contributor

tedyu commented May 17, 2019

I have created #78040 for the above points.

nikhita pushed a commit to nikhita/kubernetes that referenced this pull request Jun 13, 2019
Implementing logic for v1beta1.Event API

Kubernetes-commit: e67c266
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/apiserver area/dependency Issues or PRs related to dependency changes area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/release Categorizes an issue or PR as relevant to SIG Release. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

update eventRecorder to handle event series using the new Event API group