-
Couldn't load subscription status.
- Fork 185
Add Install Gateway section in Getting Started Latest guide #1759
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
base: main
Are you sure you want to change the base?
Add Install Gateway section in Getting Started Latest guide #1759
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dharaneeshvrd The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@dharaneeshvrd can you please rebase? |
1e022b2 to
9240af2
Compare
|
@nirrozenbaum Done, can you please take a look? |
|
@dharaneeshvrd really apologize, had unexpected urgent tasks and I didn't get to review it last week and now rebase is needed again.. can you please rebase? 🙏 |
- Move instructions from the Deploy an Inference Gateway section describing installation of Gateway API CRDs and provider specific GWs Signed-off-by: Dharaneeshwaran Ravichandran <dharaneeshwaran.ravichandran@ibm.com>
9240af2 to
bdcd2d1
Compare
|
@nirrozenbaum |
|
@danehans If you get a chance, can you please take a look at the changes? |
| ``` | ||
| Choose one of the following options to deploy an Inference Gateway. | ||
|
|
||
| === "GKE" |
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 section doesn't seem to be identical to the released quickstart
What type of PR is this?
What this PR does / why we need it:
#1752
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: