Why is max pods set to 0 on OSX? Are you running a kubelet built from HEAD?

@vishh yes, HEAD.

Capacity['pods'] wasn't set at all, which was the problem.

May be the fix is to set max pods when cadvisor is not running?

Overall, making kubelet control a docker daemon on another host doesn't
sound like a use case that is being considered whenever node design
decisions are being made.

On Tue, May 26, 2015 at 1:51 PM, Saad Ali [email protected] wrote:

Assigned #8826
#8826 to @vishh
https://github.com/vishh.

—
Reply to this email directly or view it on GitHub
#8826 (comment)
.

I think this is a scheduling issue, with the scheduler running in a process in OSX just like Kubelet.

The node has no pod capacity (CPU and memory set to 0 on line 1836). Are you suggesting I move the fix to that section?

I'm looking for advice for how to fix this (if this is a bug worth fixing) :)

Yes. Can you try setting Capacity[pods] here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/kubelet.go#L1836
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/kubelet.go#L1836
?

On Tue, May 26, 2015 at 2:14 PM, Mark Turansky [email protected]
wrote:

I think this is a scheduling issue, with the scheduler running in a
process in OSX just like Kubelet.

The node has no pod capacity (CPU and memory set to 0 on line 1836). Are
you suggesting I move the fix to that section?

I'm looking for advice for how to fix this (if this is a bug worth fixing)
:)

—
Reply to this email directly or view it on GitHub
#8826 (comment)
.

@vishh It is moved, per your request.

LGTM.

CL fails.

poke when CI passes and we can LGTM then

@thockin Poke. Travis just returned green.

@thockin poke again, rebased, and all returned green (the Jenkins builder flaked last time)