This section walks through how to build and test the operator in a running Kubernetes cluster.
| software | version | link |
|---|---|---|
| kubectl | v1.21.0+ | download |
| go | v1.16+ | download |
| docker | 19.03+ | download |
The instructions assume you have access to a running Kubernetes cluster via kubectl. If you want to test locally, consider using Minikube.
For a local kind environment setup, you can follow the Jupyter Notebook example: KubeRay-on-kind.
make build
Once building is finished, push it to DockerHub so it can be pulled down and run in the Kubernetes cluster.
IMG=kuberay/operator:nightly make docker-buildNote: replace
kuberay/operator:nightlywith your own registry, image name and tag.
make test
example results:
✗ make test
...
go fmt ./...
go vet ./...
...
setting up env vars
? github.com/ray-project/kuberay/ray-operator [no test files]
ok github.com/ray-project/kuberay/ray-operator/api/v1alpha1 0.023s coverage: 0.9% of statements
ok github.com/ray-project/kuberay/ray-operator/controllers 9.587s coverage: 66.8% of statements
ok github.com/ray-project/kuberay/ray-operator/controllers/common 0.016s coverage: 75.6% of statements
ok github.com/ray-project/kuberay/ray-operator/controllers/utils 0.015s coverage: 31.4% of statements
Build and apply the CRD:
make install
Deploy the manifests and controller
IMG=kuberay/operator:nightly make deploy
Note: remember to replace with your own image