add role rbac and add add guide (#7091)

This commit is contained in:
Qstar
2020-02-10 11:03:15 -08:00
committed by GitHub
parent 83c4e947c7
commit 52ed42635f
4 changed files with 95 additions and 8 deletions
+18 -7
View File
@@ -115,28 +115,39 @@ Below gives a guide for user to submit RayCluster step by step:
kustomize build config/crd | kubectl apply -f -
```
### Deploy controller in the configured Kubernetes cluster in ~/.kube/config
* For this version controller will run in system namespace, which maybe can't be tolerated in production.
### Build manager docker image
View Makefile for more command and info.
```shell script
make docker-build
```
### Push manager docker image to some docker repo
View Makefile for more command and info.
```shell script
make docker-push
```
### Deploy the controller in the configured Kubernetes cluster in ~/.kube/config
* For this version controller will run in ray-operator-system namespace, which maybe can't be tolerated in production.
* We will add more detailed RBAC file to control the namespace used in production, and the controller will run in that namespace to control the permission.
* Also we will provide the more detailed guide for user to run in a controlled way.
* Also, we will provide the more detailed guide for user to run in a controlled way.
```shell script
cd config/manager
kustomize build config/default | kubectl apply -f -
```
### Submit RayCluster to Kubernetes
```shell script
kubectl create -f config/samples/ray_v1_raycluster.mini.yaml
kubectl create -f config/samples/ray_v1_raycluster.mini.yaml -n ray-operator-system
```
### Apply RayCluster to Kubernetes
```shell script
kubectl apply -f config/samples/ray_v1_raycluster.mini.yaml
kubectl apply -f config/samples/ray_v1_raycluster.mini.yaml -n ray-operator-system
```
### Delete RayCluster to Kubernetes
```shell script
kubectl delete -f config/samples/ray_v1_raycluster.mini.yaml
kubectl delete -f config/samples/ray_v1_raycluster.mini.yaml -n ray-operator-system
```
### Build with bazel