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 #117258: kube-aggregator: correctly use client-go TLS cache with #117311
Automated cherry pick of #117258: kube-aggregator: correctly use client-go TLS cache with #117311
Conversation
Signed-off-by: Monis Khan <mok@microsoft.com>
/kind bug |
/lgtm |
LGTM label has been added. Git tree hash: 43c8b323658ba0c3bc188532d83181c0327f52a4
|
This is intentionally only picked back to 1.26 (and not 1.25 or 1.24) since it is resolving an issue introduced in 1.26 (in #112450) |
/cc kubernetes/release-managers |
/lgtm deferring |
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: enj, liggitt, 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 #117258 on release-1.26.
#117258: kube-aggregator: correctly use client-go TLS cache with
For details on the cherry pick process, see the cherry pick requests page.