-
Notifications
You must be signed in to change notification settings - Fork 176
fix guides index md #1531
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
fix guides index md #1531
Conversation
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: learner0810 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 |
Hi @learner0810. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Hi @learner0810, from my understanding seems like the problem that this PR is trying to address is that when http route is created the inference pool still doesn't exist and in order to fix it one should switch the creation order. is that correct? please pay attention that we have an open PR #1524 that is about to get merged and is fixing this issue. |
Sorry, I didn't notice that anyone had already submitted a pr |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Because the inferencepool resource has not been created yet, the ResolvedRefs conditions in the httproute status cannot be true,We should install inferencepool charts first and then check the status of httproute
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: