-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
generate ReportingInstance and ReportingController in Event #116506
Conversation
Hi @HirazawaUi. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
https://kubernetes.io/docs/reference/using-api/deprecation-guide/ The deprecation guide also mentioned the renames. Should that be fixed as well for now or we want to keep them that way? And if we want to keep them that way, doc also needs to be updated. |
/sig instrumentation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
LGTM label has been added. Git tree hash: bc057d9bddf7e761b40a6be42fa27245963363d6
|
/triage accepted |
/retest |
@HirazawaUi: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
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. |
@logicalhan could you please help me retest |
/ok-to-test |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
1 similar comment
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
3e8faab
to
df0a253
Compare
/retest |
2 similar comments
/retest |
/retest |
@logicalhan May you help this PR to LGTM again? |
@dgrisonnet @dashpole @logicalhan Can we continue reviewing this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
(from sig inst)
LGTM label has been added. Git tree hash: a86af5c859e996ed6ecf249b55ade3b341f5d0b2
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: HirazawaUi, logicalhan 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 |
Will this be backported to prior Kubernetes versions before 1.28? |
as it should be |
…116506-upstream-release-1.27 Automated cherry pick of #116506: generate ReportingInstance and ReportingController in Event
…116506-upstream-release-1.25 Automated cherry pick of #116506: generate ReportingInstance and ReportingController in Event
…116506-upstream-release-1.26 Automated cherry pick of #116506: generate ReportingInstance and ReportingController in Event
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
the reportingController and reportingInstance fields in the event do not have values, which is non-compliant with the Kubernetes API v1.25 specification. Further details can be found at https://kubernetes.io/docs/reference/using-api/deprecation-guide/#event-v125
Which issue(s) this PR fixes:
Fixes #116444
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: