[Feature] Ascertain the minimum essential rayStartParams and make rayStartParams optional

[Yicheng-Lu-llll]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

As #368 suggests, Figure out the minimum configurations required for a successful Ray start and make rayStartParams optional.

• : Review the Ray start options (refer to Ray start documentation) and provide explanations for each option, as well as determine their necessity for inclusion in the default configurations.

[WIP]Test:

rootPath="/home/ubuntu/kuberay"
outputFile="./original-ray-start-command.txt"
cd $rootPath

for file in $rootPath/ray-operator/config/samples/ray-cluster*.yaml
do
  echo "###########################"  >> $outputFile

  echo $file >> $outputFile

  kubectl apply -f $file
  kubectl get  $(kubectl get pods -o=name | grep head) -o yaml | grep "ulimit -n 65536; ray start" >> $outputFile
  kubectl get  $(kubectl get pods -o=name | grep worker) -o yaml | grep "ulimit -n 65536; ray start" >> $outputFile
  kubectl delete -f $file

  echo "###########################\n"  >> $outputFile
done

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!