remove ray-cluster.getting-started.yaml #987
Merged
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
Signed-off-by: Yicheng-Lu-llll <[email protected]>
kevin85421
approved these changes
Mar 24, 2023
lowang-bh
pushed a commit
to lowang-bh/kuberay
that referenced
this pull request
Sep 24, 2023
remove ray-cluster.getting-started.yaml
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?
Each configuration YAML file (files in ray-operator/config/samples) should serves a specific purpose:
alb-ingress.yaml: Used in example for AWS Application Load Balancer (ALB) Ingress support on AWS EKS
ray-cluster.autoscaler.large.yaml: used for demonstrating KubeRay's Ray autoscaler integration with resource configuration for production use-cases.
ray-cluster.autoscaler.yaml: used for demonstrating KubeRay's Ray autoscaler integration
ray-cluster.complete.large.yaml: used for showing all available custom resource properties with resource configuration for production use-cases.
ray-cluster.complete.yaml: used for showing all available custom resource properties
ray-cluster.external-redis.yaml: an example configuration that enables Ray GCS fault tolerance.
ray-cluster.head-command.yaml: an example configuration that demonstrates how to specify the container command for the head pod before ray start and after ray start.
ray-cluster.heterogeneous.yaml: an example configuration with heterogenous worker types.
ray-cluster.ingress.yaml: an example configuration that enables built-in ingress.
ray-cluster.separate-ingress.yaml: an example configuration that shows how to manually setting up customized NGINX Ingress
ray_v1alpha1_rayjob.yaml: an sample rayjob configuration.
ray_v1alpha1_rayservice.yaml: an sample rayservice configuration.
Consider removing the following files, as they lack a clear purpose:
Related issue number
Checks