-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Pluralization discrepancy in UnsafeGuessKindToResource still exists #1082
Comments
A workaround is to pass empty list of objects client-go/kubernetes/fake/clientset_generated.go Lines 124 to 130 in cab7ba1
and manually use Create() on the tracker instead of Add() as suggested here Lines 326 to 330 in cab7ba1
|
I've also stumbled across this when using dynClient := dyn_fake.NewSimpleDynamicClientWithCustomListKinds(scheme.Scheme,
map[schema.GroupVersionResource]string{
{
Group: "gateway.networking.k8s.io",
Version: "v1beta1",
Resource: "gateways",
}: "GatewayList",
},
...
) and then listing a gateway (via unstructured client) yields
from Any work arounds for this? |
I tried adding a test case in https://github.com/kubernetes/gengo/blob/940203f2dae74b24bb30948aa5a9619ba259d4a5/namer/plural_namer_test.go to verify that this is indeed broken for Ok, got it: kubernetes/kubernetes#110053 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Still an issue (I'm mostly bumping this because of the problem with Gateway APIs). /remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
There seem to be a potential way forward to fix this. I've posted kubernetes/kubernetes#110053 (comment) to ensure it's "the right way" and if that's the case I can propose something for everyone to review. /remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
any updates ? |
Expected:
gateway-> gateways
Got:
gateway-> gatewaies
Is there any way to affect this mistaken guessing?
The text was updated successfully, but these errors were encountered: