[Feature]Run kuberay in a single namespace

[wilsonwang371]

Why are these changes needed?

Run kuberay in a single namespace.

Instead of setup kuberay using

kubectl apply -k "github.com/ray-project/kuberay/manifests/cluster-scope-resources"
kubectl apply -k "github.com/ray-project/kuberay/manifests/base"

now we use

kubectl apply -k "github.com/ray-project/kuberay/manifests/cluster-scope-resources"
kubectl apply -k "github.com/ray-project/kuberay/manifests/singe-namespace"

Related issue number

#227

Checks

• I've made sure the tests are passing.
• Testing Strategy
  • Unit tests
  • Manual tests
  • This PR is not tested :(

[wilsonwang371]

cc @Jeffwan @scarlet25151

[Jeffwan]

Can we revert the rename changes? The major reason is the current folder structure is from kubebuilder output. Sometimes, when we upgrade the kubebuilder etc, we still like the structure to be working and that's why we want them remain the same.

[Jeffwan]

For the changes here, I feel we can override the setting at the root kustomization level?

[Jeffwan]

Let's have a discussion tomorrow on this.

[wilsonwang371]

now we use kustomize to patch clusterrole clusterrolebinding with a very minimal code change.

cc @Jeffwan

[Jeffwan]

What about the name? Will we have cluster-role created in namespace scope?

[wilsonwang371]

this will convert all cluster-role to role with namespace.

[Jeffwan]

BTW, This is kind of tricky. Besides Kind itself, we need to make sure apiversion is correct as well. There might be other issues like CRB doesn't have namespace field but RB does.

I think it's still acceptable at this moment. Let's do the refactor later if it lack of flexibility in the future.

[DmitriGekhtman]

kubectl apply -k "github.com/ray-project/kuberay/manifests/cluster-scope-resources"
kubectl apply -k "github.com/ray-project/kuberay/manifests/single-namespace"

I guess an admin may be the one to run the first step. A user with restricted permissions would run the second step.

[wilsonwang371]

kubectl apply -k "github.com/ray-project/kuberay/manifests/cluster-scope-resources"
kubectl apply -k "github.com/ray-project/kuberay/manifests/single-namespace"

I guess an admin may be the one to run the first step. A user with restricted permissions would run the second step.

yes, I should make this more clear. I updated the README document