-
Notifications
You must be signed in to change notification settings - Fork 690
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
improve validation around user-specified timeout values #2728
Labels
area/deployment
Issues or PRs related to deployment tooling or infrastructure.
Comments
skriss
added a commit
to skriss/contour
that referenced
this issue
Sep 11, 2020
Returns errors when parsing timeout strings so they can be reported to the user, either as invalid HTTPProxies, or in Contour logs. Previously, such errors were swallowed and the timeout in question was disabled/set to infinity. Updates projectcontour#2728 Signed-off-by: Steve Kriss <[email protected]>
skriss
added a commit
to skriss/contour
that referenced
this issue
Sep 11, 2020
Returns errors when parsing timeout strings so they can be reported to the user, either as invalid HTTPProxies, or in Contour logs. Previously, such errors were swallowed and the timeout in question was disabled/set to infinity. Updates projectcontour#2728 Signed-off-by: Steve Kriss <[email protected]>
skriss
added a commit
to skriss/contour
that referenced
this issue
Sep 14, 2020
Returns errors when parsing timeout strings so they can be reported to the user, either as invalid HTTPProxies, or in Contour logs. Previously, such errors were swallowed and the timeout in question was disabled/set to infinity. Updates projectcontour#2728 Signed-off-by: Steve Kriss <[email protected]>
// cc auth impl: #2886 (comment) |
skriss
added a commit
to skriss/contour
that referenced
this issue
Sep 15, 2020
Returns errors when parsing timeout strings so they can be reported to the user, either as invalid HTTPProxies, or in Contour logs. Previously, such errors were swallowed and the timeout in question was disabled/set to infinity. Updates projectcontour#2728 Signed-off-by: Steve Kriss <[email protected]>
skriss
added a commit
to skriss/contour
that referenced
this issue
Sep 16, 2020
Returns errors when parsing timeout strings so they can be reported to the user, either as invalid HTTPProxies, or in Contour logs. Previously, such errors were swallowed and the timeout in question was disabled/set to infinity. Updates projectcontour#2728 Signed-off-by: Steve Kriss <[email protected]>
skriss
added a commit
that referenced
this issue
Sep 16, 2020
…ty (#2905) * internal/timeout: return parse errors instead of defaulting to infinity Returns errors when parsing timeout strings so they can be reported to the user, either as invalid HTTPProxies, or in Contour logs. Previously, such errors were swallowed and the timeout in question was disabled/set to infinity. Updates #2728 Signed-off-by: Steve Kriss <[email protected]>
skriss
added a commit
to skriss/contour
that referenced
this issue
Sep 16, 2020
Adds kubebuilder regex validations for all timeout string API fields. Closes projectcontour#2728 Signed-off-by: Steve Kriss <[email protected]>
skriss
added a commit
to skriss/contour
that referenced
this issue
Sep 17, 2020
Adds kubebuilder regex validations for all timeout string API fields. Closes projectcontour#2728 Signed-off-by: Steve Kriss <[email protected]>
skriss
added a commit
to skriss/contour
that referenced
this issue
Sep 17, 2020
Adds kubebuilder regex validations for all timeout string API fields. Closes projectcontour#2728 Signed-off-by: Steve Kriss <[email protected]>
skriss
added a commit
to skriss/contour
that referenced
this issue
Sep 17, 2020
Adds kubebuilder regex validations for all timeout string API fields. Closes projectcontour#2728 Signed-off-by: Steve Kriss <[email protected]>
skriss
added a commit
that referenced
this issue
Sep 17, 2020
Adds kubebuilder regex validations for all timeout string API fields. Closes #2728 Signed-off-by: Steve Kriss <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, if an unparseable timeout value is specified in either the config file or in a
TimeoutPolicy
field in anHTTPProxy
route, the parse error is swallowed and the timeout is disabled/set to infinity.There are a few things we can do to improve this:
+kubebuilder:validation:Pattern
)contour serve
can exit, or we can log a warning/error.Also, consider what to do with unparseable timeout annotations on
Ingress
resources.ref. #2697
The text was updated successfully, but these errors were encountered: