-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
When subresource is given, non-conventional CRD resource pluralization not working in kubectl #67235
Comments
cc: @tamalsaha @nikhita @sttts |
/sig api-machinery Tried this on master, worked fine.
Tried on v1.11.1, can reproduce the error. Looks like some commit fixed it. 🎉 I'm not sure which commit fixed this, but I'll find it and report here. We should probably cherry-pick to 1.11 as well. Thanks for reporting this, @the-redback! |
Not really related to this, but creating a custom resource in this case says:
instead, it should be fooes.samplecontroller.k8s.io. |
#66249 was the fix. Will cherry-pick it into 1.11.
|
/assign |
created #67240 |
…9-upstream-release-1.11 Automatic merge from submit-queue. Automated cherry pick of #66249: fill in normal restmapping info with the legacy guess Fixes 1.11 part of #67235 Cherry pick of #66249 on release-1.11. #66249: fill in normal restmapping info with the legacy guess ```release-note Fix creation of custom resources when the CRD contains non-conventional pluralization and subresources ```
…9-upstream-release-1.11 Automatic merge from submit-queue. Automated cherry pick of #66249: fill in normal restmapping info with the legacy guess Fixes 1.11 part of kubernetes/kubernetes#67235 Cherry pick of #66249 on release-1.11. #66249: fill in normal restmapping info with the legacy guess ```release-note Fix creation of custom resources when the CRD contains non-conventional pluralization and subresources ``` Kubernetes-commit: 10ecc6db83fd47a93eb0940e2e4434f2b0a5c3ec
/cc @mbohlool |
…9-upstream-release-1.10 Automatic merge from submit-queue. Automated cherry pick of #66249: fill in normal restmapping info with the legacy guess Fixes 1.10 part of #67235 Cherry pick of #66249 on release-1.10. #66249: fill in normal restmapping info with the legacy guess ```release-note Fix creation of custom resources when the CRD contains non-conventional pluralization and subresources ```
…9-upstream-release-1.10 Automatic merge from submit-queue. Automated cherry pick of #66249: fill in normal restmapping info with the legacy guess Fixes 1.10 part of kubernetes/kubernetes#67235 Cherry pick of #66249 on release-1.10. #66249: fill in normal restmapping info with the legacy guess ```release-note Fix creation of custom resources when the CRD contains non-conventional pluralization and subresources ``` Kubernetes-commit: b16193f435cefa70de14823738a2c5af3d99b7ca
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
I was using Non-conventional CRD resource pluralization, say
fooes
(fooes.samplecontroller.k8s.io
). I usedstatus
assubresource
. Now, When I create an object ofFoo
kind withkubectl
, it gives error that there is no requested resourcepost foos.samplecontroller.k8s.io
. But, When I useclient-go:8.0.0
it works just fine.I can also confirm that, this
fooes
pluralization works fine with kubectl when no subresource is given.What you expected to happen:
kubectl
is able to handle non-conventional pluralization of CRD objects, So it also should be able to handle this when subresource is enabled.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
client-go
.postgreses
,mongodbs
, with subresource enabled.Environment:
kubectl version
):uname -a
):Linux appscode 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
minikube start --kubernetes-version=v1.11.1
The text was updated successfully, but these errors were encountered: