Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Ray-operator deploy using helm failed on minikube #136

Closed
2 tasks done
asm582 opened this issue Jan 25, 2022 · 5 comments · Fixed by #144
Closed
2 tasks done

[Bug] Ray-operator deploy using helm failed on minikube #136

asm582 opened this issue Jan 25, 2022 · 5 comments · Fixed by #144
Assignees
Labels
bug Something isn't working

Comments

@asm582
Copy link
Contributor

asm582 commented Jan 25, 2022

Search before asking

  • I searched the issues and found no similar issues.

KubeRay Component

ray-operator

What happened + What you expected to happen

Running
helm install kuberay-operator . --values values.yaml --namespace kuberay-operator --create-namespace in directory kuberay/helm-chart/kubray-operator fails.

container logs:

kubectl logs kubray-operator-5f58f68578-ff8ls -n kuberay-operator
2022-01-25T12:53:24.419Z        INFO    setup   the operator    {"version:": ""}
2022-01-25T12:53:24.966Z        INFO    controller-runtime.metrics      metrics server is starting to listen    {"addr": ":8080"}
2022-01-25T12:53:24.967Z        INFO    setup   starting manager
2022-01-25T12:53:24.967Z        INFO    controller-runtime.manager      starting metrics server {"path": "/metrics"}
2022-01-25T12:53:24.967Z        INFO    controller-runtime.manager.controller.raycluster-controller     Starting EventSource    {"reconciler group": "ray.io", "reconciler kind": "RayCluster", "source": "kind source: /, Kind="}
I0125 12:53:26.113808       1 request.go:645] Throttling request took 1.047938671s, request: GET:https://10.96.0.1:443/apis/batch/v1?timeout=32s
2022-01-25T12:53:26.915Z        ERROR   controller-runtime.source       if kind is a CRD, it should be installed before calling Start   {"kind": "RayCluster.ray.io", "error": "no matches for kind \"RayCluster\" in version \"ray.io/v1alpha1\""}
github.com/go-logr/zapr.(*zapLogger).Error
        /go/pkg/mod/github.com/go-logr/[email protected]/zapr.go:132
sigs.k8s.io/controller-runtime/pkg/source.(*Kind).Start
        /go/pkg/mod/sigs.k8s.io/[email protected]/pkg/source/source.go:117
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1
        /go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:159
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start
        /go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:205
sigs.k8s.io/controller-runtime/pkg/manager.(*controllerManager).startRunnable.func1
        /go/pkg/mod/sigs.k8s.io/[email protected]/pkg/manager/internal.go:691
2022-01-25T12:53:26.915Z        ERROR   setup   problem running manager {"error": "no matches for kind \"RayCluster\" in version \"ray.io/v1alpha1\""}
github.com/go-logr/zapr.(*zapLogger).Error
        /go/pkg/mod/github.com/go-logr/[email protected]/zapr.go:132
main.main
        /workspace/main.go:82
runtime.main
        /usr/local/go/src/runtime/proc.go:204

Reproduction script

  • Install minikube and start with command:

minikube start --cpus 16 --memory 32768

  • Run helm install kuberay-operator . --values values.yaml --namespace kuberay-operator --create-namespace in directory kuberay/helm-chart/kubray-operator

Anything else

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!
@asm582 asm582 added the bug Something isn't working label Jan 25, 2022
@asm582 asm582 changed the title [Bug] Ray-operator geploy operator failed on minikube [Bug] Ray-operator deploy operator failed on minikube Jan 25, 2022
@chenk008
Copy link
Contributor

chenk008 commented Jan 25, 2022

Sorry for missing CRD, I will add it as soon as possible.
Please use the below command to work around

kubectl apply -k "kuberay/ray-operator/config/crd"

@chenk008 chenk008 self-assigned this Jan 25, 2022
@asm582
Copy link
Contributor Author

asm582 commented Jan 26, 2022

Thanks @chenk008

I deployed ray cluster using command:

helm install my-release . --values values.yaml --namespace ray-system --create-namespace
I see below-installed helm charts:

(base) [asmalvan@learn-ray-2 ray-cluster]$ helm list --all-namespaces
NAME                    NAMESPACE               REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
kuberay-operator        kuberay-operator        1               2022-01-25 09:00:29.040162738 -0600 CST deployed        kubray-operator-0.1.0   1.0        
my-release              ray-system              1               2022-01-25 09:01:50.817172183 -0600 CST deployed        ray-cluster-0.1.0       1.0        
ray-cluster             ray-system              1               2022-01-26 07:44:06.503960301 -0600 CST deployed        ray-cluster-0.1.0       1.0        
(base) [asmalvan@learn-ray-2 ray-cluster]$ kubectl get pods -n ray-system
No resources found in ray-system namespace.

I do not see any pods in the namespaces, can you please suggest what am I missing here?

@asm582 asm582 changed the title [Bug] Ray-operator deploy operator failed on minikube [Bug] Ray-operator deploy using helm failed on minikube Jan 26, 2022
@Jeffwan
Copy link
Collaborator

Jeffwan commented Jan 27, 2022

@chenk008 Can you help cut a PR to improve the helm charts? Let's also include a quick helm command in the README.md. I did minor doc refactor in README.md and it has a quick start section with both kustomize and helm sections.

@chenk008
Copy link
Contributor

chenk008 commented Feb 2, 2022

@asm582 Sorry for delay reply. Please add rayclusters resource into role.yaml https://github.com/ray-project/kuberay/blob/eba8da689d23a20674bb6155b26679840bcf7be8/helm-chart/kubray-operator/templates/role.yaml, and re-install the kuberay-operator.

@chenk008
Copy link
Contributor

chenk008 commented Feb 2, 2022

@Jeffwan I have created a pull request to fix this issue, PTAL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants