-
Notifications
You must be signed in to change notification settings - Fork 176
Helm fix #1540
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
Helm fix #1540
Conversation
Signed-off-by: Nir Rozenbaum <[email protected]>
Signed-off-by: Nir Rozenbaum <[email protected]>
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This is a critical bug for the release |
/lgtm |
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.
/lgtm
@Gregory-Pereira: changing LGTM is restricted to collaborators In response to this:
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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Gregory-Pereira, nirrozenbaum The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* bug fix in helm chart Signed-off-by: Nir Rozenbaum <[email protected]> * comment Signed-off-by: Nir Rozenbaum <[email protected]> --------- Signed-off-by: Nir Rozenbaum <[email protected]>
What type of PR is this?
/kind bug
What this PR does / why we need it:
This is a critical bug fix. currently it's not possible to use helm chart and get an inference pool without the app label because we use it in values.yaml.
this PR is fixing the issue. labels should be set through the helm install command.
Which issue(s) this PR fixes:
Fixes #1539
Does this PR introduce a user-facing change?: