-
Notifications
You must be signed in to change notification settings - Fork 118
Add ingress2gateway information in Getting Started guide #1056
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
FYI: You also need one review from docs team to check language and formatting |
Co-authored-by: bjee19 <139261241+bjee19@users.noreply.github.com>
@ADubhlaoich Do you think this makes sense where it is? |
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.
Generally LGTM: I've made some edit suggestions
If this is a use case we want to push, it shouldn't be buried in the Get started guide. It should probably be in the install section, and include some detail about why someone would want to do this, and what the differences between the Ingress and Gateway APIs are.
Co-authored-by: Alan Dooley <github@adubhlaoi.ch>
Co-authored-by: Alan Dooley <github@adubhlaoi.ch>
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.
approved if Alan's comments are resolved
Co-authored-by: Alan Dooley <github@adubhlaoi.ch>
![]() looks good to me and all your suggestions applied @ADubhlaoich |
Proposed changes
Add ingress2gateway information in Getting Started guide
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩