Closed Jefftree closed 1 year ago
Yeah, I don't think these are meant to break anything. The way the openapi is generated is super confusing and convoluted.
If these should fail, then we should have a corresponding validation rule created to find them, and they might (or not) be excluded through the reports.
These are separate validations from the reports, as discussed offline we should make these more consistent with the violation reports as a first step.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
While investigating https://github.com/kubernetes/kube-openapi/issues/343 I noticed that we have some validation as part of
openapi-gen
but the errors are silenced: https://github.com/kubernetes/kube-openapi/blob/master/pkg/generators/openapi.go#L501-L506Errors are printed as a
klog.V(2)
and the execution of openapi-gen is unaffected if there is a validation error. Based on the comments this seems intentional? cc @apelisse @seans3 since you have worked closely with this code before.Given the way we invoke
hack/update-codegen.sh
and call openapi-gen in k/k, the errors are never surfaced and hard for us to see. We already have types that fail validation and are not surfaced. Here's an output of the current logs from runningKUBE_VERBOSE=2 ./hack/update-codegen.sh openapi