[Bug] .status.availableWorkerReplicas incorrectly counts head Pods
#885
Assignees
Labels
bug
Something isn't working
Comments
|
@kevin85421 @Jeffwan I'm happy to work on this if the bug report looks good to you. Probably a straight forward fix. |
|
Thanks, @davidxia! |
davidxia
added a commit
to davidxia/kuberay
that referenced
this issue
Jan 28, 2023
to not count head Pods. closes ray-project#885
davidxia
added a commit
to davidxia/kuberay
that referenced
this issue
Jan 29, 2023
to not count head Pods. closes ray-project#885
davidxia
added a commit
to davidxia/kuberay
that referenced
this issue
Jan 30, 2023
to not count head Pods. closes ray-project#885
davidxia
added a commit
to davidxia/kuberay
that referenced
this issue
Feb 3, 2023
to not count head Pods. closes ray-project#885
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
KubeRay Component
ray-operator
What happened + What you expected to happen
kubectl get raycluster my-cluster -o yamlshows.status.availableWorkerReplicasas always one more than.status.desiredWorkerReplicas. I think the operator is incorrectly including head Pods inavailableWorkerReplicas.see previous comment
Reproduction script
Create a RayCluster with workers. Run
kubectl get raycluster my-cluster -o yamland look at.status.Anything else
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: