jdef

disable default kubelet OOM-adjuster for k8sm

1

xref https://github.com/kubernetes/kubernetes/pull/20749 related to #355 disabling OOM adjustment by kubelet until Mesos provides better API support for OOM adjustment.

k8sm controller manager should use subcontroller options

1

upstream has finally split out subcontroller options: https://github.com/kubernetes/kubernetes/pull/20702/files

make TC "build release" work again

1

xref https://github.com/kubernetes/kubernetes/pull/20691

in cluster/mesos/docker, k8s cgroup-based pid lister is broken

2

Kubernetes (manager.go in kubelet/dockertools) uses k8s.io/pkg/util/procfs to list procs in a cgroup in order to set OOM adjustments. the default implementation looks at the devices cgroup and attempts to scrape...

Back in Sept 2015 Marathon introduced support for reviving offers into its scheduling algorithm: """ When Marathon detects new tasks that it has to launch, it will now explicitly request...

mesos will introduce `TASK_KILLING` or something like it to better support graceful task termination. once it lands we should more closely integrate support for that with k8s graceful pod deletion.

k8s cross compiles for a ton of platforms now and it (a) takes a long time, and; (b) chews up a ton of disk space. we need to contribute some...

k8s socket listeners default to 0.0.0.0, is that too open?

2

I don't see anywhere in the k8s codebase where this value is overwritten, but it is used by the kubelet: https://github.com/GoogleCloudPlatform/kubernetes/blob/9e921cc7f8dc396832edfff28fcc9cd68fc06d09/pkg/kubelet/kubelet.go#L321 Does it make sense to clobber this default (0.0.0.0)...

upstream has converted their apps to use "options" packages for command line params, separating the command line config from the app itself.