-
Notifications
You must be signed in to change notification settings - Fork 820
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
Fix "kubectl explain" output for Agones CRDs #1194
Comments
I think this is an issue of openapi spec not existing for CRDs. Based on https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/00xx-publish-crd-openapi.md it looks like once we update to 1.14 (or maybe later) this should "just work." It would be worth testing against a later k8s cluster to see what the behavior is. |
Partially fixed in Kubernetes 1.16:
So what left is to understand where to put a description. |
I was able to fix output of
|
We have schemas now for everything - I wonder what the output is now. Could be good to test. |
The output appears to be good! All of the descriptions are still
|
As per #1194 (comment) it seems like we are still missing the description, not just for the top level resource but also for the spec and status. |
Is your feature request related to a problem? Please describe.
Currently there is no option to see the description of fields using standard
kubectl
functionality:Describe the solution you'd like
Output should be similar to this:
It seems that we could update
apiserver.go
code to serve requests of this kind.Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: