-
Notifications
You must be signed in to change notification settings - Fork 480
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
apis: add implementation for GEP-1731 HTTPRoute Retries #3301
apis: add implementation for GEP-1731 HTTPRoute Retries #3301
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mikemorris!
// Implementations SHOULD retry on connection errors (disconnect, reset, timeout, | ||
// TCP failure) if a retry stanza is configured. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason not to make this configurable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Primarily because there's way too much variance in how different implementations define, default, bucket or even allow these to be configurable for this to be generally implementable within extended conformance, and secondarily because it's a simpler UX for what is often a good practice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FTR I think that makes sense, @mikemorris.
// | ||
// +optional | ||
// <gateway:experimental> | ||
Codes []HTTPRouteRetryStatusCode `json:"codes,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If at some point we want to include strings here, do we add a new Reasons []string
field?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly what I had been thinking if that we end up wanting that in the future! Per above comment on connection error variance between implementations, a Reasons []string
field may need to be implementation-specific, and could potentially even enable use cases like unsetting default behavior with a string like google.com/no-retry-connection-errors
or something.
ffc0c9d
to
68f9dc9
Compare
Co-authored-by: Rob Scott <rob.scott87@gmail.com>
68f9dc9
to
5d24b39
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with one small removal nit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mikemorris! One small nit but otherwise LGTM.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mikemorris, robscott, shaneutt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
disallowed by kubebuilder validation now
Thanks @mikemorris! /lgtm |
/hold cancel |
Just caught some last-minor minor cleanup on GEP index/status! |
Good catch, thanks! /lgtm |
remove duplicate index entry
d246bfa
to
86f5d87
Compare
Thanks @mikemorris, looks good here at this point! 🙂 /lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @mikemorris!
/lgtm
/unhold
What type of PR is this?
/kind documentation
/kind feature
What this PR does / why we need it:
Implements GEP-1731: HTTPRoute Retries
Which issue(s) this PR fixes:
Fixes #1731
Does this PR introduce a user-facing change?: