Skip to content
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

[pull] master from kubernetes-sigs:master #93

Merged
merged 4 commits into from
Dec 15, 2020

Conversation

pull[bot]
Copy link

@pull pull bot commented Dec 15, 2020

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label Dec 15, 2020
vincepri and others added 2 commits December 15, 2020 08:30
Currently, when we create a new delegating client and we force some
types to be uncached, we can only specify client.Object(s).

When these objects are passed to the delegating client, and their GVK is
matched against the internal map, the check doesn't take into account
that the client might be issuing a List call with a ObjectList instead
of a metav1.Object.

The proposed solution is taken from the discovery rest mapper, which
does the same ~hack. While it's not perfect, probably close to all
generated objects are going to have a list that has the "List" suffix,
that when removed gives back the original GVK.

If there are other solutions, happy to change this hack.

Signed-off-by: Vince Prignano <vincepri@vmware.com>
🐛 Cache bypass should take into account List types
@pull pull bot merged commit 355962a into alexeldeib:master Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants