Changed ray README.md

[hansinikarunarathne]

Pull Request Template for Kubeflow manifests Issues

✏️ A brief description of the changes

I changed create namespace of ray cluster README.md

✅ Contributor checklist

• Make sure you have tested with kustomize. See Installation Prerequisites
• All the commits have been signed-off (To pass the DCO check)

---

You can join the CNCF Slack and access our meetings at the Kubeflow Community website. Our channel on the CNCF Slack is here #kubeflow-platform.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign juliusvonkohout for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• contrib/ray/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hansinikarunarathne]

@juliusvonkohout I made the requested change.

[juliusvonkohout]

Hello, I see the v1.7 branch mentioned in a lot of places. Please do a thorough check of the readme.

[hansinikarunarathne]

Hello, I see the v1.7 branch mentioned in a lot of places. Please do a thorough check of the readme.

Can you explain it more? I can not understand what you mean

[juliusvonkohout]

For example there is

manifests/contrib/ray/README.md

Line 38 in fd32075

## Step 1: Install Kubeflow v1.7-branch

manifests/contrib/ray/README.md

Line 41 in fd32075

* Install all Kubeflow official components and all common services using [one command](https://github.com/kubeflow/manifests/tree/v1.7-branch#install-with-a-single-command).

and many more.

Sometimes it also talks about 1.9. I would rather go for the master branch in all places.

So just a general cleanup / renovation of the documentation.

[juliusvonkohout]

Also https://github.com/kubeflow/manifests/blob/master/contrib/ray/kuberay-operator/base/kustomization.yaml should be updated to be a proper kustomization file as the other ones

I think the ordering is different from other kustomization files and it is missing

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

[juliusvonkohout]

To be continued after December 10 by @hansinikarunarathne

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[juliusvonkohout]

Not stale

[juliusvonkohout]

Is anyone interested in forking and continuing this PR ?

[akagami-harsh]

@juliusvonkohout , I would be happy to pick up

[juliusvonkohout]

@juliusvonkohout , I would be happy to pick up

Amazing, just forking with the original commits and using LLMs should do most of the work for you.

[juliusvonkohout]

closed in favor of #2976