You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
[A clear and concise description of what the bug is, and what commands you ran.]
As we introduced a new SpaceWeighted scheduler, and it can do better LVM volume binding, see the details in the PR below: #178
But the default is still CapacityWeighted as we set the default value when initialize the params.
What did you expect to happen:
Use SpaceWeighted as the default scheduler.
The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other Pastebin is fine.)
What steps did you take and what happened:
[A clear and concise description of what the bug is, and what commands you ran.]
As we introduced a new SpaceWeighted scheduler, and it can do better LVM volume binding, see the details in the PR below:
#178
But the default is still CapacityWeighted as we set the default value when initialize the params.
What did you expect to happen:
Use SpaceWeighted as the default scheduler.
The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other Pastebin is fine.)
kubectl logs -f openebs-lvm-controller-0 -n kube-system -c openebs-lvm-plugin
kubectl logs -f openebs-lvm-node-[xxxx] -n kube-system -c openebs-lvm-plugin
kubectl get pods -n kube-system
kubectl get lvmvol -A -o yaml
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
): K8S 1.20.x/etc/os-release
):The text was updated successfully, but these errors were encountered: