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 #116145: Plumb stale GroupVersions through aggregated discovery #115865: Removes old discovery hack ignoring 403 and 404 #116437
Conversation
@deads2k has asked for the "stale" feature to be backported to 1.26, completing the aggregated discovery client. And I had to cherry-pick both PR's to backport the "stale" PR. Also, there is a bug we discovered in the aggregated discovery client for an edge case which was fixed in the "stale" PR. This bug could surface if a v1.26 client was used against a v1.27 or later api server. BTW, the feature gate for aggregated discovery is only server-side. |
Unrelated unit test failure: /retest |
/cc @deads2k |
/cc @Jefftree |
ah, ok. I'll let deadsk ack this since he approved the master PR |
Thanks. /lgtm |
LGTM label has been added. Git tree hash: b82de45b98c3a752bd1e1f45fcdd9aec48bd7cf7
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, seans3 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 |
/cc kubernetes/release-managers |
/priority critical-urgent |
/lgtm |
/triage accepted |
Cherry pick of #116145 #115865 on release-1.26.
#116145: Surface "stale" GroupVersions from AggregatedDiscovery
#115865: Updates old 403 and 404 discovery response tolerations
/kind feature
For details on the cherry pick process, see the cherry pick requests page.