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
{{ message }}
This repository was archived by the owner on May 25, 2023. It is now read-only.
You could check scheduler log. It might be because node resource is not enough for 6(minMember) pods. You could set the minMemeber to 2 or set pod's spec's request cpu to 0.1, and try it again.
is it possible you missed this last Note in second step
NOTE: kube-batch need to collect cluster information(such as Pod, Node, CRD, etc) for scheduling, so the service account used by the deployment must have permission to access those cluster resources, otherwise, kube-batch will fail to startup.
For users who are not familiar with Kubernetes RBAC, please copy the example/role.yaml into $GOPATH/src/github.com/kubernetes-sigs/kube-batch/deployment/kube-batch/templates/ and reinstall batch.
I faced the same issue while trying it for the first time, after adding the role.yaml my deployment was fine.
Uh oh!
There was an error while loading. Please reload this page.
I installed the kube-batch V0.4.1 in my local k8s cluster recently, And i want to run the example given by the https://github.com/kubernetes-sigs/kube-batch/blob/master/doc/usage/tutorial.md
but the pod is alaways pending.
here is the yaml
After i created the yaml , it showed:


but the pod is always pending.
i used the "kubectl describe pod " and "kubectl logs " command , but still have no idea what wrong.
so i want to know how to see the logs when kube-batch Schedule a job. Can anyone give me some advice?
Anything else we need to know?:

The result of "kubectl describe pod" command:
Environment:
Kubernetes version (use
kubectl version
): 1.13.41 master 3 node
OS (e.g. from /etc/os-release): ubuntu 16.04
kube-batch version: V0.4.1
The text was updated successfully, but these errors were encountered: