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 #112017: exec auth: support TLS config caching #112339
Automated cherry pick of #112017: exec auth: support TLS config caching #112339
Conversation
Unit test failure is legitimate |
/kind bug |
/priority important-soon |
Signed-off-by: Monis Khan <mok@vmware.com>
This change updates the transport.Config .Dial and .TLS.GetCert fields to use a struct wrapper. This indirection via a pointer allows the functions to be compared and thus makes them valid to use as map keys. This change is then leveraged by the existing global exec auth and TLS config caches to return the same authenticator and TLS config even when distinct but identical rest configs were used to create distinct clientsets. Signed-off-by: Monis Khan <mok@microsoft.com>
c59216b
to
b1b8578
Compare
I cherry picked #106014 which should fix the test failure. |
/retest Unrelated failure. |
/lgtm |
cc @kubernetes/release-managers |
From https://github.com/kubernetes/website/blob/main/content/en/releases/patch-releases.md#122:
This PR is a good reason to ship 1.22.14, in my opinion. It fixes a rare but impactful issue in client-go and kubectl encountered when using exec auth plugins, which are GA in 1.22 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enj, liggitt, saschagrunert 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 #112017 on release-1.22.
#112017: exec auth: support TLS config caching
For details on the cherry pick process, see the cherry pick requests page.