Kubernetes on CoreOS: Proxy service max out CPU

7/18/2014

I have installed Kubernetes on CoreOS under VirtualBox Vagrant. I notice that when running, each of the cluster nodes uses 100% CPU and the journalctl shows the same message being repeated:

Couldn't read file: /tmp/proxy_config : open /tmp/proxy_config: no such file or directory. 

This seems to be related to the kubernetes-proxy.service. When I stop the service the CPU usage goes to normal and the logging stops. I read somewhere that the proxy is required on the minions not the master, but I lack understanding of the overall architecture to really know what this means. I guess, my question is: is the proxy required to run Kubernetes on CoreOS and if so, is there some configuration that must happen to make this problem go away?

-- user1860138
coreos
docker
kubernetes

2 Answers

8/13/2014

This was a bug that had numerous reports. It's been fixed.

-- lavalamp
Source: StackOverflow

7/24/2014

The proxy is required on the nodes(minion). Here is a link to Google's current design documents to help: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/DESIGN.md

-- Marlon Bailey
Source: StackOverflow