Remove ElasticConfig from Service #224
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
InftyAI-Agent
added
needs-triage
kerthcet
force-pushed
the
feat/fungibility
branch
from
0ad083d to
23e4529
Compare
|
/kind cleanup |
InftyAI-Agent
added
cleanup
Signed-off-by: kerthcet <[email protected]>
kerthcet
force-pushed
the
feat/fungibility
branch
from
23e4529 to
70b4a3b
Compare
InftyAI-Agent
removed
the
lgtm
|
/lgtm |
InftyAI-Agent
added
the
lgtm
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it
ElasticConfig is used for simplify configurations when using with Playground, not user wants to use inferenceService, they should configure the HPA directly.
Which issue(s) this PR fixes
Fixes #
Special notes for your reviewer
Does this PR introduce a user-facing change?