-
Notifications
You must be signed in to change notification settings - Fork 323
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
Port: "retryOn" configuration on ServiceRouter CRD #3308
Conversation
86160cf
to
16a4826
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.
Non-blocking question: would we want to explicitly link to the docs for the list of supported conditions, or do we typically assume folks know to go looking for the corresponding Consul config docs?
@zalimeni I linked to the conditions earlier in the changelog, if that's where you're referring to? |
e421cc9
to
3200313
Compare
@DanStough sorry, I was more thinking our own inline docs here, for the sake of folks unfamiliar w/ the field's semantics - not sure whether "check the Consul docs" is typically implied |
I would say it's typically implied but no harm in adding it ✍️ |
3200313
to
f828314
Compare
f828314
to
106905a
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.
This looks good. Have a suggestion but you can ignore it if it doesnt seem valueable.
Co-authored-by: ilpianista <[email protected]>
106905a
to
78bc22a
Compare
* feat(crds): add support for retryOn in service router Co-authored-by: ilpianista <[email protected]> --------- Co-authored-by: ilpianista <[email protected]>
* feat(crds): add support for retryOn in service router Co-authored-by: ilpianista <[email protected]> --------- Co-authored-by: ilpianista <[email protected]>
* feat(crds): add support for retryOn in service router Co-authored-by: ilpianista <[email protected]> --------- Co-authored-by: ilpianista <[email protected]>
…elease/1.2.x (#3324) Port: "retryOn" configuration on ServiceRouter CRD (#3308) * feat(crds): add support for retryOn in service router --------- Co-authored-by: Dan Stough <[email protected]> Co-authored-by: ilpianista <[email protected]>
…elease/1.3.x (#3325) Port: "retryOn" configuration on ServiceRouter CRD (#3308) * feat(crds): add support for retryOn in service router --------- Co-authored-by: Dan Stough <[email protected]> Co-authored-by: ilpianista <[email protected]>
…elease/1.1.x (#3323) Port: "retryOn" configuration on ServiceRouter CRD (#3308) * feat(crds): add support for retryOn in service router --------- Co-authored-by: Dan Stough <[email protected]> Co-authored-by: ilpianista <[email protected]>
* chore: add license to gateways files * feat(crds): add support for retryOn in service router Co-authored-by: ilpianista <[email protected]> --------- Co-authored-by: ilpianista <[email protected]>
* chore: add license to gateways files * feat(crds): add support for retryOn in service router Co-authored-by: ilpianista <[email protected]> --------- Co-authored-by: ilpianista <[email protected]>
Changes proposed in this PR:
retryOn
field that is missing from the CRD.Closes #3207
How I've tested this PR: Unit tests.
How I expect reviewers to test this PR: 🔍
Checklist: