-
Notifications
You must be signed in to change notification settings - Fork 118
Design evaluation #2
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
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.
15d1089
to
710611a
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.
@f5yacobucci looks good!
small note:
note sure if this https://github.com/nginxinc/nginx-gateway-kubernetes/blob/710611a70108f7f1f7875d75b19012b41f3e0dbf/design/gateway-evaluation.md#where-applicable-gateway-evaluation-will-write-status-updates-to-gateway-api-resources-according-to-specification-requirements-each-update-is-not-recorded-in-these-flows and https://github.com/nginxinc/nginx-gateway-kubernetes/blob/710611a70108f7f1f7875d75b19012b41f3e0dbf/design/gateway-evaluation.md#notethis-is-not-a-design-requirement-and-may-not-be-met-as-a-delivery-constraint were supposed to be section headers
First draft of NGINX Gateway evaluation engineering document.
- Removed some implementation details around technologies - Moved code layout into Appendix - Added more startup constraints (no traffic passing, init state conflict resolution) - Added Service and Endpoints requirements - Grammar clean up
710611a
to
add0972
Compare
* Create gateway-evaluation.md Draft of NGINX Gateway evaluation engineering document.
NGINX Gateway initial evaluation engineering document.