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
Automated cherry pick of #119825: Move adding GroupVersion log until after an update is #122074
Automated cherry pick of #119825: Move adding GroupVersion log until after an update is #122074
Conversation
can you add a release note describing the issue this is fixing and the version the problem was introduced in, and updating the PR description with details about why this is a big enough problem to backport |
/lgtm |
LGTM label has been added. Git tree hash: 9fd7619738574828c9df39aeda304c85c0e6bca6
|
done |
/cc kubernetes/release-managers |
/triage accepted |
xref: #122096 |
should also be picked to 1.26 if that's when it regressed, right? |
oh, misread that the feature gate enablement was also required, which defaulted in 1.27 |
/kind bug |
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.
For RelEng:
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, ritazh, xmudrii 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 |
Cherry pick of #119825 on release-1.27.
#119825: Move adding GroupVersion log until after an update is
For details on the cherry pick process, see the cherry pick requests page.
Requesting cherry pick due to log volume regression xref: #119546 the code was introduced as 6e83f67 in 1.26 but the
AggregatedDiscoveryEndpoint
feature was enabled by default in 1.27 causing the huge amount of logs to be generated by default.