-
Notifications
You must be signed in to change notification settings - Fork 360
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
BackendTrafficPolicy openapi schemas do not validate correctly #4746
Comments
thanks for raising this, do we need to edit these to gateway/api/v1alpha1/healthcheck_types.go Line 81 in 6c6633c
|
ya, i poked around at how Cluster API is doing it, and i think they just leave the and it will do the right thing with the existing |
ok I see an issue we ended up using gateway/api/v1alpha1/keepalive_types.go Line 26 in 6c6633c
this has a CEL validation e.g. gateway/charts/gateway-helm/crds/generated/gateway.envoyproxy.io_backendtrafficpolicies.yaml Line 1305 in 6c6633c
, and doesnt require a kubebuilder validation this is a breaking change, because we are tightening the validation, not loosening it cc @envoyproxy/gateway-maintainers |
thanks for helping us find this @nicks we'll also need to add an entry in
|
* Also rm `+kubebuilder:validation:Format=duration` and instead rely on the CEL validation of gwapiv1.Duration Fixes: envoyproxy#4746 Signed-off-by: Arko Dasgupta <[email protected]>
Description:
I'm trying to use kubeconform to validate BackendTrafficPolicy
I get this error:
Additional info:
I think the openapi schemas that we're generating are wrong. Particularly this line:
gateway/charts/gateway-helm/crds/generated/gateway.envoyproxy.io_backendtrafficpolicies.yaml
Line 314 in 6c6633c
They say that
timeout
andinterval
are openapi durations. But they're not, they're a Kubernetes-specific duration format.The text was updated successfully, but these errors were encountered: