Closed kuaikuai closed 3 months ago
Hi @kuaikuai I'm facing the same issue, did you find the cause or any solution to this?
@heiruwu My Ray cluster was updated from version 1.0.0 to version 1.1.0. However, when the kuberay-operator and kuberay-apiserver were uninstalled using Helm, the custom resource definitions (CRDs) were not removed. In version 1.1.0 of Kuberay, the CRDs have a new configuration parameter called "NumOfHosts" with a default value of 1, which was not present in version 1.0.0. To resolve this, I deleted the CRDs and reinstalled version 1.1.0.
To delete the CRDs, I used the following commands:
kubectl delete crd rayclusters.ray.io -n mynamespace kubectl delete crd rayjobs.ray.io -n mynamespace kubectl delete crd rayservices.ray.io -n mynamespace
thank you so much! this is exactly what I needed. I read it somewhere that the CRDs need to be manually deleted when upgrading kuberay from 1.0.0->1.1.0, but totally forgot about it
Search before asking
KubeRay Component
ray-operator, apiserver
What happened + What you expected to happen
use kuberay 1.1.0
There were no small-wg pods in k8s.
Reproduction script
Anything else
No response
Are you willing to submit a PR?