-
Notifications
You must be signed in to change notification settings - Fork 45
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
Separate and organize endpoint selector manifests #202
Comments
@ahg-g PTAL at #217. I setup e2e by simply running Envoy with a static config. A user can use the following steps to run the Endpoint Selector extension:
|
We originally had a static config, and working with the Envoy folks to find something that was a little more flexible. The problem with the static config is that it works for the one case, but if a user wants to add another pool or change the httpRoute, they have to go mess with the xDS API which can be a daunting task, esp if you're area of expertise is inference/ML See the conversation in: #18 |
I found the barrier to entry quite high for new users wanting to explore the project. To address this, I created Issue #219 to track the problems with the POC README. While the README lists six steps, a new user must complete approximately ten steps to test EPP. Typically, a quickstart guide focuses on a narrow use case, is executable with a single command, and has minimal dependencies. Although we could wrap the installation process in a script, this would not address the complexity posed by the numerous resource types—particularly custom resources—that users must understand to modify or deviate from the example installation. To lower the barrier for new users, we should reconsider supporting a static configuration in the quickstart guide. This approach would simplify the onboarding process, while advanced users could be directed to the EG installation guide at the end of the quickstart for further customization. |
I think we should have two guides, a quick start where the envoy setup is bundled in one file, and a detailed guide where we break things down, wdyt? |
@ahg-g Yes, I agree. This is what I intended to convey in my previous comment. The quickstart should consist of a single |
Great! @danehans would you like to send a quick start guide once we merge #221?
I think we can postpone answering this question for now, but I would be in favor of having the guides in the gateway repo with a reference to it from this repo. |
@ahg-g I believe recent PRs resolved this issue. If you agree, please close this issue. Otherwise, provide a brief explanation of the remaining work. |
We have a bunch of yamls to install the ext-proc and a sample inferencepool and inferencemodel, I think we need to organize the manifests into three categories since not all are needed at the same time:
/cc @danehans
The text was updated successfully, but these errors were encountered: