-
Notifications
You must be signed in to change notification settings - Fork 402
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
[0.4.0 Pick] Remove ingress.enabled field from operator chart. #813
Closed
DmitriGekhtman
wants to merge
15
commits into
ray-project:master
from
DmitriGekhtman:dmitri/pick-helm-cleanup
Closed
[0.4.0 Pick] Remove ingress.enabled field from operator chart. #813
DmitriGekhtman
wants to merge
15
commits into
ray-project:master
from
DmitriGekhtman:dmitri/pick-helm-cleanup
Conversation
This file contains 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
* Fix nil pointer dereference (ray-project#429) Signed-off-by: Kevin Su <[email protected]> * Fix wrong ray start command (ray-project#431) Signed-off-by: Kevin Su <[email protected]> * Add ray state api doc link in ray service doc (ray-project#428) * Add ray state api doc link in ray service doc * Update doc * update * [doc] Fix config typos Signed-off-by: Dmitri Gekhtman <[email protected]> Fixes a couple of typos in recently introduced sample configs. * Add http resp code check for kuberay (ray-project#435) * Clean up example samples (ray-project#434) This PR cleans up the "complete" and "autoscaler" sample yamls a bit. Unnecessary pod spec fields are removed without sacrificing the completeness of the examples. The idea is to make the configuration look less intimidating. Signed-off-by: Dmitri Gekhtman <[email protected]> * Add more env for RayService head or worker pods (ray-project#439) * fix: worker node can't connect to head node service (ray-project#445) Signed-off-by: Kevin Su <[email protected]> * helm-chart/ray-cluster: allow head autoscaling (ray-project#443) Also allow setting rayVersion Signed-off-by: Christos Kotsis <[email protected]> * Disable async serve handler in Ray Service cluster (ray-project#447) * Add wget timeout to probes (ray-project#448) * Enable tests against release-0.3 branch Signed-off-by: Kevin Su <[email protected]> Signed-off-by: Dmitri Gekhtman <[email protected]> Signed-off-by: Christos Kotsis <[email protected]> Co-authored-by: Kevin Su <[email protected]> Co-authored-by: bruce <[email protected]> Co-authored-by: Dmitri Gekhtman <[email protected]> Co-authored-by: Christos Kotsis <[email protected]> Co-authored-by: Yi Cheng <[email protected]> Co-authored-by: Wilson Wang <[email protected]>
…or (ray-project#457) (ray-project#458) Co-authored-by: Yi Cheng <[email protected]>
…ay-project#464) (ray-project#477) Co-authored-by: Edward Oakes <[email protected]> This picks ray-project#464 into the KubeRay 0.3.0 branch. That PR changed the names of some config fields to match Ray Serve's API.
* Update helm chart version to 0.3.0 (ray-project#461) * helm-charts/ray-cluster: Allow extra workers (ray-project#451) * helm-charts/ray-cluster: Allow extra workers We can not set additional workers with the current helm chart. There are some PRs that aim to fix this but they appear to be stale ray-project#266 We wanted to keep untouched the default worker that is already included in the helm chart but allow the addition of new workers. The changes are adding the following logic: - Allow to disable the default worker group, if needed, via worker.disabled = true - Allow to set additional workers by using the extraWorkers map The extraWorkers map has a different structure compared to the default worker because we wanted to add additional flexibility. Due to that, some variables in the extraWorkers have different naming (which matches the name of the related CRD attributed) Note: PR was done to support additional workers in the infrastructure of Metrika.co * Sync up helm chart's role (ray-project#472) Co-authored-by: chenyu.jiang <[email protected]> * Document the raycluster status (ray-project#473) Co-authored-by: chenyu.jiang <[email protected]> Co-authored-by: Christos Kotsis <[email protected]> Co-authored-by: Chenyu Jiang <[email protected]> Co-authored-by: chenyu.jiang <[email protected]>
* Fix panic in cleanupInvalidVolumeMounts (ray-project#481) * fix * assert * refine * Properly convert unix time into meta time (ray-project#480) * Add timeout to the query parameters Signed-off-by: Kevin Su <[email protected]> * Properly convert unix time into meta time Signed-off-by: Kevin Su <[email protected]> Signed-off-by: Kevin Su <[email protected]> Signed-off-by: Kevin Su <[email protected]> Co-authored-by: WanXing Wang <[email protected]> Co-authored-by: Kevin Su <[email protected]>
) * Two more configs updated to 2.0.0 Signed-off-by: Dmitri Gekhtman <[email protected]> * autoscaler, job, service Signed-off-by: Dmitri Gekhtman <[email protected]> Signed-off-by: Dmitri Gekhtman <[email protected]>
Removes the unused ingress.Enabled field from the operator Helm chart.
wrong branch |
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.
Why are these changes needed?
Picking #812 into the release branch.
FYI @kevin85421 @sihanwang41
Related issue number
Checks