Closed jpeach closed 3 years ago
@youngnick I think that kubectl explain
pull this from the OpenAPI definition for the Resource, so maybe we could get this for free as part of #1575?
KIND: HTTPProxy
VERSION: projectcontour.io/v1
DESCRIPTION:
<empty>
KIND: HTTPProxy
VERSION: projectcontour.io/v1
DESCRIPTION:
<empty>
:(
Hmm, probably. I'll take this for now and see if that happens when I do #1414.
There is also #1567
Sadly, #1731 didn't just magically fix this one, but I think that that's due to upstream things.
Specifically:
v1beta1
(what we're currently using). We can specify it, but not with the generator I added in #1731, it doesn't support it yet. I enabled it manually in a test 1.16 cluster, but the kubectl explain
was not the full version, so I suspect the second condition is also not fulfilled currently.The tl;dr here for next steps is:
v1
. That will make solving this a lot easier. It's a big change though, and will require a long tail for updates.controller-tools
to add support for setting the pruning value in the spec, and to add support for ensuring the validation is structural.There is no way any of this will be done in rc.2, so I'm moving this to backlog. I'll keep it and poke it along.
+1
Please describe the problem you have
kubectl explain
is a built-in way to provide Kubernetes resource reference material to users. It would be great to support this as part of theHTTPProxy
documentation.